From owner-freebsd-stable Sun Oct 18 08:38:15 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA25785 for freebsd-stable-outgoing; Sun, 18 Oct 1998 08:38:15 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from lariat.lariat.org (lariat.lariat.org [206.100.185.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA25780; Sun, 18 Oct 1998 08:38:12 -0700 (PDT) (envelope-from brett@lariat.org) Received: (from brett@localhost) by lariat.lariat.org (8.8.8/8.8.6) id JAA13113; Sun, 18 Oct 1998 09:37:48 -0600 (MDT) Message-Id: <4.1.19981018093136.040d3390@mail.lariat.org> X-Sender: brett@mail.lariat.org X-Mailer: QUALCOMM Windows Eudora Pro Version 4.1 Date: Sun, 18 Oct 1998 09:32:30 -0600 To: "H. Eckert" , freebsd-stable@FreeBSD.ORG, security@FreeBSD.ORG From: Brett Glass Subject: Re: syslogd and syslog.conf In-Reply-To: <19981017095905.23337@nostromo.in-berlin.de> References: <3626320A.712D129F@internationalschool.co.uk> <199810151535.KAA09617@alecto.physics.uiuc.edu> <3626320A.712D129F@internationalschool.co.uk> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 09:59 AM 10/17/98 +0200, H. Eckert wrote: >Ee does that ? One more reason to hate it. >The first thing I do on a new installation is edit root's >dotfiles to change the editor to vim or at least vi. It >would be nice if sysconfig would copy the default editor >from the config options page if it had been changed during >the installation. I'd really like it to bring in jove. Yes, I can use vi if I must, but the command structure is so awful that I have to go very slowly.... --Brett To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Oct 18 09:24:31 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA07369 for freebsd-stable-outgoing; Sun, 18 Oct 1998 09:24:31 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from pollux.sdata.de (pollux.sdata.de [193.30.133.37]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA07349 for ; Sun, 18 Oct 1998 09:24:25 -0700 (PDT) (envelope-from chris@pollux.sdata.de) Received: (from chris@localhost) by pollux.sdata.de (8.8.7/8.8.5) id SAA24886 for freebsd-stable@FreeBSD.ORG; Sun, 18 Oct 1998 18:23:58 +0200 (MET DST) From: Christoph Splittgerber Message-Id: <199810181623.SAA24886@pollux.sdata.de> Subject: NGROUPS To: freebsd-stable@FreeBSD.ORG Date: Sun, 18 Oct 1998 18:23:58 +0200 (MET DST) Reply-to: cs@pollux.sdata.de X-Mailer: ELM [version 2.4ME+ PL22 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, first of all, I apologies if this is not the correct mailing list to ask this. We are using a 2.2.7stable with a user/group scheme where every user is assigned to her own group with a default umask of 007. For all the different projects we create an extra group and assign all users which need to work on the project to that group. This works perfectly, however with this scheme it is very likely that you hit the NGROUPS maximum which is at just "16". What problems should I expect when I increase NGROUPS_MAX to, lets say, "64" in /usr/src/sys/sys/param.h ? Is this the right place to change the limit ? Do I only have to recompile a new kernel or do I need a "make world" ? Wouldn't NGROUPS_MAX be a good candidate for the kernel config file ? Thanks in advance, and again sorry if this is not the right mailing list, Christoph -- *** Perfection is achieved only at the point of collapse.- C.N.Parkinson *** ---------------------------------------------------------------------------- Email: chris@sdata.de PGP Key fingerprint: FE0899542E27761E57C4C8F3C6188F56 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Oct 18 20:38:09 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA09893 for freebsd-stable-outgoing; Sun, 18 Oct 1998 20:38:09 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from mail.giga-mount.takatsu.kawasaki.jp (dns.giga-mount.takatsu.kawasaki.jp [210.160.89.146]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA09885 for ; Sun, 18 Oct 1998 20:38:06 -0700 (PDT) (envelope-from Kenji.Gotoh@giga-mount.takatsu.kawasaki.jp) Received: from nss1200 (ppp16021.telecom.alles.or.jp [203.139.97.213]) by mail.giga-mount.takatsu.kawasaki.jp (8.8.7+2.7Wbeta7/3.6Wbeta7+GIGA-MOUNT-LOCAL[97/10/15 10:54]) with SMTP id MAA29111; Mon, 19 Oct 1998 12:37:34 +0900 (JST) Message-Id: <199810190337.MAA29111@mail.giga-mount.takatsu.kawasaki.jp> Date: Mon, 19 Oct 1998 12:40:53 +0900 From: Kenji Gotoh To: freebsd-stable@FreeBSD.ORG MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Mailer: Becky! ver 1.24.13 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG subscribe freebsd-stable end To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Oct 18 22:18:26 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA19148 for freebsd-stable-outgoing; Sun, 18 Oct 1998 22:18:26 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from bart.zip.com.au (bart.zip.com.au [61.8.6.5]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA19131 for ; Sun, 18 Oct 1998 22:18:21 -0700 (PDT) (envelope-from bart@bart.zip.com.au) Received: (from bart@localhost) by bart.zip.com.au (8.8.8/8.8.8) id PAA01615; Mon, 19 Oct 1998 15:18:01 +1000 (EST) (envelope-from bart) Date: Mon, 19 Oct 1998 15:18:01 +1000 (EST) Message-Id: <199810190518.PAA01615@bart.zip.com.au> From: Bart Lindsey To: cs@pollux.sdata.de CC: freebsd-stable@FreeBSD.ORG In-reply-to: <199810181623.SAA24886@pollux.sdata.de> (message from Christoph Splittgerber on Sun, 18 Oct 1998 18:23:58 +0200 (MET DST)) Subject: Re: NGROUPS References: <199810181623.SAA24886@pollux.sdata.de> Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Christoph Splittgerber e-toned: > ... >We are using a 2.2.7stable with a user/group scheme where every user is >assigned to her own group with a default umask of 007. For all >the different projects we create an extra group and assign all users which >need to work on the project to that group. This works perfectly, however >with this scheme it is very likely that you hit the NGROUPS maximum which >is at just "16". > >What problems should I expect when I increase NGROUPS_MAX to, lets say, "64" >in /usr/src/sys/sys/param.h ? Is this the right place to change the limit ? >Do I only have to recompile a new kernel or do I need a "make world" ? The NGROUPS_MAX constant is often passed as an argument to getgroups to specifiy the size of the returned group access list. It's used in lots of progs from id, chown, etc to sendmail and pppd. "make world" would be the least you'd have to do. Other apps, eg in the ports collection may use this too. :-/ >Wouldn't NGROUPS_MAX be a good candidate for the kernel config file ? No, because of above. It's a system wide constant. You cannot change kern.ngroups using sysctl either. This makes you wonder why it was set so low in the first place. In most situations though, 16 is a reasonable number. An alternative (which probably doesn't meet all your needs) is to use the features of your source repository (like Commitinfo file in CVS) to restrict "commit" operations to authorised users. Cheers, Bart. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Oct 19 01:30:33 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA05213 for freebsd-stable-outgoing; Mon, 19 Oct 1998 01:30:33 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from phmit.demon.co.uk (phmit.demon.co.uk [194.222.15.209]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id BAA05208 for ; Mon, 19 Oct 1998 01:30:31 -0700 (PDT) (envelope-from dom@phmit.demon.co.uk) Received: from voodoo.pandhm.co.uk [10.100.35.12] by phmit.demon.co.uk with esmtp (Exim 1.82 #1) id 0zVAhj-00003L-00; Mon, 19 Oct 1998 09:30:15 +0100 Received: from dom by voodoo.pandhm.co.uk with local (Exim 1.92 #1) id 0zVAhA-00014G-00; Mon, 19 Oct 1998 09:29:40 +0100 To: Vince Vielhaber cc: Ted Spradley , freebsd-stable@FreeBSD.ORG, "H.Eckert" Subject: Re: syslogd and syslog.conf X-Mailer: nmh v0.26 X-Colour: Green Organization: Palmer & Harvey McLane In-reply-to: Vince Vielhaber's message of "Sat, 17 Oct 1998 15:48:18 EDT" Date: Mon, 19 Oct 1998 09:29:40 +0100 From: Dom Mitchell Message-Id: Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 17 October 1998, Vince Vielhaber proclaimed: > Why would you want to use "MeSs-Word" on syslog.conf? Don't start me. I know more than one Unix admin that downloads various text based config files into wordpad on his PC rather than use vi. -- Dom Mitchell -- Palmer & Harvey McLane -- Unix Systems Administrator "Xerox studies suggest that most people print out electronic mail that is longer than half a page; paper use rises by 40 percent in offices that introduce E-mail." -- CCM To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Oct 19 01:38:51 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA06325 for freebsd-stable-outgoing; Mon, 19 Oct 1998 01:38:51 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from amsoft.ru (amsoft.ru [194.87.86.241]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA06316 for ; Mon, 19 Oct 1998 01:38:41 -0700 (PDT) (envelope-from am@amsoft.ru) Received: (from am@localhost) by amsoft.ru (8.8.8/amsoft/1.0) id MAA01535 for freebsd-stable@freebsd.org; Mon, 19 Oct 1998 12:36:57 +0400 (MSD) From: Andrew Maltsev Message-Id: <199810190836.MAA01535@amsoft.ru> Subject: -stable to 3.0 transition To: freebsd-stable@FreeBSD.ORG Date: Mon, 19 Oct 1998 12:36:57 +0400 (MSD) Organization: AM'soft X-Location: Oryol (http://www.oryol.ru/), Russia X-Phone: +7 086 229 9988 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 What are possible caveats of transition from 2.2-stable system to 3.0? Will usual `make world' do the thing? Btw, will 3.0-stable branch be forked? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Oct 19 01:51:18 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA07489 for freebsd-stable-outgoing; Mon, 19 Oct 1998 01:51:18 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from time.cdrom.com (time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA07480 for ; Mon, 19 Oct 1998 01:51:17 -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 BAA03720; Mon, 19 Oct 1998 01:50:26 -0700 (PDT) (envelope-from jkh@time.cdrom.com) To: Andrew Maltsev cc: freebsd-stable@FreeBSD.ORG Subject: Re: -stable to 3.0 transition In-reply-to: Your message of "Mon, 19 Oct 1998 12:36:57 +0400." <199810190836.MAA01535@amsoft.ru> Date: Mon, 19 Oct 1998 01:50:25 -0700 Message-ID: <3716.908787025@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > What are possible caveats of transition from 2.2-stable system to > 3.0? Will usual `make world' do the thing? It should, yes. > Btw, will 3.0-stable branch be forked? After some of the dust finishes settling and 3.0 is more worthy of the title. Maybe January. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Oct 19 02:09:49 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA09161 for freebsd-stable-outgoing; Mon, 19 Oct 1998 02:09:49 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from pollux.sdata.de (pollux.sdata.de [193.30.133.37]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA09154 for ; Mon, 19 Oct 1998 02:09:40 -0700 (PDT) (envelope-from chris@pollux.sdata.de) Received: (from chris@localhost) by pollux.sdata.de (8.8.7/8.8.5) id LAA26834 for freebsd-stable@FreeBSD.ORG; Mon, 19 Oct 1998 11:09:16 +0200 (MET DST) From: Christoph Splittgerber Message-Id: <199810190909.LAA26834@pollux.sdata.de> Subject: Re: syslogd and syslog.conf To: freebsd-stable@FreeBSD.ORG Date: Mon, 19 Oct 1998 11:09:16 +0200 (MET DST) In-Reply-To: from Dom Mitchell at "Oct 19, 98 09:29:40 am" Reply-to: cs@pollux.sdata.de X-Mailer: ELM [version 2.4ME+ PL22 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > On 17 October 1998, Vince Vielhaber proclaimed: > > Why would you want to use "MeSs-Word" on syslog.conf? > > Don't start me. I know more than one Unix admin that downloads various > text based config files into wordpad on his PC rather than use vi. Whatever you call a "Unix admin" Christoph -- *** Perfection is achieved only at the point of collapse.- C.N.Parkinson *** ---------------------------------------------------------------------------- Email: chris@sdata.de PGP Key fingerprint: FE0899542E27761E57C4C8F3C6188F56 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Oct 19 02:10:36 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA09337 for freebsd-stable-outgoing; Mon, 19 Oct 1998 02:10:36 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from phmit.demon.co.uk (phmit.demon.co.uk [194.222.15.209]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id CAA09325 for ; Mon, 19 Oct 1998 02:10:26 -0700 (PDT) (envelope-from dom@phmit.demon.co.uk) Received: from voodoo.pandhm.co.uk [10.100.35.12] by phmit.demon.co.uk with esmtp (Exim 1.82 #1) id 0zVBKE-00005e-00; Mon, 19 Oct 1998 10:10:02 +0100 Received: from dom by voodoo.pandhm.co.uk with local (Exim 1.92 #1) id 0zVBJd-0002Fq-00; Mon, 19 Oct 1998 10:09:25 +0100 To: "Jordan K. Hubbard" cc: Andrew Maltsev , freebsd-stable@FreeBSD.ORG Subject: Re: -stable to 3.0 transition X-Mailer: nmh v0.26 X-Colour: Green Organization: Palmer & Harvey McLane In-reply-to: "Jordan K. Hubbard"'s message of "Mon, 19 Oct 1998 01:50:25 PDT" <3716.908787025@time.cdrom.com> Date: Mon, 19 Oct 1998 10:09:25 +0100 From: Dom Mitchell Message-Id: Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 19 October 1998, "Jordan K. Hubbard" proclaimed: > > What are possible caveats of transition from 2.2-stable system to > > 3.0? Will usual `make world' do the thing? > > It should, yes. How long will a.out builds be supported for? I assume that it's preferable to use "make aout_to_elf" to upgrade rather than a pure "make world"... -- Dom Mitchell -- Palmer & Harvey McLane -- Unix Systems Administrator "Xerox studies suggest that most people print out electronic mail that is longer than half a page; paper use rises by 40 percent in offices that introduce E-mail." -- CCM To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Oct 19 05:46:57 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA00940 for freebsd-stable-outgoing; Mon, 19 Oct 1998 05:46:57 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from news-ma.rhein-neckar.de (news-ma.rhein-neckar.de [193.197.90.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA00860 for ; Mon, 19 Oct 1998 05:45:33 -0700 (PDT) (envelope-from naddy@mips.rhein-neckar.de) Received: from mips.rhein-neckar.de (uucp@localhost) by news-ma.rhein-neckar.de (8.8.8/8.8.8) with bsmtp id OAA01269 for freebsd-stable@freebsd.org; Mon, 19 Oct 1998 14:45:06 +0200 (CEST) (envelope-from naddy@mips.rhein-neckar.de) Received: by mips.rhein-neckar.de id m0zVEcP-000WyOC (Debian Smail-3.2.0.101 1997-Dec-17 #2); Mon, 19 Oct 1998 14:41:01 +0200 (CEST) Message-Id: Date: Mon, 19 Oct 1998 14:41:01 +0200 (CEST) From: naddy@mips.rhein-neckar.de (Christian Weisgerber) To: freebsd-stable@FreeBSD.ORG Subject: Re: -stable to 3.0 transition In-Reply-To: <199810190836.MAA01535@amsoft.ru> Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article <199810190836.MAA01535@amsoft.ru> Andrew Maltsev wrote: > What are possible caveats of transition from 2.2-stable system to > 3.0? Will usual `make world' do the thing? This weekend I migrated my machine from 2.2-STABLE (last updated early September) to 3.0-CURRENT. 1. Get the 3.0 source. I threw away the 2.2 one and cvsup'ed for tag=. . 2. You probably want to move to ELF right away. "make aout-to-elf" will handle this. It first builds a new aout-System and then makes an ELF system. This takes a fair amount of disk space. I didn't watch exactly, but probably on the order of 300..400MB. After the ELF installation it will reboot with a 3.0 GENERIC kernel. Take a look at /usr/src/Makefile.upgrade, the main steps are quite transparent and ask for confirmation. 3. The usual stuff, build a new custom kernel, merge /etc. That's it. You probably also need to install a new X11, and update at least those ports that touch utmp. It didn't work out quite that easily for me. In the middle of the ELF installworld I ran into a bad disk block. That went away but I umount'ed and fsck'ed /usr just to be safe. Bad move. There already was a new 3.0-aout /sbin/mount installed and that didn't work with the 2.2 kernel: "mount: ufs filesystem is not available". Oops. I had to get an old 2.2 mount executable back from backup. The 3.0-R fixit.flp appears to be broken, I finally copied over the mount executable from the fixit floppy of an old 2.2-SNAP I happened to still have lying around. Another thing to be careful about is the move to the new CAM devices, i.e. sd* -> da* etc. There's no pressing need to use the new devices as yet, but if you're already in the process of upgrading... Alas, "MAKEDEV all" does _not_ create all the devices. You get e.g. da0a..h but not da0s1a etc. Foolishly I changed /etc/fstab to da0a etc. After a reboot, mount refused to re-mount / read-write because its perception (da0s1a) and the fstab entry (da0a) disagreed. I had to return to my fixit disk. "MAKDEV da0s1h" creates all of da0s1a..h. -- Christian "naddy" Weisgerber naddy@mips.rhein-neckar.de 100+ SF Book Reviews: To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Oct 19 08:04:25 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA13846 for freebsd-stable-outgoing; Mon, 19 Oct 1998 08:04:25 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from alushta.NL.net (alushta.NL.net [193.78.240.22]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA13840 for ; Mon, 19 Oct 1998 08:04:22 -0700 (PDT) (envelope-from benst@nemesis.stuyts.nl) Received: from stuyts by alushta.NL.net with UUCP id <9891-23405>; Mon, 19 Oct 1998 17:03:44 +0200 Received: from nemesis.stuyts.nl (uucp@localhost) by terminus.stuyts.nl (8.9.1/8.9.1) with UUCP id QAA07080 for stable@freebsd.org; Mon, 19 Oct 1998 16:59:06 +0200 (MET DST) (envelope-from benst@nemesis.stuyts.nl) Received: from giskard.stuyts.nl (giskard.stuyts.nl [193.78.231.1]) by nemesis.stuyts.nl (8.8.8/8.8.8) with ESMTP id QAA04173 for ; Mon, 19 Oct 1998 16:41:06 +0200 (CEST) (envelope-from benst) Received: (from benst@localhost) by giskard.stuyts.nl (8.8.5/8.8.5) id QAA16098 for stable@freebsd.org; Mon, 19 Oct 1998 16:41:05 +0200 (MET DST) Message-Id: <199810191441.QAA16098@giskard.stuyts.nl> Content-Type: text/plain MIME-Version: 1.0 (NeXT Mail 3.3 v118.2) X-Nextstep-Mailer: Mail 3.3 (Enhance 2.0b6) Received: by NeXT.Mailer (1.118.2) From: Ben Stuyts Date: Mon, 19 Oct 98 16:41:03 +0200 To: stable@FreeBSD.ORG Subject: int overflow in tar Reply-To: ben@stuyts.nl Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello, The gnu tar program included with FreeBSD has a tiny problem with the option --totals. This option prints the total number of bytes written, but unfortunately the counter used by tar (tot_written in tar.h) is an int. So it overflows after 2^31 bytes have been written, like this: Backing up nemesis:/home3 at Mon Oct 19 13:27:43 CEST 1998 ... Total bytes written: -1960021504 df /home3 shows: Filesystem 1K-blocks Used Avail Capacity Mounted on /dev/sd2s1f 3857506 2307663 1241243 65% /home3 Should I take this up with the people who maintain gnu tar, or is this something we can fix in our source tree? Could there be more int overflow problems with tar? Best regards, Ben To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Oct 19 09:17:41 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA20035 for freebsd-stable-outgoing; Mon, 19 Oct 1998 09:17:41 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from austin.polstra.com (austin.polstra.com [206.213.73.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA20029 for ; Mon, 19 Oct 1998 09:17:36 -0700 (PDT) (envelope-from jdp@austin.polstra.com) Received: from austin.polstra.com (jdp@localhost) by austin.polstra.com (8.9.1/8.9.1) with ESMTP id JAA13669; Mon, 19 Oct 1998 09:17:00 -0700 (PDT) (envelope-from jdp) Message-Id: <199810191617.JAA13669@austin.polstra.com> To: cs@pollux.sdata.de Subject: Re: NGROUPS In-Reply-To: <199810181623.SAA24886@pollux.sdata.de> References: <199810181623.SAA24886@pollux.sdata.de> Organization: Polstra & Co., Seattle, WA Cc: stable@FreeBSD.ORG Date: Mon, 19 Oct 1998 09:17:00 -0700 From: John Polstra Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article <199810181623.SAA24886@pollux.sdata.de>, Christoph Splittgerber wrote: > What problems should I expect when I increase NGROUPS_MAX to, lets say, "64" > in /usr/src/sys/sys/param.h ? For one thing, the NFS protocol doesn't support that many groups. -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Self-knowledge is always bad news." -- John Barth To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Oct 19 09:23:22 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA20523 for freebsd-stable-outgoing; Mon, 19 Oct 1998 09:23:22 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from austin.polstra.com (austin.polstra.com [206.213.73.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA20513 for ; Mon, 19 Oct 1998 09:23:13 -0700 (PDT) (envelope-from jdp@austin.polstra.com) Received: from austin.polstra.com (jdp@localhost) by austin.polstra.com (8.9.1/8.9.1) with ESMTP id JAA13720; Mon, 19 Oct 1998 09:22:38 -0700 (PDT) (envelope-from jdp) Message-Id: <199810191622.JAA13720@austin.polstra.com> To: dom@phmit.demon.co.uk Subject: Re: -stable to 3.0 transition In-Reply-To: References: Organization: Polstra & Co., Seattle, WA Cc: stable@FreeBSD.ORG Date: Mon, 19 Oct 1998 09:22:38 -0700 From: John Polstra Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article , Dom Mitchell wrote: > How long will a.out builds be supported for? I would expect them to be phased out before the next release of 3.x.x. We are trying to make a point of _not_ becoming a "pick your favorite object format" OS. -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Self-knowledge is always bad news." -- John Barth To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Oct 19 09:26:32 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA20751 for freebsd-stable-outgoing; Mon, 19 Oct 1998 09:26:32 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from px.f1.ru (px.f1.ru [194.87.86.19]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA20746 for ; Mon, 19 Oct 1998 09:26:25 -0700 (PDT) (envelope-from am@px.f1.ru) Received: (from am@localhost) by px.f1.ru (8.8.8/amsoft/1.0) id UAA21320 ; Mon, 19 Oct 1998 20:24:56 +0400 (MSD) Date: Mon, 19 Oct 1998 20:24:56 +0400 (MSD) From: Andrew Maltsev Message-Id: <199810191624.UAA21320@px.f1.ru> To: naddy@mips.rhein-neckar.de, freebsd-stable@FreeBSD.ORG Subject: Re: -stable to 3.0 transition Newsgroups: oryol.lists.freebsd.stable In-Reply-To: <199810190836.MAA01535@amsoft.ru> X-Newsreader: TIN [UNIX 1.3 unoff BETA 970826; i386 FreeBSD 2.2.6-STABLE] Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Thanx a lot! It's going to be the FAQ answer soon, isn't it? In article you wrote: > In article <199810190836.MAA01535@amsoft.ru> > Andrew Maltsev wrote: > > > What are possible caveats of transition from 2.2-stable system to > > 3.0? Will usual `make world' do the thing? > > This weekend I migrated my machine from 2.2-STABLE (last updated early > September) to 3.0-CURRENT. > > 1. Get the 3.0 source. I threw away the 2.2 one and cvsup'ed for tag=. . > > 2. You probably want to move to ELF right away. "make aout-to-elf" will > handle this. It first builds a new aout-System and then makes an ELF > system. This takes a fair amount of disk space. I didn't watch > exactly, but probably on the order of 300..400MB. After the ELF > installation it will reboot with a 3.0 GENERIC kernel. Take a look at > /usr/src/Makefile.upgrade, the main steps are quite transparent and > ask for confirmation. > > 3. The usual stuff, build a new custom kernel, merge /etc. > > That's it. You probably also need to install a new X11, and update at > least those ports that touch utmp. > > It didn't work out quite that easily for me. In the middle of the ELF > installworld I ran into a bad disk block. That went away but I umount'ed > and fsck'ed /usr just to be safe. Bad move. There already was a new > 3.0-aout /sbin/mount installed and that didn't work with the 2.2 kernel: > "mount: ufs filesystem is not available". Oops. I had to get an old 2.2 > mount executable back from backup. The 3.0-R fixit.flp appears to be > broken, I finally copied over the mount executable from the fixit floppy > of an old 2.2-SNAP I happened to still have lying around. > > Another thing to be careful about is the move to the new CAM devices, > i.e. sd* -> da* etc. There's no pressing need to use the new devices as > yet, but if you're already in the process of upgrading... Alas, "MAKEDEV > all" does _not_ create all the devices. You get e.g. da0a..h but not > da0s1a etc. Foolishly I changed /etc/fstab to da0a etc. After a reboot, > mount refused to re-mount / read-write because its perception (da0s1a) > and the fstab entry (da0a) disagreed. I had to return to my fixit disk. > "MAKDEV da0s1h" creates all of da0s1a..h. > > -- > Christian "naddy" Weisgerber naddy@mips.rhein-neckar.de > 100+ SF Book Reviews: > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message -- am To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Oct 19 09:47:36 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA22698 for freebsd-stable-outgoing; Mon, 19 Oct 1998 09:47:36 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from B1FF.nas.nasa.gov (b1ff.nas.nasa.gov [129.99.34.135]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA22691 for ; Mon, 19 Oct 1998 09:47:34 -0700 (PDT) (envelope-from rone@B1FF.nas.nasa.gov) Received: (from rone@localhost) by B1FF.nas.nasa.gov (8.8.8/8.8.8) id JAA23894; Mon, 19 Oct 1998 09:45:43 -0700 (PDT) (envelope-from rone) From: Ron Echeverri Message-Id: <199810191645.JAA23894@B1FF.nas.nasa.gov> Subject: Re: syslogd and syslog.conf In-Reply-To: from Vince Vielhaber at "Oct 17, 98 10:57:19 am" To: vev@michvhf.com (Vince Vielhaber) Date: Mon, 19 Oct 1998 09:45:43 -0700 (PDT) Cc: ripley@nostromo.in-berlin.de, stable@FreeBSD.ORG 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 Vince Vielhaber writes: > On Thu, Oct 15, 1998 at 06:34:02PM +0100, Stuart Henderson wrote: >> It might be good to add a warning to the top of the standard >> syslog.conf file if it's not too late, bearing in mind that the >> normally recommended editor for new users is ee, which by default >> converts tabs to spaces automatically. EE doesn't convert existing tabs only new ones unless you tell it not to. You can do that from the command line or from the options menu. Still, if this is ee's default behavior, it's Wrong and it should probably be changed. If ee is going to be the easy editor we're giving newbie admins, it should do the right thing as often as possible. rone -- Ron Echeverri Numerical Aerodynamic Simulation Facility DSS/Usenet Administrator NASA Ames Research Center Internet Sysop Mountain View, CA x42771 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Oct 19 15:24:14 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA26577 for freebsd-stable-outgoing; Mon, 19 Oct 1998 15:24:14 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from wizard.fuzzymagic.com (n04h3201.ex-pressnet.com [24.239.15.201]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA26572 for ; Mon, 19 Oct 1998 15:24:12 -0700 (PDT) (envelope-from sean@fuzzymagic.com) Received: from fuzzymagic.com (archmage [172.21.0.10]) by wizard.fuzzymagic.com (8.8.8/8.8.8) with ESMTP id SAA06427 for ; Mon, 19 Oct 1998 18:23:36 -0400 (EDT) Message-ID: <362BBBF8.D9B709AE@fuzzymagic.com> Date: Mon, 19 Oct 1998 18:23:53 -0400 From: Sean Brandt X-Mailer: Mozilla 4.5 [en] (X11; I; FreeBSD 3.0-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-stable@FreeBSD.ORG Subject: (no subject) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG subscribe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Oct 19 16:54:58 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA05610 for freebsd-stable-outgoing; Mon, 19 Oct 1998 16:54:58 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from luke.cpl.net (luke.cpl.net [209.150.92.68]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA05603 for ; Mon, 19 Oct 1998 16:54:55 -0700 (PDT) (envelope-from shawn@luke.cpl.net) Received: (from shawn@localhost) by luke.cpl.net (8.8.8/8.8.8) id QAA12278; Mon, 19 Oct 1998 16:54:33 -0700 (PDT) Message-ID: <19981019165433.30675@cpl.net> Date: Mon, 19 Oct 1998 16:54:33 -0700 From: Shawn Ramsey To: stable@FreeBSD.ORG Subject: /usr/obj Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89.1i Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Can /usr/obj be a symlink to another directory? I'd rather build to /disk4/obj since I have a lot more room. I get a an error I did not capture when doing a symlink?? Thanks. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Oct 19 18:27:54 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA17477 for freebsd-stable-outgoing; Mon, 19 Oct 1998 18:27:54 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from smtp4.nwnexus.com (smtp4.nwnexus.com [206.63.63.52]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA17469 for ; Mon, 19 Oct 1998 18:27:53 -0700 (PDT) (envelope-from wrsomsky@halcyon.com) Received: from gramarye (evt-lx101-ip17.nwnexus.net [204.57.235.67]) by smtp4.nwnexus.com (8.8.8/8.8.8) with ESMTP id SAA09563; Mon, 19 Oct 1998 18:27:17 -0700 (PDT) Received: (from wrsomsky@localhost) by gramarye (8.9.1/8.8.8) id SAA01163; Mon, 19 Oct 1998 18:22:52 -0700 (PDT) (envelope-from wrsomsky) Message-ID: <19981019182252.A1153@halcyon.com> Date: Mon, 19 Oct 1998 18:22:52 -0700 From: "William R. Somsky" To: "Jordan K. Hubbard" , Andrew Maltsev Cc: freebsd-stable@FreeBSD.ORG Subject: Re: -stable to 3.0 transition References: <199810190836.MAA01535@amsoft.ru> <3716.908787025@time.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <3716.908787025@time.cdrom.com>; from Jordan K. Hubbard on Mon, Oct 19, 1998 at 01:50:25AM -0700 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Oct 19, 1998 at 01:50:25AM -0700, Jordan K. Hubbard wrote: > > > Btw, will 3.0-stable branch be forked? > > After some of the dust finishes settling and 3.0 is more worthy of the > title. Maybe January. Would it be useful to establish the "RELENG_3_0" cvs tag now, even if it doesn't actually diverge from "." until January? Or is there something that would prevent this from doing/being the "right thing"? ________________________________________________________________________ William R. Somsky wrsomsky@halcyon.com Physicist, Baritone, Guitarist http://www.halcyon.com/wrsomsky To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Oct 19 18:54:24 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA21283 for freebsd-stable-outgoing; Mon, 19 Oct 1998 18:54:24 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from mail.HiWAAY.net (fly.HiWAAY.net [208.147.154.56]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA21268 for ; Mon, 19 Oct 1998 18:54:21 -0700 (PDT) (envelope-from dkelly@n4hhe.ampr.org) Received: from nospam.hiwaay.net (tnt3-41.HiWAAY.net [208.147.146.41]) by mail.HiWAAY.net (8.9.0/8.9.0) with ESMTP id UAA02103; Mon, 19 Oct 1998 20:53:45 -0500 (CDT) Received: from n4hhe.ampr.org (localhost.ampr.org [127.0.0.1]) by nospam.hiwaay.net (8.8.8/8.8.8) with ESMTP id UAA01234; Mon, 19 Oct 1998 20:51:54 -0500 (CDT) (envelope-from dkelly@n4hhe.ampr.org) Message-Id: <199810200151.UAA01234@nospam.hiwaay.net> X-Mailer: exmh version 2.0.2 2/24/98 To: Shawn Ramsey cc: stable@FreeBSD.ORG From: David Kelly Subject: Re: /usr/obj In-reply-to: Message from Shawn Ramsey of "Mon, 19 Oct 1998 16:54:33 PDT." <19981019165433.30675@cpl.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 19 Oct 1998 20:51:54 -0500 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Shawn Ramsey writes: > Can /usr/obj be a symlink to another directory? I'd rather build to > /disk4/obj since I have a lot more room. I get a an error I did not capture > when doing a symlink?? I do it all the time. That's what symlinks are for. -- David Kelly N4HHE, dkelly@nospam.hiwaay.net ===================================================================== The human mind ordinarily operates at only ten percent of its capacity -- the rest is overhead for the operating system. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Oct 19 19:01:16 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA21942 for freebsd-stable-outgoing; Mon, 19 Oct 1998 19:01:16 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from cassiopeia.caprica.com ([207.137.48.14]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id TAA21933 for ; Mon, 19 Oct 1998 19:01:14 -0700 (PDT) (envelope-from frank@exit.com) Received: from exit.com by cassiopeia.caprica.com (8.6.10/95022701) id QAA05835; Mon, 19 Oct 1998 16:08:01 -0800 Received: (from frank@localhost) by exit.com (8.8.8/8.7.3) id SAA11971; Mon, 19 Oct 1998 18:41:18 -0700 (PDT) From: Frank Mayhar Message-Id: <199810200141.SAA11971@exit.com> Subject: Re: -stable to 3.0 transition To: wrsomsky@halcyon.com (William R. Somsky) Date: Mon, 19 Oct 1998 18:41:18 -0700 (PDT) Cc: jkh@time.cdrom.com, am@amsoft.ru, freebsd-stable@FreeBSD.ORG In-Reply-To: <19981019182252.A1153@halcyon.com> from "William R. Somsky" at "Oct 19, 98 06:22:52 pm" X-Mailer: ELM [version 2.4ME+ PL17 (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 William R. Somsky wrote: > On Mon, Oct 19, 1998 at 01:50:25AM -0700, Jordan K. Hubbard wrote: > > Someone lost in the mists of time spoke thusly: > > > Btw, will 3.0-stable branch be forked? > > After some of the dust finishes settling and 3.0 is more worthy of the > > title. Maybe January. > Would it be useful to establish the "RELENG_3_0" cvs tag now, even if > it doesn't actually diverge from "." until January? Or is there > something that would prevent this from doing/being the "right thing"? Speaking as one who often finds himself in the unenviable position of trying to reconcile multiple CVS branches, the later you branch, the easier your job is. Best is to never branch at all, and I strive to maintain that state. Maintaining multiple CVS branches is a real pain, and I can certainly understand why Jordan is delaying as long as possible. -- Frank Mayhar frank@exit.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Oct 19 19:49:25 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA26137 for freebsd-stable-outgoing; Mon, 19 Oct 1998 19:49:25 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from foobar.franken.de (foobar.franken.de [194.94.249.81]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA26101 for ; Mon, 19 Oct 1998 19:49:01 -0700 (PDT) (envelope-from logix@foobar.franken.de) Received: (from logix@localhost) by foobar.franken.de (8.8.8/8.8.5) id EAA22925; Tue, 20 Oct 1998 04:43:42 +0200 (CEST) Message-ID: <19981020044341.A22803@foobar.franken.de> Date: Tue, 20 Oct 1998 04:43:41 +0200 From: Harold Gutch To: Shawn Ramsey , stable@FreeBSD.ORG Subject: Re: /usr/obj References: <19981019165433.30675@cpl.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <19981019165433.30675@cpl.net>; from Shawn Ramsey on Mon, Oct 19, 1998 at 04:54:33PM -0700 X-Organisation: BatmanSystemDistribution X-Mission: To free the world from the Penguin Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Oct 19, 1998 at 04:54:33PM -0700, Shawn Ramsey wrote: > Can /usr/obj be a symlink to another directory? I'd rather build to > /disk4/obj since I have a lot more room. I get a an error I did not capture > when doing a symlink?? > Symlinking (ln -s <...>) should work, you're not trying to hardlink, are you ? >From the ln(1) manpage: Hard links may not normally refer to directories and may not span file systems. -- bye, logix Sleep is an abstinence syndrome wich occurs due to lack of caffein. Wed Mar 4 04:53:33 CET 1998 #unix, ircnet To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Oct 19 21:01:46 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA02088 for freebsd-stable-outgoing; Mon, 19 Oct 1998 21:01:46 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from luke.cpl.net (luke.cpl.net [209.150.92.68]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA02079 for ; Mon, 19 Oct 1998 21:01:43 -0700 (PDT) (envelope-from shawn@luke.cpl.net) Received: (from shawn@localhost) by luke.cpl.net (8.8.8/8.8.8) id VAA27437; Mon, 19 Oct 1998 21:01:21 -0700 (PDT) Message-ID: <19981019210121.48459@cpl.net> Date: Mon, 19 Oct 1998 21:01:21 -0700 From: Shawn Ramsey To: Harold Gutch , stable@FreeBSD.ORG Subject: Re: /usr/obj References: <19981019165433.30675@cpl.net> <19981020044341.A22803@foobar.franken.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89.1i In-Reply-To: <19981020044341.A22803@foobar.franken.de>; from Harold Gutch on Tue, Oct 20, 1998 at 04:43:41AM +0200 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Symlinking (ln -s <...>) should work, you're not trying to > hardlink, are you ? > From the ln(1) manpage: > Hard links may > not normally refer to directories and may not span file systems. > I am using ln -s. "ln -s /disk4/obj obj" is the command I used. Are there any special permissions that the /disk4/obj directory would require? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Oct 19 23:06:42 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA11431 for freebsd-stable-outgoing; Mon, 19 Oct 1998 23:06:42 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from matsu.ipc.shimane-u.ac.jp (matsu.ipc.shimane-u.ac.jp [192.244.210.253]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA11420 for ; Mon, 19 Oct 1998 23:06:34 -0700 (PDT) (envelope-from s95218@matsu.ipc.shimane-u.ac.jp) Received: from rpc02.matsu.ipc.shimane-u.ac.jp (rpc02 [10.20.40.12]) by matsu.ipc.shimane-u.ac.jp (8.8.5+2.7Wbeta5/3.3W9-LOCAL_VERSION=NEC) with SMTP id PAA06642 for ; Tue, 20 Oct 1998 15:02:42 +0900 (JST) Message-Id: <9810200616.AA01149@rpc02.matsu.ipc.shimane-u.ac.jp> From: s95218@matsu.ipc.shimane-u.ac.jp (=?ISO-2022-JP?B?GyRCR3JAUBsoSg==?= =?ISO-2022-JP?B?GyRCMGxPOhsoSg==?=) Date: Tue, 20 Oct 1998 15:16:34 +0900 To: freebsd-stable@FreeBSD.ORG MIME-Version: 1.0 X-Mailer: AL-Mail 1.32 Content-Type: text/plain; charset=iso-2022-jp Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG $BGr@P0lO:(J s95218@matsu.ipc.shimane-u.ac.jp To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Oct 20 04:11:18 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA04088 for freebsd-stable-outgoing; Tue, 20 Oct 1998 04:11:18 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from limes.NIC.DTAG.DE (limes.NIC.DTAG.DE [194.25.1.113]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA04081 for ; Tue, 20 Oct 1998 04:11:15 -0700 (PDT) (envelope-from bm@Reineke.malepartus.de) Received: from kronos.NIC.DTAG.DE (kronos.NIC.DTAG.DE [194.25.1.92]) by limes.NIC.DTAG.DE (8.8.5/8.8.3) with ESMTP id NAA10096 for ; Tue, 20 Oct 1998 13:09:28 +0200 (MET DST) Received: from kronos.NIC.DTAG.DE (kronos.NIC.DTAG.DE [194.25.1.92]) by limes.NIC.DTAG.DE (8.8.5/8.8.3) with ESMTP id NAA10096 for ; Tue, 20 Oct 1998 13:09:28 +0200 (MET DST) Received: from Reineke.malepartus.de (reineke.malepartus.de [194.25.4.66]) by kronos.NIC.DTAG.DE (8.8.5/8.7.1) with ESMTP id NAA13459 for ; Tue, 20 Oct 1998 13:10:40 +0200 (MET DST) Received: from Reineke.malepartus.de (localhost.Malepartus.de [127.0.0.1]) by Reineke.malepartus.de (8.8.8/8.8.8) with ESMTP id NAA29461 for ; Tue, 20 Oct 1998 13:09:43 +0200 (MEST) (envelope-from bm@Reineke.malepartus.de) Message-Id: <199810201109.NAA29461@Reineke.malepartus.de> X-Mailer: exmh version 2.0.2 2/24/98 From: Burkard Meyendriesch Subject: ECC memory support To: freebsd-stable@FreeBSD.ORG Reply-To: bm@malepartus.de X-organization: The home of Reineke Fuchs X-GPOS: 52.0844N 7.9081E X-phone: +49 5484 96097 X-pgp-fingerprint: DF 83 04 CD B5 D1 10 43 57 4C AD 9A B1 02 28 17 X-face: "[-;]oI+8gP9>*J%knDN8d%DuhvJS2Lj4L\bRb7gz(pcT?2Zh6_Vam_6csAum3$<&lhAFd^ jt|!&Ut1C~Vg*E/q}+#cbFg-GU]c.bB8Ad,L'W$'9{^0y'AzM4#hS[C[F-1'|O;Kg3Vrq5q6dsU*TmJ@}+QPM\ b[^9Rhd,UoMpRpd5k[X=h.Dom*kbT`cNQ Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 20 Oct 1998 13:09:43 +0200 Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by hub.freebsd.org id EAA04084 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, I'm operating FreeBSD 2.2.7 on an ASUS T2P4S board. The chipset on this board supports error detection and correction (ECC) in conjunction with parity SIMMs. My board actually works with 256M parity memory and ECC feature enabled. My system runs 24h per day with manual reboots only after OS updates every 3-6 months. Since I use my new motherboard (see above) I recognize spurious automatic reboots every few days, without any kernel panic or syslog output. I suspect that this behavoir has something to do with my ECC memory. My questions: * Is there any support for ECC in the FreeBSD kernel? * How can I get log output of soft (e.g. correctable) memory errors? * In the case of non-correctable errors: How can I get their address? Thanks in advance Burkard -- * Burkard Meyendriesch ___ bm@malepartus.de * * Hauptstrasse 45 ________|________ tel +49 5484 96097 * * D-49219 Glandorf-Schwege 0 52 05'05"N 07 54'29"E * * PGP-Fingerprint DF 83 04 CD B5 D1 10 43 57 4C AD 9A B1 02 28 17 * To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Oct 20 04:57:09 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA08180 for freebsd-stable-outgoing; Tue, 20 Oct 1998 04:57:09 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from iserver.itworks.com.au (iserver.itworks.com.au [203.32.61.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA08175 for ; Tue, 20 Oct 1998 04:57:07 -0700 (PDT) (envelope-from gavin@itworks.com.au) Received: from localhost (gavin@localhost) by iserver.itworks.com.au (8.8.8/8.8.8) with SMTP id VAA06003 for ; Tue, 20 Oct 1998 21:56:41 +1000 (EST) (envelope-from gavin@itworks.com.au) Date: Tue, 20 Oct 1998 21:56:40 +1000 (EST) From: Gavin Cameron To: stable@FreeBSD.ORG Subject: cvsuping -STABLE 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 Hi, I just CVSuped (well a couple of hours ago) and I checked out RELENG_2_2 hoping to get the latest and greatest. The Makefile in /usr/src is version 1.109.2.31. If I go into the repository and have a look at Makefile,v I see the following symbols RELENG_3_0_0_RELEASE:1.220 RELENG_2_2_7_RELEASE:1.109.2.33 RELENG_2_2_6_RELEASE:1.109.2.25 RELENG_2_2_5_RELEASE:1.109.2.19 RELENG_2_2_2_RELEASE:1.109.2.4 RELENG_2_2_1_RELEASE:1.109.2.2 RELENG_2_2_0_RELEASE:1.109.2.2 RELENG_2_1_7_RELEASE:1.57.4.19 RELENG_2_1_6_1_RELEASE:1.57.4.19 RELENG_2_1_6_RELEASE:1.57.4.19 RELENG_2_2:1.109.0.2 Which, I think, tells me that if I was infact checking out RELENG_2_2, I should have got the Makefile that is of a later version than 2.2.7 release (or atleast that version). As far as I can tell, checking out RELENG_2_2 gives me a Makefile from before 2.2.7 was released. This also makes me wonder if all the source code I've checked out is old. So, my question is, do I still use the RELENG_2_2 tag to checkout the stable branch? and if I do, why don't I have the right Makefile checked out. Thanks in advance, Gavin []-----------------------------------+------------------------------------[] | Gavin Cameron | ITworks Consulting | | Ph : 0418 390350 | Suite 100, 85 Grattan Street | | Fax : +61 3 9347 6544 | Carlton, Victoria | | Email : gavin@itworks.com.au | Australia, 3053 | []-----------------------------------+------------------------------------[] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Oct 20 06:02:03 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA13081 for freebsd-stable-outgoing; Tue, 20 Oct 1998 06:02:03 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from burra.zip.com.au (bart.zip.com.au [61.8.6.5]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA13039 for ; Tue, 20 Oct 1998 06:01:57 -0700 (PDT) (envelope-from bart@burra.zip.com.au) Received: (from bart@localhost) by burra.zip.com.au (8.8.8/8.8.8) id XAA01587; Tue, 20 Oct 1998 23:05:01 +1000 (EST) (envelope-from bart) Date: Tue, 20 Oct 1998 23:05:01 +1000 (EST) Message-Id: <199810201305.XAA01587@burra.zip.com.au> From: Bart Lindsey To: bm@malepartus.de CC: freebsd-stable@FreeBSD.ORG In-reply-to: <199810201109.NAA29461@Reineke.malepartus.de> (message from Burkard Meyendriesch on Tue, 20 Oct 1998 13:09:43 +0200) Subject: Re: ECC memory support References: <199810201109.NAA29461@Reineke.malepartus.de> Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi Burkard, ECC occurs between the memory modules and the motherboard. The kernel doesn't get involved and the process is transparent to the kernel. The PC architecture doesn't handle memory problems very nicely and typically the CPU resets without warning or just freezes without the kernel having any opportunity to trap an error. Depending on the revision of your motherboard, you might have to download the bios patch described at URL: http://www.asus.com/downloads/bios/Jbios.asp?Motherboard=P/I-P55T2P4S#instructions There are two factors mentioned which can cause parity errors: 1. PS2 mouse installed or 2. AMD K6 installed and ECC/parity enabled. Good Luck! Bart. Burkard Meyendriesch e-toned > >I'm operating FreeBSD 2.2.7 on an ASUS T2P4S board. The chipset on this >board supports error detection and correction (ECC) in conjunction with >parity SIMMs. My board actually works with 256M parity memory and ECC >feature enabled. > >My system runs 24h per day with manual reboots only after OS updates >every 3-6 months. Since I use my new motherboard (see above) I recognize >spurious automatic reboots every few days, without any kernel panic or >syslog output. I suspect that this behavoir has something to do with my >ECC memory. > >My questions: >* Is there any support for ECC in the FreeBSD kernel? >* How can I get log output of soft (e.g. correctable) memory errors? >* In the case of non-correctable errors: How can I get their address? > >Thanks in advance >Burkard > >-- >* Burkard Meyendriesch ___ bm@malepartus.de * >* Hauptstrasse 45 ________|________ tel +49 5484 96097 * >* D-49219 Glandorf-Schwege 0 52 05'05"N 07 54'29"E * >* PGP-Fingerprint DF 83 04 CD B5 D1 10 43 57 4C AD 9A B1 02 28 17 * > > > >To Unsubscribe: send mail to majordomo@FreeBSD.org >with "unsubscribe freebsd-stable" in the body of the message > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Oct 20 06:11:09 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA14450 for freebsd-stable-outgoing; Tue, 20 Oct 1998 06:11:09 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from ifi.uio.no (ifi.uio.no [129.240.64.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA14421; Tue, 20 Oct 1998 06:10:58 -0700 (PDT) (envelope-from dag-erli@ifi.uio.no) Received: from bilskirnir.ifi.uio.no (2602@bilskirnir.ifi.uio.no [129.240.64.135]) by ifi.uio.no (8.8.8/8.8.7/ifi0.2) with ESMTP id PAA05526; Tue, 20 Oct 1998 15:09:21 +0200 (MET DST) Received: (from dag-erli@localhost) by bilskirnir.ifi.uio.no ; Tue, 20 Oct 1998 15:09:18 +0200 (MET DST) Mime-Version: 1.0 To: "Michael C. Vergallen" Cc: George , Gustavo Vieira Goncalves Coelho Rios , FreeBSD , FreeBSD Stable Subject: Re: Walnut Creek vs. CheapBytes References: Organization: University of Oslo, Department of Informatics X-url: http://www.stud.ifi.uio.no/~dag-erli/ X-other-addresses: 'finger dag-erli@ifi.uio.no' for a list X-disclaimer-1: The views expressed in this article are mine alone, and do X-disclaimer-2: not necessarily coincide with those of any organisation or X-disclaimer-3: company with which I am or have been affiliated. X-Stop-Spam: http://www.cauce.org/ From: dag-erli@ifi.uio.no (Dag-Erling C. =?iso-8859-1?Q?Sm=F8rgrav?= ) Date: 20 Oct 1998 15:09:18 +0200 In-Reply-To: "Michael C. Vergallen"'s message of "Sat, 17 Oct 1998 04:09:45 +0200 (CEST)" Message-ID: Lines: 11 X-Mailer: Gnus v5.5/Emacs 19.34 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by hub.freebsd.org id GAA14439 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > If you have the funds to actually purchase a cdrom distribution I would > purchase the full distribution from Walnut creek. Because it supports the > Freebsd project. Now about the question off witch OS is better quite > honestly I couldn't say ... It's funny that you should answer this question since the original poster *didn't ask it* :) DES -- Dag-Erling Smørgrav - dag-erli@ifi.uio.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Oct 20 06:33:50 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA17291 for freebsd-stable-outgoing; Tue, 20 Oct 1998 06:33:50 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from helios.whro.org (helios.whro.org [198.78.178.25]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA17282 for ; Tue, 20 Oct 1998 06:33:48 -0700 (PDT) (envelope-from bboone@whro.org) Received: from whro.org (happy85.whro.net [198.76.162.85]) by helios.whro.org (8.8.5/8.8.5) with ESMTP id JAA00571 for ; Tue, 20 Oct 1998 09:25:35 -0400 (EDT) Message-ID: <362C93C1.C81CF9AB@whro.org> Date: Tue, 20 Oct 1998 09:44:33 -0400 From: Bob Boone X-Mailer: Mozilla 4.04 [en] (Win95; U) MIME-Version: 1.0 To: "freebsd-stable@FreeBSD.ORG" Subject: 3.0 Questions Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, This is the only FreeBSD list I receive, so I need to ask three questions. I just built a new webserver Thursday last, from boot.flp/2.2.7, only to find 3.0 released on Friday. (1) Do I need / how do I get a "boot.flp" that will build 3.0 instead of 2.2.7, so I can nuke the Thursday build and start over?? (2) Do I WANT to move to 3.0 -- is it stable/tested enough for the "brain trust" to feel comfortable with it for a low/moderate traffic webserver ?? (3) I'm rebuilding THIS server because I was nuked thru the mail/buffer overflow hack, but I'm reading that it isn't just popper... that several pop3 and imap servers will break, and that only sendmail 8.9.1 with the 1a patch will stop it.... CAN I ADD the sendmail 8.9.1 without breaking something else ??? are there dependencies in 8.9.1 that either 2.2.7 or 3.0 won't support ???? Thanks, Bob Boone bboone@whro.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Oct 20 07:01:58 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA18884 for freebsd-stable-outgoing; Tue, 20 Oct 1998 07:01:58 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from ss3000e.cselt.it (ss3000e.cselt.it [163.162.4.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA18872 for ; Tue, 20 Oct 1998 07:01:50 -0700 (PDT) (envelope-from Enrico.Petrov@CSELT.IT) Received: from rabadan.cselt.stet.it by ss3000e.cselt.stet.it (PMDF V5.1-12 #29348) with ESMTP id <0F1400LQAPEGQI@ss3000e.cselt.stet.it> for freebsd-stable@freebsd.org; Tue, 20 Oct 1998 15:56:40 +0200 (MET DST) Received: by rabadan.cselt.stet.it with Internet Mail Service (5.5.2232.9) id <49W8KDC3>; Tue, 20 Oct 1998 16:00:14 +0200 Content-return: allowed Date: Tue, 20 Oct 1998 16:00:31 +0200 From: Petrov Enrico Subject: Problem from 2.2.1 to 3.0 FreeBSD RELEASE To: "'freebsd-stable@freebsd.org'" Message-id: <69A4AB2CD710D211A0AF00805FA6EAF10F9F57@xrr3.cselt.stet.it> X-Envelope-to: freebsd-stable@freebsd.org MIME-version: 1.0 X-Mailer: Internet Mail Service (5.5.2232.9) Content-type: text/plain Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'm trying to migrate from 2.2.1 to 3.0 RELEASE. I've just downloaded 3.0 source tree. If I type "make world" in /usr/src/ directory I find this error: [...] cc -0 -pipe -I/usr/src/usr.bin/make -I/usr/obj/aout/usr/src/tmp/usr/include -static -o make arch.o compat.o .....[skipped] main.o: Undefined symbol `_sysctlbyname` referenced from text segment *** Error code 1 What does it mean? If this is the right mailing list, can someone help me? Enrico To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Oct 20 07:57:03 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA22928 for freebsd-stable-outgoing; Tue, 20 Oct 1998 07:57:03 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from stennis.ca.sandia.gov (stennis.ca.sandia.gov [146.246.243.44]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA22922 for ; Tue, 20 Oct 1998 07:57:02 -0700 (PDT) (envelope-from bmah@stennis.ca.sandia.gov) Received: (from bmah@localhost) by stennis.ca.sandia.gov (8.9.1/8.9.1) id HAA22937; Tue, 20 Oct 1998 07:55:45 -0700 (PDT) Message-Id: <199810201455.HAA22937@stennis.ca.sandia.gov> X-Mailer: exmh version 2.0.2 2/24/98 To: Bob Boone Cc: "freebsd-stable@FreeBSD.ORG" Subject: Re: 3.0 Questions In-Reply-To: Your message of "Tue, 20 Oct 1998 09:44:33 EDT." <362C93C1.C81CF9AB@whro.org> From: bmah@CA.Sandia.GOV (Bruce A. Mah) Reply-To: bmah@CA.Sandia.GOV X-Face: g~c`.{#4q0"(V*b#g[i~rXgm*w;:nMfz%_RZLma)UgGN&=j`5vXoU^@n5v4:OO)c["!w)nD/!!~e4Sj7LiT'6*wZ83454H""lb{CC%T37O!!'S$S&D}sem7I[A 2V%N&+ X-Url: http://www.ca.sandia.gov/~bmah/ Mime-Version: 1.0 Content-Type: multipart/signed; boundary="==_Exmh_1974079544P"; micalg=pgp-md5; protocol="application/pgp-signature" Content-Transfer-Encoding: 7bit Date: Tue, 20 Oct 1998 07:55:45 -0700 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --==_Exmh_1974079544P Content-Type: text/plain; charset=us-ascii If memory serves me right, Bob Boone wrote: > This is the only FreeBSD list I receive, so I need to ask three > questions. Please don't take offense, but it looks to me like you really ought to be subscribed to freebsd-questions. None of these questions relate to -stable. > I just built a new webserver Thursday last, from boot.flp/2.2.7, only > to find 3.0 released on Friday. > (1) Do I need / how do I get a "boot.flp" that will build 3.0 instead of > 2.2.7, so I can nuke the Thursday build and start over?? You can grab a boot.flp image for 3.0 from ftp://ftp.freebsd.org/pub/FreeBSD/3. 0-RELEASE/floppies/boot.flp but see below. > (2) Do I WANT to move to 3.0 -- is it stable/tested enough for the > "brain trust" to feel comfortable with it for a low/moderate traffic > webserver ?? IMHO, if you are asking the question, no. From ftp://ftp.freebsd.org/pub/FreeB SD/3.0-RELEASE/README.TXT "This release is aimed primarily at early-adopters and the various other folks who want to get on board with 3.0 and are willing to deal with the various down-sides of a "dot-zero" release." 3.0 has some nice new features (SMP, CAM, etc.) but it sounds like in your situation they won't help you much. You'll probably be better off with 2.2.7-RELEASE (note that there will even be a 2.2.8-RELEASE later this year). > (3) I'm rebuilding THIS server because I was nuked thru the mail/buffer > overflow hack, but I'm reading that it isn't just popper... that several > pop3 and imap servers will break, and that only sendmail 8.9.1 with the > 1a patch will stop it.... CAN I ADD the sendmail 8.9.1 without breaking > something else ??? are there dependencies in 8.9.1 that either 2.2.7 or > 3.0 won't support ???? sendmail 8.9.1a was released to help protect various mail clients that had/have problems with buffer overflows in their MIME processing code. It has nothing to do with buffer overflows in various POP3 and IMAP servers. Yes, you can compile and run sendmail 8.9.1a on 2.2.7-RELEASE and/or 3.0-RELEASE. 2.2.7-RELEASE comes with sendmail-8.8.8 and 3.0-RELEASE comes with sendmail-8.9.1. If you're concerned about the security of your FreeBSD box (and I think you should be) you'll probably also want to subscribe to freebsd-security. The various buffer overflows in mail servers were discussed there (ad nauseum :-) ). Hope this helps, Bruce. --==_Exmh_1974079544P Content-Type: application/pgp-signature -----BEGIN PGP MESSAGE----- Version: 2.6.2 iQCVAwUBNiykcKjOOi0j7CY9AQFmjwP9F3OqeFHnvTraQ/9vpaLBdTEDEZ6e3z6i +puYaRJ//HDoCWz/pyCmCFfbxHxO51azsIX3o75hDJHusw+bP1WlJRD2nSpBdNqd niVV8ECs7JUX480EGzaOX+KCncNWqzYUD8X/s0mcw3aUy3w4b0muLKgNOFgkvy5w /Al3kGtVWNM= =ZizN -----END PGP MESSAGE----- --==_Exmh_1974079544P-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Oct 20 07:59:16 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA23094 for freebsd-stable-outgoing; Tue, 20 Oct 1998 07:59:16 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from rige.physik.fu-berlin.de (rige.physik.fu-berlin.de [160.45.33.59]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA23080 for ; Tue, 20 Oct 1998 07:58:58 -0700 (PDT) (envelope-from thimm@rige.physik.fu-berlin.de) Received: (from thimm@localhost) by rige.physik.fu-berlin.de (8.8.8/8.8.8) id QAA00542; Tue, 20 Oct 1998 16:58:26 +0200 (CEST) (envelope-from thimm) Message-ID: <19981020165826.A385@physik.fu-berlin.de> Date: Tue, 20 Oct 1998 16:58:26 +0200 From: Axel Thimm To: freebsd-stable@FreeBSD.ORG Subject: xl0 tx errors and unclean shutdown Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Last make world was 12. Oct. (successfull) Today (20.10) I rebuilt everything (including kernel). I got transmission errors from the new kernel: Oct 20 16:05:10 rige /kernel: xl0: transmission error: 90 Where do these come from? Is my 3c900 broken (worked fine until now) or the xl0 driver? I thus rebooted the old kernel (with the new system). The transmission errors ceased, but although I had shutdown the system under the new kernel succesfully the old kernel moaned on me. Oct 20 16:06:15 rige shutdown: reboot by root: Oct 20 16:06:17 rige syslogd: exiting on signal 15 Oct 20 16:08:47 rige /kernel: Copyright (c) 1992-1998 FreeBSD Inc. Oct 20 16:08:47 rige /kernel: Copyright (c) 1982, 1986, 1989, 1991, 1993 Oct 20 16:08:47 rige /kernel: The Regents of the University of California. All rights reserved. Oct 20 16:08:47 rige /kernel: Oct 20 16:08:47 rige /kernel: FreeBSD 2.2.7-STABLE #0: Tue Oct 20 10:43:01 CEST 1998 Oct 20 16:08:47 rige /kernel: root@puariko.home.de:/usr/src/sys/compile/RIGE [...] Oct 20 16:08:48 rige /kernel: WARNING: / was not properly dismounted. But perhaps this has to do with me copying the old kernel over the new w/o changing the kern.bootfile variable (or all the other stuff make install usually does). Regards, Axel. -- Axel.Thimm@physik.fu-berlin.de Axel.Thimm@ifh.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Oct 20 08:09:42 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA24038 for freebsd-stable-outgoing; Tue, 20 Oct 1998 08:09:42 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from austin.polstra.com (austin.polstra.com [206.213.73.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA24033 for ; Tue, 20 Oct 1998 08:09:38 -0700 (PDT) (envelope-from jdp@austin.polstra.com) Received: from austin.polstra.com (jdp@localhost) by austin.polstra.com (8.9.1/8.9.1) with ESMTP id IAA04269; Tue, 20 Oct 1998 08:08:56 -0700 (PDT) (envelope-from jdp) Message-Id: <199810201508.IAA04269@austin.polstra.com> To: gavin@itworks.com.au Subject: Re: cvsuping -STABLE In-Reply-To: References: Organization: Polstra & Co., Seattle, WA Cc: stable@FreeBSD.ORG Date: Tue, 20 Oct 1998 08:08:56 -0700 From: John Polstra Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article , Gavin Cameron wrote: > I just CVSuped (well a couple of hours ago) and I checked out RELENG_2_2 > hoping to get the latest and greatest. > > The Makefile in /usr/src is version 1.109.2.31. If I go into the > repository and have a look at Makefile,v I see the following > > symbols > RELENG_3_0_0_RELEASE:1.220 > RELENG_2_2_7_RELEASE:1.109.2.33 > RELENG_2_2_6_RELEASE:1.109.2.25 > RELENG_2_2_5_RELEASE:1.109.2.19 > RELENG_2_2_2_RELEASE:1.109.2.4 > RELENG_2_2_1_RELEASE:1.109.2.2 > RELENG_2_2_0_RELEASE:1.109.2.2 > RELENG_2_1_7_RELEASE:1.57.4.19 > RELENG_2_1_6_1_RELEASE:1.57.4.19 > RELENG_2_1_6_RELEASE:1.57.4.19 > RELENG_2_2:1.109.0.2 > > Which, I think, tells me that if I was infact checking out RELENG_2_2, I > should have got the Makefile that is of a later version than 2.2.7 > release (or atleast that version). That is a common misconception. In CVS, tags whose revision numbers contain a 0 component (like 1.109.0.2) are special. They're branch tags. The actual branch number is formed by removing the 0 and sliding the next digit over into its place. So RELENG_2_2 refers to revision 1.109.2.x for the largest existing "x". John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Nobody ever went broke underestimating the taste of the American public." -- H. L. Mencken To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Oct 20 09:20:54 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA02916 for freebsd-stable-outgoing; Tue, 20 Oct 1998 09:20:54 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from ctcdist.com. ([199.3.192.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA02898 for ; Tue, 20 Oct 1998 09:20:47 -0700 (PDT) (envelope-from placej@ctcdist.com) Received: (from placej@localhost) by ctcdist.com. (8.8.8/8.8.7) id MAA18675; Tue, 20 Oct 1998 12:20:33 -0400 (EDT) (envelope-from placej) Message-ID: <19981020122033.A18596@ctcdist.com> Date: Tue, 20 Oct 1998 12:20:33 -0400 From: "John C. Place" To: FreeBSD Stable Subject: Re: 3.0 Questions Reply-To: "John C. Place" References: <362C93C1.C81CF9AB@whro.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: <362C93C1.C81CF9AB@whro.org>; from Bob Boone on Tue, Oct 20, 1998 at 09:44:33AM -0400 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Oct 20, 1998 at 09:44:33AM -0400, Bob Boone wrote: > Hi, > > This is the only FreeBSD list I receive, so I need to ask three > questions. > > I just built a new webserver Thursday last, from boot.flp/2.2.7, only > to find 3.0 released on Friday. > (1) Do I need / how do I get a "boot.flp" that will build 3.0 instead of > 2.2.7, so I can nuke the Thursday build and start over?? > Use dd to copy boot.flp to a boot floppy this can be gotten from the floppies directory in the dist. > (2) Do I WANT to move to 3.0 -- is it stable/tested enough for the > "brain trust" to feel comfortable with it for a low/moderate traffic > webserver ?? > It is my understanding that this is release quality BUT it is not considered stable. Stable is currently 2.2.7. Sometime in November 2.2.8 is suposed to finish out the 2-2-Stable Branch. When I say 3.0 is not stable I am merely speaking to the classifaction that the FreeBSD team gives to it. Stable refers to it being stable enough to be used on Mission Critical systems. 3.0 is Release which means that it *could* have some bugs but these prove to be minor ones usually. It has been my experence that Release quality is more stable than most other commerical OSs that claim to be bullet Proof. I am currently running 2.2.7 and am quite happy with it. I usually "play" with the Releases but depend on the Stable branch for work. I can say to date I have never been burned by a Release but none the less I am catious. > (3) I'm rebuilding THIS server because I was nuked thru the mail/buffer > overflow hack, but I'm reading that it isn't just popper... that several > pop3 and imap servers will break, and that only sendmail 8.9.1 with the > 1a patch will stop it.... CAN I ADD the sendmail 8.9.1 without breaking > something else ??? are there dependencies in 8.9.1 that either 2.2.7 or > 3.0 won't support ???? > I can speak to that however I would be suprised if it fails. Good Luck John To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Oct 20 09:54:32 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA07741 for freebsd-stable-outgoing; Tue, 20 Oct 1998 09:54:32 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from rtso200.ruraltel.net (rtso200.ruraltel.net [24.225.0.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA07723 for ; Tue, 20 Oct 1998 09:54:20 -0700 (PDT) (envelope-from dlhoar@ruraltel.net) Received: from jupiter ([24.225.5.168]) by rtso200.ruraltel.net (Post.Office MTA v3.1.2 release (PO203-101c) ID# 613-55232U7000L600S0V35) with SMTP id AAA2920 for ; Tue, 20 Oct 1998 11:53:36 -0500 From: dlhoar@ruraltel.net (Darryl Hoar) To: Subject: IP Addresses Date: Tue, 20 Oct 1998 11:54:08 -0000 Message-ID: <000501bdfc20$5b6a7b60$070101c0@jupiter> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook 8.5, Build 4.71.2173.0 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3 Importance: Normal Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I have read somewhere (I'm getting old and forget), that there are a set of defined IP addresses for people to use on their LANS. This is when you are not going to try and register IP's, etc. I have been using an network address 192.1.1.X, but with my FreeBSD 2.2.6 machine which is doing ppp -auto -alias, it looks up some of the addresses and shows the real name on the internet. IE, netstat -r shows TBN2000.COLUMBIA.BBN.COM as one of our local hosts. I definitely don't want that, so have decided to use the proper IP addresses for someone in our boat. Thanks in advance, Darryl To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Oct 20 10:09:12 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA08992 for freebsd-stable-outgoing; Tue, 20 Oct 1998 10:09:12 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from the.oneinsane.net (gw.oneinsane.net [207.113.133.226]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA08987 for ; Tue, 20 Oct 1998 10:09:09 -0700 (PDT) (envelope-from insane@the.oneinsane.net) Received: (from insane@localhost) by the.oneinsane.net (8.9.0/8.9.0) id KAA07535; Tue, 20 Oct 1998 10:07:36 -0700 (PDT) Message-ID: <19981020100736.A7413@oneinsane.net> Date: Tue, 20 Oct 1998 10:07:36 -0700 From: "Ron 'The Insane One' Rosson" To: Darryl Hoar Cc: freebsd-stable@FreeBSD.ORG Subject: Re: IP Addresses Reply-To: insane@oneinsane.net References: <000501bdfc20$5b6a7b60$070101c0@jupiter> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <000501bdfc20$5b6a7b60$070101c0@jupiter>; from Darryl Hoar on Tue, Oct 20, 1998 at 11:54:08AM -0000 X-Operating-System: FreeBSD the.oneinsane.net 2.2.7-STABLE X-Opinion: What you read here is my IMHO X-Disclaimer: I am a firm believer in RTFM X-WWW: http://www.oneinsane.net Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Darryl Here are the address space listed for non INTERNET use. 192.168.0.0/16 172.16.0.0/12 10.0.0.0/8 These addresses are also specified in RFC1918. Hope this helps Ron On Tue, Oct 20, 1998 at 11:54:08AM -0000, Darryl Hoar wrote: > I have read somewhere (I'm getting old and forget), that there are > a set of defined IP addresses for people to use on their LANS. This > is when you are not going to try and register IP's, etc. I have been > using an network address 192.1.1.X, but with my FreeBSD 2.2.6 machine > which is doing ppp -auto -alias, it looks up some of the addresses and > shows the real name on the internet. IE, > > netstat -r shows > > TBN2000.COLUMBIA.BBN.COM as one of our local hosts. I definitely don't want > that, so > have decided to use the proper IP addresses for someone in our boat. > -- ------------------------------------------------------------------- Ron Rosson ... and a UNIX user said ... The InSaNe One rm -rf * insane@oneinsane.net and all was null and void ------------------------------------------------------------------- It's so nice to be insane, nobody asks you to explain. [----------------------------System Info---------------------------] 10:04AM up 7 days, 55 mins, 4 users, load averages: 0.65, 0.69, 0.72 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Oct 20 10:19:22 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA09751 for freebsd-stable-outgoing; Tue, 20 Oct 1998 10:19:22 -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 KAA09746 for ; Tue, 20 Oct 1998 10:19:20 -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 0zVfPO-0000If-00; Tue, 20 Oct 1998 10:17:22 -0700 Date: Tue, 20 Oct 1998 10:17:20 -0700 (PDT) From: Tom X-Sender: tom@shell.uniserve.ca To: Bart Lindsey cc: bm@malepartus.de, freebsd-stable@FreeBSD.ORG Subject: Re: ECC memory support In-Reply-To: <199810201305.XAA01587@burra.zip.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 Tue, 20 Oct 1998, Bart Lindsey wrote: > Hi Burkard, > > ECC occurs between the memory modules and the motherboard. The kernel doesn't > get involved and the process is transparent to the kernel. The kernel is involved, as it will handle the NMI generated by the memory fault, and panic the system, which hopefully cleanly restart the system. Also, some systems can do more with the NMI, like shutdown whatever was contained in the bad location. FreeBSD doesn't do this. FreeBSD just calls panic. > The PC architecture doesn't handle memory problems very nicely and typically > the CPU resets without warning or just freezes without the kernel having any > opportunity to trap an error. Only on non-ECC or non-parity systems where the system will run through bad memory. > Depending on the revision of your motherboard, you might have to download > the bios patch described at URL: > > http://www.asus.com/downloads/bios/Jbios.asp?Motherboard=P/I-P55T2P4S#instructions > > There are two factors mentioned which can cause parity errors: > 1. PS2 mouse installed or > 2. AMD K6 installed and ECC/parity enabled. > > Good Luck! > > Bart. Tom To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Oct 20 10:27:35 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA10361 for freebsd-stable-outgoing; Tue, 20 Oct 1998 10:27:35 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from spawn.nectar.com (spawn.nectar.com [204.27.67.86]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA10356 for ; Tue, 20 Oct 1998 10:27:34 -0700 (PDT) (envelope-from nectar@spawn.nectar.com) Received: from localhost.nectar.com ([127.0.0.1] helo=spawn.nectar.com) by spawn.nectar.com with esmtp (Exim 1.92 #1) id 0zVfYT-0005yq-00; Tue, 20 Oct 1998 12:26:45 -0500 X-Mailer: exmh version 2.0.2 2/24/98 X-PGP-RSAfprint: 00 F9 E6 A2 C5 4D 0A 76 26 8B 8B 57 73 D0 DE EE X-PGP-RSAkey: http://www.nectar.com/nectar-pgp262.txt From: Jacques Vidrine In-reply-to: <000501bdfc20$5b6a7b60$070101c0@jupiter> References: <000501bdfc20$5b6a7b60$070101c0@jupiter> Subject: Re: IP Addresses To: dlhoar@ruraltel.net (Darryl Hoar) cc: stable@FreeBSD.ORG Date: Tue, 20 Oct 1998 12:26:45 -0500 Message-Id: Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG -----BEGIN PGP SIGNED MESSAGE----- ftp://www.arin.net/rfc/rfc1918.txt Jacques Vidrine / n@nectar.com / nectar@FreeBSD.org On 20 October 1998 at 11:54, dlhoar@ruraltel.net (Darryl Hoar) wrote: > I have read somewhere (I'm getting old and forget), that there are > a set of defined IP addresses for people to use on their LANS. This > is when you are not going to try and register IP's, etc. I have been > using an network address 192.1.1.X, but with my FreeBSD 2.2.6 machine > which is doing ppp -auto -alias, it looks up some of the addresses and > shows the real name on the internet. IE, > > netstat -r shows > > TBN2000.COLUMBIA.BBN.COM as one of our local hosts. I definitely don't want > that, so > have decided to use the proper IP addresses for someone in our boat. > > Thanks in advance, > > Darryl > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message > -----BEGIN PGP SIGNATURE----- Version: 2.6.2 iQCVAwUBNizH1TeRhT8JRySpAQGyawQAnaPL50lmZFlGHflHv7l3mAwZ5kAVN8Ao 3fJZBktT9ELHMGiNZIOaYoJmqArav7Gq4t5ElpePAwxCGikHrNyyi2OeZKEN2zn+ 0Ve2ZV182emT6/qpoXEJ+S9cmRGMsBDW4+W77egHtpKFwrlgdBVS+s37wg7ShA7x jizkQLylMT0= =H+GV -----END PGP SIGNATURE----- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Oct 20 10:36:49 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA11422 for freebsd-stable-outgoing; Tue, 20 Oct 1998 10:36:49 -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 KAA11416 for ; Tue, 20 Oct 1998 10:36:48 -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 0zVfhg-0002L0-00; Tue, 20 Oct 1998 10:36:16 -0700 Date: Tue, 20 Oct 1998 10:36:15 -0700 (PDT) From: Tom X-Sender: tom@shell.uniserve.ca To: Bob Boone cc: "freebsd-stable@FreeBSD.ORG" Subject: Re: 3.0 Questions In-Reply-To: <362C93C1.C81CF9AB@whro.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 Tue, 20 Oct 1998, Bob Boone wrote: > Hi, > > This is the only FreeBSD list I receive, so I need to ask three > questions. This is not the right list for 3.0 questions. > I just built a new webserver Thursday last, from boot.flp/2.2.7, only > to find 3.0 released on Friday. > (1) Do I need / how do I get a "boot.flp" that will build 3.0 instead of > 2.2.7, so I can nuke the Thursday build and start over?? Yes, the 3.0 boot disk is very different. Every release has its own boot disk. 2.2.8 will be the next release. > (2) Do I WANT to move to 3.0 -- is it stable/tested enough for the > "brain trust" to feel comfortable with it for a low/moderate traffic > webserver ?? From what you indicating to me, definitely not. > (3) I'm rebuilding THIS server because I was nuked thru the mail/buffer > overflow hack, but I'm reading that it isn't just popper... that several > pop3 and imap servers will break, and that only sendmail 8.9.1 with the > 1a patch will stop it.... CAN I ADD the sendmail 8.9.1 without breaking > something else ??? are there dependencies in 8.9.1 that either 2.2.7 or > 3.0 won't support ???? It just is just qpopper and UW-imap. Sendmail 8.9.1 has ways of blocking out messages that exploit overrun bugs, but if you are still running old qpopper and/or UW-imap, you are still going to get screwed. The overrun protection in Sendmail is just a bandaid. You can install 8.9.1 on any version of FreeBSD version easily. > Thanks, > > Bob Boone > bboone@whro.org Tom To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Oct 20 13:25:03 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA28786 for freebsd-stable-outgoing; Tue, 20 Oct 1998 13:25:03 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from dt053nb4.san.rr.com (dt053nb4.san.rr.com [204.210.34.180]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA28780 for ; Tue, 20 Oct 1998 13:25:02 -0700 (PDT) (envelope-from Studded@gorean.org) Received: from gorean.org (Studded@localhost [127.0.0.1]) by dt053nb4.san.rr.com (8.8.8/8.8.8) with ESMTP id NAA04014; Tue, 20 Oct 1998 13:24:32 -0700 (PDT) (envelope-from Studded@gorean.org) Message-ID: <362CF180.9A18CB84@gorean.org> Date: Tue, 20 Oct 1998 13:24:32 -0700 From: Studded Organization: Triborough Bridge & Tunnel Authority X-Mailer: Mozilla 4.5b2 [en] (X11; I; FreeBSD 2.2.7-STABLE-1015 i386) X-Accept-Language: en MIME-Version: 1.0 To: Bob Boone CC: "freebsd-stable@FreeBSD.ORG" Subject: Re: 3.0 Questions References: <362C93C1.C81CF9AB@whro.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Bob Boone wrote: > (2) Do I WANT to move to 3.0 No. 3.0 is not -Stable OR stable. > (3) I'm rebuilding THIS server because I was nuked thru the mail/buffer > overflow hack, but I'm reading that it isn't just popper... Which exact hack are you referring to, what exactly happened to your system, and where can we all read about this? It's hard to answer your question without more detail. Doug -- *** Chief Operations Officer, DALnet IRC network *** Go PADRES! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Oct 20 13:27:04 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA28985 for freebsd-stable-outgoing; Tue, 20 Oct 1998 13:27:04 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from austin.polstra.com (austin.polstra.com [206.213.73.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA28980 for ; Tue, 20 Oct 1998 13:27:02 -0700 (PDT) (envelope-from jdp@austin.polstra.com) Received: from austin.polstra.com (jdp@localhost) by austin.polstra.com (8.9.1/8.9.1) with ESMTP id NAA06300; Tue, 20 Oct 1998 13:26:30 -0700 (PDT) (envelope-from jdp) Message-Id: <199810202026.NAA06300@austin.polstra.com> To: gavin@itworks.com.au Subject: Re: cvsuping -STABLE In-Reply-To: References: Organization: Polstra & Co., Seattle, WA Cc: stable@FreeBSD.ORG Date: Tue, 20 Oct 1998 13:26:30 -0700 From: John Polstra Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article , Gavin Cameron wrote: > I just CVSuped (well a couple of hours ago) and I checked out RELENG_2_2 > hoping to get the latest and greatest. > > The Makefile in /usr/src is version 1.109.2.31. If I go into the > repository and have a look at Makefile,v I see the following > > symbols > RELENG_3_0_0_RELEASE:1.220 > RELENG_2_2_7_RELEASE:1.109.2.33 > RELENG_2_2_6_RELEASE:1.109.2.25 > RELENG_2_2_5_RELEASE:1.109.2.19 > RELENG_2_2_2_RELEASE:1.109.2.4 > RELENG_2_2_1_RELEASE:1.109.2.2 > RELENG_2_2_0_RELEASE:1.109.2.2 > RELENG_2_1_7_RELEASE:1.57.4.19 > RELENG_2_1_6_1_RELEASE:1.57.4.19 > RELENG_2_1_6_RELEASE:1.57.4.19 > RELENG_2_2:1.109.0.2 > > Which, I think, tells me that if I was infact checking out RELENG_2_2, I > should have got the Makefile that is of a later version than 2.2.7 > release (or atleast that version). As far as I can tell, checking out > RELENG_2_2 gives me a Makefile from before 2.2.7 was released. This also > makes me wonder if all the source code I've checked out is old. > > So, my question is, do I still use the RELENG_2_2 tag to checkout the > stable branch? and if I do, why don't I have the right Makefile checked > out. Oops, sorry, it has been pointed out to me that I didn't read the question carefully enough before replying the last time. Let me try again. Yes, you should have gotten something later than 1.109.2.33. To find out why you didn't, you're going to have to provide more information. For starters, please send me the cvsupfile that you used when you ran CVSup. John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Nobody ever went broke underestimating the taste of the American public." -- H. L. Mencken To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Oct 20 13:27:36 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA29037 for freebsd-stable-outgoing; Tue, 20 Oct 1998 13:27:36 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from dt053nb4.san.rr.com (dt053nb4.san.rr.com [204.210.34.180]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA29030 for ; Tue, 20 Oct 1998 13:27:32 -0700 (PDT) (envelope-from Studded@gorean.org) Received: from gorean.org (Studded@localhost [127.0.0.1]) by dt053nb4.san.rr.com (8.8.8/8.8.8) with ESMTP id NAA04024; Tue, 20 Oct 1998 13:26:56 -0700 (PDT) (envelope-from Studded@gorean.org) Message-ID: <362CF20F.5542DC@gorean.org> Date: Tue, 20 Oct 1998 13:26:55 -0700 From: Studded Organization: Triborough Bridge & Tunnel Authority X-Mailer: Mozilla 4.5b2 [en] (X11; I; FreeBSD 2.2.7-STABLE-1015 i386) X-Accept-Language: en MIME-Version: 1.0 To: Petrov Enrico CC: "'freebsd-stable@freebsd.org'" Subject: Re: Problem from 2.2.1 to 3.0 FreeBSD RELEASE References: <69A4AB2CD710D211A0AF00805FA6EAF10F9F57@xrr3.cselt.stet.it> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Petrov Enrico wrote: > > I'm trying to migrate from 2.2.1 to 3.0 RELEASE. First question, why are you doing that? 3.0 is not stable, and you probably shouldn't be running it. Also, 2.2.1 -> 3.0 won't work. If you're determined to run 3.0 for some reason you should upgrade to 2.2.7-Stable first, then to 3.0. > If this is the right mailing list, can someone help me? It's not the right mailing list. You should be subscribed to freebsd-current for at least a month before considering an upgrade to 3.0. Doug -- *** Chief Operations Officer, DALnet IRC network *** Go PADRES! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Oct 20 17:39:08 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA23192 for freebsd-stable-outgoing; Tue, 20 Oct 1998 17:39:08 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from mail.HiWAAY.net (fly.HiWAAY.net [208.147.154.56]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA23187 for ; Tue, 20 Oct 1998 17:39:07 -0700 (PDT) (envelope-from dkelly@n4hhe.ampr.org) Received: from nospam.hiwaay.net (tnt3-181.HiWAAY.net [208.147.146.181]) by mail.HiWAAY.net (8.9.0/8.9.0) with ESMTP id TAA31495 for ; Tue, 20 Oct 1998 19:38:39 -0500 (CDT) Received: from n4hhe.ampr.org (localhost.ampr.org [127.0.0.1]) by nospam.hiwaay.net (8.8.8/8.8.8) with ESMTP id TAA06684 for ; Tue, 20 Oct 1998 19:38:37 -0500 (CDT) (envelope-from dkelly@n4hhe.ampr.org) Message-Id: <199810210038.TAA06684@nospam.hiwaay.net> X-Mailer: exmh version 2.0.2 2/24/98 To: freebsd-stable@FreeBSD.ORG From: David Kelly Subject: Re: ECC memory support In-reply-to: Message from Bart Lindsey of "Tue, 20 Oct 1998 23:05:01 +1000." <199810201305.XAA01587@burra.zip.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 20 Oct 1998 19:38:37 -0500 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Bart Lindsey writes: > Hi Burkard, > > ECC occurs between the memory modules and the motherboard. The kernel doesn't > get involved and the process is transparent to the kernel. Granted. But I think the original question was asking if there a reporting mechanism by which one could be notified if the ECC hardware decided to correct a bit? Searching the kernel, I haven't found any mention. Haven't downloaded whatever docs Intel offers on Pentium and PPro chipsets to see if there is any way to report an ECC event. > The PC architecture doesn't handle memory problems very nicely and typically > the CPU resets without warning or just freezes without the kernel having any > opportunity to trap an error. On ECC the MB should correct a single bit error and keep on trucking. No kernel or BIOS intervention. But it sure would be Just Like A Real Computer if one could log the ECC event via syslog. If ECC is correcting bits and keeping my computer running but not telling me, its not doing me huge amount of good. If it corrects only on bit per couple of months then it is doing good work. But if I really have a bad bit and ECC corrects it every time its used, I'd like to know about it and get a replacement memory SIMM. -- David Kelly N4HHE, dkelly@nospam.hiwaay.net ===================================================================== The human mind ordinarily operates at only ten percent of its capacity -- the rest is overhead for the operating system. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Oct 20 22:13:58 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA17352 for freebsd-stable-outgoing; Tue, 20 Oct 1998 22:13:58 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from jason01.u.washington.edu (jason01.u.washington.edu [140.142.70.24]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA17344 for ; Tue, 20 Oct 1998 22:13:57 -0700 (PDT) (envelope-from jcwells@u.washington.edu) Received: from saul5.u.washington.edu (root@saul5.u.washington.edu [140.142.83.3]) by jason01.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id WAA43280 for ; Tue, 20 Oct 1998 22:13:30 -0700 Received: from S8-37-26.student.washington.edu (S8-37-26.student.washington.edu [128.208.37.26]) by saul5.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id WAA16429 for ; Tue, 20 Oct 1998 22:13:29 -0700 (PDT) Date: Tue, 20 Oct 1998 22:13:19 -0700 (PDT) From: "Jason C. Wells" X-Sender: jason@s8-37-26.student.washington.edu Reply-To: "Jason C. Wells" To: FreeBSD-stable Subject: ELF binary type "Linux" not known 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 running 3.0-RELEASE with a fresh kernel that has 'options LINUX' and 'options COMPAT_LINUX'. I updated my ports a couple days ago. During 'make install' of linux_lib-2.5 I recieved 'Elf binary type "Linux" no known, Error code 6 ignored. I would ignore it too except that I can't get acroread going. Is there something new I need to do in 3.0 to Linuxulate my machine? Catchya Later, | UW Mechanical Engineering Jason Wells | http://weber.u.washington.edu/~jcwells/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Oct 21 06:23:36 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA15698 for freebsd-stable-outgoing; Wed, 21 Oct 1998 06:23:36 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from tibatong.ihf.rwth-aachen.de (tibatong.ihf.RWTH-Aachen.DE [134.130.90.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA15662; Wed, 21 Oct 1998 06:23:16 -0700 (PDT) (envelope-from tg@tibatong.ihf.rwth-aachen.de) Received: (from tg@localhost) by tibatong.ihf.rwth-aachen.de (8.8.8/8.8.8) id OAA01865; Wed, 21 Oct 1998 14:13:21 +0200 (CEST) (envelope-from tg) To: stable@FreeBSD.ORG Cc: jb@FreeBSD.ORG Subject: Merge libc_r from -current Mime-Version: 1.0 (generated by tm-edit 7.108) Content-Type: text/plain; charset=US-ASCII From: Thomas Gellekum Date: 21 Oct 1998 14:13:21 +0200 Message-ID: <877lxuqfj2.fsf@tibatong.ihf.rwth-aachen.de> Lines: 11 X-Mailer: Gnus v5.6.34/XEmacs 20.4 - "Emerald" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Moin, I'd like to merge the pthreads implementation from -current. Could someone please check the diffs in http://www.freebsd.org/~tg/threads-stable.diff.gz? The remaining differences to -current are due to the lack of realtime scheduling. Everything else (better performance, better standard compliance, FILE* based locks, bug fixes) should be there. tg To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Oct 21 06:44:56 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA19116 for freebsd-stable-outgoing; Wed, 21 Oct 1998 06:44:56 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from haldjas.folklore.ee (Haldjas.folklore.ee [193.40.6.121]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA19085 for ; Wed, 21 Oct 1998 06:44:39 -0700 (PDT) (envelope-from narvi@haldjas.folklore.ee) Received: from haldjas.folklore.ee (haldjas.folklore.ee [172.17.2.1] (may be forged)) by haldjas.folklore.ee (8.8.8/8.8.4) with SMTP id PAA18595; Wed, 21 Oct 1998 15:12:29 +0300 (EEST) Date: Wed, 21 Oct 1998 15:12:29 +0300 (EEST) From: Narvi To: Shawn Ramsey cc: Harold Gutch , stable@FreeBSD.ORG Subject: Re: /usr/obj In-Reply-To: <19981019210121.48459@cpl.net> 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, 19 Oct 1998, Shawn Ramsey wrote: > > Symlinking (ln -s <...>) should work, you're not trying to > > hardlink, are you ? > > From the ln(1) manpage: > > Hard links may > > not normally refer to directories and may not span file systems. > > > > I am using ln -s. "ln -s /disk4/obj obj" is the command I used. Are there > any special permissions that the /disk4/obj directory would require? > Naturally, you need be able to write to it. Sander There is no love, no good, no happiness and no future - all these are just illusions. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Oct 21 09:20:20 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA05839 for freebsd-stable-outgoing; Wed, 21 Oct 1998 09:20:20 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from jason03.u.washington.edu (jason03.u.washington.edu [140.142.77.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA05832 for ; Wed, 21 Oct 1998 09:20:19 -0700 (PDT) (envelope-from jcwells@u.washington.edu) Received: from saul9.u.washington.edu (root@saul9.u.washington.edu [140.142.82.7]) by jason03.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id JAA21180; Wed, 21 Oct 1998 09:19:51 -0700 Received: from S8-37-26.student.washington.edu (S8-37-26.student.washington.edu [128.208.37.26]) by saul9.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id JAA31301; Wed, 21 Oct 1998 09:19:50 -0700 (PDT) Date: Wed, 21 Oct 1998 09:19:33 -0700 (PDT) From: "Jason C. Wells" X-Sender: jason@s8-37-26.student.washington.edu Reply-To: "Jason C. Wells" To: "Norman C. Rice" cc: FreeBSD-stable Subject: Re: ELF binary type "Linux" not known In-Reply-To: <19981021013305.A23639@emu.sourcee.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 Wed, 21 Oct 1998, Norman C. Rice wrote: >Did you set linux_enable="YES" in /etc/rc.conf? Thanks for the help. Turns out, the whole thing was pilot error. "options COMAPT_LINUX" doesn't work like it used to work. :) Sorry to bother you all. Catchya Later, | UW Mechanical Engineering Jason Wells | http://weber.u.washington.edu/~jcwells/ JW2691 | 206-633-5994 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Oct 21 09:29:37 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA06801 for freebsd-stable-outgoing; Wed, 21 Oct 1998 09:29:37 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from axl.training.iafrica.com (axl.training.iafrica.com [196.31.1.175]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA06784 for ; Wed, 21 Oct 1998 09:29:21 -0700 (PDT) (envelope-from sheldonh@axl.training.iafrica.com) Received: from sheldonh (helo=iafrica.com) by axl.training.iafrica.com with local-esmtp (Exim 2.05 #1) id 0zW17w-0001GT-00 for freebsd-stable@freebsd.org; Wed, 21 Oct 1998 18:28:48 +0200 From: Sheldon Hearn To: freebsd-stable@FreeBSD.ORG Subject: Re: i386/7695: rc.i386 only enables mouse support for ttyv0 Date: Wed, 21 Oct 1998 18:28:48 +0200 Message-ID: <4864.908987328@iafrica.com> Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Submitted as followup to PR7695 on Tue, 29 Sep 1998 11:32:51 +0200: Having done a little more research, I now know that -CURRENT already has a knob in rc.conf and some magic in rc.i386 to do vidcontrol stuff to all virtual terminals. The appropriate code has had 8 months to mature in -CURRENT, I think it's ready for an MFC. :-) I've tested the patches that were applied to the -CURRENT branch, and they apply perfectly to the -STABLE sources now. I've tested them on my 2.2-STABLE box with no ill effects. The diffs are attached below, for your convenience. Ciao, Sheldon. Index: rc.conf =================================================================== RCS file: /home/ncvs/src/etc/rc.conf,v retrieving revision 1.41 retrieving revision 1.43 diff -u -d -r1.41 -r1.43 --- rc.conf 1998/03/09 08:50:27 1.41 +++ rc.conf 1998/04/02 15:33:36 1.43 @@ -124,6 +124,7 @@ moused_type="auto" # See man page for rc.conf(5) for available settings. moused_port="/dev/cuaa0" # Set to your mouse port. moused_flags="" # Any additional flags to moused. +allscreens_flags="" # Set this vidcontrol mode for all virtual screens ############################################################## Index: etc.i386/rc.i386 =================================================================== RCS file: /home/ncvs/src/etc/etc.i386/rc.i386,v retrieving revision 1.32 retrieving revision 1.34 diff -u -d -r1.32 -r1.34 --- rc.i386 1998/03/07 09:02:08 1.32 +++ rc.i386 1998/04/02 15:33:49 1.34 @@ -103,6 +103,15 @@ echo -n ' moused' moused ${moused_flags} -p ${moused_port} -t ${moused_type} vidcontrol <${viddev} -m on +fi + +# set this mode for all virtual screens +if [ "X${allscreens_flags}" != X"" ] ; then + echo -n ' allscreens' + for ttyv in /dev/ttyv* + do + vidcontrol <$ttyv ${allscreens_flags} + done fi echo '.' To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Oct 21 10:18:33 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA12698 for freebsd-stable-outgoing; Wed, 21 Oct 1998 10:18:33 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from sussie.datadesign.se (ns.datadesign.se [194.23.109.130]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA12690 for ; Wed, 21 Oct 1998 10:18:30 -0700 (PDT) (envelope-from kaj@interbizz.se) Received: from localhost (sussie.datadesign.se [194.23.109.130]) by sussie.datadesign.se (8.8.5/8.8.7) with ESMTP id TAA17333; Wed, 21 Oct 1998 19:17:30 +0200 (MET DST) To: jdp@polstra.com Cc: dom@phmit.demon.co.uk, stable@FreeBSD.ORG Cc: kaj@interbizz.se Subject: Re: -stable to 3.0 transition From: Rasmus Kaj In-Reply-To: Your message of "Mon, 19 Oct 1998 09:22:38 -0700" <199810191622.JAA13720@austin.polstra.com> References: <199810191622.JAA13720@austin.polstra.com> X-Mailer: Mew version 1.92.4 on XEmacs 20.4 (Emerald) X-URL: http://www.e.kth.se/~kaj/ X-Phone: +46 (0)8 - 692 35 09 / +46 (0)70 640 49 14 X-Attribution: Kaj X-Face: M9cR~WYav<"fu%MaslX0`43PAYY?uIsM8[#E(0\Xuy9rj>4gE\h3jm.7DD?]R8*^7T\o&vT U@[53Dwkuup4[0@gw#~kyu>`unH?kVj9CJa02(h>Ki\+i=%rn%sDf^KC.!?IHkKjMAbkd\jgmphp^' d|Q;OeXEAhq?ybGqOs1CHb6TJT42'C`Krnk61//AOfXtNjj/t'`5>Vw0QX!dKfOL$.f+S"LIuwR<;I Z0Qnnx(F^F]o@*V%TUtEV'1Z[TkOl^FFV9Z~A[b19%}uP*,huCU Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <19981021191729T.kaj@interbizz.se> Date: Wed, 21 Oct 1998 19:17:29 +0200 X-Dispatcher: imput version 971024 Lines: 18 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >>>>> "JP" == John Polstra writes: >> How long will a.out builds be supported for? JP> I would expect them to be phased out before the next release of JP> 3.x.x. We are trying to make a point of _not_ becoming a "pick JP> your favorite object format" OS. Wouldn't the next release of 3.x.x (or even a later release) be the first release of 3...-stable? It would be nice to have ELF support in -stable for at least a month or so of cvsup before phasing out a.out. // Rasmus -- kaj@cityonline.se --------------- Rasmus Kaj - http://www.e.kth.se/~kaj/ \ CityOnLine IB Production AB - http://www.CityOnLine.se/ \- If you think I'm talking about the future you're living in the past To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Oct 21 11:12:19 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA18615 for freebsd-stable-outgoing; Wed, 21 Oct 1998 11:12:19 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from awfulhak.org (awfulhak.force9.co.uk [195.166.136.63]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA18552 for ; Wed, 21 Oct 1998 11:12:11 -0700 (PDT) (envelope-from brian@Awfulhak.org) Received: from woof.lan.awfulhak.org (brian@woof.lan.awfulhak.org [172.16.0.7]) by awfulhak.org (8.8.8/8.8.8) with ESMTP id TAA03631; Wed, 21 Oct 1998 19:11:37 +0100 (BST) (envelope-from brian@Awfulhak.org) Received: from woof.lan.awfulhak.org (brian@localhost [127.0.0.1]) by woof.lan.awfulhak.org (8.9.1/8.9.1) with ESMTP id LAA01110; Wed, 21 Oct 1998 11:33:56 +0100 (BST) (envelope-from brian@woof.lan.awfulhak.org) Message-Id: <199810211033.LAA01110@woof.lan.awfulhak.org> X-Mailer: exmh version 2.0.2 2/24/98 To: insane@oneinsane.net cc: Darryl Hoar , freebsd-stable@FreeBSD.ORG Subject: Re: IP Addresses In-reply-to: Your message of "Tue, 20 Oct 1998 10:07:36 PDT." <19981020100736.A7413@oneinsane.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 21 Oct 1998 11:33:56 +0100 From: Brian Somers Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Darryl > > Here are the address space listed for non INTERNET use. > 192.168.0.0/16 > 172.16.0.0/12 > 10.0.0.0/8 > > These addresses are also specified in RFC1918. And for convenience, they're also mentioned in /etc/hosts :-) > Hope this helps > Ron -- Brian , , Don't _EVER_ lose your sense of humour.... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Oct 21 11:32:28 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA21149 for freebsd-stable-outgoing; Wed, 21 Oct 1998 11:32:28 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from mail.double-barrel.be (mail.double-barrel.be [194.7.102.20]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA21137 for ; Wed, 21 Oct 1998 11:32:19 -0700 (PDT) (envelope-from mvergall@mail.double-barrel.be) Received: (from uucp@localhost) by mail.double-barrel.be (8.9.1/8.8.8) id UAA09362; Wed, 21 Oct 1998 20:30:23 +0200 (CEST) (envelope-from mvergall@mail.double-barrel.be) Received: from ns.double-barrel.be(194.7.102.18) via SMTP by mail.double-barrel.be, id smtpdit9360; Wed Oct 21 20:30:20 1998 Date: Wed, 21 Oct 1998 20:30:10 +0200 (CEST) From: "Michael C. Vergallen" X-Sender: mvergall@ns.double-barrel.be To: Cy Schubert - ITSD Open Systems Group cc: freebsd-stable@FreeBSD.ORG Subject: Re: After installing W95 bootmgr failed ... In-Reply-To: <199810171449.HAA14703@cwsys.cwsent.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 Hi, Thanks to all for their advice. I found the util in the tools dir off ftp.freebsd.org and it is simple enough. Michael --- Michael C. Vergallen A.k.A. Mad Mike, Sportstraat 28 http://www.double-barrel.be/mvergall/ B 9000 Gent ftp://ftp.double-barrel.be/pub/linux/ Belgium tel : 32-9-2227764 Fax : 32-9-2224976 On Sat, 17 Oct 1998, Cy Schubert - ITSD Open Systems Group wrote: > You will need to reinstall the booteasy MBR. W95 performs an fdisk > /mbr during its install. Whenever possible, always install the MS O/S > first then non-MS O/S's. > > The Minix fdisk will save the MBR to a file. One could use it or save > the MBR using dd, install an MS O/S, and restore the MBR. > > > Regards, Phone: (250)387-8437 > Cy Schubert Fax: (250)387-5766 > Open Systems Group Internet: cschuber@uumail.gov.bc.ca > ITSD Cy.Schubert@gems8.gov.bc.ca > Government of BC > > > However I've been able to boot freeBSD from slice 2 without a bootmgr by > > just switching the activated partition and then rerun sysinstall and all > > was okey again. > > > > Michael > > --- > > Michael C. Vergallen A.k.A. Mad Mike, > > Sportstraat 28 http://www.double-barrel.be/mvergall/ > > B 9000 Gent ftp://ftp.double-barrel.be/pub/linux/ > > Belgium tel : 32-9-2227764 Fax : 32-9-2224976 > > > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-stable" in the body of the message > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Oct 21 15:38:05 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA21481 for freebsd-stable-outgoing; Wed, 21 Oct 1998 15:38:05 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from the.oneinsane.net (gw.oneinsane.net [207.113.133.226]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA21475 for ; Wed, 21 Oct 1998 15:38:03 -0700 (PDT) (envelope-from insane@the.oneinsane.net) Received: (from insane@localhost) by the.oneinsane.net (8.9.0/8.9.0) id PAA01688 for freebsd-stable@freebsd.org; Wed, 21 Oct 1998 15:37:35 -0700 (PDT) Message-ID: <19981021153735.A569@oneinsane.net> Date: Wed, 21 Oct 1998 15:37:35 -0700 From: "Ron 'The Insane One' Rosson" To: freebsd-stable@FreeBSD.ORG Subject: System will not Complete Shutdown Reply-To: insane@oneinsane.net Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i X-Operating-System: FreeBSD the.oneinsane.net 2.2.7-STABLE X-Opinion: What you read here is my IMHO X-Disclaimer: I am a firm believer in RTFM X-WWW: http://www.oneinsane.net Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I Just built a new box that I am going to make sorta a Firewall/Gateway box. Here is the dmesg output. Copyright (c) 1992-1998 FreeBSD Inc. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 2.2.7-RELEASE #0: Tue Oct 20 21:16:40 PDT 1998 root@unused.oneinsane.net:/usr/src/sys/compile/FWGW CPU: i486 DX2 (486-class CPU) Origin = "GenuineIntel" Id = 0x435 Stepping=5 Features=0x3 real memory = 16777216 (16384K bytes) avail memory = 14577664 (14236K bytes) Probing for devices on the ISA bus: sc0 at 0x60-0x6f irq 1 on motherboard sc0: VGA color <16 virtual consoles, flags=0x0> ed0 at 0x280-0x29f irq 10 maddr 0xd8000 msize 16384 on isa ed0: address 00:00:c0:13:0b:5c, type WD8013EPC (16 bit) sio0 at 0x3f8-0x3ff irq 4 on isa sio0: type 16450 sio1: configured irq 3 not in bitmap of probed irqs 0 sio1 not found at 0x2f8 lpt0 at 0x3bc-0x3c3 irq 7 on isa lpt0: Interrupt-driven port lp0: TCP/IP capable interface fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa wdc0 at 0x1f0-0x1f7 irq 14 on isa wdc0: unit 0 (wd0): wd0: 405MB (830760 sectors), 989 cyls, 15 heads, 56 S/T, 512 B/S wdc1 not found at 0x170 npx0 flags 0x1 on motherboard npx0: INT 16 interface IP packet filtering initialized, divert enabled, logging limited to 250 packets/entry The system works fine untill I issue a shutdown -r now or reboot. The system appears to shutdown untill This is the last thing on the screen. Keyboard reset did not work, attempting CPU shutdown. When the above error message appears this is where a normal system would restart. This server will not have a keyboard so the BIOS is configured to not halt on the error when it can not find the keyboard. Any info on helping figure this out and get it resolved would be greatly appreciated. TIA Ron -- ------------------------------------------------------------------- Ron Rosson ... and a UNIX user said ... The InSaNe One rm -rf * insane@oneinsane.net and all was null and void ------------------------------------------------------------------- It's so nice to be insane, nobody asks you to explain. [----------------------------System Info---------------------------] 3:10PM up 8 days, 6:01, 4 users, load averages: 1.18, 1.01, 0.94 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Oct 21 18:44:07 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA10400 for freebsd-stable-outgoing; Wed, 21 Oct 1998 18:44:07 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from outmail.utsunomiya-u.ac.jp (outmail.utsunomiya-u.ac.jp [160.12.196.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA10394 for ; Wed, 21 Oct 1998 18:44:03 -0700 (PDT) (envelope-from yokota@zodiac.mech.utsunomiya-u.ac.jp) Received: from zodiac.mech.utsunomiya-u.ac.jp (IDENT:NKM5DBYph1gBaJcoO6jXX70Iaj8VR8gg@zodiac.mech.utsunomiya-u.ac.jp [160.12.42.1]) by outmail.utsunomiya-u.ac.jp (8.9.1/8.9.1) with ESMTP id KAA02635; Thu, 22 Oct 1998 10:43:23 +0900 (JST) Received: from zodiac.mech.utsunomiya-u.ac.jp (zodiac.mech.utsunomiya-u.ac.jp [160.12.42.1]) by zodiac.mech.utsunomiya-u.ac.jp (8.7.6+2.6Wbeta7/3.4W/zodiac-May96) with ESMTP id KAA09156; Thu, 22 Oct 1998 10:44:40 +0900 (JST) Message-Id: <199810220144.KAA09156@zodiac.mech.utsunomiya-u.ac.jp> To: insane@oneinsane.net cc: freebsd-stable@FreeBSD.ORG, yokota@zodiac.mech.utsunomiya-u.ac.jp Subject: Re: System will not Complete Shutdown In-reply-to: Your message of "Wed, 21 Oct 1998 15:37:35 MST." <19981021153735.A569@oneinsane.net> References: <19981021153735.A569@oneinsane.net> Date: Thu, 22 Oct 1998 10:44:40 +0900 From: Kazutaka YOKOTA Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >I Just built a new box that I am going to make sorta a >Firewall/Gateway box. Here is the dmesg output. [...] >The system works fine untill I issue a shutdown -r now or reboot. >The system appears to shutdown untill This is the last thing on the screen. > >Keyboard reset did not work, attempting CPU shutdown. The message has confused so many people in the past. I think we should change it to something more accurate and understandable... This message has NOTHING to do with the keyboard. It is saying that the kernel has failed to reset the CPU via the keyboard CONTROLLER on the motherboard. You always have a keyboard controller on the motherboard even if you don't have a keyboard attached to it. For reasons unintelligible to me, IBM decided to put the CPU reset circuit wired to the keyboard controller in the IBM AT computer. You are supposed to instruct the keyboard controller to reset the CPU when you want to restart the system. Unfortunately, the keyboard controller is one of peripheral chips which often have subtle compatibility problems. The FreeBSD kernel talks to the keyboard controller in order to reboot the system. If it finds the reset didn't work, it prints the above message. Please add the following option to your kernel configuration file, rebuild the kernel, and see if it works. options "BROKEN_KEYBOARD_RESET" Again this option name is confusing. It has NOTHING to do with resetting the keyboard. It is about resetting the CPU via the keyboard controller.... >When the above error message appears this is where a normal system would >restart. >This server will not have a keyboard so the BIOS is configured to not halt >on the error when it can not find the keyboard. > >Any info on helping figure this out and get it resolved would be greatly >appreciated. >TIA >Ron Kazu yokota@FreeBSD.ORG To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Oct 21 19:21:41 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA14322 for freebsd-stable-outgoing; Wed, 21 Oct 1998 19:21:41 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from austin.polstra.com (austin.polstra.com [206.213.73.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA14315 for ; Wed, 21 Oct 1998 19:21:39 -0700 (PDT) (envelope-from jdp@austin.polstra.com) Received: from austin.polstra.com (jdp@localhost) by austin.polstra.com (8.9.1/8.9.1) with ESMTP id TAA14379; Wed, 21 Oct 1998 19:21:03 -0700 (PDT) (envelope-from jdp) Message-Id: <199810220221.TAA14379@austin.polstra.com> To: Rasmus Kaj cc: stable@FreeBSD.ORG Subject: Re: -stable to 3.0 transition In-reply-to: Your message of "Wed, 21 Oct 1998 19:17:29 +0200." <19981021191729T.kaj@interbizz.se> Date: Wed, 21 Oct 1998 19:21:03 -0700 From: John Polstra Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > >> How long will a.out builds be supported for? > > JP> I would expect them to be phased out before the next release of > JP> 3.x.x. We are trying to make a point of _not_ becoming a "pick > JP> your favorite object format" OS. > > Wouldn't the next release of 3.x.x (or even a later release) be the > first release of 3...-stable? Yes, some future release on the 3.0 branch will become FreeBSD-stable. > It would be nice to have ELF support in -stable for at least a month > or so of cvsup before phasing out a.out. On the contrary, -stable is not the place for phasing things in or out. It's supposed to be, well ... "stable." The 3.0 branch won't become FreeBSD-stable until it is in really good shape. Even now, there are very very few problems in 3.0 that can be attributed to ELF. There are some broken ports (which are rapidly being fixed by our ports fixing _machine_ Steve Price and others), but that's about it. John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Nobody ever went broke underestimating the taste of the American public." -- H. L. Mencken To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Oct 22 07:54:51 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA08848 for freebsd-stable-outgoing; Thu, 22 Oct 1998 07:54:51 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from amalthea.salford.ac.uk (amalthea.salford.ac.uk [146.87.255.61]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id HAA08636 for ; Thu, 22 Oct 1998 07:52:25 -0700 (PDT) (envelope-from freebsd-stable-list@salford.ac.uk) From: freebsd-stable-list@salford.ac.uk Received: (qmail 12638 invoked by alias); 22 Oct 1998 14:51:26 -0000 Received: (qmail 12632 invoked from network); 22 Oct 1998 14:51:25 -0000 Received: from ananke.salford.ac.uk (146.87.255.67) by amalthea.salford.ac.uk with SMTP; 22 Oct 1998 14:51:25 -0000 Received: (qmail 15009 invoked by alias); 22 Oct 1998 14:51:23 -0000 Delivered-To: catchall-freebsd-stable@freebsd.org Received: (qmail 15001 invoked by uid 6); 22 Oct 1998 14:51:22 -0000 Message-ID: <19981022145122.15000.qmail@ananke.salford.ac.uk> Reply-To: mark@salfrd.ac.uk (Mark Powell) Subject: Re: int overflow in tar To: freebsd-stable@FreeBSD.ORG Date: 22 Oct 1998 15:51:19 +0100 X-Gated-To-News-By: NewsMaster X-Trace: ananke.salford.ac.uk 909067881 14997 146.87.255.76 (22 Oct 1998 14:51:21 GMT) X-Complaints-To: postmaster@salford.ac.uk Xref: ananke.salford.ac.uk salford.mailing-lists.freebsd.stable:7653 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article <70fko7$af8$1@ananke.salford.ac.uk>, Ben Stuyts wrote: >The gnu tar program included with FreeBSD has a tiny problem with the option >--totals. This option prints the total number of bytes written, but >unfortunately the counter used by tar (tot_written in tar.h) is an int. So it >overflows after 2^31 bytes have been written, like this: > >Backing up nemesis:/home3 at Mon Oct 19 13:27:43 CEST 1998 >... >Total bytes written: -1960021504 > >df /home3 shows: >Filesystem 1K-blocks Used Avail Capacity Mounted on >/dev/sd2s1f 3857506 2307663 1241243 65% /home3 > >Should I take this up with the people who maintain gnu tar, or is this >something we can fix in our source tree? > >Could there be more int overflow problems with tar? I use GNU tar v1.12 for my backups. It's available as a port in, /usr/ports/sysutils/gtar. Even that overflows under FreeBSD. However, when compiled under Solaris, it doesn't have the problem. -- Mark Powell - System Administrator (UNIX) - Clifford Whitworth Building A.I.S., University of Salford, Salford, Manchester, UK. Tel: +44 161 295 5936 Fax: +44 161 295 5888 Email: M.S.Powell@ais.salfrd.ac.uk finger mark@ucsalf.ac.uk (for PGP key) NO SPAM please: Spell salford correctly to reply to me. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Oct 22 09:19:48 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA16026 for freebsd-stable-outgoing; Thu, 22 Oct 1998 09:19:48 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from as5200-01-254.no.neosoft.com (as5200-01-254.no.neosoft.com [206.27.167.254]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA16021 for ; Thu, 22 Oct 1998 09:19:45 -0700 (PDT) (envelope-from conrads@as5200-01-254.no.neosoft.com) Received: (from conrads@localhost) by as5200-01-254.no.neosoft.com (8.9.1/8.9.1) id LAA20277; Thu, 22 Oct 1998 11:15:28 -0500 (CDT) (envelope-from conrads) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <69A4AB2CD710D211A0AF00805FA6EAF10F9F57@xrr3.cselt.stet.it> Date: Thu, 22 Oct 1998 11:15:27 -0500 (CDT) Reply-To: conrads@neosoft.com Organization: NeoSoft, Inc. From: Conrad Sabatier To: Petrov Enrico Subject: RE: Problem from 2.2.1 to 3.0 FreeBSD RELEASE Cc: "freebsd-stable@freebsd.org" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 20-Oct-98 Petrov Enrico wrote: > I'm trying to migrate from 2.2.1 to 3.0 RELEASE. > I've just downloaded 3.0 source tree. > If I type "make world" in /usr/src/ directory I find this error: > > [...] > cc -0 -pipe -I/usr/src/usr.bin/make > -I/usr/obj/aout/usr/src/tmp/usr/include -static -o make arch.o compat.o > .....[skipped] > main.o: Undefined symbol `_sysctlbyname` referenced from text > segment > *** Error code 1 > > What does it mean? > If this is the right mailing list, can someone help me? While I haven't actually examined all of the Makefiles for 3.0 completely to verify this, I suspect you'd be better off trying the "aout-to-elf-build" target (followed by "aout-to-elf-install") rather than "world", as this seems more tailored to those who are upgrading from an earlier version. -- Conrad Sabatier A witty saying proves nothing, but saying something pointless gets people's attention. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Oct 22 09:22:03 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA16442 for freebsd-stable-outgoing; Thu, 22 Oct 1998 09:22:03 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from labinfo.iet.unipi.it (labinfo.iet.unipi.it [131.114.9.5]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id JAA16329 for ; Thu, 22 Oct 1998 09:21:11 -0700 (PDT) (envelope-from luigi@labinfo.iet.unipi.it) Received: from localhost (luigi@localhost) by labinfo.iet.unipi.it (8.6.5/8.6.5) id PAA12707; Thu, 22 Oct 1998 15:23:50 +0100 From: Luigi Rizzo Message-Id: <199810221423.PAA12707@labinfo.iet.unipi.it> Subject: Request for change... To: stable@FreeBSD.ORG Date: Thu, 22 Oct 1998 15:23:50 +0100 (MET) X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG As part of the diskless support with shared root and usr partitions, which i have been using for years now, I need the attached changes to /etc/rc This code detects a diskless machine from having the hostname set (through bootp) when control is given to /etc/rc, and reacts appropriately (by doing some specific actions to mount a writable /var partition and populate it -- these things can be put into a separate script, e.g. rc.diskless if necessary). This is essentially a no-op for regular machines. Details are documented in http://www.iet.unipi.it/~luigi/diskless.html Do i have permission to work on this stuff for inclusion in -stable and/or -current ? [as an aside: there are many people who use similar setups for diskless support, so if someone has suggestions please go ahead] luigi --- rc Wed Jul 22 10:16:24 1998 +++ /sd0/etc/diskless/etc/rc Thu Jun 4 11:35:21 1998 @@ -1,5 +1,5 @@ #!/bin/sh -# $Id: rc,v 1.104.2.34 1998/06/04 00:20:34 mph Exp $ +# $Id: rc,v 1.104.2.33 1998/02/15 14:24:47 jkh Exp $ # From: @(#)rc 5.27 (Berkeley) 6/5/91 # System startup script run by init on autoboot @@ -27,6 +27,7 @@ ccdconfig -C fi +DISKLESS=NO swapon -a if [ $1x = autobootx ]; then @@ -68,7 +69,9 @@ # root must be read/write both for NFS diskless and for VFS LKMs before # proceeding any further. -mount -u -o rw / +# However, do not trust fstab, could be bogus +set `df -n / ` +mount -u -o rw $8 / if [ $? != 0 ]; then echo "Filesystem mount failed, startup aborted" exit 1 @@ -76,7 +79,37 @@ umount -a >/dev/null 2>&1 +if [ "`hostname`" = "" ] +then mount -a -t nonfs +else + DISKLESS=YES + echo "This is diskless host `hostname`" + # At this point see if there is a private fstab for this machine + # to replace the default one. It goes in /var/etc/fstab + mount /var # to have something writable... + mkdir /var/etc + # at this point be careful -- /etc is empty... + cp /machine/_default_/fstab /etc/fstab + if [ -f /machine/`hostname`/fstab ] + then + echo "Customizing for `hostname`" + cp /machine/`hostname`/fstab /etc/fstab + else + echo "`hostname` does not have private fstab" + fi + mount -a -t nomfs + # now populate /var. I need /usr mounted since tar calls gunzip... + (cd / ; tar --unlink -xpzf /var.tgz ) + + if [ -d /machine/`hostname` ] + then + echo "Customizing for `hostname`" + ls /machine/`hostname` + cp /machine/`hostname`/* /etc + fi +fi + if [ $? != 0 ]; then echo "Filesystem mount failed, startup aborted" exit 1 @@ -95,7 +128,7 @@ adjkerntz -i -rm -rf /var/run/* +rm -f /var/run/* # Keep a copy of the boot messages around dmesg > /var/run/dmesg.boot @@ -122,7 +155,10 @@ network_pass1 fi +if [ "$DISKLESS" != "YES" ] +then mount -a -t nfs +fi # Whack the pty perms back into shape. chmod 666 /dev/tty[pqrsPQRS]* To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Oct 22 14:08:51 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA01605 for freebsd-stable-outgoing; Thu, 22 Oct 1998 14:08:51 -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 OAA01599 for ; Thu, 22 Oct 1998 14:08:50 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost.cdrom.com [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id OAA00926; Thu, 22 Oct 1998 14:12:05 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Message-Id: <199810222112.OAA00926@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Luigi Rizzo cc: stable@FreeBSD.ORG Subject: Re: Request for change... In-reply-to: Your message of "Thu, 22 Oct 1998 15:23:50 BST." <199810221423.PAA12707@labinfo.iet.unipi.it> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 22 Oct 1998 14:12:04 -0700 From: Mike Smith Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I don't think it's suitable for general consumption, no - there is too much of your local policy embedded in this. I'd keep it local, or perhaps see if you can't come up with a generic hook mechanism that's called out very early, and do everything inside that (optional) hook. > As part of the diskless support with shared root and usr partitions, > which i have been using for years now, I need the attached changes > to /etc/rc > > This code detects a diskless machine from having the hostname set > (through bootp) when control is given to /etc/rc, and reacts > appropriately (by doing some specific actions to mount a writable /var > partition and populate it -- these things can be put into a separate > script, e.g. rc.diskless if necessary). > This is essentially a no-op for regular machines. > > Details are documented in > > http://www.iet.unipi.it/~luigi/diskless.html > > Do i have permission to work on this stuff for inclusion in -stable > and/or -current ? > > [as an aside: there are many people who use similar setups for diskless > support, so if someone has suggestions please go ahead] > > luigi > > > --- rc Wed Jul 22 10:16:24 1998 > +++ /sd0/etc/diskless/etc/rc Thu Jun 4 11:35:21 1998 > @@ -1,5 +1,5 @@ > #!/bin/sh > -# $Id: rc,v 1.104.2.34 1998/06/04 00:20:34 mph Exp $ > +# $Id: rc,v 1.104.2.33 1998/02/15 14:24:47 jkh Exp $ > # From: @(#)rc 5.27 (Berkeley) 6/5/91 > > # System startup script run by init on autoboot > @@ -27,6 +27,7 @@ > ccdconfig -C > fi > > +DISKLESS=NO > swapon -a > > if [ $1x = autobootx ]; then > @@ -68,7 +69,9 @@ > > # root must be read/write both for NFS diskless and for VFS LKMs before > # proceeding any further. > -mount -u -o rw / > +# However, do not trust fstab, could be bogus > +set `df -n / ` > +mount -u -o rw $8 / > if [ $? != 0 ]; then > echo "Filesystem mount failed, startup aborted" > exit 1 > @@ -76,7 +79,37 @@ > > umount -a >/dev/null 2>&1 > > +if [ "`hostname`" = "" ] > +then > mount -a -t nonfs > +else > + DISKLESS=YES > + echo "This is diskless host `hostname`" > + # At this point see if there is a private fstab for this machine > + # to replace the default one. It goes in /var/etc/fstab > + mount /var # to have something writable... > + mkdir /var/etc > + # at this point be careful -- /etc is empty... > + cp /machine/_default_/fstab /etc/fstab > + if [ -f /machine/`hostname`/fstab ] > + then > + echo "Customizing for `hostname`" > + cp /machine/`hostname`/fstab /etc/fstab > + else > + echo "`hostname` does not have private fstab" > + fi > + mount -a -t nomfs > + # now populate /var. I need /usr mounted since tar calls gunzip... > + (cd / ; tar --unlink -xpzf /var.tgz ) > + > + if [ -d /machine/`hostname` ] > + then > + echo "Customizing for `hostname`" > + ls /machine/`hostname` > + cp /machine/`hostname`/* /etc > + fi > +fi > + > if [ $? != 0 ]; then > echo "Filesystem mount failed, startup aborted" > exit 1 > @@ -95,7 +128,7 @@ > > adjkerntz -i > > -rm -rf /var/run/* > +rm -f /var/run/* > > # Keep a copy of the boot messages around > dmesg > /var/run/dmesg.boot > @@ -122,7 +155,10 @@ > network_pass1 > fi > > +if [ "$DISKLESS" != "YES" ] > +then > mount -a -t nfs > +fi > > # Whack the pty perms back into shape. > chmod 666 /dev/tty[pqrsPQRS]* > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message > -- \\ 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 Oct 22 14:36:00 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA04654 for freebsd-stable-outgoing; Thu, 22 Oct 1998 14:36:00 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from ns2.interlinks.net (ns2.interlinks.net [207.107.160.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA04647; Thu, 22 Oct 1998 14:35:59 -0700 (PDT) (envelope-from bill@interlinks.net) Received: from localhost (bill@localhost) by ns2.interlinks.net (8.9.1/8.8.8) with ESMTP id RAA05042; Thu, 22 Oct 1998 17:28:33 -0400 (EDT) Date: Thu, 22 Oct 1998 17:28:33 -0400 (EDT) From: Bill Sandiford To: freebsd-current@FreeBSD.ORG cc: freebsd-stable@FreeBSD.ORG Subject: FreeBSD 3.0 Release and pw command - Potential Bug? 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 We are having a problem with FreeBSD 3.0 Release and it's associated pw command. We have scripts that used to work perfectly in the 2.2.x line. The script still works perfectly when we run it manually as root (logged in at the terminal) however when cron executes the script, the pw commands in the script don't work. We are executing the script using the crontab for root. We know that the script is executing because some of the other commands in the script are happening and working. The script is designed to add a new user to our system and the line with pw looks something like this : echo password | pw useradd username -h 0 -c "Full Name" -g group -u uid -m -d homedir obviously we substitute a correct numeric id for uid and proper groupname for group, etc. We are not sure if this is a problem with our system or a bug with the pw command that is in the 3.0 release...we have also tried invoking the script from and inetd process as well.....we have tried this script on 3 different systems and it doesn't work on any of them except when invoked manually. Any help please!!! ------------------------------------------ Bill Sandiford Jr. - Systems Administrator Interlinks - http://www.interlinks.net sysop@interlinks.net - bill@interlinks.net (905)404-0810 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Oct 22 14:51:06 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA06942 for freebsd-stable-outgoing; Thu, 22 Oct 1998 14:51:06 -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 OAA06935; Thu, 22 Oct 1998 14:51:05 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost.cdrom.com [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id OAA01173; Thu, 22 Oct 1998 14:52:24 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Message-Id: <199810222152.OAA01173@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Bill Sandiford cc: freebsd-current@FreeBSD.ORG, freebsd-stable@FreeBSD.ORG Subject: Re: FreeBSD 3.0 Release and pw command - Potential Bug? In-reply-to: Your message of "Thu, 22 Oct 1998 17:28:33 EDT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 22 Oct 1998 14:52:24 -0700 From: Mike Smith Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It is almost *never* correct to post to both -current and -stable. Please pick the one list that suits only. > We are having a problem with FreeBSD 3.0 Release and it's associated pw > command. We have scripts that used to work perfectly in the 2.2.x line. > The script still works perfectly when we run it manually as root (logged > in at the terminal) however when cron executes the script, the pw commands > in the script don't work. "Help, my car doesn't work. Help me!". You might want to start by offering some more details. Any error messages and the return code would be a good start. -- \\ 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 Oct 22 14:57:56 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA07964 for freebsd-stable-outgoing; Thu, 22 Oct 1998 14:57:56 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from limes.NIC.DTAG.DE (limes.NIC.DTAG.DE [194.25.1.113]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA07952 for ; Thu, 22 Oct 1998 14:57:48 -0700 (PDT) (envelope-from bm@Reineke.malepartus.de) Received: from kronos.NIC.DTAG.DE (kronos.NIC.DTAG.DE [194.25.1.92]) by limes.NIC.DTAG.DE (8.8.5/8.8.3) with ESMTP id XAA06450; Thu, 22 Oct 1998 23:55:50 +0200 (MET DST) Received: from Reineke.malepartus.de (reineke.malepartus.de [194.25.4.66]) by kronos.NIC.DTAG.DE (8.8.5/8.7.1) with ESMTP id XAA01609; Thu, 22 Oct 1998 23:57:03 +0200 (MET DST) Received: from Reineke.malepartus.de (localhost.Malepartus.de [127.0.0.1]) by Reineke.malepartus.de (8.8.8/8.8.8) with ESMTP id XAA04898; Thu, 22 Oct 1998 23:57:01 +0200 (MEST) (envelope-from bm@Reineke.malepartus.de) Message-Id: <199810222157.XAA04898@Reineke.malepartus.de> X-Mailer: exmh version 2.0.2 2/24/98 From: Burkard Meyendriesch To: Bart Lindsey Cc: freebsd-stable@FreeBSD.ORG Subject: Re: ECC memory support In-reply-to: Your Message from Tue, 20 Oct 1998 10:17:20 PDT. X-organization: The home of Reineke Fuchs X-GPOS: 52.0844N 7.9081E X-phone: +49 5484 96097 X-pgp-fingerprint: DF 83 04 CD B5 D1 10 43 57 4C AD 9A B1 02 28 17 X-face: "[-;]oI+8gP9>*J%knDN8d%DuhvJS2Lj4L\bRb7gz(pcT?2Zh6_Vam_6csAum3$<&lhAFd^ jt|!&Ut1C~Vg*E/q}+#cbFg-GU]c.bB8Ad,L'W$'9{^0y'AzM4#hS[C[F-1'|O;Kg3Vrq5q6dsU*TmJ@}+QPM\ b[^9Rhd,UoMpRpd5k[X=h.Dom*kbT`cNQ Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 22 Oct 1998 23:57:01 +0200 Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by hub.freebsd.org id OAA07958 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 20 Oct 1998, Bart Lindsey wrote: > Hi Burkard, > [...] > Depending on the revision of your motherboard, you might have to download > the bios patch described at URL: > > http://www.asus.com/downloads/bios/ > > There are two factors mentioned which can cause parity errors: > 1. PS2 mouse installed or > 2. AMD K6 installed and ECC/parity enabled. > > Good Luck! > > Bart. > Hi Bart, thanks for the hint. Yes indeed, I run an AMD K6/233 with ECC enabled; last night I upgraded my BIOS. Maybe it will help my spurious errors to disappear... But my original questions are still pending: Isn't there any possibility to detect 1-bit errors even if they are detected and corrected by my ECC electronics? Isn't there any register of the 82430HX chip set which can be examined after an memory error NMI? The only thing I could find is --- /usr/src/sys/i386/i386/trap.c -------------------------------------- ... /* machine/parity/power fail/"kitchen sink" faults */ if (isa_nmi(code) == 0) return; panic("NMI indicates hardware failure"); ... ------------------------------------------------------------------------ Burkard -- * Burkard Meyendriesch ___ bm@malepartus.de * * Hauptstrasse 45 ________|________ tel +49 5484 96097 * * D-49219 Glandorf-Schwege 0 52 05'05"N 07 54'29"E * * PGP-Fingerprint DF 83 04 CD B5 D1 10 43 57 4C AD 9A B1 02 28 17 * To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Oct 22 15:19:34 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA11406 for freebsd-stable-outgoing; Thu, 22 Oct 1998 15:19:34 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from gatekeeper.tsc.tdk.com (gatekeeper.tsc.tdk.com [207.113.159.21]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA11401 for ; Thu, 22 Oct 1998 15:19:33 -0700 (PDT) (envelope-from gdonl@tsc.tdk.com) Received: from sunrise.gv.tsc.tdk.com (root@sunrise.gv.tsc.tdk.com [192.168.241.191]) by gatekeeper.tsc.tdk.com (8.8.8/8.8.8) with ESMTP id PAA05751; Thu, 22 Oct 1998 15:17:30 -0700 (PDT) (envelope-from gdonl@tsc.tdk.com) Received: from salsa.gv.tsc.tdk.com (salsa.gv.tsc.tdk.com [192.168.241.194]) by sunrise.gv.tsc.tdk.com (8.8.5/8.8.5) with ESMTP id PAA10570; Thu, 22 Oct 1998 15:17:29 -0700 (PDT) Received: (from gdonl@localhost) by salsa.gv.tsc.tdk.com (8.8.5/8.8.5) id PAA17041; Thu, 22 Oct 1998 15:17:27 -0700 (PDT) From: Don Lewis Message-Id: <199810222217.PAA17041@salsa.gv.tsc.tdk.com> Date: Thu, 22 Oct 1998 15:17:26 -0700 In-Reply-To: Burkard Meyendriesch "Re: ECC memory support" (Oct 22, 11:57pm) X-Mailer: Mail User's Shell (7.2.6 alpha(3) 7/19/95) To: Burkard Meyendriesch Subject: Re: ECC memory support Cc: freebsd-stable@FreeBSD.ORG Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Oct 22, 11:57pm, Burkard Meyendriesch wrote: } Subject: Re: ECC memory support } But my original questions are still pending: Isn't there any possibility } to detect 1-bit errors even if they are detected and corrected by my } ECC electronics? Isn't there any register of the 82430HX chip set which } can be examined after an memory error NMI? Yes there is. It's documented in the chipset datasheet that you can download from Intel's web site. Also your BIOS should have a setting to configure whether a 1-bit error causes an NMI. The last time this subject came up, some folks wanted to use the BIOS (which should understand the chipset on that motherboard) to retrieve this information rather than build knowledge of specific chipsets into the kernel. On an unrelated thread, someone mentioned that there were some unresolved issues with rearming NMI. I would very much like to have this feature, however it might be implemented. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Oct 22 15:35:11 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA13396 for freebsd-stable-outgoing; Thu, 22 Oct 1998 15:35:11 -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 PAA13388 for ; Thu, 22 Oct 1998 15:35:09 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost.cdrom.com [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id PAA01440; Thu, 22 Oct 1998 15:37:06 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Message-Id: <199810222237.PAA01440@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Don Lewis cc: Burkard Meyendriesch , freebsd-stable@FreeBSD.ORG Subject: Re: ECC memory support In-reply-to: Your message of "Thu, 22 Oct 1998 15:17:26 PDT." <199810222217.PAA17041@salsa.gv.tsc.tdk.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 22 Oct 1998 15:37:06 -0700 From: Mike Smith Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > On Oct 22, 11:57pm, Burkard Meyendriesch wrote: > } Subject: Re: ECC memory support > > } But my original questions are still pending: Isn't there any possibility > } to detect 1-bit errors even if they are detected and corrected by my > } ECC electronics? Isn't there any register of the 82430HX chip set which > } can be examined after an memory error NMI? > > Yes there is. It's documented in the chipset datasheet that you can > download from Intel's web site. Also your BIOS should have a setting > to configure whether a 1-bit error causes an NMI. > > The last time this subject came up, some folks wanted to use the BIOS > (which should understand the chipset on that motherboard) to retrieve > this information rather than build knowledge of specific chipsets into > the kernel. That would be the "nice" way to do it. I haven't made much progress pursuing things related to DMI lately, and it does look as though the way Microsoft want to do it you need to have motherboard-specific drivers installed. Some systems will preserve it in the BIOS event log, which theoretically can be retrieved - there's no guarantee that you will be able to arrange a trap on soft ECC, so you may have to live with this sort of deferred notification. There may also be some hope via ACPI, but more on that in a separate message. > On an unrelated thread, someone mentioned that there were some unresolved > issues with rearming NMI. Steve Passe (fsmp@freebsd.org). I don't recall if he was going to pass his code/comments back or not. -- \\ 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 Oct 22 15:43:50 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA14652 for freebsd-stable-outgoing; Thu, 22 Oct 1998 15:43:50 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from ns2.interlinks.net (ns2.interlinks.net [207.107.160.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA14569; Thu, 22 Oct 1998 15:42:25 -0700 (PDT) (envelope-from sysop@interlinks.net) Received: from ns1 (ns3.interlinks.net [207.107.160.3]) by ns2.interlinks.net (8.9.1/8.8.8) with SMTP id SAA07374; Thu, 22 Oct 1998 18:34:02 -0400 (EDT) Message-ID: <000e01bdfe0d$09042b20$03a06bcf@ns1.interlinks.net> From: "Bill Sandiford" To: "Bill Sandiford" , "Mike Smith" Cc: , Subject: Re: FreeBSD 3.0 Release and pw command - Potential Bug? Date: Thu, 22 Oct 1998 18:40:52 -0400 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.3115.0 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Mike thanks for your kind words. If there was an error message or a return code I would of posted it...however since there was none I didn't...Nothing comes up on the screen...syslog doesn't print anything...I have even tried redirecting the output to /dev/console so that I wouldn't miss something that happened while cron was running the script...All produce nothing except for the text that the script is supposed to print out. > >It is almost *never* correct to post to both -current and -stable. >Please pick the one list that suits only. > >> We are having a problem with FreeBSD 3.0 Release and it's associated pw >> command. We have scripts that used to work perfectly in the 2.2.x line. >> The script still works perfectly when we run it manually as root (logged >> in at the terminal) however when cron executes the script, the pw commands >> in the script don't work. > >"Help, my car doesn't work. Help me!". > >You might want to start by offering some more details. Any error >messages and the return code would be a good start. > >-- >\\ 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 Oct 22 15:59:57 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA17062 for freebsd-stable-outgoing; Thu, 22 Oct 1998 15:59:57 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from gatekeeper.tsc.tdk.com (gatekeeper.tsc.tdk.com [207.113.159.21]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA17055 for ; Thu, 22 Oct 1998 15:59:56 -0700 (PDT) (envelope-from gdonl@tsc.tdk.com) Received: from sunrise.gv.tsc.tdk.com (root@sunrise.gv.tsc.tdk.com [192.168.241.191]) by gatekeeper.tsc.tdk.com (8.8.8/8.8.8) with ESMTP id PAA06414; Thu, 22 Oct 1998 15:57:04 -0700 (PDT) (envelope-from gdonl@tsc.tdk.com) Received: from salsa.gv.tsc.tdk.com (salsa.gv.tsc.tdk.com [192.168.241.194]) by sunrise.gv.tsc.tdk.com (8.8.5/8.8.5) with ESMTP id PAA11432; Thu, 22 Oct 1998 15:57:03 -0700 (PDT) Received: (from gdonl@localhost) by salsa.gv.tsc.tdk.com (8.8.5/8.8.5) id PAA17800; Thu, 22 Oct 1998 15:57:01 -0700 (PDT) From: Don Lewis Message-Id: <199810222257.PAA17800@salsa.gv.tsc.tdk.com> Date: Thu, 22 Oct 1998 15:57:01 -0700 In-Reply-To: Mike Smith "Re: ECC memory support" (Oct 22, 3:37pm) X-Mailer: Mail User's Shell (7.2.6 alpha(3) 7/19/95) To: Mike Smith , Don Lewis Subject: Re: ECC memory support Cc: Burkard Meyendriesch , freebsd-stable@FreeBSD.ORG Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Oct 22, 3:37pm, Mike Smith wrote: } Subject: Re: ECC memory support } > The last time this subject came up, some folks wanted to use the BIOS } > (which should understand the chipset on that motherboard) to retrieve } > this information rather than build knowledge of specific chipsets into } > the kernel. } } That would be the "nice" way to do it. I haven't made much progress } pursuing things related to DMI lately, and it does look as though the } way Microsoft want to do it you need to have motherboard-specific } drivers installed. Some systems will preserve it in the BIOS event } log, which theoretically can be retrieved - there's no guarantee that } you will be able to arrange a trap on soft ECC, so you may have to live } with this sort of deferred notification. In this case, who gets first crack at the NMI, the kernel or the BIOS? If the kernel sees the NMI first and it calls the BIOS, it would know if the BIOS handled the NMI and could then query the event log. If the BIOS sees the NMI, then the kernel shouldn't even see it and at least the machine won't silently reboot. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Oct 22 16:13:57 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA19592 for freebsd-stable-outgoing; Thu, 22 Oct 1998 16:13:57 -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 QAA19586; Thu, 22 Oct 1998 16:13:56 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost.cdrom.com [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id QAA01710; Thu, 22 Oct 1998 16:16:55 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Message-Id: <199810222316.QAA01710@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: "Bill Sandiford" cc: "Bill Sandiford" , "Mike Smith" , freebsd-current@FreeBSD.ORG, freebsd-stable@FreeBSD.ORG Subject: Re: FreeBSD 3.0 Release and pw command - Potential Bug? In-reply-to: Your message of "Thu, 22 Oct 1998 18:40:52 EDT." <000e01bdfe0d$09042b20$03a06bcf@ns1.interlinks.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 22 Oct 1998 16:16:55 -0700 From: Mike Smith Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > If there was an error message or a return code I would of posted > it...however since there was none I didn't...Nothing comes up on the > screen...syslog doesn't print anything...I have even tried redirecting the > output to /dev/console so that I wouldn't miss something that happened while > cron was running the script...All produce nothing except for the text that > the script is supposed to print out. Ok, but that was only half the question; pw also returns status codes according to . Something like: echo password | pw args... echo "pw returned $?" Can you send a sample, minimal example that fails? I tried: azaria# crontab -l # DO NOT EDIT THIS FILE - edit the master and reinstall. # (/tmp/crontab.nextN12946 installed on Thu Oct 22 16:15:52 1998) # (Cron version -- $Id: crontab.c,v 1.11 1997/09/15 06:39:15 charnier Exp $) 16 * * * * /tmp/pwtest azaria# cat /tmp/pwtest #!/bin/sh echo password | /usr/sbin/pw useradd foo -h 0 azaria# finger foo Login: foo Name: User Foo Directory: /home/foo Shell: /bin/sh Never logged in. No Mail. No Plan. on a 3.0-RELEASE vintage system, so it doesn't seem to be fundamental breakage. -- \\ 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 Oct 22 16:17:58 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA20131 for freebsd-stable-outgoing; Thu, 22 Oct 1998 16:17:58 -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 QAA20119 for ; Thu, 22 Oct 1998 16:17:53 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost.cdrom.com [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id QAA01737; Thu, 22 Oct 1998 16:19:21 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Message-Id: <199810222319.QAA01737@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Don Lewis cc: Mike Smith , Burkard Meyendriesch , freebsd-stable@FreeBSD.ORG Subject: Re: ECC memory support In-reply-to: Your message of "Thu, 22 Oct 1998 15:57:01 PDT." <199810222257.PAA17800@salsa.gv.tsc.tdk.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 22 Oct 1998 16:19:20 -0700 From: Mike Smith Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > On Oct 22, 3:37pm, Mike Smith wrote: > } Subject: Re: ECC memory support > > } > The last time this subject came up, some folks wanted to use the BIOS > } > (which should understand the chipset on that motherboard) to retrieve > } > this information rather than build knowledge of specific chipsets into > } > the kernel. > } > } That would be the "nice" way to do it. I haven't made much progress > } pursuing things related to DMI lately, and it does look as though the > } way Microsoft want to do it you need to have motherboard-specific > } drivers installed. Some systems will preserve it in the BIOS event > } log, which theoretically can be retrieved - there's no guarantee that > } you will be able to arrange a trap on soft ECC, so you may have to live > } with this sort of deferred notification. > > In this case, who gets first crack at the NMI, the kernel or the BIOS? > If the kernel sees the NMI first and it calls the BIOS, it would know > if the BIOS handled the NMI and could then query the event log. If the > BIOS sees the NMI, then the kernel shouldn't even see it and at least > the machine won't silently reboot. Firstly, there's no guarantee that you're going to *get* an NMI on a soft ECC error. If the design integrates error detection into the BIOS, you're going to get an SMI and the BIOS will run regardless. If you did, there would be no point in calling the BIOS, as you already know what's going on. -- \\ 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 Oct 22 18:49:53 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA06475 for freebsd-stable-outgoing; Thu, 22 Oct 1998 18:49:53 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from gatekeeper.tsc.tdk.com (gatekeeper.tsc.tdk.com [207.113.159.21]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA06460 for ; Thu, 22 Oct 1998 18:49:51 -0700 (PDT) (envelope-from gdonl@tsc.tdk.com) Received: from sunrise.gv.tsc.tdk.com (root@sunrise.gv.tsc.tdk.com [192.168.241.191]) by gatekeeper.tsc.tdk.com (8.8.8/8.8.8) with ESMTP id SAA08630; Thu, 22 Oct 1998 18:47:42 -0700 (PDT) (envelope-from gdonl@tsc.tdk.com) Received: from salsa.gv.tsc.tdk.com (salsa.gv.tsc.tdk.com [192.168.241.194]) by sunrise.gv.tsc.tdk.com (8.8.5/8.8.5) with ESMTP id SAA14542; Thu, 22 Oct 1998 18:47:41 -0700 (PDT) Received: (from gdonl@localhost) by salsa.gv.tsc.tdk.com (8.8.5/8.8.5) id SAA19488; Thu, 22 Oct 1998 18:47:39 -0700 (PDT) From: Don Lewis Message-Id: <199810230147.SAA19488@salsa.gv.tsc.tdk.com> Date: Thu, 22 Oct 1998 18:47:39 -0700 In-Reply-To: Mike Smith "Re: ECC memory support" (Oct 22, 4:19pm) X-Mailer: Mail User's Shell (7.2.6 alpha(3) 7/19/95) To: Mike Smith , Don Lewis Subject: Re: ECC memory support Cc: Burkard Meyendriesch , freebsd-stable@FreeBSD.ORG Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Oct 22, 4:19pm, Mike Smith wrote: } Subject: Re: ECC memory support } Firstly, there's no guarantee that you're going to *get* an NMI on a } soft ECC error. If the design integrates error detection into the } BIOS, you're going to get an SMI and the BIOS will run regardless. This is an area that I'm very unfamiliar with. Who sets up the interrupt vector so that the BIOS gets control? I presume it's the BIOS and the kernel is careful not to change the vector. } If you did, there would be no point in calling the BIOS, as you already } know what's going on. Ok, and I assume that if the kernel gets an SMI it is non-fatal, unlike what currently happens with an NMI. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Oct 22 22:07:30 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA21144 for freebsd-stable-outgoing; Thu, 22 Oct 1998 22:07:30 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from labinfo.iet.unipi.it (labinfo.iet.unipi.it [131.114.9.5]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id WAA21139 for ; Thu, 22 Oct 1998 22:07:28 -0700 (PDT) (envelope-from luigi@labinfo.iet.unipi.it) Received: from localhost (luigi@localhost) by labinfo.iet.unipi.it (8.6.5/8.6.5) id EAA13927; Fri, 23 Oct 1998 04:10:49 +0100 From: Luigi Rizzo Message-Id: <199810230310.EAA13927@labinfo.iet.unipi.it> Subject: Re: Request for change... To: mike@smith.net.au (Mike Smith) Date: Fri, 23 Oct 1998 04:10:49 +0100 (MET) Cc: stable@FreeBSD.ORG In-Reply-To: <199810222112.OAA00926@dingo.cdrom.com> from "Mike Smith" at Oct 22, 98 02:11:45 pm X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I don't think it's suitable for general consumption, no - there is too > much of your local policy embedded in this. > > I'd keep it local, or perhaps see if you can't come up with a generic > hook mechanism that's called out very early, and do everything inside > that (optional) hook. of course, i did not mean to commit things in the current form: > > Do i have permission to work on this stuff for inclusion in -stable > > and/or -current ? but just elaborate it and come up with something much simpler and generic along these lines: very near the beginning of /etc/rc, figure out if this is a diskless machine and set a variable. make fsck/mount/swapon contitional on this variable, and call some alternate procedure from say rc.diskless for these actions. cheers luigi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Oct 23 05:54:57 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA24783 for freebsd-stable-outgoing; Fri, 23 Oct 1998 05:54:57 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from att.com (kcgw1.att.com [192.128.133.151]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id FAA24778 for ; Fri, 23 Oct 1998 05:54:56 -0700 (PDT) (envelope-from jwb@homer.att.com) Received: from kcig1.fw.att.com by kcgw1.att.com (AT&T/IPNS/UPAS-1.0) for freebsd.org!freebsd-stable sender homer.att.com!jwb (homer.att.com!jwb); Fri Oct 23 07:53 CDT 1998 Received: from ulysses.homer.att.com (ulysses.homer.att.com [135.205.212.4]) by kcig1.fw.att.com (AT&T/IPNS/GW-1.0) with ESMTP id HAA02041 for ; Fri, 23 Oct 1998 07:53:27 -0500 (CDT) Received: from akiva.homer.att.com (akiva.homer.att.com [135.205.213.77]) by ulysses.homer.att.com (8.8.8/8.8.8) with SMTP id IAA23710 for ; Fri, 23 Oct 1998 08:53:20 -0400 (EDT) Received: by akiva.homer.att.com (4.1) id AA20962; Fri, 23 Oct 98 08:53:22 EDT Message-Id: <9810231253.AA20962@akiva.homer.att.com> Received: from localhost.homer.att.com [127.0.0.1] by akiva; Fri Oct 23 08:53:21 EDT 1998 X-Mailer: exmh version 2.0.2 2/24/98 To: freebsd-stable@FreeBSD.ORG Subject: CTM-0901 Make world problem Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 23 Oct 1998 08:53:20 -0400 From: "J. W. Ballantine" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, I'm running 2.2-stable and have undated to CTM-0901, and tried to makeworld. Everything seems to be running fine until I get to the lkm/umapfs make and at the mv tmp.o umap_mod.o the build stops running and the console just freezes up. I checked for disk space and that appears fine. Anyone have any ideas on what could be causing the problem???? Thanks, Jim Ballantine To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Oct 23 11:47:57 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA29487 for freebsd-stable-outgoing; Fri, 23 Oct 1998 11:47:57 -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 LAA29480 for ; Fri, 23 Oct 1998 11:47:56 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost.cdrom.com [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id LAA00640; Fri, 23 Oct 1998 11:51:33 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Message-Id: <199810231851.LAA00640@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Don Lewis cc: freebsd-stable@FreeBSD.ORG Subject: Re: ECC memory support In-reply-to: Your message of "Thu, 22 Oct 1998 18:47:39 PDT." <199810230147.SAA19488@salsa.gv.tsc.tdk.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 23 Oct 1998 11:51:33 -0700 From: Mike Smith Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > On Oct 22, 4:19pm, Mike Smith wrote: > } Subject: Re: ECC memory support > > } Firstly, there's no guarantee that you're going to *get* an NMI on a > } soft ECC error. If the design integrates error detection into the > } BIOS, you're going to get an SMI and the BIOS will run regardless. > > This is an area that I'm very unfamiliar with. Who sets up the interrupt > vector so that the BIOS gets control? I presume it's the BIOS and the > kernel is careful not to change the vector. The BIOS does. The kernel doesn't know anything about system management mode (SMM) or the system management interrupt (SMI), and it shouldn't, as it's specifically designed to allow the BIOS to obtain control while the system is running in order to perform system-specific tasks. > } If you did, there would be no point in calling the BIOS, as you already > } know what's going on. > > Ok, and I assume that if the kernel gets an SMI it is non-fatal, unlike > what currently happens with an NMI. The kernel doesn't get the SMI, the BIOS does. -- \\ 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 Fri Oct 23 14:57:12 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA15676 for freebsd-stable-outgoing; Fri, 23 Oct 1998 14:57:12 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from freebie.dcfinc.com (freebie.dcfinc.com [138.113.5.128]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA15670 for ; Fri, 23 Oct 1998 14:57:10 -0700 (PDT) (envelope-from chad@freebie.dcfinc.com) Received: (from chad@localhost) by freebie.dcfinc.com (8.8.7/8.8.3a) id OAA21667; Fri, 23 Oct 1998 14:55:15 -0700 (MST) From: "Chad R. Larson" Message-Id: <199810232155.OAA21667@freebie.dcfinc.com> Subject: Re: ECC memory support To: mike@smith.net.au (Mike Smith) Date: Fri, 23 Oct 1998 14:55:15 -0700 (MST) Cc: Don.Lewis@tsc.tdk.com, freebsd-stable@FreeBSD.ORG In-Reply-To: <199810231851.LAA00640@dingo.cdrom.com> from Mike Smith at "Oct 23, 98 11:51:33 am" Reply-to: chad@dcfinc.com X-unexpected: The Spanish Inquisition X-Mailer: ELM [version 2.4ME+ PL22 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> On Oct 22, 4:19pm, Mike Smith wrote: >> } Subject: Re: ECC memory support > The BIOS does. The kernel doesn't know anything about system management > mode (SMM) or the system management interrupt (SMI), and it shouldn't, > as it's specifically designed to allow the BIOS to obtain control while > the system is running in order to perform system-specific tasks. Is there any formal documentation, or standards for SMM? Does each motherboard have it's own specific BIOS and/or drivers? I have 2.2-stable up on an AST Manhattan D file server. It documents a lot of SMM features in the hardware. Cover tamper switches, under and over voltage monitors, fan motor monitors, temperature monitoring, etc. It would be good to be able to get to those features, and to invoke a powerdown under some failure conditions. -crl -- Chad R. Larson (CRL15) 602-953-1392 Brother, can you paradigm? chad@dcfinc.com chad@larsons.org chad@anasazi.com larson1@home.net DCF, Inc. - 14623 North 49th Place, Scottsdale, Arizona 85254-2207 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Oct 23 15:08:22 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA16453 for freebsd-stable-outgoing; Fri, 23 Oct 1998 15:08:22 -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 PAA16448 for ; Fri, 23 Oct 1998 15:08:20 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost.cdrom.com [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id PAA01577; Fri, 23 Oct 1998 15:10:10 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Message-Id: <199810232210.PAA01577@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: chad@dcfinc.com cc: mike@smith.net.au (Mike Smith), Don.Lewis@tsc.tdk.com, freebsd-stable@FreeBSD.ORG Subject: Re: ECC memory support In-reply-to: Your message of "Fri, 23 Oct 1998 14:55:15 PDT." <199810232155.OAA21667@freebie.dcfinc.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 23 Oct 1998 15:10:10 -0700 From: Mike Smith Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > >> On Oct 22, 4:19pm, Mike Smith wrote: > >> } Subject: Re: ECC memory support > > The BIOS does. The kernel doesn't know anything about system management > > mode (SMM) or the system management interrupt (SMI), and it shouldn't, > > as it's specifically designed to allow the BIOS to obtain control while > > the system is running in order to perform system-specific tasks. > > Is there any formal documentation, or standards for SMM? Does each > motherboard have it's own specific BIOS and/or drivers? SMM is described in the processor manuals from Intel and friends. SMM-related features are usually discussed in the documentation for the device(s) in question. > I have 2.2-stable up on an AST Manhattan D file server. It documents a lot > of SMM features in the hardware. Cover tamper switches, under and over > voltage monitors, fan motor monitors, temperature monitoring, etc. > > It would be good to be able to get to those features, and to invoke a > powerdown under some failure conditions. You don't get to the features; you use the BIOS interface (DMI or SMBIOS) if you're lucky, or motherboard-specific drivers otherwise. We're attacking the problem from several different angles; the iicbus code provides the infrastructure for talking directly to many of the peripherals involved. We're also growing kernel infrastructure to call the relevant BIOS functions. Developers for these projects are definitely wanted. -- \\ 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 Sat Oct 24 00:33:06 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA23066 for freebsd-stable-outgoing; Sat, 24 Oct 1998 00:33:06 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from unix1.it-datacntr.louisville.edu (unix1.it-datacntr.louisville.edu [136.165.4.27]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA23061 for ; Sat, 24 Oct 1998 00:33:05 -0700 (PDT) (envelope-from k.stevenson@louisville.edu) Received: from homer.louisville.edu (ktstev01@homer.it-datacntr.louisville.edu [136.165.1.20]) by unix1.it-datacntr.louisville.edu (8.8.8/8.8.7) with ESMTP id DAA23146 for ; Sat, 24 Oct 1998 03:32:32 -0400 Received: (from ktstev01@localhost) by homer.louisville.edu (8.8.8/8.8.8) id DAA07019 for freebsd-stable@freebsd.org; Sat, 24 Oct 1998 03:32:31 -0400 (EDT) Message-ID: <19981024033231.A6200@homer.louisville.edu> Date: Sat, 24 Oct 1998 03:32:31 -0400 From: Keith Stevenson To: freebsd-stable@FreeBSD.ORG Subject: kernel panic from quota? Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I appear to have tickled the bug quota bug that Dan Swartzendruber posted about on 28 September. Here is the sequence of events: # uname -a FreeBSD narn.spd.louisville.edu 2.2.7-STABLE FreeBSD 2.2.7-STABLE #0: Tue Oct 6 14:25:11 EDT 1998 root@narn.spd.louisville.edu:/usr/src/sys/compile/NARN i386 quotaoff -avug (Do some massive file transfers) checkquota -avug quotaon -avug repquota -avug quota -v quota -v ... quota -v Wham! Kernel panics on a page fault and leaves me a core file. If anyone is interested in doing some post-mortem work, I can make the core file available via FTP. (It's ~512 MB, so I'm not going to email it to anyone) In the meantime, since it hurt when I did that sequence of commands, I'm not going to do it any more :) Regards, --Keith Stevenson-- -- Keith Stevenson System Programmer - Data Center Services - University of Louisville k.stevenson@louisville.edu PGP key fingerprint = 4B 29 A8 95 A8 82 EA A2 29 CE 68 DE FC EE B6 A0 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Oct 24 07:32:13 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA15624 for freebsd-stable-outgoing; Sat, 24 Oct 1998 07:32:13 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from ibm.net. (slip166-72-224-167.pa.us.ibm.net [166.72.224.167]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA15609 for ; Sat, 24 Oct 1998 07:32:09 -0700 (PDT) (envelope-from placej@ibm.net) Received: (from placej@localhost) by ibm.net. (8.8.8/8.8.7) id KAA00192; Sat, 24 Oct 1998 10:31:20 -0400 (EDT) (envelope-from placej) Message-ID: <19981024103119.16296@ka3tis.com> Date: Sat, 24 Oct 1998 10:31:19 -0400 From: "John C. Place" To: freebsd-stable@FreeBSD.ORG Subject: Re: kernel panic from quota? Reply-To: "John C. Place" References: <19981024033231.A6200@homer.louisville.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89i In-Reply-To: <19981024033231.A6200@homer.louisville.edu>; from Keith Stevenson on Sat, Oct 24, 1998 at 03:32:31AM -0400 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, Oct 24, 1998 at 03:32:31AM -0400, Keith Stevenson wrote: > If anyone is interested in doing some post-mortem work, I can make the core > file available via FTP. (It's ~512 MB, so I'm not going to email it to anyone) > Just a comment, if you reduced your memory size to the kernel (MEMSIZE) and made another kernel wouldent that decrease the size but still give the needed info? Just thinking outloud here, 512MB sounds big and I seen core files before but NOT from a panic (thankfully so) or are they always that big? L8er John To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Oct 24 08:33:29 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA19234 for freebsd-stable-outgoing; Sat, 24 Oct 1998 08:33:29 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from unix2.it-datacntr.louisville.edu (unix2.it-datacntr.louisville.edu [136.165.4.28]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA19229 for ; Sat, 24 Oct 1998 08:33:27 -0700 (PDT) (envelope-from k.stevenson@louisville.edu) Received: from homer.louisville.edu (ktstev01@homer.it-datacntr.louisville.edu [136.165.1.20]) by unix2.it-datacntr.louisville.edu (8.8.8/8.8.8) with ESMTP id LAA27928; Sat, 24 Oct 1998 11:32:53 -0400 Received: (from ktstev01@localhost) by homer.louisville.edu (8.8.8/8.8.8) id LAA03831; Sat, 24 Oct 1998 11:32:53 -0400 (EDT) Message-ID: <19981024113253.B3102@homer.louisville.edu> Date: Sat, 24 Oct 1998 11:32:53 -0400 From: Keith Stevenson To: "John C. Place" Cc: freebsd-stable@FreeBSD.ORG Subject: Re: kernel panic from quota? References: <19981024033231.A6200@homer.louisville.edu> <19981024103119.16296@ka3tis.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <19981024103119.16296@ka3tis.com>; from John C. Place on Sat, Oct 24, 1998 at 10:31:19AM -0400 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It's my understanding that when the kernel drops core, it leaves behind an image of your _entire_ VM space. Since this particular box has 512MB of RAM in it, a 512MB core file seems reasonable to me. (I _like_ having half gig of RAM!) Regards, --Keith Stevenson-- -- Keith Stevenson System Programmer - Data Center Services - University of Louisville k.stevenson@louisville.edu PGP key fingerprint = 4B 29 A8 95 A8 82 EA A2 29 CE 68 DE FC EE B6 A0 On Sat, Oct 24, 1998 at 10:31:19AM -0400, John C. Place wrote: > On Sat, Oct 24, 1998 at 03:32:31AM -0400, Keith Stevenson wrote: > > If anyone is interested in doing some post-mortem work, I can make the core > > file available via FTP. (It's ~512 MB, so I'm not going to email it to anyone) > > > Just a comment, if you reduced your memory size to the kernel (MEMSIZE) and > made another kernel wouldent that decrease the size but still give the needed > info? Just thinking outloud here, 512MB sounds big and I seen core files > before but NOT from a panic (thankfully so) or are they always that big? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Oct 24 10:46:57 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA26537 for freebsd-stable-outgoing; Sat, 24 Oct 1998 10:46:57 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from papaya.mail.easynet.net (papaya.mail.easynet.net [195.40.1.40]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id KAA26532 for ; Sat, 24 Oct 1998 10:46:52 -0700 (PDT) (envelope-from andrew@sour.cream.org) Received: (qmail 21103 invoked from network); 24 Oct 1998 17:46:19 -0000 Received: from boothman.easynet.co.uk (194.154.100.117) by papaya.mail.easynet.net with SMTP; 24 Oct 1998 17:46:19 -0000 Received: by Boothman.easynet.co.uk (VPOP3 - Unregistered) with SMTP; Sat, 24 Oct 1998 18:39:59 +0100 Message-Id: <3.0.5.32.19981024183958.007dbe70@ice.cream.org> X-Sender: andrew@ice.cream.org X-Mailer: QUALCOMM Windows Eudora Light Version 3.0.5 (32) Date: Sat, 24 Oct 1998 18:39:58 +0100 To: freebsd-stable@FreeBSD.ORG From: Andrew Boothman Subject: Stable and CTM Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" X-Server: VPOP3 V1.2.0d Unregistered Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, I'm interested in tracking -stable so I read the section in the manual about " Synchronizing Source Trees over the Internet" and because my FreeBSD box doesn't have a connection to the 'net, I selected CTM as the best method for staying up-to-date because I can take CTM deltas to my machine on disk. I went to ftp.freebsd.org/pub/FreeBSD/CTM/src-2.2/ to find the most recent src-2.2.whateverxR227 file so that I could update from the source contained on my WC 2.2.7-RELEASE CD2. Unfortunatly the only transition deltas available where the "xempty" ones. In other words the ones that allow you to start from a completely empty source tree. What happened to all the "xR227" transition deltas? Many thanks. -- Andrew Boothman http://sour.cream.org PGP Key Available From Public Servers To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Oct 24 10:53:11 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA26911 for freebsd-stable-outgoing; Sat, 24 Oct 1998 10:53:11 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from excelsior.apana.org.au (excelsior.apana.org.au [203.11.114.15]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA26901 for ; Sat, 24 Oct 1998 10:52:54 -0700 (PDT) (envelope-from dean@odyssey.apana.org.au) Received: from odyssey.apana.org.au (odyssey.apana.org.au [203.11.114.1]) by excelsior.apana.org.au (8.8.8/8.8.8) with ESMTP id BAA13276; Sun, 25 Oct 1998 01:50:48 +0800 (WST) (envelope-from dean@odyssey.apana.org.au) Date: Sun, 25 Oct 1998 01:50:48 +0800 (WST) From: Dean Hollister To: Andrew Boothman cc: freebsd-stable@FreeBSD.ORG Subject: Re: Stable and CTM In-Reply-To: <3.0.5.32.19981024183958.007dbe70@ice.cream.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 Sat, 24 Oct 1998, Andrew Boothman wrote: > I'm interested in tracking -stable so I read the section in the manual > about " Synchronizing Source Trees over the Internet" and because my > FreeBSD box doesn't have a connection to the 'net, I selected CTM as the > best method for staying up-to-date because I can take CTM deltas to my > machine on disk. Why not just use cvsup? Regards, d. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Oct 24 10:56:16 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA27152 for freebsd-stable-outgoing; Sat, 24 Oct 1998 10:56:16 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from papaya.mail.easynet.net (papaya.mail.easynet.net [195.40.1.40]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id KAA27147 for ; Sat, 24 Oct 1998 10:56:14 -0700 (PDT) (envelope-from andrew@sour.cream.org) Received: (qmail 23549 invoked from network); 24 Oct 1998 17:55:40 -0000 Received: from boothman.easynet.co.uk (194.154.100.117) by papaya.mail.easynet.net with SMTP; 24 Oct 1998 17:55:40 -0000 Received: by Boothman.easynet.co.uk (VPOP3 - Unregistered) with SMTP; Sat, 24 Oct 1998 18:54:34 +0100 Message-Id: <3.0.5.32.19981024185433.007efe90@ice.cream.org> X-Sender: andrew@ice.cream.org X-Mailer: QUALCOMM Windows Eudora Light Version 3.0.5 (32) Date: Sat, 24 Oct 1998 18:54:33 +0100 To: Dean Hollister From: Andrew Boothman Subject: Re: Stable and CTM Cc: freebsd-stable@FreeBSD.ORG In-Reply-To: References: <3.0.5.32.19981024183958.007dbe70@ice.cream.org> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" X-Server: VPOP3 V1.2.0d Unregistered Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 01:50 25/10/98 +0800, Dean Hollister wrote: >Why not just use cvsup? Don't you need a connection to the 'net to use CVSup? -- Andrew Boothman http://sour.cream.org PGP Key Available From Public Servers To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Oct 24 11:20:55 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA28759 for freebsd-stable-outgoing; Sat, 24 Oct 1998 11:20:55 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from shrimp.dataplex.net (shrimp.dataplex.net [208.2.87.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA28754 for ; Sat, 24 Oct 1998 11:20:54 -0700 (PDT) (envelope-from rkw@Dataplex.NET) From: rkw@Dataplex.NET Received: from dataplex.net (nomad.dataplex.net [208.2.87.8]) by shrimp.dataplex.net (8.9.1/8.9.1) with ESMTP id PAA14768; Sat, 24 Oct 1998 15:01:50 -0500 (CDT) (envelope-from rkw@dataplex.net) Message-Id: <199810242001.PAA14768@shrimp.dataplex.net> Date: Sat, 24 Oct 1998 13:19:03 -0500 (CDT) Subject: Re: Stable and CTM To: dean@odyssey.apana.org.au cc: freebsd-stable@FreeBSD.ORG In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/plain; CHARSET=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 25 Oct, Dean Hollister wrote: > Why not just use cvsup? 1. cvsup provides a custom update for each individual user. ctm is broadcast publication. For a large number of users, cvsup requires more server-side resources. 2. cvsup requires a direct realtime connection from the client to a cvsup server, ctm uses "store and forward" technology which can even run on "sneaker net". The intermediate servers are generic internet servers rather than something particular to the particular project. 3. cvsup requires that each machine connect to the cvsup server while it parses its tree. Even if there is little changed, this can take quite some time. Some connections are very expensive per minute. Some connections cannot be maintained for sufficient time to do the update. 4. Ctm provides an "audit trail". In the past, this has proven valuable when it became necessary to reconstruct the master cvs tree. Don't misunderstand. Cvsup is a fine way to update certain classes of users. In fact, the ctm generator uses cvsup to retrieve its input. However, not everyone fits into the same mould. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Oct 24 12:04:52 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA01581 for freebsd-stable-outgoing; Sat, 24 Oct 1998 12:04:52 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from dingo.cdrom.com (castles209.castles.com [208.214.165.209]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA01574 for ; Sat, 24 Oct 1998 12:04:49 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id MAA05550; Sat, 24 Oct 1998 12:08:36 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Message-Id: <199810241908.MAA05550@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Luigi Rizzo cc: mike@smith.net.au (Mike Smith), stable@FreeBSD.ORG Subject: Re: Request for change... In-reply-to: Your message of "Fri, 23 Oct 1998 04:10:49 BST." <199810230310.EAA13927@labinfo.iet.unipi.it> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 24 Oct 1998 12:08:36 -0700 From: Mike Smith Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > I don't think it's suitable for general consumption, no - there is too > > much of your local policy embedded in this. > > > > I'd keep it local, or perhaps see if you can't come up with a generic > > hook mechanism that's called out very early, and do everything inside > > that (optional) hook. > > of course, i did not mean to commit things in the current form: > > > > Do i have permission to work on this stuff for inclusion in -stable > > > and/or -current ? > > but just elaborate it and come up with something much simpler and > generic along these lines: > > very near the beginning of /etc/rc, figure out if this is a > diskless machine and set a variable. > > make fsck/mount/swapon contitional on this variable, and call > some alternate procedure from say rc.diskless for these actions. That's getting closer. I still can't help but think that this is the wrong way to do it; the process should be driven by the configuration data, not by policy embedded in code. Why should the fsck/mount/swapon be conditionalised in more than one location? You can already turn all of these off in /etc/fstab. -- \\ 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 Sat Oct 24 12:30:12 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA03172 for freebsd-stable-outgoing; Sat, 24 Oct 1998 12:30:12 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from mail.westbend.net ([156.46.203.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA03165 for ; Sat, 24 Oct 1998 12:30:09 -0700 (PDT) (envelope-from hetzels@westbend.net) Received: from admin (admin.westbend.net [156.46.203.13]) by mail.westbend.net (8.8.8/8.8.8) with SMTP id OAA09742; Sat, 24 Oct 1998 14:29:34 -0500 (CDT) (envelope-from hetzels@westbend.net) Message-ID: <005e01bdff84$a21fc940$0dcb2e9c@westbend.net> From: "Scot W. Hetzel" To: "FreeBSD-Stable" , "Andrew Boothman" Subject: CTM Release Generation - (Re: Stable and CTM) Date: Sat, 24 Oct 1998 14:29:34 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset="Windows-1252" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.0810.800 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.0810.800 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG From: Andrew Boothman >I went to ftp.freebsd.org/pub/FreeBSD/CTM/src-2.2/ to find the most recent >src-2.2.whateverxR227 file so that I could update from the source contained >on my WC 2.2.7-RELEASE CD2. > >Unfortunatly the only transition deltas available where the "xempty" ones. >In other words the ones that allow you to start from a completely empty >source tree. What happened to all the "xR227" transition deltas? > They were never created on the CTM generation machine. The generation of the src-xR delta's are supposed to be generated manually after each release by either the CTM maintainer or the Release Engineer. But apparently, somebody has forgotten that this is one of their tasks. Could somebody please create these Release Deltas, so that this question never comes up on the list again. Thanks, Scot To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Oct 24 13:02:26 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA05186 for freebsd-stable-outgoing; Sat, 24 Oct 1998 13:02:26 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from labinfo.iet.unipi.it (labinfo.iet.unipi.it [131.114.9.5]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id NAA05181 for ; Sat, 24 Oct 1998 13:02:23 -0700 (PDT) (envelope-from luigi@labinfo.iet.unipi.it) Received: from localhost (luigi@localhost) by labinfo.iet.unipi.it (8.6.5/8.6.5) id SAA16763; Sat, 24 Oct 1998 18:53:16 +0100 From: Luigi Rizzo Message-Id: <199810241753.SAA16763@labinfo.iet.unipi.it> Subject: Re: Request for change... To: mike@smith.net.au (Mike Smith) Date: Sat, 24 Oct 1998 18:53:16 +0100 (MET) Cc: mike@smith.net.au, stable@FreeBSD.ORG In-Reply-To: <199810241908.MAA05550@dingo.cdrom.com> from "Mike Smith" at Oct 24, 98 12:08:17 pm X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > very near the beginning of /etc/rc, figure out if this is a > > diskless machine and set a variable. > > > > make fsck/mount/swapon contitional on this variable, and call > > some alternate procedure from say rc.diskless for these actions. > > That's getting closer. I still can't help but think that this is the > wrong way to do it; the process should be driven by the configuration > data, not by policy embedded in code. > > Why should the fsck/mount/swapon be conditionalised in more than one > location? You can already turn all of these off in /etc/fstab. ok, the context is to serve diskless machines with a shared readonly root. Here, the only config data you can have is the hostname, which you can easily map into a private config onto a writable mfs partition. Maybe you are right with your suggestions but i have one doubt: when you execute the line mount -u -o rw / in /etc/rc, you use the (readonly) /etc/fstab which might be invalid for some or all hosts. Maybe i should try to setup the mfs /var and fill it up with the per-machine data at the very beginning, right after HOME=/; export HOME PATH=/sbin:/bin:/usr/sbin:/usr/bin:/usr/local/sbin export PATH so that all the rest is consistent with a regular setup ? cheers luigi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Oct 24 13:07:26 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA05382 for freebsd-stable-outgoing; Sat, 24 Oct 1998 13:07:26 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from beatrice.rutgers.edu (beatrice.rutgers.edu [165.230.209.143]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA05377 for ; Sat, 24 Oct 1998 13:07:25 -0700 (PDT) (envelope-from easmith@beatrice.rutgers.edu) Received: (from easmith@localhost) by beatrice.rutgers.edu (980427.SGI.8.8.8/970903.SGI.AUTOCF) id QAA02205; Sat, 24 Oct 1998 16:06:30 -0400 (EDT) From: "Allen Smith" Message-Id: <9810241606.ZM2203@beatrice.rutgers.edu> Date: Sat, 24 Oct 1998 16:06:30 -0400 In-Reply-To: David Greenman "Re: Is 'xntpd' broken in -stable?" (Oct 9, 5:32pm) References: <199810091927.MAA14061@implode.root.com> X-Mailer: Z-Mail (3.2.3 08feb96 MediaMail) To: David Greenman , Studded Subject: Re: Is 'xntpd' broken in -stable? Cc: Randy Bush , Marc Gutschner , freebsd-stable@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 On Oct 9, 5:32pm, David Greenman (possibly) wrote: > >> > issue an 'ntpdate whatever.your.primary.time.host.is' then you should be > >> > able to start xntpd. > >> > >> Oct 9 10:56:57 rip ntpdate: Can't set time of day: Operation not permitted > > > > Hmmm.. that looks like you weren't root at the time. Make sure that > >you're root, that there is no ntp/xntpd server running, and type: > > > >ntpdate ucsd.ucsd.edu > > > > That should get it. If it doesn't, something is dreadfully wrong. > > I think Randy's question is: Does xntpd work when securelevel == > 2? The answer is "sort of". With securelevel > 1 you can only > speed up or slow down the clock via adjtime(); the system will > not let you set the time backwards (e.g. with settimeofday). This > is a security feature which prevents people from changing the > time of day, touching a file, and then setting it back (and thus > allow you to reset the inode change time into the past). This > restriction was adopted from NetBSD in rev 1.23 of > sys/kern/kern_time.c. I've checked with Dave Mills on this issue, and there's an option (-x, which is unfortunately not in the help files) in ntpd (as opposed to xntpd, which is about as obsolete/nonsupported as FreeBSD-1.x) to block attempting to set the clock back via a jump (as opposed to adjtime or ntp_adjtime). As long as the kernel and hardware clock are working properly, jumps far enough back to need an actual reset shouldn't be happening except at reboot (which is when ntpdate should be used, probably prior to setting securelevel to 2). -Allen -- Allen Smith easmith@beatrice.rutgers.edu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Oct 24 14:56:32 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA10610 for freebsd-stable-outgoing; Sat, 24 Oct 1998 14:56:32 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from papaya.mail.easynet.net (papaya.mail.easynet.net [195.40.1.40]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id OAA10595 for ; Sat, 24 Oct 1998 14:56:23 -0700 (PDT) (envelope-from andrew@sour.cream.org) Received: (qmail 20497 invoked from network); 24 Oct 1998 21:55:49 -0000 Received: from boothman.easynet.co.uk (194.154.100.117) by papaya.mail.easynet.net with SMTP; 24 Oct 1998 21:55:49 -0000 Received: by Boothman.easynet.co.uk (VPOP3 - Unregistered) with SMTP; Sat, 24 Oct 1998 22:54:51 +0100 Message-Id: <3.0.5.32.19981024225450.007af190@ice.cream.org> X-Sender: andrew@ice.cream.org X-Mailer: QUALCOMM Windows Eudora Light Version 3.0.5 (32) Date: Sat, 24 Oct 1998 22:54:50 +0100 To: "Scot W. Hetzel" , "FreeBSD-Stable" From: Andrew Boothman Subject: Re: CTM Release Generation - (Re: Stable and CTM) In-Reply-To: <005e01bdff84$a21fc940$0dcb2e9c@westbend.net> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" X-Server: VPOP3 V1.2.0d Unregistered Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 14:29 24/10/98 -0500, Scot W. Hetzel wrote: >The generation of the src-xR delta's are supposed >to be generated manually after each release by either the CTM maintainer or >the Release Engineer. So these deltas are only created at every release instead of every 100 deltas like the xEmpty's? Would it not be better to create an xR delta at the same time as the xEmpty delta then you could upgrade to the -stable code easily by downloading the deltas that then come afterwards as well? By only creating xR deltas during the release of another version it means that you can only update from release to release and nothing in between. For example, I am sitting here with the 2.2.7-Release code on CD. And we are currently half way in between 2.2.7-Release and 2.2.8-Release. I cannot update to the 'current' -stable code, because the next xR delta will not be created untill 2.2.8 is released. Am I right? >Could somebody please create these Release Deltas, so that this question >never comes up on the list again. Whoops. Do I detect that this has come up on the list before? :-) -- Andrew Boothman http://sour.cream.org PGP Key Available From Public Servers To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Oct 24 23:00:54 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA09788 for freebsd-stable-outgoing; Sat, 24 Oct 1998 23:00:54 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from time.cdrom.com (time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA09783 for ; Sat, 24 Oct 1998 23:00:52 -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 XAA10586; Sat, 24 Oct 1998 23:00:13 -0700 (PDT) (envelope-from jkh@time.cdrom.com) To: "Scot W. Hetzel" cc: "FreeBSD-Stable" , "Andrew Boothman" Subject: Re: CTM Release Generation - (Re: Stable and CTM) In-reply-to: Your message of "Sat, 24 Oct 1998 14:29:34 CDT." <005e01bdff84$a21fc940$0dcb2e9c@westbend.net> Date: Sat, 24 Oct 1998 23:00:13 -0700 Message-ID: <10582.909295213@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > The generation of the src-xR delta's are supposed > to be generated manually after each release by either the CTM maintainer or > the Release Engineer. Not either - I have nothing whatsoever to do with CTM generation. Only the CTM maintainer does this. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message