From owner-freebsd-current Sun Dec 7 01:08:13 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id BAA28801 for current-outgoing; Sun, 7 Dec 1997 01:08:13 -0800 (PST) (envelope-from owner-freebsd-current) Received: from Tandem.com (suntan.tandem.com [192.216.221.8]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id BAA28796; Sun, 7 Dec 1997 01:08:10 -0800 (PST) (envelope-from grog@lemis.com) Received: from papillon.lemis.com ([168.87.69.104]) by Tandem.com (8.8.8/2.0.1) with ESMTP id BAA26694; Sun, 7 Dec 1997 01:08:05 -0800 (PST) Received: (grog@localhost) by papillon.lemis.com (8.8.8/8.6.12) id QAA01155; Sun, 7 Dec 1997 16:59:34 +0800 (CST) Message-ID: <19971207165932.28970@lemis.com> Date: Sun, 7 Dec 1997 16:59:32 +0800 From: Greg Lehey To: Terry Lambert Cc: ports@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: 3.0 -release ? References: <28074.881287489@time.cdrom.com> <199712052004.NAA16482@usr08.primenet.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.84e In-Reply-To: <199712052004.NAA16482@usr08.primenet.com>; from Terry Lambert on Fri, Dec 05, 1997 at 08:04:13PM +0000 Organisation: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-41-739-7062 WWW-Home-Page: http://www.lemis.com/~grog Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Fri, Dec 05, 1997 at 08:04:13PM +0000, Terry Lambert wrote: >> The second thing I think we need to consider is that in the longer >> term, I can easily see a day where the ports and packages collection >> have grown to the point where decoupling them from the primary FreeBSD >> releases becomes essential in order that the "base system" remain >> reasonably priced. This would also allow the ports collection to move >> at its own release schedule, perhaps doing only 2 - 3 releases a year >> and published in a format closer to Rich Morin's well known Prime Time >> Freeware for UNIX CDs (http://www.ptf.com/ptf/products/UNIX). They >> come with a nifty printed book containing alphabetized short >> descriptions so you can look something up quickly before wasting your >> time mounting the wrong CD, and I think the ports & packages >> collection should do exactly the same thing. > > I like this. I think that there should be coordination with the > OpenBSD and NetBSD folks to make sure they are usable "out of the box" > for them as well. It could become simply "The BSD ports > collection". Great idea! Yes, I've read the multitude of messages that have come in so far. But you've missed one point: why don't we merge FreeBSD, NetBSD and OpenBSD? Maybe BSD/OS as well? After all, most people don't understand why there are so many BSDs anyway. What, you say, they don't want to cooperate? Oh. So why should they want to cooperate on the question of the Ports Collection? Sure, the Ports Collection would be easier. It's less coupled with the kernel. But does anybody out there really see all four (three?) teams getting together and coordinating the mess? Greg From owner-freebsd-current Sun Dec 7 01:12:25 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id BAA29025 for current-outgoing; Sun, 7 Dec 1997 01:12:25 -0800 (PST) (envelope-from owner-freebsd-current) Received: from outmail.utsunomiya-u.ac.jp (outmail.utsunomiya-u.ac.jp [160.12.196.3]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id BAA29020 for ; Sun, 7 Dec 1997 01:12:21 -0800 (PST) (envelope-from yokota@zodiac.mech.utsunomiya-u.ac.jp) Received: by outmail.utsunomiya-u.ac.jp id AA20025; Sun, 7 Dec 1997 18:11:44 +0900 Received: from zodiac.mech.utsunomiya-u.ac.jp (zodiac.mech.utsunomiya-u.ac.jp [160.12.42.1]) by zodiac.mech.utsunomiya-u.ac.jp (8.7.6+2.6Wbeta7/3.4W/zodiac-May96) with ESMTP id SAA13234; Sun, 7 Dec 1997 18:18:39 +0900 (JST) Message-Id: <199712070918.SAA13234@zodiac.mech.utsunomiya-u.ac.jp> To: jbryant@unix.tfs.net Cc: freebsd-current@freebsd.org, yokota@zodiac.mech.utsunomiya-u.ac.jp Subject: Re: sc0 scrollback flaw In-Reply-To: Your message of "Fri, 05 Dec 1997 10:36:20 CST." <199712051636.KAA00424@unix.tfs.net> References: <199712051636.KAA00424@unix.tfs.net> Date: Sun, 07 Dec 1997 18:18:38 +0900 From: Kazutaka YOKOTA Sender: owner-freebsd-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >hmmm... i just rebuilt using the SC_HISTORY_SIZE option for sc [good >idea, it was always a pain in the ass hacking up syscons.h to do this]. > >there seems to be an undesireable new behavior for the sc scrollback >facility.. > >one of the functions in my .login is a `clear` to clear the console >when i log in. this seems to erase the entire scrollback buffer. the >old behavior was to ignore screen clears in the buffer. ? My current box donsn't have this problem. The history buffer is intact after `clear'... >i'm still running the Dec. 2 version of -current, but will be >cvsupping the latest in a few minutes... i can take a look at >syscons.c, and see if i can find where this is happening... I did add SC_HISTORY_SIZE stuff to syscons.c. But, I never touched screen clearing part of the code, because SC_HISTORY_SIZE affects the driver only when the history buffer is allocated, which happens a) if the virtual console is opened for the first time, b) if the user runs `kbdcontrol -h lines' to set the history buffer size, c) or if the screen size is changed by `vidcontrol VGA_xxx'. I'm puzzled. Kazu From owner-freebsd-current Sun Dec 7 02:21:03 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id CAA02210 for current-outgoing; Sun, 7 Dec 1997 02:21:03 -0800 (PST) (envelope-from owner-freebsd-current) Received: from haldjas.folklore.ee (Haldjas.folklore.ee [193.40.6.121]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id CAA02205; Sun, 7 Dec 1997 02:21:00 -0800 (PST) (envelope-from narvi@Haldjas.folklore.ee) Received: from haldjas.folklore.ee (haldjas.folklore.ee [172.17.2.1] (may be forged)) by haldjas.folklore.ee (8.8.7/8.8.4) with SMTP id MAA23773; Sun, 7 Dec 1997 12:20:28 +0200 (EET) Date: Sun, 7 Dec 1997 12:20:27 +0200 (EET) From: Narvi To: Greg Lehey cc: Terry Lambert , ports@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: 3.0 -release ? In-Reply-To: <19971207165932.28970@lemis.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Sun, 7 Dec 1997, Greg Lehey wrote: > On Fri, Dec 05, 1997 at 08:04:13PM +0000, Terry Lambert wrote: > >> The second thing I think we need to consider is that in the longer > >> term, I can easily see a day where the ports and packages collection > >> have grown to the point where decoupling them from the primary FreeBSD > >> releases becomes essential in order that the "base system" remain > >> reasonably priced. This would also allow the ports collection to move > >> at its own release schedule, perhaps doing only 2 - 3 releases a year > >> and published in a format closer to Rich Morin's well known Prime Time > >> Freeware for UNIX CDs (http://www.ptf.com/ptf/products/UNIX). They > >> come with a nifty printed book containing alphabetized short > >> descriptions so you can look something up quickly before wasting your > >> time mounting the wrong CD, and I think the ports & packages > >> collection should do exactly the same thing. > > > > I like this. I think that there should be coordination with the > > OpenBSD and NetBSD folks to make sure they are usable "out of the box" > > for them as well. It could become simply "The BSD ports > > collection". > > Great idea! Yes, I've read the multitude of messages that have come > in so far. But you've missed one point: why don't we merge FreeBSD, > NetBSD and OpenBSD? Maybe BSD/OS as well? After all, most people > don't understand why there are so many BSDs anyway. > > What, you say, they don't want to cooperate? Oh. So why should they > want to cooperate on the question of the Ports Collection? > Well, I see several reasons for it (and also differences in the issues) : a) Different platforms - if we know port X works on the other BSDs on platforms A, B & C, we can be fairly sure that when the FreeBSD port happens to that platform, we have a ports collection that works there for sure. b) Having a larger amount of people who use the ports (and so also test them) is only beneficial as the probability of getting rid of bugs increases. It also increases the amount of potencial people donating their time towards both porting and maintaining ports. c) We don't need a grand cooperation like in the case of merging two operating systems. Everyone can keep their utilities (tar, md5, whatever) in the place they like. Everyone can keep their defaults as they like. The ports collection is not about the base OS-s but the things running atop of them. > Sure, the Ports Collection would be easier. It's less coupled with > the kernel. But does anybody out there really see all four (three?) > teams getting together and coordinating the mess? > No. But see above. > Greg > Sander There is no love, no good, no happiness and no future - all these are just illusions. From owner-freebsd-current Sun Dec 7 02:22:16 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id CAA02298 for current-outgoing; Sun, 7 Dec 1997 02:22:16 -0800 (PST) (envelope-from owner-freebsd-current) Received: from unix.tfs.net (node56.tfs.net [207.2.220.56]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id CAA02288 for ; Sun, 7 Dec 1997 02:22:11 -0800 (PST) (envelope-from jbryant@unix.tfs.net) Received: (from jbryant@localhost) by unix.tfs.net (8.8.8/8.8.5) id EAA00984; Sun, 7 Dec 1997 04:21:57 -0600 (CST) From: Jim Bryant Message-Id: <199712071021.EAA00984@unix.tfs.net> Subject: Re: sc0 scrollback flaw In-Reply-To: <199712070918.SAA13234@zodiac.mech.utsunomiya-u.ac.jp> from Kazutaka YOKOTA at "Dec 7, 97 06:18:38 pm" To: yokota@zodiac.mech.utsunomiya-u.ac.jp (Kazutaka YOKOTA) Date: Sun, 7 Dec 1997 04:21:57 -0600 (CST) Cc: freebsd-current@freebsd.org Reply-to: jbryant@unix.tfs.net X-Windows: R00LZ!@# MS-Winbl0wz DR00LZ!@# X-Operating-System: FreeBSD 3.0-CURRENT #0: Mon Dec 1 15:51:40 CST 1997 X-Mailer: ELM [version 2.4ME+ PL31H (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk In reply: > >hmmm... i just rebuilt using the SC_HISTORY_SIZE option for sc [good > >idea, it was always a pain in the ass hacking up syscons.h to do this]. > > > >there seems to be an undesireable new behavior for the sc scrollback > >facility.. > > > >one of the functions in my .login is a `clear` to clear the console > >when i log in. this seems to erase the entire scrollback buffer. the > >old behavior was to ignore screen clears in the buffer. > > ? My current box donsn't have this problem. The history buffer is > intact after `clear'... > > >i'm still running the Dec. 2 version of -current, but will be > >cvsupping the latest in a few minutes... i can take a look at > >syscons.c, and see if i can find where this is happening... > > I did add SC_HISTORY_SIZE stuff to syscons.c. But, I never touched > screen clearing part of the code, because SC_HISTORY_SIZE affects the > driver only when the history buffer is allocated, which happens a) if > the virtual console is opened for the first time, b) if the user runs > `kbdcontrol -h lines' to set the history buffer size, c) or if the > screen size is changed by `vidcontrol VGA_xxx'. > > I'm puzzled. hmmm... just remembering, i do change the screen dimensions to 80x60, but that is beside the point, as even asfter the switch, i still retained the kernel boot messages before, and now everything prior to login now is lost... my .login is enclosed... btw: i guess i don't do a clear, and the mode change does it.. note that clear is commented... sorry... ----------------------- # $Id: dot.login,v 1.5 1994/06/15 22:58:47 jkh Exp $ # umask 022 setenv TTY `/usr/bin/tty` setenv LS -G tset -Q \?$TERM if ("$TERM" == "cons60") then stty crt erase ^h /usr/sbin/kbdcontrol -r fast /usr/sbin/vidcontrol -t 300 cyan black /usr/sbin/vidcontrol -f 8x8 /usr/share/syscons/fonts/cp437-thin-8x8.fnt /usr/sbin/vidcontrol -f 8x14 /usr/share/syscons/fonts/cp437-8x14.fnt /usr/sbin/vidcontrol -f 8x16 /usr/share/syscons/fonts/cp437-thin-8x16.fnt /usr/sbin/vidcontrol VGA_80x60 /usr/sbin/vidcontrol -c destructive stty rows 60 endif if ("$TERM" == "vt420") then stty `cat .tty` stty rows 48 cols 132 erase ^\? unsetenv LS setenv LS endif #clear w echo ' ' cat /etc/motd.bill echo ' ' /usr/games/fortune -a limerick startrek echo ' ' jim -- All opinions expressed are mine, if you | "I will not be pushed, stamped, think otherwise, then go jump into turbid | briefed, debriefed, indexed, or radioactive waters and yell WAHOO !!! | numbered!" - #1, "The Prisoner" ------------------------------------------------------------------------------ Inet: jbryant@tfs.net AX.25: kc5vdj@wv0t.#neks.ks.usa.noam grid: EM28pw voice: KC5VDJ - 6 & 2 Meters AM/FM/SSB, 70cm FM. http://www.tfs.net/~jbryant ------------------------------------------------------------------------------ HF/6M/2M: IC-706-MkII, 2M: HTX-212, 2M: HTX-202, 70cm: HTX-404, Packet: KPC-3+ From owner-freebsd-current Sun Dec 7 02:44:42 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id CAA02957 for current-outgoing; Sun, 7 Dec 1997 02:44:42 -0800 (PST) (envelope-from owner-freebsd-current) Received: from outmail.utsunomiya-u.ac.jp (outmail.utsunomiya-u.ac.jp [160.12.196.3]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id CAA02949 for ; Sun, 7 Dec 1997 02:44:35 -0800 (PST) (envelope-from yokota@zodiac.mech.utsunomiya-u.ac.jp) Received: by outmail.utsunomiya-u.ac.jp id AA20108; Sun, 7 Dec 1997 19:44:30 +0900 Received: from zodiac.mech.utsunomiya-u.ac.jp (zodiac.mech.utsunomiya-u.ac.jp [160.12.42.1]) by zodiac.mech.utsunomiya-u.ac.jp (8.7.6+2.6Wbeta7/3.4W/zodiac-May96) with ESMTP id TAA15489; Sun, 7 Dec 1997 19:51:10 +0900 (JST) Message-Id: <199712071051.TAA15489@zodiac.mech.utsunomiya-u.ac.jp> To: jbryant@unix.tfs.net Cc: freebsd-current@freebsd.org, yokota@zodiac.mech.utsunomiya-u.ac.jp Subject: Re: sc0 scrollback flaw In-Reply-To: Your message of "Sun, 07 Dec 1997 04:21:57 CST." <199712071021.EAA00984@unix.tfs.net> References: <199712071021.EAA00984@unix.tfs.net> Date: Sun, 07 Dec 1997 19:50:59 +0900 From: Kazutaka YOKOTA Sender: owner-freebsd-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >> >i'm still running the Dec. 2 version of -current, but will be >> >cvsupping the latest in a few minutes... i can take a look at >> >syscons.c, and see if i can find where this is happening... >> >> I did add SC_HISTORY_SIZE stuff to syscons.c. But, I never touched >> screen clearing part of the code, because SC_HISTORY_SIZE affects the >> driver only when the history buffer is allocated, which happens a) if >> the virtual console is opened for the first time, b) if the user runs >> `kbdcontrol -h lines' to set the history buffer size, c) or if the >> screen size is changed by `vidcontrol VGA_xxx'. >> >> I'm puzzled. > >hmmm... just remembering, i do change the screen dimensions to 80x60, >but that is beside the point, as even asfter the switch, i still >retained the kernel boot messages before, and now everything prior to >login now is lost... > >my .login is enclosed... btw: i guess i don't do a clear, and the >mode change does it.. note that clear is commented... sorry... Before the introduction of SC_HISTORY_SIZE, syscons didn't check if the history buffer size is sufficient for the new screen size when the user is changing the screen size. If you set HISTORY_SIZE to a small number, say 40 lines, and changed the screen size to 80x60, the system would crash. So, syscons was to made to free the history buffer whenever the screen size is changed and allocate a new buffer. Ok, probably we should retain the history buffer contents if possible, when the screen size is changed and when the history buffer size is changed. Kazu From owner-freebsd-current Sun Dec 7 04:46:06 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id EAA07538 for current-outgoing; Sun, 7 Dec 1997 04:46:06 -0800 (PST) (envelope-from owner-freebsd-current) Received: from word.smith.net.au (ppp3.portal.net.au [202.12.71.103]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id EAA07515 for ; Sun, 7 Dec 1997 04:45:55 -0800 (PST) (envelope-from mike@word.smith.net.au) Received: from word (localhost [127.0.0.1]) by word.smith.net.au (8.8.7/8.8.5) with ESMTP id XAA02191; Sun, 7 Dec 1997 23:10:47 +1030 (CST) Message-Id: <199712071240.XAA02191@word.smith.net.au> X-Mailer: exmh version 2.0zeta 7/24/97 To: Gary Clark II cc: freebsd-current@freebsd.org Subject: Re: More on foxpro problems. In-reply-to: Your message of "Sat, 06 Dec 1997 11:23:19 MDT." <199712061723.LAA00649@main.brewich.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 07 Dec 1997 23:10:46 +1030 From: Mike Smith Sender: owner-freebsd-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > Well it seems that the keymap changes everytime I run foxpro for what ever > reason. It work perfectly on 2.2.5.... > I've ran ktrace on it, and the only big difference that I see > is a LOT of "resource deadlock avoided" or words to that effect. > I've even tried loading a keymap from 2.2.5 with no luck. > Any ideas at all??? Keyboard ioctls? Have you tried hanging some debugging code into syscons to have it tell you if/when the keymap is changed? mike From owner-freebsd-current Sun Dec 7 07:24:49 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id HAA03204 for current-outgoing; Sun, 7 Dec 1997 07:24:49 -0800 (PST) (envelope-from owner-freebsd-current) Received: from main.brewich.com (digital-01-110.hou.neoworld.net [206.109.29.110]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id HAA03197 for ; Sun, 7 Dec 1997 07:24:42 -0800 (PST) (envelope-from gclarkii@main.brewich.com) Received: (from gclarkii@localhost) by main.brewich.com (8.8.7/8.8.5) id JAA01652; Sun, 7 Dec 1997 09:23:37 -0600 (CST) From: Gary Clark II Message-Id: <199712071523.JAA01652@main.brewich.com> Subject: Re: More on foxpro problems. To: mike@smith.net.au (Mike Smith) Date: Sun, 7 Dec 1997 09:23:37 -0600 (CST) Cc: freebsd-current@freebsd.org In-Reply-To: <199712071240.XAA02191@word.smith.net.au> from Mike Smith at "Dec 7, 97 11:10:46 pm" X-Mailer: ELM [version 2.4ME+ PL22 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Mike Smith wrote: > > Well it seems that the keymap changes everytime I run foxpro for what ever > > reason. It work perfectly on 2.2.5.... > > I've ran ktrace on it, and the only big difference that I see > > is a LOT of "resource deadlock avoided" or words to that effect. > > I've even tried loading a keymap from 2.2.5 with no luck. > > Any ideas at all??? > > Keyboard ioctls? Have you tried hanging some debugging code into > syscons to have it tell you if/when the keymap is changed? > > mike Hello, Ok, I've atleast got Foxpro 2.6 running again under 3.0-current. I had to disable scancodes using the -i command line option. It now works fine. HOWEVER, the first time one brings up foxpro there is a minor problem with the keyboard. The second time works like a champ. I have no idea why this is... Gary -- Gary Clark II (N5VMF) | I speak only for myself and "maybe" my company gclarkii@main.brewich.COM | Member of the FreeBSD Doc Team From owner-freebsd-current Sun Dec 7 07:25:33 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id HAA03255 for current-outgoing; Sun, 7 Dec 1997 07:25:33 -0800 (PST) (envelope-from owner-freebsd-current) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id HAA03249 for ; Sun, 7 Dec 1997 07:25:25 -0800 (PST) (envelope-from bde@zeta.org.au) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.7/8.6.9) id CAA04113; Mon, 8 Dec 1997 02:22:27 +1100 Date: Mon, 8 Dec 1997 02:22:27 +1100 From: Bruce Evans Message-Id: <199712071522.CAA04113@godzilla.zeta.org.au> To: brian@awfulhak.org, evanc@synapse.net Subject: Re: _POSIX_SAVED_IDS Cc: freebsd-current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >AFAIK, setreuid() doesn't use saved ids - setreuid() should only be >used to swap your euid and uid. Disclaimer - this is an assumption, >I may be wrong. Don't assume, read the man^H^H^Hcode. setreuid9) does use saved ids. They are BSD saved ids, not POSIX saved ids, so _POSIX_SAVED_IDS is not defined. >However, seteuid() works ok for me (/usr/src/usr.sbin/ppp/id.c), >which implies that saved uids are functional. It works OK if you want to swap ids, but not if you want to set all ids including the saved id to the same value. Use setuid() or exec to set them all. Not knowing about the saved id is dangerous because it may result in security holes in apparently secure code, e.g.: char buf[1234]; setuid(getuid()); strcpy(buf, argv[1]); With _POSIX samantics for saved ids, it is not clear when the above setuid() sets the saved id. It sets it if the process has "appropriate privileges". The behaviour is implementation defined. At least the old FreeBSD implementation defined "has appropriate privileges" as "being root". This means that the above is secure for root but not for anyone else. OTOH, this definition makes the saved ids useless for root if only POSIX interfaces are used. FreeBSD now gives everyone "appropriate privileges" for doing setuid(getegid()), so if you uncomment _POSIX_SAVED_IDS in , then you can set all the uids to the real uid using: seteuid(getuid()); /* euid = ruid, suid = any */ setuid(geteuid()); /* all uids = euid = original ruid */ This is very unportable. Bruce From owner-freebsd-current Sun Dec 7 07:45:26 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id HAA04297 for current-outgoing; Sun, 7 Dec 1997 07:45:26 -0800 (PST) (envelope-from owner-freebsd-current) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id HAA04292 for ; Sun, 7 Dec 1997 07:45:18 -0800 (PST) (envelope-from bde@zeta.org.au) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.7/8.6.9) id CAA04419; Mon, 8 Dec 1997 02:42:42 +1100 Date: Mon, 8 Dec 1997 02:42:42 +1100 From: Bruce Evans Message-Id: <199712071542.CAA04419@godzilla.zeta.org.au> To: brian@awfulhak.org, evanc@synapse.net Subject: Re: _POSIX_SAVED_IDS Cc: freebsd-current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >Here's a problem for you: on systems where I have a saved-set seteuid(), I >would prefer to use it instead of a setreuid() swap. How do I tell if I >have a saved-set seteuid() if _POSIX_SAVED_IDS is not defined (besides >running a setuid test program -- I'd prefer something that autoconf could >figure out on its own)? Same as if _POSIX_SAVED_IDS is defined - it has nothing to do with seteuid(), since setreuid() is not in POSIX. If you can't run a setuid program, then you'll have to read all the man pages, and maybe the system sources, and maybe the kernel binary - a difficult task for autoconf :-). I think you should depend on running a setuid test program. If the program can be trusted at runtime, it can probably be trusted at build time. Bruce From owner-freebsd-current Sun Dec 7 08:18:48 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id IAA05816 for current-outgoing; Sun, 7 Dec 1997 08:18:48 -0800 (PST) (envelope-from owner-freebsd-current) Received: from fallout.campusview.indiana.edu (fallout.campusview.indiana.edu [149.159.1.1]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id IAA05797 for ; Sun, 7 Dec 1997 08:18:35 -0800 (PST) (envelope-from jfieber@indiana.edu) Received: from localhost (jfieber@localhost) by fallout.campusview.indiana.edu (8.8.7/8.8.7) with SMTP id LAA17531; Sun, 7 Dec 1997 11:18:31 -0500 (EST) Date: Sun, 7 Dec 1997 11:18:31 -0500 (EST) From: John Fieber To: David Dawes cc: current@FreeBSD.ORG Subject: Re: Oddity with netscape and current In-Reply-To: <19971207144204.50524@rf900.physics.usyd.edu.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Sun, 7 Dec 1997, David Dawes wrote: > Given the XCMSDB solution, is it possible > that those who see this have a file called Xcms.txt installed in > /usr/X11R6/lib/X11? That file was distributed with some earlier XFree86 > releases (which turned out to be a bad idea), and some people might have > still have it around. Bingo! Removing that file (with a 1995 date) made the XCMSDB variable unnecessary. -john From owner-freebsd-current Sun Dec 7 09:25:37 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id JAA09672 for current-outgoing; Sun, 7 Dec 1997 09:25:37 -0800 (PST) (envelope-from owner-freebsd-current) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id JAA09662 for ; Sun, 7 Dec 1997 09:25:21 -0800 (PST) (envelope-from bde@zeta.org.au) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.7/8.6.9) id EAA06767; Mon, 8 Dec 1997 04:24:45 +1100 Date: Mon, 8 Dec 1997 04:24:45 +1100 From: Bruce Evans Message-Id: <199712071724.EAA06767@godzilla.zeta.org.au> To: dawes@rf900.physics.usyd.edu.au, jfieber@indiana.edu Subject: Re: Oddity with netscape and current Cc: current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >> Given the XCMSDB solution, is it possible >> that those who see this have a file called Xcms.txt installed in >> /usr/X11R6/lib/X11? That file was distributed with some earlier XFree86 >> releases (which turned out to be a bad idea), and some people might have >> still have it around. > >Bingo! Removing that file (with a 1995 date) made the XCMSDB >variable unnecessary. My /usr/X11R6 is too well maintained to have it :-), but `locate' shows that the linux_lib package puts it in /usr/local/compat/linux/var/X11R6/lib/. Bruce From owner-freebsd-current Sun Dec 7 09:45:54 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id JAA10794 for current-outgoing; Sun, 7 Dec 1997 09:45:54 -0800 (PST) (envelope-from owner-freebsd-current) Received: from mailhost.shellnet.co.uk (mailhost.shellnet.co.uk [194.129.209.3]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id JAA10783 for ; Sun, 7 Dec 1997 09:45:45 -0800 (PST) (envelope-from ircadmin@shellnet.co.uk) Received: by mailhost.shellnet.co.uk with MERCUR-SMTP/POP3-Server (v2.10) for at Sun, 7 Dec 97 17:45:08 +0000 Message-ID: <348AE151.4190@shellnet.co.uk> Date: Sun, 07 Dec 1997 17:48:01 +0000 From: "Steven Fletcher (Shellnet IRC administrator)" Reply-To: ircadmin@shellnet.co.uk Organization: Shellnet Ltd X-Mailer: Mozilla 3.01 (Win95; I) MIME-Version: 1.0 To: freebsd-current@freebsd.org Subject: Where can I get help ? Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I need some help on compiling a kernel with 1024 file descriptor blocks ... which I have little idead on how to do. Could anyone help me with this, or tell me where to get help on the problem ? -- Steven Fletcher steven@shellnet.co.uk From owner-freebsd-current Sun Dec 7 10:16:51 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id KAA12394 for current-outgoing; Sun, 7 Dec 1997 10:16:51 -0800 (PST) (envelope-from owner-freebsd-current) Received: from unix.tfs.net (tc1-p28.tfs.net [139.146.197.28]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id KAA12385 for ; Sun, 7 Dec 1997 10:16:35 -0800 (PST) (envelope-from jbryant@unix.tfs.net) Received: (from jbryant@localhost) by unix.tfs.net (8.8.8/8.8.5) id MAA01529; Sun, 7 Dec 1997 12:16:16 -0600 (CST) From: Jim Bryant Message-Id: <199712071816.MAA01529@unix.tfs.net> Subject: Re: sc0 scrollback flaw In-Reply-To: <199712071051.TAA15489@zodiac.mech.utsunomiya-u.ac.jp> from Kazutaka YOKOTA at "Dec 7, 97 07:50:59 pm" To: yokota@zodiac.mech.utsunomiya-u.ac.jp (Kazutaka YOKOTA) Date: Sun, 7 Dec 1997 12:16:15 -0600 (CST) Cc: freebsd-current@freebsd.org Reply-to: jbryant@unix.tfs.net X-Windows: R00LZ!@# MS-Winbl0wz DR00LZ!@# X-Operating-System: FreeBSD 3.0-CURRENT #0: Mon Dec 1 15:51:40 CST 1997 X-Mailer: ELM [version 2.4ME+ PL31H (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk In reply: > >> >i'm still running the Dec. 2 version of -current, but will be > >> >cvsupping the latest in a few minutes... i can take a look at > >> >syscons.c, and see if i can find where this is happening... > >> > >> I did add SC_HISTORY_SIZE stuff to syscons.c. But, I never touched > >> screen clearing part of the code, because SC_HISTORY_SIZE affects the > >> driver only when the history buffer is allocated, which happens a) if > >> the virtual console is opened for the first time, b) if the user runs > >> `kbdcontrol -h lines' to set the history buffer size, c) or if the > >> screen size is changed by `vidcontrol VGA_xxx'. > >> > >> I'm puzzled. > > > >hmmm... just remembering, i do change the screen dimensions to 80x60, > >but that is beside the point, as even asfter the switch, i still > >retained the kernel boot messages before, and now everything prior to > >login now is lost... > > > >my .login is enclosed... btw: i guess i don't do a clear, and the > >mode change does it.. note that clear is commented... sorry... > > Before the introduction of SC_HISTORY_SIZE, syscons didn't check if > the history buffer size is sufficient for the new screen size when the > user is changing the screen size. If you set HISTORY_SIZE to a small > number, say 40 lines, and changed the screen size to 80x60, the system > would crash. > > So, syscons was to made to free the history buffer whenever the screen > size is changed and allocate a new buffer. > > Ok, probably we should retain the history buffer contents if possible, > when the screen size is changed and when the history buffer size is > changed. maybe do a compare against SC_HISTORY_SIZE with the current and desired screen size when changing it? truncate if SC_HISTORY_SIZE < desired. the way it was before, it only allocated a set number of char cells, do you do it by the line now? jim -- All opinions expressed are mine, if you | "I will not be pushed, stamped, think otherwise, then go jump into turbid | briefed, debriefed, indexed, or radioactive waters and yell WAHOO !!! | numbered!" - #1, "The Prisoner" ------------------------------------------------------------------------------ Inet: jbryant@tfs.net AX.25: kc5vdj@wv0t.#neks.ks.usa.noam grid: EM28pw voice: KC5VDJ - 6 & 2 Meters AM/FM/SSB, 70cm FM. http://www.tfs.net/~jbryant ------------------------------------------------------------------------------ HF/6M/2M: IC-706-MkII, 2M: HTX-212, 2M: HTX-202, 70cm: HTX-404, Packet: KPC-3+ From owner-freebsd-current Sun Dec 7 10:25:12 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id KAA12822 for current-outgoing; Sun, 7 Dec 1997 10:25:12 -0800 (PST) (envelope-from owner-freebsd-current) Received: from gaia.coppe.ufrj.br (cisigw.coppe.ufrj.br [146.164.5.200]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id KAA12804; Sun, 7 Dec 1997 10:25:00 -0800 (PST) (envelope-from jonny@coppe.ufrj.br) Received: (from jonny@localhost) by gaia.coppe.ufrj.br (8.8.8/8.8.8) id QAA18566; Sun, 7 Dec 1997 16:24:58 -0200 (EDT) (envelope-from jonny) From: Joao Carlos Mendes Luis Message-Id: <199712071824.QAA18566@gaia.coppe.ufrj.br> Subject: Re: VM system info In-Reply-To: <199712061331.IAA03947@dyson.iquest.net> from "John S. Dyson" at "Dec 6, 97 08:31:18 am" To: dyson@FreeBSD.ORG Date: Sun, 7 Dec 1997 16:24:58 -0200 (EDT) Cc: current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL32 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk #define quoting(John S. Dyson) // Notes on VM tunables: // // I have recently added some interesting VM tunables. Since it would // be nice if people other than me (or those who requested them) could // use the features, I thought it would be nice to pass this info on: Is there any place or URL where we can get this information always updated ? It's a pretty good form of documentation I've always wanted to know. Maybe it deserves a handbook section ? Jonny -- Joao Carlos Mendes Luis jonny@gta.ufrj.br +55 21 290-4698 jonny@coppe.ufrj.br Universidade Federal do Rio de Janeiro UFRJ/COPPE/CISI PGP fingerprint: 29 C0 50 B9 B6 3E 58 F2 83 5F E3 26 BF 0F EA 67 From owner-freebsd-current Sun Dec 7 10:30:49 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id KAA13050 for current-outgoing; Sun, 7 Dec 1997 10:30:49 -0800 (PST) (envelope-from owner-freebsd-current) Received: from gaia.coppe.ufrj.br (cisigw.coppe.ufrj.br [146.164.5.200]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id KAA13044 for ; Sun, 7 Dec 1997 10:30:44 -0800 (PST) (envelope-from jonny@coppe.ufrj.br) Received: (from jonny@localhost) by gaia.coppe.ufrj.br (8.8.8/8.8.8) id QAA18606; Sun, 7 Dec 1997 16:28:03 -0200 (EDT) (envelope-from jonny) From: Joao Carlos Mendes Luis Message-Id: <199712071828.QAA18606@gaia.coppe.ufrj.br> Subject: Re: wd0 interrupt timeout In-Reply-To: <19971206114018.41854@deepo.prosa.dk> from Philippe Regnauld at "Dec 6, 97 11:40:18 am" To: regnauld@deepo.prosa.dk (Philippe Regnauld) Date: Sun, 7 Dec 1997 16:28:03 -0200 (EDT) Cc: kkennawa@physics.adelaide.edu.au, freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL32 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk #define quoting(Philippe Regnauld) // Kris Kennaway writes: // > // > For the past several days (the first time being on Dec 2 as shown) I've been // > seeing the following messages popping up: // // [...] // // > The system will completely hang for several seconds - no process // > activity, no disk activity, nothing - then the drive in question makes // > the "powering up" sound it does when I first power up the machine, the // > error appears on the console and activity resumes. // // You have auto-spindown / APM enable in the BIOS, and your // disk spins down when it's been idle for some time (definable). What if I have this on a machine without APM support (a very old 486) ? I've never had a fatal error, but always have these warnings. Jonny -- Joao Carlos Mendes Luis jonny@gta.ufrj.br +55 21 290-4698 jonny@coppe.ufrj.br Universidade Federal do Rio de Janeiro UFRJ/COPPE/CISI PGP fingerprint: 29 C0 50 B9 B6 3E 58 F2 83 5F E3 26 BF 0F EA 67 From owner-freebsd-current Sun Dec 7 10:31:14 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id KAA13088 for current-outgoing; Sun, 7 Dec 1997 10:31:14 -0800 (PST) (envelope-from owner-freebsd-current) Received: from dyson.iquest.net (dyson.iquest.net [198.70.144.127]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id KAA13070; Sun, 7 Dec 1997 10:31:02 -0800 (PST) (envelope-from toor@dyson.iquest.net) Received: (from root@localhost) by dyson.iquest.net (8.8.8/8.8.8) id NAA03407; Sun, 7 Dec 1997 13:29:43 -0500 (EST) (envelope-from toor) Message-Id: <199712071829.NAA03407@dyson.iquest.net> Subject: Re: VM system info In-Reply-To: <199712071824.QAA18566@gaia.coppe.ufrj.br> from Joao Carlos Mendes Luis at "Dec 7, 97 04:24:58 pm" To: jonny@coppe.ufrj.br (Joao Carlos Mendes Luis) Date: Sun, 7 Dec 1997 13:29:42 -0500 (EST) Cc: dyson@FreeBSD.ORG, current@FreeBSD.ORG From: "John S. Dyson" Reply-To: dyson@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL31 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Joao Carlos Mendes Luis said: > #define quoting(John S. Dyson) > // Notes on VM tunables: > // > // I have recently added some interesting VM tunables. Since it would > // be nice if people other than me (or those who requested them) could > // use the features, I thought it would be nice to pass this info on: > > Is there any place or URL where we can get this information always > updated ? It's a pretty good form of documentation I've always > wanted to know. > Nope. Unfortunately, the source code is the only place for it (by inference.) The VFS sysctls also deserve some documentation. > > Maybe it deserves a handbook section ? > Maybe, but it is extremely kernel version dependent, and would require some commitment to maintain. Otherwise, the info could be confusing. I know that some of the information would be useful, especially to ISPs. That is specifically the reason that I sent the info to the mailing list. -- John dyson@freebsd.org jdyson@nc.com From owner-freebsd-current Sun Dec 7 11:35:12 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id LAA16331 for current-outgoing; Sun, 7 Dec 1997 11:35:12 -0800 (PST) (envelope-from owner-freebsd-current) Received: from wawasee.read.indiana.edu (wawasee.read.indiana.edu [149.159.108.2]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id LAA16322 for ; Sun, 7 Dec 1997 11:35:03 -0800 (PST) (envelope-from ghormann@nix.kconline.com) Received: from localhost (xwin@localhost) by wawasee.read.indiana.edu (8.8.8/8.8.8) with SMTP id OAA06140 for ; Sun, 7 Dec 1997 14:34:47 -0500 (EST) (envelope-from ghormann@nix.kconline.com) X-Authentication-Warning: wawasee.read.indiana.edu: xwin owned process doing -bs Date: Sun, 7 Dec 1997 14:34:47 -0500 (EST) From: Greg Hormann X-Sender: xwin@wawasee.read.indiana.edu To: current@freebsd.org Subject: ld.so AND emacs Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Was there ever a workaround found for the emacs/ld.so problem? I searched the archives to no avail. Thanks, Greg. ______________________________________________________________________________ Greg Hormann | | | ghormann@indiana.edu | | | http://php.ucs.indiana.edu/~ghormann/home.html |. \____/. ______________________________________________________________________________ From owner-freebsd-current Sun Dec 7 12:17:04 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id MAA18588 for current-outgoing; Sun, 7 Dec 1997 12:17:04 -0800 (PST) (envelope-from owner-freebsd-current) Received: from smtp01.primenet.com (smtp01.primenet.com [206.165.6.131]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id MAA18569 for ; Sun, 7 Dec 1997 12:16:47 -0800 (PST) (envelope-from tlambert@usr02.primenet.com) Received: (from daemon@localhost) by smtp01.primenet.com (8.8.8/8.8.8) id GAA25067; Sun, 7 Dec 1997 06:48:17 -0700 (MST) Received: from usr02.primenet.com(206.165.6.202) via SMTP by smtp01.primenet.com, id smtpd025021; Sun Dec 7 06:48:06 1997 Received: (from tlambert@localhost) by usr02.primenet.com (8.8.5/8.8.5) id NAA27994; Sun, 7 Dec 1997 13:16:01 -0700 (MST) From: Terry Lambert Message-Id: <199712072016.NAA27994@usr02.primenet.com> Subject: Re: 3.0 -release ? To: jkh@time.cdrom.com (Jordan K. Hubbard) Date: Sun, 7 Dec 1997 20:16:01 +0000 (GMT) Cc: tlambert@primenet.com, shawn@cpl.net, chuckr@glue.umd.edu, freebsd-current@FreeBSD.ORG In-Reply-To: <8744.881454315@time.cdrom.com> from "Jordan K. Hubbard" at Dec 6, 97 04:25:15 pm X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > It's win-win. > > Coming from the perspective of someone who doesn't actually have to do > any of the work-work involved, I'm sure it is! :-) Heh. That should be your perspective as well. The other camps would need to donate the work for them to be included. I think the ports themselves are compelling enough for them to do that. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-current Sun Dec 7 12:25:26 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id MAA19215 for current-outgoing; Sun, 7 Dec 1997 12:25:26 -0800 (PST) (envelope-from owner-freebsd-current) Received: from austin.polstra.com (austin.polstra.com [206.213.73.10]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id MAA19201 for ; Sun, 7 Dec 1997 12:25:08 -0800 (PST) (envelope-from jdp@austin.polstra.com) Received: from austin.polstra.com (jdp@localhost) by austin.polstra.com (8.8.8/8.8.7) with ESMTP id MAA07754; Sun, 7 Dec 1997 12:25:03 -0800 (PST) (envelope-from jdp) Message-Id: <199712072025.MAA07754@austin.polstra.com> To: ghormann@nix.kconline.com Subject: Re: ld.so AND emacs In-Reply-To: References: Organization: Polstra & Co., Seattle, WA Cc: current@freebsd.org Date: Sun, 07 Dec 1997 12:25:03 -0800 From: John Polstra Sender: owner-freebsd-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk In article , Greg Hormann wrote: > > Was there ever a workaround found for the emacs/ld.so problem? I searched > the archives to no avail. Yes, I already fixed it in -current. John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Self-knowledge is always bad news." -- John Barth From owner-freebsd-current Sun Dec 7 12:26:27 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id MAA19285 for current-outgoing; Sun, 7 Dec 1997 12:26:27 -0800 (PST) (envelope-from owner-freebsd-current) Received: from unix.tfs.net (node24.tfs.net [207.2.220.24]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id MAA19272 for ; Sun, 7 Dec 1997 12:26:15 -0800 (PST) (envelope-from jbryant@unix.tfs.net) Received: (from jbryant@localhost) by unix.tfs.net (8.8.8/8.8.5) id OAA01692 for freebsd-current@freebsd.org; Sun, 7 Dec 1997 14:26:11 -0600 (CST) From: Jim Bryant Message-Id: <199712072026.OAA01692@unix.tfs.net> Subject: Re: ld.so AND emacs To: freebsd-current@freebsd.org Date: Sun, 7 Dec 1997 14:26:10 -0600 (CST) Reply-to: jbryant@unix.tfs.net X-Windows: R00LZ!@# MS-Winbl0wz DR00LZ!@# X-Operating-System: FreeBSD 3.0-CURRENT #0: Mon Dec 1 15:51:40 CST 1997 X-Mailer: ELM [version 2.4ME+ PL31H (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk In reply: > Was there ever a workaround found for the emacs/ld.so problem? I searched > the archives to no avail. cvsup -current... it's been fixed... jim -- All opinions expressed are mine, if you | "I will not be pushed, stamped, think otherwise, then go jump into turbid | briefed, debriefed, indexed, or radioactive waters and yell WAHOO !!! | numbered!" - #1, "The Prisoner" ------------------------------------------------------------------------------ Inet: jbryant@tfs.net AX.25: kc5vdj@wv0t.#neks.ks.usa.noam grid: EM28pw voice: KC5VDJ - 6 & 2 Meters AM/FM/SSB, 70cm FM. http://www.tfs.net/~jbryant ------------------------------------------------------------------------------ HF/6M/2M: IC-706-MkII, 2M: HTX-212, 2M: HTX-202, 70cm: HTX-404, Packet: KPC-3+ From owner-freebsd-current Sun Dec 7 12:43:20 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id MAA20740 for current-outgoing; Sun, 7 Dec 1997 12:43:20 -0800 (PST) (envelope-from owner-freebsd-current) Received: from GndRsh.aac.dev.com (GndRsh.aac.dev.com [207.149.232.62] (may be forged)) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id MAA20708 for ; Sun, 7 Dec 1997 12:43:09 -0800 (PST) (envelope-from rgrimes@GndRsh.aac.dev.com) Received: (from rgrimes@localhost) by GndRsh.aac.dev.com (8.8.5/8.7.3) id MAA09920; Sun, 7 Dec 1997 12:42:50 -0800 (PST) From: "Rodney W. Grimes" Message-Id: <199712072042.MAA09920@GndRsh.aac.dev.com> Subject: Your ALIVE!! In-Reply-To: <199712061135.FAA01982@main.brewich.com> from Gary Clark II at "Dec 6, 97 05:35:02 am" To: gclarkii@main.brewich.com (Gary Clark II) Date: Sun, 7 Dec 1997 12:42:50 -0800 (PST) Cc: freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL25 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Hadn't seen you in quite some time on any of the lists... anyway, not to be a bearer of bad news, but you do owe me some money, It would be greatly appreciated if you could forward the payment for these two invoices ASAP: gary_clarkii.5 XNet 15 19960319 $285.00 gary_clarkii.6 XNet 15 19960408 $272.00 To: Rodney W. Grimes 877 SE Lambert Circle Gresham, OR 97080 -- Rod Grimes rgrimes@gndrsh.aac.dev.com Accurate Automation, Inc. Reliable computers for FreeBSD From owner-freebsd-current Sun Dec 7 12:50:37 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id MAA21344 for current-outgoing; Sun, 7 Dec 1997 12:50:37 -0800 (PST) (envelope-from owner-freebsd-current) Received: from trojanhorse.ml.org (mdean.vip.best.com [206.86.94.101]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id MAA21308 for ; Sun, 7 Dec 1997 12:50:24 -0800 (PST) (envelope-from jamil@trojanhorse.ml.org) Received: from localhost (jamil@localhost) by trojanhorse.ml.org (8.8.8/8.8.5) with SMTP id MAA00579; Sun, 7 Dec 1997 12:50:00 -0800 (PST) Date: Sun, 7 Dec 1997 12:50:00 -0800 (PST) From: "Jamil J. Weatherbee" To: Joao Carlos Mendes Luis cc: freebsd-current@FreeBSD.ORG Subject: wd0: Can someone explain the following errors, i.e. is this a bad ide, disk that needs to be replaced? In-Reply-To: <199712071828.QAA18606@gaia.coppe.ufrj.br> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk In trying to track reproduce some hard drive errors that caused my machine to hang while doing a build world I performed a: dd if=/dev/wd0 bs=1024k | dd if=/dev/wd0 bs=1024k wd0: 2014MB (4124736 sectors), 4092 cyls, 16 heads, 63 S/T, 512 B/S ... wd0: hard error reading fsbn 3688647 of 3688644-3688647 (wd0 bn 3688647; cn 3659 tn 5 sn 60)wd0: status 59 error 80 wd0: hard error reading fsbn 3688647 of 3688644-3688647 (wd0 bn 3688647; cn 3659 tn 5 sn 60)wd0: status 59 error 80 wd0: hard error reading fsbn 3688648 of 3688648-3688651 (wd0 bn 3688648; cn 3659 tn 5 sn 61)wd0: status 49 error 4 after that the dd stopped with an Input/Output Error Do I need to replace this drive? From owner-freebsd-current Sun Dec 7 12:51:15 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id MAA21446 for current-outgoing; Sun, 7 Dec 1997 12:51:15 -0800 (PST) (envelope-from owner-freebsd-current) Received: from smtp02.primenet.com (smtp02.primenet.com [206.165.6.132]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id MAA21353 for ; Sun, 7 Dec 1997 12:50:39 -0800 (PST) (envelope-from tlambert@usr02.primenet.com) Received: (from daemon@localhost) by smtp02.primenet.com (8.8.8/8.8.8) id OAA14745; Sun, 7 Dec 1997 14:01:33 -0700 (MST) Received: from usr02.primenet.com(206.165.6.202) via SMTP by smtp02.primenet.com, id smtpd014737; Sun Dec 7 14:01:31 1997 Received: (from tlambert@localhost) by usr02.primenet.com (8.8.5/8.8.5) id NAA29755; Sun, 7 Dec 1997 13:49:59 -0700 (MST) From: Terry Lambert Message-Id: <199712072049.NAA29755@usr02.primenet.com> Subject: Re: 3.0 -release ? To: toor@dyson.iquest.net (John S. Dyson) Date: Sun, 7 Dec 1997 20:49:59 +0000 (GMT) Cc: tlambert@primenet.com, shawn@cpl.net, chuckr@glue.umd.edu, freebsd-current@FreeBSD.ORG In-Reply-To: <199712062357.SAA07293@dyson.iquest.net> from "John S. Dyson" at Dec 6, 97 06:57:08 pm X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > > Why should the FreeBSD people make the port collection work with other > > > OS's? > > > > To get their tools to be cross-platform, and therefore be able > > to leverage work on other platforms which use the tools. > > When we have more than 1 or 2 platforms, then it will be *start* being > important. My opinions are not "PC", so if you are easily politically > offended, please cease reading here. Cross-platform (ie: cross-BSD/Linux), *not* cross-architecture. I didn't say "cross-architecture". That's a problem for those systems which run on other architectures. > > There is not sufficient coordination between the various BSD's to > > ensure that something distributed via installer may be installed > > on FreeBSD. That's what FreeBSD gets out of it. > > I see the problem with our cooperation being similar to the Microsoft > scheme of adopt, modify incompatibly and subsume. Let's not waste > our time. There is a severe amount of NIH abounding in other projects. Not sufficient for them to disdain the ports collection, it seems, however. I would like to see the OpenBSD and NetBSD folks contributing ports. Already, they consume the ports collection, and their contribution is in making the tools run on their platform, and not much beyond that. This is what I'd like to see change. > > It's win-win. > > Sadly, nope, not right now. ??? If FreeBSD people aren't doing the work to make the ports cross-platform, but OpenBSD and NetBSD folks are, I don't see what loss-instead-of-win they take. If FreeBSD people don't have to do all the work in the creation of ports, I don't see what loss-instead-of-win FreeBSD takes. The difference is in allocating some FreeBSD porting effort into cooperation in exchange for OpenBSD/NetBSD allocating some ports support effort into porting. There is no net loss for FreeBSD, and there will be a net win in sales volume for WC, and for BSD in general for third party developers who will see BSD as being more monolithic and therefore more worthy of a port. > > It also means that other people can add ports -- which offloads the > > work to non-FreeBSD people for some ports. > > It won't work that way. It will be more like our technology with > modifications will be adopted, and we will be left out in the cold. How is that possible with the WC CDROM centralized control having a definite FreeBSD bias? The only ways you will get "technology with modifications" is: 1) The modifications are valid (in which case, why is FreeBSD remaining gratuitiously incompatible in your scenario?). 2) The modifications are gratuitous (in which case the WC CDROM and Satoshi-based editorial policy will be to not include them, and they are a non-issue). > Let's continue forward, and let other groups cooperate with us. We > are much less likely to change our standards (due to inertia), and > there is safety for them in that fact. And there is danger for us in the same place. Look at gnu binutils non-support for a.out. > > Again, it's win-win. > > I think that there are some assumptions here. It is a good idea to > learn from history, and let's not make things more complicated than > they already are. The history that I'd pick as most analogous in this case would be the history of XFree86... Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-current Sun Dec 7 12:53:51 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id MAA21820 for current-outgoing; Sun, 7 Dec 1997 12:53:51 -0800 (PST) (envelope-from owner-freebsd-current) Received: from smtp03.primenet.com (smtp03.primenet.com [206.165.6.133]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id MAA21711 for ; Sun, 7 Dec 1997 12:53:19 -0800 (PST) (envelope-from tlambert@usr02.primenet.com) Received: (from daemon@localhost) by smtp03.primenet.com (8.8.8/8.8.8) id OAA19397; Sun, 7 Dec 1997 14:05:51 -0700 (MST) Received: from usr02.primenet.com(206.165.6.202) via SMTP by smtp03.primenet.com, id smtpd019361; Sun Dec 7 14:05:45 1997 Received: (from tlambert@localhost) by usr02.primenet.com (8.8.5/8.8.5) id NAA29848; Sun, 7 Dec 1997 13:52:38 -0700 (MST) From: Terry Lambert Message-Id: <199712072052.NAA29848@usr02.primenet.com> Subject: Re: 3.0 -release ? To: jkh@time.cdrom.com (Jordan K. Hubbard) Date: Sun, 7 Dec 1997 20:52:38 +0000 (GMT) Cc: tlambert@primenet.com, shawn@cpl.net, chuckr@Glue.umd.edu, freebsd-current@FreeBSD.ORG In-Reply-To: <8744.881454315@time.cdrom.com> from "Jordan K. Hubbard" at Dec 6, 97 04:25:15 pm X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > It's win-win. > > Coming from the perspective of someone who doesn't actually have to do > any of the work-work involved, I'm sure it is! :-) I sent one reply to this; here's another: Get me a copy of BSDI, and I'll do what I can to keep the ports working there, if you will accept the necessary changes and commit them, so long as they do not affect the operability of the port on FreeBSD. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-current Sun Dec 7 12:56:52 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id MAA22189 for current-outgoing; Sun, 7 Dec 1997 12:56:52 -0800 (PST) (envelope-from owner-freebsd-current) Received: from picnic.mat.net (picnic.mat.net [206.246.122.117]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id MAA22158 for ; Sun, 7 Dec 1997 12:56:26 -0800 (PST) (envelope-from chuckr@glue.umd.edu) Received: from localhost (chuckr@localhost) by picnic.mat.net (8.8.8/8.8.5) with SMTP id PAA20970; Sun, 7 Dec 1997 15:54:01 -0500 (EST) X-Authentication-Warning: picnic.mat.net: chuckr owned process doing -bs Date: Sun, 7 Dec 1997 15:54:01 -0500 (EST) From: Chuck Robey X-Sender: chuckr@picnic.mat.net To: Greg Hormann cc: current@FreeBSD.ORG Subject: Re: ld.so AND emacs In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Sun, 7 Dec 1997, Greg Hormann wrote: > > Was there ever a workaround found for the emacs/ld.so problem? I searched > the archives to no avail. John Polstra found the bug, it was in the odd way that emacs puts itself together, and the fix has already been committed to current. He said (I think) xemacs didn't have the bug. I believe that, since I've been beating the bejesus out of xemacs on this lousy lisp project I'm doing. Thank god CMU lisp is a port, and I have it working nicely with xemacs (instead of xemacs's native elisp) > > Thanks, > > Greg. > > ______________________________________________________________________________ > Greg Hormann | | | > ghormann@indiana.edu | | | > http://php.ucs.indiana.edu/~ghormann/home.html |. \____/. > ______________________________________________________________________________ > > > ----------------------------+----------------------------------------------- Chuck Robey | Interests include any kind of voice or data chuckr@glue.umd.edu | communications topic, C programming, and Unix. 213 Lakeside Drive Apt T-1 | Greenbelt, MD 20770 | I run Journey2 and picnic, both FreeBSD (301) 220-2114 | version 3.0 current -- and great FUN! ----------------------------+----------------------------------------------- From owner-freebsd-current Sun Dec 7 13:18:34 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id NAA23494 for current-outgoing; Sun, 7 Dec 1997 13:18:34 -0800 (PST) (envelope-from owner-freebsd-current) Received: from smtp04.primenet.com (smtp04.primenet.com [206.165.6.134]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id NAA23454; Sun, 7 Dec 1997 13:18:15 -0800 (PST) (envelope-from tlambert@usr02.primenet.com) Received: (from daemon@localhost) by smtp04.primenet.com (8.8.8/8.8.8) id OAA14276; Sun, 7 Dec 1997 14:19:45 -0700 (MST) Received: from usr02.primenet.com(206.165.6.202) via SMTP by smtp04.primenet.com, id smtpd014240; Sun Dec 7 14:19:38 1997 Received: (from tlambert@localhost) by usr02.primenet.com (8.8.5/8.8.5) id OAA00995; Sun, 7 Dec 1997 14:17:33 -0700 (MST) From: Terry Lambert Message-Id: <199712072117.OAA00995@usr02.primenet.com> Subject: Re: 3.0 -release ? To: grog@lemis.com (Greg Lehey) Date: Sun, 7 Dec 1997 21:17:33 +0000 (GMT) Cc: tlambert@primenet.com, ports@FreeBSD.ORG, current@FreeBSD.ORG In-Reply-To: <19971207165932.28970@lemis.com> from "Greg Lehey" at Dec 7, 97 04:59:32 pm X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > Great idea! Yes, I've read the multitude of messages that have come > in so far. But you've missed one point: why don't we merge FreeBSD, > NetBSD and OpenBSD? Maybe BSD/OS as well? After all, most people > don't understand why there are so many BSDs anyway. > > What, you say, they don't want to cooperate? They would lose control of something which they already have control over, and for which control is the desired end product (and OS's are nothing more than a neat side effect). > Oh. So why should they > want to cooperate on the question of the Ports Collection? Because they have something to gain personally by doing so... unlike merging the BSD's. Any merge will have to appeal to people without stepping into an area manned by their egos. The ports collection has not be seperately fenced in the process of kingdom-building, and thus is something on which the camps can cooperate on, where the marginal benefit is obviously greater than the marginal cost. Sure, NetBSD, OpenBSD, and FreeBSD could be merged, and sure, the marginal benefit would be greater than the marginal cost. It's just not that obvious, and three years of attempts at education on the mathematical basis underlying positive sum games theory have failed to make it non-obvious-but-well-understood. So at this time, an OS merge is a potitically dead end. But a ports merge is not. > Sure, the Ports Collection would be easier. It's less coupled with > the kernel. But does anybody out there really see all four (three?) > teams getting together and coordinating the mess? Has anyone with any official standing within the FreeBSD team *asked* anyone with any official standing at the other teams? Certainly, it would be to Jordan's benefit: it would buy him a broader market for a decoupled ports CD product, and maybe even packaging and coadvertising from BSDI for the thing. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-current Sun Dec 7 13:37:10 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id NAA24936 for current-outgoing; Sun, 7 Dec 1997 13:37:10 -0800 (PST) (envelope-from owner-freebsd-current) Received: from Kitten.mcs.com (Kitten.mcs.com [192.160.127.90]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id NAA24921 for ; Sun, 7 Dec 1997 13:36:53 -0800 (PST) (envelope-from karl@Mars.mcs.net) Received: from Mars.mcs.net (karl@Mars.mcs.net [192.160.127.85]) by Kitten.mcs.com (8.8.7/8.8.2) with ESMTP id PAA05684; Sun, 7 Dec 1997 15:36:52 -0600 (CST) Received: (from karl@localhost) by Mars.mcs.net (8.8.7/8.8.2) id PAA14601; Sun, 7 Dec 1997 15:36:52 -0600 (CST) Message-ID: <19971207153652.49391@mcs.net> Date: Sun, 7 Dec 1997 15:36:52 -0600 From: Karl Denninger To: Terry Lambert Cc: current@FreeBSD.ORG, Jim.Zelenka@cs.cmu.edu Subject: Re: Diffs to support RAIDframe on FreeBSD References: <19971205163442.52313@mcs.net> <199712062156.OAA09278@usr02.primenet.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.84 In-Reply-To: <199712062156.OAA09278@usr02.primenet.com>; from Terry Lambert on Sat, Dec 06, 1997 at 09:56:21PM +0000 Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Does anyone want to turn this into a port? It appears that this, along with baseline support for the AAA-130 series Adaptec controllers, gives us instant RAID on FreeBSD. That is, if it actually works. -- -- Karl Denninger (karl@MCS.Net)| MCSNet - Serving Chicagoland and Wisconsin http://www.mcs.net/ | T1's from $600 monthly to FULL DS-3 Service | NEW! K56Flex support on ALL modems Voice: [+1 312 803-MCS1 x219]| EXCLUSIVE NEW FEATURE ON ALL PERSONAL ACCOUNTS Fax: [+1 312 803-4929] | *SPAMBLOCK* Technology now included at no cost On Sat, Dec 06, 1997 at 09:56:21PM +0000, Terry Lambert wrote: > > > > Anyone gotten this to build and link on FreeBSD? > > > > > > URL, please. AltaVista has never heard of it. > > > > http://www.pdl.cs.cmu.edu/RAIDframe/ > > This was trivial. Here are the Diffs for FreeBSD. > > Jim Zelenka: I have added you to the people receiving this so you > can integrate them into the RAIDFrame distribution itself. > > > > Terry Lambert > terry@lambert.org > --- > Any opinions in this posting are my own and not those of my present > or previous employers. > =============================================================================== > *** SAVE/itomf Tue Nov 5 21:21:05 1996 > --- itomf Sat Dec 6 21:46:19 1997 > *************** > *** 50,55 **** > --- 50,57 ---- > imake -I./config -I$X11CFGDIR -DUseInstalled -DTOPDIR=. -DSCD_SRCTOP=`pwd` -DRF_ITOMF=1 -DRF_X11CONFIGDIR=$X11CFGDIR -DRF_MAKEDEPEND=$MAKEDEPEND > elif [ $SYS = "NetBSD" ]; then > imake -I./config -I$X11CFGDIR -DUseInstalled -DTOPDIR=. -DSCD_SRCTOP=`pwd` -DRF_ITOMF=1 -DRF_X11CONFIGDIR=$X11CFGDIR -DRF_MAKEDEPEND=$MAKEDEPEND > + elif [ $SYS = "FreeBSD" ]; then > + imake -v -I./config -I$X11CFGDIR -DUseInstalled -DTOPDIR=. -DSCD_SRCTOP=`pwd` -DRF_ITOMF=1 -DRF_X11CONFIGDIR=$X11CFGDIR -DRF_MAKEDEPEND=$MAKEDEPEND > elif [ $SYS = "IRIX" ]; then > imake -I./config -I$X11CFGDIR -DUseInstalled -DTOPDIR=. -DSCD_SRCTOP=`pwd` -DRF_ITOMF=1 -DRF_X11CONFIGDIR=$X11CFGDIR -DRF_MAKEDEPEND=$MAKEDEPEND > elif [ $SYS = "OSF1" ]; then > *************** > *** 63,69 **** > elif [ $SYS = "HP-UX" ]; then > imake -I./config -I$X11CFGDIR -DUseInstalled -DTOPDIR=. -DSCD_SRCTOP=`pwd` -DRF_ITOMF=1 -DRF_X11CONFIGDIR=$X11CFGDIR -DRF_MAKEDEPEND=$MAKEDEPEND > else > ! echo "Unknown system type." > exit 1 > fi > make Makefiles > --- 65,71 ---- > elif [ $SYS = "HP-UX" ]; then > imake -I./config -I$X11CFGDIR -DUseInstalled -DTOPDIR=. -DSCD_SRCTOP=`pwd` -DRF_ITOMF=1 -DRF_X11CONFIGDIR=$X11CFGDIR -DRF_MAKEDEPEND=$MAKEDEPEND > else > ! echo "Unknown system type ($SYS)." > exit 1 > fi > make Makefiles > *** SAVE/config/RAIDframe.tmpl Sat Dec 6 21:13:15 1997 > --- config/RAIDframe.tmpl Sat Dec 6 21:47:33 1997 > *************** > *** 36,41 **** > --- 36,48 ---- > #define RF_MakeSubdirs(_dirs_) MakeSubdirs(_dirs_) > #endif /* AIXArchitecture && (RF_OSMajorVersion == 4) */ > > + #ifdef FreeBSDArchitecture > + #ifdef i386Architecture > + ARCHDEFINES = -DFREEBSD -DFREEBSD_I386 > + #endif /* i386Architecture */ > + #define RF_ROLLED_SRCTOP 1 > + #endif /* FreeBSDArchitecture */ > + > #ifdef NetBSDArchitecture > #ifdef i386Architecture > ARCHDEFINES = -DNETBSD -DNETBSD_I386 > *** SAVE/config/RAIDframe_site.def Sat Dec 6 21:13:15 1997 > --- config/RAIDframe_site.def Sat Dec 6 21:16:44 1997 > *************** > *** 60,70 **** > ARCHLIBS= > #endif /* OSF1 && AlphaArchitecture */ > > ! #if defined(NetBSDArchitecture) && defined(AlphaArchitecture) > CC = gcc > CDEBUGFLAGS = -g3 -O2 > ARCHLIBS= > ! #endif /* NetBSDArchitecture && AlphaArchitecture */ > > #ifdef AIXArchitecture > #if RF_OSMajorVersion == 4 > --- 60,70 ---- > ARCHLIBS= > #endif /* OSF1 && AlphaArchitecture */ > > ! #if (defined(NetBSDArchitecture) || defined(FreeBSDArchitecture)) && defined(AlphaArchitecture) > CC = gcc > CDEBUGFLAGS = -g3 -O2 > ARCHLIBS= > ! #endif /* (NetBSDArchitecture || FreeBSDArchitecture) && AlphaArchitecture */ > > #ifdef AIXArchitecture > #if RF_OSMajorVersion == 4 > *** SAVE/lib/rf_copyback.c Sat Dec 6 21:22:18 1997 > --- lib/rf_copyback.c Sat Dec 6 21:24:28 1997 > *************** > *** 145,150 **** > --- 145,153 ---- > #include "rf_types.h" > #include > #ifndef LINUX > + #ifdef FREEBSD > + #include /* MAXPHYS*/ > + #endif /* FREEBSD*/ > #include > #endif /* !LINUX */ > #include "rf_raid.h" > *** SAVE/lib/rf_types.h Sat Dec 6 21:26:08 1997 > --- lib/rf_types.h Sat Dec 6 21:28:11 1997 > *************** > *** 328,334 **** > #define RF_LONGSHIFT 2 > #endif /* sun */ > > ! #if defined(NETBSD_I386) || defined(LINUX_I386) > #define RF_IS_BIG_ENDIAN 0 > typedef char RF_int8; > typedef unsigned char RF_uint8; > --- 328,334 ---- > #define RF_LONGSHIFT 2 > #endif /* sun */ > > ! #if defined(FREEBSD_I386) || defined(NETBSD_I386) || defined(LINUX_I386) > #define RF_IS_BIG_ENDIAN 0 > typedef char RF_int8; > typedef unsigned char RF_uint8; > *************** > *** 339,345 **** > typedef long long RF_int64; > typedef unsigned long long RF_uint64; > #define RF_LONGSHIFT 2 > ! #endif /* NETBSD_I386 || LINUX_I386 */ > > #if defined(mips) && !defined(SGI) > #define RF_IS_BIG_ENDIAN 0 > --- 339,345 ---- > typedef long long RF_int64; > typedef unsigned long long RF_uint64; > #define RF_LONGSHIFT 2 > ! #endif /* FREEBSD_I386 || NETBSD_I386 || LINUX_I386 */ > > #if defined(mips) && !defined(SGI) > #define RF_IS_BIG_ENDIAN 0 > *** SAVE/lib/rf_sys.c Sat Dec 6 21:26:08 1997 > --- lib/rf_sys.c Sat Dec 6 21:27:25 1997 > *************** > *** 39,47 **** > #include > #endif /* !KERNEL */ > #include > ! #if !defined(sun) && !defined(NETBSD) && !defined(LINUX) && (!defined(MACH) || defined(__osf__)) > #include > ! #endif /* !sun !NETBSD && !LINUX && (!MACH || __osf__) */ > #include > #ifdef __osf__ > #include > --- 39,47 ---- > #include > #endif /* !KERNEL */ > #include > ! #if !defined(sun) && !defined(FREEBSD) && !defined(NETBSD) && !defined(LINUX) && (!defined(MACH) || defined(__osf__)) > #include > ! #endif /* !sun !FREEBSD !NETBSD && !LINUX && (!MACH || __osf__) */ > #include > #ifdef __osf__ > #include > *** SAVE/lib/rf_etimer.h Sat Dec 6 21:26:34 1997 > --- lib/rf_etimer.h Sat Dec 6 21:28:43 1997 > *************** > *** 254,260 **** > /* > * XXX investigate better timing for these > */ > ! #if defined(hpux) || defined(sun) || defined(NETBSD_I386) || defined(ultrix) || defined(LINUX_I386) || defined(IRIX) || (defined(MACH) && !defined(__osf__)) > #include > > #define RF_USEC_PER_SEC 1000000 > --- 254,260 ---- > /* > * XXX investigate better timing for these > */ > ! #if defined(hpux) || defined(sun) || defined(FREEBSD_I386) || defined(NETBSD_I386) || defined(ultrix) || defined(LINUX_I386) || defined(IRIX) || (defined(MACH) && !defined(__osf__)) > #include > > #define RF_USEC_PER_SEC 1000000 > *************** > *** 288,293 **** > #define RF_ETIMER_VAL_US(_t_) (((_t_).elapsed.tv_sec*RF_USEC_PER_SEC)+(_t_).elapsed.tv_usec) > #define RF_ETIMER_VAL_MS(_t_) (((_t_).elapsed.tv_sec*RF_MSEC_PER_SEC)+((_t_).elapsed.tv_usec/1000)) > > ! #endif /* hpux || sun || NETBSD_I386 || ultrix || LINUX_I386 || IRIX || (MACH && !__osf__) */ > > #endif /* !_RF__RF_TIMER_H_ */ > --- 288,293 ---- > #define RF_ETIMER_VAL_US(_t_) (((_t_).elapsed.tv_sec*RF_USEC_PER_SEC)+(_t_).elapsed.tv_usec) > #define RF_ETIMER_VAL_MS(_t_) (((_t_).elapsed.tv_sec*RF_MSEC_PER_SEC)+((_t_).elapsed.tv_usec/1000)) > > ! #endif /* hpux || sun || FREEBSD_I386 || NETBSD_I386 || ultrix || LINUX_I386 || IRIX || (MACH && !__osf__) */ > > #endif /* !_RF__RF_TIMER_H_ */ > *** SAVE/lib/rf_general.h Sat Dec 6 21:38:19 1997 > --- lib/rf_general.h Sat Dec 6 21:38:31 1997 > *************** > *** 213,218 **** > --- 213,225 ---- > #endif /* !NBPG */ > #endif /* sun */ > > + #ifdef FREEBSD > + #include > + #ifndef NBPG > + #define NBPG PAGE_SIZE > + #endif /* !NBPG*/ > + #endif /* FREEBSD*/ > + > #ifdef IRIX > #include > #define NBPG _PAGESZ > *** SAVE/lib/rf_reconstruct.c Sat Dec 6 21:39:56 1997 > --- lib/rf_reconstruct.c Sat Dec 6 21:41:18 1997 > *************** > *** 213,218 **** > --- 213,221 ---- > #include "rf_types.h" > #include > #ifndef LINUX > + #ifdef FREEBSD > + #include /* MAXPHYS*/ > + #endif /* FREEBSD*/ > #include > #endif /* !LINUX */ > #include > =============================================================================== From owner-freebsd-current Sun Dec 7 13:49:04 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id NAA25517 for current-outgoing; Sun, 7 Dec 1997 13:49:04 -0800 (PST) (envelope-from owner-freebsd-current) Received: from smtp02.primenet.com (smtp02.primenet.com [206.165.6.132]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id NAA25508 for ; Sun, 7 Dec 1997 13:48:49 -0800 (PST) (envelope-from tlambert@usr02.primenet.com) Received: (from daemon@localhost) by smtp02.primenet.com (8.8.8/8.8.8) id OAA22784; Sun, 7 Dec 1997 14:59:41 -0700 (MST) Received: from usr02.primenet.com(206.165.6.202) via SMTP by smtp02.primenet.com, id smtpd022746; Sun Dec 7 14:59:34 1997 Received: (from tlambert@localhost) by usr02.primenet.com (8.8.5/8.8.5) id OAA02369; Sun, 7 Dec 1997 14:48:05 -0700 (MST) From: Terry Lambert Message-Id: <199712072148.OAA02369@usr02.primenet.com> Subject: Re: Diffs to support RAIDframe on FreeBSD To: karl@mcs.net (Karl Denninger) Date: Sun, 7 Dec 1997 21:48:05 +0000 (GMT) Cc: tlambert@primenet.com, current@FreeBSD.ORG, Jim.Zelenka@cs.cmu.edu In-Reply-To: <19971207153652.49391@mcs.net> from "Karl Denninger" at Dec 7, 97 03:36:52 pm X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > Does anyone want to turn this into a port? > > It appears that this, along with baseline support for the AAA-130 series > Adaptec controllers, gives us instant RAID on FreeBSD. > > That is, if it actually works. Please wait for them to incorporate the changes so there is no patching necessary for FreeBSD. That's why I put the CMU people on the "To:" line of the patches. Note that the use of Imake (the correct way to do cross-platform configuration... die, configure, die!) semi-requires X11 because of the incorrect way we install Imake from the X11 distribution instead of it being a standard system component. A port *might* want to make the FreeBSD Makefiles. Note that if it did this, it would need to "touch" them to make sure they were not recreated (with no tool to do it) from the Imakefiles. The touch would need to occur on each "install". Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-current Sun Dec 7 14:12:10 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id OAA27174 for current-outgoing; Sun, 7 Dec 1997 14:12:10 -0800 (PST) (envelope-from owner-freebsd-current) Received: from hyperreal.org (taz.hyperreal.org [204.62.130.147]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id OAA27138 for ; Sun, 7 Dec 1997 14:12:03 -0800 (PST) (envelope-from anonymous@hyperreal.org) Received: (qmail 9050 invoked by uid 24); 7 Dec 1997 22:11:58 -0000 Message-Id: <3.0.3.32.19971207135710.00924100@hyperreal.org> X-Sender: brian@hyperreal.org X-Mailer: QUALCOMM Windows Eudora Pro Version 3.0.3 (32) Date: Sun, 07 Dec 1997 13:57:10 -0800 To: Greg Lehey , Terry Lambert From: Brian Behlendorf Subject: Re: 3.0 -release ? Cc: ports@FreeBSD.ORG, current@FreeBSD.ORG In-Reply-To: <19971207165932.28970@lemis.com> References: <199712052004.NAA16482@usr08.primenet.com> <28074.881287489@time.cdrom.com> <199712052004.NAA16482@usr08.primenet.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk At 04:59 PM 12/7/97 +0800, Greg Lehey wrote: >What, you say, they don't want to cooperate? Oh. So why should they >want to cooperate on the question of the Ports Collection? Didn't a number of the PC-based Unix "vendors" (including Linus himself) get together recently and decide to work together on a common binary code format? Anyone have a reference for that? I'll agree that it's usually politics and hubris that keep the BSD's from merging more than anything else. It doesn't mean there are bits and pieces that couldn't be integrated, and that there wouldn't be benefit from doing so. Brian --=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-- "it's a big world, with lots of records to play."-sig brian@hyperreal.org From owner-freebsd-current Sun Dec 7 14:39:27 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id OAA29358 for current-outgoing; Sun, 7 Dec 1997 14:39:27 -0800 (PST) (envelope-from owner-freebsd-current) Received: from trojanhorse.ml.org (mdean.vip.best.com [206.86.94.101]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id OAA29353 for ; Sun, 7 Dec 1997 14:39:22 -0800 (PST) (envelope-from jamil@trojanhorse.ml.org) Received: from localhost (jamil@localhost) by trojanhorse.ml.org (8.8.8/8.8.5) with SMTP id OAA16006 for ; Sun, 7 Dec 1997 14:39:07 -0800 (PST) Date: Sun, 7 Dec 1997 14:39:06 -0800 (PST) From: "Jamil J. Weatherbee" To: freebsd-current@FreeBSD.ORG Subject: npx problem configing in -current In-Reply-To: <348AE151.4190@shellnet.co.uk> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk # config TROJANHORSE Removing old directory ../../compile/TROJANHORSE: Done. files.i386: i386/isa/npx.c must be optional or standard I have the line: device npx0 at isa? port "IO_NPX" irq 13 vector npxintr in my config file. So is the line in files.i386 i386/isa/npx.c mandatory npx device-driver supposed to be: i386/isa/npx.c standard npx device-driver ??? From owner-freebsd-current Sun Dec 7 14:55:16 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id OAA00763 for current-outgoing; Sun, 7 Dec 1997 14:55:16 -0800 (PST) (envelope-from owner-freebsd-current) Received: from trojanhorse.ml.org (mdean.vip.best.com [206.86.94.101]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id OAA00721 for ; Sun, 7 Dec 1997 14:54:56 -0800 (PST) (envelope-from jamil@trojanhorse.ml.org) Received: from localhost (jamil@localhost) by trojanhorse.ml.org (8.8.8/8.8.5) with SMTP id OAA19691 for ; Sun, 7 Dec 1997 14:54:40 -0800 (PST) Date: Sun, 7 Dec 1997 14:54:40 -0800 (PST) From: "Jamil J. Weatherbee" To: freebsd-current@FreeBSD.ORG Subject: Re: npx problem configing in -current In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Never mind, maybye I need to let my -current make world complete first!?! On Sun, 7 Dec 1997, Jamil J. Weatherbee wrote: > > # config TROJANHORSE > Removing old directory ../../compile/TROJANHORSE: Done. > files.i386: i386/isa/npx.c must be optional or standard > > > I have the line: > > device npx0 at isa? port "IO_NPX" irq 13 vector npxintr > > in my config file. > > So is the line in files.i386 > > i386/isa/npx.c mandatory npx device-driver > > supposed to be: > > i386/isa/npx.c standard npx device-driver > > ??? > > > > > From owner-freebsd-current Sun Dec 7 15:17:41 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id PAA02237 for current-outgoing; Sun, 7 Dec 1997 15:17:41 -0800 (PST) (envelope-from owner-freebsd-current) Received: from GndRsh.aac.dev.com (GndRsh.aac.dev.com [207.149.232.62] (may be forged)) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id PAA02213 for ; Sun, 7 Dec 1997 15:17:12 -0800 (PST) (envelope-from rgrimes@GndRsh.aac.dev.com) Received: (from rgrimes@localhost) by GndRsh.aac.dev.com (8.8.5/8.7.3) id PAA10136; Sun, 7 Dec 1997 15:15:37 -0800 (PST) From: "Rodney W. Grimes" Message-Id: <199712072315.PAA10136@GndRsh.aac.dev.com> Subject: Re: Your ALIVE!! In-Reply-To: <199712072042.MAA09920@GndRsh.aac.dev.com> from "Rodney W. Grimes" at "Dec 7, 97 12:42:50 pm" To: rgrimes@GndRsh.aac.dev.com (Rodney W. Grimes) Date: Sun, 7 Dec 1997 15:15:37 -0800 (PST) Cc: gclarkii@main.brewich.com, freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL25 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > Hadn't seen you in quite some time on any of the lists... anyway, I must appologize to Gary, and everone else, this was _NOT_ meant to be cc'ed onto the list... I couldn't kill sendmail quick enough to stop my blunder which I realized just as the headers flashed by :-(... -- Rod Grimes rgrimes@gndrsh.aac.dev.com Accurate Automation, Inc. Reliable computers for FreeBSD From owner-freebsd-current Sun Dec 7 16:44:41 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id QAA08520 for current-outgoing; Sun, 7 Dec 1997 16:44:41 -0800 (PST) (envelope-from owner-freebsd-current) Received: from ns1.yes.no (ns1.yes.no [195.119.24.10]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id QAA08491; Sun, 7 Dec 1997 16:44:31 -0800 (PST) (envelope-from eivind@bitbox.follo.net) Received: from bitbox.follo.net (bitbox.follo.net [194.198.43.36]) by ns1.yes.no (8.8.7/8.8.7) with ESMTP id AAA07989; Mon, 8 Dec 1997 00:44:28 GMT Received: (from eivind@localhost) by bitbox.follo.net (8.8.6/8.8.6) id BAA10173; Mon, 8 Dec 1997 01:44:00 +0100 (MET) To: dyson@FreeBSD.ORG Cc: current@FreeBSD.ORG Subject: Re: VM system info References: <199712071829.NAA03407@dyson.iquest.net> From: Eivind Eklund Date: 08 Dec 1997 01:43:59 +0100 In-Reply-To: "John S. Dyson"'s message of Sun, 7 Dec 1997 13:29:42 -0500 (EST) Message-ID: <867m9gpsts.fsf@bitbox.follo.net> Lines: 35 X-Mailer: Gnus v5.4.52/XEmacs 20.2 Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk "John S. Dyson" writes: > Joao Carlos Mendes Luis said: > > #define quoting(John S. Dyson) > > // Notes on VM tunables: > > // > > // I have recently added some interesting VM tunables. Since it would > > // be nice if people other than me (or those who requested them) could > > // use the features, I thought it would be nice to pass this info on: > > > > Is there any place or URL where we can get this information always > > updated ? It's a pretty good form of documentation I've always > > wanted to know. > > > Nope. Unfortunately, the source code is the only place for it (by > inference.) The VFS sysctls also deserve some documentation. > > > > > Maybe it deserves a handbook section ? > > > Maybe, but it is extremely kernel version dependent, and would require > some commitment to maintain. Otherwise, the info could be confusing. I'm going to be extremely politically incorrect here: I want this info in the kernel. At the very least, I want documentation as a part of the SYSCTL_*() macro parameters, unused but available as a (mandatory) part of the source - better would be as a part of the kernel that can be compiled away by setting a kernel option (e.g. NO_SYSCTL_DOCS). I don't care about the amount of hardwired memory it wastes - memory is extremely cheap, people's time aren't. Eivind. From owner-freebsd-current Sun Dec 7 17:52:12 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id RAA14359 for current-outgoing; Sun, 7 Dec 1997 17:52:12 -0800 (PST) (envelope-from owner-freebsd-current) Received: from dyson.iquest.net (dyson.iquest.net [198.70.144.127]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id RAA14290; Sun, 7 Dec 1997 17:51:50 -0800 (PST) (envelope-from toor@dyson.iquest.net) Received: (from root@localhost) by dyson.iquest.net (8.8.8/8.8.8) id UAA00245; Sun, 7 Dec 1997 20:51:43 -0500 (EST) (envelope-from toor) From: "John S. Dyson" Message-Id: <199712080151.UAA00245@dyson.iquest.net> Subject: Re: VM system info In-Reply-To: <867m9gpsts.fsf@bitbox.follo.net> from Eivind Eklund at "Dec 8, 97 01:43:59 am" To: perhaps@yes.no (Eivind Eklund) Date: Sun, 7 Dec 1997 20:51:43 -0500 (EST) Cc: dyson@FreeBSD.ORG, current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL31 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Eivind Eklund said: > > I'm going to be extremely politically incorrect here: > That is perfectly okay :-). I think we are all supposed to discuss, and not just rubber-stamp :-). > > I want this info in the kernel. At the very least, I want > documentation as a part of the SYSCTL_*() macro parameters, unused but > available as a (mandatory) part of the source - better would be as a > part of the kernel that can be compiled away by setting a kernel > option (e.g. NO_SYSCTL_DOCS). > The biggest problem with that is the size of the "documentation." I agree that it would be a good idea to document everything. Internally would be nice (I guess), because it would tend to stay better in sync. Some kind of literate programming scheme would be interesting also. > > I don't care about the amount of hardwired memory it wastes - memory > is extremely cheap, people's time aren't. > I understand, since it is likely that all of the internal strings wouldn't be larger than say 64K, that is a drop in the bucket for the system, and could be disabled anyway. I just don't know what to think about your notion, it *might* be a good idea for the kernel. I know that the sysctls can be tedious to wade through, and some of the features might not be clear. I don't know what the rest of the other FreeBSD developers think about this idea, and it would be a good idea to get more input. All I know is that now when people run out of swap space, I can tell them the sysctl to turn paging off :-). Then they won't try to use any more :-). -- John dyson@freebsd.org jdyson@nc.com From owner-freebsd-current Sun Dec 7 18:11:05 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id SAA15802 for current-outgoing; Sun, 7 Dec 1997 18:11:05 -0800 (PST) (envelope-from owner-freebsd-current) Received: from whqvax.picker.com (whqvax.picker.com [144.54.1.1]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id SAA15782 for ; Sun, 7 Dec 1997 18:10:49 -0800 (PST) (envelope-from rhh@ct.picker.com) Received: from ct.picker.com by whqvax.picker.com with SMTP; Sun, 7 Dec 1997 21:06:17 -0500 (EST) Received: from elmer.ct.picker.com by ct.picker.com (4.1/SMI-4.1) id AA03910; Sun, 7 Dec 97 21:06:14 EST Received: by elmer.ct.picker.com (SMI-8.6/SMI-SVR4) id VAA21243; Sun, 7 Dec 1997 21:05:45 -0500 Message-Id: <19971207210544.52901@ct.picker.com> Date: Sun, 7 Dec 1997 21:05:44 -0500 From: Randall Hopper To: Stephen Hocking , Studded , Brian Somers , John Fieber , David Dawes , Bruce Evans Cc: current@FreeBSD.ORG Subject: Re: Oddity with netscape and current References: <199712061101.VAA00582@zzshocki.dialin.uq.net.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.81 In-Reply-To: <199712061101.VAA00582@zzshocki.dialin.uq.net.au>; from Stephen Hocking on Sat, Dec 06, 1997 at 09:01:08PM +1000 Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Stephen Hocking: | Quite a lot I find that after launching netscape, itwill go into a |tight loop, consuming all the CPU on a ration of about 30% user & 70% system. |This has just happened, at src-cur.3160. Has anyone else seen it? This is |netscape 4.04 communicator. Yes. I've also been annoyed with the 4.04 lockups, especially now that 4.03b8 has expired. 3.01 has been a fallback lately. I followed this thread (and others on the lists) regarding hack-arounds, and so far, none have coerced Netscape 4.04 here into behaving itself for any length of time. So, while we're on the subject, could you all try a 4.04 test?: 1) In 4.04, turn ON Java and Javascript & turn OFF auto-loading of images. Then exit 4.04. 2) Finally, invoke: \ 'http://necxdirect.necx.com:8002/cgi-bin/auth/docroot/index.html?nonce=guest' If you don't get a lock-up, I'd sure like to see your wrapper script and preferences.js! This is just one of many pages on which 4.04 here freezes and takes any remaining CPU with it. Thanks, Randall From owner-freebsd-current Sun Dec 7 18:23:00 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id SAA16820 for current-outgoing; Sun, 7 Dec 1997 18:23:00 -0800 (PST) (envelope-from owner-freebsd-current) Received: from tera.com (tera.tera.com [207.108.223.21]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id SAA16808; Sun, 7 Dec 1997 18:22:51 -0800 (PST) (envelope-from kline@tao.thought.org) Received: (from uucp@localhost) by tera.com (8.8.7/8.8.7) with UUCP id SAA03167; Sun, 7 Dec 1997 18:19:39 -0800 (PST) Received: (from kline@localhost) by tao.thought.org (8.8.5/8.7.3) id RAA01035; Sun, 7 Dec 1997 17:51:48 -0800 (PST) From: Gary Kline Message-Id: <199712080151.RAA01035@tao.thought.org> Subject: Re: 3.0 -release ? In-Reply-To: <3.0.3.32.19971207135710.00924100@hyperreal.org> from Brian Behlendorf at "Dec 7, 97 01:57:10 pm" To: brian@hyperreal.org (Brian Behlendorf) Date: Sun, 7 Dec 1997 17:51:48 -0800 (PST) Cc: grog@lemis.com, tlambert@primenet.com, ports@FreeBSD.ORG, current@FreeBSD.ORG Organization: <> thought.org: public access uNix in service... <> X-Mailer: ELM [version 2.4ME+ PL32 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk According to Brian Behlendorf: > > Didn't a number of the PC-based Unix "vendors" (including Linus himself) > get together recently and decide to work together on a common binary code > format? Anyone have a reference for that? I read that somewhere:: EE TIMES, maybe... ((?)) > > I'll agree that it's usually politics and hubris that keep the BSD's from > merging more than anything else. It doesn't mean there are bits and pieces > that couldn't be integrated, and that there wouldn't be benefit from doing so. > Yes, and a common set of source-only ports for the *BSD's and *Linux's (and the HURD) is the best place to start. Not only the major ports that can be ftp'd, but the more obscure freeware projects are candidates. Something like PTF, but that would work after only a compile. No tweaking, no head-pounding. I understand Jordan's need to focus on FBSD, of course. This might be a niche for enterprising hackers who can invest hundred-hour weeks for months, years. gary PS to Terry Lambert: Your last note was well-written and insightful++; that about summed it up. > > -- -- Gary D. Kline kline@tao.thought.org Public service uNix From owner-freebsd-current Sun Dec 7 19:59:15 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id TAA24838 for current-outgoing; Sun, 7 Dec 1997 19:59:15 -0800 (PST) (envelope-from owner-freebsd-current) Received: from ache.relcom.ru (ache.relcom.ru [193.125.20.108]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id TAA24828 for ; Sun, 7 Dec 1997 19:59:07 -0800 (PST) (envelope-from ache@ache.relcom.ru) Received: (from ache@localhost) by ache.relcom.ru (8.8.8/8.8.8) id GAA00228; Mon, 8 Dec 1997 06:57:04 +0300 (MSK) (envelope-from ache) Date: Mon, 8 Dec 1997 06:57:00 +0300 (MSK) From: =?KOI8-R?B?4c7E0sXKIP7F0s7P1w==?= X-Sender: ache@ache.relcom.ru To: Luigi Rizzo cc: dstenn@fanfic.org, current@FreeBSD.ORG Subject: Re: PnP code (was: Re: SB AWE64 support) In-Reply-To: <199712061037.LAA25626@labinfo.iet.unipi.it> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Sat, 6 Dec 1997, Luigi Rizzo wrote: > BUT: if you want the kernel to override and PnP configuration set (or > not set) by the bios, which is what "os enable" does, that should never > happen, at least not in the driver. Hmm, why not? I.e. if pnp code sees awe0 at 0x620 in configuration file, why not "os enable" other 2 ports automatically? What is some possible bad effects I overlook? > We can write extensive documentation on how to use the _manual_ > PnP configuration features, perhaps imrove the user interface so > one does not have to use criptic numbers but more significant names, > but that's about it. I think this awe hack should be mentioned at least in some visible place like LINT... -- Andrey A. Chernov http://www.nagual.pp.ru/~ache/ From owner-freebsd-current Sun Dec 7 20:43:30 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id UAA27653 for current-outgoing; Sun, 7 Dec 1997 20:43:30 -0800 (PST) (envelope-from owner-freebsd-current) Received: from thunderdome.plutotech.com (root@thunderdome.plutotech.com [206.168.67.122]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id UAA27638 for ; Sun, 7 Dec 1997 20:43:20 -0800 (PST) (envelope-from ken@panzer.plutotech.com) Received: from panzer.plutotech.com (ken@panzer.plutotech.com [206.168.67.125]) by thunderdome.plutotech.com (8.8.7/8.8.5) with ESMTP id VAA03830; Sun, 7 Dec 1997 21:43:17 -0700 (MST) Received: (from ken@localhost) by panzer.plutotech.com (8.8.7/8.8.5) id VAA21558; Sun, 7 Dec 1997 21:43:14 -0700 (MST) Message-Id: <199712080443.VAA21558@panzer.plutotech.com> Subject: Re: Oddity with netscape and current In-Reply-To: <19971207210544.52901@ct.picker.com> from Randall Hopper at "Dec 7, 97 09:05:44 pm" To: rhh@ct.picker.com (Randall Hopper) Date: Sun, 7 Dec 1997 21:43:14 -0700 (MST) Cc: shocking@mailbox.uq.edu.au, Studded@dal.net, brian@awfulhak.org, jfieber@indiana.edu, dawes@rf900.physics.usyd.edu.au, bde@zeta.org.au, current@FreeBSD.ORG From: Kenneth Merry X-Mailer: ELM [version 2.4ME+ PL28s (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Randall Hopper wrote... > So, while we're on the subject, could you all try a 4.04 test?: > > 1) In 4.04, turn ON Java and Javascript & turn OFF auto-loading of > images. Then exit 4.04. > > 2) Finally, invoke: > > \ > 'http://necxdirect.necx.com:8002/cgi-bin/auth/docroot/index.html?nonce=guest' > > If you don't get a lock-up, I'd sure like to see your wrapper script and > preferences.js! This is just one of many pages on which 4.04 here freezes > and takes any remaining CPU with it. My solution has just been to disable Java when going to their web page. It's a rogue java applet that causes the problem, so turning off Java does the trick. Ken -- Kenneth Merry ken@plutotech.com From owner-freebsd-current Sun Dec 7 23:02:12 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id XAA06733 for current-outgoing; Sun, 7 Dec 1997 23:02:12 -0800 (PST) (envelope-from owner-freebsd-current) Received: from ns.mt.sri.com (sri-gw.MT.net [206.127.105.141]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id XAA06719 for ; Sun, 7 Dec 1997 23:02:05 -0800 (PST) (envelope-from nate@mt.sri.com) Received: from mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by ns.mt.sri.com (8.8.8/8.8.8) with SMTP id AAA18845; Mon, 8 Dec 1997 00:02:00 -0700 (MST) (envelope-from nate@rocky.mt.sri.com) Received: by mt.sri.com (SMI-8.6/SMI-SVR4) id AAA10388; Mon, 8 Dec 1997 00:01:57 -0700 Date: Mon, 8 Dec 1997 00:01:57 -0700 Message-Id: <199712080701.AAA10388@mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Terry Lambert Cc: karl@mcs.net (Karl Denninger), current@FreeBSD.ORG, Jim.Zelenka@cs.cmu.edu Subject: Re: Diffs to support RAIDframe on FreeBSD In-Reply-To: <199712072148.OAA02369@usr02.primenet.com> References: <19971207153652.49391@mcs.net> <199712072148.OAA02369@usr02.primenet.com> X-Mailer: VM 6.29 under 19.15 XEmacs Lucid Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > Note that the use of Imake (the correct way to do cross-platform > configuration... ROTFL. You've *GOT* to be kidding, right? Imake is one of those 'evil daemon spawned utilties from the pit of hell that should be killed with a wooden stake through the heart'. I've seen many a good engineer who was given that line reduced to a babbling idiot that ended up giving up software engineering and took up much safer sports like kick-boxing and arena fighting. :) It's *MUCH* easier to build your own distributed 'make' program that does this than to use Imake with anything *signficantly* large. Dinky X programs don't count, and since X doesn't compile on non-Unix platforms it doesn't count. Nate From owner-freebsd-current Sun Dec 7 23:04:49 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id XAA06949 for current-outgoing; Sun, 7 Dec 1997 23:04:49 -0800 (PST) (envelope-from owner-freebsd-current) Received: from ns.mt.sri.com (sri-gw.MT.net [206.127.105.141]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id XAA06933 for ; Sun, 7 Dec 1997 23:04:44 -0800 (PST) (envelope-from nate@mt.sri.com) Received: from mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by ns.mt.sri.com (8.8.8/8.8.8) with SMTP id XAA18776; Sun, 7 Dec 1997 23:52:22 -0700 (MST) (envelope-from nate@rocky.mt.sri.com) Received: by mt.sri.com (SMI-8.6/SMI-SVR4) id XAA10325; Sun, 7 Dec 1997 23:52:20 -0700 Date: Sun, 7 Dec 1997 23:52:20 -0700 Message-Id: <199712080652.XAA10325@mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Greg Hormann Cc: current@FreeBSD.ORG Subject: Re: ld.so AND emacs In-Reply-To: References: X-Mailer: VM 6.29 under 19.15 XEmacs Lucid Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > Was there ever a workaround found for the emacs/ld.so problem? I searched > the archives to no avail. Yes, it's fixed in -current now. Nate From owner-freebsd-current Sun Dec 7 23:04:53 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id XAA06974 for current-outgoing; Sun, 7 Dec 1997 23:04:53 -0800 (PST) (envelope-from owner-freebsd-current) Received: from ns.mt.sri.com (sri-gw.MT.net [206.127.105.141]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id XAA06936 for ; Sun, 7 Dec 1997 23:04:45 -0800 (PST) (envelope-from nate@mt.sri.com) Received: from mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by ns.mt.sri.com (8.8.8/8.8.8) with SMTP id XAA18757; Sun, 7 Dec 1997 23:51:57 -0700 (MST) (envelope-from nate@rocky.mt.sri.com) Received: by mt.sri.com (SMI-8.6/SMI-SVR4) id XAA10317; Sun, 7 Dec 1997 23:51:55 -0700 Date: Sun, 7 Dec 1997 23:51:55 -0700 Message-Id: <199712080651.XAA10317@mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Joao Carlos Mendes Luis Cc: freebsd-current@FreeBSD.ORG Subject: Re: wd0 interrupt timeout In-Reply-To: <199712071828.QAA18606@gaia.coppe.ufrj.br> References: <19971206114018.41854@deepo.prosa.dk> <199712071828.QAA18606@gaia.coppe.ufrj.br> X-Mailer: VM 6.29 under 19.15 XEmacs Lucid Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Joao Carlos Mendes Luis writes: > #define quoting(Philippe Regnauld) > // > For the past several days (the first time being on Dec 2 as shown) I've been > // > seeing the following messages popping up: > // > // [...] > // > // > The system will completely hang for several seconds - no process > // > activity, no disk activity, nothing - then the drive in question makes > // > the "powering up" sound it does when I first power up the machine, the > // > error appears on the console and activity resumes. > // > // You have auto-spindown / APM enable in the BIOS, and your > // disk spins down when it's been idle for some time (definable). > > What if I have this on a machine without APM support (a very old 486) ? > > I've never had a fatal error, but always have these warnings. Then your disk is probably going bad, like mine did recently. :( Nate From owner-freebsd-current Sun Dec 7 23:11:36 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id XAA07575 for current-outgoing; Sun, 7 Dec 1997 23:11:36 -0800 (PST) (envelope-from owner-freebsd-current) Received: from word.smith.net.au (vh1.gsoft.com.au [203.38.152.122]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id XAA07561; Sun, 7 Dec 1997 23:11:25 -0800 (PST) (envelope-from mike@word.smith.net.au) Received: from word (localhost [127.0.0.1]) by word.smith.net.au (8.8.7/8.8.5) with ESMTP id RAA00375; Mon, 8 Dec 1997 17:36:10 +1030 (CST) Message-Id: <199712080706.RAA00375@word.smith.net.au> X-Mailer: exmh version 2.0zeta 7/24/97 To: Eivind Eklund cc: dyson@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: VM system info In-reply-to: Your message of "08 Dec 1997 01:43:59 BST." <867m9gpsts.fsf@bitbox.follo.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 08 Dec 1997 17:36:08 +1030 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > I want this info in the kernel. At the very least, I want > documentation as a part of the SYSCTL_*() macro parameters, unused but > available as a (mandatory) part of the source - better would be as a > part of the kernel that can be compiled away by setting a kernel > option (e.g. NO_SYSCTL_DOCS). Would you buy it in /usr/share/misc/sysctl_nodes? I was thinking about that when I saved John's message... mike From owner-freebsd-current Sun Dec 7 23:21:53 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id XAA08374 for current-outgoing; Sun, 7 Dec 1997 23:21:53 -0800 (PST) (envelope-from owner-freebsd-current) Received: from kn6-045.ktvlpr.inet.fi (ari@kn6-045.ktvlpr.inet.fi [194.197.169.45]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id XAA08364 for ; Sun, 7 Dec 1997 23:21:45 -0800 (PST) (envelope-from ari@kn6-045.ktvlpr.inet.fi) Received: from localhost (ari@localhost) by kn6-045.ktvlpr.inet.fi (8.8.5/8.8.5) with SMTP id JAA00366 for ; Mon, 8 Dec 1997 09:21:41 +0200 (EET) Date: Mon, 8 Dec 1997 09:21:41 +0200 (EET) From: Ari Suutari To: current@freebsd.org Subject: Re: 3.0 -release ? In-Reply-To: <199712061435.OAA27381@awfulhak.demon.co.uk> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Sat, 6 Dec 1997, Brian Somers wrote: > > For the time being, I've put back the htons() :-/ As you say, this > code ain't portable. Our original number goes from a,b,c,d to > b,a,0,0 and then gets coerced into a u_short.... two wrongs make a > right :-O > I have made the corrections to natd 1.11 and placed it to ftp://ftp.suutari.iki.fi/pub/natd. I hope Brian will put them into -current ? Ari Lappeenranta, Finland From owner-freebsd-current Mon Dec 8 00:38:03 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id AAA17500 for current-outgoing; Mon, 8 Dec 1997 00:38:03 -0800 (PST) (envelope-from owner-freebsd-current) Received: from ns1.yes.no (ns1.yes.no [195.119.24.10]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id AAA17490; Mon, 8 Dec 1997 00:37:53 -0800 (PST) (envelope-from eivind@bitbox.follo.net) Received: from bitbox.follo.net (bitbox.follo.net [194.198.43.36]) by ns1.yes.no (8.8.7/8.8.7) with ESMTP id IAA11964; Mon, 8 Dec 1997 08:37:50 GMT Received: (from eivind@localhost) by bitbox.follo.net (8.8.6/8.8.6) id JAA11375; Mon, 8 Dec 1997 09:37:19 +0100 (MET) Message-ID: <19971208093719.50393@follo.net> Date: Mon, 8 Dec 1997 09:37:19 +0100 From: Eivind Eklund To: Mike Smith Cc: Eivind Eklund , dyson@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: VM system info References: <867m9gpsts.fsf@bitbox.follo.net> <199712080706.RAA00375@word.smith.net.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.88e In-Reply-To: <199712080706.RAA00375@word.smith.net.au>; from Mike Smith on Mon, Dec 08, 1997 at 05:36:08PM +1030 Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Mon, Dec 08, 1997 at 05:36:08PM +1030, Mike Smith wrote: > > I want this info in the kernel. At the very least, I want > > documentation as a part of the SYSCTL_*() macro parameters, unused but > > available as a (mandatory) part of the source - better would be as a > > part of the kernel that can be compiled away by setting a kernel > > option (e.g. NO_SYSCTL_DOCS). > > Would you buy it in /usr/share/misc/sysctl_nodes? I was thinking about > that when I saved John's message... If extracted from the kernel source, I'd say it was OK. However, if this is a file that developers are supposed to to keep up to date manually, I'm much more sceptical. Keeping documentation outside the source up to date has a tendency to be forgotten/ignored. Eivind. From owner-freebsd-current Mon Dec 8 01:11:33 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id BAA20191 for current-outgoing; Mon, 8 Dec 1997 01:11:33 -0800 (PST) (envelope-from owner-freebsd-current) Received: from eh.est.is (root@eh.est.is [194.144.208.34]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id BAA20166 for ; Mon, 8 Dec 1997 01:11:22 -0800 (PST) (envelope-from totii@est.is) Received: from est.is (ppp-22.est.is [194.144.208.122]) by eh.est.is (8.8.5/8.8.7) with ESMTP id JAA15616; Mon, 8 Dec 1997 09:10:32 GMT (envelope-from totii@est.is) Message-ID: <348BB98B.2A995AE3@est.is> Date: Mon, 08 Dec 1997 09:10:35 +0000 From: "Þorður Ivarsson" X-Mailer: Mozilla 4.04 [en] (X11; I; FreeBSD 2.2.5-RELEASE i386) MIME-Version: 1.0 To: "Jamil J. Weatherbee" CC: Joao Carlos Mendes Luis , freebsd-current@FreeBSD.ORG Subject: Re: wd0: Can someone explain the following errors, i.e. is this a bad ide, disk that needs to be replaced? References: Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Jamil J. Weatherbee wrote: > > In trying to track reproduce some hard drive errors that caused my machine > to hang while doing a build world I performed a: > > dd if=/dev/wd0 bs=1024k | dd if=/dev/wd0 bs=1024k > > wd0: 2014MB (4124736 sectors), 4092 cyls, 16 heads, 63 S/T, 512 B/S > ... > wd0: hard error reading fsbn 3688647 of 3688644-3688647 (wd0 bn 3688647; cn 3659 tn 5 sn 60)wd0: status 59 error 80 > wd0: hard error reading fsbn 3688647 of 3688644-3688647 (wd0 bn 3688647; cn 3659 tn 5 sn 60)wd0: status 59 error 80 > wd0: hard error reading fsbn 3688648 of 3688648-3688651 (wd0 bn 3688648; cn 3659 tn 5 sn 61)wd0: status 49 error 4 > > after that the dd stopped with an Input/Output Error > > Do I need to replace this drive? This drive is, I think, dying, it happened to my 1G drive few days ago and every time I marked badblock to the drive, new errors did show up, I moved the drive to windoze computer and it shows somtimes erratic behavior. ( Mine was Seagate ). The badblock mapping table might be full or disable. -- Þórður Ívarsson Thordur Ivarsson Ísland Iceland --------------------------------------------- FreeBSD has good features, Some others are full of unwanted features! --------------------------------------------- From owner-freebsd-current Mon Dec 8 03:25:01 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id DAA29063 for current-outgoing; Mon, 8 Dec 1997 03:25:01 -0800 (PST) (envelope-from owner-freebsd-current) Received: from mail.cs.tu-berlin.de (root@mail.cs.tu-berlin.de [130.149.17.13]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id DAA29033; Mon, 8 Dec 1997 03:24:52 -0800 (PST) (envelope-from wosch@cs.tu-berlin.de) Received: from panke.panke.de (anonymous215.ppp.cs.tu-berlin.de [130.149.17.215]) by mail.cs.tu-berlin.de (8.8.6/8.8.8) with ESMTP id MAA01315; Mon, 8 Dec 1997 12:09:01 +0100 (MET) Received: (from wosch@localhost) by panke.panke.de (8.8.5/8.6.12) id CAA07015; Mon, 8 Dec 1997 02:37:29 +0100 (MET) To: dyson@freebsd.org Cc: jonny@coppe.ufrj.br (Joao Carlos Mendes Luis), current@freebsd.org Subject: Re: VM system info References: <199712071829.NAA03407@dyson.iquest.net> From: Wolfram Schneider Date: 08 Dec 1997 02:37:27 +0100 In-Reply-To: "John S. Dyson"'s message of Sun, 7 Dec 1997 13:29:42 -0500 (EST) Message-ID: Lines: 14 Sender: owner-freebsd-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk "John S. Dyson" writes: > > // I have recently added some interesting VM tunables. Since it would > > // be nice if people other than me (or those who requested them) could > > // use the features, I thought it would be nice to pass this info on: > > Is there any place or URL where we can get this information always > > updated ? It's a pretty good form of documentation I've always > > wanted to know. > Nope. Unfortunately, the source code is the only place for it (by > inference.) The VFS sysctls also deserve some documentation. sysctl(3) is the right place for sysctl documentation. -- Wolfram Schneider http://www.apfel.de/~wosch/ From owner-freebsd-current Mon Dec 8 05:11:23 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id FAA04764 for current-outgoing; Mon, 8 Dec 1997 05:11:23 -0800 (PST) (envelope-from owner-freebsd-current) Received: from whqvax.picker.com (whqvax.picker.com [144.54.1.1]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id FAA04750 for ; Mon, 8 Dec 1997 05:11:16 -0800 (PST) (envelope-from rhh@ct.picker.com) Received: from ct.picker.com by whqvax.picker.com with SMTP; Mon, 8 Dec 1997 8:10:13 -0500 (EST) Received: from elmer.ct.picker.com by ct.picker.com (4.1/SMI-4.1) id AA02214; Mon, 8 Dec 97 08:10:11 EST Received: by elmer.ct.picker.com (SMI-8.6/SMI-SVR4) id IAA02147; Mon, 8 Dec 1997 08:10:08 -0500 Message-Id: <19971208081007.30060@ct.picker.com> Date: Mon, 8 Dec 1997 08:10:07 -0500 From: Randall Hopper To: Kenneth Merry Cc: current@FreeBSD.ORG Subject: Re: Oddity with netscape and current References: <19971207210544.52901@ct.picker.com> <199712080443.VAA21558@panzer.plutotech.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.81 In-Reply-To: <199712080443.VAA21558@panzer.plutotech.com>; from Kenneth Merry on Sun, Dec 07, 1997 at 09:43:14PM -0700 Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Kenneth Merry: |Randall Hopper wrote... |> So, while we're on the subject, could you all try a 4.04 test?: |> |> 1) In 4.04, turn ON Java and Javascript & turn OFF auto-loading of |> images. Then exit 4.04. |> |> 2) Finally, invoke: |> |> \ |> 'http://necxdirect.necx.com:8002/cgi-bin/auth/docroot/index.html?nonce=guest' |> |> If you don't get a lock-up, I'd sure like to see your wrapper script and |> preferences.js! This is just one of many pages on which 4.04 here freezes |> and takes any remaining CPU with it. | | My solution has just been to disable Java when going to their web |page. It's a rogue java applet that causes the problem, so turning off |Java does the trick. That's been my work-around as well. I notice this doesn't happen with 3.01 or 3.02. But it does with Solaris 4.04 as well though. I wonder if this is a bug in the Java implementation or a flaw in the applet. I forwarded the info onto necx for them to look into. Randall From owner-freebsd-current Mon Dec 8 05:29:09 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id FAA05783 for current-outgoing; Mon, 8 Dec 1997 05:29:09 -0800 (PST) (envelope-from owner-freebsd-current) Received: from www.nw.nl ([193.172.11.36]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id FAA05778 for ; Mon, 8 Dec 1997 05:29:03 -0800 (PST) (envelope-from webmaster@heaven.nl) Received: from klaas ([194.229.212.53]) by www.nw.nl (Netscape Mail Server v2.0) with SMTP id AAA135 for ; Mon, 8 Dec 1997 14:34:56 +0100 Message-ID: <348BF68E.6EB0@heaven.nl> Date: Mon, 08 Dec 1997 14:30:54 +0100 From: webmaster@heaven.nl (Supervisor) X-Mailer: Mozilla 3.0 (WinNT; I) MIME-Version: 1.0 To: current@freebsd.org Subject: subscribe Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk subscribe From owner-freebsd-current Mon Dec 8 06:35:08 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id GAA10203 for current-outgoing; Mon, 8 Dec 1997 06:35:08 -0800 (PST) (envelope-from owner-freebsd-current) Received: from hermes (hermes.uninet.net.mx [200.33.146.193]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id GAA10177 for ; Mon, 8 Dec 1997 06:34:58 -0800 (PST) (envelope-from eculp@ver1.telmex.net.mx) Received: from sunix by hermes (SMI-8.6/SMI-SVR4) id IAA22882; Mon, 8 Dec 1997 08:37:28 -0600 Message-ID: <348C06D7.15DFA166@ver1.telmex.net.mx> Date: Mon, 08 Dec 1997 08:40:23 -0600 From: Edwin Culp Organization: Mexico Communicates, S.C. X-Mailer: Mozilla 3.01Gold (X11; I; Linux 2.0.14 i586) MIME-Version: 1.0 To: freebsd-current@FreeBSD.Org Subject: Undefined symbol _procfs_exit during make release. Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.Org X-Loop: FreeBSD.org Precedence: bulk Yesterday I made my first attempt to do a make release and after about 600 Mega and 12 hours I got this Undefined symbol message. Does anyone know why? Do I have to go through the whole 12 hour process to rebuild the release? Thank you and please forgive my ignorance, this may have been discused but I have not had access to mail for about three weeks. Today is my first day back. TIA ed cc -c -O -Wreturn-type -Wcomment -Wredundant-decls -Wimplicit -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wuninitialized -nostdinc -I- -I. -I../.. -I../../../include -DMFS_ROOT=1440 -DNFS_NOSERVER -DFAILSAFE -DCOMPAT_43 -DMSDOSFS -DNFS -DFFS -DINET -DKERNEL -include opt_global.h swapkernel.c sh ../../conf/newvers.sh BOOTMFS -DMFS_ROOT=1440 -DNFS_NOSERVER -DFAILSAFE -DCOMPAT_43 -DMSDOSFS -DNFS -DFFS -DINET cc -O -Wreturn-type -Wcomment -Wredundant-decls -Wimplicit -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wuninitialized -nostdinc -I- -I. -I../.. -I../../../include -DMFS_ROOT=1440 -DNFS_NOSERVER -DFAILSAFE -DCOMPAT_43 -DMSDOSFS -DNFS -DFFS -DINET -DKERNEL -include opt_global.h -c vers.c loading kernel kern_exit.o: Undefined symbol `_procfs_exit' referenced from text segment *** Error code 1 Stop. From owner-freebsd-current Mon Dec 8 10:34:16 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id KAA27513 for current-outgoing; Mon, 8 Dec 1997 10:34:16 -0800 (PST) (envelope-from owner-freebsd-current) Received: from watermarkgroup.com (lor.watermarkgroup.com [207.202.73.33]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id KAA27497 for ; Mon, 8 Dec 1997 10:34:11 -0800 (PST) (envelope-from luoqi@watermarkgroup.com) Received: by watermarkgroup.com (4.1/SMI-4.1) id AA11655; Mon, 8 Dec 97 13:32:47 EST Date: Mon, 8 Dec 97 13:32:47 EST From: luoqi@watermarkgroup.com (Luoqi Chen) Message-Id: <9712081832.AA11655@watermarkgroup.com> To: ache@nagual.pp.ru, luigi@labinfo.iet.unipi.it Subject: Re: SB AWE64 support Cc: current@FreeBSD.ORG, dstenn@fanfic.org Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > BTW, playmidi sounds on AWE32 is really strange comparing to Win95 case... > It seems that all notes are right, but really weird... Is AWE32 require > some patch loading? I think it was able to play using default bank... > Try the AWE32 driver from http://bahamut.mm.t.u-tokyo.ac.jp/~iwai/awedrv/, it supports AWE wavetable synth. Driver in -current only supports FM synth which sounds really pathetic. Maybe we should commit this new driver, I have been running it with -stable for month without any problem. -lq > -- > Andrey A. Chernov > > http://www.nagual.pp.ru/~ache/ > > From owner-freebsd-current Mon Dec 8 11:17:41 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id LAA01083 for current-outgoing; Mon, 8 Dec 1997 11:17:41 -0800 (PST) (envelope-from owner-freebsd-current) Received: from smtp.algonet.se (tomei.algonet.se [194.213.74.114]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id LAA01068 for ; Mon, 8 Dec 1997 11:17:30 -0800 (PST) (envelope-from johang@mail.algonet.se) Message-Id: <199712081917.LAA01068@hub.freebsd.org> Received: (qmail 18231 invoked from network); 8 Dec 1997 20:16:56 +0100 Received: from du28-250.ppp.algonet.se (HELO pegasys) (195.100.250.28) by tomei.algonet.se with SMTP; 8 Dec 1997 20:16:56 +0100 Comments: Authenticated sender is From: "Johan Granlund" To: Eivind Eklund Date: Mon, 8 Dec 1997 20:06:05 +0100 MIME-Version: 1.0 Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Subject: Re: VM system info CC: current@FreeBSD.ORG Priority: normal In-reply-to: <19971208093719.50393@follo.net> References: <199712080706.RAA00375@word.smith.net.au>; from Mike Smith on Mon, Dec 08, 1997 at 05:36:08PM +1030 X-mailer: Pegasus Mail for Win32 (v2.54) Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > On Mon, Dec 08, 1997 at 05:36:08PM +1030, Mike Smith wrote: > > > I want this info in the kernel. At the very least, I want > > > documentation as a part of the SYSCTL_*() macro parameters, unused but > > > available as a (mandatory) part of the source - better would be as a > > > part of the kernel that can be compiled away by setting a kernel > > > option (e.g. NO_SYSCTL_DOCS). > > > > Would you buy it in /usr/share/misc/sysctl_nodes? I was thinking about > > that when I saved John's message... > > If extracted from the kernel source, I'd say it was OK. However, if I saw a lot of years ago a package that extracted formatted dokumentation from the sources. I dont remember the name but it should have been on a DECUS tape. > this is a file that developers are supposed to to keep up to date > manually, I'm much more sceptical. Keeping documentation outside the > source up to date has a tendency to be forgotten/ignored. More like newer work. > > Eivind. > /Johan ___________________________________________________________ Internet: Johan@elpost.com I don't even speak for myself From owner-freebsd-current Mon Dec 8 11:25:37 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id LAA01923 for current-outgoing; Mon, 8 Dec 1997 11:25:37 -0800 (PST) (envelope-from owner-freebsd-current) Received: from watermarkgroup.com (lor.watermarkgroup.com [207.202.73.33]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id LAA01894 for ; Mon, 8 Dec 1997 11:25:27 -0800 (PST) (envelope-from luoqi@watermarkgroup.com) Received: by watermarkgroup.com (4.1/SMI-4.1) id AA12202; Mon, 8 Dec 97 14:24:56 EST Date: Mon, 8 Dec 97 14:24:56 EST From: luoqi@watermarkgroup.com (Luoqi Chen) Message-Id: <9712081924.AA12202@watermarkgroup.com> To: jfieber@indiana.edu Subject: Re: Oddity with netscape and current Cc: current@freebsd.org Sender: owner-freebsd-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > For the record, the problem which this solves/works-around exists > in FreeBSD-2.2.5/XFree86-3.3.1 as well as (I gather) current (and > what version of X?). I'm using a 16 bit display and have not > tried it on 8 or 24. The reports on what works with what > combinations of FreeBSD, Netscape, and X11 have been rather > inconsistent--some curious methods of suppressing the symptoms > have been discovered but does anyone have a clue about the > problem? This has something to do with floating point exceptions. Netscape uses the fbsd default exception mask (precision/underflow/denomrmals), and *ignores* SIGFPE signal, which means when an unmasked exception arises, the FPU register stack will be completely messed up, and sometime this results in an infinite loop. To fix this problem, Netscape should either: 1. trap SIGFPE signals and handle the exceptions correctly, or 2. ignore SIGFPE, but use fpsetmask to mask ALL fp exceptions. Before Netscape fixes this problem, all we can do is to try to keep these unwanted exceptions from happening. Apparently, Netscape goes into an infinite loop when it does some CMS color lookup during startup. That's why I proposed to disable CMS by setting CMSDB to null. -lq > > -john > > From owner-freebsd-current Mon Dec 8 11:46:40 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id LAA03893 for current-outgoing; Mon, 8 Dec 1997 11:46:40 -0800 (PST) (envelope-from owner-freebsd-current) Received: from picnic.mat.net (picnic.mat.net [206.246.122.117]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id LAA03871 for ; Mon, 8 Dec 1997 11:46:30 -0800 (PST) (envelope-from chuckr@glue.umd.edu) Received: from localhost (chuckr@localhost) by picnic.mat.net (8.8.8/8.8.5) with SMTP id OAA04378 for ; Mon, 8 Dec 1997 14:46:13 -0500 (EST) X-Authentication-Warning: picnic.mat.net: chuckr owned process doing -bs Date: Mon, 8 Dec 1997 14:46:12 -0500 (EST) From: Chuck Robey X-Sender: chuckr@picnic.mat.net To: FreeBSD-current@FreeBSD.org Subject: printing Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk I know changes have recently gone into the lpd, and I haven't the time to find out why my printer has begun kicking out a blank page on the start of every print. The 'fo' property is not in any of my printcap entries (which come from apsfilter) and the default value for 'fo' (according to the printcap man page, this is the property controlling whether a formfeed is sent on the beginning of each new print job) is false. If no one looks at this until my semester gets over, I'll fix at it myself then. ----------------------------+----------------------------------------------- Chuck Robey | Interests include any kind of voice or data chuckr@glue.umd.edu | communications topic, C programming, and Unix. 213 Lakeside Drive Apt T-1 | Greenbelt, MD 20770 | I run Journey2 and picnic, both FreeBSD (301) 220-2114 | version 3.0 current -- and great FUN! ----------------------------+----------------------------------------------- From owner-freebsd-current Mon Dec 8 12:48:53 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id MAA09609 for current-outgoing; Mon, 8 Dec 1997 12:48:53 -0800 (PST) (envelope-from owner-freebsd-current) Received: from smtp01.primenet.com (smtp01.primenet.com [206.165.6.131]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id MAA09593 for ; Mon, 8 Dec 1997 12:48:43 -0800 (PST) (envelope-from tlambert@usr08.primenet.com) Received: (from daemon@localhost) by smtp01.primenet.com (8.8.8/8.8.8) id HAA21881; Mon, 8 Dec 1997 07:21:22 -0700 (MST) Received: from usr08.primenet.com(206.165.6.208) via SMTP by smtp01.primenet.com, id smtpd021777; Mon Dec 8 07:21:13 1997 Received: (from tlambert@localhost) by usr08.primenet.com (8.8.5/8.8.5) id NAA14881; Mon, 8 Dec 1997 13:47:37 -0700 (MST) From: Terry Lambert Message-Id: <199712082047.NAA14881@usr08.primenet.com> Subject: Re: Diffs to support RAIDframe on FreeBSD To: nate@mt.sri.com (Nate Williams) Date: Mon, 8 Dec 1997 20:47:37 +0000 (GMT) Cc: tlambert@primenet.com, karl@mcs.net, current@FreeBSD.ORG, Jim.Zelenka@cs.cmu.edu In-Reply-To: <199712080701.AAA10388@mt.sri.com> from "Nate Williams" at Dec 8, 97 00:01:57 am X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > Note that the use of Imake (the correct way to do cross-platform > > configuration... > > ROTFL. You've *GOT* to be kidding, right? > > Imake is one of those 'evil daemon spawned utilties from the pit of hell > that should be killed with a wooden stake through the heart'. I've seen > many a good engineer who was given that line reduced to a babbling > idiot that ended up giving up software engineering and took up much > safer sports like kick-boxing and arena fighting. :) And "configure" is another. Only Imake doesn't depend on anything but Imake, so at least you can generate VMS and DOS build files with it without having to turn your DOS or VMS system into GNU. Novell used Imake for cross-platform (AIX/UnixWare/Solaris/SunOS/Ultrix) builds for the NetWare for UNIX product, with great success. It just takes sitting down and understanding it, and writing a template file for your own project. The Imake X11 dependency in RAIDframe is an artifact of the way it's used, not of Imake itself. Imake is crap, but it's the best crap out there so far. It has a much better grasp of metasyntax than GNU configure pretends to... > It's *MUCH* easier to build your own distributed 'make' program that > does this than to use Imake with anything *signficantly* large. Dinky X > programs don't count, and since X doesn't compile on non-Unix platforms > it doesn't count. X *does* compile on non-UNIX platforms; it's XFree86 which does not. As far as "rolling your own", yes, you can, at the expense of having to "roll your own" each and every time. Anyway, it was just an editorial comment; I noted that a "port" might want to prebuild the Makefiles so it wasn't an issue (I'd like to see you get any utility out of RAIDframe for a DOS or VMS system anyway, since neither really has a cache). Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-current Mon Dec 8 14:19:36 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id OAA19996 for current-outgoing; Mon, 8 Dec 1997 14:19:36 -0800 (PST) (envelope-from owner-freebsd-current) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id OAA19975 for ; Mon, 8 Dec 1997 14:19:24 -0800 (PST) (envelope-from j@uriah.heep.sax.de) Received: (from uucp@localhost) by sax.sax.de (8.8.8/8.8.8) with UUCP id XAA16156 for freebsd-current@freebsd.org; Mon, 8 Dec 1997 23:19:14 +0100 (CET) (envelope-from j@uriah.heep.sax.de) Received: (from j@localhost) by uriah.heep.sax.de (8.8.8/8.8.5) id XAA29514; Mon, 8 Dec 1997 23:15:12 +0100 (MET) Date: Mon, 8 Dec 1997 23:15:12 +0100 (MET) Message-Id: <199712082215.XAA29514@uriah.heep.sax.de> X-Newsreader: knews 0.9.6 Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) Organization: Private BSD site, Dresden X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E References: <01bd01aa$f4f35de0$09d181c2@user2.shellnet.co.uk> <199712052035.OAA00812@unix.tfs.net> <19971205163751.03734@hydrogen.nike.efn.org> From: j@uriah.heep.sax.de (J Wunsch) Subject: Re: Telnet Root access X-Original-Newsgroups: poster In-Reply-To: To: freebsd-current@freebsd.org Sender: owner-freebsd-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Jacques Vidrine wrote: > > Like it is illeagal to export ssh from the US? > > It hasn't been tested. As far as I know, it was written outside of the > US, but that doesn't mean that you can't re-export it. Of course, it does. US, the crypto-motel: you can always check in, but never check out. It doesn't count whether some crypto thing has been invented outside of the US or not, you are not allowed exporting it from there. The entire world already has this technology, but they keep on insisting it being `ammunition'. Politics are braindead? They are too braindead to understand that they are. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-current Mon Dec 8 14:22:27 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id OAA20566 for current-outgoing; Mon, 8 Dec 1997 14:22:27 -0800 (PST) (envelope-from owner-freebsd-current) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id OAA20498; Mon, 8 Dec 1997 14:22:09 -0800 (PST) (envelope-from andrew@ZETA.ORG.AU) Received: from gurney.reilly.home (d66.syd2.zeta.org.au [203.26.11.66]) by godzilla.zeta.org.au (8.8.7/8.6.9) with ESMTP id JAA03730; Tue, 9 Dec 1997 09:10:28 +1100 Received: (from andrew@localhost) by gurney.reilly.home (8.8.7/8.8.5) id IAA10768; Tue, 9 Dec 1997 08:28:15 +1100 (EST) From: Andrew Reilly Message-Id: <199712082128.IAA10768@gurney.reilly.home> Date: Tue, 9 Dec 1997 08:28:15 +1100 (EST) Subject: Re: VM system info To: toor@dyson.iquest.net cc: perhaps@yes.no, dyson@FreeBSD.ORG, current@FreeBSD.ORG In-Reply-To: <199712080151.UAA00245@dyson.iquest.net> MIME-Version: 1.0 Content-Type: TEXT/plain; CHARSET=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On 7 Dec, John S. Dyson wrote: > Eivind Eklund said: >> >> I want this info in the kernel. At the very least, I want >> documentation as a part of the SYSCTL_*() macro parameters, unused but >> available as a (mandatory) part of the source - better would be as a >> part of the kernel that can be compiled away by setting a kernel >> option (e.g. NO_SYSCTL_DOCS). >> > The biggest problem with that is the size of the "documentation." I > agree that it would be a good idea to document everything. Internally > would be nice (I guess), because it would tend to stay better in sync. > Some kind of literate programming scheme would be interesting also. I've been thinking about this for a while, but haven't arrived at the "perfect" solution yet. Literate programming is definitely good: possibly the only solution to this sort of problem. The devil is in the details, of course. How about a kern-doc compiler that filters through the kernel source as part of the build process, and compiles all of the sysctl doco into an HTML tree, with the appropriate links to man pages. This could just be put somewhere in the file system, or, for extra points, compiled into the kernel itself as an MFS image that could be accessed with the appropriate tweaks to mount_mfs. (Or something much simpler, since you only read read-only, world-access semantics.) -- Andrew "The steady state of disks is full." -- Ken Thompson From owner-freebsd-current Mon Dec 8 14:25:19 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id OAA21095 for current-outgoing; Mon, 8 Dec 1997 14:25:19 -0800 (PST) (envelope-from owner-freebsd-current) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id OAA21056 for ; Mon, 8 Dec 1997 14:25:04 -0800 (PST) (envelope-from j@uriah.heep.sax.de) Received: (from uucp@localhost) by sax.sax.de (8.8.8/8.8.8) with UUCP id XAA16275 for freebsd-current@freebsd.org; Mon, 8 Dec 1997 23:25:02 +0100 (CET) (envelope-from j@uriah.heep.sax.de) Received: (from j@localhost) by uriah.heep.sax.de (8.8.8/8.8.5) id XAA29484; Mon, 8 Dec 1997 23:09:35 +0100 (MET) Date: Mon, 8 Dec 1997 23:09:35 +0100 (MET) Message-Id: <199712082209.XAA29484@uriah.heep.sax.de> X-Newsreader: knews 0.9.6 Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) Organization: Private BSD site, Dresden X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E References: <01bd01aa$f4f35de0$09d181c2@user2.shellnet.co.uk> <199712051941.NAA18863@home.dragondata.com> <199712052104.PAA00924@unix.tfs.net> From: j@uriah.heep.sax.de (J Wunsch) Subject: Re: Telnet Root access X-Original-Newsgroups: poster In-Reply-To: <199712052104.PAA00924@unix.tfs.net> To: freebsd-current@freebsd.org Sender: owner-freebsd-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Jim Bryant wrote: > is ssh/sshd a package yet? last time i made it, i had to build it > myself... You gotta shoot your government first, i'm afraid. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-current Mon Dec 8 14:25:24 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id OAA21112 for current-outgoing; Mon, 8 Dec 1997 14:25:24 -0800 (PST) (envelope-from owner-freebsd-current) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id OAA21075 for ; Mon, 8 Dec 1997 14:25:12 -0800 (PST) (envelope-from j@uriah.heep.sax.de) Received: (from uucp@localhost) by sax.sax.de (8.8.8/8.8.8) with UUCP id XAA16277 for freebsd-current@freebsd.org; Mon, 8 Dec 1997 23:25:07 +0100 (CET) (envelope-from j@uriah.heep.sax.de) Received: (from j@localhost) by uriah.heep.sax.de (8.8.8/8.8.5) id XAA29498; Mon, 8 Dec 1997 23:11:03 +0100 (MET) Date: Mon, 8 Dec 1997 23:11:03 +0100 (MET) Message-Id: <199712082211.XAA29498@uriah.heep.sax.de> X-Newsreader: knews 0.9.6 Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) Organization: Private BSD site, Dresden X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E References: <01bd01aa$f4f35de0$09d181c2@user2.shellnet.co.uk> <199712052035.OAA00812@unix.tfs.net> From: j@uriah.heep.sax.de (J Wunsch) Subject: Re: Telnet Root access X-Original-Newsgroups: poster In-Reply-To: To: freebsd-current@freebsd.org Sender: owner-freebsd-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Brian Mitchell wrote: > > man su > > This is pretty dumb, as the password is _still_ passing over an insecure > network in plaintext form. You've always got the option to use S/Key. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-current Mon Dec 8 14:54:35 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id OAA23899 for current-outgoing; Mon, 8 Dec 1997 14:54:35 -0800 (PST) (envelope-from owner-freebsd-current) Received: from sci.brooklyn.cuny.edu (dayton@louis.sci.brooklyn.cuny.edu [146.245.1.7]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id OAA23877 for ; Mon, 8 Dec 1997 14:54:23 -0800 (PST) (envelope-from dayton@sci.brooklyn.cuny.edu) Received: (from dayton@localhost) by sci.brooklyn.cuny.edu (8.8.7/8.8.4) id RAA26506; Mon, 8 Dec 1997 17:53:14 -0500 (EST) Date: Mon, 8 Dec 1997 17:53:14 -0500 (EST) Message-Id: <199712082253.RAA26506@sci.brooklyn.cuny.edu> From: Dayton Clark To: current@freebsd.org Subject: -current, goliath, smp -- problems Sender: owner-freebsd-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Folks, I tired of people saying how good stable -current is ;-). I've had a system w/4 PPro 200 on a goliath motherboard for about a year now. It's had some hardware problems, but I believe those are fixed now. It runs multiprocessor Solaris and NT without a hitch but what I really want to run is FreeBSD SMP (this message is appropriate for current also). Alas, the fates are against me. Lack of time on my part is the main reason I haven't made more progress, but I've had enough time recently to get *some* evidence about what's going wrong. I will pick away at the problem, as time permits, and I hope you all have some insights on how I might proceed, or (hope, hope) perhaps someone knows just what the problem is. The system: Motherboard AMI Goliath EISA & PCI busses Chipset 450GX Processor 4X PPRO 200 Cache 256K Memory 64M Disk Adaptec 2940w 4G, 8x cdrom Video ATI Mach 32 OS FreeBSD-current SNAP-971203 (also some Sept snap). The problems: There are three problems I'm having the first two are sporadic and typcially disappear on when repeated. They also occur only with the SMP kernel (the generic smp kernel except NCPU=4), I believe. I suspect that the first two are related. o Commands (e.g., ls, mv) die with error code = 0. A message is printed on stderr, perhaps by the shell, stating that the process died with error code 0. Repeat it and it usually works. o When I try a large make (make world or making emacs) programs will disappear, i.e. make all of a sudden can't find cc or rm (after many successful uses of the command). Repeat the make and it will continue. o Emacs doesn't work at all and I can't do much without emacs 8-). The emacs from the packages distribution hangs. I brought over emacs 20.2 it dereferences a null pointer in malloc_internal(). I compiled 19.34 in /usr/ports and it gets a segment violation in malloc_internal() but at a different location. This happens with both the UP and SMP kernels. Any help would be appreciated. thanks dayton Dayton Clark CIS Department dayton@brooklyn.cuny.edu Brooklyn College/CUNY 1-718-951-4811 Brooklyn, New York 11210 1-718-951-4842 (fax) From owner-freebsd-current Mon Dec 8 15:33:45 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id PAA28668 for current-outgoing; Mon, 8 Dec 1997 15:33:45 -0800 (PST) (envelope-from owner-freebsd-current) Received: from send1a.yahoomail.com (send1a.yahoomail.com [205.180.60.22]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id PAA28651 for ; Mon, 8 Dec 1997 15:33:19 -0800 (PST) (envelope-from osiris2002@yahoo.com) Message-ID: <19971208233300.15803.rocketmail@send1a.yahoomail.com> Received: from [194.79.98.83] by send1a; Mon, 08 Dec 1997 15:33:00 PST Date: Mon, 8 Dec 1997 15:33:00 -0800 (PST) From: Charlie Roots Subject: subscribe To: current@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk subscribe _________________________________________________________ DO YOU YAHOO!? Get your free @yahoo.com address at http://mail.yahoo.com From owner-freebsd-current Mon Dec 8 15:46:44 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id PAA00312 for current-outgoing; Mon, 8 Dec 1997 15:46:44 -0800 (PST) (envelope-from owner-freebsd-current) Received: from Ilsa.StevesCafe.com (Ilsa.StevesCafe.com [205.168.119.129]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id PAA00300 for ; Mon, 8 Dec 1997 15:46:33 -0800 (PST) (envelope-from fbsd@Ilsa.StevesCafe.com) Received: from Ilsa.StevesCafe.com (localhost [127.0.0.1]) by Ilsa.StevesCafe.com (8.8.7/8.8.5) with ESMTP id QAA13842; Mon, 8 Dec 1997 16:46:26 -0700 (MST) Message-Id: <199712082346.QAA13842@Ilsa.StevesCafe.com> X-Mailer: exmh version 2.0gamma 1/27/96 From: Steve Passe To: Dayton Clark cc: current@freebsd.org Subject: Re: -current, goliath, smp -- problems In-reply-to: Your message of "Mon, 08 Dec 1997 17:53:14 EST." <199712082253.RAA26506@sci.brooklyn.cuny.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 08 Dec 1997 16:46:26 -0700 Sender: owner-freebsd-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi, > o Emacs doesn't work at all and I can't do much without emacs 8-). > The emacs from the packages distribution hangs. I brought over > emacs 20.2 it dereferences a null pointer in malloc_internal(). I > compiled 19.34 in /usr/ports and it gets a segment violation in > malloc_internal() but at a different location. This happens with > both the UP and SMP kernels. rtld was broken on december 3rd, causing emacs to die. OI think it was fixed by the 5th or 6th. I'm at a loss about the other 2 problems. They may be related to 4 CPUs, but I have been TOTALLY unsuccessful in getting access to a 4 CPU machine for testing. Show of hands, anyone successfully running SMP on 4 or more CPUs? -- Steve Passe | powered by smp@csn.net | Symmetric MultiProcessor FreeBSD From owner-freebsd-current Mon Dec 8 15:49:55 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id PAA00603 for current-outgoing; Mon, 8 Dec 1997 15:49:55 -0800 (PST) (envelope-from owner-freebsd-current) Received: from send1a.yahoomail.com (send1a.yahoomail.com [205.180.60.22]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id PAA00592 for ; Mon, 8 Dec 1997 15:49:48 -0800 (PST) (envelope-from osiris2002@yahoo.com) Message-ID: <19971208234930.22903.rocketmail@send1a.yahoomail.com> Received: from [194.79.98.83] by send1a; Mon, 08 Dec 1997 15:49:30 PST Date: Mon, 8 Dec 1997 15:49:30 -0800 (PST) From: Charlie Roots Subject: subscribe freebsd-current To: current@FreeBSD.Org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-current@FreeBSD.Org X-Loop: FreeBSD.org Precedence: bulk subscribe freebsd-current _________________________________________________________ DO YOU YAHOO!? Get your free @yahoo.com address at http://mail.yahoo.com From owner-freebsd-current Mon Dec 8 16:10:46 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id QAA02136 for current-outgoing; Mon, 8 Dec 1997 16:10:46 -0800 (PST) (envelope-from owner-freebsd-current) Received: from word.smith.net.au (ppp4.portal.net.au [202.12.71.104]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id QAA02063; Mon, 8 Dec 1997 16:09:52 -0800 (PST) (envelope-from mike@word.smith.net.au) Received: from word (localhost [127.0.0.1]) by word.smith.net.au (8.8.7/8.8.5) with ESMTP id KAA02916; Tue, 9 Dec 1997 10:34:29 +1030 (CST) Message-Id: <199712090004.KAA02916@word.smith.net.au> X-Mailer: exmh version 2.0zeta 7/24/97 To: Eivind Eklund cc: Mike Smith , Eivind Eklund , dyson@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: VM system info In-reply-to: Your message of "Mon, 08 Dec 1997 09:37:19 BST." <19971208093719.50393@follo.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 09 Dec 1997 10:34:26 +1030 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > On Mon, Dec 08, 1997 at 05:36:08PM +1030, Mike Smith wrote: > > > I want this info in the kernel. At the very least, I want > > > documentation as a part of the SYSCTL_*() macro parameters, unused but > > > available as a (mandatory) part of the source - better would be as a > > > part of the kernel that can be compiled away by setting a kernel > > > option (e.g. NO_SYSCTL_DOCS). > > > > Would you buy it in /usr/share/misc/sysctl_nodes? I was thinking about > > that when I saved John's message... > > If extracted from the kernel source, I'd say it was OK. Extracting from kernel source (at build time) is quite obviously pointless. It's also not useful for parts of the tree that are dynamically generated (although sysctl isn't actually too good at walking those parts of the tree anyway). > However, if > this is a file that developers are supposed to to keep up to date > manually, I'm much more sceptical. Keeping documentation outside the > source up to date has a tendency to be forgotten/ignored. This is the only way to do it; maintaining a document which describes a superset of nodes. Even if it's incomplete (like scsi_modes) it would be Better than Nothing. mike From owner-freebsd-current Mon Dec 8 16:40:44 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id QAA04962 for current-outgoing; Mon, 8 Dec 1997 16:40:44 -0800 (PST) (envelope-from owner-freebsd-current) Received: from ns1.yes.no (ns1.yes.no [195.119.24.10]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id QAA04919; Mon, 8 Dec 1997 16:40:20 -0800 (PST) (envelope-from eivind@bitbox.follo.net) Received: from bitbox.follo.net (bitbox.follo.net [194.198.43.36]) by ns1.yes.no (8.8.7/8.8.7) with ESMTP id AAA23174; Tue, 9 Dec 1997 00:40:16 GMT Received: (from eivind@localhost) by bitbox.follo.net (8.8.6/8.8.6) id BAA16299; Tue, 9 Dec 1997 01:39:41 +0100 (MET) Message-ID: <19971209013941.17444@follo.net> Date: Tue, 9 Dec 1997 01:39:41 +0100 From: Eivind Eklund To: Mike Smith Cc: dyson@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: VM system info References: <19971208093719.50393@follo.net> <199712090004.KAA02916@word.smith.net.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.88e In-Reply-To: <199712090004.KAA02916@word.smith.net.au>; from Mike Smith on Tue, Dec 09, 1997 at 10:34:26AM +1030 Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk [Mike Smith] > [Eivind Eklund] >> [Mike Smith] >>> Would you buy it in /usr/share/misc/sysctl_nodes? I was thinking >>> about that when I saved John's message... >> >> If extracted from the kernel source, I'd say it was OK. > > Extracting from kernel source (at build time) is quite obviously > pointless. ? I'd say this give you a fairly recent snapshot of the available IOCTLs; I certainly update my kernel more often that my manpages (and much more often that /usr/share). I'd opt for it to be compiled as part of 'make world' instead, but there are certainly some good points to doing it at the kernel build tilme. > It's also not useful for parts of the tree that are dynamically > generated (although sysctl isn't actually too good at walking those > parts of the tree anyway). Ehm - what tree? The sysctl tree in the kernel? I'd guess we'd be able to find some way to document that in the source too, if we really wanted to. A single SYSCTL_DOC() macro could do it. >> However, if this is a file that developers are supposed to to keep >> up to date manually, I'm much more sceptical. Keeping >> documentation outside the source up to date has a tendency to be >> forgotten/ignored. > > This is the only way to do it; maintaining a document which describes a > superset of nodes. Even if it's incomplete (like scsi_modes) it would > be Better than Nothing. It might be better than nothing, but it is almost certainly going to wander far from the ultimate. Any form of documentation that is in-line in the code is much more likely to be kept up-to-date, and it _is_ fairly cheap. Any attempt at making things easier for the newcomers at a slight, indirect expense to the people 'in the know' seems to be shouted down immedately. Leanness of the kernel and the source tree seems to have a small but vocal minority that shout down any documentation that might actually be kept up to date. (Ref my attempt at finding some tolerable way to provide inline documentation for kernel file use last easter). Eivind. From owner-freebsd-current Mon Dec 8 17:04:24 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id RAA07219 for current-outgoing; Mon, 8 Dec 1997 17:04:24 -0800 (PST) (envelope-from owner-freebsd-current) Received: from word.smith.net.au (vh1.gsoft.com.au [203.38.152.122]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id RAA07179; Mon, 8 Dec 1997 17:04:01 -0800 (PST) (envelope-from mike@word.smith.net.au) Received: from word (localhost [127.0.0.1]) by word.smith.net.au (8.8.7/8.8.5) with ESMTP id LAA06720; Tue, 9 Dec 1997 11:28:53 +1030 (CST) Message-Id: <199712090058.LAA06720@word.smith.net.au> X-Mailer: exmh version 2.0zeta 7/24/97 To: Eivind Eklund cc: Mike Smith , dyson@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: VM system info In-reply-to: Your message of "Tue, 09 Dec 1997 01:39:41 BST." <19971209013941.17444@follo.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 09 Dec 1997 11:28:50 +1030 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > [Mike Smith] > > [Eivind Eklund] > >> [Mike Smith] > >>> Would you buy it in /usr/share/misc/sysctl_nodes? I was thinking > >>> about that when I saved John's message... > >> > >> If extracted from the kernel source, I'd say it was OK. > > > > Extracting from kernel source (at build time) is quite obviously > > pointless. > > ? > > I'd say this give you a fairly recent snapshot of the available > IOCTLs; I certainly update my kernel more often that my manpages (and > much more often that /usr/share). Exactly. Now assume I go build a kernel for someone else. Or build a 2.2 release on a 3.x machine. The kernel build doesn't affect anything outside the build arena; changing this would be a fatal mistake. > I'd opt for it to be compiled as part of 'make world' instead, but > there are certainly some good points to doing it at the kernel build > tilme. If it was possible to automatically generate a supserset listing at 'world' time, that would be good. > > Any attempt at making things easier for the newcomers at a slight, > indirect expense to the people 'in the know' seems to be shouted down > immedately. Leanness of the kernel and the source tree seems to have > a small but vocal minority that shout down any documentation that > might actually be kept up to date. (Ref my attempt at finding some > tolerable way to provide inline documentation for kernel file use last > easter). > I'm glad you made this a "general" rant; I'd have been *extremely* offended if you put me in that category. If I thought that there was an easy way to arrange pageable kernel data, I would be leaping and screaming about putting the above data in the kernel RBN. As it is, any alternative scheme that will serve as a stopgap for now and actually achieve the desired goal without requiring massive trampling of the kernel and major changes to the interface appeals. Hacking some gratuitous macro changes in as a quickie-fix just doesn't cut it. mike From owner-freebsd-current Mon Dec 8 17:40:34 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id RAA10147 for current-outgoing; Mon, 8 Dec 1997 17:40:34 -0800 (PST) (envelope-from owner-freebsd-current) Received: from onyx.atipa.com (user4169@ns.atipa.com [208.128.22.10]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id RAA10110 for ; Mon, 8 Dec 1997 17:40:26 -0800 (PST) (envelope-from freebsd@atipa.com) Received: (qmail-queue invoked by uid 1018); 9 Dec 1997 01:46:12 -0000 Date: Mon, 8 Dec 1997 18:46:11 -0700 (MST) From: Atipa X-Sender: freebsd@dot.ishiboo.com To: Chuck Robey cc: FreeBSD-current@FreeBSD.org Subject: Re: printing In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk Try "sh" for supress header. Kevin On Mon, 8 Dec 1997, Chuck Robey wrote: > I know changes have recently gone into the lpd, and I haven't the time to > find out why my printer has begun kicking out a blank page on the start of > every print. The 'fo' property is not in any of my printcap entries > (which come from apsfilter) and the default value for 'fo' (according to > the printcap man page, this is the property controlling whether a > formfeed is sent on the beginning of each new print job) is false. > > If no one looks at this until my semester gets over, I'll fix at it > myself then. > > ----------------------------+----------------------------------------------- > Chuck Robey | Interests include any kind of voice or data > chuckr@glue.umd.edu | communications topic, C programming, and Unix. > 213 Lakeside Drive Apt T-1 | > Greenbelt, MD 20770 | I run Journey2 and picnic, both FreeBSD > (301) 220-2114 | version 3.0 current -- and great FUN! > ----------------------------+----------------------------------------------- > > > > > From owner-freebsd-current Mon Dec 8 18:00:48 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id SAA13155 for current-outgoing; Mon, 8 Dec 1997 18:00:48 -0800 (PST) (envelope-from owner-freebsd-current) Received: from picnic.mat.net (picnic.mat.net [206.246.122.117]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id SAA13135 for ; Mon, 8 Dec 1997 18:00:41 -0800 (PST) (envelope-from chuckr@glue.umd.edu) Received: from localhost (chuckr@localhost) by picnic.mat.net (8.8.8/8.8.5) with SMTP id VAA05185; Mon, 8 Dec 1997 21:00:15 -0500 (EST) X-Authentication-Warning: picnic.mat.net: chuckr owned process doing -bs Date: Mon, 8 Dec 1997 21:00:14 -0500 (EST) From: Chuck Robey X-Sender: chuckr@picnic.mat.net To: Atipa cc: FreeBSD-current@FreeBSD.org Subject: Re: printing In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk On Mon, 8 Dec 1997, Atipa wrote: > > Try "sh" for supress header. Nope, that's a standard feature of apsfilter (it was already in there). Understand, this has been working for months fine; there's something odd about the recent changes to lpd, because expressly setting fo to false is being ignored also. It's not a problem with my printcap (unless the basic printcap format rules have changed in some major regard). > > Kevin > > On Mon, 8 Dec 1997, Chuck Robey wrote: > > > I know changes have recently gone into the lpd, and I haven't the time to > > find out why my printer has begun kicking out a blank page on the start of > > every print. The 'fo' property is not in any of my printcap entries > > (which come from apsfilter) and the default value for 'fo' (according to > > the printcap man page, this is the property controlling whether a > > formfeed is sent on the beginning of each new print job) is false. > > > > If no one looks at this until my semester gets over, I'll fix at it > > myself then. > > > > ----------------------------+----------------------------------------------- > > Chuck Robey | Interests include any kind of voice or data > > chuckr@glue.umd.edu | communications topic, C programming, and Unix. > > 213 Lakeside Drive Apt T-1 | > > Greenbelt, MD 20770 | I run Journey2 and picnic, both FreeBSD > > (301) 220-2114 | version 3.0 current -- and great FUN! > > ----------------------------+----------------------------------------------- > > > > > > > > > > > > ----------------------------+----------------------------------------------- Chuck Robey | Interests include any kind of voice or data chuckr@glue.umd.edu | communications topic, C programming, and Unix. 213 Lakeside Drive Apt T-1 | Greenbelt, MD 20770 | I run Journey2 and picnic, both FreeBSD (301) 220-2114 | version 3.0 current -- and great FUN! ----------------------------+----------------------------------------------- From owner-freebsd-current Mon Dec 8 18:04:53 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id SAA13591 for current-outgoing; Mon, 8 Dec 1997 18:04:53 -0800 (PST) (envelope-from owner-freebsd-current) Received: from smtp03.primenet.com (smtp03.primenet.com [206.165.6.133]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id SAA13568; Mon, 8 Dec 1997 18:04:37 -0800 (PST) (envelope-from tlambert@usr05.primenet.com) Received: (from daemon@localhost) by smtp03.primenet.com (8.8.8/8.8.8) id TAA22319; Mon, 8 Dec 1997 19:18:09 -0700 (MST) Received: from usr05.primenet.com(206.165.6.205) via SMTP by smtp03.primenet.com, id smtpd022304; Mon Dec 8 19:18:07 1997 Received: (from tlambert@localhost) by usr05.primenet.com (8.8.5/8.8.5) id TAA02842; Mon, 8 Dec 1997 19:03:41 -0700 (MST) From: Terry Lambert Message-Id: <199712090203.TAA02842@usr05.primenet.com> Subject: Re: VM system info To: perhaps@yes.no (Eivind Eklund) Date: Tue, 9 Dec 1997 02:03:41 +0000 (GMT) Cc: mike@smith.net.au, dyson@freebsd.org, current@freebsd.org In-Reply-To: <19971209013941.17444@follo.net> from "Eivind Eklund" at Dec 9, 97 01:39:41 am X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-freebsd-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > wander far from the ultimate. Any form of documentation that is > in-line in the code is much more likely to be kept up-to-date, and it > _is_ fairly cheap. > > > Any attempt at making things easier for the newcomers at a slight, > indirect expense to the people 'in the know' seems to be shouted down > immedately. Leanness of the kernel and the source tree seems to have > a small but vocal minority that shout down any documentation that > might actually be kept up to date. (Ref my attempt at finding some > tolerable way to provide inline documentation for kernel file use last > easter). > I'm firmly in the "if you commit it, document it" camp. HOWEVER... Inline documentation is just as bad, or worse, than non-inline documentation. I disagree with the premise that it "is much more likely to be kept up-to-date". Further, such documentation tends to obfuscate otherwise readable code with all sorts of non-code pieces, making it less likely the code will be maintained, either. I've worked places where inline documentation was supposed to have been maintained "to the benefit of all", and have seen only grief from it. In FreeBSD, where the effort is all volunteer, you can't even threaten to fire someone for not playing by the rules in order to get them to (grudgingly, at the end of the project) document the code that should have been documented and the documentation up-to-date since day one of the project. Certainly, there's room for improvement in code commenting, and there is definitely room for architectural "white papers" describing what the code is intended to implement, but writing whitepapers (or man pages) in block comments preceeding functions, etc., is just not the place for whitepapers or man pages. Inlining documentation is evil. Non-documenting is evil. And two wrongs don't make a right. IMO, of course... Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-current Mon Dec 8 19:28:16 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id TAA20347 for current-outgoing; Mon, 8 Dec 1997 19:28:16 -0800 (PST) (envelope-from owner-freebsd-current) Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id TAA20337 for ; Mon, 8 Dec 1997 19:28:11 -0800 (PST) (envelope-from jkh@time.cdrom.com) Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.7/8.6.9) with ESMTP id TAA12962; Mon, 8 Dec 1997 19:18:05 -0800 (PST) To: luoqi@watermarkgroup.com (Luoqi Chen) cc: ache@nagual.pp.ru, luigi@labinfo.iet.unipi.it, current@FreeBSD.ORG, dstenn@fanfic.org Subject: Re: SB AWE64 support In-reply-to: Your message of "Mon, 08 Dec 1997 13:32:47 EST." <9712081832.AA11655@watermarkgroup.com> Date: Mon, 08 Dec 1997 19:18:05 -0800 Message-ID: <12959.881637485@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > Try the AWE32 driver from http://bahamut.mm.t.u-tokyo.ac.jp/~iwai/awedrv/, > it supports AWE wavetable synth. Driver in -current only supports FM synth > which sounds really pathetic. Maybe we should commit this new driver, I have > been running it with -stable for month without any problem. Sounds good to me. I assume that Amancio and Luigi are still the "point men" on the sound driver these days? Jordan From owner-freebsd-current Mon Dec 8 20:15:24 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id UAA24389 for current-outgoing; Mon, 8 Dec 1997 20:15:24 -0800 (PST) (envelope-from owner-freebsd-current) Received: from pluto.plutotech.com (mail.plutotech.com [206.168.67.137]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id UAA24340; Mon, 8 Dec 1997 20:15:10 -0800 (PST) (envelope-from gibbs@plutotech.com) Received: from narnia.plutotech.com (narnia.plutotech.com [206.168.67.130]) by pluto.plutotech.com (8.8.7/8.8.5) with ESMTP id VAA29018; Mon, 8 Dec 1997 21:15:09 -0700 (MST) Message-Id: <199712090415.VAA29018@pluto.plutotech.com> Date: Mon, 08 Dec 1997 21:13:29 -0700 From: "Justin T. Gibbs" Subject: 971208 CAM Snapshot Available Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk To: undisclosed-recipients:; ------- Blind-Carbon-Copy Subject: 971208 CAM Snapshot Available Date: Mon, 08 Dec 1997 21:13:29 -0700 From: "Justin T. Gibbs" Bcc: Blind Distribution List: ; Common Access Method SCSI layer Patches Available You've all seen messages talking about a new SCSI layer for FreeBSD, and I'm pleased to announce yet another snapshot of that work. I plan to release snapshots on a regular basis as new features and hardware support are added. To see what is currently supported, skip down to the supported hardware section. "What is CAM? and why would I want it?" CAM is an ANSI ratified spec that defines a software interface for talking to SCSI and ATAPI devices. This new SCSI layer for FreeBSD is not strictly CAM compliant, but follows many of the precepts of CAM. More importantly, this work addresses many of the short comings of the previous SCSI layer and should provide better performance, reliability, and ease the task of adding support for new controllers. I hope that many of you will try CAM. Although "work in progress", this code has been through over four months of testing here at Pluto and I feel pretty good about the stability of the code. If you do have the facilities to experiment (you must be running current), please do. I welcome your feedback especially about the performance of the new system. Features Since Last Snapshot: Preliminary tape support. This has only been tested on a DDS2 drive and the driver is fairly green. New device statistic code. A whole slew of information is now recorded on a per-device basis. The interface is generic and once we have iostat and systat converted to using this code, all other drivers using the old "dk" stat interface will be converted. A sample utility is included in this snapshot so you can read the statistics. Bus DMA based bounce buffer support. ISA AdvanSys support now works in all memory configurations. aic7xxx driver improvements. The aic7895 is now supported. The command queing algorithm is now more efficient. Bug fixes include some problems with error recovery and target initiated sync/wide negotiation. AdvanSys driver improvements. The driver has now been tested on almost every narrow SCSI card AdvanSys has produced. Many bugs in the device probe code have been fixed. Table driven error handling. This greatly simplifies the task of enhancing or modifying how errors are handled. Enhanced PCI conf support. Although this isn't really CAM related, you get it for free. Check out the pciconf utilty for details. Numerous other bug fixes I've forgotten about. Features: Round-robin, per priority level scheduling of devices and their resources. I/O Completion, error recovery, and processing queued I/O is performed in a separate software interrupt handler. The old system had the potential of blocking out hardware interrupts for lengthy periods as much of this processing occurred as the result of a call from the controller's interrupt handler. The generic SCSI layer now understands tagged I/O and exports this functionality to the peripheral drivers. This allows drivers like the "direct access" driver to perform ordered tagged transactions for meta-data writes. Async, ordered, meta-data writes are now enabled in vfs_bio.c The "direct access" driver prevents "tag starvation" from occurring by guaranteeing that at least one write in every 5 second period to a tagged queuing device has an ordered tag. This removes the need for individual controller drivers to worry about this problem. Complete and controller independent handling of the "QUEUE FULL" and "BUSY" status codes. The number of tags that are queued to a device are dynamically adjusted by the generic layer. Interrupt driven sub-device probing. At boot time, all buses are probed in parallel yielding a much faster boot. As probing occurs after all interrupt and timer services are available, no additional (and often error prone) "polling" code is needed in each controller driver. Better error recovery. When an error occurs, the queue of transactions to the erring device is "frozen", full status is reported back to the peripheral driver, and the peripheral driver can recover the device without perturbing queued up I/O. As all transactions have an associated priority and generation count, after recovery is complete, transactions that are retried are automatically re-queued in their original order. All error handling is performed based on a detected failure. The old code would often perform actions "just in case" before accessing a device as the error recovery mechanism was inadequate. Now, for example, if your disk spins down, the system will properly recover even if the device is already open. Support for "high power" commands. Peripheral drivers can mark actions that may tax a power supply as "high powered". Only a certain number (default of 4, but configurable with the CAM_MAX_HIGHPOWER kernel option) of these commands are allowed to be active at a time. This allows a user to, for example, disable spin-up on the drives in an enclosure and let the system spin them up in a controlled fashion. By default, all luns are scanned on devices during probe. In the old SCSI layer, this was often problematic as it performed a Test Unit Ready prior to performing an Identify. Many devices that properly handle the Identify will hang the bus if you attempt a different command to a high lun. Transfer negotiations only occurs to devices that actually support negotiations (based on their inquiry information). This is performed in a controller independent fashion. There is now a generic quirk mechanism that allows controllers, peripheral drivers, or the CAM transport layer to define their own quirks entries. Currently the CAM transport layer has quirk entries that allow for modulation of tags and disabling multi-lun probing. The AdvanSys driver uses quirk entries to control some of the "hardware bug fixes" in the driver that only apply to certain types of devices. Hard-wiring of devices to specific unit numbers is supported as it was in the old system. Userland "pass-through" commands are supported. The interface is different than from the old SCSI code, but sample code is provided (including patches to XMCD), and we do plan to provide a scsi.8 command in the future. SUPPORTED HARDWARE Aic7xxx driver (ahc): This driver supports all of the devices the original FreeBSD driver supports but with the following new features: Support for aic7895 based controllers. Autotermination support for aic7860 based cards. SCB paging that allows up to 255 SCBs to be active on aic7770, aic7850, and aic7860 cards. Bug fixes to the multi-lun support. The beginnings of a target mode implementation. AdvanSys Driver (adv): This driver supports the entire line of AdvanSys narrow channel devices. Tagged queuing is also supported. Supported peripherals: Direct Access driver (da): 512 byte sectored disk drivers. Support for other sector sizes is planned, but further investigation on the "right" approach for this is needed. It probably belongs in the disk-slice code. CDROM driver (cd): This driver should support everything the old driver did. Sequential Access driver (sa): This driver should support most "newer" tape drives. It does not have the ability to change either the density or compression settings yet. This is the "greenest" component in CAM currently, having only been tested on an Archive Python. Look for additional enhancements to this driver in the near term. Other peripheral drivers are in the works. HOW TO INSTALL IT BACKUP YOUR OLD SRC TREE AND KERNEL!!!! cp /kernel /kernel.works Get the code: ftp://ftp.FreeBSD.org/pub/FreeBSD/cam/cam-971208.diffs.gz ftp://ftp.FreeBSD.org/pub/FreeBSD/cam/cam-971208.samples.tar.gz or ftp://ftp.kdm.org/pub/FreeBSD/cam/cam-971208.diffs.gz ftp://ftp.kdm.org/pub/FreeBSD/cam/cam-971208.samples.tar.gz On a FreeBSD-current system from ~971208: cd /usr/src zcat cam-971208.diffs.gz | patch cd usr.sbin/config make clean all install cd sys/i386/conf vi MYKERNEL Comment out all unsupported SCSI devices, and substitute "da" for "sd" and "sa" for "st". Look in LINT or GENERIC for examples. config MYKERNEL cd ../../MYKERNEL make all make install If you want XMCD or the userland sample code, untar cam-971208.samples.tar.gz and read the enclosed README files. - -- Justin T. Gibbs gibbs@FreeBSD.org =========================================== FreeBSD - Turning PCs into workstations =========================================== ------- End of Blind-Carbon-Copy From owner-freebsd-current Mon Dec 8 20:20:45 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id UAA24821 for current-outgoing; Mon, 8 Dec 1997 20:20:45 -0800 (PST) (envelope-from owner-freebsd-current) Received: from rah.star-gate.com (rah.star-gate.com [204.188.121.18]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id UAA24805 for ; Mon, 8 Dec 1997 20:20:35 -0800 (PST) (envelope-from hasty@rah.star-gate.com) Received: from rah.star-gate.com (localhost.star-gate.com [127.0.0.1]) by rah.star-gate.com (8.8.8/8.8.8) with ESMTP id UAA09182; Mon, 8 Dec 1997 20:19:49 -0800 (PST) (envelope-from hasty@rah.star-gate.com) Message-Id: <199712090419.UAA09182@rah.star-gate.com> X-Mailer: exmh version 2.0gamma 1/27/96 To: "Jordan K. Hubbard" cc: luoqi@watermarkgroup.com (Luoqi Chen), ache@nagual.pp.ru, luigi@labinfo.iet.unipi.it, current@FreeBSD.ORG, dstenn@fanfic.org Subject: Re: SB AWE64 support In-reply-to: Your message of "Mon, 08 Dec 1997 19:18:05 PST." <12959.881637485@time.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 08 Dec 1997 20:19:48 -0800 From: Amancio Hasty Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Once again, questions related to multimedia stuff to multimedia@freebsd.org. If anyone wants to contribute a sound driver thats fantastic! So lets just pick this subject in the multimedia mailing list. Amancio From owner-freebsd-current Mon Dec 8 22:56:31 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id WAA06023 for current-outgoing; Mon, 8 Dec 1997 22:56:31 -0800 (PST) (envelope-from owner-freebsd-current) Received: from zippy.dyn.ml.org (lhasa-214.ppp.hooked.net [206.169.229.214]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id WAA06008 for ; Mon, 8 Dec 1997 22:56:26 -0800 (PST) (envelope-from garbanzo@hooked.net) Received: from localhost (garbanzo@localhost) by zippy.dyn.ml.org (8.8.8/8.8.7) with SMTP id WAA03135; Mon, 8 Dec 1997 22:57:21 -0800 (PST) X-Authentication-Warning: zippy.dyn.ml.org: garbanzo owned process doing -bs Date: Mon, 8 Dec 1997 22:57:19 -0800 (PST) From: Alex X-Sender: garbanzo@zippy.dyn.ml.org To: Steve Passe cc: current Subject: Re: -current, goliath, smp -- problems In-Reply-To: <199712082346.QAA13842@Ilsa.StevesCafe.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Mon, 8 Dec 1997, Steve Passe wrote: > rtld was broken on december 3rd, causing emacs to die. OI think it was > fixed by the 5th or 6th. > > I'm at a loss about the other 2 problems. They may be related to 4 CPUs, > but I have been TOTALLY unsuccessful in getting access to a 4 CPU > machine for testing. Show of hands, anyone successfully running SMP on 4 > or more CPUs? Speaking of more CPUs, did anyone catch the release of HP's newest SMP server? An 8 CPU (I'm assuming PPro) *drool*. I'm assuming it comes with gobs of ram and disk space, and it amusingly enough looked like an overgrown dot-matrix printer with no paper. I didn't realize there were production machines with more than 4 Intel CPUs *drool*. - alex From owner-freebsd-current Mon Dec 8 23:00:12 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id XAA06297 for current-outgoing; Mon, 8 Dec 1997 23:00:12 -0800 (PST) (envelope-from owner-freebsd-current) Received: from zippy.dyn.ml.org (lhasa-214.ppp.hooked.net [206.169.229.214]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id XAA06268 for ; Mon, 8 Dec 1997 23:00:03 -0800 (PST) (envelope-from garbanzo@hooked.net) Received: from localhost (garbanzo@localhost) by zippy.dyn.ml.org (8.8.8/8.8.7) with SMTP id XAA06174; Mon, 8 Dec 1997 23:00:52 -0800 (PST) X-Authentication-Warning: zippy.dyn.ml.org: garbanzo owned process doing -bs Date: Mon, 8 Dec 1997 23:00:51 -0800 (PST) From: Alex X-Sender: garbanzo@zippy.dyn.ml.org To: Edwin Culp cc: freebsd-current@freebsd.org Subject: Re: Undefined symbol _procfs_exit during make release. In-Reply-To: <348C06D7.15DFA166@ver1.telmex.net.mx> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Mon, 8 Dec 1997, Edwin Culp wrote: > Yesterday I made my first attempt to do a make release and after about > 600 Mega and 12 hours > I got this Undefined symbol message. > > Does anyone know why? > Do I have to go through the whole 12 hour process to rebuild the > release? This was actually fixed right before your message was sent. Easiest thing to do is run cvsup on your whole src tree which will update only the things that need to be changed. Then you can rebuild anything you really want to (like the kernel). - alex From owner-freebsd-current Mon Dec 8 23:01:55 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id XAA06506 for current-outgoing; Mon, 8 Dec 1997 23:01:55 -0800 (PST) (envelope-from owner-freebsd-current) Received: from zippy.dyn.ml.org (lhasa-214.ppp.hooked.net [206.169.229.214]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id XAA06495 for ; Mon, 8 Dec 1997 23:01:48 -0800 (PST) (envelope-from garbanzo@hooked.net) Received: from localhost (garbanzo@localhost) by zippy.dyn.ml.org (8.8.8/8.8.7) with SMTP id XAA06552; Mon, 8 Dec 1997 23:02:43 -0800 (PST) X-Authentication-Warning: zippy.dyn.ml.org: garbanzo owned process doing -bs Date: Mon, 8 Dec 1997 23:02:43 -0800 (PST) From: Alex X-Sender: garbanzo@zippy.dyn.ml.org To: Joerg Wunsch cc: freebsd-current@freebsd.org Subject: Re: Telnet Root access In-Reply-To: <199712082209.XAA29484@uriah.heep.sax.de> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Mon, 8 Dec 1997, J Wunsch wrote: > Jim Bryant wrote: > > > is ssh/sshd a package yet? last time i made it, i had to build it > > myself... > > You gotta shoot your government first, i'm afraid. Why doesn't someone outside of the US make a package of it? And whatever happened to the SF District Judge's rulings (which applied to Walnut Creek right?) on the whole encryption dealies? - alex From owner-freebsd-current Mon Dec 8 23:45:29 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id XAA09748 for current-outgoing; Mon, 8 Dec 1997 23:45:29 -0800 (PST) (envelope-from owner-freebsd-current) Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id XAA09740 for ; Mon, 8 Dec 1997 23:45:24 -0800 (PST) (envelope-from jkh@time.cdrom.com) Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.7/8.6.9) with ESMTP id XAA14260; Mon, 8 Dec 1997 23:38:50 -0800 (PST) To: "Justin T. Gibbs" Cc: current@freebsd.org Subject: Re: 971208 CAM Snapshot Available In-reply-to: Your message of "Mon, 08 Dec 1997 21:13:29 MST." <199712090415.VAA29018@pluto.plutotech.com> Date: Mon, 08 Dec 1997 23:38:50 -0800 Message-ID: <14255.881653130@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > On a FreeBSD-current system from ~971208: > > cd /usr/src > zcat cam-971208.diffs.gz | patch Actually, patch -p0 on my -current box here to get things to apply successfully. Also during this, I noticed an interesting anomaly with patch(1) here: c /a/perforce/src/lib/libcam/camlib.c |*** /usr/src/lib/libcam/camlib.c Wed Dec 31 17:00:00 1969 |--- /a/perforce/src/lib/libcam/camlib.c Thu Oct 30 20:38:49 1997 -------------------------- (Creating file /usr/src/lib/libcam/camlib.c...) usage: mkdir [-p] [-m mode] directory ... Patching file /usr/src/lib/libcam/camlib.c using Plan A... Hunk #1 succeeded at 1. See the diagnostic from mkdir? Strangely enough, the new /usr/src/lib/libcap directory is made anyway so it doesn't result in any actual patch malfunction, but it sure looks suspiciously like something is broken somewhere. Finally, your patch blew up in application here: (Creating file /usr/src/sys/compile/DM/.depend...) Patching file /usr/src/sys/compile/DM/.depend using Plan A... patch: **** malformed patch at line 17430: p.c ../../netinet/ip_input.c ../../netinet/ip_mroute.c ../../netinet/ip_output.c ../../netinet/raw_ip.c ../../netinet/tcp_input.c ../../netinet/tcp_output.c ../../netinet/tcp_subr.c ../../netinet/t Jordan From owner-freebsd-current Tue Dec 9 03:13:01 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id DAA23815 for current-outgoing; Tue, 9 Dec 1997 03:13:01 -0800 (PST) (envelope-from owner-freebsd-current) Received: from wakko.visint.co.uk (wakko.visint.co.uk [194.207.134.12]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id DAA23810 for ; Tue, 9 Dec 1997 03:12:56 -0800 (PST) (envelope-from steve@visint.co.uk) Received: from dylan.visint.co.uk (dylan.visint.co.uk [194.207.134.180]) by wakko.visint.co.uk (8.8.5/8.7.3) with SMTP id KAA22882; Tue, 9 Dec 1997 10:12:50 GMT Date: Tue, 9 Dec 1997 10:13:34 +0000 (GMT) From: Stephen Roome To: Randall Hopper cc: current@FreeBSD.ORG Subject: Re: Oddity with netscape and current In-Reply-To: <19971207210544.52901@ct.picker.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Sun, 7 Dec 1997, Randall Hopper wrote: > So, while we're on the subject, could you all try a 4.04 test?: > > 1) In 4.04, turn ON Java and Javascript & turn OFF auto-loading of > images. Then exit 4.04. What! I can't find the option to turn off auto-loading of images, they've hidden it well since 3.x versions. Besides, the evil configuration screens are so slow ! >2) Finally, invoke: > > \ I don't have one. > 'http://necxdirect.necx.com:8002/cgi-bin/auth/docroot/index.html?nonce=guest' This page worked for some time, and then locked up, I didn't have to turn off auto-loading of images though. > If you don't get a lock-up, I'd sure like to see your wrapper script and > preferences.js! This is just one of many pages on which 4.04 here freezes > and takes any remaining CPU with it. This is the first time netscape has locked up on me since the first 4.x beta that was FreeBSD native. This is current from 2 Dec, and I installed netscape by downloading it and running the ns.install script as I didn't get hold of the ports collection. Has anyone actually been keeping netscape informed of these problems ? [I guess so, but thought I'd ask.] Steve -- Steve Roome - Vision Interactive Ltd. Tel:+44(0)117 9730597 Home:+44(0)976 241342 WWW: http://dylan.visint.co.uk/ From owner-freebsd-current Tue Dec 9 04:37:26 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id EAA28418 for current-outgoing; Tue, 9 Dec 1997 04:37:26 -0800 (PST) (envelope-from owner-freebsd-current) Received: from whqvax.picker.com (whqvax.picker.com [144.54.1.1]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id EAA28409 for ; Tue, 9 Dec 1997 04:37:19 -0800 (PST) (envelope-from rhh@ct.picker.com) Received: from ct.picker.com by whqvax.picker.com with SMTP; Tue, 9 Dec 1997 7:36:02 -0500 (EST) Received: from elmer.ct.picker.com by ct.picker.com (4.1/SMI-4.1) id AA20020; Tue, 9 Dec 97 07:36:00 EST Received: by elmer.ct.picker.com (SMI-8.6/SMI-SVR4) id HAA22115; Tue, 9 Dec 1997 07:35:51 -0500 Message-Id: <19971209073551.43175@ct.picker.com> Date: Tue, 9 Dec 1997 07:35:51 -0500 From: Randall Hopper To: Stephen Roome Cc: current@FreeBSD.ORG Subject: Re: Oddity with netscape and current References: <19971207210544.52901@ct.picker.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.81 In-Reply-To: ; from Stephen Roome on Tue, Dec 09, 1997 at 10:13:34AM +0000 Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Stephen Roome: |On Sun, 7 Dec 1997, Randall Hopper wrote: |> So, while we're on the subject, could you all try a 4.04 test?: |> |> 1) In 4.04, turn ON Java and Javascript & turn OFF auto-loading of |> images. Then exit 4.04. | |What! I can't find the option to turn off auto-loading of images, they've |hidden it well since 3.x versions. Besides, the evil configuration screens |are so slow ! They buried it in menus: Edit->Preferences->Advanced->Automatically load images... Maybe pressure from advertisers -- who knows. Over a dial-up link, images off by-default is the only way to go. |This page worked for some time, and then locked up, I didn't have to turn |off auto-loading of images though. Interesting. Randall From owner-freebsd-current Tue Dec 9 05:36:58 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id FAA01645 for current-outgoing; Tue, 9 Dec 1997 05:36:58 -0800 (PST) (envelope-from owner-freebsd-current) Received: from Kitten.mcs.com (Kitten.mcs.com [192.160.127.90]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id FAA01640 for ; Tue, 9 Dec 1997 05:36:54 -0800 (PST) (envelope-from karl@Mars.mcs.net) Received: from Mars.mcs.net (karl@Mars.mcs.net [192.160.127.85]) by Kitten.mcs.com (8.8.7/8.8.2) with ESMTP id HAA22281; Tue, 9 Dec 1997 07:36:49 -0600 (CST) Received: (from karl@localhost) by Mars.mcs.net (8.8.7/8.8.2) id HAA23069; Tue, 9 Dec 1997 07:36:49 -0600 (CST) Message-ID: <19971209073649.52545@mcs.net> Date: Tue, 9 Dec 1997 07:36:49 -0600 From: Karl Denninger To: Mike Fisher Cc: abuse@mcs.net, noc@harborcom.net, current@freebsd.org Subject: Re: Your message has been BOUNCED by Spamblock(tm) (fwd) References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.84 In-Reply-To: ; from Mike Fisher on Tue, Dec 09, 1997 at 07:20:25AM -0500 Sender: owner-freebsd-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk FreeBSD - Note that Harborcom doesn't like us bitching about spam they relay to us. Awww, poor babies! Harborcom: See below. In a word: No. The message you cite below IS abusive, and IS spam. If you'd like, I can block all traffic from your network. That will prevent you from being "bothered". I will not prevent our system from bitching about spam to the people who send it to us. Sorry. CC: current@freebsd.org -- -- Karl Denninger (karl@MCS.Net)| MCSNet - Serving Chicagoland and Wisconsin http://www.mcs.net/ | T1's from $600 monthly to FULL DS-3 Service | NEW! K56Flex support on ALL modems Voice: [+1 312 803-MCS1 x219]| EXCLUSIVE NEW FEATURE ON ALL PERSONAL ACCOUNTS Fax: [+1 312 803-4929] | *SPAMBLOCK* Technology now included at no cost On Tue, Dec 09, 1997 at 07:20:25AM -0500, Mike Fisher wrote: > Please stop sending us these for posts that eminate from FreeBSD.org. We > have allowed them to relay through us, otherwise our hosts only allow the > mail relaying for our customers. > > Begin bounced message: > > >From owner-freebsd-ports@freebsd.org Tue Dec 9 03:30:23 1997 > Received: from ns3.harborcom.net (root@ns3.harborcom.net [206.158.4.7]) by > Mail$ > Received: from hub.freebsd.org [204.216.27.18] > > This message is from FreeBSD; they are starting (slowly) to implement > better restrictions for posting to their mailing lists. > > Thank you. > > Michael A. Fisher > Harbor Communications > > > ---------- Forwarded message ---------- > Date: Tue, 9 Dec 1997 04:45:00 -0500 > From: Spamblocker@mcs.net > To: The Abuse Coordinator and Postmaster > Subject: Your message has been BOUNCED by Spamblock(tm) > > ************************************************************************** > Your message has been refused by MCSNet's SPAMBLOCK technology, and the > customer you directed the email to requested that we return the mail > to you. > > You are the relay site from which this mail was sent to us. Due to the fact > that the overwhelming majority of Spam messages contain forged headers, we > have not attempted to deliver this bounce to the claimed "sender". > > If your site was abused by a spammer to send this mail to us, we strongly > suggest that you implement the "antispam" rulesets for Sendmail or other > mail transport agents, and consider both civil and criminal prosecution > of the originator of the message for abusing your service. > > http://www.sendmail.org has information on this technology for sendmail > users. > > If this message was inadvertently caught by our Spamblock system, it really > did come from a user of your network, and it is not Spam, please advise them > of the failure to deliver the mail and ask them to resolve the issue > through other media with their intended recipient. > > If you *ARE* a Spammer, or a Spam-friendly provider of Internet services, > you are hereby notified that this material is unwanted and will not be > accepted or tolerated by our network. You are wasting your time and money > in attempting to spam our customers, as we have detected and filtered your > transmission by customer request. > > You will receive ONE (1) of these messages for each item which meets > the follow criteria: > > 1) It is trapped by MCSNet's SPAMBLOCK system. > AND > 2) The customer has requested that the blocked messages be bounced. > > The user who you sent email to in the below included message is not > reachable via MCSNet from your host. > > ------------------------------------------------------------------------ > Begin bounced message: > > >From owner-freebsd-ports@freebsd.org Tue Dec 9 03:30:23 1997 > Received: from ns3.harborcom.net (root@ns3.harborcom.net [206.158.4.7]) by Mailbox.mcs.net (8.8.7/8.8.2) with SMTP id DAA06962; Tue, 9 Dec 1997 03:30:22 -0600 (CST) > Received: from hub.freebsd.org [204.216.27.18] > by ns3.harborcom.net with esmtp (Exim 1.73 #1) > id 0xfLvb-0004gi-00; Tue, 9 Dec 1997 04:26:07 -0500 > Received: from localhost (daemon@localhost) > by hub.freebsd.org (8.8.7/8.8.7) with SMTP id AAA13271; > Tue, 9 Dec 1997 00:31:53 -0800 (PST) > (envelope-from owner-freebsd-ports) > Received: (from root@localhost) > by hub.freebsd.org (8.8.7/8.8.7) id AAA13253 > for ports-outgoing; Tue, 9 Dec 1997 00:31:46 -0800 (PST) > (envelope-from owner-freebsd-ports) > Received: from gbms01.uwgb.edu (gbms01.uwgb.edu [143.200.128.3]) > by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id AAA13243; > Tue, 9 Dec 1997 00:31:40 -0800 (PST) > (envelope-from replyz_bulk@juno.com) > Received: from vucqpqlj (sfdn6-198.sf.compuserve.com) > by gbms01.uwgb.edu (PMDF V5.1-10 #25737) > with SMTP id <01IQYAKEZRQS0001OX@gbms01.uwgb.edu>; Tue, 9 Dec 1997 01:29:20 CST > Date: Mon, 08 Dec 1997 23:16:03 -0800 (PST) > From: Bulk Email > Subject: Affordable Bulk Email > Message-id: <01IQYAKFMGBA0001OX@gbms01.uwgb.edu> > Sender: owner-freebsd-ports@freebsd.org > X-Loop: FreeBSD.org > Precedence: bulk > > Get Immediate Results With Our Affordable Bulk Email Services! > ////////////////////////////////////////////////////////////////// > > Love it or hate it..Bulk Email gets RESULTS! How else can you > > reach thousands of potential customers without spending a fortune? > > **Do you have a Business Opportunity to offer? > > **Are you involved with MLM? > > **Do you have a product you are trying to sell? > > **Do you have a website and would you like more traffic? > > If you answered "yes" to any one of the above questions, Bulk Email > > could very well help you get the results you're looking for. > > Not all Bulk Email services are the same, we have the LOWEST PRICES > > along with the BEST SERVICE. We offer Full Service Bulk Email where > > we will help you write your ad and will mail it out for you saving > > you the hassle of having to purchase expensive Bulk Email software. > > If you would like to do the mailing yourself, we also provide the > > best and most current email lists at very low prices, in fact, we > > will beat ANY price! > > ***OUR CURRENT SPECIAL*** > > We'll email your full length ad to 5,000 WWW users > for only $15.00!! Thats HALF OFF! This is for a > limited time only so ACT NOW! You can finally get > the results you've been waiting for. > > Order 1 Million FRESH Email Addresses for only $50.00! > > This list is barely a month old and we will replace every > non deliverable with 3 new addresses! Order now! > > > > For more information on our prices and services, please email us at: > > bulkreply3@yahoo.com > > Thank You. > From owner-freebsd-current Tue Dec 9 05:44:02 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id FAA01989 for current-outgoing; Tue, 9 Dec 1997 05:44:02 -0800 (PST) (envelope-from owner-freebsd-current) Received: from hermes (hermes.uninet.net.mx [200.33.146.193]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id FAA01973 for ; Tue, 9 Dec 1997 05:43:56 -0800 (PST) (envelope-from eculp@ver1.telmex.net.mx) Received: from sunix by hermes (SMI-8.6/SMI-SVR4) id HAA20707; Tue, 9 Dec 1997 07:46:28 -0600 Message-ID: <348D4C63.231835E6@ver1.telmex.net.mx> Date: Tue, 09 Dec 1997 07:49:23 -0600 From: Edwin Culp Organization: Mexico Communicates, S.C. X-Mailer: Mozilla 3.01Gold (X11; I; Linux 2.0.14 i586) MIME-Version: 1.0 To: Alex CC: freebsd-current@freebsd.org Subject: Re: Undefined symbol _procfs_exit during make release. References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Alex wrote: > > On Mon, 8 Dec 1997, Edwin Culp wrote: > > > Yesterday I made my first attempt to do a make release and after about > > 600 Mega and 12 hours > > I got this Undefined symbol message. > > > > Does anyone know why? > > Do I have to go through the whole 12 hour process to rebuild the > > release? > > This was actually fixed right before your message was sent. Easiest thing > to do is run cvsup on your whole src tree which will update only the > things that need to be changed. Then you can rebuild anything you really > want to (like the kernel). > > - alex I did just that. I'm now about 6 hours into a new make release that I assume will be successful. This is the first time I've made a release so I'm still lacking confidence:-) Thanks a lot. ed From owner-freebsd-current Tue Dec 9 05:53:12 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id FAA02724 for current-outgoing; Tue, 9 Dec 1997 05:53:12 -0800 (PST) (envelope-from owner-freebsd-current) Received: from whqvax.picker.com (whqvax.picker.com [144.54.1.1]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id FAA02719 for ; Tue, 9 Dec 1997 05:53:06 -0800 (PST) (envelope-from rhh@ct.picker.com) Received: from ct.picker.com by whqvax.picker.com with SMTP; Tue, 9 Dec 1997 8:49:27 -0500 (EST) Received: from elmer.ct.picker.com by ct.picker.com (4.1/SMI-4.1) id AA23155; Tue, 9 Dec 97 08:49:25 EST Received: by elmer.ct.picker.com (SMI-8.6/SMI-SVR4) id IAA23174; Tue, 9 Dec 1997 08:49:14 -0500 Message-Id: <19971209084913.32436@ct.picker.com> Date: Tue, 9 Dec 1997 08:49:13 -0500 From: Randall Hopper To: Dennis Tenn , Luigi Rizzo , =?iso-8859-1?Q?=E1=CE=C4=D2=C5=CA_=FE=C5=D2=CE=CF=D7?= , Luoqi Chen , "Jordan K. Hubbard" , Amancio Hasty Cc: FreeBSD-current Subject: Re: SB AWE64 support References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.81 In-Reply-To: ; from Dennis Tenn on Fri, Dec 05, 1997 at 06:03:42AM -0500 Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Dennis Tenn: |Has anyone been able to get this card to work under FreeBSD 2.2.x or 3.0? Luoqi Chen: |Try the AWE32 driver from http://bahamut.mm.t.u-tokyo.ac.jp/~iwai/awedrv/, |it supports AWE wavetable synth. Driver in -current only supports FM synth |which sounds really pathetic. Maybe we should commit this new driver, I have |been running it with -stable for month without any problem. Conrad Sabatier got his AWE64 working with the port of the Linux AWEDRV using Luigi's PnP code. Check out: http://multiverse.com/~rhh/awedrv for FreeBSD port/package links. There's a link to Conrad's AWE PnP setup how-to off of this page. Randall From owner-freebsd-current Tue Dec 9 06:13:04 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id GAA03775 for current-outgoing; Tue, 9 Dec 1997 06:13:04 -0800 (PST) (envelope-from owner-freebsd-current) Received: from ns1.yes.no (ns1.yes.no [195.119.24.10]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id GAA03746; Tue, 9 Dec 1997 06:12:38 -0800 (PST) (envelope-from eivind@bitbox.follo.net) Received: from bitbox.follo.net (bitbox.follo.net [194.198.43.36]) by ns1.yes.no (8.8.7/8.8.7) with ESMTP id OAA02625; Tue, 9 Dec 1997 14:12:31 GMT Received: (from eivind@localhost) by bitbox.follo.net (8.8.6/8.8.6) id PAA18385; Tue, 9 Dec 1997 15:11:54 +0100 (MET) Message-ID: <19971209151153.42427@follo.net> Date: Tue, 9 Dec 1997 15:11:53 +0100 From: Eivind Eklund To: Mike Smith Cc: Eivind Eklund , dyson@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: VM system info References: <19971209013941.17444@follo.net> <199712090058.LAA06720@word.smith.net.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.88e In-Reply-To: <199712090058.LAA06720@word.smith.net.au>; from Mike Smith on Tue, Dec 09, 1997 at 11:28:50AM +1030 Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Tue, Dec 09, 1997 at 11:28:50AM +1030, Mike Smith wrote: > > I'd opt for it to be compiled as part of 'make world' instead, but > > there are certainly some good points to doing it at the kernel build > > time. > > If it was possible to automatically generate a supserset listing at > 'world' time, that would be good. I once more don't follow you - which superset? I was thinking of something like a perl script that goes through the kernel source and finds SYSCTL() macros and grab documentation from them, with support for some form of support for adding documentation for non-static SYSCTLs - possibly just by having a static file that describe them. This file would be concatenated with the doc extracted from the kernel source to create the documentation installed. > If I thought that there was an easy way to arrange pageable kernel > data, I would be leaping and screaming about putting the above data in > the kernel RBN. RBN? (Right B* Now?) > As it is, any alternative scheme that will serve as a stopgap for > now and actually achieve the desired goal without requiring massive > trampling of the kernel and major changes to the interface appeals. > Hacking some gratuitous macro changes in as a quickie-fix just > doesn't cut it. Let's try to orient this towards solutions instead of bashing each others solutions. My main priorities are as follows: (1) Documentation becomes available to user(s) (2) Documentation stays correct and complete (covering the relevant variables). (3) Keeping (1) and (2) add minimal workload to the developers; as far as possible we do work up front and cut the later costs (as otherwise we'll either block later development or let the documentation slip) (4) System should not be a stopgap - parts of the implementation of the scheme might change later, but the scaffolding itself should be good enough to be used as far down the road as we can see. (5) Any significant kernel bloat caused by this should be possible to disable. As far as I can see, the best solution to this is to change the sysctl-macros to add documentation, but I'm open to other solutions (as long as they at least satisfy (1), (2) and (3)). But before proposing other solutions, let me just outline the way I see this progress: (A) This will give us a standardized form of documentation in the kernel source. Nothing new will be exported to userland, no new interface will be defined, no new files created - the docs are just added as a required part of the kernel, so they can be looked up by people that have the kernel sources. (B) Documentation is exported to userland, by scanning kernel sources and generating text files as a part of 'make world'. (C) Parts of the kernel is made swappable; documentation is consigned to such a part. I don't know if this can be done by a C macro; if it can't, it will probably be necessary to scan the kernel and construct a new file for the documentation strings. If this is prohibitively expensive, we could add a make target to do it, and provide a default version in the CVS repository (which could be updated from time to time by running 'make sysctldocs' and committing). (D) Documentation is exported to userland by a kernel interface. I'm not certain that this is the best solution, as parts of it suck (esp. (C)) - but I've not seen any other suggestion that seems likely to satisfy requirement (1), (2) and (3) :-( But - to see if we can find a better solution - what are your priorities? Eivind. From owner-freebsd-current Tue Dec 9 06:27:32 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id GAA04788 for current-outgoing; Tue, 9 Dec 1997 06:27:32 -0800 (PST) (envelope-from owner-freebsd-current) Received: from germanium.xtalwind.net (germanium.xtalwind.net [205.160.242.5]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id GAA04777 for ; Tue, 9 Dec 1997 06:27:25 -0800 (PST) (envelope-from jack@germanium.xtalwind.net) Received: from localhost (localhost.xtalwind.net [127.0.0.1]) by germanium.xtalwind.net (8.8.8/8.8.7) with SMTP id JAA01069; Tue, 9 Dec 1997 09:27:56 -0500 (EST) Date: Tue, 9 Dec 1997 09:27:56 -0500 (EST) From: jack To: Alex cc: freebsd-current@FreeBSD.ORG Subject: Re: Telnet Root access In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Mon, 8 Dec 1997, Alex wrote: > On Mon, 8 Dec 1997, J Wunsch wrote: > > > Jim Bryant wrote: > > > > > is ssh/sshd a package yet? last time i made it, i had to build it > > > myself... > > > > You gotta shoot your government first, i'm afraid. > > Why doesn't someone outside of the US make a package of it? And whatever > happened to the SF District Judge's rulings (which applied to Walnut > Creek right?) on the whole encryption dealies? It was, almost immediately, stayed pending an appeal by the feds. I think the hearing on that is scheduled within the next week or so. -------------------------------------------------------------------------- Jack O'Neill Finger jacko@diamond.xtalwind.net or jack@xtalwind.net http://www.xtalwind.net/~jacko/pubpgp.html #include for my PGP key. PGP Key fingerprint = F6 C4 E6 D4 2F 15 A7 67 FD 09 E9 3C 5F CC EB CD enriched, vcard, HTML messages > /dev/null -------------------------------------------------------------------------- From owner-freebsd-current Tue Dec 9 06:33:45 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id GAA05440 for current-outgoing; Tue, 9 Dec 1997 06:33:45 -0800 (PST) (envelope-from owner-freebsd-current) Received: from ns1.yes.no (ns1.yes.no [195.119.24.10]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id GAA05426 for ; Tue, 9 Dec 1997 06:33:33 -0800 (PST) (envelope-from eivind@bitbox.follo.net) Received: from bitbox.follo.net (bitbox.follo.net [194.198.43.36]) by ns1.yes.no (8.8.7/8.8.7) with ESMTP id OAA02956; Tue, 9 Dec 1997 14:33:26 GMT Received: (from eivind@localhost) by bitbox.follo.net (8.8.6/8.8.6) id PAA18426; Tue, 9 Dec 1997 15:32:49 +0100 (MET) Message-ID: <19971209153249.09488@follo.net> Date: Tue, 9 Dec 1997 15:32:49 +0100 From: Eivind Eklund To: Terry Lambert Cc: current@freebsd.org Subject: Re: VM system info References: <19971209013941.17444@follo.net> <199712090203.TAA02842@usr05.primenet.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.88e In-Reply-To: <199712090203.TAA02842@usr05.primenet.com>; from Terry Lambert on Tue, Dec 09, 1997 at 02:03:41AM +0000 Sender: owner-freebsd-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Tue, Dec 09, 1997 at 02:03:41AM +0000, Terry Lambert wrote: > I'm firmly in the "if you commit it, document it" camp. > > HOWEVER... > > Inline documentation is just as bad, or worse, than non-inline > documentation. > > I disagree with the premise that it "is much more likely to be kept > up-to-date". > > Further, such documentation tends to obfuscate otherwise readable code > with all sorts of non-code pieces, making it less likely the code will > be maintained, either. Here is the way I work: (1) Files should have a single short comment at the top explain what this file is for. Maximum 3 lines. (2) Functions have a brief (1-2 lines) comment giving their reason for being. (3) Variables should have comments unless they have extremely explict names. You should never have to go hunting through the code to find how a variable is used; each variable is only allowed to have a single clear purpose. (4) Code is not commented. If necessary, the function comment can contain a reference to external documentation that explain the code. This should only happen for core functionality that can't be be implemented simply; in other cases, either drop the functionality or re-implement until it is simple. If something is so complex that it needs external documentation, it had better be non-changing. (5) Code prerequisites is documented through assert() or similar functionality. (6) Data structures are documented through a full invariant. This invariant is not necessarily called from the program, but it has been used during testing and is used to check any changes to manipulation routines. These rules work amazingly well. They work especially well when coupled with reviews or inspections (as in the formal review researched by IBM), as they create a good background for an inspection, but I don't think I've ever seen them result in outdated comments (even without regular reviews). BTW: If anybody is interested, I have a couple of invariants for FreeBSD kernel data structures. I haven't committed them as they would be dead code except when somebody actively used them to debug. They are too expensive to generally enable, even when running 'DIAGNOSTIC'. (They've saved my skin a couple of times, though.) Eivind. From owner-freebsd-current Tue Dec 9 08:43:46 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id IAA15074 for current-outgoing; Tue, 9 Dec 1997 08:43:46 -0800 (PST) (envelope-from owner-freebsd-current) Received: from crh.cl.msu.edu (crh.cl.msu.edu [35.8.1.24]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id IAA15061 for ; Tue, 9 Dec 1997 08:43:33 -0800 (PST) (envelope-from henrich@crh.cl.msu.edu) Received: (from henrich@localhost) by crh.cl.msu.edu (8.8.7/8.8.7) id LAA04851; Tue, 9 Dec 1997 11:43:31 -0500 (EST) (envelope-from henrich) Date: Tue, 9 Dec 1997 11:43:31 -0500 (EST) From: Charles Henrich Message-Id: <199712091643.LAA04851@crh.cl.msu.edu> To: perhaps@yes.no, freebsd-current@freebsd.org Subject: Re: VM system info Newsgroups: lists.freebsd.current References: <66jnt0$ddh$1@msunews.cl.msu.edu> X-Newsreader: NN version 6.5.0 CURRENT #1 Sender: owner-freebsd-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk In lists.freebsd.current you write: >(4) Code is not commented. If necessary, the function comment can > contain a reference to external documentation that explain the > code. This should only happen for core functionality that can't > be be implemented simply; in other cases, either drop the > functionality or re-implement until it is simple. If something is > so complex that it needs external documentation, it had better be > non-changing. YUCK! All code should be commented! Just to make things entirely clear, just because the author things this code "is so simple, everyone must understand it" does not make it so. >(5) Code prerequisites is documented through assert() or similar > functionality. Egads! I wish assert() was thrown down to the pits of hell. Its a programmers cop out. In almost no circumstance does one ever need to assert. If you find an error condition, COPE as best you can! Especially in the kernel. -Crh -- Charles Henrich Michigan State University henrich@msu.edu http://pilot.msu.edu/~henrich From owner-freebsd-current Tue Dec 9 09:21:19 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id JAA17108 for current-outgoing; Tue, 9 Dec 1997 09:21:19 -0800 (PST) (envelope-from owner-freebsd-current) Received: from critter.freebsd.dk (critter.freebsd.dk [195.8.129.26]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id JAA17100 for ; Tue, 9 Dec 1997 09:21:05 -0800 (PST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost.cybercity.dk [127.0.0.1]) by critter.freebsd.dk (8.8.7/8.8.7) with ESMTP id SAA00774; Tue, 9 Dec 1997 18:18:45 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: Charles Henrich cc: perhaps@yes.no, freebsd-current@FreeBSD.ORG Subject: Re: VM system info In-reply-to: Your message of "Tue, 09 Dec 1997 11:43:31 EST." <199712091643.LAA04851@crh.cl.msu.edu> Date: Tue, 09 Dec 1997 18:18:45 +0100 Message-ID: <772.881687925@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >>(5) Code prerequisites is documented through assert() or similar >> functionality. > >Egads! I wish assert() was thrown down to the pits of hell. Its a >programmers cop out. In almost no circumstance does one ever need to assert >. >If you find an error condition, COPE as best you can! Especially in the >kernel. Well, suffice to say that I disagree more than words can express. In particular in a kernel should assert be used to guard against "bad news", but lets just remember that an assert can be as stealthy as a syslog entry or as intrusive as a panic. It all depends exactly how bad. -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." From owner-freebsd-current Tue Dec 9 09:29:00 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id JAA17584 for current-outgoing; Tue, 9 Dec 1997 09:29:00 -0800 (PST) (envelope-from owner-freebsd-current) Received: from tgn2.tgn.net (root@tgn2.tgn.net [205.241.85.2]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id JAA17556 for ; Tue, 9 Dec 1997 09:28:48 -0800 (PST) (envelope-from gemohler@tgn2.tgn.net) Received: (from gemohler@localhost) by tgn2.tgn.net (8.8.5/8.8.5) id LAA20296; Tue, 9 Dec 1997 11:27:53 -0600 (CST) Date: Tue, 9 Dec 1997 11:27:53 -0600 (CST) From: Geoff Mohler To: current@FreeBSD.ORG Subject: Namei cache? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Did there used to be a directive for configuring the kernel to hav a large(r) namei cache? I thought I saw this around 2.1.5 (or so) in the LINT file, and it really beefed up the speed of my INN server. Ive got my CCD running great at 64k interleave, with -i2048 -c16 as flags to newfs. Im just wondering where that one directive went off to. Thanks. From owner-freebsd-current Tue Dec 9 09:34:54 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id JAA18153 for current-outgoing; Tue, 9 Dec 1997 09:34:54 -0800 (PST) (envelope-from owner-freebsd-current) Received: from austin.polstra.com (austin.polstra.com [206.213.73.10]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id JAA18145 for ; Tue, 9 Dec 1997 09:34:45 -0800 (PST) (envelope-from jdp@austin.polstra.com) Received: from austin.polstra.com (jdp@localhost) by austin.polstra.com (8.8.8/8.8.7) with ESMTP id JAA01223; Tue, 9 Dec 1997 09:34:37 -0800 (PST) (envelope-from jdp) Message-Id: <199712091734.JAA01223@austin.polstra.com> To: smp@csn.net Subject: Re: -current, goliath, smp -- problems In-Reply-To: <199712082346.QAA13842@Ilsa.StevesCafe.com> References: <199712082346.QAA13842@Ilsa.StevesCafe.com> Organization: Polstra & Co., Seattle, WA Cc: current@freebsd.org Date: Tue, 09 Dec 1997 09:34:37 -0800 From: John Polstra Sender: owner-freebsd-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > rtld was broken on december 3rd, causing emacs to die. OI think it was > fixed by the 5th or 6th. More like: Emacs was and is broken, but it happened to work anyway until a change was made to the dynamic linker on November 29. To make the broken emacs work again, a work-around was implemented in the dynamic linker on December 5. John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Self-knowledge is always bad news." -- John Barth From owner-freebsd-current Tue Dec 9 09:40:29 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id JAA18457 for current-outgoing; Tue, 9 Dec 1997 09:40:29 -0800 (PST) (envelope-from owner-freebsd-current) Received: from crh.cl.msu.edu (crh.cl.msu.edu [35.8.1.24]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id JAA18448 for ; Tue, 9 Dec 1997 09:40:22 -0800 (PST) (envelope-from henrich@crh.cl.msu.edu) Received: (from henrich@localhost) by crh.cl.msu.edu (8.8.7/8.8.7) id MAA05374; Tue, 9 Dec 1997 12:40:16 -0500 (EST) (envelope-from henrich) Message-ID: <19971209124016.19617@crh.cl.msu.edu> Date: Tue, 9 Dec 1997 12:40:16 -0500 From: Charles Henrich To: Poul-Henning Kamp Cc: perhaps@yes.no, freebsd-current@FreeBSD.ORG Subject: Re: VM system info References: <199712091643.LAA04851@crh.cl.msu.edu> <772.881687925@critter.freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.84 In-Reply-To: <772.881687925@critter.freebsd.dk>; from Poul-Henning Kamp on Tue, Dec 09, 1997 at 06:18:45PM +0100 X-Operating-System: FreeBSD 2.2.5-RELEASE X-PGP-Fingerprint: 1024/F7 FD C7 3A F5 6A 23 BF 76 C4 B8 C9 6E 41 A4 4F Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On the subject of Re: VM system info, Poul-Henning Kamp stated: > >>(5) Code prerequisites is documented through assert() or similar > >>functionality. > > > >Egads! I wish assert() was thrown down to the pits of hell. Its a > >programmers cop out. In almost no circumstance does one ever need to > >assert . If you find an error condition, COPE as best you can! Especially > >in the kernel. > > Well, suffice to say that I disagree more than words can express. > > In particular in a kernel should assert be used to guard against "bad news", > but lets just remember that an assert can be as stealthy as a syslog entry > or as intrusive as a panic. It all depends exactly how bad. I am referring to the assert() function which says if this fails, panic.. Thats (in most cases) not a good approach. Now I agree that one should test all conditions all the time to make sure the actions your about to take are sane. -Crh Charles Henrich Michigan State University henrich@msu.edu http://pilot.msu.edu/~henrich From owner-freebsd-current Tue Dec 9 10:58:42 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id KAA23952 for current-outgoing; Tue, 9 Dec 1997 10:58:42 -0800 (PST) (envelope-from owner-freebsd-current) Received: from critter.freebsd.dk (critter.freebsd.dk [195.8.129.26]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id KAA23921 for ; Tue, 9 Dec 1997 10:58:25 -0800 (PST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost.cybercity.dk [127.0.0.1]) by critter.freebsd.dk (8.8.7/8.8.7) with ESMTP id TAA00964; Tue, 9 Dec 1997 19:55:36 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: Geoff Mohler cc: current@FreeBSD.ORG Subject: Re: Namei cache? In-reply-to: Your message of "Tue, 09 Dec 1997 11:27:53 CST." Date: Tue, 09 Dec 1997 19:55:35 +0100 Message-ID: <962.881693735@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk In message , Geoff Mohle r writes: >Did there used to be a directive for configuring the kernel to hav a >large(r) namei cache? > >I thought I saw this around 2.1.5 (or so) in the LINT file, and it really >beefed up the speed of my INN server. > >Ive got my CCD running great at 64k interleave, with -i2048 -c16 as flags >to newfs. > >Im just wondering where that one directive went off to. In current there is little you can do. You can try to increase: kern.maxvnodes debug.wantfreevnodes -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." From owner-freebsd-current Tue Dec 9 10:59:57 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id KAA24080 for current-outgoing; Tue, 9 Dec 1997 10:59:57 -0800 (PST) (envelope-from owner-freebsd-current) Received: from ns1.yes.no (ns1.yes.no [195.119.24.10]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id KAA24017 for ; Tue, 9 Dec 1997 10:59:17 -0800 (PST) (envelope-from eivind@bitbox.follo.net) Received: from bitbox.follo.net (bitbox.follo.net [194.198.43.36]) by ns1.yes.no (8.8.7/8.8.7) with ESMTP id SAA05699; Tue, 9 Dec 1997 18:59:05 GMT Received: (from eivind@localhost) by bitbox.follo.net (8.8.6/8.8.6) id TAA19119; Tue, 9 Dec 1997 19:58:27 +0100 (MET) Message-ID: <19971209195826.64951@follo.net> Date: Tue, 9 Dec 1997 19:58:26 +0100 From: Eivind Eklund To: Charles Henrich Cc: perhaps@yes.no, freebsd-current@freebsd.org Subject: Re: VM system info References: <66jnt0$ddh$1@msunews.cl.msu.edu> <199712091643.LAA04851@crh.cl.msu.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.88e In-Reply-To: <199712091643.LAA04851@crh.cl.msu.edu>; from Charles Henrich on Tue, Dec 09, 1997 at 11:43:31AM -0500 Sender: owner-freebsd-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Tue, Dec 09, 1997 at 11:43:31AM -0500, Charles Henrich wrote: > In lists.freebsd.current you write: > > >(4) Code is not commented. If necessary, the function comment can > > contain a reference to external documentation that explain the > > code. This should only happen for core functionality that can't > > be be implemented simply; in other cases, either drop the > > functionality or re-implement until it is simple. If something is > > so complex that it needs external documentation, it had better be > > non-changing. > > YUCK! All code should be commented! Just to make things entirely > clear, just because the author things this code "is so simple, > everyone must understand it" does not make it so. If you read carefully, you'd have found that there were quite a few other rules about commenting. Have you ever tried reading code where variables are clearly documented? It is _way_ easier to read than code that is directly documented. "Say it in code; comment if you can't." That "can't" is fairly rare. > >(5) Code prerequisites is documented through assert() or similar > > functionality. > > Egads! I wish assert() was thrown down to the pits of hell. Its a > programmers cop out. In almost no circumstance does one ever need to assert. > If you find an error condition, COPE as best you can! Especially in the > kernel. There are four ways to cope: (1) Ignore error; return OK, even though the function failed to do it's job. (2) Return error code (3) Throw an exception of some sort, e.g. longjmp(). (4) panic(), a la assert(). I'm arguing that when there is a BUG in your program, the correct answer is (4), possibly as a combination with (3) or (2). Why? You're already dealing with a buggy system. There is no chance in hell that you caller 'know how to deal with the error' - the error is an error of program structure, and a routine isn't supposed to know how to deal with errors from calls that can't fail. If you argue that this is an exceptional case just like a file not being present, and should be handled the same way - I disagree. A complicated and sloppy system has a much higher risk of being buggy than a small and rigidly defined system which trap all errors as soon as possible. The assertions are part of the definition of the system. They are a technique to get that rigid definition, the one that create an error when the system would otherwise behave outside the specs - to allow you to actually limit the system to behave exactly inside spec. This isn't laziness - it is the way to create robust, correct systems. Eivind. From owner-freebsd-current Tue Dec 9 11:24:44 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id LAA25764 for current-outgoing; Tue, 9 Dec 1997 11:24:44 -0800 (PST) (envelope-from owner-freebsd-current) Received: from sumatra.americantv.com (sumatra.americantv.com [207.170.17.37]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id LAA25750 for ; Tue, 9 Dec 1997 11:24:38 -0800 (PST) (envelope-from jlemon@americantv.com) Received: from right.PCS (right.PCS [148.105.10.31]) by sumatra.americantv.com (8.8.5/8.8.5) with ESMTP id NAA11843; Tue, 9 Dec 1997 13:24:32 -0600 (CST) Received: (from jlemon@localhost) by right.PCS (8.6.13/8.6.4) id NAA18297; Tue, 9 Dec 1997 13:24:00 -0600 Message-ID: <19971209132400.25371@right.PCS> Date: Tue, 9 Dec 1997 13:24:00 -0600 From: Jonathan Lemon To: Karl Denninger Cc: Mike Fisher , abuse@mcs.net, noc@harborcom.net, current@FreeBSD.ORG Subject: Re: Your message has been BOUNCED by Spamblock(tm) (fwd) References: <19971209073649.52545@mcs.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.61.1 In-Reply-To: <19971209073649.52545@mcs.net>; from Karl Denninger on Dec 12, 1997 at 07:36:49AM -0600 Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Dec 12, 1997 at 07:36:49AM -0600, Karl Denninger wrote: > FreeBSD - Note that Harborcom doesn't like us bitching about spam they relay > to us. Awww, poor babies! Uh, I believe that harborcom is a mail exploder for the FreeBSD list. They don't have anything to do with this spam. > > Received: from gbms01.uwgb.edu (gbms01.uwgb.edu [143.200.128.3]) > > by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id AAA13243; > > Tue, 9 Dec 1997 00:31:40 -0800 (PST) > > (envelope-from replyz_bulk@juno.com) > > Received: from vucqpqlj (sfdn6-198.sf.compuserve.com) > > by gbms01.uwgb.edu (PMDF V5.1-10 #25737) > > with SMTP id <01IQYAKEZRQS0001OX@gbms01.uwgb.edu>; Tue, 9 Dec 1997 01:29:20 CST You should be complaining to uwgb.edu, who _is_ apparently being used as a relay, in this case, by a compuserve customer. -- Jonathan From owner-freebsd-current Tue Dec 9 11:40:50 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id LAA27067 for current-outgoing; Tue, 9 Dec 1997 11:40:50 -0800 (PST) (envelope-from owner-freebsd-current) Received: from frmug.org (frmug-gw.frmug.org [193.56.58.252]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id LAA27055; Tue, 9 Dec 1997 11:40:36 -0800 (PST) (envelope-from roberto@keltia.freenix.fr) Received: (from uucp@localhost) by frmug.org (8.8.8/frmug-2.1/nospam) with UUCP id UAA00200; Tue, 9 Dec 1997 20:40:25 +0100 (CET) (envelope-from roberto@keltia.freenix.fr) Received: (from roberto@localhost) by keltia.freenix.fr (8.8.8/keltia-2.13/nospam) id UAA00651; Tue, 9 Dec 1997 20:36:35 +0100 (CET) (envelope-from roberto) Message-ID: <19971209203634.38303@keltia.freenix.fr> Date: Tue, 9 Dec 1997 20:36:34 +0100 From: Ollivier Robert To: "FreeBSD Current Users' list" Cc: sef@FreeBSD.ORG Subject: Interaction between truss(1) and ktrace(1) ? Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.88 X-Operating-System: FreeBSD 3.0-CURRENT ctm#3883 AMD-K6 MMX @ 208 MHz Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk I have a very recent kernel (with the latest procfs fixes from Sean) and it has KTRACE defined in it. The main problem I have is that truss does execute the command but doesn't show anything... Running this: 203 [20:30] roberto@keltia:~> truss /bin/echo foo cannot set PF_LINGER: Inappropriate ioctl for device foo ^C ...and sits there till I kill it. Sources from CTM delta cvs-cur #3883 1997/12/09 14:11:27. Make world done yesterday. Is there a problem between KTRACE and truss ? What did I miss ? Latest patch from Sean is this one: sef 1997/12/08 21:03:43 PST Modified files: sys/miscfs/procfs procfs_subr.c Log: Code to prevent a panic caused by procfs_exit(). Note that i don't know what is teh root cause -- but, sometimes, a procfs vnode in pfshead is apparantly corrupt (or a UFS vnode instead). Without this patch, I can get it to panic by doing (in csh) Kernel config. file available on demand. -- Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- roberto@keltia.freenix.fr FreeBSD keltia.freenix.fr 3.0-CURRENT #19: Tue Dec 9 20:17:10 CET 1997 From owner-freebsd-current Tue Dec 9 11:56:16 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id LAA28525 for current-outgoing; Tue, 9 Dec 1997 11:56:16 -0800 (PST) (envelope-from owner-freebsd-current) Received: from crh.cl.msu.edu (crh.cl.msu.edu [35.8.1.24]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id LAA28441 for ; Tue, 9 Dec 1997 11:55:59 -0800 (PST) (envelope-from henrich@crh.cl.msu.edu) Received: (from henrich@localhost) by crh.cl.msu.edu (8.8.7/8.8.7) id OAA00729; Tue, 9 Dec 1997 14:55:49 -0500 (EST) (envelope-from henrich) Message-ID: <19971209145549.60899@crh.cl.msu.edu> Date: Tue, 9 Dec 1997 14:55:49 -0500 From: Charles Henrich To: Eivind Eklund Cc: perhaps@yes.no, freebsd-current@freebsd.org Subject: Re: VM system info References: <66jnt0$ddh$1@msunews.cl.msu.edu> <199712091643.LAA04851@crh.cl.msu.edu> <19971209195826.64951@follo.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.84 In-Reply-To: <19971209195826.64951@follo.net>; from Eivind Eklund on Tue, Dec 09, 1997 at 07:58:26PM +0100 X-Operating-System: FreeBSD 2.2.5-RELEASE X-PGP-Fingerprint: 1024/F7 FD C7 3A F5 6A 23 BF 76 C4 B8 C9 6E 41 A4 4F Sender: owner-freebsd-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On the subject of Re: VM system info, Eivind Eklund stated: > If you read carefully, you'd have found that there were quite a few other > rules about commenting. Have you ever tried reading code where variables > are clearly documented? It is _way_ easier to read than code that is > directly documented. I did read what you said, I only commented on those I disagreed with. Variable commenting is important. > There are four ways to cope: (1) Ignore error; return OK, even though the > function failed to do it's job. (2) Return error code (3) Throw an > exception of some sort, e.g. longjmp(). (4) panic(), a la assert(). That depends greatly on the situation. There is also a (5) that says take all given known information and continue onward, while logging the error. In some cases its obviously not possible where a routine is designed to have no return value. This reminds me entirely of AFS, one of the worst pieces of kernel code I've ever stumbled upon, that spends half its time in asserts() where completely unnecessary. Instead of taking a moment to figure out whats really going on when a condition failed, the programmers took the easy way out, and panic'd the machine. Hardly acceptable in the case of a production environment where users very well may lose months of ongoing work. > present, and should be handled the same way - I disagree. A complicated and > sloppy system has a much higher risk of being buggy than a small and rigidly > defined system which trap all errors as soon as possible. Im not arguing the trap all errors as soon as possible piece, im arguing in what you do when you detect one. To shutdown the machine is the worst solution. Lets think for a moment about the case if your the computer system on a F-15 fighter jet, the last thing the pilot wants to see is "Panic, system halted" as he spirals to his death instead of the software attempting to cope as best as possible. -Crh Charles Henrich Michigan State University henrich@msu.edu http://pilot.msu.edu/~henrich From owner-freebsd-current Tue Dec 9 12:17:56 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id MAA00742 for current-outgoing; Tue, 9 Dec 1997 12:17:56 -0800 (PST) (envelope-from owner-freebsd-current) Received: from tgn2.tgn.net (root@tgn2.tgn.net [205.241.85.2]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id MAA00732 for ; Tue, 9 Dec 1997 12:17:46 -0800 (PST) (envelope-from gemohler@tgn2.tgn.net) Received: (from gemohler@localhost) by tgn2.tgn.net (8.8.5/8.8.5) id OAA29290; Tue, 9 Dec 1997 14:14:16 -0600 (CST) Date: Tue, 9 Dec 1997 14:14:16 -0600 (CST) From: Geoff Mohler To: Poul-Henning Kamp cc: current@FreeBSD.ORG Subject: Re: Namei cache? In-Reply-To: <962.881693735@critter.freebsd.dk> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > In current there is little you can do. > > You can try to increase: > > kern.maxvnodes > debug.wantfreevnodes I see what these values currently are, but what are my boundaries and rules I have to follow in changing them..IE: stay in 4096 incrememnts..dont go above 99999...etc. From owner-freebsd-current Tue Dec 9 12:24:18 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id MAA01266 for current-outgoing; Tue, 9 Dec 1997 12:24:18 -0800 (PST) (envelope-from owner-freebsd-current) Received: from Ilsa.StevesCafe.com (Ilsa.StevesCafe.com [205.168.119.129]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id MAA01208; Tue, 9 Dec 1997 12:23:59 -0800 (PST) (envelope-from fbsd@Ilsa.StevesCafe.com) Received: from Ilsa.StevesCafe.com (localhost [127.0.0.1]) by Ilsa.StevesCafe.com (8.8.7/8.8.5) with ESMTP id NAA17839; Tue, 9 Dec 1997 13:23:51 -0700 (MST) Message-Id: <199712092023.NAA17839@Ilsa.StevesCafe.com> X-Mailer: exmh version 2.0gamma 1/27/96 From: Steve Passe To: smp@freebsd.org cc: current@freebsd.org Subject: Usable SMP on 971208 Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 09 Dec 1997 13:23:51 -0700 Sender: owner-freebsd-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi, I just finished rebuilding the world from yesterdays -current (97-12-08) It completed, installed, and rebuilt itself without errors, the 2nd buildworld: 258 # date; time make -k -j4 buildworld; date Tue Dec 9 09:57:09 MST 1997 ... 5826.47s real 4846.91s user 3213.41s system Tue Dec 9 11:34:15 MST 1997 It would appear that December 8, 1997 is a good date for which to grab SMP source. -- Steve Passe | powered by smp@csn.net | Symmetric MultiProcessor FreeBSD From owner-freebsd-current Tue Dec 9 12:47:52 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id MAA03935 for current-outgoing; Tue, 9 Dec 1997 12:47:52 -0800 (PST) (envelope-from owner-freebsd-current) Received: from mom.hooked.net (root@mom.hooked.net [206.80.6.10]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id MAA03921 for ; Tue, 9 Dec 1997 12:47:44 -0800 (PST) (envelope-from garbanzo@hooked.net) Received: from fish.hooked.net (garbanzo@fish.hooked.net [206.80.6.48]) by mom.hooked.net (8.8.5/8.8.5) with SMTP id MAA09807; Tue, 9 Dec 1997 12:47:28 -0800 (PST) Date: Tue, 9 Dec 1997 12:47:28 -0800 (PST) From: Alex To: Edwin Culp cc: freebsd-current@freebsd.org Subject: Re: Undefined symbol _procfs_exit during make release. In-Reply-To: <348D4C63.231835E6@ver1.telmex.net.mx> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Tue, 9 Dec 1997, Edwin Culp wrote: > Alex wrote: > > > > On Mon, 8 Dec 1997, Edwin Culp wrote: > > > > > Yesterday I made my first attempt to do a make release and after about > > > 600 Mega and 12 hours > > > I got this Undefined symbol message. > > > > > > Does anyone know why? > > > Do I have to go through the whole 12 hour process to rebuild the > > > release? > > > > This was actually fixed right before your message was sent. Easiest thing > > to do is run cvsup on your whole src tree which will update only the > > things that need to be changed. Then you can rebuild anything you really > > want to (like the kernel). > > > > - alex > > I did just that. I'm now about 6 hours into a new make release that I > assume > will be successful. This is the first time I've made a release so I'm > still > lacking confidence:-) Well actually you don't need to make release to build your own kernel. Just make your kernel config file (usually placed in src/sys/i386/conf) cd to that dir (the one you put your config file) run config configfilename, cd to the dir that config spitsout, and run make (then make install if you want to use it). config -g will generate a set of makefiles that add debugging info to the kernel. - alex From owner-freebsd-current Tue Dec 9 13:06:48 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id NAA05623 for current-outgoing; Tue, 9 Dec 1997 13:06:48 -0800 (PST) (envelope-from owner-freebsd-current) Received: from frmug.org (frmug-gw.frmug.org [193.56.58.252]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id NAA05601 for ; Tue, 9 Dec 1997 13:06:37 -0800 (PST) (envelope-from roberto@keltia.freenix.fr) Received: (from uucp@localhost) by frmug.org (8.8.8/frmug-2.1/nospam) with UUCP id WAA12328 for freebsd-current@FreeBSD.ORG; Tue, 9 Dec 1997 22:06:14 +0100 (CET) (envelope-from roberto@keltia.freenix.fr) Received: (from roberto@localhost) by keltia.freenix.fr (8.8.8/keltia-2.13/nospam) id WAA03330; Tue, 9 Dec 1997 22:05:05 +0100 (CET) (envelope-from roberto) Message-ID: <19971209220505.49592@keltia.freenix.fr> Date: Tue, 9 Dec 1997 22:05:05 +0100 From: Ollivier Robert To: "FreeBSD Current Users' list" Subject: Re: Interaction between truss(1) and ktrace(1) ? References: <19971209203634.38303@keltia.freenix.fr> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.88 In-Reply-To: <19971209203634.38303@keltia.freenix.fr>; from Ollivier Robert on Tue, Dec 09, 1997 at 08:36:34PM +0100 X-Operating-System: FreeBSD 3.0-CURRENT ctm#3883 AMD-K6 MMX @ 208 MHz Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk According to Ollivier Robert: > I have a very recent kernel (with the latest procfs fixes from Sean) and it > has KTRACE defined in it. The main problem I have is that truss does > execute the command but doesn't show anything... Pilot error. /sys/sys/pioctl.h was good whereas /usr/include/sys/pioctl.h was bad (old definition). Running happily truss(1) now, thank to Sean. *-<:-) -- Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- roberto@keltia.freenix.fr FreeBSD keltia.freenix.fr 3.0-CURRENT #19: Tue Dec 9 20:17:10 CET 1997 From owner-freebsd-current Tue Dec 9 13:22:53 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id NAA06650 for current-outgoing; Tue, 9 Dec 1997 13:22:53 -0800 (PST) (envelope-from owner-freebsd-current) Received: from critter.freebsd.dk (critter.freebsd.dk [195.8.129.26]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id NAA06639 for ; Tue, 9 Dec 1997 13:22:40 -0800 (PST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost.cybercity.dk [127.0.0.1]) by critter.freebsd.dk (8.8.7/8.8.7) with ESMTP id WAA01202; Tue, 9 Dec 1997 22:20:23 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: Geoff Mohler cc: current@FreeBSD.ORG Subject: Re: Namei cache? In-reply-to: Your message of "Tue, 09 Dec 1997 14:14:16 CST." Date: Tue, 09 Dec 1997 22:20:23 +0100 Message-ID: <1200.881702423@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk In message , Geoff Mohle r writes: >> In current there is little you can do. >> >> You can try to increase: >> >> kern.maxvnodes >> debug.wantfreevnodes > >I see what these values currently are, but what are my boundaries and >rules I have to follow in changing them..IE: stay in 4096 >incrememnts..dont go above 99999...etc. You'll run out of memory if you set them too high... Add 10% or so at a a time, let it run for a day before you judge the result... -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." From owner-freebsd-current Tue Dec 9 14:26:46 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id OAA12093 for current-outgoing; Tue, 9 Dec 1997 14:26:46 -0800 (PST) (envelope-from owner-freebsd-current) Received: from sci.brooklyn.cuny.edu (dayton@louis.sci.brooklyn.cuny.edu [146.245.1.7]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id OAA12081 for ; Tue, 9 Dec 1997 14:26:35 -0800 (PST) (envelope-from dayton@sci.brooklyn.cuny.edu) Received: (from dayton@localhost) by sci.brooklyn.cuny.edu (8.8.7/8.8.4) id RAA18006; Tue, 9 Dec 1997 17:25:41 -0500 (EST) Date: Tue, 9 Dec 1997 17:25:41 -0500 (EST) Message-Id: <199712092225.RAA18006@sci.brooklyn.cuny.edu> From: Dayton Clark To: garbanzo@hooked.net CC: smp@csn.net, current@freebsd.org In-reply-to: (message from Alex on Mon, 8 Dec 1997 22:57:19 -0800 (PST)) Subject: 8CPUs Sender: owner-freebsd-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk IBM has advertised an 8 cpu server for several years. I was never able to get anyone to give me a quote though. There is a French organization (or company) that implemented a multi-pentium connection scheme. I think it is called the CBUS. As I remember, it's an interesting system, but totally incompatible with the Intel MP stuff. dayton >>>>> "Alex" == Alex writes: Alex> On Mon, 8 Dec 1997, Steve Passe wrote: >> rtld was broken on december 3rd, causing emacs to die. OI think it >> was fixed by the 5th or 6th. >> >> I'm at a loss about the other 2 problems. They may be related to 4 >> CPUs, but I have been TOTALLY unsuccessful in getting access to a 4 >> CPU machine for testing. Show of hands, anyone successfully running >> SMP on 4 or more CPUs? Alex> Speaking of more CPUs, did anyone catch the release of Alex> HP's newest SMP server? An 8 CPU (I'm assuming PPro) *drool*. Alex> I'm assuming it comes with gobs of ram and disk space, and it Alex> amusingly enough looked like an overgrown dot-matrix printer with Alex> no paper. I didn't realize there were production machines with Alex> more than 4 Intel CPUs *drool*. Alex> - alex From owner-freebsd-current Tue Dec 9 14:31:24 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id OAA12715 for current-outgoing; Tue, 9 Dec 1997 14:31:24 -0800 (PST) (envelope-from owner-freebsd-current) Received: from frmug.org (frmug-gw.frmug.org [193.56.58.252]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id OAA12679 for ; Tue, 9 Dec 1997 14:31:11 -0800 (PST) (envelope-from roberto@keltia.freenix.fr) Received: (from uucp@localhost) by frmug.org (8.8.8/frmug-2.1/nospam) with UUCP id XAA22404 for freebsd-current@FreeBSD.ORG; Tue, 9 Dec 1997 23:31:00 +0100 (CET) (envelope-from roberto@keltia.freenix.fr) Received: (from roberto@localhost) by keltia.freenix.fr (8.8.8/keltia-2.13/nospam) id XAA00308; Tue, 9 Dec 1997 23:28:40 +0100 (CET) (envelope-from roberto) Message-ID: <19971209232839.18908@keltia.freenix.fr> Date: Tue, 9 Dec 1997 23:28:39 +0100 From: Ollivier Robert To: "FreeBSD Current Users' list" Subject: Weird panic Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.88 X-Operating-System: FreeBSD 3.0-CURRENT ctm#3883 AMD-K6 MMX @ 208 MHz Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk I've seen my machine completely lockup under X regularely (generally during the night of course) and switched to a virtual console to see if I could catch it panicing (I use DDB). Here is what I got kernel: type 12 trap, code=0 Stopped at _tcp_slowtime+0x35 cmpl $0x1,0x8(%eax) trace _tcp_slowtimo(0,f0126568,f4880fa0,f0109863,0) at _tcp_slowtimo+0x35 _pfslowtimo(0,c0000000,f125e396,89789d64,1c22ee48) at _pfslowtimo+0x23 _softclock(0,27,27,1c22ee48,89789d64) at _softclock+0xc3 doreti_swi() at doreti_swi+0xf registers: cs 0x8 ds 0x10 es 0x10 ss 0x10 eax 0x400 ecx 0xf27b8914 edx 0x4b0 ebx 0xf01c1ba8 _inetsw+0x68 esp 0xf4880f60 ebp 0xf4880f6c esi 0xf0825e00 edi 0xc0000000 eip 0xf01579cd _tcp_slowtimo+0x35 efl 0x10206 Does it sound familiar to anyone ? The lockups stopped during most of November and started again a few days ago. I have a dump but without -g it won't be very useful. K6-210, 64 MB RAM, 1x SC-875 UW, 1x SC-810 SCSI. Here my kernel config: # # GENERIC -- Generic machine with WD/AHx/NCR/BTx family disks # # $Id: GENERIC,v 1.11 1994/11/08 07:39:26 jkh Exp $ # machine "i386" cpu "I586_CPU" ident "NKELTIA" maxusers 20 options INET #InterNETworking options FFS #Berkeley Fast Filesystem options MFS #Berkeley Memory Filesystem options PROCFS #Berkeley proc Filesystem options NULLFS #Berkeley null Filesystem options "COMPAT_43" #Compatible with BSD 4.3 options UCONSOLE #for xconsole options USERCONFIG #boot -c editor options VISUAL_USERCONFIG #visual boot -c editor # options "MD5" options "VM86" # options SYSVSHM options SYSVSEM options SYSVMSG options "SHMMAXPGS=1024" # 4096 KB of sharable memory # options PQ_LARGECACHE options "CLK_USE_I586_CALIBRATION" # # Enable the kernel debugger. # options DDB options KTRACE options "AUTO_EOI_1" config kernel root on sd0 swap on sd0 and sd1 and sd2 dumps on sd0 controller isa0 controller fdc0 at isa? port "IO_FD1" bio irq 6 drq 2 vector fdintr disk fd0 at fdc0 drive 0 controller pci0 controller ncr0 controller ncr1 controller scbus0 at ncr0 controller scbus1 at ncr1 # NCR0: ibm + ibm + tandberg disk sd0 at scbus0 target 0 unit 0 disk sd1 at scbus0 target 1 disk sd2 at scbus0 target 2 disk sd3 at scbus0 target 3 tape st1 at scbus0 target 4 # NCR1: conner + micropolis + CD + HP DAT disk sd10 at scbus1 target 0 disk sd11 at scbus1 target 1 disk sd12 at scbus1 target 2 disk sd13 at scbus1 target 3 tape st0 at scbus1 target 5 device cd0 at scbus1 target 6 device pcm0 at isa? port ? tty irq 5 drq 3 flags 0x0 vector pcmintr options "CONFIG_SBPRO" device sc0 at isa? port "IO_KBD" tty irq 1 vector scintr device npx0 at isa? port "IO_NPX" irq 13 flags 0x7 vector npxintr device sio0 at isa? port "IO_COM1" tty irq 4 vector siointr device sio1 at isa? port "IO_COM2" tty irq 3 vector siointr device lpt0 at isa? port? tty irq 7 vector lptintr device psm0 at isa? port "IO_KBD" conflicts tty irq 12 vector psmintr device ed0 at isa? port 0x300 net irq 10 iomem 0xb0000 vector edintr pseudo-device loop pseudo-device ether pseudo-device ppp 1 pseudo-device bpfilter 4 #Berkeley packet filter pseudo-device pty 64 pseudo-device speaker pseudo-device vn #Vnode driver (turns a file into a device) pseudo-device tun 1 #Enable user-level PPP see ppp(8) pseudo-device snp 3 #Snoop device - to look at pty/vty/etc.. -- Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- roberto@keltia.freenix.fr FreeBSD keltia.freenix.fr 3.0-CURRENT #19: Tue Dec 9 20:17:10 CET 1997 From owner-freebsd-current Tue Dec 9 15:32:44 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id PAA17022 for current-outgoing; Tue, 9 Dec 1997 15:32:44 -0800 (PST) (envelope-from owner-freebsd-current) Received: from word.smith.net.au (vh1.gsoft.com.au [203.38.152.122]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id PAA16995; Tue, 9 Dec 1997 15:32:26 -0800 (PST) (envelope-from mike@word.smith.net.au) Received: from word (localhost [127.0.0.1]) by word.smith.net.au (8.8.8/8.8.5) with ESMTP id JAA00418; Wed, 10 Dec 1997 09:56:17 +1030 (CST) Message-Id: <199712092326.JAA00418@word.smith.net.au> X-Mailer: exmh version 2.0zeta 7/24/97 To: Eivind Eklund cc: Mike Smith , Eivind Eklund , dyson@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: VM system info In-reply-to: Your message of "Tue, 09 Dec 1997 15:11:53 BST." <19971209151153.42427@follo.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 10 Dec 1997 09:56:17 +1030 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > On Tue, Dec 09, 1997 at 11:28:50AM +1030, Mike Smith wrote: > > > I'd opt for it to be compiled as part of 'make world' instead, but > > > there are certainly some good points to doing it at the kernel build > > > time. > > > > If it was possible to automatically generate a supserset listing at > > 'world' time, that would be good. > > I once more don't follow you - which superset? A given built kernel will contain some subset of all the possible sysctl nodes. For a non-kernel-specific resource to be useful, it should contain (as far as possible) the union of all these sets, ie. a superset. > I was thinking of > something like a perl script that goes through the kernel source and > finds SYSCTL() macros and grab documentation from them, with support > for some form of support for adding documentation for non-static > SYSCTLs - possibly just by having a static file that describe them. I would probably prefer your original suggestion whereby a null macro or specially-formatted comment placed the documentation close to the code where the dynamically-created nodes were generated. > > If I thought that there was an easy way to arrange pageable kernel > > data, I would be leaping and screaming about putting the above data in > > the kernel RBN. > > RBN? (Right B* Now?) Yes. 8) > Let's try to orient this towards solutions instead of bashing each > others solutions. My main priorities are as follows: > > (1) Documentation becomes available to user(s) > (2) Documentation stays correct and complete (covering the relevant > variables). > (3) Keeping (1) and (2) add minimal workload to the developers; as far > as possible we do work up front and cut the later costs (as > otherwise we'll either block later development or let the > documentation slip) > (4) System should not be a stopgap - parts of the implementation of > the scheme might change later, but the scaffolding itself should > be good enough to be used as far down the road as we can see. > (5) Any significant kernel bloat caused by this should be possible to > disable. Sounds good. > As far as I can see, the best solution to this is to change the > sysctl-macros to add documentation, but I'm open to other solutions > (as long as they at least satisfy (1), (2) and (3)). How about something more generalised, that lets us document other kernel items than just sysctl nodes? Perhaps looking at the tools available for automatically generating code-related documentation would be enlightening? > But before proposing other solutions, let me just outline the way I > see this progress: > > (A) This will give us a standardized form of documentation in the > kernel source. Nothing new will be exported to userland, no new > interface will be defined, no new files created - the docs are just > added as a required part of the kernel, so they can be looked up by > people that have the kernel sources. Yup. > (B) Documentation is exported to userland, by scanning kernel sources > and generating text files as a part of 'make world'. Yup. > (C) Parts of the kernel is made swappable; documentation is consigned > to such a part. I don't know if this can be done by a C macro; if it > can't, it will probably be necessary to scan the kernel and construct > a new file for the documentation strings. If this is prohibitively > expensive, we could add a make target to do it, and provide a default > version in the CVS repository (which could be updated from time to > time by running 'make sysctldocs' and committing). If you are doing (B), this is not terribly useful; the output from (B) should be available via a standard API to userland programs. > (D) Documentation is exported to userland by a kernel interface. See (C). mike From owner-freebsd-current Tue Dec 9 15:33:51 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id PAA17159 for current-outgoing; Tue, 9 Dec 1997 15:33:51 -0800 (PST) (envelope-from owner-freebsd-current) Received: from limbo.rtfm.net (rtfm.net [204.141.125.38]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id PAA17137 for ; Tue, 9 Dec 1997 15:33:37 -0800 (PST) (envelope-from nathan@limbo.rtfm.net) Received: (from nathan@localhost) by limbo.rtfm.net (8.8.7/8.8.6) id RAA24863 for freebsd-current@FreeBSD.org; Tue, 9 Dec 1997 17:46:34 -0500 (EST) Date: Tue, 9 Dec 1997 17:46:34 -0500 (EST) From: Nathan Dorfman Message-Id: <199712092246.RAA24863@limbo.rtfm.net> To: freebsd-current@FreeBSD.org Subject: files.i386, npx mandatory, config problem? Sender: owner-freebsd-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk Latest cvsup (22:30 GMT, Tue Dec 9) has given me a small problem in kernel configuration. /usr/sbin/config LIMBO now prints an error: files.i386: npx must be either optional or standard The config and subsequent compile works fine if I change npx to standard. The compile worked before the cvsup (which was 971022-SNAP) worked fine. I haven't made world, it was the cvsup alone that started these problems. Obi-Wan cvsuped at the same time and got no problems; it isn't my configuration since config on GENERIC returns the same error. Any ideas? From owner-freebsd-current Tue Dec 9 16:07:11 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id QAA20559 for current-outgoing; Tue, 9 Dec 1997 16:07:11 -0800 (PST) (envelope-from owner-freebsd-current) Received: from pop.uniserve.com (pop.uniserve.com [204.244.156.3]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id QAA20553 for ; Tue, 9 Dec 1997 16:06:59 -0800 (PST) (envelope-from tom@uniserve.com) Received: from shell.uniserve.com [204.244.210.252] by pop.uniserve.com with smtp (Exim 1.73 #1) id 0xfZfa-0002jM-00; Tue, 9 Dec 1997 16:06:30 -0800 Date: Tue, 9 Dec 1997 16:06:27 -0800 (PST) From: Tom To: Nathan Dorfman cc: freebsd-current@freebsd.org Subject: Re: files.i386, npx mandatory, config problem? In-Reply-To: <199712092246.RAA24863@limbo.rtfm.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Tue, 9 Dec 1997, Nathan Dorfman wrote: ... > worked fine. I haven't made world, it was the cvsup alone that > started these problems. Obi-Wan cvsuped at the same time and got > no problems; it isn't my configuration since config on GENERIC returns > the same error. Probably "config" has changed, and you missed it because you haven't done a "make world" for some time. Probably a new "config" will understand the config file. > Any ideas? Tom From owner-freebsd-current Tue Dec 9 16:24:54 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id QAA22106 for current-outgoing; Tue, 9 Dec 1997 16:24:54 -0800 (PST) (envelope-from owner-freebsd-current) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id QAA22079 for ; Tue, 9 Dec 1997 16:24:44 -0800 (PST) (envelope-from j@uriah.heep.sax.de) Received: (from uucp@localhost) by sax.sax.de (8.8.8/8.8.8) with UUCP id BAA01851 for freebsd-current@freebsd.org; Wed, 10 Dec 1997 01:24:41 +0100 (CET) (envelope-from j@uriah.heep.sax.de) Received: (from j@localhost) by uriah.heep.sax.de (8.8.8/8.8.5) id XAA04562; Tue, 9 Dec 1997 23:40:29 +0100 (MET) Date: Tue, 9 Dec 1997 23:40:29 +0100 (MET) Message-Id: <199712092240.XAA04562@uriah.heep.sax.de> X-Newsreader: knews 0.9.6 Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) Organization: Private BSD site, Dresden X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E References: <199712031706.EAA03912@godzilla.zeta.org.au> From: j@uriah.heep.sax.de (J Wunsch) Subject: Re: Bootloader/kernel ignores "-a" flag... X-Original-Newsgroups: poster In-Reply-To: <199712031706.EAA03912@godzilla.zeta.org.au> To: freebsd-current@freebsd.org Sender: owner-freebsd-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Bruce Evans wrote: > -a only works with "config kernel swap on generic" in the > kernel config file. This should be the default, but it breaks > "root on ...". It has nothing to do with swap. What is the "root on ..." stuff required for in GENERIC? I'm wondering all the time why the line in GENERIC doesn't read just config kernel swap generic Perhaps config's syntax rules should be changed so to allow config kernel generic instead. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-current Tue Dec 9 16:25:13 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id QAA22143 for current-outgoing; Tue, 9 Dec 1997 16:25:13 -0800 (PST) (envelope-from owner-freebsd-current) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id QAA22133 for ; Tue, 9 Dec 1997 16:25:02 -0800 (PST) (envelope-from j@uriah.heep.sax.de) Received: (from uucp@localhost) by sax.sax.de (8.8.8/8.8.8) with UUCP id BAA01854; Wed, 10 Dec 1997 01:24:48 +0100 (CET) (envelope-from j@uriah.heep.sax.de) Received: (from j@localhost) by uriah.heep.sax.de (8.8.8/8.8.5) id XAA04600; Tue, 9 Dec 1997 23:52:19 +0100 (MET) Date: Tue, 9 Dec 1997 23:52:19 +0100 (MET) Message-Id: <199712092252.XAA04600@uriah.heep.sax.de> X-Newsreader: knews 0.9.6 Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) Organization: Private BSD site, Dresden X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E References: <348AE151.4190@shellnet.co.uk> From: j@uriah.heep.sax.de (J Wunsch) Subject: Re: Where can I get help ? X-Original-Newsgroups: poster In-Reply-To: <348AE151.4190@shellnet.co.uk> To: freebsd-current@freebsd.org Cc: Sender: owner-freebsd-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk "Steven Fletcher (Shellnet IRC administrator)" wrote: > I need some help on compiling a kernel with 1024 file descriptor > blocks .... which I have little idead on how to do. First, you should realize the actual number is a resource limit. See the `limit' (csh) or `ulimit' (sh) shell builtins for documentation. My current limits look like: j@uriah 439% limit -h descriptors descriptors 680 (That's the `hard' limit.) This number is NPROC*2, with NPROC being computed in /sys/conf/param.c as 20 + 16 * MAXUSERS. So basically, by bumping `maxusers' (in your kernel config file) to (1024 / 2 - 20) / 16 (= 30.75 :-), you'd get a default of 1024. Actually, you can change it at runtime using sysctl, it's the sysctl variable kern.maxfilesperproc (you probably want kern.maxfiles to be larger then). Thus, no kernel recompilation needed. (Disclaimer: i don't know offhand when this tunable variable has been introduced, so it depends on your FreeBSD version.) -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-current Tue Dec 9 16:25:52 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id QAA22244 for current-outgoing; Tue, 9 Dec 1997 16:25:52 -0800 (PST) (envelope-from owner-freebsd-current) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id QAA22200 for ; Tue, 9 Dec 1997 16:25:32 -0800 (PST) (envelope-from j@uriah.heep.sax.de) Received: (from uucp@localhost) by sax.sax.de (8.8.8/8.8.8) with UUCP id BAA01859 for freebsd-current@freebsd.org; Wed, 10 Dec 1997 01:25:08 +0100 (CET) (envelope-from j@uriah.heep.sax.de) Received: (from j@localhost) by uriah.heep.sax.de (8.8.8/8.8.5) id AAA04681; Wed, 10 Dec 1997 00:09:44 +0100 (MET) Date: Wed, 10 Dec 1997 00:09:44 +0100 (MET) Message-Id: <199712092309.AAA04681@uriah.heep.sax.de> Mime-Version: 1.0 X-Newsreader: knews 0.9.8 Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) Organization: Private BSD site, Dresden X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E References: <199712071829.NAA03407@dyson.iquest.net> <867m9gpsts.fsf@bitbox.follo.net> In-Reply-To: <867m9gpsts.fsf@bitbox.follo.net> From: j@uriah.heep.sax.de (J Wunsch) Subject: Re: VM system info X-Original-Newsgroups: local.freebsd.current To: freebsd-current@freebsd.org Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Eivind Eklund wrote: > I'm going to be extremely politically incorrect here: > > I want this info in the kernel. At the very least, I want > documentation as a part of the SYSCTL_*() macro parameters, unused but > available as a (mandatory) part of the source - better would be as a > part of the kernel that can be compiled away by setting a kernel > option (e.g. NO_SYSCTL_DOCS). ``A section in an ELF file. A section in an ELF file.'' :-) -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-current Tue Dec 9 16:26:32 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id QAA22347 for current-outgoing; Tue, 9 Dec 1997 16:26:32 -0800 (PST) (envelope-from owner-freebsd-current) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id QAA22322 for ; Tue, 9 Dec 1997 16:26:25 -0800 (PST) (envelope-from j@uriah.heep.sax.de) Received: (from uucp@localhost) by sax.sax.de (8.8.8/8.8.8) with UUCP id BAA01870 for freebsd-current@freebsd.org; Wed, 10 Dec 1997 01:26:08 +0100 (CET) (envelope-from j@uriah.heep.sax.de) Received: (from j@localhost) by uriah.heep.sax.de (8.8.8/8.8.5) id AAA04697; Wed, 10 Dec 1997 00:14:11 +0100 (MET) Date: Wed, 10 Dec 1997 00:14:11 +0100 (MET) Message-Id: <199712092314.AAA04697@uriah.heep.sax.de> Mime-Version: 1.0 X-Newsreader: knews 0.9.8 Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) Organization: Private BSD site, Dresden X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E References: From: j@uriah.heep.sax.de (J Wunsch) Subject: Re: npx problem configing in -current X-Original-Newsgroups: local.freebsd.current To: freebsd-current@freebsd.org Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk (Why did you followup to a totally unrelated mail, btw.? This confuses the heck out of threading newsreaders, or mail->news gateways.) "Jamil J. Weatherbee" wrote: > # config TROJANHORSE > Removing old directory ../../compile/TROJANHORSE: Done. > files.i386: i386/isa/npx.c must be optional or standard In case of doubt, rebuild and rerun config(8) first. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-current Tue Dec 9 16:53:59 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id QAA24693 for current-outgoing; Tue, 9 Dec 1997 16:53:59 -0800 (PST) (envelope-from owner-freebsd-current) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id QAA24683 for ; Tue, 9 Dec 1997 16:53:50 -0800 (PST) (envelope-from j@uriah.heep.sax.de) Received: (from uucp@localhost) by sax.sax.de (8.8.8/8.8.8) with UUCP id BAA02388; Wed, 10 Dec 1997 01:53:29 +0100 (CET) (envelope-from j@uriah.heep.sax.de) Received: (from j@localhost) by uriah.heep.sax.de (8.8.8/8.8.5) id BAA05167; Wed, 10 Dec 1997 01:42:15 +0100 (MET) Date: Wed, 10 Dec 1997 01:42:15 +0100 (MET) Message-Id: <199712100042.BAA05167@uriah.heep.sax.de> Mime-Version: 1.0 X-Newsreader: knews 0.9.8 Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) Organization: Private BSD site, Dresden X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E References: <199712092246.RAA24863@limbo.rtfm.net> In-Reply-To: <199712092246.RAA24863@limbo.rtfm.net> From: j@uriah.heep.sax.de (J Wunsch) Subject: Re: files.i386, npx mandatory, config problem? X-Original-Newsgroups: local.freebsd.current To: freebsd-current@freebsd.org Cc: Nathan Dorfman Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Nathan Dorfman wrote: > Latest cvsup (22:30 GMT, Tue Dec 9) has given me a small problem in > kernel configuration. /usr/sbin/config LIMBO now prints an error: > files.i386: npx must be either optional or standard Rule #1: Follow the -current list. Rule #2: When in doubt, rebuild config(8), and re-run it on your config file. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-current Tue Dec 9 17:04:42 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id RAA25516 for current-outgoing; Tue, 9 Dec 1997 17:04:42 -0800 (PST) (envelope-from owner-freebsd-current) Received: from send1a.yahoomail.com (send1a.yahoomail.com [205.180.60.22]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id RAA25498 for ; Tue, 9 Dec 1997 17:04:20 -0800 (PST) (envelope-from osiris2002@yahoo.com) Message-ID: <19971210010404.13018.rocketmail@send1a.yahoomail.com> Received: from [194.79.98.71] by send1a; Tue, 09 Dec 1997 17:04:03 PST Date: Tue, 9 Dec 1997 17:04:03 -0800 (PST) From: Charlie Roots Subject: FreeBSD-3.0 Current - utmp To: freebsd-current@freebsd.org Cc: root@isis.dynip.com MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi everybody, I understand that freebsd 3.0 allows usernames to be 16 instead of 8, and this is defined in the include files, and there's a converter utility in the tools directory of the cvsup. I have used this utility to convert older files, now the problem that I have a third-party daemon called 'idled' which as its name implies automatically logs off any idle user or process after certain time, it uses utmp files, and is now unable to read the utmp files and giving enormous amount of logging saying 'Error can't read utmp file' repeatedly, I have recompiled the daemon and changed the definition of USERNAME 16 instead of 8 in its include files, the problem persists, although it successfully logs off any idle user. please help. The second issue is that I am having an error saying; 'gzip : broken pipe' when I am rebuilding the WHATIS database, I tried to manage the man pages manually, no solution, this problem also breaks the 'make world' in its final stages, please help. Thanks everyone. MAY THE FORCE BE WITH YOU. _________________________________________________________ DO YOU YAHOO!? Get your free @yahoo.com address at http://mail.yahoo.com From owner-freebsd-current Tue Dec 9 17:11:01 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id RAA26284 for current-outgoing; Tue, 9 Dec 1997 17:11:01 -0800 (PST) (envelope-from owner-freebsd-current) Received: from acroal.com (firewall0.acroal.com [209.24.61.154]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id RAA26271 for ; Tue, 9 Dec 1997 17:10:54 -0800 (PST) (envelope-from jamil@acroal.com) Received: from localhost (jamil@localhost) by acroal.com (8.8.8/8.8.7) with SMTP id RAA14469; Tue, 9 Dec 1997 17:10:41 -0800 (PST) (envelope-from jamil@acroal.com) Date: Tue, 9 Dec 1997 17:10:41 -0800 (PST) From: "J. Weatherbee - Senior Systems Architect" To: Nathan Dorfman cc: freebsd-current@freebsd.org Subject: Re: files.i386, npx mandatory, config problem? In-Reply-To: <199712092246.RAA24863@limbo.rtfm.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Yes you need to make world first before building your kernel. On Tue, 9 Dec 1997, Nathan Dorfman wrote: > Latest cvsup (22:30 GMT, Tue Dec 9) has given me a small problem in > kernel configuration. /usr/sbin/config LIMBO now prints an error: > files.i386: npx must be either optional or standard > > The config and subsequent compile works fine if I change npx to > standard. The compile worked before the cvsup (which was 971022-SNAP) > worked fine. I haven't made world, it was the cvsup alone that > started these problems. Obi-Wan cvsuped at the same time and got > no problems; it isn't my configuration since config on GENERIC returns > the same error. > > Any ideas? > From owner-freebsd-current Tue Dec 9 18:19:37 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id SAA02123 for current-outgoing; Tue, 9 Dec 1997 18:19:37 -0800 (PST) (envelope-from owner-freebsd-current) Received: from awfulhak.demon.co.uk (awfulhak.demon.co.uk [158.152.17.1]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id SAA02083 for ; Tue, 9 Dec 1997 18:19:06 -0800 (PST) (envelope-from brian@awfulhak.org) Received: from gate.lan.awfulhak.org (localhost [127.0.0.1]) by awfulhak.demon.co.uk (8.8.7/8.8.7) with ESMTP id CAA06985; Wed, 10 Dec 1997 02:17:33 GMT (envelope-from brian@gate.lan.awfulhak.org) Message-Id: <199712100217.CAA06985@awfulhak.demon.co.uk> X-Mailer: exmh version 2.0zeta 7/24/97 To: Ari Suutari cc: current@freebsd.org Subject: Re: 3.0 -release ? In-reply-to: Your message of "Mon, 08 Dec 1997 09:21:41 +0200." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 10 Dec 1997 02:17:32 +0000 From: Brian Somers Sender: owner-freebsd-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > On Sat, 6 Dec 1997, Brian Somers wrote: > > > > > For the time being, I've put back the htons() :-/ As you say, this > > code ain't portable. Our original number goes from a,b,c,d to > > b,a,0,0 and then gets coerced into a u_short.... two wrongs make a > > right :-O > > > > I have made the corrections to natd 1.11 and placed > it to ftp://ftp.suutari.iki.fi/pub/natd. I hope Brian > will put them into -current ? Done. Thanks. > Ari > Lappeenranta, Finland -- Brian , , Don't _EVER_ lose your sense of humour.... From owner-freebsd-current Tue Dec 9 18:25:42 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id SAA02650 for current-outgoing; Tue, 9 Dec 1997 18:25:42 -0800 (PST) (envelope-from owner-freebsd-current) Received: from send1a.yahoomail.com (send1a.yahoomail.com [205.180.60.22]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id SAA02639 for ; Tue, 9 Dec 1997 18:25:32 -0800 (PST) (envelope-from osiris2002@yahoo.com) Message-ID: <19971210022515.15414.rocketmail@send1a.yahoomail.com> Received: from [194.79.98.71] by send1a; Tue, 09 Dec 1997 18:25:15 PST Date: Tue, 9 Dec 1997 18:25:15 -0800 (PST) From: Charlie Roots Subject: Re: files.i386, npx mandatory, config problem? To: Joerg Wunsch Cc: freebsd-current@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk This problem is evidently causing much trouble for many people who use cvsup to be current, so its current afterall. That's why I suggested to Dough White in the past few days that the config kernel should have a technique to check for discrapencies between the version of config and the system being rebuilt, and gives a stub message telling the user to make world first, this also includes rebuilding new config, before attempting to compile a new kernel, but he just LAUGHED in my face for that suggestion, I still remember not so far ago reading; This Program Requires Microsoft Windows. come on guys, make the users feel the power of the system from the first touch. MAY THE FORCE BE WITH you. ---J Wunsch wrote: > > Nathan Dorfman wrote: > > > Latest cvsup (22:30 GMT, Tue Dec 9) has given me a small problem in > > kernel configuration. /usr/sbin/config LIMBO now prints an error: > > files.i386: npx must be either optional or standard > > Rule #1: Follow the -current list. > Rule #2: When in doubt, rebuild config(8), and re-run it on your > config file. > > -- > cheers, J"org > > joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE > Never trust an operating system you don't have sources for. ;-) > _________________________________________________________ DO YOU YAHOO!? Get your free @yahoo.com address at http://mail.yahoo.com From owner-freebsd-current Tue Dec 9 19:15:44 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id TAA06793 for current-outgoing; Tue, 9 Dec 1997 19:15:44 -0800 (PST) (envelope-from owner-freebsd-current) Received: from zippy.dyn.ml.org (spain-7.ppp.hooked.net [206.169.228.7]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id TAA06751 for ; Tue, 9 Dec 1997 19:15:20 -0800 (PST) (envelope-from garbanzo@hooked.net) Received: from localhost (garbanzo@localhost) by zippy.dyn.ml.org (8.8.8/8.8.7) with SMTP id TAA00496; Tue, 9 Dec 1997 19:15:07 -0800 (PST) X-Authentication-Warning: zippy.dyn.ml.org: garbanzo owned process doing -bs Date: Tue, 9 Dec 1997 19:15:07 -0800 (PST) From: Alex X-Sender: garbanzo@zippy.dyn.ml.org To: Dayton Clark cc: smp@csn.net, current@freebsd.org Subject: Re: 8CPUs In-Reply-To: <199712092225.RAA18006@sci.brooklyn.cuny.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Tue, 9 Dec 1997, Dayton Clark wrote: > > IBM has advertised an 8 cpu server for several years. I was never able to > get anyone to give me a quote though. There is a French organization (or > company) that implemented a multi-pentium connection scheme. I think it > is called the CBUS. As I remember, it's an interesting system, but totally > incompatible with the Intel MP stuff. > > dayton > Alex> Speaking of more CPUs, did anyone catch the release of > Alex> HP's newest SMP server? An 8 CPU (I'm assuming PPro) *drool*. > Alex> I'm assuming it comes with gobs of ram and disk space, and it > Alex> amusingly enough looked like an overgrown dot-matrix printer with > Alex> no paper. I didn't realize there were production machines with > Alex> more than 4 Intel CPUs *drool*. This advertised system was compatable with some form of Intel SMP as it ran *gag* NT. Imagine if FreeBSD could run on that sucker. - alex From owner-freebsd-current Tue Dec 9 19:16:03 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id TAA06856 for current-outgoing; Tue, 9 Dec 1997 19:16:03 -0800 (PST) (envelope-from owner-freebsd-current) Received: from mail.cdsnet.net (mail.cdsnet.net [204.118.244.5]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id TAA06599; Tue, 9 Dec 1997 19:13:31 -0800 (PST) (envelope-from mrcpu@cdsnet.net) Received: from mail.cdsnet.net (mail.cdsnet.net [204.118.244.5]) by mail.cdsnet.net (8.8.6/8.8.6) with SMTP id TAA22553; Tue, 9 Dec 1997 19:13:21 -0800 (PST) Date: Tue, 9 Dec 1997 19:13:20 -0800 (PST) From: Jaye Mathisen To: Steve Passe cc: current@FreeBSD.ORG, smp@FreeBSD.ORG Subject: Re: -current, goliath, smp -- problems In-Reply-To: <199712082346.QAA13842@Ilsa.StevesCafe.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Mon, 8 Dec 1997, Steve Passe wrote: > I'm at a loss about the other 2 problems. They may be related to 4 CPUs, > but I have been TOTALLY unsuccessful in getting access to a 4 CPU > machine for testing. Show of hands, anyone successfully running SMP on 4 > or more CPUs? I will have a 4 processor DEC P6-200 box in my hands in appx 2 more days, you're welcome to bash on it then. It has 3CPU's in it now, and the 4th will be installed soon. (I haven't installed FreeBSD on it yet, which is tonights project). From owner-freebsd-current Tue Dec 9 19:37:05 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id TAA08462 for current-outgoing; Tue, 9 Dec 1997 19:37:05 -0800 (PST) (envelope-from owner-freebsd-current) Received: from smtp03.primenet.com (smtp03.primenet.com [206.165.6.133]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id TAA08451 for ; Tue, 9 Dec 1997 19:36:52 -0800 (PST) (envelope-from tlambert@usr06.primenet.com) Received: (from daemon@localhost) by smtp03.primenet.com (8.8.8/8.8.8) id UAA14744; Tue, 9 Dec 1997 20:51:55 -0700 (MST) Received: from usr06.primenet.com(206.165.6.206) via SMTP by smtp03.primenet.com, id smtpd014671; Tue Dec 9 20:51:42 1997 Received: (from tlambert@localhost) by usr06.primenet.com (8.8.5/8.8.5) id UAA06192; Tue, 9 Dec 1997 20:36:05 -0700 (MST) From: Terry Lambert Message-Id: <199712100336.UAA06192@usr06.primenet.com> Subject: Re: VM system info To: henrich@crh.cl.msu.edu (Charles Henrich) Date: Wed, 10 Dec 1997 03:36:05 +0000 (GMT) Cc: perhaps@yes.no, freebsd-current@freebsd.org In-Reply-To: <199712091643.LAA04851@crh.cl.msu.edu> from "Charles Henrich" at Dec 9, 97 11:43:31 am X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-freebsd-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > >(5) Code prerequisites is documented through assert() or similar > > functionality. > > Egads! I wish assert() was thrown down to the pits of hell. Its a > programmers cop out. In almost no circumstance does one ever need to assert. > If you find an error condition, COPE as best you can! Especially in the > kernel. The function of an assert() is not to live in production code. The function of assert() is to provide developers with feedback about improper use of function interfaces. This lets functions document expectations on the way in, and, if you correctly implement single-entry/single-exit like you should, on the way out as well. A good example would be functions with locking side-effects. Like those involved in causeing the "free vnode isn't" bug we are all so fond of, but for which the code is a sacred cow and so it's never been fixed. Knowing that a lock that was supposed to be held is not held as expected, or is held when it is not expected to be held, in combination with a branch-patch validation to exercise all code paths can result in early and easy identification and correction of bugs. Right now, there is an obvious error in VOP_LOCK()'s interaction with vclean() and associated functions (for example), resulting in the "free vnode isn't" bug described above. This is only going to get worse in the SMP kernel, and in the UP kernel, assuming we allow for kernel preemption for use in supporting things like kernel threads and kernel processes. So it's not an SMP only problem. Topologically, other than the names for the primitives, Kernel preemption for RT support is equivalent to kernel preemption for kernel threading support is equivalent to kernel reeentrancy for SMP. I can't see SMP progressing to discrete locking with any reasonable guarantess against deadlock or inversion bugs without this type of assurance. In production code, and assert becomes a comment, and is not even compiled into the code. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-current Tue Dec 9 19:43:23 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id TAA09015 for current-outgoing; Tue, 9 Dec 1997 19:43:23 -0800 (PST) (envelope-from owner-freebsd-current) Received: from word.smith.net.au (vh1.gsoft.com.au [203.38.152.122]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id TAA08990 for ; Tue, 9 Dec 1997 19:43:06 -0800 (PST) (envelope-from mike@word.smith.net.au) Received: from word (localhost [127.0.0.1]) by word.smith.net.au (8.8.8/8.8.5) with ESMTP id OAA01369; Wed, 10 Dec 1997 14:06:54 +1030 (CST) Message-Id: <199712100336.OAA01369@word.smith.net.au> X-Mailer: exmh version 2.0zeta 7/24/97 To: Charlie Roots cc: Joerg Wunsch , freebsd-current@freebsd.org Subject: Re: files.i386, npx mandatory, config problem? In-reply-to: Your message of "Tue, 09 Dec 1997 18:25:15 -0800." <19971210022515.15414.rocketmail@send1a.yahoomail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 10 Dec 1997 14:06:53 +1030 From: Mike Smith Sender: owner-freebsd-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > This problem is evidently causing much trouble for many people who use > cvsup to be current, so its current afterall. No, it's the people *using* current. Note that none of the "regulars" are complaining. Does this tell you something> > That's why I suggested > to Dough White in the past few days that the config kernel should have > a technique to check for discrapencies between the version of config > and the system being rebuilt, and gives a stub message telling the > user to make world first, this also includes rebuilding new config, > before attempting to compile a new kernel, but he just LAUGHED in my > face for that suggestion, Probably because it was implemented ages ago. If your config(8) doesn't bitch about being out of sync with your kernel sources, then it's either up to date or too old. I'll send you a copy of 'Staying -current with FreeBSD' off the list. Anyone else wants a copy, please ask. mike From owner-freebsd-current Tue Dec 9 19:43:56 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id TAA09067 for current-outgoing; Tue, 9 Dec 1997 19:43:56 -0800 (PST) (envelope-from owner-freebsd-current) Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id TAA09040; Tue, 9 Dec 1997 19:43:43 -0800 (PST) (envelope-from jkh@time.cdrom.com) Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.7/8.6.9) with ESMTP id TAA18900; Tue, 9 Dec 1997 19:43:35 -0800 (PST) To: Steve Passe cc: smp@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: Usable SMP on 971208 In-reply-to: Your message of "Tue, 09 Dec 1997 13:23:51 MST." <199712092023.NAA17839@Ilsa.StevesCafe.com> Date: Tue, 09 Dec 1997 19:43:35 -0800 Message-ID: <18896.881725415@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > It would appear that December 8, 1997 is a good date for which to grab SMP > source. Yep! Which is why I downloaded a copy of that snapshot onto ftp.freebsd.org for easier installation a day ago (great minds think alike :-). Jordan From owner-freebsd-current Tue Dec 9 19:55:44 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id TAA09862 for current-outgoing; Tue, 9 Dec 1997 19:55:44 -0800 (PST) (envelope-from owner-freebsd-current) Received: from smtp01.primenet.com (smtp01.primenet.com [206.165.6.131]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id TAA09847 for ; Tue, 9 Dec 1997 19:55:31 -0800 (PST) (envelope-from tlambert@usr06.primenet.com) Received: (from daemon@localhost) by smtp01.primenet.com (8.8.8/8.8.8) id UAA26571; Tue, 9 Dec 1997 20:54:59 -0700 (MST) Received: from usr06.primenet.com(206.165.6.206) via SMTP by smtp01.primenet.com, id smtpd026546; Tue Dec 9 20:54:54 1997 Received: (from tlambert@localhost) by usr06.primenet.com (8.8.5/8.8.5) id UAA07489; Tue, 9 Dec 1997 20:54:50 -0700 (MST) From: Terry Lambert Message-Id: <199712100354.UAA07489@usr06.primenet.com> Subject: Re: VM system info To: henrich@crh.cl.msu.edu (Charles Henrich) Date: Wed, 10 Dec 1997 03:54:50 +0000 (GMT) Cc: eivind@yes.no, perhaps@yes.no, freebsd-current@freebsd.org In-Reply-To: <19971209145549.60899@crh.cl.msu.edu> from "Charles Henrich" at Dec 9, 97 02:55:49 pm X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-freebsd-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > There are four ways to cope: (1) Ignore error; return OK, even though the > > function failed to do it's job. (2) Return error code (3) Throw an > > exception of some sort, e.g. longjmp(). (4) panic(), a la assert(). > > That depends greatly on the situation. There is also a (5) that says > take all given known information and continue onward, while logging > the error. In some cases its obviously not possible where a routine > is designed to have no return value. [ ... ] > Im not arguing the trap all errors as soon as possible piece, im arguing in > what you do when you detect one. To shutdown the machine is the worst > solution. I've recently identified (but not isolated a bug in the FreeBSD network code that can apparently spam the kernel stack of anyprocess currently in the kernel. I have yet to track this down because all I can see is the side effect, not the effect that results in the spamming. Another engineer has identified the most probably place that the spam occurred, simply because there's no place else that even looks vaguely like it could result in what I'm seeing: o In select(), selscan() got a page not present error when accessing obits[ 0]. This is not an error I can "ignore and log". The select() was initiated by syslogd for input on its TCP (fd=3) and UDP (fd=4) ports. o Apparently, something is spamming the contents of the kernel stack. You can see this by going into kdb and examining the *ibits[3], *obits[3]; atv values and noting something that looks like a sockaddr with the following attributes: o A sa_len of 0x20 o A sa_family of 0xff o The MAC addr of a remote machine o The MAC addr of the local machine o A protocol value of 0800 (TCP) o There is (apparently) only one place in the kernel (a dereference of *eh members, where eh is an mdata(m...) of an mbuf) where this data could have originated. The only fruitful approach is to check for a *eh < 0xf0000000. With an assert with a panic to stop the processor earlier in the problem. This particular problem could result in random "non-fatal" corruption of data in *your* kernel. It's probably responsible for many "impossible" situation type crashes (hint: random kernel stack stomping of a victim processes stack is not a good thing). If you can think of a way *other* than an assert to find this problem, I'm open to suggestions. > Lets think for a moment about the case if your the computer system > on a F-15 fighter jet, the last thing the pilot wants to see is > "Panic, system halted" as he spirals to his death instead of the > software attempting to cope as best as possible. Probably he would be less happy with "missle launched" as he's landing on a friendly aircraft carrier because of some cascade failure. BTW, to handle: You do a fast reset from ROM and hope the error doesn't occur again. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-current Tue Dec 9 19:59:49 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id TAA10166 for current-outgoing; Tue, 9 Dec 1997 19:59:49 -0800 (PST) (envelope-from owner-freebsd-current) Received: from smtp03.primenet.com (smtp03.primenet.com [206.165.6.133]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id TAA10161 for ; Tue, 9 Dec 1997 19:59:42 -0800 (PST) (envelope-from tlambert@usr06.primenet.com) Received: (from daemon@localhost) by smtp03.primenet.com (8.8.8/8.8.8) id VAA22690; Tue, 9 Dec 1997 21:14:14 -0700 (MST) Received: from usr06.primenet.com(206.165.6.206) via SMTP by smtp03.primenet.com, id smtpd022607; Tue Dec 9 21:14:03 1997 Received: (from tlambert@localhost) by usr06.primenet.com (8.8.5/8.8.5) id UAA07787; Tue, 9 Dec 1997 20:58:22 -0700 (MST) From: Terry Lambert Message-Id: <199712100358.UAA07787@usr06.primenet.com> Subject: Re: files.i386, npx mandatory, config problem? To: osiris2002@yahoo.com (Charlie Roots) Date: Wed, 10 Dec 1997 03:58:22 +0000 (GMT) Cc: joerg_wunsch@uriah.heep.sax.de, freebsd-current@freebsd.org, sef@kithrup.com In-Reply-To: <19971210022515.15414.rocketmail@send1a.yahoomail.com> from "Charlie Roots" at Dec 9, 97 06:25:15 pm X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-freebsd-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > This Program Requires Microsoft Windows. Heh. Any chance of a kernel printf() of this when someone attempts to exercise the f00f bug? 8-) 8-). Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-current Tue Dec 9 20:32:04 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id UAA13028 for current-outgoing; Tue, 9 Dec 1997 20:32:04 -0800 (PST) (envelope-from owner-freebsd-current) Received: from mail.san.rr.com (san.rr.com [204.210.0.1]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id UAA12984 for ; Tue, 9 Dec 1997 20:31:49 -0800 (PST) (envelope-from studded@san.rr.com) Received: (from studded@localhost) by mail.san.rr.com (8.8.7/8.8.7) id UAA12373; Tue, 9 Dec 1997 20:32:56 -0800 (PST) Message-Id: <199712100432.UAA12373@mail.san.rr.com> From: "Studded" To: "Charlie Roots" , "freebsd-current@FreeBSD.ORG" Cc: "root@isis.dynip.com" Date: Tue, 09 Dec 97 20:30:47 -0800 Reply-To: "Studded" Priority: Normal X-Mailer: PMMail 1.95a For OS/2 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Subject: Re: FreeBSD-3.0 Current - utmp Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Tue, 9 Dec 1997 17:04:03 -0800 (PST), Charlie Roots wrote: >to convert older files, now the problem that I have a third-party >daemon called 'idled' which as its name implies automatically logs off >any idle user or process after certain time, it uses utmp files, and >is now unable to read the utmp files and giving enormous amount of >logging saying 'Error can't read utmp file' repeatedly, > >I have recompiled the daemon and changed the definition of USERNAME 16 >instead of 8 in its include files, the problem persists, although it >successfully logs off any idle user. please help. FWIW, I've been running -Stable with 16 char usernames, and I appear to be getting some corruption in utmp. When I do 'last' it shows my 16 char name, but it also shows some weird high ascii characters. I deleted utmp and wtmp, and still have the same problems. Wish I could help more, but at least you're not alone. :) Doug *** Proud operator, designer and maintainer of the world's largest *** Internet Relay Chat server. 4,297 clients and still growing. :-) *** Try spider.dal.net on ports 6662-4 (Powered by FreeBSD) *** Part of the DALnet IRC network *** From owner-freebsd-current Tue Dec 9 20:35:03 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id UAA13305 for current-outgoing; Tue, 9 Dec 1997 20:35:03 -0800 (PST) (envelope-from owner-freebsd-current) Received: from home.dragondata.com (toasty@home.dragondata.com [204.137.237.2]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id UAA13291 for ; Tue, 9 Dec 1997 20:34:54 -0800 (PST) (envelope-from toasty@home.dragondata.com) Received: (from toasty@localhost) by home.dragondata.com (8.8.5/8.8.5) id WAA20572 for freebsd-current@freebsd.org; Tue, 9 Dec 1997 22:34:50 -0600 (CST) From: Kevin Day Message-Id: <199712100434.WAA20572@home.dragondata.com> Subject: 971208 and the nfs rollback didn't fix it... To: freebsd-current@freebsd.org Date: Tue, 9 Dec 1997 22:34:50 -0600 (CST) X-Mailer: ELM [version 2.4ME+ PL31 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I grabbed everything on 971208, hoping it would cure my nfs problems... It didn't. :) I still will see on my console: shell syslogd: sendto: no buffer space available Which is my first symptom that i'm going to have to reboot... Any attempt to read a file on an nfs system will completely hang the process. (kill -9 doesn't even get rid of it). 3028 mbufs in use: 2111 mbufs allocated to data 304 mbufs allocated to packet headers 11 mbufs allocated to protocol control blocks 2 mbufs allocated to socket names and addresses 554/1392 mbuf clusters in use 8694 Kbytes allocated to network (97% in use) 0 requests for memory denied 0 requests for memory delayed 0 calls to protocol drain routines A reboot advises me that not all processes died, check ps axl, then it locks up. This system is a dual P/200, acting as an nfs client.... Both machines(this client, and a 2.2.1 server) get random 'nfsd send error 55's on them... Is this news to anyone? Kevin From owner-freebsd-current Tue Dec 9 21:40:20 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id VAA18015 for current-outgoing; Tue, 9 Dec 1997 21:40:20 -0800 (PST) (envelope-from owner-freebsd-current) Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id VAA18008 for ; Tue, 9 Dec 1997 21:40:13 -0800 (PST) (envelope-from jkh@time.cdrom.com) Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.7/8.6.9) with ESMTP id VAA19624; Tue, 9 Dec 1997 21:40:02 -0800 (PST) To: "Studded" cc: "Charlie Roots" , "freebsd-current@FreeBSD.ORG" , "root@isis.dynip.com" Subject: Re: FreeBSD-3.0 Current - utmp In-reply-to: Your message of "Tue, 09 Dec 1997 20:30:47 PST." <199712100432.UAA12373@mail.san.rr.com> Date: Tue, 09 Dec 1997 21:40:02 -0800 Message-ID: <19619.881732402@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > FWIW, I've been running -Stable with 16 char usernames, and I > appear to be getting some corruption in utmp. When I do 'last' it shows > my 16 char name, but it also shows some weird high ascii characters. I > deleted utmp and wtmp, and still have the same problems. You sure you recompiled *everything* in -stable with 16 character usernames? I've seen people get bitten by both sshd and xterm, forgetting that these optional packages also write utmp entries. :) Jordan From owner-freebsd-current Tue Dec 9 21:54:30 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id VAA18615 for current-outgoing; Tue, 9 Dec 1997 21:54:30 -0800 (PST) (envelope-from owner-freebsd-current) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id VAA18600 for ; Tue, 9 Dec 1997 21:54:20 -0800 (PST) (envelope-from bde@zeta.org.au) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.7/8.6.9) id QAA08722; Wed, 10 Dec 1997 16:45:06 +1100 Date: Wed, 10 Dec 1997 16:45:06 +1100 From: Bruce Evans Message-Id: <199712100545.QAA08722@godzilla.zeta.org.au> To: gemohler@tgn2.tgn.net, phk@critter.freebsd.dk Subject: Re: Namei cache? Cc: current@freebsd.org Sender: owner-freebsd-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >>> In current there is little you can do. >>> >>> You can try to increase: >>> >>> kern.maxvnodes >>> debug.wantfreevnodes >> >>I see what these values currently are, but what are my boundaries and >>rules I have to follow in changing them..IE: stay in 4096 >>incrememnts..dont go above 99999...etc. > >You'll run out of memory if you set them too high... > >Add 10% or so at a a time, let it run for a day before you judge >the result... In current there is little you can do. Setting kern.maxvnodes has no effect unless debug.wantvnodes is set to 0. Setting debug.wantvnodes to 0 just gives kern.maxvnodes the old function of debug.wantvnodes. Setting debug.wantvnodes has very little effect. It just controls how fast the system ramps up to peak vnode allocation. This is bogus of course. The man page is more bogus/incomplete. Bruce From owner-freebsd-current Tue Dec 9 23:22:24 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id XAA24217 for current-outgoing; Tue, 9 Dec 1997 23:22:24 -0800 (PST) (envelope-from owner-freebsd-current) Received: from paladio.canonware.com (canonware.com [206.184.206.112]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id XAA24207 for ; Tue, 9 Dec 1997 23:22:18 -0800 (PST) (envelope-from jasone@canonware.com) Received: from localhost (jasone@localhost) by paladio.canonware.com (8.8.5/8.8.5) with SMTP id XAA15132; Tue, 9 Dec 1997 23:22:20 -0800 Date: Tue, 9 Dec 1997 23:22:20 -0800 (PST) From: Jason Evans X-Sender: jasone@paladio To: Alex cc: Steve Passe , current Subject: Re: -current, goliath, smp -- problems In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Mon, 8 Dec 1997, Alex wrote: > Speaking of more CPUs, did anyone catch the release of HP's newest SMP > server? An 8 CPU (I'm assuming PPro) *drool*. I'm assuming it comes with > gobs of ram and disk space, and it amusingly enough looked like an > overgrown dot-matrix printer with no paper. I didn't realize there were > production machines with more than 4 Intel CPUs *drool*. Well, I don't know that I would necessarily expect this to be as cool as it sounds. I'm not an expert on this by any means, but I've repeatedly heard the following: Tightly coupled MP machines work well until memory bandwidth becomes a bottleneck. Last I heard, the memory bandwidth on Intel-based machines is in the neighborhood of 500 MB/sec, which is enough to feed 4 processors, but quite inadequate for 8. So, even though there are twice as many processors, the performance gain is not impressive. If there's anyone else out there that knows any better, please correct me. =) Jason Jason Evans Email: [jasone@canonware.com] Home phone: [(650) 856-8204] Quote: ["Invention is 1% inspiration, 99% perspiration" - Thomas Edison] From owner-freebsd-current Tue Dec 9 23:29:41 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id XAA24691 for current-outgoing; Tue, 9 Dec 1997 23:29:41 -0800 (PST) (envelope-from owner-freebsd-current) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id XAA24683 for ; Tue, 9 Dec 1997 23:29:30 -0800 (PST) (envelope-from bde@zeta.org.au) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.7/8.6.9) id SAA12673; Wed, 10 Dec 1997 18:25:27 +1100 Date: Wed, 10 Dec 1997 18:25:27 +1100 From: Bruce Evans Message-Id: <199712100725.SAA12673@godzilla.zeta.org.au> To: freebsd-current@FreeBSD.ORG, j@uriah.heep.sax.de Subject: Re: Bootloader/kernel ignores "-a" flag... Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >> -a only works with "config kernel swap on generic" in the >> kernel config file. This should be the default, but it breaks >> "root on ...". It has nothing to do with swap. > >What is the "root on ..." stuff required for in GENERIC? I'm So that booting -r gives wd0 :-). >Perhaps config's syntax rules should be changed so to allow > > config kernel generic > >instead. It should allow config kernel and swap*.c shouldn't exist. swapgeneric.c should be in autoconf.c and the two variables in the automatically generated swap*.c's (rootdev and dumpdev) should be in param.c (they can be configured using #defines). Bruce From owner-freebsd-current Tue Dec 9 23:40:45 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id XAA25520 for current-outgoing; Tue, 9 Dec 1997 23:40:45 -0800 (PST) (envelope-from owner-freebsd-current) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id XAA25509 for ; Tue, 9 Dec 1997 23:40:37 -0800 (PST) (envelope-from bde@zeta.org.au) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.7/8.6.9) id SAA12760; Wed, 10 Dec 1997 18:28:00 +1100 Date: Wed, 10 Dec 1997 18:28:00 +1100 From: Bruce Evans Message-Id: <199712100728.SAA12760@godzilla.zeta.org.au> To: freebsd-current@FreeBSD.ORG, j@uriah.heep.sax.de Subject: Re: VM system info Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >> I want this info in the kernel. At the very least, I want >> documentation as a part of the SYSCTL_*() macro parameters, unused but >``A section in an ELF file. A section in an ELF file.'' :-) ``A stab in an a.out file...'' :-) Bruce From owner-freebsd-current Wed Dec 10 00:02:09 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id AAA26701 for current-outgoing; Wed, 10 Dec 1997 00:02:09 -0800 (PST) (envelope-from owner-freebsd-current) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id AAA26696 for ; Wed, 10 Dec 1997 00:01:59 -0800 (PST) (envelope-from bde@zeta.org.au) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.7/8.6.9) id SAA13693; Wed, 10 Dec 1997 18:58:34 +1100 Date: Wed, 10 Dec 1997 18:58:34 +1100 From: Bruce Evans Message-Id: <199712100758.SAA13693@godzilla.zeta.org.au> To: freebsd-current@FreeBSD.ORG, j@uriah.heep.sax.de Subject: Re: Where can I get help ? Cc: ircadmin@shellnet.co.uk Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >My current limits look like: > >j@uriah 439% limit -h descriptors >descriptors 680 Using a real shell: $ limit -h descriptors limit: not found $ ulimit $ ulimit -Hn 360 >(That's the `hard' limit.) > >This number is NPROC*2, with NPROC being computed in /sys/conf/param.c >as 20 + 16 * MAXUSERS. So basically, by bumping `maxusers' (in your >kernel config file) to (1024 / 2 - 20) / 16 (= 30.75 :-), you'd get a >default of 1024. > >Actually, you can change it at runtime using sysctl, it's the sysctl >variable kern.maxfilesperproc (you probably want kern.maxfiles to be >larger then). Thus, no kernel recompilation needed. (Disclaimer: i Have you tried it? :-) It only works for login classes that set the hard limit (in the current login.conf, these are root (value infinity), daemon (1024), news (256) and dialer (32)). Everything else inherits the old hard limits from init. This is just one of the reasons why kern.maxfilesperproc should not exist. It only works to restrict (break) the limits advertised by getrlimit(). It just gets in the way of expanding the limits. >don't know offhand when this tunable variable has been introduced, so >it depends on your FreeBSD version.) kern.maxfiles was introduced in FreeBSD-2.0 (actually in 4.4BSD-Lite). kern.maxfilesperproc was introduced in FreeBSD-2.0.5 (kern_descrip.c rev.1.8 1995/02/20). It was broken (read-only) in -current between rev.1.19 (1995/12/04) and rev.1.32 (1996/09/28). It should have been removed when login classes were introduced. Login classes make it possible for increasing it to work (all classes just need to set a hard limit to pick up the new limit), but they also make it redundant. Bruce From owner-freebsd-current Wed Dec 10 00:51:30 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id AAA29304 for current-outgoing; Wed, 10 Dec 1997 00:51:30 -0800 (PST) (envelope-from owner-freebsd-current) Received: from isbalham.ist.co.uk (isbalham.ist.co.uk [192.31.26.1]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id AAA29294 for ; Wed, 10 Dec 1997 00:51:24 -0800 (PST) (envelope-from rb@gid.co.uk) Received: from gid.co.uk (uucp@localhost) by isbalham.ist.co.uk (8.8.7/8.8.4) with UUCP id IAA29708; Wed, 10 Dec 1997 08:34:59 GMT Received: from [194.32.164.2] by seagoon.gid.co.uk; Wed, 10 Dec 1997 08:17:08 GMT X-Sender: rb@194.32.164.1 Message-Id: In-Reply-To: <199712092225.RAA18006@sci.brooklyn.cuny.edu> References: (message from Alex on Mon, 8 Dec 1997 22:57:19 -0800 (PST)) Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Wed, 10 Dec 1997 08:15:54 +0000 To: Dayton Clark , garbanzo@hooked.net From: Bob Bishop Subject: Re: 8CPUs Cc: smp@csn.net, current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >>>>>> "Alex" == Alex writes: > > Alex>I didn't realize there were production machines with > Alex> more than 4 Intel CPUs *drool*. Sequent -- Bob Bishop (0118) 977 4017 international code +44 118 rb@gid.co.uk fax (0118) 989 4254 between 0800 and 1800 UK From owner-freebsd-current Wed Dec 10 03:01:06 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id DAA05671 for current-outgoing; Wed, 10 Dec 1997 03:01:06 -0800 (PST) (envelope-from owner-freebsd-current) Received: from ns.tesco-stores.cz (root@ns.tesco-stores.cz [194.228.14.253]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id DAA05660 for ; Wed, 10 Dec 1997 03:01:00 -0800 (PST) (envelope-from frf@crux.tesco-stores.cz) Received: from crux.tesco-stores.cz (crux.tesco-stores.cz [194.228.14.134]) by ns.tesco-stores.cz (8.8.2/8.8.2) with ESMTP id LAA10588 for ; Wed, 10 Dec 1997 11:54:51 +0100 Received: (from frf@localhost) by crux.tesco-stores.cz (8.8.8/8.8.7) id MAA05905 for freebsd-current@freebsd.org; Wed, 10 Dec 1997 12:00:53 +0100 (CET) From: frf Message-Id: <199712101100.MAA05905@crux.tesco-stores.cz> Subject: Which libtermcap is current? To: freebsd-current@freebsd.org Date: Wed, 10 Dec 1997 12:00:52 +0100 (CET) X-Mailer: ELM [version 2.4ME+ PL32 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I'm having a problem with buildworld. It seems usr.bin/top wants to depend on libtermcap.so.3.0. A quick look at the makefile for libtermcap includes a hack to work around this dependency. ===> usr.bin/top make: don't know how to make /usr/obj/usr/src/tmp/usr/lib/libtermcap.so.3.0. Stop *** Error code 2 $ less /usr/src/lib/libtermcap/Makefile # This is a hack.. Work around a major number bump that should have been # done differently. Back out this delta when it's time to go to 3.0 for real. .if !defined(NOPIC) LINKS+= ${SHLIBDIR}/libtermcap.so.${SHLIB_MAJOR}.${SHLIB_MINOR} \ /usr/lib/compat/libtermcap.so.3.0 LINKS+= ${SHLIBDIR}/libtermcap.so.${SHLIB_MAJOR}.${SHLIB_MINOR} \ /usr/lib/compat/libtermlib.so.3.0 .endif Anyone else seen this behavior? -- frf at xocolatl dot com frf at tesco dash stores dot cz Fortune's Office Door Sign of the Week: Incorrigible punster -- Do not incorrige. From owner-freebsd-current Wed Dec 10 03:40:29 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id DAA07990 for current-outgoing; Wed, 10 Dec 1997 03:40:29 -0800 (PST) (envelope-from owner-freebsd-current) Received: from pi-caninde.telepisa.net.br ([200.241.133.2]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id DAA07980 for ; Wed, 10 Dec 1997 03:40:23 -0800 (PST) (envelope-from andreas@telepisa.net.br) Received: from pi-desenv04.frei-serafim.telepisa.net.br by pi-caninde.telepisa.net.br (Lotus SMTP MTA v1.05 (274.9 11-27-1996)) with SMTP id 03256569.004099A5; Wed, 10 Dec 1997 08:45:36 -0300 Reply-To: "Andreas Friedrich Berendsen" From: "Andreas Friedrich Berendsen" To: Date: Wed, 10 Dec 1997 08:36:04 -0200 Message-ID: <01bd0557$6b1258a0$7b08560a@pi-desenv04.frei-serafim.telepisa.net.br> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 4.71.1712.3 X-MimeOLE: Produced By Microsoft MimeOLE V4.71.1712.3 Sender: owner-freebsd-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk help From owner-freebsd-current Wed Dec 10 05:30:01 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id FAA12537 for current-outgoing; Wed, 10 Dec 1997 05:30:01 -0800 (PST) (envelope-from owner-freebsd-current) Received: from fax.ceniai.inf.cu (fax.ceniai.inf.cu [169.158.128.146]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id FAA12495 for ; Wed, 10 Dec 1997 05:29:44 -0800 (PST) (envelope-from ogaspar@tinored.cu) Received: from ceniai.inf.cu by fax.ceniai.inf.cu with esmtp (Smail3.2) id m0xfmCX-000M4uC; Wed, 10 Dec 1997 08:29:21 -0500 (CST) Received: from by ceniai.inf.cu with bsmtp (Smail3.2) id m0xfmFg-000AtmC; Wed, 10 Dec 1997 08:32:36 -0500 (CST) Received: from tinored by gateway with smtp (Smail3.1.28.1 #7) id m0xflpE-0005UjC; Wed, 10 Dec 97 08:05 EST Received: by tinored (Smail3.1.28.1 #24) id m0xflnf-0001M9C; Wed, 10 Dec 97 08:03 EST Message-Id: From: ogaspar@tinored.cu (Omar Gaspar Navarro) To: freebsd-current@freebsd.org Date: Wed, 10 Dec 1997 08:03:38 -0500 (EST) X-Mailer: CARIBE [version 3.0] Content-Type: text Sender: owner-freebsd-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk unsubscribe ogaspar@tinored.cu From owner-freebsd-current Wed Dec 10 06:21:01 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id GAA15981 for current-outgoing; Wed, 10 Dec 1997 06:21:01 -0800 (PST) (envelope-from owner-freebsd-current) Received: from Kitten.mcs.com (Kitten.mcs.com [192.160.127.90]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id GAA15963 for ; Wed, 10 Dec 1997 06:20:50 -0800 (PST) (envelope-from karl@Mars.mcs.net) Received: from Mars.mcs.net (karl@Mars.mcs.net [192.160.127.85]) by Kitten.mcs.com (8.8.7/8.8.2) with ESMTP id IAA28735; Wed, 10 Dec 1997 08:20:49 -0600 (CST) Received: (from karl@localhost) by Mars.mcs.net (8.8.7/8.8.2) id IAA29880; Wed, 10 Dec 1997 08:20:49 -0600 (CST) Message-ID: <19971210082048.20706@mcs.net> Date: Wed, 10 Dec 1997 08:20:48 -0600 From: Karl Denninger To: Kevin Day Cc: freebsd-current@FreeBSD.ORG Subject: Re: 971208 and the nfs rollback didn't fix it... References: <199712100434.WAA20572@home.dragondata.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.84 In-Reply-To: <199712100434.WAA20572@home.dragondata.com>; from Kevin Day on Tue, Dec 09, 1997 at 10:34:50PM -0600 Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Tue, Dec 09, 1997 at 10:34:50PM -0600, Kevin Day wrote: > > I grabbed everything on 971208, hoping it would cure my nfs problems... It > didn't. :) > > I still will see on my console: > > shell syslogd: sendto: no buffer space available > > Which is my first symptom that i'm going to have to reboot... > > Any attempt to read a file on an nfs system will completely hang the > process. (kill -9 doesn't even get rid of it). > > 3028 mbufs in use: > 2111 mbufs allocated to data > 304 mbufs allocated to packet headers > 11 mbufs allocated to protocol control blocks > 2 mbufs allocated to socket names and addresses > 554/1392 mbuf clusters in use > 8694 Kbytes allocated to network (97% in use) > 0 requests for memory denied > 0 requests for memory delayed > 0 calls to protocol drain routines > > > A reboot advises me that not all processes died, check ps axl, then it locks > up. > > > This system is a dual P/200, acting as an nfs client.... > > Both machines(this client, and a 2.2.1 server) get random 'nfsd send error > 55's on them... > > Is this news to anyone? > > Kevin Post a "dmesg" with the boot log in it. What ethernet card are you using? -- -- Karl Denninger (karl@MCS.Net)| MCSNet - Serving Chicagoland and Wisconsin http://www.mcs.net/ | T1's from $600 monthly to FULL DS-3 Service | NEW! K56Flex support on ALL modems Voice: [+1 312 803-MCS1 x219]| EXCLUSIVE NEW FEATURE ON ALL PERSONAL ACCOUNTS Fax: [+1 312 803-4929] | *SPAMBLOCK* Technology now included at no cost From owner-freebsd-current Wed Dec 10 07:08:12 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id HAA19709 for current-outgoing; Wed, 10 Dec 1997 07:08:12 -0800 (PST) (envelope-from owner-freebsd-current) Received: from whizzo.TransSys.COM (whizzo.TransSys.COM [144.202.42.10]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id HAA19698 for ; Wed, 10 Dec 1997 07:08:07 -0800 (PST) (envelope-from louie@whizzo.TransSys.COM) Received: from whizzo.TransSys.COM (localhost.transsys.com [127.0.0.1]) by whizzo.TransSys.COM (8.8.7/8.7.3) with ESMTP id KAA08420; Wed, 10 Dec 1997 10:07:56 -0500 (EST) Message-Id: <199712101507.KAA08420@whizzo.TransSys.COM> X-Mailer: exmh version 2.0zeta 7/24/97 To: Jason Evans cc: Alex , Steve Passe , current From: "Louis A. Mamakos" Subject: Re: -current, goliath, smp -- problems References: In-reply-to: Your message of "Tue, 09 Dec 1997 23:22:20 PST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 10 Dec 1997 10:07:56 -0500 Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk I understand that there are versions of the PPro CPU with 1MB of L2 cache, specifically intended for the MP situation where memory bandwidth is precious. I don't know how widely available these CPUs are. louie From owner-freebsd-current Wed Dec 10 08:26:48 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id IAA24837 for current-outgoing; Wed, 10 Dec 1997 08:26:48 -0800 (PST) (envelope-from owner-freebsd-current) Received: from dyson.iquest.net (dyson.iquest.net [198.70.144.127]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id IAA24822 for ; Wed, 10 Dec 1997 08:26:37 -0800 (PST) (envelope-from toor@dyson.iquest.net) Received: (from root@localhost) by dyson.iquest.net (8.8.8/8.8.8) id LAA00918; Wed, 10 Dec 1997 11:26:13 -0500 (EST) (envelope-from toor) From: "John S. Dyson" Message-Id: <199712101626.LAA00918@dyson.iquest.net> Subject: Re: 971208 and the nfs rollback didn't fix it... In-Reply-To: <19971210082048.20706@mcs.net> from Karl Denninger at "Dec 10, 97 08:20:48 am" To: karl@Mcs.Net (Karl Denninger) Date: Wed, 10 Dec 1997 11:26:13 -0500 (EST) Cc: toasty@home.dragondata.com, freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL31 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Karl Denninger said: > > > > A reboot advises me that not all processes died, check ps axl, then it locks > > up. > > > > > > This system is a dual P/200, acting as an nfs client.... > > > > Both machines(this client, and a 2.2.1 server) get random 'nfsd send error > > 55's on them... > > > > Is this news to anyone? > > > > Kevin > > Post a "dmesg" with the boot log in it. What ethernet card are you using? > I am not an NFS "expert", so you guys tell me exactly what the symptoms are, and I will TRY to help work out the problems. -- John dyson@freebsd.org jdyson@nc.com From owner-freebsd-current Wed Dec 10 09:13:15 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id JAA28532 for current-outgoing; Wed, 10 Dec 1997 09:13:15 -0800 (PST) (envelope-from owner-freebsd-current) Received: from Kitten.mcs.com (Kitten.mcs.com [192.160.127.90]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id JAA28522 for ; Wed, 10 Dec 1997 09:13:07 -0800 (PST) (envelope-from karl@Mars.mcs.net) Received: from Mars.mcs.net (karl@Mars.mcs.net [192.160.127.85]) by Kitten.mcs.com (8.8.7/8.8.2) with ESMTP id LAA15577; Wed, 10 Dec 1997 11:13:04 -0600 (CST) Received: (from karl@localhost) by Mars.mcs.net (8.8.7/8.8.2) id LAA11607; Wed, 10 Dec 1997 11:13:04 -0600 (CST) Message-ID: <19971210111304.33701@mcs.net> Date: Wed, 10 Dec 1997 11:13:04 -0600 From: Karl Denninger To: "John S. Dyson" Cc: toasty@home.dragondata.com, freebsd-current@freebsd.org Subject: Re: 971208 and the nfs rollback didn't fix it... References: <19971210082048.20706@mcs.net> <199712101626.LAA00918@dyson.iquest.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.84 In-Reply-To: <199712101626.LAA00918@dyson.iquest.net>; from John S. Dyson on Wed, Dec 10, 1997 at 11:26:13AM -0500 Sender: owner-freebsd-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Wed, Dec 10, 1997 at 11:26:13AM -0500, John S. Dyson wrote: > Karl Denninger said: > > > > > > A reboot advises me that not all processes died, check ps axl, then it locks > > > up. > > > > > > > > > This system is a dual P/200, acting as an nfs client.... > > > > > > Both machines(this client, and a 2.2.1 server) get random 'nfsd send error > > > 55's on them... > > > > > > Is this news to anyone? > > > > > > Kevin > > > > Post a "dmesg" with the boot log in it. What ethernet card are you using? > > > I am not an NFS "expert", so you guys tell me exactly what the symptoms are, > and I will TRY to help work out the problems. > > -- > John > dyson@freebsd.org > jdyson@nc.com The posted "netstat -m" looks like an mbuf leak, and I'm not seeing them here (with VERY heavy load and use). An example machine here: 11:11AM up 8 days, 22:30, 37 users, load averages: 0.24, 0.31, 0.25 284/1280 mbufs in use: 155 mbufs allocated to data 129 mbufs allocated to packet headers 65/824 mbuf clusters in use 1808 Kbytes allocated to network (9% in use) 0 requests for memory denied 0 requests for memory delayed 0 calls to protocol drain routines That's why I asked for the "dmesg" output and card in use - its possible that the problem here is with the ethernet driver losing mbufs somewhere, and if that's the case then the NFS code is not implicated at all. That I haven't seen this kind of problem is relatively good evidence of this - especially under our load profile. I *am* running 1.41 of nfs_bio.c in my kernels, because later versions blow up very, very badly, and I haven't rebuilt the master distribution since late November here. -- -- Karl Denninger (karl@MCS.Net)| MCSNet - Serving Chicagoland and Wisconsin http://www.mcs.net/ | T1's from $600 monthly to FULL DS-3 Service | NEW! K56Flex support on ALL modems Voice: [+1 312 803-MCS1 x219]| EXCLUSIVE NEW FEATURE ON ALL PERSONAL ACCOUNTS Fax: [+1 312 803-4929] | *SPAMBLOCK* Technology now included at no cost From owner-freebsd-current Wed Dec 10 09:19:45 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id JAA29256 for current-outgoing; Wed, 10 Dec 1997 09:19:45 -0800 (PST) (envelope-from owner-freebsd-current) Received: from dyson.iquest.net (dyson.iquest.net [198.70.144.127]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id JAA29228 for ; Wed, 10 Dec 1997 09:19:29 -0800 (PST) (envelope-from toor@dyson.iquest.net) Received: (from root@localhost) by dyson.iquest.net (8.8.8/8.8.8) id MAA01134; Wed, 10 Dec 1997 12:18:51 -0500 (EST) (envelope-from toor) From: "John S. Dyson" Message-Id: <199712101718.MAA01134@dyson.iquest.net> Subject: Re: 971208 and the nfs rollback didn't fix it... In-Reply-To: <19971210111304.33701@mcs.net> from Karl Denninger at "Dec 10, 97 11:13:04 am" To: karl@mcs.net (Karl Denninger) Date: Wed, 10 Dec 1997 12:18:51 -0500 (EST) Cc: toor@dyson.iquest.net, toasty@home.dragondata.com, freebsd-current@freebsd.org X-Mailer: ELM [version 2.4ME+ PL31 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Karl Denninger said: > > That I haven't seen this kind of problem is relatively good evidence of > this - especially under our load profile. I *am* running 1.41 of nfs_bio.c > in my kernels, because later versions blow up very, very badly, and I haven't > rebuilt the master distribution since late November here. > Thanks, Keep me posted, and I'll keep up with you (for a change.) :-). -- John dyson@freebsd.org jdyson@nc.com From owner-freebsd-current Wed Dec 10 09:24:43 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id JAA29713 for current-outgoing; Wed, 10 Dec 1997 09:24:43 -0800 (PST) (envelope-from owner-freebsd-current) Received: from home.dragondata.com (toasty@home.dragondata.com [204.137.237.2]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id JAA29693 for ; Wed, 10 Dec 1997 09:24:24 -0800 (PST) (envelope-from toasty@home.dragondata.com) Received: (from toasty@localhost) by home.dragondata.com (8.8.5/8.8.5) id LAA19545; Wed, 10 Dec 1997 11:24:09 -0600 (CST) From: Kevin Day Message-Id: <199712101724.LAA19545@home.dragondata.com> Subject: Re: 971208 and the nfs rollback didn't fix it... In-Reply-To: <199712101626.LAA00918@dyson.iquest.net> from "John S. Dyson" at "Dec 10, 97 11:26:13 am" To: toor@dyson.iquest.net (John S. Dyson) Date: Wed, 10 Dec 1997 11:24:09 -0600 (CST) Cc: karl@Mcs.Net, freebsd-current@freebsd.org X-Mailer: ELM [version 2.4ME+ PL31 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > > > > > Kevin > > > > Post a "dmesg" with the boot log in it. What ethernet card are you using? > > > I am not an NFS "expert", so you guys tell me exactly what the symptoms are, > and I will TRY to help work out the problems. > > -- > John > dyson@freebsd.org > jdyson@nc.com > I'm using a 3C509B... They've worked great, up until we started using NFS... One machine running 2.2 has been up more than 200 days, with a 509B, with no indication of a memory leak, with heavy net traffic.. Dec 10 05:03:11 shell /kernel: Copyright (c) 1992-1997 FreeBSD Inc. Dec 10 05:03:11 shell /kernel: Copyright (c) 1982, 1986, 1989, 1991, 1993 Dec 10 05:03:11 shell /kernel: The Regents of the University of California. All rights reserved. Dec 10 05:03:11 shell /kernel: FreeBSD 3.0-CURRENT #0: Mon Nov 24 19:26:11 CST 1997 Dec 10 05:03:11 shell /kernel: toasty@shell.dragondata.com:/usr/src/sys/compile/SHELL Dec 10 05:03:11 shell /kernel: CPU: Pentium (586-class CPU) Dec 10 05:03:11 shell /kernel: Origin = "GenuineIntel" Id = 0x52c Stepping=12 Dec 10 05:03:11 shell /kernel: Features=0x3bf Dec 10 05:03:11 shell /kernel: real memory = 83886080 (81920K bytes) Dec 10 05:03:11 shell /kernel: avail memory = 78573568 (76732K bytes) Dec 10 05:03:11 shell /kernel: FreeBSD/SMP: Multiprocessor motherboard Dec 10 05:03:11 shell /kernel: cpu0 (BSP): apic id: 0, version: 0x00030010, at 0xfee00000 Dec 10 05:03:11 shell /kernel: cpu1 (AP): apic id: 1, version: 0x00030010, at 0xfee00000 Dec 10 05:03:11 shell /kernel: io0 (APIC): apic id: 2, version: 0x00170011, at 0xfec00000 Dec 10 05:03:11 shell /kernel: Probing for devices on PCI bus 0: Dec 10 05:03:12 shell /kernel: chip0: rev 0x03 on pci0.0.0 Dec 10 05:03:12 shell /kernel: chip1: rev 0x01 on pci0.7.0 Dec 10 05:03:12 shell /kernel: ide_pci0: rev 0x00 on pci0.7.1 Dec 10 05:03:12 shell /kernel: Probing for devices on the ISA bus: Dec 10 05:03:12 shell /kernel: sc0 at 0x60-0x6f irq 1 on motherboard Dec 10 05:03:12 shell /kernel: sc0: VGA color <16 virtual consoles, flags=0x0> Dec 10 05:03:12 shell /kernel: sio0 at 0x3f8-0x3ff irq 4 on isa Dec 10 05:03:12 shell /kernel: sio0: type 16550A Dec 10 05:03:12 shell /kernel: sio1 at 0x2f8-0x2ff irq 3 on isa Dec 10 05:03:12 shell /kernel: sio1: type 16550A Dec 10 05:03:12 shell /kernel: lpt0 at 0x378-0x37f irq 7 on isa Dec 10 05:03:12 shell /kernel: lpt0: Interrupt-driven port Dec 10 05:03:12 shell /kernel: lp0: TCP/IP capable interface Dec 10 05:03:13 shell /kernel: lpt1 not found Dec 10 05:03:13 shell /kernel: mse0 not found at 0x23c Dec 10 05:03:13 shell /kernel: fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa Dec 10 05:03:13 shell /kernel: wdc0 at 0x1f0-0x1f7 irq 14 on isa Dec 10 05:03:13 shell /kernel: wdc0: unit 0 (wd0): Dec 10 05:03:13 shell /kernel: wd0: 2014MB (4124736 sectors), 4092 cyls, 16 heads, 63 S/T, 512 B/S Dec 10 05:03:13 shell /kernel: wdc1 not found at 0x170 Dec 10 05:03:13 shell /kernel: 1 3C5x9 board(s) on ISA found at 0x300 Dec 10 05:03:13 shell /kernel: ep0 at 0x300-0x30f irq 10 on isa Dec 10 05:03:13 shell /kernel: ep0: utp[*UTP*] address 00:60:97:6b:88:f4 Dec 10 05:03:13 shell /kernel: npx0 on motherboard Dec 10 05:03:13 shell /kernel: npx0: INT 16 interface Dec 10 05:03:13 shell /kernel: APIC_IO: routing 8254 via 8259 on pin 0 Dec 10 05:03:14 shell /kernel: SMP: AP CPU #1 Launched! Dec 10 05:03:14 shell /kernel: WARNING: / was not properly dismounted. Dec 10 05:03:14 shell named[80]: starting. named 4.9.6-REL Sat Nov 8 08:44:53 GMT 1997 root@make.ican.net:/usr/obj/usr/src/usr.sbin/named Dec 10 05:03:14 shell named[81]: Ready to answer queries. Dec 10 05:23:10 shell /kernel: Copyright (c) 1992-1997 FreeBSD Inc. Dec 10 05:23:10 shell /kernel: Copyright (c) 1982, 1986, 1989, 1991, 1993 Dec 10 05:23:10 shell /kernel: The Regents of the University of California. All rights reserved. Dec 10 05:23:10 shell /kernel: FreeBSD 3.0-CURRENT #0: Mon Nov 24 19:26:11 CST 1997 Dec 10 05:23:10 shell /kernel: toasty@shell.dragondata.com:/usr/src/sys/compile/SHELL Dec 10 05:23:10 shell /kernel: CPU: Pentium (586-class CPU) Dec 10 05:23:10 shell /kernel: Origin = "GenuineIntel" Id = 0x52c Stepping=12 Dec 10 05:23:10 shell /kernel: Features=0x3bf Dec 10 05:23:11 shell /kernel: real memory = 83886080 (81920K bytes) Dec 10 05:23:11 shell /kernel: avail memory = 78573568 (76732K bytes) Dec 10 05:23:11 shell /kernel: FreeBSD/SMP: Multiprocessor motherboard Dec 10 05:23:11 shell /kernel: cpu0 (BSP): apic id: 0, version: 0x00030010, at 0xfee00000 Dec 10 05:23:11 shell /kernel: cpu1 (AP): apic id: 1, version: 0x00030010, at 0xfee00000 Dec 10 05:23:11 shell /kernel: io0 (APIC): apic id: 2, version: 0x00170011, at 0xfec00000 Dec 10 05:23:11 shell /kernel: Probing for devices on PCI bus 0: Dec 10 05:23:11 shell /kernel: chip0: rev 0x03 on pci0.0.0 Dec 10 05:23:11 shell /kernel: chip1: rev 0x01 on pci0.7.0 Dec 10 05:23:11 shell /kernel: ide_pci0: rev 0x00 on pci0.7.1 Dec 10 05:23:11 shell /kernel: Probing for devices on the ISA bus: Dec 10 05:23:11 shell /kernel: sc0 at 0x60-0x6f irq 1 on motherboard Dec 10 05:23:11 shell /kernel: sc0: VGA color <16 virtual consoles, flags=0x0> Dec 10 05:23:11 shell /kernel: sio0 at 0x3f8-0x3ff irq 4 on isa Dec 10 05:23:12 shell /kernel: sio0: type 16550A Dec 10 05:23:12 shell /kernel: sio1 at 0x2f8-0x2ff irq 3 on isa Dec 10 05:23:12 shell /kernel: sio1: type 16550A Dec 10 05:23:12 shell /kernel: lpt0 at 0x378-0x37f irq 7 on isa Dec 10 05:23:12 shell /kernel: lpt0: Interrupt-driven port Dec 10 05:23:12 shell /kernel: lp0: TCP/IP capable interface Dec 10 05:23:12 shell /kernel: lpt1 not found Dec 10 05:23:12 shell /kernel: mse0 not found at 0x23c Dec 10 05:23:12 shell /kernel: fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa Dec 10 05:23:12 shell /kernel: wdc0 at 0x1f0-0x1f7 irq 14 on isa Dec 10 05:23:12 shell /kernel: wdc0: unit 0 (wd0): Dec 10 05:23:12 shell /kernel: wd0: 2014MB (4124736 sectors), 4092 cyls, 16 heads, 63 S/T, 512 B/S Dec 10 05:23:13 shell /kernel: wdc1 not found at 0x170 Dec 10 05:23:13 shell /kernel: 1 3C5x9 board(s) on ISA found at 0x300 Dec 10 05:23:13 shell /kernel: ep0 at 0x300-0x30f irq 10 on isa Dec 10 05:23:13 shell /kernel: ep0: utp[*UTP*] address 00:60:97:6b:88:f4 Dec 10 05:23:13 shell /kernel: npx0 on motherboard Dec 10 05:23:13 shell /kernel: npx0: INT 16 interface Dec 10 05:23:13 shell /kernel: APIC_IO: routing 8254 via 8259 on pin 0 Dec 10 05:23:13 shell /kernel: SMP: AP CPU #1 Launched! Dec 10 05:23:13 shell /kernel: WARNING: / was not properly dismounted. (when it probes for wdc1, it sits there no less than 10 minutes. I really thought it was hung the first few times it did it... is that normal?) It leaves no log as to why it crashes, and the screen is just full of: I'm on CPU #1, waiting to be on CPU #0... (or whatever the message is) It scrolls so quickly I miss the panic message. (another idea: after a kernel panic, unblank the screen, and disable the screen saver.... the daemon screensaver will keep going, even after a nasty panic.... I walk by the machine, see chuck running around on there, and assume everything's ok) Here's a copy of the output from mptable: =============================================================================== MPTable, version 2.0.15 ------------------------------------------------------------------------------- MP Floating Pointer Structure: location: BIOS physical address: 0x000f5c50 signature: '_MP_' length: 16 bytes version: 1.1 checksum: 0xd4 mode: Virtual Wire ------------------------------------------------------------------------------- MP Config Table Header: physical address: 0x000f5c64 signature: 'PCMP' base table length: 396 version: 1.1 checksum: 0x3a OEM ID: 'OEM00000' Product ID: 'PROD00000000' OEM table pointer: 0x00000000 OEM table size: 0 entry count: 28 local APIC address: 0xfee00000 extended table length: 0 extended table checksum: 0 ------------------------------------------------------------------------------- MP Config Base Table Entries: -- Processors: APIC ID Version State Family Model Step Flags 0 0x11 BSP, usable 5 2 1 0x07bf 1 0x11 AP, usable 5 2 1 0x07bf -- Bus: Bus ID Type 0 PCI 1 ISA -- I/O APICs: APIC ID Version State Address 2 0x11 usable 0xfec00000 -- I/O Ints: Type Polarity Trigger Bus ID IRQ APIC ID PIN# ExtINT conforms conforms 1 0 2 0 INT conforms conforms 1 1 2 1 INT conforms conforms 1 0 2 2 INT conforms conforms 1 3 2 3 INT conforms conforms 1 4 2 4 INT conforms conforms 1 5 2 5 INT conforms conforms 1 6 2 6 INT conforms conforms 1 7 2 7 INT conforms conforms 1 8 2 8 INT conforms conforms 1 9 2 9 INT conforms conforms 1 10 2 10 INT conforms conforms 1 11 2 11 INT conforms conforms 1 12 2 12 INT conforms conforms 1 13 2 13 INT conforms conforms 1 14 2 14 INT conforms conforms 1 15 2 15 INT active-lo level 0 20:A 2 16 INT active-lo level 0 19:A 2 17 INT active-lo level 0 18:A 2 18 INT active-lo level 0 17:A 2 19 SMI conforms conforms 1 0 2 23 -- Local Ints: Type Polarity Trigger Bus ID IRQ APIC ID PIN# ExtINT conforms conforms 0 0:A 255 0 NMI conforms conforms 0 0:A 255 1 ------------------------------------------------------------------------------- # SMP kernel config file options: # Required: options SMP # Symmetric MultiProcessor Kernel options APIC_IO # Symmetric (APIC) I/O # Optional (built-in defaults will work in most cases): #options NCPU=2 # number of CPUs #options NBUS=2 # number of busses #options NAPIC=1 # number of IO APICs #options NINTR=24 # number of INTs =============================================================================== The machine crashes with SMP or without SMP, but SMP speeds it up greatly. I'm not sure what's going on, because it was up for 15+ days, then suddenly can't stay up for more than 20 minutes... I've changed nothing, and don't really notice any difference in what users are doing on it.. (it's a shell account machine) Kevin From owner-freebsd-current Wed Dec 10 09:28:07 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id JAA29982 for current-outgoing; Wed, 10 Dec 1997 09:28:07 -0800 (PST) (envelope-from owner-freebsd-current) Received: from dyson.iquest.net (dyson.iquest.net [198.70.144.127]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id JAA29946; Wed, 10 Dec 1997 09:27:52 -0800 (PST) (envelope-from toor@dyson.iquest.net) Received: (from root@localhost) by dyson.iquest.net (8.8.8/8.8.8) id MAA01181; Wed, 10 Dec 1997 12:27:40 -0500 (EST) (envelope-from toor) From: "John S. Dyson" Message-Id: <199712101727.MAA01181@dyson.iquest.net> Subject: Re: VM system info In-Reply-To: from Wolfram Schneider at "Dec 8, 97 02:37:27 am" To: wosch@cs.tu-berlin.de (Wolfram Schneider) Date: Wed, 10 Dec 1997 12:27:40 -0500 (EST) Cc: dyson@freebsd.org, jonny@coppe.ufrj.br, current@freebsd.org X-Mailer: ELM [version 2.4ME+ PL31 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Wolfram Schneider said: > "John S. Dyson" writes: > > > // I have recently added some interesting VM tunables. Since it would > > > // be nice if people other than me (or those who requested them) could > > > // use the features, I thought it would be nice to pass this info on: > > > Is there any place or URL where we can get this information always > > > updated ? It's a pretty good form of documentation I've always > > > wanted to know. > > Nope. Unfortunately, the source code is the only place for it (by > > inference.) The VFS sysctls also deserve some documentation. > > sysctl(3) is the right place for sysctl documentation. > I am willing to pass info to people who have better language skills for inclusion into whatever docs we decide upon. -- John dyson@freebsd.org jdyson@nc.com From owner-freebsd-current Wed Dec 10 09:42:53 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id JAA01206 for current-outgoing; Wed, 10 Dec 1997 09:42:53 -0800 (PST) (envelope-from owner-freebsd-current) Received: from Kitten.mcs.com (Kitten.mcs.com [192.160.127.90]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id JAA01200 for ; Wed, 10 Dec 1997 09:42:44 -0800 (PST) (envelope-from karl@Mars.mcs.net) Received: from Mars.mcs.net (karl@Mars.mcs.net [192.160.127.85]) by Kitten.mcs.com (8.8.7/8.8.2) with ESMTP id LAA18787; Wed, 10 Dec 1997 11:42:26 -0600 (CST) Received: (from karl@localhost) by Mars.mcs.net (8.8.7/8.8.2) id LAA13377; Wed, 10 Dec 1997 11:42:26 -0600 (CST) Message-ID: <19971210114226.23033@mcs.net> Date: Wed, 10 Dec 1997 11:42:26 -0600 From: Karl Denninger To: Kevin Day Cc: "John S. Dyson" , freebsd-current@freebsd.org Subject: Re: 971208 and the nfs rollback didn't fix it... References: <199712101626.LAA00918@dyson.iquest.net> <199712101724.LAA19545@home.dragondata.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.84 In-Reply-To: <199712101724.LAA19545@home.dragondata.com>; from Kevin Day on Wed, Dec 10, 1997 at 11:24:09AM -0600 Sender: owner-freebsd-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Do you have an SMC card around there? Do this: 1) If you can, replace the 509B with an SMC Etherpower 10/100. That's a decent card, and is what we're using here without trouble. 2) Back out nfs_bio.c to V1.41 with "cvs update -r1.41 nfs_bio.c" in the nfs directory of your kernel area. Rebuild, and try it again. If it STILL blows up, get rid of the SMP support and see if THAT is stable. That ought to be, because that's what I'm running here and that *IS* stable. -- -- Karl Denninger (karl@MCS.Net)| MCSNet - Serving Chicagoland and Wisconsin http://www.mcs.net/ | T1's from $600 monthly to FULL DS-3 Service | NEW! K56Flex support on ALL modems Voice: [+1 312 803-MCS1 x219]| EXCLUSIVE NEW FEATURE ON ALL PERSONAL ACCOUNTS Fax: [+1 312 803-4929] | *SPAMBLOCK* Technology now included at no cost On Wed, Dec 10, 1997 at 11:24:09AM -0600, Kevin Day wrote: > > > > > > > > Kevin > > > > > > Post a "dmesg" with the boot log in it. What ethernet card are you using? > > > > > I am not an NFS "expert", so you guys tell me exactly what the symptoms are, > > and I will TRY to help work out the problems. > > > > -- > > John > > dyson@freebsd.org > > jdyson@nc.com > > > > I'm using a 3C509B... They've worked great, up until we started using NFS... > One machine running 2.2 has been up more than 200 days, with a 509B, with no > indication of a memory leak, with heavy net traffic.. > > Dec 10 05:03:11 shell /kernel: Copyright (c) 1992-1997 FreeBSD Inc. > Dec 10 05:03:11 shell /kernel: Copyright (c) 1982, 1986, 1989, 1991, 1993 > Dec 10 05:03:11 shell /kernel: The Regents of the University of California. All rights reserved. > Dec 10 05:03:11 shell /kernel: FreeBSD 3.0-CURRENT #0: Mon Nov 24 19:26:11 CST 1997 > Dec 10 05:03:11 shell /kernel: toasty@shell.dragondata.com:/usr/src/sys/compile/SHELL > Dec 10 05:03:11 shell /kernel: CPU: Pentium (586-class CPU) > Dec 10 05:03:11 shell /kernel: Origin = "GenuineIntel" Id = 0x52c Stepping=12 > Dec 10 05:03:11 shell /kernel: Features=0x3bf > Dec 10 05:03:11 shell /kernel: real memory = 83886080 (81920K bytes) > Dec 10 05:03:11 shell /kernel: avail memory = 78573568 (76732K bytes) > Dec 10 05:03:11 shell /kernel: FreeBSD/SMP: Multiprocessor motherboard > Dec 10 05:03:11 shell /kernel: cpu0 (BSP): apic id: 0, version: 0x00030010, at 0xfee00000 > Dec 10 05:03:11 shell /kernel: cpu1 (AP): apic id: 1, version: 0x00030010, at 0xfee00000 > Dec 10 05:03:11 shell /kernel: io0 (APIC): apic id: 2, version: 0x00170011, at 0xfec00000 > Dec 10 05:03:11 shell /kernel: Probing for devices on PCI bus 0: > Dec 10 05:03:12 shell /kernel: chip0: rev 0x03 on pci0.0.0 > Dec 10 05:03:12 shell /kernel: chip1: rev 0x01 on pci0.7.0 > Dec 10 05:03:12 shell /kernel: ide_pci0: rev 0x00 on pci0.7.1 > Dec 10 05:03:12 shell /kernel: Probing for devices on the ISA bus: > Dec 10 05:03:12 shell /kernel: sc0 at 0x60-0x6f irq 1 on motherboard > Dec 10 05:03:12 shell /kernel: sc0: VGA color <16 virtual consoles, flags=0x0> > Dec 10 05:03:12 shell /kernel: sio0 at 0x3f8-0x3ff irq 4 on isa > Dec 10 05:03:12 shell /kernel: sio0: type 16550A > Dec 10 05:03:12 shell /kernel: sio1 at 0x2f8-0x2ff irq 3 on isa > Dec 10 05:03:12 shell /kernel: sio1: type 16550A > Dec 10 05:03:12 shell /kernel: lpt0 at 0x378-0x37f irq 7 on isa > Dec 10 05:03:12 shell /kernel: lpt0: Interrupt-driven port > Dec 10 05:03:12 shell /kernel: lp0: TCP/IP capable interface > Dec 10 05:03:13 shell /kernel: lpt1 not found > Dec 10 05:03:13 shell /kernel: mse0 not found at 0x23c > Dec 10 05:03:13 shell /kernel: fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa > Dec 10 05:03:13 shell /kernel: wdc0 at 0x1f0-0x1f7 irq 14 on isa > Dec 10 05:03:13 shell /kernel: wdc0: unit 0 (wd0): > Dec 10 05:03:13 shell /kernel: wd0: 2014MB (4124736 sectors), 4092 cyls, 16 heads, 63 S/T, 512 B/S > Dec 10 05:03:13 shell /kernel: wdc1 not found at 0x170 > Dec 10 05:03:13 shell /kernel: 1 3C5x9 board(s) on ISA found at 0x300 > Dec 10 05:03:13 shell /kernel: ep0 at 0x300-0x30f irq 10 on isa > Dec 10 05:03:13 shell /kernel: ep0: utp[*UTP*] address 00:60:97:6b:88:f4 > Dec 10 05:03:13 shell /kernel: npx0 on motherboard > Dec 10 05:03:13 shell /kernel: npx0: INT 16 interface > Dec 10 05:03:13 shell /kernel: APIC_IO: routing 8254 via 8259 on pin 0 > Dec 10 05:03:14 shell /kernel: SMP: AP CPU #1 Launched! > Dec 10 05:03:14 shell /kernel: WARNING: / was not properly dismounted. > Dec 10 05:03:14 shell named[80]: starting. named 4.9.6-REL Sat Nov 8 08:44:53 GMT 1997 root@make.ican.net:/usr/obj/usr/src/usr.sbin/named > Dec 10 05:03:14 shell named[81]: Ready to answer queries. > Dec 10 05:23:10 shell /kernel: Copyright (c) 1992-1997 FreeBSD Inc. > Dec 10 05:23:10 shell /kernel: Copyright (c) 1982, 1986, 1989, 1991, 1993 > Dec 10 05:23:10 shell /kernel: The Regents of the University of California. All rights reserved. > Dec 10 05:23:10 shell /kernel: FreeBSD 3.0-CURRENT #0: Mon Nov 24 19:26:11 CST 1997 > Dec 10 05:23:10 shell /kernel: toasty@shell.dragondata.com:/usr/src/sys/compile/SHELL > Dec 10 05:23:10 shell /kernel: CPU: Pentium (586-class CPU) > Dec 10 05:23:10 shell /kernel: Origin = "GenuineIntel" Id = 0x52c Stepping=12 > Dec 10 05:23:10 shell /kernel: Features=0x3bf > Dec 10 05:23:11 shell /kernel: real memory = 83886080 (81920K bytes) > Dec 10 05:23:11 shell /kernel: avail memory = 78573568 (76732K bytes) > Dec 10 05:23:11 shell /kernel: FreeBSD/SMP: Multiprocessor motherboard > Dec 10 05:23:11 shell /kernel: cpu0 (BSP): apic id: 0, version: 0x00030010, at 0xfee00000 > Dec 10 05:23:11 shell /kernel: cpu1 (AP): apic id: 1, version: 0x00030010, at 0xfee00000 > Dec 10 05:23:11 shell /kernel: io0 (APIC): apic id: 2, version: 0x00170011, at 0xfec00000 > Dec 10 05:23:11 shell /kernel: Probing for devices on PCI bus 0: > Dec 10 05:23:11 shell /kernel: chip0: rev 0x03 on pci0.0.0 > Dec 10 05:23:11 shell /kernel: chip1: rev 0x01 on pci0.7.0 > Dec 10 05:23:11 shell /kernel: ide_pci0: rev 0x00 on pci0.7.1 > Dec 10 05:23:11 shell /kernel: Probing for devices on the ISA bus: > Dec 10 05:23:11 shell /kernel: sc0 at 0x60-0x6f irq 1 on motherboard > Dec 10 05:23:11 shell /kernel: sc0: VGA color <16 virtual consoles, flags=0x0> > Dec 10 05:23:11 shell /kernel: sio0 at 0x3f8-0x3ff irq 4 on isa > Dec 10 05:23:12 shell /kernel: sio0: type 16550A > Dec 10 05:23:12 shell /kernel: sio1 at 0x2f8-0x2ff irq 3 on isa > Dec 10 05:23:12 shell /kernel: sio1: type 16550A > Dec 10 05:23:12 shell /kernel: lpt0 at 0x378-0x37f irq 7 on isa > Dec 10 05:23:12 shell /kernel: lpt0: Interrupt-driven port > Dec 10 05:23:12 shell /kernel: lp0: TCP/IP capable interface > Dec 10 05:23:12 shell /kernel: lpt1 not found > Dec 10 05:23:12 shell /kernel: mse0 not found at 0x23c > Dec 10 05:23:12 shell /kernel: fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa > Dec 10 05:23:12 shell /kernel: wdc0 at 0x1f0-0x1f7 irq 14 on isa > Dec 10 05:23:12 shell /kernel: wdc0: unit 0 (wd0): > Dec 10 05:23:12 shell /kernel: wd0: 2014MB (4124736 sectors), 4092 cyls, 16 heads, 63 S/T, 512 B/S > Dec 10 05:23:13 shell /kernel: wdc1 not found at 0x170 > Dec 10 05:23:13 shell /kernel: 1 3C5x9 board(s) on ISA found at 0x300 > Dec 10 05:23:13 shell /kernel: ep0 at 0x300-0x30f irq 10 on isa > Dec 10 05:23:13 shell /kernel: ep0: utp[*UTP*] address 00:60:97:6b:88:f4 > Dec 10 05:23:13 shell /kernel: npx0 on motherboard > Dec 10 05:23:13 shell /kernel: npx0: INT 16 interface > Dec 10 05:23:13 shell /kernel: APIC_IO: routing 8254 via 8259 on pin 0 > Dec 10 05:23:13 shell /kernel: SMP: AP CPU #1 Launched! > Dec 10 05:23:13 shell /kernel: WARNING: / was not properly dismounted. > > (when it probes for wdc1, it sits there no less than 10 minutes. I really > thought it was hung the first few times it did it... is that normal?) > > It leaves no log as to why it crashes, and the screen is just full of: > > I'm on CPU #1, waiting to be on CPU #0... (or whatever the message is) > > It scrolls so quickly I miss the panic message. > > (another idea: after a kernel panic, unblank the screen, and disable the > screen saver.... the daemon screensaver will keep going, even after a nasty > panic.... I walk by the machine, see chuck running around on there, and > assume everything's ok) > > > > Here's a copy of the output from mptable: > > > > > =============================================================================== > > MPTable, version 2.0.15 > > ------------------------------------------------------------------------------- > > MP Floating Pointer Structure: > > location: BIOS > physical address: 0x000f5c50 > signature: '_MP_' > length: 16 bytes > version: 1.1 > checksum: 0xd4 > mode: Virtual Wire > > ------------------------------------------------------------------------------- > > MP Config Table Header: > > physical address: 0x000f5c64 > signature: 'PCMP' > base table length: 396 > version: 1.1 > checksum: 0x3a > OEM ID: 'OEM00000' > Product ID: 'PROD00000000' > OEM table pointer: 0x00000000 > OEM table size: 0 > entry count: 28 > local APIC address: 0xfee00000 > extended table length: 0 > extended table checksum: 0 > > ------------------------------------------------------------------------------- > > MP Config Base Table Entries: > > -- > Processors: APIC ID Version State Family Model Step Flags > 0 0x11 BSP, usable 5 2 1 0x07bf > 1 0x11 AP, usable 5 2 1 0x07bf > -- > Bus: Bus ID Type > 0 PCI > 1 ISA > -- > I/O APICs: APIC ID Version State Address > 2 0x11 usable 0xfec00000 > -- > I/O Ints: Type Polarity Trigger Bus ID IRQ APIC ID PIN# > ExtINT conforms conforms 1 0 2 0 > INT conforms conforms 1 1 2 1 > INT conforms conforms 1 0 2 2 > INT conforms conforms 1 3 2 3 > INT conforms conforms 1 4 2 4 > INT conforms conforms 1 5 2 5 > INT conforms conforms 1 6 2 6 > INT conforms conforms 1 7 2 7 > INT conforms conforms 1 8 2 8 > INT conforms conforms 1 9 2 9 > INT conforms conforms 1 10 2 10 > INT conforms conforms 1 11 2 11 > INT conforms conforms 1 12 2 12 > INT conforms conforms 1 13 2 13 > INT conforms conforms 1 14 2 14 > INT conforms conforms 1 15 2 15 > INT active-lo level 0 20:A 2 16 > INT active-lo level 0 19:A 2 17 > INT active-lo level 0 18:A 2 18 > INT active-lo level 0 17:A 2 19 > SMI conforms conforms 1 0 2 23 > -- > Local Ints: Type Polarity Trigger Bus ID IRQ APIC ID PIN# > ExtINT conforms conforms 0 0:A 255 0 > NMI conforms conforms 0 0:A 255 1 > > ------------------------------------------------------------------------------- > > # SMP kernel config file options: > > > # Required: > options SMP # Symmetric MultiProcessor Kernel > options APIC_IO # Symmetric (APIC) I/O > > # Optional (built-in defaults will work in most cases): > #options NCPU=2 # number of CPUs > #options NBUS=2 # number of busses > #options NAPIC=1 # number of IO APICs > #options NINTR=24 # number of INTs > > =============================================================================== > > > > The machine crashes with SMP or without SMP, but SMP speeds it up greatly. > I'm not sure what's going on, because it was up for 15+ days, then suddenly > can't stay up for more than 20 minutes... I've changed nothing, and don't > really notice any difference in what users are doing on it.. (it's a shell > account machine) > > Kevin From owner-freebsd-current Wed Dec 10 10:47:13 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id KAA06729 for current-outgoing; Wed, 10 Dec 1997 10:47:13 -0800 (PST) (envelope-from owner-freebsd-current) Received: from home.dragondata.com (toasty@home.dragondata.com [204.137.237.2]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id KAA06718 for ; Wed, 10 Dec 1997 10:47:06 -0800 (PST) (envelope-from toasty@home.dragondata.com) Received: (from toasty@localhost) by home.dragondata.com (8.8.5/8.8.5) id MAA26627; Wed, 10 Dec 1997 12:46:40 -0600 (CST) From: Kevin Day Message-Id: <199712101846.MAA26627@home.dragondata.com> Subject: Re: 971208 and the nfs rollback didn't fix it... In-Reply-To: <19971210114226.23033@mcs.net> from Karl Denninger at "Dec 10, 97 11:42:26 am" To: karl@mcs.net (Karl Denninger) Date: Wed, 10 Dec 1997 12:46:39 -0600 (CST) Cc: toor@dyson.iquest.net, freebsd-current@freebsd.org X-Mailer: ELM [version 2.4ME+ PL31 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Ok... Well... I'm not sure if I should feel stupid or not, but... Looking through /var/log/messages I noticed something... The system was rebooting on exact 10 minute boundaries... every time... (i.e. at 10:30:01, 10:50:01, etc) Lookking through /etc/crontab I found nothing. /var/cron/tabs showed me 5 users have 'botchk' in their tabs, to keep their eggdrops up. I'm not sure which user's script is causing the problem, but removing them all fixed it. What it looks like is happening, from cron's log, is that after a reboot, the first time botchk runs, it restarts the bot... the second time, it runs, the system crashes. I can reproduce this every time... Does anyone really feel the need to investigate this? I realize userland programs should never crash the kernel, but... is this a big enough deal for someone to want to investigate? Kevin From owner-freebsd-current Wed Dec 10 11:35:22 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id LAA10830 for current-outgoing; Wed, 10 Dec 1997 11:35:22 -0800 (PST) (envelope-from owner-freebsd-current) Received: from home.dragondata.com (toasty@home.dragondata.com [204.137.237.2]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id LAA10822 for ; Wed, 10 Dec 1997 11:35:17 -0800 (PST) (envelope-from toasty@home.dragondata.com) Received: (from toasty@localhost) by home.dragondata.com (8.8.5/8.8.5) id NAA29304; Wed, 10 Dec 1997 13:34:27 -0600 (CST) From: Kevin Day Message-Id: <199712101934.NAA29304@home.dragondata.com> Subject: Re: 971208 and the nfs rollback didn't fix it... In-Reply-To: <19971210114226.23033@mcs.net> from Karl Denninger at "Dec 10, 97 11:42:26 am" To: karl@mcs.net (Karl Denninger) Date: Wed, 10 Dec 1997 13:34:27 -0600 (CST) Cc: toor@dyson.iquest.net, freebsd-current@freebsd.org X-Mailer: ELM [version 2.4ME+ PL31 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Ok... A bit of progress... I figured out which user has the problem... The usr chronos is running an eggdrop... I tried to 'su' to his user name, so I could run things somewhat safely... After I su to him, all I get is 'su: fork: Resource temporarily unavailable'. What's going on, and does this have anything to do with his cron job crashing the system? $ su Password: You have mail. shell# su toasty $ df Filesystem 1K-blocks Used Avail Capacity Mounted on /dev/wd0a 1835919 571239 1117807 34% / procfs 4 4 0 100% /proc $ ^D shell# su chronos bash$ df su: fork: Resource temporarily unavailable bash$ ulimit unlimited bash$ ls su: fork: Resource temporarily unavailable bash$ Kevin From owner-freebsd-current Wed Dec 10 14:10:45 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id OAA23750 for current-outgoing; Wed, 10 Dec 1997 14:10:45 -0800 (PST) (envelope-from owner-freebsd-current) Received: from ns1.yes.no (ns1.yes.no [195.119.24.10]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id OAA23735 for ; Wed, 10 Dec 1997 14:10:32 -0800 (PST) (envelope-from eivind@bitbox.follo.net) Received: from bitbox.follo.net (bitbox.follo.net [194.198.43.36]) by ns1.yes.no (8.8.7/8.8.7) with ESMTP id WAA25638; Wed, 10 Dec 1997 22:10:24 GMT Received: (from eivind@localhost) by bitbox.follo.net (8.8.6/8.8.6) id XAA22400; Wed, 10 Dec 1997 23:10:18 +0100 (MET) To: Kevin Day Cc: freebsd-current@FreeBSD.ORG Subject: Re: 971208 and the nfs rollback didn't fix it... References: <199712101846.MAA26627@home.dragondata.com> From: Eivind Eklund Date: 10 Dec 1997 23:10:14 +0100 In-Reply-To: Kevin Day's message of Wed, 10 Dec 1997 12:46:39 -0600 (CST) Message-ID: <867m9c4zp5.fsf@bitbox.follo.net> Lines: 17 X-Mailer: Gnus v5.4.52/XEmacs 20.2 Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Kevin Day writes: > I can reproduce this every time... > > Does anyone really feel the need to investigate this? I realize userland > programs should never crash the kernel, but... is this a big enough deal for > someone to want to investigate? Yes. Userland programs should NEVER be able to crash the kernel, especially not running as users (instead of root). Now - more details :-) Do you get a kernel panic when it crash? Have you traced .cshrc files and tried changing /etc/login.conf for the user that gave you the strange effects? Eivind. From owner-freebsd-current Wed Dec 10 14:19:06 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id OAA24457 for current-outgoing; Wed, 10 Dec 1997 14:19:06 -0800 (PST) (envelope-from owner-freebsd-current) Received: from home.dragondata.com (toasty@home.dragondata.com [204.137.237.2]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id OAA24423 for ; Wed, 10 Dec 1997 14:18:56 -0800 (PST) (envelope-from toasty@home.dragondata.com) Received: (from toasty@localhost) by home.dragondata.com (8.8.5/8.8.5) id QAA09186; Wed, 10 Dec 1997 16:18:51 -0600 (CST) From: Kevin Day Message-Id: <199712102218.QAA09186@home.dragondata.com> Subject: Re: 971208 and the nfs rollback didn't fix it... In-Reply-To: <867m9c4zp5.fsf@bitbox.follo.net> from Eivind Eklund at "Dec 10, 97 11:10:14 pm" To: perhaps@yes.no (Eivind Eklund) Date: Wed, 10 Dec 1997 16:18:50 -0600 (CST) Cc: freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL31 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > Kevin Day writes: > > > I can reproduce this every time... > > > > Does anyone really feel the need to investigate this? I realize userland > > programs should never crash the kernel, but... is this a big enough deal for > > someone to want to investigate? > > Yes. Userland programs should NEVER be able to crash the kernel, > especially not running as users (instead of root). > > Now - more details :-) Do you get a kernel panic when it crash? 90% of the time, it's just a reboot., No crash, just jumps straight to the memory test. The other 10% it give a 'fault on nofault entry' panic. > > Have you traced .cshrc files and tried changing /etc/login.conf for > the user that gave you the strange effects? > > Eivind. > His .cshrc is essentially empty. # $Id: dot.cshrc,v 1.5 1996/09/21 21:35:35 wosch Exp $ # # .cshrc - csh resource script, read at beginning # of execution by each shell # # see also csh(1), environ(7). # alias h history 25 alias j jobs -l alias la ls -a alias lf ls -FA alias ll ls -lA setenv EDITOR vi setenv PAGER more setenv BLOCKSIZE K if ($?prompt) then # An interactive shell -- set some stuff up set filec set history = 100 set savehist = 100 set mail = (/var/mail/$USER) endif Our /etc/login.conf is untouched from our install. I have the entire eggdrop directory .tar'ed if someone wants to play with it. Kevin From owner-freebsd-current Wed Dec 10 14:23:19 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id OAA24947 for current-outgoing; Wed, 10 Dec 1997 14:23:19 -0800 (PST) (envelope-from owner-freebsd-current) Received: from ns1.yes.no (ns1.yes.no [195.119.24.10]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id OAA24928 for ; Wed, 10 Dec 1997 14:23:10 -0800 (PST) (envelope-from eivind@bitbox.follo.net) Received: from bitbox.follo.net (bitbox.follo.net [194.198.43.36]) by ns1.yes.no (8.8.7/8.8.7) with ESMTP id WAA25764; Wed, 10 Dec 1997 22:23:03 GMT Received: (from eivind@localhost) by bitbox.follo.net (8.8.6/8.8.6) id XAA23475; Wed, 10 Dec 1997 23:23:03 +0100 (MET) Message-ID: <19971210232302.35402@follo.net> Date: Wed, 10 Dec 1997 23:23:02 +0100 From: Eivind Eklund To: Kevin Day Cc: Eivind Eklund , freebsd-current@FreeBSD.ORG Subject: Re: 971208 and the nfs rollback didn't fix it... References: <867m9c4zp5.fsf@bitbox.follo.net> <199712102218.QAA09186@home.dragondata.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.88e In-Reply-To: <199712102218.QAA09186@home.dragondata.com>; from Kevin Day on Wed, Dec 10, 1997 at 04:18:50PM -0600 Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Wed, Dec 10, 1997 at 04:18:50PM -0600, Kevin Day wrote: > > Yes. Userland programs should NEVER be able to crash the kernel, > > especially not running as users (instead of root). > > > > Now - more details :-) Do you get a kernel panic when it crash? > > 90% of the time, it's just a reboot., No crash, just jumps straight to the > memory test. The other 10% it give a 'fault on nofault entry' panic. Have you ruled out faulty hardware? Do you get the same fault if you run with the same disk on another machine? (If not: Is this something you can afford to test?) > His .cshrc is essentially empty. > [default .cshrc file removed] > > Our /etc/login.conf is untouched from our install. > > > I have the entire eggdrop directory .tar'ed if someone wants to play with > it. If you can reproduce on other hardware and other installs, it's probably best to go that way. If it isn't reproducable I'd guess at a hardware-dependent problem - that'll be much harder. It might even be just a single case of faulty hardware. Eivind. From owner-freebsd-current Wed Dec 10 14:25:30 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id OAA25235 for current-outgoing; Wed, 10 Dec 1997 14:25:30 -0800 (PST) (envelope-from owner-freebsd-current) Received: from home.dragondata.com (toasty@home.dragondata.com [204.137.237.2]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id OAA25206 for ; Wed, 10 Dec 1997 14:25:21 -0800 (PST) (envelope-from toasty@home.dragondata.com) Received: (from toasty@localhost) by home.dragondata.com (8.8.5/8.8.5) id QAA09556; Wed, 10 Dec 1997 16:25:16 -0600 (CST) From: Kevin Day Message-Id: <199712102225.QAA09556@home.dragondata.com> Subject: Re: 971208 and the nfs rollback didn't fix it... In-Reply-To: <19971210232302.35402@follo.net> from Eivind Eklund at "Dec 10, 97 11:23:02 pm" To: perhaps@yes.no (Eivind Eklund) Date: Wed, 10 Dec 1997 16:25:16 -0600 (CST) Cc: perhaps@yes.no, freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL31 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > On Wed, Dec 10, 1997 at 04:18:50PM -0600, Kevin Day wrote: > > > Yes. Userland programs should NEVER be able to crash the kernel, > > > especially not running as users (instead of root). > > > > > > Now - more details :-) Do you get a kernel panic when it crash? > > > > 90% of the time, it's just a reboot., No crash, just jumps straight to the > > memory test. The other 10% it give a 'fault on nofault entry' panic. > > Have you ruled out faulty hardware? Do you get the same fault if you > run with the same disk on another machine? (If not: Is this something > you can afford to test?) I untarred the archive on another -current machine for testing, and it locked up tight. (didn't reboot, though) I could actually move the drive too, if you felt it was necessary. I'm pretty sure there's a bug somewhere in here. Kevin From owner-freebsd-current Wed Dec 10 15:40:15 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id PAA04045 for current-outgoing; Wed, 10 Dec 1997 15:40:15 -0800 (PST) (envelope-from owner-freebsd-current) Received: from shell5.ba.best.com (cbray@shell5.ba.best.com [206.184.139.136]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id PAA04040 for ; Wed, 10 Dec 1997 15:40:10 -0800 (PST) (envelope-from cbray@shell5.ba.best.com) Received: from localhost (cbray@localhost) by shell5.ba.best.com (8.8.8/8.8.BEST) with SMTP id PAA23485 for ; Wed, 10 Dec 1997 15:40:09 -0800 (PST) Date: Wed, 10 Dec 1997 15:40:09 -0800 (PST) From: Curtis Bray To: freebsd-current@FreeBSD.ORG Subject: FreeBSD 3.0-current(12/10): rfork() problems in USERLAND? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Hey Folks, I'm curious if anyone else if seeing this behavior with rfork... I've cvsup'ed to the latest code as of 12/10 and I'm still having difficulties with rfork(RFPROC | RFMEM) out in userland. From past discussions my understanding was John Dyson had added the RFMEM support into current as part of the kernel thread support for the AIO stuff, but I'm unclear if the user process support has been finished. Anyway, here's a dump of the program I'm running (very very basic) and the output that occurs. The core file was truncated when I tried to look at it with gdb. -------- #include #include #include #include #include #include #include #include void child_proc(int procNum, int time) { printf("Child %d is exiting\n", procNum); exit(0); } void main(int argc, char *argv[]) { int numProc = 1; int procNum = 0; int time = 2; int ret, status; int numReturned = 0; if(argc > 1) numProc = atoi(argv[1]); if(argc > 2) time = atoi(argv[2]); printf("Going to create %d rfork() process\n", numProc); for(procNum = 0; procNum < numProc; procNum++) { if((ret = rfork(RFPROC | RFMEM)) == 0) { printf("Inside child from fork: %d\n", procNum); child_proc(procNum, time); } else printf("Parent forked %d (ret = %d)\n", procNum, ret); } printf("Parent waiting for children.\n"); while((ret = wait(&status)) != -1) { printf("Parent woke up on wait for %d with status %d (#%d)\n", ret, status, numReturned++); printf("%d : Signaled? %d / %d\n", ret, WIFSIGNALED(status), WTERMSIG(status)); } } ----------- program output: Going to create 1 rfork() process Parent forked 0 (ret = 444) Parent waiting for children. Parent woke up on wait for 0 with status 4231 (#0) 0 : Signaled? 1 / 7 Bus error (core dumped) ---------- Any ideas? Thanks in advance! Curtis From owner-freebsd-current Wed Dec 10 15:52:11 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id PAA05105 for current-outgoing; Wed, 10 Dec 1997 15:52:11 -0800 (PST) (envelope-from owner-freebsd-current) Received: from isis.ie-eg.com ([194.79.98.72]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id PAA05001 for ; Wed, 10 Dec 1997 15:51:52 -0800 (PST) (envelope-from root@isis.dynip.com) Received: from localhost (root@localhost) by isis.ie-eg.com (8.8.8/8.8.8) with SMTP id BAA01126 for ; Thu, 11 Dec 1997 01:51:14 +0200 (EET) Date: Thu, 11 Dec 1997 01:51:13 +0200 (EET) From: Charlie Roots X-Sender: root@isis.ie-eg.com To: FreeBSD-current Mailing List Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk index freebsd-current end MAY THE FORCE BE WITH YOU. From owner-freebsd-current Wed Dec 10 15:52:47 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id PAA05208 for current-outgoing; Wed, 10 Dec 1997 15:52:47 -0800 (PST) (envelope-from owner-freebsd-current) Received: from frmug.org (frmug-gw.frmug.org [193.56.58.252]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id PAA05165 for ; Wed, 10 Dec 1997 15:52:31 -0800 (PST) (envelope-from roberto@keltia.freenix.fr) Received: (from uucp@localhost) by frmug.org (8.8.8/frmug-2.1/nospam) with UUCP id AAA25127 for freebsd-current@FreeBSD.ORG; Thu, 11 Dec 1997 00:13:14 +0100 (CET) (envelope-from roberto@keltia.freenix.fr) Received: (from roberto@localhost) by keltia.freenix.fr (8.8.8/keltia-2.13/nospam) id AAA04501; Thu, 11 Dec 1997 00:02:52 +0100 (CET) (envelope-from roberto) Message-ID: <19971211000252.23749@keltia.freenix.fr> Date: Thu, 11 Dec 1997 00:02:52 +0100 From: Ollivier Robert To: freebsd-current@FreeBSD.ORG Subject: Re: Which libtermcap is current? References: <199712101100.MAA05905@crux.tesco-stores.cz> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Mailer: Mutt 0.88 In-Reply-To: <199712101100.MAA05905@crux.tesco-stores.cz>; from frf on Wed, Dec 10, 1997 at 12:00:52PM +0100 X-Operating-System: FreeBSD 3.0-CURRENT ctm#3883 AMD-K6 MMX @ 208 MHz Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk According to frf: > look at the makefile for libtermcap includes a hack to work around > this dependency. > > ===> usr.bin/top > make: don't know how to make /usr/obj/usr/src/tmp/usr/lib/libtermcap.so.3.0. Stop Just either delete obj/.depend or blow away /usr/obj before running "make world". -- Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- roberto@keltia.freenix.fr FreeBSD keltia.freenix.fr 3.0-CURRENT #19: Tue Dec 9 20:17:10 CET 1997 From owner-freebsd-current Wed Dec 10 16:16:39 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id QAA07956 for current-outgoing; Wed, 10 Dec 1997 16:16:39 -0800 (PST) (envelope-from owner-freebsd-current) Received: from Hydro.CAM.ORG (Hydro.CAM.ORG [198.168.100.7]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id QAA07945; Wed, 10 Dec 1997 16:16:30 -0800 (PST) (envelope-from owilson@CAM.ORG) Received: from siren.sirn.org (owilson.HIP.CAM.ORG [205.151.117.34]) by Hydro.CAM.ORG (8.8.4/8.8.4) with SMTP id RAA23626; Wed, 10 Dec 1997 17:56:16 -0500 (EST) Message-ID: <348ED760.41C67EA6@cam.org> Date: Wed, 10 Dec 1997 12:54:40 -0500 From: Oliver Wilson Organization: SIRN X-Mailer: Mozilla 3.0Gold (X11; I; FreeBSD 2.1.5-RELEASE i386) MIME-Version: 1.0 To: "Jordan K. Hubbard" CC: Steve Passe , smp@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: Usable SMP on 971208 References: <18896.881725415@time.cdrom.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Hi, How does one determine which are 'good dates' for downloading SMP source? I'm planning to download SMP in the near future. Regards Oliver Wilson Metaphor Data Methods Inc. Jordan K. Hubbard wrote: > > > It would appear that December 8, 1997 is a good date for which to grab SMP > > source. > > Yep! Which is why I downloaded a copy of that snapshot onto > ftp.freebsd.org for easier installation a day ago (great minds think > alike :-). > > Jordan --  From owner-freebsd-current Wed Dec 10 16:29:28 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id QAA09138 for current-outgoing; Wed, 10 Dec 1997 16:29:28 -0800 (PST) (envelope-from owner-freebsd-current) Received: from send1b.yahoomail.com (send1b.yahoomail.com [205.180.60.23]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id QAA09120 for ; Wed, 10 Dec 1997 16:29:19 -0800 (PST) (envelope-from osiris2002@yahoo.com) Message-ID: <19971211002906.2617.rocketmail@send1b.yahoomail.com> Received: from [194.79.98.72] by send1b; Wed, 10 Dec 1997 16:29:06 PST Date: Wed, 10 Dec 1997 16:29:06 -0800 (PST) From: Charlie Roots Subject: FreeBSD 3.0 Current. Is HUNGRY For Swap ?? To: freebsd-current@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi people all around the globe. I have noticed on XsysInfo monitor that the swap filesystem consumption is much higher for FreeBSD-3.0 current in comparison with FreeBSD-2.2.2-RELEASE, my previous OS, especially when using Netscape Communicator 4.04 for FreeBSD Version 4, but unfortunately I have upgraded at the same time BOTH netscape and the FreeBSD itself, as I was using netscape 4.01b. So I can't tell for sure which one is doing this. Is there anyone having larger swap consumtion on current, and if so, what are we looking at now, is it a memory LEAK, or what ? Your help is appreciated, please guide. == MAY THE FORCE BE WITH YOU. _________________________________________________________ DO YOU YAHOO!? Get your free @yahoo.com address at http://mail.yahoo.com From owner-freebsd-current Wed Dec 10 17:27:49 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id RAA14461 for current-outgoing; Wed, 10 Dec 1997 17:27:49 -0800 (PST) (envelope-from owner-freebsd-current) Received: from dyson.iquest.net (dyson.iquest.net [198.70.144.127]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id RAA14439 for ; Wed, 10 Dec 1997 17:27:29 -0800 (PST) (envelope-from toor@dyson.iquest.net) Received: (from root@localhost) by dyson.iquest.net (8.8.8/8.8.8) id UAA01339; Wed, 10 Dec 1997 20:27:20 -0500 (EST) (envelope-from toor) From: "John S. Dyson" Message-Id: <199712110127.UAA01339@dyson.iquest.net> Subject: Re: FreeBSD 3.0-current(12/10): rfork() problems in USERLAND? In-Reply-To: from Curtis Bray at "Dec 10, 97 03:40:09 pm" To: cbray@best.com (Curtis Bray) Date: Wed, 10 Dec 1997 20:27:20 -0500 (EST) Cc: freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL31 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Curtis Bray said: > Hey Folks, > > I'm curious if anyone else if seeing this behavior with rfork... I've > cvsup'ed to the latest code as of 12/10 and I'm still having difficulties > with rfork(RFPROC | RFMEM) out in userland. > > From past discussions my understanding was John Dyson had added the > RFMEM support into current as part of the kernel thread support for the > AIO stuff, but I'm unclear if the user process support has been finished. > Anyway, here's a dump of the program I'm running (very very basic) and > the output that occurs. The core file was truncated when I tried to look > at it with gdb. > You cannot use rfork() the way that you are. Take a look at the rf.S following this email. Our rfork() pushes as much into userland as possible. -- John dyson@freebsd.org jdyson@nc.com .file "rf.S" #include #include "DEFS.h" #include "SYS.h" #define KERNEL #include #undef KERNEL #undef DEBUG /* * 8 12 16 20 24 28 * _rfork(flags, stack, startrtn, startarg, userrtn, arg); * * flags: RF* flags for rfork in unistd.h. * subr: subroutine to run as a thread. * stack: top of stack for thread. * arg: argument to thread. */ .stabs "rf.S",100,0,0,Ltext0 .text Ltext0: .type _thrfork,@function .stabd 68,0,1 ENTRY(thrfork) pushl %ebp movl %esp, %ebp pushl %esi /* * Push thread info onto the new thread's stack */ movl 12(%ebp), %esi / get stack addr subl $4, %esi movl 28(%ebp), %eax / get user argument movl %eax, (%esi) subl $4, %esi movl 24(%ebp), %eax / get user thread address movl %eax, (%esi) subl $4, %esi movl 20(%ebp), %eax / get internal argument movl %eax, (%esi) subl $4, %esi movl 16(%ebp), %eax / get internal subroutine movl %eax, (%esi) .stabd 68,0,2 /* * Prepare and execute rfork */ pushl 8(%ebp) pushl %esi leal SYS_rfork, %eax KERNCALL jb 2f .stabd 68,0,3 /* * Check to see if we are in the parent or child */ cmpl $0, %edx jnz 1f addl $8, %esp popl %esi movl %ebp, %esp popl %ebp ret .p2align 2 /* * If we are in the child (new thread), then * set-up the call to the internal subroutine. If it * returns, then call __exit. */ .stabd 68,0,4 1: movl %esi,%esp #ifdef DEBUG movl %esp, _stackaddr movl (%esp), %eax movl %eax, _stack movl 4(%esp), %eax movl %eax,_stack+4 movl 8(%esp), %eax movl %eax,_stack+8 movl 12(%esp), %eax movl %eax,_stack+12 #endif popl %eax #ifdef DEBUG movl %eax,_fcn #endif call %eax addl $12, %esp /* * Exit system call */ pushl %eax pushl $SYS_exit call _syscall .stabd 68,0,5 2: movl $EAGAIN, _errno movl $-1, %eax leave ret .stabs "thrfork:f67",36,0,6,_thrfork Lfe1: .size _thrfork,Lfe1-_thrfork #ifdef DEBUG .data .globl _stack _stack: .long 0 .long 0 .long 0 .long 0 .long 0 .globl _stackaddr _stackaddr: .long 0 .globl _fcn _fcn: .long 0 #endif From owner-freebsd-current Wed Dec 10 17:30:16 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id RAA14823 for current-outgoing; Wed, 10 Dec 1997 17:30:16 -0800 (PST) (envelope-from owner-freebsd-current) Received: from Kitten.mcs.com (Kitten.mcs.com [192.160.127.90]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id RAA14814 for ; Wed, 10 Dec 1997 17:30:09 -0800 (PST) (envelope-from karl@Mars.mcs.net) Received: from Mars.mcs.net (karl@Mars.mcs.net [192.160.127.85]) by Kitten.mcs.com (8.8.7/8.8.2) with ESMTP id TAA02838; Wed, 10 Dec 1997 19:30:01 -0600 (CST) Received: (from karl@localhost) by Mars.mcs.net (8.8.7/8.8.2) id TAA04411; Wed, 10 Dec 1997 19:30:00 -0600 (CST) Message-ID: <19971210193000.15751@mcs.net> Date: Wed, 10 Dec 1997 19:30:00 -0600 From: Karl Denninger To: Eivind Eklund Cc: Kevin Day , freebsd-current@FreeBSD.ORG Subject: Re: 971208 and the nfs rollback didn't fix it... References: <867m9c4zp5.fsf@bitbox.follo.net> <199712102218.QAA09186@home.dragondata.com> <19971210232302.35402@follo.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.84 In-Reply-To: <19971210232302.35402@follo.net>; from Eivind Eklund on Wed, Dec 10, 1997 at 11:23:02PM +0100 Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Wed, Dec 10, 1997 at 11:23:02PM +0100, Eivind Eklund wrote: > On Wed, Dec 10, 1997 at 04:18:50PM -0600, Kevin Day wrote: > > > Yes. Userland programs should NEVER be able to crash the kernel, > > > especially not running as users (instead of root). > > > > > > Now - more details :-) Do you get a kernel panic when it crash? > > > > 90% of the time, it's just a reboot., No crash, just jumps straight to the > > memory test. The other 10% it give a 'fault on nofault entry' panic. Bingo. Fault on nofault entry is the NFS client code problem. Roll back to 1.41 of nfs_bio.c (as I suggested before) and it should go away. -- -- Karl Denninger (karl@MCS.Net)| MCSNet - Serving Chicagoland and Wisconsin http://www.mcs.net/ | T1's from $600 monthly to FULL DS-3 Service | NEW! K56Flex support on ALL modems Voice: [+1 312 803-MCS1 x219]| EXCLUSIVE NEW FEATURE ON ALL PERSONAL ACCOUNTS Fax: [+1 312 803-4929] | *SPAMBLOCK* Technology now included at no cost From owner-freebsd-current Wed Dec 10 18:18:17 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id SAA18757 for current-outgoing; Wed, 10 Dec 1997 18:18:17 -0800 (PST) (envelope-from owner-freebsd-current) Received: from zippy.dyn.ml.org (spain-19.ppp.hooked.net [206.169.228.19]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id SAA18736 for ; Wed, 10 Dec 1997 18:18:11 -0800 (PST) (envelope-from garbanzo@hooked.net) Received: from localhost (garbanzo@localhost) by zippy.dyn.ml.org (8.8.8/8.8.7) with SMTP id SAA02689; Wed, 10 Dec 1997 18:19:06 -0800 (PST) X-Authentication-Warning: zippy.dyn.ml.org: garbanzo owned process doing -bs Date: Wed, 10 Dec 1997 18:19:05 -0800 (PST) From: Alex X-Sender: garbanzo@zippy.dyn.ml.org To: Jason Evans cc: Steve Passe , current Subject: Re: -current, goliath, smp -- problems In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Tue, 9 Dec 1997, Jason Evans wrote: > Well, I don't know that I would necessarily expect this to be as cool as > it sounds. I'm not an expert on this by any means, but I've > repeatedly heard the following: > > Tightly coupled MP machines work well until memory bandwidth becomes a > bottleneck. Last I heard, the memory bandwidth on Intel-based machines is > in the neighborhood of 500 MB/sec, which is enough to feed 4 processors, > but quite inadequate for 8. So, even though there are twice as many > processors, the performance gain is not impressive. > > If there's anyone else out there that knows any better, please correct me. > =) Who knows, HP may have (and hopefully did) use a different sort of memory bus, and tweaked whatever else might not be up to snuff for 8cpus. - alex From owner-freebsd-current Wed Dec 10 18:43:32 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id SAA21273 for current-outgoing; Wed, 10 Dec 1997 18:43:32 -0800 (PST) (envelope-from owner-freebsd-current) Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id SAA21255 for ; Wed, 10 Dec 1997 18:43:20 -0800 (PST) (envelope-from jkh@time.cdrom.com) Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.7/8.6.9) with ESMTP id SAA24111; Wed, 10 Dec 1997 18:43:15 -0800 (PST) To: Kevin Day cc: freebsd-current@FreeBSD.ORG Subject: Re: 971208 and the nfs rollback didn't fix it... In-reply-to: Your message of "Wed, 10 Dec 1997 12:46:39 CST." <199712101846.MAA26627@home.dragondata.com> Date: Wed, 10 Dec 1997 18:43:15 -0800 Message-ID: <24108.881808195@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > Does anyone really feel the need to investigate this? I realize userland > programs should never crash the kernel, but... is this a big enough deal for > someone to want to investigate? Yes, I'd say it is. Is this 2.2.5 or -current, however? Jordan From owner-freebsd-current Wed Dec 10 18:56:29 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id SAA22421 for current-outgoing; Wed, 10 Dec 1997 18:56:29 -0800 (PST) (envelope-from owner-freebsd-current) Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id SAA22409 for ; Wed, 10 Dec 1997 18:56:16 -0800 (PST) (envelope-from jkh@time.cdrom.com) Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.7/8.6.9) with ESMTP id SAA24257; Wed, 10 Dec 1997 18:56:13 -0800 (PST) To: Kevin Day cc: freebsd-current@FreeBSD.ORG Subject: Re: 971208 and the nfs rollback didn't fix it... In-reply-to: Your message of "Wed, 10 Dec 1997 13:34:27 CST." <199712101934.NAA29304@home.dragondata.com> Date: Wed, 10 Dec 1997 18:56:13 -0800 Message-ID: <24253.881808973@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > What's going on, and does this have anything to do with his cron job > crashing the system? Unlikely. Jordan From owner-freebsd-current Wed Dec 10 18:58:18 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id SAA22511 for current-outgoing; Wed, 10 Dec 1997 18:58:18 -0800 (PST) (envelope-from owner-freebsd-current) Received: from home.dragondata.com (toasty@home.dragondata.com [204.137.237.2]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id SAA22483 for ; Wed, 10 Dec 1997 18:58:02 -0800 (PST) (envelope-from toasty@home.dragondata.com) Received: (from toasty@localhost) by home.dragondata.com (8.8.5/8.8.5) id UAA22490; Wed, 10 Dec 1997 20:57:53 -0600 (CST) From: Kevin Day Message-Id: <199712110257.UAA22490@home.dragondata.com> Subject: Re: 971208 and the nfs rollback didn't fix it... In-Reply-To: <24108.881808195@time.cdrom.com> from "Jordan K. Hubbard" at "Dec 10, 97 06:43:15 pm" To: jkh@time.cdrom.com (Jordan K. Hubbard) Date: Wed, 10 Dec 1997 20:57:53 -0600 (CST) Cc: freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL31 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > Does anyone really feel the need to investigate this? I realize userland > > programs should never crash the kernel, but... is this a big enough deal for > > someone to want to investigate? > > Yes, I'd say it is. Is this 2.2.5 or -current, however? > > Jordan > -current. I have two machines running the exact same setup. (I installed one, then duped the hard drive, so they are identical, software wise). Totally different hardware though... Both machines can reproduce the crash. It doesn't work on a 2.2.1 machine I have though. Essentially, here's the best I can pin it down. A user has eggdrop1.2.0 semi-installed on here. Somewhere along the way he lost his eggdrop binary. He sets up botchk to run in his crontab anyway. Botchk executes his conf file, which should bomb immediately... It executes /home/chronos/egg/eggdrop1.2.0/Pipeline, and nstead it either randomly reboots the machine, or garbles the first 5 letters in the file. bash$cat /home/chronos/egg/eggdrop1.2.0/Pipeline #!/home/chronos/egg/eggdrop1.2.0/ # ^- set that to the directory eggdrop is in ie "#!/users/lamest/egg/eggdrop" # # This is a sample configuration file for your bot. You will definitely # want to edit this, to set up your bot. Right now it creates a bot called # "LamestBot" which sits on channel #lamest. turns in to: Az^MDme/chronos/egg/eggdrop1.2.0/ # ^- set that to the directory eggdrop is in ie "#!/users/lamest/egg/eggdrop" # # This is a sample configuration file for your bot. You will definitely # want to edit this, to set up your bot. Right now it creates a bot called # "LamestBot" which sits on channel #lamest. If it doesn't scramble the file, it jumps straight to the ram test. No panic message, nothing. If it *does* scramble the file, that user can't do anything from that point on. All he see will see is 'fork: resource temporarily unavailable' until I reboot the machine. Does this make sense to anyone? Kevin From owner-freebsd-current Wed Dec 10 19:07:54 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id TAA23567 for current-outgoing; Wed, 10 Dec 1997 19:07:54 -0800 (PST) (envelope-from owner-freebsd-current) Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id TAA23553; Wed, 10 Dec 1997 19:07:43 -0800 (PST) (envelope-from jkh@time.cdrom.com) Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.7/8.6.9) with ESMTP id TAA24434; Wed, 10 Dec 1997 19:07:31 -0800 (PST) To: Oliver Wilson cc: Steve Passe , smp@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: Usable SMP on 971208 In-reply-to: Your message of "Wed, 10 Dec 1997 12:54:40 EST." <348ED760.41C67EA6@cam.org> Date: Wed, 10 Dec 1997 19:07:31 -0800 Message-ID: <24431.881809651@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > Hi, > > How does one determine which are 'good dates' for downloading SMP > source? You run it on your SMP hardware and decide when it's a good day. At least that's how I do it. :) Jordan From owner-freebsd-current Wed Dec 10 19:33:16 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id TAA25808 for current-outgoing; Wed, 10 Dec 1997 19:33:16 -0800 (PST) (envelope-from owner-freebsd-current) Received: from dyson.iquest.net (dyson.iquest.net [198.70.144.127]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id TAA25796; Wed, 10 Dec 1997 19:33:08 -0800 (PST) (envelope-from toor@dyson.iquest.net) Received: (from root@localhost) by dyson.iquest.net (8.8.8/8.8.8) id WAA02154; Wed, 10 Dec 1997 22:32:56 -0500 (EST) (envelope-from toor) From: "John S. Dyson" Message-Id: <199712110332.WAA02154@dyson.iquest.net> Subject: Re: Usable SMP on 971208 In-Reply-To: <24431.881809651@time.cdrom.com> from "Jordan K. Hubbard" at "Dec 10, 97 07:07:31 pm" To: jkh@time.cdrom.com (Jordan K. Hubbard) Date: Wed, 10 Dec 1997 22:32:56 -0500 (EST) Cc: owilson@CAM.ORG, smp@csn.net, smp@FreeBSD.ORG, current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL31 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Jordan K. Hubbard said: > > Hi, > > > > How does one determine which are 'good dates' for downloading SMP > > source? > > You run it on your SMP hardware and decide when it's a good day. > At least that's how I do it. :) > Following up on what JKH says, SMP and -current are for developers, and users willing to do their own release mgmt and bugfixes. Generally, the various developers will notify the group when they feel especially good about the code, but otherwise, it is up to the individual -current users. -- John dyson@freebsd.org jdyson@nc.com From owner-freebsd-current Wed Dec 10 22:38:35 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id WAA09152 for current-outgoing; Wed, 10 Dec 1997 22:38:35 -0800 (PST) (envelope-from owner-freebsd-current) Received: from haywire.csuhayward.edu (bsampley@haywire.csuhayward.edu [134.154.5.50]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id WAA09146 for ; Wed, 10 Dec 1997 22:38:31 -0800 (PST) (envelope-from bsampley@haywire.csuhayward.edu) Received: from localhost by haywire.csuhayward.edu (SMI-8.6/SMI-SVR4) id WAA21335; Wed, 10 Dec 1997 22:43:59 -0800 Date: Wed, 10 Dec 1997 22:43:58 -0800 (PST) From: BURTON SAMPLEY To: "Louis A. Mamakos" cc: current Subject: Re: -current, goliath, smp -- problems In-Reply-To: <199712101507.KAA08420@whizzo.TransSys.COM> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Wed, 10 Dec 1997, Louis A. Mamakos wrote: > I understand that there are versions of the PPro CPU with 1MB of L2 > cache, specifically intended for the MP situation where memory bandwidth > is precious. I don't know how widely available these CPUs are. > > louie I've also heard of this cpu. I think they are available on the Compaq Proliant 7000 servers. I think you're also looking at about $5000.00 USD per cpu. Don't quote me on this, I could be wrong. - burton From owner-freebsd-current Thu Dec 11 00:00:26 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id AAA15007 for current-outgoing; Thu, 11 Dec 1997 00:00:26 -0800 (PST) (envelope-from owner-freebsd-current) Received: from mail.cdsnet.net (mail.cdsnet.net [204.118.244.5]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id AAA14996; Thu, 11 Dec 1997 00:00:18 -0800 (PST) (envelope-from mrcpu@cdsnet.net) Received: from mail.cdsnet.net (mail.cdsnet.net [204.118.244.5]) by mail.cdsnet.net (8.8.6/8.8.6) with SMTP id AAA29341; Thu, 11 Dec 1997 00:00:04 -0800 (PST) Date: Thu, 11 Dec 1997 00:00:04 -0800 (PST) From: Jaye Mathisen To: "Jordan K. Hubbard" cc: Oliver Wilson , Steve Passe , smp@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: Usable SMP on 971208 In-Reply-To: <24431.881809651@time.cdrom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Well, I follow a slightly different approach: 1) Pick a date X 2) Watch the mailing lists for screams of anguish for a period, call it Y. 3) At time Z=X+Y, if screaming has devolved to whimpering, upgrade to -current as of time X. 4) Y should be on the order of 10-14 days. I used to have a more complicated formula involving the analysis of the volumes of mail on smp, correlated with the # of postings by John or DG, subtract out the number of postings by DG involving network cards, add all the RCS version numbers together, and then correlate that whole mess with the number of postings by Doug White already answered in the FAQ, and when those two events when graphed with my crayola's and a sheet of graph paper were indistinguishable from the asymptote, and 8 planets lined up, then I installed. But it was taking longer to run the analysis than to do the backup/upgrade, and then finally the batteries in my HP48GX ran out, and I couldn't figure it all out anymore. And I ran out of Burnt Umber, and I hate to graph in Sienna. And it's late. And I need to go install -current, because everything seems in conjunction. I'll probably adopt Jordan's approach. :) On Wed, 10 Dec 1997, Jordan K. Hubbard wrote: > > Hi, > > > > How does one determine which are 'good dates' for downloading SMP > > source? > > You run it on your SMP hardware and decide when it's a good day. > At least that's how I do it. :) > > Jordan > From owner-freebsd-current Thu Dec 11 00:12:59 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id AAA15862 for current-outgoing; Thu, 11 Dec 1997 00:12:59 -0800 (PST) (envelope-from owner-freebsd-current) Received: from mail.cdsnet.net (mail.cdsnet.net [204.118.244.5]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id AAA15857 for ; Thu, 11 Dec 1997 00:12:54 -0800 (PST) (envelope-from mrcpu@cdsnet.net) Received: from mail.cdsnet.net (mail.cdsnet.net [204.118.244.5]) by mail.cdsnet.net (8.8.6/8.8.6) with SMTP id AAA00677; Thu, 11 Dec 1997 00:12:24 -0800 (PST) Date: Thu, 11 Dec 1997 00:12:24 -0800 (PST) From: Jaye Mathisen To: Jason Evans cc: Alex , Steve Passe , current Subject: Re: -current, goliath, smp -- problems In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Tue, 9 Dec 1997, Jason Evans wrote: > On Mon, 8 Dec 1997, Alex wrote: > in the neighborhood of 500 MB/sec, which is enough to feed 4 processors, > but quite inadequate for 8. So, even though there are twice as many > processors, the performance gain is not impressive. > > If there's anyone else out there that knows any better, please correct me. > =) While I can't correct you, I have a couple DEC ZX6000's, that when using the add-on memory boards, so there's something like 4GB of SIMMS, the memory path becomes 256bit wide, 4 way interleaved, and runs at some hellacious rate, and I remember the memory bandwidth being significantly higher than 500MB/s. Heck, if somebody knows of some memory benchmarking software, I'd be happy to try it out. From owner-freebsd-current Thu Dec 11 01:45:23 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id BAA25486 for current-outgoing; Thu, 11 Dec 1997 01:45:23 -0800 (PST) (envelope-from owner-freebsd-current) Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id BAA25478; Thu, 11 Dec 1997 01:45:17 -0800 (PST) (envelope-from jkh@time.cdrom.com) Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.7/8.6.9) with ESMTP id BAA25846; Thu, 11 Dec 1997 01:35:33 -0800 (PST) To: Jaye Mathisen cc: Oliver Wilson , Steve Passe , smp@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: Usable SMP on 971208 In-reply-to: Your message of "Thu, 11 Dec 1997 00:00:04 PST." Date: Thu, 11 Dec 1997 01:35:33 -0800 Message-ID: <25843.881832933@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > I'll probably adopt Jordan's approach. :) No! No! I was just about to say that I found yours to be far more elegant and I was thinking of trying it myself! :-) Jordan From owner-freebsd-current Thu Dec 11 02:02:28 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id CAA28019 for current-outgoing; Thu, 11 Dec 1997 02:02:28 -0800 (PST) (envelope-from owner-freebsd-current) Received: from mail.san.rr.com (ns.san.rr.com [204.210.0.1]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id CAA27983 for ; Thu, 11 Dec 1997 02:02:20 -0800 (PST) (envelope-from studded@san.rr.com) Received: (from studded@localhost) by mail.san.rr.com (8.8.7/8.8.8) id CAA05520; Thu, 11 Dec 1997 02:03:30 -0800 (PST) Message-Id: <199712111003.CAA05520@mail.san.rr.com> From: "Studded" To: "Jordan K. Hubbard" Cc: "Charlie Roots" , "freebsd-current@FreeBSD.ORG" Date: Thu, 11 Dec 97 02:01:14 -0800 Reply-To: "Studded" Priority: Normal X-Mailer: PMMail 1.95a For OS/2 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Subject: Re: FreeBSD-3.0 Current - utmp Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Tue, 09 Dec 1997 21:40:02 -0800, Jordan K. Hubbard wrote: >> FWIW, I've been running -Stable with 16 char usernames, and I >> appear to be getting some corruption in utmp. When I do 'last' it shows >> my 16 char name, but it also shows some weird high ascii characters. I >> deleted utmp and wtmp, and still have the same problems. > >You sure you recompiled *everything* in -stable with 16 character >usernames? I've seen people get bitten by both sshd and xterm, >forgetting that these optional packages also write utmp entries. :) D'oh! I knew about sshd, but when I went to check on xterm a while back I couldn't find the sources right off, so I lost track. I installed X developer, but looking it over now, I can't figure out where to get the sources for xterm, or anything else in the X distribution. Pointers welcome, :) Doug *** Proud operator, designer and maintainer of the world's largest *** Internet Relay Chat server. 4,297 clients and still growing. :-) *** Try spider.dal.net on ports 6662-4 (Powered by FreeBSD) *** Part of the DALnet IRC network *** From owner-freebsd-current Thu Dec 11 09:07:31 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id JAA26622 for current-outgoing; Thu, 11 Dec 1997 09:07:31 -0800 (PST) (envelope-from owner-freebsd-current) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id JAA26586 for ; Thu, 11 Dec 1997 09:07:20 -0800 (PST) (envelope-from bde@zeta.org.au) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.7/8.6.9) id DAA16579; Fri, 12 Dec 1997 03:59:07 +1100 Date: Fri, 12 Dec 1997 03:59:07 +1100 From: Bruce Evans Message-Id: <199712111659.DAA16579@godzilla.zeta.org.au> To: bde@zeta.org.au, rcarter@consys.com Subject: Re: xlock: caught signal 8 while running galaxy mode. Cc: freebsd-current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Long ago (2 months :-), Russell wrote: >}>to control the internal precision of arithmetic operations, >}>silly me. A lot of the debate on "Pure" java fp focuses on >}>the (unmodifiable) 80 bit internal representation of x87 operands >}>stored on the fp stack, but this flag apparently renders that >}>problem moot. Oddly, Sun has been >}>insisting that the only way to make x87 fp "Pure" is to store >}>the result of EVERY fp operation to main memory and read it >}>back in again. That way of course every arithmetic operation >}>gets performed with 53b precision operands. >}>Surely they know about this flag... no no I won't be cynical ;-) >} The C9x draft specifies pure behaviour. Values must be independent of whether they are represented in a (wide) register or in memory or calculated at compile time. In particular, implicit spills must not change the value. Explicit stores and loads must round to the precision of the storage type. In particular, casts and assignments must perform their specified conversion. I wrote: >}Neither way is completely pure - there are some problems with >}double rounding that could not possibly be fixed by running with >}64-bit precision and reducing to 53-bit precision by storing. >}I believe they aren't fixed by running with 53-bit precision >}either, at least for division - the FPU apparently first rounds >}to 64 bits. For transcendental functions, storing is the only >}way. A good referennce for the double rounding problem: David Goldberg Differences Among IEEE 754 Implementations http://www.validgh.com/goldberg/addendum.html 1997-10-26 >[lots deleted] >My original statement said there are "counterexamples" >to the general rule that more accuracy is better for >application codes. After a lot of thought and rereading >of papers in my archive I can think of only two, >very tiny, classes of codes that 53 bit precision >benefits more than 64bit precision (given identical >compuation costs). Those are test programs with bugs, >like paranoia, and iterative algorithms that require >a bit of noise to be coaxed to converge. Are there >more? At any rate, "counterexamples" was much too >charitable. These are probably the main examples. Goldberg gives some interesting ones. Bruce From owner-freebsd-current Thu Dec 11 09:41:06 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id JAA29557 for current-outgoing; Thu, 11 Dec 1997 09:41:06 -0800 (PST) (envelope-from owner-freebsd-current) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id JAA29545 for ; Thu, 11 Dec 1997 09:40:56 -0800 (PST) (envelope-from bde@zeta.org.au) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.7/8.6.9) id EAA17753; Fri, 12 Dec 1997 04:36:09 +1100 Date: Fri, 12 Dec 1997 04:36:09 +1100 From: Bruce Evans Message-Id: <199712111736.EAA17753@godzilla.zeta.org.au> To: bde@zeta.org.au, reilly@zeta.org.au Subject: Re: xlock: caught signal 8 while running galaxy mode. Cc: freebsd-current@FreeBSD.ORG, rcarter@consys.com Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk In old mail, Andrew wrote: >>>I recently tried to port some speech recognition code that runs fine on >>>two different DSPs, a Dec Alpha, a Sparc and a SCO Pentium box to my >>>FreeBSD machine. The HMM is expected to underflow all the time. In >>>the brief time I had available, I could not figure out how to stop the >>>FreeBSD maths from trapping at that point, and I couldn't write a trap >>>handler that would ignore the error and continue, so I gave up. So I wrote: >> Do you mean overflow? FreeBSD masks underflow, denormal and precision >> exceptions by default. > >I'm pretty sure it wasn't an overflow. I am not all that familiar with >the x87 instruction set, so I don't for sure what was happening. The >breakage was in a comparison (>) between a float in a register variable >with a float loaded from memory. This resulted in a SIGFPE >sometimes. That shouldn't trap unless one of the operands is a NaN. Traps occur on the FP instruction (usually immediately) following the one that set the exception bits, so a comparison may trigger a SIGFPE for a previous exception. >---time lapse--- > >In the interests of exactitude, and since I seem to have the >attention of people who really know about this sort of >thing, here is a bit of detail about this specific "bug". > >With the default FreeBSD maths environment (from a build >world on current 2.2 sources on 3rd September), and the C >program compiled in GCC with -g -Wall switches (only). > >No compiler warnings. > >(gdb) run -S call.lst >Starting program: xxx_ux -S call.lst >Call Setup. >RunUtterance(model:amt4.bin, speech:amt1.lin) > >Program received signal SIGFPE, Arithmetic exception. >0x4a8c in CalcU () at state.c:305 >305 if (s > *pMax) *pMax = s; > >[ register float s; register float *pMax; ] > >(gdb) p s >$1 = 5.46506401e-44 `p' can't handle variables in x87 registers. It prints the above value after `register float z; z = 1' here. I think it just doesn't know where the variables really are. Use `info float' to get more information. >(gdb) p *pMax >$2 = -32.9900398 >(gdb) disassemble >Dump of assembler code for function CalcU: >[elided] >0x4a76 : addl $0x4,%ecx >0x4a79 : movl (%edi),%esi >0x4a7b : movl %esi,0xffffffe8(%ebp) >0x4a7e : movl 0xffffffe8(%ebp),%eax >0x4a81 : fsts (%eax) >0x4a83 : addl $0x4,(%edi) >0x4a86 : addl $0x4,%edi >0x4a89 : movl 0xffffffe4(%ebp),%eax >0x4a8c : fcoms (%eax) >0x4a8e : fnstsw >0x4a90 : andb $0x45,%ah >0x4a93 : jne 0x4a9c >0x4a95 : movl 0xffffffe4(%ebp),%esi >0x4a98 : fstps (%esi) >0x4a9a : jmp 0x4a9e >0x4a9c : fstp %st(0) Not much to go wrong there. `info float' would show the (FPU) pc where the exception occurred (the next FP instruction causes the trap but it doesn't get executed, so the pc still points to the previous FP instruction. Bruce From owner-freebsd-current Thu Dec 11 10:15:08 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id KAA01709 for current-outgoing; Thu, 11 Dec 1997 10:15:08 -0800 (PST) (envelope-from owner-freebsd-current) Received: from consys.com (consys.com [209.60.202.194]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id KAA01696 for ; Thu, 11 Dec 1997 10:14:59 -0800 (PST) (envelope-from rcarter@consys.com) Received: from dnstoo.consys.com (dnstoo.ConSys.COM [209.60.202.195]) by consys.com (8.8.6/8.8.6) with ESMTP id LAA06694; Thu, 11 Dec 1997 11:13:02 -0700 (MST) Received: from dnstoo.consys.com (localhost [127.0.0.1]) by dnstoo.consys.com (8.8.8/8.8.6) with ESMTP id LAA06477; Thu, 11 Dec 1997 11:14:48 -0700 (MST) Message-Id: <199712111814.LAA06477@dnstoo.consys.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: Bruce Evans cc: freebsd-current@freebsd.org Subject: Re: xlock: caught signal 8 while running galaxy mode. In-reply-to: Your message of "Fri, 12 Dec 1997 03:59:07 +1100." <199712111659.DAA16579@godzilla.zeta.org.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 11 Dec 1997 11:14:48 -0700 From: "Russell L. Carter" Sender: owner-freebsd-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Referring to stuff I wrote so long ago I'd almost forgotten :-), Bruce observes: }The C9x draft specifies pure behaviour. Values must be independent }of whether they are represented in a (wide) register or in memory or }calculated at compile time. In particular, implicit spills must not }change the value. Explicit stores and loads must round to the precision }of the storage type. In particular, casts and assignments must perform }their specified conversion. Yes, and the implications for conforming x86 fp performance are large. Whereas the implications for non-conforming fp accuracy is insignificant at worst, and at best a useless exercise in trying to prostitute numerical mathematics to meet the requirements for a branding campaign, the value of same which is now getting resolved in court. } David Goldberg } Differences Among IEEE 754 Implementations } http://www.validgh.com/goldberg/addendum.html } 1997-10-26 } }>[lots deleted] } }>My original statement said there are "counterexamples" }>to the general rule that more accuracy is better for }>application codes. After a lot of thought and rereading }>of papers in my archive I can think of only two, }>very tiny, classes of codes that 53 bit precision }>benefits more than 64bit precision (given identical }>compuation costs). Those are test programs with bugs, }>like paranoia, and iterative algorithms that require }>a bit of noise to be coaxed to converge. Are there }>more? At any rate, "counterexamples" was much too }>charitable. } }These are probably the main examples. Goldberg gives some }interesting ones. And a numerical mathematician parses his argument as follows: 1. A numerical algorithm was devised for a particular floating point arithmetic. 2. Said algorithm fails on extended precision fp systems (such as x86) 3. => (therefore), the numerical mathematician should use a different algorithm on extended precision fp systems (such as x86). Which is different from a product based view that would have every algorithm behave the same on all possible architectures, and damn all other consequences... Now I'll let Goldberg (as apparently interpreted by David Hough) restate my issue for me: (quote taken from above reference) +Neither should these remarks suggest that all single/double systems +deliver identical numerical results. Diverse systems differ in +features not covered or anticipated by IEEE 754: math libraries contain +different implementations of the elementary functions, +not all systems provide correctly rounded binary/decimal conversions +throughout the range of each format they support, and +some processors provide a primitive operation to multiply two numbers +and add a third with just one rounding at the end. (This +operation, called a fused multiply-add, can foil the splitting +process of Theorem 6, yet it can also be used in a non-portable way +to perform multiple precision multiplication without the need for splitting.) +These factors contribute to produce different results from +one machine to another, too, though they are far less insidious than +indiscriminate and gratuitous use of extended precision. The upshot (restated from the last go around) is as long as we have runtime access to the fp rounding and extended precision modes, *and* the mods to make default fp behaviour do not significantly slow down the system (by less than 1% say) then uniform behaviour is ok. That's not what a "100% Pure" implementation of java (on x86) would imply. It would fail miserably both requirements. Anyway, I hope I'm not sounding too rancorous here, because I sure don't feel that way, and I appreciate the care with which you've worked on these issues, Bruce. Regards, Russell (for those who are interested but not familiar with the some of the background issues, long discussions over this stuff have been held for years on the numeric-interest and for a little while java-for-cse lists. And a quick perusal of David Hough's site shows an even worse anti x86 bias then I recalled (some nice reengineering of history there); interesting, since Kahan happens to disagree with most of the cross-platform assertions, c.f. 1997 SIAM General Meeting talk(#) (Hough was a student of Kahan...) aren't mathematicians fun ;-)) (#) http://nextra.msri.org/lecturenotes/97/SIAM/ From owner-freebsd-current Thu Dec 11 14:40:41 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id OAA21267 for current-outgoing; Thu, 11 Dec 1997 14:40:41 -0800 (PST) (envelope-from owner-freebsd-current) Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id OAA21247 for ; Thu, 11 Dec 1997 14:40:25 -0800 (PST) (envelope-from julian@whistle.com) Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by freefall.freebsd.org (8.8.6/8.8.5) with ESMTP id OAA04033 for ; Thu, 11 Dec 1997 14:38:22 -0800 (PST) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id OAA08836 for ; Thu, 11 Dec 1997 14:34:56 -0800 (PST) Received: from UNKNOWN(), claiming to be "current1.whistle.com" via SMTP by alpo.whistle.com, id smtpd008832; Thu Dec 11 14:34:49 1997 Message-ID: <349069EE.167EB0E7@whistle.com> Date: Thu, 11 Dec 1997 14:32:14 -0800 From: Julian Elischer Organization: Whistle Communications X-Mailer: Mozilla 3.0Gold (X11; I; FreeBSD 2.2-CURRENT i386) MIME-Version: 1.0 To: current@freebsd.com Subject: DEVFS testers needed Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Please please please, if you have a few spare cycles.... This is really a quite low-impact test. it shouldn't need to take much time.. (a kernel compile, a few patches, a few edits and a reboot) WARNING: Please do not test this if you: 1/ have REALLY OLD ESDI drives 2/ are using DOS extended partitions to hold filesystems (I think that excuses about 3 people) I have placed a copy of the needed patchfile on ftp://hub.freebsd.org/pub/scsi/slice3.tar.gz I am looking for more testers. The changes are COMPLETELY non-intrusive, by which I mean, If you do not define SLICE and DEVFS there are no changes in what is compiled from the present -current tree. All new code is marked #ifdef SLICE, or is in new files. I have included a sample config file SLICE. I have had positive tests from a couple of people but need a LOT wider testing.. What you need to do to be able to switch back and forth between norma and DEVFS kernels is limited to a small hack in the norma /dev. If you don't want to switch back this isn't needed :) first it depends on whether your boot device is 'dangerously dedicated' or not. if it is, there is nothing to do. if it is not, you need to go to the old /dev and do: ln -f /dev/sd0a /dev/sd0s1a (or the equivalent for your system) then: edit /etc/fstab and change all the 'shortcut' device names totheir long forms. (remember this is only for non-dangerously dedicated drives) reboot like this on your old kernel. it should still work. fix till it does. remember this is just nomenclature. Nothing physical should be changing except that link. build your DEVFS kernel. install as /kernel.slice. add the line: mount -t devfs devfs /dev >/dev/null 2>&1 to /etc/rc before the swapon -a reboot off the new kernel. let me know what happens :) julian From owner-freebsd-current Thu Dec 11 19:33:59 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id TAA10596 for current-outgoing; Thu, 11 Dec 1997 19:33:59 -0800 (PST) (envelope-from owner-freebsd-current) Received: from pluto.plutotech.com (mail.plutotech.com [206.168.67.137]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id TAA10575 for ; Thu, 11 Dec 1997 19:33:53 -0800 (PST) (envelope-from gibbs@plutotech.com) Received: from narnia.plutotech.com (narnia.plutotech.com [206.168.67.130]) by pluto.plutotech.com (8.8.7/8.8.5) with ESMTP id UAA27137 for ; Thu, 11 Dec 1997 20:33:51 -0700 (MST) Message-Id: <199712120333.UAA27137@pluto.plutotech.com> Date: Thu, 11 Dec 1997 20:32:02 -0700 From: "Justin T. Gibbs" Subject: CAM Update. Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk To: undisclosed-recipients:; ------- Blind-Carbon-Copy To: scsi@FreeBSD.org Subject: CAM Update. Date: Thu, 11 Dec 1997 20:32:02 -0700 From: "Justin T. Gibbs" I've uploaded a set of "incremental" diffs that will update a system running the 971209 snapshot to 971211. If you happen to be testing/using CAM, please drop me a line so I can find out what peripherals and adapters you have. For those of you using CAM on an SMP system, you might notice a few timeouts at boot time. It seems that in some systems the clock is running fast causing "bogus" timeouts. The system should recover from these timeouts and the boot proceed normally. Please let me know if that isn't the case for you. The 971211 snapshot includes the following changes: Tape Driver: The driver did not properly set the B_ERROR buffer flag when handling a defered EOF condition. This meant that the client would not see the residual. The driver now returns ENOSPC on writes that hit EOM. CDROM Driver: Correct a stupid logic bug that snuck in just before the last snapshot. This prevented CDROMs from being mounted. Aic7xxx Driver: Correct a bug that caused the driver to never renegotiate sync with wide targets after an automatic request sense. Needless to say, this killed performance. Don't use AAP to deal with the KERNEL_QINPOS scratch ram variable. There are occasions where the AAP write fails and the sequencer doesn't see a new entry in the input queue. Deal with "immediate resets" in the error recovery code correctly. These used to leave the controller queue in the frozen state so that no further I/O occured. XPT Layer: We now probe all device in parallel. This greatly increases the probe stage. The code already performed all device attachments in parallel. Snoop the device control page on devices that say they can perform tagged queuing. This allows us to read the DQUE flag indicating that tagged queuing is disabled on this target and avoid attempting any tagged I/O. Use cam_periph_error during device probes. In the past, the probe code bailed out on most errors. Fix a race condition that might allow a transaction to slip after a device queue or sim queue was placed into the frozen state. iostat: iostat will now report statistics for all CAM devices. It is far from it's final state though. Suggestions to ken@plutotech.com To apply the patches: cd /usr/src zcat cam-971211.incremental.diffs.gz | patch -p0 The patch may be obtain from: ftp://ftp.FreeBSD.org/pub/FreeBSD/cam/cam-971211.incremental.diffs.gz or ftp://ftp.kdm.org/pub/FreeBSD/cam/cam-971211.incremental.diffs.gz - -- Justin ------- End of Blind-Carbon-Copy From owner-freebsd-current Fri Dec 12 00:43:38 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id AAA03308 for current-outgoing; Fri, 12 Dec 1997 00:43:38 -0800 (PST) (envelope-from owner-freebsd-current) Received: from acroal.com (firewall0.acroal.com [209.24.61.154]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id AAA03302 for ; Fri, 12 Dec 1997 00:43:33 -0800 (PST) (envelope-from jamil@acroal.com) Received: from localhost (jamil@localhost) by acroal.com (8.8.8/8.8.7) with SMTP id AAA15056 for ; Fri, 12 Dec 1997 00:43:28 -0800 (PST) (envelope-from jamil@acroal.com) Date: Fri, 12 Dec 1997 00:43:28 -0800 (PST) From: "J. Weatherbee - Senior Systems Architect" To: freebsd-current@freebsd.org Subject: PPPD is core dumping on -current! Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I have tracked it down to this: if you put the option "auth" in your /etc/ppp/options file, pppd core dumps. Who is responsible for pppd? From owner-freebsd-current Fri Dec 12 01:32:39 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id BAA06290 for current-outgoing; Fri, 12 Dec 1997 01:32:39 -0800 (PST) (envelope-from owner-freebsd-current) Received: from dyson.iquest.net (dyson.iquest.net [198.70.144.127]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id BAA06285; Fri, 12 Dec 1997 01:32:33 -0800 (PST) (envelope-from toor@dyson.iquest.net) Received: (from root@localhost) by dyson.iquest.net (8.8.8/8.8.8) id EAA02722; Fri, 12 Dec 1997 04:32:15 -0500 (EST) (envelope-from toor) Message-Id: <199712120932.EAA02722@dyson.iquest.net> Subject: Re: Usable SMP on 971208 In-Reply-To: <25843.881832933@time.cdrom.com> from "Jordan K. Hubbard" at "Dec 11, 97 01:35:33 am" To: jkh@time.cdrom.com (Jordan K. Hubbard) Date: Fri, 12 Dec 1997 04:32:15 -0500 (EST) Cc: mrcpu@cdsnet.net, owilson@CAM.ORG, smp@csn.net, smp@FreeBSD.ORG, current@FreeBSD.ORG From: "John S. Dyson" Reply-To: dyson@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL31 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Jordan K. Hubbard said: > > I'll probably adopt Jordan's approach. :) > > No! No! I was just about to say that I found yours to be far more > elegant and I was thinking of trying it myself! :-) > Oh, I see -- make a CDROM first??? :-). -- John dyson@freebsd.org jdyson@nc.com From owner-freebsd-current Fri Dec 12 02:48:42 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id CAA10208 for current-outgoing; Fri, 12 Dec 1997 02:48:42 -0800 (PST) (envelope-from owner-freebsd-current) Received: from hydrogen.nike.efn.org (resnet.uoregon.edu [128.223.170.28]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id CAA10202 for ; Fri, 12 Dec 1997 02:48:34 -0800 (PST) (envelope-from gurney_j@efn.org) Received: (from jmg@localhost) by hydrogen.nike.efn.org (8.8.7/8.8.7) id CAA00834; Fri, 12 Dec 1997 02:48:23 -0800 (PST) Message-ID: <19971212024823.53946@hydrogen.nike.efn.org> Date: Fri, 12 Dec 1997 02:48:23 -0800 From: John-Mark Gurney To: "J. Weatherbee - Senior Systems Architect" Cc: freebsd-current@FreeBSD.ORG Subject: Re: PPPD is core dumping on -current! References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.69 In-Reply-To: ; from J. Weatherbee - Senior Systems Architect on Fri, Dec 12, 1997 at 12:43:28AM -0800 Reply-To: John-Mark Gurney Organization: Cu Networking X-Operating-System: FreeBSD 2.2.1-RELEASE i386 X-PGP-Fingerprint: B7 EC EF F8 AE ED A7 31 96 7A 22 B3 D8 56 36 F4 X-Files: The truth is out there X-URL: http://resnet.uoregon.edu/~gurney_j/ Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk J. Weatherbee - Senior Systems Architect scribbled this message on Dec 12: > I have tracked it down to this: if you put the option "auth" in your > /etc/ppp/options file, pppd core dumps. > > Who is responsible for pppd? well... Peter did the recient upgrade to 2.3.0, and I was going to help test these changes out as I normally use pppd... also, are you sure that auth in /etc/ppp/options is the ONLY cause? I just added auth to my (previously non-existant) /etc/ppp/options file on a -current box and I got: bash# echo auth > /etc/ppp/options bash# pppd pppd: peer authentication required but no suitable secret(s) found pppd: for authenticating any peer to us (boron.nike.efn.org) other than the need to remove some redundant newlines... I don't see a problem... now if I add a secret to the mix, it does core dump on me... I'm not sure when I can get to it... is there anyway you can debug the problem yourself?? the problem should solely be in the userland part of pppd... -- John-Mark Gurney Modem/FAX: +1 541 683 6954 Cu Networking Live in Peace, destroy Micro$oft, support free software, run FreeBSD From owner-freebsd-current Fri Dec 12 03:40:13 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id DAA13125 for current-outgoing; Fri, 12 Dec 1997 03:40:13 -0800 (PST) (envelope-from owner-freebsd-current) Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id DAA13120 for ; Fri, 12 Dec 1997 03:40:08 -0800 (PST) (envelope-from julian@whistle.com) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id DAA24724 for ; Fri, 12 Dec 1997 03:39:02 -0800 (PST) Received: from UNKNOWN(), claiming to be "current1.whistle.com" via SMTP by alpo.whistle.com, id smtpd024710; Fri Dec 12 03:38:54 1997 Date: Fri, 12 Dec 1997 03:36:18 -0800 (PST) From: Julian Elischer To: current@freebsd.org Subject: DEVFS: new sample code Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk After some feedback, I've made a new version: ftp://hub.freebsd.org/pub/scsi/slice4.tar.gz also, see teh readme for brief instructions. ftp://hub.freebsd.org/pub/scsi/README changes: * Disklabel probes can actually fail if there is no disklabel. * Debug messages at boot make a lot more sense. * Accidentally included (old) bad144 code ifdef'd out (I don't yet support that and the lowest level driver is definitly not the place to do that anyhow). Appologies to the previous testers, but there is no 'incremental upgrade'. You have to start with a virgin tree again to add the new patches. julian From owner-freebsd-current Fri Dec 12 09:51:19 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id JAA08612 for current-outgoing; Fri, 12 Dec 1997 09:51:19 -0800 (PST) (envelope-from owner-freebsd-current) Received: from rah.star-gate.com (rah.star-gate.com [204.188.121.18]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id JAA08601 for ; Fri, 12 Dec 1997 09:51:12 -0800 (PST) (envelope-from hasty@rah.star-gate.com) Received: from rah.star-gate.com (localhost.star-gate.com [127.0.0.1]) by rah.star-gate.com (8.8.8/8.8.8) with ESMTP id JAA02049 for ; Fri, 12 Dec 1997 09:51:02 -0800 (PST) (envelope-from hasty@rah.star-gate.com) Message-Id: <199712121751.JAA02049@rah.star-gate.com> X-Mailer: exmh version 2.0gamma 1/27/96 To: current@freebsd.org Subject: recent rtl changes... Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 12 Dec 1997 09:51:02 -0800 From: Amancio Hasty Sender: owner-freebsd-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I noticed that some of my programs started running out of memory for instance netscape and exmh. I got back in the old version of rtld and the system seems to be okay now. Will know for sure if rtld was triggering this symptom by the end of the day -- like if exmh stays up all day. Regards, Amancio From owner-freebsd-current Fri Dec 12 10:55:35 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id KAA14282 for current-outgoing; Fri, 12 Dec 1997 10:55:35 -0800 (PST) (envelope-from owner-freebsd-current) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id KAA14254 for ; Fri, 12 Dec 1997 10:55:18 -0800 (PST) (envelope-from bde@zeta.org.au) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.7/8.6.9) id FAA00920; Sat, 13 Dec 1997 05:37:52 +1100 Date: Sat, 13 Dec 1997 05:37:52 +1100 From: Bruce Evans Message-Id: <199712121837.FAA00920@godzilla.zeta.org.au> To: current@FreeBSD.ORG, julian@whistle.com Subject: Re: DEVFS: new sample code Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >changes: > * Disklabel probes can actually fail if there is no disklabel. > * Debug messages at boot make a lot more sense. > * Accidentally included (old) bad144 code ifdef'd out (I don't yet > support that and the lowest level driver is definitly not the place to > do that anyhow). Yes it is. dscheck() should clip the transfer at bad sector boundaries and somehow get called again if there is more to transfer. Bruce From owner-freebsd-current Fri Dec 12 11:11:46 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id LAA15394 for current-outgoing; Fri, 12 Dec 1997 11:11:46 -0800 (PST) (envelope-from owner-freebsd-current) Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id LAA15386 for ; Fri, 12 Dec 1997 11:11:37 -0800 (PST) (envelope-from julian@whistle.com) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id LAA04756; Fri, 12 Dec 1997 11:02:13 -0800 (PST) Received: from UNKNOWN(), claiming to be "current1.whistle.com" via SMTP by alpo.whistle.com, id smtpd004754; Fri Dec 12 11:02:09 1997 Date: Fri, 12 Dec 1997 10:59:32 -0800 (PST) From: Julian Elischer To: Bruce Evans cc: current@freebsd.org Subject: Re: DEVFS: new sample code In-Reply-To: <199712121837.FAA00920@godzilla.zeta.org.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Disclaimer: *this of course only applies to what I'm doing of course* It ain't going to get done there it's getting done in a layer just below, and in conjunction with, the disk label layer. The disklabel layer notices the bad144 flag and sticks the bad144 'wedge' below itself. the bad144 has no business being lower than that because it doesn't cover other slices. They may have their own badblock handlers. it CERTAINLY doesn't get to be in the disk driver because THAT only knows how to move blocks of data and how to propogate up error reports. I've CC'd "current" because this is an issue that I'd like others to comment on. On Sat, 13 Dec 1997, Bruce Evans wrote: > >changes: > > * Disklabel probes can actually fail if there is no disklabel. > > * Debug messages at boot make a lot more sense. > > * Accidentally included (old) bad144 code ifdef'd out (I don't yet > > support that and the lowest level driver is definitly not the place to > > do that anyhow). > > Yes it is. dscheck() should clip the transfer at bad sector boundaries > and somehow get called again if there is more to transfer. dscheck is no longer IN this code. dsxxx() functions are not used by this code. That's the whole point. To replace them with a more modular interface. > > Bruce > julian "help, help I'm being repressed" " Come see the violence inherrent in the system" -Monty Python and the Holy Grail- From owner-freebsd-current Fri Dec 12 11:14:47 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id LAA15828 for current-outgoing; Fri, 12 Dec 1997 11:14:47 -0800 (PST) (envelope-from owner-freebsd-current) Received: from korin.warman.org.pl (korin.nask.waw.pl [148.81.160.10]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id LAA15730 for ; Fri, 12 Dec 1997 11:14:06 -0800 (PST) (envelope-from abial@korin.warman.org.pl) Received: from localhost (abial@localhost) by korin.warman.org.pl (8.8.8/8.8.5) with SMTP id UAA21117 for ; Fri, 12 Dec 1997 20:16:19 +0100 (CET) Date: Fri, 12 Dec 1997 20:16:18 +0100 (CET) From: Andrzej Bialecki To: freebsd-current@freebsd.org Subject: JDK 1.1.3 and -current Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi! I'm trying to run Sun's JDK, Linux binary (I'd rather use kaffe, but for now its AWT is broken). And I can't make it work... well, partially, but in the most important part :-(( javac works OK, and produces valid bytecode. But when I try to run the VM (i.e. 'java MyClass') it dies right away the moment I start new thread. It prints out quite detailed internal state trace, so if anyone feels like inclined to help me with it, I could send it. This version uses something called 'green_threads' user-space thread library. I suspect it somehow badly interacts with our linux emulation or something... Can you think of any solution for it? TIA. Andrzej Bialecki ---------------------+--------------------------------------------------------- abial@warman.org.pl | if(halt_per_mth > 0) { fetch("http://www.freebsd.org") } Research & Academic | "Be open-minded, but don't let your brains to fall out." Network in Poland | All of the above (and more) is just my personal opinion. ---------------------+--------------------------------------------------------- From owner-freebsd-current Fri Dec 12 12:27:07 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id MAA21770 for current-outgoing; Fri, 12 Dec 1997 12:27:07 -0800 (PST) (envelope-from owner-freebsd-current) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id MAA21762 for ; Fri, 12 Dec 1997 12:26:59 -0800 (PST) (envelope-from bde@zeta.org.au) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.7/8.6.9) id HAA04091; Sat, 13 Dec 1997 07:23:28 +1100 Date: Sat, 13 Dec 1997 07:23:28 +1100 From: Bruce Evans Message-Id: <199712122023.HAA04091@godzilla.zeta.org.au> To: bde@zeta.org.au, julian@whistle.com Subject: Re: DEVFS: new sample code Cc: current@freebsd.org Sender: owner-freebsd-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >It ain't going to get done there it's getting done in a layer just below, >and in conjunction with, the disk label layer. The disklabel layer notices >the bad144 flag and sticks the bad144 'wedge' below itself. the bad144 has >no business being lower than that because it doesn't cover other slices. >They may have their own badblock handlers. > >it CERTAINLY doesn't get to be in the disk driver >because THAT only knows how to move blocks of data and >how to propogate up error reports. That's what I meant. In my code, the disklabel layer is below drivers because drivers call it. It doesn't actually handle bad144 because only one driver needed (wd) it so leaving the handling in that driver was good enough. >> > * Accidentally included (old) bad144 code ifdef'd out (I don't yet >> > support that and the lowest level driver is definitly not the place to >> > do that anyhow). >> >> Yes it is. dscheck() should clip the transfer at bad sector boundaries >> and somehow get called again if there is more to transfer. > >dscheck is no longer IN this code. dsxxx() functions are not used by this >code. That's the whole point. To replace them with a more modular >interface. I don't see any need to entirely replace them. Bruce From owner-freebsd-current Fri Dec 12 14:40:35 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id OAA01710 for current-outgoing; Fri, 12 Dec 1997 14:40:35 -0800 (PST) (envelope-from owner-freebsd-current) Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id OAA01698 for ; Fri, 12 Dec 1997 14:40:24 -0800 (PST) (envelope-from julian@whistle.com) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id OAA11526; Fri, 12 Dec 1997 14:30:28 -0800 (PST) Received: from UNKNOWN(), claiming to be "current1.whistle.com" via SMTP by alpo.whistle.com, id smtpd011502; Fri Dec 12 14:30:17 1997 Message-ID: <3491BA5B.41C67EA6@whistle.com> Date: Fri, 12 Dec 1997 14:27:39 -0800 From: Julian Elischer Organization: Whistle Communications X-Mailer: Mozilla 3.0Gold (X11; I; FreeBSD 2.2-CURRENT i386) MIME-Version: 1.0 To: Bruce Evans CC: current@freebsd.org Subject: Re: DEVFS: new sample code References: <199712122023.HAA04091@godzilla.zeta.org.au> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Bruce Evans wrote: > > > >code. That's the whole point. To replace them with a more modular > >interface. > > I don't see any need to entirely replace them. because they don't fit what I'm trying to do? The slice code you wrote is a great piece of optimsed level-collapsed work, but for what I want to do, it's too non-modular (integrated?) and the layers are collapsed too much for what I'm trying to achieve. The interfaces are different for each layer, (in fact there is no standard interface for them) and you need to know too much about what is below you.. there is too much layer crossing, and it's too much designed about the specifics of PC layouts. It doesn't fit with DEVFS well, (because it only looks at the slices at OPEN time leading to a chicken/egg problem)It has no support for handlers that can do striping or mirroring or raid, or for dynamicly growing slices. It has no support for recusive arbitrary partitionning, and it cannot easily be extended to handle other partitionning schemes, )e.g. MAC or SUN disks). It does not provide a usable framework for new modules (e.g. a reliability layer (or bad144 shim). The drivers know too much about slicing and require duplicated code. Now having said all that, It DOES do what it does do, very well. It's just that it was not designrd to do what I want to be able to do. (e.g. mount SUN disks, or do arbitrary slicing and recombination of disk arrays etc. The stuff I'm trying out is VERY EARLY code but is definitly beyond the 'proof of concept' stage. PHK has been working on something similar, and when I get the time to really understand his stuff (I'm still sorting out his user-level test framework from the actual code) I'm going to try integrate as many of his ideas as I can. SOmetimes it comes time for software to give way to a new better generation. e.g My SCSI code and thenew CAM scsi code. I'm not saying that my stuff WILL replace the dsxxx() code, but I at least want to try see if my ideas are feasable. > > Bruce From owner-freebsd-current Fri Dec 12 15:06:13 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id PAA03613 for current-outgoing; Fri, 12 Dec 1997 15:06:13 -0800 (PST) (envelope-from owner-freebsd-current) Received: from omnivax (skynet.ctr.columbia.edu [128.59.64.70]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id PAA03581 for ; Fri, 12 Dec 1997 15:05:53 -0800 (PST) (envelope-from wpaul@skynet.ctr.columbia.edu) Received: (from wpaul@localhost) by skynet.ctr.columbia.edu (8.6.12/8.6.9) id RAA08542; Fri, 12 Dec 1997 17:39:34 -0500 From: Bill Paul Message-Id: <199712122239.RAA08542@skynet.ctr.columbia.edu> Subject: mmap() + NFS problems persist To: current@freebsd.org, toor@dyson.iquest.net Date: Fri, 12 Dec 1997 17:39:32 -0500 (EST) X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-freebsd-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Yes, I'm still here. I'm still seeing problems with FreeBSD-current, mmap() and NFS. I've upgraded to a 3.0 SNAP from Dec, 9th and the trouble is still there. Again, there are two possible failure modes: in the first case, the process becomes wedged and unkillable with ps -alx showing wait channel to be "vmopar", and in the second case, the whole system wedges because nfs_bioread() gets caught in an endless loop. I've been trying to investigate the latter problem since it's more of a show-stopper, but my RPC clue isn't enough to help me understand the inner workings of the VM system, which I think is partly where the problem lies (inasmuch as it relates to NFS anyway). Within nfs_bioread(), there is a large do {} while(); loop, inside which you have the following code: switch (vp->v_type) { case VREG: nfsstats.biocache_reads++; lbn = uio->uio_offset / biosize; on = uio->uio_offset & (biosize - 1); not_readin = 1; [...] /* * If the block is in the cache and has the required data * in a valid region, just copy it out. * Otherwise, get the block and write back/read in, * as required. */ again: bufsize = biosize; if ((off_t)(lbn + 1) * biosize > np->n_size && (off_t)(lbn + 1) * biosize - np->n_size < biosize) { bufsize = np->n_size - lbn * biosize; bufsize = (bufsize + DEV_BSIZE - 1) & ~(DEV_BSIZE - 1); } bp = nfs_getcacheblk(vp, lbn, bufsize, p); if (!bp) return (EINTR); /* * If we are being called from nfs_getpages, we must * make sure the buffer is a vmio buffer. The vp will * already be setup for vmio but there may be some old * non-vmio buffers attached to it. */ if (getpages && !(bp->b_flags & B_VMIO)) { #ifdef DIAGNOSTIC printf("nfs_bioread: non vmio buf found, discarding\n"); #endif bp->b_flags |= B_NOCACHE; bp->b_flags |= B_INVAFTERWRITE; if (bp->b_dirtyend > 0) { if ((bp->b_flags & B_DELWRI) == 0) panic("nfsbioread"); if (VOP_BWRITE(bp) == EINTR) return (EINTR); } else brelse(bp); goto again; } if ((bp->b_flags & B_CACHE) == 0) { bp->b_flags |= B_READ; bp->b_flags &= ~(B_DONE | B_ERROR | B_INVAL); not_readin = 0; vfs_busy_pages(bp, 0); error = nfs_doio(bp, cred, p); if (error) { brelse(bp); return (error); } } if (bufsize > on) { n = min((unsigned)(bufsize - on), uio->uio_resid); } else { n = 0; } diff = np->n_size - uio->uio_offset; if (diff < n) n = diff; if (not_readin && n > 0) { if (on < bp->b_validoff || (on + n) > bp->b_validend) { bp->b_flags |= B_NOCACHE; bp->b_flags |= B_INVAFTERWRITE; if (bp->b_dirtyend > 0) { if ((bp->b_flags & B_DELWRI) == 0) panic("nfsbioread"); if (VOP_BWRITE(bp) == EINTR) return (EINTR); } else brelse(bp); goto again; <----- LOOPS HERE!! } } vp->v_lastr = lbn; diff = (on >= bp->b_validend) ? 0 : (bp->b_validend - on); if (diff < n) n = diff; break; case VLNK: [...] The spot labeled 'LOOPS HERE!!' is there the infinite loop happens. The code calls nfs_getcacheblk() to return the block from the mmap()ed file that is being faulted in, but it is not happy with the block that it gets, so branches back around to do the 'again' label which causes nfs_getcacheblk() to be called again, but it returns the same block which it doesn't like, and the cycle repeats. The buffer that is returned has bp_validoff == 0 and bp_validend == 4096. Also, bufsize == 8192 and uio_offset == 4096. The value for uio_offset makes sense based on the behavior of my program: the page fault happens when the program first crosses the boundary into the second 4096-byte page. However, each time nfs_getcacheblk() is called, it returns the same buffer with bp_validoff == 0 and bp_validend == 4096. These numbers are not what the code expects (I suppose bp->validend would need to be 8192), so it releases the block and tries again. Why it never gets the right block I don't know. To help debug this (I hope) I've slapped together the source for the program I have that wedges my system you can get it from: ftp.ctr.columbia.edu:/pub/misc/freebsd/mmap_locktest.tar.gz skynet.ctr.columbia.edu:/pub/freebsd/mmap_locktest.tar.gz freebsd.org:/home/wpaul/mmap_locktest.tar.gz This should compile standalone (i.e. without any other NIS+ cruft). Please excuse all the NIS+ headers. To reproduce the bug, do the following: - Configure a FreeBSD 3.0 host as an NFS client - Unpack the source code onto an NFS filesystem and type 'make.' This will build a program called (stupidly enough) 'foo.' - Run 'foo' several times. When you run it, you will see things like this: [/proj/mbone/nis/usr.sbin/nis_cachemgr/mmap_test]:mbone{217}% ./foo FSIZE: 8192 data SIZE 1044 truncating... mmaping... copying... unmapping ver: 2 FSIZE: 8192 data SIZE 1132 truncating... mmaping... copying... unmapping The first time you run 'foo' it will create a file in the current directory called 'test.' The program attempts to read and write data into this file via mmap(). Each time you run the program, 'SIZE' will increase. SIZE indicates the amount of data written into the mmap()ed region. After you run 'foo' enough times, 'SIZE' will approach 4096 bytes. Once SIZE gets to be just under 4096 bytes, run foo one more time, and the system will hang. At least, it does for me. Note that you have to run the program a few dozen times in succession to get it up to 4096 bytes. Again, what seems to happen is that the crossing into the next 4K page causes a page fault because the second 4K region isn't in core. This causes vm_fault() to eventually call into nfs_getpages(), which calls into nfs_bioread(), which gets all tied up in knots. Hopefully somebody besides me can duplicate this. Hey, wait: ampere runs 3.0-current... Uh-oh. I'm in trouble. Uhmm... could somebody reboot ampere? :( -Bill -- ============================================================================= -Bill Paul (212) 854-6020 | System Manager, Master of Unix-Fu Work: wpaul@ctr.columbia.edu | Center for Telecommunications Research Home: wpaul@skynet.ctr.columbia.edu | Columbia University, New York City ============================================================================= "It is not I who am crazy; it is I who am mad!" - Ren Hoek, "Space Madness" ============================================================================= From owner-freebsd-current Fri Dec 12 19:51:54 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id TAA21013 for current-outgoing; Fri, 12 Dec 1997 19:51:54 -0800 (PST) (envelope-from owner-freebsd-current) Received: from lamb.sas.com (root@lamb.sas.com [192.35.83.8]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id TAA21004 for ; Fri, 12 Dec 1997 19:51:47 -0800 (PST) (envelope-from jwd@unx.sas.com) Received: from mozart (wether.sas.com [192.35.83.7]) by lamb.sas.com (8.8.7/8.8.7) with SMTP id WAA16219 for ; Fri, 12 Dec 1997 22:51:45 -0500 (EST) Received: from iluvatar.unx.sas.com by mozart (5.65c/SAS/Domains/5-6-90) id AA28492; Fri, 12 Dec 1997 22:51:44 -0500 From: "John W. DeBoskey" Received: by iluvatar.unx.sas.com (5.65c/SAS/Generic 9.01/3-26-93) id AA10332; Fri, 12 Dec 1997 22:51:44 -0500 Message-Id: <199712130351.AA10332@iluvatar.unx.sas.com> Subject: sysinstall sd0 vs sd1 bug To: freebsd-current@freebsd.org Date: Fri, 12 Dec 1997 22:51:43 -0500 (EST) X-Mailer: ELM [version 2.4 PL23] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi, I beleive I've run into a rather nasty (and very annoying) bug in sysinstall. From a running system (on sd0), I enter sysinstall to do a system installation onto sd1 which is an already partitioned Jaz drive. (ie: an old SNAP which I can boot from). 1. Go to custom. 2. Enter partition (choose sd1) and 'q' 3. Enter label and mount pre-existing slices Mount / Newfs=y swap (not really mounted, but here) /var Newfs=y /usr Newfs=y and 'q' 4. Select distributions (All) and 'exit' 5. Select Media (NFS, multi-user & network already operational) 6. Commit. And the fun begins. The newfs process never executes (or it's failing very quickly with no error msgs). It then proceeds to download and install the system. Unfortunately, it puts them on sd0 instead of sd1. I did this twice, just to make sure I didn't do something wrong, and because I do so much enjoy restoring my system.. :-) (reconfig'ing since it does leave a bootable system on sd0). If I boot from the boot disk, everything works correctly. I'm using 3.0-971209-SNAP (running on the machine) and installing 3.0-971209-SNAP onto the Jaz disk. ie: no possible mis-matches. Any clues? ideas? Comments? I haven't looked at sysinstall closely yet.. Does it contain debugging hooks I can use to help identify the problem? (I did notice wizard mode, that's kind of slick.. :-) Thanks, John -- jwd@unx.sas.com (w) John W. De Boskey (919) 677-8000 x6915 From owner-freebsd-current Fri Dec 12 19:58:30 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id TAA21272 for current-outgoing; Fri, 12 Dec 1997 19:58:30 -0800 (PST) (envelope-from owner-freebsd-current) Received: from zippy.dyn.ml.org (garbanzo@haiti-107.ppp.hooked.net [206.169.228.107]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id TAA21260 for ; Fri, 12 Dec 1997 19:58:22 -0800 (PST) (envelope-from garbanzo@hooked.net) Received: from localhost (garbanzo@localhost) by zippy.dyn.ml.org (8.8.8/8.8.7) with SMTP id UAA17562 for ; Fri, 12 Dec 1997 20:00:44 -0800 (PST) X-Authentication-Warning: zippy.dyn.ml.org: garbanzo owned process doing -bs Date: Fri, 12 Dec 1997 20:00:44 -0800 (PST) From: Alex X-Sender: garbanzo@zippy.dyn.ml.org To: current Subject: ELF binaries Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I've seen some messages before about getting FreeBSD ELF support in the binutils, and a recent interest in egcs got me wondering. How hard would it be for the fbsd changes committed with the egcs stuff (so one can do dynamic libraries with egcs), or what kind of problems would I run into if I decided to grab a newer gnu binutils and use that? - alex From owner-freebsd-current Fri Dec 12 21:16:51 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id VAA24884 for current-outgoing; Fri, 12 Dec 1997 21:16:51 -0800 (PST) (envelope-from owner-freebsd-current) Received: from rah.star-gate.com (rah.star-gate.com [204.188.121.18]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id VAA24865 for ; Fri, 12 Dec 1997 21:16:37 -0800 (PST) (envelope-from hasty@rah.star-gate.com) Received: from rah.star-gate.com (localhost.star-gate.com [127.0.0.1]) by rah.star-gate.com (8.8.8/8.8.8) with ESMTP id VAA04208 for ; Fri, 12 Dec 1997 21:16:28 -0800 (PST) (envelope-from hasty@rah.star-gate.com) Message-Id: <199712130516.VAA04208@rah.star-gate.com> X-Mailer: exmh version 2.0gamma 1/27/96 To: current@FreeBSD.ORG Subject: Re: recent rtl changes... In-reply-to: Your message of "Fri, 12 Dec 1997 09:51:02 PST." <199712121751.JAA02049@rah.star-gate.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 12 Dec 1997 21:16:27 -0800 From: Amancio Hasty Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk No surprises over here today so I guess the culprit of processes running out of memory was rtld. Cheers, Amancio From owner-freebsd-current Sat Dec 13 00:08:51 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id AAA03827 for current-outgoing; Sat, 13 Dec 1997 00:08:51 -0800 (PST) (envelope-from owner-freebsd-current) Received: from home.dragondata.com (toasty@home.dragondata.com [204.137.237.2]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id AAA03792 for ; Sat, 13 Dec 1997 00:08:36 -0800 (PST) (envelope-from toasty@home.dragondata.com) Received: (from toasty@localhost) by home.dragondata.com (8.8.5/8.8.5) id CAA20468; Sat, 13 Dec 1997 02:08:27 -0600 (CST) From: Kevin Day Message-Id: <199712130808.CAA20468@home.dragondata.com> Subject: No more 'nfsd send error 55's! Yaaa! In-Reply-To: <24253.881808973@time.cdrom.com> from "Jordan K. Hubbard" at "Dec 10, 97 06:56:13 pm" To: jkh@time.cdrom.com (Jordan K. Hubbard) Date: Sat, 13 Dec 1997 02:08:27 -0600 (CST) Cc: freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL31 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk I grabbed the full sources today, and rebuilt... I can't make the 'nfsd send error 55' happen now... Before, opening elm or pine on a machine that had to load the /var/mail file via nfs would take 10+ minutes, and fill the console with 'nfsd send error 55'... That's gone now.. So, whoever fixed it, thanks... I'm not sure what fixed it, or when the fix was put in, since I don't see any nfs checkins recently, but I'm not going to argue. :) However, there's a new error randomly coming up: sendmail[19390]: NOQUEUE: SYSERR: putoutmsg (31.net10.nauticom.net): error on output channel sending "220 home.dragondata.com ESMTP Sendmail 8.8.5/8.8.5; Sat 13 Dec 1997 01:33:59 -0600 (CST)": Broken pipe sendmail[19390]: NOQUEUE: SYSERR: putoutmsg (31.net10.nauticom.net): error on output channel sending "250 home.dragondata.com Hello test@31.net10.nauticom.net [208.148.242.31], pleased to meet you": Broken pipe /kernel: pid 19390 (sendmail), uid 0: exited on signal 11 It's not major, just an interesting swap. :) Kevin From owner-freebsd-current Sat Dec 13 02:23:24 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id CAA11237 for current-outgoing; Sat, 13 Dec 1997 02:23:24 -0800 (PST) (envelope-from owner-freebsd-current) Received: from nlsystems.com (nlsys.demon.co.uk [158.152.125.33]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id CAA11228 for ; Sat, 13 Dec 1997 02:23:17 -0800 (PST) (envelope-from dfr@nlsystems.com) Received: from herring.nlsystems.com (herring.nlsystems.com [10.0.0.2]) by nlsystems.com (8.8.5/8.8.5) with SMTP id KAA00793; Sat, 13 Dec 1997 10:23:42 GMT Date: Sat, 13 Dec 1997 10:23:42 +0000 (GMT) From: Doug Rabson Reply-To: Doug Rabson To: Bill Paul cc: current@freebsd.org, toor@dyson.iquest.net Subject: Re: mmap() + NFS problems persist In-Reply-To: <199712122239.RAA08542@skynet.ctr.columbia.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Fri, 12 Dec 1997, Bill Paul wrote: > Yes, I'm still here. > > I'm still seeing problems with FreeBSD-current, mmap() and NFS. I've > upgraded to a 3.0 SNAP from Dec, 9th and the trouble is still there. > Again, there are two possible failure modes: in the first case, the > process becomes wedged and unkillable with ps -alx showing wait channel > to be "vmopar", and in the second case, the whole system wedges because > nfs_bioread() gets caught in an endless loop. > > I've been trying to investigate the latter problem since it's more of > a show-stopper, but my RPC clue isn't enough to help me understand the > inner workings of the VM system, which I think is partly where the > problem lies (inasmuch as it relates to NFS anyway). I think I understand what might be happening. I can't easily check since my FreeBSD hacking box is at work though. What I think happens is that when brelse is called in this code fragment, > if (not_readin && n > 0) { > if (on < bp->b_validoff || (on + n) > > bp->b_validend) { > bp->b_flags |= B_NOCACHE; > bp->b_flags |= B_INVAFTERWRITE; > if (bp->b_dirtyend > 0) { > if ((bp->b_flags & B_DELWRI) == 0) > panic("nfsbioread"); > if (VOP_BWRITE(bp) == EINTR) > return (EINTR); > } else > brelse(bp); > goto again; <----- LOOPS HERE!! the 8k buffer has exactly one VM page associated with it. The NFS code is attempting to throw the buffer away since it is only partially valid and it wants to read from the invalid section of the buf. It does this by setting the B_NOCACHE flag before calling brelse. Unfortunately the underlying VM page is still valid, so when getblk is called, the code in allocbuf which tracks down the underlying VM pages carefully resets b_validoff and b_validend causing the loop. Basically, the VMIO system has managed to ignore the NFS code's request for a cache flush, which the NFS code relied on to break the loop in nfs_bioread. As I see it, the problem can be fixed in two ways. The first would be for brelse() on a B_NOCACHE buffer to invalidate the VM pages in the buffer, restoring the old behaviour which NFS expected and the second would be to rewrite that section of the NFS client to cope differently with partially valid buffers. -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 951 1891 Fax: +44 181 381 1039 From owner-freebsd-current Sat Dec 13 05:05:16 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id FAA21993 for current-outgoing; Sat, 13 Dec 1997 05:05:16 -0800 (PST) (envelope-from owner-freebsd-current) Received: from frmug.org (frmug-gw.frmug.org [193.56.58.252]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id FAA21965 for ; Sat, 13 Dec 1997 05:04:52 -0800 (PST) (envelope-from pb@fasterix.frmug.org) Received: (from uucp@localhost) by frmug.org (8.8.8/frmug-2.1/nospam) with UUCP id OAA28527 for freebsd-current@freebsd.org; Sat, 13 Dec 1997 14:04:24 +0100 (CET) (envelope-from pb@fasterix.frmug.org) Received: (from pb@localhost) by fasterix.frmug.org (8.8.8/8.8.5/pb-19970302) id OAA02438; Sat, 13 Dec 1997 14:04:07 +0100 (CET) Message-ID: <19971213140407.LZ64565@@> Date: Sat, 13 Dec 1997 14:04:07 +0100 From: pb@fasterix.freenix.org (Pierre Beyssac) To: freebsd-current@freebsd.org Subject: panics when stopping pppd X-Mailer: Mutt 0.59.1e Mime-Version: 1.0 Sender: owner-freebsd-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I have a problem when using -current /usr/sbin/pppd, which panics the machine when pppd is killed at the end of the connection. It doesn't happen quite every time I try: I once killed pppd just after connecting and it didn't panic. It makes me think this might have to do with dynamic routes (I'm running gated to announce the route to my /28 subnet to the outside and receive several others /28 routes). I have no idea if this bug is recent or not, this machine was a FreeBSD 2.2.2 until yesterday. Here's the kernel stack trace (ctm patch 3166 or 3167). #3 0xf0190db4 in trap_pfault () #4 0xf0190a1f in trap () #5 0x6e655000 in ?? () #6 0xf014dd3c in in_ifadownkill () #7 0xf0147740 in rn_walktree () #8 0xf014dd80 in in_ifadown () #9 0xf015470b in rip_ctlinput () #10 0xf0123c2d in pfctlinput () #11 0xf013f3c9 in if_down () #12 0xf013f716 in ifioctl () #13 0xf011b39e in soo_ioctl () #14 0xf0118d43 in ioctl () #15 0xf01915b3 in syscall () The address in in_ifadownkill (0xf014dd3c) is the instruction just after the call to rtroute, which seems to indicate that the real culprit is rtroute: 0xf014dd35 : pushl $0x2 0xf014dd37 : call 0xf01482b0 0xf014dd3c : addl $0x18,%esp 0xf014dd3f : testl %eax,%eax I'm trying to investigate some more. I'll keep the crash dump in case anyone wants more details (registers or other). Here are the routes when I'm not connected: Destination Gateway Flags Refs Use Netif Expire 127 127.0.0.1 URc 0 0 lo0 127.0.0.1 127.0.0.1 UH 10 135 lo0 193.56.58.96/28 link#1 UC 0 0 Just after I connected: Destination Gateway Flags Refs Use Netif Expire default 193.56.58.33 UGSc 4 0 ppp0 127 127.0.0.1 URc 0 0 lo0 127.0.0.1 127.0.0.1 UH 10 136 lo0 193.56.58.33 193.56.58.97 UH 7 16 ppp0 193.56.58.96/28 link#1 UC 0 0 After gated receives the RIP announce for the other routes: Destination Gateway Flags Refs Use Netif Expire default 193.56.58.33 UGSc 3 0 ppp0 127 127.0.0.1 URc 0 0 lo0 127.0.0.1 127.0.0.1 UH 10 137 lo0 193.56.58.32/28 193.56.58.33 UGc 0 0 ppp0 193.56.58.33 193.56.58.97 UH 11 16 ppp0 193.56.58.48/28 193.56.58.33 UGc 0 0 ppp0 193.56.58.96/28 link#1 UC 0 0 193.56.58.112/28 193.56.58.33 UGc 0 0 ppp0 193.56.58.240/28 193.56.58.33 UGc 1 0 ppp0 -- Pierre Beyssac pb@fasterix.frmug.org pb@fasterix.freenix.org {Free,Net,Open}BSD, Linux : il y a moins bien, mais c'est plus cher Free domains: http://www.eu.org/ or mail dns-manager@EU.org From owner-freebsd-current Sat Dec 13 07:26:39 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id HAA28322 for current-outgoing; Sat, 13 Dec 1997 07:26:39 -0800 (PST) (envelope-from owner-freebsd-current) Received: from didda.est.is (ppp-21.est.is [194.144.208.121]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id HAA28313 for ; Sat, 13 Dec 1997 07:26:25 -0800 (PST) (envelope-from totii@est.is) Received: from est.is (didda.est.is [192.168.255.1]) by didda.est.is (8.8.7/8.8.7) with ESMTP id PAA00350; Sat, 13 Dec 1997 15:25:19 GMT (envelope-from totii@est.is) Message-ID: <3492A8DE.27B270DB@est.is> Date: Sat, 13 Dec 1997 15:25:18 +0000 From: "Þorður Ivarsson" X-Mailer: Mozilla 4.04 [en] (X11; I; FreeBSD 2.2.5-RELEASE i386) MIME-Version: 1.0 To: Pierre Beyssac CC: freebsd-current@FreeBSD.ORG Subject: Re: panics when stopping pppd References: <19971213140407.LZ64565@@> Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Pierre Beyssac wrote: > > I have a problem when using -current /usr/sbin/pppd, which panics > the machine when pppd is killed at the end of the connection. It > doesn't happen quite every time I try: I once killed pppd just > after connecting and it didn't panic. It makes me think this might > have to do with dynamic routes (I'm running gated to announce the > route to my /28 subnet to the outside and receive several others > /28 routes). > > I have no idea if this bug is recent or not, this machine was a > FreeBSD 2.2.2 until yesterday. > > Here's the kernel stack trace (ctm patch 3166 or 3167). > > #3 0xf0190db4 in trap_pfault () > #4 0xf0190a1f in trap () > #5 0x6e655000 in ?? () > #6 0xf014dd3c in in_ifadownkill () > #7 0xf0147740 in rn_walktree () > #8 0xf014dd80 in in_ifadown () > #9 0xf015470b in rip_ctlinput () > #10 0xf0123c2d in pfctlinput () > #11 0xf013f3c9 in if_down () > #12 0xf013f716 in ifioctl () > #13 0xf011b39e in soo_ioctl () > #14 0xf0118d43 in ioctl () > #15 0xf01915b3 in syscall () > > The address in in_ifadownkill (0xf014dd3c) is the instruction just > after the call to rtroute, which seems to indicate that the real > culprit is rtroute: > > 0xf014dd35 : pushl $0x2 > 0xf014dd37 : call 0xf01482b0 > 0xf014dd3c : addl $0x18,%esp > 0xf014dd3f : testl %eax,%eax > > I'm trying to investigate some more. I'll keep the crash dump in > case anyone wants more details (registers or other). > > Here are the routes when I'm not connected: > > Destination Gateway Flags Refs Use Netif Expire > 127 127.0.0.1 URc 0 0 lo0 > 127.0.0.1 127.0.0.1 UH 10 135 lo0 > 193.56.58.96/28 link#1 UC 0 0 > > Just after I connected: > > Destination Gateway Flags Refs Use Netif Expire > default 193.56.58.33 UGSc 4 0 ppp0 > 127 127.0.0.1 URc 0 0 lo0 > 127.0.0.1 127.0.0.1 UH 10 136 lo0 > 193.56.58.33 193.56.58.97 UH 7 16 ppp0 > 193.56.58.96/28 link#1 UC 0 0 > > After gated receives the RIP announce for the other routes: > > Destination Gateway Flags Refs Use Netif Expire > default 193.56.58.33 UGSc 3 0 ppp0 > 127 127.0.0.1 URc 0 0 lo0 > 127.0.0.1 127.0.0.1 UH 10 137 lo0 > 193.56.58.32/28 193.56.58.33 UGc 0 0 ppp0 > 193.56.58.33 193.56.58.97 UH 11 16 ppp0 > 193.56.58.48/28 193.56.58.33 UGc 0 0 ppp0 > 193.56.58.96/28 link#1 UC 0 0 > 193.56.58.112/28 193.56.58.33 UGc 0 0 ppp0 > 193.56.58.240/28 193.56.58.33 UGc 1 0 ppp0 > -- > Pierre Beyssac pb@fasterix.frmug.org pb@fasterix.freenix.org > {Free,Net,Open}BSD, Linux : il y a moins bien, mais c'est plus cher > Free domains: http://www.eu.org/ or mail dns-manager@EU.org This might have been in some installation of 2.1.X also. I remember problem I did notice more than two years ago I think, FreeBSD rebooting in disconnection of pppd. -- Þórður Ívarsson Thordur Ivarsson Rafeindavirki Electronic technician Norðurgötu 30 Nordurgotu 30 Box 309 Box 309 602 Akureyri 602 Akureyri Ísland Iceland --------------------------------------------- FreeBSD has good features, Some others are full of unwanted features! --------------------------------------------- From owner-freebsd-current Sat Dec 13 09:20:26 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id JAA03615 for current-outgoing; Sat, 13 Dec 1997 09:20:26 -0800 (PST) (envelope-from owner-freebsd-current) Received: from frmug.org (frmug-gw.frmug.org [193.56.58.252]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id JAA03595 for ; Sat, 13 Dec 1997 09:20:09 -0800 (PST) (envelope-from pb@fasterix.frmug.org) Received: (from uucp@localhost) by frmug.org (8.8.8/frmug-2.1/nospam) with UUCP id SAA27958 for freebsd-current@freebsd.org; Sat, 13 Dec 1997 18:20:06 +0100 (CET) (envelope-from pb@fasterix.frmug.org) Received: (from pb@localhost) by fasterix.frmug.org (8.8.8/8.8.5/pb-19970302) id SAA00647; Sat, 13 Dec 1997 18:18:09 +0100 (CET) Message-ID: <19971213181809.AU40295@@> Date: Sat, 13 Dec 1997 18:18:09 +0100 From: pb@fasterix.freenix.org (Pierre Beyssac) To: freebsd-current@freebsd.org Subject: small patch to fix MSG_COMPAT in recvfrom() X-Mailer: Mutt 0.59.1e Mime-Version: 1.0 Sender: owner-freebsd-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hello, Could someone check this and possibly commit it to -current if it is correct? It seems to fix a bug with orecvfrom() or recvfrom() called with the MSG_COMPAT flag on kernels compiled with the COMPAT_43 option. The symptom is that the fromaddr is not correctly returned. This affects the Linux emulator. I also have several other patches regarding the use of sockets by the Linux emulator, notably getsockopt(), raw sockets, and the IP_HDRINCL option which Linux handles differently from BSD in a subtle way. It allows me to run Linux ping, traceroute, and other small network "utilities" compiled on Linux such as teardrop. Should I send these patches to the list or to the Linux emulator maintainer? --- /sys/kern/uipc_syscalls.c.orig Tue Dec 9 01:42:58 1997 +++ /sys/kern/uipc_syscalls.c Sat Dec 13 18:05:46 1997 @@ -699,17 +699,18 @@ len = mp->msg_namelen; if (len <= 0 || fromsa == 0) len = 0; else { +#ifndef MIN +#define MIN(a,b) ((a)>(b)?(b):(a)) +#endif + /* save sa_len before it is destroyed by MSG_COMPAT */ + len = MIN(len, fromsa->sa_len); #ifdef COMPAT_OLDSOCK if (mp->msg_flags & MSG_COMPAT) ((struct osockaddr *)fromsa)->sa_family = fromsa->sa_family; #endif -#ifndef MIN -#define MIN(a,b) ((a)>(b)?(b):(a)) -#endif - len = MIN(len, fromsa->sa_len); error = copyout(fromsa, (caddr_t)mp->msg_name, (unsigned)len); if (error) goto out; -- Pierre Beyssac pb@fasterix.frmug.org pb@fasterix.freenix.org {Free,Net,Open}BSD, Linux : il y a moins bien, mais c'est plus cher Free domains: http://www.eu.org/ or mail dns-manager@EU.org From owner-freebsd-current Sat Dec 13 11:30:09 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id LAA09544 for current-outgoing; Sat, 13 Dec 1997 11:30:09 -0800 (PST) (envelope-from owner-freebsd-current) Received: from zed.ludd.luth.se (zed.ludd.luth.se [130.240.16.33]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id LAA09539 for ; Sat, 13 Dec 1997 11:30:01 -0800 (PST) (envelope-from gozer@ludd.luth.se) Received: from brother.ludd.luth.se (gozer@brother.ludd.luth.se [130.240.16.78]) by zed.ludd.luth.se (8.8.5/8.8.5) with SMTP id UAA06605; Sat, 13 Dec 1997 20:29:49 +0100 Date: Sat, 13 Dec 1997 20:29:48 +0100 (MET) From: Johan Larsson To: Pierre Beyssac cc: freebsd-current@FreeBSD.ORG Subject: Re: small patch to fix MSG_COMPAT in recvfrom() In-Reply-To: <19971213181809.AU40295@@> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk YES! Thank you soooo much. This solved the problem i've had with WordPerfect (long++ startup time), and rvplayer now works like a charm (well, the best it can do ;). I haven't had time to check anything else, but this should be commited yesterday ;) (if there's no major faults in it :) Johan On Sat, 13 Dec 1997, Pierre Beyssac wrote: > Hello, > > Could someone check this and possibly commit it to -current if it > is correct? > > It seems to fix a bug with orecvfrom() or recvfrom() called with > the MSG_COMPAT flag on kernels compiled with the COMPAT_43 option. > The symptom is that the fromaddr is not correctly returned. > > This affects the Linux emulator. > > I also have several other patches regarding the use of sockets by > the Linux emulator, notably getsockopt(), raw sockets, and the > IP_HDRINCL option which Linux handles differently from BSD in a > subtle way. It allows me to run Linux ping, traceroute, and other > small network "utilities" compiled on Linux such as teardrop. > Should I send these patches to the list or to the Linux emulator > maintainer? > > --- /sys/kern/uipc_syscalls.c.orig Tue Dec 9 01:42:58 1997 > +++ /sys/kern/uipc_syscalls.c Sat Dec 13 18:05:46 1997 > @@ -699,17 +699,18 @@ > len = mp->msg_namelen; > if (len <= 0 || fromsa == 0) > len = 0; > else { > +#ifndef MIN > +#define MIN(a,b) ((a)>(b)?(b):(a)) > +#endif > + /* save sa_len before it is destroyed by MSG_COMPAT */ > + len = MIN(len, fromsa->sa_len); > #ifdef COMPAT_OLDSOCK > if (mp->msg_flags & MSG_COMPAT) > ((struct osockaddr *)fromsa)->sa_family = > fromsa->sa_family; > #endif > -#ifndef MIN > -#define MIN(a,b) ((a)>(b)?(b):(a)) > -#endif > - len = MIN(len, fromsa->sa_len); > error = copyout(fromsa, > (caddr_t)mp->msg_name, (unsigned)len); > if (error) > goto out; > -- > Pierre Beyssac pb@fasterix.frmug.org pb@fasterix.freenix.org > {Free,Net,Open}BSD, Linux : il y a moins bien, mais c'est plus cher > Free domains: http://www.eu.org/ or mail dns-manager@EU.org > > -- * mailto:gozer@ludd.luth.se * http://www.ludd.luth.se/users/gozer/ * * Powered by FreeBSD. http://www.se.freebsd.org/ +-+-+-+-+-+-+-+-+ * From owner-freebsd-current Sat Dec 13 12:04:05 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id MAA11380 for current-outgoing; Sat, 13 Dec 1997 12:04:05 -0800 (PST) (envelope-from owner-freebsd-current) Received: from netserv.com.br (server.netserv.com.br [200.230.41.10]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id MAA11355 for ; Sat, 13 Dec 1997 12:03:49 -0800 (PST) (envelope-from rromero@netfriendly.com) Received: by netserv.com.br from localhost (router,SLMail V2.6); Sat, 13 Dec 1997 16:56:36 -0200 Received: by netserv.com.br from netfriendly.com (200.230.141.40::mail daemon; unverified,SLMail V2.6); Sat, 13 Dec 1997 16:56:35 -0200 Message-ID: <3492EAA1.92E1A69C@netfriendly.com> Date: Sat, 13 Dec 1997 18:05:53 -0200 From: Ricardo Romero Organization: NetFriendly Solucoes em Conectividade Ltda. X-Mailer: Mozilla 4.04 [en] (Win95; I) MIME-Version: 1.0 To: freebsd-current@freebsd.org Subject: subscribe Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk subscribe From owner-freebsd-current Sat Dec 13 12:10:24 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id MAA11866 for current-outgoing; Sat, 13 Dec 1997 12:10:24 -0800 (PST) (envelope-from owner-freebsd-current) Received: from rah.star-gate.com (rah.star-gate.com [204.188.121.18]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id MAA11859 for ; Sat, 13 Dec 1997 12:10:17 -0800 (PST) (envelope-from hasty@rah.star-gate.com) Received: from rah.star-gate.com (localhost.star-gate.com [127.0.0.1]) by rah.star-gate.com (8.8.8/8.8.8) with ESMTP id MAA00640; Sat, 13 Dec 1997 12:09:15 -0800 (PST) (envelope-from hasty@rah.star-gate.com) Message-Id: <199712132009.MAA00640@rah.star-gate.com> X-Mailer: exmh version 2.0gamma 1/27/96 To: pb@fasterix.freenix.org (Pierre Beyssac) cc: freebsd-current@FreeBSD.ORG Subject: Re: small patch to fix MSG_COMPAT in recvfrom() In-reply-to: Your message of "Sat, 13 Dec 1997 18:18:09 +0100." <19971213181809.AU40295@@> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 13 Dec 1997 12:09:15 -0800 From: Amancio Hasty Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk If you don't mind please post the patches to the list it will allow others to review them and test them. Tnks! Amancio From owner-freebsd-current Sat Dec 13 12:46:53 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id MAA13721 for current-outgoing; Sat, 13 Dec 1997 12:46:53 -0800 (PST) (envelope-from owner-freebsd-current) Received: from austin.polstra.com (austin.polstra.com [206.213.73.10]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id MAA13713 for ; Sat, 13 Dec 1997 12:46:40 -0800 (PST) (envelope-from jdp@austin.polstra.com) Received: from austin.polstra.com (jdp@localhost) by austin.polstra.com (8.8.8/8.8.7) with ESMTP id MAA13651; Sat, 13 Dec 1997 12:46:37 -0800 (PST) (envelope-from jdp) Message-Id: <199712132046.MAA13651@austin.polstra.com> To: gurney_j@resnet.uoregon.edu Subject: Re: PPPD is core dumping on -current! In-Reply-To: <19971212024823.53946@hydrogen.nike.efn.org> References: <19971212024823.53946@hydrogen.nike.efn.org> Organization: Polstra & Co., Seattle, WA Cc: current@freebsd.org Date: Sat, 13 Dec 1997 12:46:37 -0800 From: John Polstra Sender: owner-freebsd-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk In article <19971212024823.53946@hydrogen.nike.efn.org>, John-Mark Gurney wrote: > J. Weatherbee - Senior Systems Architect scribbled this message on Dec 12: > > I have tracked it down to this: if you put the option "auth" in your > > /etc/ppp/options file, pppd core dumps. I committed the fix for this last night. John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Self-knowledge is always bad news." -- John Barth From owner-freebsd-current Sat Dec 13 13:51:14 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id NAA17907 for current-outgoing; Sat, 13 Dec 1997 13:51:14 -0800 (PST) (envelope-from owner-freebsd-current) Received: from smtp03.primenet.com (smtp03.primenet.com [206.165.6.133]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id NAA17894 for ; Sat, 13 Dec 1997 13:51:07 -0800 (PST) (envelope-from tlambert@usr06.primenet.com) Received: (from daemon@localhost) by smtp03.primenet.com (8.8.8/8.8.8) id PAA26771; Sat, 13 Dec 1997 15:03:55 -0700 (MST) Received: from usr06.primenet.com(206.165.6.206) via SMTP by smtp03.primenet.com, id smtpd026767; Sat Dec 13 15:03:51 1997 Received: (from tlambert@localhost) by usr06.primenet.com (8.8.5/8.8.5) id OAA03369; Sat, 13 Dec 1997 14:50:21 -0700 (MST) From: Terry Lambert Message-Id: <199712132150.OAA03369@usr06.primenet.com> Subject: Re: panics when stopping pppd To: totii@est.is (?or?ur Ivarsson) Date: Sat, 13 Dec 1997 21:50:21 +0000 (GMT) Cc: pb@fasterix.freenix.org, freebsd-current@FreeBSD.ORG In-Reply-To: <3492A8DE.27B270DB@est.is> from "?or?ur Ivarsson" at Dec 13, 97 03:25:18 pm X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > I have a problem when using -current /usr/sbin/pppd, which panics > > the machine when pppd is killed at the end of the connection. It > > doesn't happen quite every time I try: I once killed pppd just > > after connecting and it didn't panic. It makes me think this might > > have to do with dynamic routes (I'm running gated to announce the > > route to my /28 subnet to the outside and receive several others > > /28 routes). > > > > I have no idea if this bug is recent or not, this machine was a > > FreeBSD 2.2.2 until yesterday. > > > > Here's the kernel stack trace (ctm patch 3166 or 3167). > > > > #3 0xf0190db4 in trap_pfault () > > #4 0xf0190a1f in trap () > > #5 0x6e655000 in ?? () > > #6 0xf014dd3c in in_ifadownkill () > > #7 0xf0147740 in rn_walktree () > > #8 0xf014dd80 in in_ifadown () > > #9 0xf015470b in rip_ctlinput () > > #10 0xf0123c2d in pfctlinput () > > #11 0xf013f3c9 in if_down () > > #12 0xf013f716 in ifioctl () > > #13 0xf011b39e in soo_ioctl () > > #14 0xf0118d43 in ioctl () > > #15 0xf01915b3 in syscall () If you have a local ethernet, look at the variables that exist on your stack to see if your local ethernet MAC address is there somewhere; this looks remarkably similar to a crash I saw, but have not yet been able to reproduce. The crash resulted from some code somewhere writing a remote MAC address, a local MAC addres, 0x8000, and a length of 0x20 (and an invalid family -- 0xff) -- basically, a struct sockaddr -- to my kernel stack. The current hypothesis is that something is writing a sockaddr at interrupt time; this is a machine using the if_ed.c driver, but it looks to be in the ARP or routing code. Maybe it finally shot its own foot off by writing the sockaddr to the wrong place, so it wasn't there when it needed it? Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-current Sat Dec 13 14:32:19 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id OAA20335 for current-outgoing; Sat, 13 Dec 1997 14:32:19 -0800 (PST) (envelope-from owner-freebsd-current) Received: from austin.polstra.com (austin.polstra.com [206.213.73.10]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id OAA20321 for ; Sat, 13 Dec 1997 14:32:13 -0800 (PST) (envelope-from jdp@austin.polstra.com) Received: from austin.polstra.com (jdp@localhost) by austin.polstra.com (8.8.8/8.8.7) with ESMTP id OAA14089; Sat, 13 Dec 1997 14:32:10 -0800 (PST) (envelope-from jdp) Message-Id: <199712132232.OAA14089@austin.polstra.com> To: hasty@rah.star-gate.com Subject: Re: recent rtl changes... In-Reply-To: <199712121751.JAA02049@rah.star-gate.com> References: <199712121751.JAA02049@rah.star-gate.com> Organization: Polstra & Co., Seattle, WA Cc: current@freebsd.org Date: Sat, 13 Dec 1997 14:32:09 -0800 From: John Polstra Sender: owner-freebsd-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk In article <199712121751.JAA02049@rah.star-gate.com>, Amancio Hasty wrote: > I noticed that some of my programs started running out of memory for > instance netscape and exmh. I got back in the old version of > rtld and the system seems to be okay now. More details, please. Which version of exmh? Was it running out of memory because it grew too large and hit the resource limit, or because it simply decided it was out of memory? How long did it take before it ran out? John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Self-knowledge is always bad news." -- John Barth From owner-freebsd-current Sat Dec 13 15:02:30 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id PAA22019 for current-outgoing; Sat, 13 Dec 1997 15:02:30 -0800 (PST) (envelope-from owner-freebsd-current) Received: from rah.star-gate.com (rah.star-gate.com [204.188.121.18]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id PAA22011 for ; Sat, 13 Dec 1997 15:02:22 -0800 (PST) (envelope-from hasty@rah.star-gate.com) Received: from rah.star-gate.com (localhost.star-gate.com [127.0.0.1]) by rah.star-gate.com (8.8.8/8.8.8) with ESMTP id PAA07172; Sat, 13 Dec 1997 15:02:17 -0800 (PST) (envelope-from hasty@rah.star-gate.com) Message-Id: <199712132302.PAA07172@rah.star-gate.com> X-Mailer: exmh version 2.0gamma 1/27/96 To: John Polstra cc: current@freebsd.org Subject: Re: recent rtl changes... In-reply-to: Your message of "Sat, 13 Dec 1997 14:32:09 PST." <199712132232.OAA14089@austin.polstra.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 13 Dec 1997 15:02:17 -0800 From: Amancio Hasty Sender: owner-freebsd-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I was hoping that others on the list would noticed the behavior if not then don't worry about it . Regards, Amancio > In article <199712121751.JAA02049@rah.star-gate.com>, > Amancio Hasty wrote: > > > I noticed that some of my programs started running out of memory for > > instance netscape and exmh. I got back in the old version of > > rtld and the system seems to be okay now. > > More details, please. Which version of exmh? Was it running out > of memory because it grew too large and hit the resource limit, or > because it simply decided it was out of memory? How long did it take > before it ran out? > > John > -- > John Polstra jdp@polstra.com > John D. Polstra & Co., Inc. Seattle, Washington USA > "Self-knowledge is always bad news." -- John Barth From owner-freebsd-current Sat Dec 13 15:07:11 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id PAA22266 for current-outgoing; Sat, 13 Dec 1997 15:07:11 -0800 (PST) (envelope-from owner-freebsd-current) Received: from frmug.org (frmug-gw.frmug.org [193.56.58.252]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id PAA22244 for ; Sat, 13 Dec 1997 15:06:53 -0800 (PST) (envelope-from pb@fasterix.frmug.org) Received: (from uucp@localhost) by frmug.org (8.8.8/frmug-2.1/nospam) with UUCP id AAA09258; Sun, 14 Dec 1997 00:06:10 +0100 (CET) (envelope-from pb@fasterix.frmug.org) Received: (from pb@localhost) by fasterix.frmug.org (8.8.8/8.8.5/pb-19970302) id AAA27183; Sun, 14 Dec 1997 00:02:43 +0100 (CET) Message-ID: <19971214000243.EA63641@@> Date: Sun, 14 Dec 1997 00:02:43 +0100 From: pb@fasterix.freenix.org (Pierre Beyssac) To: hasty@rah.star-gate.com (Amancio Hasty) Cc: freebsd-current@FreeBSD.ORG Subject: Re: small patch to fix MSG_COMPAT in recvfrom() References: <19971213181809.AU40295@@> <199712132009.MAA00640@rah.star-gate.com> X-Mailer: Mutt 0.59.1e Mime-Version: 1.0 In-Reply-To: <199712132009.MAA00640@rah.star-gate.com>; from Amancio Hasty on Dec 13, 1997 12:09:15 -0800 Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Amancio Hasty writes: > If you don't mind please post the patches to the list it will allow others > to review them and test them. Ok, here they are. They implement the following: - emulate Linux IP_HDRINCL behaviour in sendto(): byte order fixed Note that we do an extra getsockopt() on every sendto() to check if the option is set because we don't keep state in the emulator code. Is there a better way to implement this? - correct a bug (value of "name" not passed) with getsockopt() (see last hunk) I have a slightly different version (fewer comments and messier code ;-)) of the IP_HDRINCL fix adapted to 2.2.5 with the int *retval stuff everywhere, but I suppose there's too much new code for it to be included in -stable. OTOH the getsockopt() fix is only one line and can probably go into -stable, though it's not much use without the HDRINCL stuff. There may be other patches to come for recvfrom() (possibly the same problem as sendto() with the byte order on ip_len and ip_off on received packets, I haven't been able to check this yet). I'd also hope to emulate Linux "snoop" sockets (the equivalent of bpf) but I'm not yet sure it's very easy... For the anecdote, I hacked this code after I got tired porting Linux raw IP code to BSD again and again because of those incompatible Linux network includes. After I told my boss it would be a good idea to convert our FreeBSD network testing box to a Linux box for that very reason, I regretted this and decided it was way better to improve the Linux emulator instead :-) --- linux_socket.c.orig Tue Dec 9 01:42:58 1997 +++ linux_socket.c Sat Dec 13 23:32:15 1997 @@ -31,16 +31,20 @@ /* XXX we use functions that might not exist. */ #define COMPAT_43 1 #include +#include #include #include #include #include +#include +#include #include #include +#include static int linux_to_bsd_domain(int domain) { @@ -92,8 +96,9 @@ return IP_ADD_MEMBERSHIP; case LINUX_IP_DROP_MEMBERSHIP: return IP_DROP_MEMBERSHIP; case LINUX_IP_HDRINCL: + return IP_HDRINCL; default: return -1; } } @@ -130,8 +135,111 @@ return -1; } } +/* Return 0 if IP_HDRINCL is set of the given socket, not 0 otherwise */ +static int +linux_check_hdrincl(struct proc *p, int s) +{ + struct getsockopt_args /* { + int s; + int level; + int name; + caddr_t val; + int *avalsize; + } */ bsd_args; + int error; + caddr_t sg, val, valsize; + int size_val = sizeof val; + int optval; + + sg = stackgap_init(); + val = stackgap_alloc(&sg, sizeof(int)); + valsize = stackgap_alloc(&sg, sizeof(int)); + + if ((error=copyout(&size_val, valsize, sizeof(size_val)))) + return error; + bsd_args.s = s; + bsd_args.level = IPPROTO_IP; + bsd_args.name = IP_HDRINCL; + bsd_args.val = val; + bsd_args.avalsize = (int *)valsize; + if ((error=getsockopt(p, &bsd_args))) + return error; + if ((error=copyin(val, &optval, sizeof(optval)))) + return error; + return optval == 0; +} + +/* + * Updated sendto() when IP_HDRINCL is set: + * tweak endian-dependent fields in the IP packet. + */ +static int +linux_sendto_hdrincl(struct proc *p, struct sendto_args *bsd_args) +{ +/* + * linux_ip_copysize defines how many bytes we should copy + * from the beginning of the IP packet before we customize it for BSD. + * It should include all the fields we modify (ip_len and ip_off) + * and be as small as possible to minimize copying overhead. + */ +#define linux_ip_copysize 8 + + caddr_t sg; + struct ip *packet; + struct msghdr *msg; + struct iovec *iov; + + int error; + struct sendmsg_args /* { + int s; + caddr_t msg; + int flags; + } */ sendmsg_args; + + /* Check the packet isn't too small before we mess with it */ + if (bsd_args->len < linux_ip_copysize) + return EINVAL; + + /* + * Tweaking the user buffer in place would be bad manners. + * We create a corrected IP header with just the needed length, + * then use an iovec to glue it to the rest of the user packet + * when calling sendmsg(). + */ + sg = stackgap_init(); + packet = (struct ip *)stackgap_alloc(&sg, linux_ip_copysize); + msg = (struct msghdr *)stackgap_alloc(&sg, sizeof(*msg)); + iov = (struct iovec *)stackgap_alloc(&sg, sizeof(*iov)*2); + + /* Make a copy of the beginning of the packet to be sent */ + if ((error = copyin(bsd_args->buf, (caddr_t)packet, linux_ip_copysize))) + return error; + + /* Convert fields from Linux to BSD raw IP socket format */ + packet->ip_len = bsd_args->len; + packet->ip_off = ntohs(packet->ip_off); + + /* Prepare the msghdr and iovec structures describing the new packet */ + msg->msg_name = bsd_args->to; + msg->msg_namelen = bsd_args->tolen; + msg->msg_iov = iov; + msg->msg_iovlen = 2; + msg->msg_control = NULL; + msg->msg_controllen = 0; + msg->msg_flags = 0; + iov[0].iov_base = (char *)packet; + iov[0].iov_len = linux_ip_copysize; + iov[1].iov_base = (char *)(bsd_args->buf) + linux_ip_copysize; + iov[1].iov_len = bsd_args->len - linux_ip_copysize; + + sendmsg_args.s = bsd_args->s; + sendmsg_args.msg = (caddr_t)msg; + sendmsg_args.flags = bsd_args->flags; + return sendmsg(p, &sendmsg_args); +} + struct linux_socket_args { int domain; int type; int protocol; @@ -146,17 +254,48 @@ int type; int protocol; } */ bsd_args; int error; + int retval_socket; if ((error=copyin((caddr_t)args, (caddr_t)&linux_args, sizeof(linux_args)))) return error; bsd_args.protocol = linux_args.protocol; bsd_args.type = linux_args.type; bsd_args.domain = linux_to_bsd_domain(linux_args.domain); if (bsd_args.domain == -1) return EINVAL; - return socket(p, &bsd_args); + + retval_socket = socket(p, &bsd_args); + if (bsd_args.type == SOCK_RAW + && (bsd_args.protocol == IPPROTO_RAW || bsd_args.protocol == 0) + && bsd_args.domain == AF_INET + && retval_socket >= 0) { + /* It's a raw IP socket: set the IP_HDRINCL option. */ + struct setsockopt_args /* { + int s; + int level; + int name; + caddr_t val; + int valsize; + } */ bsd_setsockopt_args; + caddr_t sg; + int *hdrincl; + + sg = stackgap_init(); + hdrincl = (int *)stackgap_alloc(&sg, sizeof(*hdrincl)); + *hdrincl = 1; + bsd_setsockopt_args.s = p->p_retval[0]; + bsd_setsockopt_args.level = IPPROTO_IP; + bsd_setsockopt_args.name = IP_HDRINCL; + bsd_setsockopt_args.val = (caddr_t)hdrincl; + bsd_setsockopt_args.valsize = sizeof(*hdrincl); + /* We ignore any error returned by setsockopt() */ + setsockopt(p, &bsd_setsockopt_args); + /* Copy back the return value from socket() */ + p->p_retval[0] = bsd_setsockopt_args.s; + } + return retval_socket; } struct linux_bind_args { int s; @@ -421,8 +560,13 @@ bsd_args.len = linux_args.len; bsd_args.flags = linux_args.flags; bsd_args.to = linux_args.to; bsd_args.tolen = linux_args.tolen; + + if (linux_check_hdrincl(p, linux_args.s) == 0) + /* IP_HDRINCL set, tweak the packet before sending */ + return linux_sendto_hdrincl(p, &bsd_args); + return sendto(p, &bsd_args); } struct linux_recvfrom_args { @@ -560,8 +704,9 @@ return EINVAL; } if (name == -1) return EINVAL; + bsd_args.name = name; bsd_args.val = linux_args.optval; bsd_args.avalsize = linux_args.optlen; return getsockopt(p, &bsd_args); } -- Pierre Beyssac pb@fasterix.frmug.org pb@fasterix.freenix.org {Free,Net,Open}BSD, Linux : il y a moins bien, mais c'est plus cher Free domains: http://www.eu.org/ or mail dns-manager@EU.org From owner-freebsd-current Sat Dec 13 16:09:22 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id QAA25788 for current-outgoing; Sat, 13 Dec 1997 16:09:22 -0800 (PST) (envelope-from owner-freebsd-current) Received: from freebie.lemis.com (gregl1.lnk.telstra.net [139.130.136.133]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id QAA25777 for ; Sat, 13 Dec 1997 16:09:14 -0800 (PST) (envelope-from grog@lemis.com) Received: (from grog@localhost) by freebie.lemis.com (8.8.8/8.8.7) id KAA00667; Sun, 14 Dec 1997 10:39:10 +1030 (CST) (envelope-from grog) Message-ID: <19971214103908.54930@lemis.com> Date: Sun, 14 Dec 1997 10:39:08 +1030 From: Greg Lehey To: FreeBSD current users Subject: Changes in gdb -k? Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.84e Organisation: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-41-739-7062 WWW-Home-Page: http://www.lemis.com/~grog Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk I've just had a couple of panics (ffs_alloccg: map corrupted, but I think it's probably hardware), and I tried to look at them with gdb -k, but I get: #0 boot (howto=0) at ../../kern/kern_shutdown.c:285 285 dumppcb.pcb_cr3 = rcr3(); (kgdb) t Please specify a thread ID. Use the "info threads" command to see the IDs of currently known threads. (kgdb) i threads (kgdb) info threads (kgdb) t Please specify a thread ID. Use the "info threads" command to see the IDs of currently known threads. (kgdb) t 0 Thread ID 0 not known. Use the "info threads" command to see the IDs of currently known threads. (kgdb) t 1 Thread ID 1 not known. Use the "info threads" command to see the IDs of currently known threads. (kgdb) t 2 Thread ID 2 not known. Use the "info threads" command to see the IDs of currently known threads. (kgdb) q === root@freebie (/dev/ttyp4) /var/crash 9 -> wh gdb -r-xr-xr-x 1 bin bin 757760 Nov 23 18:07 /usr/bin/gdb Any ideas? Greg From owner-freebsd-current Sat Dec 13 16:14:07 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id QAA26265 for current-outgoing; Sat, 13 Dec 1997 16:14:07 -0800 (PST) (envelope-from owner-freebsd-current) Received: from freebie.lemis.com (gregl1.lnk.telstra.net [139.130.136.133]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id QAA26218 for ; Sat, 13 Dec 1997 16:13:12 -0800 (PST) (envelope-from grog@lemis.com) Received: (from grog@localhost) by freebie.lemis.com (8.8.8/8.8.7) id KAA00889; Sun, 14 Dec 1997 10:42:52 +1030 (CST) (envelope-from grog) Message-ID: <19971214104251.63209@lemis.com> Date: Sun, 14 Dec 1997 10:42:51 +1030 From: Greg Lehey To: Julian Elischer Cc: Bruce Evans , current@FreeBSD.ORG Subject: Re: DEVFS: new sample code References: <199712121837.FAA00920@godzilla.zeta.org.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.84e In-Reply-To: ; from Julian Elischer on Fri, Dec 12, 1997 at 10:59:32AM -0800 Organisation: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-41-739-7062 WWW-Home-Page: http://www.lemis.com/~grog Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Fri, Dec 12, 1997 at 10:59:32AM -0800, Julian Elischer wrote: > Disclaimer: > *this of course only applies to what I'm doing of course* > > It ain't going to get done there it's getting done in a layer just below, > and in conjunction with, the disk label layer. The disklabel layer notices > the bad144 flag and sticks the bad144 'wedge' below itself. the bad144 has > no business being lower than that because it doesn't cover other slices. > They may have their own badblock handlers. I don't understand why slices should have any notion of bad blocks. The way I see it, a slice is a virtual disk, and virtual disks are immaculate. Bad blocks are a fact of life of the dirty representations of our idealized disks. > it CERTAINLY doesn't get to be in the disk driver because THAT only > knows how to move blocks of data and how to propogate up error > reports. Still, it's the disk driver which should be maintaining problems on the disk. I (still!) haven't looked at the code, but wouldn't it be possible to teach the driver to propagate the errors? Greg From owner-freebsd-current Sat Dec 13 16:24:14 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id QAA27226 for current-outgoing; Sat, 13 Dec 1997 16:24:14 -0800 (PST) (envelope-from owner-freebsd-current) Received: from ns.mt.sri.com (sri-gw.MT.net [206.127.105.141]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id QAA27193 for ; Sat, 13 Dec 1997 16:24:05 -0800 (PST) (envelope-from nate@mt.sri.com) Received: from mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by ns.mt.sri.com (8.8.8/8.8.8) with SMTP id RAA08357; Sat, 13 Dec 1997 17:22:30 -0700 (MST) (envelope-from nate@rocky.mt.sri.com) Received: by mt.sri.com (SMI-8.6/SMI-SVR4) id RAA00744; Sat, 13 Dec 1997 17:22:29 -0700 Date: Sat, 13 Dec 1997 17:22:29 -0700 Message-Id: <199712140022.RAA00744@mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Amancio Hasty Cc: pb@fasterix.freenix.org (Pierre Beyssac), freebsd-current@freebsd.org Subject: Re: small patch to fix MSG_COMPAT in recvfrom() In-Reply-To: <199712132009.MAA00640@rah.star-gate.com> References: <19971213181809.AU40295@@> <199712132009.MAA00640@rah.star-gate.com> X-Mailer: VM 6.29 under 19.15 XEmacs Lucid Sender: owner-freebsd-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > If you don't mind please post the patches to the list it will allow others > to review them and test them. He did. Nate From owner-freebsd-current Sat Dec 13 16:28:31 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id QAA27608 for current-outgoing; Sat, 13 Dec 1997 16:28:31 -0800 (PST) (envelope-from owner-freebsd-current) Received: from rah.star-gate.com (rah.star-gate.com [204.188.121.18]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id QAA27569 for ; Sat, 13 Dec 1997 16:28:20 -0800 (PST) (envelope-from hasty@rah.star-gate.com) Received: from rah.star-gate.com (localhost.star-gate.com [127.0.0.1]) by rah.star-gate.com (8.8.8/8.8.8) with ESMTP id QAA07648; Sat, 13 Dec 1997 16:27:12 -0800 (PST) (envelope-from hasty@rah.star-gate.com) Message-Id: <199712140027.QAA07648@rah.star-gate.com> X-Mailer: exmh version 2.0gamma 1/27/96 To: Nate Williams cc: pb@fasterix.freenix.org (Pierre Beyssac), freebsd-current@freebsd.org Subject: Re: small patch to fix MSG_COMPAT in recvfrom() In-reply-to: Your message of "Sat, 13 Dec 1997 17:22:29 MST." <199712140022.RAA00744@mt.sri.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 13 Dec 1997 16:27:12 -0800 From: Amancio Hasty Sender: owner-freebsd-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Tnks ----- Next who can review the patches? Tnks, Amancio From owner-freebsd-current Sat Dec 13 16:49:20 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id QAA01260 for current-outgoing; Sat, 13 Dec 1997 16:49:20 -0800 (PST) (envelope-from owner-freebsd-current) Received: from word.smith.net.au (ppp5.portal.net.au [202.12.71.105]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id QAA01196 for ; Sat, 13 Dec 1997 16:49:03 -0800 (PST) (envelope-from mike@word.smith.net.au) Received: from word (localhost [127.0.0.1]) by word.smith.net.au (8.8.8/8.8.5) with ESMTP id LAA04478; Sun, 14 Dec 1997 11:12:14 +1030 (CST) Message-Id: <199712140042.LAA04478@word.smith.net.au> X-Mailer: exmh version 2.0zeta 7/24/97 To: pb@fasterix.freenix.org (Pierre Beyssac) cc: freebsd-current@freebsd.org Subject: Re: small patch to fix MSG_COMPAT in recvfrom() In-reply-to: Your message of "Sat, 13 Dec 1997 18:18:09 BST." <19971213181809.AU40295@@> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 14 Dec 1997 11:12:13 +1030 From: Mike Smith Sender: owner-freebsd-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > I also have several other patches regarding the use of sockets by > the Linux emulator, notably getsockopt(), raw sockets, and the > IP_HDRINCL option which Linux handles differently from BSD in a > subtle way. It allows me to run Linux ping, traceroute, and other > small network "utilities" compiled on Linux such as teardrop. > Should I send these patches to the list or to the Linux emulator > maintainer? If at all possible, please use send-pr to submit them, and then post the PR number you receive to the emulation list. I am *extremely* interested in following this through; thanks a million for tracking the problems down! mike From owner-freebsd-current Sat Dec 13 17:44:19 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id RAA09133 for current-outgoing; Sat, 13 Dec 1997 17:44:19 -0800 (PST) (envelope-from owner-freebsd-current) Received: from frmug.org (frmug-gw.frmug.org [193.56.58.252]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id RAA09093 for ; Sat, 13 Dec 1997 17:44:08 -0800 (PST) (envelope-from pb@fasterix.frmug.org) Received: (from uucp@localhost) by frmug.org (8.8.8/frmug-2.1/nospam) with UUCP id CAA28064; Sun, 14 Dec 1997 02:43:26 +0100 (CET) (envelope-from pb@fasterix.frmug.org) Received: (from pb@localhost) by fasterix.frmug.org (8.8.8/8.8.5/pb-19970302) id CAA02108; Sun, 14 Dec 1997 02:41:35 +0100 (CET) Message-ID: <19971214024134.PL39369@@> Date: Sun, 14 Dec 1997 02:41:34 +0100 From: pb@fasterix.freenix.org (Pierre Beyssac) To: tlambert@primenet.com (Terry Lambert) Cc: totii@est.is (?or?ur Ivarsson), pb@fasterix.freenix.org, freebsd-current@FreeBSD.ORG Subject: Re: panics when stopping pppd References: <3492A8DE.27B270DB@est.is> <199712132150.OAA03369@usr06.primenet.com> X-Mailer: Mutt 0.59.1e Mime-Version: 1.0 In-Reply-To: <199712132150.OAA03369@usr06.primenet.com>; from Terry Lambert on Dec 13, 1997 21:50:21 +0000 Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Terry Lambert writes: [ crash when disconnecting PPP ] > If you have a local ethernet, look at the variables that exist on your > stack to see if your local ethernet MAC address is there somewhere; > this looks remarkably similar to a crash I saw, but have not yet been > able to reproduce. I have a local ethernet, but apparently no MAC address on the stack (I might have missed it though). On the other hand, I can reproduce the crash almost at will. It happens only when I have dynamic routes _and_ they are removed when PPP is down; if I stop gated before I stop PPP, there is no crash at all even when gated routes are removed. If I spray a few printf in the rtrequest code for RTM_DELETE to figure out what happens, it doesn't crash anymore. There might be a race condition somewhere. rtrequest() appears to at least sometimes return with an error before crashing, because in_ifadownkill managed to log the following once (from strings vmcore | tail -100): <4>in_ifadownkill: error 3 The instruction pointer is 0x6e655000 every time I've been able to see it: instruction pointer = 0x8:0x6e655000 stack pointer = 0x10:0xf4d4cd74 frame pointer = 0x10:0xf4d4cdb0 -- Pierre Beyssac pb@fasterix.frmug.org pb@fasterix.freenix.org {Free,Net,Open}BSD, Linux : il y a moins bien, mais c'est plus cher Free domains: http://www.eu.org/ or mail dns-manager@EU.org From owner-freebsd-current Sat Dec 13 18:26:20 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id SAA15936 for current-outgoing; Sat, 13 Dec 1997 18:26:20 -0800 (PST) (envelope-from owner-freebsd-current) Received: from send1b.yahoomail.com (send1b.yahoomail.com [205.180.60.23]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id SAA15859 for ; Sat, 13 Dec 1997 18:26:10 -0800 (PST) (envelope-from osiris2002@yahoo.com) Message-ID: <19971214022555.29020.rocketmail@send1b.yahoomail.com> Received: from [194.79.98.71] by send1b; Sat, 13 Dec 1997 18:25:55 PST Date: Sat, 13 Dec 1997 18:25:55 -0800 (PST) From: Charlie Roots Subject: ps proc size mismatch - HELP ME To: freebsd-current@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I cvsuped on 5/12/97 and build world, build kernel, all went fine. I cvsuped again 13/12/97 and build kernel only. NOW, I am having this error whenever I type ps to get a list of active processes. Any Idea what is going on, did I make a mistake somewhere or the cvsuped files got soaped. Please Help. == MAY THE FORCE BE WITH YOU. _________________________________________________________ DO YOU YAHOO!? Get your free @yahoo.com address at http://mail.yahoo.com From owner-freebsd-current Sat Dec 13 18:56:08 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id SAA27194 for current-outgoing; Sat, 13 Dec 1997 18:56:08 -0800 (PST) (envelope-from owner-freebsd-current) Received: from send1a.yahoomail.com (send1a.yahoomail.com [205.180.60.22]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id SAA27092 for ; Sat, 13 Dec 1997 18:55:56 -0800 (PST) (envelope-from osiris2002@yahoo.com) Message-ID: <19971214025537.28861.rocketmail@send1a.yahoomail.com> Received: from [194.79.98.71] by send1a; Sat, 13 Dec 1997 18:55:37 PST Date: Sat, 13 Dec 1997 18:55:37 -0800 (PST) From: Charlie Roots Subject: FreeBSD utmp problem To: freebsd-current@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi there, I posted a problem that I have on this list, it is about utmp and the new 16 USERNAME stuff, but no one gave as yet an answer. The problem is that I am using idled, a program that uses utmp, and functions to disconnect idle users, it is complaining of errors opening the utmp file, although I recompiled it with 16 as the USERNAME size. Any help is highly appreciated. Thanks == MAY THE FORCE BE WITH YOU. _________________________________________________________ DO YOU YAHOO!? Get your free @yahoo.com address at http://mail.yahoo.com From owner-freebsd-current Sat Dec 13 19:31:53 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id TAA02401 for current-outgoing; Sat, 13 Dec 1997 19:31:53 -0800 (PST) (envelope-from owner-freebsd-current) Received: from dyson.iquest.net (dyson.iquest.net [198.70.144.127]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id TAA02375 for ; Sat, 13 Dec 1997 19:31:44 -0800 (PST) (envelope-from toor@dyson.iquest.net) Received: (from root@localhost) by dyson.iquest.net (8.8.8/8.8.8) id WAA05829; Sat, 13 Dec 1997 22:31:38 -0500 (EST) (envelope-from toor) From: "John S. Dyson" Message-Id: <199712140331.WAA05829@dyson.iquest.net> Subject: Re: ps proc size mismatch - HELP ME In-Reply-To: <19971214022555.29020.rocketmail@send1b.yahoomail.com> from Charlie Roots at "Dec 13, 97 06:25:55 pm" To: osiris2002@yahoo.com (Charlie Roots) Date: Sat, 13 Dec 1997 22:31:38 -0500 (EST) Cc: freebsd-current@freebsd.org X-Mailer: ELM [version 2.4ME+ PL31 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Charlie Roots said: > I cvsuped on 5/12/97 and build world, build kernel, all went fine. > > I cvsuped again 13/12/97 and build kernel only. > NOW, I am having this error whenever I type ps to get a list of active > processes. > > Any Idea what is going on, did I make a mistake somewhere or the > cvsuped files got soaped. > > Please Help. > You are not really indicating a bug, but an error that is a frequently asked question. One is usually only lucky that ps will continue to work between kernel revs. What you need to do is to rebuild libkvm, and then various programs that use it including ps, w, and a few others. Make sure that you re-cvsup libkvm and ps. All of these steps aren't always needed, and that is where we get caught with people who don't know about this problem :-(. (Basically, the abstraction for our interface between user and kernel data structures is in need of work.) -- John dyson@freebsd.org jdyson@nc.com From owner-freebsd-current Sat Dec 13 19:40:16 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id TAA03614 for current-outgoing; Sat, 13 Dec 1997 19:40:16 -0800 (PST) (envelope-from owner-freebsd-current) Received: from zippy.dyn.ml.org (garbanzo@haiti-110.ppp.hooked.net [206.169.228.110]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id TAA03608 for ; Sat, 13 Dec 1997 19:40:07 -0800 (PST) (envelope-from garbanzo@hooked.net) Received: from localhost (garbanzo@localhost) by zippy.dyn.ml.org (8.8.8/8.8.7) with SMTP id TAA22551 for ; Sat, 13 Dec 1997 19:41:14 -0800 (PST) X-Authentication-Warning: zippy.dyn.ml.org: garbanzo owned process doing -bs Date: Sat, 13 Dec 1997 19:41:12 -0800 (PST) From: Alex X-Sender: garbanzo@zippy.dyn.ml.org Reply-To: Alex To: current Subject: problems with gzip'd executables Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Has anyone else noticed that gzip'd programs will give errors when you run them, however uncompressing them will remedy the situation. I have a feeling this has something to do with the recent changes to the dynamic linker. Any ideas? zippy:~#/usr/local/bin/tcsh You have mail. # exit zippy:~#cd /usr/local/bin zippy:/usr/local/bin#gzip -9 tcsh zippy:/usr/local/bin#./tcsh.gz /usr/libexec/ld.so: Cannot find program's a.out header zippy:/usr/local/bin#strings /kernel|grep gzip gzip ___pseudo-device gzip # Exec gzipped a.out's - alex From owner-freebsd-current Sat Dec 13 19:44:25 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id TAA04057 for current-outgoing; Sat, 13 Dec 1997 19:44:25 -0800 (PST) (envelope-from owner-freebsd-current) Received: from rah.star-gate.com (rah.star-gate.com [204.188.121.18]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id TAA04045 for ; Sat, 13 Dec 1997 19:44:17 -0800 (PST) (envelope-from hasty@rah.star-gate.com) Received: from rah.star-gate.com (localhost.star-gate.com [127.0.0.1]) by rah.star-gate.com (8.8.8/8.8.8) with ESMTP id TAA08964; Sat, 13 Dec 1997 19:43:07 -0800 (PST) (envelope-from hasty@rah.star-gate.com) Message-Id: <199712140343.TAA08964@rah.star-gate.com> X-Mailer: exmh version 2.0gamma 1/27/96 To: Mike Smith cc: pb@fasterix.freenix.org (Pierre Beyssac), freebsd-current@freebsd.org Subject: Re: small patch to fix MSG_COMPAT in recvfrom() In-reply-to: Your message of "Sun, 14 Dec 1997 11:12:13 +1030." <199712140042.LAA04478@word.smith.net.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 13 Dec 1997 19:43:06 -0800 From: Amancio Hasty Sender: owner-freebsd-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Tnks Mike! cvs commit: src/sys/kern uipc_syscalls.c cvs commit: src/sys/i386/linux linux_socket.c Amancio From owner-freebsd-current Sat Dec 13 19:47:51 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id TAA04379 for current-outgoing; Sat, 13 Dec 1997 19:47:51 -0800 (PST) (envelope-from owner-freebsd-current) Received: from zippy.dyn.ml.org (garbanzo@haiti-110.ppp.hooked.net [206.169.228.110]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id TAA04358 for ; Sat, 13 Dec 1997 19:47:40 -0800 (PST) (envelope-from garbanzo@hooked.net) Received: from localhost (garbanzo@localhost) by zippy.dyn.ml.org (8.8.8/8.8.7) with SMTP id TAA22678; Sat, 13 Dec 1997 19:48:46 -0800 (PST) X-Authentication-Warning: zippy.dyn.ml.org: garbanzo owned process doing -bs Date: Sat, 13 Dec 1997 19:48:46 -0800 (PST) From: Alex X-Sender: garbanzo@zippy.dyn.ml.org To: Charlie Roots cc: freebsd-current@FreeBSD.ORG Subject: Re: ps proc size mismatch - HELP ME In-Reply-To: <19971214022555.29020.rocketmail@send1b.yahoomail.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Sat, 13 Dec 1997, Charlie Roots wrote: > I cvsuped on 5/12/97 and build world, build kernel, all went fine. > > I cvsuped again 13/12/97 and build kernel only. > NOW, I am having this error whenever I type ps to get a list of active > processes. > > Any Idea what is going on, did I make a mistake somewhere or the > cvsuped files got soaped. I think between those two dates, changes were commited to the procfs that allowed truss to work, however you'll need to rebuild (and install) a few things first, usually in this order: includes, lkms, kernel, programs that use the procfs (top,ps, and maybe w). Then reboot. - alex From owner-freebsd-current Sat Dec 13 20:05:12 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id UAA05851 for current-outgoing; Sat, 13 Dec 1997 20:05:12 -0800 (PST) (envelope-from owner-freebsd-current) Received: from word.smith.net.au (ppp3.portal.net.au [202.12.71.103]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id UAA05838 for ; Sat, 13 Dec 1997 20:05:03 -0800 (PST) (envelope-from mike@word.smith.net.au) Received: from word (localhost [127.0.0.1]) by word.smith.net.au (8.8.8/8.8.5) with ESMTP id OAA05112; Sun, 14 Dec 1997 14:28:33 +1030 (CST) Message-Id: <199712140358.OAA05112@word.smith.net.au> X-Mailer: exmh version 2.0zeta 7/24/97 To: Amancio Hasty cc: Mike Smith , pb@fasterix.freenix.org (Pierre Beyssac), freebsd-current@freebsd.org Subject: Re: small patch to fix MSG_COMPAT in recvfrom() In-reply-to: Your message of "Sat, 13 Dec 1997 19:43:06 -0800." <199712140343.TAA08964@rah.star-gate.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 14 Dec 1997 14:28:32 +1030 From: Mike Smith Sender: owner-freebsd-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > Tnks Mike! > > cvs commit: src/sys/kern uipc_syscalls.c > cvs commit: src/sys/i386/linux linux_socket.c Don't thank me; I just committed the stuff. Thanks to Pierre for actually doing the work! Now, Amancio, if you back out the orecvfrom->recvfrom change that you made to get Q2 going, does it still work properly? That change and these are going to collide otherwise... mike From owner-freebsd-current Sat Dec 13 20:21:13 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id UAA06695 for current-outgoing; Sat, 13 Dec 1997 20:21:13 -0800 (PST) (envelope-from owner-freebsd-current) Received: from rah.star-gate.com (rah.star-gate.com [204.188.121.18]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id UAA06688 for ; Sat, 13 Dec 1997 20:21:05 -0800 (PST) (envelope-from hasty@rah.star-gate.com) Received: from rah.star-gate.com (localhost.star-gate.com [127.0.0.1]) by rah.star-gate.com (8.8.8/8.8.8) with ESMTP id UAA09215; Sat, 13 Dec 1997 20:20:04 -0800 (PST) (envelope-from hasty@rah.star-gate.com) Message-Id: <199712140420.UAA09215@rah.star-gate.com> X-Mailer: exmh version 2.0gamma 1/27/96 To: Mike Smith cc: pb@fasterix.freenix.org (Pierre Beyssac), freebsd-current@freebsd.org Subject: Re: small patch to fix MSG_COMPAT in recvfrom() In-reply-to: Your message of "Sun, 14 Dec 1997 14:28:32 +1030." <199712140358.OAA05112@word.smith.net.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 13 Dec 1997 20:20:04 -0800 From: Amancio Hasty Sender: owner-freebsd-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I know just wanted to thank you for committing the change around here it can take a while! Yes, Q2 works peachy over here without the orecvfrom->recvfrom change. I will post my patches to the linux layer tomorrow . Cheers, Amancio > > > > Tnks Mike! > > > > cvs commit: src/sys/kern uipc_syscalls.c > > cvs commit: src/sys/i386/linux linux_socket.c > > Don't thank me; I just committed the stuff. Thanks to Pierre for > actually doing the work! > > Now, Amancio, if you back out the orecvfrom->recvfrom change that you > made to get Q2 going, does it still work properly? That change and > these are going to collide otherwise... > > mike