From owner-freebsd-stable Sun Dec 8 0:17:12 2002 Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 94FA237B401 for ; Sun, 8 Dec 2002 00:17:11 -0800 (PST) Received: from mx0.gmx.net (mx0.gmx.net [213.165.64.100]) by mx1.FreeBSD.org (Postfix) with SMTP id ED49043EEF for ; Sun, 8 Dec 2002 00:17:09 -0800 (PST) (envelope-from belphoebe@gmx.net) Received: (qmail 11077 invoked by uid 0); 8 Dec 2002 08:17:02 -0000 Date: Sun, 8 Dec 2002 09:17:02 +0100 (MET) From: belphoebe@gmx.net To: freebsd-stable@freebsd.org MIME-Version: 1.0 References: <87lm31t3ui.fsf@pooh.honeypot.net> Subject: Re: If you shop . . . [DON'T] read this . . . X-Priority: 5 (Lowest) X-Authenticated-Sender: #0013230382@gmx.net X-Authenticated-IP: [65.28.10.43] Message-ID: <18580.1039335422@www67.gmx.net> X-Mailer: WWW-Mail 1.6 (Global Message Exchange) X-Flags: 0001 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 8bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > > No, thank you. I was bored . . . > > I have mixed feelings about . . . > Kirk Strauser I have mixed feelings about Humpty Dumpty driving a 1958 Ferrari 250 Testa Rossa 3 blocks to get groceries (we all know about his whole "balance" thing) when he lives on an exclusive diet of psychokenetically-created fish protein and rainwater. Or did Ferrari discontinue the Testa Rossa (and I mean the original one, not the Testarossa) in '57? This e-mail has something to do with S/N, static, white noise, pink noise, brownian noise being pumped backwards through SETI@underage.babysitters, and a recursive julia-set quine in brainf*ck. We now return you to your regularly scheduled -STABLE -- +++ GMX - Mail, Messaging & more http://www.gmx.net +++ NEU: Mit GMX ins Internet. Rund um die Uhr für 1 ct/ Min. surfen! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Dec 8 5:52: 8 2002 Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C7C6037B404 for ; Sun, 8 Dec 2002 05:52:06 -0800 (PST) Received: from fish.ish.com.au (212-86.dsl.connexus.net.au [203.17.212.86]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2F90343EA9 for ; Sun, 8 Dec 2002 05:52:05 -0800 (PST) (envelope-from ari@ish.com.au) Received: from [203.29.62.130] (helo=ish.com.au) by fish.ish.com.au with esmtp (Exim 6.66 #1) id 18L1qR-0002ky-00; Mon, 09 Dec 2002 00:51:43 +1100 Date: Mon, 9 Dec 2002 00:51:41 +1100 Subject: Re: update strategies Content-Type: text/plain; charset=US-ASCII; format=flowed Mime-Version: 1.0 (Apple Message framework v548) Cc: Mike Hoskins , freebsd-stable@FreeBSD.ORG To: dmagda@ee.ryerson.ca From: Aristedes Maniatis In-Reply-To: <867kelp9t9.fsf@number6.magda.ca> Message-Id: <2E37135F-0AB4-11D7-B2B7-003065A9024A@ish.com.au> Content-Transfer-Encoding: 7bit X-Mailer: Apple Mail (2.548) X-Scanner: exiscan *18L1qR-0002ky-00*HsnyxVHeHkw* on Astaro Security Linux Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG OK. This is where I get confused. I thought that the point of putting these applications into the base FreeBSD distribution was that they need to be tightly integrated into the OS. I understand that this is critical for basic system tools like "adduser". It appears this makes it important to build the whole distribution together (buildworld) and not get one tool out of sync with the rest. But if this is not the case, and we are supposed to build portions of the /usr/src/ without rebuilding the whole thing, why aren't these tools in /usr/ports? I'm new here, so I'm not telling you how to suck eggs. Perhaps there are historical reasons for this hierarchy. But I want to make sure I do the right thing. Is this the safest approach: * install ports for named, ssh, etc. * disable the base FreeBSD distributions of these tools * use cvsup to update these tools whenever I need to because of security/bugs/features * use cvsup to update base FreeBSD (src-all) for each tagged release (every 3 months or sooner in case of problems). Or less often if the update doesn't look important. Then buildworld to build a consistent FreeBSD release. Cheers Ari Maniatis On Sunday, December 8, 2002, at 12:40 PM, David Magda wrote: > You don't have to rebuild world: > > # cd /usr/src/usr.sbin/named > # make > # make install > > should work fine. The resultant binary after the 'make' is in the > /usr/obj hierachy. --------------------------> ish group pty ltd 7 Darghan St Glebe 2037 Australia phone +61 2 9660 1400 fax +61 2 9660 7400 http www.ish.com.au | email info@ish.com.au PGP fingerprint 08 57 20 4B 80 69 59 E2 A9 BF 2D 48 C2 20 0C C8 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Dec 8 6:46: 0 2002 Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 521AD37B401 for ; Sun, 8 Dec 2002 06:45:58 -0800 (PST) Received: from tomts14-srv.bellnexxia.net (tomts14.bellnexxia.net [209.226.175.35]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8D0BD43E4A for ; Sun, 8 Dec 2002 06:45:57 -0800 (PST) (envelope-from dmagda@magda.ca) Received: from number6.magda.ca ([64.229.177.206]) by tomts14-srv.bellnexxia.net (InterMail vM.5.01.04.19 201-253-122-122-119-20020516) with ESMTP id <20021208144556.HUKB4004.tomts14-srv.bellnexxia.net@number6.magda.ca>; Sun, 8 Dec 2002 09:45:56 -0500 Received: from number6.magda.ca (localhost.magda.ca [127.0.0.1]) by number6.magda.ca (8.12.6/8.12.6) with ESMTP id gB8EjufW000889 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Sun, 8 Dec 2002 09:45:56 -0500 (EST) (envelope-from dmagda@magda.ca) Received: (from dmagda@localhost) by number6.magda.ca (8.12.6/8.12.6/Submit) id gB8EjtRt000888; Sun, 8 Dec 2002 09:45:55 -0500 (EST) (envelope-from dmagda) Date: Sun, 8 Dec 2002 09:45:55 -0500 From: David Magda To: Aristedes Maniatis Cc: freebsd-stable@FreeBSD.ORG Subject: Re: update strategies Message-ID: <20021208144552.GB269@number6.magda.ca> Reply-To: David Magda References: <867kelp9t9.fsf@number6.magda.ca> <2E37135F-0AB4-11D7-B2B7-003065A9024A@ish.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <2E37135F-0AB4-11D7-B2B7-003065A9024A@ish.com.au> User-Agent: Mutt/1.4i Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Mon, Dec 09, 2002 at 12:51:41AM +1100, Aristedes Maniatis wrote: > OK. This is where I get confused. I thought that the point of putting > these applications into the base FreeBSD distribution was that they > need to be tightly integrated into the OS. I understand that this is > critical for basic system tools like "adduser". It appears this makes > it important to build the whole distribution together (buildworld) and > not get one tool out of sync with the rest. Well think of it this way. You cvsup to get the up-to-date and do a buildworld. The next day an advisory comes out for tool XXX. The problem is that there exists an off-by-one remote buffer-overflow on line Y of some file in program XXX. A fix is released and incorporated in CVS. All that's changed between the previous day's source today's where the diff file would be: - strcpy( dst, src, MAXDATA); + strcpy( dst, src, MAXDATA+1); (Yes I know, *really* contrived example, but....) For that one change are you going to do a buildworld? Not really, it would be easier to go into program XXX's directory and recompile just it. Stand alone programs can usually be compiled by themselves. Things that touch a whole bunch of stuff (libraries, PAM, gcc, etc.) should be followed with a buildworld. It all depends on how much has changed since your last buildworld. If you cvsup weekly but not much has changed in way of functionality are you going to bother with a buildworld? Not really. However, if one of the updates is a fix for an exploit, another is a new feature to ls(1), a third is some documentation fixes to the intro(7) manpage, and the fourth is some indenation changes (but no functionality changes) to src/sbin/kget/kget.c what are you going to do? Personally, I would simply rebuild the fixed program. > But if this is not the case, and we are supposed to build portions of > the /usr/src/ without rebuilding the whole thing, why aren't these > tools in /usr/ports? Many of the utilities (bind, ssh, Kerberos/Heimdal, etc.) already are in the ports. Just because people want to have more control over how things are installed than is generally available in the base system. Also for the people that want to do what you do. When the advisory for BIND 8 came out a couple of weeks ago I know an admin who installed BIND 9 for the ports until version 8 was fixed. When 8 was fixed in CVS he updated it and went back to it. Why? Because with ports you have to fiddle with knobs, and look at CVS logs to see when things are updated, etc. With the base system the FreeBSD developers do a good of making sure things (generally) "just work". Said admin used to use Linux heavily (Slackware). He liked the simplicity of Slackware that most of the other distributions lacked. Even Debian which has an awesome way of updating the distribution, but there is a certain "way" of doing things. He doesn't like that. Now, every try updating glibc on a Linux distribution? Unless you have magic utilities (Debian, etc.) that do things for you it's a pain. With FreeBSD you just, cvsup and re-install: no fuss, no mess. Even when I went from 4-STABLE to 5-CURRENT on a test box it was simply a matter of cvsup'ing and re-installing. Do you know what I had to go through when I was using Linux and went from GNU libc 5 to GNU libc 6? And another time, from a.out to ELF? Ugly. > I'm new here, so I'm not telling you how to suck eggs. Perhaps there > are historical reasons for this hierarchy. But I want to make sure I do > the right thing. Is this the safest approach: [...] I'll let others comment on this procedure: I'm not experienced enough with admin'ing boxes yet to really say. -- David Magda Because the innovator has for enemies all those who have done well under the old conditions, and lukewarm defenders in those who may do well under the new. -- Niccolo Machiavelli, _The Prince_, Chapter VI To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Dec 8 9:41:10 2002 Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 486E937B401 for ; Sun, 8 Dec 2002 09:41:09 -0800 (PST) Received: from speicher.org (sirius.speicher.org [209.74.10.51]) by mx1.FreeBSD.org (Postfix) with ESMTP id D3AEB43EB2 for ; Sun, 8 Dec 2002 09:41:07 -0800 (PST) (envelope-from geoff@speicher.org) Received: from localhost (geoff@localhost) by speicher.org (8.11.6/8.11.6) with ESMTP id gB8Ht3F07249; Sun, 8 Dec 2002 12:55:04 -0500 (EST) (envelope-from geoff@speicher.org) Date: Sun, 8 Dec 2002 12:55:03 -0500 (EST) From: "Geoffrey C. Speicher" To: Wes Peters Cc: Don Bowman , "'freebsd-stable@freebsd.org'" Subject: Re: pw useradd not atomic? In-Reply-To: <3DF2DC28.21C1511B@softweyr.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Sat, 7 Dec 2002, Wes Peters wrote: > > This is discussed in bin/38676 in gnats, but there has been no followup > > since June. This problem bit me more than once by corrupting > > master.passwd, so I'm running a locally patched version until some kind of > > fix hits -stable. > > If your patch fixes the problem, have you replied to the PR with it? The original PR included a working patch. Or did you mean something else? Geoff To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Dec 8 10:19:10 2002 Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5CC4737B401 for ; Sun, 8 Dec 2002 10:19:09 -0800 (PST) Received: from sccrmhc02.attbi.com (sccrmhc02.attbi.com [204.127.202.62]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9839243EC5 for ; Sun, 8 Dec 2002 10:19:08 -0800 (PST) (envelope-from timothy@voidnet.com) Received: from repose (12-210-146-224.client.attbi.com[12.210.146.224]) by sccrmhc02.attbi.com (sccrmhc02) with SMTP id <2002120818190700200gcmube>; Sun, 8 Dec 2002 18:19:07 +0000 Content-Type: text/plain; charset="us-ascii" From: Eric Timme To: stable@freebsd.org Subject: ioctl(SIOCGNATL): No such process Date: Sun, 8 Dec 2002 12:19:05 -0600 User-Agent: KMail/1.4.3 MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Message-Id: <200212081219.05959.timothy@voidnet.com> Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG I rebuilt my world last night from stable-cvs, and now when I try and con= nect=20 to the internet through a transparent proxy (tircproxy) working with my=20 former version, the gateway spews=20 ioctl(SIOCGNATL): No such process to my console, and the attempt to connect to IRC fails with "Software cau= sed=20 connection abort", or similar message. Manually attempts to connect to a= =20 remote host yield a successful connection that immediately closes. Ideas? I'm using ipf with ipnat, and my ruleset hasn't changed from the last ker= nel=20 to this one, nor has the kernel file I used to compile with. Thanks, Eric To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Dec 8 10:19:51 2002 Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1665237B401 for ; Sun, 8 Dec 2002 10:19:50 -0800 (PST) Received: from woozle.rinet.ru (woozle.rinet.ru [195.54.192.68]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7564143EA9 for ; Sun, 8 Dec 2002 10:19:48 -0800 (PST) (envelope-from marck@rinet.ru) Received: from localhost (localhost [127.0.0.1]) by woozle.rinet.ru (8.12.5/8.12.5) with ESMTP id gB8IJkTJ000880 for ; Sun, 8 Dec 2002 21:19:46 +0300 (MSK) (envelope-from marck@rinet.ru) Date: Sun, 8 Dec 2002 21:19:46 +0300 (MSK) From: Dmitry Morozovsky To: stable@freebsd.org Subject: fdrop: count < 0 Message-ID: <20021208211802.C97276-100000@woozle.rinet.ru> X-NCC-RegID: ru.rinet MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hi there colleagues, Today I'd encountered sporadic reboots on one of our machines. Unfortunately, there is not enough swap to write crash dump, so I can't provide enough info, sorry. AFAIC, the only place where such error can be emitted is kern_descrip.c:1294: panic("fdrop: count < 0"); Any thoughts/clues? Thanks in advance. Sincerely, D.Marck [DM5020, DM268-RIPE, DM3-RIPN] ------------------------------------------------------------------------ *** Dmitry Morozovsky --- D.Marck --- Wild Woozle --- marck@rinet.ru *** ------------------------------------------------------------------------ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Dec 8 10:28:26 2002 Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 98A6A37B401 for ; Sun, 8 Dec 2002 10:28:25 -0800 (PST) Received: from kanga.honeypot.net (kanga.honeypot.net [208.162.254.122]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7ADAE43E4A for ; Sun, 8 Dec 2002 10:28:24 -0800 (PST) (envelope-from kirk@strauser.com) Received: from pooh.honeypot.net (mail@pooh.honeypot.net [10.0.1.2]) by kanga.honeypot.net (8.12.6/8.12.6) with ESMTP id gB8ISDRO016435 for ; Sun, 8 Dec 2002 12:28:13 -0600 (CST) (envelope-from kirk@strauser.com) Received: from kirk by pooh.honeypot.net with local (Exim 3.36 #1 (Debian)) id 18L6A1-0003uk-00 for ; Sun, 08 Dec 2002 12:28:13 -0600 To: freebsd-stable@freebsd.org Subject: Re: If you shop . . . [DON'T] read this . . . References: <87lm31t3ui.fsf@pooh.honeypot.net> <18580.1039335422@www67.gmx.net> From: Kirk Strauser Date: 08 Dec 2002 12:28:12 -0600 In-Reply-To: <18580.1039335422@www67.gmx.net> Message-ID: <873cp8tlfn.fsf@pooh.honeypot.net> Lines: 9 X-Mailer: Gnus/5.09 (Gnus v5.9.0) Emacs/21.2 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG At 2002-12-08T08:17:02Z, belphoebe@gmx.net writes: > We now return you to your regularly scheduled -STABLE Thank you fnord for the diversion. Hail Eris! -- Kirk Strauser In Googlis non est, ergo non est. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Dec 8 11:47: 7 2002 Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 43F8C37B401 for ; Sun, 8 Dec 2002 11:47:05 -0800 (PST) Received: from mtiwmhc11.worldnet.att.net (mtiwmhc11.worldnet.att.net [204.127.131.115]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9D15043EC5 for ; Sun, 8 Dec 2002 11:47:04 -0800 (PST) (envelope-from cswiger@mac.com) Received: from prime ([12.88.87.97]) by mtiwmhc11.worldnet.att.net (InterMail vM.5.01.05.12 201-253-122-126-112-20020820) with SMTP id <20021208194702.INAP20682.mtiwmhc11.worldnet.att.net@prime> for ; Sun, 8 Dec 2002 19:47:02 +0000 Message-ID: <00bb01c29ef2$9599bcf0$0301a8c0@prime> From: "Charles Swiger" To: References: <2E37135F-0AB4-11D7-B2B7-003065A9024A@ish.com.au> Subject: Re: update strategies Date: Sun, 8 Dec 2002 14:47:04 -0500 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 6.00.2800.1106 X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Aristedes Maniatis wrote: > OK. This is where I get confused. I thought that the point of putting > these applications into the base FreeBSD distribution was that they > need to be tightly integrated into the OS. Some applications do, some don't. Perhaps it would be closer to say that it's highly desirable to have critical pieces of shared infrastructure tightly integrated with the OS. For example, lots of things want to do SSL, nowadays. If the OS can provide a well-tuned, tested version of OpenSSL, plus dependencies (let's add /dev/random to the system; let's compile Apache with mod_ssl by default now; etc), that gives you a better starting point. While I find it satisfying to upgrade old versions of software in quick response to security issues, and there are benefits to being proactive about security, the danger in rolling your own versions lies in limited testing compared with OS vendor patches, and maintainability. There's a cost in terms of time, documentation, organization, and so forth with every change you make to a machine; highly customized or interdependent changes tend to cost a lot, unless you're careful to document everything. Perhaps I should say they cost a lot if you're careful to document everything; if you don't document everything, the next person to muck with it is likely to break the system entirely (because they missed some dependency). Installing the latest OS patches, doing a cvsup and recompile the changed parts (or world), running dselect, or apt, or fink, or portupgrade, are all fairly low in terms of cost and risk. > I understand that this is critical for basic system tools like "adduser". > It appears this makes it important to build the whole distribution together > (buildworld) and not get one tool out of sync with the rest. This is a consideration, yes. If you understand how different components and tools depend on each other, you can save time by only rebuilding the stuff that's necessary. On the other hand, make is pretty good doing that as well, and it errors on the side of caution and building more than it needs to. > But if this is not the case, and we are supposed to build portions of > the /usr/src/ without rebuilding the whole thing, why aren't these > tools in /usr/ports? Which tools? You'll find things like apache, BIND, sendmail, openssh, and so forth in ports as well. [ ... ] > * install ports for named, ssh, etc. > * disable the base FreeBSD distributions of these tools > * use cvsup to update these tools whenever I need to because of > security/bugs/features > * use cvsup to update base FreeBSD (src-all) for each tagged release > (every 3 months or sooner in case of problems). Or less often if the > update doesn't look important. Then buildworld to build a consistent > FreeBSD release. The safest approach would be to track the security branch of the installed OS, and upgrade to RELENG_4_7 [or RELENG_4_(STABLE - 1), perhaps], a week or so after a new release comes out and any initial problems have had a chance to be detected. You should be tracking security advisories and may decide to install your own fixes sooner. This tends to be a good idea for services which the machine is offering (examples are sendmail for a mail server, apache for a web server, BIND for a name server, etc), particularly if you've customized the build of something due to your specific application requirements. Perhaps you have your own apache modules or whatever, for example. Anyway, if you feel you can do a better job of tracking a certain piece of software and keeping it secure or better integrated and tested than the OS vendor currently does, congratulations. :-) At least in the case of FreeBSD, you can also contribute your efforts and help make the OS better by doing things like reporting bugs, generating patches, taking over (or making) a port, etc. -Chuck To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Dec 8 13: 2:45 2002 Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8581337B401; Sun, 8 Dec 2002 13:02:43 -0800 (PST) Received: from falcon.mail.pas.earthlink.net (falcon.mail.pas.earthlink.net [207.217.120.74]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1314A43EC2; Sun, 8 Dec 2002 13:02:43 -0800 (PST) (envelope-from oistrakh@earthlink.net) Received: from h-69-3-208-66.lsanca54.covad.net ([69.3.208.66] helo=pirastro.oistrakh.org) by falcon.mail.pas.earthlink.net with esmtp (Exim 3.33 #1) id 18L8ZI-00058v-00; Sun, 08 Dec 2002 13:02:28 -0800 Received: from pirastro.oistrakh.org (localhost [127.0.0.1]) by pirastro.oistrakh.org (8.12.6/8.12.6) with ESMTP id gB8L2P5s000332; Sun, 8 Dec 2002 13:02:25 -0800 (PST) (envelope-from oistrakh@earthlink.net) Received: (from oistrakh@localhost) by pirastro.oistrakh.org (8.12.6/8.12.6/Submit) id gB8L2N8n000331; Sun, 8 Dec 2002 13:02:23 -0800 (PST) X-Authentication-Warning: pirastro.oistrakh.org: oistrakh set sender to oistrakh@earthlink.net using -f Date: Sun, 8 Dec 2002 13:02:23 -0800 From: Christian Chen To: Peter Leftwich Cc: Michael Nottebrock , "Ulrich 'Q' Spoerlein" , FreeBSD LIST , freebsd-stable@FreeBSD.ORG Subject: Re: Power off problem Message-ID: <20021208210223.GA289@earthlink.net> References: <3DD7E0FA.2080808@gmx.net> <20021117143635.I80685-100000@earl-grey.cloud9.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20021117143635.I80685-100000@earl-grey.cloud9.net> User-Agent: Mutt/1.5.1i Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Sun, Nov 17, 2002 at 02:38:58PM -0500, Peter Leftwich wrote: > On Sun, 17 Nov 2002, Michael Nottebrock wrote: > > Ulrich 'Q' Spoerlein wrote: > > > halt -p or shutdown -p now > > ... does indeed not work on a lot of modern systems. All my athlon boxes > > here will only poweroff with 5-CURRENT, thanks to acpi-support there. > > Michael Nottebrock > > There was another post about having to recompile the kernel as well as add > apmd_enable="YES" to /etc/rc.conf by the way. The most common issue I've seen is that the default apm line in both the GENERIC and LINT files compiles apm0 support in, and then DISABLES it: # Power management support (see LINT for more options) device apm0 at nexus? disable flags 0x20 # Advanced Power Management ^^^^^^^ So not only do you have to make sure you've added device apm0, you also have to delete/comment the "disable" part: device apm0 at nexus? Once I did this and rebuilt my kernel, I've had no problems powering down on several AMD Athlon/Pentium III/Pentium 4 systems. Christian Chen To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Dec 8 13: 7:30 2002 Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D985437B401; Sun, 8 Dec 2002 13:07:28 -0800 (PST) Received: from ece.cmu.edu (ECE.CMU.EDU [128.2.136.200]) by mx1.FreeBSD.org (Postfix) with ESMTP id 21CAE43E4A; Sun, 8 Dec 2002 13:07:28 -0800 (PST) (envelope-from allbery@ece.cmu.edu) Received: from [10.9.204.87] (allbery@dhcp-7-29.dsl.telerama.com [205.201.7.29]) (authenticated) by ece.cmu.edu (8.11.0/8.10.2) with ESMTP id gB8L6uH23885; Sun, 8 Dec 2002 16:06:56 -0500 (EST) Subject: Re: Power off problem From: Brandon S Allbery KF8NH To: Christian Chen Cc: Peter Leftwich , Michael Nottebrock , "Ulrich 'Q' Spoerlein" , FreeBSD LIST , freebsd-stable@FreeBSD.ORG In-Reply-To: <20021208210223.GA289@earthlink.net> References: <3DD7E0FA.2080808@gmx.net> <20021117143635.I80685-100000@earl-grey.cloud9.net> <20021208210223.GA289@earthlink.net> Content-Type: text/plain Organization: Message-Id: <1039381591.1626.1.camel@pyanfar.ece.cmu.edu> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.2.0 Date: 08 Dec 2002 16:06:31 -0500 Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Sun, 2002-12-08 at 16:02, Christian Chen wrote: > So not only do you have to make sure you've added device apm0, you also > have to delete/comment the "disable" part: No, you don't: 2@pyanfar:5001 Z$ cat /boot/kernel.conf di fd1 en apm0 <--- q -- brandon s. allbery [os/2][linux][solaris][japh] allbery@kf8nh.apk.net system administrator [WAY too many hats] allbery@ece.cmu.edu electrical and computer engineering KF8NH carnegie mellon university ["better check the oblivious first" -ke6sls] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Dec 8 13:57:41 2002 Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9261137B401 for ; Sun, 8 Dec 2002 13:57:39 -0800 (PST) Received: from anchor-post-35.mail.demon.net (anchor-post-35.mail.demon.net [194.217.242.85]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0D6DE43EB2 for ; Sun, 8 Dec 2002 13:57:39 -0800 (PST) (envelope-from steve@sliderule.demon.co.uk) Received: from sliderule.demon.co.uk ([80.177.21.188]) by anchor-post-35.mail.demon.net with esmtp (Exim 3.36 #2) id 18L9Qd-0004QB-0U; Sun, 08 Dec 2002 21:57:35 +0000 Message-ID: <3DF3C04D.14C8E88@sliderule.demon.co.uk> Date: Sun, 08 Dec 2002 21:57:33 +0000 From: Steve Burton X-Mailer: Mozilla 4.7 [en-gb] (Win95; U) X-Accept-Language: en,en-GB MIME-Version: 1.0 To: Harald Neuffer Cc: freebsd-stable@FreeBSD.ORG Subject: Re: Via EPIA Mini-ITX motherboard References: <006601c29cab$ec3a9c80$0100000a@D9NLZD0J> <3DF09B14.C9007B42@lrs.eei.uni-erlangen.de> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG FWIW. I have a 4.6.2 system that used the vr driver. It seems to work fine with at 10Megabits but not at 100Megabits (this with a Cisco 2950 switch). Steve. Harald Neuffer wrote: > > George Barnett wrote: > > > > Hi, > > > > Has anybody got experience running a recent snapshot on one of these? > > > > I'm looking to get the C3 800 model and make a small fileserver for home use > > and am looking for feedback on hardware compatibility / problems / etc. > > > > http://www.viavpsd.com/product/epia_mini_itx_spec.jsp?motherboardId=21 > > Hello, > > at the moment I am inquiring for a small motherboard that could be my > kitchen mp3-player and WWW-browser. One of the choices is the mentioned > VIA Eden board, but I found a open PR for the vr ethernet device. See > also: > > http://www.FreeBSD.org/cgi/query-pr.cgi?pr=i386/44572 > > It is still mark as open, but there where some changes at the vr source > recently, thus may it is fixed. > > Does somebody run XFree86 4.2.1 on these kind of boards? > > An alternative would be the board cv860a from Lex. This board is not > mini-itx and has the possibility to have a Intel nic, but it has no PCI > slot. See http://www.lex.com.tw/cv860a.htm > Has somebody run FreeBSD with X and sound on the Lex board? > > See you, > > Harald > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message -- Steve Burton Webmaster & Sub-optimal Coder To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Dec 8 13:58:17 2002 Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3724B37B406 for ; Sun, 8 Dec 2002 13:58:15 -0800 (PST) Received: from smtp-relay.omnis.com (smtp-relay.omnis.com [216.239.128.27]) by mx1.FreeBSD.org (Postfix) with ESMTP id C534B43ED4 for ; Sun, 8 Dec 2002 13:58:13 -0800 (PST) (envelope-from wes@softweyr.com) Received: from softweyr.com (dslpool2-019.networldnoc.net [209.63.227.179]) by smtp-relay.omnis.com (Postfix) with ESMTP id 80C49431E3; Sun, 8 Dec 2002 13:57:56 -0800 (PST) Message-ID: <3DF3C0A6.41041867@softweyr.com> Date: Sun, 08 Dec 2002 13:59:02 -0800 From: Wes Peters Organization: Softweyr LLC X-Mailer: Mozilla 4.78 [en] (X11; U; Linux 2.4.2 i386) X-Accept-Language: en MIME-Version: 1.0 To: Aristedes Maniatis Cc: dmagda@ee.ryerson.ca, Mike Hoskins , freebsd-stable@FreeBSD.ORG Subject: Re: update strategies References: <2E37135F-0AB4-11D7-B2B7-003065A9024A@ish.com.au> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Aristedes Maniatis wrote: > > OK. This is where I get confused. I thought that the point of putting > these applications into the base FreeBSD distribution was that they > need to be tightly integrated into the OS. Not in the case of BIND (and Sendmail, for example). Ther were integrated with the system because "it was always done that way before". > I understand that this is > critical for basic system tools like "adduser". It appears this makes > it important to build the whole distribution together (buildworld) and > not get one tool out of sync with the rest. > > But if this is not the case, and we are supposed to build portions of > the /usr/src/ without rebuilding the whole thing, why aren't these > tools in /usr/ports? See the mailing list archives for YEARS of discussion on this exact same topic. The best answer you'll probably find in your research is because FreeBSD needs SOME sort of resolver library, name services, and even a network mailer to be generally considered functional, and it was a lot easier to leave BIND and Sendmail in the distribution than to adapt sysinstall to forcefully make the average installer choose one of each. Yes, this is pretty lame reason. If you're ready to step up to the plate and do the sysinstall work to overcome this lameness, you'll be welcomed with open arms. > I'm new here, so I'm not telling you how to suck eggs. Perhaps there > are historical reasons for this hierarchy. But I want to make sure I do > the right thing. Is this the safest approach: > > * install ports for named, ssh, etc. > * disable the base FreeBSD distributions of these tools > * use cvsup to update these tools whenever I need to because of > security/bugs/features > * use cvsup to update base FreeBSD (src-all) for each tagged release > (every 3 months or sooner in case of problems). Or less often if the > update doesn't look important. Then buildworld to build a consistent > FreeBSD release. Close. Replace the latter with "follow the FreeBSD security advisories and update both ports and system sources as advised." Be warned that when security advisories come in to the FreeBSD security team, they are most likely to focus on getting fixes into the "base" system, then into ports as needed. If you can offer assistance to the port maintainers for critical infrastructure pieces like name servers and/or mailers, that will be welcomed as well. -- "Where am I, and what am I doing in this handbasket?" Wes Peters Softweyr LLC wes@softweyr.com http://softweyr.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Dec 8 14:27:48 2002 Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id CE37B37B401 for ; Sun, 8 Dec 2002 14:27:46 -0800 (PST) Received: from smtp-1.paradise.net.nz (smtp-1b.paradise.net.nz [202.0.32.210]) by mx1.FreeBSD.org (Postfix) with ESMTP id 246D743EA9 for ; Sun, 8 Dec 2002 14:27:46 -0800 (PST) (envelope-from james.pole@paradise.net.nz) Received: from 203-79-98-71.tnt13.paradise.net.nz (203-79-98-71.tnt13.paradise.net.nz [203.79.98.71]) by smtp-1.paradise.net.nz (Postfix) with ESMTP id 893D982B71 for ; Mon, 9 Dec 2002 11:27:39 +1300 (NZDT) Subject: Re: Power off problem From: James Pole To: stable@freebsd.org Content-Type: text/plain Organization: Message-Id: <1039386429.233.4.camel@localhost> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.2.0 Date: 09 Dec 2002 11:27:09 +1300 Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Mon, 2002-12-09 at 10:06, Brandon S Allbery KF8NH wrote: > On Sun, 2002-12-08 at 16:02, Christian Chen wrote: > > So not only do you have to make sure you've added device apm0, you also > > have to delete/comment the "disable" part: > > No, you don't: > > 2@pyanfar:5001 Z$ cat /boot/kernel.conf > di fd1 > en apm0 <--- > q Not all of us likes to configure the kernel at run-time -- it's much easier to just have it _work_ without having to tweak the kernel's run-time configuration. Anyhow, soft-power-off works perfectly on my AMD computer running 4.7-STABLE from a few weeks ago. It also worked fine under 4.7-RELEASE. - James To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Dec 8 14:29:24 2002 Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 836BF37B401; Sun, 8 Dec 2002 14:29:22 -0800 (PST) Received: from meitner.wh.uni-dortmund.de (meitner.wh.Uni-Dortmund.DE [129.217.129.133]) by mx1.FreeBSD.org (Postfix) with ESMTP id A320943E4A; Sun, 8 Dec 2002 14:29:19 -0800 (PST) (envelope-from michaelnottebrock@gmx.net) Received: from lofi.dyndns.org ([10.3.12.105]) by meitner.wh.uni-dortmund.de (8.10.2/8.10.2/SuSE Linux 8.10.0-0.3) with ESMTP id gB8Ljec04407; Sun, 8 Dec 2002 22:45:43 +0100 X-Authentication-Warning: meitner.wh.uni-dortmund.de: Host [10.3.12.105] claimed to be lofi.dyndns.org Received: from gmx.net (kiste.my.domain [192.168.8.4]) (authenticated bits=0) by lofi.dyndns.org (8.12.6/8.12.6) with ESMTP id gB8MSeck005651 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NO); Sun, 8 Dec 2002 23:28:42 +0100 (CET) (envelope-from michaelnottebrock@gmx.net) Message-ID: <3DF3C793.1070001@gmx.net> Date: Sun, 08 Dec 2002 23:28:35 +0100 From: Michael Nottebrock User-Agent: Mozilla/5.0 (X11; U; Linux i386; en-US; rv:1.0.1) Gecko/20020823 Netscape/7.0 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Brandon S Allbery KF8NH Cc: Christian Chen , Peter Leftwich , "Ulrich 'Q' Spoerlein" , FreeBSD LIST , freebsd-stable@freebsd.org Subject: Re: Power off problem References: <3DD7E0FA.2080808@gmx.net> <20021117143635.I80685-100000@earl-grey.cloud9.net> <20021208210223.GA289@earthlink.net> <1039381591.1626.1.camel@pyanfar.ece.cmu.edu> X-Enigmail-Version: 0.63.3.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enig164CADC81E015CB21140539A" X-Virus-Scanned: by amavisd-milter (http://amavis.org/) Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enig164CADC81E015CB21140539A Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Brandon S Allbery KF8NH wrote: > On Sun, 2002-12-08 at 16:02, Christian Chen wrote: > >>So not only do you have to make sure you've added device apm0, you also >>have to delete/comment the "disable" part: Doh! > No, you don't: > > 2@pyanfar:5001 Z$ cat /boot/kernel.conf > di fd1 > en apm0 <--- > q Doh!! *slaps forehead* Thanks guys. All the boxen here powering down fine now... -- Regards, Michael Nottebrock --------------enig164CADC81E015CB21140539A Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (FreeBSD) Comment: Using GnuPG with Netscape - http://enigmail.mozdev.org iD8DBQE988eYXhc68WspdLARArUrAKCTwBI+JaCXjoRFfAjIaUI5WCUyIwCgmI3L pTdDAGWphaSan3Ov4DT/ySs= =T8qf -----END PGP SIGNATURE----- --------------enig164CADC81E015CB21140539A-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Dec 8 16:49: 8 2002 Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id AAD3B37B401 for ; Sun, 8 Dec 2002 16:49:05 -0800 (PST) Received: from topperwein.dyndns.org (acs-24-154-51-184.zoominternet.net [24.154.51.184]) by mx1.FreeBSD.org (Postfix) with ESMTP id 90FD543EBE for ; Sun, 8 Dec 2002 16:49:04 -0800 (PST) (envelope-from behanna@topperwein.dyndns.org) Received: from topperwein.pennasoft.com (localhost [127.0.0.1]) by topperwein.dyndns.org (8.12.6/8.12.6) with ESMTP id gB90mrH6058951 for ; Sun, 8 Dec 2002 19:48:53 -0500 (EST) (envelope-from behanna@topperwein.dyndns.org) Received: (from behanna@localhost) by topperwein.pennasoft.com (8.12.6/8.12.6/Submit) id gB90mmIq058950 for stable@freebsd.org; Sun, 8 Dec 2002 19:48:48 -0500 (EST) Content-Type: text/plain; charset="iso-8859-1" From: Chris BeHanna Reply-To: chris@pennasoft.com Organization: Western Pennsylvania Pizza Disposal Unit To: stable@freebsd.org Subject: Re: update strategies Date: Sun, 8 Dec 2002 19:48:48 -0500 User-Agent: KMail/1.4.3 References: <867kelp9t9.fsf@number6.magda.ca> <2E37135F-0AB4-11D7-B2B7-003065A9024A@ish.com.au> <20021208144552.GB269@number6.magda.ca> In-Reply-To: <20021208144552.GB269@number6.magda.ca> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Message-Id: <200212081948.48217.chris@pennasoft.com> Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Sunday 08 December 2002 09:45 am, David Magda wrote: > > I'm new here, so I'm not telling you how to suck eggs. Perhaps there > > are historical reasons for this hierarchy. But I want to make sure I do > > the right thing. Is this the safest approach: > > [...] > > I'll let others comment on this procedure: I'm not experienced enough > with admin'ing boxes yet to really say. The safest approach: 1) On production servers, use the RELENG_4_x branch (currently, x = 7). Deploy first on a test box that as nearly as possible mimics your production environment. Beat on it until you are comfortable with it, then deploy *that* *same* *build* on your production hardware (e.g., export /usr/src and /usr/obj over NFS, mount on the production box, and do the installkernel/installworld/mergemaster thing). Given modern hardware, a full buildworld cycle each time the patchlevel is bumped is not onerous[1], especially if you kick the build off when you leave at the end of the day--it's ready for you the following morning. This is a "just in case there are changes in a few places in the tree that interact" anti-foot-shooting measure. 2) Workstations are more forgiving. Follow the -STABLE mailing list. During a window of time in which no one has reported serious bugs on any of the hardware you use, or with any of the software you use, cvsup and do a build/install/mergemaster cycle. If the workstation serves a critical purpose and can't brook downtime from the occasional -STABLE hiccup, then track the RELENG_4_x branch, just as you would for a server, and try it out on a test box first, just as you would for a server. 3) In all cases, the following steps are prudent: a) Make sure to back up /usr/src and /usr/obj *before* you cvsup, so that you can put your system back to a known good state if something goes really wrong. b) Make sure to back up, at the least, /etc, /usr/local/etc, and any critical data you have before updating--this includes the contents of databases. c) Prior to updating, copy your kernel config, LINT, and GENERIC to (e.g.) YOURKERNEL.old, LINT.old, and GENERIC.old. After the update, running diff -u on LINT and GENERIC will clue you in to new options that you may or may not want to apply to your kernel config. d) When running cvsup, it is prudent to run it twice, with a gap of five or ten minute between runs. That way, if your first cvsup occurred in the middle of a large commit, the second cvsup will pick up any files that the first missed. This way, a critical system component with many changes spanning many files won't end up in an intermediate state in your local source tree. Note that if you see changes being downloaded in your 2nd cvsup, you should wait five minutes and then cvsup again. Repeat the cycle until cvsup doesn't change any more files. e) Read and obey /usr/src/UPDATING before and during your upgrade--always. f) Save the timestamp of your last cvsup. When reporting problems, make sure you mention this timestamp in the report--it is the identifier for the snapshot of the source tree that you are running. Be sure you note the timezone of the timestamp--if you do something like: date >> cvsup.log cvsup -g -L2 my_supfile 2>&1 | tee cvsup.out date >> cvsup.log Then the timezone will be your local timezone, so mention it (by the by, CVS itself stores timestamps as GMT). [1] On my 1.33 GHz Athlon w/256MB PC2100 ECC, and my source and object trees living on a vinum-controlled two-disk RAID-0 stripeset (a pair of old IBM 7200rpm 9GB U2W SCSI drives), I can do a buildworld in less than 30 minutes. Currently, that build is I/O-bound. If anyone has done a build with a similar CPU using a malloc disk, I'd be interested in the results. -- Chris BeHanna http://www.pennasoft.com Principal Consultant PennaSoft Corporation chris@pennasoft.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Dec 8 19:30:59 2002 Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1002C37B401 for ; Sun, 8 Dec 2002 19:30:58 -0800 (PST) Received: from magus.nostrum.com (magus.nostrum.com [208.21.192.130]) by mx1.FreeBSD.org (Postfix) with ESMTP id 491A943EBE for ; Sun, 8 Dec 2002 19:30:57 -0800 (PST) (envelope-from pckizer@nostrum.com) Received: from magus.nostrum.com (pckizer@localhost [127.0.0.1]) by magus.nostrum.com (8.12.5/8.12.5) with ESMTP id gB93B5dk045592; Sun, 8 Dec 2002 21:11:05 -0600 (CST) Received: (from pckizer@localhost) by magus.nostrum.com (8.12.5/8.12.5/Submit) id gB93B57S045590; Sun, 8 Dec 2002 21:11:05 -0600 (CST) Message-Id: <200212090311.gB93B57S045590@magus.nostrum.com> From: Philip Kizer To: Mark Nipper Cc: freebsd-stable@FreeBSD.ORG Subject: Re: question about swap files and crash dumps In-reply-to: Your message of "Wed, 27 Nov 2002 13:35:44 CST." <20021127193544.GA4399@ops.tamu.edu> Date: Sun, 08 Dec 2002 21:11:05 -0600 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Mark Nipper wrote: >I have 768MB of physical RAM and only 512MB of swap. Don't ask... :) Yuck, indeed. >The question is, if I add a swap file using the vnode driver, will the >kernel know to make use of the space or does the crash dump handler only >use dedicated swap partitions? Good question on dumping to a vn device, but I doubt it would work, dumpon(8) sets kern.dumpdev with "the device number of the designated special_file". Looks like a physical device is the only option for that. Since I'm just cathing up and your question was 1.5 weeks ago, had any luck since then otherwise? -p To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Dec 8 19:38:54 2002 Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E0DA837B401 for ; Sun, 8 Dec 2002 19:38:52 -0800 (PST) Received: from hardtime.linuxman.net (hardtime.linuxman.net [66.147.26.65]) by mx1.FreeBSD.org (Postfix) with ESMTP id D110C43ED4 for ; Sun, 8 Dec 2002 19:38:51 -0800 (PST) (envelope-from fullermd@over-yonder.net) Received: from mortis.over-yonder.net (localhost [127.0.0.1]) by hardtime.linuxman.net (8.11.6/8.11.6) with ESMTP id gB956mp18457; Sun, 8 Dec 2002 23:06:49 -0600 Received: by mortis.over-yonder.net (Postfix, from userid 100) id 569AD1F3B; Sun, 8 Dec 2002 21:38:37 -0600 (CST) Date: Sun, 8 Dec 2002 21:38:36 -0600 From: "Matthew D. Fuller" To: "Geoffrey C. Speicher" Cc: Don Bowman , "'freebsd-stable@freebsd.org'" Subject: Re: pw useradd not atomic? Message-ID: <20021209033836.GE67692@over-yonder.net> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4i-fullermd.1 X-Editor: vi X-OS: FreeBSD Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Sat, Dec 07, 2002 at 02:46:02AM -0500 I heard the voice of Geoffrey C. Speicher, and lo! it spake thus: > On Fri, 6 Dec 2002, Don Bowman wrote: > > > Sometimes after this script been run I end up with only the > > last few lines of the groups file. > > > > Is 'pw' not atomic somehow? The lines that are there seem > > complete, i'm just missing the first 100 lines or so. Its > > not always the same amount missing. > > This is discussed in bin/38676 in gnats, but there has been no followup > since June. This problem bit me more than once by corrupting > master.passwd, so I'm running a locally patched version until some kind of > fix hits -stable. There was also a good long discussion on -stable and -hackers over it. See PR bin/40127 for some of the code I had written to wrap a giant lock around it in a way that is generalized. Somewhere, I have the patches to pw(8) and friends to use that code that I could dig up; many of them were posted on the various threads referenced in that PR. I may be able to resurrect all my patches if there's interest; the previous thread pretty much petered out without anybody with a commit bit poking in enough interest to do anything with it. -- Matthew Fuller (MF4839) | fullermd@over-yonder.net Systems/Network Administrator | http://www.over-yonder.net/~fullermd/ "The only reason I'm burning my candle at both ends, is because I haven't figured out how to light the middle yet" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Dec 8 23: 8:40 2002 Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 05BA337B401 for ; Sun, 8 Dec 2002 23:08:39 -0800 (PST) Received: from smtp1.eunet.yu (smtp1.EUnet.yu [194.247.192.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7992843EBE for ; Sun, 8 Dec 2002 23:08:37 -0800 (PST) (envelope-from kolicz@eunet.yu) Received: (from root@localhost) by smtp1.eunet.yu (8.11.6/8.11.6) id gB978Ue00928 for freebsd-stable@FreeBSD.ORG.KAV; Mon, 9 Dec 2002 08:08:30 +0100 Received: from localhost.localdomain (P-2.100.eunet.yu [213.240.2.100]) by smtp1.eunet.yu (8.11.6/8.11.6) with ESMTP id gB978Td31359 for ; Mon, 9 Dec 2002 08:08:30 +0100 Content-Type: text/plain; charset="us-ascii" From: Zoran Kolic Reply-To: kolicz@eunet.yu To: freebsd-stable@FreeBSD.ORG Subject: X Date: Mon, 9 Dec 2002 08:07:10 +0100 User-Agent: KMail/1.4.1 MIME-Version: 1.0 Message-Id: <200212090807.10954.kolicz@eunet.yu> Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by smtp1.eunet.yu id gB978Td31359 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Dear folks! I have release 4.7 and a lot of problems with ATI radeon VE card and KFC CB6546SL monitor on my workstation. It works perfect on linux, but freeBSD doesn't run it proprerly. Papers say about parameters, system says "It's not what I want". I've used every possible combination. KDE looks dicent, by I like small managers like fvwm, blackbox... They are funky. Black and of bad behaviour. Does someone have expirience with this monitor. I believed that X-problems are past. Did't sand any output due to it looks as a metter of simple input of parameters. Best regards Zoran To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Dec 9 1:21:21 2002 Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 92B0737B401 for ; Mon, 9 Dec 2002 01:21:13 -0800 (PST) Received: from goliath.siemens.de (goliath.siemens.de [192.35.17.28]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7739143EFF for ; Mon, 9 Dec 2002 01:21:11 -0800 (PST) (envelope-from andre.albsmeier@mchp.siemens.de) Received: from mail1.siemens.de (mail1.siemens.de [139.23.33.14]) by goliath.siemens.de (8.11.6/8.11.6) with ESMTP id gB99L4q18259 for ; Mon, 9 Dec 2002 10:21:04 +0100 (MET) Received: from curry.mchp.siemens.de (curry.mchp.siemens.de [139.25.42.7]) by mail1.siemens.de (8.11.6/8.11.6) with ESMTP id gB99L4327499 for ; Mon, 9 Dec 2002 10:21:04 +0100 (MET) Received: (from localhost) by curry.mchp.siemens.de (8.12.6/8.12.6) id gB99L3UY019713; Date: Mon, 9 Dec 2002 10:21:03 +0100 From: Andre Albsmeier To: freebsd-stable@FreeBSD.ORG Cc: Andre.Albsmeier@mchp.siemens.de Subject: panic: page fault on 4.7-STABLE Message-ID: <20021209102103.A43135@curry.mchp.siemens.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable User-Agent: Mutt/1.2.5.1i X-Echelon: 15kg, smuggle, FBI, strike, SEMTEX Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG This happened on my server two nights ago (solid machine: Asus P3B-F board, not overclocked, Kingston ECC RAM, Adaptec SCSI controllers, Enermax 430W Power Supply): The box was building a giant tar file on a temporary holding disk so it can be dumped onto the attached DLT-8000 drive (like it does it every night). Today I discovered that it had crashed during this process. Last night everything went well again (as it did for the last years as well :-). root@server:/var/crash>gdb -k /usr/obj/src/src-4/sys/server/kernel.debug vm= core.14 GNU gdb 4.18 (FreeBSD) Copyright 1998 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain condition= s. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "i386-unknown-freebsd"...Deprecated bfd_read cal= led at /src/src-4/gnu/usr.bin/binutils/gdb/../../../../contrib/gdb/gdb/dbxr= ead.c line 2627 in elfstab_build_psymtabs Deprecated bfd_read called at /src/src-4/gnu/usr.bin/binutils/gdb/../../../= ../contrib/gdb/gdb/dbxread.c line 933 in fill_symbuf IdlePTD at phsyical address 0x0030e000 initial pcb at physical address 0x0028bf20 panicstr: page fault panic messages: --- Fatal trap 12: page fault while in kernel mode fault virtual address =3D 0x4c fault code =3D supervisor read, page not present instruction pointer =3D 0x8:0xc0211a50 stack pointer =3D 0x10:0xd6c62c8c frame pointer =3D 0x10:0xd6c62c94 code segment =3D base 0x0, limit 0xfffff, type 0x1b =3D DPL 0, pres 1, def32 1, gran 1 processor eflags =3D interrupt enabled, resume, IOPL =3D 0 current process =3D 14414 (gtar) interrupt mask =3D bio=20 trap number =3D 12 panic: page fault syncing disks... 49 28 27 26 26 26 26 26 26 26 27 25 25 25 25 25 25 25 28 2= 5 25 25 25 25 25 25 25 25 25 25 25 25 25 25 25 25 25 25 25=20 giving up on 17 buffers Uptime: 7d12h50m6s dumping to dev #da/9, offset 276584 dump 511 510 509 508 507 506 505 504 503 502 501 500 499 498 497 496 495 49= 4 493 492 491 490 489 488 487 486 485 484 483 482 481 480 479 478 477 476 4= 75 474 473 472 471 470 469 468 467 466 465 464 463 462 461 460 459 458 457 = 456 455 454 453 452 451 450 449 448 447 446 445 444 443 442 441 440 439 438= 437 436 435 434 433 432 431 430 429 428 427 426 425 424 423 422 421 420 41= 9 418 417 416 415 414 413 412 411 410 409 408 407 406 405 404 403 402 401 4= 00 399 398 397 396 395 394 393 392 391 390 389 388 387 386 385 384 383 382 = 381 380 379 378 377 376 375 374 373 372 371 370 369 368 367 366 365 364 363= 362 361 360 359 358 357 356 355 354 353 352 351 350 349 348 347 346 345 34= 4 343 342 341 340 339 338 337 336 335 334 333 332 331 330 329 328 327 326 3= 25 324 323 322 321 320 319 318 317 316 315 314 313 312 311 310 309 308 307 = 306 305 304 303 302 301 300 299 298 297 296 295 294 293 292 291 290 289 288= 287 286 285 284 283 282 281 280 279 278 277 276 275 274 273 272 271 270 26= 9 268 267 266 265 264 263 262 261 260 259 258 257 256 255 254 253 252 251 2= 50 249 248 247 246 245 244 243 242 241 240 239 238 237 236 235 234 233 232 = 231 230 229 228 227 226 225 224 223 222 221 220 219 218 217 216 215 214 213= 212 211 210 209 208 207 206 205 204 203 202 201 200 199 198 197 196 195 19= 4 193 192 191 190 189 188 187 186 185 184 183 182 181 180 179 178 177 176 1= 75 174 173 172 171 170 169 168 167 166 165 164 163 162 161 160 159 158 157 = 156 155 154 153 152 151 150 149 148 147 146 145 144 143 142 141 140 139 138= 137 136 135 134 133 132 131 130 129 128 127 126 125 124 123 122 121 120 11= 9 118 117 116 115 114 113 112 111 110 109 108 107 106 105 104 103 102 101 1= 00 99 98 97 96 95 94 93 92 91 90 89 88 87 86 85 84 83 82 81 80 79 78 77 76 = 75 74 73 72 71 70 69 68 67 66 65 64 63 62 61 60 59 58 57 56 55 54 53 52 51 = 50 49 48 47 46 45 44 43 42 41 40 39 38 37 36 35 34 33 32 31 30 29 28 27 26 = 25 24 23 22 21 20 19 18 17 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0=20 --- #0 dumpsys () at /src/src-4/sys/kern/kern_shutdown.c:487 487 if (dumping++) { (kgdb) where #0 dumpsys () at /src/src-4/sys/kern/kern_shutdown.c:487 #1 0xc016242b in boot (howto=3D256) at /src/src-4/sys/kern/kern_shutdown.c= :316 #2 0xc0162850 in poweroff_wait (junk=3D0xc026566c, howto=3D-1071230577) at= /src/src-4/sys/kern/kern_shutdown.c:595 #3 0xc02351c6 in trap_fatal (frame=3D0xd6c62c4c, eva=3D76) at /src/src-4/s= ys/i386/i386/trap.c:974 #4 0xc0234e99 in trap_pfault (frame=3D0xd6c62c4c, usermode=3D0, eva=3D76) = at /src/src-4/sys/i386/i386/trap.c:867 #5 0xc0234a83 in trap (frame=3D{tf_fs =3D 92012560, tf_es =3D 16, tf_ds = =3D -691666928, tf_edi =3D -855842988, tf_esi =3D 3255426, tf_ebp =3D -6916= 55532, tf_isp =3D -691655560, tf_ebx =3D -697071168, tf_edx =3D 56,=20 tf_ecx =3D 1605556592, tf_eax =3D 25783, tf_trapno =3D 12, tf_err =3D= 0, tf_eip =3D -1071572400, tf_cs =3D 8, tf_eflags =3D 66050, tf_esp =3D -1= 062613128, tf_ss =3D 3255426}) at /src/src-4/sys/i386/i386/trap.c:466 #6 0xc0211a50 in vm_page_lookup (object=3D0xd67389c0, pindex=3D3255426) at= /src/src-4/sys/vm/vm_page.c:514 #7 0xc0189f02 in allocbuf (bp=3D0xccfcdf54, size=3D16384) at /src/src-4/sy= s/kern/vfs_bio.c:2510 #8 0xc0189af6 in getblk (vp=3D0xd6d04a40, blkno=3D813856, size=3D16384, sl= pflag=3D0, slptimeo=3D0) at /src/src-4/sys/kern/vfs_bio.c:2292 #9 0xc01f61d2 in ffs_balloc (ap=3D0xd6c62e2c) at /src/src-4/sys/ufs/ffs/ff= s_balloc.c:303 #10 0xc01ff6f1 in ffs_write (ap=3D0xd6c62e64) at vnode_if.h:1056 #11 0xc0197162 in vn_write (fp=3D0xc4897900, uio=3D0xd6c62ed4, cred=3D0xc33= eba80, flags=3D0, p=3D0xd6c59c60) at vnode_if.h:363 #12 0xc0171485 in dofilewrite (p=3D0xd6c59c60, fp=3D0xc4897900, fd=3D3, buf= =3D0x806e400, nbyte=3D10240, offset=3D-1, flags=3D0) at /src/src-4/sys/sys/= file.h:163 #13 0xc017133e in write (p=3D0xd6c59c60, uap=3D0xd6c62f80) at /src/src-4/sy= s/kern/sys_generic.c:329 #14 0xc0235475 in syscall2 (frame=3D{tf_fs =3D -1078001617, tf_es =3D -6916= 66897, tf_ds =3D 47, tf_edi =3D 0, tf_esi =3D 134669312, tf_ebp =3D -107793= 9692, tf_isp =3D -691654700, tf_ebx =3D 10240, tf_edx =3D 134679552,=20 tf_ecx =3D 0, tf_eax =3D 4, tf_trapno =3D 22, tf_err =3D 2, tf_eip = =3D 537907000, tf_cs =3D 31, tf_eflags =3D 659, tf_esp =3D -1077939736, tf_= ss =3D 47}) at /src/src-4/sys/i386/i386/trap.c:1175 #15 0xc02295d5 in Xint0x80_syscall () #16 0x8049fdb in ?? () #17 0x804b0d1 in ?? () #18 0x804bc8d in ?? () #19 0x8049ddd in ?? () #20 0x804e0fa in ?? () #21 0x804f4a6 in ?? () #22 0x804f001 in ?? () #23 0x804f001 in ?? () #24 0x804f001 in ?? () #25 0x804f001 in ?? () #26 0x804f001 in ?? () #27 0x804f001 in ?? () #28 0x804f001 in ?? () #29 0x804f001 in ?? () #30 0x804ea3d in ?? () #31 0x8058fc9 in ?? () #32 0x8049b51 in ?? () (kgdb)=20 If anyone wants me to examine certain data: tell me, I'll keep the core file for a while. Ah, here is the dmesg in case it helps: Copyright (c) 1992-2002 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 4.7-STABLE #0: Fri Nov 29 09:43:46 CET 2002 root@bali.ofw.tld:/src/obj-4/src/src-4/sys/server Timecounter "i8254" frequency 1193189 Hz Timecounter "TSC" frequency 1029990375 Hz CPU: Pentium III/Pentium III Xeon/Celeron (1000.07-MHz 686-class CPU) Origin =3D "GenuineIntel" Id =3D 0x686 Stepping =3D 6 Features=3D0x383f9ff real memory =3D 536788992 (524208K bytes) avail memory =3D 519434240 (507260K bytes) Preloaded elf kernel "kernel" at 0xc02ef000. ccd0-2: Concatenated disk drivers Pentium Pro MTRR support enabled Using $PIR table, 8 entries at 0xc00f0e80 npx0: on motherboard npx0: INT 16 interface pcib0: on motherboard pci0: on pcib0 pcib1: at device 1.0 on pci0 pci1: on pcib1 pci1: at 0.0 irq 11 isab0: at device 4.0 on pci0 isa0: on isab0 pci0: at 4.1 pci0: at 4.2 intpm0: port 0xe800-0xe80f irq = 9 at device 4.3 on pci0 intpm0: I/O mapped e800 intpm0: intr IRQ 9 enabled revision 0 smbus0: on intsmb0 smb0: on smbus0 intpm0: PM I/O mapped e400=20 ahc0: port 0xd000-0xd0ff mem 0xdf0000= 00-0xdf000fff irq 15 at device 9.0 on pci0 ahc0: Bugs (0x0040): SCBCHAN_UPLOAD aic7892: Ultra160 Wide Channel A, SCSI Id=3D7, 32/253 SCBs ahc1: port 0xb800-0xb8ff mem 0xde8000= 00-0xde800fff irq 10 at device 11.0 on pci0 ahc1: Bugs (0x0040): SCBCHAN_UPLOAD aic7892: Ultra160 Wide Channel A, SCSI Id=3D7, 32/253 SCBs pcib2: at device 12.0 on pci0 pci2: on pcib2 fxp0: port 0xa800-0xa81f mem 0xde000000-0= xde0fffff,0xe3000000-0xe3000fff irq 11 at device 4.0 on pci2 fxp0: Ethernet address 00:90:27:d3:16:b7 inphy0: on miibus0 inphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto fxp1: port 0xa400-0xa41f mem 0xdd800000-0= xdd8fffff,0xe2800000-0xe2800fff irq 10 at device 5.0 on pci2 fxp1: Ethernet address 00:90:27:d3:16:b8 inphy1: on miibus1 inphy1: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto ahc2: port 0x9800-0x98ff mem 0xdd0000= 00-0xdd000fff irq 15 at device 13.0 on pci0 ahc2: Bugs (0x0040): SCBCHAN_UPLOAD aic7892: Ultra160 Wide Channel A, SCSI Id=3D7, 32/253 SCBs ahc3: port 0x9400-0x94ff mem 0xdc8000= 00-0xdc800fff irq 12 at device 14.0 on pci0 ahc3: Bugs (0x0040): SCBCHAN_UPLOAD aic7892: Ultra160 Wide Channel A, SCSI Id=3D7, 32/253 SCBs orm0: