From owner-freebsd-current Sun Sep 28 00:14:43 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id AAA14019 for current-outgoing; Sun, 28 Sep 1997 00:14:43 -0700 (PDT) Received: from zippy.dyn.ml.org (garbanzo@spain-21.ppp.hooked.net [206.169.228.21]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id AAA14013 for ; Sun, 28 Sep 1997 00:14:39 -0700 (PDT) Received: from localhost (garbanzo@localhost) by zippy.dyn.ml.org (8.8.7/8.8.7) with SMTP id AAA00595 for ; Sun, 28 Sep 1997 00:15:00 -0700 (PDT) X-Authentication-Warning: zippy.dyn.ml.org: garbanzo owned process doing -bs Date: Sun, 28 Sep 1997 00:15:00 -0700 (PDT) From: Alex X-Sender: garbanzo@zippy.dyn.ml.org Reply-To: Alex To: current@freebsd.org Subject: Login is causing the kernel to panic :( 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 The subject says it all. I noticed that this happens with kernels built right around the time the vn bug(s) were introduced. Everything boots fine until I attempt to login as any user. After hitting return the system will hand for a while (keyboard leds respond) and the system will eventually panic. A kernel built today booted fine once, attempts after this panic'd. A generic kernel from quite a while back (pre poll()) works fine but causes some lkms to complain *duh*. Rebuilding login didn't work, and a few days ago building world bombed out, I'm currently trying to build world to see if that would work. Any ideas? - alex From owner-freebsd-current Sun Sep 28 01:00:07 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id BAA16888 for current-outgoing; Sun, 28 Sep 1997 01:00:07 -0700 (PDT) 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 BAA16849 for ; Sun, 28 Sep 1997 01:00:02 -0700 (PDT) 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 JAA05963; Sun, 28 Sep 1997 09:59:16 +0200 (CEST) To: Alex cc: current@freebsd.org Subject: Re: Login is causing the kernel to panic :( In-reply-to: Your message of "Sun, 28 Sep 1997 00:15:00 PDT." Date: Sun, 28 Sep 1997 09:59:14 +0200 Message-ID: <5961.875433554@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk In message , Alex writ es: >The subject says it all. I noticed that this happens with kernels built >right around the time the vn bug(s) were introduced. Everything boots >fine until I attempt to login as any user. After hitting return the >system will hand for a while (keyboard leds respond) and the system will >eventually panic. A kernel built today booted fine once, attempts after >this panic'd. A generic kernel from quite a while back (pre poll()) works >fine but causes some lkms to complain *duh*. Rebuilding login didn't >work, and a few days ago building world bombed out, I'm currently trying >to build world to see if that would work. Any ideas? Yes, I just commited a fix to __getcwd, please try that out. -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." From owner-freebsd-current Sun Sep 28 01:05:36 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id BAA17158 for current-outgoing; Sun, 28 Sep 1997 01:05:36 -0700 (PDT) Received: from gratis.grondar.za (gratis.grondar.za [196.7.18.133]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id BAA17153 for ; Sun, 28 Sep 1997 01:05:31 -0700 (PDT) Received: from greenpeace.grondar.za (ROb5PEuMv/t+tkA+RtmuEYHWqFTpSDEX@greenpeace.grondar.za [196.7.18.132]) by gratis.grondar.za (8.8.7/8.8.7) with ESMTP id KAA14949 for ; Sun, 28 Sep 1997 10:05:51 +0200 (SAT) Received: from greenpeace.grondar.za (dkfb1zRjT+FIHsGHXiIx6MXyoR8CyWLG@localhost [127.0.0.1]) by greenpeace.grondar.za (8.8.7/8.8.7) with ESMTP id KAA00466 for ; Sun, 28 Sep 1997 10:05:23 +0200 (SAT) Message-Id: <199709280805.KAA00466@greenpeace.grondar.za> X-Mailer: exmh version 2.0zeta 7/24/97 To: current@freebsd.org Subject: HEAR YE! HEAR YE! New Kerberos! Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 28 Sep 1997 10:05:20 +0200 From: Mark Murray Sender: owner-freebsd-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi It is Sunday morning, Cape town, South Africa. I am about to start committing the userland changes to make the new Kerberos work. This will take me some time as the changes are all over the tree, and my connection to WC is not the fastest. Please bear with me; until I am finished, "make world" will be broken, so please do not panic until I have announced the completion. Thanks! M -- Mark Murray Join the anti-SPAM movement: http://www.cauce.org From owner-freebsd-current Sun Sep 28 01:10:09 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id BAA17368 for current-outgoing; Sun, 28 Sep 1997 01:10:09 -0700 (PDT) Received: from sendero-ppp.i-connect.net (sendero-ppp.i-Connect.Net [206.190.143.100]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id BAA17363 for ; Sun, 28 Sep 1997 01:10:06 -0700 (PDT) Received: (qmail 29719 invoked by uid 1000); 28 Sep 1997 08:10:30 -0000 Message-ID: X-Mailer: XFMail 1.2-alpha-092397 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit MIME-Version: 1.0 In-Reply-To: <342DE052.FE793D33@nconnect.net> Date: Sun, 28 Sep 1997 01:10:30 -0700 (PDT) Organization: Atlas Telecom From: Simon Shapiro To: Randy DuCharme Subject: RE: Make world failure Cc: current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Hi Randy DuCharme; On 28-Sep-97 you wrote: > Now what did I do?? I just tried to do a make world after grabbing > fresh sources as > of 5:30pm It stops shortly after starting with > > . > . > . > t.lib/lstInit.c /usr/src/usr.bin/make/lst.lib/lstInsert.c > /usr/src/usr.bin/make/lst.lib/lstIsAtEnd.c > /usr/src/usr.bin/make/lst.lib/lstIsEmpty.c > /usr/src/usr.bin/make/lst.lib/lstLast.c > /usr/src/usr.bin/make/lst.lib/lstMember.c > /usr/src/usr.bin/make/lst.lib/lstNext.c > /usr/src/usr.bin/make/lst.lib/lstOpen.c > /usr/src/usr.bin/make/lst.lib/lstRemove.c > /usr/src/usr.bin/make/lst.lib/lstReplace.c > /usr/src/usr.bin/make/lst.lib/lstSucc.c > /usr/bin/mkdep: cannot create _mkdep28392: directory nonexistent > *** Error code 2 > > Stop. > *** Error code 1 > > Stop. > *** Error code 1 > > Stop. > # > > > I've been digging around for the last 5 hrs or so. I'm Stumped! rm -rf /usr/obj/* I have been digging too. Not this long, though. When in doubt, blow /usr/obj. Note: There is no logical, mathematical or sceitific reason for the above (that I am aware of). --- Sincerely Yours, Simon Shapiro Atlas Telecom Senior Architect 14355 SW Allen Blvd., Suite 130 Beaverton OR 97005 Shimon@i-Connect.Net Voice: 503.799.2313 From owner-freebsd-current Sun Sep 28 02:02:15 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id CAA19913 for current-outgoing; Sun, 28 Sep 1997 02:02:15 -0700 (PDT) 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 CAA19906 for ; Sun, 28 Sep 1997 02:02:11 -0700 (PDT) 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 LAA18143 for ; Sun, 28 Sep 1997 11:01:27 +0200 (CEST) To: current@freebsd.org Subject: Come on guys... From: Poul-Henning Kamp Date: Sun, 28 Sep 1997 11:01:25 +0200 Message-ID: <18132.875437285@critter.freebsd.dk> Sender: owner-freebsd-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk It's seemed to have become vogue lately to send emails that say "my kernel panics when ..." with no detail at all. So for any newcomers or old hands that might have forgotten: WHAT TO DO If your -current kernel panics: 1, Update to the absolutely latest sources, unless emails has been warning against this. 2. rm /lkm/* 3. If you have any local patches, back them out. 4. Recompile, from scratch, your kernel with DDB in it. (For extra points: use "config -g" and do not strip your kernel before booting) 5. Report all details from the panic. As a minimum all info from "show reg" and "trace" are mandatory. Try to secure a kernel-dump. Check the handbook for info on how to run gdb on it. Unless you do at least this, chances are pretty good that your email is a waste of time. Remember guys, you're asking somebody to use their spare-time on your problem, so make it easy for them. -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." From owner-freebsd-current Sun Sep 28 02:57:54 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id CAA23367 for current-outgoing; Sun, 28 Sep 1997 02:57:54 -0700 (PDT) Received: from implode.root.com (implode.root.com [198.145.90.17]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id CAA23362 for ; Sun, 28 Sep 1997 02:57:51 -0700 (PDT) Received: from implode.root.com (localhost [127.0.0.1]) by implode.root.com (8.8.5/8.8.5) with ESMTP id CAA19719; Sun, 28 Sep 1997 02:59:11 -0700 (PDT) Message-Id: <199709280959.CAA19719@implode.root.com> To: John Hay cc: freebsd-current@FreeBSD.ORG (FreeBSD-current) Subject: Re: ed0 not found on reboots In-reply-to: Your message of "Sat, 28 Sep 1997 08:32:08 +0200." <199709280632.IAA21096@zibbi.mikom.csir.co.za> From: David Greenman Reply-To: dg@root.com Date: Sun, 28 Sep 1997 02:59:11 -0700 Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >I have updated my -current box for the first time in about 6 weeks and >found that with the latest kernel my ed0 device is only found atfter >a power up or physical reset. After reboot or shutdown -r now it isn't >found. Has anyone seen something like this? > >My machine is a 90MHz Pentium and the ed0 device (when found) probes >like this: >===== >ed0 at 0x280-0x29f irq 5 maddr 0xd8000 msize 16384 on isa >ed0: address 00:00:c0:70:bf:94, type SMC8216/SMC8216C (16 bit) >===== I had a report of an NE2000 clone not passing the station address checksum after a warmboot, but this is the first problem I've heard with the SMC Ultra. The only significant change that's been made is the 0WS flag is turned on, but this should only affect accesses to the shared memory. You might want to add some printf's to the probe code to find out which test is failing. -DG David Greenman Core-team/Principal Architect, The FreeBSD Project From owner-freebsd-current Sun Sep 28 03:14:13 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id DAA24147 for current-outgoing; Sun, 28 Sep 1997 03:14:13 -0700 (PDT) Received: from gratis.grondar.za (gratis.grondar.za [196.7.18.133]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id DAA24142 for ; Sun, 28 Sep 1997 03:14:08 -0700 (PDT) Received: from greenpeace.grondar.za (PgnA432SjN+ZxShLcr7mCT7VSVvVBa4U@greenpeace.grondar.za [196.7.18.132]) by gratis.grondar.za (8.8.7/8.8.7) with ESMTP id MAA15192 for ; Sun, 28 Sep 1997 12:14:31 +0200 (SAT) Received: from greenpeace.grondar.za (caSjMedhEuw2aeCS4OFAvC+Lgd5irBIy@localhost [127.0.0.1]) by greenpeace.grondar.za (8.8.7/8.8.7) with ESMTP id MAA01564 for ; Sun, 28 Sep 1997 12:14:06 +0200 (SAT) Message-Id: <199709281014.MAA01564@greenpeace.grondar.za> X-Mailer: exmh version 2.0zeta 7/24/97 To: current@FreeBSD.ORG Subject: Re: HEAR YE! HEAR YE! New Kerberos! Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 28 Sep 1997 12:14:05 +0200 From: Mark Murray Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk A couple of hours later, and it was not too painful! I am done now. Those of you wanting to test this new Kerberos should please 1) rm -rf /usr/include/kerberosIV 2) cp /usr/src/etc/services /etc 3) in /etc/make.conf replace MAKE_EBONES= yes with MAKE_KERBEROS4= yes 4) Make world. Please let me know if you have problems. Thanks! M Mark Murray wrote: > Hi > > It is Sunday morning, Cape town, South Africa. I am about to start > committing the userland changes to make the new Kerberos work. This > will take me some time as the changes are all over the tree, and my > connection to WC is not the fastest. Please bear with me; until I am > finished, "make world" will be broken, so please do not panic until I > have announced the completion. > > Thanks! > > M > -- > Mark Murray > Join the anti-SPAM movement: http://www.cauce.org > > -- Mark Murray Join the anti-SPAM movement: http://www.cauce.org From owner-freebsd-current Sun Sep 28 03:52:25 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id DAA25497 for current-outgoing; Sun, 28 Sep 1997 03:52:25 -0700 (PDT) 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 DAA25492 for ; Sun, 28 Sep 1997 03:52:19 -0700 (PDT) Received: from gid.co.uk (uucp@localhost) by isbalham.ist.co.uk (8.8.4/8.8.4) with UUCP id LAA26519; Sun, 28 Sep 1997 11:41:15 +0100 (BST) Received: from [194.32.164.2] by seagoon.gid.co.uk; Sun, 28 Sep 1997 11:40:40 +0100 X-Sender: rb@194.32.164.1 Message-Id: In-Reply-To: References: <342DE052.FE793D33@nconnect.net> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Sun, 28 Sep 1997 11:33:56 +0100 To: current@FreeBSD.ORG From: Bob Bishop Subject: RE: Make world failure Cc: Simon Shapiro , Randy DuCharme Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Hi, At 9:10 am +0100 28/9/97, Simon Shapiro wrote: >>[...] >> /usr/bin/mkdep: cannot create _mkdep28392: directory nonexistent >> *** Error code 2 >> [etc] >> >> I've been digging around for the last 5 hrs or so. I'm Stumped! > > > >I have been digging too. Not this long, though. When in doubt, blow >/usr/obj. > >Note: There is no logical, mathematical or sceitific reason for the above >(that I am aware of). My piece of the jigsaw: I had exactly the same problem. Working my way through the over-the-counter remedies I too reached the rm -rf /usr/obj/* stage. Actually, I cd to /usr/obj and rm -rf *. It refuses to remove several leaf files, citing "Operation not permitted" (errno 1 I assume). But I'm root! As it happens, I keep /usr/obj on a separate filesystem connected up by a symlink. So I unmount the sucker, clri these odd files, fsck the thing back to normal, remount and do the rm -rf. This is where it gets interesting: the build still fails in exactly the same way. There are no unremovable files below /usr/obj now, but this time I blow away the directory which is the target of my /usr/obj symlink as well as points south (and remake the directory, of course). Now everything works. Wierd or what? -- 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 Sun Sep 28 04:18:20 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id EAA26113 for current-outgoing; Sun, 28 Sep 1997 04:18:20 -0700 (PDT) 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 EAA26108 for ; Sun, 28 Sep 1997 04:18:11 -0700 (PDT) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.5/8.6.9) id VAA16774; Sun, 28 Sep 1997 21:13:45 +1000 Date: Sun, 28 Sep 1997 21:13:45 +1000 From: Bruce Evans Message-Id: <199709281113.VAA16774@godzilla.zeta.org.au> To: randyd@nconnect.net, Shimon@i-Connect.Net Subject: RE: Make world failure Cc: current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >>... >> /usr/src/usr.bin/make/lst.lib/lstReplace.c >> /usr/src/usr.bin/make/lst.lib/lstSucc.c >> /usr/bin/mkdep: cannot create _mkdep28392: directory nonexistent >> *** Error code 2 >> ... >> I've been digging around for the last 5 hrs or so. I'm Stumped! > >rm -rf /usr/obj/* > >I have been digging too. Not this long, though. When in doubt, blow >/usr/obj. > >Note: There is no logical, mathematical or sceitific reason for the above >(that I am aware of). Haven't you been reading your commit mail? :-) I discussed the bug in cvs-committers yesterday. Perhaps I removed the cc's to the general cvs lists. The diagnosis of a bug in the log message for rev.1.146 was obviously wrong, and the "fix" turned out to introduce the current bug without actually fixing the old one. Now, if the obj directory already exists, then `make' shoots itself in the foot by removing its current directory. Then re-making the obj directory does not help. Untested fix (for -current): diff -c2 Makefile~ Makefile *** Makefile~ Sat Sep 27 01:42:58 1997 --- Makefile Sat Sep 27 01:53:47 1997 *************** *** 223,231 **** @echo "--------------------------------------------------------------" mkdir -p ${WORLDTMP}/usr/bin cd ${.CURDIR}/usr.bin/make && \ ! ${IBMAKE} -I${.CURDIR}/share/mk \ ! ${CLEANDIR} ${OBJDIR} depend && \ ! ${IBMAKE} -I${.CURDIR}/share/mk ${MK_FLAGS} \ ! all install clean cleandepend @echo @echo "--------------------------------------------------------------" --- 223,233 ---- @echo "--------------------------------------------------------------" mkdir -p ${WORLDTMP}/usr/bin + .if !defined(NOCLEAN) || !defined(NOOBJDIR) cd ${.CURDIR}/usr.bin/make && \ ! ${IBMAKE} -I${.CURDIR}/share/mk ${CLEANDIR} ${OBJDIR} ! .endif ! cd ${.CURDIR}/usr.bin/make && \ ! ${IBMAKE} -I${.CURDIR}/share/mk depend && \ ! ${IBMAKE} -I${.CURDIR}/share/mk ${MK_FLAGS} all install @echo @echo "--------------------------------------------------------------" This also removes the superflous final clean and cleandepend steps. Bruce From owner-freebsd-current Sun Sep 28 04:22:21 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id EAA26246 for current-outgoing; Sun, 28 Sep 1997 04:22:21 -0700 (PDT) Received: from darkening.com (nonxstnt@darkening.com [206.249.210.200]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id EAA26238 for ; Sun, 28 Sep 1997 04:22:13 -0700 (PDT) Received: (from nonxstnt@localhost) by darkening.com (8.8.7/8.8.7) id FAA22849 for freebsd-current@freebsd.org; Sun, 28 Sep 1997 05:28:29 -0600 (MDT) Date: Sun, 28 Sep 1997 05:28:29 -0600 (MDT) From: nobody Message-Id: <199709281128.FAA22849@darkening.com> To: freebsd-current@freebsd.org Sender: owner-freebsd-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk subscribe nobody@darkening.com From owner-freebsd-current Sun Sep 28 04:41:08 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id EAA26956 for current-outgoing; Sun, 28 Sep 1997 04:41:08 -0700 (PDT) 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 EAA26951 for ; Sun, 28 Sep 1997 04:41:04 -0700 (PDT) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.5/8.6.9) id VAA17476; Sun, 28 Sep 1997 21:37:40 +1000 Date: Sun, 28 Sep 1997 21:37:40 +1000 From: Bruce Evans Message-Id: <199709281137.VAA17476@godzilla.zeta.org.au> To: current@FreeBSD.ORG, rb@gid.co.uk Subject: RE: Make world failure Cc: randyd@nconnect.net, Shimon@i-Connect.Net Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >Actually, I cd to /usr/obj and rm -rf *. It refuses to remove several leaf >files, citing "Operation not permitted" (errno 1 I assume). But I'm root! Many files are installed in the temporary bin directories, and some of them are installed with flags schg. That's why the Makefile does a `chflags -R noschg ...' before `rm -rf ...' Bruce From owner-freebsd-current Sun Sep 28 04:53:05 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id EAA27417 for current-outgoing; Sun, 28 Sep 1997 04:53:05 -0700 (PDT) Received: from word.smith.net.au (ppp20.portal.net.au [202.12.71.120]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id EAA27406 for ; Sun, 28 Sep 1997 04:52:45 -0700 (PDT) Received: from word.smith.net.au (localhost.smith.net.au [127.0.0.1]) by word.smith.net.au (8.8.7/8.8.5) with ESMTP id VAA05954; Sun, 28 Sep 1997 21:19:06 +0930 (CST) Message-Id: <199709281149.VAA05954@word.smith.net.au> X-Mailer: exmh version 2.0zeta 7/24/97 To: Bob Bishop cc: current@FreeBSD.ORG, Simon Shapiro , Randy DuCharme Subject: Re: Make world failure In-reply-to: Your message of "Sun, 28 Sep 1997 11:33:56 +0100." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 28 Sep 1997 21:19:04 +0930 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > Actually, I cd to /usr/obj and rm -rf *. It refuses to remove several leaf > files, citing "Operation not permitted" (errno 1 I assume). But I'm root! > > As it happens, I keep /usr/obj on a separate filesystem connected up by a > symlink. So I unmount the sucker, clri these odd files, fsck the thing back > to normal, remount and do the rm -rf. It's normally much easier just to 'chflags -R nochg /usr/obj', as there are several objects (eg. libc) that are installed in the temporary build area with the system-immutable flag set. > This is where it gets interesting: the build still fails in exactly the > same way. There are no unremovable files below /usr/obj now, but this time > I blow away the directory which is the target of my /usr/obj symlink as > well as points south (and remake the directory, of course). Now everything > works. Wierd or what? Sounds like your symlink target's permissions were "unhappy". Yes weird, but hard to actually debug once you've deleted it all. mike From owner-freebsd-current Sun Sep 28 04:54:52 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id EAA27536 for current-outgoing; Sun, 28 Sep 1997 04:54:52 -0700 (PDT) Received: from mexico.brainstorm.eu.org (mexico.brainstorm.fr [193.56.58.253]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id EAA27517 for ; Sun, 28 Sep 1997 04:54:45 -0700 (PDT) Received: from brasil.brainstorm.eu.org (brasil.brainstorm.fr [193.56.58.33]) by mexico.brainstorm.eu.org (8.8.4/8.8.4) with ESMTP id NAA23831 for ; Sun, 28 Sep 1997 13:54:48 +0200 Received: (from uucp@localhost) by brasil.brainstorm.eu.org (8.8.6/brasil-1.2) with UUCP id NAA23758 for current@FreeBSD.ORG; Sun, 28 Sep 1997 13:54:32 +0200 Received: (from roberto@localhost) by keltia.freenix.fr (8.8.7/keltia-2.10/nospam) id NAA12003; Sun, 28 Sep 1997 13:22:52 +0200 (CEST) Message-ID: <19970928132251.32998@keltia.freenix.fr> Date: Sun, 28 Sep 1997 13:22:51 +0200 From: Ollivier Robert To: current@FreeBSD.ORG Subject: Re: Make world failure References: <342DE052.FE793D33@nconnect.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.84 In-Reply-To: ; from Bob Bishop on Sun, Sep 28, 1997 at 11:33:56AM +0100 X-Operating-System: FreeBSD 3.0-CURRENT Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk According to Bob Bishop: > Actually, I cd to /usr/obj and rm -rf *. It refuses to remove several leaf > files, citing "Operation not permitted" (errno 1 I assume). But I'm root! Do chflags -R noschg /usr/obj/* to remove the immutable flag. -- Ollivier ROBERT -=- FreeBSD: There are no limits -=- roberto@keltia.freenix.fr FreeBSD keltia.freenix.fr 3.0-CURRENT #35: Sun Sep 21 19:28:07 CEST 1997 From owner-freebsd-current Sun Sep 28 05:10:16 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id FAA28158 for current-outgoing; Sun, 28 Sep 1997 05:10:16 -0700 (PDT) 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 FAA28144 for ; Sun, 28 Sep 1997 05:10:01 -0700 (PDT) Received: (from jmg@localhost) by hydrogen.nike.efn.org (8.8.7/8.8.7) id FAA00273; Sun, 28 Sep 1997 05:09:16 -0700 (PDT) Message-ID: <19970928050916.54436@hydrogen.nike.efn.org> Date: Sun, 28 Sep 1997 05:09:16 -0700 From: John-Mark Gurney To: Bob Bishop Cc: current@FreeBSD.ORG Subject: Re: Make world failure References: <342DE052.FE793D33@nconnect.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.69 In-Reply-To: ; from Bob Bishop on Sun, Sep 28, 1997 at 11:33:56AM +0100 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 Bob Bishop scribbled this message on Sep 28: > Actually, I cd to /usr/obj and rm -rf *. It refuses to remove several leaf > files, citing "Operation not permitted" (errno 1 I assume). But I'm root! this is usually because a file has the schng flag set on it... you must first clear this flag before you can remove the file, this includes root users... and in -current there is also a flag that prevents removal of a file (but still lets you modify it)... ttyl.. -- 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 Sun Sep 28 06:58:08 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id GAA01991 for current-outgoing; Sun, 28 Sep 1997 06:58:08 -0700 (PDT) Received: from khavrinen.lcs.mit.edu (khavrinen.lcs.mit.edu [18.24.4.193]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id GAA01982 for ; Sun, 28 Sep 1997 06:57:49 -0700 (PDT) Received: (from wollman@localhost) by khavrinen.lcs.mit.edu (8.8.5/8.8.5) id JAA08605; Sun, 28 Sep 1997 09:57:42 -0400 (EDT) Date: Sun, 28 Sep 1997 09:57:42 -0400 (EDT) From: Garrett Wollman Message-Id: <199709281357.JAA08605@khavrinen.lcs.mit.edu> To: Wolfgang Helbig Cc: current@freebsd.org Subject: Re: Adding algorithms [Was: cvs commit: src/usr.bin/cksum crc32.c ...] In-Reply-To: <199709281226.OAA23108@rvc1.informatik.ba-stuttgart.de> References: <19970928080813.MB43888@uriah.heep.sax.de> <199709281226.OAA23108@rvc1.informatik.ba-stuttgart.de> Sender: owner-freebsd-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk < said: > I'd like to supply two or three fundamental calendar calculations: > o Computes from a date the number of days since March 1st 1600 Would be better to use astronomical Julian Day Numbers. Remember, Great Britain and her colonies did not adopt the Gregorian calendar until August of 1752. (Your mission, should you choose to accept it... create a database of ``switch dates'' and modify cal(1) to use it.) > o Computes the Number of Week from a given date. > According to DIN 1355 : The first week of year y is the first week > that includes at least four days in year y. A week starts with > Monday. I don't know about international standards so it might be > useful for Germany only. ISO 8601. The strftime(3) function already provides this functionality, although there is unfortunately no direct iso8601weeknumber() function to give you the integer value directly. This is of course not in the C standard because nobody in the US could care less about counting weeks (well, except for accountants at those companies whose quarter is exactly 13 weeks long and ends on a Friday). -GAWollman -- Garrett A. Wollman | O Siem / We are all family / O Siem / We're all the same wollman@lcs.mit.edu | O Siem / The fires of freedom Opinions not those of| Dance in the burning flame MIT, LCS, CRS, or NSA| - Susan Aglukark and Chad Irschick From owner-freebsd-current Sun Sep 28 07:59:18 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id HAA07720 for current-outgoing; Sun, 28 Sep 1997 07:59:18 -0700 (PDT) Received: from silent.darkening.com (nonxstnt@iskh122.haninge.kth.se [130.237.83.122]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id HAA07715 for ; Sun, 28 Sep 1997 07:59:14 -0700 (PDT) Received: from localhost (nonxstnt@localhost) by silent.darkening.com (8.8.7/8.8.7) with SMTP id RAA23748 for ; Sun, 28 Sep 1997 17:00:33 +0200 (CEST) X-Authentication-Warning: silent.darkening.com: nonxstnt owned process doing -bs Date: Sun, 28 Sep 1997 17:00:28 +0200 (CEST) From: nobody To: current@freebsd.org Subject: 0926-SNAP failed install. Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from QUOTED-PRINTABLE to 8bit by hub.freebsd.org id HAA07716 Sender: owner-freebsd-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I couldnt delve into the problem very far, but when installing the 0926 SNAP, I got a panic when it was "writing kernel -c changes" after installing the distribution peices. I installed 0927-RELENG right afterwards with the exact same configuration with no problem. details: P166/Asus TX97-e motherboard Two IDE HD's, one installing to was slice 2 of ide1. Installed just bin+manpages+XFree86 from the first IDE. Just wanted to put the snap on before I got to writing kernconf & update. --- thomas strömberg . system admin, royal institute of technology (stockholm) nobody@darkening.com . irc:nobody@EFnet . talk:nonxstnt@silent.darkening.com real coders don't use comments. It was hard to write; it should be hard to read From owner-freebsd-current Sun Sep 28 08:36:31 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id IAA09412 for current-outgoing; Sun, 28 Sep 1997 08:36:31 -0700 (PDT) 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 IAA09407 for ; Sun, 28 Sep 1997 08:36:27 -0700 (PDT) Received: from gid.co.uk (uucp@localhost) by isbalham.ist.co.uk (8.8.4/8.8.4) with UUCP id QAA27091; Sun, 28 Sep 1997 16:26:18 +0100 (BST) Received: from [194.32.164.2] by seagoon.gid.co.uk; Sun, 28 Sep 1997 16:24:14 +0100 X-Sender: rb@194.32.164.1 Message-Id: In-Reply-To: <199709281137.VAA17476@godzilla.zeta.org.au> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Sun, 28 Sep 1997 16:17:30 +0100 To: Bruce Evans From: Bob Bishop Subject: RE: Make world failure Cc: current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk At 12:37 pm +0100 28/9/97, Bruce Evans wrote: >>Actually, I cd to /usr/obj and rm -rf *. It refuses to remove several leaf >>files, citing "Operation not permitted" (errno 1 I assume). But I'm root! > >Many files are installed in the temporary bin directories, and some >of them are installed with flags schg. That's why the Makefile does a >`chflags -R noschg ...' before `rm -rf ...' Silly me, assuming nothing in a temp tree would be flagged immutable. Doesn't explain the other thing though... -- 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 Sun Sep 28 10:12:26 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id KAA13589 for current-outgoing; Sun, 28 Sep 1997 10:12:26 -0700 (PDT) Received: from word.smith.net.au (ppp20.portal.net.au [202.12.71.120]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id KAA13578 for ; Sun, 28 Sep 1997 10:12:09 -0700 (PDT) Received: from word.smith.net.au (localhost.smith.net.au [127.0.0.1]) by word.smith.net.au (8.8.7/8.8.5) with ESMTP id CAA06890 for ; Mon, 29 Sep 1997 02:39:43 +0930 (CST) Message-Id: <199709281709.CAA06890@word.smith.net.au> X-Mailer: exmh version 2.0zeta 7/24/97 To: current@freebsd.org Subject: Staying -current with FreeBSD Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 29 Sep 1997 02:39:39 +0930 From: Mike Smith Sender: owner-freebsd-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I submit the following for commentary; please everyone elaborate on your personal experiences, add points, gripe about my terminology, etc. Ultimately, I'd like anyone that pops up with a "my -current doesn't work" question get about a dozen copies of this (or something similar and perhaps politer) in their mailbox. [... tappita ...] Eep. It's turned into something more of a Really Big Frothing Penguin. Any idea where this monstrosity belongs? (Another newsletter artikel, Jordan?) = = = = = = = = Staying -current with FreeBSD FreeBSD-current represents the bleeding edge of FreeBSD development. It's where all the new features, performance improvements and bugfixes are unleashed on the user community. If you are interested in developing for FreeBSD, or just want the heady thrill of getting all the latest stuff first, -current is what you want. FreeBSD-current changes daily, and like any new product it goes through patches of instability and unreliability. This is part and parcel of using -current; if you don't think you can deal with it, now is a good time to opt out. A -release or -stable version will still give you excellent service, and with greatly improved dependability. However, there are a lot of people that do run FreeBSD-current, and many use nothing else. If you are serious about contributing to ongoing FreeBSD development, you may need to run -current too. In order to help new -current users, and old ones with bad habits, this is a guide to getting along with FreeBSD-current. If you're having problems, check here first because if you don't, you may find your (quite valid) complaint ignored simply because there's not enough information for anyone to do anything about it, and you just might find the information you need to get you going again. Notes ----- It is assumed that the reader is reasonably familiar with FreeBSD; no attempt will be made here to explain basic operating procedure or commands. All command examples assume a 'csh'-like shell. If you are using an 'sh'-like shell, you will need to translate. Preparation ----------- If you are not subscribed to the FreeBSD-current mailing list, you should do this first. Running -current and not reading the mailing list is like driving at night with duct tape over your eyes and jellybeans in your ears; ie. not a good idea. Read the -current mailing list for a few days before starting with FreeBSD-current; it's possible that you might have picked a really bad time to start. If there are problems, people will be discussing them; wait for a resolution to be announced, or for other people to indicate that the problem has been solved. If you're not sure after a few days, post a short message asking whether people think that it's OK to go ahead. As you become more familiar with the atmosphere and the people on -current, you will learn to judge what constitutes "really bad" and what is merely "interesting". Remember that while FreeBSD-current is a development environment, the desired result is indeed a stable platform and if something is broken people will be working to fix it. Starting -------- Once you're subscribed to the -current mailing list, there are a couple of different ways to get FreeBSD-current onto your system. Which is best for you will depend on your circumstances. - FTP : You can install a FreeBSD-current snapshot via FTP just like a release version. FreeBSD-current snapshots are normally built daily and can be downloaded from ftp://current.freebsd.org/. - CDROM : Walnut Creek CDROM occasionally release a FreeBSD-current snapshot CDROM, and other vendors may too. These are generally a bargain, as they come with a copy of the CVS repository which can save you a lot of download time. You can install from a snapshot CDROM in exactly the same fashion as you would a release version. Be careful though; a snapshot more than a few months old may be just as tough to upgrade from as a previous release. - Bootstrap : If you have the FreeBSD CVS repository on your system you can checkout a copy of the -current source tree and bootstrap a previous release system. You can also get the -current source using CVSup or CTM (see below). Bootstrapping may take a little perseverance, but that's good practice for later. Note that bootstrapping from anything older than the most recent release is something best left to the truly adventurous. If you have problems bootstrapping, and really can't get -current going any other way then you should post a concise message to the FreeBSD-current mailing list clearly detailing what you are trying to do, the release you are bootstrapping from, and any error messages that you receive during the process. Keeping -current ---------------- Once you have a -current system up and running: Congratulations, it's obsolete! FreeBSD-current changes daily, and part of running a -current system is keeping up to date. There are two parts to keeping your system -current; getting the source, and building it. You can obtain the source in two forms; either the raw source tree, or the CVS repository. The former requires around 100MB of disk space, the latter perhaps three times that; expect these values to grow with time. The raw source tree is all that's required to build the source, however the CVS repository is useful if you are interested in tracking or becoming involved with development. In particular, the CVS repository can be invaluable if you are trying to locate a new problem. There are two distribution strategies in common use for keeping your source up to date, named after the tools used to perform the updating : CVSup and CTM. CVSup ''''' CVSup replaces an older tool, 'sup' (the Source Update Protocol), and is the preferred method for tracking the -current source tree. It requires an active network connection and provides guaranteed-accuracy updates of your CVS repository or checked-out source tree. CVSup can also repair a damaged or modified repository or tree. If you have a -stable or -current system up and running, sample control files for CVSup are located in /usr/share/examples/cvsup. You can get CVSup itself from the FreeBSD ports collection. CTM ''' CTM can be interpreted as 'CVS Thru eMail'; it provides updates for your CVS repository or source tree via email messages. CTM is ideal if your network connection is indirect, expensive or otherwise cannot support CVSup. Checking out with CVS ''''''''''''''''''''' If you are fetching the CVS repository, there is one important step required before you can build anything. This is known as "checking out" the source; literally you will generate a complete copy of the -current source tree from the information in the repository. The source tree wants to be in /usr/src, and the intermediate files generated during the build will be placed under /usr/obj. If the filesystem containing /usr doesn't have ~250MB of free space, you will need to create directories elsewhere and use symbolic links to refer to the new locations. To check out the source tree, go to where the 'src' directory is to be located and issue the command : # cvs -d checkout src This will create a directory 'src' and populate it with the source tree. When the repository is updated by CVSup or CTM you can propagate the changes to this source tree by making the src directory your current directory and saying : # cvs update -Pd Building the World '''''''''''''''''' Once you have your source tree checked out, make sure the 'src' tree is reachable as /usr/src, become root and change to the /usr/src directory. Now is the time to select your build options. If you've built the FreeBSD tree before, you will be familiar with these. Options are set via environment variables, or by editing /etc/make.conf. Using the environment, a variable is set with # setenv VARIABLE and unset (if you set one by accident) with # unset VARIABLE The common variables and their uses are : NOCLEAN Do not clean out the old build tree. This can save on build time, but may introduce subtle problems. NOSECURE Do not build the export-restricted modules. If you haven't downloaded the source for these, then you won't want to try to build them. This is a good option to use if you are not in the USA. NOGAMES Don't rebuild the games. If you don't have or want them installed, set this. NOSHARE Don't rebuild /usr/share. This can save some time, and if /usr/share (containing manpages, data files and examples) hasn't changed much it won't cause you any trouble. NOPROFILE Don't build the profiling libraries. If you're not doing any development involving profiling, this can save a considerable amount of time and space. If you don't know what profiling libraries are, you don't want them. Once your options are set, start the build. It's generally a good idea to keep a record of the build, in case there are problems and you want to look over it. There are two good ways to do this. The first uses the 'script' command, which arranges a transcript of a session. You would say : # script Script started, output file is typescript # make world When the build has finished, use 'exit' to close the script. The second method runs the build in the background, and watches it with the 'tail' command. The advantage of this method is that you can let the build run without having to watch it all the time; you can come back to check on it at your leisure. To do this, you would say : # make world >& makelog # tail -f makelog You can hit ^C at any time to exit the 'tail' command, and then reissue it whenever you want to check on the build. A world build transcript generated like this will generally be around the 7 megabyte mark; you should make sure you have space for it. If you are unsure about whether the buid will work, and would prefer to make sure it builds properly before allowing it to install over your running system, you can use the 'buildworld' rather than 'world' target. This will compile everything, but not install it. Once you are happy that the build has completed OK, you can invoke the 'installworld' target, which will install the built world. If your 'buildworld' is failing on something that you think is trivial you can add the '-k' option to the make command. This will cause make to continue after an error, rather than stopping the build. If you have built with '-k' you should examine the build log very carefully before proceeding to install, as it is possible to make an enormous mess like this. Building the Kernel ''''''''''''''''''' Changes in -current often require coordinated rebuilding of both the 'world' (userland) and the kernel. Normally you should build a new kernel after you have built the world, but before you reboot. There are a couple of important points to bear in mind regarding the kernel : - The 'config' program is closely tied to the kernel. It is normally built as part of userland, but it can also be built manually with # cd /usr/src/usr.sbin/config # make depend all install clean Using an outdated 'config' program can cause strange errors when configuring or building a kernel. - The kernel and LKMs are closely relatd. Mismatches can cause fatal kernel errors or strange behaviour. LKMs are also built as part of userland. Changes to -current may require matching changes in your kernel configuration file. These are normally reflected in changes to the LINT or GENERIC files, and/or described in messages posted to the mailing list. Once the kernel has been built and installed, reboot the system. It is generally a good idea to do this at this point, in order to ensure that the running kernel and userland programs correspond. When Things go Wrong -------------------- Problems with FreeBSD-current can generally be divided into three groups : - It won't build. - It won't boot. - Something funny happens when... It won't Build '''''''''''''' If it won't build, and the reason isn't immediately obvious, there are several steps you should take. Always remember to go through these in order; skipping them may miss the problem and waste more of your time. - Completely remove the object tree and start again. You can do this with : # chflags -R noschg /usr/obj # rm -rf /usr/obj/* Normally the 'world' target will do this for you, unless you have NOCLEAN or one of the related non-cleaning options set. - Completely remove the source tree and start again. This is normally only a good idea if you have a local copy of the CVS repository. Make sure you make a backup of your kernel configuration files, and then remove /usr/src and everything in it. Check it out or update it as above. - Update your local sources, either by waiting for the next CTM diff, or re-running CVSup, and then perform a 'cvs update' if you have a local repository. It is possible that your last update came in the middle of a compound change to the source tree, and that updating will correct things. - Wait a day or two, and watch the mailing list for messages about your problem. If the problem is widespread (ie. not a result of local circumstances) then other people will have encountered it, and a fix is likely to be discussed rapidly. - If you cannot obtain a clean build after a couple of days of watching the list and updating your source tree, you should post a message to the -current list describing your problem. It is extremely important that you provide enough information to diagnose your problem; without this information your post is likely to be ignored because it represents a great deal of work. At the very least, your post should include : x The last update date of your source tree. If you are using CVSup, the time at which you last ran CVSup, and the server you updated from. If you are using CTM, the number of the last CTM delta that you have applied. x An excerpt from the the end of the build transcript above. Try to include the last few lines of commands before the "error 1" lines, as these will generally contain information needed to locate the problem. x A list of all the build options that were enabled. You may be asked for additional information, or to try various things; be prepared to become involved in solving your problem, and look to learn from the experience. In time, you may be able to apply the solutions you have discovered to someone else's problem, and in turn help them out. It Won't Boot ''''''''''''' Occasionally you will encounter a newly-built kernel that won't boot. "Won't boot" may mean that it produces a panic message, or a fatal trap while starting up, or the system may freeze up, or reboot spontaenously. There can be a number of reasons for these failures; the two most common are : - You have stale LKMs. - A new change to the kernel is broken. You should always check for an LKM problem before suspecting that the kernel is broken. It is easy to check whether you have such a problem : - Boot single-user (specify '-s' at the boot: prompt) - Mount the root filesystem read/write : # mount / - Move the LKM directory out of the way : # mv /lkm /lkm.bad - Continue to multi-user : # exit If this fixes your problem, then you should remove all of the old LKMs, and install a new set. This can be achieved with : # mv /lkm.bad /lkm # rm -rf /lkm/* # cd /usr/src/lkm # make depend all install clean Note that both this technique and the one above for config may make temporary files in the source tree; this is dirty but expedient. If the kernel doesn't get to the single-user stage, or if it still fails, then it is likely that the kernel is broken. You should boot the backup kernel, which is a copy of the previous kernel which was made when you installed the new one. This is achieved by entering the name of the backup kernel at the 'boot:' prompt. You can copy the backup kernel over the newer kernel with the commands : # chflags noschg /kernel # cp /kernel.old /kerne # chflags schg /kernel Once you have your system up and running again in this fashion, you should again keep an eye on the FreeBSD-current mailing list. It's possible that your problem will already have been noticed, and a fix may have been made already. If your problem persists after several days and several rebuilds, you can participate in tracking it down as follows. It is important to provide a lot of information about kernel problems, as they can be very subtle. You should build a kernel with the debugger enabled, ie. with options DDB in the configuration file. Ideally, the kernel should be configured with the '-g' flag to config, and installed in this form. Be aware that this will result in a kernel that may be up to 10 megabytes in size, as it includes copious debugging information. When the system panics, or encounters a trap, it will print a message giving details of the panic or trap, and leave the system in the debugger at the 'ddb>' prompt. At this point, you should make a note of all of this information. It is important that you do this, as it identifies the basic nature of the problem, its location and the state of the system when the problem occurred. You should then issue the 'trace' command to ddb, and note all of its output. This provides more vital information as to the state of the system. Armed with this information, you are ready to post to the FreeBSD-current mailing list. You should include in your message : - The trap/panic message and 'trace' output. - The last update date/CTM number from which the kernel was built. - Your hardware configuration details. - The kernel configuration file from which the kernel was generated. - The activity which causes the problem (booting, heavy load, etc.) If your problem is due to a fault which is triggered by your system configuration or load profile you may be asked to try making changes to the source in order to locate a suitable fix. These changes are often provided in the form of patches, which are discussed below. Something Funny happens When... ''''''''''''''''''''''''''''''' You may notice that the new kernel or userland doesn't behave 'quite right'. A command may behave differently, or the system may not respond as it did previously under some circumstances. In the worst case, you may find that the kernel may panic or encounter a fatal trap. Under these circumstances, it is important to characterise the nature of the fault. This means that you should attempt to establish, by trial and error, exactly what it is that is causing the problem to manifest. It may be a combination of arguments to a command; a particular sort of system load, or any of many other things. If the system is panicing or stopping on a trap, build and install a kernel with DDB and preferably debugging enabled as above. Otherwise, gather as much information about the problem and any identified causes for it, and watch the FreeBSD-current mailing list. If the problem isn't discussed after a couple of days, post your findings. As always, provide as much information as you believe may be relevant, and be prepared to become involved in finding the solution. Patching it Up --------------- When you are chasing a problem with your -current system, or if you want to try out something so new that it hasn't been added yet, you may encounter 'patch' or 'diff' files. These files contain information which allows you to make automated changes to your source tree. They are fed as input to the 'patch' program, usually as : # patch -p < It is important to be in the correct directory when applying a patch. If you can't establish this from the details at the top of the patch file, be sure to ask the author. You can check that a patch will apply by supplying the '-C' option to patch; if any hunks are rejected, the patch will not apply cleanly. Note that if you apply a patch to your source tree, CTM will no longer be able to update the file(s) patched. The patch program makes a backup of patched files with the suffix '.orig'; after you have tested a patch you may wish to move these files back to their original names. If you are using a CVS repository, CVS will try to merge your patched changes with new changes to the repository. This can occasionally result in files that cannot be used to build from, as they contain merge comments. The easiest way to deal with such a file is to delete it and then say : # cvs update -Pd If you are using CVSup to update your source tree directly, it will replace any patched files with the current version. How Often? ---------- Now you are running -current, how often should you update? This will depend on your personal schedule, the load and demand on your system, and the general health of -current. In general once a week is a good number if you are keen to keep up to date. Once a month is good if you want to avoid falling too far behind. Another alternative is to wait for a few days after a new major feature of interest is announced, to make sure it is stable and worthwhile. Wrapup ------ FreeBSD-current can be a rewarding and useful environment. Users of -current provide vital feedback to the developer community, who in turn depend on this feedback as a check on their work. -current users must be prepared to work with developers in the pursuit of a stable, reliable, high-performance system, and in turn developers must work with users towards the same goals. Using -current can be a lot more work than a release or -stable version, but the rewards are well worth the effort. From owner-freebsd-current Sun Sep 28 10:29:39 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id KAA14308 for current-outgoing; Sun, 28 Sep 1997 10:29:39 -0700 (PDT) Received: from atlantis.nconnect.net (root@atlantis.nconnect.net [207.227.50.2]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id KAA14302 for ; Sun, 28 Sep 1997 10:29:35 -0700 (PDT) Received: from nconnect.net (dial180.nconnect.net [207.227.50.180]) by atlantis.nconnect.net (8.8.4/8.7.3) with ESMTP id MAA19239; Sun, 28 Sep 1997 12:32:01 -0500 (CDT) Message-ID: <342E934A.79144293@nconnect.net> Date: Sun, 28 Sep 1997 12:26:34 -0500 From: Randy DuCharme Organization: Astrolab Development X-Mailer: Mozilla 4.03b8 [en] (X11; I; FreeBSD 3.0-CURRENT i386) MIME-Version: 1.0 To: Simon Shapiro CC: current@freebsd.org Subject: Re: Make world failure References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Simon Shapiro wrote: > > rm -rf /usr/obj/* > > I have been digging too. Not this long, though. When in doubt, blow > /usr/obj. > > Note: There is no logical, mathematical or sceitific reason for the above > (that I am aware of). > Many thanks to all of you! I must have missed that piece of commit mail that Bruce mentioned. -- Randall D DuCharme Systems Engineer Novell, Microsoft, and UNIX Networking Support Computer Specialists BSDI Internet Success Partners 414-253-9998 414-253-9919 (fax) BSD/OS Authorized Resellers From owner-freebsd-current Sun Sep 28 11:54:50 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id LAA17707 for current-outgoing; Sun, 28 Sep 1997 11:54:50 -0700 (PDT) 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 LAA17698 for ; Sun, 28 Sep 1997 11:54:46 -0700 (PDT) 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 LAA03409; Sun, 28 Sep 1997 11:54:25 -0700 (PDT) To: Mike Smith cc: current@FreeBSD.ORG Subject: Re: Staying -current with FreeBSD In-reply-to: Your message of "Mon, 29 Sep 1997 02:39:39 +0930." <199709281709.CAA06890@word.smith.net.au> Date: Sun, 28 Sep 1997 11:54:25 -0700 Message-ID: <3406.875472865@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > Eep. It's turned into something more of a Really Big Frothing Penguin. > Any idea where this monstrosity belongs? (Another newsletter artikel, > Jordan?) Indeed! In fact, I like this one better than your other one. ;-) Jordan P.S. Though both will also be fine, don't get me wrong - we're not exactly bursting at the seams with articles. ;) From owner-freebsd-current Sun Sep 28 12:15:53 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id MAA18313 for current-outgoing; Sun, 28 Sep 1997 12:15:53 -0700 (PDT) Received: from zibbi.mikom.csir.co.za (zibbi.mikom.csir.co.za [146.64.24.58]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id MAA18304 for ; Sun, 28 Sep 1997 12:15:43 -0700 (PDT) Received: (from jhay@localhost) by zibbi.mikom.csir.co.za (8.8.7/8.8.7) id VAA02446; Sun, 28 Sep 1997 21:15:28 +0200 (SAT) From: John Hay Message-Id: <199709281915.VAA02446@zibbi.mikom.csir.co.za> Subject: Re: ed0 not found on reboots In-Reply-To: <199709280959.CAA19719@implode.root.com> from David Greenman at "Sep 28, 97 02:59:11 am" To: dg@root.com Date: Sun, 28 Sep 1997 21:15:28 +0200 (SAT) 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 have updated my -current box for the first time in about 6 weeks and > >found that with the latest kernel my ed0 device is only found atfter > >a power up or physical reset. After reboot or shutdown -r now it isn't > >found. Has anyone seen something like this? > > > >My machine is a 90MHz Pentium and the ed0 device (when found) probes > >like this: > >===== > >ed0 at 0x280-0x29f irq 5 maddr 0xd8000 msize 16384 on isa > >ed0: address 00:00:c0:70:bf:94, type SMC8216/SMC8216C (16 bit) > >===== > > I had a report of an NE2000 clone not passing the station address checksum > after a warmboot, but this is the first problem I've heard with the SMC > Ultra. The only significant change that's been made is the 0WS flag is turned > on, but this should only affect accesses to the shared memory. You might want > to add some printf's to the probe code to find out which test is failing. > It fails in ed_probe_WD80x3() when it reads the 8 bytes out of the PROM. The bytes read are totally bogus. I tried to clear the ED_WD_LAAR register just before it reads the PROM, but that didn't help. What did fix it was to switch off ED_WD790_GCR_ZWSEN just before reading the PROM. I attach the patch that made it work, although it is probably too invasive at such an early stage of the probe. Maybe it would be better to switch it on just before memory access and off after it like the 16bit memory access? John -- John Hay -- John.Hay@mikom.csir.co.za --- if_ed.c.org Thu Sep 25 21:35:19 1997 +++ if_ed.c Sun Sep 28 20:42:52 1997 @@ -469,6 +469,8 @@ * this, though: some clone WD boards don't pass the checksum test. * Danpex boards for one. */ + outb(sc->asic_addr + ED_WD790_GCR, inb(sc->asic_addr + + ED_WD790_GCR) & ~ED_WD790_GCR_ZWSEN); for (sum = 0, i = 0; i < 8; ++i) sum += inb(sc->asic_addr + ED_WD_PROM + i); From owner-freebsd-current Sun Sep 28 12:42:54 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id MAA19363 for current-outgoing; Sun, 28 Sep 1997 12:42:54 -0700 (PDT) Received: from pluto.plutotech.com (root@mail.plutotech.com [206.168.67.137]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id MAA19355 for ; Sun, 28 Sep 1997 12:42:48 -0700 (PDT) Received: from narnia.plutotech.com (narnia.plutotech.com [206.168.67.130]) by pluto.plutotech.com (8.8.5/8.8.5) with ESMTP id NAA14122 for ; Sun, 28 Sep 1997 13:42:47 -0600 (MDT) Message-Id: <199709281942.NAA14122@pluto.plutotech.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: current@FreeBSD.org Subject: Re: cvs commit: src/sys/i386/isa apic_vector.s icu_vector.s In-reply-to: Your message of "Sun, 28 Sep 1997 12:30:03 PDT." <199709281930.MAA10261@freefall.freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 28 Sep 1997 13:42:33 -0600 From: "Justin T. Gibbs" Sender: owner-freebsd-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk Those of you complaining of "mysterious hangs", NFS related or otherwise, this change will probably fix your problem. >gibbs 1997/09/28 12:30:03 PDT > > Modified files: > sys/i386/isa apic_vector.s icu_vector.s > Log: > Fix a serious bug I introduced while adding in support for CAM interrupts. > It seems I didn't count my 0's properly when adding the new masks into > icu_vector.s pushing SWI_AST_MASK off the end of the array and screwing > up the indexing for SWI_CLOCK_MASK. > > Fix the bug icu_vector.s and also reformat the code in both icu_vector.s and > apic_vector.s so that it will be much harder to make the same mistake in > the future. > > Submitted by: Bruce Evans > > Revision Changes Path > 1.23 +3 -2 src/sys/i386/isa/apic_vector.s > 1.6 +7 -5 src/sys/i386/isa/icu_vector.s > -- Justin T. Gibbs =========================================== FreeBSD: Turning PCs into workstations =========================================== From owner-freebsd-current Sun Sep 28 12:49:40 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id MAA19528 for current-outgoing; Sun, 28 Sep 1997 12:49:40 -0700 (PDT) Received: from ppp1656.on.sympatico.ca (ppp1656.on.sympatico.ca [206.172.249.120]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id MAA19523 for ; Sun, 28 Sep 1997 12:49:31 -0700 (PDT) Received: from localhost (tim@localhost) by ppp1656.on.sympatico.ca (8.8.7/8.8.7) with SMTP id PAA02415; Sun, 28 Sep 1997 15:47:38 -0400 (EDT) Date: Sun, 28 Sep 1997 15:47:38 -0400 (EDT) From: Tim Vanderhoek Reply-To: ac199@hwcn.org To: Mike Smith cc: current@FreeBSD.ORG Subject: Re: Staying -current with FreeBSD In-Reply-To: <199709281709.CAA06890@word.smith.net.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 Mon, 29 Sep 1997, Mike Smith wrote: > - FTP : You can install a FreeBSD-current snapshot via FTP just like > a release version. FreeBSD-current snapshots are normally built daily > and can be downloaded from ftp://current.freebsd.org/. You can also use sysinstall to upgrade in a piecemeal fashion with the "custom" install and "custom" distributions. Of course, this puts a greater burden on the user to handle details (eg. copy /etc/ to a temp location before installing the "bin" dist) and to make sure that things are sufficiently synchronized on their own machine. -- tIM...HOEk OPTIMIZATION: the process of using many one-letter variables names hoping that the resultant code will run faster. From owner-freebsd-current Sun Sep 28 14:17:49 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id OAA23361 for current-outgoing; Sun, 28 Sep 1997 14:17:49 -0700 (PDT) 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 OAA23356 for ; Sun, 28 Sep 1997 14:17:40 -0700 (PDT) Received: (from jmg@localhost) by hydrogen.nike.efn.org (8.8.7/8.8.7) id OAA01549; Sun, 28 Sep 1997 14:17:19 -0700 (PDT) Message-ID: <19970928141718.10371@hydrogen.nike.efn.org> Date: Sun, 28 Sep 1997 14:17:18 -0700 From: John-Mark Gurney To: Mike Smith Cc: current@FreeBSD.ORG Subject: Re: Staying -current with FreeBSD References: <199709281709.CAA06890@word.smith.net.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.69 In-Reply-To: <199709281709.CAA06890@word.smith.net.au>; from Mike Smith on Mon, Sep 29, 1997 at 02:39:39AM +0930 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 Mike Smith scribbled this message on Sep 29: > You can obtain the source in two forms; either the raw source tree, or > the CVS repository. The former requires around 100MB of disk space, > the latter perhaps three times that; expect these values to grow with > time. The raw source tree is all that's required to build the source, > however the CVS repository is useful if you are interested in tracking or > becoming involved with development. In particular, the CVS repository > can be invaluable if you are trying to locate a new problem. -current source tree (as of a few days ago) about 181megs... cvs tree as of last night at about 11pm PST is about 390megs... -- 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 Sun Sep 28 14:46:36 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id OAA24937 for current-outgoing; Sun, 28 Sep 1997 14:46:36 -0700 (PDT) Received: from sendero-ppp.i-connect.net (sendero-ppp.i-Connect.Net [206.190.143.100]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id OAA24927 for ; Sun, 28 Sep 1997 14:46:33 -0700 (PDT) Received: (qmail 15574 invoked by uid 1000); 28 Sep 1997 21:46:49 -0000 Message-ID: X-Mailer: XFMail 1.2-alpha-092397 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: Date: Sun, 28 Sep 1997 14:46:49 -0700 (PDT) Organization: Atlas Telecom From: Simon Shapiro To: Bob Bishop Subject: RE: Make world failure Cc: Randy DuCharme , current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Hi Bob Bishop; On 28-Sep-97 you wrote: ... > I had exactly the same problem. Working my way through the > over-the-counter > remedies I too reached the rm -rf /usr/obj/* stage. > > Actually, I cd to /usr/obj and rm -rf *. It refuses to remove several > leaf > files, citing "Operation not permitted" (errno 1 I assume). But I'm > root! chflags -R noschg /usr/obj ... > works. Wierd or what? I suspect this is a side effect of doing make install into /usr/obj. The whole thing is wierd. A major percentage of the traffic in this list evolves around make problems. It is an artifact of the language. --- Sincerely Yours, Simon Shapiro Atlas Telecom Senior Architect 14355 SW Allen Blvd., Suite 130 Beaverton OR 97005 Shimon@i-Connect.Net Voice: 503.799.2313 From owner-freebsd-current Sun Sep 28 15:27:13 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id PAA26754 for current-outgoing; Sun, 28 Sep 1997 15:27:13 -0700 (PDT) Received: from sendero-ppp.i-connect.net (sendero-ppp.i-Connect.Net [206.190.143.100]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id PAA26743 for ; Sun, 28 Sep 1997 15:27:05 -0700 (PDT) Received: (qmail 19900 invoked by uid 1000); 28 Sep 1997 22:27:26 -0000 Message-ID: X-Mailer: XFMail 1.2-alpha-092397 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <199709281014.MAA01564@greenpeace.grondar.za> Date: Sun, 28 Sep 1997 15:27:26 -0700 (PDT) Organization: Atlas Telecom From: Simon Shapiro To: Mark Murray Subject: Re: HEAR YE! HEAR YE! New Kerberos! Cc: current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Hi Mark Murray; On 28-Sep-97 you wrote: > A couple of hours later, and it was not too painful! > > I am done now. Those of you wanting to test this new Kerberos should > please > > 1) rm -rf /usr/include/kerberosIV > 2) cp /usr/src/etc/services /etc > 3) in /etc/make.conf replace > MAKE_EBONES= yes > with > MAKE_KERBEROS4= yes > 4) Make world. > > Please let me know if you have problems. make buildworld produces: install -C -o bin -g bin -m 444 /usr/src/3.0/src/secure/lib/libdes/des.h /usr/obj/usr/src/3.0/src/tmp/usr/include cd /usr/src/3.0/src/kerberosIV/lib/libacl && /usr/obj/usr/src/3.0/src/tmp/usr/bin/make beforeinstall make: don't know how to make /usr/src/3.0/src/kerberosIV/lib/libacl/../../../crypto/kerberosIV/lib/acl/ac l.h. Stop *** Error code 2 By the way, the problem with make shooting itself in the foot early in the build is still there. --- Sincerely Yours, Simon Shapiro Atlas Telecom Senior Architect 14355 SW Allen Blvd., Suite 130 Beaverton OR 97005 Shimon@i-Connect.Net Voice: 503.799.2313 From owner-freebsd-current Sun Sep 28 16:26:39 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id QAA00216 for current-outgoing; Sun, 28 Sep 1997 16:26:39 -0700 (PDT) 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 QAA00210 for ; Sun, 28 Sep 1997 16:26:28 -0700 (PDT) Received: (from grog@localhost) by freebie.lemis.com (8.8.7/8.8.5) id IAA11741; Mon, 29 Sep 1997 08:56:18 +0930 (CST) Message-ID: <19970929085618.64898@lemis.com> Date: Mon, 29 Sep 1997 08:56:18 +0930 From: Greg Lehey To: John-Mark Gurney Cc: Mike Smith , current@FreeBSD.ORG Subject: Re: Staying -current with FreeBSD References: <199709281709.CAA06890@word.smith.net.au> <19970928141718.10371@hydrogen.nike.efn.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.84e In-Reply-To: <19970928141718.10371@hydrogen.nike.efn.org>; from John-Mark Gurney on Sun, Sep 28, 1997 at 02:17:18PM -0700 Organisation: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8250 Fax: +61-8-8388-8250 Mobile: +61-41-739-7062 WWW-Home-Page: http://www.lemis.com/~grog Fight-Spam-Now: http://www.cauce.org Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Sun, Sep 28, 1997 at 02:17:18PM -0700, John-Mark Gurney wrote: > Mike Smith scribbled this message on Sep 29: >> You can obtain the source in two forms; either the raw source tree, or >> the CVS repository. The former requires around 100MB of disk space, >> the latter perhaps three times that; expect these values to grow with >> time. The raw source tree is all that's required to build the source, >> however the CVS repository is useful if you are interested in tracking or >> becoming involved with development. In particular, the CVS repository >> can be invaluable if you are trying to locate a new problem. > > -current source tree (as of a few days ago) about 181megs... > cvs tree as of last night at about 11pm PST is about 390megs... What are you including in these figures? About a month ago, I calculated: Table 16-1. Approximate source tree sizes +-------------------------+-----------+ |Component | Size (MB) | +-------------------------+-----------+ |Repository src/sys | 53 | |Repository src | 330 | |Repository ports | 36 | |Source tree /usr/src/sys | 65 | |Source tree /usr/src | 372 | |Source tree /usr/ports | 160 | |Object tree src | 160 | +-------------------------+-----------+ I've just checked /usr/src again: # du -s /usr/src/ 383294 /usr/src/ Am I missing something? Greg From owner-freebsd-current Sun Sep 28 17:06:31 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id RAA02283 for current-outgoing; Sun, 28 Sep 1997 17:06:31 -0700 (PDT) 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 RAA02277 for ; Sun, 28 Sep 1997 17:06:21 -0700 (PDT) Received: (from jmg@localhost) by hydrogen.nike.efn.org (8.8.7/8.8.7) id RAA00800; Sun, 28 Sep 1997 17:05:10 -0700 (PDT) Message-ID: <19970928170510.39583@hydrogen.nike.efn.org> Date: Sun, 28 Sep 1997 17:05:10 -0700 From: John-Mark Gurney To: Greg Lehey Cc: Mike Smith , current@FreeBSD.ORG Subject: Re: Staying -current with FreeBSD References: <199709281709.CAA06890@word.smith.net.au> <19970928141718.10371@hydrogen.nike.efn.org> <19970929085618.64898@lemis.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.69 In-Reply-To: <19970929085618.64898@lemis.com>; from Greg Lehey on Mon, Sep 29, 1997 at 08:56:18AM +0930 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 Greg Lehey scribbled this message on Sep 29: > On Sun, Sep 28, 1997 at 02:17:18PM -0700, John-Mark Gurney wrote: > > Mike Smith scribbled this message on Sep 29: > >> You can obtain the source in two forms; either the raw source tree, or > >> the CVS repository. The former requires around 100MB of disk space, > >> the latter perhaps three times that; expect these values to grow with > >> time. The raw source tree is all that's required to build the source, > >> however the CVS repository is useful if you are interested in tracking or > >> becoming involved with development. In particular, the CVS repository > >> can be invaluable if you are trying to locate a new problem. > > > > -current source tree (as of a few days ago) about 181megs... > > cvs tree as of last night at about 11pm PST is about 390megs... > > What are you including in these figures? About a month ago, I > calculated: > > Table 16-1. Approximate source tree sizes > > +-------------------------+-----------+ > |Component | Size (MB) | > +-------------------------+-----------+ > |Repository src/sys | 53 | > |Repository src | 330 | > |Repository ports | 36 | > |Source tree /usr/src/sys | 65 | > |Source tree /usr/src | 372 | > |Source tree /usr/ports | 160 | > |Object tree src | 160 | > +-------------------------+-----------+ > > I've just checked /usr/src again: > > # du -s /usr/src/ > 383294 /usr/src/ > > Am I missing something? arg.. that's right... I grab these cvs parts: src-all www cvs-crypto ports-all doc-all my src tree is simply, cvs co src in a directory.. and updated with cvs update . of course I have: update -Pd co -P in my .cvsrc file.. do your /usr/src include object files or possibly kernel builds? I had to remove about 16megs from my du -sk srcdir because of a kernel build I had in there... now I just did a du -sk of the obj dir for my last build world 158megs -- 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 Sun Sep 28 17:23:44 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id RAA03284 for current-outgoing; Sun, 28 Sep 1997 17:23:44 -0700 (PDT) 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 RAA03279 for ; Sun, 28 Sep 1997 17:23:39 -0700 (PDT) Received: from right.PCS (right.PCS [148.105.10.31]) by sumatra.americantv.com (8.8.5/8.8.5) with ESMTP id TAA23354; Sun, 28 Sep 1997 19:23:13 -0500 (CDT) Received: (from jlemon@localhost) by right.PCS (8.6.13/8.6.4) id TAA12977; Sun, 28 Sep 1997 19:22:41 -0500 Message-ID: <19970928192241.25439@right.PCS> Date: Sun, 28 Sep 1997 19:22:41 -0500 From: Jonathan Lemon To: Greg Lehey Cc: John-Mark Gurney , Mike Smith , current@FreeBSD.ORG Subject: Re: Staying -current with FreeBSD References: <199709281709.CAA06890@word.smith.net.au> <19970928141718.10371@hydrogen.nike.efn.org> <19970929085618.64898@lemis.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.61.1 In-Reply-To: <19970929085618.64898@lemis.com>; from Greg Lehey on Sep 09, 1997 at 08:56:18AM +0930 Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Sep 09, 1997 at 08:56:18AM +0930, Greg Lehey wrote: > > +-------------------------+-----------+ > |Component | Size (MB) | > +-------------------------+-----------+ > |Repository src/sys | 53 | > |Repository src | 330 | > |Repository ports | 36 | > |Source tree /usr/src/sys | 65 | > |Source tree /usr/src | 372 | > |Source tree /usr/ports | 160 | > |Object tree src | 160 | > +-------------------------+-----------+ Just a minute. Are you saying that the CVS src repository (330 MB) is smaller than the checked out version of the /usr/src tree (372 MB)? I think you're probably forgetting about src/sys/compile. -- Jonathan From owner-freebsd-current Sun Sep 28 17:33:20 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id RAA03753 for current-outgoing; Sun, 28 Sep 1997 17:33:20 -0700 (PDT) Received: from sendero-ppp.i-connect.net (sendero-ppp.i-Connect.Net [206.190.143.100]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id RAA03747 for ; Sun, 28 Sep 1997 17:33:15 -0700 (PDT) Received: (qmail 16294 invoked by uid 1000); 29 Sep 1997 00:33:37 -0000 Message-ID: X-Mailer: XFMail 1.2-alpha-092597 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <199709281113.VAA16774@godzilla.zeta.org.au> Date: Sun, 28 Sep 1997 17:33:37 -0700 (PDT) Organization: Atlas Telecom From: Simon Shapiro To: Bruce Evans Subject: RE: Make world failure Cc: current@FreeBSD.ORG, randyd@nconnect.net Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Hi Bruce Evans; On 28-Sep-97 you wrote: ... > Untested fix (for -current): > > diff -c2 Makefile~ Makefile > *** Makefile~ Sat Sep 27 01:42:58 1997 > --- Makefile Sat Sep 27 01:53:47 1997 The net effect of this fix is the fastest make buildworld ever experienced :-) It build make allright. But this is all it did here. Made make and exited quietly. Wiping /usr/obj out still works. --- Sincerely Yours, Simon Shapiro Atlas Telecom Senior Architect 14355 SW Allen Blvd., Suite 130 Beaverton OR 97005 Shimon@i-Connect.Net Voice: 503.799.2313 From owner-freebsd-current Sun Sep 28 17:51:25 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id RAA04718 for current-outgoing; Sun, 28 Sep 1997 17:51:25 -0700 (PDT) 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 RAA04713 for ; Sun, 28 Sep 1997 17:51:20 -0700 (PDT) Received: (from grog@localhost) by freebie.lemis.com (8.8.7/8.8.5) id KAA12157; Mon, 29 Sep 1997 10:21:10 +0930 (CST) Message-ID: <19970929102109.27252@lemis.com> Date: Mon, 29 Sep 1997 10:21:09 +0930 From: Greg Lehey To: Jonathan Lemon Cc: John-Mark Gurney , Mike Smith , current@FreeBSD.ORG Subject: Re: Staying -current with FreeBSD References: <199709281709.CAA06890@word.smith.net.au> <19970928141718.10371@hydrogen.nike.efn.org> <19970929085618.64898@lemis.com> <19970928192241.25439@right.PCS> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.84e In-Reply-To: <19970928192241.25439@right.PCS>; from Jonathan Lemon on Sun, Sep 28, 1997 at 07:22:41PM -0500 Organisation: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8250 Fax: +61-8-8388-8250 Mobile: +61-41-739-7062 WWW-Home-Page: http://www.lemis.com/~grog Fight-Spam-Now: http://www.cauce.org Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Sun, Sep 28, 1997 at 07:22:41PM -0500, Jonathan Lemon wrote: > On Sep 09, 1997 at 08:56:18AM +0930, Greg Lehey wrote: >> >>> -------------------------+-----------+ >>> Component | Size (MB) | >>> -------------------------+-----------+ >>> Repository src/sys | 53 | >>> Repository src | 330 | >>> Repository ports | 36 | >>> Source tree /usr/src/sys | 65 | >>> Source tree /usr/src | 372 | >>> Source tree /usr/ports | 160 | >>> Object tree src | 160 | >>> -------------------------+-----------+ > > Just a minute. Are you saying that the CVS src repository (330 MB) is > smaller than the checked out version of the /usr/src tree (372 MB)? Yes. > I think you're probably forgetting about src/sys/compile. No. I just didn't mention it :-) The intention in this table (out of the draft second edition of "The Complete FreeBSD") is to show people how much a typical tree holds. As such, it includes objects and such. Here's what comes after the table: The size of /usr/src/sys includes the files involved in a single kernel build. This changes the size of /usr/src as well, of course. Similiarly, the size of /usr/ports includes a few ports. It will, of course, grow extremely large if you start porting all available packages. Note, however, that that's less than the 53 MB in /usr/src/sys. Unfortunately, I've just discovered my mistake: I had the ports tree inside /usr/src, so it's been counted twice. Take 160 MB off that figure... (crawls into corner and dies of shame) Greg From owner-freebsd-current Sun Sep 28 20:37:25 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id UAA12608 for current-outgoing; Sun, 28 Sep 1997 20:37:25 -0700 (PDT) Received: from earth.mat.net (root@earth.mat.net [206.246.122.2]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id UAA12600 for ; Sun, 28 Sep 1997 20:37:20 -0700 (PDT) Received: from Journey2.mat.net (journey2.mat.net [206.246.122.116]) by earth.mat.net (8.8.7/8.6.12) with SMTP id XAA21562; Sun, 28 Sep 1997 23:37:08 -0400 (EDT) Date: Sun, 28 Sep 1997 23:37:07 -0400 (EDT) From: Chuck Robey X-Sender: chuckr@Journey2.mat.net To: Carlo Dapor cc: freebsd-current@FreeBSD.ORG Subject: Re: Suggestions on some make rules as far as the -o option is concerned In-Reply-To: <199709261645.SAA06025@nessie.ethz.ch> 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, 26 Sep 1997, Carlo Dapor wrote: > Hello, everybody > > My situation is this. > I have a Pentium 90 MHz machine, freshly installed with 2.2.2. > I unpacked src-2.2.0400xEmpty.gz successfully. I applied the > patches up until src-2.2.0447 inclusively. > Furthermore, I ran a 'make install' in /usr/src/share/mk. > > In attempt to make world the success was always broken when some > file had to be build by bison. > The command line looked like > bison -d /some/directory/where/the/dot-y-files-lies/file.y -o foo.c Excuse me, why are you using bison, instead of the native yacc that's in FreeBSD? I don't think anyone is going to make changes to support this. > > Bison doesn't like the option after the argument given to the -d > option. In fact, bison built foo.tab.[ch], ignoring the rest. > The build procedure then tried to build foo.o ===>> end of the build > process. So I modified all the rules where .y.c is applied. > Fortunately there are only 3 occurences. > > The next run (making the world) outlived the first attempt by a factor > of 6 or 7, but ended when a .info file had to be produced. > The command line looked very similar to the one mentioned above: > makeinfo -d /some/directory/file.texi [ some more options ] -o foo.info > > Here makeinfo broke hopelessly !! So I modified share/mk/bsd.info.mk. > So far, I have fixed some build issues. > IMHO both bison and makeinfo do not behave the way they are designed. > I am aware that the patches I include in this mail should not be > necessary. > > But then, didn't anybody build the world recently ? Do I have to assume > I am the only one ? Everybody else is building current (3.0) all the time ? > > Who knows, maybe these patches are not the only ones to be applied > to successfully 'make world'. > > And yes, another thing. I am a subscriber of both Release and Snapshots CDs. > One thing I miss is the mentioning which source patch number the release > corresponds to actually. > Just for making this clear: FreeBSD 2.2-RELEASE is equivalent to the > sources up and until src-2.2.0209, 2.2.1 up to src-2.2.0216, 2.2.2 up to > src-2.2.0286. I'd like to know that, before I have to find it out myself > and learning from it when it is rather late. > Why the hell do I ask for this thing ? > The reason is I usually install the sources from the CD. And to keep up with > the rest of You guys, I apply the necessary patches every day. > But I need to know where to start from each release. So far I had to operate > with trial and error (not fun at all). > > So, enough talking, here are the patches: > > > --- contrib/gcc/Makefile.in.orig Thu Sep 25 19:54:12 1997 > +++ contrib/gcc/Makefile.in Fri Sep 26 10:11:57 1997 > @@ -1063 +1063 @@ > - cd $(srcdir); $(BISON) $(BISONFLAGS) -d c-parse.y -o c-parse.c > + cd $(srcdir); $(BISON) -o c-parse.c $(BISONFLAGS) -d c-parse.y > @@ -1125 +1125 @@ > - cd $(srcdir); $(BISON) $(BISONFLAGS) objc-parse.y -o objc-parse.c > + cd $(srcdir); $(BISON) -o objc-parse.c $(BISONFLAGS) objc-parse.y > @@ -1561 +1561 @@ > - cd $(srcdir); $(BISON) $(BISONFLAGS) -d bi-parser.y -o bi-parser.c > + cd $(srcdir); $(BISON) -o bi-parser.c $(BISONFLAGS) -d bi-parser.y > --- gnu/usr.bin/cc/cc1plus/Makefile.orig Thu Sep 25 19:59:10 1997 > +++ gnu/usr.bin/cc/cc1plus/Makefile Fri Sep 26 09:55:45 1997 > @@ -21 +21 @@ > - ${BISON} -d ${GCCDIR}/cp/parse.y -o parse.c > + ${BISON} -o parse.c -d ${GCCDIR}/cp/parse.y > --- gnu/usr.bin/cc/cc_tools/Makefile.orig Thu Sep 25 19:59:15 1997 > +++ gnu/usr.bin/cc/cc_tools/Makefile Fri Sep 26 09:30:23 1997 > @@ -30 +30 @@ > - ${BISON} ${BISONFLAGS} -d ${.ALLSRC} -o ${.TARGET} > + ${BISON} ${BISONFLAGS} -o ${.TARGET} -d ${.ALLSRC} > @@ -89 +89 @@ > - ${BISON} -d c-parse.y -o c-parse.c > + ${BISON} -o c-parse.c -d c-parse.y > @@ -101 +101 @@ > - ${BISON} -d objc-parse.y -o objc-parse.c > + ${BISON} -o objc-parse.c -d objc-parse.y > --- gnu/usr.bin/cc/cpp/Makefile.orig Thu Sep 25 19:59:15 1997 > +++ gnu/usr.bin/cc/cpp/Makefile Fri Sep 26 09:54:40 1997 > @@ -13 +13 @@ > - ${BISON} -d ${GCCDIR}/cexp.y -o cexp.c > + ${BISON} -o cexp.c -d ${GCCDIR}/cexp.y > --- share/mk/bsd.info.mk.orig Thu Sep 25 20:03:17 1997 > +++ share/mk/bsd.info.mk Fri Sep 26 17:55:53 1997 > @@ -92,2 +92,2 @@ > - ${MAKEINFO} ${MAKEINFOFLAGS} -I ${.CURDIR} -I ${SRCDIR} ${.IMPSRC} \ > - -o ${.TARGET}.new > + ${MAKEINFO} -o ${.TARGET}.new ${MAKEINFOFLAGS} \ > + -I ${.CURDIR} -I ${SRCDIR} ${.IMPSRC} > @@ -97,2 +97,2 @@ > - ${MAKEINFO} ${MAKEINFOFLAGS} -I ${.CURDIR} -I ${SRCDIR} ${.IMPSRC} \ > - -o ${.TARGET}.new > + ${MAKEINFO} -o ${.TARGET}.new ${MAKEINFOFLAGS} \ > + -I ${.CURDIR} -I ${SRCDIR} ${.IMPSRC} > > > -- > Carlo Dapor > > ----------------------------+----------------------------------------------- Chuck Robey | Interests include any kind of voice or data chuckr@eng.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 Sep 28 21:09:54 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id VAA14140 for current-outgoing; Sun, 28 Sep 1997 21:09:54 -0700 (PDT) Received: from mantar.slip.netcom.com (mantar.slip.netcom.com [192.187.167.134]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id VAA14128 for ; Sun, 28 Sep 1997 21:09:49 -0700 (PDT) Received: from localhost (root@localhost) by mantar.slip.netcom.com (8.8.7/8.8.7) with SMTP id VAA01550 for ; Sun, 28 Sep 1997 21:09:46 -0700 (PDT) Date: Sun, 28 Sep 1997 21:09:46 -0700 (PDT) From: Manfred Antar To: current@freebsd.org Subject: kernel compile faliure 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 Trying to build a kernel on a system running current I get : loading kernel exception.o: Undefined symbol `_cil' referenced from text segment exception.o: Undefined symbol `_inside_intr' referenced from text segment *** Error code 1 Anybody have any ideas. Thanks Manfred ============================== || mantar@netcom.com || || Ph. (415) 647-4843 || ============================== From owner-freebsd-current Sun Sep 28 22:18:39 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id WAA17273 for current-outgoing; Sun, 28 Sep 1997 22:18:39 -0700 (PDT) Received: from sendero-ppp.i-connect.net (sendero-ppp.i-Connect.Net [206.190.143.100]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id WAA17267 for ; Sun, 28 Sep 1997 22:18:35 -0700 (PDT) Received: (qmail 13810 invoked by uid 1000); 29 Sep 1997 05:18:59 -0000 Message-ID: X-Mailer: XFMail 1.2-alpha-092597 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: Date: Sun, 28 Sep 1997 22:18:59 -0700 (PDT) Organization: Atlas Telecom From: Simon Shapiro To: Manfred Antar Subject: RE: kernel compile faliure Cc: current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Hi Manfred Antar; On 29-Sep-97 you wrote: > Trying to build a kernel on a system running current > I get : > loading kernel > exception.o: Undefined symbol `_cil' referenced from text segment > exception.o: Undefined symbol `_inside_intr' referenced from text > segment > *** Error code 1 > Anybody have any ideas. Something to do with an SMP problem. check earlier postings, maybe on the smp mailing list. --- Sincerely Yours, Simon Shapiro Atlas Telecom Senior Architect 14355 SW Allen Blvd., Suite 130 Beaverton OR 97005 Shimon@i-Connect.Net Voice: 503.799.2313 From owner-freebsd-current Sun Sep 28 22:39:11 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id WAA18328 for current-outgoing; Sun, 28 Sep 1997 22:39:11 -0700 (PDT) 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 WAA18322 for ; Sun, 28 Sep 1997 22:39:08 -0700 (PDT) Received: from Ilsa.StevesCafe.com (localhost [127.0.0.1]) by Ilsa.StevesCafe.com (8.8.7/8.8.5) with ESMTP id XAA08882; Sun, 28 Sep 1997 23:38:44 -0600 (MDT) Message-Id: <199709290538.XAA08882@Ilsa.StevesCafe.com> X-Mailer: exmh version 2.0gamma 1/27/96 From: Steve Passe To: Manfred Antar cc: current@FreeBSD.ORG Subject: Re: kernel compile faliure In-reply-to: Your message of "Sun, 28 Sep 1997 21:09:46 PDT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 28 Sep 1997 23:38:44 -0600 Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Hi, > Trying to build a kernel on a system running current > I get : > loading kernel > exception.o: Undefined symbol `_cil' referenced from text segment > exception.o: Undefined symbol `_inside_intr' referenced from text segment > *** Error code 1 This was my fault, these are both SMP specific variables. I believe its fixed by grabbing a new ipl.s. Pass me the hat, please... Here's a patch till it propigates to the mirrors: =================================================================== RCS file: /home/ncvs/src/sys/i386/isa/ipl.s,v retrieving revision 1.16 diff -c -r1.16 ipl.s *** ipl.s 1997/09/29 00:04:33 1.16 --- ipl.s 1997/09/29 05:27:13 *************** *** 36,42 **** * * @(#)ipl.s * ! * $Id: ipl.s,v 1.16 1997/09/29 00:04:33 fsmp Exp $ */ --- 36,42 ---- * * @(#)ipl.s * ! * $Id: ipl.s,v 1.15 1997/09/28 19:34:46 fsmp Exp $ */ *************** *** 89,99 **** --- 89,112 ---- .text + #ifdef SMP + #define TEST_CIL \ + cmpl $0x0100, _cil ; \ + jne 1f ; \ + cmpl $0, _inside_intr ; \ + jne 1f ; \ + int $3 ; \ + 1: + #endif + /* * Handle return from interrupts, traps and syscalls. */ SUPERALIGN_TEXT _doreti: + #ifdef SMP + TEST_CIL + #endif FAKE_MCOUNT(_bintr) /* init "from" _bintr -> _doreti */ addl $4,%esp /* discard unit number */ popl %eax /* cpl or cml to restore */ *************** *** 108,113 **** --- 121,127 ---- * handlers is limited by the number of bits in cpl). */ #ifdef SMP + TEST_CIL cli /* early to prevent INT deadlock */ movl %eax, %edx /* preserve cpl while getting lock */ ICPL_LOCK *************** *** 125,130 **** --- 139,147 ---- andl _ipending,%ecx /* set bit = unmasked pending INT */ jne doreti_unpend doreti_exit: + #ifdef SMP + TEST_CIL + #endif #ifdef CPL_AND_CML movl %eax, _cml #else *************** *** 203,216 **** * for them again. */ #ifdef SMP /* we enter with cpl locked */ bsfl %ecx, %ecx /* slow, but not worth optimizing */ btrl %ecx, _ipending jnc doreti_next2 /* some intr cleared memory copy */ cmpl $NHWI, %ecx ! jae no_cil btsl %ecx, _cil ! no_cil: FAST_ICPL_UNLOCK /* preserves %eax */ sti /* late to prevent INT deadlock */ #else --- 220,234 ---- * for them again. */ #ifdef SMP + TEST_CIL /* we enter with cpl locked */ bsfl %ecx, %ecx /* slow, but not worth optimizing */ btrl %ecx, _ipending jnc doreti_next2 /* some intr cleared memory copy */ cmpl $NHWI, %ecx ! jae 1f btsl %ecx, _cil ! 1: FAST_ICPL_UNLOCK /* preserves %eax */ sti /* late to prevent INT deadlock */ #else *************** *** 231,240 **** /* XXX SMP this would leave cil set: */ je doreti_next /* "can't happen" */ #else ! jne ih_ok int $3 /* _breakpoint */ jmp doreti_next /* "can't happen" */ ! ih_ok: #endif cmpl $NHWI,%ecx jae doreti_swi --- 249,258 ---- /* XXX SMP this would leave cil set: */ je doreti_next /* "can't happen" */ #else ! jne 1f int $3 /* _breakpoint */ jmp doreti_next /* "can't happen" */ ! 1: #endif cmpl $NHWI,%ecx jae doreti_swi *************** *** 256,268 **** ALIGN_TEXT doreti_swi: ! #if 1 ! cmpl $0x0100, _cil ! jne 1f ! cmpl $0, _inside_intr ! jne 1f ! int $3 ! 1: #endif pushl %eax /* --- 274,281 ---- ALIGN_TEXT doreti_swi: ! #ifdef SMP ! TEST_CIL #endif pushl %eax /* -- Steve Passe | powered by smp@csn.net | Symmetric MultiProcessor FreeBSD From owner-freebsd-current Sun Sep 28 22:42:16 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id WAA18571 for current-outgoing; Sun, 28 Sep 1997 22:42:16 -0700 (PDT) Received: from usr08.primenet.com (tlambert@usr08.primenet.com [206.165.6.208]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id WAA18561 for ; Sun, 28 Sep 1997 22:42:13 -0700 (PDT) Received: (from tlambert@localhost) by usr08.primenet.com (8.8.5/8.8.5) id WAA16510; Sun, 28 Sep 1997 22:42:01 -0700 (MST) From: Terry Lambert Message-Id: <199709290542.WAA16510@usr08.primenet.com> Subject: Re: Suggestions on some make rules as far as the -o option is concerned To: chuckr@glue.umd.edu (Chuck Robey) Date: Mon, 29 Sep 1997 05:42:00 +0000 (GMT) Cc: dapor@nessie.inf.ethz.ch, freebsd-current@FreeBSD.ORG In-Reply-To: from "Chuck Robey" at Sep 28, 97 11:37:07 pm X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > In attempt to make world the success was always broken when some > > file had to be build by bison. > > The command line looked like > > bison -d /some/directory/where/the/dot-y-files-lies/file.y -o foo.c > > Excuse me, why are you using bison, instead of the native yacc that's in > FreeBSD? I don't think anyone is going to make changes to support this. Because the new gcc has some makefile and .y file changes that make it un-yacc'able. If I were paranoid, I'd accuse them of wanting to force installation of BISON on more machines... 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 Sep 28 22:55:49 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id WAA19263 for current-outgoing; Sun, 28 Sep 1997 22:55:49 -0700 (PDT) Received: from gratis.grondar.za (gratis.grondar.za [196.7.18.133]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id WAA19258 for ; Sun, 28 Sep 1997 22:55:44 -0700 (PDT) Received: from greenpeace.grondar.za (4zGuBhCT3H/lOJclzEGdKfaEmVQS4Cuy@greenpeace.grondar.za [196.7.18.132]) by gratis.grondar.za (8.8.7/8.8.7) with ESMTP id HAA16906; Mon, 29 Sep 1997 07:56:07 +0200 (SAT) Received: from greenpeace.grondar.za (tNakZRl7Yz8a6KtGkLGBNufUkMN1A8f6@localhost [127.0.0.1]) by greenpeace.grondar.za (8.8.7/8.8.7) with ESMTP id HAA04287; Mon, 29 Sep 1997 07:56:43 +0200 (SAT) Message-Id: <199709290556.HAA04287@greenpeace.grondar.za> X-Mailer: exmh version 2.0zeta 7/24/97 To: Simon Shapiro cc: Mark Murray , current@FreeBSD.ORG Subject: Re: HEAR YE! HEAR YE! New Kerberos! Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 29 Sep 1997 07:56:42 +0200 From: Mark Murray Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Simon Shapiro wrote: > make buildworld produces: > > install -C -o bin -g bin -m 444 /usr/src/3.0/src/secure/lib/libdes/des.h > /usr/obj/usr/src/3.0/src/tmp/usr/include > cd /usr/src/3.0/src/kerberosIV/lib/libacl && > /usr/obj/usr/src/3.0/src/tmp/usr/bin/make beforeinstall > make: don't know how to make > /usr/src/3.0/src/kerberosIV/lib/libacl/../../../crypto/kerberosIV/lib/acl/ac > l.h. Stop Does the file exist? Does the directory crypto/... exist? > By the way, the problem with make shooting itself in the foot early in the > build is still there. Details please. M -- Mark Murray Join the anti-SPAM movement: http://www.cauce.org From owner-freebsd-current Sun Sep 28 23:08:39 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id XAA20017 for current-outgoing; Sun, 28 Sep 1997 23:08:39 -0700 (PDT) Received: from sendero-ppp.i-connect.net (sendero-ppp.i-Connect.Net [206.190.143.100]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id XAA20012 for ; Sun, 28 Sep 1997 23:08:35 -0700 (PDT) Received: (qmail 3596 invoked by uid 1000); 29 Sep 1997 06:08:59 -0000 Message-ID: X-Mailer: XFMail 1.2-alpha-092597 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <199709290556.HAA04287@greenpeace.grondar.za> Date: Sun, 28 Sep 1997 23:08:59 -0700 (PDT) Organization: Atlas Telecom From: Simon Shapiro To: Mark Murray Subject: Re: HEAR YE! HEAR YE! New Kerberos! Cc: current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Hi Mark Murray; On 29-Sep-97 you wrote: > Simon Shapiro wrote: > > make buildworld produces: > > > > install -C -o bin -g bin -m 444 > > /usr/src/3.0/src/secure/lib/libdes/des.h > > /usr/obj/usr/src/3.0/src/tmp/usr/include > > cd /usr/src/3.0/src/kerberosIV/lib/libacl && > > /usr/obj/usr/src/3.0/src/tmp/usr/bin/make beforeinstall > > make: don't know how to make > > /usr/src/3.0/src/kerberosIV/lib/libacl/../../../crypto/kerberosIV/lib/ac > > l/ac > > l.h. Stop > > Does the file exist? Does the directory crypto/... exist? My apologies. I did not realize I simply do not have the crypto directory on my system. I dounloaded it from your ftp server. Thanx! Now a question: How do I stay current with it? It does not seem to be present on cvsup.freebsd.org. > > By the way, the problem with make shooting itself in the foot early in > > the > > build is still there. > > Details please. Lately, if you do a make world (make buildworld) and there is a build already present in /usr/obj, make, when trying to build itself, early in the process, deletes some files fomr itself and fails to find them. A (``untested'') patch was posted during the weekend, which cures this problem, but has the amusing side-efect of only building make. It exists successfully after make is done. --- Sincerely Yours, Simon Shapiro Atlas Telecom Senior Architect 14355 SW Allen Blvd., Suite 130 Beaverton OR 97005 Shimon@i-Connect.Net Voice: 503.799.2313 From owner-freebsd-current Sun Sep 28 23:17:54 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id XAA20590 for current-outgoing; Sun, 28 Sep 1997 23:17:54 -0700 (PDT) Received: from gratis.grondar.za (gratis.grondar.za [196.7.18.133]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id XAA20582 for ; Sun, 28 Sep 1997 23:17:51 -0700 (PDT) Received: from greenpeace.grondar.za (5FDLzasXNjkn21NP0kuoyF2tMv5YzOvq@greenpeace.grondar.za [196.7.18.132]) by gratis.grondar.za (8.8.7/8.8.7) with ESMTP id IAA16971; Mon, 29 Sep 1997 08:18:15 +0200 (SAT) Received: from greenpeace.grondar.za (9ExpSYlHWFpYHbxsnM89cQ2DxEf173Hs@localhost [127.0.0.1]) by greenpeace.grondar.za (8.8.7/8.8.7) with ESMTP id IAA16677; Mon, 29 Sep 1997 08:18:52 +0200 (SAT) Message-Id: <199709290618.IAA16677@greenpeace.grondar.za> X-Mailer: exmh version 2.0zeta 7/24/97 To: Simon Shapiro cc: Mark Murray , current@FreeBSD.ORG Subject: Re: HEAR YE! HEAR YE! New Kerberos! Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 29 Sep 1997 08:18:47 +0200 From: Mark Murray Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Simon Shapiro wrote: > Now a question: How do I stay current with it? It does not seem to be > present on cvsup.freebsd.org. Please look at the various options in share/examples/cvsup etc. There are some sample supfiles and configs for cvsup, ctm and so on. If you are not in the USA, you should get your stuff from cvsup.internat.freebsd.org, ftp.internat.freebsd.org. If you are in USA, any cvsup server or ftp mirror should be able to help. > Lately, if you do a make world (make buildworld) and there is a build > already present in /usr/obj, make, when trying to build itself, early in > the process, deletes some files fomr itself and fails to find them. Oh, that. Luckily, not my problem :-) M -- Mark Murray Join the anti-SPAM movement: http://www.cauce.org From owner-freebsd-current Sun Sep 28 23:19:04 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id XAA20674 for current-outgoing; Sun, 28 Sep 1997 23:19:04 -0700 (PDT) Received: from mexico.brainstorm.eu.org (root@mexico.brainstorm.fr [193.56.58.253]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id XAA20668 for ; Sun, 28 Sep 1997 23:18:56 -0700 (PDT) Received: from brasil.brainstorm.eu.org (brasil.brainstorm.fr [193.56.58.33]) by mexico.brainstorm.eu.org (8.8.4/8.8.4) with ESMTP id IAA27195 for ; Mon, 29 Sep 1997 08:19:03 +0200 Received: (from uucp@localhost) by brasil.brainstorm.eu.org (8.8.6/brasil-1.2) with UUCP id IAA22693 for current@FreeBSD.ORG; Mon, 29 Sep 1997 08:18:31 +0200 Received: (from roberto@localhost) by keltia.freenix.fr (8.8.7/keltia-2.10/nospam) id IAA23183; Mon, 29 Sep 1997 08:13:28 +0200 (CEST) Message-ID: <19970929081328.27479@keltia.freenix.fr> Date: Mon, 29 Sep 1997 08:13:28 +0200 From: Ollivier Robert To: current@FreeBSD.ORG Subject: Re: Staying -current with FreeBSD References: <199709281709.CAA06890@word.smith.net.au> <19970928141718.10371@hydrogen.nike.efn.org> <19970929085618.64898@lemis.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.84 In-Reply-To: <19970929085618.64898@lemis.com>; from Greg Lehey on Mon, Sep 29, 1997 at 08:56:18AM +0930 X-Operating-System: FreeBSD 3.0-CURRENT Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk According to Greg Lehey: > # du -s /usr/src/ > 383294 /usr/src/ > > Am I missing something? My current figures are: Filesystem 1K-blocks Used Avail Capacity Mounted on /dev/sd0s2h 698831 227042 415883 35% /src /usr/{src,ports} /dev/sd12h 464045 394793 32129 92% /spare CVS repos. The entire CVS repository is a bit more than 390 MB and /usr/src is: 257 [8:11] roberto@keltia:/usr/src> du -s . 170530 . /usr/ports is a few dozen megabytes with no distfiles extracted. -- Ollivier ROBERT -=- FreeBSD: There are no limits -=- roberto@keltia.freenix.fr FreeBSD keltia.freenix.fr 3.0-CURRENT #35: Sun Sep 21 19:28:07 CEST 1997 From owner-freebsd-current Sun Sep 28 23:22:17 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id XAA20983 for current-outgoing; Sun, 28 Sep 1997 23:22:17 -0700 (PDT) Received: from mail.san.rr.com (mail-atm.san.rr.com [204.210.0.1]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id XAA20975 for ; Sun, 28 Sep 1997 23:22:14 -0700 (PDT) Received: from dt5h1n61.san.rr.com (dt5h1n61.san.rr.com [204.210.31.97]) by mail.san.rr.com (8.8.7/8.8.7) with SMTP id XAA10818; Sun, 28 Sep 1997 23:20:58 -0700 (PDT) Message-Id: <199709290620.XAA10818@mail.san.rr.com> From: "Studded" To: "Greg Lehey" Cc: "current@FreeBSD.ORG" Date: Sun, 28 Sep 97 23:20:56 -0700 Reply-To: "Studded" Priority: Normal X-Mailer: PMMail 1.92 For OS/2 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Subject: Re: Staying -current with FreeBSD Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Mon, 29 Sep 1997 10:21:09 +0930, Greg Lehey wrote: >Unfortunately, I've just discovered my mistake: I had the ports tree >inside /usr/src, so it's been counted twice. Take 160 MB off that >figure... Ok, so how about a semi-definitive answer to that age-old question. I want to know how much hard disk space I should allocate for a fairly complete freebsd system. I'm talking binaries, CVS source tree, and room to make the world. I'll add swap space and room for my files as needed. Assume a fairly luxurious system with some games, ports, etc. Disk space is fairly cheap right now, but it's always good to plan ahead. Any takers? :) Thanks, Doug Do thou amend thy face, and I'll amend my life. -Shakespeare, "Henry V" From owner-freebsd-current Sun Sep 28 23:50:47 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id XAA22486 for current-outgoing; Sun, 28 Sep 1997 23:50:47 -0700 (PDT) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id XAA22464 for ; Sun, 28 Sep 1997 23:50:40 -0700 (PDT) Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id IAA13223; Mon, 29 Sep 1997 08:50:39 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.8.7/8.8.5) id IAA03546; Mon, 29 Sep 1997 08:41:00 +0200 (MET DST) Message-ID: <19970929084059.CN40115@uriah.heep.sax.de> Date: Mon, 29 Sep 1997 08:40:59 +0200 From: j@uriah.heep.sax.de (J Wunsch) To: current@FreeBSD.ORG Cc: Shimon@i-Connect.Net (Simon Shapiro) Subject: Re: HEAR YE! HEAR YE! New Kerberos! References: <199709281014.MAA01564@greenpeace.grondar.za> X-Mailer: Mutt 0.60_p2-3,5,8-9 Mime-Version: 1.0 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 Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: ; from Simon Shapiro on Sep 28, 1997 15:27:26 -0700 Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk As Simon Shapiro wrote: > install -C -o bin -g bin -m 444 /usr/src/3.0/src/secure/lib/libdes/des.h > /usr/obj/usr/src/3.0/src/tmp/usr/include > cd /usr/src/3.0/src/kerberosIV/lib/libacl && > /usr/obj/usr/src/3.0/src/tmp/usr/bin/make beforeinstall > make: don't know how to make > /usr/src/3.0/src/kerberosIV/lib/libacl/../../../crypto/kerberosIV/lib/acl/ac > l.h. Stop > *** Error code 2 Old .depend 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 Sun Sep 28 23:50:53 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id XAA22513 for current-outgoing; Sun, 28 Sep 1997 23:50:53 -0700 (PDT) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id XAA22487 for ; Sun, 28 Sep 1997 23:50:47 -0700 (PDT) Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id IAA13226 for current@FreeBSD.ORG; Mon, 29 Sep 1997 08:50:46 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.8.7/8.8.5) id IAA03597; Mon, 29 Sep 1997 08:48:53 +0200 (MET DST) Message-ID: <19970929084853.BL18523@uriah.heep.sax.de> Date: Mon, 29 Sep 1997 08:48:53 +0200 From: j@uriah.heep.sax.de (J Wunsch) To: current@FreeBSD.ORG Subject: Re: Come on guys... References: <18132.875437285@critter.freebsd.dk> X-Mailer: Mutt 0.60_p2-3,5,8-9 Mime-Version: 1.0 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 Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <18132.875437285@critter.freebsd.dk>; from Poul-Henning Kamp on Sep 28, 1997 11:01:25 +0200 Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk As Poul-Henning Kamp wrote: > 4. Recompile, from scratch, your kernel with DDB in it. (For extra > points: use "config -g" and do not strip your kernel before booting) Warning: do not do this unless you've got at least 16 MB (preferrably 32 MB) of RAM. Doing this on an 8 MB machine won't get you very far at all, probably not even into the main() of the kernel. In these cases, you can however install a strip -d'ed kernel, but keep the -g kernel around to analyze a kernel core dump with gdb -k. See also: the section about kernel debugging in the handbook (file:/usr/share/doc/handbook/kerneldebug.html or http://www.freebsd.org/handbook/kerneldebug.html -- hope i've got this right.) -- 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 Sep 29 00:17:04 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id AAA23890 for current-outgoing; Mon, 29 Sep 1997 00:17:04 -0700 (PDT) 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 AAA23883 for ; Mon, 29 Sep 1997 00:16:57 -0700 (PDT) Received: (from grog@localhost) by freebie.lemis.com (8.8.7/8.8.5) id QAA14015; Mon, 29 Sep 1997 16:46:43 +0930 (CST) Message-ID: <19970929164643.40234@lemis.com> Date: Mon, 29 Sep 1997 16:46:43 +0930 From: Greg Lehey To: Studded Cc: "current@FreeBSD.ORG" Subject: Re: Staying -current with FreeBSD References: <199709290620.XAA10818@mail.san.rr.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.84e In-Reply-To: <199709290620.XAA10818@mail.san.rr.com>; from Studded on Sun, Sep 28, 1997 at 11:20:56PM -0700 Organisation: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8250 Fax: +61-8-8388-8250 Mobile: +61-41-739-7062 WWW-Home-Page: http://www.lemis.com/~grog Fight-Spam-Now: http://www.cauce.org Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Sun, Sep 28, 1997 at 11:20:56PM -0700, Studded wrote: > On Mon, 29 Sep 1997 10:21:09 +0930, Greg Lehey wrote: > >> Unfortunately, I've just discovered my mistake: I had the ports tree >> inside /usr/src, so it's been counted twice. Take 160 MB off that >> figure... > > Ok, so how about a semi-definitive answer to that age-old > question. I want to know how much hard disk space I should allocate > for a fairly complete freebsd system. I'm talking binaries, CVS source > tree, and room to make the world. I'll add swap space and room for my > files as needed. Assume a fairly luxurious system with some games, > ports, etc. Disk space is fairly cheap right now, but it's always good > to plan ahead. Any takers? :) Well, I've removed my duplicate ports tree and run du through them again. Here are the revised values: Table 16-1. Approximate source tree sizes +-------------------------+-----------+ |Component | Size (MB) | +-------------------------+-----------+ |Repository src/sys | 53 | |Repository src | 330 | |Repository ports | 36 | |Source tree /usr/src/sys | 65 | |Source tree /usr/src | 225 | |Source tree /usr/ports | 200 | |Object tree src | 160 | +-------------------------+-----------+ Compared to the previous, /usr/src has gone down from 372 to 225 (as a result of the ports being moved out), and ports have gone up from 160 to 200. In fact, I measured 224 MB for ports, but as I observe, you could fill up several gigabytes of disk with ports if you wanted to. 200 MB is comfortable if you do a make clean from time to time. Greg From owner-freebsd-current Mon Sep 29 01:00:45 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id BAA26051 for current-outgoing; Mon, 29 Sep 1997 01:00:45 -0700 (PDT) Received: from sendero-ppp.i-connect.net (sendero-ppp.i-Connect.Net [206.190.143.100]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id BAA26045 for ; Mon, 29 Sep 1997 01:00:39 -0700 (PDT) Received: (qmail 8745 invoked by uid 1000); 29 Sep 1997 08:01:04 -0000 Message-ID: X-Mailer: XFMail 1.2-alpha-092597 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <19970929084059.CN40115@uriah.heep.sax.de> Date: Mon, 29 Sep 1997 01:01:04 -0700 (PDT) Organization: Atlas Telecom From: Simon Shapiro To: (Joerg Wunsch) Subject: Re: HEAR YE! HEAR YE! New Kerberos! Cc: current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Hi J Wunsch; On 29-Sep-97 you wrote: > As Simon Shapiro wrote: > > > install -C -o bin -g bin -m 444 > > /usr/src/3.0/src/secure/lib/libdes/des.h > > /usr/obj/usr/src/3.0/src/tmp/usr/include > > cd /usr/src/3.0/src/kerberosIV/lib/libacl && > > /usr/obj/usr/src/3.0/src/tmp/usr/bin/make beforeinstall > > make: don't know how to make > > /usr/src/3.0/src/kerberosIV/lib/libacl/../../../crypto/kerberosIV/lib/ac > > l/ac > > l.h. Stop > > *** Error code 2 > > Old .depend file? Maybe. It started doing that about a week ago. You saw the exchange on that. Right? --- Sincerely Yours, Simon Shapiro Atlas Telecom Senior Architect 14355 SW Allen Blvd., Suite 130 Beaverton OR 97005 Shimon@i-Connect.Net Voice: 503.799.2313 From owner-freebsd-current Mon Sep 29 01:24:54 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id BAA26978 for current-outgoing; Mon, 29 Sep 1997 01:24:54 -0700 (PDT) Received: from sendero-ppp.i-connect.net (sendero-ppp.i-Connect.Net [206.190.143.100]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id BAA26973 for ; Mon, 29 Sep 1997 01:24:48 -0700 (PDT) Received: (qmail 21573 invoked by uid 1000); 29 Sep 1997 08:25:13 -0000 Message-ID: X-Mailer: XFMail 1.2-alpha-092597 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <199709290618.IAA16677@greenpeace.grondar.za> Date: Mon, 29 Sep 1997 01:25:13 -0700 (PDT) Organization: Atlas Telecom From: Simon Shapiro To: Mark Murray Subject: Re: HEAR YE! HEAR YE! New Kerberos! Cc: current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Hi Mark Murray; On 29-Sep-97 you wrote: > Simon Shapiro wrote: > > Now a question: How do I stay current with it? It does not seem to be > > present on cvsup.freebsd.org. > > Please look at the various options in share/examples/cvsup etc. There > are some sample supfiles and configs for cvsup, ctm and so on. If you > are not in the USA, you should get your stuff from > cvsup.internat.freebsd.org, ftp.internat.freebsd.org. If you are in > USA, any cvsup server or ftp mirror should be able to help. Thanx, but this is not what I meant to ask. For cvsup, what is the sup collection label? I already am getting src-all and src-eBones. Your new stuff is in src/crypt, and there is no such collection. So, if you were to cvsup Kerberos4 from FreeBSD, what sup entry would you use? Thanx for your help. --- Sincerely Yours, Simon Shapiro Atlas Telecom Senior Architect 14355 SW Allen Blvd., Suite 130 Beaverton OR 97005 Shimon@i-Connect.Net Voice: 503.799.2313 From owner-freebsd-current Mon Sep 29 01:38:34 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id BAA27734 for current-outgoing; Mon, 29 Sep 1997 01:38:34 -0700 (PDT) Received: from gratis.grondar.za (gratis.grondar.za [196.7.18.133]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id BAA27726 for ; Mon, 29 Sep 1997 01:38:29 -0700 (PDT) Received: from greenpeace.grondar.za (9UhPYLRIewb0ioBwc4Kc6+ii8+FaSi89@greenpeace.grondar.za [196.7.18.132]) by gratis.grondar.za (8.8.7/8.8.7) with ESMTP id KAA17229; Mon, 29 Sep 1997 10:38:53 +0200 (SAT) Received: from greenpeace.grondar.za (avpvRo7IF2P7UMhuGQ8yo3VMszk4MUso@localhost [127.0.0.1]) by greenpeace.grondar.za (8.8.7/8.8.7) with ESMTP id KAA11601; Mon, 29 Sep 1997 10:38:27 +0200 (SAT) Message-Id: <199709290838.KAA11601@greenpeace.grondar.za> To: Simon Shapiro cc: current@FreeBSD.ORG Subject: Re: HEAR YE! HEAR YE! New Kerberos! Date: Mon, 29 Sep 1997 10:38:26 +0200 From: Mark Murray Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Simon Shapiro wrote: > Thanx, but this is not what I meant to ask. For cvsup, what is the sup > collection label? I already am getting src-all and src-eBones. Your new > stuff is in src/crypt, and there is no such collection. I dont know offhand. > So, if you were to cvsup Kerberos4 from FreeBSD, what sup entry would you > use? Please look in the files. The label is there. M -- Mark Murray Join the anti-SPAM movement: http://www.cauce.org From owner-freebsd-current Mon Sep 29 01:50:56 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id BAA28310 for current-outgoing; Mon, 29 Sep 1997 01:50:56 -0700 (PDT) Received: from sendero-ppp.i-connect.net (sendero-ppp.i-Connect.Net [206.190.143.100]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id BAA28304 for ; Mon, 29 Sep 1997 01:50:48 -0700 (PDT) Received: (qmail 21759 invoked by uid 1000); 29 Sep 1997 08:51:13 -0000 Message-ID: X-Mailer: XFMail 1.2-alpha-092597 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <199709290838.KAA11601@greenpeace.grondar.za> Date: Mon, 29 Sep 1997 01:51:13 -0700 (PDT) Organization: Atlas Telecom From: Simon Shapiro To: Mark Murray Subject: Re: HEAR YE! HEAR YE! New Kerberos! Cc: current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Hi Mark Murray; On 29-Sep-97 you wrote: > > So, if you were to cvsup Kerberos4 from FreeBSD, what sup entry would > > you > > use? > > Please look in the files. The label is there. To get src/crypt, use src-crypto. Works like a charm. RTFM, Simon! --- Sincerely Yours, Simon Shapiro Atlas Telecom Senior Architect 14355 SW Allen Blvd., Suite 130 Beaverton OR 97005 Shimon@i-Connect.Net Voice: 503.799.2313 From owner-freebsd-current Mon Sep 29 02:19:52 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id CAA29762 for current-outgoing; Mon, 29 Sep 1997 02:19:52 -0700 (PDT) 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 CAA29757 for ; Mon, 29 Sep 1997 02:19:50 -0700 (PDT) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.5/8.6.9) id TAA26024; Mon, 29 Sep 1997 19:12:40 +1000 Date: Mon, 29 Sep 1997 19:12:40 +1000 From: Bruce Evans Message-Id: <199709290912.TAA26024@godzilla.zeta.org.au> To: bde@zeta.org.au, Shimon@i-Connect.Net Subject: RE: Make world failure Cc: current@FreeBSD.ORG, randyd@nconnect.net Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >> Untested fix (for -current): >> >> diff -c2 Makefile~ Makefile >> *** Makefile~ Sat Sep 27 01:42:58 1997 >> --- Makefile Sat Sep 27 01:53:47 1997 > >The net effect of this fix is the fastest make buildworld ever experienced >:-) > >It build make allright. But this is all it did here. Made make and exited >quietly. Wiping /usr/obj out still works. I tested it a bit. It doesn't exit early even when ${MAKEOBJDIRPREFIX} exists here (DESTDIR=/c/z/root MAKEOBJDIRPREFIX=/c/z/obj). Bruce From owner-freebsd-current Mon Sep 29 03:16:22 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id DAA02450 for current-outgoing; Mon, 29 Sep 1997 03:16:22 -0700 (PDT) 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 DAA02440 for ; Mon, 29 Sep 1997 03:16:16 -0700 (PDT) Received: from panke.panke.de (anonymous214.ppp.cs.tu-berlin.de [130.149.17.214]) by mail.cs.tu-berlin.de (8.8.6/8.8.7) with ESMTP id MAA28713 for ; Mon, 29 Sep 1997 12:13:25 +0200 (MET DST) Received: (from wosch@localhost) by panke.panke.de (8.8.5/8.6.12) id MAA01857; Mon, 29 Sep 1997 12:11:14 +0200 (MET DST) Date: Mon, 29 Sep 1997 12:11:14 +0200 (MET DST) Message-Id: <199709291011.MAA01857@panke.panke.de> From: Wolfram Schneider To: current@freebsd.org Subject: silent cp -i MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk cp(1) is too silent if used with the option -i. It should print which input cp expect (y/n) and print a warning if the file was not overwritten. [current behavior] $ touch from to $ cp -i from to overwrite to? n [new] $ cp -i from to overwrite to? (y/n [n]) n not overwritten Index: utils.c =================================================================== RCS file: /usr/cvs/src/bin/cp/utils.c,v retrieving revision 1.13 diff -u -r1.13 utils.c --- utils.c 1997/02/22 14:01:34 1.13 +++ utils.c 1997/09/28 10:38:32 @@ -81,13 +81,16 @@ * modified by the umask.) */ if (!dne) { +#define YESNO "(y/n [n]) " if (iflag) { - (void)fprintf(stderr, "overwrite %s? ", to.p_path); + (void)fprintf(stderr, "overwrite %s? %s", + to.p_path, YESNO); checkch = ch = getchar(); while (ch != '\n' && ch != EOF) ch = getchar(); if (checkch != 'y' && checkch != 'Y') { (void)close(from_fd); + (void)printf("not overwritten\n"); return (0); } } -- Wolfram Schneider http://www.apfel.de/~wosch/ From owner-freebsd-current Mon Sep 29 04:41:02 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id EAA06004 for current-outgoing; Mon, 29 Sep 1997 04:41:02 -0700 (PDT) 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 EAA05991 for ; Mon, 29 Sep 1997 04:41:00 -0700 (PDT) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.5/8.6.9) id VAA31427; Mon, 29 Sep 1997 21:39:46 +1000 Date: Mon, 29 Sep 1997 21:39:46 +1000 From: Bruce Evans Message-Id: <199709291139.VAA31427@godzilla.zeta.org.au> To: current@freebsd.org, wosch@cs.tu-berlin.de Subject: Re: silent cp -i Sender: owner-freebsd-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >cp(1) is too silent if used with the option -i. It should >print which input cp expect (y/n) and print a warning if the >file was not overwritten. cp actually expects y/Y/other. POSIX.2 doesn't permit cp to print to stdout. stderr is permitted for diagnostics. Bruce From owner-freebsd-current Mon Sep 29 06:05:08 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id GAA08968 for current-outgoing; Mon, 29 Sep 1997 06:05:08 -0700 (PDT) Received: from al.imforei.apana.org.au (pjchilds@al.imforei.apana.org.au [202.12.89.41]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id GAA08954 for ; Mon, 29 Sep 1997 06:05:01 -0700 (PDT) Received: (from pjchilds@localhost) by al.imforei.apana.org.au (beBop) id WAA03763; Mon, 29 Sep 1997 22:34:46 +0930 (CST) Date: Mon, 29 Sep 1997 22:34:46 +0930 (CST) From: Peter Childs Message-Id: <199709291304.WAA03763@al.imforei.apana.org.au> To: "Studded" , freebsd-current@freebsd.org Subject: Re: Staying -current with FreeBSD Newsgroups: apana.lists.os.freebsd.current In-Reply-To: <199709290620.XAA10818@mail.san.rr.com> X-Newsreader: TIN [UNIX 1.3 unoff BETA 970731; i386 FreeBSD 2.2-STABLE] Sender: owner-freebsd-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk In article <199709290620.XAA10818@mail.san.rr.com> you wrote: > On Mon, 29 Sep 1997 10:21:09 +0930, Greg Lehey wrote: > Ok, so how about a semi-definitive answer to that age-old > question. I want to know how much hard disk space I should allocate > for a fairly complete freebsd system. I'm talking binaries, CVS source > tree, and room to make the world. I'll add swap space and room for my > files as needed. Assume a fairly luxurious system with some games, > ports, etc. Disk space is fairly cheap right now, but it's always good > to plan ahead. Any takers? :) a make world can chew up a bit, as well as the cvs tree, x, the ports, and the rest... i found last time i built a release i needed a bit over a gig scratch to do it in.. lets say 2Gb and you shouldn't have space problems.. not for a few weeks anyway :) peter (churning along with much less than 2Gb..) PS. make sure its scsi (just to add fuel to religious wars..) -- Peter Childs --- http://www.imforei.apana.org.au/~pjchilds Finger pjchilds@al.imforei.apana.org.au for public PGP key From owner-freebsd-current Mon Sep 29 06:26:41 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id GAA10050 for current-outgoing; Mon, 29 Sep 1997 06:26:41 -0700 (PDT) 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 GAA10045 for ; Mon, 29 Sep 1997 06:26:36 -0700 (PDT) Received: from panke.panke.de (anonymous220.ppp.cs.tu-berlin.de [130.149.17.220]) by mail.cs.tu-berlin.de (8.8.6/8.8.7) with ESMTP id PAA17132; Mon, 29 Sep 1997 15:18:13 +0200 (MET DST) Received: (from wosch@localhost) by panke.panke.de (8.8.5/8.6.12) id OAA11574; Mon, 29 Sep 1997 14:51:52 +0200 (MET DST) Message-ID: <19970929145151.50498@panke.de> Date: Mon, 29 Sep 1997 14:51:51 +0200 From: Wolfram Schneider To: Bruce Evans Cc: current@freebsd.org, wosch@cs.tu-berlin.de Subject: Re: silent cp -i References: <199709291139.VAA31427@godzilla.zeta.org.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.79 In-Reply-To: <199709291139.VAA31427@godzilla.zeta.org.au>; from Bruce Evans on Mon, Sep 29, 1997 at 09:39:46PM +1000 Sender: owner-freebsd-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Mon, Sep 29, 1997 at 09:39:46PM +1000, Bruce Evans wrote: > >cp(1) is too silent if used with the option -i. It should > >print which input cp expect (y/n) and print a warning if the > >file was not overwritten. > > cp actually expects y/Y/other. This is correct, but may confus new users (press [yY]*\n for yes or *\n for no). -- Wolfram Schneider http://www.apfel.de/~wosch/ From owner-freebsd-current Mon Sep 29 08:46:31 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id IAA17670 for current-outgoing; Mon, 29 Sep 1997 08:46:31 -0700 (PDT) Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id IAA17658 for ; Mon, 29 Sep 1997 08:46:25 -0700 (PDT) Received: from harmony [10.0.0.6] by rover.village.org with esmtp (Exim 1.71 #1) id 0xFi1Y-00066u-00; Mon, 29 Sep 1997 09:46:16 -0600 Received: from harmony.village.org (localhost [127.0.0.1]) by harmony.village.org (8.8.7/8.8.3) with ESMTP id JAA11719; Mon, 29 Sep 1997 09:46:47 -0600 (MDT) Message-Id: <199709291546.JAA11719@harmony.village.org> To: "Studded" Subject: Re: Staying -current with FreeBSD Cc: "Greg Lehey" , "current@FreeBSD.ORG" In-reply-to: Your message of "Sun, 28 Sep 1997 23:20:56 PDT." <199709290620.XAA10818@mail.san.rr.com> References: <199709290620.XAA10818@mail.san.rr.com> Date: Mon, 29 Sep 1997 09:46:47 -0600 From: Warner Losh Sender: owner-freebsd-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk In message <199709290620.XAA10818@mail.san.rr.com> "Studded" writes: : Ok, so how about a semi-definitive answer to that age-old : question. I want to know how much hard disk space I should allocate : for a fairly complete freebsd system. I'm talking binaries, CVS source : tree, and room to make the world. I'll add swap space and room for my : files as needed. Assume a fairly luxurious system with some games, : ports, etc. Disk space is fairly cheap right now, but it's always good : to plan ahead. Any takers? :) I found things really cramped when I had the 1.2G disk for stuff. I found things much less cramped on the 3.2G drive that I have now, but I also supplement that with a 1.0G JAZ drive for the CVS tree. With disk being as cheap as it is today, I'd get a couple of 2G-3G IDE drives. Warner From owner-freebsd-current Mon Sep 29 15:09:59 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id PAA13876 for current-outgoing; Mon, 29 Sep 1997 15:09:59 -0700 (PDT) Received: from rvc1.informatik.ba-stuttgart.de (isdn022.stuttgart.netsurf.de [194.195.220.213]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id PAA13871 for ; Mon, 29 Sep 1997 15:09:54 -0700 (PDT) Received: (from helbig@localhost) by rvc1.informatik.ba-stuttgart.de (8.8.7/8.8.5) id XAA05359; Mon, 29 Sep 1997 23:47:33 +0200 (MET DST) From: Wolfgang Helbig Message-Id: <199709292147.XAA05359@rvc1.informatik.ba-stuttgart.de> Subject: Re: Adding algorithms [Was: cvs commit: src/usr.bin/cksum crc32.c ...] In-Reply-To: <199709281357.JAA08605@khavrinen.lcs.mit.edu> from Garrett Wollman at "Sep 28, 97 09:57:42 am" To: wollman@khavrinen.lcs.mit.edu (Garrett Wollman) Date: Mon, 29 Sep 1997 23:47:32 +0200 (MET DST) Cc: helbig@Informatik.BA-Stuttgart.DE, current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL30 (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 [...] > > o Computes the Number of Week from a given date. > > According to DIN 1355 : The first week of year y is the first week > > that includes at least four days in year y. A week starts with > > Monday. I don't know about international standards so it might be > > useful for Germany only. > > ISO 8601. The strftime(3) function already provides this > functionality, although there is unfortunately no direct > iso8601weeknumber() function to give you the integer value directly. Unfortunately strftime(3)'s notion of week number only comes close to DIN 1355: According to ISO 9899: "%W" is replaced by the week number of the year (the first Monday as the first day of week 1) That's quite different from DIN 1355 and thus renders strftime's week numbers useless in Germany (and probably in other countries that adopted the ISO 8601 standard as well). BTW. the wording in ISO 9899 is a little less ambiguous and more consistent for "%W" and "%U". I guess I'll change the man page. Wolfgang From owner-freebsd-current Mon Sep 29 15:21:22 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id PAA14628 for current-outgoing; Mon, 29 Sep 1997 15:21:22 -0700 (PDT) Received: from nagual.pp.ru (ache@ache.relcom.ru [194.58.229.133]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id PAA14621 for ; Mon, 29 Sep 1997 15:21:13 -0700 (PDT) Received: (from ache@localhost) by nagual.pp.ru (8.8.7/8.8.7) id CAA00543; Tue, 30 Sep 1997 02:20:33 +0400 (MSD) Date: Tue, 30 Sep 1997 02:20:29 +0400 (MSD) From: =?KOI8-R?B?4c7E0sXKIP7F0s7P1w==?= To: John Polstra cc: FreeBSD-current Subject: Re: CVSup-15.2 is now available In-Reply-To: <199709282215.PAA20418@austin.polstra.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, 28 Sep 1997, John Polstra wrote: > Package: > ftp://ftp.FreeBSD.org/pub/FreeBSD/packages-current/net/cvsup-15.2.tgz Please somebody rebuild this package for -current, I see most of current packages are obsoleted, so it seems there is no chance to have cvsup-15.2 package for -current. -- Andrey A. Chernov http://www.nagual.pp.ru/~ache/ From owner-freebsd-current Mon Sep 29 15:45:57 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id PAA15833 for current-outgoing; Mon, 29 Sep 1997 15:45:57 -0700 (PDT) Received: from mail.san.rr.com (mail-atm.san.rr.com [204.210.0.1]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id PAA15828 for ; Mon, 29 Sep 1997 15:45:54 -0700 (PDT) Received: from dt5h1n61.san.rr.com (dt5h1n61.san.rr.com [204.210.31.97]) by mail.san.rr.com (8.8.7/8.8.7) with SMTP id PAA19326 for ; Mon, 29 Sep 1997 15:45:18 -0700 (PDT) Message-Id: <199709292245.PAA19326@mail.san.rr.com> From: "Studded" To: "current@freebsd.org" Date: Mon, 29 Sep 97 15:45:17 -0700 Reply-To: "Studded" Priority: Normal X-Mailer: PMMail 1.92 For OS/2 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Subject: Re: Staying -current with FreeBSD Sender: owner-freebsd-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Sun, 28 Sep 97 23:20:56 -0700, Studded wrote: > Ok, so how about a semi-definitive answer to that age-old >question. I want to know how much hard disk space I should allocate >for a fairly complete freebsd system. Thank you for all of the very helpful responses. :) Now I know what to put on my Christmas list. Doug Do thou amend thy face, and I'll amend my life. -Shakespeare, "Henry V" From owner-freebsd-current Mon Sep 29 16:29:05 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id QAA17883 for current-outgoing; Mon, 29 Sep 1997 16:29:05 -0700 (PDT) Received: from khavrinen.lcs.mit.edu (khavrinen.lcs.mit.edu [18.24.4.193]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id QAA17877 for ; Mon, 29 Sep 1997 16:29:03 -0700 (PDT) Received: (from wollman@localhost) by khavrinen.lcs.mit.edu (8.8.5/8.8.5) id TAA13519; Mon, 29 Sep 1997 19:28:32 -0400 (EDT) Date: Mon, 29 Sep 1997 19:28:32 -0400 (EDT) From: Garrett Wollman Message-Id: <199709292328.TAA13519@khavrinen.lcs.mit.edu> To: Wolfgang Helbig Cc: wollman@khavrinen.lcs.mit.edu (Garrett Wollman), current@FreeBSD.ORG Subject: Re: Adding algorithms [Was: cvs commit: src/usr.bin/cksum crc32.c ...] In-Reply-To: <199709292147.XAA05359@rvc1.informatik.ba-stuttgart.de> References: <199709281357.JAA08605@khavrinen.lcs.mit.edu> <199709292147.XAA05359@rvc1.informatik.ba-stuttgart.de> Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk < said: >> ISO 8601. The strftime(3) function already provides this >> functionality, although there is unfortunately no direct >> iso8601weeknumber() function to give you the integer value directly. > Unfortunately strftime(3)'s notion of week number only comes close > to DIN 1355: > [ISO 9899 quotation deleted] UTSL. case 'V': /* ** From Arnold Robbins' strftime version 3.0: ** "the week number of the year (the first ** Monday as the first day of week 1) as a ** decimal number (01-53). The method for ** determining the week number is as specified ** by ISO 8601 (to wit: if the week containing ** January 1 has four or more days in the new ** year, then it is week 1, otherwise it is ** week 53 of the previous year and the next ** week is week 1)." ** (ado, 5/24/93) */ /* ** XXX--If January 1 falls on a Friday, ** January 1-3 are part of week 53 of the ** previous year. By analogy, if January ** 1 falls on a Thursday, are December 29-31 ** of the PREVIOUS year part of week 1??? ** (ado 5/24/93) */ /* ** You are understood not to expect this. */ { int i; I believe that more recent versions of this code also provide a conversion to match the ISO 8601 year-of-week, but our current version doesn't. (I once made a stab at updating ours, but the locale code has changed too much.) -GAWollman -- Garrett A. Wollman | O Siem / We are all family / O Siem / We're all the same wollman@lcs.mit.edu | O Siem / The fires of freedom Opinions not those of| Dance in the burning flame MIT, LCS, CRS, or NSA| - Susan Aglukark and Chad Irschick From owner-freebsd-current Mon Sep 29 20:59:07 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id UAA29527 for current-outgoing; Mon, 29 Sep 1997 20:59:07 -0700 (PDT) Received: from bsdx.dyn.ml.org (root@pm335-39.dialip.mich.net [35.9.11.41]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id UAA29514 for ; Mon, 29 Sep 1997 20:59:00 -0700 (PDT) Received: from hotmail.com (user1@localhost.dyn.ml.org [127.0.0.1]) by bsdx.dyn.ml.org (8.8.7/8.8.5) with ESMTP id XAA14321 for ; Mon, 29 Sep 1997 23:58:56 -0400 (EDT) Message-ID: <343078FE.891ADB13@hotmail.com> Date: Mon, 29 Sep 1997 23:58:54 -0400 From: Adam McDougall X-Mailer: Mozilla 4.03b8 [en] (X11; I; FreeBSD 3.0-CURRENT i386) MIME-Version: 1.0 To: current@freebsd.org Subject: ISDN in 3.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 know BISDN was an experimental option in 2.2.2-RELEASE, has it been integrated into 3.0? Also, is it safe to try to put it in yourself if its meant for 2.2.2? TIA From owner-freebsd-current Mon Sep 29 21:50:13 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id VAA02105 for current-outgoing; Mon, 29 Sep 1997 21:50:13 -0700 (PDT) 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 VAA02100 for ; Mon, 29 Sep 1997 21:50:06 -0700 (PDT) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id VAA23888 for ; Mon, 29 Sep 1997 21:41:59 -0700 (PDT) Received: from current1.whistle.com(207.76.205.22) via SMTP by alpo.whistle.com, id smtpd023882; Tue Sep 30 04:41:53 1997 Message-ID: <343082D9.41C67EA6@whistle.com> Date: Mon, 29 Sep 1997 21:40:57 -0700 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.org Subject: buf struct & scsi disk IO availability. Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I have hit a point on which I am not on firm ground.. I would like to do some IO from a disk at PROBE time. In my original SCSI code, this would have been ok, as long as I didn't need interrupts. I thought I should check the following points with thre readers of -current before I go further however.. 1/ is the buf system set up fully by this time, i.e. can I user getebuf()? david? bruce? john? 2/ Jason, if I use the disk as a direct result of the scsi_attach() routine, does that catch you off guard in the aic driver? In other words, when you call scsi_attach() and friends, are you set up enough to handle that routine looping back and in turn asking you to perform IO (e.g. to read the fdisk table). If this is not the case, I have a work-around which would be to queue further configuration to occur at some later time (but before mounting root), but it wouldn't be so clean. julian From owner-freebsd-current Tue Sep 30 00:03:27 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id AAA08056 for current-outgoing; Tue, 30 Sep 1997 00:03:27 -0700 (PDT) Received: from usr01.primenet.com (tlambert@usr01.primenet.com [206.165.6.201]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id AAA08051 for ; Tue, 30 Sep 1997 00:03:24 -0700 (PDT) Received: (from tlambert@localhost) by usr01.primenet.com (8.8.5/8.8.5) id AAA16827; Tue, 30 Sep 1997 00:03:22 -0700 (MST) From: Terry Lambert Message-Id: <199709300703.AAA16827@usr01.primenet.com> Subject: Re: buf struct & scsi disk IO availability. To: julian@whistle.com (Julian Elischer) Date: Tue, 30 Sep 1997 07:03:21 +0000 (GMT) Cc: current@FreeBSD.ORG In-Reply-To: <343082D9.41C67EA6@whistle.com> from "Julian Elischer" at Sep 29, 97 09:40:57 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 hit a point on which I am not on firm ground.. > > I would like to do some IO from a disk at PROBE time. > In my original SCSI code, this would have been ok, as long as > I didn't need interrupts. I thought I should check the following > points with thre readers of -current before I go further however.. > > 1/ is the buf system set up fully by this time, > i.e. can I user getebuf()? > david? bruce? john? Heh. I wrote the original SYSINIT stuff and you checked it in, but you have to ask??? 8-). SI_SUB_DRIVERS = 0x23000000, /* Let Drivers initialize */ SI_SUB_CONFIGURE = 0x24000000, /* Configure devices */ SI_SUB_VM_CONF = 0x38000000, /* config VM, set limits*/ This should mean "no". Probably the "probe" and the "attach" need to be seperated. Can you live with attach time instead of probe time? I think if the answer is "no", an architectural change is required. See /sys/sys/kernel.h and search for "SI_". If this is for a "registry" type mechanism, a BIOS-based I/O is not out of the question, I think. > 2/ Jason, if I use the disk as a direct result of the scsi_attach() > routine, does that catch you off guard in the aic driver? I don't know this, but the attach should be much more ready than the probe. > In other words, when you call scsi_attach() and friends, > are you set up enough to handle that routine looping back and in turn > asking you to perform IO (e.g. to read the fdisk table). > > If this is not the case, I have a work-around which would be to queue > further configuration to occur at some later time (but before > mounting root), but it wouldn't be so clean. This sounds most reasonable. Windows does the same thing, and generates certain "subsystem is read for use" initialization events which drivers and other things can catch and then do incremental work using. Despite the source of the idea, it's a good idea, IMO. 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 Sep 30 00:34:47 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id AAA09662 for current-outgoing; Tue, 30 Sep 1997 00:34:47 -0700 (PDT) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id AAA09651 for ; Tue, 30 Sep 1997 00:34:42 -0700 (PDT) Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id JAA28866; Tue, 30 Sep 1997 09:34:40 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.8.7/8.8.5) id JAA07929; Tue, 30 Sep 1997 09:29:26 +0200 (MET DST) Message-ID: <19970930092926.PP33761@uriah.heep.sax.de> Date: Tue, 30 Sep 1997 09:29:26 +0200 From: j@uriah.heep.sax.de (J Wunsch) To: current@FreeBSD.ORG Cc: mcdougala@hotmail.com (Adam McDougall) Subject: Re: ISDN in 3.0? References: <343078FE.891ADB13@hotmail.com> X-Mailer: Mutt 0.60_p2-3,5,8-9 Mime-Version: 1.0 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 Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <343078FE.891ADB13@hotmail.com>; from Adam McDougall on Sep 29, 1997 23:58:54 -0400 Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk As Adam McDougall wrote: > I know BISDN was an experimental option in 2.2.2-RELEASE, has it been > integrated into 3.0? The current status of BISDN is ``on indefinite hold'', for legal reasons. If all goes well, and given the currently planned timeframe for FreeBSD 3.0 (and the current pace of Hellmuth Michaelis's ongoing work :), it's not unlikely that the rewrite will be complete before FreeBSD 3.0. > Also, is it safe to try to put it in yourself if > its meant for 2.2.2? BISND 0.97 is quite a little aged now, but with some hand-fiddling, you should get it going. A number of people are running it in some 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 Sep 30 00:59:37 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id AAA11007 for current-outgoing; Tue, 30 Sep 1997 00:59:37 -0700 (PDT) Received: from news1.gtn.com (news1.gtn.com [194.77.0.15]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id AAA10995 for ; Tue, 30 Sep 1997 00:59:28 -0700 (PDT) Received: (from uucp@localhost) by news1.gtn.com (8.8.6/8.8.6) with UUCP id IAA20512; Tue, 30 Sep 1997 08:45:11 +0100 (MET) Received: (from andreas@localhost) by klemm.gtn.com (8.8.7/8.8.7) id JAA24276; Tue, 30 Sep 1997 09:41:02 +0200 (CEST) Message-ID: <19970930094102.02347@klemm.gtn.com> Date: Tue, 30 Sep 1997 09:41:02 +0200 From: Andreas Klemm To: Adam McDougall Cc: current@FreeBSD.ORG Subject: Re: ISDN in 3.0? References: <343078FE.891ADB13@hotmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.81 In-Reply-To: <343078FE.891ADB13@hotmail.com>; from Adam McDougall on Mon, Sep 29, 1997 at 11:58:54PM -0400 X-Disclaimer: A free society is one where it is safe to be unpopular X-Operating-System: FreeBSD 3.0-CURRENT SMP Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Mon, Sep 29, 1997 at 11:58:54PM -0400, Adam McDougall wrote: > I know BISDN was an experimental option in 2.2.2-RELEASE, has it been > integrated into 3.0? Also, is it safe to try to put it in yourself if > its meant for 2.2.2? TIA I'm running it here without problems on a -current system. All you need are some patches, since -current introduces some changes. My patches aren't officially released and are still not on a ftp server. If you like I can send them to you. -- Andreas Klemm powered by ,,symmetric multiprocessor FreeBSD'' andreas@klemm.gtn.com - http://www.freebsd.org/~fsmp/SMP/SMP.html andreas@FreeBSD.ORG - http://www.freebsd.org/~fsmp/SMP/benches.html From owner-freebsd-current Tue Sep 30 01:13:37 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id BAA12038 for current-outgoing; Tue, 30 Sep 1997 01:13:37 -0700 (PDT) Received: from sendero-ppp.i-connect.net (sendero-ppp.i-Connect.Net [206.190.143.100]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id BAA12030 for ; Tue, 30 Sep 1997 01:13:34 -0700 (PDT) Received: (qmail 5746 invoked by uid 1000); 30 Sep 1997 08:13:59 -0000 Message-ID: X-Mailer: XFMail 1.2-alpha-092597 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <199709300703.AAA16827@usr01.primenet.com> Date: Tue, 30 Sep 1997 01:13:59 -0700 (PDT) Organization: Atlas Telecom From: Simon Shapiro To: Terry Lambert Subject: Re: buf struct & scsi disk IO availability. Cc: current@FreeBSD.ORG, (Julian Elischer) Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Hi Terry Lambert; On 30-Sep-97 you wrote: ... > SI_SUB_DRIVERS = 0x23000000, /* Let Drivers initialize */ > SI_SUB_CONFIGURE = 0x24000000, /* Configure devices */ > SI_SUB_VM_CONF = 0x38000000, /* config VM, set limits*/ > > This should mean "no". > > Probably the "probe" and the "attach" need to be seperated. Can you > live with attach time instead of probe time? I think if the answer > is "no", an architectural change is required. > > See /sys/sys/kernel.h and search for "SI_". > > If this is for a "registry" type mechanism, a BIOS-based I/O is not > out of the question, I think. There is always the posibility of issuing SCSI commands directly into static buffers, or even malloced one. I issue a number of SCSI command at init time from the DPT driver. Not disk i/o but scsi commands all the same. --- Sincerely Yours, Simon Shapiro Atlas Telecom Senior Architect 14355 SW Allen Blvd., Suite 130 Beaverton OR 97005 Shimon@i-Connect.Net Voice: 503.799.2313 From owner-freebsd-current Tue Sep 30 01:21:22 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id BAA12595 for current-outgoing; Tue, 30 Sep 1997 01:21:22 -0700 (PDT) Received: from silvia.HIP.Berkeley.EDU (ala-ca13-23.ix.netcom.com [204.32.168.55]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id BAA12587 for ; Tue, 30 Sep 1997 01:21:19 -0700 (PDT) Received: (from asami@localhost) by silvia.HIP.Berkeley.EDU (8.8.7/8.6.9) id BAA10604; Tue, 30 Sep 1997 01:21:03 -0700 (PDT) Date: Tue, 30 Sep 1997 01:21:03 -0700 (PDT) Message-Id: <199709300821.BAA10604@silvia.HIP.Berkeley.EDU> To: ache@nagual.pp.ru CC: jdp@polstra.com, current@freebsd.org In-reply-to: (message from =?KOI8-R?B?4c7E0sXKIP7F0s7P1w==?= on Tue, 30 Sep 1997 02:20:29 +0400 (MSD)) Subject: Re: CVSup-15.2 is now available From: asami@cs.berkeley.edu (Satoshi Asami) Sender: owner-freebsd-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk * > ftp://ftp.FreeBSD.org/pub/FreeBSD/packages-current/net/cvsup-15.2.tgz This should probably be "packages-stable" for now. I think it will run on -current too. Satoshi From owner-freebsd-current Tue Sep 30 01:50:17 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id BAA13896 for current-outgoing; Tue, 30 Sep 1997 01:50:17 -0700 (PDT) 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 BAA13890 for ; Tue, 30 Sep 1997 01:50:12 -0700 (PDT) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id BAA28128; Tue, 30 Sep 1997 01:41:35 -0700 (PDT) Received: from current1.whistle.com(207.76.205.22) via SMTP by alpo.whistle.com, id smtpd028126; Tue Sep 30 08:41:33 1997 Date: Tue, 30 Sep 1997 01:40:37 -0700 (PDT) From: Julian Elischer To: Simon Shapiro cc: Terry Lambert , current@FreeBSD.ORG Subject: Re: buf struct & scsi disk IO availability. 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, 30 Sep 1997, Simon Shapiro wrote: > > Hi Terry Lambert; On 30-Sep-97 you wrote: > > ... > > > SI_SUB_DRIVERS = 0x23000000, /* Let Drivers initialize */ > > SI_SUB_CONFIGURE = 0x24000000, /* Configure devices */ > > SI_SUB_VM_CONF = 0x38000000, /* config VM, set limits*/ > > > > This should mean "no". > > > > Probably the "probe" and the "attach" need to be seperated. Can you > > live with attach time instead of probe time? I think if the answer > > is "no", an architectural change is required. > > > > See /sys/sys/kernel.h and search for "SI_". > > > > If this is for a "registry" type mechanism, a BIOS-based I/O is not > > out of the question, I think. > > There is always the posibility of issuing SCSI commands directly into > static buffers, or even malloced one. I issue a number of SCSI command at > init time from the DPT driver. Not disk i/o but scsi commands all the same. I've ended up queuing requests for more work to be done at time SI_SUB_INT_CONFIG_HOOK which is for this.. I think Justin (who I mistakenly called JASON in my email) is worlking on a generic way of doing this but till I see it I've hacked my own little function as I write the machine is booting.. (looks on other VTY to see if it made it) hmm it came up and my callout queue worked but my IO failed.. back tothe drawing board.. oh yeah, the reason I'm not doing it staticaly is I want this to be able to happen at any time, from loadable modules. (etc.) and statically declared stuff is a pain. > > > --- > > > Sincerely Yours, > > Simon Shapiro Atlas Telecom > Senior Architect 14355 SW Allen Blvd., Suite 130 Beaverton OR 97005 > Shimon@i-Connect.Net Voice: 503.799.2313 > From owner-freebsd-current Tue Sep 30 04:01:55 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id EAA19596 for current-outgoing; Tue, 30 Sep 1997 04:01:55 -0700 (PDT) Received: from rvc1.informatik.ba-stuttgart.de (isdn019.stuttgart.netsurf.de [194.195.220.210]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id EAA19585 for ; Tue, 30 Sep 1997 04:01:49 -0700 (PDT) Received: (from helbig@localhost) by rvc1.informatik.ba-stuttgart.de (8.8.7/8.8.5) id NAA00699; Tue, 30 Sep 1997 13:01:08 +0200 (MET DST) From: Wolfgang Helbig Message-Id: <199709301101.NAA00699@rvc1.informatik.ba-stuttgart.de> Subject: Re: Adding algorithms [Was: cvs commit: src/usr.bin/cksum crc32.c ...] In-Reply-To: <199709292328.TAA13519@khavrinen.lcs.mit.edu> from Garrett Wollman at "Sep 29, 97 07:28:32 pm" To: wollman@khavrinen.lcs.mit.edu (Garrett Wollman) Date: Tue, 30 Sep 1997 13:01:03 +0200 (MET DST) Cc: helbig@Informatik.BA-Stuttgart.DE, wollman@khavrinen.lcs.mit.edu, current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL30 (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 > < said: > > >> ISO 8601. The strftime(3) function already provides this > >> functionality, although there is unfortunately no direct > >> iso8601weeknumber() function to give you the integer value directly. > > > Unfortunately strftime(3)'s notion of week number only comes close > > to DIN 1355: > > > [ISO 9899 quotation deleted] It seems to me that %V is not specified in ISO 9899. So our strftime(3) is an extension to ISO C in this respect. (The man page mentions %s as the only extension) > > UTSL. > > case 'V': > /* > ** From Arnold Robbins' strftime version 3.0: > ** "the week number of the year (the first > ** Monday as the first day of week 1) as a > ** decimal number (01-53). The method for > ** determining the week number is as specified > ** by ISO 8601 (to wit: if the week containing > ** January 1 has four or more days in the new > ** year, then it is week 1, otherwise it is > ** week 53 of the previous year and the next > ** week is week 1)." > ** (ado, 5/24/93) > */ > /* > ** XXX--If January 1 falls on a Friday, > ** January 1-3 are part of week 53 of the > ** previous year. By analogy, if January > ** 1 falls on a Thursday, are December 29-31 > ** of the PREVIOUS year part of week 1??? > ** (ado 5/24/93) According to ISO 8601 the answer is "yes" and the current implementation of strftime(3) is wrong in this respect. For Dec. 31st 1996 it replaces %V by 53 instead of 01. Another error occurs on Jan. 1st 1999: It should be week 53 but %V is replaced by 52. Any objections to fix it? [...] > I believe that more recent versions of this code also provide a > conversion to match the ISO 8601 year-of-week, but our current version > doesn't. (I once made a stab at updating ours, but the locale code > has changed too much.) Where can one get that more recent versions? Wolfgang From owner-freebsd-current Tue Sep 30 04:52:09 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id EAA21297 for current-outgoing; Tue, 30 Sep 1997 04:52:09 -0700 (PDT) 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 EAA21292 for ; Tue, 30 Sep 1997 04:52:04 -0700 (PDT) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.5/8.6.9) id VAA21109; Tue, 30 Sep 1997 21:45:51 +1000 Date: Tue, 30 Sep 1997 21:45:51 +1000 From: Bruce Evans Message-Id: <199709301145.VAA21109@godzilla.zeta.org.au> To: julian@whistle.com, tlambert@primenet.com Subject: Re: buf struct & scsi disk IO availability. Cc: current@freebsd.org Sender: owner-freebsd-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >> I would like to do some IO from a disk at PROBE time. >> ... >> 1/ is the buf system set up fully by this time, Not quite. >> i.e. can I user getebuf()? getebuf() doesn't exist. If you mean geteblk(), not quite. Buffers are initialized before devices, but bad things happen in the (unlikely here) event that geteblk() sleeps. `cold' is still 1, so tsleep() doesn't actually sleep, it just does slplx(safepri) and returns. There are several problems with this: 1. safepri isn't actually safe in general. It is 0 but should be at least SWI_AST_MASK; this is a bug. 2. safepri isn't safe during device initialization. During at least ISA initialization, the ipl is splhigh(), and lowering this is not good. 3. Lowering the ipl can't be expected to work during device initialization. Device drivers can't be expected to handle interrupts at this time, so no progress may be made towards freeing the resources that Lowering the ipl is not good in general. However, it sometimes helps(?) by allowing writing of dirty buffers after the system panics at a high ipl (tsleep() also lowers the ipl if it is called during a panic). Disk drivers can't be expected to work at this time, but lowering the ipl may allow the to work (dangerously). Another answer: no :-). >Heh. I wrote the original SYSINIT stuff and you checked it in, but >you have to ask??? 8-). > >SI_SUB_DRIVERS = 0x23000000, /* Let Drivers initialize */ >SI_SUB_CONFIGURE = 0x24000000, /* Configure devices */ >SI_SUB_VM_CONF = 0x38000000, /* config VM, set limits*/ > >This should mean "no". This doesn't mean much. SI_SUB_VM_CONF doesn't configure VM, it just sets limits. VM is initialized earlier in SI_SUB_VM. Buffers are initialized earlier in SI_SUB_CPU. However, because of the above problems, buffers can't be used until at least the end of device configuration when `cold' is cleared. I think geteblk() does work then - I think tsleep() works well enough, although clock interrupts are not initialized, so timeouts don't work. Anyway, you should use Justin's new method of delaying device configuration until all interrupts work. Bruce From owner-freebsd-current Tue Sep 30 06:43:33 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id GAA25865 for current-outgoing; Tue, 30 Sep 1997 06:43:33 -0700 (PDT) Received: from khavrinen.lcs.mit.edu (khavrinen.lcs.mit.edu [18.24.4.193]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id GAA25859 for ; Tue, 30 Sep 1997 06:43:29 -0700 (PDT) Received: (from wollman@localhost) by khavrinen.lcs.mit.edu (8.8.5/8.8.5) id JAA15468; Tue, 30 Sep 1997 09:43:02 -0400 (EDT) Date: Tue, 30 Sep 1997 09:43:02 -0400 (EDT) From: Garrett Wollman Message-Id: <199709301343.JAA15468@khavrinen.lcs.mit.edu> To: Wolfgang Helbig Cc: wollman@khavrinen.lcs.mit.edu (Garrett Wollman), current@FreeBSD.ORG Subject: Re: Adding algorithms [Was: cvs commit: src/usr.bin/cksum crc32.c ...] In-Reply-To: <199709301101.NAA00699@rvc1.informatik.ba-stuttgart.de> References: <199709292328.TAA13519@khavrinen.lcs.mit.edu> <199709301101.NAA00699@rvc1.informatik.ba-stuttgart.de> Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk < said: >> I believe that more recent versions of this code also provide a >> conversion to match the ISO 8601 year-of-week, but our current version >> doesn't. (I once made a stab at updating ours, but the locale code >> has changed too much.) > Where can one get that more recent versions? ftp://elsie.nci.nih.gov -GAWollman -- Garrett A. Wollman | O Siem / We are all family / O Siem / We're all the same wollman@lcs.mit.edu | O Siem / The fires of freedom Opinions not those of| Dance in the burning flame MIT, LCS, CRS, or NSA| - Susan Aglukark and Chad Irschick From owner-freebsd-current Tue Sep 30 06:57:12 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id GAA26395 for current-outgoing; Tue, 30 Sep 1997 06:57:12 -0700 (PDT) Received: from pluto.plutotech.com (root@mail.plutotech.com [206.168.67.137]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id GAA26386 for ; Tue, 30 Sep 1997 06:57:08 -0700 (PDT) Received: from narnia.plutotech.com (narnia.plutotech.com [206.168.67.130]) by pluto.plutotech.com (8.8.5/8.8.5) with ESMTP id HAA05978; Tue, 30 Sep 1997 07:57:07 -0600 (MDT) Message-Id: <199709301357.HAA05978@pluto.plutotech.com> To: Julian Elischer cc: current@FreeBSD.ORG Subject: Re: buf struct & scsi disk IO availability. In-reply-to: Your message of "Mon, 29 Sep 1997 21:40:57 PDT." <343082D9.41C67EA6@whistle.com> Date: Tue, 30 Sep 1997 07:56:40 -0600 From: "Justin T. Gibbs" Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >2/ Jason, if I use the disk as a direct result of the scsi_attach() Are you talking to me? 8-) >If this is not the case, I have a work-around which would be to queue >further configuration to occur at some later time (but before >mounting root), but it wouldn't be so clean. > >julian All I/O to the SCSI system should be postponed until interrupt services are available. This was why I added the "interrupt driven configuration hooks". Your hook will be called before the root and dump device are configured and the boot will only continue once you remove your hook. Look in sys/kern/subr_autoconf.c for details. -- Justin T. Gibbs =========================================== FreeBSD: Turning PCs into workstations =========================================== From owner-freebsd-current Tue Sep 30 07:11:43 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id HAA27100 for current-outgoing; Tue, 30 Sep 1997 07:11:43 -0700 (PDT) Received: from pluto.plutotech.com (root@mail.plutotech.com [206.168.67.137]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id HAA27092 for ; Tue, 30 Sep 1997 07:11:41 -0700 (PDT) Received: from narnia.plutotech.com (narnia.plutotech.com [206.168.67.130]) by pluto.plutotech.com (8.8.5/8.8.5) with ESMTP id IAA06291; Tue, 30 Sep 1997 08:11:17 -0600 (MDT) Message-Id: <199709301411.IAA06291@pluto.plutotech.com> To: Julian Elischer cc: Simon Shapiro , Terry Lambert , current@FreeBSD.ORG Subject: Re: buf struct & scsi disk IO availability. In-reply-to: Your message of "Tue, 30 Sep 1997 01:40:37 PDT." Date: Tue, 30 Sep 1997 08:10:50 -0600 From: "Justin T. Gibbs" Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >I've ended up queuing requests for more work to be done at >time SI_SUB_INT_CONFIG_HOOK >which is for this.. >I think Justin (who I mistakenly called JASON in my email) >is worlking on a generic way of doing this but till I see it >I've hacked my own little function It's in current. If you have a kernel that has SI_SUB_INT_CONFIG_HOOK, you have all of the code in there to do this. -- Justin T. Gibbs =========================================== FreeBSD: Turning PCs into workstations =========================================== From owner-freebsd-current Tue Sep 30 07:37:03 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id HAA28577 for current-outgoing; Tue, 30 Sep 1997 07:37:03 -0700 (PDT) Received: from nagual.pp.ru (ache@ache.relcom.ru [194.58.229.133]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id HAA28572 for ; Tue, 30 Sep 1997 07:36:57 -0700 (PDT) Received: (from ache@localhost) by nagual.pp.ru (8.8.7/8.8.7) id SAA00606; Tue, 30 Sep 1997 18:35:47 +0400 (MSD) Date: Tue, 30 Sep 1997 18:35:44 +0400 (MSD) From: =?KOI8-R?B?4c7E0sXKIP7F0s7P1w==?= To: Satoshi Asami cc: jdp@polstra.com, current@FreeBSD.ORG Subject: Re: CVSup-15.2 is now available In-Reply-To: <199709300821.BAA10604@silvia.HIP.Berkeley.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, 30 Sep 1997, Satoshi Asami wrote: > * > ftp://ftp.FreeBSD.org/pub/FreeBSD/packages-current/net/cvsup-15.2.tgz > > This should probably be "packages-stable" for now. I think it will > run on -current too. I like run its -current version for some reasons (f.e. malloc optimization). Could somebody put -current version there? -- Andrey A. Chernov http://www.nagual.pp.ru/~ache/ From owner-freebsd-current Tue Sep 30 10:34:11 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id KAA08963 for current-outgoing; Tue, 30 Sep 1997 10:34:11 -0700 (PDT) Received: from ady.warp.starnets.ro (ady.warp.starnets.ro [193.226.124.33]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id KAA08949 for ; Tue, 30 Sep 1997 10:33:58 -0700 (PDT) Received: from localhost (ady@localhost) by ady.warp.starnets.ro (8.8.5/8.8.5) with SMTP id UAA02093 for ; Tue, 30 Sep 1997 20:32:35 +0300 (EEST) Date: Tue, 30 Sep 1997 20:32:35 +0300 (EEST) From: Penisoara Adrian To: current@FreeBSD.org Subject: Missing a chunk from the 3.0-970718-SNAP distribution... 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, Sorry to bother you, but I'm in a bit of a trouble: does anybody have the 'doc/doc.aj' (MD5 = 5b9e23cf58007c985141a16260df5492) chunk from the 3.0-970718-SNAP ? My mirrored tree was corrupted and I badly need the "doc" package ... If you have it please send it to me as an attachement to 'ady@warp.starnets.ro' or please give me a URL link to it... TIA, Ady (@warp.starnets.ro) From owner-freebsd-current Tue Sep 30 11:37:45 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id LAA12382 for current-outgoing; Tue, 30 Sep 1997 11:37:45 -0700 (PDT) Received: from bmccane.uit.net (bmccane.uit.net [209.83.205.48]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id LAA12362; Tue, 30 Sep 1997 11:37:38 -0700 (PDT) Received: from bmccane.uit.net (localhost.mccane.com [127.0.0.1]) by bmccane.uit.net (8.8.7/8.8.5) with ESMTP id NAA07381; Tue, 30 Sep 1997 13:37:23 -0500 (CDT) Message-Id: <199709301837.NAA07381@bmccane.uit.net> X-Mailer: exmh version 2.0gamma 1/27/96 To: current@freebsd.org cc: hackers@freebsd.org Subject: PPP problems Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 30 Sep 1997 13:37:21 -0500 From: Wm Brian McCane Sender: owner-freebsd-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Greetings, Sorry for the crosspost, but I thought I might not get hold of the right person without it. I did a make world, and kernel rebuild on Sep 20 using current, and everything worked just spiffy. On Sep 26, I replaced my old slow internal modem with a new fast PNP modem. This motherboard does not have PNP in the BIOS so I rebuilt the kernel with pnp installed. After rebooting, everything seemed to work ok, but my ps and other `kvm' related programs didn't work. So, not wanting to look foolish, I did the right thing, I did a `make world', and another kernel build and rebooted. Once again everything worked, until I went to eat dinner.... Okay, here's what I am seeing: I use kernel PPP for a full time connection to the InterNet My connection gets dropped every 5 hours by my ISP (shouldn't unlimited mean UNLIMITED!) Occasionally pppd does not recognize that the connection has dropped, and hangs there. If I kill -9 pppd, it becomes a Zombie (state in `ps' is SEs) I tried to change to iij-ppp, and it will not reconnect after it is disconnected (It doesn't recognize the disconnect). If I kill iij-ppp and restart it by hand, it is screwed up and still will not talk. If I run iij-ppp first, then kill it when the connection dies, I can connect with pppd (once). The only way to reconnect after that is to reboot. I tried my old modem, it has the same behaviour so it is not an incompatibility issue as I see it. When the PPP is screwed up, there is a noticable slow down of the system. But systat shows 90-95% idle. Logging in from another PC feels like I am doing telnet over a 9600 baud dialin line (I've done this, it sucks). My console is dead. It goes through the "Local package initialization", and then no more output goes to the screen. If I login blind, it succeeds, I verified this from a rlogin. help!!! brian BTW> I have already written a script to check out all the code as it was on 09/20/97, and will probably do this unless someone has some helpful suggestions. From owner-freebsd-current Tue Sep 30 13:17:30 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id NAA19133 for current-outgoing; Tue, 30 Sep 1997 13:17:30 -0700 (PDT) Received: from sendero-ppp.i-connect.net (sendero-ppp.i-Connect.Net [206.190.143.100]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id NAA19123 for ; Tue, 30 Sep 1997 13:17:24 -0700 (PDT) Received: (qmail 11576 invoked by uid 1000); 30 Sep 1997 20:17:37 -0000 Message-ID: X-Mailer: XFMail 1.2-alpha-092597 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <199709301837.NAA07381@bmccane.uit.net> Date: Tue, 30 Sep 1997 13:17:37 -0700 (PDT) Organization: Atlas Telecom From: Simon Shapiro To: Wm Brian McCane Subject: RE: PPP problems Cc: hackers@FreeBSD.ORG, current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Hi Wm Brian McCane; On 30-Sep-97 you wrote: ... > and another kernel build and rebooted. Once again everything worked, > until I > went to eat dinner.... You see! Had you stayed at the keyboard... :-) > Okay, here's what I am seeing: > > I use kernel PPP for a full time connection to the InterNet > My connection gets dropped every 5 hours by my ISP > (shouldn't unlimited mean UNLIMITED!) Yup! Here too... To this i might add: Sep 29 10:52:30 sendero /kernel.sendero: ppp0: no compressor for [15 3 29], 3 Sep 29 10:52:30 sendero /kernel.sendero: ppp0: no compressor for [18 4 8], 4 Sep 30 01:21:27 sendero /kernel.sendero: ppp0: no compressor for [15 3 29], 3 Sep 30 01:21:27 sendero /kernel.sendero: ppp0: no compressor for [18 4 8], 4 Sep 30 01:24:47 sendero /kernel.sendero: ppp0: no compressor for [15 3 29], 3 Sep 30 01:24:47 sendero /kernel.sendero: ppp0: no compressor for [18 4 8], 4 Sep 30 12:16:56 sendero /kernel.sendero: ppp0: no compressor for [15 3 29], 3 Sep 30 12:16:56 sendero /kernel.sendero: ppp0: no compressor for [18 4 8], 4 and ... Sep 30 12:24:09 sendero /kernel.sendero: ppp0: line error 4000000 Sep 30 12:24:09 sendero last message repeated 2 times Sep 30 12:24:10 sendero /kernel.sendero: sio2: 3 more silo overflows (total 3) Sep 30 12:38:23 sendero /kernel.sendero: ppp0: line error 4000000 Sep 30 12:38:24 sendero /kernel.sendero: sio2: 1 more silo overflow (total 4) Current as of last night. Also ppp in sysinstall needs -ldes again to compile... --- Sincerely Yours, Simon Shapiro Atlas Telecom Senior Architect 14355 SW Allen Blvd., Suite 130 Beaverton OR 97005 Shimon@i-Connect.Net Voice: 503.799.2313 From owner-freebsd-current Tue Sep 30 13:37:11 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id NAA20512 for current-outgoing; Tue, 30 Sep 1997 13:37:11 -0700 (PDT) Received: from mexico.brainstorm.eu.org (root@mexico.brainstorm.fr [193.56.58.253]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id NAA20500 for ; Tue, 30 Sep 1997 13:36:54 -0700 (PDT) Received: from brasil.brainstorm.eu.org (brasil.brainstorm.fr [193.56.58.33]) by mexico.brainstorm.eu.org (8.8.4/8.8.4) with ESMTP id WAA02953 for ; Tue, 30 Sep 1997 22:36:46 +0200 Received: (from uucp@localhost) by brasil.brainstorm.eu.org (8.8.6/brasil-1.2) with UUCP id WAA28883 for freebsd-current@FreeBSD.ORG; Tue, 30 Sep 1997 22:36:35 +0200 Received: (from roberto@localhost) by keltia.freenix.fr (8.8.7/keltia-2.10/nospam) id WAA00597; Tue, 30 Sep 1997 22:35:43 +0200 (CEST) Message-ID: <19970930223542.44057@keltia.freenix.fr> Date: Tue, 30 Sep 1997 22:35:42 +0200 From: Ollivier Robert To: "FreeBSD Current Users' list" Subject: Geometry weirdness with sysinstall/libdisk Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.84 X-Operating-System: FreeBSD 3.0-CURRENT Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Hi, Why is tst01 (bundled with libdisk) getting my geometry 1) wrong and 2) differently for each of my disks ? It forbid me to use sysinstall as a disk configuration utility for all my other disks because 1. the geometry is wrong and giving it the good one doesn't help, 2. the slices information is decoded wrongly so I can't just modify the existing label with it. sd0 is an IBM DCAS UW 4.3 GB with 2 DOS slices and my booting FreeBSD slice. tst01 sd0 correctly gives: --==##==-- Debug_Disk(sd0) flags=0 bios_geom=1018/132/63 = 8465688 boot1=0x0, boot2=0x0, bootmgr=0x0 --> 0x14040 0 8467200 8467199 sd0 whole 0x00 --> 0x14080 0 63 62 - unused 0x00 --> 0x140c0 63 415737 415799 sd0s1 fat 0x06 = --> 0x14100 415800 5729724 6145523 sd0s2 freebsd 0xa5 C= --> 0x14180 415800 51200 466999 sd0s2a part 0x07 --> 0x14200 467000 262144 729143 sd0s2b part 0x01 --> 0x14240 729144 409600 1138743 sd0s2e part 0x07 --> 0x14280 1138744 1024000 2162743 sd0s2f part 0x07 --> 0x142c0 2162744 819200 2981943 sd0s2g part 0x07 --> 0x14300 2981944 1433600 4415543 sd0s2h part 0x07 --> 0x14340 4415544 1729980 6145523 sd0s2d part 0x07 --> 0x141c0 6145524 2320164 8465687 sd0s3 extended 0x05 = --> 0x14380 6145524 63 6145586 - unused 0x00 --> 0x14140 6145587 2320101 8465687 sd0s5 fat 0x06 = --> 0x143c0 8465688 1512 8467199 - unused 0x00 Now, sd2 is an IBM DORS 2 GB narrow. tst01 sd2 gives this absolutely false geometry: --==##==-- Debug_Disk(sd2) flags=0 bios_geom=13045/54/6 = 4226580 boot1=0x0, boot2=0x0, bootmgr=0x0 --> 0x14040 0 4226725 4226724 sd2 whole 0x00 > --> 0x14080 0 4226725 4226724 - unused 0x00 > The right one is obtained by using sd2c as a device : --==##==-- Debug_Disk(sd2c) flags=0 bios_geom=2063/64/32 = 4225024 boot1=0x0, boot2=0x0, bootmgr=0x0 --> 0x14040 0 4226725 4226724 sd2c whole 0x00 > --> 0x14080 0 4226725 4226724 - unused 0x00 > Anyway, the output of tst01 is still wrong on one account because the real label is the following. Why is disklabel getting the right information when libdisk can't ??? I thought they were using the same ioctl ?? And where is this 13045 coming from ? It doesn't match the -- fictious -- geometry displayed when booting with -v. Controller is an ASUS PCI-875. sd0 on internal wide cable and DORS on the internal narrow one. # /dev/rsd2c: type: SCSI disk: IBM32160 label: flags: bytes/sector: 512 sectors/track: 32 tracks/cylinder: 64 sectors/cylinder: 2048 cylinders: 2063 sectors/unit: 4226725 rpm: 5400 interleave: 1 trackskew: 0 cylinderskew: 0 headswitch: 0 # milliseconds track-to-track seek: 0 # milliseconds drivedata: 0 8 partitions: # size offset fstype [fsize bsize bps/cpg] a: 40960 0 4.2BSD 1024 8192 16 # (Cyl. 0 - 19) b: 131072 40960 swap # (Cyl. 20 - 83) c: 4226725 0 unused 0 0 # (Cyl. 0 - 2063*) d: 204800 172032 4.2BSD 1024 8192 16 # (Cyl. 84 - 183) e: 716800 376832 4.2BSD 1024 8192 16 # (Cyl. 184 - 533) f: 409600 1093632 4.2BSD 1024 8192 16 # (Cyl. 534 - 733) g: 1024000 1503232 4.2BSD 1024 8192 16 # (Cyl. 734 - 1233) h: 1699493 2527232 4.2BSD 1024 8192 16 # (Cyl. 1234 - 2063*) -- Ollivier ROBERT -=- FreeBSD: There are no limits -=- roberto@keltia.freenix.fr FreeBSD keltia.freenix.fr 3.0-CURRENT #35: Sun Sep 21 19:28:07 CEST 1997 From owner-freebsd-current Tue Sep 30 15:14:10 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id PAA25587 for current-outgoing; Tue, 30 Sep 1997 15:14:10 -0700 (PDT) Received: from bmccane.uit.net (bmccane.uit.net [209.83.205.48]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id PAA25520; Tue, 30 Sep 1997 15:13:33 -0700 (PDT) Received: (from root@localhost) by bmccane.uit.net (8.8.7/8.8.5) id RAA20779; Tue, 30 Sep 1997 17:11:06 -0500 (CDT) Date: Tue, 30 Sep 1997 17:11:06 -0500 (CDT) From: Wm Brian McCane To: Simon Shapiro cc: hackers@FreeBSD.ORG, current@FreeBSD.ORG Subject: RE: PPP 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, 30 Sep 1997, Simon Shapiro wrote: > > Hi Wm Brian McCane; On 30-Sep-97 you wrote: > > ... > > > and another kernel build and rebooted. Once again everything worked, > > until I > > went to eat dinner.... > > You see! Had you stayed at the keyboard... :-) I tried to use this argument with my wife too. I have the still healing bite marks to prove it 8(. > > Okay, here's what I am seeing: > > > > I use kernel PPP for a full time connection to the InterNet > > My connection gets dropped every 5 hours by my ISP > > (shouldn't unlimited mean UNLIMITED!) > > Yup! Here too... > > To this i might add: I haven't seen these errors, what level of debugging do you have to have turned on for them? > Sep 29 10:52:30 sendero /kernel.sendero: ppp0: no compressor for [15 3 29], > 3 > Sep 29 10:52:30 sendero /kernel.sendero: ppp0: no compressor for [18 4 8], 4 > Sep 30 01:21:27 sendero /kernel.sendero: ppp0: no compressor for [15 3 29], ... > and ... > > Sep 30 12:24:09 sendero /kernel.sendero: ppp0: line error 4000000 > Sep 30 12:24:09 sendero last message repeated 2 times > Sep 30 12:24:10 sendero /kernel.sendero: sio2: 3 more silo overflows (total > 3) > Sep 30 12:38:23 sendero /kernel.sendero: ppp0: line error 4000000 > Sep 30 12:38:24 sendero /kernel.sendero: sio2: 1 more silo overflow (total > 4) ... I have pppd run automatically from cron. It checks to see if the port is already locked, and if not it starts processing. So what I see in messages file is: Sep 29 08:00:01 bmccane pppd[13936]: Device cuaa1 is locked by pid 75 Sep 29 08:00:01 bmccane last message repeated 13 times Sep 29 08:00:01 bmccane pppd[12853]: Device cuaa1 is locked by pid 75 Sep 29 08:00:01 bmccane last message repeated 9 times Sep 29 08:00:01 bmccane pppd[13936]: Device cuaa1 is locked by pid 75 Sep 29 08:00:01 bmccane last message repeated 25 times Sep 29 08:00:03 bmccane pppd[12853]: Device cuaa1 is locked by pid 75 Nice to know that even without a valid `pid' file in /var/run, the port is still locked. This also happens after I try to kill the #*$(&% program. brian From owner-freebsd-current Tue Sep 30 15:25:42 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id PAA26399 for current-outgoing; Tue, 30 Sep 1997 15:25:42 -0700 (PDT) Received: from peeper.my.domain ([208.128.8.69]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id PAA26387 for ; Tue, 30 Sep 1997 15:25:36 -0700 (PDT) Received: (from tom@localhost) by peeper.my.domain (8.8.7/8.7.3) id RAA00741; Tue, 30 Sep 1997 17:25:23 -0500 (CDT) Message-ID: <19970930172443.47675@my.domain> Date: Tue, 30 Sep 1997 17:24:43 -0500 From: Tom Jackson To: FreeBSD Current Subject: Kernel Build/aicasm Fails Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.81e Sender: owner-freebsd-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Waiting a couple of days, still nobody else. Antbody else getting this make failure with the 30current kernel? make -f ../../dev/aic7xxx/Makefile MAKESRCPATH=../../dev/aic7xxx Warning: Object directory not changed from original /usr/src/sys/compile/PEEPER cc -O -pipe -I. -c aicasm_scan.c ../../dev/aic7xxx/aicasm_scan.l: In function `yylex': ../../dev/aic7xxx/aicasm_scan.l:69: `T_DOWNLOAD' undeclared (first use this function) ../../dev/aic7xxx/aicasm_scan.l:69: (Each undeclared identifier is reported only once ../../dev/aic7xxx/aicasm_scan.l:69: for each function it appears in.) *** Error code 1 Stop. *** Error code 1 Stop. Last good build was ctm#3068 on Sept 26 Tom From owner-freebsd-current Tue Sep 30 15:55:22 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id PAA28517 for current-outgoing; Tue, 30 Sep 1997 15:55:22 -0700 (PDT) Received: from bob.scl.ameslab.gov (bob.scl.ameslab.gov [147.155.137.254]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id PAA28509 for ; Tue, 30 Sep 1997 15:55:18 -0700 (PDT) Received: from bob.scl.ameslab.gov (localhost [127.0.0.1]) by bob.scl.ameslab.gov (8.8.7/8.8.5) with ESMTP id RAA01497; Tue, 30 Sep 1997 17:55:01 -0500 (CDT) Message-Id: <199709302255.RAA01497@bob.scl.ameslab.gov> X-Mailer: exmh version 2.0zeta 7/24/97 To: Tom Jackson cc: FreeBSD Current Subject: Re: Kernel Build/aicasm Fails In-reply-to: Your message of "Tue, 30 Sep 1997 17:24:43 CDT." <19970930172443.47675@my.domain> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 30 Sep 1997 17:55:01 -0500 From: Chris Csanady Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >Waiting a couple of days, still nobody else. Antbody else getting >this make failure with the 30current kernel? This seems to be due to the building of the asm stuff in the sys dir, and things not being up to date. Cd to ../../dev/aic7xxx/aicasm_scan.l and make clean. Chris >make -f ../../dev/aic7xxx/Makefile MAKESRCPATH=../../dev/aic7xxx >Warning: Object directory not changed from original /usr/src/sys/compile/PEEPE R >cc -O -pipe -I. -c aicasm_scan.c >../../dev/aic7xxx/aicasm_scan.l: In function `yylex': >../../dev/aic7xxx/aicasm_scan.l:69: `T_DOWNLOAD' undeclared (first use this fu nction) >../../dev/aic7xxx/aicasm_scan.l:69: (Each undeclared identifier is reported on ly once >../../dev/aic7xxx/aicasm_scan.l:69: for each function it appears in.) >*** Error code 1 > >Stop. >*** Error code 1 > >Stop. > >Last good build was ctm#3068 on Sept 26 > >Tom From owner-freebsd-current Tue Sep 30 16:04:19 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id QAA28979 for current-outgoing; Tue, 30 Sep 1997 16:04:19 -0700 (PDT) Received: from pluto.plutotech.com (root@mail.plutotech.com [206.168.67.137]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id QAA28973 for ; Tue, 30 Sep 1997 16:04:17 -0700 (PDT) Received: from narnia.plutotech.com (narnia.plutotech.com [206.168.67.130]) by pluto.plutotech.com (8.8.5/8.8.5) with ESMTP id RAA19785; Tue, 30 Sep 1997 17:04:09 -0600 (MDT) Message-Id: <199709302304.RAA19785@pluto.plutotech.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: Tom Jackson cc: FreeBSD Current Subject: Re: Kernel Build/aicasm Fails In-reply-to: Your message of "Tue, 30 Sep 1997 17:24:43 CDT." <19970930172443.47675@my.domain> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 30 Sep 1997 17:03:42 -0600 From: "Justin T. Gibbs" Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >Waiting a couple of days, still nobody else. Antbody else getting >this make failure with the 30current kernel? Perform a: make -f ../../dev/aic7xxx/Makefile MAKESRCPATH=../../dev/aic7xxx clean in your kernel build directory and just to be safe, a: cd /usr/src/sys/dev/aic7xxx;make clean >Tom -- Justin T. Gibbs =========================================== FreeBSD: Turning PCs into workstations =========================================== From owner-freebsd-current Tue Sep 30 19:02:44 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id TAA08750 for current-outgoing; Tue, 30 Sep 1997 19:02:44 -0700 (PDT) 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 TAA08742 for ; Tue, 30 Sep 1997 19:02:35 -0700 (PDT) Received: from austin.polstra.com (jdp@localhost) by austin.polstra.com (8.8.7/8.8.5) with ESMTP id TAA06712; Tue, 30 Sep 1997 19:02:11 -0700 (PDT) Message-Id: <199710010202.TAA06712@austin.polstra.com> To: =?KOI8-R?B?4c7E0sXKIP7F0s7P1w==?= cc: Satoshi Asami , current@FreeBSD.ORG Subject: Re: CVSup-15.2 is now available In-reply-to: Your message of "Tue, 30 Sep 1997 18:35:44 +0400." Date: Tue, 30 Sep 1997 19:02:11 -0700 From: John Polstra Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > I like run its -current version for some reasons (f.e. malloc > optimization). For CVSup the malloc comes from modula-3-lib, so it will be the same whether the package was built on -2.2 or -current. It's the latest version of phkmalloc, slightly modified for thread safety. Regarding other improvements in -current: The packages use shared libraries, so you should get the benefits of those improvements simply by running the program on a -current system. > Could somebody put -current version there? I don't really know what to do about this. I understand your desire for a package that's made for -current. But my -current machine usually isn't adequately up to date for building packages that are going to be publicly released. Even when I've done a make world, it still has X libraries (for example) which are somewhat old. And of course -current this week isn't the same as -current next week, so the packages would need to be updated regularly. 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 Sep 30 20:49:47 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id UAA12987 for current-outgoing; Tue, 30 Sep 1997 20:49:47 -0700 (PDT) Received: from sendero-ppp.i-connect.net (sendero-ppp.i-Connect.Net [206.190.143.100]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id UAA12932 for ; Tue, 30 Sep 1997 20:49:38 -0700 (PDT) Received: (qmail 15300 invoked by uid 1000); 1 Oct 1997 03:50:01 -0000 Message-ID: X-Mailer: XFMail 1.2-alpha-092597 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: Date: Tue, 30 Sep 1997 20:50:01 -0700 (PDT) Organization: Atlas Telecom From: Simon Shapiro To: Wm Brian McCane Subject: RE: PPP problems Cc: hackers@FreeBSD.ORG, current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Hi Wm Brian McCane; On 30-Sep-97 you wrote: ... > > To this i might add: > I haven't seen these errors, what level of debugging do you have to have > turned on for them? Just ``debug'' in /etc/ppp/options --- Sincerely Yours, Simon Shapiro Atlas Telecom Senior Architect 14355 SW Allen Blvd., Suite 130 Beaverton OR 97005 Shimon@i-Connect.Net Voice: 503.799.2313 From owner-freebsd-current Tue Sep 30 22:21:41 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id WAA17442 for current-outgoing; Tue, 30 Sep 1997 22:21:41 -0700 (PDT) Received: from peeper.my.domain ([208.128.8.69]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id WAA17436 for ; Tue, 30 Sep 1997 22:21:30 -0700 (PDT) Received: (from tom@localhost) by peeper.my.domain (8.8.7/8.7.3) id AAA04456; Wed, 1 Oct 1997 00:21:22 -0500 (CDT) Message-ID: <19971001002122.17272@my.domain> Date: Wed, 1 Oct 1997 00:21:22 -0500 From: Tom Jackson To: FreeBSD Current Subject: Re: Kernel Build/aicasm Fails References: <19970930172443.47675@my.domain> <199709302304.RAA19785@pluto.plutotech.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.81e In-Reply-To: <199709302304.RAA19785@pluto.plutotech.com>; from Justin T. Gibbs on Tue, Sep 30, 1997 at 05:03:42PM -0600 Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Yes by-zimmanee, that does work, thanks very much. I will spend the next week trying to figure why I have never seen this before ;-O Tom From owner-freebsd-current Tue Sep 30 22:50:45 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id WAA18923 for current-outgoing; Tue, 30 Sep 1997 22:50:45 -0700 (PDT) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id WAA18908 for ; Tue, 30 Sep 1997 22:50:40 -0700 (PDT) Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id HAA12273 for freebsd-current@FreeBSD.ORG; Wed, 1 Oct 1997 07:50:34 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.8.7/8.8.5) id HAA11590; Wed, 1 Oct 1997 07:26:48 +0200 (MET DST) Message-ID: <19971001072648.MU20136@uriah.heep.sax.de> Date: Wed, 1 Oct 1997 07:26:48 +0200 From: j@uriah.heep.sax.de (J Wunsch) To: freebsd-current@FreeBSD.ORG (FreeBSD Current Users' list) Subject: Re: Geometry weirdness with sysinstall/libdisk References: <19970930223542.44057@keltia.freenix.fr> X-Mailer: Mutt 0.60_p2-3,5,8-9 Mime-Version: 1.0 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 Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <19970930223542.44057@keltia.freenix.fr>; from Ollivier Robert on Sep 30, 1997 22:35:42 +0200 Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk As Ollivier Robert wrote: > Why is tst01 (bundled with libdisk) getting my geometry 1) wrong and > 2) differently for each of my disks ? Because it has sometimes too few hints what geometry the BIOS is using? > sd0 is an IBM DCAS UW 4.3 GB with 2 DOS slices and my booting FreeBSD > slice. If there are existing slices, libdisk's guesswork is IMHO easy. > tst01 sd2 gives this absolutely false geometry: > > --==##==-- > Debug_Disk(sd2) flags=0 bios_geom=13045/54/6 = 4226580 Certainly no slices present yet. > The right one is obtained by using sd2c as a device : > > --==##==-- > Debug_Disk(sd2c) flags=0 bios_geom=2063/64/32 = 4225024 They are not `right' in the sense of FreeBSD either, since they are useless for the BIOS. 2063 > 1024. 13045/54/6 is probably close to the actual drive geometry (except that for an actual geometry, it's more likely that the 54 is something like `some value between 35 and 70' or such). Actual drive geometries are uninteresting. > And where is this 13045 coming from ? >From the drive itself, i'd say. Well, no, this drive has 8205 cylinders and 6 heads: uriah # scsi -f /dev/rsd1.ctl -m 4 Number of Cylinders: 8205 Number of Heads: 6 ... uriah # scsi -f /dev/rsd1.ctl -m 3 ... Sectors per Track: 171 But again, these values are largely irrelevant. If you need to make a disk DOS-compatible, it's never a bad idea to create the DOS partition first. If you don't want it DOS-compatible, why caring for a ficticuous geometry at all? -- 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 Sep 30 22:52:22 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id WAA19045 for current-outgoing; Tue, 30 Sep 1997 22:52:22 -0700 (PDT) Received: from implode.root.com (implode.root.com [198.145.90.17]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id WAA19040 for ; Tue, 30 Sep 1997 22:52:19 -0700 (PDT) Received: from implode.root.com (localhost [127.0.0.1]) by implode.root.com (8.8.5/8.8.5) with ESMTP id WAA07634; Tue, 30 Sep 1997 22:55:01 -0700 (PDT) Message-Id: <199710010555.WAA07634@implode.root.com> To: "Justin T. Gibbs" cc: Tom Jackson , FreeBSD Current Subject: Re: Kernel Build/aicasm Fails In-reply-to: Your message of "Tue, 30 Sep 1997 17:03:42 MDT." <199709302304.RAA19785@pluto.plutotech.com> From: David Greenman Reply-To: dg@root.com Date: Tue, 30 Sep 1997 22:55:01 -0700 Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >>Waiting a couple of days, still nobody else. Antbody else getting >>this make failure with the 30current kernel? > >Perform a: > make -f ../../dev/aic7xxx/Makefile MAKESRCPATH=../../dev/aic7xxx clean > >in your kernel build directory and just to be safe, a: > > cd /usr/src/sys/dev/aic7xxx;make clean I tried a "make clean" in that directory when I had this problem, and it didn't remove the old files. I have to manually delete the old copy of the assembler. -DG David Greenman Core-team/Principal Architect, The FreeBSD Project From owner-freebsd-current Wed Oct 1 02:03:02 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id CAA00202 for current-outgoing; Wed, 1 Oct 1997 02:03:02 -0700 (PDT) Received: from murkwood.gaffaneys.com (dialup2.gaffaneys.com [208.155.161.52]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id CAA00193 for ; Wed, 1 Oct 1997 02:02:53 -0700 (PDT) Received: (from zach@localhost) by murkwood.gaffaneys.com (8.8.7/8.8.6) id EAA00964; Wed, 1 Oct 1997 04:01:19 -0500 (CDT) From: Zach Heilig Message-ID: <19971001040119.61326@gaffaneys.com> Date: Wed, 1 Oct 1997 04:01:19 -0500 To: Joerg Wunsch Cc: current@freebsd.org Subject: Re: Geometry weirdness with sysinstall/libdisk References: <19970930223542.44057@keltia.freenix.fr> <19971001072648.MU20136@uriah.heep.sax.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.84 In-Reply-To: <19971001072648.MU20136@uriah.heep.sax.de>; from J Wunsch on Wed, Oct 01, 1997 at 07:26:48AM +0200 Sender: owner-freebsd-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Wed, Oct 01, 1997 at 07:26:48AM +0200, J Wunsch wrote: > But again, these values are largely irrelevant. If you need to make a > disk DOS-compatible, it's never a bad idea to create the DOS partition > first. If you don't want it DOS-compatible, why caring for a > ficticuous geometry at all? Well, as long as the values are fairly sane [i.e. allow a bios boot], there is no real reason I can see to care. However, I had to figure out a way to hammer my disk into submission. Its geometry was 62496c 2h 33s. It would barely start reading in the kernel when it would say: xxxx>1024 BIOS limit, and hang. I tried using disklabel to give it the 257c 255h 63s geometry that the controller expects, but the controller still saw the original bad geometry. I gave the 257c 255h 63s parameters to fdisk, and it actually modified the geometry (to 341c 192h 63s, instead of what I entered). Now, the controller and fdisk report 341c 192h 63s, with disklabel reporting 2014c 255h 63s. At least they all got the number of sectors right (4124736). There are some physical problems with the drive, so I don't care to actually fix these other (non-?)problems. -- Zach Heilig From owner-freebsd-current Wed Oct 1 08:53:28 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id IAA21301 for current-outgoing; Wed, 1 Oct 1997 08:53:28 -0700 (PDT) Received: from chess.inetspace.com (chess.inetspace.com [206.50.163.14]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id IAA21292 for ; Wed, 1 Oct 1997 08:53:20 -0700 (PDT) Received: (from kgor@localhost) by chess.inetspace.com (8.8.5/8.7.3) id KAA28335; Wed, 1 Oct 1997 10:52:03 -0500 (CDT) Date: Wed, 1 Oct 1997 10:52:03 -0500 (CDT) Message-Id: <199710011552.KAA28335@chess.inetspace.com> From: "Kent S. Gordon" To: jdp@polstra.com CC: ache@nagual.pp.ru, asami@cs.berkeley.edu, current@FreeBSD.ORG In-reply-to: <199710010202.TAA06712@austin.polstra.com> (message from John Polstra on Tue, 30 Sep 1997 19:02:11 -0700) Subject: Re: CVSup-15.2 is now available Mime-Version: 1.0 (generated by tm-edit 7.106) Content-Type: text/plain; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk How much memory is required to compile CVSup? I am running a FreeBSD 2.2-STABLE system and I am getting the following message when trying to compile CVSup using the ports collection. I was running X at the time but 32MB of memory and 49MB of swap should be enough. new source -> compiling ../src/trestle/Trestle.m3 Trestle.m3: In function `TrestleImpl__UpdateChalk': Trestle.m3:930: virtual memory exhausted Fatal Error: program "/usr/local/ports/lang/modula-3-lib/work/installed/lib/m3/FreeBSD2/m3cgc1" failed, exit status = 8448 My system has 32MB and the uname -a is as follows FreeBSD chess.inetspace.com 2.2-STABLE FreeBSD 2.2-STABLE #0: Fri May 16 19:21:22 CDT 1997 kgor@chess.inetspace.com:/usr/src/sys/compile/CHESS i386 Here is the information from swapinfo on my swap space. Device 512-blocks Used Avail Capacity Type /dev/sd0b 49152 15760 33264 32% Interleaved /dev/sd1b 49152 16080 32944 33% Interleaved Total 98048 31840 66208 32% The following is my configuration as reported using dmesg. Copyright (c) 1992-1997 FreeBSD Inc. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 2.2-STABLE #0: Fri May 16 19:21:22 CDT 1997 kgor@chess.inetspace.com:/usr/src/sys/compile/CHESS CPU: i486DX (486-class CPU) real memory = 33554432 (32768K bytes) avail memory = 30670848 (29952K bytes) Probing for devices on the ISA bus: sc0 at 0x60-0x6f irq 1 on motherboard sc0: VGA color <16 virtual consoles, flags=0x0> ed0 at 0x300-0x31f irq 5 on isa ed0: address 00:00:e8:cb:ac:1a, type NE2000 (16 bit) sio0 at 0x3f8-0x3ff irq 4 on isa sio0: type 16550A sio1 at 0x2f8-0x2ff irq 3 on isa sio1: type 16550A lpt0 at 0x378-0x37f irq 7 on isa lpt0: Interrupt-driven port lp0: TCP/IP capable interface fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa fdc0: NEC 765 fd0: 1.44MB 3.5in fd1: 1.2MB 5.25in bt0: Bt445S/ 0-ISA(24bit) bus bt0: Your card cannot DMA above 16MB boundary. Bounce buffering enabled. bt0: reading board settings, dma=5, int=11 bt0: version 3.36, fast sync, parity, 32 mbxs, 32 ccbs bt0: targ 0 sync rate=10.00MB/s(100ns), offset=15 bt0: targ 1 sync rate=10.00MB/s(100ns), offset=15 bt0: Using Strict Round robin scheme bt0 at 0x330 irq 11 drq 5 on isa (bt0:0:0): "DEC DSP5200S T392" type 0 fixed SCSI 2 sd0(bt0:0:0): Direct-Access 1908MB (3907911 512 byte sectors) (bt0:1:0): "SEAGATE ST31200N 8648" type 0 fixed SCSI 2 sd1(bt0:1:0): Direct-Access 1006MB (2061108 512 byte sectors) npx0 on motherboard npx0: INT 16 interface changing root device to sd0a arp: 206.50.163.16 moved from 00:00:86:16:20:77 to 00:a0:24:d3:a3:89 arp: 206.50.163.16 moved from 00:a0:24:d3:a3:89 to 00:00:86:16:20:77 arp: 206.50.163.16 moved from 00:00:86:16:20:77 to 00:a0:24:d3:a3:89 bt0: Try to abort bt0: Try to abort bt0: Try to abort arp: 00:a0:c9:1f:c1:a2 is using my IP address 206.50.163.14! pid 21453 (netscape.bin), uid 101: exited on signal 10 ed0: promiscuous mode enabled arp: 206.50.163.13 moved from 00:a0:c9:1f:c1:a2 to 08:00:07:0f:8a:fc swap_pager: out of swap space swap_pager: out of swap space swap_pager: out of swap space Kent S. Gordon Senior Software Engineer iNetSpace Co. voice: (972)851-3494 fax:(972)702-0384 e-mail:kgor@inetspace.com From owner-freebsd-current Wed Oct 1 09:36:39 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id JAA23771 for current-outgoing; Wed, 1 Oct 1997 09:36:39 -0700 (PDT) Received: from earth.mat.net (root@earth.mat.net [206.246.122.2]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id JAA23766 for ; Wed, 1 Oct 1997 09:36:32 -0700 (PDT) Received: from Journey2.mat.net (journey2.mat.net [206.246.122.116]) by earth.mat.net (8.8.7/8.6.12) with SMTP id MAA26726; Wed, 1 Oct 1997 12:34:27 -0400 (EDT) Date: Wed, 1 Oct 1997 12:34:24 -0400 (EDT) From: Chuck Robey X-Sender: chuckr@Journey2.mat.net To: "Kent S. Gordon" cc: jdp@polstra.com, ache@nagual.pp.ru, asami@cs.berkeley.edu, current@FreeBSD.ORG Subject: Re: CVSup-15.2 is now available In-Reply-To: <199710011552.KAA28335@chess.inetspace.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, 1 Oct 1997, Kent S. Gordon wrote: > How much memory is required to compile CVSup? I am running a FreeBSD > 2.2-STABLE system and I am getting the following message when trying to > compile CVSup using the ports collection. I was running X at the time > but 32MB of memory and 49MB of swap should be enough. John's worked hard to cut it down, but it's not cvsup that's the hog, it's the Modula-3 compiler. I ran out of swap building it before John cut it down to size, on a machine with 64 megs of memory and 192 megs of swap! It's still a hog, tho. Why don't you use the Modula-3 package, and then compile the cvsup port, which is more reasonably sized? > > > new source -> compiling ../src/trestle/Trestle.m3 > Trestle.m3: In function `TrestleImpl__UpdateChalk': > Trestle.m3:930: virtual memory exhausted > > Fatal Error: program "/usr/local/ports/lang/modula-3-lib/work/installed/lib/m3/FreeBSD2/m3cgc1" failed, exit status = 8448 > > My system has 32MB and the uname -a is as follows > FreeBSD chess.inetspace.com 2.2-STABLE FreeBSD 2.2-STABLE #0: Fri May 16 19:21:22 CDT 1997 kgor@chess.inetspace.com:/usr/src/sys/compile/CHESS i386 > > Here is the information from swapinfo on my swap space. > > Device 512-blocks Used Avail Capacity Type > /dev/sd0b 49152 15760 33264 32% Interleaved > /dev/sd1b 49152 16080 32944 33% Interleaved > Total 98048 31840 66208 32% > > The following is my configuration as reported using dmesg. > > Copyright (c) 1992-1997 FreeBSD Inc. > Copyright (c) 1982, 1986, 1989, 1991, 1993 > The Regents of the University of California. All rights reserved. > > FreeBSD 2.2-STABLE #0: Fri May 16 19:21:22 CDT 1997 > kgor@chess.inetspace.com:/usr/src/sys/compile/CHESS > CPU: i486DX (486-class CPU) > real memory = 33554432 (32768K bytes) > avail memory = 30670848 (29952K bytes) > Probing for devices on the ISA bus: > sc0 at 0x60-0x6f irq 1 on motherboard > sc0: VGA color <16 virtual consoles, flags=0x0> > ed0 at 0x300-0x31f irq 5 on isa > ed0: address 00:00:e8:cb:ac:1a, type NE2000 (16 bit) > sio0 at 0x3f8-0x3ff irq 4 on isa > sio0: type 16550A > sio1 at 0x2f8-0x2ff irq 3 on isa > sio1: type 16550A > lpt0 at 0x378-0x37f irq 7 on isa > lpt0: Interrupt-driven port > lp0: TCP/IP capable interface > fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa > fdc0: NEC 765 > fd0: 1.44MB 3.5in > fd1: 1.2MB 5.25in > bt0: Bt445S/ 0-ISA(24bit) bus > bt0: Your card cannot DMA above 16MB boundary. Bounce buffering enabled. > bt0: reading board settings, dma=5, int=11 > bt0: version 3.36, fast sync, parity, 32 mbxs, 32 ccbs > bt0: targ 0 sync rate=10.00MB/s(100ns), offset=15 > bt0: targ 1 sync rate=10.00MB/s(100ns), offset=15 > bt0: Using Strict Round robin scheme > bt0 at 0x330 irq 11 drq 5 on isa > (bt0:0:0): "DEC DSP5200S T392" type 0 fixed SCSI 2 > sd0(bt0:0:0): Direct-Access 1908MB (3907911 512 byte sectors) > (bt0:1:0): "SEAGATE ST31200N 8648" type 0 fixed SCSI 2 > sd1(bt0:1:0): Direct-Access 1006MB (2061108 512 byte sectors) > npx0 on motherboard > npx0: INT 16 interface > changing root device to sd0a > arp: 206.50.163.16 moved from 00:00:86:16:20:77 to 00:a0:24:d3:a3:89 > arp: 206.50.163.16 moved from 00:a0:24:d3:a3:89 to 00:00:86:16:20:77 > arp: 206.50.163.16 moved from 00:00:86:16:20:77 to 00:a0:24:d3:a3:89 > bt0: Try to abort > bt0: Try to abort > bt0: Try to abort > arp: 00:a0:c9:1f:c1:a2 is using my IP address 206.50.163.14! > pid 21453 (netscape.bin), uid 101: exited on signal 10 > ed0: promiscuous mode enabled > arp: 206.50.163.13 moved from 00:a0:c9:1f:c1:a2 to 08:00:07:0f:8a:fc > swap_pager: out of swap space > swap_pager: out of swap space > swap_pager: out of swap space > > Kent S. Gordon > Senior Software Engineer > iNetSpace Co. > voice: (972)851-3494 fax:(972)702-0384 e-mail:kgor@inetspace.com > > ----------------------------+----------------------------------------------- Chuck Robey | Interests include any kind of voice or data chuckr@eng.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 Wed Oct 1 10:18:57 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id KAA25634 for current-outgoing; Wed, 1 Oct 1997 10:18:57 -0700 (PDT) Received: from oxmail4.ox.ac.uk (oxmail4.ox.ac.uk [163.1.2.33]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id KAA25627 for ; Wed, 1 Oct 1997 10:18:54 -0700 (PDT) Received: from njl2.materials.ox.ac.uk by oxmail4 with SMTP (PP); Wed, 1 Oct 1997 18:18:47 +0100 Received: by njl2.materials.ox.ac.uk (950413.SGI.8.6.12/940406.SGI) for current@FreeBSD.ORG id SAA08211; Wed, 1 Oct 1997 18:18:46 +0100 From: neil.long@materials.oxford.ac.uk (Neil J Long) Message-Id: <199710011718.SAA08211@njl2.materials.ox.ac.uk> Subject: Re: CVSup-15.2 is now available X-ELM-OSV: (Our standard violations) no-mime=1; no-hdr-encoding=1 To: current@freebsd.org Date: Wed, 1 Oct 1997 18:18:46 +0100 (BST) X-Mailer: ELM [version 2.4ME+ PL32 (25)] Content-Type: text Sender: owner-freebsd-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi I keep checking the URL but I only ever see 15.1. Where is 15.2 (binary pacakge that is)? Ta Neil From owner-freebsd-current Wed Oct 1 11:21:24 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id LAA28638 for current-outgoing; Wed, 1 Oct 1997 11:21:24 -0700 (PDT) Received: from cs.ru.ac.za (omega.ru.ac.za [146.231.24.56]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id LAA28624 for ; Wed, 1 Oct 1997 11:21:04 -0700 (PDT) Received: by cs.ru.ac.za (Smail3.1.29.1 #11) id m0xGTOs-001ZHPC; Wed, 1 Oct 97 20:21 GMT Message-Id: Subject: SCSI error causes crash To: current@FreeBSD.ORG Date: Wed, 1 Oct 1997 20:21:30 +0200 (GMT) From: Graham Smith From: csgs@omega.ru.ac.za (Graham Smith) Reply-to: csgs@omega.ru.ac.za X-Mailer: ELM [version 2.4ME+ PL15 (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 We're running FreeBSD current on a dual pentium 200. At least three times now the machine has crashed with the error message below. It isn't actually dead. The daemons that don't need the file system still live on for a while. This is the message faithfully copied off the console: ---- Error Message Begins ---- sd0: SCB 0x2 - timed out while idle, LASTPHASE == 0x1, SCSISIGI = 0x0 SEQADDR = 0x6 SCSISEQ = 0x12 SSTAT0 = 0x5 SSTAT1 = 0x9 sd0: Queuing an abort SCB sd0: reconnect SCB abort successfull sd0: SCB 0x2 - timed out in message in phase, SCSISIGI = 0xb6 SEQADDR = 0x42 SCSISEQ = 0x50 SSTAT0 = 0x7 SSTAT1 = 0x13 sd0: no longer in timeout ahc0: Issued Channel A Bus Reset. 2 SCBs aborted. sd0: SCB 0x2 - timed out in message out phase, SCSISIGI = 0xb6 SEQADDR = 0x9a SCSISEQ = 0x12 SSTAT0 = 0x7 SSTAT = 0x3 sd0: abort message in message buffer sd0: SCB1 - Abort Completed sd0: no longer in timeout sd0: SCB 0x1 - timed out while idle, LASTPHASE == 0x1, SCSISIGI = 0x0 SEQADDR = 0x145 SCSISEQ = 0x12 SSTAT0 = 0x4 SSTAT1 = 0x2 sd0: Queuing an Abort SCB ---- Error Message Ends ---- I'm not sure exactly which 'current' version we have, though it is probably less than a week older than the compile date. Here's the top of dmesg: ---------------------------------------------------------- Copyright (c) 1992-1997 FreeBSD Inc. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 3.0-CURRENT #0: Sun Sep 14 23:58:02 SAT 1997 grahams@rucus.ru.ac.za:/usr/src/sys/compile/RUCUS-SMP CPU: Pentium (586-class CPU) Origin = "GenuineIntel" Id = 0x52c Stepping=12 Features=0x3bf real memory = 67108864 (65536K bytes) avail memory = 62742528 (61272K bytes) FreeBSD/SMP: Multiprocessor motherboard cpu0 (BSP): apic id: 0, version: 0x00030010, at 0xfee00000 cpu1 (AP): apic id: 1, version: 0x00030010, at 0xfee00000 io0 (APIC): apic id: 2, version: 0x00170011, at 0xfec00000 Probing for devices on PCI bus 0: chip0: rev 0x03 on pci0.0.0 chip1: rev 0x01 on pci0.7.0 ide_pci0: rev 0x00 on pci0.7.1 ahc0: rev 0x00 int a irq 19 on pci0.12 .0 ahc0: Using left over BIOS settings ahc0: aic7880 Wide Channel, SCSI Id=7, 16 SCBs ahc0: waiting for scsi devices to settle scbus0 at ahc0 bus 0 sd0 at scbus0 target 0 lun 0 sd0: type 0 fixed SCSI 2 sd0: Direct-Access 1010MB (2069860 512 byte sectors) sd1 at scbus0 target 6 lun 0 sd1: type 0 fixed SCSI 2 sd1: Direct-Access 2063MB (4226725 512 byte sectors) Probing for devices on the ISA bus: sc0 at 0x60-0x6f irq 1 on motherboard sc0: VGA color <16 virtual consoles, flags=0x0> ed0 at 0x300-0x31f irq 3 on isa ed0: address 00:00:e8:1c:7b:57, type NE2000 (16 bit) sio0 at 0x3f8-0x3ff irq 4 on isa sio0: type 16550A lpt0 at 0x378-0x37f irq 7 on isa lpt0: Interrupt-driven port lp0: TCP/IP capable interface lpt1 not found psm0: disabled, not probed. fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa fdc0: NEC 72065B wdc0 at 0x1f0-0x1f7 irq 14 on isa wdc0: unit 0 (wd0): wd0: 3020MB (6185088 sectors), 6136 cyls, 16 heads, 63 S/T, 512 B/S wdc0: unit 1 (wd1): wd1: 249MB (510510 sectors), 1001 cyls, 15 heads, 34 S/T, 512 B/S wdc1 not found at 0x170 aha0 not found at 0x330 mcd0 not probed due to I/O address conflict with ed0 at 0x300 matcdc0 not found at 0x230 scd0 not found at 0x230 npx0 on motherboard npx0: INT 16 interface apm0: disabled, not probed. APIC_IO: routing 8254 via 8259 on pin 0 SMP: AP CPU #1 Launched! WARNING: / was not properly dismounted. sd1: raw partition size != slice size sd1: start 0, end 4226724, size 4226725 sd1c: start 0, end 4222888, size 4222889 sd1: raw partition size != slice size sd1: start 0, end 4226724, size 4226725 sd1c: start 0, end 4222888, size 4222889 ------------------------------------------------------------------- bash$ df -k Filesystem 1K-blocks Used Avail Capacity Mounted on /dev/sd0a 31775 25630 3603 88% / /dev/sd0s1f 635791 576415 8513 99% /usr /dev/sd0s1e 197951 142433 39682 78% /var /dev/sd1e 1699282 1158432 404908 74% /www /dev/wd0a 2900302 2518820 149458 94% /home procfs 4 4 0 100% /proc kernfs 1 1 0 100% /kern ------------- From owner-freebsd-current Wed Oct 1 11:28:43 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id LAA29084 for current-outgoing; Wed, 1 Oct 1997 11:28:43 -0700 (PDT) Received: from cs.ru.ac.za (omega.ru.ac.za [146.231.24.56]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id LAA29076 for ; Wed, 1 Oct 1997 11:28:33 -0700 (PDT) Received: by cs.ru.ac.za (Smail3.1.29.1 #11) id m0xGTWF-001ZHPC; Wed, 1 Oct 97 20:29 GMT Message-Id: Subject: fdesc file system causes instant reboot To: current@FreeBSD.ORG Date: Wed, 1 Oct 1997 20:29:07 +0200 (GMT) From: Graham Smith From: csgs@omega.ru.ac.za (Graham Smith) Reply-to: csgs@omega.ru.ac.za X-Mailer: ELM [version 2.4ME+ PL15 (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 We are running freeBSD current on a dual pentium 200. If we mount fdesc with an /etc/fstab like so: fdesc /dev fdesc rw,union and then do something like: bash$ cat /dev/stdout | somenonexistantfile the machine reboots instantly. this is the top of dmesg: Copyright (c) 1992-1997 FreeBSD Inc. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 3.0-CURRENT #0: Sun Sep 14 23:58:02 SAT 1997 grahams@rucus.ru.ac.za:/usr/src/sys/compile/RUCUS-SMP CPU: Pentium (586-class CPU) Origin = "GenuineIntel" Id = 0x52c Stepping=12 Features=0x3bf real memory = 67108864 (65536K bytes) avail memory = 62742528 (61272K bytes) FreeBSD/SMP: Multiprocessor motherboard cpu0 (BSP): apic id: 0, version: 0x00030010, at 0xfee00000 cpu1 (AP): apic id: 1, version: 0x00030010, at 0xfee00000 io0 (APIC): apic id: 2, version: 0x00170011, at 0xfec00000 Probing for devices on PCI bus 0: chip0: rev 0x03 on pci0.0.0 chip1: rev 0x01 on pci0.7.0 ide_pci0: rev 0x00 on pci0.7.1 ahc0: rev 0x00 int a irq 19 on pci0.12 .0 ahc0: Using left over BIOS settings ahc0: aic7880 Wide Channel, SCSI Id=7, 16 SCBs ahc0: waiting for scsi devices to settle scbus0 at ahc0 bus 0 sd0 at scbus0 target 0 lun 0 sd0: type 0 fixed SCSI 2 sd0: Direct-Access 1010MB (2069860 512 byte sectors) sd1 at scbus0 target 6 lun 0 sd1: type 0 fixed SCSI 2 sd1: Direct-Access 2063MB (4226725 512 byte sectors) Probing for devices on the ISA bus: sc0 at 0x60-0x6f irq 1 on motherboard sc0: VGA color <16 virtual consoles, flags=0x0> ed0 at 0x300-0x31f irq 3 on isa ed0: address 00:00:e8:1c:7b:57, type NE2000 (16 bit) sio0 at 0x3f8-0x3ff irq 4 on isa sio0: type 16550A lpt0 at 0x378-0x37f irq 7 on isa lpt0: Interrupt-driven port lp0: TCP/IP capable interface lpt1 not found psm0: disabled, not probed. fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa fdc0: NEC 72065B wdc0 at 0x1f0-0x1f7 irq 14 on isa wdc0: unit 0 (wd0): wd0: 3020MB (6185088 sectors), 6136 cyls, 16 heads, 63 S/T, 512 B/S wdc0: unit 1 (wd1): wd1: 249MB (510510 sectors), 1001 cyls, 15 heads, 34 S/T, 512 B/S wdc1 not found at 0x170 aha0 not found at 0x330 mcd0 not probed due to I/O address conflict with ed0 at 0x300 matcdc0 not found at 0x230 scd0 not found at 0x230 npx0 on motherboard npx0: INT 16 interface apm0: disabled, not probed. APIC_IO: routing 8254 via 8259 on pin 0 SMP: AP CPU #1 Launched! From owner-freebsd-current Wed Oct 1 12:39:28 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id MAA03036 for current-outgoing; Wed, 1 Oct 1997 12:39:28 -0700 (PDT) Received: from shell.monmouth.com (root@shell.monmouth.com [205.164.220.9]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id MAA03025 for ; Wed, 1 Oct 1997 12:39:14 -0700 (PDT) Received: from i4got.lakewood.com (fh-ppp22.monmouth.com [205.164.221.54]) by shell.monmouth.com (8.8.5/8.7.3) with ESMTP id PAA00319; Wed, 1 Oct 1997 15:34:00 -0400 (EDT) Received: (from pechter@localhost) by i4got.lakewood.com id PAA01465 (8.8.5/IDA-1.6); Wed, 1 Oct 1997 15:37:33 -0400 (EDT) From: Bill Pechter Message-ID: <199710011937.PAA01465@i4got.lakewood.com> Subject: Re: SCSI error causes crash In-Reply-To: from Graham Smith at "Oct 1, 97 08:21:30 pm" To: csgs@omega.ru.ac.za Date: Wed, 1 Oct 1997 15:37:32 -0400 (EDT) Cc: current@freebsd.org Reply-to: pechter@lakewood.com X-Phone-Number: 908-389-3592 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 > > We're running FreeBSD current on a dual pentium 200. At > least three times now the machine has crashed with the error > message below. It isn't actually dead. The daemons that > don't need the file system still live on for a while. This > is the message faithfully copied off the console: I see the same kind of errors on my DORS (and the drive light is on permanently when it happens...) Running 2.2-STABLE from August. Bill From owner-freebsd-current Wed Oct 1 13:57:12 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id NAA07449 for current-outgoing; Wed, 1 Oct 1997 13:57:12 -0700 (PDT) Received: from hauki.clinet.fi (root@hauki.clinet.fi [194.100.0.1]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id NAA07437 for ; Wed, 1 Oct 1997 13:56:58 -0700 (PDT) Received: from katiska.clinet.fi (root@katiska.clinet.fi [194.100.0.4]) by hauki.clinet.fi (8.8.6/8.8.6) with ESMTP id WAA07082; Wed, 1 Oct 1997 22:56:33 +0200 (EET) Received: (hsu@localhost) by katiska.clinet.fi (8.8.7/8.6.4) id XAA05552; Wed, 1 Oct 1997 23:56:33 +0300 (EEST) Date: Wed, 1 Oct 1997 23:56:33 +0300 (EEST) Message-Id: <199710012056.XAA05552@katiska.clinet.fi> From: Heikki Suonsivu To: Karl Denninger Cc: freebsd-current@freebsd.org In-reply-to: Karl Denninger's message of 27 Sep 1997 23:37:48 +0300 Subject: Re: WARNING! Builds from the last few days have BROKEN NFS Organization: Clinet Ltd, Espoo, Finland References: <19970927145131.64000@Mars.Mcs.Net> <13496.875390123@critter.freebsd.dk> <19970927150755.39452@Mars.Mcs.Net> Sender: owner-freebsd-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Similar lockups happen under 2.2-STABLE also. I do not know exactly if the reason is the same, it just happens to match your symptoms. Other symptoms are panics which are repeatable by doing specific pattern of command (this evening it was generating a zip file larger than 10M which reproduceably generated a panic. See my last PR for traces). In article <19970927150755.39452@Mars.Mcs.Net> Karl Denninger writes: Ok -- tomorrow evening I will check out another copy of the current sources, and give this another shot with the parameters you're referring to. The problem shows up only during fairly heavy I/O load -- my initial tests didn't show it, but putting the code on a reasonably-busy web server does, and its easily reproduced in about 20-30 minutes. Same with the shell systems here. The symptom is that a single disk I/O request will hang in a "D" state. Further attempts to access that same object then also hang, but others, even to the same disk pack, do NOT. That is, a "df" still works, but a "cat " locks up. If "object" is a directory then a "ls" will freeze. If its a file then you have to reference the specific file to see the behavior. Over a fairly short period of time once this starts you're in *big* trouble; you'll end up with thousands of processes hung in a disk wait for a specific file, and eventually run out of either process slots or page space (most people retry failed accesses, which makes the problem worse). Per-user process limits (which I have turned off on these machines) would stop some of the damage, but not all. Exactly the same symptoms. I was trying to resolve cache inconsistency problems with NFS when I ran headfirst into this. There is a problem with V3 mounts (the default now) where you can "mv" a file on one client, and another client never sees the change. This is particularly distressing when you "mv" the access_log file from a web server (from another amchine), kick the server to re-create the access_log file, and then find that it never shows up on the other syste (or does with zero length, but no data in it -- ever). Maybe far-fetched, but one of the directories which are locking up on us are user's www access log directories. I do not know if this is related. If you look on the other system, a "ls" doesn't show the errant file. But a "cat" does -- the data is still there. Needless to say this is pretty troublesome, and leads to lots of head-scratching. -- Karl Denninger (karl@MCS.Net)| MCSNet - Serving Chicagoland and Wisconsin http://www.mcs.net/~karl | T1's from $600 monthly to FULL DS-3 Service | NEW! K56Flex modem support is now available Voice: [+1 312 803-MCS1 x219]| 56kbps DIGITAL ISDN DOV on analog lines! Fax: [+1 312 803-4929] | 2 FULL DS-3 Internet links; 400Mbps B/W Internal -- Heikki Suonsivu, T{ysikuu 10 C 83/02210 Espoo/FINLAND, hsu@clinet.fi mobile +358-40-5519679 work +358-9-43542270 fax -4555276 From owner-freebsd-current Wed Oct 1 14:37:46 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id OAA10618 for current-outgoing; Wed, 1 Oct 1997 14:37:46 -0700 (PDT) Received: from roguetrader.com (brandon@cold.org [206.81.134.103]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id OAA10603 for ; Wed, 1 Oct 1997 14:37:38 -0700 (PDT) Received: from localhost (brandon@localhost) by roguetrader.com (8.8.5/8.8.5) with SMTP id PAA28487 for ; Wed, 1 Oct 1997 15:39:36 -0600 (MDT) Date: Wed, 1 Oct 1997 15:39:36 -0600 (MDT) From: Brandon Gillespie To: freebsd-current@freeBSD.org Subject: new command: doconfig Message-ID: MIME-Version: 1.0 Content-Type: MULTIPART/MIXED; BOUNDARY="0-1583598220-875741976=:28417" Sender: owner-freebsd-current@freeBSD.org X-Loop: FreeBSD.org Precedence: bulk This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. Send mail to mime@docserver.cac.washington.edu for more info. --0-1583598220-875741976=:28417 Content-Type: TEXT/PLAIN; charset=US-ASCII I would like to add this as a new command to FreeBSD. I mentioned it a few months back when I originally wrote it, and received positive responses about it. This command derives from a similar command in Digital Unix. 'doconfig' is basically a simplifier for kernel compiling, by wrapping 'vi /sys/i386/conf/MINE; config; cd ../../compile/MINE; make depend; make; make install; reboot' or whatnot into a simpler, nicer interface.. For instance, I just recompiled my kernel with (the GLACIER config file already existed): ---------------------------------------------------------------- % doconfig -r -c GLACIER Remove existing kernel log /sys/i386/conf/kernelbuild.log? [yes] y Removing old directory ../../compile/GLACIER: Done. Kernel build directory is ../../compile/GLACIER Building Dependancies.. 1-Oct-1997 15:20.49 Building Dependancies.. 1-Oct-1997 15:21.57 Building Kernel.. 1-Oct-1997 15:21.57 Building Kernel.. 1-Oct-1997 15:32.38 Installing Kernel.. 1-Oct-1997 15:32.38 A backup kernel already exists, rename to /kernel.29-Jul-1997? [yes] yes *** *** Ready to reboot. If the system is unable to bootup, you can type: *** *** /kernel.old *** *** At the 'Boot:' prompt, to boot from the old kernel. *** [Press ENTER to Reboot] ---------------------------------------------------------------- This program is a PERL program, and has a few places where I would like to expand it in the future (for instance, I've heard rumors about a auto-kernel-config-file-generation program, so for now I just run a few seds and whatnot on the GENERIC template, when generating a new config file--this could instead hook into the auto-generation one). I would like to add: /usr/sbin/doconfig /usr/share/man/man8/doconfig.8.gz Comments, questions? The manpage is attached. -Brandon Gillespie --0-1583598220-875741976=:28417 Content-Type: TEXT/PLAIN; charset=US-ASCII; name="doconfig.man" Content-Transfer-Encoding: BASE64 Content-ID: Content-Description: DQpET0NPTkZJRyg4KSAgICAgICAgICAgICBGcmVlQlNEIFN5c3RlbSBNYW5h Z2VyJ3MgTWFudWFsICAgICAgICAgICAgRE9DT05GSUcoOCkNCg0KTkFNRQ0K ICAgICBkb2NvbmZpZyAtIGludGVyYWN0aXZlbHkgY29uZmlndXJlIGFuZCBi dWlsZCBrZXJuZWwNCg0KU1lOT1BTSVMNCiAgICAgZG9jb25maWcgWy1jIGZp bGVdIFstZSBbZWRpdG9yXV0gWy1haXJdIFstZ3BuXQ0KDQpERVNDUklQVElP Tg0KICAgICBEb2NvbmZpZyBpcyB1c2VkIHRvIGJ1aWxkIGFuZCBpbnN0YWxs IGEgbmV3IGtlcm5lbCBmb3IgdGhlIHN5c3RlbS4gIEl0DQogICAgIGludGVy YWN0aXZlbHkgZ2VuZXJhdGVzIHRoZSBrZXJuZWwgY29uZmlnIGZpbGVzICh1 c2luZyBjb25maWcoOCkpLiAgY29tLQ0KICAgICBwaWxlcyB0aGUga2VybmVs IGFuZCBvcHRpb25hbHkgaW5zdGFsbHMgYW5kIHJlYm9vdHMgdGhlIHN5c3Rl bSB3aGVuIGZpbi0NCiAgICAgaXNoZWQuDQoNCiAgICAgQXZhaWxhYmxlIG9w dGlvbnM6DQoNCiAgICAgLWMgZmlsZSAgICAgIFVzZSBmaWxlIGFzIHRoZSBj b25maWd1cmF0aW9uIGZpbGUuIElmIHRoZSBmdWxsIHBhdGggaXMgZ2l2LQ0K ICAgICAgICAgICAgICAgICAgZW4gaW4gZmlsZSwgZG9jb25maWcgd2lsbCBj b3B5IGl0IHRvIC9zeXMvaTM4Ni9jb25mLiBPdGhlci0NCiAgICAgICAgICAg ICAgICAgIHdpc2UsIGl0IHdpbGwgYXNzdW1lIHRoZSBmaWxlIGV4aXN0cyBp biAvc3lzL2kzODYvY29uZi4gSWYNCiAgICAgICAgICAgICAgICAgIHRoaXMg b3B0aW9uIGlzIHVzZWQsIGRvY29uZmlnIHdpbGwgbm90IHJ1biBhbiBlZGl0 b3Igb24gdGhlDQogICAgICAgICAgICAgICAgICBjb25maWcgZmlsZSwgdW5s ZXNzIHRoZSAtZSBvcHRpb24gaXMgYWxzbyBzcGVjaWZpZWQuDQoNCiAgICAg LWUgW2VkaXRvcl0gIEVkaXQgdGhlIGNvbmZpZyBmaWxlICh0aGlzIGlzIHRo ZSBkZWZ1YWx0IGFjdGlvbiwgdW5sZXNzIC1jDQogICAgICAgICAgICAgICAg ICB3YXMgc3BlY2lmaWVkKS4gIElmIGVkaXRvciBpcyBzcGVjaWZpZWQgdXNl IGl0IGFzIHRoZSBlZGl0b3INCiAgICAgICAgICAgICAgICAgIGluc3RlYWQg KGZ1bGwgcGF0aCBtYXkgYmUgcmVxdWlyZWQpLiAgSWYgZWRpdG9yIGlzIG5v dCBzcGVjLQ0KICAgICAgICAgICAgICAgICAgaWZpZWQgZG9jb25maWcgd2ls bCB1c2UgdGhlIEVESVRPUiBlbnZpcm9ubWVudCB2YXJpYWJsZSwgb3INCiAg ICAgICAgICAgICAgICAgIC91c3IvYmluL3ZpLg0KDQogICAgIC1hICAgICAg ICAgICBJZ25vcmVkIGJ5IGRvY29uZmlnIGFuZCBwYXNzZWQgdG8gYXV0b2tl cm5jb25mIGlmIHRoZSBrZXJuZWwNCiAgICAgICAgICAgICAgICAgIGNvbmZp Z3VyYXRpb24gZmlsZSBpcyBhdXRvbWF0aWNhbGx5IGdlbmVyYXRlZC4gIElm IHNwZWNpLQ0KICAgICAgICAgICAgICAgICAgZmllZCwgaXQgd2lsbCBkaXJl Y3QgYXV0b2tlcm5jb25mIHRvIGp1c3QgYXV0b21hdGljYWxseSBzZS0NCiAg ICAgICAgICAgICAgICAgIGxlY3QgZGVmYXVsdHMsIHJhdGhlciB0aGFuIGlu dGVyYWN0aXZlbHkgZGVjaWRpbmcgYWxsIHNldC0NCiAgICAgICAgICAgICAg ICAgIHRpbmdzIGZvciB0aGUgY29uZmlndXJhdGlvbiBmaWxlLg0KDQogICAg IC1pICAgICAgICAgICBJbnN0YWxsIHRoZSBrZXJuZWwgaW50byB0aGUgcm9v dCBkaXJlY3RvcnkgYWZ0ZXIgYSBzdWNjZXNzLQ0KICAgICAgICAgICAgICAg ICAgZnVsIGNvbXBpbGUuICBJZiAva2VybmVsIGV4aXN0cywgbW92ZSBpdCB0 byAva2VybmVsLkRBVEUuDQoNCiAgICAgLXIgICAgICAgICAgIFJlYm9vdCBh ZnRlciBzdWNjZXNzZnVsbHkgYnVpbGRpbmcgYW5kIGluc3RhbGxpbmcuICBU aGlzIG9wLQ0KICAgICAgICAgICAgICAgICAgdGlvbiBhbHNvIGluc3RhbGxz IHRoZSBrZXJuZWwgKGFzIC1pIG5vcm1hbGx5IHdvdWxkKS0tdXNlcg0KICAg ICAgICAgICAgICAgICAgd2lsbCBiZSBwcm9tcHRlZCBiZWZvcmUgdGhlIHJl Ym9vdCBvY2N1cnMuDQoNCiAgICAgLWcgLXAgLW4gICAgIElnbm9yZWQgYnkg ZG9jb25maWcgYW5kIHBhc3NlZCB0byBjb25maWcuDQoNCiAgICAgRG9jb25m aWcgY2FuIGJlIHJ1biBmcm9tIGFueSBsb2NhdGlvbiBvbiB0aGUgZmlsZXN5 c3RlbSwgYXMgaXQgd2lsbCBpbi0NCiAgICAgdGVybmFsbHkgbWFuYWdlIGZp bGUgbG9jYXRpb25zIGFuZCB3b3JraW5nIGRpcmVjdG9yaWVzLiAgRG9jb25m aWcgd2lsbA0KICAgICBwcm9tcHQgdGhlIHVzZXIgZm9yIHRoZSBrZXJuZWwg YnVpbGQgbmFtZSB3aGljaCBpcyBzZW50IHRvIGNvbmZpZywgd2l0aA0KICAg ICBpdCBkZWZhdWx0aW5nIHRvIHRoZSBjdXJyZW50IGhvc3RuYW1lLg0KDQog ICAgIElmIHRoZSBrZXJuZWwgY29uZmlndXJhdGlvbiBmaWxlIGlzIG5vdCBz cGVjaWZpZWQgd2l0aCAtYyB0aGVuIHRoZSBwcm8tDQogICAgIGdyYW0gYXV0 b2tlcm5jb25mIGlzIGV4ZWN1dGVkIHRvIGNyZWF0ZSBpdC4NCg0KRklMRVMN CiAgICAgL3N5cy9pMzg2L2NvbmYva2VybmVsYnVpbGQubG9nICBMb2dmaWxl IG9mIGtlcm5lbCBjb21waWxlLg0KICAgICAvc3lzL2kzODYvY29uZi9GSUxF ICAgICAgICAgICAgIENvbmZpZyBmaWxlIGdlbmVyYXRlZCBmb3IgY29uZmln Lg0KICAgICAva2VybmVsICAgICAgICAgICAgICAgICAgICAgICAgIFN5c3Rl bSBLZXJuZWwuDQogICAgIC9rZXJuZWwuREFURSAgICAgICAgICAgICAgICAg ICAgQmFja3VwIG9mIG9sZCBzeXN0ZW0gS2VybmVsLg0KDQpTRUUgQUxTTw0K ICAgICBjb25maWcoOCksICBhdXRva2VybmNvbmYoOCkNCg0KSElTVE9SWQ0K ICAgICBDcmVhdGVkIGZvciBGcmVlQlNEIDIuMiwgYmFzZWQgb2ZmIHRoZSBE aWdpdGFsIFVuaXggZG9jb25maWcuDQoNCiBGcmVlQlNEICAgICAgICAgICAg ICAgICAgICAgICAgQXByaWwgMTYsIDE5OTcgICAgICAgICAgICAgICAgICAg ICAgICAgICAgICAgMQ0K --0-1583598220-875741976=:28417-- From owner-freebsd-current Wed Oct 1 15:14:51 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id PAA12643 for current-outgoing; Wed, 1 Oct 1997 15:14:51 -0700 (PDT) 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 PAA12633 for ; Wed, 1 Oct 1997 15:14:46 -0700 (PDT) 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 PAA04452; Wed, 1 Oct 1997 15:14:44 -0700 (PDT) To: Brandon Gillespie cc: freebsd-current@FreeBSD.ORG Subject: Re: new command: doconfig In-reply-to: Your message of "Wed, 01 Oct 1997 15:39:36 MDT." Date: Wed, 01 Oct 1997 15:14:44 -0700 Message-ID: <4448.875744084@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > I would like to add this as a new command to FreeBSD. I mentioned it a > few months back when I originally wrote it, and received positive > responses about it. This command derives from a similar command in > Digital Unix. 'doconfig' is basically a simplifier for kernel compiling, > by wrapping 'vi /sys/i386/conf/MINE; config; cd ../../compile/MINE; make > depend; make; make install; reboot' or whatnot into a simpler, nicer > interface.. For instance, I just recompiled my kernel with (the GLACIER > config file already existed): My only problem with this is that it didn't go far enough. Yes, it front-ends a few steps, but only a few of the ones you'd expect in a configuration front-end tool. It should also build the configuration file through a complete interactive Q&A process if you don't have one. Jordan From owner-freebsd-current Wed Oct 1 15:19:42 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id PAA12877 for current-outgoing; Wed, 1 Oct 1997 15:19:42 -0700 (PDT) Received: from roguetrader.com (brandon@cold.org [206.81.134.103]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id PAA12866 for ; Wed, 1 Oct 1997 15:19:37 -0700 (PDT) Received: from localhost (brandon@localhost) by roguetrader.com (8.8.5/8.8.5) with SMTP id QAA28670; Wed, 1 Oct 1997 16:21:46 -0600 (MDT) Date: Wed, 1 Oct 1997 16:21:45 -0600 (MDT) From: Brandon Gillespie To: "Jordan K. Hubbard" cc: freebsd-current@FreeBSD.ORG Subject: Re: new command: doconfig In-Reply-To: <4448.875744084@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 On Wed, 1 Oct 1997, Jordan K. Hubbard wrote: > > I would like to add this as a new command to FreeBSD. I mentioned it a > > few months back when I originally wrote it, and received positive > > responses about it. This command derives from a similar command in > > Digital Unix. 'doconfig' is basically a simplifier for kernel compiling, > > by wrapping 'vi /sys/i386/conf/MINE; config; cd ../../compile/MINE; make > > depend; make; make install; reboot' or whatnot into a simpler, nicer > > interface.. For instance, I just recompiled my kernel with (the GLACIER > > config file already existed): > > My only problem with this is that it didn't go far enough. Yes, it > front-ends a few steps, but only a few of the ones you'd expect in a > configuration front-end tool. > > It should also build the configuration file through a complete > interactive Q&A process if you don't have one. I agree :) The only reason I didn't do it, was because I've never been able to find out if anybody is working on this already... If not, then perhaps we can make one. I have a few ideas on various modular ways this could be implemented. As it is right now, 'doconfig' actually runs an external program to 'auto-generate' the initial file. The external program does nothing other than sed the GENERIC kernel, but only because of the above reasons. So I guess the question is, what is there right now for auto generating a kernel config file? -Brandon From owner-freebsd-current Wed Oct 1 15:27:19 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id PAA13303 for current-outgoing; Wed, 1 Oct 1997 15:27:19 -0700 (PDT) Received: from earth.mat.net (root@earth.mat.net [206.246.122.2]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id PAA13296 for ; Wed, 1 Oct 1997 15:27:14 -0700 (PDT) Received: from Journey2.mat.net (journey2.mat.net [206.246.122.116]) by earth.mat.net (8.8.7/8.6.12) with SMTP id SAA08229; Wed, 1 Oct 1997 18:26:59 -0400 (EDT) Date: Wed, 1 Oct 1997 18:26:54 -0400 (EDT) From: Chuck Robey X-Sender: chuckr@Journey2.mat.net To: Brandon Gillespie cc: freebsd-current@FreeBSD.ORG Subject: Re: new command: doconfig 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 Wed, 1 Oct 1997, Brandon Gillespie wrote: > I would like to add this as a new command to FreeBSD. I mentioned it a > few months back when I originally wrote it, and received positive > responses about it. This command derives from a similar command in > Digital Unix. 'doconfig' is basically a simplifier for kernel compiling, > by wrapping 'vi /sys/i386/conf/MINE; config; cd ../../compile/MINE; make > depend; make; make install; reboot' or whatnot into a simpler, nicer > interface.. For instance, I just recompiled my kernel with (the GLACIER > config file already existed): > > ---------------------------------------------------------------- > % doconfig -r -c GLACIER > Remove existing kernel log /sys/i386/conf/kernelbuild.log? [yes] y > Removing old directory ../../compile/GLACIER: Done. > Kernel build directory is ../../compile/GLACIER > Building Dependancies.. 1-Oct-1997 15:20.49 > Building Dependancies.. 1-Oct-1997 15:21.57 > Building Kernel.. 1-Oct-1997 15:21.57 > Building Kernel.. 1-Oct-1997 15:32.38 > Installing Kernel.. 1-Oct-1997 15:32.38 > A backup kernel already exists, rename to /kernel.29-Jul-1997? [yes] yes > *** > *** Ready to reboot. If the system is unable to bootup, you can type: > *** > *** /kernel.old > *** > *** At the 'Boot:' prompt, to boot from the old kernel. > *** > > [Press ENTER to Reboot] This is the part I don't like. It's simply not necessary to do the reboot as part of the doconfig, and far more likely to cause problems than to solve them. Another thing ... how about doing a datestamp check on the lkm's and failing if they're more than 24 hours out of date? I mean, failing the install part (the build could proceed). > ---------------------------------------------------------------- > > This program is a PERL program, and has a few places where I would like to > expand it in the future (for instance, I've heard rumors about a > auto-kernel-config-file-generation program, so for now I just run a few > seds and whatnot on the GENERIC template, when generating a new config > file--this could instead hook into the auto-generation one). > > I would like to add: > > /usr/sbin/doconfig > /usr/share/man/man8/doconfig.8.gz > > Comments, questions? The manpage is attached. > > -Brandon Gillespie > ----------------------------+----------------------------------------------- Chuck Robey | Interests include any kind of voice or data chuckr@eng.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 Wed Oct 1 15:36:26 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id PAA13925 for current-outgoing; Wed, 1 Oct 1997 15:36:26 -0700 (PDT) Received: from roguetrader.com (brandon@cold.org [206.81.134.103]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id PAA13918 for ; Wed, 1 Oct 1997 15:36:23 -0700 (PDT) Received: from localhost (brandon@localhost) by roguetrader.com (8.8.5/8.8.5) with SMTP id QAA28717; Wed, 1 Oct 1997 16:37:12 -0600 (MDT) Date: Wed, 1 Oct 1997 16:37:12 -0600 (MDT) From: Brandon Gillespie To: Chuck Robey cc: freebsd-current@FreeBSD.ORG Subject: Re: new command: doconfig 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 Wed, 1 Oct 1997, Chuck Robey wrote: > > [Press ENTER to Reboot] > > This is the part I don't like. It's simply not necessary to do the reboot > as part of the doconfig, and far more likely to cause problems than to > solve them. It is an optional (not default) option. By default, it doesn't even install the kernel. You can either specify -i (to install, but not reboot) or -r (to install and reboot). > Another thing ... how about doing a datestamp check on the lkm's and > failing if they're more than 24 hours out of date? I mean, failing the > install part (the build could proceed). Could be done.. is there a better way to determine 'good' status of an lkm tho? -Brandon From owner-freebsd-current Wed Oct 1 16:33:58 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id QAA16301 for current-outgoing; Wed, 1 Oct 1997 16:33:58 -0700 (PDT) Received: from mexico.brainstorm.eu.org (root@mexico.brainstorm.fr [193.56.58.253]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id QAA16292 for ; Wed, 1 Oct 1997 16:33:53 -0700 (PDT) Received: from brasil.brainstorm.eu.org (brasil.brainstorm.fr [193.56.58.33]) by mexico.brainstorm.eu.org (8.8.4/8.8.4) with ESMTP id BAA07598 for ; Thu, 2 Oct 1997 01:33:52 +0200 Received: (from uucp@localhost) by brasil.brainstorm.eu.org (8.8.6/brasil-1.2) with UUCP id BAA12265 for current@FreeBSD.ORG; Thu, 2 Oct 1997 01:33:20 +0200 Received: (from roberto@localhost) by keltia.freenix.fr (8.8.7/keltia-2.10/nospam) id BAA01077; Thu, 2 Oct 1997 01:28:05 +0200 (CEST) Message-ID: <19971002012804.28680@keltia.freenix.fr> Date: Thu, 2 Oct 1997 01:28:04 +0200 From: Ollivier Robert To: current@FreeBSD.ORG Subject: Re: Geometry weirdness with sysinstall/libdisk References: <19970930223542.44057@keltia.freenix.fr> <19971001072648.MU20136@uriah.heep.sax.de> <19971001040119.61326@gaffaneys.com> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Mailer: Mutt 0.84 In-Reply-To: <19971001072648.MU20136@uriah.heep.sax.de>; from Joerg Wunsch on Wed, Oct 01, 1997 at 04:01:19AM -0500 X-Operating-System: FreeBSD 3.0-CURRENT Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk According to Jörg: > > Debug_Disk(sd2) flags=0 bios_geom=13045/54/6 = 4226580 > > Certainly no slices present yet. As you can see in disklabel output, it certainly _has_ slices, it used to be my boot drive !!! # /dev/rsd2c: type: SCSI disk: IBM32160 ... 8 partitions: # size offset fstype [fsize bsize bps/cpg] a: 40960 0 4.2BSD 1024 8192 16 # (Cyl. 0 - 19) b: 131072 40960 swap # (Cyl. 20 - 83) c: 4226725 0 unused 0 0 # (Cyl. 0 - 2063*) d: 204800 172032 4.2BSD 1024 8192 16 # (Cyl. 84 - 183) e: 716800 376832 4.2BSD 1024 8192 16 # (Cyl. 184 - 533) f: 409600 1093632 4.2BSD 1024 8192 16 # (Cyl. 534 - 733) g: 1024000 1503232 4.2BSD 1024 8192 16 # (Cyl. 734 - 1233) h: 1699493 2527232 4.2BSD 1024 8192 16 # (Cyl. 1234 - 2063*) > They are not `right' in the sense of FreeBSD either, since they are > useless for the BIOS. 2063 > 1024. It has never prevented it to boot into FreeBSD (no boot manager on that drive). > From the drive itself, i'd say. Well, no, this drive has 8205 > cylinders and 6 heads: It is a 32160 so it is 6703 cyl. x 5 heads so I still don't see where does the 13045 come from... > But again, these values are largely irrelevant. If you need to make a > disk DOS-compatible, it's never a bad idea to create the DOS partition > first. If you don't want it DOS-compatible, why caring for a > ficticuous geometry at all? What bother me a lot is why libdisk/sysinstall don't see the slices when disklabel can ! I can mount every slice on that drive without problem so the kernel has the right label but why disklabel is the only program to display it correctly ? It is inconsistent to say the least. -- Ollivier ROBERT -=- FreeBSD: There are no limits -=- roberto@keltia.freenix.fr FreeBSD keltia.freenix.fr 3.0-CURRENT #35: Sun Sep 21 19:28:07 CEST 1997 From owner-freebsd-current Wed Oct 1 16:52:44 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id QAA17178 for current-outgoing; Wed, 1 Oct 1997 16:52:44 -0700 (PDT) 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 QAA17170 for ; Wed, 1 Oct 1997 16:52:41 -0700 (PDT) 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 QAA18525; Wed, 1 Oct 1997 16:52:40 -0700 (PDT) To: Brandon Gillespie cc: freebsd-current@FreeBSD.ORG Subject: Re: new command: doconfig In-reply-to: Your message of "Wed, 01 Oct 1997 16:21:45 MDT." Date: Wed, 01 Oct 1997 16:52:40 -0700 Message-ID: <18521.875749960@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > The only reason I didn't do it, was because I've never been able to find > out if anybody is working on this already... If not, then perhaps we can > make one. I have a few ideas on various modular ways this could be > implemented. I don't think that anyone is really working on it - they keep waiting for a miracle to happen and config(1) to simply go away. ;-) Since that's not likely anytime soon, I say go for it with doconfig. > So I guess the question is, what is there right now for auto generating a > kernel config file? Nothing. :( Jordan From owner-freebsd-current Wed Oct 1 17:36:23 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id RAA19406 for current-outgoing; Wed, 1 Oct 1997 17:36:23 -0700 (PDT) Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.95.76.54]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id RAA19400; Wed, 1 Oct 1997 17:36:18 -0700 (PDT) Received: (from kargl@localhost) by troutmask.apl.washington.edu (8.8.7/8.8.5) id RAA00335; Wed, 1 Oct 1997 17:38:49 -0700 (PDT) From: "Steven G. Kargl" Message-Id: <199710020038.RAA00335@troutmask.apl.washington.edu> Subject: netatalk broken in -current To: wollman@freebsd.org Date: Wed, 1 Oct 1997 17:38:48 -0700 (PDT) Cc: 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 Garrett, [cc'd to freebsd-current] Netatalk is broken in -current. I've tracked the problem down to commits made on Aug 16. A kernel built with sources cvsup'd with *default host=cvsup.FreeBSD.org *default base=/freebsd *default prefix=/freebsd *default release=cvs tag=. *default delete use-rel-suffix *default date=97.08.16.00.00.00 boots and netatalk works. If date= is changed to 97.08.17.00.00.00, then the resulting kernel claims that the netatalk protocols are not supported. I believe that this problem arose with some of the changes to src/sys/netatalk/ddp_usrreq.c. ----------------------------- 1.9 Sat Aug 16 19:15:33 1997 by wollman Diffs to 1.8 Fix all areas of the system (or at least all those in LINT) to avoid storing socket addresses in mbufs. (Socket buffers are the one exception.) A number of kernel APIs needed to get fixed in order to make this happen. Also, fix three protocol families which kept PCBs in mbufs to not malloc them instead. Delete some old compatibility cruft while we're at it, and add some new routines in the in_cksum family. ----------------------------- Unfortunately, it looks like massive changes went into cleaning up the use of mbufs, so I don't know where to look to fix the problem. -- Steve finger kargl@troutmask.apl.washington.edu http://troutmask.apl.washington.edu/~kargl/sgk.html From owner-freebsd-current Wed Oct 1 17:44:54 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id RAA19781 for current-outgoing; Wed, 1 Oct 1997 17:44:54 -0700 (PDT) Received: from caliban.dihelix.com (caliban.dihelix.com [198.180.136.122]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id RAA19773 for ; Wed, 1 Oct 1997 17:44:49 -0700 (PDT) Received: (from langfod@localhost) by caliban.dihelix.com (8.8.7/8.8.3) id OAA11591 for current@freebsd.org; Wed, 1 Oct 1997 14:44:42 -1000 (HST) Date: Wed, 1 Oct 1997 14:44:42 -1000 (HST) From: David Langford Message-Id: <199710020044.OAA11591@caliban.dihelix.com> To: current@freebsd.org Subject: problem with free() and junk pointers? Sender: owner-freebsd-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I have a three week old current box that I am trying to get more current but I keep getting the following: make in free(): warning: modified (chunk-) pointer. make in free(): warning: junk pointer, too low to make sense. Segmentation fault - core dumped This seems to be a random occurance and makes getting through a make world a wee bit of a pain. Do I have a bad library or could this be a sign of bad memory? I dont get the normal "cc died due to signal such and such" so I was disconting the memory bit but.... Any thoughts on where I should beat raw would be appreciated. -David Langford langfod@dihelix.com From owner-freebsd-current Wed Oct 1 18:58:11 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id SAA23125 for current-outgoing; Wed, 1 Oct 1997 18:58:11 -0700 (PDT) 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 SAA23120; Wed, 1 Oct 1997 18:58:07 -0700 (PDT) Received: from right.PCS (right.PCS [148.105.10.31]) by sumatra.americantv.com (8.8.5/8.8.5) with ESMTP id UAA00510; Wed, 1 Oct 1997 20:57:55 -0500 (CDT) Received: (from jlemon@localhost) by right.PCS (8.6.13/8.6.4) id UAA06854; Wed, 1 Oct 1997 20:57:23 -0500 Message-ID: <19971001205723.43367@right.PCS> Date: Wed, 1 Oct 1997 20:57:23 -0500 From: Jonathan Lemon To: "Steven G. Kargl" Cc: wollman@FreeBSD.ORG, freebsd-current@FreeBSD.ORG Subject: Re: netatalk broken in -current References: <199710020038.RAA00335@troutmask.apl.washington.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.61.1 In-Reply-To: <199710020038.RAA00335@troutmask.apl.washington.edu>; from Steven G. Kargl on Oct 10, 1997 at 05:38:48PM -0700 Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Oct 10, 1997 at 05:38:48PM -0700, Steven G. Kargl wrote: > Netatalk is broken in -current. I've tracked the problem > down to commits made on Aug 16. A kernel built with sources I've been trying to track this one down today. I'm able to get the `atalkd' daemon up and running, and then execute _one_ appletalk command (say, getzones). The second time around, it errors with EPROTONOSUPPORT. Tracing the second program into the kernel shows that somehow, between the completion of the first `getzones' call, and the start of the second, `prp->pr_usrreqs->pru_attach' has been set to 0. -- Jonathan From owner-freebsd-current Wed Oct 1 21:15:13 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id VAA00474 for current-outgoing; Wed, 1 Oct 1997 21:15:13 -0700 (PDT) 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 VAA00456 for ; Wed, 1 Oct 1997 21:15:09 -0700 (PDT) Received: from austin.polstra.com (jdp@localhost) by austin.polstra.com (8.8.7/8.8.5) with ESMTP id VAA23375; Wed, 1 Oct 1997 21:15:04 -0700 (PDT) Message-Id: <199710020415.VAA23375@austin.polstra.com> To: neil.long@materials.oxford.ac.uk Subject: Re: CVSup-15.2 is now available In-Reply-To: <199710011718.SAA08211@njl2.materials.ox.ac.uk> References: <199710011718.SAA08211@njl2.materials.ox.ac.uk> Organization: Polstra & Co., Seattle, WA Cc: current@freebsd.org Date: Wed, 01 Oct 1997 21:15:03 -0700 From: John Polstra Sender: owner-freebsd-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk In article <199710011718.SAA08211@njl2.materials.ox.ac.uk>, Neil J Long wrote: > > I keep checking the URL but I only ever see 15.1. Where is 15.2 (binary > pacakge that is)? My announcement was wrong because packages-current is no longer kept up to date. There is a package for CVSup-15.2 in packages-stable, and it is rumored to work under -current as well. If it doesn't, you'll have to either use the static binary or build the program from the port. 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 Wed Oct 1 21:38:24 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id VAA01631 for current-outgoing; Wed, 1 Oct 1997 21:38:24 -0700 (PDT) Received: from lsd.relcom.eu.net (lsd.relcom.eu.net [193.124.23.23]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id VAA01617 for ; Wed, 1 Oct 1997 21:38:14 -0700 (PDT) Received: (from ache@localhost) by lsd.relcom.eu.net (8.8.7/8.8.7) id IAA11313; Thu, 2 Oct 1997 08:38:10 +0400 (MSD) Date: Thu, 2 Oct 1997 08:38:08 +0400 (MSD) From: =?KOI8-R?B?4c7E0sXKIP7F0s7P1w==?= X-Sender: ache@lsd.relcom.eu.net To: FreeBSD-current Subject: Which PCI Ethernet card is best for FreeBSD-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 Could someone share his experience with me and tell about 2-3 best models? Stability is more essential than performance for me. -- Andrey A. Chernov http://www.nagual.pp.ru/~ache/ From owner-freebsd-current Wed Oct 1 22:16:05 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id WAA03610 for current-outgoing; Wed, 1 Oct 1997 22:16:05 -0700 (PDT) Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.95.76.54]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id WAA03585; Wed, 1 Oct 1997 22:15:59 -0700 (PDT) Received: (from sgk@localhost) by troutmask.apl.washington.edu (8.8.7/8.8.5) id WAA00972; Wed, 1 Oct 1997 22:18:25 -0700 (PDT) From: Steve Kargl Message-Id: <199710020518.WAA00972@troutmask.apl.washington.edu> Subject: Re: netatalk broken in -current In-Reply-To: <19971001205723.43367@right.PCS> from Jonathan Lemon at "Oct 1, 97 08:57:23 pm" To: jlemon@americantv.com (Jonathan Lemon) Date: Wed, 1 Oct 1997 22:18:25 -0700 (PDT) Cc: kargl@troutmask.apl.washington.edu, wollman@FreeBSD.ORG, 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 According to Jonathan Lemon: > On Oct 10, 1997 at 05:38:48PM -0700, Steven G. Kargl wrote: > > Netatalk is broken in -current. I've tracked the problem > > down to commits made on Aug 16. A kernel built with sources > > I've been trying to track this one down today. I'm able to get > the `atalkd' daemon up and running, and then execute _one_ appletalk > command (say, getzones). The second time around, it errors with > EPROTONOSUPPORT. > > Tracing the second program into the kernel shows that somehow, between > the completion of the first `getzones' call, and the start of the > second, `prp->pr_usrreqs->pru_attach' has been set to 0. > Your analysis suggests that this might be an "off by one" indexing problem or using a pointer that was previously freed. I would think that phkmalloc would catch memory management problems. I have no idea where to look at the moment. -- Steve finger kargl@troutmask.apl.washington.edu http://troutmask.apl.washington.edu/~kargl/sgk.html From owner-freebsd-current Wed Oct 1 22:28:35 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id WAA04236 for current-outgoing; Wed, 1 Oct 1997 22:28:35 -0700 (PDT) Received: from word.smith.net.au (word.smith.net.au [202.0.75.3]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id WAA04230 for ; Wed, 1 Oct 1997 22:28:30 -0700 (PDT) Received: from word.smith.net.au (localhost.smith.net.au [127.0.0.1]) by word.smith.net.au (8.8.7/8.8.5) with ESMTP id OAA00472; Thu, 2 Oct 1997 14:54:57 +0930 (CST) Message-Id: <199710020524.OAA00472@word.smith.net.au> X-Mailer: exmh version 2.0zeta 7/24/97 To: =?KOI8-R?B?4c7E0sXKIP7F0s7P1w==?= cc: FreeBSD-current Subject: Re: Which PCI Ethernet card is best for FreeBSD-current? In-reply-to: Your message of "Thu, 02 Oct 1997 08:38:08 +0400." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 02 Oct 1997 14:54:57 +0930 From: Mike Smith Sender: owner-freebsd-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > Could someone share his experience with me and tell about 2-3 best models? > Stability is more essential than performance for me. Anything using the Realtek RTL8029 will be stable, for sure. Almost any "NE2000 compatible" card will do. Performance won't be so great though (but quite adequate). Alternatively many vendors do cards based on the Digital DC2104x chips, and these perform better and are also generally very stable. mike From owner-freebsd-current Wed Oct 1 22:57:54 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id WAA05666 for current-outgoing; Wed, 1 Oct 1997 22:57:54 -0700 (PDT) Received: from sinbin.demos.su (sinbin.demos.su [194.87.0.31]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id WAA05659 for ; Wed, 1 Oct 1997 22:57:49 -0700 (PDT) Received: by sinbin.demos.su id JAA12728; (8.6.12/D) Thu, 2 Oct 1997 09:56:34 +0400 From: bag@sinbin.demos.su (Alex G. Bulushev) Message-Id: <199710020556.JAA12728@sinbin.demos.su> Subject: Re: problem with free() and junk pointers? In-Reply-To: <199710020044.OAA11591@caliban.dihelix.com> from "David Langford" at "Oct 1, 97 02:44:42 pm" X-ELM-OSV: (Our standard violations) no-mime=1; no-hdr-encoding=1 To: langfod@dihelix.com (David Langford) Date: Thu, 2 Oct 1997 09:56:33 +0400 (MSD) Cc: current@freebsd.org X-Mailer: ELM [version 2.4ME+ PL32 (25)] Content-Type: text Sender: owner-freebsd-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > > I have a three week old current box that I am trying to > get more current but I keep getting the following: > > make in free(): warning: modified (chunk-) pointer. > make in free(): warning: junk pointer, too low to make sense. > Segmentation fault - core dumped > > > This seems to be a random occurance and makes getting through a make world > a wee bit of a pain. > > Do I have a bad library or could this be a sign of bad memory? > I dont get the normal "cc died due to signal such and such" so I was > disconting the memory bit but.... > this is feature :) for fsck -p via reboot this err occure for big ( >=8 GB ) disk with big number of inodes ... i see this err in Oct 1996 and in Oct 1997 :) for FreeBSD 3.0-970919-SNAP dual PPro 233/512, Intel PR440FX, 256MB RAM sd1: type 0 fixed SCSI 2 sd1: Direct-Access 8683MB (17783112 512 byte sectors) with ~7000000 inodes, fsck report: cannot alloc 7900289 bytes for typemap. fsck in free(): warning: page is already free. fsck in free(): warning: page is already free. fsck in free(): warning: chunk is already free. fsck in free(): warning: page is already free. fsck in free(): warning: chunk is already free. fsck in free(): warning: page is already free. fsck in free(): warning: chunk is already free. fsck in free(): warning: page is already free. fsck in free(): warning: chunk is already free. fsck in free(): warning: page is already free. fsck in free(): warning: chunk is already free. /dev/rsd1e: CAN'T CHECK FILE SYSTEM. /dev/rsd1e: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY. and now for FreeBSD 3.0-970926-SNAP fsck report: cannot alloc 7900289 bytes for typemap. fsck in free(): warning: page is already free. fsck in free(): warning: page is already free. fsck in free(): warning: chunk is already free. fsck in free(): warning: page is already free. fsck in free(): warning: chunk is already free. fsck in free(): warning: junk pointer too low to make sense. fsck: Panic: lost 2 buffers Automatic file system check failed ... help! Alex. From owner-freebsd-current Wed Oct 1 23:53:44 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id XAA08249 for current-outgoing; Wed, 1 Oct 1997 23:53:44 -0700 (PDT) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id XAA08241 for ; Wed, 1 Oct 1997 23:53:40 -0700 (PDT) Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id IAA27047; Thu, 2 Oct 1997 08:53:26 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.8.7/8.8.5) id IAA15631; Thu, 2 Oct 1997 08:38:25 +0200 (MET DST) Message-ID: <19971002083825.DC08068@uriah.heep.sax.de> Date: Thu, 2 Oct 1997 08:38:25 +0200 From: j@uriah.heep.sax.de (J Wunsch) To: current@FreeBSD.ORG Cc: csgs@omega.ru.ac.za, pechter@lakewood.com Subject: Re: SCSI error causes crash References: <199710011937.PAA01465@i4got.lakewood.com> X-Mailer: Mutt 0.60_p2-3,5,8-9 Mime-Version: 1.0 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 Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <199710011937.PAA01465@i4got.lakewood.com>; from Bill Pechter on Oct 1, 1997 15:37:32 -0400 Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk As Bill Pechter wrote: > I see the same kind of errors on my DORS (and the drive light is on > permanently when it happens...) Does it also happen with tagged command queuing disabled? See the threads about ``Command failed'' for the NCR driver that recently were in freebsd-scsi. -- 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 Wed Oct 1 23:54:54 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id XAA08311 for current-outgoing; Wed, 1 Oct 1997 23:54:54 -0700 (PDT) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id XAA08306 for ; Wed, 1 Oct 1997 23:54:51 -0700 (PDT) Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id IAA27051; Thu, 2 Oct 1997 08:54:50 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.8.7/8.8.5) id IAA15649; Thu, 2 Oct 1997 08:41:32 +0200 (MET DST) Message-ID: <19971002084132.IV40498@uriah.heep.sax.de> Date: Thu, 2 Oct 1997 08:41:32 +0200 From: j@uriah.heep.sax.de (J Wunsch) To: current@FreeBSD.ORG Cc: csgs@omega.ru.ac.za Subject: Re: fdesc file system causes instant reboot References: X-Mailer: Mutt 0.60_p2-3,5,8-9 Mime-Version: 1.0 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 Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: ; from Graham Smith on Oct 1, 1997 20:29:07 +0200 Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk As Graham Smith wrote: > We are running freeBSD current on a dual pentium 200. If we > mount fdesc with an /etc/fstab like so: > fdesc /dev fdesc rw,union > > and then do something like: > bash$ cat /dev/stdout | somenonexistantfile > > the machine reboots instantly. Probably not very surprising. I don't think fdesc is a supported filesystem currently. Also, mounting something over /dev cries for an error (you shadow all the existing /dev entries, so the only filesystem you should ever mount there is devfs). Finally, why don't you simply use the existing /dev/std* and /dev/fd/* entries? They are using a pseudo-device driver instead of a filesystem, but achieve the same goal. -- 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 Wed Oct 1 23:56:22 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id XAA08464 for current-outgoing; Wed, 1 Oct 1997 23:56:22 -0700 (PDT) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id XAA08455 for ; Wed, 1 Oct 1997 23:56:19 -0700 (PDT) Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id IAA27066; Thu, 2 Oct 1997 08:56:18 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.8.7/8.8.5) id IAA15672; Thu, 2 Oct 1997 08:48:52 +0200 (MET DST) Message-ID: <19971002084852.PP26017@uriah.heep.sax.de> Date: Thu, 2 Oct 1997 08:48:52 +0200 From: j@uriah.heep.sax.de (J Wunsch) To: current@FreeBSD.ORG Cc: roberto@keltia.freenix.fr (Ollivier Robert) Subject: Re: Geometry weirdness with sysinstall/libdisk References: <19970930223542.44057@keltia.freenix.fr> <19971001072648.MU20136@uriah.heep.sax.de> <19971001040119.61326@gaffaneys.com> <19971002012804.28680@keltia.freenix.fr> X-Mailer: Mutt 0.60_p2-3,5,8-9 Mime-Version: 1.0 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 Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <19971002012804.28680@keltia.freenix.fr>; from Ollivier Robert on Oct 2, 1997 01:28:04 +0200 Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk As Ollivier Robert wrote: > > > Debug_Disk(sd2) flags=0 bios_geom=13045/54/6 = 4226580 > > > > Certainly no slices present yet. > > As you can see in disklabel output, it certainly _has_ slices, it used to > be my boot drive !!! > > # /dev/rsd2c: > type: SCSI > disk: IBM32160 > ... > 8 partitions: These are partitions, not slices. You ought to learn the difference by now... -- 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 Thu Oct 2 01:46:44 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id BAA13716 for current-outgoing; Thu, 2 Oct 1997 01:46:44 -0700 (PDT) Received: from usr08.primenet.com (tlambert@usr08.primenet.com [206.165.6.208]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id BAA13711 for ; Thu, 2 Oct 1997 01:46:42 -0700 (PDT) Received: (from tlambert@localhost) by usr08.primenet.com (8.8.5/8.8.5) id BAA25188; Thu, 2 Oct 1997 01:46:39 -0700 (MST) From: Terry Lambert Message-Id: <199710020846.BAA25188@usr08.primenet.com> Subject: Re: Geometry weirdness with sysinstall/libdisk To: joerg_wunsch@uriah.heep.sax.de Date: Thu, 2 Oct 1997 08:46:38 +0000 (GMT) Cc: current@FreeBSD.ORG, roberto@keltia.freenix.fr In-Reply-To: <19971002084852.PP26017@uriah.heep.sax.de> from "J Wunsch" at Oct 2, 97 08:48:52 am X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > These are partitions, not slices. You ought to learn the difference > by now... In case you haven't: Slices are what DOS 'fdisk' calls partitions, and partitions are what SunOS 'disklabel' calls slices. Yes, we *are* bass-akwards from the rest of the world... lump it until the distinction becomes irrelevant. 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 Thu Oct 2 01:47:24 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id BAA13768 for current-outgoing; Thu, 2 Oct 1997 01:47:24 -0700 (PDT) Received: from tyree.iii.co.uk (tyree.iii.co.uk [193.117.77.66]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id BAA13757 for ; Thu, 2 Oct 1997 01:47:16 -0700 (PDT) Received: from carrig.strand.iii.co.uk (carrig.strand.iii.co.uk [192.168.7.25]) by tyree.iii.co.uk (8.8.7/8.8.7) with ESMTP id JAA23194; Thu, 2 Oct 1997 09:43:45 +0100 (BST) Received: (from nik@localhost) by carrig.strand.iii.co.uk (8.8.7/8.8.7) id JAA10767; Thu, 2 Oct 1997 09:49:20 +0100 (BST) Message-ID: <19971002094919.21626@strand.iii.co.uk> Date: Thu, 2 Oct 1997 09:49:19 +0100 From: nik@iii.co.uk To: "Jordan K. Hubbard" Cc: Brandon Gillespie , freebsd-current@FreeBSD.ORG Subject: Re: new command: doconfig References: <4448.875744084@time.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.76e In-Reply-To: <4448.875744084@time.cdrom.com>; from Jordan K. Hubbard on Wed, Oct 01, 1997 at 03:14:44PM -0700 Organization: interactive investor Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Wed, Oct 01, 1997 at 03:14:44PM -0700, Jordan K. Hubbard wrote: > It should also build the configuration file through a complete > interactive Q&A process if you don't have one. Is this anything that "The Dotfile generator" (it's in ports, and a web page is at http://www.imada.ou.dk/~blackie/dotfile/) could handle? It's not something I've ever used (lack of round tuits) but it looks possible. Anyone here who's used it got any comments as to its suitability? N -- --+==[ Nik Clayton is Just Another Perl Hacker at Interactive Investor ]==+-- And I'd have gotten away with it too, if it hadn't been for those pesky kids. From owner-freebsd-current Thu Oct 2 01:52:01 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id BAA14068 for current-outgoing; Thu, 2 Oct 1997 01:52:01 -0700 (PDT) Received: from news.NL.net (news.NL.net [193.78.240.11]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id BAA14046 for ; Thu, 2 Oct 1997 01:51:58 -0700 (PDT) Received: from smtp01.oce.nl ([134.188.1.25] HELO smtp01.oce.nl ident: NO-IDENT-SERVICE [port 46214]) by news.NL.net with SMTP id <2913283-20602>; Thu, 2 Oct 1997 10:51:49 +0200 Received: by smtp01.oce.nl (5.x/SMI-SVR4) id AA15351; Thu, 2 Oct 1997 10:51:29 +0200 >Return-Path: Received: (qmail 12563 invoked from network); 2 Oct 1997 08:49:58 -0000 Received: from st1-jos.oce.nl (134.188.60.60) by ns-venlo.oce.nl with SMTP; 2 Oct 1997 08:49:58 -0000 Received: (qmail 4706 invoked by uid 911); 2 Oct 1997 08:47:46 -0000 Message-Id: <19971002084746.4705.qmail@st1-jos.oce.nl> To: pechter@lakewood.com Cc: csgs@omega.ru.ac.za, current@FreeBSD.ORG Subject: Re: SCSI error causes crash In-Reply-To: Your message of "Wed, 01 Oct 1997 15:37:32 EDT." <199710011937.PAA01465@i4got.lakewood.com> Date: Thu, 02 Oct 1997 10:47:46 +0200 From: Jos Backus Content-Type: text Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk In message <199710011937.PAA01465@i4got.lakewood.com> you wrote: >I see the same kind of errors on my DORS (and the drive light is on >permanently when it happens...) > >Running 2.2-STABLE from August. Same here (Asus P55T2P4S w/ Adaptec 2940UW, 2xIBM DORS31260UW disks). An fsck right after booting just hangs, with the controller light on. Groetjes, Jos -- Jos Backus _/ _/_/_/ CIM-ISGA/IS _/ _/ _/ Oce-Technologies B.V. _/ _/_/_/ Venlo, The Netherlands _/ _/ _/ _/ jos@oce.nl _/_/ _/_/_/ #include From owner-freebsd-current Thu Oct 2 02:47:56 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id CAA16662 for current-outgoing; Thu, 2 Oct 1997 02:47:56 -0700 (PDT) Received: from time.cdrom.com (time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id CAA16655 for ; Thu, 2 Oct 1997 02:47:52 -0700 (PDT) Received: from time.cdrom.com (localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.7/8.6.9) with ESMTP id CAA27405; Thu, 2 Oct 1997 02:46:34 -0700 (PDT) To: nik@iii.co.uk cc: Brandon Gillespie , freebsd-current@FreeBSD.ORG Subject: Re: new command: doconfig In-reply-to: Your message of "Thu, 02 Oct 1997 09:49:19 BST." <19971002094919.21626@strand.iii.co.uk> Date: Thu, 02 Oct 1997 02:46:33 -0700 Message-ID: <27384.875785593@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > On Wed, Oct 01, 1997 at 03:14:44PM -0700, Jordan K. Hubbard wrote: > > It should also build the configuration file through a complete > > interactive Q&A process if you don't have one. > > Is this anything that "The Dotfile generator" (it's in ports, and a web > page is at http://www.imada.ou.dk/~blackie/dotfile/) could handle? It's > not something I've ever used (lack of round tuits) but it looks possible. The dotfile generator does indeed supply a pretty cute approach to solving the problem of creating generic config file editors. Powerful enough to do a kernel configurator in? I don't know - I haven't looked at it *that* closely. I wouldn't discourage anyone else from doing so, however. :) Jordan From owner-freebsd-current Thu Oct 2 03:01:37 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id DAA17151 for current-outgoing; Thu, 2 Oct 1997 03:01:37 -0700 (PDT) Received: from tyree.iii.co.uk (tyree.iii.co.uk [193.117.77.66]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id DAA17141 for ; Thu, 2 Oct 1997 03:01:17 -0700 (PDT) Received: from carrig.strand.iii.co.uk (carrig.strand.iii.co.uk [192.168.7.25]) by tyree.iii.co.uk (8.8.7/8.8.7) with ESMTP id KAA07049; Thu, 2 Oct 1997 10:57:50 +0100 (BST) Received: (from nik@localhost) by carrig.strand.iii.co.uk (8.8.7/8.8.7) id LAA10844; Thu, 2 Oct 1997 11:03:25 +0100 (BST) Message-ID: <19971002110324.14949@strand.iii.co.uk> Date: Thu, 2 Oct 1997 11:03:24 +0100 From: nik@iii.co.uk To: "Jordan K. Hubbard" Cc: freebsd-current@FreeBSD.ORG Subject: Re: new command: doconfig References: <19971002094919.21626@strand.iii.co.uk> <27384.875785593@time.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.76e In-Reply-To: <27384.875785593@time.cdrom.com>; from Jordan K. Hubbard on Thu, Oct 02, 1997 at 02:46:33AM -0700 Organization: interactive investor Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Thu, Oct 02, 1997 at 02:46:33AM -0700, Jordan K. Hubbard wrote: > > Is this anything that "The Dotfile generator" (it's in ports, and a web > > page is at http://www.imada.ou.dk/~blackie/dotfile/) could handle? It's > > not something I've ever used (lack of round tuits) but it looks possible. > > The dotfile generator does indeed supply a pretty cute approach to > solving the problem of creating generic config file editors. Powerful > enough to do a kernel configurator in? I don't know - I haven't > looked at it *that* closely. I wouldn't discourage anyone else from > doing so, however. :) I'll cheerfully put it on my list of interesting things to do. Currently, however, I'm trying to work out why, given 2 copies of src.tgz on different machines but with identical MD5 checksums, extracting it on one machine works with no problems, and on another certain files are replaced with binary rubbish. This is slowing down my 'make world' somewhat . Particularly as this second machine is nowhere near anything 'net connected, and I have to do all file transfers by parallel port Zip drive every 18 hours or so. . . This is with an ASUSTeK P6UP5-P6 Pentium Pro Mainboard with the NCR SCSI BIOS (no idea of version at the moment, I didn't note the info) running on a (for the moment) 2.2.2-RELEASE system. N -- --+==[ Nik Clayton is Just Another Perl Hacker at Interactive Investor ]==+-- And I'd have gotten away with it too, if it hadn't been for those pesky kids. From owner-freebsd-current Thu Oct 2 03:07:34 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id DAA17327 for current-outgoing; Thu, 2 Oct 1997 03:07:34 -0700 (PDT) Received: from firewall.ftf.dk (root@mail.ftf.dk [129.142.64.2]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id DAA17322 for ; Thu, 2 Oct 1997 03:07:28 -0700 (PDT) Received: from mail.prosa.dk ([192.168.100.2]) by firewall.ftf.dk (8.7.6/8.7.3) with ESMTP id MAA17267 for ; Thu, 2 Oct 1997 12:37:33 +0200 Received: from deepo.prosa.dk (deepo.prosa.dk [192.168.100.10]) by mail.prosa.dk (8.8.5/8.8.5/prosa-1.1) with ESMTP id MAA14580 for ; Thu, 2 Oct 1997 12:18:45 +0200 (CEST) Received: (from regnauld@localhost) by deepo.prosa.dk (8.8.5/8.8.5/prosa-1.1) id MAA14794; Thu, 2 Oct 1997 12:06:26 +0200 (CEST) Message-ID: <19971002120626.14007@deepo.prosa.dk> Date: Thu, 2 Oct 1997 12:06:26 +0200 From: Philippe Regnauld To: freebsd-current@FreeBSD.ORG Subject: Re: new command: doconfig References: <19971002094919.21626@strand.iii.co.uk> <27384.875785593@time.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Description: Main Body X-Mailer: Mutt 0.69 In-Reply-To: <27384.875785593@time.cdrom.com>; from Jordan K. Hubbard on Thu, Oct 02, 1997 at 02:46:33AM -0700 X-Operating-System: FreeBSD 2.2.1-RELEASE i386 Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Jordan K. Hubbard writes: > > The dotfile generator does indeed supply a pretty cute approach to > solving the problem of creating generic config file editors. Powerful > enough to do a kernel configurator in? I don't know - I haven't Yes, but X-based. It should work in both modes. -- -- Phil -[ Philippe Regnauld / Systems Administrator / regnauld@deepo.prosa.dk ]- -[ Location.: +55.4N +11.3E PGP Key: finger regnauld@hotel.prosa.dk ]- From owner-freebsd-current Thu Oct 2 04:32:09 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id EAA19921 for current-outgoing; Thu, 2 Oct 1997 04:32:09 -0700 (PDT) Received: from g23.relcom.ru (g23.relcom.ru [193.125.152.117]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id EAA19886 for ; Thu, 2 Oct 1997 04:32:00 -0700 (PDT) Received: from prfbank1-dawn1.ll.relcom.ru (prfbank1-dawn1.ll.relcom.ru [193.124.250.145]) by g23.relcom.ru (8.7.5.R.ML.S/Relcom-2A) with SMTP id PAA26574 for ;Thu, 2 Oct 1997 15:18:44 +0400 (MSD) Received: from [100.0.0.52] by diamond.mas2000.msk.ru (NTMail 3.02.13) with ESMTP id ma002352 for ; Thu, 2 Oct 1997 14:06:07 +0300 Message-Id: <3.0.32.19971002030234.00694870@100.0.0.2> X-Sender: maxim@100.0.0.2 X-Mailer: Windows Eudora Pro Version 3.0 (32) Date: Thu, 02 Oct 1997 03:02:35 +0300 To: current@FreeBSD.ORG From: Maxim Surdu Subject: Compiling Kernel fails.... Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Help needed.... Yesterday I tried to recompile kernel and found that it fails with following lines: Loading kernel.... isa.o: undefined symbol __isa_(somthing I can't remember now) .............{the message repeats 5 times}................ Stop. You have to compile kernel before tryimg to load it. Stop. Of course I'll try to recompile kernel after "make world" command. (it seems to work just fine except few warnings :-)). ---------------------- Regards from Maxim Surdu maxim@mas2000.msk.ru From owner-freebsd-current Thu Oct 2 04:36:52 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id EAA20110 for current-outgoing; Thu, 2 Oct 1997 04:36:52 -0700 (PDT) Received: from news.NL.net (news.NL.net [193.78.240.11]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id EAA20104 for ; Thu, 2 Oct 1997 04:36:50 -0700 (PDT) Received: from smtp01.oce.nl ([134.188.1.25] HELO smtp01.oce.nl ident: NO-IDENT-SERVICE [port 42119]) by news.NL.net with SMTP id <2913365-24353>; Thu, 2 Oct 1997 13:36:47 +0200 Received: by smtp01.oce.nl (5.x/SMI-SVR4) id AA19164; Thu, 2 Oct 1997 13:36:19 +0200 >Return-Path: Received: (qmail 20977 invoked from network); 2 Oct 1997 11:31:19 -0000 Received: from st1-jos.oce.nl (134.188.60.60) by ns-venlo.oce.nl with SMTP; 2 Oct 1997 11:31:19 -0000 Received: (qmail 7633 invoked by uid 911); 2 Oct 1997 11:29:07 -0000 Message-Id: <19971002112907.7632.qmail@st1-jos.oce.nl> To: current@FreeBSD.ORG Subject: Re: SCSI error causes crash In-Reply-To: Your message of "Thu, 02 Oct 1997 08:38:25 +0200." <19971002083825.DC08068@uriah.heep.sax.de> Date: Thu, 02 Oct 1997 13:29:07 +0200 From: Jos Backus Content-Type: text Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk In message <19971002083825.DC08068@uriah.heep.sax.de> J Wunsch wrote: >Does it also happen with tagged command queuing disabled? Turning it off seems to fix it on one system (with two UW disks) but another system (with a single DORS32160, to be sure) seems to run just fine with tqing enabled. Hm... Groetjes, Jos -- Jos Backus _/ _/_/_/ CIM-ISGA/IS _/ _/ _/ Oce-Technologies B.V. _/ _/_/_/ Venlo, The Netherlands _/ _/ _/ _/ jos@oce.nl _/_/ _/_/_/ #include From owner-freebsd-current Thu Oct 2 06:05:03 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id GAA24202 for current-outgoing; Thu, 2 Oct 1997 06:05:03 -0700 (PDT) Received: from khavrinen.lcs.mit.edu (khavrinen.lcs.mit.edu [18.24.4.193]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id GAA24183 for ; Thu, 2 Oct 1997 06:04:56 -0700 (PDT) Received: (from wollman@localhost) by khavrinen.lcs.mit.edu (8.8.5/8.8.5) id JAA22567; Thu, 2 Oct 1997 09:04:45 -0400 (EDT) Date: Thu, 2 Oct 1997 09:04:45 -0400 (EDT) From: Garrett Wollman Message-Id: <199710021304.JAA22567@khavrinen.lcs.mit.edu> To: =?KOI8-R?B?4c7E0sXKIP7F0s7P1w==?= Cc: FreeBSD-current Subject: Which PCI Ethernet card is best for FreeBSD-current? In-Reply-To: References: Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk < said: > Could someone share his experience with me and tell about 2-3 best models? > Stability is more essential than performance for me. Intel EE Pro/100B, without question. Second choice, DEC DE500 and some clones. Never buy anything from 3Com. -GAWollman -- Garrett A. Wollman | O Siem / We are all family / O Siem / We're all the same wollman@lcs.mit.edu | O Siem / The fires of freedom Opinions not those of| Dance in the burning flame MIT, LCS, CRS, or NSA| - Susan Aglukark and Chad Irschick From owner-freebsd-current Thu Oct 2 06:32:01 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id GAA25579 for current-outgoing; Thu, 2 Oct 1997 06:32:01 -0700 (PDT) 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 GAA25542 for ; Thu, 2 Oct 1997 06:31:56 -0700 (PDT) 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 PAA04013; Thu, 2 Oct 1997 15:30:47 +0200 (CEST) To: David Langford cc: current@FreeBSD.ORG Subject: Re: problem with free() and junk pointers? In-reply-to: Your message of "Wed, 01 Oct 1997 14:44:42 -1000." <199710020044.OAA11591@caliban.dihelix.com> Date: Thu, 02 Oct 1997 15:30:47 +0200 Message-ID: <4011.875799047@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk In message <199710020044.OAA11591@caliban.dihelix.com>, David Langford writes: > >I have a three week old current box that I am trying to >get more current but I keep getting the following: > >make in free(): warning: modified (chunk-) pointer. >make in free(): warning: junk pointer, too low to make sense. >Segmentation fault - core dumped > > >This seems to be a random occurance and makes getting through a make world >a wee bit of a pain. > >Do I have a bad library or could this be a sign of bad memory? >I dont get the normal "cc died due to signal such and such" so I was >disconting the memory bit but.... It could be bad mem. The only other instance where this has been reported it was a wrong kind of refresh setup for the chips, if you can't change that in your bios (very likely), try out some other RAM sticks and see if that helps. -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." From owner-freebsd-current Thu Oct 2 06:42:00 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id GAA25963 for current-outgoing; Thu, 2 Oct 1997 06:42:00 -0700 (PDT) Received: from labinfo.iet.unipi.it (labinfo.iet.unipi.it [131.114.9.5]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id GAA25946 for ; Thu, 2 Oct 1997 06:40:58 -0700 (PDT) Received: from localhost (luigi@localhost) by labinfo.iet.unipi.it (8.6.5/8.6.5) id NAA12138; Thu, 2 Oct 1997 13:23:52 +0100 From: Luigi Rizzo Message-Id: <199710021223.NAA12138@labinfo.iet.unipi.it> Subject: Re: Which PCI Ethernet card is best for FreeBSD-current? To: wollman@khavrinen.lcs.mit.edu (Garrett Wollman) Date: Thu, 2 Oct 1997 13:23:52 +0100 (MET) Cc: ache@nagual.pp.ru, current@FreeBSD.ORG In-Reply-To: <199710021304.JAA22567@khavrinen.lcs.mit.edu> from "Garrett Wollman" at Oct 2, 97 09:04:26 am X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > Could someone share his experience with me and tell about 2-3 best models? > > Stability is more essential than performance for me. > > Intel EE Pro/100B, without question. Second choice, DEC DE500 and > some clones. Never buy anything from 3Com. you may want to notice though that the data sheets for the DEC21x4x are available on line so if you have problems with some driver you can at least try and fix them yourself. Not sure if the data sheets for the Pro/100B are available for the casual user or without NDA. Secondly the 2114x is used by many many vendors so you can find these cards very cheap. Cheers Luigi -----------------------------+-------------------------------------- Luigi Rizzo | Dip. di Ingegneria dell'Informazione email: luigi@iet.unipi.it | Universita' di Pisa tel: +39-50-568533 | via Diotisalvi 2, 56126 PISA (Italy) fax: +39-50-568522 | http://www.iet.unipi.it/~luigi/ _____________________________|______________________________________ From owner-freebsd-current Thu Oct 2 07:47:56 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id HAA29396 for current-outgoing; Thu, 2 Oct 1997 07:47:56 -0700 (PDT) Received: from news1.gtn.com (news1.gtn.com [192.109.159.3]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id HAA29317 for ; Thu, 2 Oct 1997 07:45:23 -0700 (PDT) Received: (from uucp@localhost) by news1.gtn.com (8.8.6/8.8.6) with UUCP id PAA15003; Thu, 2 Oct 1997 15:30:14 +0100 (MET) Received: (from andreas@localhost) by klemm.gtn.com (8.8.7/8.8.7) id QAA11539; Thu, 2 Oct 1997 16:23:25 +0200 (CEST) Message-ID: <19971002162324.02664@klemm.gtn.com> Date: Thu, 2 Oct 1997 16:23:24 +0200 From: Andreas Klemm To: =?iso-8859-1?Q?=E1=CE=C4=D2=C5=CA_=FE=C5=D2=CE=CF=D7?= Cc: FreeBSD-current Subject: Re: Which PCI Ethernet card is best for FreeBSD-current? References: <199710020524.OAA00472@word.smith.net.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.84 In-Reply-To: <199710020524.OAA00472@word.smith.net.au>; from Mike Smith on Thu, Oct 02, 1997 at 02:54:57PM +0930 X-Disclaimer: A free society is one where it is safe to be unpopular X-Operating-System: FreeBSD 3.0-CURRENT SMP Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Thu, Oct 02, 1997 at 02:54:57PM +0930, Mike Smith wrote: > > Could someone share his experience with me and tell about 2-3 best models? > > Stability is more essential than performance for me. > > Anything using the Realtek RTL8029 will be stable, for sure. Almost > any "NE2000 compatible" card will do. Performance won't be so great > though (but quite adequate). > > Alternatively many vendors do cards based on the Digital DC2104x chips, > and these perform better and are also generally very stable. Fastest and possibly best supported should be the EtherExpress/Pro 100B card (10/100). Supports full duplex mode. As far as I remember Rodney said about this card, that it is very server friendly. This card has been recommended many times on different fbsd mailinglists. So if there would be a problem with this card, people would surely complain very loud and clear ;-) I suggest best would be to browse the fbsd mailing list archive for technical discussion about this card, to be sure. Andreas /// -- Andreas Klemm powered by ,,symmetric multiprocessor FreeBSD'' andreas@klemm.gtn.com - http://www.freebsd.org/~fsmp/SMP/SMP.html andreas@FreeBSD.ORG - http://www.freebsd.org/~fsmp/SMP/benches.html From owner-freebsd-current Thu Oct 2 07:48:50 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id HAA29497 for current-outgoing; Thu, 2 Oct 1997 07:48:50 -0700 (PDT) Received: from forbidden-donut.anet-stl.com (forbidden-donut.anet-stl.com [209.83.128.17]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id HAA29485 for ; Thu, 2 Oct 1997 07:48:45 -0700 (PDT) Received: from localhost (doogie@localhost) by forbidden-donut.anet-stl.com (8.8.7/8.8.5) with SMTP id JAA02435; Thu, 2 Oct 1997 09:43:32 GMT Date: Thu, 2 Oct 1997 09:43:00 +0000 (GMT) From: Jason Young To: Garrett Wollman cc: =?KOI8-R?B?4c7E0sXKIP7F0s7P1w==?= , FreeBSD-current Subject: Re: Which PCI Ethernet card is best for FreeBSD-current? In-Reply-To: <199710021304.JAA22567@khavrinen.lcs.mit.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 Thu, 2 Oct 1997, Garrett Wollman wrote: > Intel EE Pro/100B, without question. Second choice, DEC DE500 and > some clones. Never buy anything from 3Com. May I inquire as to why you don't like 3Com? They work for me, I've got a mix of 3Com and DEC switching 10/100s around here with zero problems. Jason Young ANET Chief Network Engineer From owner-freebsd-current Thu Oct 2 07:56:05 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id HAA29975 for current-outgoing; Thu, 2 Oct 1997 07:56:05 -0700 (PDT) Received: from implode.root.com (implode.root.com [198.145.90.17]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id HAA29970 for ; Thu, 2 Oct 1997 07:56:03 -0700 (PDT) Received: from implode.root.com (localhost [127.0.0.1]) by implode.root.com (8.8.5/8.8.5) with ESMTP id HAA20848; Thu, 2 Oct 1997 07:56:40 -0700 (PDT) Message-Id: <199710021456.HAA20848@implode.root.com> To: Luigi Rizzo cc: wollman@khavrinen.lcs.mit.edu (Garrett Wollman), ache@nagual.pp.ru, current@FreeBSD.ORG Subject: Re: Which PCI Ethernet card is best for FreeBSD-current? In-reply-to: Your message of "Thu, 02 Oct 1997 13:23:52 BST." <199710021223.NAA12138@labinfo.iet.unipi.it> From: David Greenman Reply-To: dg@root.com Date: Thu, 02 Oct 1997 07:56:39 -0700 Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >> > Could someone share his experience with me and tell about 2-3 best models? >> > Stability is more essential than performance for me. >> >> Intel EE Pro/100B, without question. Second choice, DEC DE500 and >> some clones. Never buy anything from 3Com. > >you may want to notice though that the data sheets for the DEC21x4x are >available on line so if you have problems with some driver you can at >least try and fix them yourself. Not sure if the data sheets for the >Pro/100B are available for the casual user or without NDA. I haven't verified this, but I'm told that the data sheet for the i82557 is available on the Intel developer's web site and on the "developer's insight" CDROM. >Secondly the 2114x is used by many many vendors so you can find >these cards very cheap. Last I heard, you could buy the Pro/100B PCI for $59.95 in the Bay Area. My local price is around $65-$75, however. I don't think price is an issue at this level. -DG David Greenman Core-team/Principal Architect, The FreeBSD Project From owner-freebsd-current Thu Oct 2 07:56:22 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id HAA00118 for current-outgoing; Thu, 2 Oct 1997 07:56:22 -0700 (PDT) Received: from bmccane.uit.net (bmccane.uit.net [209.83.205.48]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id HAA29924 for ; Thu, 2 Oct 1997 07:55:13 -0700 (PDT) Received: (from root@localhost) by bmccane.uit.net (8.8.7/8.8.5) id JAA15160; Thu, 2 Oct 1997 09:51:07 -0500 (CDT) Date: Thu, 2 Oct 1997 09:51:07 -0500 (CDT) From: Wm Brian McCane To: Brandon Gillespie cc: freebsd-current@FreeBSD.ORG Subject: Re: new command: doconfig 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 Brandon, You might look at my program `kc'. It is a simple curses based kernel configuration tool. If you copy `GENERIC' to your new name, and then run `kc ', it gives a fairly simple point and click interface. You can get it via FTP: $ fetch ftp://bmccane.uit.net/pub/kc/kc1.1.tgz a current configuration file is in: $ fetch ftp://bmccane.uit.net/pub/kc/options.list.Z brian +-------------------------------------+----------------------------------------+ He rides a cycle of mighty days, and \ Wm Brian and Lori McCane he represents the last great schizm \ McCane Consulting among the gods. Evil though he obviously \ root@bmccane.uit.net is, he is a mighty figure, this father of \ http://bmccane.uit.net/ my spirit, and I respect him as the sons \ http://bmccane.uit.net/~pictures/ of old did the fathers of their bodies. \ http://bmccane.uit.net/~bmccane/ Roger Zelazny - "Lord of Light" \ http://bmccane.uit.net/~bbs/ +---------------------------------------------+--------------------------------+ On Wed, 1 Oct 1997, Brandon Gillespie wrote: > On Wed, 1 Oct 1997, Jordan K. Hubbard wrote: > > > I would like to add this as a new command to FreeBSD. I mentioned it a > > > few months back when I originally wrote it, and received positive > > > responses about it. This command derives from a similar command in > > > Digital Unix. 'doconfig' is basically a simplifier for kernel compiling, > > > by wrapping 'vi /sys/i386/conf/MINE; config; cd ../../compile/MINE; make > > > depend; make; make install; reboot' or whatnot into a simpler, nicer > > > interface.. For instance, I just recompiled my kernel with (the GLACIER > > > config file already existed): > > > > My only problem with this is that it didn't go far enough. Yes, it > > front-ends a few steps, but only a few of the ones you'd expect in a > > configuration front-end tool. > > > > It should also build the configuration file through a complete > > interactive Q&A process if you don't have one. > > I agree :) > > The only reason I didn't do it, was because I've never been able to find > out if anybody is working on this already... If not, then perhaps we can > make one. I have a few ideas on various modular ways this could be > implemented. > > As it is right now, 'doconfig' actually runs an external program to > 'auto-generate' the initial file. The external program does nothing other > than sed the GENERIC kernel, but only because of the above reasons. > > So I guess the question is, what is there right now for auto generating a > kernel config file? > > -Brandon > > From owner-freebsd-current Thu Oct 2 07:57:21 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id HAA00188 for current-outgoing; Thu, 2 Oct 1997 07:57:21 -0700 (PDT) Received: from khavrinen.lcs.mit.edu (khavrinen.lcs.mit.edu [18.24.4.193]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id HAA00176 for ; Thu, 2 Oct 1997 07:57:16 -0700 (PDT) Received: (from wollman@localhost) by khavrinen.lcs.mit.edu (8.8.5/8.8.5) id KAA22895; Thu, 2 Oct 1997 10:56:31 -0400 (EDT) Date: Thu, 2 Oct 1997 10:56:31 -0400 (EDT) From: Garrett Wollman Message-Id: <199710021456.KAA22895@khavrinen.lcs.mit.edu> To: Luigi Rizzo Cc: wollman@khavrinen.lcs.mit.edu (Garrett Wollman), ache@nagual.pp.ru, current@FreeBSD.ORG Subject: Re: Which PCI Ethernet card is best for FreeBSD-current? In-Reply-To: <199710021223.NAA12138@labinfo.iet.unipi.it> References: <199710021304.JAA22567@khavrinen.lcs.mit.edu> <199710021223.NAA12138@labinfo.iet.unipi.it> Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk < said: > Secondly the 2114x is used by many many vendors so you can find > these cards very cheap. Well, the Intel chip is pretty cheap, and in our tests performed better (had a lower DMA overhead) than the DEC chip. The trades are advertising a retail price of $65 each for the Intels (in quantity 5), and I know I can get a discount off of that. What's more, a lot of motherboards are starting to come with built in Fast Ethernet, and many of those (including all of the Intel-OEMed motherboards) have the 82557 chip on them. We have indeed had some trouble getting the actual documentation out of Intel; they seem to be reluctant to give out documents for this whizzo updateable microcode feature, but we don't much care about that (although it might be nice if we could program the DMA engine to speak mbuf directly). The overall programming model for this thing is just like every other Intel Ethernet chip ever made; a colleague here was able to implement the multicast filtering by almost directly copying the code out of the `ie' (82586/82596) driver. DEC chips have the bug that the Ethernet header has to be aligned on a longword boundary, which means that the protocol header---i.e., the part that actually matters---is guaranteed unaligned, thus necessitating an expensive copy operation or expensive unaligned accesses, depending on the CPU architecture. For someone building a router-type box, the standard designs involving either one is really inappropriate. What we would have liked (I no longer work on that project) would be a board with several NIC chips, a PCI-to-PCI bridge, and (most importantly) a good chunk of memory, on the order of a megabyte. We were easily able to DMA-starve the systems we were using for testing at that time (with slow Orion chipsets) using the workstation-type cards, since all of the traffic had to transit the (only) PCI bus twice. With a shared-memory design, the NIC and the CPU no longer have to compete for bus bandwith, and in a single-copy network implementation this is a big win. (It probably would also be helpful for SMP.) -GAWollman -- Garrett A. Wollman | O Siem / We are all family / O Siem / We're all the same wollman@lcs.mit.edu | O Siem / The fires of freedom Opinions not those of| Dance in the burning flame MIT, LCS, CRS, or NSA| - Susan Aglukark and Chad Irschick From owner-freebsd-current Thu Oct 2 07:58:58 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id HAA00298 for current-outgoing; Thu, 2 Oct 1997 07:58:58 -0700 (PDT) Received: from khavrinen.lcs.mit.edu (khavrinen.lcs.mit.edu [18.24.4.193]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id HAA00292 for ; Thu, 2 Oct 1997 07:58:55 -0700 (PDT) Received: (from wollman@localhost) by khavrinen.lcs.mit.edu (8.8.5/8.8.5) id KAA22916; Thu, 2 Oct 1997 10:58:48 -0400 (EDT) Date: Thu, 2 Oct 1997 10:58:48 -0400 (EDT) From: Garrett Wollman Message-Id: <199710021458.KAA22916@khavrinen.lcs.mit.edu> To: Jason Young Cc: FreeBSD-current Subject: Re: Which PCI Ethernet card is best for FreeBSD-current? In-Reply-To: References: <199710021304.JAA22567@khavrinen.lcs.mit.edu> Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk < said: > May I inquire as to why you don't like 3Com? They work for me, I've got a > mix of 3Com and DEC switching 10/100s around here with zero problems. Poor performance, and a brain-dead design that has no multicast address filters. Maybe they have now fix these, but they've made enough people unhappy that there really is no support for the drivers. -GAWollman -- Garrett A. Wollman | O Siem / We are all family / O Siem / We're all the same wollman@lcs.mit.edu | O Siem / The fires of freedom Opinions not those of| Dance in the burning flame MIT, LCS, CRS, or NSA| - Susan Aglukark and Chad Irschick From owner-freebsd-current Thu Oct 2 08:08:25 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id IAA00894 for current-outgoing; Thu, 2 Oct 1997 08:08:25 -0700 (PDT) Received: from Campino.Informatik.RWTH-Aachen.DE (campino.Informatik.RWTH-Aachen.DE [137.226.116.240]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id IAA00885 for ; Thu, 2 Oct 1997 08:08:21 -0700 (PDT) Received: from gil.physik.rwth-aachen.de (gilberto.physik.rwth-aachen.de [137.226.30.2]) by Campino.Informatik.RWTH-Aachen.DE (8.8.7/RBI-Z13) with ESMTP id RAA02567 for ; Thu, 2 Oct 1997 17:08:19 +0200 (MET DST) Received: (from kuku@localhost) by gil.physik.rwth-aachen.de (8.8.5/8.6.9) id RAA01742 for freebsd-current@freefall.cdrom.com; Thu, 2 Oct 1997 17:15:37 +0200 (MEST) Date: Thu, 2 Oct 1997 17:15:37 +0200 (MEST) From: Christoph Kukulies Message-Id: <199710021515.RAA01742@gil.physik.rwth-aachen.de> To: freebsd-current@freefall.FreeBSD.org Subject: netboot.com Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Anyone using netboot.com recently? I compiled a version for WD (-DINCLUDE_WD) and want to use it with a WD8013. Before the ask boot prompt appears netboot.com writes out a bunch of garbage on the screen and reboots. That is, it happens before eth_probe() is being called at all. Any clues? -- Chris Christoph P. U. Kukulies kuku@gil.physik.rwth-aachen.de From owner-freebsd-current Thu Oct 2 08:49:13 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id IAA03683 for current-outgoing; Thu, 2 Oct 1997 08:49:13 -0700 (PDT) Received: from implode.root.com (implode.root.com [198.145.90.17]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id IAA03674 for ; Thu, 2 Oct 1997 08:49:08 -0700 (PDT) Received: from implode.root.com (localhost [127.0.0.1]) by implode.root.com (8.8.5/8.8.5) with ESMTP id IAA21135; Thu, 2 Oct 1997 08:51:26 -0700 (PDT) Message-Id: <199710021551.IAA21135@implode.root.com> To: Jason Young cc: Garrett Wollman , =?KOI8-R?B?4c7E0sXKIP7F0s7P1w==?= , FreeBSD-current Subject: Re: Which PCI Ethernet card is best for FreeBSD-current? In-reply-to: Your message of "Thu, 02 Oct 1997 09:43:00 -0000." From: David Greenman Reply-To: dg@root.com Date: Thu, 02 Oct 1997 08:51:25 -0700 Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >> Intel EE Pro/100B, without question. Second choice, DEC DE500 and >> some clones. Never buy anything from 3Com. > >May I inquire as to why you don't like 3Com? They work for me, I've got a >mix of 3Com and DEC switching 10/100s around here with zero problems. Not speaking for Garrett, but the 3Com device drivers (ep/vx) in FreeBSD have had a long tradition of having various problems. In addition, the PCI 3Com cards aren't up to the performance levels that they are capable of; apparantly, 3Com won't release the information about programming the PCI DMA for them without an NDA (or at all??)...which means that they have to be used in "compatibility" mode, which I believe is programmed I/O (yech). -DG David Greenman Core-team/Principal Architect, The FreeBSD Project From owner-freebsd-current Thu Oct 2 10:16:18 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id KAA09629 for current-outgoing; Thu, 2 Oct 1997 10:16:18 -0700 (PDT) Received: from biggusdiskus.flyingfox.com (biggusdiskus.flyingfox.com [206.14.52.27]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id KAA09621 for ; Thu, 2 Oct 1997 10:16:14 -0700 (PDT) Received: (from jas@localhost) by biggusdiskus.flyingfox.com (8.8.5/8.8.5) id KAA08304; Thu, 2 Oct 1997 10:17:08 -0700 (PDT) Date: Thu, 2 Oct 1997 10:17:08 -0700 (PDT) From: Jim Shankland Message-Id: <199710021717.KAA08304@biggusdiskus.flyingfox.com> To: dg@root.com Subject: Re: Which PCI Ethernet card is best for FreeBSD-current? Cc: freebsd-current@freebsd.org Sender: owner-freebsd-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk dg writes: > the 3Com device drivers (ep/vx) in FreeBSD have had a long > tradition of having various problems. One data point as a counterindicator: I have an old 486/DX2-66 box with 4 3C509's (ep driver) in it that's been running for nearly 3 years (modulo power failures, upgrades, etc.). It's been rock solid. Two of the Ethernets get pretty heavy usage (not quite saturated, but getting close); the other 2 are pretty lightly loaded. Started with FreeBSD 2.1.5, now at 2.2.2-RELEASE. As I said, rock solid throughout. These days, I use the Intel PCI cards; $65 at the corner store, full duplex, driver very well supported under FreeBSD :-). I did recently get bitten by the "scrambled preamble" problem, which locks up (at least) rev 1 cards in (at least) 10 Mb mode when the wrong kind of noise is on the line. The DEC chip cards are second choice. The various vendors' cards are not all interchangeable: the de driver is full of code to try to figure out which of dozens of kinds of cards it is dealing with. Worse, the vendors change their cards from time to time, so the new card you just bought suddenly doesn't work until the driver catches up :-(. On the other hand, the only quad cards I know of are based on the DEC chip; I'll be trying out the Znyx quad card (I think) soon. Jim Shankland Flying Fox Computer Systems, Inc. From owner-freebsd-current Thu Oct 2 10:20:25 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id KAA09851 for current-outgoing; Thu, 2 Oct 1997 10:20:25 -0700 (PDT) Received: from implode.root.com (implode.root.com [198.145.90.17]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id KAA09835 for ; Thu, 2 Oct 1997 10:20:13 -0700 (PDT) Received: from implode.root.com (localhost [127.0.0.1]) by implode.root.com (8.8.5/8.8.5) with ESMTP id KAA21858; Thu, 2 Oct 1997 10:22:46 -0700 (PDT) Message-Id: <199710021722.KAA21858@implode.root.com> To: Jim Shankland cc: freebsd-current@freebsd.org Subject: Re: Which PCI Ethernet card is best for FreeBSD-current? In-reply-to: Your message of "Thu, 02 Oct 1997 10:17:08 PDT." <199710021717.KAA08304@biggusdiskus.flyingfox.com> From: David Greenman Reply-To: dg@root.com Date: Thu, 02 Oct 1997 10:22:46 -0700 Sender: owner-freebsd-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >duplex, driver very well supported under FreeBSD :-). I did recently >get bitten by the "scrambled preamble" problem, which locks up (at least) >rev 1 cards in (at least) 10 Mb mode when the wrong kind of noise is >on the line. BTW, I added a work-around for this bug a few days ago in -current and -stable. If you could verify that the problem is 'fixed', that would be most helpful. Try as I might, I can't reproduce the lock-up problem here, so I don't know for certain if it is really fixed. -DG David Greenman Core-team/Principal Architect, The FreeBSD Project From owner-freebsd-current Thu Oct 2 10:38:30 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id KAA10830 for current-outgoing; Thu, 2 Oct 1997 10:38:30 -0700 (PDT) Received: from george.arc.nasa.gov (george.arc.nasa.gov [128.102.194.142]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id KAA10821 for ; Thu, 2 Oct 1997 10:38:26 -0700 (PDT) From: lamaster@george.arc.nasa.gov Received: (from lamaster@localhost) by george.arc.nasa.gov (8.8.7/8.8.7) id KAA07677; Thu, 2 Oct 1997 10:37:07 -0700 (PDT) Date: Thu, 2 Oct 1997 10:37:07 -0700 (PDT) Message-Id: <199710021737.KAA07677@george.arc.nasa.gov> To: wollman@khavrinen.lcs.mit.edu Subject: Re: Which PCI Ethernet card is best for FreeBSD-current? Cc: current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk |> Garrett Wollman wrote: |> |> < said: |> |> > Could someone share his experience with me and tell about 2-3 best models? |> > Stability is more essential than performance for me. |> |> Intel EE Pro/100B, without question. Second choice, DEC DE500 and |> some clones. Never buy anything from 3Com. In retrospect it was probably a bad choice, but, so far, my 3Com 3C595 has worked OK, including for multicast, although network performance is not really an observable on that system. It was fairly expensive, although it was the cheapest PCI card I could get at the time. A couple of weeks later, the cheap DEC tulip cards came out... Also, although I have heard complaints about certain chip revision levels, my DEC Tulip-based card has also worked just fine, including under a heavy load and with numerous multicast sessions going: de0: rev 0x20 int a irq 12 on pci0.10.0 de0: SMC 9332BDT 21140A [10-100Mb/s] pass 2.0 de0: address 00:00:c0:e7:69:ef Can anyone describe exactly which revs of the Tulip chipset are likely to cause problems? As I said, mine has worked fine. These Tulip-based cards can be had very inexpensively now, and, I would recommend them. I know that the memory alignment rules are pessimal, but, at least at 10 Mbits/sec, it doesn't seem to matter much. I guess at 100 Mbits/sec, it would be serious performance hit. -Hugh LaMaster From owner-freebsd-current Thu Oct 2 10:42:26 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id KAA11129 for current-outgoing; Thu, 2 Oct 1997 10:42:26 -0700 (PDT) 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 KAA11119 for ; Thu, 2 Oct 1997 10:42:22 -0700 (PDT) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.5/8.6.9) id DAA06047; Fri, 3 Oct 1997 03:40:07 +1000 Date: Fri, 3 Oct 1997 03:40:07 +1000 From: Bruce Evans Message-Id: <199710021740.DAA06047@godzilla.zeta.org.au> To: current@FreeBSD.ORG, roberto@keltia.freenix.fr Subject: Re: Geometry weirdness with sysinstall/libdisk Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >> > Debug_Disk(sd2) flags=0 bios_geom=13045/54/6 = 4226580 >> >> Certainly no slices present yet. > >As you can see in disklabel output, it certainly _has_ slices, it used to >be my boot drive !!! disklabel(8) knows/shows nothing about slices (or BIOS geometries). >> From the drive itself, i'd say. Well, no, this drive has 8205 >> cylinders and 6 heads: > >It is a 32160 so it is 6703 cyl. x 5 heads so I still don't see where does >the 13045 come from... Someone set up a wrong BIOS geometry of 54 heads and 6 sectors (by setting up the corresponding MBR in /dev/rsd2). 13045 is just total_sectors / (54 * 6). >What bother me a lot is why libdisk/sysinstall don't see the slices when >disklabel can ! disklabel(8) knows/shows nothing about slices (or BIOS geometries). >I can mount every slice on that drive without problem so >the kernel has the right label but why disklabel is the only program to >display it correctly ? libdisk/sysinstall must be wrong. The 54/6 geometry should work if there are no booting problems. Bruc From owner-freebsd-current Thu Oct 2 11:18:17 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id LAA13126 for current-outgoing; Thu, 2 Oct 1997 11:18:17 -0700 (PDT) Received: from verdi.nethelp.no (verdi.nethelp.no [195.1.171.130]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id LAA13121 for ; Thu, 2 Oct 1997 11:18:12 -0700 (PDT) From: sthaug@nethelp.no Received: (qmail 9025 invoked by uid 1001); 2 Oct 1997 18:18:03 +0000 (GMT) To: jas@flyingfox.com Cc: freebsd-current@FreeBSD.ORG Subject: Re: Which PCI Ethernet card is best for FreeBSD-current? In-Reply-To: Your message of "Thu, 2 Oct 1997 10:17:08 -0700 (PDT)" References: <199710021717.KAA08304@biggusdiskus.flyingfox.com> X-Mailer: Mew version 1.05+ on Emacs 19.28.2 Mime-Version: 1.0 Content-Type: Text/Plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Date: Thu, 02 Oct 1997 20:18:03 +0200 Message-ID: <9023.875816283@verdi.nethelp.no> Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > On the other hand, the only quad cards I know of are based > on the DEC chip; I'll be trying out the Znyx quad card (I think) soon. We have the ZNYX 4-port 10 Mbps card, and the SMC 2-port 100 Mbps card in a FreeBSD machine here. They work very well for us. Note that SMC recently changed Ethernet controllers, and I believe their current cards are *not* based on the DEC chips. Steinar Haug, Nethelp consulting, sthaug@nethelp.no From owner-freebsd-current Thu Oct 2 12:05:23 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id MAA15740 for current-outgoing; Thu, 2 Oct 1997 12:05:23 -0700 (PDT) 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 MAA15732 for ; Thu, 2 Oct 1997 12:05:14 -0700 (PDT) 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 VAA05119; Thu, 2 Oct 1997 21:03:19 +0200 (CEST) To: sthaug@nethelp.no cc: jas@flyingfox.com, freebsd-current@FreeBSD.ORG Subject: Re: Which PCI Ethernet card is best for FreeBSD-current? In-reply-to: Your message of "Thu, 02 Oct 1997 20:18:03 +0200." <9023.875816283@verdi.nethelp.no> Date: Thu, 02 Oct 1997 21:03:19 +0200 Message-ID: <5117.875818999@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk In message <9023.875816283@verdi.nethelp.no>, sthaug@nethelp.no writes: >> On the other hand, the only quad cards I know of are based >> on the DEC chip; I'll be trying out the Znyx quad card (I think) soon. > >We have the ZNYX 4-port 10 Mbps card, and the SMC 2-port 100 Mbps card >in a FreeBSD machine here. They work very well for us. I have a machine with 4 of the ZNYX boards (16 ports total) doing the "collapsed backbone" thing. Works like a charm, and in difference from a cisco that would cost 10 times as much, you can run tcpdump and trafshow on it :-) -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." From owner-freebsd-current Thu Oct 2 12:19:23 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id MAA16553 for current-outgoing; Thu, 2 Oct 1997 12:19:23 -0700 (PDT) Received: from verdi.nethelp.no (verdi.nethelp.no [195.1.171.130]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id MAA16502 for ; Thu, 2 Oct 1997 12:18:42 -0700 (PDT) From: sthaug@nethelp.no Received: (qmail 9310 invoked by uid 1001); 2 Oct 1997 19:18:32 +0000 (GMT) To: phk@critter.freebsd.dk Cc: freebsd-current@FreeBSD.ORG Subject: Re: Which PCI Ethernet card is best for FreeBSD-current? In-Reply-To: Your message of "Thu, 02 Oct 1997 21:03:19 +0200" References: <5117.875818999@critter.freebsd.dk> X-Mailer: Mew version 1.05+ on Emacs 19.28.2 Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Date: Thu, 02 Oct 1997 21:18:32 +0200 Message-ID: <9308.875819912@verdi.nethelp.no> Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > I have a machine with 4 of the ZNYX boards (16 ports total) doing the > "collapsed backbone" thing. Works like a charm, and in difference > from a cisco that would cost 10 times as much, you can run tcpdump > and trafshow on it :-) Good point. However, I suspect you may not be able to route 16 ports at full Ethernet speeds. Have you tried saturating multiple segments with ttcp? Steinar Haug, Nethelp consulting, sthaug@nethelp.no From owner-freebsd-current Thu Oct 2 12:32:55 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id MAA17541 for current-outgoing; Thu, 2 Oct 1997 12:32:55 -0700 (PDT) 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 MAA16952 for ; Thu, 2 Oct 1997 12:25:57 -0700 (PDT) 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 VAA05185; Thu, 2 Oct 1997 21:24:47 +0200 (CEST) To: sthaug@nethelp.no cc: freebsd-current@freebsd.org Subject: Re: Which PCI Ethernet card is best for FreeBSD-current? In-reply-to: Your message of "Thu, 02 Oct 1997 21:18:32 +0200." <9308.875819912@verdi.nethelp.no> Date: Thu, 02 Oct 1997 21:24:47 +0200 Message-ID: <5183.875820287@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk In message <9308.875819912@verdi.nethelp.no>, sthaug@nethelp.no writes: >> I have a machine with 4 of the ZNYX boards (16 ports total) doing the >> "collapsed backbone" thing. Works like a charm, and in difference >> from a cisco that would cost 10 times as much, you can run tcpdump >> and trafshow on it :-) > >Good point. However, I suspect you may not be able to route 16 ports >at full Ethernet speeds. Have you tried saturating multiple segments >with ttcp? So far that is not a concern, and in any real networks, if you were seing that level of trafic, you would upgrade to any >10Mbit/sec media RSN. -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." From owner-freebsd-current Thu Oct 2 12:44:32 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id MAA18185 for current-outgoing; Thu, 2 Oct 1997 12:44:32 -0700 (PDT) Received: from cod.nosc.mil (root@cod.nosc.mil [128.49.4.5]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id MAA18174 for ; Thu, 2 Oct 1997 12:44:27 -0700 (PDT) Received: from [128.49.16.48] (aegis.nosc.mil [128.49.16.48]) by cod.nosc.mil (8.8.7/8.8.7) with ESMTP id MAA15784; Thu, 2 Oct 1997 12:42:53 -0700 (PDT) X-Sender: gshaffer@cod.nosc.mil Message-Id: In-Reply-To: <199710021851.UAA18569@greenpeace.grondar.za> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Thu, 2 Oct 1997 12:40:23 -0700 To: Mark Murray From: Greg Shaffer Subject: Re: Making world on an SMP system. Cc: current@FreeBSD.Org, gshaffer@cod.nosc.mil Sender: owner-freebsd-current@FreeBSD.Org X-Loop: FreeBSD.org Precedence: bulk >Hi > >I am a recent convert to the world of SMP. Much of what I do on this >board (a Giga-Byte GA586DX w 2xP5/200) is a _helluva_ lot easier, >now that the load average is a bit more reasonable. (I do real number- >crunching here :-) ). > >One thing that I have found to be frought with danger is large makes >and "make -j N" (N an int). > >EG: make -j2 world usually falls over in a couple of minutes. It seems >1) either the dependancies are not SMP-friendly, or >2) make is broken. > >I suspect 1). Is this a known "thing"? Is anyone working on it? ISTR >that PHK was into massively parallel makes a few years ago (?). > >Are you (PHK) still doing stuff there? > >M >-- >Mark Murray >Join the anti-SPAM movement: http://www.cauce.org Several months ago there was some discussion on this. Someone actually went through the *.mk and make files to make them parallel safe (i.e. make -jN). The patches really improved the make world time. As far as I know these patches were never committed! Greg Shaffer From owner-freebsd-current Thu Oct 2 13:04:03 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id NAA19336 for current-outgoing; Thu, 2 Oct 1997 13:04:03 -0700 (PDT) Received: from gratis.grondar.za (gratis.grondar.za [196.7.18.133]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id NAA19298 for ; Thu, 2 Oct 1997 13:03:54 -0700 (PDT) Received: from greenpeace.grondar.za (tzdWwcWWjumTi09qAXPTGMcH+Lt7wjKp@greenpeace.grondar.za [196.7.18.132]) by gratis.grondar.za (8.8.7/8.8.7) with ESMTP id VAA24748; Thu, 2 Oct 1997 21:53:36 +0200 (SAT) Received: from greenpeace.grondar.za (MBkJ093ci/nUkoRbAZzUl6XL3n6CwKwP@localhost [127.0.0.1]) by greenpeace.grondar.za (8.8.7/8.8.7) with ESMTP id VAA22187; Thu, 2 Oct 1997 21:53:42 +0200 (SAT) Message-Id: <199710021953.VAA22187@greenpeace.grondar.za> To: Greg Shaffer cc: current@FreeBSD.Org, gshaffer@cod.nosc.mil Subject: Re: Making world on an SMP system. Date: Thu, 02 Oct 1997 21:53:41 +0200 From: Mark Murray Sender: owner-freebsd-current@FreeBSD.Org X-Loop: FreeBSD.org Precedence: bulk Greg Shaffer wrote: > Several months ago there was some discussion on this. Someone actually > went through the *.mk and make files to make them parallel safe (i.e. > make -jN). The patches really improved the make world time. As far as > I know these patches were never committed! Thanks! Time to search old mail, methinks. M -- Mark Murray Join the anti-SPAM movement: http://www.cauce.org From owner-freebsd-current Thu Oct 2 14:03:19 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id OAA22894 for current-outgoing; Thu, 2 Oct 1997 14:03:19 -0700 (PDT) Received: from hetzels (171-158-235.ipt.aol.com [152.171.158.235]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id OAA22863; Thu, 2 Oct 1997 14:03:03 -0700 (PDT) From: "Scot W. Hetzel" To: "Stable" , "Current" Subject: CTM patch level added to newvers.sh Date: Thu, 2 Oct 1997 15:07:13 -0500 Message-ID: <01bccf6e$c649aa80$0400000a@hetzels> 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 I am currently tracking 2.2-STABLE and use the following patch to newvers.sh to have my kernel indicate what CTM patch was used to create it. example: Copyright (c) 1992-1997 FreeBSD Inc. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 2.2-STABLE (0448) #0: Fri Sep 26 21:16:21 CDT 1997 ^^^^^^^ Last CTM update applied 0448. The CTM value will only be shown if the user is using STABLE or CURRENT and has the .ctm_status file in the src directory. Could the attched patch be applied to the src tree for both CURRENT's and STABLE's newvers.sh? Also, is there a better way of locating the .ctm_status file (look at variable S1)? Thanks, Scot ------cut here---- *** /sys/conf/newvers.sh.orig Thu Jun 5 18:01:42 1997 --- /sys/conf/newvers.sh Thu Oct 2 14:55:05 1997 *************** *** 39,47 **** --- 39,62 ---- BRANCH="STABLE" RELEASE="${REVISION}-${BRANCH}" SNAPDATE="" + + #Location of .ctm_status file + S1="../../.." + CTM_STATUS="${S1}/.ctm_status" + if [ "X${SNAPDATE}" != "X" ]; then RELEASE="${RELEASE}-${SNAPDATE}" fi + + #Add CTM patch level for the STABLE or CURRENT Branches + #Only if we are using CTM (.ctm_status exists in the source directory) + if [ "${BRANCH}" = "STABLE" ] || [ "${BRANCH}" = "CURRENT" ]; then + if [ -f ${CTM_STATUS} ]; then + sCTM=`awk '{ printf "%04d", $2 }' ${CTM_STATUS}` + RELEASE="${RELEASE} (${sCTM})" + fi + fi + VERSION="${TYPE} ${RELEASE}" RELDATE="222001" ------cut here---- From owner-freebsd-current Thu Oct 2 14:05:42 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id OAA23107 for current-outgoing; Thu, 2 Oct 1997 14:05:42 -0700 (PDT) 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 OAA23096 for ; Thu, 2 Oct 1997 14:05:31 -0700 (PDT) Received: from Mars.mcs.net (karl@Mars.mcs.net [192.160.127.85]) by Kitten.mcs.com (8.8.5/8.8.2) with ESMTP id QAA02701 for ; Thu, 2 Oct 1997 16:05:30 -0500 (CDT) Received: (from karl@localhost) by Mars.mcs.net (8.8.7/8.8.2) id QAA09144; Thu, 2 Oct 1997 16:05:30 -0500 (CDT) Message-ID: <19971002160530.23364@Mars.Mcs.Net> Date: Thu, 2 Oct 1997 16:05:30 -0500 From: Karl Denninger To: current@freebsd.org Subject: Argh! Now what?! Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.64 Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by hub.freebsd.org id OAA23098 Sender: owner-freebsd-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk $ make world n/make/lst.lib/lstAtFront.c /usr/src/usr.bin/make/lst.lib/lstClose.c /usr/src/usr.bin/make/lst.lib/lstConcat.c /usr/src/usr.bin/make/lst.lib/lstDatum.c /usr/src/usr.bin/make/lst.lib/lstDeQueue.c /usr/src/usr.bin/make/lst.lib/lstDestroy.c /usr/src/usr.bin/make/lst.lib/lstDupl.c /usr/src/usr.bin/make/lst.lib/lstEnQueue.c /usr/src/usr.bin/make/lst.lib/lstFind.c /usr/src/usr.bin/make/lst.lib/lstFindFrom.c /usr/src/usr.bin/make/lst.lib/lstFirst.c /usr/src/usr.bin/make/lst.lib/lstForEach.c /usr/src/usr.bin/make/lst.lib/lstForEachFrom.c /usr/src/usr.bin/make/lst.lib/lstInit.c /usr/src/usr.bin/make/lst.lib/lstInsert.c /usr/src/usr.bin/make/lst.lib/lstIsAtEnd.c /usr/src/usr.bin/make/lst.lib/lstIsEmpty.c /usr/src/usr.bin/make/lst.lib/lstLast.c /usr/src/usr.bin/make/lst.lib/lstMember.c /usr/src/usr.bin/make/lst.lib/lstNext.c /usr/src/usr.bin/make/lst.lib/lstOpen.c /usr/src/usr.bin/make/lst.lib/lstRemove.c /usr/src/usr.bin/make/lst.lib/lstReplace.c /usr/src/usr.bin/make/lst.lib/lstSucc.c /usr/bin/mkdep: cannot create _mkdep16352: directory nonexistent *** Error code 2 Stop. *** Error code 1 Stop. *** Error code 1 Stop. Huh? -- -- Karl Denninger (karl@MCS.Net)| MCSNet - Serving Chicagoland and Wisconsin http://www.mcs.net/~karl | T1's from $600 monthly to FULL DS-3 Service | NEW! K56Flex modem support is now available Voice: [+1 312 803-MCS1 x219]| 56kbps DIGITAL ISDN DOV on analog lines! Fax: [+1 312 803-4929] | 2 FULL DS-3 Internet links; 400Mbps B/W Internal From owner-freebsd-current Thu Oct 2 14:23:43 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id OAA24160 for current-outgoing; Thu, 2 Oct 1997 14:23:43 -0700 (PDT) Received: from mail.uniserve.com (dns1-van.uniserve.com [204.244.163.48]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id OAA24146 for ; Thu, 2 Oct 1997 14:23:32 -0700 (PDT) Received: from shell.uniserve.com [204.244.210.252] by mail.uniserve.com with smtp (Exim 1.70 #1) id 0xGsfH-0007Ux-00; Thu, 2 Oct 1997 14:20:07 -0700 Date: Thu, 2 Oct 1997 14:20:03 -0700 (PDT) From: Tom To: Poul-Henning Kamp cc: sthaug@nethelp.no, jas@flyingfox.com, freebsd-current@freebsd.org Subject: Re: Which PCI Ethernet card is best for FreeBSD-current? In-Reply-To: <5117.875818999@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 On Thu, 2 Oct 1997, Poul-Henning Kamp wrote: > In message <9023.875816283@verdi.nethelp.no>, sthaug@nethelp.no writes: > >> On the other hand, the only quad cards I know of are based > >> on the DEC chip; I'll be trying out the Znyx quad card (I think) soon. > > > >We have the ZNYX 4-port 10 Mbps card, and the SMC 2-port 100 Mbps card > >in a FreeBSD machine here. They work very well for us. > > I have a machine with 4 of the ZNYX boards (16 ports total) doing the > "collapsed backbone" thing. Works like a charm, and in difference > from a cisco that would cost 10 times as much, you can run tcpdump > and trafshow on it :-) I would have liked to have been able to use a solution like that. However, currently ethernet interfaces that do not have carrier/link active, still show us UP. I wish that loss of carrier/link would force the interface into a DOWN state automatically. I realize this would require some driver changes. Why do I want this? Because I can tell remotely that a particular interface is properly connected, rather to try to figure out ping'able systems on that segment. Also, this would work very nicely with gated. Gated will automatically stop advertising routes to a DOWN interface. This is needed if you want to have multiple connections to a network, as you don't want to advertising a route to a failed interface, when other router(s) may still have an active connection to that network. > -- > Poul-Henning Kamp FreeBSD coreteam member > phk@FreeBSD.ORG "Real hackers run -current on their laptop." > Tom From owner-freebsd-current Thu Oct 2 14:32:03 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id OAA24869 for current-outgoing; Thu, 2 Oct 1997 14:32:03 -0700 (PDT) Received: from mexico.brainstorm.eu.org (root@mexico.brainstorm.fr [193.56.58.253]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id OAA24822 for ; Thu, 2 Oct 1997 14:31:54 -0700 (PDT) Received: from brasil.brainstorm.eu.org (brasil.brainstorm.fr [193.56.58.33]) by mexico.brainstorm.eu.org (8.8.4/8.8.4) with ESMTP id XAA10662 for ; Thu, 2 Oct 1997 23:31:53 +0200 Received: (from uucp@localhost) by brasil.brainstorm.eu.org (8.8.6/brasil-1.2) with UUCP id XAA18814 for current@FreeBSD.ORG; Thu, 2 Oct 1997 23:31:12 +0200 Received: (from roberto@localhost) by keltia.freenix.fr (8.8.7/keltia-2.10/nospam) id VAA04690; Thu, 2 Oct 1997 21:43:16 +0200 (CEST) Message-ID: <19971002214316.29628@keltia.freenix.fr> Date: Thu, 2 Oct 1997 21:43:16 +0200 From: Ollivier Robert To: current@FreeBSD.ORG Subject: Re: Geometry weirdness with sysinstall/libdisk References: <19970930223542.44057@keltia.freenix.fr> <19971001072648.MU20136@uriah.heep.sax.de> <19971001040119.61326@gaffaneys.com> <19971002012804.28680@keltia.freenix.fr> <19971002084852.PP26017@uriah.heep.sax.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.84 In-Reply-To: <19971002084852.PP26017@uriah.heep.sax.de>; from J Wunsch on Thu, Oct 02, 1997 at 08:48:52AM +0200 X-Operating-System: FreeBSD 3.0-CURRENT Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk According to J Wunsch: > These are partitions, not slices. You ought to learn the difference > by now... Whatever suits you. The problem's not here. There is one slice with 8 partitions in it. Why sysinstall is not able to _see_ them ??? -- Ollivier ROBERT -=- FreeBSD: There are no limits -=- roberto@keltia.freenix.fr FreeBSD keltia.freenix.fr 3.0-CURRENT #35: Sun Sep 21 19:28:07 CEST 1997 From owner-freebsd-current Thu Oct 2 14:42:38 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id OAA25446 for current-outgoing; Thu, 2 Oct 1997 14:42:38 -0700 (PDT) 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 OAA25050 for ; Thu, 2 Oct 1997 14:35:40 -0700 (PDT) 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 XAA05654; Thu, 2 Oct 1997 23:34:10 +0200 (CEST) To: Tom cc: sthaug@nethelp.no, jas@flyingfox.com, freebsd-current@freebsd.org Subject: Re: Which PCI Ethernet card is best for FreeBSD-current? In-reply-to: Your message of "Thu, 02 Oct 1997 14:20:03 PDT." Date: Thu, 02 Oct 1997 23:34:10 +0200 Message-ID: <5652.875828050@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk In message , Tom w rites: > >On Thu, 2 Oct 1997, Poul-Henning Kamp wrote: > >> In message <9023.875816283@verdi.nethelp.no>, sthaug@nethelp.no writes: >> >> On the other hand, the only quad cards I know of are based >> >> on the DEC chip; I'll be trying out the Znyx quad card (I think) soon. >> > >> >We have the ZNYX 4-port 10 Mbps card, and the SMC 2-port 100 Mbps card >> >in a FreeBSD machine here. They work very well for us. >> >> I have a machine with 4 of the ZNYX boards (16 ports total) doing the >> "collapsed backbone" thing. Works like a charm, and in difference >> from a cisco that would cost 10 times as much, you can run tcpdump >> and trafshow on it :-) > > I would have liked to have been able to use a solution like that. >However, currently ethernet interfaces that do not have carrier/link >active, still show us UP. I wish that loss of carrier/link would force >the interface into a DOWN state automatically. I realize this would >require some driver changes. Well, go for it :-) -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." From owner-freebsd-current Thu Oct 2 15:07:14 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id PAA26651 for current-outgoing; Thu, 2 Oct 1997 15:07:14 -0700 (PDT) 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 PAA26627 for ; Thu, 2 Oct 1997 15:07:02 -0700 (PDT) Received: from gid.co.uk (uucp@localhost) by isbalham.ist.co.uk (8.8.4/8.8.4) with UUCP id WAA27398; Thu, 2 Oct 1997 22:56:25 +0100 (BST) Received: from [194.32.164.2] by seagoon.gid.co.uk; Thu, 2 Oct 1997 23:01:30 +0100 X-Sender: rb@194.32.164.1 Message-Id: In-Reply-To: <19971002160530.23364@Mars.Mcs.Net> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Thu, 2 Oct 1997 22:54:56 +0100 To: Karl Denninger , current@FreeBSD.ORG From: Bob Bishop Subject: Re: Argh! Now what?! Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk At 10:05 pm +0100 2/10/97, Karl Denninger wrote: >$ make world > >[...] >/usr/bin/mkdep: cannot create _mkdep16352: directory nonexistent >*** Error code 2 > >Stop. [etc] Me too, it's happening every *(&^$ time now... -- 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 Thu Oct 2 15:11:06 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id PAA26823 for current-outgoing; Thu, 2 Oct 1997 15:11:06 -0700 (PDT) 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 PAA26816 for ; Thu, 2 Oct 1997 15:11:00 -0700 (PDT) Received: from Mars.mcs.net (karl@Mars.mcs.net [192.160.127.85]) by Kitten.mcs.com (8.8.5/8.8.2) with ESMTP id RAA06320; Thu, 2 Oct 1997 17:10:50 -0500 (CDT) Received: (from karl@localhost) by Mars.mcs.net (8.8.7/8.8.2) id RAA12030; Thu, 2 Oct 1997 17:10:50 -0500 (CDT) Message-ID: <19971002171050.55219@Mars.Mcs.Net> Date: Thu, 2 Oct 1997 17:10:50 -0500 From: Karl Denninger To: Bob Bishop Cc: Karl Denninger , current@FreeBSD.ORG Subject: Re: Argh! Now what?! References: <19971002160530.23364@Mars.Mcs.Net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.64 In-Reply-To: ; from Bob Bishop on Thu, Oct 02, 1997 at 10:54:56PM +0100 Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Thu, Oct 02, 1997 at 10:54:56PM +0100, Bob Bishop wrote: > At 10:05 pm +0100 2/10/97, Karl Denninger wrote: > >$ make world > > > >[...] > >/usr/bin/mkdep: cannot create _mkdep16352: directory nonexistent > >*** Error code 2 > > > >Stop. > [etc] > > Me too, it's happening every *(&^$ time now... As someone else emailed me: chflags noschg /usr/obj rm -rf /usr/obj .... make world How schg got set on /usr/obj is another matter. -- -- Karl Denninger (karl@MCS.Net)| MCSNet - Serving Chicagoland and Wisconsin http://www.mcs.net/~karl | T1's from $600 monthly to FULL DS-3 Service | NEW! K56Flex modem support is now available Voice: [+1 312 803-MCS1 x219]| 56kbps DIGITAL ISDN DOV on analog lines! Fax: [+1 312 803-4929] | 2 FULL DS-3 Internet links; 400Mbps B/W Internal From owner-freebsd-current Thu Oct 2 15:22:05 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id PAA27418 for current-outgoing; Thu, 2 Oct 1997 15:22:05 -0700 (PDT) Received: from brane.digs.iafrica.com (brane.digs.iafrica.com [196.7.162.25]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id PAA27413 for ; Thu, 2 Oct 1997 15:21:57 -0700 (PDT) Received: from iang by brane.digs.iafrica.com with local (Exim 1.71 #1) id 0xGtcV-0000iI-00; Fri, 3 Oct 1997 00:21:19 +0200 Subject: Re: Argh! Now what?! In-Reply-To: from Bob Bishop at "Oct 2, 97 10:54:56 pm" To: rb@gid.co.uk (Bob Bishop) Date: Fri, 3 Oct 1997 00:21:18 +0200 (SAT) Cc: karl@Mcs.Net, 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 Message-Id: From: Ian Freislich Sender: owner-freebsd-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Bob Bishop spake thusly: > At 10:05 pm +0100 2/10/97, Karl Denninger wrote: > >$ make world > > > >[...] > >/usr/bin/mkdep: cannot create _mkdep16352: directory nonexistent > >*** Error code 2 > > Me too, it's happening every *(&^$ time now... Apparently there was some explanation of this in an earlier thread, which I absent-mindedly deleted. Some people have had some success with the following, until the problem gets sorted out: [brane] /usr/obj/usr/src # chflags -R noschg tmp [brane] /usr/obj/usr/src # cd - [brane] /usr/obj # rm -r usr/ [brane] /usr/obj # cd ../src [brane] /usr/src # nohup time make world & -- igf (Ian Freislich) From owner-freebsd-current Thu Oct 2 15:27:16 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id PAA27683 for current-outgoing; Thu, 2 Oct 1997 15:27:16 -0700 (PDT) Received: from time.cdrom.com (time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id PAA27676 for ; Thu, 2 Oct 1997 15:27:11 -0700 (PDT) Received: from time.cdrom.com (localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.7/8.6.9) with ESMTP id PAA23966; Thu, 2 Oct 1997 15:26:20 -0700 (PDT) To: Greg Shaffer cc: Mark Murray , current@FreeBSD.ORG, gshaffer@cod.nosc.mil Subject: Re: Making world on an SMP system. In-reply-to: Your message of "Thu, 02 Oct 1997 12:40:23 PDT." Date: Thu, 02 Oct 1997 15:26:19 -0700 Message-ID: <23948.875831179@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > Several months ago there was some discussion on this. Someone actually > went through the *.mk and make files to make them parallel safe (i.e. > make -jN). The patches really improved the make world time. As far as > I know these patches were never committed! What was the PR# for this? I don't remember seeing one. :( Jordan From owner-freebsd-current Thu Oct 2 15:28:05 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id PAA27760 for current-outgoing; Thu, 2 Oct 1997 15:28:05 -0700 (PDT) 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 PAA27724 for ; Thu, 2 Oct 1997 15:27:58 -0700 (PDT) Received: from Mars.mcs.net (karl@Mars.mcs.net [192.160.127.85]) by Kitten.mcs.com (8.8.5/8.8.2) with ESMTP id RAA07528; Thu, 2 Oct 1997 17:27:57 -0500 (CDT) Received: (from karl@localhost) by Mars.mcs.net (8.8.7/8.8.2) id RAA12631; Thu, 2 Oct 1997 17:27:57 -0500 (CDT) Message-ID: <19971002172756.26631@Mars.Mcs.Net> Date: Thu, 2 Oct 1997 17:27:56 -0500 From: Karl Denninger To: "Justin T. Gibbs" Cc: current@FreeBSD.ORG Subject: Re: cvs commit: src/sys/i386/isa apic_vector.s icu_vector.s References: <199709281930.MAA10261@freefall.freebsd.org> <199709281942.NAA14122@pluto.plutotech.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.64 In-Reply-To: <199709281942.NAA14122@pluto.plutotech.com>; from Justin T. Gibbs on Sun, Sep 28, 1997 at 01:42:33PM -0600 Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk It looks like in fact it did. Now if we can find a way around the cache coherency problems in NFS we'll be reasonably-well set. The suggested "-kk" fix didn't, so we're still in trouble there. Is there ANY fix for this? NQNFS? Anything? Or is it just hosed right now? The client and server are both FreeBSD, although the server is running code that's a few months old, so if it has to be upgraded that's possible (but a pain in the butt due to the fact that rebooting those servers is INCREDIBLY unpopular, not to mention the risk if the code that gets on them is *bad* in some way). -- -- Karl Denninger (karl@MCS.Net)| MCSNet - Serving Chicagoland and Wisconsin http://www.mcs.net/~karl | T1's from $600 monthly to FULL DS-3 Service | NEW! K56Flex modem support is now available Voice: [+1 312 803-MCS1 x219]| 56kbps DIGITAL ISDN DOV on analog lines! Fax: [+1 312 803-4929] | 2 FULL DS-3 Internet links; 400Mbps B/W Internal On Sun, Sep 28, 1997 at 01:42:33PM -0600, Justin T. Gibbs wrote: > Those of you complaining of "mysterious hangs", NFS related or otherwise, > this change will probably fix your problem. > > >gibbs 1997/09/28 12:30:03 PDT > > > > Modified files: > > sys/i386/isa apic_vector.s icu_vector.s > > Log: > > Fix a serious bug I introduced while adding in support for CAM interrupts. > > It seems I didn't count my 0's properly when adding the new masks into > > icu_vector.s pushing SWI_AST_MASK off the end of the array and screwing > > up the indexing for SWI_CLOCK_MASK. > > > > Fix the bug icu_vector.s and also reformat the code in both icu_vector.s and > > apic_vector.s so that it will be much harder to make the same mistake in > > the future. > > > > Submitted by: Bruce Evans > > > > Revision Changes Path > > 1.23 +3 -2 src/sys/i386/isa/apic_vector.s > > 1.6 +7 -5 src/sys/i386/isa/icu_vector.s > > > > -- > Justin T. Gibbs > =========================================== > FreeBSD: Turning PCs into workstations > =========================================== > > From owner-freebsd-current Thu Oct 2 15:32:41 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id PAA28117 for current-outgoing; Thu, 2 Oct 1997 15:32:41 -0700 (PDT) Received: from gratis.grondar.za (gratis.grondar.za [196.7.18.133]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id PAA28108 for ; Thu, 2 Oct 1997 15:32:31 -0700 (PDT) Received: from greenpeace.grondar.za (vnCUXq8Zb2OR9H1rjt82fNqwg6wfUBb3@greenpeace.grondar.za [196.7.18.132]) by gratis.grondar.za (8.8.7/8.8.7) with ESMTP id AAA00382; Fri, 3 Oct 1997 00:31:29 +0200 (SAT) Received: from greenpeace.grondar.za (NycFPvUgL3TNzzWZu3574K4jkFA0rIhi@localhost [127.0.0.1]) by greenpeace.grondar.za (8.8.7/8.8.7) with ESMTP id AAA10706; Fri, 3 Oct 1997 00:31:28 +0200 (SAT) Message-Id: <199710022231.AAA10706@greenpeace.grondar.za> To: "Jordan K. Hubbard" cc: Greg Shaffer , current@FreeBSD.ORG, gshaffer@cod.nosc.mil Subject: Re: Making world on an SMP system. Date: Fri, 03 Oct 1997 00:31:21 +0200 From: Mark Murray Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk "Jordan K. Hubbard" wrote: > > Several months ago there was some discussion on this. Someone actually > > went through the *.mk and make files to make them parallel safe (i.e. > > make -jN). The patches really improved the make world time. As far as > > I know these patches were never committed! > > What was the PR# for this? I don't remember seeing one. :( I'll submit one tomorrow when the make world that is using them works :-) M -- Mark Murray Join the anti-SPAM movement: http://www.cauce.org From owner-freebsd-current Thu Oct 2 16:01:43 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id QAA29484 for current-outgoing; Thu, 2 Oct 1997 16:01:43 -0700 (PDT) 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 QAA29467 for ; Thu, 2 Oct 1997 16:01:32 -0700 (PDT) Received: from chop.cdsnet.net (chop.cdsnet.net [204.118.244.3]) by mail.cdsnet.net (8.8.6/8.8.6) with ESMTP id QAA01690; Thu, 2 Oct 1997 16:01:27 -0700 (PDT) Received: from nowin (1Cust76.max3.boston.ma.ms.uu.net [153.35.70.204]) by chop.cdsnet.net (8.8.5/8.8.5) with SMTP id QAA05129; Thu, 2 Oct 1997 16:01:24 -0700 (PDT) Message-Id: <3.0.3.32.19971002185741.0305e1c4@ranier.altavista-software.com> X-Sender: 3ampop@ranier.altavista-software.com X-Mailer: QUALCOMM Windows Eudora Pro Version 3.0.3 (32) Date: Thu, 02 Oct 1997 18:57:41 -0400 To: Tom From: Matt Thomas Subject: Re: Which PCI Ethernet card is best for FreeBSD-current? Cc: freebsd-current@FreeBSD.ORG In-Reply-To: References: <5117.875818999@critter.freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk At 02:20 PM 10/2/97 -0700, Tom wrote: > >On Thu, 2 Oct 1997, Poul-Henning Kamp wrote: > >> In message <9023.875816283@verdi.nethelp.no>, sthaug@nethelp.no writes: >> >> On the other hand, the only quad cards I know of are based >> >> on the DEC chip; I'll be trying out the Znyx quad card (I think) soon. >> > >> >We have the ZNYX 4-port 10 Mbps card, and the SMC 2-port 100 Mbps card >> >in a FreeBSD machine here. They work very well for us. >> >> I have a machine with 4 of the ZNYX boards (16 ports total) doing the >> "collapsed backbone" thing. Works like a charm, and in difference >> from a cisco that would cost 10 times as much, you can run tcpdump >> and trafshow on it :-) > > I would have liked to have been able to use a solution like that. >However, currently ethernet interfaces that do not have carrier/link >active, still show us UP. I wish that loss of carrier/link would force >the interface into a DOWN state automatically. I realize this would >require some driver changes. FWIW, the ifmedia already supports this. Depending on if the link is up, media will have IFM_ALIVE set or clear. -- Matt Thomas Internet: matt@3am-software.com 3am Software Foundry WWW URL: http://www.3am-software.com/bio/matt.html Nashua, NH Disclaimer: I disavow all knowledge of this message From owner-freebsd-current Thu Oct 2 16:21:31 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id QAA00687 for current-outgoing; Thu, 2 Oct 1997 16:21:31 -0700 (PDT) Received: from mail.uniserve.com (dns1-van.uniserve.com [204.244.163.48]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id QAA00678 for ; Thu, 2 Oct 1997 16:21:22 -0700 (PDT) Received: from shell.uniserve.com [204.244.210.252] by mail.uniserve.com with smtp (Exim 1.70 #1) id 0xGuYY-00007q-00; Thu, 2 Oct 1997 16:21:18 -0700 Date: Thu, 2 Oct 1997 16:21:14 -0700 (PDT) From: Tom To: Matt Thomas cc: freebsd-current@freebsd.org Subject: Re: Which PCI Ethernet card is best for FreeBSD-current? In-Reply-To: <3.0.3.32.19971002185741.0305e1c4@ranier.altavista-software.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 Thu, 2 Oct 1997, Matt Thomas wrote: > At 02:20 PM 10/2/97 -0700, Tom wrote: > > > >On Thu, 2 Oct 1997, Poul-Henning Kamp wrote: > > > >> In message <9023.875816283@verdi.nethelp.no>, sthaug@nethelp.no writes: > >> >> On the other hand, the only quad cards I know of are based > >> >> on the DEC chip; I'll be trying out the Znyx quad card (I think) soon. > >> > > >> >We have the ZNYX 4-port 10 Mbps card, and the SMC 2-port 100 Mbps card > >> >in a FreeBSD machine here. They work very well for us. > >> > >> I have a machine with 4 of the ZNYX boards (16 ports total) doing the > >> "collapsed backbone" thing. Works like a charm, and in difference > >> from a cisco that would cost 10 times as much, you can run tcpdump > >> and trafshow on it :-) > > > > I would have liked to have been able to use a solution like that. > >However, currently ethernet interfaces that do not have carrier/link > >active, still show us UP. I wish that loss of carrier/link would force > >the interface into a DOWN state automatically. I realize this would > >require some driver changes. > > FWIW, the ifmedia already supports this. Depending on if the > link is up, media will have IFM_ALIVE set or clear. But that won't translate into a UP or DOWN state? Somehow gated gets the interface states (via routing socket?). How can I read that state via a user-mode program? I think it would be great to add some indication to ifconfig to indicate that the physical layer is up. > -- > Matt Thomas Internet: matt@3am-software.com > 3am Software Foundry WWW URL: http://www.3am-software.com/bio/matt.html > Nashua, NH Disclaimer: I disavow all knowledge of this message > Tom From owner-freebsd-current Thu Oct 2 16:28:13 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id QAA01111 for current-outgoing; Thu, 2 Oct 1997 16:28:13 -0700 (PDT) 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 QAA01099 for ; Thu, 2 Oct 1997 16:28:05 -0700 (PDT) Received: from chop.cdsnet.net (chop.cdsnet.net [204.118.244.3]) by mail.cdsnet.net (8.8.6/8.8.6) with ESMTP id QAA06691; Thu, 2 Oct 1997 16:28:03 -0700 (PDT) Received: from nowin (1Cust76.max3.boston.ma.ms.uu.net [153.35.70.204]) by chop.cdsnet.net (8.8.5/8.8.5) with SMTP id QAA11505; Thu, 2 Oct 1997 16:28:00 -0700 (PDT) Message-Id: <3.0.3.32.19971002192513.006f42cc@ranier.altavista-software.com> X-Sender: 3ampop@ranier.altavista-software.com X-Mailer: QUALCOMM Windows Eudora Pro Version 3.0.3 (32) Date: Thu, 02 Oct 1997 19:25:13 -0400 To: Tom From: Matt Thomas Subject: Re: Which PCI Ethernet card is best for FreeBSD-current? Cc: freebsd-current@FreeBSD.ORG In-Reply-To: References: <3.0.3.32.19971002185741.0305e1c4@ranier.altavista-software.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:21 PM 10/2/97 -0700, Tom wrote: > >On Thu, 2 Oct 1997, Matt Thomas wrote: > >> FWIW, the ifmedia already supports this. Depending on if the >> link is up, media will have IFM_ALIVE set or clear. > > But that won't translate into a UP or DOWN state? Somehow gated gets >the interface states (via routing socket?). How can I read that state >via a user-mode program? Use the SIOCGIFMEDIA ioctl. > I think it would be great to add some indication to ifconfig to indicate >that the physical layer is up. ifconfig -m de0 de1: flags=8863 mtu 1500 address: 00:00:f8:02:c0:cc media: autoselect (10baseT/UTP) status: active supported media: autoselect 100baseTX 100baseTX 10baseT/UTP 10baseT/UTP (notice the status: alive) -- Matt Thomas Internet: matt@3am-software.com 3am Software Foundry WWW URL: http://www.3am-software.com/bio/matt.html Nashua, NH Disclaimer: I disavow all knowledge of this message From owner-freebsd-current Thu Oct 2 17:41:12 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id RAA05023 for current-outgoing; Thu, 2 Oct 1997 17:41:12 -0700 (PDT) Received: from sendero-ppp.i-connect.net (sendero-ppp.i-Connect.Net [206.190.143.100]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id RAA04999 for ; Thu, 2 Oct 1997 17:41:06 -0700 (PDT) Received: (qmail 14174 invoked by uid 1000); 3 Oct 1997 00:41:25 -0000 Message-ID: X-Mailer: XFMail 1.2-alpha-092597 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <199710020556.JAA12728@sinbin.demos.su> Date: Thu, 02 Oct 1997 17:41:25 -0700 (PDT) Organization: Atlas Telecom From: Simon Shapiro To: (Alex G. Bulushev) Subject: Re: problem with free() and junk pointers? Cc: current@FreeBSD.ORG, (David Langford) Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Hi Alex G. Bulushev; On 02-Oct-97 you wrote: > > > > > > I have a three week old current box that I am trying to > > get more current but I keep getting the following: > > > > make in free(): warning: modified (chunk-) pointer. > > make in free(): warning: junk pointer, too low to make sense. > > Segmentation fault - core dumped > > > > > > This seems to be a random occurance and makes getting through a make > > world > > a wee bit of a pain. > > > > Do I have a bad library or could this be a sign of bad memory? > > I dont get the normal "cc died due to signal such and such" so I was > > disconting the memory bit but.... > > > > this is feature :) for fsck -p via reboot this err occure for > big ( >=8 GB ) disk with big number of inodes ... >From sendero's /etc/rc: if [ $1x = autobootx ]; then echo Automatic reboot in progress... ulimit -t unlimited ulimit -f unlimited ulimit -d unlimited ulimit -s unlimited ulimit -c unlimited ulimit -m unlimited ulimit -l unlimited ulimit -u unlimited ulimit -h unlimited fsck -p case $? in 0) ;; Works every time. One of these ulimit is wrong. Too lazy to find which :-) --- Sincerely Yours, Simon Shapiro Atlas Telecom Senior Architect 14355 SW Allen Blvd., Suite 130 Beaverton OR 97005 Shimon@i-Connect.Net Voice: 503.799.2313 From owner-freebsd-current Thu Oct 2 17:41:13 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id RAA05032 for current-outgoing; Thu, 2 Oct 1997 17:41:13 -0700 (PDT) Received: from sendero-ppp.i-connect.net (sendero-ppp.i-Connect.Net [206.190.143.100]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id RAA04994 for ; Thu, 2 Oct 1997 17:41:05 -0700 (PDT) Received: (qmail 14165 invoked by uid 1000); 3 Oct 1997 00:41:25 -0000 Message-ID: X-Mailer: XFMail 1.2-alpha-092597 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit MIME-Version: 1.0 Date: Thu, 02 Oct 1997 17:41:25 -0700 (PDT) Organization: Atlas Telecom From: Simon Shapiro To: freebsd-current@freebsd.org Subject: Make depend is broken? Still?? Sender: owner-freebsd-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi Y'all, I may dare say there is a possibility of a bug in the -current main makefile; Last time I did ``make buildworld'' was yesterday. I am trying it today, and within minutes I have: /usr/obj/usr/src/3.0/src/usr.bin/make created for /usr/src/3.0/src/usr.bin/make rm -f .depend mkdep -f .depend -a -I/usr/src/3.0/src/usr.bin/make -I/usr/obj/usr/src/3.0/src/tmp/usr/include /usr/src/3.0/src/usr.bin/make/arch.c /usr/src/3.0/src/usr.bin/make/buf.c /usr/src/3.0/src/usr.bin/make/compat.c /usr/src/3.0/src/usr.bin/make/cond.c /usr/src/3.0/src/usr.bin/make/dir.c /usr/src/3.0/src/usr.bin/make/for.c /usr/src/3.0/src/usr.bin/make/hash.c /usr/src/3.0/src/usr.bin/make/job.c /usr/src/3.0/src/usr.bin/make/main.c /usr/src/3.0/src/usr.bin/make/make.c /usr/src/3.0/src/usr.bin/make/parse.c /usr/src/3.0/src/usr.bin/make/str.c /usr/src/3.0/src/usr.bin/make/suff.c /usr/src/3.0/src/usr.bin/make/targ.c /usr/src/3.0/src/usr.bin/make/var.c /usr/src/3.0/src/usr.bin/make/util.c /usr/src/3.0/src/usr.bin/make/lst.lib/lstAppend.c /usr/src/3.0/src/usr.bin/make/lst.lib/lstAtEnd.c /usr/src/3.0/src/usr.bin/make/lst.lib/lstAtFront.c /usr/src/3.0/src/usr.bin/make/lst.lib/lstClose.c /usr/src/3.0/src/usr.bin/make/lst.lib/lstConcat.c /usr/src/3.0/src/usr.bin/make/lst.lib/lstDatum.c /usr/src/3.0/src/usr.bin/make/lst.lib/lstDeQueue.c /usr/src/3.0/src/usr.bin/make/lst.lib/lstDestroy.c /usr/src/3.0/src/usr.bin/make/lst.lib/lstDupl.c /usr/src/3.0/src/usr.bin/make/lst.lib/lstEnQueue.c /usr/src/3.0/src/usr.bin/make/lst.lib/lstFind.c /usr/src/3.0/src/usr.bin/make/lst.lib/lstFindFrom.c /usr/src/3.0/src/usr.bin/make/lst.lib/lstFirst.c /usr/src/3.0/src/usr.bin/make/lst.lib/lstForEach.c /usr/src/3.0/src/usr.bin/make/lst.lib/lstForEachFrom.c /usr/src/3.0/src/usr.bin/make/lst.lib/lstInit.c /usr/src/3.0/src/usr.bin/make/lst.lib/lstInsert.c /usr/src/3.0/src/usr.bin/make/lst.lib/lstIsAtEnd.c /usr/src/3.0/src/usr.bin/make/lst.lib/lstIsEmpty.c /usr/src/3.0/src/usr.bin/make/lst.lib/lstLast.c /usr/src/3.0/src/usr.bin/make/lst.lib/lstMember.c /usr/src/3.0/src/usr.bin/make/lst.lib/lstNext.c /usr/src/3.0/src/usr.bin/make/lst.lib/lstOpen.c /usr/src/3.0/src/usr.bin/make/lst.lib/lstRemove.c /usr/src/3.0/src/usr.bin/make/lst.lib/lstReplace.c /usr/src/3.0/src/usr.bin/make/lst.lib/lstSucc.c /usr/bin/mkdep: cannot create _mkdep10285: directory nonexistent *** Error code 2 Stop. It really is all in one line, etc. This is relatively new. Wish I had the time to roll back the release one at a time. Maybe someone can recognize what is happening. Wiping /usr/obj works real well but sort of defeats the purpose of a Makefile... Thanx! --- Sincerely Yours, Simon Shapiro Atlas Telecom Senior Architect 14355 SW Allen Blvd., Suite 130 Beaverton OR 97005 Shimon@i-Connect.Net Voice: 503.799.2313 From owner-freebsd-current Thu Oct 2 18:03:22 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id SAA06363 for current-outgoing; Thu, 2 Oct 1997 18:03:22 -0700 (PDT) Received: from mixer.visi.com (root@mixer.visi.com [204.73.178.1]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id SAA06358 for ; Thu, 2 Oct 1997 18:03:13 -0700 (PDT) Received: from agentq.invisinet.visi.com (192-162.dynamic.visi.com [206.11.192.162]) by mixer.visi.com (8.8.6/8.7.5) with ESMTP id UAA26317 for ; Thu, 2 Oct 1997 20:03:02 -0500 (CDT) Posted-Date: Thu, 2 Oct 1997 20:03:02 -0500 (CDT) Received: (from invis@localhost) by agentq.invisinet.visi.com (8.8.7/8.8.5) id UAA02236; Thu, 2 Oct 1997 20:01:41 GMT Message-ID: <19971002200140.10833@visi.com> Date: Thu, 2 Oct 1997 20:01:40 +0000 From: Invis To: freebsd-current@freebsd.org Subject: How much work does running -current take? Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.84e Sender: owner-freebsd-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Just a few questions before I dive into -current, that didn't seem 100% answered by the FAQ :) : 1. If I install -current, will I have to do 'make worlds' or other 6 hour CPU tasks often? 2. Will my system more often than not be able to boot and run most of the time? i.e. I have one computer, I don't mind constant reboots, even making my own code patches if necessary, but if this is something it's almost necessary to have two machines for, please tell me! 3. Where can I get a list of new features available in 3.0-current ?? Please pardon me if I have asked common questions, however I have done my best to find answers to these *nagging* questions, and haven't found all the assurance I need :) invis invis@visi.com From owner-freebsd-current Thu Oct 2 18:33:20 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id SAA07691 for current-outgoing; Thu, 2 Oct 1997 18:33:20 -0700 (PDT) Received: from rfd1.oit.umass.edu (mailhub.oit.umass.edu [128.119.175.4]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id SAA07669 for ; Thu, 2 Oct 1997 18:32:21 -0700 (PDT) Received: from emily.oit.umass.edu by rfd1.oit.umass.edu (PMDF V5.1-10 #20973) with ESMTP id <0EHG005XIC9FQM@rfd1.oit.umass.edu> for freebsd-current@FreeBSD.ORG; Thu, 2 Oct 1997 21:32:03 -0400 (EDT) Received: from localhost (gp@localhost) by emily.oit.umass.edu (8.8.3/8.8.6) with SMTP id VAA21568; Thu, 02 Oct 1997 21:32:02 -0400 (EDT) Date: Thu, 02 Oct 1997 21:32:01 -0400 (EDT) From: Greg Pavelcak Subject: Re: How much work does running -current take? In-reply-to: <19971002200140.10833@visi.com> To: Invis Cc: freebsd-current@FreeBSD.ORG 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 Thu, 2 Oct 1997, Invis wrote: > Just a few questions before I dive into -current, that didn't seem 100% answered > by the FAQ :) : I can only tell you my experience. I am not a FreeBSD, or any kind of computer expert. In fact, if you see the questions I post, you know I am quite the opposite. I did dive into -current last week. > > 1. If I install -current, will I have to do 'make worlds' or other 6 hour CPU > tasks often? I run a Cyrix 6x86 P200+ with 48MB RAM. I think my "make world" was about 3 1/2 hrs. I had to do it several times, but that wasn't because of the make world, it was because I didn't mount the partitions properly in single user mode so I couldn't do the merge/copy stuff. Once I got that sorted out all went smoothly. If you want to upgrade regularly, I don't know if you have to rebuild the whole thing every time, but I think that's discussed in the handbook or the upgrade tutorial at www.freebsd.org > > 2. Will my system more often than not be able to boot and run most of the time? > i.e. I have one computer, I don't mind constant reboots, even making my own > code patches if necessary, but if this is something it's almost necessary > to have two machines for, please tell me! For the past week I have been customizing my window manager, trying to set up a zip drive and trying to use my -current machine to install 2.2.2-RELEASE on to my laptop. I have built several kernels and re-booted many times, but not because some difficulty forced me to. Of course I'm just running my own PC, not a server or anything, so I probably don't really test the limits. > > 3. Where can I get a list of new features available in 3.0-current ?? > Don't know. Being on the -current mailing list is a good place to start. > > Please pardon me if I have asked common questions, however I have done my best > to find answers to these *nagging* questions, and haven't found all the assurance I > need :) > > invis > invis@visi.com > From owner-freebsd-current Thu Oct 2 19:02:29 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id TAA08934 for current-outgoing; Thu, 2 Oct 1997 19:02:29 -0700 (PDT) Received: from word.smith.net.au (ppp20.portal.net.au [202.12.71.120]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id TAA08923 for ; Thu, 2 Oct 1997 19:02:21 -0700 (PDT) Received: from word.smith.net.au (localhost.smith.net.au [127.0.0.1]) by word.smith.net.au (8.8.7/8.8.5) with ESMTP id LAA00633; Fri, 3 Oct 1997 11:29:42 +0930 (CST) Message-Id: <199710030159.LAA00633@word.smith.net.au> X-Mailer: exmh version 2.0zeta 7/24/97 To: Simon Shapiro cc: freebsd-current@freebsd.org Subject: Re: Make depend is broken? Still?? In-reply-to: Your message of "Thu, 02 Oct 1997 17:41:25 MST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 03 Oct 1997 11:29:39 +0930 From: Mike Smith Sender: owner-freebsd-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > Hi Y'all, > > I may dare say there is a possibility of a bug in the -current main > makefile; It's not there. The problem is that the initial depend pass for 'make' puts the .depend file in the source directory : kingsford:/work/src/usr.bin/make>ls -la .depend -rw-r--r-- 1 root users 35208 Oct 2 15:24 .depend Here I'm worlding as root and thus can write it OK; I suspect your problem is that you aren't, and thus can't. I don't know why this is happening. mike From owner-freebsd-current Thu Oct 2 20:05:44 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id UAA11684 for current-outgoing; Thu, 2 Oct 1997 20:05:44 -0700 (PDT) Received: from cod.nosc.mil (gshaffer@cod.nosc.mil [128.49.4.5]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id UAA11679 for ; Thu, 2 Oct 1997 20:05:40 -0700 (PDT) Received: (from gshaffer@localhost) by cod.nosc.mil (8.8.7/8.8.7) id UAA26079; Thu, 2 Oct 1997 20:00:32 -0700 (PDT) Date: Thu, 2 Oct 1997 20:00:32 -0700 (PDT) From: "Gregory M. Shaffer" Message-Id: <199710030300.UAA26079@cod.nosc.mil> To: jkh@time.cdrom.com Cc: current@FreeBSD.Org, gshaffer.mark@grondar.za Subject: Re:: Making world on an SMP system. In-reply-to: Your Message-ID: <23948.875831179@time.cdrom.com> Sender: owner-freebsd-current@FreeBSD.Org X-Loop: FreeBSD.org Precedence: bulk ------- >From jkh@time.cdrom.com Thu Oct 2 15:26:57 1997 Received: from droid.nosc.mil (root@droid.nosc.mil [198.253.206.12]) by cod.nosc.mil (8.8.7/8.8.7) with ESMTP id PAA06304 for ; Thu, 2 Oct 1997 15:26:56 -0700 (PDT) Received: from time.cdrom.com (time.cdrom.com [204.216.27.226]) by droid.nosc.mil (8.8.7/8.8.7) with ESMTP id PAA27737 for ; Thu, 2 Oct 1997 15:25:59 -0700 (PDT) Received: from time.cdrom.com (localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.7/8.6.9) with ESMTP id PAA23966; Thu, 2 Oct 1997 15:26:20 -0700 (PDT) To: Greg Shaffer cc: Mark Murray , current@FreeBSD.ORG, gshaffer@cod.nosc.mil Subject: Re: Making world on an SMP system. In-reply-to: Your message of "Thu, 02 Oct 1997 12:40:23 PDT." Date: Thu, 02 Oct 1997 15:26:19 -0700 Message-ID: <23948.875831179@time.cdrom.com> From: "Jordan K. Hubbard" Status: RO > Several months ago there was some discussion on this. Someone actually > went through the *.mk and make files to make them parallel safe (i.e. > make -jN). The patches really improved the make world time. As far as > I know these patches were never committed! What was the PR# for this? I don't remember seeing one. :( Jordan I believe it was someones experament to see how difficult it would be to make the *.mk and make files parallel safe. I don't think there was a PR associated with it. I still have the patches somewhere on my system, I'd be happy to forward them to you for you inspection. Greg Shaffer ------- From owner-freebsd-current Thu Oct 2 20:40:55 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id UAA13352 for current-outgoing; Thu, 2 Oct 1997 20:40:55 -0700 (PDT) Received: from pluto.plutotech.com (root@mail.plutotech.com [206.168.67.137]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id UAA13305; Thu, 2 Oct 1997 20:40:46 -0700 (PDT) Received: from narnia.plutotech.com (narnia.plutotech.com [206.168.67.130]) by pluto.plutotech.com (8.8.5/8.8.5) with ESMTP id VAA13129; Thu, 2 Oct 1997 21:40:44 -0600 (MDT) Message-Id: <199710030340.VAA13129@pluto.plutotech.com> Date: Thu, 02 Oct 1997 21:40:15 -0600 From: "Justin T. Gibbs" Subject: New SCSI Framework Patches Available Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk To: undisclosed-recipients:; ------- Blind-Carbon-Copy X-Mailer: exmh version 2.0zeta 7/24/97 To: gibbs@FreeBSD.org Subject: New SCSI Framework Patches Available Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 02 Oct 1997 21:40:15 -0600 From: "Justin T. Gibbs" 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 the first Alpha release of that work. I plan to release snapshots on a weekly basis as new features and hardware support are added. To see what is currently supported, skip down to the supported hardware section. So now you must be asking yourself, "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 it. "work in progress", this code has been through over two 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, please do. I welcome your feedback especially about the performance of the new system. 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: Autotermination support for aic7860 based cards. Indirect 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. The only caveat is that bounce buffering is not implemented yet, so ISA cards must be used in systems with less than 16MB of RAM. The next driver I will be working on will support the Buslogic Multimaster cards. 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. Other peripheral drivers are in the works. HOW TO INSTALL IT BACKUP YOUR OLD KERNEL!!! cp /kernel /kernel.works Get the code: ftp://ftp.FreeBSD.org/pub/FreeBSD/incoming/cam-971002.tar.gz ftp://ftp.FreeBSD.org/pub/FreeBSD/incoming/cam-971002.diffs.gz ftp://ftp.FreeBSD.org/pub/FreeBSD/incoming/cam-971002samples.tar.gz cd /usr/src tar xvfz cam-971002.tar.gz zcat cam-971002.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". 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-971002samples.tar.gz and read the enclosed README file. - -- Justin T. Gibbs =========================================== FreeBSD - Turning PCs into workstations =========================================== ------- End of Blind-Carbon-Copy From owner-freebsd-current Thu Oct 2 20:52:27 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id UAA13914 for current-outgoing; Thu, 2 Oct 1997 20:52:27 -0700 (PDT) Received: from comp.polyu.edu.hk (csns02.comp.polyu.edu.hk [158.132.25.95]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id UAA13642 for ; Thu, 2 Oct 1997 20:44:54 -0700 (PDT) Received: from cssolar40.COMP.HKP.HK by comp.polyu.edu.hk (SMI-8.6/SMI-SVR4) id LAA27618; Fri, 3 Oct 1997 11:41:27 +0800 Received: (from c5666305@localhost) by cssolar40.COMP.HKP.HK (SMI-8.6/) id LAA23813 for current@freebsd.org; Fri, 3 Oct 1997 11:41:26 +0800 Message-Id: <199710030341.LAA23813@cssolar40.COMP.HKP.HK> Subject: anyone playing with obliq-3D software (2.2.2 Rel) To: current@freebsd.org Date: Fri, 3 Oct 1997 11:41:25 +0800 (HKT) From: "c5666305" X-Mailer: ELM [version 2.4 PL25] 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 Hello, I am not sure it is the right place to ask for help. If I am wrong, please tell me the correct one. I am the student of Hong Kong Polytechnic University and doing a final project concerning hierachical information visuazlization. I recently installed the obliq-3D under 2.2.2 Rel. I have include lesstif, mesagl and some other libraires. WHen I tried to run the obliq commands like obliqsrv -std, I got the bus error (core dump). Is there anyone can help out of the trouble ? Thanks a lot. Clarence CHAN c5666305@comp.polyu.edu.hk From owner-freebsd-current Thu Oct 2 21:59:03 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id VAA17047 for current-outgoing; Thu, 2 Oct 1997 21:59:03 -0700 (PDT) Received: from sendero-ppp.i-connect.net (sendero-ppp.i-Connect.Net [206.190.143.100]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id VAA17042 for ; Thu, 2 Oct 1997 21:58:59 -0700 (PDT) Received: (qmail 17342 invoked by uid 1000); 3 Oct 1997 04:59:20 -0000 Message-ID: X-Mailer: XFMail 1.2-alpha-092597 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <199710030159.LAA00633@word.smith.net.au> Date: Thu, 02 Oct 1997 21:59:20 -0700 (PDT) Organization: Atlas Telecom From: Simon Shapiro To: Mike Smith Subject: Re: Make depend is broken? Still?? Cc: freebsd-current@freebsd.org Sender: owner-freebsd-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi Mike Smith; On 03-Oct-97 you wrote: > > Hi Y'all, > > > > I may dare say there is a possibility of a bug in the -current main > > makefile; > > It's not there. The problem is that the initial depend pass for 'make' > puts the .depend file in the source directory : > > kingsford:/work/src/usr.bin/make>ls -la .depend > -rw-r--r-- 1 root users 35208 Oct 2 15:24 .depend > > Here I'm worlding as root and thus can write it OK; I suspect your > problem is that you aren't, and thus can't. Wrong guess :-) I am running it as root. The mistake was explained to me (it was mine). As long as the problem is recognizable and the solution workable, I am a happy man. It is and I am. Thanx! --- Sincerely Yours, Simon Shapiro Atlas Telecom Senior Architect 14355 SW Allen Blvd., Suite 130 Beaverton OR 97005 Shimon@i-Connect.Net Voice: 503.799.2313 From owner-freebsd-current Thu Oct 2 22:43:26 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id WAA19400 for current-outgoing; Thu, 2 Oct 1997 22:43:26 -0700 (PDT) Received: from 586quick166.saturn-tech.com ([207.229.19.32]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id WAA19392 for ; Thu, 2 Oct 1997 22:43:22 -0700 (PDT) Received: from localhost (drussell@localhost) by 586quick166.saturn-tech.com (8.8.7/8.8.4) with SMTP id XAA02392; Thu, 2 Oct 1997 23:42:44 -0600 (MDT) X-Authentication-Warning: 586quick166.saturn-tech.com: drussell owned process doing -bs Date: Thu, 2 Oct 1997 23:42:43 -0600 (MDT) From: Doug Russell To: lamaster@george.arc.nasa.gov cc: wollman@khavrinen.lcs.mit.edu, current@FreeBSD.ORG Subject: Re: Which PCI Ethernet card is best for FreeBSD-current? In-Reply-To: <199710021737.KAA07677@george.arc.nasa.gov> 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 Thu, 2 Oct 1997 lamaster@george.arc.nasa.gov wrote: > In retrospect it was probably a bad choice, but, so far, my > 3Com 3C595 has worked OK, including for multicast, although > network performance is not really an observable on that > system. It was fairly expensive, although it was the cheapest > PCI card I could get at the time. A couple of weeks later, I have 3 3c905TX cards here, all of which seem to work great. I'm sur ethey aren't the best, but at 10 Mbps I consistently get 1 Meg/sec FTP rates between them, something that I didn't usually get with my old DEC 10 Mbps card. I'm sure at 100 Mbps they wouldn't fare quite as well as the Intel cards, but I'll probably have migrated them do some Windoze machines by the time I get a 100 Mbps hub. :) Later...... Mr. :) Happy is really cute in this font. :) From owner-freebsd-current Thu Oct 2 22:51:06 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id WAA20029 for current-outgoing; Thu, 2 Oct 1997 22:51:06 -0700 (PDT) Received: from digger1.defence.gov.au (digger1.defence.gov.au [203.5.217.4]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id WAA19823; Thu, 2 Oct 1997 22:49:32 -0700 (PDT) Received: from fang.dsto.defence.gov.au (fang.dsto.defence.gov.au [131.185.2.5]) by digger1.defence.gov.au (8.7.5/8.7.3) with ESMTP id PAA25373; Fri, 3 Oct 1997 15:17:37 +0930 (CST) Received: from eddie.dsto.defence.gov.au (eddie.dsto.defence.gov.au [131.185.2.111]) by fang.dsto.defence.gov.au (8.8.5/) with ESMTP id PAA22151; Fri, 3 Oct 1997 15:18:04 +0930 (CST) Received: from dsto.defence.gov.au (localhost [127.0.0.1]) by eddie.dsto.defence.gov.au (8.8.5/8.8.5) with ESMTP id PAA27907; Fri, 3 Oct 1997 15:18:03 +0930 (CST) Message-ID: <34348712.F0962930@dsto.defence.gov.au> Date: Fri, 03 Oct 1997 15:18:02 +0930 From: Matthew Thyer Organization: Defence Science Technology Organisation X-Mailer: Mozilla 4.03b8 [en] (X11; I; FreeBSD 3.0-970618-SNAP i386) MIME-Version: 1.0 To: freebsd-current@freebsd.org, ports@freebsd.org Subject: xlock: caught signal 8 while running galaxy mode. 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 else have this problem or can anyone confirm that it will be solved by a newer incarnation of -CURRENT or a newer xlockmore ? I run xlockmore-4.02 on a somewhat dated FreeBSD 3.0-CURRENT now (3.0-970618-SNAP). I always use the galaxy mode for screen locking (because I love it!) and it often dies with the following error in my .xsession-errors file: "xlock: caught signal 8 while running galaxy mode." Signal 8 appears to be a floating point exception (FPE) according to kill -l. I'm finding I can't rely on the screen being locked when I leave my office. Could this be a Pentium FPU bug ?? Dmesg output for my CPU: CPU: Pentium (99.72-MHz 586-class CPU) Origin = "GenuineIntel" Id = 0x526 Stepping=6 Features=0x1bf I will get around to updating my -CURRENT soon (maybe not that soon given the recent instabilities with NFS client) and my installed ports. (I've got to work out the socks support for cvsup first before I can keep my ports collection up to date easily). Please reply directly as this address is not subscribed to the current list. -- Matthew Thyer Phone: +61 8 8259 7249 Corporate Information Systems Fax: +61 8 8259 5537 Defence Science and Technology Organisation, Salisbury PO Box 1500 Salisbury South Australia 5108 From owner-freebsd-current Thu Oct 2 23:02:00 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id XAA20866 for current-outgoing; Thu, 2 Oct 1997 23:02:00 -0700 (PDT) Received: from vinyl.quickweb.com (vinyl.quickweb.com [209.112.4.14]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id XAA20861 for ; Thu, 2 Oct 1997 23:01:58 -0700 (PDT) Received: (from mark@localhost) by vinyl.quickweb.com (8.8.7/8.6.12) id CAA24955; Fri, 3 Oct 1997 02:02:40 -0400 (EDT) Message-ID: <19971003020238.59335@vinyl.quickweb.com> Date: Fri, 3 Oct 1997 02:02:38 -0400 From: Mark Mayo To: freebsd-current@freebsd.org Subject: NFS changes since Rick Maclem... Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.81e Sender: owner-freebsd-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi. I go to school at the University of Guelph, home of Rick Maclem of BSD-Lite NFS fame. I was talking to Rick the other day and he said that 99% of the NFS code in FreeBSD (and the other BSDs) was still his - I questioned this since NFS seems to be always under a state of minor change (at least since I've been using FreeBSD). So how far has the code deviated from Rick's code? I would have imagined quite a bit in all this time, especially with NFS v3 now being the default.. Anyways, there are a few of us here that are looking for something to code, and if NFS is in need of repiar/enhancement it would be a good project since the original NFS guru is at our finger tips. If the code hasn't changed much, maybe I'll be able to convince Rick to get off his ass and look at it again :-) And if it has changed a bunch maybe this will scare him out of compacity... :-) TIA, -Mark (P.S. I had a disk blow up so I'm really pressed for disk space right now which has made it nearly impossible to get back to a situation where it's convenient to compare the 2 NFS sources..) -- ------------------------------------------------------------------------ Mark Mayo mark@quickweb.com RingZero Comp. http://vinyl.quickweb.com/mark finger mark@quickweb.com for my PGP key and GCS code ------------------------------------------------------------------------ Win95/NT - 32 bit extensions and a graphical shell for a 16 bit patch to an an 8 bit operating system originally coded for a 4 bit microprocessor, written by a 2 bit company that can't stand 1 bit of competition. -UGU From owner-freebsd-current Thu Oct 2 23:39:54 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id XAA23477 for current-outgoing; Thu, 2 Oct 1997 23:39:54 -0700 (PDT) Received: from silvia.HIP.Berkeley.EDU (ala-ca14-03.ix.netcom.com [204.32.168.67]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id XAA23472 for ; Thu, 2 Oct 1997 23:39:50 -0700 (PDT) Received: (from asami@localhost) by silvia.HIP.Berkeley.EDU (8.8.7/8.6.9) id XAA12795; Thu, 2 Oct 1997 23:39:49 -0700 (PDT) Date: Thu, 2 Oct 1997 23:39:49 -0700 (PDT) Message-Id: <199710030639.XAA12795@silvia.HIP.Berkeley.EDU> To: current@freebsd.org Subject: cleanworld From: asami@cs.berkeley.edu (Satoshi Asami) Sender: owner-freebsd-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Seems a lot of people are unable to understand the immutable flag bit, how about this? Satoshi P.S. This patch is relative to the 2.2 branch. ------- Index: Makefile =================================================================== RCS file: /usr/cvs/src/Makefile,v retrieving revision 1.109.2.19 diff -u -r1.109.2.19 Makefile --- Makefile 1997/09/28 16:33:05 1.109.2.19 +++ Makefile 1997/10/03 06:38:59 @@ -23,6 +23,7 @@ # The intended user-driven targets are: # buildworld - rebuild *everything*, including glue to help do upgrades # installworld- install everything built by "buildworld" +# cleanworld - remove the temporary build tree for "buildworld" # world - buildworld + installworld # update - convenient way to update your source tree (eg: sup/cvs) # most - build user commands, no libraries or include files @@ -194,6 +195,17 @@ IXMAKE= ${XMAKEENV} ${WORLDTMP}/usr/bin/${MAKE} # +# cleanworld +# +# Deletes the temporary build tree. +# +cleanworld: +.if exists(${WORLDTMP}) + chflags -R noschg ${WORLDTMP}/ + rm -rf ${WORLDTMP} +.endif + +# # buildworld # # Attempt to rebuild the entire system, with reasonable chance of @@ -205,9 +217,7 @@ @echo "--------------------------------------------------------------" @echo " Cleaning up the temporary build tree" @echo "--------------------------------------------------------------" - mkdir -p ${WORLDTMP} - chflags -R noschg ${WORLDTMP}/ - rm -rf ${WORLDTMP} + cd ${.CURDIR} && ${MAKE} cleanworld .endif @echo @echo "--------------------------------------------------------------" From owner-freebsd-current Fri Oct 3 00:00:02 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id AAA25017 for current-outgoing; Fri, 3 Oct 1997 00:00:02 -0700 (PDT) Received: from silvia.HIP.Berkeley.EDU (ala-ca14-03.ix.netcom.com [204.32.168.67]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id XAA24964 for ; Thu, 2 Oct 1997 23:59:55 -0700 (PDT) Received: (from asami@localhost) by silvia.HIP.Berkeley.EDU (8.8.7/8.6.9) id XAA12834; Thu, 2 Oct 1997 23:59:36 -0700 (PDT) Date: Thu, 2 Oct 1997 23:59:36 -0700 (PDT) Message-Id: <199710030659.XAA12834@silvia.HIP.Berkeley.EDU> To: drussell@saturn-tech.com CC: lamaster@george.arc.nasa.gov, wollman@khavrinen.lcs.mit.edu, current@FreeBSD.ORG In-reply-to: (message from Doug Russell on Thu, 2 Oct 1997 23:42:43 -0600 (MDT)) Subject: Re: Which PCI Ethernet card is best for FreeBSD-current? From: asami@cs.berkeley.edu (Satoshi Asami) Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk * From: Doug Russell * I have 3 3c905TX cards here, all of which seem to work great. I'm sur * ethey aren't the best, but at 10 Mbps I consistently get 1 Meg/sec FTP * rates between them, something that I didn't usually get with my old DEC 10 * Mbps card. I'm sure at 100 Mbps they wouldn't fare quite as well as the * Intel cards, but I'll probably have migrated them do some Windoze machines * by the time I get a 100 Mbps hub. :) At 100Mbps, Intel and SMC (old 9332DST) cards blow 595TX into chunks. My small test was to create a ccd on both ends of a crossover connection and ftp a large file over. Result: over 10MB/s with Intel/SMC, less than 5MB/s with 3c595TX. Also, the 595TX exhibited very poor performance with a noisy link. TCP performance was like 100~200KB/s on my workstation with a 10BaseT shared net with a long cable. I changed it with an old SMC card (10BaseT), I can get 500KB/s (or some other reasonable number, depending on how congested the line is at that time). All of the above is with 2.2-stable of about a month ago. Satoshi From owner-freebsd-current Fri Oct 3 00:36:57 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id AAA27739 for current-outgoing; Fri, 3 Oct 1997 00:36:57 -0700 (PDT) Received: from silvia.HIP.Berkeley.EDU (ala-ca14-03.ix.netcom.com [204.32.168.67]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id AAA27730; Fri, 3 Oct 1997 00:36:53 -0700 (PDT) Received: (from asami@localhost) by silvia.HIP.Berkeley.EDU (8.8.7/8.6.9) id AAA12977; Fri, 3 Oct 1997 00:35:48 -0700 (PDT) Date: Fri, 3 Oct 1997 00:35:48 -0700 (PDT) Message-Id: <199710030735.AAA12977@silvia.HIP.Berkeley.EDU> To: Matthew.Thyer@dsto.defence.gov.au CC: freebsd-current@FreeBSD.ORG, ports@FreeBSD.ORG In-reply-to: <34348712.F0962930@dsto.defence.gov.au> (message from Matthew Thyer on Fri, 03 Oct 1997 15:18:02 +0930) Subject: Re: xlock: caught signal 8 while running galaxy mode. From: asami@cs.berkeley.edu (Satoshi Asami) Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk * "xlock: caught signal 8 while running galaxy mode." * * Signal 8 appears to be a floating point exception (FPE) according to * kill -l. A lot of xscreensaver programs die with this too. Is this one of those "our FP exception model is absolutely correct but different from every other system" things? Satoshi From owner-freebsd-current Fri Oct 3 01:08:17 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id BAA29245 for current-outgoing; Fri, 3 Oct 1997 01:08:17 -0700 (PDT) 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 BAA29238; Fri, 3 Oct 1997 01:08:06 -0700 (PDT) Received: (from jmg@localhost) by hydrogen.nike.efn.org (8.8.7/8.8.7) id BAA22162; Fri, 3 Oct 1997 01:07:37 -0700 (PDT) Message-ID: <19971003010737.54157@hydrogen.nike.efn.org> Date: Fri, 3 Oct 1997 01:07:37 -0700 From: John-Mark Gurney To: Matthew Thyer Cc: freebsd-current@FreeBSD.ORG, ports@FreeBSD.ORG Subject: Re: xlock: caught signal 8 while running galaxy mode. References: <34348712.F0962930@dsto.defence.gov.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.69 In-Reply-To: <34348712.F0962930@dsto.defence.gov.au>; from Matthew Thyer on Fri, Oct 03, 1997 at 03:18:02PM +0930 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 Matthew Thyer scribbled this message on Oct 3: > Does anyone else have this problem or can anyone confirm that it > will be solved by a newer incarnation of -CURRENT or a newer > xlockmore ? don't worry.. I have the same problem.. and my processor is a amd k5-90, and I'm pretty sure I saw it on my amd5x86-133... I think it's just a programming error.... of course I'm running it on a 2.2.1-R.. ttyl.. -- 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 Oct 3 02:20:35 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id CAA02806 for current-outgoing; Fri, 3 Oct 1997 02:20:35 -0700 (PDT) Received: from oxmail4.ox.ac.uk (oxmail4.ox.ac.uk [163.1.2.33]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id CAA02801 for ; Fri, 3 Oct 1997 02:20:28 -0700 (PDT) Received: from njl2.materials.ox.ac.uk by oxmail4 with SMTP (PP); Fri, 3 Oct 1997 10:19:41 +0100 Received: by njl2.materials.ox.ac.uk (950413.SGI.8.6.12/940406.SGI) for freebsd-current@FreeBSD.ORG id KAA12629; Fri, 3 Oct 1997 10:19:27 +0100 Date: Fri, 3 Oct 1997 10:19:27 +0100 From: neil.long@materials.oxford.ac.uk (Neil J Long) Message-Id: <9710031019.ZM12627@njl2.materials.ox.ac.uk> X-Mailer: Z-Mail-SGI (3.2S.3 08feb96 MediaMail) To: freebsd-current@freebsd.org Subject: Network related lockups Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hello I have a 486/33 running RELENG_2_2 and continue to experience network related lockups whose nature has changed with the recent kernel network mods. The machine is currently on a thin-wire segment and runs arpwatch. There is very high activity on this segment at night while the amanda server (SGI Challenge S) backups up a lot of machines but the total data is around 2G over a couple of hours. The PC also gets backed up during this spell and the only solution I have found so far is to use at to killall arpwatch and re-start it later and reduce the number of amanda 'dumpers' per client to 1 from 2. I used to get messages related to routed (some may remember my previous postings) but the current changes give /kernel: ed0: NIC memory corrupt - invalid packet length 2800 /kernel: ed0: NIC memory corrupt - invalid packet length 2776 This is using a NE2000 clone, I will switch back again to a ep0 3Com card and see what happens tonight. It seems that arpwatch is just too much for the network card to cope with when the network is heavily utilised and I will switch to using another SG box to monitor for users hell-bent on misconfiguring their W95 boxes. Just for info - I never seem to be able to get any more debug info to go on _ I only got the above error by unloading the lkm screen saver otherwise the lockup seems total needing a power cycle. Cheers Neil From owner-freebsd-current Fri Oct 3 06:36:04 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id GAA13696 for current-outgoing; Fri, 3 Oct 1997 06:36:04 -0700 (PDT) Received: from morse.satech.net.au (morse.satech.net.au [203.56.210.66]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id GAA13663; Fri, 3 Oct 1997 06:35:51 -0700 (PDT) Received: from matte.box.net.au (matte.satech.net.au [203.1.91.219]) by morse.satech.net.au (8.8.5/8.8.5.SAT.GJR.970426) with ESMTP id XAA22316; Fri, 3 Oct 1997 23:05:40 +0930 Received: from box.net.au (localhost.satech.net.au [127.0.0.1]) by matte.box.net.au (8.8.7/8.7.3) with ESMTP id XAA04253; Fri, 3 Oct 1997 23:05:59 +0930 (CST) Message-ID: <3434F4BE.B77C9E2D@box.net.au> Date: Fri, 03 Oct 1997 23:05:58 +0930 From: Matthew Thyer X-Mailer: Mozilla 4.03b8 [en] (X11; I; FreeBSD 3.0-CURRENT i386) MIME-Version: 1.0 To: John-Mark Gurney CC: Matthew Thyer , freebsd-current@FreeBSD.ORG, ports@FreeBSD.ORG Subject: Re: xlock: caught signal 8 while running galaxy mode. References: <34348712.F0962930@dsto.defence.gov.au> <19971003010737.54157@hydrogen.nike.efn.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk By the way, I've never seen this problem on my home machine running: current as at ctm-src-cur.3049 with xlockmore-4.03 and CPU: CPU: Pentium (100.23-MHz 586-class CPU) Origin = "GenuineIntel" Id = 0x52c Stepping=12 Features=0x1bf (which is actually a P150 on a motherboard that can only do 100 MHz as I'm strapped for cash and cant afford $120 Australian for a new motherboard - boo hoo thats what 1 income, a small child and two housing loans gets you ;) So I'll update the work machine and tell you all if it solves the problem. John-Mark Gurney wrote: > > Matthew Thyer scribbled this message on Oct 3: > > Does anyone else have this problem or can anyone confirm that it > > will be solved by a newer incarnation of -CURRENT or a newer > > xlockmore ? > > don't worry.. I have the same problem.. and my processor is a amd k5-90, > and I'm pretty sure I saw it on my amd5x86-133... I think it's just a > programming error.... of course I'm running it on a 2.2.1-R.. > > ttyl.. > > -- > John-Mark Gurney Modem/FAX: +1 541 683 6954 > Cu Networking > > Live in Peace, destroy Micro$oft, support free software, run FreeBSD -- /=====================================================================\ | Work: Matthew.Thyer@dsto.defence.gov.au | Home: thyerm@box.net.au | \=====================================================================/ "If it is true that our Universe has a zero net value for all conserved quantities, then it may simply be a fluctuation of the vacuum of some larger space in which our Universe is imbedded. In answer to the question of why it happened, I offer the modest proposal that our Universe is simply one of those things which happen from time to time." E. P. Tryon from "Nature" Vol.246 Dec.14, 1973 From owner-freebsd-current Fri Oct 3 07:13:50 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id HAA15872 for current-outgoing; Fri, 3 Oct 1997 07:13:50 -0700 (PDT) Received: from word.smith.net.au (word.smith.net.au [202.0.75.3]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id HAA15862 for ; Fri, 3 Oct 1997 07:13:45 -0700 (PDT) Received: from word.smith.net.au (localhost.smith.net.au [127.0.0.1]) by word.smith.net.au (8.8.7/8.8.5) with ESMTP id XAA00752; Fri, 3 Oct 1997 23:40:50 +0930 (CST) Message-Id: <199710031410.XAA00752@word.smith.net.au> X-Mailer: exmh version 2.0zeta 7/24/97 To: Invis cc: freebsd-current@freebsd.org Subject: Re: How much work does running -current take? In-reply-to: Your message of "Thu, 02 Oct 1997 20:01:40 GMT." <19971002200140.10833@visi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 03 Oct 1997 23:40:48 +0930 From: Mike Smith Sender: owner-freebsd-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > 1. If I install -current, will I have to do 'make worlds' or other 6 hour CPU > tasks often? You won't have to. You may want to. > 2. Will my system more often than not be able to boot and run most of the time? > i.e. I have one computer, I don't mind constant reboots, even making my own > code patches if necessary, but if this is something it's almost necessary > to have two machines for, please tell me! It can be helpful to have two systems, but things are generally better now than they were in terms of re-bootstrapping yourself. > 3. Where can I get a list of new features available in 3.0-current ?? The CVS commitlogs are the most verbose resource. mike From owner-freebsd-current Fri Oct 3 07:32:12 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id HAA17337 for current-outgoing; Fri, 3 Oct 1997 07:32:12 -0700 (PDT) Received: from shadows.aeon.net (shadows.aeon.net [194.100.41.1]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id HAA16830 for ; Fri, 3 Oct 1997 07:25:41 -0700 (PDT) Received: (from bsdcur@localhost) by shadows.aeon.net (8.8.7/8.8.3) id RAA10996; Fri, 3 Oct 1997 17:20:56 +0200 (EET) From: mika ruohotie Message-Id: <199710031520.RAA10996@shadows.aeon.net> Subject: Re: Which PCI Ethernet card is best for FreeBSD-current? In-Reply-To: from "[______ ______]" at "Oct 2, 97 08:38:08 am" To: ache@nagual.pp.ru (=?KOI8-R?B?4c7E0sXKIP7F0s7P1w==?=) Date: Fri, 3 Oct 1997 17:20:56 +0200 (EET) Cc: 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 > Could someone share his experience with me and tell about 2-3 best models? > Stability is more essential than performance for me. > -- > Andrey A. Chernov > > http://www.nagual.pp.ru/~ache/ > > From owner-freebsd-current Fri Oct 3 07:49:28 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id HAA18686 for current-outgoing; Fri, 3 Oct 1997 07:49:28 -0700 (PDT) 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 HAA18681 for ; Fri, 3 Oct 1997 07:49:25 -0700 (PDT) Received: from Mars.mcs.net (karl@Mars.mcs.net [192.160.127.85]) by Kitten.mcs.com (8.8.5/8.8.2) with ESMTP id JAA11898; Fri, 3 Oct 1997 09:49:22 -0500 (CDT) Received: (from karl@localhost) by Mars.mcs.net (8.8.7/8.8.2) id JAA11785; Fri, 3 Oct 1997 09:49:22 -0500 (CDT) Message-ID: <19971003094922.63232@Mars.Mcs.Net> Date: Fri, 3 Oct 1997 09:49:22 -0500 From: Karl Denninger To: Mike Smith Cc: Invis , freebsd-current@FreeBSD.ORG Subject: Re: How much work does running -current take? References: <19971002200140.10833@visi.com> <199710031410.XAA00752@word.smith.net.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.64 In-Reply-To: <199710031410.XAA00752@word.smith.net.au>; from Mike Smith on Fri, Oct 03, 1997 at 11:40:48PM +0930 Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Fri, Oct 03, 1997 at 11:40:48PM +0930, Mike Smith wrote: > > > > 1. If I install -current, will I have to do 'make worlds' or other 6 hour CPU > > tasks often? > > You won't have to. You may want to. > > > 2. Will my system more often than not be able to boot and run most of the time? > > i.e. I have one computer, I don't mind constant reboots, even making my own > > code patches if necessary, but if this is something it's almost necessary > > to have two machines for, please tell me! > > It can be helpful to have two systems, but things are generally better > now than they were in terms of re-bootstrapping yourself. > > > 3. Where can I get a list of new features available in 3.0-current ?? > > The CVS commitlogs are the most verbose resource. > > mike There are times when -current is EXTREMELY unstable. My hints and tricks include: 1) If you have two machines, its a REALLY good idea to keep one of them in usable condition at all times until you've completed testing on new stuff. 2) Any time the kernel changes drastically enough that libkvm and friends (ie: ps, etc) needs to be rebuilt you can get screwed. Use extra caution at those times. Those are the times when its most dangerous, because you might not be easily able to back out a bad change. 3) Learn how to check out and/or update your local copy with the "-D" switch to cvs (ie: cvs update -D "yesterday" .). This can save your bacon if you ARE rebuilding all the time and one day it breaks when you knew it was ok yesterday. 4) If you are making local changes to the sources (we do here) be extremely cautious in exactly how you go about things. You must learn how CVS actually does stuff so you don't accidentially lose your local changes. ALWAYS, ALWAYS keep a local context diff of your changes against a known base version SOMEWHERE ELSE. -- -- Karl Denninger (karl@MCS.Net)| MCSNet - Serving Chicagoland and Wisconsin http://www.mcs.net/~karl | T1's from $600 monthly to FULL DS-3 Service | NEW! K56Flex modem support is now available Voice: [+1 312 803-MCS1 x219]| 56kbps DIGITAL ISDN DOV on analog lines! Fax: [+1 312 803-4929] | 2 FULL DS-3 Internet links; 400Mbps B/W Internal From owner-freebsd-current Fri Oct 3 08:55:27 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id IAA22863 for current-outgoing; Fri, 3 Oct 1997 08:55:27 -0700 (PDT) Received: from seagull.cdrom.com (cracauer@seagull.cdrom.com [204.216.27.14]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id IAA22858; Fri, 3 Oct 1997 08:55:25 -0700 (PDT) Received: (from cracauer@localhost) by seagull.cdrom.com (8.8.6/8.6.6) id IAA07278 ; Fri, 3 Oct 1997 08:54:35 -0700 (PDT) Message-ID: <19971003175433.64822@cons.org> Date: Fri, 3 Oct 1997 17:54:33 +0200 From: Martin Cracauer To: Matthew Thyer Cc: freebsd-current@FreeBSD.ORG, ports@FreeBSD.ORG Subject: Re: xlock: caught signal 8 while running galaxy mode. References: <34348712.F0962930@dsto.defence.gov.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.81 In-Reply-To: <34348712.F0962930@dsto.defence.gov.au>; from Matthew Thyer on Fri, Oct 03, 1997 at 03:18:02PM +0930 Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk In <34348712.F0962930@dsto.defence.gov.au>, Matthew Thyer wrote: > Does anyone else have this problem or can anyone confirm that it > will be solved by a newer incarnation of -CURRENT or a newer > xlockmore ? > > I run xlockmore-4.02 on a somewhat dated FreeBSD 3.0-CURRENT now > (3.0-970618-SNAP). > > I always use the galaxy mode for screen locking (because I love it!) > and it often dies with the following error in my > .xsession-errors file: > > "xlock: caught signal 8 while running galaxy mode." > > Signal 8 appears to be a floating point exception (FPE) according to > kill -l. This has been discusssed several times. FreeBSD defaults to abort a program at a floating point exception while anyone else does not. The default for then is to set the result to IEEE exceptional values (InF, NaN etc.). You can switch all systems to do the other. I tried to convince people that FreeBSD hurts itself here, and the dying screensavers are my primary example how this can hurt users. The solution was to tell the port maintainers to switch FP mode for their ports, which haven't happend for any port, as far as I know. There are bugs in our gcc that make relying on FP exceptions handled right dangerous and Bruce Evans felt it is better to through the signal, so that people get aware of the problem. With all respect to Bruce, I'm still conviced that we should switch to default to set exceptional values and not signal the process. Our gcc isn't that much worse than NetBSD's and Linux and those systems obviously didn't get into trouble, at least not my my applications. I think that a user who maintains a critical floating point program is much more likely to be aware of turning on exceptions for his program than any random user is aware of turning them off for a black-box (for his viewpoint) package like xlockmore. If you want to change the system-wide default, add this to npx.h before building a kernel: undef __INITIAL_NPXCW__ #define __INITIAL_NPXCW__ 0x127f If you come to an educated opinion about the issue a mail to core may be useful. Martin -- %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% Martin Cracauer http://www.cons.org/cracauer/ BSD User Group Hamburg/Germany http://www.bsdhh.org/ From owner-freebsd-current Fri Oct 3 10:03:41 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id KAA28037 for current-outgoing; Fri, 3 Oct 1997 10:03:41 -0700 (PDT) Received: from time.cdrom.com (time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id KAA28014; Fri, 3 Oct 1997 10:03:35 -0700 (PDT) Received: from time.cdrom.com (localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.7/8.6.9) with ESMTP id KAA22022; Fri, 3 Oct 1997 10:02:30 -0700 (PDT) To: Martin Cracauer cc: Matthew Thyer , freebsd-current@FreeBSD.ORG, ports@FreeBSD.ORG Subject: Re: xlock: caught signal 8 while running galaxy mode. In-reply-to: Your message of "Fri, 03 Oct 1997 17:54:33 +0200." <19971003175433.64822@cons.org> Date: Fri, 03 Oct 1997 10:02:30 -0700 Message-ID: <22019.875898150@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > I tried to convince people that FreeBSD hurts itself here, and the > dying screensavers are my primary example how this can hurt users. The > solution was to tell the port maintainers to switch FP mode for their > ports, which haven't happend for any port, as far as I know. > > There are bugs in our gcc that make relying on FP exceptions handled > right dangerous and Bruce Evans felt it is better to through the > signal, so that people get aware of the problem. > > With all respect to Bruce, I'm still conviced that we should switch to > default to set exceptional values and not signal the process. Our gcc > isn't that much worse than NetBSD's and Linux and those systems > obviously didn't get into trouble, at least not my my applications. You're not alone in this point of view, but even several of us arguing for years with Bruce on this issue has not been enough to sway him from the point of view that purity exceeds the value of functionality here. :-) Jordan From owner-freebsd-current Fri Oct 3 10:48:01 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id KAA00557 for current-outgoing; Fri, 3 Oct 1997 10:48:01 -0700 (PDT) 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 KAA00539 for ; Fri, 3 Oct 1997 10:47:59 -0700 (PDT) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id KAA03300; Fri, 3 Oct 1997 10:40:02 -0700 (PDT) Received: from current1.whistle.com(207.76.205.22) via SMTP by alpo.whistle.com, id smtpd003285; Fri Oct 3 17:39:54 1997 Message-ID: <34352DAD.ABD322C@whistle.com> Date: Fri, 03 Oct 1997 10:38:53 -0700 From: Julian Elischer Organization: Whistle Communications X-Mailer: Mozilla 3.0Gold (X11; I; FreeBSD 2.2-CURRENT i386) MIME-Version: 1.0 To: Mike Smith CC: Invis , freebsd-current@FreeBSD.ORG Subject: Re: How much work does running -current take? References: <199710031410.XAA00752@word.smith.net.au> 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: > > > > > 1. If I install -current, will I have to do 'make worlds' or other 6 hour CPU > > tasks often? > > You won't have to. You may want to. > > > 2. Will my system more often than not be able to boot and run most of the time? > > i.e. I have one computer, I don't mind constant reboots, even making my own > > code patches if necessary, but if this is something it's almost necessary > > to have two machines for, please tell me! > > It can be helpful to have two systems, but things are generally better > now than they were in terms of re-bootstrapping yourself. the problem is that new binaries cannot run on old machines because there is a new system call so everything falls over especially /bin/sh so you can't even boot on your old kernel if something goes wrong witf the new one. From owner-freebsd-current Fri Oct 3 11:25:21 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id LAA03358 for current-outgoing; Fri, 3 Oct 1997 11:25:21 -0700 (PDT) Received: from consys.com (consys.com [209.60.202.194]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id LAA03346; Fri, 3 Oct 1997 11:25:18 -0700 (PDT) Received: from cssunix.conceptual.com (cssunix.conceptual.com [10.0.2.5]) by consys.com (8.8.6/8.8.6) with ESMTP id LAA03005; Fri, 3 Oct 1997 11:25:16 -0700 (MST) Received: from cssunix.conceptual.com (localhost [127.0.0.1]) by cssunix.conceptual.com (8.8.5/8.8.6) with ESMTP id LAA00695; Fri, 3 Oct 1997 11:25:16 -0700 (MST) Message-Id: <199710031825.LAA00695@cssunix.conceptual.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: freebsd-current@FreeBSD.ORG, ports@FreeBSD.ORG Subject: Re: xlock: caught signal 8 while running galaxy mode. In-reply-to: Your message of "Fri, 03 Oct 1997 10:02:30 MST." <22019.875898150@time.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 03 Oct 1997 11:25:15 -0700 From: "Russell L. Carter" Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Perhaps this is a faq, though I was unable to tickle it out of the archives. What is the difference between "Our" gcc and the NetBSD, Linux incarnations that requires the default FreeBSD behaviour? (A search phrase for the archives would make me happy :) I have never been too dogmatic about requiring identical floating point behavior across platforms but the current rather energetic arguments over what "Pure" Java floating point must be has piqued my interest in the FreeBSD situation. Russell }> I tried to convince people that FreeBSD hurts itself here, and the }> dying screensavers are my primary example how this can hurt users. The }> solution was to tell the port maintainers to switch FP mode for their }> ports, which haven't happend for any port, as far as I know. }> }> There are bugs in our gcc that make relying on FP exceptions handled }> right dangerous and Bruce Evans felt it is better to through the }> signal, so that people get aware of the problem. }> }> With all respect to Bruce, I'm still conviced that we should switch to }> default to set exceptional values and not signal the process. Our gcc }> isn't that much worse than NetBSD's and Linux and those systems }> obviously didn't get into trouble, at least not my my applications. } }You're not alone in this point of view, but even several of us arguing }for years with Bruce on this issue has not been enough to sway him }from the point of view that purity exceeds the value of functionality }here. :-) } } Jordan From owner-freebsd-current Fri Oct 3 12:11:48 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id MAA06311 for current-outgoing; Fri, 3 Oct 1997 12:11:48 -0700 (PDT) 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 MAA06287; Fri, 3 Oct 1997 12:11:33 -0700 (PDT) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.5/8.6.9) id FAA28989; Sat, 4 Oct 1997 05:05:45 +1000 Date: Sat, 4 Oct 1997 05:05:45 +1000 From: Bruce Evans Message-Id: <199710031905.FAA28989@godzilla.zeta.org.au> To: cracauer@cons.org, jkh@time.cdrom.com Subject: Re: xlock: caught signal 8 while running galaxy mode. Cc: freebsd-current@FreeBSD.ORG, Matthew.Thyer@dsto.defence.gov.au, ports@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >> I tried to convince people that FreeBSD hurts itself here, and the >> dying screensavers are my primary example how this can hurt users. The Dying screensavers are a good example of why trapping on FP exceptions is good: FP exceptions are often due to bugs, and trapping helps find the bugs. Galaxy mode gets a SIGFPE for an overflowing float to int conversion near line 363 in galaxy.c: --- #ifndef NO_VELOCITY_COLORING st->color = COLORSTEP * gt->galcol + ((int) ((v0 * v0 + v1 * v1 + v2 * v2) / (3.0 * DELTAT * DELTAT))) % COLORSTEP; #endif --- If (v0 * v0 + v1 * v1 + v2 * v2) is greater than or equal to INT_MAX + 1.0, then casting it to int gives undefined behaviour. The actual behaviour on i386's (if FP exceptions are not trapped) is to give the result INT_MIN. Note that this has the wrong sign as well as being too small. This happens to be unimportant here. >> solution was to tell the port maintainers to switch FP mode for their >> ports, which haven't happend for any port, as far as I know. According to "find /home/ncvs/ports -name 'patch-*' | xargs grep fpsetmask", fpsetmask() is used in the following ports: Scilab, felt, mpeg2codec, vfghostscript and has been used in the following ports: tcl, tcl74. >> There are bugs in our gcc that make relying on FP exceptions handled >> right dangerous and Bruce Evans felt it is better to through the >> signal, so that people get aware of the problem. I don't know of any bugs in gcc related to FP exceptions. >> With all respect to Bruce, I'm still conviced that we should switch to >> default to set exceptional values and not signal the process. Our gcc >> isn't that much worse than NetBSD's and Linux and those systems >> obviously didn't get into trouble, at least not my my applications. How is our gcc worse than NetBSD's or Linux's? >You're not alone in this point of view, but even several of us arguing >for years with Bruce on this issue has not been enough to sway him >from the point of view that purity exceeds the value of functionality >here. :-) Who is Bruce? ;-) bde's point of view is recorded in npx.h: --- /* Intel prefers long real (53 bit) precision */ #define __iBCS_NPXCW__ 0x262 /* wfj prefers temporary real (64 bit) precision */ #define __386BSD_NPXCW__ 0x362 /* * bde prefers 53 bit precision and all exceptions masked. --- This hasn't changed since 386BSD-0.1. I decided not to commit the change to the control word until someone fixes the error handling in lib/msun. Bruce From owner-freebsd-current Fri Oct 3 12:13:04 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id MAA06503 for current-outgoing; Fri, 3 Oct 1997 12:13:04 -0700 (PDT) Received: from celebris.tddhome (sil-wa4-51.ix.netcom.com [207.93.136.115]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id MAA06486 for ; Fri, 3 Oct 1997 12:12:57 -0700 (PDT) Received: (from tomdean@localhost) by celebris.tddhome (8.8.7/8.8.5) id MAA00994; Fri, 3 Oct 1997 12:12:50 -0700 (PDT) Date: Fri, 3 Oct 1997 12:12:50 -0700 (PDT) Message-Id: <199710031912.MAA00994@celebris.tddhome> From: Thomas Dean To: freebsd-current@FreeBSD.ORG Subject: Re: xlock: caught signal 8 while running galaxy mode. Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk FreeBSD clears the exception register in the fpu when the trap code catches an fpu exception prior to calling the user's handler, if any. In npx.c, the exception register is cleared prior to sending a SIGFPE to the process. I want to be able to catch an exception, if I want, and determine what the cause of the problem was, and, possibly work around it. I want my exception handler to know exactly what the exception was. tomdean From owner-freebsd-current Fri Oct 3 12:30:51 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id MAA07666 for current-outgoing; Fri, 3 Oct 1997 12:30:51 -0700 (PDT) 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 MAA07655 for ; Fri, 3 Oct 1997 12:30:45 -0700 (PDT) Received: (from jmg@localhost) by hydrogen.nike.efn.org (8.8.7/8.8.7) id MAA26726; Fri, 3 Oct 1997 12:30:07 -0700 (PDT) Message-ID: <19971003123007.53783@hydrogen.nike.efn.org> Date: Fri, 3 Oct 1997 12:30:07 -0700 From: John-Mark Gurney To: Julian Elischer Cc: Mike Smith , Invis , freebsd-current@FreeBSD.ORG Subject: Re: How much work does running -current take? References: <199710031410.XAA00752@word.smith.net.au> <34352DAD.ABD322C@whistle.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.69 In-Reply-To: <34352DAD.ABD322C@whistle.com>; from Julian Elischer on Fri, Oct 03, 1997 at 10:38:53AM -0700 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 Julian Elischer scribbled this message on Oct 3: > Mike Smith wrote: > > > > > > > > 1. If I install -current, will I have to do 'make worlds' or other 6 hour CPU > > > tasks often? > > > > You won't have to. You may want to. > > > > > 2. Will my system more often than not be able to boot and run most of the time? > > > i.e. I have one computer, I don't mind constant reboots, even making my own > > > code patches if necessary, but if this is something it's almost necessary > > > to have two machines for, please tell me! > > > > It can be helpful to have two systems, but things are generally better > > now than they were in terms of re-bootstrapping yourself. > > the problem is that new binaries cannot run on old machines > because there is a new system call > so everything falls over > especially /bin/sh so you can't even boot on your old kernel if > something goes wrong witf the new one. well... if you have multiple hard disks in your system, it isn't hard to fix... I'm about to do some testing of -current, and what I'm going to do is us one of the 32meg partions on the other hard drives as a -current boot, then I will just mount and symlink /usr to the place that I've done the temporary install to... then for -current testing I just boot the second hard drive.. and if problems occure, I can just go back to normal booting... note, this hasn't actually been attempted, so it's just an idea that I have floating around... and I plan on trying out this method when I test out Justin's new CAM scsi code.. -- 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 Oct 3 12:41:08 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id MAA08197 for current-outgoing; Fri, 3 Oct 1997 12:41:08 -0700 (PDT) Received: from artorius.sunflower.com (artorius.sunflower.com [24.124.0.13]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id MAA08192 for ; Fri, 3 Oct 1997 12:41:04 -0700 (PDT) Received: from localhost (lists@localhost) by artorius.sunflower.com (8.8.7/8.8.5) with SMTP id JAA00287 for ; Fri, 3 Oct 1997 09:40:53 -0500 (CDT) Date: Fri, 3 Oct 1997 09:40:51 -0500 (CDT) From: "Stephen D. Spencer" To: freebsd-current@freebsd.org Subject: Re: new command: doconfig In-Reply-To: <18521.875749960@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 On Wed, 1 Oct 1997, Jordan K. Hubbard wrote: > [...] > I don't think that anyone is really working on it - they keep > waiting for a miracle to happen and config(1) to simply go away. ;-) > [...] Hey now, don't wish *too* hard for that. A more intuitive configuration utility would be welcome; however, it's nice to have something simple (primitive?) to fall back on. Gosh... next thing you know, folks will be wish for vi to disappear (mutter, mutter, grumble, grumble :) -Stephen ----------------------------------------------------------------------------- - Stephen Spencer finger gladiatr@artorius.sunflower.com for - - administrator PGP key. - - Sunflower Datavision http://www.sunflower.com - ----------------------------------------------------------------------------- From owner-freebsd-current Fri Oct 3 12:52:40 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id MAA08912 for current-outgoing; Fri, 3 Oct 1997 12:52:40 -0700 (PDT) Received: from veda.is (adam@veda.is [193.4.230.1]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id MAA08886 for ; Fri, 3 Oct 1997 12:52:34 -0700 (PDT) Received: (from adam@localhost) by veda.is (8.8.7/8.8.5) id TAA19556; Fri, 3 Oct 1997 19:52:00 GMT Date: Fri, 3 Oct 1997 19:52:00 GMT From: Adam David Message-Id: <199710031952.TAA19556@veda.is> To: ortmann@sparc.ISl.NET (Daniel Ortmann) Cc: freebsd-current@freebsd.org Subject: Re: ipfw outputs 0's with default numbering References: <199709151623.LAA01132@watcher.isl.net> X-Newsreader: NN version 6.5.0 #2 (NOV) Sender: owner-freebsd-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >ipfw -f flush >ipfw add 1000 pass all from 127.0.0.1 to 127.0.0.1 >ipfw add pass all from ${ip} to ${net}:${mask} >Then I get output as follows ... >Flushed all rules. >01000 allow ip from 127.0.0.1 to 127.0.0.1 >00000 allow ip from 199.3.25.128 to 199.3.25.0/24 >But "ipfw list" shows the following ... >01000 allow ip from 127.0.0.1 to 127.0.0.1 >01100 allow ip from 199.3.25.128 to 199.3.25.0/24 >I expected to see the real sequence numbers instead of just 0's. Is the 0000 intended to show that the rule is inserted according to automatic numbering, or would it be better to intend that the actual number assigned gets displayed? -- Adam David From owner-freebsd-current Fri Oct 3 13:56:33 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id NAA12304 for current-outgoing; Fri, 3 Oct 1997 13:56:33 -0700 (PDT) Received: from hobbes.saturn-tech.com (drussell@drussell.internode.net [198.161.228.154]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id NAA12296 for ; Fri, 3 Oct 1997 13:56:12 -0700 (PDT) Received: from localhost (drussell@localhost) by hobbes.saturn-tech.com (8.8.4/8.8.2) with SMTP id OAA06250; Fri, 3 Oct 1997 14:54:47 -0600 (MDT) Date: Fri, 3 Oct 1997 14:54:47 -0600 (MDT) From: Doug Russell To: Satoshi Asami cc: lamaster@george.arc.nasa.gov, wollman@khavrinen.lcs.mit.edu, current@FreeBSD.ORG Subject: Re: Which PCI Ethernet card is best for FreeBSD-current? In-Reply-To: <199710030659.XAA12834@silvia.HIP.Berkeley.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 Thu, 2 Oct 1997, Satoshi Asami wrote: > * From: Doug Russell > > At 100Mbps, Intel and SMC (old 9332DST) cards blow 595TX into chunks. > My small test was to create a ccd on both ends of a crossover > connection and ftp a large file over. Result: over 10MB/s with > Intel/SMC, less than 5MB/s with 3c595TX. I'm not surprised they aren't that hot at 100Mbps.... That's about what I figured. :) > Also, the 595TX exhibited very poor performance with a noisy link. > TCP performance was like 100~200KB/s on my workstation with a 10BaseT > shared net with a long cable. I changed it with an old SMC card > (10BaseT), I can get 500KB/s (or some other reasonable number, > depending on how congested the line is at that time). That is quite sick.... Later...... From owner-freebsd-current Fri Oct 3 14:11:25 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id OAA13083 for current-outgoing; Fri, 3 Oct 1997 14:11:25 -0700 (PDT) Received: from GndRsh.aac.dev.com (GndRsh.aac.dev.com [198.145.92.241]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id OAA13078 for ; Fri, 3 Oct 1997 14:11:21 -0700 (PDT) Received: (from rgrimes@localhost) by GndRsh.aac.dev.com (8.8.5/8.7.3) id OAA00273; Fri, 3 Oct 1997 14:04:19 -0700 (PDT) From: "Rodney W. Grimes" Message-Id: <199710032104.OAA00273@GndRsh.aac.dev.com> Subject: Re: Which PCI Ethernet card is best for FreeBSD-current? In-Reply-To: <19971002162324.02664@klemm.gtn.com> from Andreas Klemm at "Oct 2, 97 04:23:24 pm" To: andreas@klemm.gtn.com (Andreas Klemm) Date: Fri, 3 Oct 1997 14:04:19 -0700 (PDT) Cc: ache@nagual.pp.ru, 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 > On Thu, Oct 02, 1997 at 02:54:57PM +0930, Mike Smith wrote: > > > Could someone share his experience with me and tell about 2-3 best models? > > > Stability is more essential than performance for me. > > > > Anything using the Realtek RTL8029 will be stable, for sure. Almost > > any "NE2000 compatible" card will do. Performance won't be so great > > though (but quite adequate). > > > > Alternatively many vendors do cards based on the Digital DC2104x chips, > > and these perform better and are also generally very stable. > > Fastest and possibly best supported should be the EtherExpress/Pro 100B > card (10/100). Supports full duplex mode. As far as I remember Rodney > said about this card, that it is very server friendly. If I am the ``Rodney'' you are refering to above, I do not recommend the EtherExpress cards, or infact any card made by Intel, I sell and recommend DEC DC21x4x based cards, if my client specifically request the EtherExpress/ Pro 100B I will sell it, buy only when specifically requested. > This card has been recommended many times on different fbsd mailinglists. > So if there would be a problem with this card, people would surely > complain very loud and clear ;-) > > I suggest best would be to browse the fbsd mailing list archive > for technical discussion about this card, to be sure. > > Andreas /// > > -- > Andreas Klemm powered by ,,symmetric multiprocessor FreeBSD'' > andreas@klemm.gtn.com - http://www.freebsd.org/~fsmp/SMP/SMP.html > andreas@FreeBSD.ORG - http://www.freebsd.org/~fsmp/SMP/benches.html > -- Rod Grimes rgrimes@gndrsh.aac.dev.com Accurate Automation, Inc. Reliable computers for FreeBSD From owner-freebsd-current Fri Oct 3 14:27:47 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id OAA13676 for current-outgoing; Fri, 3 Oct 1997 14:27:47 -0700 (PDT) Received: from whistle.com (s205m131.whistle.com [207.76.205.131]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id OAA13670 for ; Fri, 3 Oct 1997 14:27:42 -0700 (PDT) Received: (from smap@localhost) by whistle.com (8.7.5/8.6.12) id OAA17187; Fri, 3 Oct 1997 14:27:11 -0700 (PDT) Received: from bubba.whistle.com(207.76.205.7) by whistle.com via smap (V1.3) id sma017185; Fri Oct 3 14:27:02 1997 Received: (from archie@localhost) by bubba.whistle.com (8.8.5/8.6.12) id OAA23642; Fri, 3 Oct 1997 14:27:02 -0700 (PDT) From: Archie Cobbs Message-Id: <199710032127.OAA23642@bubba.whistle.com> Subject: Re: ipfw outputs 0's with default numbering In-Reply-To: <199710031952.TAA19556@veda.is> from Adam David at "Oct 3, 97 07:52:00 pm" To: adam@veda.is (Adam David) Date: Fri, 3 Oct 1997 14:27:01 -0700 (PDT) Cc: ortmann@sparc.ISl.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 Adam David writes: > >ipfw -f flush > >ipfw add 1000 pass all from 127.0.0.1 to 127.0.0.1 > >ipfw add pass all from ${ip} to ${net}:${mask} > > >Then I get output as follows ... > > >Flushed all rules. > >01000 allow ip from 127.0.0.1 to 127.0.0.1 > >00000 allow ip from 199.3.25.128 to 199.3.25.0/24 > > >But "ipfw list" shows the following ... > > >01000 allow ip from 127.0.0.1 to 127.0.0.1 > >01100 allow ip from 199.3.25.128 to 199.3.25.0/24 > > >I expected to see the real sequence numbers instead of just 0's. > > Is the 0000 intended to show that the rule is inserted according to > automatic numbering, or would it be better to intend that the actual > number assigned gets displayed? Yes and yes :-) -Archie ___________________________________________________________________________ Archie Cobbs * Whistle Communications, Inc. * http://www.whistle.com From owner-freebsd-current Fri Oct 3 15:24:08 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id PAA16681 for current-outgoing; Fri, 3 Oct 1997 15:24:08 -0700 (PDT) Received: from consys.com (consys.com [209.60.202.194]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id PAA16675 for ; Fri, 3 Oct 1997 15:24:02 -0700 (PDT) Received: from cssunix.conceptual.com (cssunix.conceptual.com [10.0.2.5]) by consys.com (8.8.6/8.8.6) with ESMTP id PAA03739; Fri, 3 Oct 1997 15:23:56 -0700 (MST) Received: from cssunix.conceptual.com (localhost [127.0.0.1]) by cssunix.conceptual.com (8.8.5/8.8.6) with ESMTP id PAA04679; Fri, 3 Oct 1997 15:23:55 -0700 (MST) Message-Id: <199710032223.PAA04679@cssunix.conceptual.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 "Sat, 04 Oct 1997 05:05:45 +1000." <199710031905.FAA28989@godzilla.zeta.org.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 03 Oct 1997 15:23:55 -0700 From: "Russell L. Carter" Sender: owner-freebsd-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk } }Who is Bruce? ;-) bde's point of view is recorded in npx.h: } }--- }/* Intel prefers long real (53 bit) precision */ }#define __iBCS_NPXCW__ 0x262 }/* wfj prefers temporary real (64 bit) precision */ }#define __386BSD_NPXCW__ 0x362 }/* } * bde prefers 53 bit precision and all exceptions masked. }--- } Interesting, in the long run 0x200 is the most "standard", if Sun has its way. I did not realize that it was possible 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 ;-) However, your comment in npx.h opines that "64-bit precision often gives bad results", and that is not true at all. More accurately, (oops, I punned:) if computing intermediate values to higher precision causes *different* final results, then in all but the mostly highly contrived cases the problem lies with the code, or in your terminology it's a bug :). (in that case the algorithm is unstable wrt precision). Not to say counterexamples don't exist but they are uncommon enough to be addressed in Kahan's SIAM talk this year. So there is an inconsistency here: on the one hand your preferences yield compatibility for buggy programs when the bug is instability of the program algorithm when subjected to (increased) intermediate precision; OTOH if the "bug" is manifested by something that generates an exception, FreeBSD by default calls it out. Java is consistent, there is one fp format and as far as fp exceptions go mask 'em all! What do I think? I don't really care that much, as long as *I* can modify that control word. And java doesn't let me do that... Regards, Russell From owner-freebsd-current Fri Oct 3 15:54:37 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id PAA18302 for current-outgoing; Fri, 3 Oct 1997 15:54:37 -0700 (PDT) Received: from seagull.cdrom.com (root@seagull.cdrom.com [204.216.27.14]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id PAA18274; Fri, 3 Oct 1997 15:54:20 -0700 (PDT) Received: from cons.org (knight.cons.org [194.233.237.86]) by seagull.cdrom.com (8.8.6/8.6.6) with ESMTP id PAA07791 ; Fri, 3 Oct 1997 15:53:35 -0700 (PDT) Received: (from cracauer@localhost) by cons.org (8.8.5/8.7.3) id AAA13984; Sat, 4 Oct 1997 00:49:49 +0200 (CEST) Message-ID: <19971004004948.45758@cons.org> Date: Sat, 4 Oct 1997 00:49:48 +0200 From: Martin Cracauer To: Bruce Evans Cc: cracauer@cons.org, jkh@time.cdrom.com, freebsd-current@FreeBSD.ORG, Matthew.Thyer@dsto.defence.gov.au, ports@FreeBSD.ORG Subject: Re: xlock: caught signal 8 while running galaxy mode. References: <199710031905.FAA28989@godzilla.zeta.org.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.81 In-Reply-To: <199710031905.FAA28989@godzilla.zeta.org.au>; from Bruce Evans on Sat, Oct 04, 1997 at 05:05:45AM +1000 Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk In <199710031905.FAA28989@godzilla.zeta.org.au>, Bruce Evans wrote: > >> I tried to convince people that FreeBSD hurts itself here, and the > >> dying screensavers are my primary example how this can hurt users. The > > Dying screensavers are a good example of why trapping on FP exceptions > is good: FP exceptions are often due to bugs, and trapping helps find > the bugs. Sure. But most free (and commercial) software has been developed and tested on machines that don't trap. So if applications show SIGFPE on FreeBSD, I can nothingtheless assume that either: a) The developer wrote the program expecting to get IEEE exceptional values and handles them just fine and just forgot to set the status in case the default isn't what he expects. Quite reasonable given the number of platforms that don't trap by default. b) The bugs don't matter. Many programs, especially free productivity tools use floating point just for nonimportant graphical effects, calculating progress bars and such. xlockmore is probably an example. Drawing something wrong isn't an important bug for a screen saver, dying is. c) I have no idea if the developer was aware of his floating point bugs, but the program is so useful for me that I have to assume that his testing on a nontrapping platform ensured that it is useable. I want to use it, preferrably without patching it first. Again, I think the killer argument is that a serious FP user is much more likely to be aware of the need to set the mask in case he needs traps as is a random user to be able to even recognize why his program dumps core. We could at least improve the error messages. > >> solution was to tell the port maintainers to switch FP mode for their > >> ports, which haven't happend for any port, as far as I know. > > According to "find /home/ncvs/ports -name 'patch-*' | xargs grep fpsetmask", > fpsetmask() is used in the following ports: > > Scilab, felt, mpeg2codec, vfghostscript > > and has been used in the following ports: > > tcl, tcl74. OK, didn't really look. Given the number of applications aware of the problem, we probably are best off changing bsd.port.mk to add a patch to set the mask by default. > >> There are bugs in our gcc that make relying on FP exceptions handled > >> right dangerous and Bruce Evans felt it is better to through the > >> signal, so that people get aware of the problem. > > I don't know of any bugs in gcc related to FP exceptions. > > >> With all respect to Bruce, I'm still conviced that we should switch to > >> default to set exceptional values and not signal the process. Our gcc > >> isn't that much worse than NetBSD's and Linux and those systems > >> obviously didn't get into trouble, at least not my my applications. > > How is our gcc worse than NetBSD's or Linux's? s/gcc/FreeBSD/ If I remeber correctly (and the one who told me was probably you), one can't disable FP exceptions easily without hiding stack exceptions as well. Behaviour for compile-time and runtime evaluation is different in quite a few places. There was something that we can't set errno (as we should accourding to POSIX) if we use IEEE non-trapping. Correct me if I'm wrong, but if we don't trap, these's little point in setting errno, isn't it? As I understand, we don't have working errno support anyway. So there's nothing to loose. The second problems about compile-and-runtime evalution is cleary only an issue for serious FP users. And trapping doesn't fix these bugs and the user can't do anything about them, it just make the user aware of them. For me, this isn't worth the trouble at other places. I'm not sure about the implications of the first issue. [...] > I decided not to commit the change to the control word until someone > fixes the error handling in lib/msun. Well, is there any agreement which standard to follow? Is plain IEEE reasonable? Maybe we can add a kernel config value to set the default mask? That way, we can't make npx.h reflect the real value, but I found no place in userland that uses it. Martin P.S.: To make it clear for other readers: I don't have a real clue about all the issues at hand, I just want a compatible default ignoring the problems. :-) -- %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% Martin Cracauer http://www.cons.org/cracauer cracauer@wavehh.hanse.de (batched, preferred for large mails) Tel.: (daytime) +4940 41478712 Fax.: (daytime) +4940 41478715 Tel.: (private) +4940 5221829 Fax.: (private) +4940 5228536 Paper: (private) Waldstrasse 200, 22846 Norderstedt, Germany From owner-freebsd-current Sat Oct 4 00:45:59 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id AAA04148 for current-outgoing; Sat, 4 Oct 1997 00:45:59 -0700 (PDT) Received: from gratis.grondar.za (gratis.grondar.za [196.7.18.133]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id AAA04137 for ; Sat, 4 Oct 1997 00:45:51 -0700 (PDT) Received: from greenpeace.grondar.za (Ekmf7DPRoRsGYF2svByfYgnaLvsOdGCr@greenpeace.grondar.za [196.7.18.132]) by gratis.grondar.za (8.8.7/8.8.7) with ESMTP id JAA05632 for ; Sat, 4 Oct 1997 09:45:50 +0200 (SAT) Received: from greenpeace.grondar.za (YSe1Ghe8XvW/nhB/ewb/NgYeITqBoCQJ@localhost [127.0.0.1]) by greenpeace.grondar.za (8.8.7/8.8.7) with ESMTP id JAA28726 for ; Sat, 4 Oct 1997 09:45:51 +0200 (SAT) Message-Id: <199710040745.JAA28726@greenpeace.grondar.za> X-Mailer: exmh version 2.0zeta 7/24/97 To: current@freebsd.org Subject: Patches so parallel make works (on SMP) Mime-Version: 1.0 Content-Type: multipart/mixed ; boundary="==_Exmh_6587434810" Date: Sat, 04 Oct 1997 09:45:50 +0200 From: Mark Murray Sender: owner-freebsd-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk This is a multipart MIME message. --==_Exmh_6587434810 Content-Type: text/plain; charset=us-ascii Hi Some folks posted these patches some days (weeks?) ago, and they weren't really followed up. Seing that I have a brand new SMP-capable motherboard witrh 2xP5/200, I felt the need to make this work. The original patches were fore an earlier CURRENT, and some of the bits have been applied. Included in this are the diffs to my tree (as of CURRENT/3-Oct-1997), and these patches have been used (twice!) to do a # make -j12 world with /usr/obj _empty_to_start_with_. There is a DRAMATIC improvement in the speed of a make world when you do this!! I include the patches, and the README parts of the original authors' postings. Enjoy! M -- Mark Murray Join the anti-SPAM movement: http://www.cauce.org --==_Exmh_6587434810 Content-Type: text/plain ; name="README2"; charset=us-ascii Content-Description: README2 Content-Disposition: attachment; filename="README2" Message-Id: <199709141740.CAA02407@peace.calm.imasy.or.jp> To: nnd@itfs.nsk.su Cc: current@FreeBSD.ORG Cc: ume@calm.imasy.or.jp Subject: Re: Make and SMP - what can be done ? References: <5t64ts$7ae@news.itfs.nsk.su> Date: Mon, 15 Sep 1997 02:40:10 +0900 From: Hajimu UMEMOTO >>>>> On 17 Aug 1997 06:15:24 GMT, nnd@itfs.nsk.su said: nnd> Here is a report of my experiments in "parallel" nnd> world making. I applied your patch with recent -current, and tried `make -j8 buildworld'. It failed in sys/i386/boot/netboot. sys/i386/boot/netboot/Makefile is seems to not parallel-safe. Here is a patch. --==_Exmh_6587434810 Content-Type: text/plain ; name="README"; charset=us-ascii Content-Description: README Content-Disposition: attachment; filename="README" From: nnd@itfs.nsk.su To: current@FreeBSD.ORG Subject: Re: Make and SMP - what can be done ? Date: 25 Aug 1997 12:18:04 GMT Message-ID: <5trt5s$kh1@news.itfs.nsk.su> References: <199708130432.VAA06415@silvia.HIP.Berkeley.EDU> <5t64ts$7ae@news.it fs.nsk.su> This weekend's results of "parallel buildworld" investigations: To make 'buildworld' target making more "parallel" I try to do 'make depend' step with '-j12' flag and fails (;-). 1) First reason to this fault is in 'bsd.dep.mk' where 'depend' target usually looks like: depend: beforedepend .depend afterdepend _SUBDIR which (from the names of 'before/after'depend targets) assumes "sequential" evaluation. The patch (bsd.dep-patch) address this problem and (nearly) solves it. The only unsolved case - if there is 'Makefile' wich sets dependencies for 'beforedepend' target BUT not defines actions for such a rule. It turns out that all such cases in FreeBSD-3.0 src tree can be solved by deleting such a rule for 'beforedepend' from corresponding 'Makefile' and adding all the sources from this rule to the SRCS variable (see the patches for Makefiles later in this message). 2) The second source of troubles was presented by "functions with many results" (;-) - i.e. ${YACC} or ${BISON} commands which produces both and and have the following sort of rules for them in Makefile(s): foo.c bar.h: baz.y ${YACC} ... baz.y mv y.tab.c foo.c mv y.tab.h bar.h Such a rules obviously presents problems when we try to use "parallel making". All the reallife (i.e. from FreeBSD src tree) examples of such rules can be made "parallel-safe" by adding the rule of the form: .ORDER: foo.c bar.h to the corresponding Makefile. To be correct such an additional rule must followed the requirement - "The first source of this rule must be required for all those targets (all,install, depend ...) for which the second one is necessary". 3) src/gnu/cc/cc_tools/Makefile is too complex (to me) to make it "parallel safe" with respect to 'make -j12 depend' ;-( So I gave up and insert '.SINGLESHELL:' rule in this Makefile which sets the 'compatMake' compatible mode ;-) 4) Some of the 'builworld' steps are too "sequential" - f.e cleaning or rebuilding of the 'obj' tree. There is the shell's 'for' loop through SUBDIRs and small number of the (simple) commands for each of (sub)directory. To feed SMP system with more work I change some of such steps (see the 'par-" part in Makefile.patch). Such a construct must be used very carefully - it can produce too many processes ;-). As a result my last successfull 'make -j12 buildworld' produced 170.9% processor's usage and takes 2:54:00 as opposed to 104.1% and 4:34:23 for 'make buildworld' (without any patches). To achieve this I use following patches: 1) 'make-patch' - propagate '-B' flag to inner 'make's; 2) 'bsd.dep-patch' - to "order" depend's subtargets; 3) 'makefiles-patch' - to make various Makefiles "parallel-safe"; 4) 'Makefile-patch' - patch to src/Makefile to restrict "parallelism" in some cases and to "broaden" it in other steps. --==_Exmh_6587434810 Content-Type: text/plain; name="SMP.diff"; charset=us-ascii Content-Description: SMP.diff Content-Transfer-Encoding: quoted-printable Content-Disposition: attachment; filename="SMP.diff" Index: Makefile =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D RCS file: /home/ncvs/src/Makefile,v retrieving revision 1.148 diff -u -d -r1.148 Makefile --- Makefile 1997/09/28 16:25:28 1.148 +++ Makefile 1997/10/03 05:58:33 @@ -154,7 +154,7 @@ cd ${.CURDIR} && ${MAKE} pre-world .endif cd ${.CURDIR} && ${MAKE} buildworld - cd ${.CURDIR} && ${MAKE} installworld + cd ${.CURDIR} && ${MAKE} -B installworld .if target(post-world) @echo @echo "--------------------------------------------------------------" @@ -224,9 +224,10 @@ mkdir -p ${WORLDTMP}/usr/bin cd ${.CURDIR}/usr.bin/make && \ ${IBMAKE} -I${.CURDIR}/share/mk \ - ${CLEANDIR} ${OBJDIR} depend && \ + -B ${CLEANDIR} ${OBJDIR} depend && \ + ${IBMAKE} -I${.CURDIR}/share/mk ${MK_FLAGS} all && \ ${IBMAKE} -I${.CURDIR}/share/mk ${MK_FLAGS} \ - all install clean cleandepend + -B all install clean cleandepend @echo @echo "--------------------------------------------------------------" @echo " Making hierarchy" @@ -237,14 +238,14 @@ @echo "--------------------------------------------------------------" @echo " Cleaning up the obj tree" @echo "--------------------------------------------------------------" - cd ${.CURDIR} && ${BMAKE} ${CLEANDIR} + cd ${.CURDIR} && ${BMAKE} par-${CLEANDIR} .endif .if !defined(NOOBJDIR) @echo @echo "--------------------------------------------------------------" @echo " Rebuilding the obj tree" @echo "--------------------------------------------------------------" - cd ${.CURDIR} && ${BMAKE} obj + cd ${.CURDIR} && ${BMAKE} par-obj .endif @echo @echo "--------------------------------------------------------------" @@ -280,7 +281,7 @@ @echo "--------------------------------------------------------------" @echo " Rebuilding dependencies" @echo "--------------------------------------------------------------" - cd ${.CURDIR} && ${XMAKE} depend + cd ${.CURDIR} && ${XMAKE} -j4 par-depend @echo @echo "--------------------------------------------------------------" @echo " Building everything.." @@ -423,11 +424,14 @@ cd ${.CURDIR}/include && make symlinks .endif cd ${.CURDIR}/usr.bin/make && ${MAKE} depend && \ - ${MAKE} ${MK_FLAGS} all install ${CLEANDIR} ${OBJDIR} + ${MAKE} ${MK_FLAGS} all && \ + ${MAKE} ${MK_FLAGS} -B install ${CLEANDIR} ${OBJDIR} cd ${.CURDIR}/usr.bin/xinstall && ${MAKE} depend && \ - ${MAKE} ${MK_FLAGS} all install ${CLEANDIR} ${OBJDIR} + ${MAKE} ${MK_FLAGS} all && \ + ${MAKE} ${MK_FLAGS} -B install ${CLEANDIR} ${OBJDIR} cd ${.CURDIR}/usr.bin/lex && ${MAKE} bootstrap && ${MAKE} depend && \ - ${MAKE} ${MK_FLAGS} -DNOLIB all install ${CLEANDIR} + ${MAKE} ${MK_FLAGS} -DNOLIB && \ + ${MAKE} ${MK_FLAGS} -DNOLIB -B install ${CLEANDIR} .if !defined(NOOBJDIR) cd ${.CURDIR}/usr.bin/lex && ${MAKE} obj .endif @@ -441,8 +445,9 @@ # on cleaned away headers in ${WORLDTMP}. # include-tools: - cd ${.CURDIR}/usr.bin/rpcgen && ${MAKE} cleandepend depend && \ - ${MAKE} ${MK_FLAGS} all install ${CLEANDIR} ${OBJDIR} + cd ${.CURDIR}/usr.bin/rpcgen && ${MAKE} -B cleandepend depend && \ + ${MAKE} ${MK_FLAGS} all && \ + ${MAKE} ${MK_FLAGS} -B install ${CLEANDIR} ${OBJDIR} = # # includes - possibly generate and install the include files. @@ -453,7 +458,7 @@ mtree -deU -f ${.CURDIR}/etc/mtree/BSD.include.dist \ -p ${DESTDIR}/usr/include .endif - cd ${.CURDIR}/include && ${MAKE} all install + cd ${.CURDIR}/include && ${MAKE} -B all install cd ${.CURDIR}/gnu/include && ${MAKE} install cd ${.CURDIR}/gnu/lib/libmp && ${MAKE} beforeinstall cd ${.CURDIR}/gnu/lib/libobjc && ${MAKE} beforeinstall @@ -528,7 +533,8 @@ usr.bin/ranlib \ usr.bin/uudecode cd ${.CURDIR}/$d && ${MAKE} depend && \ - ${MAKE} ${MK_FLAGS} all install ${CLEANDIR} ${OBJDIR} + ${MAKE} ${MK_FLAGS} all && \ + ${MAKE} ${MK_FLAGS} -B install ${CLEANDIR} ${OBJDIR} .endfor = # @@ -537,43 +543,53 @@ libraries: .if exists(lib/csu/i386) cd ${.CURDIR}/lib/csu/i386 && ${MAKE} depend && \ - ${MAKE} ${MK_FLAGS} all install ${CLEANDIR} ${OBJDIR} + ${MAKE} ${MK_FLAGS} all && \ + ${MAKE} ${MK_FLAGS} -B install ${CLEANDIR} ${OBJDIR} .endif .if exists(lib/libcompat) cd ${.CURDIR}/lib/libcompat && ${MAKE} depend && \ - ${MAKE} ${MK_FLAGS} all install ${CLEANDIR} ${OBJDIR} + ${MAKE} ${MK_FLAGS} all && \ + ${MAKE} ${MK_FLAGS} -B install ${CLEANDIR} ${OBJDIR} .endif .if exists(lib/libncurses) cd ${.CURDIR}/lib/libncurses && ${MAKE} depend && \ - ${MAKE} ${MK_FLAGS} all install ${CLEANDIR} ${OBJDIR} + ${MAKE} ${MK_FLAGS} all && \ + ${MAKE} ${MK_FLAGS} -B install ${CLEANDIR} ${OBJDIR} .endif .if exists(lib/libtermcap) cd ${.CURDIR}/lib/libtermcap && ${MAKE} depend && \ - ${MAKE} ${MK_FLAGS} all install ${CLEANDIR} ${OBJDIR} + ${MAKE} ${MK_FLAGS} all && \ + ${MAKE} ${MK_FLAGS} -B install ${CLEANDIR} ${OBJDIR} .endif .if exists(gnu) cd ${.CURDIR}/gnu/lib && ${MAKE} depend && \ - ${MAKE} ${MK_FLAGS} all install ${CLEANDIR} ${OBJDIR} + ${MAKE} ${MK_FLAGS} all && \ + ${MAKE} ${MK_FLAGS} -B install ${CLEANDIR} ${OBJDIR} .endif .if exists(secure) && !defined(NOCRYPT) && !defined(NOSECURE) cd ${.CURDIR}/secure/lib && ${MAKE} depend && \ - ${MAKE} ${MK_FLAGS} all install ${CLEANDIR} ${OBJDIR} + ${MAKE} ${MK_FLAGS} all && \ + ${MAKE} ${MK_FLAGS} -B install ${CLEANDIR} ${OBJDIR} .endif .if exists(lib) cd ${.CURDIR}/lib && ${MAKE} depend && \ - ${MAKE} ${MK_FLAGS} all install ${CLEANDIR} ${OBJDIR} + ${MAKE} ${MK_FLAGS} all && \ + ${MAKE} ${MK_FLAGS} -B install ${CLEANDIR} ${OBJDIR} .endif .if exists(usr.bin/lex/lib) cd ${.CURDIR}/usr.bin/lex/lib && ${MAKE} depend && \ - ${MAKE} ${MK_FLAGS} all install ${CLEANDIR} ${OBJDIR} + ${MAKE} ${MK_FLAGS} all && \ + ${MAKE} ${MK_FLAGS} -B install ${CLEANDIR} ${OBJDIR} .endif .if !defined(NOCRYPT) && defined(MAKE_KERBEROS4) cd ${.CURDIR}/kerberosIV/lib && ${MAKE} depend && \ - ${MAKE} ${MK_FLAGS} all install ${CLEANDIR} ${OBJDIR} + ${MAKE} ${MK_FLAGS} all && \ + ${MAKE} ${MK_FLAGS} -B install ${CLEANDIR} ${OBJDIR} .endif .if exists(usr.sbin/pcvt/keycap) cd ${.CURDIR}/usr.sbin/pcvt/keycap && ${MAKE} depend && \ - ${MAKE} ${MK_FLAGS} all install ${CLEANDIR} ${OBJDIR} + ${MAKE} ${MK_FLAGS} all && \ + ${MAKE} ${MK_FLAGS} -B install ${CLEANDIR} ${OBJDIR} .endif = # @@ -644,7 +660,25 @@ usr.sbin/mtree \ usr.sbin/zic cd ${.CURDIR}/$d && ${MAKE} depend && \ - ${MAKE} ${MK_FLAGS} all install ${CLEANDIR} ${OBJDIR} + ${MAKE} ${MK_FLAGS} all && \ + ${MAKE} ${MK_FLAGS} -B install ${CLEANDIR} ${OBJDIR} +.endfor + +.for __target in clean cleandir obj depend +.for entry in ${SUBDIR} +${entry}.${__target}__D: .PHONY + if test -d ${.CURDIR}/${entry}.${MACHINE}; then \ + ${ECHODIR} "=3D=3D=3D> ${DIRPRFX}${entry}.${MACHINE}"; \ + edir=3D${entry}.${MACHINE}; \ + cd ${.CURDIR}/$${edir}; \ + else \ + ${ECHODIR} "=3D=3D=3D> ${DIRPRFX}${entry}"; \ + edir=3D${entry}; \ + cd ${.CURDIR}/$${edir}; \ + fi; \ + ${MAKE} ${__target} DIRPRFX=3D${DIRPRFX}$${edir}/ +.endfor +par-${__target}: ${SUBDIR:S/$/.${__target}__D/} .endfor = .include Index: bin/sh/Makefile =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D RCS file: /home/ncvs/src/bin/sh/Makefile,v retrieving revision 1.22 diff -u -d -r1.22 Makefile --- Makefile 1997/08/25 19:50:01 1.22 +++ Makefile 1997/10/02 22:03:09 @@ -7,7 +7,8 @@ mystring.c options.c output.c parser.c printf.c redir.c show.c \ trap.c var.c GENSRCS=3D arith.c arith_lex.c builtins.c init.c nodes.c syntax.c -SRCS=3D ${SHSRCS} ${GENSRCS} +GENHDRS=3D builtins.h nodes.h syntax.h token.h +SRCS=3D ${SHSRCS} ${GENSRCS} ${GENHDRS} = DPADD+=3D ${LIBL} ${LIBEDIT} ${LIBTERMCAP} LDADD+=3D -ll -ledit -ltermcap @@ -19,13 +20,13 @@ = .PATH: ${.CURDIR}/bltin ${.CURDIR}/../../usr.bin/printf = -CLEANFILES+=3D builtins.h mkinit mkinit.o mknodes mknodes.o \ +CLEANFILES+=3D mkinit mkinit.o mknodes mknodes.o \ mksyntax mksyntax.o \ - nodes.h syntax.h token.h y.tab.h -CLEANFILES+=3D ${GENSRCS} + y.tab.h +CLEANFILES+=3D ${GENSRCS} ${GENHDRS} = -beforedepend: builtins.h nodes.h syntax.h token.h = +.ORDER: builtins.c builtins.h builtins.c builtins.h: mkbuiltins builtins.def cd ${.CURDIR}; sh mkbuiltins ${.OBJDIR} = @@ -45,9 +46,11 @@ mksyntax: mksyntax.o mksyntax.o: mksyntax.c # XXX and many headers = +.ORDER: nodes.c nodes.h nodes.c nodes.h: mknodes nodetypes nodes.c.pat ./mknodes ${.CURDIR}/nodetypes ${.CURDIR}/nodes.c.pat = +.ORDER: syntax.c syntax.h syntax.c syntax.h: mksyntax ./mksyntax = Index: gnu/usr.bin/cc/cc1plus/Makefile =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D RCS file: /home/ncvs/src/gnu/usr.bin/cc/cc1plus/Makefile,v retrieving revision 1.12 diff -u -d -r1.12 Makefile --- Makefile 1997/06/29 06:03:27 1.12 +++ Makefile 1997/10/02 22:01:17 @@ -6,7 +6,7 @@ .PATH: ${.CURDIR}/../../../../contrib/gcc/cp = PROG =3D cc1plus -SRCS =3D parse.c \ +SRCS =3D parse.c parse.h \ call.c class.c cvt.c decl.c decl2.c edsel.c errfn.c \ error.c except.c expr.c gc.c init.c lex.c method.c pt.c \ ptree.c repo.c search.c sig.c spew.c tree.c typeck.c typeck2.c xref.c @@ -17,6 +17,7 @@ LDADD+=3D ${LIBCC_INT} CFLAGS+=3D -I. # I mean it. = +.ORDER: parse.c parse.h parse.c parse.h: parse.y ${BISON} -d ${GCCDIR}/cp/parse.y -o parse.c = grep '^#define[ ]*YYEMPTY' parse.c >>parse.h Index: gnu/usr.bin/cc/cc_tools/Makefile =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D RCS file: /home/ncvs/src/gnu/usr.bin/cc/cc_tools/Makefile,v retrieving revision 1.3 diff -u -d -r1.3 Makefile --- Makefile 1997/02/22 15:44:58 1.3 +++ Makefile 1997/10/02 22:01:17 @@ -26,8 +26,9 @@ = .endfor = +.ORDER: bi-parser.c bi-parser.h bi-parser.c bi-parser.h: bi-parser.y - ${BISON} ${BISONFLAGS} -d ${.ALLSRC} -o ${.TARGET} + ${BISON} ${BISONFLAGS} -d ${.ALLSRC} -o bi-parser.c = SRCS+=3D bi-parser.c bi-parser.h = @@ -82,6 +83,7 @@ = #-----------------------------------------------------------------------= # C parser +.ORDER: c-parse.c c-parse.h c-parse.c c-parse.h: c-parse.in sed -e "/^ifobjc$$/,/^end ifobjc$$/d" \ -e "/^ifc$$/d" -e "/^end ifc$$/d" \ @@ -94,6 +96,7 @@ = #-----------------------------------------------------------------------= # objc parser +.ORDER: objc-parse.c objc-parse.h objc-parse.c objc-parse.h: c-parse.in sed -e "/^ifc$$/,/^end ifc$$/d" \ -e "/^ifobjc$$/d" -e "/^end ifobjc$$/d" \ @@ -114,6 +117,12 @@ = #-----------------------------------------------------------------------= all: ${BINFORMAT} ${SRCS} + +#-----------------------------------------------------------------------= +# Make 'depend' in compat mode +.if make(depend) +.SINGLESHELL: +.endif = beforedepend: ${BINFORMAT} = Index: gnu/usr.bin/cc/cpp/Makefile =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D RCS file: /home/ncvs/src/gnu/usr.bin/cc/cpp/Makefile,v retrieving revision 1.9 diff -u -d -r1.9 Makefile --- Makefile 1997/02/22 15:44:59 1.9 +++ Makefile 1997/10/02 22:01:17 @@ -9,6 +9,7 @@ MAN1=3D cccp.1 MLINKS=3D cccp.1 cpp.1 = +.ORDER: cexp.c cexp.h cexp.c cexp.h: cexp.y ${BISON} -d ${GCCDIR}/cexp.y -o cexp.c = Index: gnu/usr.bin/gdb/gdb/Makefile =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D RCS file: /home/ncvs/src/gnu/usr.bin/gdb/gdb/Makefile,v retrieving revision 1.28 diff -u -d -r1.28 Makefile --- Makefile 1997/05/02 11:22:51 1.28 +++ Makefile 1997/10/02 22:01:17 @@ -39,7 +39,8 @@ #CFLAGS+=3D -g = CLEANFILES+=3D c-exp.c f-exp.c m2-exp.c init.c y.tab.h init.c-tmp -beforedepend: c-exp.c f-exp.c m2-exp.c init.c +#beforedepend: c-exp.c f-exp.c m2-exp.c init.c +.ORDER: c-exp.c f-exp.c m2-exp.c = .if exists(${.OBJDIR}/../bfd) LDADD+=3D -L${.OBJDIR}/../bfd -lbfd Index: lib/libpcap/Makefile =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D RCS file: /home/ncvs/src/lib/libpcap/Makefile,v retrieving revision 1.16 diff -u -d -r1.16 Makefile --- Makefile 1997/05/27 00:08:01 1.16 +++ Makefile 1997/10/02 22:01:17 @@ -32,6 +32,7 @@ ${DESTDIR}/usr/include .endfor = +.ORDER: grammar.c tokdefs.h tokdefs.h grammar.c: grammar.y ${YACC} ${YACCFLAGS} -d ${PCAP_DISTDIR}/grammar.y mv y.tab.c grammar.c Index: libexec/ftpd/Makefile =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D RCS file: /home/ncvs/src/libexec/ftpd/Makefile,v retrieving revision 1.22 diff -u -d -r1.22 Makefile --- Makefile 1997/04/29 12:42:07 1.22 +++ Makefile 1997/07/31 06:58:53 @@ -5,7 +5,8 @@ MAN8=3D ftpd.8 SRCS=3D ftpd.c ftpcmd.c logwtmp.c popen.c skey-stuff.c = -CFLAGS+=3D-DSETPROCTITLE -DSKEY -DLOGIN_CAP -DVIRTUAL_HOSTING -Wall +CFLAGS+=3D-DSETPROCTITLE -DSKEY -DLOGIN_CAP -DVIRTUAL_HOSTING -Wall \ + -I${.CURDIR}/../../contrib-crypto/telnet = LDADD=3D -lskey -lmd -lcrypt -lutil DPADD=3D ${LIBSKEY} ${LIBMD} ${LIBCRYPT} ${LIBUTIL} @@ -19,7 +20,7 @@ CFLAGS+=3D-DINTERNAL_LS -Dmain=3Dls_main -I${.CURDIR}/${LSDIR} .endif = -.if exists(${DESTDIR}/usr/lib/libkrb.a) && defined(MAKE_EBONES) +.if exists(${DESTDIR}/usr/lib/libkrb.a) && defined(MAKE_KERBEROS4) .PATH: ${.CURDIR}/../../usr.bin/login SRCS+=3D klogin.c LDADD+=3D -lkrb -ldes Index: secure/Makefile =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D RCS file: /home/ncvs/src/secure/Makefile,v retrieving revision 1.7 diff -u -d -r1.7 Makefile --- Makefile 1996/05/04 08:33:51 1.7 +++ Makefile 1997/10/03 06:39:31 @@ -12,9 +12,9 @@ ${MAKE} ${MFLAGS} obj; \ ${MAKE} ${MFLAGS} depend all install = -CODAD=3D ${MAKE} ${MFLAGS} MAKE_EBONES=3Dyes cleandir; \ - ${MAKE} ${MFLAGS} MAKE_EBONES=3Dyes obj; \ - ${MAKE} ${MFLAGS} MAKE_EBONES=3Dyes depend all distribute +CODAD=3D ${MAKE} ${MFLAGS} cleandir; \ + ${MAKE} ${MFLAGS} obj; \ + ${MAKE} ${MFLAGS} depend all distribute = # These are the programs which depend on secure libs sprog: Index: share/mk/bsd.dep.mk =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D RCS file: /home/ncvs/src/share/mk/bsd.dep.mk,v retrieving revision 1.14 diff -u -d -r1.14 bsd.dep.mk --- bsd.dep.mk 1997/08/26 16:54:33 1.14 +++ bsd.dep.mk 1997/10/02 21:55:44 @@ -33,8 +33,8 @@ = # some of the rules involve .h sources, so remove them from mkdep line .if !target(depend) -depend: beforedepend ${DEPENDFILE} afterdepend _SUBDIR .if defined(SRCS) +depend: beforedepend ${DEPENDFILE} afterdepend _SUBDIR = # .if defined ${SRCS:M*.[sS]} does not work __depend_s=3D ${SRCS:M*.[sS]} @@ -60,11 +60,15 @@ cd ${.CURDIR}; ${MAKE} _EXTRADEPEND .endif = +.ORDER: ${DEPENDFILE} afterdepend .else -${DEPENDFILE}: _SUBDIR +depend: beforedepend afterdepend _SUBDIR .endif .if !target(beforedepend) beforedepend: +.else +.ORDER: beforedepend ${DEPENDFILE} +.ORDER: beforedepend afterdepend .endif .if !target(afterdepend) afterdepend: Index: sys/i386/boot/netboot/Makefile =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D RCS file: /home/ncvs/src/sys/i386/boot/netboot/Makefile,v retrieving revision 1.12 diff -u -d -r1.12 Makefile --- Makefile 1997/05/15 19:04:33 1.12 +++ Makefile 1997/10/02 22:07:39 @@ -72,16 +72,18 @@ ${.OBJDIR}/makerom ${.TARGET} = nb8390.com: makerom start2.ro ${SRCS:N*.h:R:S/$/.o/g} ns8390.o - ${LD} ${LDFLAGS} -o netboot.com ${OBJS} ns8390.o - strip netboot.com - size netboot.com - dd ibs=3D32 skip=3D1 if=3Dnetboot.com of=3D${.TARGET} + ${LD} ${LDFLAGS} -o ${.TARGET}.tmp ${OBJS} ns8390.o + strip ${.TARGET}.tmp + size ${.TARGET}.tmp + dd ibs=3D32 skip=3D1 if=3D${.TARGET}.tmp of=3D${.TARGET} + rm -f ${.TARGET}.tmp = nb3c509.com: start2.o ${SRCS:N*.h:R:S/$/.o/g} 3c509.o - ${LD} ${LDFLAGS} -o netboot.com ${OBJS} 3c509.o - strip netboot.com - size netboot.com - dd ibs=3D32 skip=3D1 if=3Dnetboot.com of=3D${.TARGET} + ${LD} ${LDFLAGS} -o ${.TARGET}.tmp ${OBJS} 3c509.o + strip ${.TARGET}.tmp + size ${.TARGET}.tmp + dd ibs=3D32 skip=3D1 if=3D${.TARGET}.tmp of=3D${.TARGET} + rm -f ${.TARGET}.tmp = = .include Index: usr.bin/ftp/Makefile =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D RCS file: /home/ncvs/src/usr.bin/ftp/Makefile,v retrieving revision 1.6 diff -u -d -r1.6 Makefile --- Makefile 1997/06/25 08:56:33 1.6 +++ Makefile 1997/07/31 06:58:20 @@ -5,6 +5,7 @@ PROG=3D ftp SRCS=3D cmds.c cmdtab.c complete.c domacro.c fetch.c ftp.c main.c ruserp= ass.c \ util.c +CFLAGS+=3D-I${.CURDIR}/../../contrib-crypto/telnet = LDADD+=3D -ledit -ltermcap DPADD+=3D ${LIBEDIT} ${LIBTERMCAP} Index: usr.bin/lex/Makefile =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D RCS file: /home/ncvs/src/usr.bin/lex/Makefile,v retrieving revision 1.10 diff -u -d -r1.10 Makefile --- Makefile 1997/02/22 19:55:34 1.10 +++ Makefile 1997/10/02 22:01:17 @@ -15,6 +15,7 @@ LINKS+=3D ${BINDIR}/lex ${BINDIR}/flex++ = SRCS=3D scan.c ccl.c dfa.c ecs.c gen.c main.c misc.c nfa.c parse.c \ + parse.h \ skel.c sym.c tblcmp.c yylex.c LFLAGS+=3D -is CFLAGS+=3D -I. -I${.CURDIR} @@ -34,6 +35,7 @@ ${.CURDIR}/FlexLexer.h ${DESTDIR}/usr/include/g++ = = +.ORDER: parse.c parse.h parse.c parse.h: parse.y $(YACC) -d $(.CURDIR)/parse.y mv -f y.tab.c parse.c @@ -46,7 +48,6 @@ cp -f ${.CURDIR}/initscan.c scan.c ; \ } = -beforedepend: parse.h scan.o: parse.h = test: check Index: usr.sbin/amd/fsinfo/Makefile =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D RCS file: /home/ncvs/src/usr.sbin/amd/fsinfo/Makefile,v retrieving revision 1.5 diff -u -d -r1.5 Makefile --- Makefile 1997/02/22 16:03:14 1.5 +++ Makefile 1997/10/02 22:01:17 @@ -3,7 +3,7 @@ = PROG=3D fsinfo MAN8=3D fsinfo.8 -SRCS=3D fsinfo.c fsi_gram.c fsi_lex.c \ +SRCS=3D fsinfo.c fsi_gram.c fsi_gram.h fsi_lex.c \ fsi_util.c fsi_analyze.c fsi_dict.c \ wr_atab.c wr_bparam.c wr_dumpset.c \ wr_exportfs.c wr_fstab.c @@ -16,6 +16,7 @@ CFLAGS+=3D-DOS_HDR=3D\"os-bsd44.h\" = fsi_lex.o fsinfo.o: fsi_gram.h +.ORDER: fsi_gram.c fsi_gram.h fsi_gram.c fsi_gram.h: ../fsinfo/fsi_gram.y @echo "# expect 2 shift/reduce conflicts" ${YACC} -d ${.CURDIR}/fsi_gram.y Index: usr.sbin/sendmail/src/Makefile =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D RCS file: /home/ncvs/src/usr.sbin/sendmail/src/Makefile,v retrieving revision 1.13 diff -u -d -r1.13 Makefile --- Makefile 1997/09/28 09:31:43 1.13 +++ Makefile 1997/09/28 12:42:09 @@ -22,8 +22,8 @@ NIS=3D -DNIS = # If you want tcp wrapper support, uncomment the following two lines -#TCPWRAPPERSBASEDIR=3D /usr/local -#TCPWRAPPERS=3D -DTCPWRAPPERS -I${TCPWRAPPERSBASEDIR}/include +TCPWRAPPERSBASEDIR=3D /usr/local +TCPWRAPPERS=3D -DTCPWRAPPERS -I${TCPWRAPPERSBASEDIR}/include = CFLAGS+=3D-I${.CURDIR} ${DBMDEF} ${NIS} ${TCPWRAPPERS} #-DNETISO = Index: usr.sbin/vipw/pw_util.c =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D RCS file: /home/ncvs/src/usr.sbin/vipw/pw_util.c,v retrieving revision 1.7 diff -u -d -r1.7 pw_util.c --- pw_util.c 1997/09/29 13:13:51 1.7 +++ pw_util.c 1997/10/02 06:32:47 @@ -32,7 +32,7 @@ */ = #ifndef lint -static char sccsid[] =3D "@(#)pw_util.c 8.3 (Berkeley) 4/2/94"; +static const char sccsid[] =3D "@(#)pw_util.c 8.3 (Berkeley) 4/2/94"; #endif /* not lint */ = /* @@ -126,7 +126,7 @@ int fd; char *p; = - if (p =3D strrchr(path, '/')) + if ((p =3D strrchr(path, '/'))) ++p; else p =3D path; @@ -172,7 +172,7 @@ = if (!(editor =3D getenv("EDITOR"))) editor =3D _PATH_VI; - if (p =3D strrchr(editor, '/')) + if ((p =3D strrchr(editor, '/'))) ++p; else p =3D editor; --==_Exmh_6587434810-- From owner-freebsd-current Sat Oct 4 01:52:10 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id BAA07166 for current-outgoing; Sat, 4 Oct 1997 01:52:10 -0700 (PDT) Received: from cc621.ntu.ac.sg (cc621.ntu.ac.sg [155.69.4.102]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id BAA07093 for ; Sat, 4 Oct 1997 01:51:55 -0700 (PDT) Received: (from ktsin@localhost) by cc621.ntu.ac.sg (8.8.5/8.8.5) id QAA08511 for current@FreeBSD.ORG; Sat, 4 Oct 1997 16:51:25 +0800 (SGT) Message-Id: <199710040851.QAA08511@cc621.ntu.ac.sg> Subject: lock manager panics To: current@FreeBSD.ORG Date: Sat, 4 Oct 1997 16:51:25 +0800 (SGT) From: Sin Key Teck 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 hi there I have installed 3.0-971003-SNAP and the lock manager still panics on shutdown if quota is enabled. I believe the problem has persisted since the SMP code was merged into 3.0. Is there a problem with the lock manager or is it due to misconfiguration? kt From owner-freebsd-current Sat Oct 4 03:32:57 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id DAA11837 for current-outgoing; Sat, 4 Oct 1997 03:32:57 -0700 (PDT) Received: from news1.gtn.com (news1.gtn.com [192.109.159.3]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id DAA11760 for ; Sat, 4 Oct 1997 03:32:52 -0700 (PDT) Received: (from uucp@localhost) by news1.gtn.com (8.8.6/8.8.6) with UUCP id KAA06995; Sat, 4 Oct 1997 10:15:08 +0100 (MET) Received: (from andreas@localhost) by klemm.gtn.com (8.8.7/8.8.7) id AAA13522; Sat, 4 Oct 1997 00:46:55 +0200 (CEST) Message-ID: <19971004004655.42362@klemm.gtn.com> Date: Sat, 4 Oct 1997 00:46:55 +0200 From: Andreas Klemm To: "Rodney W. Grimes" Cc: ache@nagual.pp.ru, current@FreeBSD.ORG Subject: Re: Which PCI Ethernet card is best for FreeBSD-current? References: <19971002162324.02664@klemm.gtn.com> <199710032104.OAA00273@GndRsh.aac.dev.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.84 In-Reply-To: <199710032104.OAA00273@GndRsh.aac.dev.com>; from Rodney W. Grimes on Fri, Oct 03, 1997 at 02:04:19PM -0700 X-Disclaimer: A free society is one where it is safe to be unpopular X-Operating-System: FreeBSD 3.0-CURRENT SMP Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Fri, Oct 03, 1997 at 02:04:19PM -0700, Rodney W. Grimes wrote: > If I am the ``Rodney'' you are refering to above, I do not recommend the > EtherExpress cards, or infact any card made by Intel, I sell and recommend > DEC DC21x4x based cards, if my client specifically request the EtherExpress/ > Pro 100B I will sell it, buy only when specifically requested. Sorry, I remembered that wrong. I thought it were you. -- Andreas Klemm powered by ,,symmetric multiprocessor FreeBSD'' andreas@klemm.gtn.com - http://www.freebsd.org/~fsmp/SMP/SMP.html andreas@FreeBSD.ORG - http://www.freebsd.org/~fsmp/SMP/benches.html From owner-freebsd-current Sat Oct 4 08:36:47 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id IAA20132 for current-outgoing; Sat, 4 Oct 1997 08:36:47 -0700 (PDT) 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 IAA20127 for ; Sat, 4 Oct 1997 08:36:42 -0700 (PDT) Received: from localhost (abial@localhost) by korin.warman.org.pl (8.8.7/8.8.5) with SMTP id RAA23966; Sat, 4 Oct 1997 17:37:26 +0200 (CEST) Date: Sat, 4 Oct 1997 17:37:26 +0200 (CEST) From: Andrzej Bialecki To: Brandon Gillespie cc: freebsd-current@FreeBSD.ORG Subject: Re: new command: doconfig 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 Wed, 1 Oct 1997, Brandon Gillespie wrote: > I would like to add this as a new command to FreeBSD. I mentioned it a > few months back when I originally wrote it, and received positive > responses about it. This command derives from a similar command in > Digital Unix. 'doconfig' is basically a simplifier for kernel compiling, > by wrapping 'vi /sys/i386/conf/MINE; config; cd ../../compile/MINE; make > depend; make; make install; reboot' or whatnot into a simpler, nicer > interface.. For instance, I just recompiled my kernel with (the GLACIER > config file already existed): I use sometimes SCO, and there is (almost only :-) one thing that I liked: curses-driven program to tune running system parameters (such as mbufs, recv/send buffers etc.. - the whole stuff in FreeBSD's sysctl). I think it would be extremely helpful for novice administrators to have it -even it's presence alone would encourage people to tune their systems. So, I think you could do something more general in purpose: something like sysadmin's tool for tuning system's parameters. What do you think? 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 Sat Oct 4 09:21:27 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id JAA21984 for current-outgoing; Sat, 4 Oct 1997 09:21:27 -0700 (PDT) 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 JAA21972 for ; Sat, 4 Oct 1997 09:21:17 -0700 (PDT) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.5/8.6.9) id CAA31787; Sun, 5 Oct 1997 02:15:54 +1000 Date: Sun, 5 Oct 1997 02:15:54 +1000 From: Bruce Evans Message-Id: <199710041615.CAA31787@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 >}--- >}/* Intel prefers long real (53 bit) precision */ >}#define __iBCS_NPXCW__ 0x262 >}/* wfj prefers temporary real (64 bit) precision */ >}#define __386BSD_NPXCW__ 0x362 >}/* >} * bde prefers 53 bit precision and all exceptions masked. >}--- >} >Interesting, in the long run 0x200 is the most "standard", >if Sun has its way. I did not realize that it was possible I think you mean 0x137f? 0x00 in the low 8 bits would unmask all exceptions. The 0x40 and 0x1000 bits are forced to 1 by the h/w. The 0x0300 its give the precision. >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 ;-) 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. >However, your comment in npx.h opines that "64-bit precision often >gives bad results", and that is not true at all. More accurately, >(oops, I punned:) if computing intermediate values to higher >precision causes *different* final results, then in all but the >mostly highly contrived cases the problem lies with the code, >or in your terminology it's a bug :). (in that case the >algorithm is unstable wrt precision). Not to say counterexamples >don't exist but they are uncommon enough to be addressed in >Kahan's SIAM talk this year. Counterexamples are well known. Many can be found in Kahan's old "paranioa" program. Bugfeatures in gcc provide many more counterexamples. Double-precision arithmetic operations operations done at compile time are always done in 53-bit precision, but the same computations done at runtime are done partly in 53-bit precision and partly in the h/w precision, where the parts depend on the optimization level. The only sure way to get consistent results is to store the result of EVERY fp operation to main memory ... >So there is an inconsistency here: on the one hand your preferences >yield compatibility for buggy programs when the bug is instability >of the program algorithm when subjected to (increased) intermediate >precision; OTOH if the "bug" is manifested by something that >generates an exception, FreeBSD by default calls it out. My precision preference yields compatibility for non-buggy programs compiled by buggy compilers (provided the programs only use double precision - float precision has the same bugs). >Java is consistent, there is one fp format and as far as fp exceptions >go mask 'em all! This is the best default behaviour. Bruce From owner-freebsd-current Sat Oct 4 09:31:47 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id JAA22342 for current-outgoing; Sat, 4 Oct 1997 09:31:47 -0700 (PDT) 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 JAA22336 for ; Sat, 4 Oct 1997 09:31:44 -0700 (PDT) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.5/8.6.9) id CAA32086; Sun, 5 Oct 1997 02:27:09 +1000 Date: Sun, 5 Oct 1997 02:27:09 +1000 From: Bruce Evans Message-Id: <199710041627.CAA32086@godzilla.zeta.org.au> To: freebsd-current@freebsd.org, tomdean@ix.netcom.com Subject: Re: xlock: caught signal 8 while running galaxy mode. Sender: owner-freebsd-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >FreeBSD clears the exception register in the fpu when the trap code >catches an fpu exception prior to calling the user's handler, if any. > >In npx.c, the exception register is cleared prior to sending a SIGFPE >to the process. > >I want to be able to catch an exception, if I want, and determine what >the cause of the problem was, and, possibly work around it. I want my >exception handler to know exactly what the exception was. Here is the (unfinished) code for it (in npx.c): --- #ifdef notyet /* * Encode the appropriate code for detailed information on * this exception. */ code = XXX_ENCODE(curpcb->pcb_savefpu.sv_ex_sw); #else code = 0; /* XXX */ #endif --- The signal code for a SIGFPE can also be FPE_INTDIV_TRAP (integer divide fault), FPE_INTOVF_TRAP (integer overflow fault), FPE_SUBRNG_TRAP (bounds check fault) or FPE_FPU_NP_TRAP (no FPU h/w and no FPU emulator). This already works. See trap.c and trap.h. Bruce From owner-freebsd-current Sat Oct 4 10:11:45 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id KAA24548 for current-outgoing; Sat, 4 Oct 1997 10:11:45 -0700 (PDT) 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 KAA24520; Sat, 4 Oct 1997 10:11:29 -0700 (PDT) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.5/8.6.9) id DAA00343; Sun, 5 Oct 1997 03:09:38 +1000 Date: Sun, 5 Oct 1997 03:09:38 +1000 From: Bruce Evans Message-Id: <199710041709.DAA00343@godzilla.zeta.org.au> To: bde@zeta.org.au, cracauer@cons.org Subject: Re: xlock: caught signal 8 while running galaxy mode. Cc: freebsd-current@FreeBSD.ORG, jkh@time.cdrom.com, Matthew.Thyer@dsto.defence.gov.au, ports@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >> Dying screensavers are a good example of why trapping on FP exceptions >> is good: FP exceptions are often due to bugs, and trapping helps find >> the bugs. > >Sure. But most free (and commercial) software has been developed and >tested on machines that don't trap. Most commercial (and free?) software has been developed for DOS and Windows :-). I'm not sure what Microsoft C libraries do, but Borland C libraries trap by default. >> >> There are bugs in our gcc that make relying on FP exceptions handled >> >> right dangerous and Bruce Evans felt it is better to through the >> >> signal, so that people get aware of the problem. >> >> I don't know of any bugs in gcc related to FP exceptions. >> ... >> How is our gcc worse than NetBSD's or Linux's? > >s/gcc/FreeBSD/ > >If I remeber correctly (and the one who told me was probably you), one >can't disable FP exceptions easily without hiding stack exceptions as mask >well. Also, one can't mask FP exceptions without masking FP -> int conversion exceptions (like the one in xlock) as well. >Behaviour for compile-time and runtime evaluation is different >in quite a few places. This is unrelated to FP exceptions. >There was something that we can't set errno (as >we should accourding to POSIX) if we use IEEE non-trapping. No, the library problem is that we don't set errno (as we should according to ANSI) if we use "IEEE_MODE" in lib/msun (as we do now), and we wouldn't return IEEE-ish exception values (except for most cases involving HUGE_VAL = +Inf) if we used "POSIX_MODE" in lib/msun. >Correct me if I'm wrong, but if we don't trap, these's little point in >setting errno, isn't it? As I understand, we don't have working errno >support anyway. So there's nothing to loose. If we trap (as we do now), then the correct value for errno after a call to a math functions is unimportant since code that checks it is unreachable, but if we didn't trap then the code would be reachable, so it is important for errno to be correct. >[...] >> I decided not to commit the change to the control word until someone >> fixes the error handling in lib/msun. > >Well, is there any agreement which standard to follow? Is plain IEEE >reasonable? No, not yet (perhaps after C9X?). It is also not fully implemented by gcc. Bruce From owner-freebsd-current Sat Oct 4 10:23:19 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id KAA25413 for current-outgoing; Sat, 4 Oct 1997 10:23:19 -0700 (PDT) Received: from roguetrader.com (brandon@cold.org [206.81.134.103]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id KAA25406 for ; Sat, 4 Oct 1997 10:23:16 -0700 (PDT) Received: from localhost (brandon@localhost) by roguetrader.com (8.8.5/8.8.5) with SMTP id LAA17565; Sat, 4 Oct 1997 11:22:56 -0600 (MDT) Date: Sat, 4 Oct 1997 11:22:55 -0600 (MDT) From: Brandon Gillespie To: Andrzej Bialecki cc: freebsd-current@FreeBSD.ORG Subject: Re: new command: doconfig 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 Sat, 4 Oct 1997, Andrzej Bialecki wrote: > On Wed, 1 Oct 1997, Brandon Gillespie wrote: > > > I would like to add this as a new command to FreeBSD. I mentioned it a > > few months back when I originally wrote it, and received positive > > responses about it. This command derives from a similar command in > > Digital Unix. 'doconfig' is basically a simplifier for kernel compiling, > > by wrapping 'vi /sys/i386/conf/MINE; config; cd ../../compile/MINE; make > > depend; make; make install; reboot' or whatnot into a simpler, nicer > > interface.. For instance, I just recompiled my kernel with (the GLACIER > > config file already existed): > > I use sometimes SCO, and there is (almost only :-) one thing that I liked: > curses-driven program to tune running system parameters (such as mbufs, > recv/send buffers etc.. - the whole stuff in FreeBSD's sysctl). I think it > would be extremely helpful for novice administrators to have it -even it's > presence alone would encourage people to tune their systems. > > So, I think you could do something more general in purpose: something like > sysadmin's tool for tuning system's parameters. What do you think? Modularity :) I think a kernel configuration subsystem is fine on its own, as a single module. Later somebody can easilly wrap it in a more general kerneltuner program (which tunes and configures), but there is no reason to over-do one thing in complexity... (IMHO) -Brandon From owner-freebsd-current Sat Oct 4 11:07:39 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id LAA28235 for current-outgoing; Sat, 4 Oct 1997 11:07:39 -0700 (PDT) Received: from scrooge.ee.swin.oz.au (scrooge.ee.swin.oz.au [136.186.4.20]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id LAA28229 for ; Sat, 4 Oct 1997 11:07:33 -0700 (PDT) Received: (from dtc@localhost) by scrooge.ee.swin.oz.au (8.6.9/8.6.9) id EAA00380 for freebsd-current@freebsd.org; Sun, 5 Oct 1997 04:10:48 +1000 From: Douglas Thomas Crosher Message-Id: <199710041810.EAA00380@scrooge.ee.swin.oz.au> Subject: Re: xlock: caught signal 8 while running galaxy mode. To: freebsd-current@freebsd.org Date: Sun, 5 Oct 1997 04:10:47 +1000 (EST) In-Reply-To: <199710041627.CAA32086@godzilla.zeta.org.au> from "Bruce Evans" at Oct 5, 97 02:27:09 am X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-freebsd-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > >I want to be able to catch an exception, if I want, and determine what > >the cause of the problem was, and, possibly work around it. I want my > >exception handler to know exactly what the exception was. > > Here is the (unfinished) code for it (in npx.c): ... > The signal code for a SIGFPE can also be FPE_INTDIV_TRAP (integer divide > fault), FPE_INTOVF_TRAP (integer overflow fault), FPE_SUBRNG_TRAP (bounds > check fault) or FPE_FPU_NP_TRAP (no FPU h/w and no FPU emulator). This > already works. See trap.c and trap.h. Simply returning a few general codes is not enough. Apart from detecting exceptional values, applications many also depend on a combinations of: 1. Enabling and detecting specific exceptions. E.g. An overflow, underflow, loss of precision etc. Not possible in FreeBSD. 2. Monitoring the accrued exceptions. Not reliable in FreeBSD as a SIGFPE will clear these and gives the application no chance of restoring them when doing the equivalent of a long jump. If freebsd isn't going to save the NPX state in the sigcontext then perhaps it could pass the status word back to the application - see PR4597. This would at least give the application a chance of doing the right thing. Regards Douglas Crosher From owner-freebsd-current Sat Oct 4 11:16:25 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id LAA28830 for current-outgoing; Sat, 4 Oct 1997 11:16:25 -0700 (PDT) Received: from ns.mt.sri.com (SRI-56K-FR.mt.net [206.127.65.42]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id LAA28824; Sat, 4 Oct 1997 11:16:22 -0700 (PDT) Received: from rocky.mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by ns.mt.sri.com (8.8.7/8.8.7) with ESMTP id MAA28728; Sat, 4 Oct 1997 12:16:19 -0600 (MDT) Received: (from nate@localhost) by rocky.mt.sri.com (8.7.5/8.7.3) id MAA23555; Sat, 4 Oct 1997 12:16:13 -0600 (MDT) Date: Sat, 4 Oct 1997 12:16:13 -0600 (MDT) Message-Id: <199710041816.MAA23555@rocky.mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: "Scot W. Hetzel" Cc: "Stable" , "Current" Subject: Re: CTM patch level added to newvers.sh In-Reply-To: <01bccf6e$c649aa80$0400000a@hetzels> References: <01bccf6e$c649aa80$0400000a@hetzels> X-Mailer: VM 6.29 under 19.15 XEmacs Lucid Sender: owner-freebsd-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > I am currently tracking 2.2-STABLE and use the following patch to newvers.sh > to have my kernel indicate what CTM patch was used to create it. We need a solution that isn't specific to the transport medium, or in more specific terms a solution that works irregardless of how you got the bits. Nate From owner-freebsd-current Sat Oct 4 11:33:00 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id LAA29729 for current-outgoing; Sat, 4 Oct 1997 11:33:00 -0700 (PDT) Received: from emout19.mail.aol.com (emout19.mx.aol.com [198.81.11.45]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id LAA29709; Sat, 4 Oct 1997 11:32:55 -0700 (PDT) From: Hetzels@aol.com Received: (from root@localhost) by emout19.mail.aol.com (8.7.6/8.7.3/AOL-2.0.0) id OAA10221; Sat, 4 Oct 1997 14:32:23 -0400 (EDT) Date: Sat, 4 Oct 1997 14:32:23 -0400 (EDT) Message-ID: <971004143220_-729141990@emout19.mail.aol.com> To: nate@mt.sri.com cc: stable@freebsd.org, current@freebsd.org Subject: Re: CTM patch level added to newvers.sh Sender: owner-freebsd-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk In a message dated 97-10-04 14:16:27 EDT, nate@mt.sri.com writes: > > I am currently tracking 2.2-STABLE and use the following patch to newvers.sh > > to have my kernel indicate what CTM patch was used to create it. > > We need a solution that isn't specific to the transport medium, or in > more specific terms a solution that works irregardless of how you got > the bits. > I agree. One method I would like to see is that the .ctm_status file becomes a permanant part of the src tree. (Why?) Because CTM deltas are created at least once every day. Also, when a site is upgrading a RELEASE system to a STABLE system, via CTM, they don't have to ask "What CTM version is my RELEASE?"! They would know by looking at the .ctm_status file. As for CVS, since each site can download different parts of the source tree, it is more difficult to assign a general number to their version. Unless they download the entire sources and then the .ctm_status file would be updated to the latest #. NOTE: the # may/may not be compatible with the latest CTM delta, as the src is always updated between CTM delta's. But, at least this would give people an idea as to how far off from the sources they are at for both CTM/CVS. Scot From owner-freebsd-current Sat Oct 4 11:48:10 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id LAA00692 for current-outgoing; Sat, 4 Oct 1997 11:48:10 -0700 (PDT) Received: from news1.gtn.com (news1.gtn.com [194.77.0.15]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id LAA00639 for ; Sat, 4 Oct 1997 11:48:00 -0700 (PDT) Received: (from uucp@localhost) by news1.gtn.com (8.8.6/8.8.6) with UUCP id RAA04652; Sat, 4 Oct 1997 17:30:09 +0100 (MET) Received: (from andreas@localhost) by klemm.gtn.com (8.8.7/8.8.7) id SAA03050; Sat, 4 Oct 1997 18:18:03 +0200 (CEST) (envelope-from andreas) Message-ID: <19971004181803.01059@klemm.gtn.com> Date: Sat, 4 Oct 1997 18:18:03 +0200 From: Andreas Klemm To: "Gregory M. Shaffer" Cc: jkh@time.cdrom.com, current@FreeBSD.ORG, gshaffer.mark@grondar.za Subject: Re: : Making world on an SMP system. References: <23948.875831179@time.cdrom.com> <199710030300.UAA26079@cod.nosc.mil> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.84 In-Reply-To: <199710030300.UAA26079@cod.nosc.mil>; from Gregory M. Shaffer on Thu, Oct 02, 1997 at 08:00:32PM -0700 X-Disclaimer: A free society is one where it is safe to be unpopular X-Operating-System: FreeBSD 3.0-CURRENT SMP Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Thu, Oct 02, 1997 at 08:00:32PM -0700, Gregory M. Shaffer wrote: > > I believe it was someones experament to see how difficult > it would be to make the *.mk and make files parallel safe. > I don't think there was a PR associated with it. > > I still have the patches somewhere on my system, I'd be > happy to forward them to you for you inspection. If I remember correctly, then Steve (Passe) said, these patches were working good on his system, as well. But he didn't want to commit them without more testing, because he didn't want to break "make", that was patched as well. I'd appreciate as well, that these diffs go into -current, since it already worked for many people and didn't break anything so far. BTW: - would it be possible to control the -j parameter via /etc/make.conf ?! - did someone test, if "make release" also works using these patches ? Andreas /// -- Andreas Klemm powered by ,,symmetric multiprocessor FreeBSD'' andreas@klemm.gtn.com - http://www.freebsd.org/~fsmp/SMP/SMP.html andreas@FreeBSD.ORG - http://www.freebsd.org/~fsmp/SMP/benches.html From owner-freebsd-current Sat Oct 4 12:10:51 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id MAA01796 for current-outgoing; Sat, 4 Oct 1997 12:10:51 -0700 (PDT) Received: from gratis.grondar.za (gratis.grondar.za [196.7.18.133]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id MAA01781 for ; Sat, 4 Oct 1997 12:10:40 -0700 (PDT) Received: from greenpeace.grondar.za (0Xda/MAQpvcoNUf5zTd/0qg/K0K+rATV@greenpeace.grondar.za [196.7.18.132]) by gratis.grondar.za (8.8.7/8.8.7) with ESMTP id VAA06444; Sat, 4 Oct 1997 21:10:36 +0200 (SAT) Received: from greenpeace.grondar.za (J6EzsesHefjxzfVECgpCndWecB10ljA+@localhost [127.0.0.1]) by greenpeace.grondar.za (8.8.7/8.8.7) with ESMTP id VAA00424; Sat, 4 Oct 1997 21:10:34 +0200 (SAT) Message-Id: <199710041910.VAA00424@greenpeace.grondar.za> X-Mailer: exmh version 2.0zeta 7/24/97 To: Andreas Klemm cc: "Gregory M. Shaffer" , jkh@time.cdrom.com, current@FreeBSD.ORG Subject: Re: : Making world on an SMP system. Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 04 Oct 1997 21:10:33 +0200 From: Mark Murray Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Andreas Klemm wrote: > If I remember correctly, then Steve (Passe) said, these patches were > working good on his system, as well. Jordan and I have some of these, and they are working well.. > But he didn't want to commit them without more testing, because he > didn't want to break "make", that was patched as well. Yes, make is patched, and no, it is not broken. > I'd appreciate as well, that these diffs go into -current, since > it already worked for many people and didn't break anything so far. We all want it! > BTW: > - would it be possible to control the -j parameter via /etc/make.conf ?! Should be no problem. > - did someone test, if "make release" also works using these patches ? jkh - How did it work? M -- Mark Murray Join the anti-SPAM movement: http://www.cauce.org From owner-freebsd-current Sat Oct 4 14:13:31 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id OAA06912 for current-outgoing; Sat, 4 Oct 1997 14:13:31 -0700 (PDT) Received: from time.cdrom.com (time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id OAA06904 for ; Sat, 4 Oct 1997 14:13:27 -0700 (PDT) Received: from time.cdrom.com (localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.7/8.6.9) with ESMTP id OAA07948; Sat, 4 Oct 1997 14:12:16 -0700 (PDT) To: Mark Murray cc: Andreas Klemm , "Gregory M. Shaffer" , current@FreeBSD.ORG Subject: Re: : Making world on an SMP system. In-reply-to: Your message of "Sat, 04 Oct 1997 21:10:33 +0200." <199710041910.VAA00424@greenpeace.grondar.za> Date: Sat, 04 Oct 1997 14:12:15 -0700 Message-ID: <7944.875999535@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > - did someone test, if "make release" also works using these patches ? > > jkh - How did it work? As I wrote you on current.freebsd.org, there were a few misapplications with the patches you originally sent out for today's -current (e.g. 971004) so I fixed those up and started a make -j12 world on the box, just to thrash it good (and this is a *uniprocessor* P6/200 box :-). Here are the times: root@make-> grep 'make world' make.world-j12.out make world started on Sat Oct 4 10:38:38 EDT 1997 make world completed on Sat Oct 4 12:53:40 EDT 1997 Needless to say, it appears to have worked. I've re-rolled the patch for you [Mark] to look at and if it seems reasonable for you too and we can also get that icky -j4 out of there and more configurable, I'd say it'd be time to commit it. Jordan From owner-freebsd-current Sat Oct 4 15:06:23 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id PAA09511 for current-outgoing; Sat, 4 Oct 1997 15:06:23 -0700 (PDT) Received: from cod.nosc.mil (gshaffer@cod.nosc.mil [128.49.4.5]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id PAA09504 for ; Sat, 4 Oct 1997 15:06:19 -0700 (PDT) Received: (from gshaffer@localhost) by cod.nosc.mil (8.8.7/8.8.7) id PAA11839; Sat, 4 Oct 1997 15:06:15 -0700 (PDT) Date: Sat, 4 Oct 1997 15:06:15 -0700 (PDT) From: "Gregory M. Shaffer" Message-Id: <199710042206.PAA11839@cod.nosc.mil> To: jkh@time.cdrom.com Cc: current@FreeBSD.Org, mark@grondar.za, andreas@klemm.gtn.com Subject: Re:: : Making world on an SMP system. In-reply-to: Your Message-ID: <7944.875999535@time.cdrom.com> Sender: owner-freebsd-current@FreeBSD.Org X-Loop: FreeBSD.org Precedence: bulk ------- > > - did someone test, if "make release" also works using these patches ? > > jkh - How did it work? As I wrote you on current.freebsd.org, there were a few misapplications with the patches you originally sent out for today's -current (e.g. 971004) so I fixed those up and started a make -j12 world on the box, just to thrash it good (and this is a *uniprocessor* P6/200 box :-). Here are the times: root@make-> grep 'make world' make.world-j12.out make world started on Sat Oct 4 10:38:38 EDT 1997 make world completed on Sat Oct 4 12:53:40 EDT 1997 Needless to say, it appears to have worked. I've re-rolled the patch for you [Mark] to look at and if it seems reasonable for you too and we can also get that icky -j4 out of there and more configurable, I'd say it'd be time to commit it. Thanks for doing this, I have several SMP boxes at work that I can't wait to do this on. I'd aslo be interested in pounding on the patch if you send it to me. Greg Shaffer ------- From owner-freebsd-current Sat Oct 4 17:55:54 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id RAA16869 for current-outgoing; Sat, 4 Oct 1997 17:55:54 -0700 (PDT) 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 RAA16864 for ; Sat, 4 Oct 1997 17:55:51 -0700 (PDT) Received: from gurney.reilly.home (d29.syd2.zeta.org.au [203.26.11.29]) by godzilla.zeta.org.au (8.8.5/8.6.9) with ESMTP id KAA11971; Sun, 5 Oct 1997 10:52:49 +1000 Received: (from andrew@localhost) by gurney.reilly.home (8.8.7/8.8.5) id KAA09111; Sun, 5 Oct 1997 10:50:41 +1000 (EST) From: Andrew Reilly Message-Id: <199710050050.KAA09111@gurney.reilly.home> Date: Sun, 5 Oct 1997 10:50:41 +1000 (EST) Subject: Re: xlock: caught signal 8 while running galaxy mode. To: bde@zeta.org.au cc: rcarter@consys.com, freebsd-current@FreeBSD.ORG In-Reply-To: <199710041615.CAA31787@godzilla.zeta.org.au> MIME-Version: 1.0 Content-Type: TEXT/plain; CHARSET=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On 5 Oct, Bruce Evans wrote: > optimization level. The only sure way to get consistent results is > to store the result of EVERY fp operation to main memory ... I wasn't quite able to figure out which "side" of the argument you were going for here (maybe your last comment indicates that it is my side after all), but all I can say is Bah, Humbug! I do numerical (DSP) work all the time, and I'd much rather the floating point maths was absolutely as fast as it possibly could be, rather than worrying about the last few bits of precision. I usually work with 32-bit floats anyway. Consistency of floating point results is a myth, and dependance on every bit of precision, and rounding modes is algorithmic error. 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 there is a magic function that enables the "exceptions" to be masked, but it isn't mentioned in math(3). >>Java is consistent, there is one fp format and as far as fp exceptions >>go mask 'em all! > > This is the best default behaviour. Absolutely! I only disagree with Java that exact precision is important. I don't want the math libraries to jump through hoops to achieve it. -- Andrew "The steady state of disks is full." -- Ken Thompson From owner-freebsd-current Sat Oct 4 21:26:27 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id VAA23990 for current-outgoing; Sat, 4 Oct 1997 21:26:27 -0700 (PDT) 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 VAA23980 for ; Sat, 4 Oct 1997 21:26:11 -0700 (PDT) Received: (from grog@localhost) by freebie.lemis.com (8.8.7/8.8.5) id NAA25943; Sun, 5 Oct 1997 13:56:00 +0930 (CST) Message-ID: <19971005135600.20520@lemis.com> Date: Sun, 5 Oct 1997 13:56:00 +0930 From: Greg Lehey To: FreeBSD current users Subject: IPC problems in latest -current? 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-8250 Fax: +61-8-8388-8250 Mobile: +61-41-739-7062 WWW-Home-Page: http://www.lemis.com/~grog Fight-Spam-Now: http://www.cauce.org Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Since rebuilding -current on Friday, I've noticed a strange phenomenon: compared to the build a week previously, ghostview hangs on redisplay. During this time, the machine is completely idle, and I've discovered that it will continue if I move the cursor in and out of the window. It definitely has never done this before--I use ghostview/ghostscript a lot, and I would have noticed it. I've also tried various versions of ghostview and ghostscript, and they all repeat the problem. It looks as if something is interfering with the interaction ghostview/ghostscript, and the X events are triggering a retry. I know this isn't much to go on, but if anybody has any ideas, I'll gladly follow them up. BTW, is anybody else experiencing mail problems? I've had almost no mail from the mailing lists in the last few days, and what mail has come through has been delayed up to 8 hours. Personal mail is still coming. Greg From owner-freebsd-current Sat Oct 4 21:57:58 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id VAA25231 for current-outgoing; Sat, 4 Oct 1997 21:57:58 -0700 (PDT) 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 VAA25224 for ; Sat, 4 Oct 1997 21:57:53 -0700 (PDT) Received: (from root@localhost) by dyson.iquest.net (8.8.6/8.8.5) id XAA11236 for current@freebsd.org; Sat, 4 Oct 1997 23:57:45 -0500 (EST) From: "John S. Dyson" Message-Id: <199710050457.XAA11236@dyson.iquest.net> Subject: I have placed a potentially useful PPro utility up for FTP To: current@freebsd.org Date: Sat, 4 Oct 1997 23:57:45 -0500 (EST) 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 This utility http://ftp.freebsd.org/pub/FreeBSD/incoming/pm.cpio.gz supports relatively convienient access to the P6/P2 performance counters. This code will not work with a P5, or on SMP systems. -- John dyson@freebsd.org jdyson@nc.com From owner-freebsd-current Sat Oct 4 23:01:00 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id XAA28660 for current-outgoing; Sat, 4 Oct 1997 23:01:00 -0700 (PDT) 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 XAA28645 for ; Sat, 4 Oct 1997 23:00:56 -0700 (PDT) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.5/8.6.9) id PAA20163; Sun, 5 Oct 1997 15:56:31 +1000 Date: Sun, 5 Oct 1997 15:56:31 +1000 From: Bruce Evans Message-Id: <199710050556.PAA20163@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 >after all), but all I can say is Bah, Humbug! I do numerical (DSP) work >all the time, and I'd much rather the floating point maths was >absolutely as fast as it possibly could be, rather than worrying about But you would rather not write it all in assembler? :-) >the last few bits of precision. I usually work with 32-bit floats >anyway. Consistency of floating point results is a myth, and >dependance on every bit of precision, and rounding modes is algorithmic >error. IEEE floating point is consistent, and some algorithms depend on it. >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 Do you mean overflow? FreeBSD masks underflow, denormal and precision exceptions by default. Continuing from SIGFPE handlers is much harder than masking FP exceptions, at least on i386's. Bruce From owner-freebsd-current Sat Oct 4 23:56:16 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id XAA02598 for current-outgoing; Sat, 4 Oct 1997 23:56:16 -0700 (PDT) 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 XAA02593 for ; Sat, 4 Oct 1997 23:56:13 -0700 (PDT) Received: from gurney.reilly.home (d21.syd2.zeta.org.au [203.26.11.21]) by godzilla.zeta.org.au (8.8.5/8.6.9) with ESMTP id QAA21771; Sun, 5 Oct 1997 16:54:03 +1000 Received: (from andrew@localhost) by gurney.reilly.home (8.8.7/8.8.5) id QAA10186; Sun, 5 Oct 1997 16:53:14 +1000 (EST) From: Andrew Reilly Message-Id: <199710050653.QAA10186@gurney.reilly.home> Date: Sun, 5 Oct 1997 16:53:13 +1000 (EST) Subject: Re: xlock: caught signal 8 while running galaxy mode. To: bde@zeta.org.au cc: reilly@zeta.org.au, freebsd-current@FreeBSD.ORG, rcarter@consys.com In-Reply-To: <199710050556.PAA20163@godzilla.zeta.org.au> MIME-Version: 1.0 Content-Type: TEXT/plain; CHARSET=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On 5 Oct, Bruce Evans wrote: >>after all), but all I can say is Bah, Humbug! I do numerical (DSP) work >>all the time, and I'd much rather the floating point maths was >>absolutely as fast as it possibly could be, rather than worrying about > > But you would rather not write it all in assembler? :-) Hmmm. I generally do anyway, because C is not a good fit for the DSP processors I have to use, but I can see that the days of special purpose DSP architectures is limited, as workstation processors get faster at maths and cheaper, and more DSP-ish applications must run on workstations and PCs. Certainly once it is possible to write efficient code in C, then that (or some other HLL) is the way to do it. >>the last few bits of precision. I usually work with 32-bit floats >>anyway. Consistency of floating point results is a myth, and >>dependance on every bit of precision, and rounding modes is algorithmic >>error. > > IEEE floating point is consistent, and some algorithms depend on it. I believe you. It's just that most of the floating point code I've had to write recently was not running on IEEE floating point processors. >>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 > > 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. ---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 (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) So: I imagine fcoms is a short floating point compare. Any reason that should generate an exception in this case? On a system without denorms and with real 32-bit floats, the comparison would be 0.0>-30.99..., which is hardly going to be a problem. > Continuing from SIGFPE handlers is much harder than masking FP exceptions, > at least on i386's. Yes. I tried doing a signal(SIGFPE,SIG_IGN) at the top of main, but that just made it produce totally incorrect results. -- Andrew "The steady state of disks is full." -- Ken Thompson