From owner-freebsd-stable Sun Jun 28 05:40:15 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA16346 for freebsd-stable-outgoing; Sun, 28 Jun 1998 05:40:15 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from techpower.net (fragment@techpower.net [205.133.231.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA16295 for ; Sun, 28 Jun 1998 05:40:08 -0700 (PDT) (envelope-from fragment@techpower.net) Received: from localhost (fragment@localhost) by techpower.net (8.8.8/8.8.8) with SMTP id IAA15984 for ; Sun, 28 Jun 1998 08:40:51 -0400 (EDT) (envelope-from fragment@techpower.net) Date: Sun, 28 Jun 1998 08:40:51 -0400 (EDT) From: defragmented Reply-To: defragmented To: freebsd-stable@FreeBSD.ORG Subject: make world fails Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I have tryed to buildworld under stable I get the following error: n-freebsd\" -I/usr/obj/usr/src/gnu/usr.bin/cc/cc_int/../cc_tools -I/usr/obj/usr/ src/tmp/usr/include -c /usr/src/gnu/usr.bin/cc/cc_int/../../../../contrib/gcc/re gclass.c -o regclass.o cc -O -pipe -DFREEBSD_AOUT -I/usr/src/gnu/usr.bin/cc/cc_int/../../../../contrib/ gcc -I/usr/src/gnu/usr.bin/cc/cc_int/../../../../contrib/gcc/config -DFREEBSD_NA TIVE -DDEFAULT_TARGET_VERSION=\"2.7.2.1\" -DDEFAULT_TARGET_MACHINE=\"i386-unknow n-freebsd\" -I/usr/obj/usr/src/gnu/usr.bin/cc/cc_int/../cc_tools -I/usr/obj/usr/ src/tmp/usr/include -c /usr/src/gnu/usr.bin/cc/cc_int/../../../../contrib/gcc/re load.c -o reload.o Jun 28 08:37:10 hometeam /kernel: pid 15973 (cc1), uid 0: exited on signal 11 (c ore dumped) cc: Internal compiler error: program cc1 got fatal signal 11 *** Error code 1 Stop. *** Error code 1 Stop. *** Error code 1 Stop. *** Error code 1 anyone know how to fix this? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Jun 28 05:49:29 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA17209 for freebsd-stable-outgoing; Sun, 28 Jun 1998 05:49:29 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from techpower.net (hometeam@techpower.net [205.133.231.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA17204 for ; Sun, 28 Jun 1998 05:49:25 -0700 (PDT) (envelope-from hometeam@techpower.net) Received: from localhost (hometeam@localhost) by techpower.net (8.8.8/8.8.8) with SMTP id IAA16018 for ; Sun, 28 Jun 1998 08:50:17 -0400 (EDT) (envelope-from hometeam@techpower.net) Date: Sun, 28 Jun 1998 08:50:17 -0400 (EDT) From: Jt Reply-To: Jt To: freebsd-stable@FreeBSD.ORG Subject: cvsup In-Reply-To: <6133.898984165@time.cdrom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I am getting the follow on cvsup Cannot connect to cvsup.FreeBSD.org: Connection refused Will retry at 08:49:02 I connected the cvsup3.FreeBSD.org I notice the makefile.i386 %VERSREQ= 220000 Can someone fix the % on this ? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Jun 28 05:59:40 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA17944 for freebsd-stable-outgoing; Sun, 28 Jun 1998 05:59:40 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from techpower.net (hometeam@techpower.net [205.133.231.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA17939 for ; Sun, 28 Jun 1998 05:59:39 -0700 (PDT) (envelope-from hometeam@techpower.net) Received: from localhost (hometeam@localhost) by techpower.net (8.8.8/8.8.8) with SMTP id JAA16062 for ; Sun, 28 Jun 1998 09:00:31 -0400 (EDT) (envelope-from hometeam@techpower.net) Date: Sun, 28 Jun 1998 09:00:31 -0400 (EDT) From: Jt To: freebsd-stable@FreeBSD.ORG Subject: makefile Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Removing old directory ../../compile/hometeam: Done. Unknown % constructin generic makefile: %VERSREQ= 220000 Kernel build directory is ../../compile/hometeam Every cvsup puts the % sign back on the Makefile.i386 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Jun 28 06:45:20 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA23312 for freebsd-stable-outgoing; Sun, 28 Jun 1998 06:45:20 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from techpower.net (hometeam@techpower.net [205.133.231.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA23295 for ; Sun, 28 Jun 1998 06:45:16 -0700 (PDT) (envelope-from hometeam@techpower.net) Received: from localhost (hometeam@localhost) by techpower.net (8.8.8/8.8.8) with SMTP id JAA00385 for ; Sun, 28 Jun 1998 09:46:05 -0400 (EDT) (envelope-from hometeam@techpower.net) Date: Sun, 28 Jun 1998 09:46:05 -0400 (EDT) From: Jt To: freebsd-stable@FreeBSD.ORG Subject: cvsup Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I am getting the follow on cvsup Cannot connect to cvsup.FreeBSD.org: Connection refused Will retry at 08:49:02 I connected the cvsup3.FreeBSD.org I notice the makefile.i386 %VERSREQ= 220000 Can someone fix the % on this ? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Jun 28 07:46:57 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA29582 for freebsd-stable-outgoing; Sun, 28 Jun 1998 07:46:57 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from bastian.attic.ch (bastian.attic.ch [194.235.45.178]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA29573 for ; Sun, 28 Jun 1998 07:46:53 -0700 (PDT) (envelope-from blapp@attic.ch) Received: from attic.ch (oensingen-gate1-04.solnet.ch [194.235.47.99]) by bastian.attic.ch (8.9.0/8.9.0) with ESMTP id QAA25674; Sun, 28 Jun 1998 16:46:32 +0200 (CEST) Message-ID: <3596571B.215768FE@attic.ch> Date: Sun, 28 Jun 1998 16:45:47 +0200 From: Martin Blapp Reply-To: blapp@attic.ch Organization: Attic Internet Services X-Mailer: Mozilla 4.05 [en] (WinNT; U) MIME-Version: 1.0 To: defragmented , "freebsd-stable@FreeBSD.ORG" Subject: Re: make world fails References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > reload.o Jun 28 08:37:10 hometeam /kernel: pid 15973 (cc1), uid 0: exited > on signal 11 (c ore dumped) cc: Internal compiler error: program cc1 got > fatal signal 11 *** Error code 1 Have a look at : http://www.bitwizard.nl/sig11/ Hope this helps :) Martin -- ------------------------------------------------------------------------ Martin Blapp, (blapp@attic.ch) Attic Internet Services, Bechburgstrasse 8, 4702 Oensingen, Switzerland Phone: +41 62 396 43 70, Fax: +41 62 396 43 72 PGP fingerprint: 4E96 1AE8 4AA6 AB40 1AD6 DB42 7623 995D 522A 1D38 ------------------------------------------------------------------------ Public key available at: http://www.attic.ch/pgp-public.html To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Jun 28 08:58:56 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA06041 for freebsd-stable-outgoing; Sun, 28 Jun 1998 08:58:56 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from techpower.net (hometeam@techpower.net [205.133.231.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA06026 for ; Sun, 28 Jun 1998 08:58:54 -0700 (PDT) (envelope-from hometeam@techpower.net) Received: from localhost (hometeam@localhost) by techpower.net (8.8.8/8.8.8) with SMTP id LAA23439 for ; Sun, 28 Jun 1998 11:59:37 -0400 (EDT) (envelope-from hometeam@techpower.net) Date: Sun, 28 Jun 1998 11:59:37 -0400 (EDT) From: Jt Reply-To: Jt To: freebsd-stable@FreeBSD.ORG Subject: make world fails Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I get the following errors when attemping make world My make.conf I use default setting . I had changed them to uncommenting Cflags and noprofile thing this might be a problem I changed them back. I removed /usr/obj I tryed a make world in /usr/src I get the following error cc -O -DLIBC_RCS -DSYSLIBC_RCS -D__DBINTERFACE_PRIVATE -DPOSIX_MISTAKE -I/usr/sr c/lib/libc/../libc/locale -DYP -I/usr/obj/usr/src/tmp/usr/include -c /usr/src/li b/libc/../libc/i386/sys/i386_set_ldt.c -o i386_set_ldt.o building standard c library nm: bt_debug.o: no name list nm: euc.o: no name list nm: mskanji.o: no name list nm: utf2.o: no name list ar: rpc_dtable{ize.o: No such file or directory *** Error code 1 Stop. *** Error code 1 Stop. *** Error code 1 Stop. *** Error code 1 I tryed a cd /usr/src ; make depend I get the following: /libI77/wrtfmt.c /usr/src/lib/libf2c/../libI77/wsfe.c /usr/src/lib/libf2c/../lib I77/wsle.c /usr/src/lib/libf2c/../libI77/wsne.c /usr/src/lib/libf2c/../libI77/xw sne.c /usr/src/lib/libf2c/../libI77/uio.c:29: unterminated string or character constan t /usr/src/lib/libf2c/../libI77/uio.c:23: possible real start of unterminated cons tant mkdep: compile failed *** Error code 1 Stop. *** Error code 1 Stop. *** Error code 1 Stop. Everthing was working fine I cvsup nitely cron job and make world once a month Last make world was fine. Any help would be appreciated. Thanks. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Jun 28 09:36:04 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA10326 for freebsd-stable-outgoing; Sun, 28 Jun 1998 09:36:04 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from ix.netcom.com (sil-wa5-20.ix.netcom.com [206.214.137.116]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA10320 for ; Sun, 28 Jun 1998 09:36:01 -0700 (PDT) (envelope-from tomdean@ix.netcom.com) Received: (from tomdean@localhost) by ix.netcom.com (8.8.8/8.8.8) id JAA18687; Sun, 28 Jun 1998 09:35:19 -0700 (PDT) (envelope-from tomdean) Date: Sun, 28 Jun 1998 09:35:19 -0700 (PDT) Message-Id: <199806281635.JAA18687@ix.netcom.com> From: Thomas Dean To: hometeam@techpower.net CC: freebsd-stable@FreeBSD.ORG In-reply-to: (message from Jt on Sun, 28 Jun 1998 09:00:31 -0400 (EDT)) Subject: Re: makefile Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG What version of FreeBSD are you running? What are you trying to do? What command is failing? In sys/i386/conf/Makefile.i386, %VERSREQ= 220000 may be correct, depending on which version of FreeBSD you are running. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Jun 28 14:26:59 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA10720 for freebsd-stable-outgoing; Sun, 28 Jun 1998 14:26:59 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA10715 for ; Sun, 28 Jun 1998 14:26:58 -0700 (PDT) (envelope-from jkh@time.cdrom.com) Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.8/8.8.8) with ESMTP id OAA03585; Sun, 28 Jun 1998 14:25:09 -0700 (PDT) (envelope-from jkh@time.cdrom.com) To: Jt cc: freebsd-stable@FreeBSD.ORG Subject: Re: makefile In-reply-to: Your message of "Sun, 28 Jun 1998 09:00:31 EDT." Date: Sun, 28 Jun 1998 14:25:09 -0700 Message-ID: <3581.899069109@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Removing old directory ../../compile/hometeam: Done. > Unknown % constructin generic makefile: %VERSREQ= 220000 > Kernel build directory is ../../compile/hometeam As always, syncronize your kernel sources AND the sources to config and make sure that one is built before the other. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Jun 28 15:16:22 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA16988 for freebsd-stable-outgoing; Sun, 28 Jun 1998 15:16:22 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from mail.wsg.net (ns1.wsg.net [206.97.122.2]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id PAA16981 for ; Sun, 28 Jun 1998 15:16:19 -0700 (PDT) (envelope-from gilem@wsg.net) Message-Id: <199806282216.PAA16981@hub.freebsd.org> Received: (qmail 27228 invoked by uid 0); 28 Jun 1998 22:22:03 -0000 Received: from mike.wsg.net (HELO tc) (206.97.122.31) by mail.wsg.net with SMTP; 28 Jun 1998 22:22:03 -0000 X-Sender: mikemail@mail.wsg.net X-Mailer: QUALCOMM Windows Eudora Pro Version 4.0.1 Date: Sun, 28 Jun 1998 18:11:15 -0400 To: freebsd-stable@FreeBSD.ORG From: "Michael R. Gile" Subject: determining ecc errors on freebsd-stable In-Reply-To: <199806280154.SAA05074@hub.freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG there have been some suggestions to my previous post about signal 10 errors that it could be a memory problem. If this is the case, i would think that the ecc controller would be correcting at least some of these problems. Is there a way freebsd can be set to log the ecc corrections, like a sun box does? If not, can someone point me to the necessary docs to add this? Thanks ====================================================== Michael Gile gilem@wsg.net President (518)435-0682 Web Services Group http://www.wsg.net/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Jun 28 17:05:03 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA00825 for freebsd-stable-outgoing; Sun, 28 Jun 1998 17:05:03 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from pop.uniserve.com (pop.uniserve.com [204.244.156.3]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id RAA00803 for ; Sun, 28 Jun 1998 17:04:51 -0700 (PDT) (envelope-from tom@uniserve.com) Received: from shell.uniserve.ca [204.244.186.218] by pop.uniserve.com with smtp (Exim 1.82 #4) id 0yqRR6-0001VO-00; Sun, 28 Jun 1998 17:04:44 -0700 Date: Sun, 28 Jun 1998 17:04:41 -0700 (PDT) From: Tom X-Sender: tom@shell.uniserve.ca To: "Michael R. Gile" cc: freebsd-stable@FreeBSD.ORG Subject: Re: determining ecc errors on freebsd-stable In-Reply-To: <199806282216.PAA16981@hub.freebsd.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 28 Jun 1998, Michael R. Gile wrote: > there have been some suggestions to my previous post about signal 10 errors > that it could be a memory problem. If this is the case, i would think that > the ecc controller would be correcting at least some of these problems. > Is there a way freebsd can be set to log the ecc corrections, like a sun > box does? If not, can someone point me to the necessary docs to add this? Most systems do not have ECC capable memory. All off the shelf consumer level computers certainly don't, though most can be upgraded by replaced the memory. There is no way to log ECC corrections are they are done transparently in the hardware, and currently there is no mechanism for the hardware to make available that kind of info. Tom To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Jun 28 19:49:09 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA21013 for freebsd-stable-outgoing; Sun, 28 Jun 1998 19:49:09 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from mail.wsg.net (ns1.wsg.net [206.97.122.2]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id TAA21008 for ; Sun, 28 Jun 1998 19:49:07 -0700 (PDT) (envelope-from gilem@wsg.net) Message-Id: <199806290249.TAA21008@hub.freebsd.org> Received: (qmail 1580 invoked by uid 0); 29 Jun 1998 02:54:54 -0000 Received: from mike.wsg.net (HELO tc) (206.97.122.31) by mail.wsg.net with SMTP; 29 Jun 1998 02:54:54 -0000 X-Sender: mikemail@mail.wsg.net X-Mailer: QUALCOMM Windows Eudora Pro Version 4.0.1 Date: Sun, 28 Jun 1998 22:43:26 -0400 To: Tom From: "Michael R. Gile" Subject: Re: determining ecc errors on freebsd-stable Cc: freebsd-stable@FreeBSD.ORG In-Reply-To: References: <199806282216.PAA16981@hub.freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 05:04 PM 6/28/98 -0700, Tom wrote: > >On Sun, 28 Jun 1998, Michael R. Gile wrote: > >> there have been some suggestions to my previous post about signal 10 errors >> that it could be a memory problem. If this is the case, i would think that >> the ecc controller would be correcting at least some of these problems. >> Is there a way freebsd can be set to log the ecc corrections, like a sun >> box does? If not, can someone point me to the necessary docs to add this? > > Most systems do not have ECC capable memory. All off the shelf consumer >level computers certainly don't, though most can be upgraded by replaced >the memory. agreed. however, this particular machine is an AST server, with ECC capability. > There is no way to log ECC corrections are they are done >transparently in the hardware, and currently there is no mechanism for the >hardware to make available that kind of info. there must be some status register that records these errors. Otherwise what good is ECC? If it doesn't tell you that something is wrong, then it is useless for detection of problems, no? The information i have found indicates that these errors are stored in the configuration registers of the memory controllers. Unfortunately, i have been unable to get confirmation from intel on this subject. Is there any way to get to these registers from within freebsd? Thanks. ====================================================== Michael Gile gilem@wsg.net President (518)435-0682 Web Services Group http://www.wsg.net/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Jun 28 19:57:35 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA22242 for freebsd-stable-outgoing; Sun, 28 Jun 1998 19:57:35 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from pop.uniserve.com (pop.uniserve.com [204.244.156.3]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id TAA22237 for ; Sun, 28 Jun 1998 19:57:32 -0700 (PDT) (envelope-from tom@uniserve.com) Received: from shell.uniserve.ca [204.244.186.218] by pop.uniserve.com with smtp (Exim 1.82 #4) id 0yqU8H-0004Dq-00; Sun, 28 Jun 1998 19:57:29 -0700 Date: Sun, 28 Jun 1998 19:57:26 -0700 (PDT) From: Tom X-Sender: tom@shell.uniserve.ca To: "Michael R. Gile" cc: freebsd-stable@FreeBSD.ORG Subject: Re: determining ecc errors on freebsd-stable In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 28 Jun 1998, Michael R. Gile wrote: > > There is no way to log ECC corrections are they are done > >transparently in the hardware, and currently there is no mechanism for the > >hardware to make available that kind of info. > > there must be some status register that records these errors. Otherwise what > good is ECC? If it doesn't tell you that something is wrong, then it is useless Either ECC fixes the error, or if the error is unfixable, the hardware generates a NMI which will cause a panic and reboot. Basically, if a fixable error occurs, you won't know about it. If an unfixable error occurs, you'll know real fast. Tom To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Jun 28 20:09:10 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA23429 for freebsd-stable-outgoing; Sun, 28 Jun 1998 20:09:10 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from weck.brokersys.com (root@weck.brokersys.com [209.113.60.130]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA23423 for ; Sun, 28 Jun 1998 20:09:08 -0700 (PDT) (envelope-from jim.king@mail.sstar.com) Received: from jim-home (ernie-60.brokersys.com [209.113.60.61]) by weck.brokersys.com (8.8.8/8.8.8) with SMTP id WAA29549 for ; Sun, 28 Jun 1998 22:12:28 -0500 Message-Id: <3.0.5.32.19980628220904.008411f0@mail.sstar.com> X-Sender: jim.king@mail.sstar.com X-Mailer: QUALCOMM Windows Eudora Light Version 3.0.5 (32) Date: Sun, 28 Jun 1998 22:09:04 -0500 To: freebsd-stable@FreeBSD.ORG From: Jim King Subject: Re: determining ecc errors on freebsd-stable In-Reply-To: References: <199806282216.PAA16981@hub.freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 05:04 PM 6/28/98 -0700, Tom wrote: > >On Sun, 28 Jun 1998, Michael R. Gile wrote: > >> there have been some suggestions to my previous post about signal 10 errors >> that it could be a memory problem. If this is the case, i would think that >> the ecc controller would be correcting at least some of these problems. >> Is there a way freebsd can be set to log the ecc corrections, like a sun >> box does? If not, can someone point me to the necessary docs to add this? > > Most systems do not have ECC capable memory. All off the shelf consumer >level computers certainly don't, though most can be upgraded by replaced >the memory. > > There is no way to log ECC corrections are they are done >transparently in the hardware, and currently there is no mechanism for the >hardware to make available that kind of info. My very newest PC (a Gateway 400 MHz Pentium II, just unboxed Friday) has an option in the BIOS configuration to log ECC corrections via DMI. I know almost nothing about DMI, but I would assume there's some way to get at this information besides the BIOS config utility. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Jun 28 22:49:29 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA11042 for freebsd-stable-outgoing; Sun, 28 Jun 1998 22:49:29 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from whizzo.transsys.com (whizzo.TransSys.COM [144.202.42.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA11036 for ; Sun, 28 Jun 1998 22:49:24 -0700 (PDT) (envelope-from louie@whizzo.transsys.com) Received: from whizzo.transsys.com (localhost.transsys.com [127.0.0.1]) by whizzo.transsys.com (8.8.8/8.7.3) with ESMTP id BAA02456; Mon, 29 Jun 1998 01:49:20 -0400 (EDT) Message-Id: <199806290549.BAA02456@whizzo.transsys.com> X-Mailer: exmh version 2.0.1 12/23/97 To: Tom cc: "Michael R. Gile" , freebsd-stable@FreeBSD.ORG From: "Louis A. Mamakos" Subject: Re: determining ecc errors on freebsd-stable References: In-reply-to: Your message of "Sun, 28 Jun 1998 19:57:26 PDT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 29 Jun 1998 01:49:20 -0400 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > On Sun, 28 Jun 1998, Michael R. Gile wrote: > > > > There is no way to log ECC corrections are they are done > > >transparently in the hardware, and currently there is no mechanism for the > > >hardware to make available that kind of info. > > > > there must be some status register that records these errors. Otherwise what > > good is ECC? If it doesn't tell you that something is wrong, then it is useless > > Either ECC fixes the error, or if the error is unfixable, the hardware > generates a NMI which will cause a panic and reboot. > > Basically, if a fixable error occurs, you won't know about it. If an > unfixable error occurs, you'll know real fast. Well, geez, it would be nice to know that you had bum memory in the machine so you could replace it at some time of your choosing. ECC memory ought to be better than just having your system crash later rather than sooner. This is the kind of thing that seperates toy computers from robust, has to be up no matter what mission critical computers. louie To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Jun 28 22:50:18 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA11258 for freebsd-stable-outgoing; Sun, 28 Jun 1998 22:50:18 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from antipodes.cdrom.com (castles338.castles.com [208.214.167.38]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA11247 for ; Sun, 28 Jun 1998 22:50:15 -0700 (PDT) (envelope-from mike@antipodes.cdrom.com) Received: from antipodes.cdrom.com (localhost [127.0.0.1]) by antipodes.cdrom.com (8.8.8/8.8.5) with ESMTP id WAA22882; Sun, 28 Jun 1998 22:51:00 -0700 (PDT) Message-Id: <199806290551.WAA22882@antipodes.cdrom.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: Jim King cc: freebsd-stable@FreeBSD.ORG Subject: Re: determining ecc errors on freebsd-stable In-reply-to: Your message of "Sun, 28 Jun 1998 22:09:04 CDT." <3.0.5.32.19980628220904.008411f0@mail.sstar.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 28 Jun 1998 22:51:00 -0700 From: Mike Smith Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > At 05:04 PM 6/28/98 -0700, Tom wrote: > > > >On Sun, 28 Jun 1998, Michael R. Gile wrote: > > > >> there have been some suggestions to my previous post about signal 10 errors > >> that it could be a memory problem. If this is the case, i would think > that > >> the ecc controller would be correcting at least some of these problems. > >> Is there a way freebsd can be set to log the ecc corrections, like a sun > >> box does? If not, can someone point me to the necessary docs to add this? > > > > Most systems do not have ECC capable memory. All off the shelf consumer > >level computers certainly don't, though most can be upgraded by replaced > >the memory. > > > > There is no way to log ECC corrections are they are done > >transparently in the hardware, and currently there is no mechanism for the > >hardware to make available that kind of info. > > My very newest PC (a Gateway 400 MHz Pentium II, just unboxed Friday) has > an option in the BIOS configuration to log ECC corrections via DMI. I know > almost nothing about DMI, but I would assume there's some way to get at > this information besides the BIOS config utility. Yes; you have to use the PnP BIOS. Unfortunately, we won't be able to support this in the 2.2 family (it requires 3.x features). Typically, the system hardware will generate an SMI event during which the SMI handler (part of the BIOS) will examine the ECC event(s) and log them. For Intel hardware, you should study the Intel datasheets, however it should be noted that we cannot play on the BIOS side of the SMI fence - we have to talk to it according to the rules, ie. you should be focussing on using the PnP BIOS to obtain event log information, not poking the hardware. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Jun 28 23:12:06 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA13869 for freebsd-stable-outgoing; Sun, 28 Jun 1998 23:12:06 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from pop.uniserve.com (pop.uniserve.com [204.244.156.3]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id XAA13864 for ; Sun, 28 Jun 1998 23:12:05 -0700 (PDT) (envelope-from tom@uniserve.com) Received: from shell.uniserve.ca [204.244.186.218] by pop.uniserve.com with smtp (Exim 1.82 #4) id 0yqXAU-00026X-00; Sun, 28 Jun 1998 23:11:58 -0700 Date: Sun, 28 Jun 1998 23:11:54 -0700 (PDT) From: Tom X-Sender: tom@shell.uniserve.ca To: "Louis A. Mamakos" cc: "Michael R. Gile" , freebsd-stable@FreeBSD.ORG Subject: Re: determining ecc errors on freebsd-stable In-Reply-To: <199806290549.BAA02456@whizzo.transsys.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 29 Jun 1998, Louis A. Mamakos wrote: > > On Sun, 28 Jun 1998, Michael R. Gile wrote: > > > > > > There is no way to log ECC corrections are they are done > > > >transparently in the hardware, and currently there is no mechanism for the > > > >hardware to make available that kind of info. > > > > > > there must be some status register that records these errors. Otherwise what > > > good is ECC? If it doesn't tell you that something is wrong, then it is useless > > > > Either ECC fixes the error, or if the error is unfixable, the hardware > > generates a NMI which will cause a panic and reboot. > > > > Basically, if a fixable error occurs, you won't know about it. If an > > unfixable error occurs, you'll know real fast. > > Well, geez, it would be nice to know that you had bum memory in the > machine so you could replace it at some time of your choosing. ECC > memory ought to be better than just having your system crash later > rather than sooner. Well, you could trap the NMI and kill whatever occupied the offending location, and make it sure it wasn't used again. This is an operating system issue, not a hardware one. An NMI panic is MUCH better that "crashing later", as you know precisely what caused it. Memory corruption on non-ECC/non-parity systems is very difficult to track. Plus, you could be corrupting valuable data in the process. With existing ECC systems, at least you get a clean reboot before anything serious is wreaked. > This is the kind of thing that seperates toy computers from robust, > has to be up no matter what mission critical computers. Yeah, yeah... Sun makes a big deal about this... fact of the matter is, if you lose some memory containing the kernel you have to reboot anyhow. If you don't want a toy computer, you get a cluster anyhow, since there is way more stuff that can fail than memory (and more often too). > louie Tom To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Jun 28 23:12:23 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA13905 for freebsd-stable-outgoing; Sun, 28 Jun 1998 23:12:23 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from gatekeeper.alcatel.com.au (gatekeeper.alcatel.com.au [203.17.66.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA13896 for ; Sun, 28 Jun 1998 23:12:18 -0700 (PDT) (envelope-from peter.jeremy@alcatel.com.au) Received: from mfg1.cim.alcatel.com.au ("port 2893"@[139.188.23.1]) by gatekeeper.alcatel.com.au (PMDF V5.1-7 #U2695) with ESMTP id <01IYT7Q11C0G004OTJ@gatekeeper.alcatel.com.au> for freebsd-stable@FreeBSD.ORG; Mon, 29 Jun 1998 14:02:16 +1000 Received: from gsms01.alcatel.com.au by cim.alcatel.com.au (PMDF V5.1-10 #23324) with ESMTP id <01IYT7PL7T0GCWIH03@cim.alcatel.com.au> for freebsd-stable@FreeBSD.ORG; Mon, 29 Jun 1998 14:01:56 +1000 Received: (from jeremyp@localhost) by gsms01.alcatel.com.au (8.8.8/8.7.3) id OAA02134 for freebsd-stable@FreeBSD.ORG; Mon, 29 Jun 1998 14:01:52 +1000 (EST) Date: Mon, 29 Jun 1998 14:01:52 +1000 (EST) From: Peter Jeremy Subject: Re: determining ecc errors on freebsd-stable To: freebsd-stable@FreeBSD.ORG Message-id: <199806290401.OAA02134@gsms01.alcatel.com.au> Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 28 Jun 1998 19:57:26 -0700 (PDT), Tom wrote: > Basically, if a fixable error occurs, you won't know about it. If an >unfixable error occurs, you'll know real fast. Which substantially reduces the usefulness of ECC. It may increase the MTBF (since a single-bit failure is now hidden), but it no longer provides fault tolerance since you can't detect a memory module that is getting flaky (or has a hard error). Yet another design engineer for the firing squad... Peter -- Peter Jeremy (VK2PJ) peter.jeremy@alcatel.com.au Alcatel Australia Limited 41 Mandible St Phone: +61 2 9690 5019 ALEXANDRIA NSW 2015 Fax: +61 2 9690 5247 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jun 29 01:37:30 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA03800 for freebsd-stable-outgoing; Mon, 29 Jun 1998 01:37:30 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from tyree.iii.co.uk (tyree.iii.co.uk [195.89.149.230]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA03771; Mon, 29 Jun 1998 01:37:13 -0700 (PDT) (envelope-from nik@iii.co.uk) From: nik@iii.co.uk Received: from carrig.strand.iii.co.uk (carrig.strand.iii.co.uk [192.168.7.25]) by tyree.iii.co.uk (8.8.8/8.8.8) with ESMTP id JAA27562; Mon, 29 Jun 1998 09:36:52 +0100 (BST) Received: (from nik@localhost) by carrig.strand.iii.co.uk (8.8.8/8.8.7) id JAA05111; Mon, 29 Jun 1998 09:36:31 +0100 (BST) Message-ID: <19980629093631.60284@iii.co.uk> Date: Mon, 29 Jun 1998 09:36:31 +0100 To: Stefan Esser Cc: Doug Russell , stable@FreeBSD.ORG, scsi@FreeBSD.ORG Subject: Re: Make world failures (ncr wierdness?) References: <19980627151834.05015@mi.uni-koeln.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.85e In-Reply-To: <19980627151834.05015@mi.uni-koeln.de>; from Stefan Esser on Sat, Jun 27, 1998 at 03:18:34PM +0200 Organization: interactive investor Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [ cc'd to -scsi ] On Sat, Jun 27, 1998 at 03:18:34PM +0200, Stefan Esser wrote: > > Jun 26 10:19:46 doug /kernel: assertion "cp" failed: file "../../pci/ncr.c", line 6191 > > Jun 26 10:19:46 doug /kernel: sd0(ncr0:6:0): COMMAND FAILED (4 28) @f05a9800. > > This is your drive complaining about too many simultanous commands. > Some drives support varying numbers of tags depending on parameters > we have no control over, some have firmware bugs and can't even deal > with 2 tagged commands at times. IIRC, then the LXY4 revision of the > Quantum Atlas II firmware is known to cause such problems. You may > want to upgrade to a later revision (available from the Quantum FTP > server at ftp://ftp.qntm.com/pub/support/Firmware). The upgrade can > be performed from a DOS floppy with ASPI drivers for SDMS (came with > your NCR card). Not having easy access to a machine running DOS, this is a bit tricky for me to do. Would anyone be kind enough to build a floppy image with the right files on and make it available for FTP? N -- Work: nik@iii.co.uk | FreeBSD + Perl + Apache Rest: nik@nothing-going-on.demon.co.uk | Remind me again why we need Play: nik@freebsd.org | Microsoft? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jun 29 08:44:03 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA07610 for freebsd-stable-outgoing; Mon, 29 Jun 1998 08:44:03 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from pop.uniserve.com (pop.uniserve.com [204.244.156.3]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id IAA07583 for ; Mon, 29 Jun 1998 08:43:58 -0700 (PDT) (envelope-from tom@uniserve.com) Received: from shell.uniserve.ca [204.244.186.218] by pop.uniserve.com with smtp (Exim 1.82 #4) id 0yqg4e-0003qG-00; Mon, 29 Jun 1998 08:42:32 -0700 Date: Mon, 29 Jun 1998 08:42:31 -0700 (PDT) From: Tom X-Sender: tom@shell.uniserve.ca To: Peter Jeremy cc: freebsd-stable@FreeBSD.ORG Subject: Re: determining ecc errors on freebsd-stable In-Reply-To: <199806290401.OAA02134@gsms01.alcatel.com.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 29 Jun 1998, Peter Jeremy wrote: > On Sun, 28 Jun 1998 19:57:26 -0700 (PDT), Tom wrote: > > Basically, if a fixable error occurs, you won't know about it. If an > >unfixable error occurs, you'll know real fast. > > Which substantially reduces the usefulness of ECC. It may increase > the MTBF (since a single-bit failure is now hidden), but it no longer It will increase MTBF a lot, because you know you have a memory problem after one crash and reboot (outage: < 5 minutes), as compared to non-ECC where you will probably have to go through a dozen application crashes and a few system hangs and/or panics. System hangs are the worst (outage: until someone notices and gets down to power cycle the machine). > provides fault tolerance since you can't detect a memory module that > is getting flaky (or has a hard error). Huh? "no longer provides fault tolerance"? How does it provide fault tolerance? If memory fails, something has to die. The FreeBSD approach of simply rebooting is a bit drastic, but at minimum you have to kill whatever process (assuming it isn't the kernel) is occupying that memory. Also, using single bit errrors to detect "flaky but still working modules" doesn't hold much wait with me. Why? Either memory works or it doesn't. "flaky" memory typically is heat triggered, not random. I have a bunch of 24x7 servers with parity memory (which will crash on even single bit errror), and memory failure is rare. Summary: - ECC is MUCH better than non-ECC - Memory failure is rare. FreeBSD still doesn't have multi-path IO to recover from controler card failure, which occurs much more often. Or, clustering which can protect against software failures (which are still much common than any kind of hardware failure). So putting so much emphasis on ECC is unnecessary. > Yet another design engineer for the firing squad... Still waiting for someone's patches to FreeBSD... > Peter > -- > Peter Jeremy (VK2PJ) peter.jeremy@alcatel.com.au > Alcatel Australia Limited > 41 Mandible St Phone: +61 2 9690 5019 > ALEXANDRIA NSW 2015 Fax: +61 2 9690 5247 Tom To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jun 29 09:37:38 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA17167 for freebsd-stable-outgoing; Mon, 29 Jun 1998 09:37:38 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from gateman.zeus.leitch.com (gateman.zeus.leitch.com [204.187.61.193]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA17143 for ; Mon, 29 Jun 1998 09:37:25 -0700 (PDT) (envelope-from woods@tap.zeus.leitch.com) Received: from zeus.leitch.com (tap.zeus.leitch.com [204.187.61.10]) by gateman.zeus.leitch.com (8.8.5/8.7.3/1.0) with ESMTP id MAA14847 for ; Mon, 29 Jun 1998 12:36:11 -0400 (EDT) Received: from brain.zeus.leitch.com (brain.zeus.leitch.com [204.187.61.32]) by zeus.leitch.com (8.7.5/8.7.3/1.0) with ESMTP id MAA00280 for ; Mon, 29 Jun 1998 12:36:11 -0400 (EDT) Received: (from woods@localhost) by brain.zeus.leitch.com (8.8.8/8.8.8) id MAA20240; Mon, 29 Jun 1998 12:36:11 -0400 (EDT) (envelope-from woods@tap.zeus.leitch.com) Date: Mon, 29 Jun 1998 12:36:11 -0400 (EDT) Message-Id: <199806291636.MAA20240@brain.zeus.leitch.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit From: woods@zeus.leitch.com (Greg A. Woods) To: freebsd-stable@FreeBSD.ORG Subject: Re: determining ecc errors on freebsd-stable In-Reply-To: Mike Smith's message of "Sun, June 28, 1998 22:51:00 -0700" regarding "Re: determining ecc errors on freebsd-stable " id <199806290551.WAA22882@antipodes.cdrom.com> References: <3.0.5.32.19980628220904.008411f0@mail.sstar.com> <199806290551.WAA22882@antipodes.cdrom.com> X-Mailer: VM 6.45 under Emacs 20.2.1 Reply-To: freebsd-stable@FreeBSD.ORG Organization: Planix, Inc.; Toronto, Ontario; Canada Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [ On Sun, June 28, 1998 at 22:51:00 (-0700), Mike Smith wrote: ] > Subject: Re: determining ecc errors on freebsd-stable > > Jim King > > > > At 05:04 PM 6/28/98 -0700, Tom wrote: > > > > > > There is no way to log ECC corrections are they are done > > > transparently in the hardware, and currently there is no mechanism > > > for the hardware to make available that kind of info. > > > > My very newest PC (a Gateway 400 MHz Pentium II, just unboxed Friday) has > > an option in the BIOS configuration to log ECC corrections via DMI. I know > > almost nothing about DMI, but I would assume there's some way to get at > > this information besides the BIOS config utility. I've also been trying to find out how to log ECC errors on an ASUS P2L97 motherboard (using the Intel 440LX chipset). > Yes; you have to use the PnP BIOS. Unfortunately, we won't be able to > support this in the 2.2 family (it requires 3.x features). That sucks. But then why use the PnP BIOS anyway? (more on this below) > Typically, the system hardware will generate an SMI event during which > the SMI handler (part of the BIOS) will examine the ECC event(s) and log > them. I'd actually expect an NMI, at least on boards using Intel chipsets such as the 440LX. I don't think an SMI would make much sense. When I cause an SMI via the LM78 on my ASUS P2L97 motherboard the system seems to go into suspend mode. That's asssuming, of course, that the LM78's SMI pin is hooked up to the same SMI as the i82371 ASIC, which is a fair assumption given the apparent behaviour. > For Intel hardware, you should study the Intel datasheets, however it > should be noted that we cannot play on the BIOS side of the SMI fence - > we have to talk to it according to the rules, ie. you should be > focussing on using the PnP BIOS to obtain event log information, not > poking the hardware. I've always been very wary of anything claiming to be "PnP", even with the "(tm)" [suggesting it's some industry "standard"], and I've also been very wary of ever trying to access a system BIOS that wasn't designed with Unix firmly in mind. Poking at the hardware is often far simpler and avoids needless confusion and complication introduced by foreign interfaces. Unfortunately motherboard manufacturers make it really hard to know how to poke at the hardware (Intel's manuals are the best I've seen in PC-land recently, and they're far below good). One potentially positive potential seems is that the SMBIOS v2.1 spec. provides a pointer to the (packed) SMBIOS data structures residing somewhere in 32-bit physical address space so that the data can be accesssed from a 32-bit protected mode operating system. The only problem is that I don't see how an OS such as Unix is to allow the SMBIOS code to handle NMIs as it would need to in order to record things like ECC events. Yet another reason why it's probably better to just support the hardware directly. There's already ample direct hardware support in FreeBSD, and most of it is not going to go away no matter how fancy the BIOS gets (even the OpenFirmware guys are going direct to the hardware when they can for performance reasons), so a wee bit more hardware knowledge shouldn't hurt much. -- Greg A. Woods +1 416 443-1734 VE3TCP Planix, Inc. ; Secrets of the Weird To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jun 29 10:07:30 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA21559 for freebsd-stable-outgoing; Mon, 29 Jun 1998 10:07:30 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA21539 for ; Mon, 29 Jun 1998 10:07:15 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.8.8/8.8.5) with ESMTP id KAA00714 for ; Mon, 29 Jun 1998 10:07:39 -0700 (PDT) Message-Id: <199806291707.KAA00714@dingo.cdrom.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: freebsd-stable@FreeBSD.ORG Subject: Re: determining ecc errors on freebsd-stable In-reply-to: Your message of "Mon, 29 Jun 1998 12:36:11 EDT." <199806291636.MAA20240@brain.zeus.leitch.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 29 Jun 1998 10:07:39 -0700 From: Mike Smith Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > My very newest PC (a Gateway 400 MHz Pentium II, just unboxed Friday) has > > > an option in the BIOS configuration to log ECC corrections via DMI. I know > > > almost nothing about DMI, but I would assume there's some way to get at > > > this information besides the BIOS config utility. > > I've also been trying to find out how to log ECC errors on an ASUS P2L97 > motherboard (using the Intel 440LX chipset). Log them or retrieve them from the log? Use the DMI interface to retrieve them from the log. > > Yes; you have to use the PnP BIOS. Unfortunately, we won't be able to > > support this in the 2.2 family (it requires 3.x features). > > That sucks. But then why use the PnP BIOS anyway? (more on this below) Because the BIOS is the only component that knows how the hardware is configured. > > Typically, the system hardware will generate an SMI event during which > > the SMI handler (part of the BIOS) will examine the ECC event(s) and log > > them. > > I'd actually expect an NMI, at least on boards using Intel chipsets such > as the 440LX. That depends on how the board implementor wants to do it. Using SMI means that you don't run the risk of the OS stealing the vector from you. > I don't think an SMI would make much sense. When I cause an SMI via the > LM78 on my ASUS P2L97 motherboard the system seems to go into suspend > mode. That's asssuming, of course, that the LM78's SMI pin is hooked up > to the same SMI as the i82371 ASIC, which is a fair assumption given the > apparent behaviour. Not necessarily. > > For Intel hardware, you should study the Intel datasheets, however it > > should be noted that we cannot play on the BIOS side of the SMI fence - > > we have to talk to it according to the rules, ie. you should be > > focussing on using the PnP BIOS to obtain event log information, not > > poking the hardware. > > I've always been very wary of anything claiming to be "PnP", even with > the "(tm)" [suggesting it's some industry "standard"], and I've also > been very wary of ever trying to access a system BIOS that wasn't > designed with Unix firmly in mind. Given that current BIOS standards are being developed and implemented with NT in mind, and given that NT is as anally 32-bit as most Unix systems are, I think you may need to reassess your position. > Poking at the hardware is often far simpler and avoids needless > confusion and complication introduced by foreign interfaces. > Unfortunately motherboard manufacturers make it really hard to know how > to poke at the hardware (Intel's manuals are the best I've seen in > PC-land recently, and they're far below good). The whole point is that you should *not* be poking at the hardware, but rather talking to the BIOS. This is just the same as eg. under OpenFirmware. (Performance isn't an issue for this sort of information, but abstraction and portability is.) > One potentially positive potential seems is that the SMBIOS v2.1 spec. > provides a pointer to the (packed) SMBIOS data structures residing > somewhere in 32-bit physical address space so that the data can be > accesssed from a 32-bit protected mode operating system. Unfortunately, what you generally get with this is a minimal table in ROM (it varies between vendors) only describing the static hardware in the system. I have a tool for dumping this (via /dev/mem), I haven't found too many systems where there's much interesting there (as opposed to what can be retrieved using the LanDesk client, eg.). > The only > problem is that I don't see how an OS such as Unix is to allow the > SMBIOS code to handle NMIs as it would need to in order to record things > like ECC events. This is why board implementers use SMI. It's also used eg. for APM (see the APM mailbox register in the PIIX4). > Yet another reason why it's probably better to just > support the hardware directly. Not at all. Why try to support all the different hardware (an impossible task) when we can move up a level and use the same API that everyone else is using? It's documented and it works. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jun 29 15:41:41 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA25576 for freebsd-stable-outgoing; Mon, 29 Jun 1998 15:41:41 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from homer.supersex.com (homer.supersex.com [209.5.1.4]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA25556 for ; Mon, 29 Jun 1998 15:41:31 -0700 (PDT) (envelope-from leo@homer.supersex.com) Received: (from leo@localhost) by homer.supersex.com (8.8.8/8.8.5) id SAA18881; Mon, 29 Jun 1998 18:42:21 -0400 (EDT) Message-ID: <19980629184220.15472@supersex.com> Date: Mon, 29 Jun 1998 18:42:20 -0400 From: Leo Papandreou To: stable@FreeBSD.ORG Subject: Re: determining ecc errors on freebsd-stable References: <199806290401.OAA02134@gsms01.alcatel.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89i In-Reply-To: ; from Tom on Mon, Jun 29, 1998 at 08:42:31AM -0700 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Jun 29, 1998 at 08:42:31AM -0700, Tom wrote: > [...] > > Summary: > > - ECC is MUCH better than non-ECC Will ECC on the cache trap RAM errors even if the RAM doesnt have ECC? > - Memory failure is rare. FreeBSD still doesn't have multi-path IO to > recover from controler card failure, which occurs much more often. Or, > clustering which can protect against software failures (which are still > much common than any kind of hardware failure). So putting so much > emphasis on ECC is unnecessary. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jun 29 15:44:19 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA25920 for freebsd-stable-outgoing; Mon, 29 Jun 1998 15:44:19 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from pine.liii.com (pine.liii.com [198.207.193.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA25837 for ; Mon, 29 Jun 1998 15:44:05 -0700 (PDT) (envelope-from chrisp@liii.com) Received: from rowan.liii.com (chrisp@rowan.liii.com [198.207.193.5]) by pine.liii.com (8.8.6/8.8.5) with ESMTP id WAA22313 for ; Mon, 29 Jun 1998 22:43:55 GMT Received: from localhost (chrisp@localhost) by rowan.liii.com (8.8.6/8.8.4) with SMTP id SAA14103 for ; Mon, 29 Jun 1998 18:43:52 -0400 (EDT) X-Authentication-Warning: rowan.liii.com: chrisp owned process doing -bs Date: Mon, 29 Jun 1998 18:43:51 -0400 (EDT) From: Chris Puccio To: freebsd-stable@FreeBSD.ORG Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG subscribe freebsd-stable To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jun 29 22:33:33 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA03492 for freebsd-stable-outgoing; Mon, 29 Jun 1998 22:33:33 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from pop.uniserve.com (pop.uniserve.com [204.244.156.3]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id WAA03466 for ; Mon, 29 Jun 1998 22:33:18 -0700 (PDT) (envelope-from tom@uniserve.com) Received: from shell.uniserve.ca [204.244.186.218] by pop.uniserve.com with smtp (Exim 1.82 #4) id 0yqt2W-0005Mb-00; Mon, 29 Jun 1998 22:33:12 -0700 Date: Mon, 29 Jun 1998 22:33:08 -0700 (PDT) From: Tom X-Sender: tom@shell.uniserve.ca To: Leo Papandreou cc: stable@FreeBSD.ORG Subject: Re: determining ecc errors on freebsd-stable In-Reply-To: <19980629184220.15472@supersex.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 29 Jun 1998, Leo Papandreou wrote: > On Mon, Jun 29, 1998 at 08:42:31AM -0700, Tom wrote: > > > > Summary: > > > > - ECC is MUCH better than non-ECC > > Will ECC on the cache trap RAM errors even if the RAM doesnt > have ECC? No. ECC on cache only protects the data that has made it the cache. Hopefully your internal bus between cache and CPU also support ECC! Basically all data paths need protection to cover all the bases. Tom To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jun 30 09:13:01 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA16352 for freebsd-stable-outgoing; Tue, 30 Jun 1998 09:13:01 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from gateman.zeus.leitch.com (gateman.zeus.leitch.com [204.187.61.193]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA16326 for ; Tue, 30 Jun 1998 09:12:41 -0700 (PDT) (envelope-from woods@tap.zeus.leitch.com) Received: from zeus.leitch.com (tap.zeus.leitch.com [204.187.61.10]) by gateman.zeus.leitch.com (8.8.5/8.7.3/1.0) with ESMTP id MAA20119 for ; Tue, 30 Jun 1998 12:11:20 -0400 (EDT) Received: from brain.zeus.leitch.com (brain.zeus.leitch.com [204.187.61.32]) by zeus.leitch.com (8.7.5/8.7.3/1.0) with ESMTP id MAA06043 for ; Tue, 30 Jun 1998 12:11:19 -0400 (EDT) Received: (from woods@localhost) by brain.zeus.leitch.com (8.8.8/8.8.8) id MAA05306; Tue, 30 Jun 1998 12:11:19 -0400 (EDT) (envelope-from woods@tap.zeus.leitch.com) Date: Tue, 30 Jun 1998 12:11:19 -0400 (EDT) Message-Id: <199806301611.MAA05306@brain.zeus.leitch.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit From: woods@zeus.leitch.com (Greg A. Woods) To: freebsd-stable@FreeBSD.ORG Subject: Re: determining ecc errors on freebsd-stable In-Reply-To: Tom's message of "Mon, June 29, 1998 22:33:08 -0700" regarding "Re: determining ecc errors on freebsd-stable" id References: <19980629184220.15472@supersex.com> X-Mailer: VM 6.45 under Emacs 20.2.1 Reply-To: freebsd-stable@FreeBSD.ORG Organization: Planix, Inc.; Toronto, Ontario; Canada Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [ On Mon, June 29, 1998 at 22:33:08 (-0700), Tom wrote: ] > Subject: Re: determining ecc errors on freebsd-stable > > Hopefully your internal bus between cache and CPU also support ECC! The bus and the cache RAM both! Unfortunately not many older or lower-end machines in the Intel world do have ECC on the cache, and very few have ECC on the data paths between the CPU and other devices. Most Pentium-Pro and all Pentium-II systems have ECC on the cache, and *can* have ECC on the data bus paths. I don't know how many actually have it enabled, though various server manufacurers, such as Dell, IBM, et al claim they've turned it on. > Basically all data paths need protection to cover all the bases. Buy a good Alpha or Sparc or Power-PC or really good P-Pro for this level of protection. -- Greg A. Woods +1 416 443-1734 VE3TCP Planix, Inc. ; Secrets of the Weird To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jul 1 14:30:09 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA26228 for freebsd-stable-outgoing; Wed, 1 Jul 1998 14:30:09 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from dragonfly.rain.com (methane.dragonfly.rain.com [206.163.85.177]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA26159 for ; Wed, 1 Jul 1998 14:30:03 -0700 (PDT) (envelope-from mason@methane.dragonfly.rain.com) Received: (from mason@localhost) by dragonfly.rain.com (8.8.7/8.8.7) id OAA27148; Wed, 1 Jul 1998 14:30:02 -0700 (PDT) From: mason@methane.dragonfly.rain.com Message-Id: <199807012130.OAA27148@dragonfly.rain.com> Subject: Strange NFS behaviour To: freebsd-stable@FreeBSD.ORG Date: Wed, 1 Jul 1998 14:30:02 -0700 (PDT) Cc: mason@methane.dragonfly.rain.com () X-Mailer: ELM [version 2.4ME+ PL31H (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello all, We've seen some strange behaviour on our FreeBSD 2.2.6-RELEASE system with regards to NFS. 'Sinkhole' is a ASUS P2L97-S/233 system (running FreeBSD 2.2.6-RELEASE) with an Intel Pro-100 card which acts as a NFS server for the /prj for the rest of our network. One of it's clients is 'methane' our Sun 167MHz Ultra2 (running Solaris 2.5.1). What we where seeing is an rm -rf /prj/mumble/dir executed from methane would complete without all of the contents of the directory (or the directory itself) being removed. If you re-ran the rm -rf by hand, the rest of the directory would be removed. We've seen this when doing a build of gcc for MIPS (the makefiles create and remove a number of temporary directories during multilib generation), which would fail (because the directory wasn't removed as the makefile expected). It's also been reported by one of our users typing at the shell. We tried unmounting and remounting with NFS vers 2, same problem. When I changed the vfstab on methane to "vers=2,wsize=1024" the problem disappeared. I'm afraid that this didn't actually fix the problem, it just masked it. Any ideas what's going on here? I've searched through deja news for past messages that might be related to this problem with no luck. Thanks in advance, Mark _______________________________________________________________________________ Mark Mason Dragonfly Software Consulting Company. mason@dragonfly.rain.com 503-641-3440 (office) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jul 1 17:45:30 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA26685 for freebsd-stable-outgoing; Wed, 1 Jul 1998 17:45:30 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from zebedee.local (pdx67-i48-34.teleport.com [204.202.172.48]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA26661 for ; Wed, 1 Jul 1998 17:45:21 -0700 (PDT) (envelope-from tony@rtd.com) Received: from zebedee.local (localhost.local [127.0.0.1]) by zebedee.local (8.8.8/8.8.6) with ESMTP id RAA00361 for ; Wed, 1 Jul 1998 17:48:00 -0700 (PDT) Message-Id: <199807020048.RAA00361@zebedee.local> X-Mailer: exmh version 2.0zeta 7/24/97 To: stable@FreeBSD.ORG X-Face: ZQe?G+$UQG8,i~KL=gy`T:c1bxG<{7ta&{,'$LiA !`"u>-"@wkx>yf.z_5 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, I'm running 2.2-stable (ctm#670 - pre Mike's partition changes) and am having a boot problem. I'm getting the following message when the system tries to mountall, which stops the system from getting to multiuser: /dev/sd1a on /: specified device does not match mounted device I used to have the following disk setup using Booteasy to switch between the OSs: Win95 (IDE, 0x80) FreeBSD(SCSI id=1, 0x81) FreeBSD(SCSI id=2) ... I dropped Win95 and switched to NT 4.0 (SCSI) using the NT bootloader (configured it using the 'bootpart' PD utility): NT 4.0 (SCSI id=0, 0x80) FreeBSD(SCSI id=1, 0x81) FreeBSD (SCSI id=2) ... Removed the IDE disk. I could boot FreeBSD fine (though I would get the message "Can't find file kernel.config" which I don't recall seeing before). Everything was OK until I rebuilt the kernel (I removed my noname sound card which wasn't working). Once I rebuilt I started getting the above 'does not match mounted device' error. I could boot OK if I selected 'kernel.old' or flags '-r' (never quite understood what this does). The only thing to add is that I have the disks wired down in the kernel config file: # Base scsi support: 'scbus', 'sd' (disc), 'st' (tape), 'cd' (cdrom) controller scbus0 at ncr0 device sd0 device st0 device cd0 disk sd1 at scbus0 target 1 unit 0 disk sd2 at scbus0 target 2 unit 0 disk sd3 at scbus0 target 3 unit 0 If anyone knows the answer (or even better would spend a few minutes educating me on the details of why I'm having this problem) I would appreciate it. Thanks Tony To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jul 1 20:48:39 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA23565 for freebsd-stable-outgoing; Wed, 1 Jul 1998 20:48:39 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from emerald.carrot.kansai.oki.co.jp (okigate.oki.co.jp [202.226.91.194]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA23556 for ; Wed, 1 Jul 1998 20:48:31 -0700 (PDT) (envelope-from hyama@emerald.carrot.kansai.oki.co.jp) Received: from localhost (localhost [127.0.0.1]) by emerald.carrot.kansai.oki.co.jp (8.8.6/3.3W-94070111) with ESMTP id MAA00011; Thu, 2 Jul 1998 12:47:53 +0900 (JST) Message-Id: <199807020347.MAA00011@emerald.carrot.kansai.oki.co.jp> To: mike@sentex.net Cc: jkh@time.cdrom.com, stable@FreeBSD.ORG Subject: Re: Release schedule for 2.2.7 From: Hideki Yamamoto In-Reply-To: Your message of "Tue, 23 Jun 1998 08:02:21 -0400" References: <3.0.5.32.19980623080221.00ed3930@sentex.net> X-Mailer: Mew version 1.70 on Emacs 19.28.1 / Mule 2.3 Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Thu, 02 Jul 1998 12:47:53 +0900 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, >>>>> On Tue, 23 Jun 1998 08:02:21 -0400, Mike Tancsa said: Mike> Hello from luser land :-) Mike> It would be great to see support in stable for > 8GIG IDE drives. I dont Mike> know how conservative the change would be, but the big fat drives make Mike> excellent backup devices.... Maybe, you are using FAT32 partition as a backup device, aren't you. I was porting FreeBSD-current msdosfs to FreeBSD-2.2.x. The latest version is on http://members.aol.com/hyama99/. Would you try this? BTY, would someone tell me what to do to merge my port into -stable brunch? I plan to do the followings in one or two weeks. When is deadline to merge codes of new functions? Is my plan too late? Don't I have to do (1)? Items for me to do: (1) delete lines between #if(n)def FBSDCUR and #endif /*FBSDCUR*/ (2) pack sources and documents, and send them by send-pr --------------------------------- Hideki Yamamoto (hyama@acm.org) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jul 1 22:12:06 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA02942 for freebsd-stable-outgoing; Wed, 1 Jul 1998 22:12:06 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from coal.sentex.ca (coal.sentex.ca [209.112.4.16]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA02925 for ; Wed, 1 Jul 1998 22:12:01 -0700 (PDT) (envelope-from mike@sentex.net) Received: from gravel (ospf-mdt.sentex.net [205.211.164.81]) by coal.sentex.ca (8.8.8/8.8.7) with SMTP id BAA25459; Thu, 2 Jul 1998 01:11:51 -0400 (EDT) (envelope-from mike@sentex.net) Message-Id: <3.0.5.32.19980702011201.01179430@sentex.net> X-Sender: mdtancsa@sentex.net X-Mailer: QUALCOMM Windows Eudora Pro Version 3.0.5 (32) Date: Thu, 02 Jul 1998 01:12:01 -0400 To: Hideki Yamamoto From: Mike Tancsa Subject: Re: Release schedule for 2.2.7 Cc: jkh@time.cdrom.com, stable@FreeBSD.ORG In-Reply-To: <199807020347.MAA00011@emerald.carrot.kansai.oki.co.jp> References: <3.0.5.32.19980623080221.00ed3930@sentex.net> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 12:47 PM 7/2/98 +0900, Hideki Yamamoto wrote: > >Hi, > >>>>>> On Tue, 23 Jun 1998 08:02:21 -0400, Mike Tancsa said: > >Mike> Hello from luser land :-) > >Mike> It would be great to see support in stable for > 8GIG IDE drives. I dont >Mike> know how conservative the change would be, but the big fat drives make >Mike> excellent backup devices.... > >Maybe, you are using FAT32 partition as a backup device, aren't you. Sorry, by big fat drives, I meant fat as in large/big/high-in-capacity, not as in the Microsoft File Allocation Table (FAT) ---Mike ********************************************************************** Mike Tancsa (mike@sentex.net) * To do is to be -- Nietzsche Sentex Communications Corp, * To be is to do -- Sartre Cambridge, Ontario * Do be do be do -- Sinatra (http://www.sentex.net/~mdtancsa) * To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Jul 2 00:34:51 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA23378 for freebsd-stable-outgoing; Thu, 2 Jul 1998 00:34:51 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA23373 for ; Thu, 2 Jul 1998 00:34:50 -0700 (PDT) (envelope-from jkh@time.cdrom.com) Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.8/8.8.8) with ESMTP id AAA17148; Thu, 2 Jul 1998 00:34:24 -0700 (PDT) (envelope-from jkh@time.cdrom.com) To: Hideki Yamamoto cc: mike@sentex.net, stable@FreeBSD.ORG Subject: Re: Release schedule for 2.2.7 In-reply-to: Your message of "Thu, 02 Jul 1998 12:47:53 +0900." <199807020347.MAA00011@emerald.carrot.kansai.oki.co.jp> Date: Thu, 02 Jul 1998 00:34:24 -0700 Message-ID: <17143.899364864@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > BTY, would someone tell me what to do to merge my port into -stable brunch? Give me a version which, you feel, meets your criteria for functionlity and has debugging messages and such turned off (if this is going into -stable code, it will be in the production releases to follow) and I'll do my best to merge it. If you can give me your changes as diffs relative to the -stable branch (which you can CVSup locally), that would be even better. > I plan to do the followings in one or two weeks. > When is deadline to merge codes of new functions? It would be good to have them in 15 days or less. > Is my plan too late? Don't I have to do (1)? If you have code which can compile for *both* 2.2-stable and 3.0-current, it might be a good idea to simply make those ifdefs more functional and standard (don't use "FBSDCUR", for example, use __FreeBSD_version from osreldate.h) so that you can have a single set of msdosfs sources which can stay syncronized between the two branches. Thanks! - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Jul 2 04:31:18 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA03085 for freebsd-stable-outgoing; Thu, 2 Jul 1998 04:31:18 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from dpi.dgtu.donetsk.ua (root@dipt-38.4K-dgtu-gw.dgtu.donetsk.ua [194.44.183.221]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA03069 for ; Thu, 2 Jul 1998 04:30:48 -0700 (PDT) (envelope-from yk@info.dgtu.donetsk.ua) Received: from info.dgtu.donetsk.ua (root@info.dgtu.donetsk.ua [194.44.183.7]) by dpi.dgtu.donetsk.ua (8.8.7/8.8.7) with ESMTP id OAA10863 for ; Thu, 2 Jul 1998 14:30:23 +0300 (EET DST) Received: (from yk@localhost) by info.dgtu.donetsk.ua (8.8.7/8.8.5) id OAA03952 for stable@freebsd.org; Thu, 2 Jul 1998 14:30:21 +0300 (EET DST) From: Yury Yaroshevsky Message-Id: <199807021130.OAA03952@info.dgtu.donetsk.ua> Subject: FreBSD 2.2-STABLE & slip - rebooted after up slattach ... To: stable@FreeBSD.ORG Date: Thu, 2 Jul 1998 14:30:21 +0300 (EET DST) 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-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi , I'm running FreeBSD 2.2-STABLE (cvs(over ctm)#4434) and am having problem with slip: Jul 2 12:40:18 cross /kernel: Copyright (c) 1992-1998 FreeBSD Inc. Jul 2 12:40:18 cross /kernel: Copyright (c) 1982, 1986, 1989, 1991, 1993 Jul 2 12:40:18 cross /kernel: The Regents of the University of California. All rights reserved. Jul 2 12:40:19 cross /kernel: Jul 2 12:40:19 cross /kernel: FreeBSD 2.2.6-STABLE #0: Thu Jul 2 12:39:43 EEST 1998 Jul 2 12:40:19 cross /kernel: yk@work.dgtu.donetsk.ua:/usr/src/sys/compile/CROSS Jul 2 12:40:19 cross /kernel: CPU: AMD Am5x86 Write-Back (486-class CPU) Jul 2 12:40:19 cross /kernel: Origin = "AuthenticAMD" Id = 0x4f4 Stepping=4 Jul 2 12:40:19 cross /kernel: Features=0x1 Jul 2 12:40:19 cross /kernel: real memory = 16777216 (16384K bytes) Jul 2 12:40:20 cross /kernel: Probing for devices on PCI bus 0: Jul 2 12:40:20 cross /kernel: chip0 rev 49 on pci0:5:0 Jul 2 12:40:20 cross /kernel: Probing for devices on the ISA bus: Jul 2 12:40:20 cross /kernel: sc0 at 0x60-0x6f irq 1 on motherboard Jul 2 12:40:20 cross /kernel: sc0: VGA color <16 virtual consoles, flags=0x0> Jul 2 12:40:20 cross /kernel: ed0 at 0x340-0x35f irq 5 on isa Jul 2 12:40:20 cross /kernel: ed0: address 00:50:4e:05:90:89, type NE2000 (16 bit) Jul 2 12:40:20 cross /kernel: lpt0 at 0x378-0x37f irq 7 on isa Jul 2 12:40:20 cross /kernel: lpt0: Interrupt-driven port Jul 2 12:40:20 cross /kernel: lp0: TCP/IP capable interface Jul 2 12:40:20 cross /kernel: sio0 at 0x3f8-0x3ff irq 4 on isa Jul 2 12:40:20 cross /kernel: sio0: type 16550A Jul 2 12:40:21 cross /kernel: sio1 at 0x2f8-0x2ff irq 3 on isa Jul 2 12:40:21 cross /kernel: sio1: type 16550A Jul 2 12:40:21 cross /kernel: wdc0 at 0x1f0-0x1f7 irq 14 on isa Jul 2 12:40:21 cross /kernel: wdc0: unit 0 (wd0): Jul 2 12:40:21 cross /kernel: wd0: 610MB (1249920 sectors), 1240 cyls, 16 heads, 63 S/T, 512 B/S Jul 2 12:40:21 cross /kernel: fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa Jul 2 12:40:21 cross /kernel: npx0 on motherboard Jul 2 12:40:21 cross /kernel: npx0: INT 16 interface Jul 2 12:40:21 cross /kernel: ccd0-3: Concatenated disk drivers Jul 2 12:40:21 cross /kernel: IP packet filtering initialized, divert enabled, default to accept, unlimited logging Jul 2 12:41:21 cross login: ROOT LOGIN (root) ON ttyv1 I'm run slattach manually. Jul 2 12:41:41 cross slattach[187]: sl10 connected to /dev//ttyd1 at 57600 baud ifconfig sl10 inet ip1 ip2 After probe ping remote host, my host was rebooted :(((((( without any warning. See below. Also situations repeated for any of kind traffic, going throw this slip interface. Jul 2 12:48:22 cross /kernel: Copyright (c) 1992-1998 FreeBSD Inc. Jul 2 12:48:22 cross /kernel: Copyright (c) 1982, 1986, 1989, 1991, 1993 Jul 2 12:48:22 cross /kernel: The Regents of the University of California. All rights reserved. Jul 2 12:48:22 cross /kernel: Jul 2 12:48:22 cross /kernel: FreeBSD 2.2.6-STABLE #0: Thu Jul 2 12:39:43 EEST 1998 Jul 2 12:48:22 cross /kernel: yk@work.dgtu.donetsk.ua:/usr/src/sys/compile/CROSS Jul 2 12:48:22 cross /kernel: CPU: AMD Am5x86 Write-Back (486-class CPU) Jul 2 12:48:22 cross /kernel: Origin = "AuthenticAMD" Id = 0x4f4 Stepping=4 Jul 2 12:48:22 cross /kernel: Features=0x1 Jul 2 12:48:22 cross /kernel: real memory = 16777216 (16384K bytes) Jul 2 12:48:22 cross /kernel: avail memory = 14856192 (14508K bytes) Jul 2 12:48:22 cross /kernel: Probing for devices on PCI bus 0: Jul 2 12:48:22 cross /kernel: chip0 rev 49 on pci0:5:0 Jul 2 12:48:23 cross /kernel: Probing for devices on the ISA bus: Jul 2 12:48:23 cross /kernel: sc0 at 0x60-0x6f irq 1 on motherboard Jul 2 12:48:23 cross /kernel: sc0: VGA color <16 virtual consoles, flags=0x0> Jul 2 12:48:23 cross /kernel: ed0 at 0x340-0x35f irq 5 on isa Jul 2 12:48:23 cross /kernel: ed0: address 00:50:4e:05:90:89, type NE2000 (16 bit) Jul 2 12:48:23 cross /kernel: lpt0 at 0x378-0x37f irq 7 on isa Jul 2 12:48:23 cross /kernel: lpt0: Interrupt-driven port Jul 2 12:48:23 cross /kernel: lp0: TCP/IP capable interface Jul 2 12:48:23 cross /kernel: sio0 at 0x3f8-0x3ff irq 4 on isa Jul 2 12:48:23 cross /kernel: sio0: type 16550A Jul 2 12:48:23 cross /kernel: sio1 at 0x2f8-0x2ff irq 3 on isa Jul 2 12:48:23 cross /kernel: sio1: type 16550A Jul 2 12:48:23 cross /kernel: wdc0 at 0x1f0-0x1f7 irq 14 on isa Jul 2 12:48:24 cross /kernel: wdc0: unit 0 (wd0): Jul 2 12:48:24 cross /kernel: wd0: 610MB (1249920 sectors), 12 Jul 2 12:48:24 cross /kernel: 40 cyls, 16 heads, 63 S/T, 512 B/S Jul 2 12:48:24 cross /kernel: fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa Jul 2 12:48:24 cross /kernel: npx0 on motherboard Jul 2 12:48:24 cross /kernel: npx0: INT 16 interface Jul 2 12:48:24 cross /kernel: ccd0-3: Concatenated disk drivers Jul 2 12:48:24 cross /kernel: IP packet filtering initialized, divert enabled, default to accept, unlimited logging Jul 2 12:48:24 cross /kernel: WARNING: / was not properly dismounted. ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ Jul 2 12:49:26 cross login: ROOT LOGIN (root) ON ttyv2 Jul 2 13:13:21 cross login: ROOT LOGIN (root) ON ttyv1 This is bug in slattach? Any ideas? PS. I'm probe some version cvs. #4389 - #4434. (20-30 June 1998) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Jul 2 07:13:19 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA28072 for freebsd-stable-outgoing; Thu, 2 Jul 1998 07:13:19 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from mfo00.iij.ad.jp (root@mfo00.iij.ad.jp [202.232.2.117]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA28030 for ; Thu, 2 Jul 1998 07:13:09 -0700 (PDT) (envelope-from kuroda-t@ss.iij4u.or.jp) Received: from ss.iij4u.or.jp (root@ss.iij4u.or.jp [210.130.0.44]) by mfo00.iij.ad.jp (8.8.8/MFO1.1) with ESMTP id XAA29597 for ; Thu, 2 Jul 1998 23:13:08 +0900 (JST) Received: from localhost (h173.p075.iij4u.or.jp [210.130.75.173]) by ss.iij4u.or.jp (8.8.8+2.2IIJ/4U1.1) with ESMTP id XAA13382 for ; Thu, 2 Jul 1998 23:13:07 +0900 (JST) Message-Id: <199807021413.XAA13382@ss.iij4u.or.jp> To: freebsd-stable@FreeBSD.ORG X-Mailer: Mew version 1.92.4 on XEmacs 20.4 (Emerald) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Thu, 02 Jul 1998 23:12:58 +0900 From: Tatsuhiro Kuroda X-Dispatcher: imput version 971024 Lines: 1 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG auth 8280d529 subscribe freebsd-stable kuroda-t@ss.iij4u.or.jp To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Jul 2 07:26:08 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA01033 for freebsd-stable-outgoing; Thu, 2 Jul 1998 07:26:08 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from ns1.yes.no (ns1.yes.no [195.119.24.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA00981 for ; Thu, 2 Jul 1998 07:26:00 -0700 (PDT) (envelope-from eivind@bitbox.follo.net) Received: from bitbox.follo.net (bitbox.follo.net [195.204.143.218]) by ns1.yes.no (8.8.7/8.8.7) with ESMTP id OAA27973; Thu, 2 Jul 1998 14:25:57 GMT Received: (from eivind@localhost) by bitbox.follo.net (8.8.8/8.8.6) id QAA17213; Thu, 2 Jul 1998 16:25:52 +0200 (MET DST) Message-ID: <19980702162552.23041@follo.net> Date: Thu, 2 Jul 1998 16:25:52 +0200 From: Eivind Eklund To: "Jordan K. Hubbard" , Hideki Yamamoto Cc: mike@sentex.net, stable@FreeBSD.ORG Subject: Re: Release schedule for 2.2.7 References: <199807020347.MAA00011@emerald.carrot.kansai.oki.co.jp> <17143.899364864@time.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89.1i In-Reply-To: <17143.899364864@time.cdrom.com>; from Jordan K. Hubbard on Thu, Jul 02, 1998 at 12:34:24AM -0700 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Jul 02, 1998 at 12:34:24AM -0700, Jordan K. Hubbard wrote: > > Is my plan too late? Don't I have to do (1)? > > If you have code which can compile for *both* 2.2-stable and > 3.0-current, it might be a good idea to simply make those ifdefs more > functional and standard (don't use "FBSDCUR", for example, use > __FreeBSD_version from osreldate.h) so that you can have a single set > of msdosfs sources which can stay syncronized between the two > branches. __FreeBSD_version in the kernel should be gotten from . Be aware that this might suddenly decide to enter RELENG_2_2, too ;-) Eivind. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Jul 2 07:42:14 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA03272 for freebsd-stable-outgoing; Thu, 2 Jul 1998 07:42:14 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA03265 for ; Thu, 2 Jul 1998 07:42:12 -0700 (PDT) (envelope-from jkh@time.cdrom.com) Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.8/8.8.8) with ESMTP id HAA20182; Thu, 2 Jul 1998 07:41:37 -0700 (PDT) (envelope-from jkh@time.cdrom.com) To: Eivind Eklund cc: Hideki Yamamoto , mike@sentex.net, stable@FreeBSD.ORG Subject: Re: Release schedule for 2.2.7 In-reply-to: Your message of "Thu, 02 Jul 1998 16:25:52 +0200." <19980702162552.23041@follo.net> Date: Thu, 02 Jul 1998 07:41:37 -0700 Message-ID: <20179.899390497@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > __FreeBSD_version from osreldate.h) so that you can have a single set > > of msdosfs sources which can stay syncronized between the two > > branches. > > __FreeBSD_version in the kernel should be gotten from . Not in 2.2 at this time, which is why I specifically didn't say that. :) - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Jul 2 07:47:35 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA03913 for freebsd-stable-outgoing; Thu, 2 Jul 1998 07:47:35 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from ns1.yes.no (ns1.yes.no [195.119.24.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA03907 for ; Thu, 2 Jul 1998 07:47:33 -0700 (PDT) (envelope-from eivind@bitbox.follo.net) Received: from bitbox.follo.net (bitbox.follo.net [195.204.143.218]) by ns1.yes.no (8.8.7/8.8.7) with ESMTP id OAA28388; Thu, 2 Jul 1998 14:47:26 GMT Received: (from eivind@localhost) by bitbox.follo.net (8.8.8/8.8.6) id QAA17288; Thu, 2 Jul 1998 16:47:25 +0200 (MET DST) Message-ID: <19980702164724.07060@follo.net> Date: Thu, 2 Jul 1998 16:47:24 +0200 From: Eivind Eklund To: "Jordan K. Hubbard" Cc: Hideki Yamamoto , mike@sentex.net, stable@FreeBSD.ORG Subject: Re: Release schedule for 2.2.7 References: <19980702162552.23041@follo.net> <20179.899390497@time.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89.1i In-Reply-To: <20179.899390497@time.cdrom.com>; from Jordan K. Hubbard on Thu, Jul 02, 1998 at 07:41:37AM -0700 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Jul 02, 1998 at 07:41:37AM -0700, Jordan K. Hubbard wrote: > > > __FreeBSD_version from osreldate.h) so that you can have a single set > > > of msdosfs sources which can stay syncronized between the two > > > branches. > > > > __FreeBSD_version in the kernel should be gotten from . > > Not in 2.2 at this time, which is why I specifically didn't say that. :) Simple - if __FreeBSD_version isn't available, it is 2.2 :-) cannot be retrieved from the kernel (I believe it will even fail to compile in some circumstances), so getting it from there isn't an option. Then it would even be better (*shudder*) to rely on __FreeBSD__ (reader, please don't. Use __FreeBSD_version, and assume 2.2 if not available). Eivind. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Jul 2 12:43:18 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA24773 for freebsd-stable-outgoing; Thu, 2 Jul 1998 12:43:18 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from hscmg02.hou.ucarb.com ([144.68.4.25]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA24736 for ; Thu, 2 Jul 1998 12:42:48 -0700 (PDT) (envelope-from NguyenHM@ucarb.com) Received: by hscmg02.hou.ucarb.com with Internet Mail Service (5.0.1458.49) id ; Thu, 2 Jul 1998 14:43:11 -0500 Message-ID: <332F90115D96D0119CD500805FEA976B0178C24F@HSCMS01> From: "Nguyen HM (Mike)" To: freebsd-stable@FreeBSD.ORG Subject: How to make (build)world go faster Date: Thu, 2 Jul 1998 14:41:59 -0500 X-Priority: 3 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.0.1458.49) Content-Type: text/plain Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, I've been reading the mailing lists, and people are claiming they can get make worlds down to around 100 minutes or so. Can anyone give me some hints (besides the /usr/obj and /usr/src on different spindles trick, I only have one disk, but /usr/src is mounted from another system). I haven't been able to go below 4hrs or so. I have a P2/233, Asus P2L97S, 128mb of RAM, and a Seagate ST15150W (original Barracuda). I am running X, but I don't do anything else on the system while the build is going on. Thanks, Mike. // Mike Nguyen // Unix Systems Analyst and Geek // Union Carbide Corporation * (281) 212-8073 // nguyenhm@ucarb.com * mikenguyen@sprintmail.com (personal) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Jul 2 14:24:07 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA11843 for freebsd-stable-outgoing; Thu, 2 Jul 1998 14:24:07 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from rachel.glenatl.glenayre.com (mail.glenatl.glenayre.com [157.230.160.51]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id OAA11781 for ; Thu, 2 Jul 1998 14:24:00 -0700 (PDT) (envelope-from jhicks@glenatl.glenayre.com) Received: from jhicks.glenatl.glenayre.com by rachel.glenatl.glenayre.com (SMI-8.6/SMI-SVR4) id RAA15052; Thu, 2 Jul 1998 17:17:19 -0400 Received: from jhicks.glenatl.glenayre.com (localhost.glenatl.glenayre.com [127.0.0.1]) by jhicks.glenatl.glenayre.com (8.8.8/8.8.5) with ESMTP id RAA08354; Thu, 2 Jul 1998 17:17:18 -0400 (EDT) Message-Id: <199807022117.RAA08354@jhicks.glenatl.glenayre.com> X-Mailer: exmh version 2.0.2 2/24/98 To: "Nguyen HM (Mike)" cc: freebsd-stable@FreeBSD.ORG Subject: Re: How to make (build)world go faster In-reply-to: Your message of "Thu, 02 Jul 1998 14:41:59 CDT." <332F90115D96D0119CD500805FEA976B0178C24F@HSCMS01> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 02 Jul 1998 17:17:18 -0400 From: Jerry Hicks Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG mount your /usr/obj async Good Luck, Jerry Hicks jhicks@glenatl.glenayre.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Jul 2 18:27:29 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA14085 for freebsd-stable-outgoing; Thu, 2 Jul 1998 18:27:29 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from mail.wsg.net (ns1.wsg.net [206.97.122.2]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id SAA14079 for ; Thu, 2 Jul 1998 18:27:27 -0700 (PDT) (envelope-from gilem@wsg.net) Message-Id: <199807030127.SAA14079@hub.freebsd.org> Received: (qmail 22554 invoked by uid 0); 3 Jul 1998 01:33:21 -0000 Received: from mike.wsg.net (HELO tc) (206.97.122.31) by mail.wsg.net with SMTP; 3 Jul 1998 01:33:21 -0000 X-Sender: mikemail@mail.wsg.net X-Mailer: QUALCOMM Windows Eudora Pro Version 4.0.1 Date: Thu, 02 Jul 1998 21:20:10 -0400 To: freebsd-stable@FreeBSD.ORG From: "Michael R. Gile" Subject: 2.2 and SMI conflicts (was: signal 10 errors) In-Reply-To: <199806301611.MAA05306@brain.zeus.leitch.com> References: <19980629184220.15472@supersex.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >This is a new install of freebsd-stable, and it causes these errors >during long builds, namely kernels and big apps. I have tested the >system with all the diags i could find, including Norton and AMI, >which turned up nothing. The strange thing is that this system almost >always exhibits this problem when building a freebsd kernel, but the >stock installation of RedHat 5.1 works fine, built at least 10 kernels >in a row with no errors like this. well, after searching high and low for hardware failures, i found a section in the BIOS for this machine for SMI. This was set to enabled, and had the following individual settings - automatic system reboot - over temperature alarm - ecc scrubbing turning off any of these individually did not get rid of the signal 10 problem. However, disabling the SMI totally makes 2.2-stable run rocksolid. it is now performed almost 400 kernel compiles with not so much as a hiccup. Any comments on this apparent incompatibility? Thanks. ====================================================== Michael Gile gilem@wsg.net President (518)435-0682 Web Services Group http://www.wsg.net/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Jul 2 19:04:34 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA18039 for freebsd-stable-outgoing; Thu, 2 Jul 1998 19:04:34 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from ix.netcom.com (sil-wa3-15.ix.netcom.com [206.214.137.79]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA18021 for ; Thu, 2 Jul 1998 19:04:27 -0700 (PDT) (envelope-from tomdean@ix.netcom.com) Received: (from tomdean@localhost) by ix.netcom.com (8.8.8/8.8.8) id TAA01019; Thu, 2 Jul 1998 19:04:14 -0700 (PDT) (envelope-from tomdean) Date: Thu, 2 Jul 1998 19:04:14 -0700 (PDT) Message-Id: <199807030204.TAA01019@ix.netcom.com> From: Thomas Dean To: NguyenHM@ucarb.com CC: freebsd-stable@FreeBSD.ORG In-reply-to: <332F90115D96D0119CD500805FEA976B0178C24F@HSCMS01> (NguyenHM@ucarb.com) Subject: Re: How to make (build)world go faster Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I suspect the 100 minute builds to be partial builds, not including clean, etc. These 100 minute builds are not from an unmodified Makefile tree, with the command `make world`. I have a Digital Celebris 5133DP, 2 133Mhz Pentiums and 96MB RAM. >From dmesg: ... FreeBSD 3.0-CURRENT #0: Fri Jun 19 09:15:17 PDT 1998 ... Timecounter "i8254" frequency 1193182 Hz cost 2540 ns CPU: Pentium/P54C (586-class CPU) Origin = "GenuineIntel" Id = 0x525 Stepping=5 Features=0x3bf real memory = 100663296 (98304K bytes) avail memory = 95272960 (93040K 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: 0x000f0011, at 0xfec00000 ... sd1 at scbus0 target 1 lun 0 sd1: type 0 fixed SCSI 2 sd1: Direct-Access sd1: 10.0 MB/s (100 ns, offset 8) ... SMP: AP CPU #1 Launched! FreeBSD is on sd1. With the -current cvsup'ed on 6/18 and an unmodified Makefile tree and the command 'make world', I get: ... make world started on Thu Jun 18 20:27:31 PDT 1998 ... make world completed on Fri Jun 19 01:36:06 PDT 1998 ... That is 5 hours. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Jul 2 19:09:31 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA19123 for freebsd-stable-outgoing; Thu, 2 Jul 1998 19:09:31 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from post.mail.demon.net (post-11.mail.demon.net [194.217.242.40]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id TAA19110 for ; Thu, 2 Jul 1998 19:09:26 -0700 (PDT) (envelope-from aw1@titus.stade.co.uk) Received: from (titus.stade.co.uk) [158.152.29.164] by post.mail.demon.net with esmtp (Exim 1.82 #2) id 0yrvHu-0006Q5-00; Fri, 3 Jul 1998 02:09:25 +0000 Received: (from aw1@localhost) by titus.stade.co.uk (8.8.8/8.8.3) id DAA06874; Fri, 3 Jul 1998 03:06:22 +0100 (BST) Message-ID: <19980703030622.A5624@stade.co.uk> Date: Fri, 3 Jul 1998 03:06:22 +0100 From: Adrian Wontroba To: freebsd-stable@FreeBSD.ORG Subject: Re: How to make (build)world go faster Reply-To: aw1@stade.co.uk Mail-Followup-To: freebsd-stable@freebsd.org References: <332F90115D96D0119CD500805FEA976B0178C24F@HSCMS01> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: <332F90115D96D0119CD500805FEA976B0178C24F@HSCMS01>; from Nguyen HM (Mike) on Thu, Jul 02, 1998 at 02:41:59PM -0500 Organization: Stade Computers Ltd, UK X-Phone: +(44) 121 681 6677 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Jul 02, 1998 at 02:41:59PM -0500, Nguyen HM (Mike) wrote: > get make worlds down to around 100 minutes or so. Can anyone give me > trick Does /etc/make.conf have CFLAGS= -O -pipe enabled or commented out? This can make quite a difference. A memory based /tmp is an alternative. Put option MFS in your kernel configuration, and mount /tmp thus: Extract from /etc/fstab # Device Mountpoint FStype Options Dump Pass# /dev/sd0s2e /usr ufs rw 1 1 ............ /dev/sd0s2b /tmp mfs rw 0 0 -- Adrian Wontroba, Stade Computers Limited. phone: (+44) 121 681 6677 Mail info@accu.org for information about the Association of C and C++ Users or see To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Jul 2 21:09:09 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA06722 for freebsd-stable-outgoing; Thu, 2 Jul 1998 21:09:09 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from antipodes.cdrom.com (castles185.castles.com [208.214.165.185]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA06669 for ; Thu, 2 Jul 1998 21:09:00 -0700 (PDT) (envelope-from mike@antipodes.cdrom.com) Received: from antipodes.cdrom.com (localhost [127.0.0.1]) by antipodes.cdrom.com (8.8.8/8.8.5) with ESMTP id VAA03744; Thu, 2 Jul 1998 21:09:36 -0700 (PDT) Message-Id: <199807030409.VAA03744@antipodes.cdrom.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: "Michael R. Gile" cc: freebsd-stable@FreeBSD.ORG Subject: Re: 2.2 and SMI conflicts (was: signal 10 errors) In-reply-to: Your message of "Thu, 02 Jul 1998 21:20:10 EDT." <199807030127.SAA14079@hub.freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 02 Jul 1998 21:09:35 -0700 From: Mike Smith Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > >This is a new install of freebsd-stable, and it causes these errors > >during long builds, namely kernels and big apps. I have tested the > >system with all the diags i could find, including Norton and AMI, > >which turned up nothing. The strange thing is that this system almost > >always exhibits this problem when building a freebsd kernel, but the > >stock installation of RedHat 5.1 works fine, built at least 10 kernels > >in a row with no errors like this. > > well, after searching high and low for hardware failures, i found a section > in the BIOS for this machine for SMI. This was set to enabled, and had the > following individual settings > > - automatic system reboot > - over temperature alarm > - ecc scrubbing > > turning off any of these individually did not get rid of the signal 10 problem. > > However, disabling the SMI totally makes 2.2-stable run rocksolid. it is now > performed almost 400 kernel compiles with not so much as a hiccup. Any comments > on this apparent incompatibility? Only that it looks like the SMI handler is doing something wierd or otherwise broken that upsets the system. If you can pursue BIOS upgrades, or possibly talk to the manufacturer about it, you might get some results. (Maybe tell them that NT falls over with it on... 8) -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Jul 2 23:12:01 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA21090 for freebsd-stable-outgoing; Thu, 2 Jul 1998 23:12:01 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from rachel.glenatl.glenayre.com (mail.glenatl.glenayre.com [157.230.160.51]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id XAA21061 for ; Thu, 2 Jul 1998 23:11:55 -0700 (PDT) (envelope-from jhicks@glenatl.glenayre.com) Received: from jhicks.glenatl.glenayre.com by rachel.glenatl.glenayre.com (SMI-8.6/SMI-SVR4) id CAA15667; Fri, 3 Jul 1998 02:03:40 -0400 Received: (from jhicks@localhost) by jhicks.glenatl.glenayre.com (8.8.8/8.8.5) id CAA09136; Fri, 3 Jul 1998 02:03:38 -0400 (EDT) Date: Fri, 3 Jul 1998 02:03:38 -0400 (EDT) From: Jerry Hicks Message-Id: <199807030603.CAA09136@jhicks.glenatl.glenayre.com> To: NguyenHM@ucarb.com, tomdean@ix.netcom.com Subject: Re: How to make (build)world go faster Cc: freebsd-stable@FreeBSD.ORG In-Reply-To: <199807030204.TAA01019@ix.netcom.com> Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Ouch... That's r e a l s l o w. My home system (200Mhz Pentium) finishes in just a couple of hours. Cheers, J. Hicks To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Jul 2 23:58:31 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA26961 for freebsd-stable-outgoing; Thu, 2 Jul 1998 23:58:31 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from ix.netcom.com (sil-wa4-33.ix.netcom.com [207.93.136.97]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA26954 for ; Thu, 2 Jul 1998 23:58:27 -0700 (PDT) (envelope-from tomdean@ix.netcom.com) Received: (from tomdean@localhost) by ix.netcom.com (8.8.8/8.8.8) id XAA00611; Thu, 2 Jul 1998 23:58:21 -0700 (PDT) (envelope-from tomdean) Date: Thu, 2 Jul 1998 23:58:21 -0700 (PDT) Message-Id: <199807030658.XAA00611@ix.netcom.com> From: Thomas Dean To: jhicks@glenatl.glenayre.com CC: NguyenHM@ucarb.com, freebsd-stable@FreeBSD.ORG In-reply-to: <199807030603.CAA09136@jhicks.glenatl.glenayre.com> (message from Jerry Hicks on Fri, 3 Jul 1998 02:03:38 -0400 (EDT)) Subject: Re: How to make (build)world go faster Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Have you modified any of the makefiles or /etc/make.conf or /usr/share/mk/*? I have not modified any of these files. Do you keep the output of make in a file? If so, please send me the output of grep -i ^mak I use a domake.sh script to run make and keep a log. #!/bin/sh make -j4 world > `date "+%y%m%d.make.out"` 2>&1 My /etc/make.conf is # $Id: make.conf,v 1.37.2.4 1997/04/15 08:26:19 asami Exp $ My /usr/src/Makefile is # $Id: Makefile,v 1.203 1998/06/17 09:34:42 bde Exp $ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Jul 3 00:44:56 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA04197 for freebsd-stable-outgoing; Fri, 3 Jul 1998 00:44:56 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from dpi.dgtu.donetsk.ua (root@dipt-38.4K-dgtu-gw.dgtu.donetsk.ua [194.44.183.221]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA04161 for ; Fri, 3 Jul 1998 00:44:43 -0700 (PDT) (envelope-from yk@info.dgtu.donetsk.ua) Received: from info.dgtu.donetsk.ua (root@info.dgtu.donetsk.ua [194.44.183.7]) by dpi.dgtu.donetsk.ua (8.8.7/8.8.7) with ESMTP id KAA16232 for ; Fri, 3 Jul 1998 10:44:33 +0300 (EET DST) Received: (from yk@localhost) by info.dgtu.donetsk.ua (8.8.7/8.8.5) id KAA29544 for freebsd-stable@freeBSD.org; Fri, 3 Jul 1998 10:44:31 +0300 (EET DST) From: Yury Yaroshevsky Message-Id: <199807030744.KAA29544@info.dgtu.donetsk.ua> Subject: Troubles with slattach in 2.2.6-STABLE ... To: freebsd-stable@FreeBSD.ORG Date: Fri, 3 Jul 1998 10:44:31 +0300 (EET DST) 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-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi , I'm running FreeBSD 2.2-STABLE (cvs(over ctm)#4434) and am having problem with slip: Jul 2 12:40:18 cross /kernel: Copyright (c) 1992-1998 FreeBSD Inc. Jul 2 12:40:18 cross /kernel: Copyright (c) 1982, 1986, 1989, 1991, 1993 Jul 2 12:40:18 cross /kernel: The Regents of the University of California. All rights reserved. Jul 2 12:40:19 cross /kernel: Jul 2 12:40:19 cross /kernel: FreeBSD 2.2.6-STABLE #0: Thu Jul 2 12:39:43 EEST 1998 Jul 2 12:40:19 cross /kernel: yk@work.dgtu.donetsk.ua:/usr/src/sys/compile/CROSS Jul 2 12:40:19 cross /kernel: CPU: AMD Am5x86 Write-Back (486-class CPU) Jul 2 12:40:19 cross /kernel: Origin = "AuthenticAMD" Id = 0x4f4 Stepping=4 Jul 2 12:40:19 cross /kernel: Features=0x1 Jul 2 12:40:19 cross /kernel: real memory = 16777216 (16384K bytes) Jul 2 12:40:20 cross /kernel: Probing for devices on PCI bus 0: Jul 2 12:40:20 cross /kernel: chip0 rev 49 on pci0:5:0 Jul 2 12:40:20 cross /kernel: Probing for devices on the ISA bus: Jul 2 12:40:20 cross /kernel: sc0 at 0x60-0x6f irq 1 on motherboard Jul 2 12:40:20 cross /kernel: sc0: VGA color <16 virtual consoles, flags=0x0> Jul 2 12:40:20 cross /kernel: ed0 at 0x340-0x35f irq 5 on isa Jul 2 12:40:20 cross /kernel: ed0: address 00:50:4e:05:90:89, type NE2000 (16 bit) Jul 2 12:40:20 cross /kernel: lpt0 at 0x378-0x37f irq 7 on isa Jul 2 12:40:20 cross /kernel: lpt0: Interrupt-driven port Jul 2 12:40:20 cross /kernel: lp0: TCP/IP capable interface Jul 2 12:40:20 cross /kernel: sio0 at 0x3f8-0x3ff irq 4 on isa Jul 2 12:40:20 cross /kernel: sio0: type 16550A Jul 2 12:40:21 cross /kernel: sio1 at 0x2f8-0x2ff irq 3 on isa Jul 2 12:40:21 cross /kernel: sio1: type 16550A Jul 2 12:40:21 cross /kernel: wdc0 at 0x1f0-0x1f7 irq 14 on isa Jul 2 12:40:21 cross /kernel: wdc0: unit 0 (wd0): Jul 2 12:40:21 cross /kernel: wd0: 610MB (1249920 sectors), 1240 cyls, 16 heads, 63 S/T, 512 B/S Jul 2 12:40:21 cross /kernel: fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa Jul 2 12:40:21 cross /kernel: npx0 on motherboard Jul 2 12:40:21 cross /kernel: npx0: INT 16 interface Jul 2 12:40:21 cross /kernel: ccd0-3: Concatenated disk drivers Jul 2 12:40:21 cross /kernel: IP packet filtering initialized, divert enabled, default to accept, unlimited logging Jul 2 12:41:21 cross login: ROOT LOGIN (root) ON ttyv1 Leased line is up by SRM Patton 1004. I'm run slattach manually. /sbin/slattach -c -l -S 10 -s 57600 ttyd1 Jul 2 12:41:41 cross slattach[187]: sl10 connected to /dev//ttyd1 at 57600 baud ifconfig sl10 inet ip1 ip2 If I trying to send any TCP or UDP packets, my host was rebooted :(((((( without any warning. But pinging remote host perform successfully. Jul 2 12:48:22 cross /kernel: Copyright (c) 1992-1998 FreeBSD Inc. Jul 2 12:48:22 cross /kernel: Copyright (c) 1982, 1986, 1989, 1991, 1993 Jul 2 12:48:22 cross /kernel: The Regents of the University of California. All rights reserved. Jul 2 12:48:22 cross /kernel: Jul 2 12:48:22 cross /kernel: FreeBSD 2.2.6-STABLE #0: Thu Jul 2 12:39:43 EEST 1998 Jul 2 12:48:22 cross /kernel: yk@work.dgtu.donetsk.ua:/usr/src/sys/compile/CROSS Jul 2 12:48:22 cross /kernel: CPU: AMD Am5x86 Write-Back (486-class CPU) Jul 2 12:48:22 cross /kernel: Origin = "AuthenticAMD" Id = 0x4f4 Stepping=4 Jul 2 12:48:22 cross /kernel: Features=0x1 Jul 2 12:48:22 cross /kernel: real memory = 16777216 (16384K bytes) Jul 2 12:48:22 cross /kernel: avail memory = 14856192 (14508K bytes) Jul 2 12:48:22 cross /kernel: Probing for devices on PCI bus 0: Jul 2 12:48:22 cross /kernel: chip0 rev 49 on pci0:5:0 Jul 2 12:48:23 cross /kernel: Probing for devices on the ISA bus: Jul 2 12:48:23 cross /kernel: sc0 at 0x60-0x6f irq 1 on motherboard Jul 2 12:48:23 cross /kernel: sc0: VGA color <16 virtual consoles, flags=0x0> Jul 2 12:48:23 cross /kernel: ed0 at 0x340-0x35f irq 5 on isa Jul 2 12:48:23 cross /kernel: ed0: address 00:50:4e:05:90:89, type NE2000 (16 bit) Jul 2 12:48:23 cross /kernel: lpt0 at 0x378-0x37f irq 7 on isa Jul 2 12:48:23 cross /kernel: lpt0: Interrupt-driven port Jul 2 12:48:23 cross /kernel: lp0: TCP/IP capable interface Jul 2 12:48:23 cross /kernel: sio0 at 0x3f8-0x3ff irq 4 on isa Jul 2 12:48:23 cross /kernel: sio0: type 16550A Jul 2 12:48:23 cross /kernel: sio1 at 0x2f8-0x2ff irq 3 on isa Jul 2 12:48:23 cross /kernel: sio1: type 16550A Jul 2 12:48:23 cross /kernel: wdc0 at 0x1f0-0x1f7 irq 14 on isa Jul 2 12:48:24 cross /kernel: wdc0: unit 0 (wd0): Jul 2 12:48:24 cross /kernel: wd0: 610MB (1249920 sectors), 12 Jul 2 12:48:24 cross /kernel: 40 cyls, 16 heads, 63 S/T, 512 B/S Jul 2 12:48:24 cross /kernel: fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa Jul 2 12:48:24 cross /kernel: npx0 on motherboard Jul 2 12:48:24 cross /kernel: npx0: INT 16 interface Jul 2 12:48:24 cross /kernel: ccd0-3: Concatenated disk drivers Jul 2 12:48:24 cross /kernel: IP packet filtering initialized, divert enabled, default to accept, unlimited logging Jul 2 12:48:24 cross /kernel: WARNING: / was not properly dismounted. ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ Jul 2 12:49:26 cross login: ROOT LOGIN (root) ON ttyv2 Jul 2 13:13:21 cross login: ROOT LOGIN (root) ON ttyv1 This is bug in slattach? Any ideas? PS. I'm probe some version cvs. #4389 - #4434. (20-30 June 1998) PPS. After experiments I discovered that : I have 16 slip interfaces in kernel. So, if I try up slattach on sl0 - this work. But if I try up slattach on any other slip interfaces - situation described above repeated. See my config of kernel: machine "i386" ident CROSS maxusers 30 options INCLUDE_CONFIG_FILE # Include this file in kernel config kernel root on wd0 ##################################################################### # CPU OPTIONS cpu "I486_CPU" cpu "I586_CPU" # aka Pentium(tm) ##################################################################### # COMPATIBILITY OPTIONS options "COMPAT_43" options SYSVSHM options SYSVSEM options SYSVMSG options "MD5" ##################################################################### # DEBUGGING OPTIONS #options DDB #options DDB_UNATTENDED #options KTRACE #kernel tracing #options DIAGNOSTIC #options PERFMON #options UCONSOLE options USERCONFIG #boot -c editor options VISUAL_USERCONFIG #visual boot -c editor ##################################################################### # NETWORKING OPTIONS options INET #Internet communications protocols pseudo-device ether #Generic Ethernet pseudo-device loop #Network loopback device pseudo-device sl 16 #Serial Line IP #pseudo-device ppp 2 #Point-to-point protocol pseudo-device bpfilter 4 #Berkeley packet filter pseudo-device disc #Discard device pseudo-device tun 1 #Tunnel driver(user process ppp) options IPFIREWALL #firewall options IPFIREWALL_VERBOSE #print information about # dropped packets options IPFIREWALL_DEFAULT_TO_ACCEPT #allow everything by default options IPDIVERT #divert sockets ##################################################################### # FILESYSTEM OPTIONS options FFS #Fast filesystem options "CD9660" #ISO 9660 filesystem options KERNFS #Kernel filesystem options MSDOSFS #MS DOS filesystem options PROCFS #Process filesystem ##################################################################### # SCSI DEVICES ##################################################################### # MISCELLANEOUS DEVICES AND OPTIONS pseudo-device pty 20 #Pseudo ttys - can go as high as 256 #pseudo-device vcfs 4 #coda minicache <-> venus comm. #pseudo-device speaker #Play IBM BASIC-style noises out your speaker pseudo-device log #Kernel syslog interface (/dev/klog) pseudo-device gzip #Exec gzipped a.out's pseudo-device vn #Vnode driver (turns a file into a device) pseudo-device snp 3 #Snoop device - to look at pty/vty/etc.. pseudo-device ccd 4 #Concatenated disk driver # Size of the kernel message buffer. Should be N * pagesize. options "MSGBUF_SIZE=40960" ##################################################################### # HARDWARE DEVICE CONFIGURATION controller isa0 options "AUTO_EOI_1" #controller pnp0 device sc0 at isa? port "IO_KBD" tty irq 1 vector scintr options MAXCONS=16 # number of virtual consoles device npx0 at isa? port "IO_NPX" iosiz 0x0 flags 0x0 irq 13 vector npxintr controller wdc0 at isa? port "IO_WD1" bio irq 14 vector wdintr disk wd0 at wdc0 drive 0 disk wd1 at wdc0 drive 1 #options ATAPI #Enable ATAPI support for IDE bus #options ATAPI_STATIC #Don't do it as an LKM #device wcd0 controller fdc0 at isa? port "IO_FD1" bio irq 6 drq 2 vector fdintr disk fd0 at fdc0 drive 0 device lpt0 at isa? port? tty irq 7 vector lptintr device sio0 at isa? port "IO_COM1" tty irq 4 vector siointr device sio1 at isa? port "IO_COM2" tty irq 3 vector siointr device ed0 at isa? port 0x320 net irq 10 iomem 0xd8000 vector edintr #controller snd0 #device sb0 at isa? port 0x220 irq 5 drq 1 vector sbintr #device mpu0 at isa? port 0x330 irq 10 drq 0 #device pca0 at isa? port IO_TIMER1 tty #options APM_IDLE_CPU # Tell APM to idle rather than halt'ing the cpu #device apm0 at isa? #options APM_BROKEN_STATCLOCK controller pci0 #options COMPAT_LINUX #options DEBUG #options "EXT2FS" #options "IBCS2" Any of ideas? This is problems with options "-S" ? How I can resolve this task? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Jul 3 05:09:28 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA18297 for freebsd-stable-outgoing; Fri, 3 Jul 1998 05:09:28 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from mrelay.jrc.it (mrelay.jrc.it [139.191.1.65]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA18265; Fri, 3 Jul 1998 05:09:19 -0700 (PDT) (envelope-from nick.hibma@jrc.it) Received: from elect8 (elect8.jrc.it [139.191.71.152]) by mrelay.jrc.it (LMC5688) with SMTP id OAA00078; Fri, 3 Jul 1998 14:09:16 +0200 (MET DST) Date: Fri, 3 Jul 1998 14:02:02 +0200 (MET DST) From: Nick Hibma X-Sender: n_hibma@elect8 Reply-To: Nick Hibma To: chat@FreeBSD.ORG, current@FreeBSD.ORG, stable@FreeBSD.ORG, newbies@FreeBSD.ORG, questions@FreeBSD.ORG Subject: PKGINFO statistics Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In short, it would be appreciated if you could execute the command below on your FreeBSD box. It is harmless. /usr/sbin/pkg_info -aI | \ /usr/bin/mail -s "PKGINFO `hostname`" \ nick.hibma@jrc.it (this command should be all on one line, like: /usr/bin/pkg_info -aI | mail -s "PKGINFO `hostname`" nick.hibma@jrc.it The `hostname` in the subject is there to be able to filter out duplicates but is not required at all, in case you want to send it anonymously. It sends me a list of all the packages you have installed on the machine you execute the command on. Reason to do this: In a discussion the idea came up to see if profiles for the usage of packages could be found. If a large number of these pkg_info lists are retrieved we can try to find relations between each two installed packages. This could be used to offer predefined profiles to the user when installing packages. This avoids the user to having to wade through the entire list of packages when deciding what to install. The directory structure present in the /usr/ports directory already provides a means to do this but this could be improved upon. See for a more elaborate discussion the message below. Thanks for your help and my apologies for the cross posting. Please note that I am not subscribed to any of the mailing lists (except hackers) and any flames should be sent to my personal address only. I will collect all the flames and post a digest. :-) Nick Hibma ======== >From nick.hibma@jrc.it Fri Jul 3 13:34:37 1998 Date: Wed, 17 Jun 1998 19:01:14 +0200 (MET DST) From: Nick Hibma To: Garance A Drosihn Cc: FreeBSD hackers mailing list Subject: Re: 2.2.6 CD-ROM : Package dependencies up the creek ? > > That is true, but the idea of profiles and a more copious choice of > > what you might want to install is not a bad idea either I think. > > I think it is a "slippery slope", as each of us has a different > collection of packages which we feel are important for machines > once we have them setup as a production service. If we start down > this path, we will probably end up just reorganizing the ports list, > whereas what I'm hoping for is a very short list of packages which > are displayed during the initial install time. Let's separate between two different issues. One, the more important and urgent one: your point of creating a list of packages which should be optional but most probably necessary on a newly installed system. You mention bash as an example, perl5 is another one. Add a tick box in one of the installation menus and add the packages to the CD and you are done. The more room on the CD the more packages you can add to that list if you like. The idea of profiles is the other one and as you say, it is a slippery slope. Most people install the operating system for the first time to try and if they have the feeling that they are being coached through the process and been given choices that they can easily understand, they'll probably have a better feeling about what is happening to them. Profiles you can see as different views on the database of packages available. You can already see this if you look at the way the packages are structured now. The point is that you can select a number of profiles that suite you. They might overlap, for example web, mail and software development, but you have a preselection of packages which should fullfill most your intended uses. Enhancing the profiles with relations makes it even more sexy. For example, installing MSQL on a development system that also has perl installed could trigger the adding perl5-msql. Having selected X and ghostscript makes it invitable to install ghostview as well. An idea is to collect a lot of pkg_info -aI lists and see if you can use statistics to guess what someone might want to install as well. Taking into account the available disk space and using the statistical analysis to rank the automatically added packages would keep the thing from installing too many things. REQUEST: I hereby post a request for pkg_info -aI listings of FBSD machines. Please add in the subject PKGINFO. That makes the message more of an object that _just_knows_ which mail folder to go to. The following should do: pkg_info -aI | mail -s "PKGINFO `hostname`" nick.hibma@jrc.it should do the trick. And, someone has said this (I cannot remember his name), there should be a step in between the installation of the base system (O sys and basic functionality /usr/bin and packages) and the installation of the packages through selection/profiles/whatever. In contrast to MicroDollar there is a difference between the operating system and the user interface. A remark about the fact that the operating system and base functionality (including the item above, the packages on CD 1) has been completely installed and that he now can continue with the installation of added functionality if he wishes to do so, should be added. To avoid the problem Garance had when installing FreeBSD (supposedly nuking his fresh installation during the installation of XFree) maybe some consolidation stage should be added (reboot) after dumping a README on what to do next to the screen/to more. Shouldn't we force a reboot to make sure we run off a decent medium (common guys, one reboot is not the end of the world! :-) Is it at all possible to install XFree at that stage, because of the lack of swap and RO /usr partition? > I would expect most shells will be on this "short list". As part of the > install process the user going to be asked to create some personal ID's, Account creation is a good one as well for the initial setup phase. At least you can log in as user root with a password or as someone else. It makes it feel more like home instead of a black hole. > shell I "need". Obviously I can get by using other shells, but it > only takes about five minutes before I start missing shell features > which I'm pretty used to. The cursor jumping all over the place when pressing tab, very annoying, yes. :-) Someone who has the CD1 handy should tell us how much space is left there before we embark on listing all our favourite toys. Nick Hibma To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Jul 3 07:02:38 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA02709 for freebsd-stable-outgoing; Fri, 3 Jul 1998 07:02:38 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from kosh.cococo.net (kosh.cococo.net [208.134.89.131]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA02703 for ; Fri, 3 Jul 1998 07:02:35 -0700 (PDT) (envelope-from kosh@kosh.cococo.net) Received: from localhost (kosh@localhost) by kosh.cococo.net (8.8.7/8.8.7) with SMTP id KAA07628; Fri, 3 Jul 1998 10:03:05 -0400 Date: Fri, 3 Jul 1998 10:03:05 -0400 (EDT) From: "Kelley L." Reply-To: "Kelley L." To: "Nguyen HM (Mike)" cc: freebsd-stable@FreeBSD.ORG Subject: Re: How to make (build)world go faster In-Reply-To: <332F90115D96D0119CD500805FEA976B0178C24F@HSCMS01> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 2 Jul 1998, Nguyen HM (Mike) wrote: > Hi, > > I've been reading the mailing lists, and people are claiming they can > get make worlds down to around 100 minutes or so. Can anyone give me > some hints (besides the /usr/obj and /usr/src on different spindles > trick, I only have one disk, but /usr/src is mounted from another I suspect /usr/src mounted from another system is your problem. > system). I haven't been able to go below 4hrs or so. I have a P2/233, > Asus P2L97S, 128mb of RAM, and a Seagate ST15150W (original Barracuda). > I am running X, but I don't do anything else on the system while the > build is going on. > I'm running a fairly similar setup, Acer MotherBoard w/BX chipset, 128Mb Ram, P2/266, UDMA IDE Drive(only the one). I do have in the /etc/make.conf CFLAGS= -O -pipe options enabled. make buildworld took 99 minutes, just last night. If I get a chance, I will try it with the noatime and async mount options and see what I can get, but I can't believe that the difference between a PII/233 and PII/266 can be that significant. later Kelley To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Jul 3 09:11:15 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA16566 for freebsd-stable-outgoing; Fri, 3 Jul 1998 09:11:15 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from atreju.lan.attic.ch (oensingen-gate1-09.solnet.ch [194.235.47.104]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA16557 for ; Fri, 3 Jul 1998 09:11:06 -0700 (PDT) (envelope-from blapp@attic.ch) Received: from attic.ch (furchur.lan.attic.ch [192.168.0.1]) by atreju.lan.attic.ch (8.8.8/8.8.8) with ESMTP id RAA24512 for ; Fri, 3 Jul 1998 17:21:41 GMT (envelope-from blapp@attic.ch) Message-ID: <359D025C.D9BE4B31@attic.ch> Date: Fri, 03 Jul 1998 18:10:05 +0200 From: Martin Blapp Reply-To: blapp@attic.ch Organization: Attic Internet Services X-Mailer: Mozilla 4.05 [en] (WinNT; U) MIME-Version: 1.0 To: "freebsd-stable@FreeBSD.ORG" Subject: PPPd with option 'active-filter' Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello I use at home natd in connection with pppd. To use dial on demand, I made a custom kernel with these options : pseudo-device bpfilter 16 # Berkeley packet filter options IPFIREWALL #Firewall options IPDIVERT #Natd options PPP_FILTER #enable bpf filtering (needs bpfilter) options PPP_BSDCOMP #PPP BSD-compress support options PPP_DEFLATE #PPP zlib/deflate/gzip support All's working great, with one exeption. pppd refuses to know the option "active-filter". So I tried to recompile pppd with the option -DPPP_FILTER. But I got an error after depend and make: [/usr/src/usr.sbin/pppd] make -DPPP_FILTER cc -O -DHAVE_PATHS_H -DPPP_FILTER -c /usr/src/usr.sbin/pppd/main.c cc -O -DHAVE_PATHS_H -DPPP_FILTER -c /usr/src/usr.sbin/pppd/magic.c cc -O -DHAVE_PATHS_H -DPPP_FILTER -c /usr/src/usr.sbin/pppd/fsm.c cc -O -DHAVE_PATHS_H -DPPP_FILTER -c /usr/src/usr.sbin/pppd/lcp.c cc -O -DHAVE_PATHS_H -DPPP_FILTER -c /usr/src/usr.sbin/pppd/ipcp.c cc -O -DHAVE_PATHS_H -DPPP_FILTER -c /usr/src/usr.sbin/pppd/ipxcp.c cc -O -DHAVE_PATHS_H -DPPP_FILTER -c /usr/src/usr.sbin/pppd/upap.c cc -O -DHAVE_PATHS_H -DPPP_FILTER -c /usr/src/usr.sbin/pppd/chap.c cc -O -DHAVE_PATHS_H -DPPP_FILTER -c /usr/src/usr.sbin/pppd/ccp.c cc -O -DHAVE_PATHS_H -DPPP_FILTER -c /usr/src/usr.sbin/pppd/demand.c cc -O -DHAVE_PATHS_H -DPPP_FILTER -c /usr/src/usr.sbin/pppd/auth.c cc -O -DHAVE_PATHS_H -DPPP_FILTER -c /usr/src/usr.sbin/pppd/options.c cc -O -DHAVE_PATHS_H -DPPP_FILTER -c /usr/src/usr.sbin/pppd/sys-bsd.c cc -O -DHAVE_PATHS_H -DPPP_FILTER -o pppd main.o magic.o fsm.o lcp.o ipcp.o i pxcp.o upap.o chap.o ccp.o demand.o auth.o options.o sys-bsd.o -lcrypt -lutil - lmd demand.o: Undefined symbol `_bpf_filter' referenced from text segment options.o: Undefined symbol `_pcap_compile' referenced from text segment options.o: Undefined symbol `_pcap_geterr' referenced from text segment options.o: Undefined symbol `_pcap_compile' referenced from text segment options.o: Undefined symbol `_pcap_geterr' referenced from text segment *** Error code 1 Stop. [/usr/src/usr.sbin/pppd] What made I wrong ? Why isn't "PPP_FILTER" a default option in pppd ? I thing if i make cvsup and a make buildworld, I have also to recompile pppd. Are I'm right ? Is active-filter in pppd working fore somebody. Can you give me a hint :) ? Thanks for your answer. Martin. -- ------------------------------------------------------------------------ Martin Blapp, (blapp@attic.ch) Attic Internet Services, Bechburgstrasse 8, 4702 Oensingen, Switzerland Phone: +41 62 396 43 70, Fax: +41 62 396 43 72 PGP fingerprint: 4E96 1AE8 4AA6 AB40 1AD6 DB42 7623 995D 522A 1D38 ------------------------------------------------------------------------ Public key available at: http://www.attic.ch/pgp-public.html To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Jul 3 10:00:17 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA21915 for freebsd-stable-outgoing; Fri, 3 Jul 1998 10:00:17 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from kosh.cococo.net (kosh.cococo.net [208.134.89.131]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA21847 for ; Fri, 3 Jul 1998 10:00:09 -0700 (PDT) (envelope-from kosh@kosh.cococo.net) Received: from localhost (kosh@localhost) by kosh.cococo.net (8.8.7/8.8.7) with SMTP id NAA07987; Fri, 3 Jul 1998 13:00:39 -0400 Date: Fri, 3 Jul 1998 13:00:39 -0400 (EDT) From: "Kelley L." To: "Nguyen HM (Mike)" cc: freebsd-stable@FreeBSD.ORG Subject: Re: How to make (build)world go faster In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 3 Jul 1998, Kelley L. wrote: > > > On Thu, 2 Jul 1998, Nguyen HM (Mike) wrote: > > > Hi, > > > > I've been reading the mailing lists, and people are claiming they can > > get make worlds down to around 100 minutes or so. Can anyone give me > > some hints (besides the /usr/obj and /usr/src on different spindles > > trick, I only have one disk, but /usr/src is mounted from another > > I suspect /usr/src mounted from another system is your problem. > > > > system). I haven't been able to go below 4hrs or so. I have a P2/233, > > Asus P2L97S, 128mb of RAM, and a Seagate ST15150W (original Barracuda). > > I am running X, but I don't do anything else on the system while the > > build is going on. > > > > I'm running a fairly similar setup, Acer MotherBoard w/BX chipset, 128Mb > Ram, P2/266, UDMA IDE Drive(only the one). I do have in the /etc/make.conf > CFLAGS= -O -pipe > > options enabled. make buildworld took 99 minutes, just last night. > > If I get a chance, I will try it with the noatime and async mount options > and see what I can get, but I can't believe that the difference between a > PII/233 and PII/266 can be that significant. > Just following up on this post, I cheated to get this speed, I have the bus speed set to 83.3 MHz, and the PII is actually running at 333 MHz. I did have a time for buildworld at 266 MHz and a 66 MHz Bus, it was 2 hours and 35 minutes with, the -O -pipe options enabled in make.conf. I just did a make buildworld at the 83.3 MHz Bus Speed, and the PII running at 333 MHz, the time for buildworld, with noatime and async mount options was 68 minutes, installworld was 5 min 16 seconds, a kernel make was 2 min 23 seconds. I only have a regular /usr partition. later Kelley To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Jul 3 10:58:45 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA29085 for freebsd-stable-outgoing; Fri, 3 Jul 1998 10:58:45 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from tim.xenologics.com (tim.xenologics.com [194.77.5.24]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA29075 for ; Fri, 3 Jul 1998 10:58:42 -0700 (PDT) (envelope-from seggers@semyam.dinoco.de) Received: (from uucp@localhost) by tim.xenologics.com (8.8.5/8.8.8) with UUCP id TAA23118; Fri, 3 Jul 1998 19:57:19 +0200 (MET DST) Received: from localhost (localhost [127.0.0.1]) by semyam.dinoco.de (8.8.8/8.8.8) with ESMTP id LAA07606; Fri, 3 Jul 1998 11:02:43 +0200 (CEST) (envelope-from seggers@semyam.dinoco.de) Message-Id: <199807030902.LAA07606@semyam.dinoco.de> Cc: "Nguyen HM (Mike)" , seggers@semyam.dinoco.de Subject: Re: How to make (build)world go faster In-reply-to: Your message of "Thu, 02 Jul 1998 14:41:59 CDT." <332F90115D96D0119CD500805FEA976B0178C24F@HSCMS01> To: freebsd-stable@FreeBSD.ORG Date: Fri, 03 Jul 1998 11:02:41 +0200 From: Stefan Eggers Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > trick, I only have one disk, but /usr/src is mounted from another > system). I haven't been able to go below 4hrs or so. I have a P2/233, > Asus P2L97S, 128mb of RAM, and a Seagate ST15150W (original Barracuda). My P100 ASUS board with only 48 MByte RAM and some Seagate IDE hard- disk takes about 5 hours with src and obj on the same disk. I didn't exactly time it. Just noted I start it at about tea time and it's finished at about 9 o'clock in the evening. I put the compiler options "-O -pipe" into /etc/make.conf (as someone else noted on the list) due to reading it on the make world WWW pages. Nothing else changed for performance. The next thing I'll try is using an async filesystem with mount option noatime for obj now that I have room for that on a new harddisk. I'd expect a system with much faster processor, more memory and faster harddisk to be far better than mine. Maybe the remote /usr/src is slowing it a bit down, too. It might be worth to try it with local /usr/src and see if that is faster. For a first impression buildworld till a certain point in the process and comparing the performance will do. > I am running X, but I don't do anything else on the system while the > build is going on. I just do a buildworld with the processes so nice that they just eats up idle time and do some work meanwhile. Nothing which uses much CPU for long periods, though. Stefan. -- Stefan Eggers Lu4 yao2 zhi1 ma3 li4, Max-Slevogt-Str. 1 ri4 jiu3 jian4 ren2 xin1. 51109 Koeln Federal Republic of Germany To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Jul 3 11:59:49 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA06197 for freebsd-stable-outgoing; Fri, 3 Jul 1998 11:59:49 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from ix.netcom.com (sil-wa4-33.ix.netcom.com [207.93.136.97]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA06192 for ; Fri, 3 Jul 1998 11:59:47 -0700 (PDT) (envelope-from tomdean@ix.netcom.com) Received: (from tomdean@localhost) by ix.netcom.com (8.8.8/8.8.8) id LAA02776; Fri, 3 Jul 1998 11:59:37 -0700 (PDT) (envelope-from tomdean) Date: Fri, 3 Jul 1998 11:59:37 -0700 (PDT) Message-Id: <199807031859.LAA02776@ix.netcom.com> From: Thomas Dean To: kosh@kosh.cococo.net CC: NguyenHM@ucarb.com, freebsd-stable@FreeBSD.ORG In-reply-to: Subject: Re: How to make (build)world go faster Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Make buildworld time does not compare directly with make world times. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Jul 3 12:59:46 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA11569 for freebsd-stable-outgoing; Fri, 3 Jul 1998 12:59:46 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from fvt.com (usr44-dialup38.mix1.Sacramento.mci.net [166.55.13.230]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id MAA11564 for ; Fri, 3 Jul 1998 12:59:44 -0700 (PDT) (envelope-from dcooper@fvt.com) Received: from pell [192.168.1.2] by fvt.com [192.168.1.2] with SMTP (MDaemon.v2.7.SP3.R) for ; Fri, 03 Jul 1998 12:52:27 -0700 Message-ID: <001301bda6bc$1b208360$0201a8c0@pell.fvt.com> From: "Dan Cooper" To: "FreeBSD-Stable" Subject: Questions on the subject buildworld subject Date: Fri, 3 Jul 1998 12:52:27 -0700 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.72.3110.5 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3 X-MDaemon-Deliver-To: freebsd-stable@FreeBSD.ORG Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I have been building/installing the world for the first time, updating 2.2.6 release to 2.2-stable, following the directions in the tutorial by Nik Clayton (http://www.nothing-going-on.demon.uk/make-world/make-work.html) , and I have a couple of questions. The tutorial mentions that you can use '-jx' as an option with the -current source to allow make to spawn 'x' simultaneous processes (-j4 was recommended for single CPU machines) to speed up the build. Can you do this with 2.2-stable and does it speed up the build significantly? Also, the post install step discusses updating the configuration files in /etc, /usr, and /var. The tutorial recommends creating a dummy directory, installing the new /etc and other files, and then going through and comparing each new file with its old counterpart to see if there are any changes. My question: is there an easier way of doing this? Is there a list of important revisions to configuration files somewhere? I'm still poking my way through each file trying to judge what is important or not. Thanks, Dan Cooper dcooper@fvt.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Jul 3 13:47:16 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA15865 for freebsd-stable-outgoing; Fri, 3 Jul 1998 13:47:16 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from pop.uniserve.com (pop.uniserve.com [204.244.156.3]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id NAA15842 for ; Fri, 3 Jul 1998 13:47:09 -0700 (PDT) (envelope-from tom@uniserve.com) Received: from shell.uniserve.ca [204.244.186.218] by pop.uniserve.com with smtp (Exim 1.82 #4) id 0ysCjW-00043U-00; Fri, 3 Jul 1998 13:47:02 -0700 Date: Fri, 3 Jul 1998 13:47:00 -0700 (PDT) From: Tom X-Sender: tom@shell.uniserve.ca To: Dan Cooper cc: FreeBSD-Stable Subject: Re: Questions on the subject buildworld subject In-Reply-To: <001301bda6bc$1b208360$0201a8c0@pell.fvt.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 3 Jul 1998, Dan Cooper wrote: > The tutorial mentions that you can use '-jx' as an option with the -current > source to allow make to spawn 'x' simultaneous processes (-j4 was > recommended for single CPU machines) to speed up the build. Can you do this > with 2.2-stable and does it speed up the build significantly? "-jX" is not too staff on stable because the makefiles haven't been updated. > Also, the post install step discusses updating the configuration files in > /etc, /usr, and /var. The tutorial recommends creating a dummy directory, > installing the new /etc and other files, and then going through and > comparing each new file with its old counterpart to see if there are any > changes. My question: is there an easier way of doing this? Is there a > list of important revisions to configuration files somewhere? I'm still > poking my way through each file trying to judge what is important or not. I'd just ignore this step. Updating /etc is not important, unless there are specific compatibility changes required (like the /etc/fstab change sometime ago). So don't update /etc/ unless you know of some reason why you need to. I've got some 2.2-stable machines running with /etc from 2.2-RELEASE (the old /etc/sysconfig stuff). > Thanks, > > Dan Cooper > dcooper@fvt.com Tom To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Jul 3 13:54:34 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA17050 for freebsd-stable-outgoing; Fri, 3 Jul 1998 13:54:34 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from ix.netcom.com (sil-wa4-33.ix.netcom.com [207.93.136.97]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA17030 for ; Fri, 3 Jul 1998 13:54:25 -0700 (PDT) (envelope-from tomdean@ix.netcom.com) Received: (from tomdean@localhost) by ix.netcom.com (8.8.8/8.8.8) id NAA02996; Fri, 3 Jul 1998 13:54:11 -0700 (PDT) (envelope-from tomdean) Date: Fri, 3 Jul 1998 13:54:11 -0700 (PDT) Message-Id: <199807032054.NAA02996@ix.netcom.com> From: Thomas Dean To: dcooper@fvt.com CC: freebsd-stable@FreeBSD.ORG In-reply-to: <001301bda6bc$1b208360$0201a8c0@pell.fvt.com> (dcooper@fvt.com) Subject: Re: Questions on the subject buildworld subject Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG If you have /etc and /etc.old. Then, do a diff on each pair of files to see the changes. See 'man diff' I created a directory /etc.old and used tar to copy the files from /etc into /etc/old. For example, 'diff /etc/file1 /etc.old/file1' will show the changes necessary to chamge /etc/file into /etc.old/file1. Create a couple of small files with minor differences, like a spelling on line 1 and a missing line 3. Then run diff and see the output. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Jul 3 15:56:30 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA28170 for freebsd-stable-outgoing; Fri, 3 Jul 1998 15:56:30 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from atreju.lan.attic.ch (oensingen-gate1-04.solnet.ch [194.235.47.99]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA28160 for ; Fri, 3 Jul 1998 15:56:25 -0700 (PDT) (envelope-from blapp@attic.ch) Received: from attic.ch (blapp@furchur.lan.attic.ch [192.168.0.1]) by atreju.lan.attic.ch (8.8.8/8.8.8) with ESMTP id AAA02104 for ; Sat, 4 Jul 1998 00:06:52 GMT (envelope-from blapp@attic.ch) Message-ID: <359D6154.33CDB90F@attic.ch> Date: Sat, 04 Jul 1998 00:55:16 +0200 From: Martin Blapp Reply-To: blapp@attic.ch Organization: Attic Internet Services X-Mailer: Mozilla 4.05 [en] (WinNT; U) MIME-Version: 1.0 To: "freebsd-stable@FreeBSD.ORG" Subject: Re: PPPd with option 'active-filter' References: <359D025C.D9BE4B31@attic.ch> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I got it working myself. But I have no idea why it compiled suddently. :)Natd works, but there I have also a little problem: Does anybode know how to prevent the first packet to be destroyed when pppd opens the connection ? Martin -- ------------------------------------------------------------------------ Martin Blapp, (blapp@attic.ch) Attic Internet Services, Bechburgstrasse 8, 4702 Oensingen, Switzerland Phone: +41 62 396 43 70, Fax: +41 62 396 43 72 PGP fingerprint: 4E96 1AE8 4AA6 AB40 1AD6 DB42 7623 995D 522A 1D38 ------------------------------------------------------------------------ Public key available at: http://www.attic.ch/pgp-public.html To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Jul 4 06:02:22 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA28523 for freebsd-stable-outgoing; Sat, 4 Jul 1998 06:02:22 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from ns.totalware.gifu.gifu.jp (ns.totalware.gifu.gifu.jp [210.154.78.26]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA28503 for ; Sat, 4 Jul 1998 06:02:11 -0700 (PDT) (envelope-from hayashi@totalware.gifu.gifu.jp) Received: from [192.168.47.69] (mira.totalware.gifu.gifu.jp [192.168.47.69]) by ns.totalware.gifu.gifu.jp (8.8.8/3.6W) with ESMTP id WAA05882 for ; Sat, 4 Jul 1998 22:02:08 +0900 (JST) Message-Id: <199807041302.WAA05882@ns.totalware.gifu.gifu.jp> X-Sender: hayashi@deneb.totalware.gifu.gifu.jp X-Mailer: Macintosh Eudora Pro Version 3.1.1-Jr2 Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Sat, 4 Jul 1998 22:02:06 +0900 To: stable@FreeBSD.ORG From: Akihiko Hayashi Subject: ftp via 2.2-stable natd Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I am using 2.2-stable natd machine. >From about Jul.1, 2.2-stable natd can't process ftp. /usr/src/sys/netinet/* is backed to 98062?, and rebuild kernel, this problem is not appeared. Test machines: tx0 100BaseTX de0 ed0 10Base +-----------------+ +---------- router ... internet | | | 2.2-stable98062? 2.2-stable98070x client0 nat0 At machine client0 ftp get internet internet ftp hosts file size is about 500KB ftp program says, "Connection reset by peer" "421 Service not available, remote server has close connection" At machine nat0 kernel options: IPFIREWALL IPDIVERT /etc/rc.conf: firewall_enable="YES" gateway_enable="YES" natd command: natd -interface ed0 ipfw command: ipfw -f flush ipfw add divert natd all from any to any via ed0 ipfw add pass all from any to any ---- hayashi@totalware.gifu.gifu.jp To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Jul 4 06:48:48 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA02324 for freebsd-stable-outgoing; Sat, 4 Jul 1998 06:48:48 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from emerald.carrot.kansai.oki.co.jp (okigate.oki.co.jp [202.226.91.194]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA02319 for ; Sat, 4 Jul 1998 06:48:45 -0700 (PDT) (envelope-from hyama@emerald.carrot.kansai.oki.co.jp) Received: from localhost (localhost [127.0.0.1]) by emerald.carrot.kansai.oki.co.jp (8.8.6/3.3W-94070111) with ESMTP id WAA18723; Sat, 4 Jul 1998 22:48:24 +0900 (JST) Message-Id: <199807041348.WAA18723@emerald.carrot.kansai.oki.co.jp> To: eivind@yes.no Cc: jkh@time.cdrom.com, mike@sentex.net, stable@FreeBSD.ORG Subject: Re: Release schedule for 2.2.7 From: Hideki Yamamoto In-Reply-To: Your message of "Thu, 2 Jul 1998 16:47:24 +0200" References: <19980702164724.07060@follo.net> X-Mailer: Mew version 1.70 on Emacs 19.28.1 / Mule 2.3 Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Sat, 04 Jul 1998 22:48:23 +0900 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, Thank you for your good ideas and tips. > Not in 2.2 at this time, which is why I specifically didn't say that. :) Eivind> Simple - if __FreeBSD_version isn't available, it is 2.2 :-) Eivind> cannot be retrieved from the kernel (I believe it will Eivind> even fail to compile in some circumstances), so getting it from there Eivind> isn't an option. Then it would even be better (*shudder*) to rely on Eivind> __FreeBSD__ (reader, please don't. Use __FreeBSD_version, and assume Eivind> 2.2 if not available). I have a question. Is the technique available both kernel module and the others? I have ported msdosfs module in kernel and mount_msdos command in sbin/i386. In mount_msdos source code, I think we can add the following code to distinguish between two branches. --------------- #include #if __FreeBSD_version > 300000 printf(" This code is for -current branche\n"); #else printf(" This code is for -stable branche\n"); #endif --------------- My disk is so small (400M for FreeBSD, 800M for Win95), that I cannot have the whole -current environment. After finishing this porting, I will buy a fat disk. :-) ~~~ Thanks in advance. ---------------------------------- Hideki Yamamoto (hyama@acm.org) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Jul 4 08:55:09 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA11912 for freebsd-stable-outgoing; Sat, 4 Jul 1998 08:55:09 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from amor.wcs.uq.edu.au (amor.wcs.uq.edu.au [130.102.222.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA11907 for ; Sat, 4 Jul 1998 08:55:05 -0700 (PDT) (envelope-from garyr@amor.wcs.uq.edu.au) Received: (from garyr@localhost) by amor.wcs.uq.edu.au (8.8.8/8.8.8) id BAA02923; Sun, 5 Jul 1998 01:54:06 +1000 (EST) (envelope-from garyr) From: Gary Roberts Message-Id: <199807041554.BAA02923@amor.wcs.uq.edu.au> Subject: Re: Questions on the subject buildworld subject In-Reply-To: from Tom at "Jul 3, 98 01:47:00 pm" To: tom@uniserve.com (Tom) Date: Sun, 5 Jul 1998 01:54:06 +1000 (EST) Cc: dcooper@fvt.com, freebsd-stable@FreeBSD.ORG Organisation: Well Control Australia Phone: +617 3844 0400 Fax: +617 3844 0444 Reply-To: garyr@wcs.uq.edu.au (Gary Roberts) X-Mailer: ELM [version 2.4ME+ PL38 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Tom writes :- > On Fri, 3 Jul 1998, Dan Cooper wrote: > > > I have been building/installing the world for the first time, updating 2.2.6 > > release to 2.2-stable, following the directions in the tutorial by Nik > > Clayton (http://www.nothing-going-on.demon.uk/make-world/make-work.html) , > > and I have a couple of questions. In case others are trying to check out that URL, the correct value is:- http://www.nothing-going-on.demon.co.uk/FreeBSD/make-world/make-world.html ^^ ^^ Since there is other interesting info there you might like to use http://www.nothing-going-on.demon.co.uk/FreeBSD/index.html and follow the links. > > Also, the post install step discusses updating the configuration files in > > /etc, /usr, and /var. The tutorial recommends creating a dummy directory, > > installing the new /etc and other files, and then going through and > > comparing each new file with its old counterpart to see if there are any > > changes. My question: is there an easier way of doing this? Is there a > > list of important revisions to configuration files somewhere? I'm still > > poking my way through each file trying to judge what is important or not. > > I'd just ignore this step. Updating /etc is not important, unless there > are specific compatibility changes required (like the /etc/fstab change > sometime ago). So don't update /etc/ unless you know of some reason why > you need to. I've got some 2.2-stable machines running with /etc from > 2.2-RELEASE (the old /etc/sysconfig stuff). Of course the counter point is that as time goes by you get more and more out of sync with what the mainstream is doing. Rather than ignoring the changes, why not back up your current /etc (just the bits you have customised really) and do a recursive diff on the old and the new and merge your customisations into the new. Its a bit of a pain when you have left it for a while but it's a good self-teaching exercise on how everything works :-). I thought that the tutorial covered all the options rather well and gave sensible suggestions to ease the pain. Cheers, -- Gary Roberts (garyr@wcs.uq.edu.au) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Jul 4 09:07:20 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA13046 for freebsd-stable-outgoing; Sat, 4 Jul 1998 09:07:20 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from ns1.yes.no (ns1.yes.no [195.119.24.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA13022 for ; Sat, 4 Jul 1998 09:07:08 -0700 (PDT) (envelope-from eivind@bitbox.follo.net) Received: from bitbox.follo.net (bitbox.follo.net [195.204.143.218]) by ns1.yes.no (8.8.7/8.8.7) with ESMTP id QAA01340; Sat, 4 Jul 1998 16:06:59 GMT Received: (from eivind@localhost) by bitbox.follo.net (8.8.8/8.8.6) id SAA03739; Sat, 4 Jul 1998 18:06:57 +0200 (MET DST) Message-ID: <19980704180656.03205@follo.net> Date: Sat, 4 Jul 1998 18:06:56 +0200 From: Eivind Eklund To: Hideki Yamamoto Cc: jkh@time.cdrom.com, mike@sentex.net, stable@FreeBSD.ORG Subject: Re: Release schedule for 2.2.7 References: <19980702164724.07060@follo.net> <199807041348.WAA18723@emerald.carrot.kansai.oki.co.jp> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89.1i In-Reply-To: <199807041348.WAA18723@emerald.carrot.kansai.oki.co.jp>; from Hideki Yamamoto on Sat, Jul 04, 1998 at 10:48:23PM +0900 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, Jul 04, 1998 at 10:48:23PM +0900, Hideki Yamamoto wrote: > > Hi, > > Thank you for your good ideas and tips. > > > Not in 2.2 at this time, which is why I specifically didn't say that. :) > > Eivind> Simple - if __FreeBSD_version isn't available, it is 2.2 :-) > > Eivind> cannot be retrieved from the kernel (I believe it will > Eivind> even fail to compile in some circumstances), so getting it from there > Eivind> isn't an option. Then it would even be better (*shudder*) to rely on > Eivind> __FreeBSD__ (reader, please don't. Use __FreeBSD_version, and assume > Eivind> 2.2 if not available). > > I have a question. Is the technique available both kernel module > and the others? Yes. > I have ported msdosfs module in kernel and > mount_msdos command in sbin/i386. > > In mount_msdos source code, I think we can add the following > code to distinguish between two branches. > > --------------- > #include > > #if __FreeBSD_version > 300000 > printf(" This code is for -current branche\n"); > #else > printf(" This code is for -stable branche\n"); > #endif > --------------- This is correct. If you want to do this in the kernel, just replace with Eivind. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Jul 4 18:06:35 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA03012 for freebsd-stable-outgoing; Sat, 4 Jul 1998 18:06:35 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from socko.cdnow.com (socko.cdnow.com [209.83.166.75]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA03007 for ; Sat, 4 Jul 1998 18:06:33 -0700 (PDT) (envelope-from heller@daria.cdnow.com) Received: from daria.cdnow.com (daria.cdnow.com [209.83.166.60]) by socko.cdnow.com (8.9.0/8.9.0) with ESMTP id VAA18767 for ; Sat, 4 Jul 1998 21:06:30 -0400 (EDT) Received: (from heller@localhost) by daria.cdnow.com (8.8.8/8.8.8) id VAA28584 for freebsd-stable@freebsd.org; Sat, 4 Jul 1998 21:05:00 -0400 (EDT) From: "A. Karl Heller" Message-Id: <199807050105.VAA28584@daria.cdnow.com> Subject: July 2nd SNAP question. To: freebsd-stable@FreeBSD.ORG Date: Sat, 4 Jul 1998 21:05:00 -0400 (EDT) Reply-To: heller@cdnow.com X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I recently upgraded two 9707 snap machines. Can anyone explain to me what I did wrong that causes the system to startup with the wrong hostname? This code from rc.network displays "Doing initial network setup: hostname" network_pass1() { echo -n 'Doing initial network setup:' # Set the host name if it is not already set if [ -z "`hostname -s`" ] ; then hostname $hostname echo -n ' hostname' fi I can't seem to figure out what is causing it to return that when $hostname IS set. Anybody else see this or just me? Also, who do I talk to about making some changes to the sysinstall program? For example, doing an upgrade it is possible to want to re-select the packages you want to install. However, you are always forced to the partition program if you already picked an install package and then exited out to the main menu to start over. Also, during this procedure, as soon as you pick your packages you are put back to the initial package screen without the package number you selected highlighted. I ran in a loop here not knowing when to stop. I assumed it would remember my settings, exited the menu, and then the installation continued. Just little things here and there. One last thing, does anyone have any helpfull tools for those of us who upgrade? I might start writing some of my own to merge /etc/upgrade in to the system, etc.. Karl PS. When do the current ports get upgraded? I was very surprised to see the ports on the July 2nd SNAP had the new version of qpopper...this is automated isn't it? if not... congrats on a great job. -- A. Karl Heller - Senior Systems Engineer - heller@cdnow.com ----------------------------------------------------------------------------- An unbreakable toy is useful for breaking other toys. Do something unusual today. Accomplish work on the computer. >>>>> HTTP://CDNOW.COM - BIGGEST FASTEST BEST <<<<< To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message