Kazutaka YOKOTA wrote:
>
> I have had reports on similar lockup in both 4.0-CURRENT and 3.X.
> I personally have not been able to reproduce it, but now my new sand box
> machine exhibits this problem occasionally.
>
> The I/O access to the AT keyboard by the atkbd driver have not changed
> much
In message <[EMAIL PROTECTED]> Bruce Evans
writes:
: > So I should back this out? I didn't do a 3.3 buildworld.
:
: Of course.
OK. I'm doing a 3.3 buildworld right now on a virgin 3.3R system.
I'll let you know what happens with that. If it is a problem at all,
then I'll back it out (since o
> On Fri, Jan 28, 2000 at 07:07:39PM -0500, Louis A. Mamakos wrote:
> > Is it possible to bump the revision of libstdc++ (and perhaps others) so
> > that existing programs can continue to function?
>
> Nope. This is -CURRENT and this type of thing happens. And with a
> RELEASE about to happen,
On Fri, 28 Jan 2000, Warner Losh wrote:
> In message <[EMAIL PROTECTED]> Bruce Evans
>writes:
> : This breaks bootetrapping of fortran. Fortran is not built as a build-
> : tool. Only a tool to build fortran is built. This tool is like the
> : internal tools for sh and libcurses, etc. It mus
[I said about ntpd usage of sched_* functions:]
> > We should make them standard IMO.
According to John Polstra:
> I agree.
BTW, as the sched_* POSIX functions are now standard in GENERIC, I've decided
along with the upgrade to ntpd 4.0.99b to re-enable them.
--
Ollivier ROBERT -=- FreeBSD: Th
On Fri, 28 Jan 2000, John Baldwin wrote:
>...
> Solution:
>
> We need statically built install tools just like we have build tools.
> I think we should use the newer versions (i.e. static versions of the
> ones we just built under /usr/obj during buildworld that are linked
> against the new libr
In message <[EMAIL PROTECTED]> Bruce Evans
writes:
: This breaks bootetrapping of fortran. Fortran is not built as a build-
: tool. Only a tool to build fortran is built. This tool is like the
: internal tools for sh and libcurses, etc. It must be built in the host
: environment, since the ve
On Fri, 28 Jan 2000, Warner Losh wrote:
> The following has survived a make buildworld at least once. It
> optimizes buildworld a little by not building fortran as part of the
> build tools.
This breaks bootetrapping of fortran. Fortran is not built as a build-
tool. Only a tool to build fort
On Fri, Jan 28, 2000 at 07:07:39PM -0500, Louis A. Mamakos wrote:
> Is it possible to bump the revision of libstdc++ (and perhaps others) so
> that existing programs can continue to function?
Nope. This is -CURRENT and this type of thing happens. And with a
RELEASE about to happen, I don't want
On 28-Jan-00 Marcel Moolenaar wrote:
> It's also related to the kernel, where installworld is installing and
> subsequently running binaries that won't work with the current kernel. The
> same applies to installing shared binaries and running them without the
> proper libraries.
Ok, I'll buy tha
I just put a new -current on my test machine, and watched a bunch of stuff
fall over and die due to the new C++ implementation.
Is it possible to bump the revision of libstdc++ (and perhaps others) so
that existing programs can continue to function? I fear I will be
tracking down occasional bro
Are there differences in the Linux emulation from -stable -> -current?
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]On Behalf Of Brian Hechinger
> Sent: Thursday, January 27, 2000 5:34 PM
> To: [EMAIL PROTECTED]; [EMAIL PROTECTED]
> Subject: ColdFusion 4.5 RC
> > I already have patches (somewhere :-) that solve this problem. I choose
not
> > to apply these before the release. I will fix installworld after the
> > release. For now, you can use the buildkernel and installkernel targets
> > (after a buildworld) to solve the (possibly complex) dependencies
In message <[EMAIL PROTECTED]> Jeroen Ruigrok/Asmodai
writes:
: All the bits help. =)
:
: And anyways, as you said, compiling it twice seems a bit unnecessary.
:
: Feel free to commit when you're sure.
I'm sure.
I did a make buildworld make installworld. I then did a make
buildworld -DNOCLEA
-On [2128 20:00], Warner Losh ([EMAIL PROTECTED]) wrote:
>In message <[EMAIL PROTECTED]> "David O'Brien" writes:
>: I like it. If it passes a clean and -DNOCLEAN buildworld, commit that
>: baby!
>
>OK. It passes a clean buildworld + installworld. I&
sgk wrote:
> Marcel Moolenaar wrote:
> >
> > I already have patches (somewhere :-) that solve this problem. I choose not
> > to apply these before the release. I will fix installworld after the
> > release. For now, you can use the buildkernel and installkernel targets
> > (after a buildworld) to
Marcel Moolenaar wrote:
>
> I already have patches (somewhere :-) that solve this problem. I choose not
> to apply these before the release. I will fix installworld after the
> release. For now, you can use the buildkernel and installkernel targets
> (after a buildworld) to solve the (possibly co
On 28-Jan-00 Marcel Moolenaar wrote:
>> On 28-Jan-00 Jeroen Ruigrok van der Werven wrote:
>> > ===> bin/pwd
>> > install -c -s -o root -g wheel -m 555 pwd /bin
>> > install -c -o root -g wheel -m 444 pwd.1.gz /usr/share/man/man1
>> > ===> bin/rcp
>> > install -c -s -o root -g wheel -m 4555 -f
> On 28-Jan-00 Jeroen Ruigrok van der Werven wrote:
> > ===> bin/pwd
> > install -c -s -o root -g wheel -m 555 pwd /bin
> > install -c -o root -g wheel -m 444 pwd.1.gz /usr/share/man/man1
> > ===> bin/rcp
> > install -c -s -o root -g wheel -m 4555 -fschg rcp /bin
> > /usr/libexec/ld-elf.so.1:
My parallel port is back. Switching the it from 3BC to 378 made the probe
recognize it again.
Apparently the new code doesn't like the 3BC address as much as the old code..
Paul
--
Paul van der Zwan paulz @ trantor.xs4all.nl
"I think I'll move to theory, everything wor
On 28-Jan-00 Jeroen Ruigrok van der Werven wrote:
> ===> bin/pwd
> install -c -s -o root -g wheel -m 555 pwd /bin
> install -c -o root -g wheel -m 444 pwd.1.gz /usr/share/man/man1
> ===> bin/rcp
> install -c -s -o root -g wheel -m 4555 -fschg rcp /bin
> /usr/libexec/ld-elf.so.1: install: Unde
-On [2128 19:30], John Baldwin ([EMAIL PROTECTED]) wrote:
>
>> ===> bin/rcp
>> install -c -s -o root -g wheel -m 4555 -fschg rcp /bin
>> /usr/libexec/ld-elf.so.1: install: Undefined symbol "string_to_flags"
>> *** Error code 1
>>
>> Stop i
In message <[EMAIL PROTECTED]> "David O'Brien" writes:
: I like it. If it passes a clean and -DNOCLEAN buildworld, commit that
: baby!
OK. It passes a clean buildworld + installworld. I'll crank up the
-DNOCLEAN right now.
Looks like the savings aren't huge. Like 3 minutes out of 140 on my
f
On Fri, Jan 28, 2000 at 09:33:32AM -0700, Warner Losh wrote:
> This looks like a safe change to make, since we have no fortran in the
> tree that needs to get built. It doesn't disable building of fortran
> later in the build, just from building it potentially twice.
>
> Comments?
I like it. I
:Hi there,
:
: I reported a former heavy filesystem crash recently; have a look
: at:
:
:http://www.FreeBSD.org/cgi/getmsg.cgi?fetch=846852+849687+/usr/local/www/db/text/2000/freebsd-current/2123.freebsd-current
:
: I got it again.
: Meanwhile my system got updated to
: FreeBSD abc.xyz.de 4
> Ok, guys.
>
> This is another patch for the atkbd driver. I expect this one is
> better than my previous one. Remove the previous patch and try this
> one instead. Stress the keyboard (like hitting the Return key twice
> when booting the system), and see if it works.
Just in case you hadn't
It seems D. Rock wrote:
> Hi,
>
> just noticed the new sysctl variable for ata. I just wanted to
> use the new way for disabling DMA on my disk (has some strange
> problems, even under windows).
>
> Previously I just commented out the ata_dmainit() lines in
> ata_disk.c, now I wanted to set it w
Hi,
just noticed the new sysctl variable for ata. I just wanted to
use the new way for disabling DMA on my disk (has some strange
problems, even under windows).
Previously I just commented out the ata_dmainit() lines in
ata_disk.c, now I wanted to set it with sysctl:
sysctl -w hw.atamodes="pio,
The following has survived a make buildworld at least once. It
optimizes buildworld a little by not building fortran as part of the
build tools.
This looks like a safe change to make, since we have no fortran in the
tree that needs to get built. It doesn't disable building of fortran
later in
...
>
> Starting an 'fsck' results in:
>
> cage:[/] # fsck /scratch
> ** /dev/da1s1g
> ** Last Mounted on /scratch
> ** Phase 1 - Check Blocks and Sizes
> PARTIALLY TRUNCATED INODE I=16
> SALVAGE? [yn] ^C
> * FILE SYSTEM MARKED DIRTY *
Next step is run the `
Hi there,
I reported a former heavy filesystem crash recently; have a look
at:
http://www.FreeBSD.org/cgi/getmsg.cgi?fetch=846852+849687+/usr/local/www/db/text/2000/freebsd-current/2123.freebsd-current
I got it again.
Meanwhile my system got updated to
FreeBSD abc.xyz.de 4.0-CURRENT
< said:
> Since the hostname is simply a plain-text token for the IP address
Wrong.
-GAWollman
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
On Thu, 27 Jan 2000 13:46:47 +0900, Yoshinobu Inoue wrote:
> I just added debug flag check instead of changing syslog
> level.
> Could you please try the following patch to
> usr.sbin/inetd/inetd.c ?
I would expect the messages to be sent to stderr in debug mode.
Ciao,
Sheldon.
To Unsubscri
In message <[EMAIL PROTECTED]>, Leif Neland
writes:
>
>
>On Wed, 26 Jan 2000, Poul-Henning Kamp wrote:
>
>> In message <[EMAIL PROTECTED]>,
>[EMAIL PROTECTED] writes:
>> >I'm wondering how one can do a buildworld on a machine, and then NFS
>> >mount /usr/src and /usr/obj on a client machine and
> > When using rsh from a friendly linux-mandrake box i get:
> >
> > rsh jfh00 ls
> > poll: protocol failure in circuit setup
> >
> > from a friendly freebsd box i get:
> > select: protocol failure in circuit setup
Woops bug was in rshd from the beginning. My test had a
leakage. It only happen
On Thursday, 27th January 2000, "Rodney W. Grimes" wrote:
>> <
>said:
>>
>> >> 3. On the first reboot after installing, the keyboard was in a funny
>> >> state.
>I have seen this on numerious occasion, but have never tracked it down
>to any one specific thing. All on desktop and servers, but
I totally aggree. As soon as CF is ported to FreeBSD the bettter
At 21:20 27/01/00 -0500, James Howard wrote:
>On Thu, 27 Jan 2000, Brian Hechinger wrote:
>
>> yes. sorry about the confusion, i forgot to mention that.
>> Allaire off-record said that they aren't happy with Linux
>> and are seekin
Ok, guys.
This is another patch for the atkbd driver. I expect this one is
better than my previous one. Remove the previous patch and try this
one instead. Stress the keyboard (like hitting the Return key twice
when booting the system), and see if it works.
Thank you.
Kazu
>> I have on a nu
>
>/home/kris/tmp/world/obj/.amd_mnt/freefall/host/c/users/kris/tmp/world/src/alpha/.amd_mnt/freefall/host/c/users/kris/tmp/world/src/gnu/usr.bin/cc/cpp/../cc_fbsd/libcc_fbsd.a(mktemp.o):
> In
> function `_gettemp':
> mktemp.c(.text+0x3f0): undefined reference to `_open'
> mktemp.c(.text+0x3f4):
> with yesterdays kernel or rshd, something has changed.
> When using rsh from a friendly linux-mandrake box i get:
>
> rsh jfh00 ls
> poll: protocol failure in circuit setup
>
> from a friendly freebsd box i get:
> select: protocol failure in circuit setup
As the change to src/lib/libc/net/ge
On Thu, 27 Jan 2000 18:35:33 PST, Jason Evans wrote:
> This is the same kind of breakage I caused when moving some definitions
> into unistd.h. I would call it bootstrapping breakage, but others who know
> the build system better claim it's avoidable.
I think it _is_ avoidable. One way to av
with yesterdays kernel or rshd, something has changed.
When using rsh from a friendly linux-mandrake box i get:
rsh jfh00 ls
poll: protocol failure in circuit setup
from a friendly freebsd box i get:
select: protocol failure in circuit setup
--
Fritz Heinrichmeyer mailto:[EMAIL PROTECTED]
Fer
On Fri, Jan 28, 2000 at 12:05:21AM -0800, Kris Kennaway wrote:
>
>/home/kris/tmp/world/obj/.amd_mnt/freefall/host/c/users/kris/tmp/world/src/alpha/.amd_mnt/freefall/host/c/users/kris/tmp/world/src/gnu/usr.bin/cc/cpp/../cc_int/libcc_int.a(choose-temp.o):
> In function `choose_temp_base':
> choose-
It seems Alex Zepeda wrote:
OK, I got my junkbox back into commission today, I just need to get it
update into -current, then I'll take a stab at it...
-Søren
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
/home/kris/tmp/world/obj/.amd_mnt/freefall/host/c/users/kris/tmp/world/src/alpha/.amd_mnt/freefall/host/c/users/kris/tmp/world/src/gnu/usr.bin/cc/cpp/../cc_int/libcc_int.a(choose-temp.o):
In function `choose_temp_base':
choose-temp.c(.text+0x218): warning: mktemp() possibly used
unsafely; consider
It seems Will Andrews wrote:
> On Thu, Jan 27, 2000 at 07:31:50PM -0500, Donn Miller wrote:
> > I recently cvsup'd the sources (around Thu Jan 27 19:30:48 EST 2000), and
> > I'm getting these errors compiling the kernel:
> >
> > cc -c -mpentium -O3 -pipe -Wall -Wredundant-decls -Wnested-externs
>
46 matches
Mail list logo
