Re: A different light, perhaps.
Kris Kennaway wrote: ...I expect the problem will be resolved by those who have already said they'll resolve it ;) I obviously missed that discussion. I don't want to pester people about things that they are already working on, so is there somewhere besides the -current and cvs mailing lists I should be watching? To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
A different light, perhaps.
cheerleading There seems to be many complaints of things being broken. Maybe I'm just lucky and never cvsup when things are broken. I have encountered -no- errors over the past month when building world and kernel. So anyway to add to that I'd just like to report on today's build so as to balance things out. After running cvsup at about 5PM EDT (September 23, 2002 -- using cvsup3) and running a full build I am happy to report that everything worked fine. No war stories to speak of. laptop% uname -a FreeBSD laptop.slackerbsd.org 5.0-CURRENT FreeBSD 5.0-CURRENT #0: Mon Sep 23 19:20:39 EDT 2002 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/LAPTOP i386 /cheerleading Now if only my laptop would stop overheating whenever I run FreeBSD on it. That is all. -- Carl Schmidt To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: A different light, perhaps.
On Mon, Sep 23, 2002 at 10:11:56PM -0400, Carl Schmidt wrote: cheerleading There seems to be many complaints of things being broken. Maybe I'm just lucky and never cvsup when things are broken. I have encountered -no- errors over the past month when building world and kernel. So anyway to add to that I'd just like to report on today's build so as to balance things out. After running cvsup at about 5PM EDT (September 23, 2002 -- using cvsup3) and running a full build I am happy to report that everything worked fine. No war stories to speak of. I've not had any problems either and I usually build once or twice a week. Now if only my laptop would stop overheating whenever I run FreeBSD on it. Does the fan not turn on? Are you using acpi? -- David W. Chapman Jr. [EMAIL PROTECTED] Raintree Network Services, Inc. www.inethouston.net [EMAIL PROTECTED] FreeBSD Committer www.FreeBSD.org To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: A different light, perhaps.
Hi, Now if only my laptop would stop overheating whenever I run FreeBSD on it. Does the fan not turn on? Are you using acpi? I built a current yesterday on my laptop too, and acpi drove it crazy ;) I noticed every 1 or 2 second(s) high interrupts load. clem To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: A different light, perhaps.
Carl Schmidt wrote: cheerleading Me too :-) After running cvsup at about 5PM EDT (September 23, 2002 -- using cvsup3) and running a full build I am happy to report that everything worked fine... In an attempt to understand this black magic we practice every day could I ask you to do two quick experiments for me? 1. Type 'sort +1' at any command prompt. What do you see? 2. cd /usr/src/lib/libncurses make clean make What do you see? [Warning: this may break your world on the next go-round.] Thanks! (Sorry if this is a duplicate post.) To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: A different light, perhaps.
On Mon, Sep 23, 2002 at 08:28:06PM -0700, walt wrote: Carl Schmidt wrote: After running cvsup at about 5PM EDT (September 23, 2002 -- using cvsup3) and running a full build I am happy to report that everything worked fine... In an attempt to understand this black magic we practice every day could I ask you to do two quick experiments for me? Heh... 1. Type 'sort +1' at any command prompt. What do you see? 2. cd /usr/src/lib/libncurses make clean make What do you see? [Warning: this may break your world on the next go-round.] Okay I ran into the same problems everyone else ran into and I have a solution. Get rid of gnu-sort from contrib and use NetBSD's sort, which was imported five months ago but apparently never incorporated into the build process. Gnu-sort does not appear to understand +# arguments whereas NetBSD's sort does. This solved the problem for me. -- Carl Schmidt To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: A different light, perhaps.
On Mon, Sep 23, 2002 at 08:28:06PM -0700, walt wrote: In an attempt to understand this black magic we practice every day could I ask you to do two quick experiments for me? 1. Type 'sort +1' at any command prompt. What do you see? 2. cd /usr/src/lib/libncurses make clean make What do you see? [Warning: this may break your world on the next go-round.] As has been already explained, it's caused by sort using a newer value of the _POSIX2_VERSION directive during the buildworld, meaning Use POSIX version mumble behaviour, where version mumble does not allow the 'sort +1' syntax. Kris msg43291/pgp0.pgp Description: PGP signature
Re: A different light, perhaps.
On Tue, Sep 24, 2002 at 12:10:23AM -0400, Carl Schmidt wrote: Get rid of gnu-sort from contrib and use NetBSD's sort, which was imported five months ago but apparently never incorporated into the build process. It was, briefly, but was backed out because it's not a sufficiently complete replacement for everyone's liking. Gnu-sort does not appear to understand +# arguments whereas NetBSD's sort does. It's actually a case of NetBSD's sort not disabling non-standard behaviour when you ask it to. Kris msg43292/pgp0.pgp Description: PGP signature
Re: A different light, perhaps.
On Tue, Sep 24, 2002 at 12:37:24AM -0400, Carl Schmidt wrote: On Mon, Sep 23, 2002 at 09:34:07PM -0700, Kris Kennaway wrote: On Tue, Sep 24, 2002 at 12:10:23AM -0400, Carl Schmidt wrote: [...] Right, okay. But NetBSD's sort actually works. I should rephrase this ... NetBSD's sort works with the current world setup. -- Carl Schmidt To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: A different light, perhaps.
On Tue, Sep 24, 2002 at 12:39:27AM -0400, Carl Schmidt wrote: On Tue, Sep 24, 2002 at 12:37:24AM -0400, Carl Schmidt wrote: On Mon, Sep 23, 2002 at 09:34:07PM -0700, Kris Kennaway wrote: On Tue, Sep 24, 2002 at 12:10:23AM -0400, Carl Schmidt wrote: [...] Right, okay. But NetBSD's sort actually works. I should rephrase this ... NetBSD's sort works with the current world setup. Yes, I expect the problem will be resolved by those who have already said they'll resolve it ;) Kris msg43295/pgp0.pgp Description: PGP signature
Re: A different light, perhaps.
On Mon, Sep 23, 2002 at 09:43:59PM -0700, Kris Kennaway wrote: Yes, I expect the problem will be resolved by those who have already said they'll resolve it ;) Okay good. I obviously missed a lot of the discussion on this. While we're at it someone should close PR 43317 since I am a fucking idiot and don't know what is going on. Bleh. -- Carl Schmidt To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
