From owner-freebsd-stable Sun Oct 5 02:04:47 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id CAA08053 for stable-outgoing; Sun, 5 Oct 1997 02:04:47 -0700 (PDT) Received: from shasta.wstein.com (shasta.wstein.com [207.173.11.132]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id CAA08045 for ; Sun, 5 Oct 1997 02:04:42 -0700 (PDT) Received: (from joes@localhost) by shasta.wstein.com (8.8.7/8.8.7) id CAA05857 for stable@freebsd.org; Sun, 5 Oct 1997 02:04:38 -0700 (PDT) From: Joseph Stein Message-Id: <199710050904.CAA05857@shasta.wstein.com> Subject: pstat? To: stable@freebsd.org Date: Sun, 5 Oct 1997 02:04:37 -0700 (PDT) X-Mailer: ELM [version 2.4ME+ PL31H (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Has anybody thought about fixing pstat before 2.2.5 rolls out? From my machine (9/30/97 build): --- pstat: sysctl: KERN_VNODE: No such file or directory 159/4136 files --- just a thought, Joe From owner-freebsd-stable Sun Oct 5 02:39:54 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id CAA09376 for stable-outgoing; Sun, 5 Oct 1997 02:39:54 -0700 (PDT) Received: from silent.darkening.com (nonxstnt@iskh122.haninge.kth.se [130.237.83.122]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id CAA09371 for ; Sun, 5 Oct 1997 02:39:52 -0700 (PDT) Received: from localhost (nonxstnt@localhost) by silent.darkening.com (8.8.7/8.8.7) with SMTP id LAA04564 for ; Sun, 5 Oct 1997 11:39:04 +0200 (CEST) X-Authentication-Warning: silent.darkening.com: nonxstnt owned process doing -bs Date: Sun, 5 Oct 1997 11:39:03 +0200 (CEST) From: nobody To: freebsd-stable@freebsd.org Subject: hangups Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from QUOTED-PRINTABLE to 8bit by hub.freebsd.org id CAA09372 Sender: owner-freebsd-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I've been helping several friends with PPP under RELENG's and 2.2.5-BETA, and all my friends who use PPP (ex. FTP install over PPP, or the userlevel PPP) have complained about constant hangups (via 3 different ISP's). Is there any kind of problem I should be knowing about? Cant seem to get an FTP install to finish with any of them. --- thomas strömberg . system admin, royal institute of technology (stockholm) nobody@darkening.com . irc:nobody@EFnet . talk:nonxstnt@silent.darkening.com real coders don't use comments. It was hard to write; it should be hard to read From owner-freebsd-stable Sun Oct 5 03:03:09 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id DAA10681 for stable-outgoing; Sun, 5 Oct 1997 03:03:09 -0700 (PDT) Received: from implode.root.com (implode.root.com [198.145.90.17]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id DAA10676 for ; Sun, 5 Oct 1997 03:03:04 -0700 (PDT) Received: from implode.root.com (localhost [127.0.0.1]) by implode.root.com (8.8.5/8.8.5) with ESMTP id DAA18504; Sun, 5 Oct 1997 03:05:01 -0700 (PDT) Message-Id: <199710051005.DAA18504@implode.root.com> To: Joseph Stein cc: stable@FreeBSD.ORG Subject: Re: pstat? In-reply-to: Your message of "Sun, 05 Oct 1997 02:04:37 PDT." <199710050904.CAA05857@shasta.wstein.com> From: David Greenman Reply-To: dg@root.com Date: Sun, 05 Oct 1997 03:05:01 -0700 Sender: owner-freebsd-stable@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >Has anybody thought about fixing pstat before 2.2.5 rolls out? From >my machine (9/30/97 build): >--- > >pstat: sysctl: KERN_VNODE: No such file or directory >159/4136 files I've thought about it. :-) -DG David Greenman Core-team/Principal Architect, The FreeBSD Project From owner-freebsd-stable Sun Oct 5 03:38:25 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id DAA12025 for stable-outgoing; Sun, 5 Oct 1997 03:38:25 -0700 (PDT) Received: from bubble.didi.com (sjx-ca25-27.ix.netcom.com [204.30.65.219]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id DAA12018 for ; Sun, 5 Oct 1997 03:38:15 -0700 (PDT) Received: (from asami@localhost) by bubble.didi.com (8.8.7/8.8.5) id DAA05559; Sun, 5 Oct 1997 03:36:11 -0700 (PDT) Date: Sun, 5 Oct 1997 03:36:11 -0700 (PDT) Message-Id: <199710051036.DAA05559@bubble.didi.com> To: rgrimes@GndRsh.aac.dev.com CC: dg@root.com, jkh@time.cdrom.com, andrsn@andrsn.stanford.edu, freebsd-stable@FreeBSD.ORG In-reply-to: <199710032101.OAA00264@GndRsh.aac.dev.com> (rgrimes@GndRsh.aac.dev.com) Subject: Re: CVSUP vs. SNAPS From: asami@cs.berkeley.edu (Satoshi Asami) Sender: owner-freebsd-stable@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk * David, perhaps you should try and figure out just what OS I am running: * Orbit:root {104}# uname -a * FreeBSD Orbit.qcsn.com 2.2-STABLE FreeBSD 2.2-STABLE #2: Fri Sep 19 13:56:36 PDT 1997 root@Orbit.aac.dev.com:/usr/src/sys/compile/ORBIT i386 * * Now you tell me, is that before or after 2.2.2??? I don't know. All I know is that you built your kernel on 9/19. Why does it matter whether it's before or after 2.2.2? What I need (if I were David trying to debug your system), what I need is exactly when you cvsupped (and cvs updated) your stuff last. Whether you did that before or after 2.2.2 is really too large of a glanurality to be of any help. You are tracking a moving target for christsakes, the uname can say "FreeBSD-STABLE" for all we care (except that will be confusing because of 2.1 and 2.2). Besides, if I show you a uname that says "3.0-CURRENT Fri Jan 18 13:56:36 PST 1998", can you tell whether it's before or after 3.0R? Satoshi From owner-freebsd-stable Sun Oct 5 04:00:57 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id EAA12796 for stable-outgoing; Sun, 5 Oct 1997 04:00:57 -0700 (PDT) Received: from awfulhak.demon.co.uk (awfulhak.demon.co.uk [158.152.17.1]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id EAA12786 for ; Sun, 5 Oct 1997 04:00:39 -0700 (PDT) Received: from gate.lan.awfulhak.org (localhost [127.0.0.1]) by awfulhak.demon.co.uk (8.8.5/8.8.5) with ESMTP id LAA12422; Sun, 5 Oct 1997 11:58:20 +0100 (BST) Message-Id: <199710051058.LAA12422@awfulhak.demon.co.uk> X-Mailer: exmh version 2.0zeta 7/24/97 To: nobody cc: freebsd-stable@FreeBSD.ORG Subject: Re: hangups In-reply-to: Your message of "Sun, 05 Oct 1997 11:39:03 +0200." Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Date: Sun, 05 Oct 1997 11:58:20 +0100 From: Brian Somers Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by hub.freebsd.org id EAA12790 Sender: owner-freebsd-stable@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > I've been helping several friends with PPP under RELENG's and 2.2.5-BETA, > and all my friends who use PPP (ex. FTP install over PPP, or the > userlevel PPP) have complained about constant hangups (via 3 different > ISP's). > > Is there any kind of problem I should be knowing about? Cant seem to get > an FTP install to finish with any of them. You could try suggesting a "set reconnect 5 100" (check the man page for what this means). However, if this is happening frequently, I'd look for a dodgy modem setting that isn't very tolerant of temporary CD glitches. On a USR Sportster for example, you may want to ATS10=10 so that carrier must be lost for a whole second before the modem notices. Remember, never use "set reconnect" with a timeout value that's less than your ISP..... > --- > thomas strömberg . system admin, royal institute of technology (stockholm) > nobody@darkening.com . irc:nobody@EFnet . talk:nonxstnt@silent.darkening.com > real coders don't use comments. It was hard to write; it should be hard to read -- Brian , , Don't _EVER_ lose your sense of humour.... From owner-freebsd-stable Sun Oct 5 05:30:42 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id FAA16185 for stable-outgoing; Sun, 5 Oct 1997 05:30:42 -0700 (PDT) Received: from emout05.mail.aol.com (emout05.mx.aol.com [198.81.11.96]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id FAA16178 for ; Sun, 5 Oct 1997 05:30:40 -0700 (PDT) From: Hetzels@aol.com Received: (from root@localhost) by emout05.mail.aol.com (8.7.6/8.7.3/AOL-2.0.0) id IAA26488; Sun, 5 Oct 1997 08:30:01 -0400 (EDT) Date: Sun, 5 Oct 1997 08:30:01 -0400 (EDT) Message-ID: <971005083000_1543650796@emout05.mail.aol.com> To: chad@dcfinc.com cc: freebsd-stable@freebsd.org Subject: Re: CVSup release identity Sender: owner-freebsd-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk In a message dated 97-10-04 18:27:20 EDT, chad@freebie.dcfinc.com writes: > > I agree that it needs a little work in order to support cvs & ctm. > > One thought is to make .ctm_status a permant part of the source tree > > and to have an additional file .cvs_status that would be used to track > > version #'s of source files that have changed between each CTM delta. > > That way a CVS user could pull down modified source files and know how > > far off from the CTM delta they are. > > Reverse the thinking. Make .cvs_status a permanent part of the tree, > and increment it each and every time a change is comitted. Then there > is a known place to get a marker of where along the line of updates a > particular system resides. > I see one problem with a permanant .cvs_status file. If commiter A changes files X,Y, & Z, does he increment .cvs_status for each file or per change. Then if 2 commiters A (X, Y, Z) & B (D, E) change files which one changes the .cvs_status file. What prevents them from submitting the same change to the file? A tool that would automaticly update the .cvs_status file would then be needed. I suggested the .ctm_status file because there is already such a tool to create this file. Besides how fine a grain do you need?, An Exact version identity, or at least knowing that your between point A & B. Thus, if someone reports a bug at point A, and it is fixed at point B, all anyone has to say is update your system to at least point B and your problem is solved. Since CTM deltas are created every so often during the day, it makes the perfect choice to track where the source tree is at during any given time period. Scot From owner-freebsd-stable Sun Oct 5 05:36:25 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id FAA16491 for stable-outgoing; Sun, 5 Oct 1997 05:36:25 -0700 (PDT) Received: from emout11.mail.aol.com (emout11.mx.aol.com [198.81.11.26]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id FAA16481 for ; Sun, 5 Oct 1997 05:36:22 -0700 (PDT) From: Hetzels@aol.com Received: (from root@localhost) by emout11.mail.aol.com (8.7.6/8.7.3/AOL-2.0.0) id IAA25452 for freebsd-stable@freebsd.org; Sun, 5 Oct 1997 08:35:51 -0400 (EDT) Date: Sun, 5 Oct 1997 08:35:51 -0400 (EDT) Message-ID: <971005083550_897666284@emout11.mail.aol.com> To: freebsd-stable@freebsd.org Subject: Re: CVSup release identity Sender: owner-freebsd-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk JKH, Is there a cron job that checks the sources for changes since the last CTM update, and if there is a change, create a new .ctm_status file, and roll a CTM delta. How often does such a job check the source tree? (Every couple of Hours?) Scot From owner-freebsd-stable Sun Oct 5 06:15:34 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id GAA17781 for stable-outgoing; Sun, 5 Oct 1997 06:15:34 -0700 (PDT) Received: from emout05.mail.aol.com (emout05.mx.aol.com [198.81.11.96]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id GAA17776 for ; Sun, 5 Oct 1997 06:15:30 -0700 (PDT) From: Hetzels@aol.com Received: (from root@localhost) by emout05.mail.aol.com (8.7.6/8.7.3/AOL-2.0.0) id JAA15703; Sun, 5 Oct 1997 09:14:59 -0400 (EDT) Date: Sun, 5 Oct 1997 09:14:59 -0400 (EDT) Message-ID: <971005091458_-826790286@emout05.mail.aol.com> To: rkw@dataplex.net cc: stable@freebsd.org Subject: Fwd: CVSup release identity Sender: owner-freebsd-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk rkw, We are having a discussion in STABLE about how best to track each persons position in CVS, & CTM. Basically, We would like to be able to do a uname -r which will result in the message: FreeBSD 2.2-STABLE-AB or FreeBSD 2.2-STABLE (0360) I suggested using the .ctm_status file as a permant part of the source tree, because it does produce a # every so often during the day. Could you please advise on how often the CTM deltas are created? In a message dated 97-10-05 09:06:01 EDT, jkh@time.cdrom.com writes: > I have no idea - I don't have anything to do with CTM delta > generation. :) > > Talk to rkw@dataplex.net > > Jordan > > > JKH, > > > > Is there a cron job that checks the sources for changes since the last > CTM > > update, and if there is a change, create a new .ctm_status file, and roll > a > > CTM delta. > > > > How often does such a job check the source tree? (Every couple of Hours?) > > > > Scot > --------------------- Forwarded message: From: jkh@time.cdrom.com (Jordan K. Hubbard) To: Hetzels@aol.com Date: 97-10-05 09:06:01 EDT I have no idea - I don't have anything to do with CTM delta generation. :) Talk to rkw@dataplex.net Jordan > JKH, > > Is there a cron job that checks the sources for changes since the last CTM > update, and if there is a change, create a new .ctm_status file, and roll a > CTM delta. > > How often does such a job check the source tree? (Every couple of Hours?) > > Scot From owner-freebsd-stable Sun Oct 5 07:25:02 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id HAA20281 for stable-outgoing; Sun, 5 Oct 1997 07:25:02 -0700 (PDT) Received: from cgi.sstar.com (cgi.sstar.com [204.27.72.160]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id HAA20269 for ; Sun, 5 Oct 1997 07:24:58 -0700 (PDT) Received: from jim-home (p04.sstar.com [204.27.72.36]) by cgi.sstar.com (8.8.7/8.7.3) with SMTP id JAA22611 for ; Sun, 5 Oct 1997 09:24:55 -0500 (CDT) Message-Id: <3.0.2.32.19971005092418.006c18fc@mail.sstar.com> X-Sender: jim.king@mail.sstar.com X-Mailer: QUALCOMM Windows Eudora Light Version 3.0.2 (32) Date: Sun, 05 Oct 1997 09:24:18 -0500 To: freebsd-stable@freebsd.org From: Jim King Subject: DE21140-AE in 2.2.5 In-Reply-To: <199710050313.VAA07177@obie.softweyr.ml.org> References: <3.0.1.32.19971002102621.009a3790@mail.sstar.com> <3.0.1.32.19971002102621.009a3790@mail.sstar.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk At 09:13 PM 10/4/97 -0600, Wes Peters wrote: >Jim King writes: > > The boot disk from 2.2-971002-BETA doesn't like my Netgear Fast Ethernet card: > > > > de0 rev 34 int a irq 9 on pci0:17 > > de0: 21140A [10-100Mb/s] pass 2.2 > > de0: address 00:40:05:37:e8:f7 > > de0: enabling 100baseTX port > > > > As soon as this message appears the link light on the hub goes out. > > Network stuff doesn't work in the install program. As soon as I exit the > > install program the link light on the hub comes on. > > > > Is there an ifconfig option to make this card work? > >You don't mention if the hub is 10Base-T or 100Base-TX. Fast or not? Fast, although I seem to get the same results with a 10BaseT hub (the 10BaseT hub is another room, so I can't watch the link lights on it). From owner-freebsd-stable Sun Oct 5 08:21:45 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id IAA25097 for stable-outgoing; Sun, 5 Oct 1997 08:21:45 -0700 (PDT) Received: from hetzels (171-83-74.ipt.aol.com [152.171.83.74]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id IAA25078; Sun, 5 Oct 1997 08:20:59 -0700 (PDT) From: "Scot W. Hetzel" To: "Frank Volf" , Cc: "Stable" Subject: Re: CTM patch level added to newvers.sh Date: Sun, 5 Oct 1997 10:18:32 -0500 Message-ID: <01bcd1a1$f152b340$4a53ab98@hetzels> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 4.71.1712.3 X-MimeOle: Produced By Microsoft MimeOLE V4.71.1712.3 Sender: owner-freebsd-stable@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk -----Original Message----- From: Frank Volf Newsgroups: list.freebsd.stable To: Hetzels@aol.com ; nate@mt.sri.com Date: Sunday, October 05, 1997 9:39 AM Subject: Re: CTM patch level added to newvers.sh >In article <971004143220_-729141990@emout19.mail.aol.com>, > wrote: >>In a message dated 97-10-04 14:16:27 EDT, nate@mt.sri.com writes: >> >>> > I am currently tracking 2.2-STABLE and use the following patch to newvers.sh >>> > to have my kernel indicate what CTM patch was used to create it. >>> >>> We need a solution that isn't specific to the transport medium, or in >>> more specific terms a solution that works irregardless of how you got >>> the bits. >>> >>I agree. >> >>One method I would like to see is that the .ctm_status file becomes a >>permanant part of the src tree. (Why?) Because CTM deltas are created at >>least once every day. > >Yes and that is exactly the problem with this solution. If I sup the CVS >tree then some rcs deltas may (and will) be added to the tree that are not >yet noticed by CTM. In other words, during one day a sup would give me >different versions of the source tree, all with the same CTM delta version. >And since people are building 'releases' from the CVS tree (instead of >ftp'ing them) this is not good. > Actually, according to the handbook on CTM http://www.freebsd.org/handbook/handbook239.html#ctm ) "You will need to transfer up to four deltas per day". This suggest that CTM deltas are created every 6 Hours. And Thus if you sup at 4 different times during the day, you will get at least 4 different versions. Now, if you sup between the 6 hour delta creations, then you will get different versions with the same CTM value. How fine, do you want it? Scot. From owner-freebsd-stable Sun Oct 5 08:43:28 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id IAA26058 for stable-outgoing; Sun, 5 Oct 1997 08:43:28 -0700 (PDT) Received: from shrimp.dataplex.net (shrimp.dataplex.net [208.2.87.3]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id IAA26049 for ; Sun, 5 Oct 1997 08:43:22 -0700 (PDT) Received: from [208.2.87.4] (user4.dataplex.net [208.2.87.4]) by shrimp.dataplex.net (8.8.5/8.8.5) with ESMTP id KAA07590; Sun, 5 Oct 1997 10:43:08 -0500 (CDT) X-Sender: rkw@mail.dataplex.net Message-Id: In-Reply-To: <971005091458_-826790286@emout05.mail.aol.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Sun, 5 Oct 1997 10:42:51 -0500 To: Hetzels@aol.com From: Richard Wackerbarth Subject: Re: Fwd: CVSup release identity Cc: stable@freebsd.org Sender: owner-freebsd-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk At 8:14 AM -0500 10/5/97, Hetzels@aol.com wrote: >We are having a discussion in STABLE about how best to track each persons >position in CVS, & CTM. Basically, We would like to be able to do a > >uname -r > >which will result in the message: > >FreeBSD 2.2-STABLE-AB > >or > >FreeBSD 2.2-STABLE (0360) I think that this is a very good idea. I would delete the "-STABLE" portion of the label. "FreeBSD 2.2 (0360)" conveys the same info, is shorter and eliminates some of the confusion. For the RELEASES, I would use "FreeBSD 2.2.0", "FreeBSD 2.2.5", etc. >I suggested using the .ctm_status file as a permant part of the source tree, >because it does produce a # every so often during the day. Being partial to ctm, I like this also. However, that would require that the various distribution schemes take their "feed" from the ctm stream. Sascha is already running a cvsup server in this mode and the others could do likewise. Alternatively, a distribution ID could be attached at an earlier "choke point" in the distribution stream. I believe that, except for those who have commit privledges to the master cvs tree, the rest of us get a feed that is derived from a periodic snapshot of the master tree. I think that the ID should be inserted at that point. Since I suspect that this is done many times a day, the ID might need to be derived from the time of the transfer. >Could you please advise on how often the CTM deltas are created? The master ctm generator runs every 8 hours. On each cycle, it generates an update for the cvs tree and a source distribution. The present schedule alternates between "current" and "2.2". As a result, each of those get checked every 16 hours. (1.5 times per day). The "2.1" distribution gets one slot on Sunday. However, you must remember that a delta is not generated unless there is a change. As a result, there are occasions where no delta is generated and the sequence number is deferred to a later run. Times per week -- Distribution 21 cvs 10 2.2, current, ports 1 2.1 >>Is there a cron job that checks the sources for changes since the last CTM >> update, and if there is a change, create a new .ctm_status file, and roll >> a CTM delta. Yes. >> How often does such a job check the source tree? (Every couple of Hours?) See above. Richard Wackerbarth From owner-freebsd-stable Sun Oct 5 09:14:10 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id JAA27395 for stable-outgoing; Sun, 5 Oct 1997 09:14:10 -0700 (PDT) Received: from shrimp.dataplex.net (shrimp.dataplex.net [208.2.87.3]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id JAA27390 for ; Sun, 5 Oct 1997 09:14:05 -0700 (PDT) Received: from [208.2.87.4] (user4.dataplex.net [208.2.87.4]) by shrimp.dataplex.net (8.8.5/8.8.5) with ESMTP id LAA08841; Sun, 5 Oct 1997 11:13:54 -0500 (CDT) X-Sender: rkw@mail.dataplex.net Message-Id: In-Reply-To: <01bcd1a1$f152b340$4a53ab98@hetzels> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Sun, 5 Oct 1997 11:14:52 -0500 To: "Scot W. Hetzel" From: Richard Wackerbarth Subject: Re: CTM patch level added to newvers.sh Cc: stable@FreeBSD.ORG, nate@mt.sri.com Sender: owner-freebsd-stable@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >>>One method I would like to see is that the .ctm_status file becomes a >>>permanant part of the src tree. (Why?) Because CTM deltas are created at >>>least once every day. >> >>Yes and that is exactly the problem with this solution. If I sup the CVS >>tree then some rcs deltas may (and will) be added to the tree that are not >>yet noticed by CTM. In other words, during one day a sup would give me >>different versions of the source tree, all with the same CTM delta version. >>And since people are building 'releases' from the CVS tree (instead of >>ftp'ing them) this is not good. >This suggest that CTM deltas are created every 6 Hours. Actually, that depends on which tree you are "sup"ping. The updates for the cvs tree are presently done every 8 hours. Source trees are on a slower interval. > And Thus if you sup >at 4 different times during the day, you will get at least 4 different >versions. Now, if you sup between the 6 hour delta creations, then you will >get different versions with the same CTM value. That all depends on what source you "sup". I believe that only those who can directly commit to the master tree are able to get a version without some latency. For the bulk of the users, they can only access a snapshot of the tree that is taken at some interval. >How fine, do you want it? Personally, I think that the granularity of ctm deltas is adequate to excessive for this purpose. Those of you who can commit are quite capable of cobbling pieces together and understand which pieces you got when and where. For the "unwashed masses", being able to identify the particular snapshot in an easy and understandable manner is important. However, their granularity is more likely to be weeks rather than minutes. See my other reply for additional comment. Richard Wackerbarth From owner-freebsd-stable Sun Oct 5 11:00:21 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id LAA02145 for stable-outgoing; Sun, 5 Oct 1997 11:00:21 -0700 (PDT) Received: from set.spradley.dyn.ml.org (fcn104-99.tmi.net [207.170.104.99]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id LAA02140 for ; Sun, 5 Oct 1997 11:00:17 -0700 (PDT) Received: from set.spradley.dyn.ml.org (tsprad@localhost.sands.com [127.0.0.1]) by set.spradley.dyn.ml.org (8.8.5/8.8.5) with ESMTP id NAA02733; Sun, 5 Oct 1997 13:22:25 -0500 (CDT) Message-Id: <199710051822.NAA02733@set.spradley.dyn.ml.org> X-Mailer: exmh version 2.0zeta 7/24/97 To: Richard Wackerbarth cc: Hetzels@aol.com, stable@FreeBSD.ORG Subject: Re: Fwd: CVSup release identity In-reply-to: Your message of "Sun, 05 Oct 1997 10:42:51 CDT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 05 Oct 1997 13:22:24 -0500 From: Ted Spradley Sender: owner-freebsd-stable@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > >uname -r > > > >which will result in the message: > > > >FreeBSD 2.2-STABLE-AB > > > >or > > > >FreeBSD 2.2-STABLE (0360) > > I think that this is a very good idea. I would delete the "-STABLE" > portion of the label. "FreeBSD 2.2 (0360)" conveys the same info, is shorter > and eliminates some of the confusion. For the RELEASES, I would use > "FreeBSD 2.2.0", "FreeBSD 2.2.5", etc. I like this. If it's got three digits (e.g. 2.2.5), it's a release. If it's got two digits plus the extra part, it's taken from an on-going branch, and the extra part indicates when it was taken. That should help clear up any confusion between branches and releases. From owner-freebsd-stable Sun Oct 5 12:54:29 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id MAA06266 for stable-outgoing; Sun, 5 Oct 1997 12:54:29 -0700 (PDT) Received: from mail-gw.pacbell.net (mail-gw.pacbell.net [206.13.28.25]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id MAA06261 for ; Sun, 5 Oct 1997 12:54:27 -0700 (PDT) From: oski@pacbell.net Received: from pacbell.net (ppp-207-215-85-195.scrm01.pacbell.net [207.215.85.195]) by mail-gw.pacbell.net (8.8.7/8.7.1+antispam) with ESMTP id MAA29866 for ; Sun, 5 Oct 1997 12:54:26 -0700 (PDT) Message-ID: <3437F00A.AEB324C2@pacbell.net> Date: Sun, 05 Oct 1997 12:52:43 -0700 X-Mailer: Mozilla 4.03 [en] (Win95; I) MIME-Version: 1.0 To: stable@freebsd.org Subject: Re: Fwd: CVSup release identity References: <199710051822.NAA02733@set.spradley.dyn.ml.org> Content-Type: multipart/alternative; boundary="------------9091C42655BCB582E261C518" Sender: owner-freebsd-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk --------------9091C42655BCB582E261C518 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Hello all... I've been tracking - silently - this dialog and must first say "This is exactly why I like FreeBSD so much!" Where else can one monitor and contribute to to the most granular detail of development? My $0.1997 (damn inflation!) is that the suggestion below sounds great. I've been slowly turning co-workers away from NT, OS/2, and other beasts for some time. I always seem to have trouble explaining the -STABLE branch. They typically order the CDROM from W.C. and install the latest "release". Then come to me with questions about how I'm doing things on my own systems. It can be difficult to explain why I can run a specific port and they can't, even though they just bought the CDROM last week. Keep up excellent work - I'll keep trying to convert the misguided... Michael Ted Spradley wrote: > > >uname -r > > > > > >which will result in the message: > > > > > >FreeBSD 2.2-STABLE-AB > > > > > >or > > > > > >FreeBSD 2.2-STABLE (0360) > > > > I think that this is a very good idea. I would delete the "-STABLE" > > portion of the label. "FreeBSD 2.2 (0360)" conveys the same info, is shorter > > and eliminates some of the confusion. For the RELEASES, I would use > > "FreeBSD 2.2.0", "FreeBSD 2.2.5", etc. > > I like this. If it's got three digits (e.g. 2.2.5), it's a release. If it's > got two digits plus the extra part, it's taken from an on-going branch, and > the extra part indicates when it was taken. That should help clear up any > confusion between branches and releases. --------------9091C42655BCB582E261C518 Content-Type: text/html; charset=us-ascii Content-Transfer-Encoding: 7bit Hello all...

I've been tracking - silently - this dialog and must first say "This is exactly why I like FreeBSD so much!" Where else can one monitor and contribute to to the most granular detail of development?

My $0.1997 (damn inflation!) is that the suggestion below sounds great. I've been slowly turning co-workers away from NT, OS/2, and other beasts for some time. I always seem to have trouble explaining the -STABLE branch. They typically order the CDROM from W.C. and install the latest "release". Then come to me with questions about how I'm doing things on my own systems. It can be difficult to explain why I can run a specific port and they can't, even though they just bought the CDROM last week.

Keep up excellent work - I'll keep trying to convert the misguided...

Michael

Ted Spradley wrote:

> >uname -r
> >
> >which will result in the message:
> >
> >FreeBSD 2.2-STABLE-AB
> >
> >or
> >
> >FreeBSD 2.2-STABLE (0360)
>
> I think that this is a very good idea. I would delete the "-STABLE"
> portion of the label. "FreeBSD 2.2 (0360)" conveys the same info, is shorter
> and eliminates some of the confusion. For the RELEASES, I would use
> "FreeBSD 2.2.0", "FreeBSD 2.2.5", etc.

I like this.  If it's got three digits (e.g. 2.2.5), it's a release.  If it's
got two digits plus the extra part, it's taken from an on-going branch, and
the extra part indicates when it was taken.  That should help clear up any
confusion between branches and releases.

  --------------9091C42655BCB582E261C518-- From owner-freebsd-stable Sun Oct 5 17:21:30 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id RAA19359 for stable-outgoing; Sun, 5 Oct 1997 17:21:30 -0700 (PDT) (envelope-from owner-freebsd-stable) Received: from merit.edu (merit.edu [198.108.1.42]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id RAA19350 for ; Sun, 5 Oct 1997 17:21:26 -0700 (PDT) (envelope-from matt@zigg.com) Received: from megaweapon.zigg.com (tcgr-200.dialup.alliance.net [207.74.43.200]) by merit.edu (8.8.7/8.8.5) with ESMTP id UAA23912 for ; Sun, 5 Oct 1997 20:21:23 -0400 (EDT) Received: from localhost (matt@localhost) by megaweapon.zigg.com (8.8.7/8.8.7) with SMTP id UAA07617 for ; Sun, 5 Oct 1997 20:21:59 -0400 (EDT) Date: Sun, 5 Oct 1997 20:21:59 -0400 (EDT) From: Matt Behrens To: stable@freebsd.org Subject: netstat not working on 2.2-STABLE (make world and kernel compiles both done in past week) Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I get the following: matt@megaweapon:/usr/home/matt>netstat netstat: kvm_read: Bad address ??? Active UNIX domain sockets Address Type Recv-Q Send-Q Inode Conn Refs Nextref Addr f0741400 dgram 0 0 0 f0487f14 0 f0487d14 f071eb00 dgram 0 0 0 f0487f14 0 f0487914 f070d400 dgram 0 0 0 f0487f14 0 f0487c14 f070da00 stream 0 0 f070b600 0 0 0 /var/run/printer f070df00 dgram 0 0 0 f0487f14 0 f0487d94 f0707000 dgram 0 0 0 f0487f14 0 f0487c94 f075f200 dgram 0 0 0 f0487f14 0 f0487014 f06cbe00 dgram 0 0 0 f0487f14 0 f0487e94 f06bf100 dgram 0 0 0 f0487f14 0 0 f06bc400 dgram 0 0 f06be880 0 f048fc14 0 /var/run/log Ideas? Matt Behrens | matt@zigg.com MST3K #85995 | http://www.zigg.com/ From owner-freebsd-stable Sun Oct 5 20:22:50 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id UAA28341 for stable-outgoing; Sun, 5 Oct 1997 20:22:50 -0700 (PDT) (envelope-from owner-freebsd-stable) Received: from cgi.sstar.com (cgi.sstar.com [204.27.72.160]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id UAA28334 for ; Sun, 5 Oct 1997 20:22:46 -0700 (PDT) (envelope-from jim.king@mail.sstar.com) Received: from jim-home (p15.sstar.com [204.27.72.47]) by cgi.sstar.com (8.8.7/8.7.3) with SMTP id WAA26058 for ; Sun, 5 Oct 1997 22:22:43 -0500 (CDT) Message-Id: <3.0.2.32.19971005222201.006d3010@mail.sstar.com> X-Sender: jim.king@mail.sstar.com X-Mailer: QUALCOMM Windows Eudora Light Version 3.0.2 (32) Date: Sun, 05 Oct 1997 22:22:01 -0500 To: freebsd-stable@freebsd.org From: Jim King Subject: DE21140-AE in 2.2.5 In-Reply-To: <199710060203.UAA08211@obie.softweyr.ml.org> References: <3.0.2.32.19971005092418.006c18fc@mail.sstar.com> <3.0.1.32.19971002102621.009a3790@mail.sstar.com> <199710050313.VAA07177@obie.softweyr.ml.org> <3.0.2.32.19971005092418.006c18fc@mail.sstar.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk At 08:03 PM 10/5/97 -0600, you wrote: >Jim King writes: > > At 09:13 PM 10/4/97 -0600, Wes Peters wrote: > > >Jim King writes: > > > > The boot disk from 2.2-971002-BETA doesn't like my Netgear Fast > > Ethernet card: > > > > > > > > de0 rev 34 int a irq 9 on pci0:17 > > > > de0: 21140A [10-100Mb/s] pass 2.2 > > > > de0: address 00:40:05:37:e8:f7 > > > > de0: enabling 100baseTX port > > > > > > > > As soon as this message appears the link light on the hub goes out. > > > > Network stuff doesn't work in the install program. As soon as I exit the > > > > install program the link light on the hub comes on. > > > > > > > > Is there an ifconfig option to make this card work? > > > > > >You don't mention if the hub is 10Base-T or 100Base-TX. Fast or not? > > > > Fast, although I seem to get the same results with a 10BaseT hub (the > > 10BaseT hub is another room, so I can't watch the link lights on it). > >Maybe the auto-sense on the card is failing, and is selecting a mode the >hub won't support. I'm stumped at this point without having some >hardware to test on. The fact that it fails with a 10Base hub is bad >news, Bay may be using a PHY (physical layer interface) chip not >supported by the driver. At this point I'd say it's a problem with the 2.2 driver. I'm still getting the same failure with the boot floppy from 2.2.5-971005-BETA, but this hardware works with the boot floppy from 3.0-971005-SNAP, as well as with Windows NT (using Netgear's driver). >Have you filed a bug report with send-pr? No. >And, more importantly, can you get your money back on this card? Since the card appears to work with NT and with FreeBSD 3.0, I'd rather bring it to the attention of someone who can get it working in FreeBSD 2.2.5. I'm willing to do whatever I can - apply patches, ship out a loaner card, etc. From owner-freebsd-stable Sun Oct 5 22:03:25 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id WAA03477 for stable-outgoing; Sun, 5 Oct 1997 22:03:25 -0700 (PDT) (envelope-from owner-freebsd-stable) Received: from andrsn.stanford.edu (andrsn.Stanford.EDU [36.33.0.163]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id WAA03469 for ; Sun, 5 Oct 1997 22:03:21 -0700 (PDT) (envelope-from andrsn@andrsn.stanford.edu) Received: from localhost (localhost.stanford.edu [127.0.0.1]) by andrsn.stanford.edu (8.8.7/8.6.12) with SMTP id VAA02077; Sun, 5 Oct 1997 21:59:09 -0700 (PDT) Date: Sun, 5 Oct 1997 21:59:08 -0700 (PDT) From: Annelise Anderson To: Ted Spradley cc: Richard Wackerbarth , Hetzels@aol.com, stable@FreeBSD.ORG Subject: Re: Fwd: CVSup release identity In-Reply-To: <199710051822.NAA02733@set.spradley.dyn.ml.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Sun, 5 Oct 1997, Ted Spradley wrote: > > > >uname -r > > > > > >which will result in the message: > > > > > >FreeBSD 2.2-STABLE-AB > > > > > >or > > > > > >FreeBSD 2.2-STABLE (0360) > > > > I think that this is a very good idea. I would delete the "-STABLE" > > portion of the label. "FreeBSD 2.2 (0360)" conveys the same info, is shorter > > and eliminates some of the confusion. For the RELEASES, I would use > > "FreeBSD 2.2.0", "FreeBSD 2.2.5", etc. > > I like this. If it's got three digits (e.g. 2.2.5), it's a release. If it's > got two digits plus the extra part, it's taken from an on-going branch, and > the extra part indicates when it was taken. That should help clear up any > confusion between branches and releases. But releases are also taken from ongoing branches. In any case, uname -r on my machine now produces: 2.2-STABLE-971004-19:45 PDT which is explicit in indicating the date and time at which cvsup began downloading the sources. That seems more informative than a code that has to be translated into a date. Annelise From owner-freebsd-stable Sun Oct 5 23:57:29 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id XAA08966 for stable-outgoing; Sun, 5 Oct 1997 23:57:29 -0700 (PDT) (envelope-from owner-freebsd-stable) Received: from time.cdrom.com (time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id XAA08961; Sun, 5 Oct 1997 23:57:27 -0700 (PDT) (envelope-from jkh@time.cdrom.com) Received: from time.cdrom.com (localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.7/8.6.9) with ESMTP id XAA01952; Sun, 5 Oct 1997 23:56:51 -0700 (PDT) To: current@freebsd.org cc: stable@freebsd.org Subject: Attention all users of the de driver! Date: Sun, 05 Oct 1997 23:56:51 -0700 Message-ID: <1948.876121011@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk If you have a de0 device in your machine and you're running -current, NOW is the time to let us know if there are any problems with it! We know for a fact that 2.2-stable's driver does not work on at least one card, the Znyx 4-port NIC, but we also don't know if 3.0-current is going to break a lot more people if we bring it in. Therefore, if you do NOT wish to see the de driver in 2.2-stable updated using the 3.0-current bits, now is the time to speak up since we will otherwise take your silence as "it works great, bring it on over!" Jordan From owner-freebsd-stable Mon Oct 6 00:50:45 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id AAA11571 for stable-outgoing; Mon, 6 Oct 1997 00:50:45 -0700 (PDT) (envelope-from owner-freebsd-stable) Received: from scotty.masternet.it (scotty.masternet.it [194.184.65.2]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id AAA11566; Mon, 6 Oct 1997 00:50:29 -0700 (PDT) (envelope-from gmarco@scotty.masternet.it) Received: from gmarco (ts2port3d.masternet.it [194.184.65.217]) by scotty.masternet.it (8.8.7/8.8.5) with SMTP id JAA03430; Mon, 6 Oct 1997 09:48:57 GMT Message-Id: <3.0.3.32.19971006095219.032e3858@scotty.masternet.it> X-Sender: gmarco@scotty.masternet.it X-Mailer: QUALCOMM Windows Eudora Pro Version 3.0.3 (32) Date: Mon, 06 Oct 1997 09:52:19 +0200 To: "Jordan K. Hubbard" , current@FreeBSD.ORG From: Gianmarco Giovannelli Subject: Re: Attention all users of the de driver! Cc: stable@FreeBSD.ORG In-Reply-To: <1948.876121011@time.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-stable@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk At 11:56 PM 10/5/97 -0700, Jordan K. Hubbard wrote: >If you have a de0 device in your machine and you're running -current, >NOW is the time to let us know if there are any problems with it! I am using de0 on about 5 box, 3 of them 2.2.2-STABLE (cvsupped nearly daily) of my ISP :-) The other two are in my house and are running 3.0-CURRENT (also cvsupped everyday...) I am not having any troubles at all.... all errors I got from this boxes was on hardware or my fault. They are very different configuration from : IDE HD (1), A2940 (1) and 2940uw (3); Pentium MMX 233 (2) , Pentium PRO 200 (1), Cyryx 166+ (1), AMD K6 (1) ... and so on... So in my humble opinion of newbie and user there aren't problem at all... If you need some further tests please let me know.... I hope it helps... Regards... Gianmarco "Unix expert since yesterday" Home page: http://www2.masternet.it/~gmarco Server page: http://www2.masternet.it/ From owner-freebsd-stable Mon Oct 6 01:17:50 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id BAA12946 for stable-outgoing; Mon, 6 Oct 1997 01:17:50 -0700 (PDT) (envelope-from owner-freebsd-stable) Received: from schizo.dk.tfs.com (mail.trw.dk [195.8.133.123]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id BAA12925; Mon, 6 Oct 1997 01:17:30 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (critter.dk.tfs.com [140.145.230.252]) by schizo.dk.tfs.com (8.8.7/8.7.3) with ESMTP id KAA28908; Mon, 6 Oct 1997 10:16:58 +0200 (MET DST) Received: from critter.freebsd.dk (localhost.dk.tfs.com [127.0.0.1]) by critter.freebsd.dk (8.8.7/8.8.7) with ESMTP id KAA02280; Mon, 6 Oct 1997 10:16:48 +0200 (CEST) To: "Jordan K. Hubbard" cc: current@freebsd.org, stable@freebsd.org Subject: Re: Attention all users of the de driver! In-reply-to: Your message of "Sun, 05 Oct 1997 23:56:51 PDT." <1948.876121011@time.cdrom.com> Date: Mon, 06 Oct 1997 10:16:48 +0200 Message-ID: <2278.876125808@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk In message <1948.876121011@time.cdrom.com>, "Jordan K. Hubbard" writes: >If you have a de0 device in your machine and you're running -current, >NOW is the time to let us know if there are any problems with it! > >We know for a fact that 2.2-stable's driver does not work on at least >one card, the Znyx 4-port NIC, but we also don't know if 3.0-current Uhm, that is news to me. The check for the MAC address may be too strict I changed that in -current, but I can't remember when. I will test this tonight. -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." From owner-freebsd-stable Mon Oct 6 01:31:02 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id BAA13858 for stable-outgoing; Mon, 6 Oct 1997 01:31:02 -0700 (PDT) (envelope-from owner-freebsd-stable) Received: from verdi.nethelp.no (verdi.nethelp.no [195.1.171.130]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id BAA13808 for ; Mon, 6 Oct 1997 01:30:42 -0700 (PDT) (envelope-from sthaug@nethelp.no) From: sthaug@nethelp.no Received: (qmail 5019 invoked by uid 1001); 6 Oct 1997 08:30:36 +0000 (GMT) To: jkh@time.cdrom.com Cc: current@FreeBSD.ORG, stable@FreeBSD.ORG Subject: Re: Attention all users of the de driver! In-Reply-To: Your message of "Sun, 05 Oct 1997 23:56:51 -0700" References: <1948.876121011@time.cdrom.com> X-Mailer: Mew version 1.05+ on Emacs 19.28.2 Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Date: Mon, 06 Oct 1997 10:30:36 +0200 Message-ID: <5017.876126636@verdi.nethelp.no> Sender: owner-freebsd-stable@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > We know for a fact that 2.2-stable's driver does not work on at least > one card, the Znyx 4-port NIC, but we also don't know if 3.0-current > is going to break a lot more people if we bring it in. The 2.2-stable de driver (1.54.2.6) works fine for us. 2.2-970901-RELENG, ZNYX ZX314 4x10 Mbps, SMC 8434T 2x10 Mbps, SMC9332BDT 2x100 Mbps: Probing for devices on PCI bus 1: de0 rev 35 int a irq 10 on pci1:4 de0: ZNYX ZX314 21040 [10Mb/s] pass 2.3 de0: address 00:c0:95:f0:1d:20 de0: enabling 10baseT port de1 rev 35 int a irq 10 on pci1:5 de1: (null)21040 [10Mb/s] pass 2.3 de1: address 00:c0:95:f0:1d:21 de1: enabling 10baseT port de2 rev 35 int a irq 11 on pci1:6 de2: (null)21040 [10Mb/s] pass 2.3 de2: address 00:c0:95:f0:1d:22 de2: enabling 10baseT port de3 rev 35 int a irq 11 on pci1:7 de3: (null)21040 [10Mb/s] pass 2.3 de3: address 00:c0:95:f0:1d:23 de3: enabling 10baseT port Probing for devices on PCI bus 2: de4 rev 35 int a irq 11 on pci2:4 de4: SMC 8434T-CH1 21040 [10Mb/s] pass 2.3 de4: address 00:00:c0:2b:0e:c0 de4: enabling 10baseT port de5 rev 35 int a irq 10 on pci2:5 de5: SMC 8434T-CH2 21040 [10Mb/s] pass 2.3 de5: address 00:00:c0:4e:10:c0 de5: enabling 10baseT port Probing for devices on PCI bus 3: de6 rev 32 int a irq 11 on pci3:4 de6: SMC 9332BDT 21140A [10-100Mb/s] pass 2.0 de6: address 00:00:c0:cd:8d:ef de7 rev 32 int a irq 11 on pci3:5 de7: SMC 9332BDT 21140A [10-100Mb/s] pass 2.0 de7: address 00:00:c0:cc:8d:ef The *heavy* traffic on this machine is through de6, but there's also quite a bit of traffic through de2 (ZNYX) , and we've seen no problems. Steinar Haug, Nethelp consulting, sthaug@nethelp.no From owner-freebsd-stable Mon Oct 6 03:44:59 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id DAA19877 for stable-outgoing; Mon, 6 Oct 1997 03:44:59 -0700 (PDT) (envelope-from owner-freebsd-stable) Received: from shrimp.dataplex.net (shrimp.dataplex.net [208.2.87.3]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id DAA19866 for ; Mon, 6 Oct 1997 03:44:54 -0700 (PDT) (envelope-from rkw@dataplex.net) Received: from [208.2.87.4] (user4.dataplex.net [208.2.87.4]) by shrimp.dataplex.net (8.8.5/8.8.5) with ESMTP id FAA28454; Mon, 6 Oct 1997 05:44:48 -0500 (CDT) X-Sender: rkw@mail.dataplex.net Message-Id: In-Reply-To: References: <199710051822.NAA02733@set.spradley.dyn.ml.org> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Mon, 6 Oct 1997 05:38:51 -0500 To: Annelise Anderson From: Richard Wackerbarth Subject: Re: Fwd: CVSup release identity Cc: stable@FreeBSD.ORG Sender: owner-freebsd-stable@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >But releases are also taken from ongoing branches. In any case, uname -r >on my machine now produces: > >2.2-STABLE-971004-19:45 PDT > >which is explicit in indicating the date and time at which cvsup began >downloading the sources. That seems more informative than a code that >has to be translated into a date. Well, I would still get rid of the "-STABLE". I would also use Zulu time and convert it all to a number. Thus "FreeBSD 2.2 (9710050245)" However, the date/time stamp should be made when the source is extracted from the master source and not when YOU get a second or third generation copy from some distribution point. On the subject of releases being taken from ongoing branches, I think that releases deserve special consideration and a simpler form of identification. Remember that an individual who rebuilds a system from source is slightly more knowledgable. For someone who simply installs a release, we need to KISS. If the wrapper on the CD says "2.2.5", that is what they would expect uname to deliver. Richard Wackerbarth From owner-freebsd-stable Mon Oct 6 04:30:35 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id EAA21717 for stable-outgoing; Mon, 6 Oct 1997 04:30:35 -0700 (PDT) (envelope-from owner-freebsd-stable) Received: from bob.tri-lakes.net ([207.3.81.6]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id EAA21712 for ; Mon, 6 Oct 1997 04:30:33 -0700 (PDT) (envelope-from cdillon@tri-lakes.net) Received: from [207.3.81.139] by bob.tri-lakes.net (NTMail 3.02.13) with ESMTP id qa291398 for ; Mon, 6 Oct 1997 06:30:44 -0500 Message-ID: X-Mailer: XFMail 1.1 [p0] on FreeBSD Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: Date: Mon, 06 Oct 1997 06:23:46 -0000 (GMT) From: Chris Dillon To: stable@FreeBSD.ORG Subject: Re: Fwd: CVSup release identity Sender: owner-freebsd-stable@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On 06-Oct-97 Annelise Anderson wrote: > > >On Sun, 5 Oct 1997, Ted Spradley wrote: > >> >> > >uname -r >> > > >> > >which will result in the message: >> > > >> > >FreeBSD 2.2-STABLE-AB >> > > >> > >or >> > > >> > >FreeBSD 2.2-STABLE (0360) >> > >> > I think that this is a very good idea. I would delete the "-STABLE" >> > portion of the label. "FreeBSD 2.2 (0360)" conveys the same info, is >shorter >> > and eliminates some of the confusion. For the RELEASES, I would use >> > "FreeBSD 2.2.0", "FreeBSD 2.2.5", etc. >> >> I like this. If it's got three digits (e.g. 2.2.5), it's a release. >If it's >> got two digits plus the extra part, it's taken from an on-going branch, >and >> the extra part indicates when it was taken. That should help clear up >any >> confusion between branches and releases. > >But releases are also taken from ongoing branches. In any case, uname -r >on my machine now produces: > >2.2-STABLE-971004-19:45 PDT > >which is explicit in indicating the date and time at which cvsup began >downloading the sources. That seems more informative than a code that >has to be translated into a date. > > Annelise I have been following this debate since it started, and my own idea at the beginning of it was very similar to the above. A time stamp is about as fine-grained as you can get, and is not dependant on how either CTM or cvsup work. After all, this has been how we have been describing just how far along we are on the stable tree for a long time now. "And you cvsupped when? 19:45 10/4/97? Oh, thats just before I made those changes." --- Chris Dillon --- cdillon@tri-lakes.net --- Powered by FreeBSD, the best free OS on the planet ---- (http://www.freebsd.org) From owner-freebsd-stable Mon Oct 6 04:33:04 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id EAA21853 for stable-outgoing; Mon, 6 Oct 1997 04:33:04 -0700 (PDT) (envelope-from owner-freebsd-stable) Received: from gate.mgt.msk.ru (mgtrep.24h.dialup.ru [194.87.18.139]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id EAA21845; Mon, 6 Oct 1997 04:32:59 -0700 (PDT) (envelope-from tarkhil@mgt.msk.ru) Received: from asteroid.mgt.msk.ru (asteroid.mgt.msk.ru [192.168.133.145]) by gate.mgt.msk.ru (8.8.6/8.8.6) with ESMTP id PAA01137; Mon, 6 Oct 1997 15:32:02 +0400 (MSD) Received: from asteroid.mgt.msk.ru (localhost.mgt.msk.ru [127.0.0.1]) by asteroid.mgt.msk.ru (8.8.7/8.8.6) with ESMTP id PAA19069; Mon, 6 Oct 1997 15:32:22 +0400 (MSD) Message-Id: <199710061132.PAA19069@asteroid.mgt.msk.ru> To: stable@freebsd.org cc: hackers@freebsd.org Reply-To: tarkhil@mgt.msk.ru Subject: bug in syslogd! Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 06 Oct 1997 15:32:20 +0400 From: "Alexander B. Povolotsky" Sender: owner-freebsd-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hello! Trying to set up syslogd to make time marks, I've found bug in /usr/include/ syslog.h: in facilitynames, _ALL_ facility codes are shifted 3 bits left. EXCEPT INTERNAL_MARK, so it is impossible to set mark.info from syslog.conf. I don't know if I should change definition of INTERNAL_MARK, or the corresponding line in facilityname. Hope someone more familiar with FBSD internals can fix it properly. Alex. From owner-freebsd-stable Mon Oct 6 05:53:54 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id FAA25921 for stable-outgoing; Mon, 6 Oct 1997 05:53:54 -0700 (PDT) (envelope-from owner-freebsd-stable) Received: from shrimp.dataplex.net (shrimp.dataplex.net [208.2.87.3]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id FAA25911 for ; Mon, 6 Oct 1997 05:53:50 -0700 (PDT) (envelope-from rkw@dataplex.net) Received: from [208.2.87.4] (user4.dataplex.net [208.2.87.4]) by shrimp.dataplex.net (8.8.5/8.8.5) with ESMTP id HAA29628; Mon, 6 Oct 1997 07:53:46 -0500 (CDT) X-Sender: rkw@mail.dataplex.net Message-Id: In-Reply-To: References: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Mon, 6 Oct 1997 07:54:54 -0500 To: Chris Dillon From: Richard Wackerbarth Subject: Re: Fwd: CVSup release identity Cc: stable@FreeBSD.ORG Sender: owner-freebsd-stable@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >I have been following this debate since it started, and my own idea at the >beginning of it was very similar to the above. A time stamp is about as >fine-grained as you can get, and is not dependant on how either CTM or >cvsup work. After all, this has been how we have been describing just how >far along we are on the stable tree for a long time now. "And you cvsupped >when? 19:45 10/4/97? Oh, thats just before I made those >changes." I have no objection to using timestamps to identify "progress" along a branch. However, you need to realize that the stamp must be applied at the time that the snapshot is taken from the master tree. We used to look at the timestamp placed on the kernel at compile time. However, I don't care when you compile the source. (Although I can conclude that you are missing later changes.) What I want to know is WHICH version of the master source you are using. I also do not care when YOU got the source from someone else. Since you do not have direct access to the master source by either ctm or cvsup, we need to stamp the sources at the time that they are extracted from the master source by the primary distributor. Anything less increases the uncertainty interval. The more latency in the distribution mechanism, the higher the uncertainty. The only objection that I have to the use of timestamps as the identifier is that they may not be "user friendly". A user who gets a release CD knows that he has release "5.1.9". He doesn't realize that it was generated on October 31 at 4:26:37 PM PDT. Similarly, users of CTM distributions know that they have updated through delta 4726. Richard Wackerbarth From owner-freebsd-stable Mon Oct 6 06:30:44 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id GAA27779 for stable-outgoing; Mon, 6 Oct 1997 06:30:44 -0700 (PDT) (envelope-from owner-freebsd-stable) Received: from mail.wintek.com (mail.wintek.com [199.233.104.76]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id GAA27756; Mon, 6 Oct 1997 06:30:37 -0700 (PDT) (envelope-from csg@wintek.com) Received: from mail.wintek.com (csg@localhost) by mail.wintek.com (8.8.7/1.34wintek(3.6davy)) id NAA12904; Mon, 6 Oct 1997 13:30:30 GMT Message-Id: <199710061330.NAA12904@mail.wintek.com> From: "C. Stephen Gunn" Subject: Re: Attention all users of the de driver! In-Reply-To: <1948.876121011@time.cdrom.com> from "Jordan K. Hubbard" at "Oct 5, 97 11:56:51 pm" To: jkh@time.cdrom.com (Jordan K. Hubbard) Date: Mon, 6 Oct 1997 08:30:30 -0500 (EST) Cc: stable@freebsd.org, current@freebsd.org X-Mailer: ELM [version 2.4ME+ PL31 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > If you have a de0 device in your machine and you're running -current, > NOW is the time to let us know if there are any problems with it! We have been using the patched version from 3am-software.com on a couple of our FreeBSD Machines here. When I tried to start atalkd (part of the netatalk package) the machine lost its mind on the ethernet after 2-3 minutes. Doing a "ifconfig down de0" on the interface seemed to work. I'm not positive this is a de driver problem. We are using the patched version to get the NetGear 10/100 cards to work. It could be something with the default "atalk.conf" that the package installs, since it runs fine on a machine with a SMC card 10/100 de0 card. I will try to track the problem down further, I just haven't had time. Just wanted to make sure to speak up with the 2.2.5-BETA and all in progress. Both machines are running 2.2-STABLE that was cvsup'd and "buildworld"'d in the last week or so. Neither are production servers, so they are available for testing if necessary. - Steve -- C. Stephen Gunn Wintek Corporation E-mail: csg@wintek.com 427 N 6th Street Tel: +1 (765) 742-8428 Lafayette, IN 47901-1126 Fax: +1 (765) 742-0547 United States of America From owner-freebsd-stable Mon Oct 6 07:36:24 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id HAA01817 for stable-outgoing; Mon, 6 Oct 1997 07:36:24 -0700 (PDT) (envelope-from owner-freebsd-stable) Received: from GndRsh.aac.dev.com (GndRsh.aac.dev.com [198.145.92.241]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id HAA01812 for ; Mon, 6 Oct 1997 07:36:21 -0700 (PDT) (envelope-from rgrimes@GndRsh.aac.dev.com) Received: (from rgrimes@localhost) by GndRsh.aac.dev.com (8.8.5/8.7.3) id HAA00223; Mon, 6 Oct 1997 07:36:00 -0700 (PDT) From: "Rodney W. Grimes" Message-Id: <199710061436.HAA00223@GndRsh.aac.dev.com> Subject: Re: CVSUP vs. SNAPS In-Reply-To: <11918.875811660@time.cdrom.com> from "Jordan K. Hubbard" at "Oct 2, 97 10:01:00 am" To: jkh@time.cdrom.com (Jordan K. Hubbard) Date: Mon, 6 Oct 1997 07:36:00 -0700 (PDT) Cc: andrsn@andrsn.stanford.edu, freebsd-stable@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL25 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > Please, not again, don't duplicate the errors of your past handling > > of this. > > > > The sequence of commits should be something that creates > > > > 2.2-STABLE (where we are today) > > 2.2.5-BETA (for while we are in BETA on the branch) > > 2.2.5-RELEASE (when you finally roll the puppy up) > > 2.2.5-STABLE (after you roll the release). > > That would be totally and utterly bogus. And I suppose you'll replace my above ``2.2.5-STABLE'' with ``2.2-STABLE'', like that isn't totally bogus too! 2.2 < 2.2.5, thats going backwards, and makes it very hard to tell if this ``STABLE'' is post 2.2.1, post 2.2.2, or post 2.2.5! YOUR CONFUSING THE USERS, AND MY CLIENTS!!!! -- Rod Grimes rgrimes@gndrsh.aac.dev.com Accurate Automation, Inc. Reliable computers for FreeBSD From owner-freebsd-stable Mon Oct 6 07:43:17 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id HAA02309 for stable-outgoing; Mon, 6 Oct 1997 07:43:17 -0700 (PDT) (envelope-from owner-freebsd-stable) Received: from GndRsh.aac.dev.com (GndRsh.aac.dev.com [198.145.92.241]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id HAA02298 for ; Mon, 6 Oct 1997 07:43:09 -0700 (PDT) (envelope-from rgrimes@GndRsh.aac.dev.com) Received: (from rgrimes@localhost) by GndRsh.aac.dev.com (8.8.5/8.7.3) id HAA00246; Mon, 6 Oct 1997 07:42:50 -0700 (PDT) From: "Rodney W. Grimes" Message-Id: <199710061442.HAA00246@GndRsh.aac.dev.com> Subject: Re: CVSUP vs. SNAPS In-Reply-To: <12048.875812329@time.cdrom.com> from "Jordan K. Hubbard" at "Oct 2, 97 10:12:09 am" To: jkh@time.cdrom.com (Jordan K. Hubbard) Date: Mon, 6 Oct 1997 07:42:50 -0700 (PDT) Cc: imp@village.org, andrsn@andrsn.stanford.edu, freebsd-stable@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL25 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > But it results from an essential confusion as to what "2.2" means. > > 2.2 is the branch ID, it's not 2.2.0 as Rod seems to see it and hence > there's no "decrease" in the release number (if you had to think of it > strictly numerically then 2.2 would be equivalent to 2.2.x, where x = > infinity :). > > To put it another way, we have 3 branches right now: > > 2.1 AKA 2.1-stable > 2.2 AKA 2.2-stable > 3.0 AKA 3.0-current > > And I would expect all branches to have their BRANCH variable in > /sys/conf/newvers.sh set accordingly except for those brief periods > when an actual release was going out, at which point it would briefly Ahhhh.... your confusing things a bit, REVISION in newvers.sh != BRANCH, never did, never was meant to. BRANCH in the file infact was short cited when I created it, it's value is the one used to tweak in the ``RELEASE'', ``STABLE'' and ``CURRENT'' values, oh well, perhaps it should be called ``FLAVOR''?. > transition to RELEASE. Suddenly inventing 2.2.5-stable would be a > tragic mistake since it leads in turn to the suggestion that there's a > RELENG_2_2_5 branch tag to go with it which, of course, there is not. No, newvers.sh does not reference BRANCHes, other than the above error. It was meant to keep things clear as to what one is running, REVISION, should always be set to reflect the value of the last release done on that branch in the respective branches newvers.sh, REVSION should NEVER NEVER NEVER decrease in value! Your arguing with the person that wrote the current version of newvers.sh, who had specific intents for each of those values, and what you are doing is _not_ what was suppose to be done! > Jordan > > > In message <199710021358.GAA28556@GndRsh.aac.dev.com> "Rodney W. Grimes" writ > es: > > : You did this in the 2.1 branch when I proded you to change the > > : word ``RELEASE'' to ``STABLE'', but your commit also changed > > : 2.1.5 back to 2.1, _decreasing_ the version number, again I > > : iterate, version numbers should never decrease! > > > > Let me stand up and lend my 100% whole-hearted support to Rod's > > request. I think it is an excellent idea. > > > > Warner > > -- Rod Grimes rgrimes@gndrsh.aac.dev.com Accurate Automation, Inc. Reliable computers for FreeBSD From owner-freebsd-stable Mon Oct 6 07:51:20 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id HAA02713 for stable-outgoing; Mon, 6 Oct 1997 07:51:20 -0700 (PDT) (envelope-from owner-freebsd-stable) Received: from GndRsh.aac.dev.com (GndRsh.aac.dev.com [198.145.92.241]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id HAA02708 for ; Mon, 6 Oct 1997 07:51:16 -0700 (PDT) (envelope-from rgrimes@GndRsh.aac.dev.com) Received: (from rgrimes@localhost) by GndRsh.aac.dev.com (8.8.5/8.7.3) id HAA00281; Mon, 6 Oct 1997 07:50:32 -0700 (PDT) From: "Rodney W. Grimes" Message-Id: <199710061450.HAA00281@GndRsh.aac.dev.com> Subject: Re: CVSUP vs. SNAPS In-Reply-To: <12160.875813096@time.cdrom.com> from "Jordan K. Hubbard" at "Oct 2, 97 10:24:56 am" To: jkh@time.cdrom.com (Jordan K. Hubbard) Date: Mon, 6 Oct 1997 07:50:32 -0700 (PDT) Cc: kkennawa@physics.adelaide.edu.au, dg@root.com, andrsn@andrsn.stanford.edu, freebsd-stable@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL25 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk ... > I think we're really better off just leaving it the heck alone for > now. During BETA test is *not* the time to contemplate major changes > in our release engineering strategy, for better or for worse. This > should have been brought up several months ago if Rod was actually > hoping for any sort of genuine effect here. :-) As it is, I certain Ahh... I tried to get this fixed after 2.1.7, but you did it wrong, you made MORE change than what I asked you to do. I asked you to change ``RELEASE'' to ``STABLE'' in newvers.sh, you did that PLUS you changed REVISION from 2.1.7 to 2.1, WRONG, get a grip, REVISION never goes down in value!! Index: newvers.sh =================================================================== RCS file: /home/ncvs/src/sys/conf/newvers.sh,v retrieving revision 1.16.4.11 retrieving revision 1.16.4.12 diff -u -r1.16.4.11 -r1.16.4.12 --- newvers.sh 1997/02/10 06:36:10 1.16.4.11 +++ newvers.sh 1997/04/19 01:11:18 1.16.4.12 @@ -32,11 +32,11 @@ # SUCH DAMAGE. # # @(#)newvers.sh 8.1 (Berkeley) 4/20/94 -# $Id: newvers.sh,v 1.16.4.11 1997/02/10 06:36:10 jkh Exp $ +# $Id: newvers.sh,v 1.16.4.12 1997/04/19 01:11:18 jkh Exp $ TYPE="FreeBSD" -REVISION="2.1.7" -BRANCH="RELEASE" +REVISION="2.1" +BRANCH="STABLE" RELEASE="${REVISION}-${BRANCH}" SNAPDATE="" if [ "X${SNAPDATE}" != "X" ]; then You seem to be totally and utterly convinced that REVISION == CVS branch tag, but it DON'T! > intend on doing absolutely nothing different than "usual" at this late > stage in the game. It doesn't even occur until after you do the release, when you go to change ``RELEASE'' back to ``STABLE'' DON'T TOUCH THE BLOODY REVSION NUMBER! -- Rod Grimes rgrimes@gndrsh.aac.dev.com Accurate Automation, Inc. Reliable computers for FreeBSD From owner-freebsd-stable Mon Oct 6 07:51:37 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id HAA02756 for stable-outgoing; Mon, 6 Oct 1997 07:51:37 -0700 (PDT) (envelope-from owner-freebsd-stable) Received: from implode.root.com (implode.root.com [198.145.90.17]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id HAA02730; Mon, 6 Oct 1997 07:51:29 -0700 (PDT) (envelope-from root@implode.root.com) Received: from implode.root.com (localhost [127.0.0.1]) by implode.root.com (8.8.5/8.8.5) with ESMTP id HAA27354; Mon, 6 Oct 1997 07:53:29 -0700 (PDT) Message-Id: <199710061453.HAA27354@implode.root.com> To: "C. Stephen Gunn" cc: stable@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: Attention all users of the de driver! In-reply-to: Your message of "Mon, 06 Oct 1997 08:30:30 CDT." <199710061330.NAA12904@mail.wintek.com> From: David Greenman Reply-To: dg@root.com Date: Mon, 06 Oct 1997 07:53:29 -0700 Sender: owner-freebsd-stable@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >We have been using the patched version from 3am-software.com on a couple >of our FreeBSD Machines here. When I tried to start atalkd (part of the >netatalk package) the machine lost its mind on the ethernet after 2-3 >minutes. When you say "patched version", do you mean it has the bugfixes that were made to it in -current, or do you mean some other patches? -DG David Greenman Core-team/Principal Architect, The FreeBSD Project From owner-freebsd-stable Mon Oct 6 08:06:07 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id IAA03421 for stable-outgoing; Mon, 6 Oct 1997 08:06:07 -0700 (PDT) (envelope-from owner-freebsd-stable) Received: from GndRsh.aac.dev.com (GndRsh.aac.dev.com [198.145.92.241]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id IAA03408 for ; Mon, 6 Oct 1997 08:06:00 -0700 (PDT) (envelope-from rgrimes@GndRsh.aac.dev.com) Received: (from rgrimes@localhost) by GndRsh.aac.dev.com (8.8.5/8.7.3) id IAA00297; Mon, 6 Oct 1997 08:05:27 -0700 (PDT) From: "Rodney W. Grimes" Message-Id: <199710061505.IAA00297@GndRsh.aac.dev.com> Subject: Re: CVSUP vs. SNAPS In-Reply-To: <2674.875831475@time.cdrom.com> from "Jordan K. Hubbard" at "Oct 2, 97 03:31:15 pm" To: jkh@time.cdrom.com (Jordan K. Hubbard) Date: Mon, 6 Oct 1997 08:05:27 -0700 (PDT) Cc: jfarmer@sabre.goldsword.com, kkennawa@physics.adelaide.edu.au, andrsn@andrsn.stanford.edu, dg@root.com, freebsd-stable@FreeBSD.ORG, jfarmer@goldsword.com X-Mailer: ELM [version 2.4ME+ PL25 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk ... > > I think you're confused - there would still be only one branch tag > involved here, no matter what I tweak newvers.sh to say. We're not > creating a new branch with every release along another branch here - > that would be insane. ;-) Hummm.. I called it REVISION, not BRANCH_TAG, why must you equate the two?? I only see one other person who has even supported your point of view here, WHY must you continue to do bad things to the REVISION number as the RELEASE engineer. When I held that role there was now confusion about what was running on any system I looked at or helped someone with, now that you have this role there is mass confusion, might I wonder if Jordan is doing something wrong?? Might I find out that the REVISION number is going backwards. Might I try and complain and have it fixed during the next release cycle only to have Jordan insist on continueing to make the same error just becase that is the way he has been doing it. Looks like 5 to 1 in favor of what I stated, so what, your going to pull the Release Engineer Hat out and say NO? Well, if you do everytime I have to spend 15 minutes instead of 1 minute to figure out what someone is running so I can help them I am going to send you an invoice for that time instead of billing my client for it! Nahhh.... I'll just make it my first commit after you open the RELENG_2_2 branch (another error by you, until then all RELENG tags had 3 digit components :-() to set REVISION to 2.2.5 and BRANCH to STABLE. -- Rod Grimes rgrimes@gndrsh.aac.dev.com Accurate Automation, Inc. Reliable computers for FreeBSD From owner-freebsd-stable Mon Oct 6 08:09:33 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id IAA03675 for stable-outgoing; Mon, 6 Oct 1997 08:09:33 -0700 (PDT) (envelope-from owner-freebsd-stable) Received: from GndRsh.aac.dev.com (GndRsh.aac.dev.com [198.145.92.241]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id IAA03657 for ; Mon, 6 Oct 1997 08:09:30 -0700 (PDT) (envelope-from rgrimes@GndRsh.aac.dev.com) Received: (from rgrimes@localhost) by GndRsh.aac.dev.com (8.8.5/8.7.3) id IAA00318; Mon, 6 Oct 1997 08:08:48 -0700 (PDT) From: "Rodney W. Grimes" Message-Id: <199710061508.IAA00318@GndRsh.aac.dev.com> Subject: Re: CVSUP vs. SNAPS In-Reply-To: <199710022335.RAA06331@harmony.village.org> from Warner Losh at "Oct 2, 97 05:35:52 pm" To: imp@village.org (Warner Losh) Date: Mon, 6 Oct 1997 08:08:48 -0700 (PDT) Cc: chad@dcfinc.com, dg@root.com, jkh@time.cdrom.com, andrsn@andrsn.stanford.edu, freebsd-stable@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL25 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > In message <199710022331.QAA29397@freebie.dcfinc.com> "Chad R. Larson" writes: > : In other words, say I get my new, hot 2.2.5-RELEASE CD-ROMs from Walnut > : Creek via my subscription. I build a brand new box and load it from the > : CD. Then I CVSup against 2.2-STABLE to pick up any last minute bug > : fixes. What should the release identifier be now? Whatever it is, it > : should be different than before the CVSup. And it should be something > : that can be easily determined from within a script, for autoconfigures > : and the like. > > Unless I'm missing something, that's what I'm proposing. uname -r > should return 2.2.5-STABLE in this scenario. This is a good > compromise between being too precise (heisenberg would have something > to say about the CVS tree, if Terry doesn't beat him to it) and too > vauge (the current status quo). And it did this, when I was still pretty active in this stuff: Script started on Mon Oct 6 08:08:08 1997 GndRsh# uname -r 2.1.5-STABLE GndRsh# exit Script done on Mon Oct 6 08:08:11 1997 -- Rod Grimes rgrimes@gndrsh.aac.dev.com Accurate Automation, Inc. Reliable computers for FreeBSD From owner-freebsd-stable Mon Oct 6 08:10:52 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id IAA03774 for stable-outgoing; Mon, 6 Oct 1997 08:10:52 -0700 (PDT) (envelope-from owner-freebsd-stable) Received: from GndRsh.aac.dev.com (GndRsh.aac.dev.com [198.145.92.241]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id IAA03767 for ; Mon, 6 Oct 1997 08:10:48 -0700 (PDT) (envelope-from rgrimes@GndRsh.aac.dev.com) Received: (from rgrimes@localhost) by GndRsh.aac.dev.com (8.8.5/8.7.3) id IAA00329; Mon, 6 Oct 1997 08:10:01 -0700 (PDT) From: "Rodney W. Grimes" Message-Id: <199710061510.IAA00329@GndRsh.aac.dev.com> Subject: Re: CVSUP vs. SNAPS In-Reply-To: from Doug Russell at "Oct 2, 97 11:32:11 pm" To: drussell@saturn-tech.com (Doug Russell) Date: Mon, 6 Oct 1997 08:10:01 -0700 (PDT) Cc: imp@village.org, dg@root.com, jkh@time.cdrom.com, andrsn@andrsn.stanford.edu, freebsd-stable@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL25 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > On Thu, 2 Oct 1997, Warner Losh wrote: > > > *PLEASE*PLEASE*PLEASE* listen to Rod. The kernels after 2.2.5-RELEASE > > should be called 2.2.5-STABLE. > > Or we could always call it 2.2.x-STABLE, to indicate that it is the most > recent of the 2.2 branch (which is therefore, the 2.2.x branch...) Won't do you any good, you wont know if your post 2.2.1, 2.2.2, 2.2.5, kinda defeats the purpose of REVISION :-(. -- Rod Grimes rgrimes@gndrsh.aac.dev.com Accurate Automation, Inc. Reliable computers for FreeBSD From owner-freebsd-stable Mon Oct 6 08:14:48 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id IAA03956 for stable-outgoing; Mon, 6 Oct 1997 08:14:48 -0700 (PDT) (envelope-from owner-freebsd-stable) Received: from GndRsh.aac.dev.com (GndRsh.aac.dev.com [198.145.92.241]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id IAA03950 for ; Mon, 6 Oct 1997 08:14:45 -0700 (PDT) (envelope-from rgrimes@GndRsh.aac.dev.com) Received: (from rgrimes@localhost) by GndRsh.aac.dev.com (8.8.5/8.7.3) id IAA00340; Mon, 6 Oct 1997 08:14:27 -0700 (PDT) From: "Rodney W. Grimes" Message-Id: <199710061514.IAA00340@GndRsh.aac.dev.com> Subject: Re: CVSUP vs. SNAPS In-Reply-To: <199710032209.PAA15020@bofh.noc.best.net> from Ron Echeverri at "Oct 3, 97 03:09:51 pm" To: rone@bofh.noc.best.net (Ron Echeverri) Date: Mon, 6 Oct 1997 08:14:27 -0700 (PDT) Cc: stable@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL25 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > Rodney W. Grimes writes: > > >How about the fact that a 2.2.2 release occured, but somthing built > > >from the bits on the 2.2.0 branch report via uname that they are > > >2.2-STABLE. That is going down! > > No, "2.2" refers to the branch, not to a release. I think we make that > > pretty clear. > David, perhaps you should try and figure out just what OS I am running: > Orbit:root {104}# uname -a > FreeBSD Orbit.qcsn.com 2.2-STABLE FreeBSD 2.2-STABLE #2: Fri Sep 19 13:56:36 PDT 1997 root@Orbit.aac.dev.com:/usr/src/sys/compile/ORBIT i386 > > Now you tell me, is that before or after 2.2.2??? > > If you're running -stable, you're supposed to be tracking -stable. If > you aren't, it's your own fault. Ohh... let me see, I sell system for a living, 100's a year, my clients like them to come preloaded with the latest bits that I have certified for production use, they install the box and it runs, infact it runs great for a year or so, then they call me because they want to change some things, well, I have to figure out what they have before I go makeing recomendations. No, noone said just because you LOAD a custom built X.Y-STABLE that you have to track it. -- Rod Grimes rgrimes@gndrsh.aac.dev.com Accurate Automation, Inc. Reliable computers for FreeBSD From owner-freebsd-stable Mon Oct 6 08:16:13 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id IAA04120 for stable-outgoing; Mon, 6 Oct 1997 08:16:13 -0700 (PDT) (envelope-from owner-freebsd-stable) Received: from GndRsh.aac.dev.com (GndRsh.aac.dev.com [198.145.92.241]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id IAA04112 for ; Mon, 6 Oct 1997 08:16:09 -0700 (PDT) (envelope-from rgrimes@GndRsh.aac.dev.com) Received: (from rgrimes@localhost) by GndRsh.aac.dev.com (8.8.5/8.7.3) id IAA00354; Mon, 6 Oct 1997 08:14:47 -0700 (PDT) From: "Rodney W. Grimes" Message-Id: <199710061514.IAA00354@GndRsh.aac.dev.com> Subject: Re: CVSUP vs. SNAPS In-Reply-To: <24377.875919219@time.cdrom.com> from "Jordan K. Hubbard" at "Oct 3, 97 03:53:39 pm" To: jkh@time.cdrom.com (Jordan K. Hubbard) Date: Mon, 6 Oct 1997 08:14:47 -0700 (PDT) Cc: imp@village.org, jdp@polstra.com, mark@quickweb.com, stable@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL25 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > Jordan, when's the first day that you'll listen to new arguments on > > this :-) > > The day after 2.2.5 goes out the door. ;) Okay, I'll fix it as soon as I see your commit :-) -- Rod Grimes rgrimes@gndrsh.aac.dev.com Accurate Automation, Inc. Reliable computers for FreeBSD From owner-freebsd-stable Mon Oct 6 08:21:10 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id IAA04409 for stable-outgoing; Mon, 6 Oct 1997 08:21:10 -0700 (PDT) (envelope-from owner-freebsd-stable) Received: from GndRsh.aac.dev.com (GndRsh.aac.dev.com [198.145.92.241]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id IAA04389 for ; Mon, 6 Oct 1997 08:21:06 -0700 (PDT) (envelope-from rgrimes@GndRsh.aac.dev.com) Received: (from rgrimes@localhost) by GndRsh.aac.dev.com (8.8.5/8.7.3) id IAA00369; Mon, 6 Oct 1997 08:20:44 -0700 (PDT) From: "Rodney W. Grimes" Message-Id: <199710061520.IAA00369@GndRsh.aac.dev.com> Subject: Re: CVSUP vs. SNAPS In-Reply-To: <199710051036.DAA05559@bubble.didi.com> from Satoshi Asami at "Oct 5, 97 03:36:11 am" To: asami@cs.berkeley.edu (Satoshi Asami) Date: Mon, 6 Oct 1997 08:20:44 -0700 (PDT) Cc: dg@root.com, jkh@time.cdrom.com, andrsn@andrsn.stanford.edu, freebsd-stable@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL25 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > * David, perhaps you should try and figure out just what OS I am running: > * Orbit:root {104}# uname -a > * FreeBSD Orbit.qcsn.com 2.2-STABLE FreeBSD 2.2-STABLE #2: Fri Sep 19 13:56:36 PDT 1997 root@Orbit.aac.dev.com:/usr/src/sys/compile/ORBIT i386 > * > * Now you tell me, is that before or after 2.2.2??? > > I don't know. All I know is that you built your kernel on 9/19. > > Why does it matter whether it's before or after 2.2.2? What I need > (if I were David trying to debug your system), what I need is exactly > when you cvsupped (and cvs updated) your stuff last. Whether you did > that before or after 2.2.2 is really too large of a glanurality to be > of any help. You are tracking a moving target for christsakes, the > uname can say "FreeBSD-STABLE" for all we care (except that will > be confusing because of 2.1 and 2.2). Of all people to make this mistake. Okay, I got this old box, I need to grab a port for it, but I need to know if I want the port from the 2.2, 2.2.1 or 2.2.2 cdrom. Yea, I updated the box a couple times, but it still should run any port from the correct cdrom, or for that matter from the archives on the ftp site. Get the picture??? > Besides, if I show you a uname that says "3.0-CURRENT Fri Jan 18 > 13:56:36 PST 1998", can you tell whether it's before or after 3.0R? Nope, not if Jordan insistes on continuing to equate a variable named REVISION to a management tool called cvs and it's branch tags :-( -- Rod Grimes rgrimes@gndrsh.aac.dev.com Accurate Automation, Inc. Reliable computers for FreeBSD From owner-freebsd-stable Mon Oct 6 08:35:36 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id IAA05250 for stable-outgoing; Mon, 6 Oct 1997 08:35:36 -0700 (PDT) (envelope-from owner-freebsd-stable) Received: from time.cdrom.com (time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id IAA05245 for ; Mon, 6 Oct 1997 08:35:33 -0700 (PDT) (envelope-from jkh@time.cdrom.com) Received: from time.cdrom.com (localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.7/8.6.9) with ESMTP id IAA03111; Mon, 6 Oct 1997 08:34:01 -0700 (PDT) To: "Rodney W. Grimes" cc: jfarmer@sabre.goldsword.com, kkennawa@physics.adelaide.edu.au, andrsn@andrsn.stanford.edu, dg@root.com, freebsd-stable@FreeBSD.ORG, jfarmer@goldsword.com Subject: Re: CVSUP vs. SNAPS In-reply-to: Your message of "Mon, 06 Oct 1997 08:05:27 PDT." <199710061505.IAA00297@GndRsh.aac.dev.com> Date: Mon, 06 Oct 1997 08:34:00 -0700 Message-ID: <3107.876152040@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-stable@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Rod, give *me* a break. Where were you several months ago with this Burning Urgent Crisis of yours? I've already said once during this little tempest-in-a-teapot we've been having over newvers.sh that, had this been brought up at some time other than the BETA period, I'd have been happy to do something about it! This is basically called "leaving it too late," Rod, a concept which I'll grant you're probably simply unfamiliar with given your own sordid history of taking 12 months to do 6 month jobs. :-P You also grace us so infrequently in these mailing lists, occasionally popping up only long enough to fire a couple of rounds at someone from your little bell tower before disappearing again, that I'm afraid I just can't summon up all that much enthusiasm for participating in this latest attack of Rodness. You missed the boat and you had several months' warning on the sailing date - you've no one to blame but yourself so let's just cut the crap and reconvene this issue *after* 2.2.5 is out the door, at which point in time everyone here who feels so bloody passionately about the value of this little string can debate it for weeks on end if they so choose. After the debate is over and a concensus is reached, I'll be *more than happy* to commit whatever change your little hearts desire. Until then, however, I'll spend my remaining time between now and 2.2.5-RELEASE on more reasonable worries like basic functionality and reading through our oh-so-exciting PR database, OK? Grrr. Bike shelters. Bike shelters! Jordan From owner-freebsd-stable Mon Oct 6 08:44:01 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id IAA05838 for stable-outgoing; Mon, 6 Oct 1997 08:44:01 -0700 (PDT) (envelope-from owner-freebsd-stable) Received: from andrsn.stanford.edu (andrsn.Stanford.EDU [36.33.0.163]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id IAA05800 for ; Mon, 6 Oct 1997 08:43:11 -0700 (PDT) (envelope-from andrsn@andrsn.stanford.edu) Received: from localhost (localhost.stanford.edu [127.0.0.1]) by andrsn.stanford.edu (8.8.7/8.6.12) with SMTP id IAA06087 for ; Mon, 6 Oct 1997 08:41:10 -0700 (PDT) Date: Sun, 5 Oct 1997 21:59:08 -0700 (PDT) From: Annelise Anderson To: Ted Spradley cc: Richard Wackerbarth , Hetzels@aol.com, stable@freebsd.org Subject: Re: Fwd: CVSup release identity In-Reply-To: <199710051822.NAA02733@set.spradley.dyn.ml.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII ReSent-Date: Mon, 6 Oct 1997 08:40:50 -0700 (PDT) ReSent-From: Annelise Anderson ReSent-To: freebsd-stable@freebsd.org ReSent-Message-ID: Sender: owner-freebsd-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Sun, 5 Oct 1997, Ted Spradley wrote: > > > >uname -r > > > > > >which will result in the message: > > > > > >FreeBSD 2.2-STABLE-AB > > > > > >or > > > > > >FreeBSD 2.2-STABLE (0360) > > > > I think that this is a very good idea. I would delete the "-STABLE" > > portion of the label. "FreeBSD 2.2 (0360)" conveys the same info, is shorter > > and eliminates some of the confusion. For the RELEASES, I would use > > "FreeBSD 2.2.0", "FreeBSD 2.2.5", etc. > > I like this. If it's got three digits (e.g. 2.2.5), it's a release. If it's > got two digits plus the extra part, it's taken from an on-going branch, and > the extra part indicates when it was taken. That should help clear up any > confusion between branches and releases. But releases are also taken from ongoing branches. In any case, uname -r on my machine now produces: 2.2-STABLE-971004-19:45 PDT which is explicit in indicating the date and time at which cvsup began downloading the sources. That seems more informative than a code that has to be translated into a date. Annelise From owner-freebsd-stable Mon Oct 6 09:02:24 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id JAA07236 for stable-outgoing; Mon, 6 Oct 1997 09:02:24 -0700 (PDT) (envelope-from owner-freebsd-stable) Received: from macs.mxim.com (macs.mxim.com [204.17.143.130]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id JAA07227 for ; Mon, 6 Oct 1997 09:02:08 -0700 (PDT) (envelope-from michaele@mxim.com) Received: from localhost (michaele@localhost) by macs.mxim.com (8.7/8.6.9) with SMTP id JAA10633 for ; Mon, 6 Oct 1997 09:01:55 -0700 (PDT) Date: Mon, 6 Oct 1997 09:01:55 -0700 (PDT) From: Michael Enkelis X-Sender: michaele@macs To: freebsd-stable@freebsd.org Subject: 2.2-970930-RELENG Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hardware on systems: #1 = Intel 586/100 16 meg EDO ram Adaptec 2940UW + Quantum 3.2GB drive(*) 3COM 3C900combo S3-TRIO display card #2 = Intel 486/50 32 meg ram Adaptec 2742T + Quantum 3.2GB drive(*) 3COM 3C589 ATI-MACH32 display card (*) Drive is in removable scsi bay, and switched between systems. System booted "-s" and at shell prompt, Panic seen on system #1,when trying to "ifconfig" vx0: Fatal trap 12: Page fault virtual addr: 0x80000000 fault code: Supervisor read, page not present IP: 0x8:0xf0148e9c SP: 0x10:0xefbffde0 FP: 0x10:0xefbffe0c CS: base 0x0, limit 0xfffff, type 0x1b DPL 0, PRES 1, def32 1,gran 1 Eflags: IE, resume, IOPL=0 Current Process: 43 ifconfig System booted "-s", Halt on system probe seen on system #2: ahc0: aic 7770 <= REV C . . . apm0: disabled, not probed. ahc0: brkadrint, Illegal Host Access as seqaddr = 0x0 _ _ _ __ michaele@mxim.com ' ) ) ) / /) / ` / /) Michael Enkelis / / / o _. /_ __. _ // /-- __ /_ _ // o _ (503) 641 - 3737 x2245 / ' (_(_(__/ /_(_(_(<_(/_ (___, /) )_/ <_(<_(/_(_/_)_ From owner-freebsd-stable Mon Oct 6 09:23:01 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id JAA08645 for stable-outgoing; Mon, 6 Oct 1997 09:23:01 -0700 (PDT) (envelope-from owner-freebsd-stable) Received: from krabi.mbp.ee (root@krabi.mbp.ee [194.204.12.83]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id JAA08607 for ; Mon, 6 Oct 1997 09:22:44 -0700 (PDT) (envelope-from root@krabi.mbp.ee) Received: from krabi.mbp.ee ([127.0.0.1]) by krabi.mbp.ee with esmtp (ident root using rfc1413) id m0xIIcC-0008VtC (Debian Smail-3.2 1996-Jul-4 #2); Mon, 6 Oct 1997 22:14:48 +0300 (EEST) Message-ID: <343938A6.25C68AC9@krabi.mbp.ee> Date: Mon, 06 Oct 1997 22:14:46 +0300 From: Superuser Organization: Mainor Bonnier Publications Ltd. X-Mailer: Mozilla 4.03 [en] (X11; I; Linux 2.0.30 i586) MIME-Version: 1.0 To: freebsd-stable@FreeBSD.ORG Subject: (no subject) Content-Type: multipart/alternative; boundary="------------78B1EE39265A3B9C0AD89889" Sender: owner-freebsd-stable@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk --------------78B1EE39265A3B9C0AD89889 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit subscribe freebsd-stable -- _____________ Lauri Laupmaa mauri@mbp.ee --------------78B1EE39265A3B9C0AD89889 Content-Type: text/html; charset=us-ascii Content-Transfer-Encoding: 7bit subscribe freebsd-stable 
-- 
_____________
Lauri Laupmaa
mauri@mbp.ee
  --------------78B1EE39265A3B9C0AD89889-- From owner-freebsd-stable Mon Oct 6 10:06:05 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id KAA11645 for stable-outgoing; Mon, 6 Oct 1997 10:06:05 -0700 (PDT) (envelope-from owner-freebsd-stable) Received: from freebie.dcfinc.com (freebie.dcfinc.com [138.113.2.8]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id KAA11640 for ; Mon, 6 Oct 1997 10:06:01 -0700 (PDT) (envelope-from chad@freebie.dcfinc.com) Received: (from chad@localhost) by freebie.dcfinc.com (8.8.3/8.8.3a) id KAA06072; Mon, 6 Oct 1997 10:04:36 -0700 (MST) From: "Chad R. Larson" Message-Id: <199710061704.KAA06072@freebie.dcfinc.com> Subject: Re: Fwd: CVSup release identity To: rkw@dataplex.net (Richard Wackerbarth) Date: Mon, 6 Oct 1997 10:04:34 -0700 (MST) Cc: andrsn@andrsn.stanford.edu, stable@FreeBSD.ORG In-Reply-To: from Richard Wackerbarth at "Oct 6, 97 05:38:51 am" Reply-to: chad@dcfinc.com 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 X-Loop: FreeBSD.org Precedence: bulk > >But releases are also taken from ongoing branches. In any case, uname -r > >on my machine now produces: > > > >2.2-STABLE-971004-19:45 PDT > > > >which is explicit in indicating the date and time at which cvsup began > >downloading the sources. That seems more informative than a code that > >has to be translated into a date. > > Well, I would still get rid of the "-STABLE". I would also use Zulu time > and convert it all to a number. Thus > > "FreeBSD 2.2 (9710050245)" I agree with the deletion of the "STABLE" string; the other changes would make it redundant. As an aside, we could drop the "RELEASE" string as well, for the same reason. But I would argue for a sequence number, rather than a date/time. In two digits there are 3800 or so possible combinations of [A-z][0-9]. Just for economy, "2.2-BD" rings better to me, and eliminates worry about time zones and daylight savings. > However, the date/time stamp should be made when the source is extracted > from the master source and not when YOU get a second or third generation > copy from some distribution point. Yes. We would want the commit process to increment the counter. > Richard Wackerbarth -crl -- Chad R. Larson (CRL22) Brother, can you paradigm? 602-953-1392 chad@dcfinc.com chad@anasazi.com crl22@aol.com DCF, Inc. - 14523 North 49th Place, Scottsdale, Arizona 85254 From owner-freebsd-stable Mon Oct 6 10:20:04 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id KAA12546 for stable-outgoing; Mon, 6 Oct 1997 10:20:04 -0700 (PDT) (envelope-from owner-freebsd-stable) Received: from florence.pavilion.net (florence.pavilion.net [194.242.128.25]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id KAA12498; Mon, 6 Oct 1997 10:19:57 -0700 (PDT) (envelope-from joe@florence.pavilion.net) Received: (from joe@localhost) by florence.pavilion.net (8.8.7/8.8.7) id SAA08911; Mon, 6 Oct 1997 18:18:30 +0100 (BST) Message-ID: <19971006181829.25378@pavilion.net> Date: Mon, 6 Oct 1997 18:18:29 +0100 From: Josef Karthauser To: dg@root.com Cc: "C. Stephen Gunn" , stable@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: Attention all users of the de driver! References: <199710061330.NAA12904@mail.wintek.com> <199710061453.HAA27354@implode.root.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.81 In-Reply-To: <199710061453.HAA27354@implode.root.com>; from David Greenman on Mon, Oct 06, 1997 at 07:53:29AM -0700 X-NCC-RegID: uk.pavilion Sender: owner-freebsd-stable@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk We've been running SMC Etherpower 10Mbps cards since 2.0.5, currently on RELENG_2_2 with no problems at all. (We've currently got 9 servers.) Joe -- Josef Karthauser Technical Manager Email: joe@pavilion.net Pavilion Internet plc. [Tel: +44 1273 607072 Fax: +44 1273 607073] From owner-freebsd-stable Mon Oct 6 11:19:51 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id LAA16501 for stable-outgoing; Mon, 6 Oct 1997 11:19:51 -0700 (PDT) (envelope-from owner-freebsd-stable) Received: from btp1da.phy.uni-bayreuth.de (btp1da.phy.uni-bayreuth.de [132.180.20.32]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id LAA16495 for ; Mon, 6 Oct 1997 11:19:47 -0700 (PDT) (envelope-from werner@btp1da.phy.uni-bayreuth.de) Received: (from werner@localhost) by btp1da.phy.uni-bayreuth.de (8.8.7/8.7.3) id UAA00510; Mon, 6 Oct 1997 20:19:41 +0200 (MEST) Message-ID: <19971006201941.41373@btp1da.phy.uni-bayreuth.de> Date: Mon, 6 Oct 1997 20:19:41 +0200 From: Werner Griessl To: stable@freebsd.org Subject: panic on 2.2-stable from today Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.84e Sender: owner-freebsd-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk A 2.2-stable kernel after a make world and new kernel-build from today (Mon Oct 6) panics for me with: kernel: type 12 trap, code 0 stopped at _pmap_extract+0x28: movl 0(%edx,%eax,4),%edx Rebooting the system with the old kernel from Oct 1 everything is fine. Werner Here is the dmesg from the old kernel: Copyright (c) 1992-1997 FreeBSD Inc. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 2.2-STABLE #0: Wed Oct 1 14:37:38 MEST 1997 croot@btp1da.phy.uni-bayreuth.de:/spare/F/src/sys/compile/BTP1DA CPU: Pentium (199.43-MHz 586-class CPU) Origin = "GenuineIntel" Id = 0x544 Stepping=4 Features=0x8001bf real memory = 33554432 (32768K bytes) avail memory = 31035392 (30308K bytes) Probing for devices on PCI bus 0: chip0 rev 1 on pci0:0 chip1 rev 1 on pci0:7:0 chip2 rev 0 on pci0:7:1 vga0 rev 84 int a irq 11 on pci0:14 ncr0 rev 17 int a irq 10 on pci0:15 (ncr0:0:0): 5.0 MB/s (200 ns, offset 8) (ncr0:0:0): "IBM OEM 0664M1H 7 70" type 0 fixed SCSI 2 sd0(ncr0:0:0): Direct-Access sd0(ncr0:0:0): 10.0 MB/s (100 ns, offset 8) 1920MB (3933040 512 byte sectors) (ncr0:1:0): "DEC DSP3160S 426F" type 0 fixed SCSI 2 sd1(ncr0:1:0): Direct-Access sd1(ncr0:1:0): 10.0 MB/s (100 ns, offset 8) 1526MB (3125408 512 byte sectors) (ncr0:2:0): "TOSHIBA CD-ROM XM-5401TA 3605" type 5 removable SCSI 2 cd0(ncr0:2:0): CD-ROM cd0(ncr0:2:0): asynchronous. can't get the size (ncr0:3:0): "IBM DCAS-34330 S65A" type 0 fixed SCSI 2 sd2(ncr0:3:0): Direct-Access sd2(ncr0:3:0): 10.0 MB/s (100 ns, offset 8) 4134MB (8467200 512 byte sectors) Probing for devices on the ISA bus: vt0 at 0x60-0x6f irq 1 on motherboard vt0: unkown s3, 80 col, color, 8 scr, mf2-kbd, [R3.20-b24] ed0 at 0x280-0x29f irq 5 maddr 0xd8000 msize 16384 on isa ed0: address 00:00:c0:ac:a3:61, type WD8013EPC (16 bit) sio0 at 0x3f8-0x3ff irq 4 on isa sio0: type 16550A sio1 at 0x2f8-0x2ff irq 3 on isa sio1: type 16550A lpt0 at 0x378-0x37f irq 7 on isa lpt0: Interrupt-driven port lp0: TCP/IP capable interface lpt1 not found at 0xffffffff mcac0 at 0x340 irq 12 on isa mca0-63: Bitzer Digital-I/O 0:static (NBPG=4096) 19970812 fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa fdc0: NEC 72065B fd0: 1.44MB 3.5in wdc0 at 0x1f0-0x1f7 irq 14 flags 0x80008000 on isa wdc0: unit 0 (wd0): , 32-bit wd0: 1222MB (2503872 sectors), 2484 cyls, 16 heads, 63 S/T, 512 B/S wdc1 not found at 0x170 npx0 on motherboard npx0: INT 16 interface WARNING: / was not properly dismounted. From owner-freebsd-stable Mon Oct 6 11:23:13 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id LAA16861 for stable-outgoing; Mon, 6 Oct 1997 11:23:13 -0700 (PDT) (envelope-from owner-freebsd-stable) Received: from pooh.cdrom.com (pooh.cdrom.com [204.216.28.222]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id LAA16856 for ; Mon, 6 Oct 1997 11:23:11 -0700 (PDT) (envelope-from murray@pooh.cdrom.com) Received: from localhost (murray@localhost) by pooh.cdrom.com (8.8.7/8.7.3) with SMTP id LAA07943; Mon, 6 Oct 1997 11:21:46 -0700 (PDT) Date: Mon, 6 Oct 1997 11:21:46 -0700 (PDT) From: Murray Stokely To: Richard Wackerbarth cc: Annelise Anderson , stable@FreeBSD.ORG Subject: Re: Fwd: CVSup release identity In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Mon, 6 Oct 1997, Richard Wackerbarth wrote: % Well, I would still get rid of the "-STABLE". I would also use Zulu time % and convert it all to a number. Thus Then what about -CURRENT?! -STABLE needs to stay there. Murray Stokely From owner-freebsd-stable Mon Oct 6 11:39:46 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id LAA18424 for stable-outgoing; Mon, 6 Oct 1997 11:39:46 -0700 (PDT) (envelope-from owner-freebsd-stable) Received: from shrimp.dataplex.net (shrimp.dataplex.net [208.2.87.3]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id LAA18407 for ; Mon, 6 Oct 1997 11:39:37 -0700 (PDT) (envelope-from rkw@dataplex.net) Received: from [204.69.236.50] (GATEWAY.SKIPSTONE.COM [198.214.10.129]) by shrimp.dataplex.net (8.8.5/8.8.5) with ESMTP id NAA02976; Mon, 6 Oct 1997 13:39:14 -0500 (CDT) X-Sender: rkw@mail.dataplex.net Message-Id: In-Reply-To: References: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Mon, 6 Oct 1997 13:39:02 -0500 To: Murray Stokely From: Richard Wackerbarth Subject: Re: Fwd: CVSup release identity Cc: stable@FreeBSD.ORG Sender: owner-freebsd-stable@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >On Mon, 6 Oct 1997, Richard Wackerbarth wrote: >% Well, I would still get rid of the "-STABLE". I would also use Zulu time >% and convert it all to a number. Thus > >Then what about -CURRENT?! -STABLE needs to stay there. No, it does not! The "current" branch is presently called "3.0". As far as distinguishing the versions of 2.2 which preceeded the initial release, whatever naming convention we use to distinguish later versions can be applied. For example, were we to have used the ctm delta numbers, as I recall, they were above 0100 when the 2.2.0 release happened. I can see the argument that designating the head of the development tree as 3.0 is premature. That designation probably should not have been applied until there was an actual development branch created. However, since it is likely that everything presently going into the tree will be included in 3.0, I don't think it hurts. Perhaps we should revisit this just before we split the next development branch. At that time we might want to apply a name to the development head which will not become obsolete. However, using "4.0" for the next year or so would also work. Richard Wackerbarth From owner-freebsd-stable Mon Oct 6 13:02:17 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id NAA23914 for stable-outgoing; Mon, 6 Oct 1997 13:02:17 -0700 (PDT) (envelope-from owner-freebsd-stable) Received: from live-oak.cycon.com (live-oak.CYCON.COM [198.202.237.69]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id NAA23908; Mon, 6 Oct 1997 13:02:14 -0700 (PDT) (envelope-from ardoin@cycon.com) Received: from localhost (ardoin@localhost) by live-oak.cycon.com (8.8.5/8.7.3) with SMTP id QAA15634; Mon, 6 Oct 1997 16:12:37 -0400 (EDT) X-Authentication-Warning: live-oak.cycon.com: ardoin owned process doing -bs Date: Mon, 6 Oct 1997 16:12:32 -0400 (EDT) From: Cy Ardoin To: "Jordan K. Hubbard" cc: current@FreeBSD.ORG, stable@FreeBSD.ORG Subject: Re: Attention all users of the de driver! In-Reply-To: <1948.876121011@time.cdrom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Well I've had problems. With 2.2 switching from 10BT to BNC and refusing to switch back or reset. Installed the new drivers in Aug from 3.0 and the problem is still there. Both SMC and SMC dual 10Mb cards. This never happened with 2.1.5. These cards are under VERY HEAVY LOADS! Hundreds of MB per hour. It hangs once a day (or more). But it doesn't look like a problem between the 2.2 and 3.0 code. Tried using fxp cards on 10MB but they have to be reset (ifconfig up) every few min. to keep running. Any suggestions for good 10Mb PCI ethernet cards? [Still trying to get more details on the problem] -- Cy Ardoin ardoin@cycon.com From owner-freebsd-stable Mon Oct 6 13:18:43 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id NAA25193 for stable-outgoing; Mon, 6 Oct 1997 13:18:43 -0700 (PDT) (envelope-from owner-freebsd-stable) Received: from emout16.mail.aol.com (emout16.mx.aol.com [198.81.11.42]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id NAA25188 for ; Mon, 6 Oct 1997 13:18:40 -0700 (PDT) (envelope-from Hetzels@aol.com) From: Hetzels@aol.com Received: (from root@localhost) by emout16.mail.aol.com (8.7.6/8.7.3/AOL-2.0.0) id QAA28990 for stable@freebsd.org; Mon, 6 Oct 1997 16:18:07 -0400 (EDT) Date: Mon, 6 Oct 1997 16:18:07 -0400 (EDT) Message-ID: <971006161539_1833122661@emout16.mail.aol.com> To: stable@freebsd.org Subject: Re: CVSup release identity Sender: owner-freebsd-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk In a message dated 97-10-06 14:28:35 EDT, chad@freebie.dcfinc.com writes: > > Well, I would still get rid of the "-STABLE". I would also use Zulu time > > and convert it all to a number. Thus > > > > "FreeBSD 2.2 (9710050245)" I would keep the CURRENT & STABLE tags. As some one has mentioned, how can you know if they are running CURRENT or STABLE. Is 2.2 xxxx CURRENT or is it STABLE, as before the first RELEASE on a branch it would be CURRENT and after the RELEASE it would become STABLE. > But I would argue for a sequence number, rather than a date/time. In > two digits there are 3800 or so possible combinations of [A-z][0-9]. > Just for economy, "2.2-BD" rings better to me, and eliminates worry > about time zones and daylight savings. > > > However, the date/time stamp should be made when the source is extracted > > from the master source and not when YOU get a second or third generation > > copy from some distribution point. > > Yes. We would want the commit process to increment the counter. I, aggree that the counter should be incremented during the commit process also. But that it would probably be easier to increment a numerical counter than a Alpha/Numeric counter. Also, the format could be "FreeBSD 2.2.x.yyyy-STABLE" yyyy - current # of updates to the src tree x - Minor Minor revision # Scot From owner-freebsd-stable Mon Oct 6 13:25:32 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id NAA25765 for stable-outgoing; Mon, 6 Oct 1997 13:25:32 -0700 (PDT) (envelope-from owner-freebsd-stable) Received: from merit.edu (merit.edu [198.108.1.42]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id NAA25752 for ; Mon, 6 Oct 1997 13:25:24 -0700 (PDT) (envelope-from matt@zigg.com) Received: from megaweapon.zigg.com (tcgr-64.dialup.alliance.net [207.74.43.64]) by merit.edu (8.8.7/8.8.5) with ESMTP id QAA09748 for ; Mon, 6 Oct 1997 16:25:10 -0400 (EDT) Received: from localhost (matt@localhost) by megaweapon.zigg.com (8.8.7/8.8.7) with SMTP id QAA00215 for ; Mon, 6 Oct 1997 16:24:53 -0400 (EDT) Date: Mon, 6 Oct 1997 16:24:02 -0400 (EDT) From: Matt Behrens To: stable@freebsd.org Subject: netstat problem appears fixed Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Over the weekend, I re-CVSup'ed, rebuilt kernel, and remade world, and the netstat problem no longer exists. Matt Behrens | Help bring a free inter-user communication http://www.zigg.com | system to the Internet. Join the NetPager matt@zigg.com | Project! http://www.zigg.com/netpager/ From owner-freebsd-stable Mon Oct 6 14:47:58 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id OAA01863 for stable-outgoing; Mon, 6 Oct 1997 14:47:58 -0700 (PDT) (envelope-from owner-freebsd-stable) Received: from shrimp.dataplex.net (shrimp.dataplex.net [208.2.87.3]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id OAA01855 for ; Mon, 6 Oct 1997 14:47:54 -0700 (PDT) (envelope-from rkw@dataplex.net) Received: from [204.69.236.50] (GATEWAY.SKIPSTONE.COM [198.214.10.129]) by shrimp.dataplex.net (8.8.5/8.8.5) with ESMTP id QAA08137; Mon, 6 Oct 1997 16:47:44 -0500 (CDT) X-Sender: rkw@mail.dataplex.net Message-Id: In-Reply-To: <971006161539_1833122661@emout16.mail.aol.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Mon, 6 Oct 1997 16:47:39 -0500 To: Hetzels@aol.com From: Richard Wackerbarth Subject: Re: CVSup release identity Cc: stable@FreeBSD.ORG Sender: owner-freebsd-stable@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Hetzels@aol.com writes: >In a message dated 97-10-06 14:28:35 EDT, chad@freebie.dcfinc.com writes: > >> > Well, I would still get rid of the "-STABLE". I would also use Zulu time >> > and convert it all to a number. Thus >> > >> > "FreeBSD 2.2 (9710050245)" > >I would keep the CURRENT & STABLE tags. As some one has mentioned, how can >you know if they are running CURRENT or STABLE. What difference does it make? You are running 2.2 as of (whenever). To NAME a system on the basis of its STATUS is bogus. Nothing magic happened to the 2.2 code when someone decided to declare it "STABLE". Just one update earlier, it was just as stable. Further, declaring 2.2 "STABLE" did not make 2.1 go away. It is still around. IMHO, people should think of "STABLE" as an alias to conveniently find the most current system to have reached that level of maturity. Once they have selected some system, they no longer should care what level of maturity it has reached. The system either works for them or it does not. Having anyone place a label on it is not going to affect that. BTW, by the time that 3.0 goes BETA, I expect our great team of developers to already be working on features that did not make the 3.0 cut. "CURRENT" (although I would prefer a different name) will belong to this new development. We all know that there will have to be some time between the time that 3.0.0-RELEASE comes out and the time that it can, in good faith be declared "STABLE". What are you going to call the first update after 3.0.0-RELEASE? Richard Wackerbarth From owner-freebsd-stable Mon Oct 6 15:32:01 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id PAA04595 for stable-outgoing; Mon, 6 Oct 1997 15:32:01 -0700 (PDT) (envelope-from owner-freebsd-stable) Received: from dopey.pathlink.com (dopey.pathlink.com [204.30.237.226]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id PAA04562; Mon, 6 Oct 1997 15:31:53 -0700 (PDT) (envelope-from kachun@zippo.com) Received: from dvl-1.pathlink.com (kachun@dvl-1.pathlink.com [204.30.237.241]) by dopey.pathlink.com (8.8.6/8.8.7) with SMTP id PAA25655; Mon, 6 Oct 1997 15:38:21 -0700 (PDT) Message-Id: <199710062238.PAA25655@dopey.pathlink.com> To: freebsd-scsi@freebsd.org Subject: Re: AHC error messages with 2.2.5-BETA Cc: freebsd-stable@freebsd.org From: kachun@zippo.com (Kachun Lee) Date: Mon, 06 Oct 1997 15:31:49 -0700 X-Mailer: WinVN 0.99.8 (x86 32bit) In-Reply-To: <616rbe$758@news.pathlink.com> References: <616rbe$758@news.pathlink.com> MIME-Version: 1.0 Content-Type: Text/Plain; charset=US-ASCII Sender: owner-freebsd-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk In article <616rbe$758@news.pathlink.com>, you say... > >I has a P6 200mhz system running 2.2-releng to the latest 2.2.5-BETA that >had 2 2740 controllers. I replaced 1 of 2740 with a 3740 when I added an >extra drive to it and splitted 12 drives into 3 channels. The system has >been generating the following errors about twice a day with different >drives/ahc channel... > >Oct 4 16:16:39 clark /kernel: ahc1: WARNING no command for scb 99 (cmdcmplt) >Oct 4 16:16:39 clark /kernel: QOUTCNT == 1 > [snip] The above system crashed twice (same sd8, which was running for 1 yr with the 2740) during the past couple days. I can't tell if it is specific to 2.2.5-BETA, since I exchanged a 2740 with a 3740 then upgraded to 2.2.5-BETA. In the meantime, I am trying to do something by disabled SCBPAGING. Any comment would be greately appreciated. Best regards. --------------------------------------------------------- sd8(ahc1:10:0): Target Busy sd8(ahc1:10:0): Target Busy sd8(ahc1:10:0): Target Busy sd8(ahc1:10:0): Target Busy sd8(ahc1:10:0): Target Busy sd8(ahc1:10:0): Target Busy sd8(ahc1:10:0): Target Busy sd8(ahc1:10:0): Target Busy sd8(ahc1:10:0): Target Busy sd8(ahc1:10:0): Target Busy sd8(ahc1:10:0): ABORTED COMMAND asc:4e,0 Overlapped commands attempted field rep laceable unit: 1 , retries:4 sd8(ahc1:10:0): SCB 0x7 - timed out while idle, LASTPHASE == 0x1, SCSISIGI == 0xe6 SEQADDR = 0x5 SCSISEQ = 0x12 SSTAT0 = 0x27 SSTAT1 = 0xb Ordered Tag queued Ordered Tag sent sd8(ahc1:10:0): SCB 0x7 - timed out while idle, LASTPHASE == 0x1, SCSISIGI == 0xe6 SEQADDR = 0x6 SCSISEQ = 0x12 SSTAT0 = 0x27 SSTAT1 = 0xb sd8(ahc1:10:0): Queueing an Abort SCB sd8(ahc1:10:0): Abort Message Sent sd8(ahc1:10:0): SCB 7 - Abort Tag Completed. sd8(ahc1:10:0): no longer in timeout ahc1: WARNING no command for scb 0 (cmdcmplt) QOUTCNT == 1 sd9(ahc1:11:0): SCB 0x5 - timed out while idle, LASTPHASE == 0x1, SCSISIGI == 0x0 SEQADDR = 0x6 SCSISEQ = 0x12 SSTAT0 = 0x5 SSTAT1 = 0xa Ordered Tag queued Ordered Tag sent sd9(ahc1:11:0): SCB 0x5 - timed out while idle, LASTPHASE == 0x1, SCSISIGI == 0x0 SEQADDR = 0x7 SCSISEQ = 0x12 SSTAT0 = 0x5 SSTAT1 = 0xa sd9(ahc1:11:0): Queueing an Abort SCB sd9(ahc1:11:0): Abort Message Sent sd9(ahc1:11:0): SCB 5 - Abort Tag Completed. sd9(ahc1:11:0): no longer in timeout sd8(ahc1:10:0): data overrun of 16736233 bytes detected in Data-In phase. Tag = = 0x0. Forcing a retry. sd8(ahc1:10:0): Have seen Data Phase. Length = 40960. NumSGs = 10. sg[0] - Addr 0xc852000 : Length 4096 sg[1] - Addr 0xbad3000 : Length 4096 sg[2] - Addr 0x9ad4000 : Length 4096 sg[3] - Addr 0x995000 : Length 4096 sg[4] - Addr 0x8ad8000 : Length 4096 sg[5] - Addr 0x4357000 : Length 4096 sg[6] - Addr 0xbd8000 : Length 4096 sg[7] - Addr 0x64d9000 : Length 4096 sg[8] - Addr 0x7a9a000 : Length 4096 sg[9] - Addr 0xa89b000 : Length 4096 sd8(ahc1:10:0): data overrun of 16719337 bytes detected in Data-In phase. Tag = = 0x0. Forcing a retry. sd8(ahc1:10:0): Haven't seen Data Phase. Length = 40960. NumSGs = 10. sg[0] - Addr 0xc852000 : Length 4096 sg[1] - Addr 0xbad3000 : Length 4096 sg[2] - Addr 0x9ad4000 : Length 4096 sg[3] - Addr 0x995000 : Length 4096 sg[4] - Addr 0x8ad8000 : Length 4096 sg[5] - Addr 0x4357000 : Length 4096 sg[6] - Addr 0xbd8000 : Length 4096 sg[7] - Addr 0x64d9000 : Length 4096 sg[8] - Addr 0x7a9a000 : Length 4096 sg[9] - Addr 0xa89b000 : Length 4096 Fatal trap 12: page fault while in kernel mode fault virtual address = 0x513c4073 fault code = supervisor read, page not present instruction pointer = 0x8:0xf019d510 stack pointer = 0x10:0xefbffac8 frame pointer = 0x10:0xefbffad4 code segment = base 0x0, limit 0xfffff, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags = interrupt enabled, resume, IOPL = 0 current process = 107 (nfsd) interrupt mask = panic: page fault syncing disks... From owner-freebsd-stable Mon Oct 6 15:53:38 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id PAA06213 for stable-outgoing; Mon, 6 Oct 1997 15:53:38 -0700 (PDT) (envelope-from owner-freebsd-stable) Received: from implode.root.com (implode.root.com [198.145.90.17]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id PAA06185; Mon, 6 Oct 1997 15:53:22 -0700 (PDT) (envelope-from root@implode.root.com) Received: from implode.root.com (localhost [127.0.0.1]) by implode.root.com (8.8.5/8.8.5) with ESMTP id PAA02577; Mon, 6 Oct 1997 15:55:10 -0700 (PDT) Message-Id: <199710062255.PAA02577@implode.root.com> To: Josef Karthauser cc: stable@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: Attention all users of the de driver! In-reply-to: Your message of "Mon, 06 Oct 1997 18:18:29 BST." <19971006181829.25378@pavilion.net> From: David Greenman Reply-To: dg@root.com Date: Mon, 06 Oct 1997 15:55:10 -0700 Sender: owner-freebsd-stable@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >We've been running SMC Etherpower 10Mbps cards since 2.0.5, currently on >RELENG_2_2 with no problems at all. (We've currently got 9 servers.) Just to make it very clear: we're interested in problems with the new version of the driver in -current, NOT the driver in -stable (which we already know has problems with newer cards, which is why we're considering bringing in the version from -current which has fixed much of this). -DG David Greenman Core-team/Principal Architect, The FreeBSD Project From owner-freebsd-stable Mon Oct 6 17:41:22 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id RAA11471 for stable-outgoing; Mon, 6 Oct 1997 17:41:22 -0700 (PDT) (envelope-from owner-freebsd-stable) Received: from awfulhak.demon.co.uk (awfulhak.demon.co.uk [158.152.17.1]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id RAA11458; Mon, 6 Oct 1997 17:41:02 -0700 (PDT) (envelope-from brian@awfulhak.org) Received: from gate.lan.awfulhak.org (localhost [127.0.0.1]) by awfulhak.demon.co.uk (8.8.5/8.8.5) with ESMTP id WAA03723; Mon, 6 Oct 1997 22:50:11 +0100 (BST) Message-Id: <199710062150.WAA03723@awfulhak.demon.co.uk> X-Mailer: exmh version 2.0zeta 7/24/97 To: "Jordan K. Hubbard" cc: current@FreeBSD.ORG, stable@FreeBSD.ORG Subject: Re: Attention all users of the de driver! In-reply-to: Your message of "Sun, 05 Oct 1997 23:56:51 PDT." <1948.876121011@time.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 06 Oct 1997 22:50:11 +0100 From: Brian Somers Sender: owner-freebsd-stable@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > If you have a de0 device in your machine and you're running -current, > NOW is the time to let us know if there are any problems with it! > > We know for a fact that 2.2-stable's driver does not work on at least > one card, the Znyx 4-port NIC, but we also don't know if 3.0-current > is going to break a lot more people if we bring it in. Therefore, if > you do NOT wish to see the de driver in 2.2-stable updated using the > 3.0-current bits, now is the time to speak up since we will otherwise > take your silence as "it works great, bring it on over!" > > Jordan Just this (posted to -hackers on Sep 13): Subject: de0: system error: master abort > I haven't looked into this myself, but it's annoying me enough (dmesg > is useless) to ask if anyone else is seeing it. > > I get literally millions of these *all* the time. I've commented out > the error locally, but I thought I might ask if anyone added this > feature on purpose. > -- > Brian , > > Don't _EVER_ lose your sense of humour.... It's an SMC card... de0: rev 0x11 int a irq 9 on pci0.17.0 de0: SMC 21041 [10Mb/s] pass 1.1 de0: address 00:00:c0:ff:e9:ce de0: enabling 10baseT port If anyone wants to know more, I'll open the box. The card seems to function ok - the errors are annoying though :-| -- Brian , , Don't _EVER_ lose your sense of humour.... From owner-freebsd-stable Mon Oct 6 18:19:40 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id SAA13734 for stable-outgoing; Mon, 6 Oct 1997 18:19:40 -0700 (PDT) (envelope-from owner-freebsd-stable) Received: from actcom.co.il (baum@actcom.co.il [192.114.47.1]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id SAA13711; Mon, 6 Oct 1997 18:19:30 -0700 (PDT) (envelope-from baum@actcom.co.il) Received: from localhost by actcom.co.il with SMTP (8.8.6/actcom-0.2) id DAA06199; Tue, 7 Oct 1997 03:16:31 +0200 (EET) (rfc931-sender: baum@localhost) Date: Tue, 7 Oct 1997 03:16:31 +0200 (EET) From: Alexander Indenbaum To: stable@FreeBSD.ORG cc: current@FreeBSD.ORG Subject: EXT2FS code from -current to -stable In-Reply-To: <199710062255.PAA02577@implode.root.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Hi! I was wondering - is it possible to merge ext2fs code from -current to -stable, because -stable code is bugged it can not sync while rebooting. I heard it is fixed in current. Alexander Indenbaum baum@actcom.co.il From owner-freebsd-stable Mon Oct 6 20:19:31 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id UAA20966 for stable-outgoing; Mon, 6 Oct 1997 20:19:31 -0700 (PDT) (envelope-from owner-freebsd-stable) Received: from bob.tri-lakes.net ([207.3.81.6]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id UAA20961 for ; Mon, 6 Oct 1997 20:19:29 -0700 (PDT) (envelope-from cdillon@tri-lakes.net) Received: from [207.3.81.152] by bob.tri-lakes.net (NTMail 3.02.13) with ESMTP id va292105 for ; Mon, 6 Oct 1997 22:19:21 -0500 Message-ID: X-Mailer: XFMail 1.1 [p0] on FreeBSD Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: Date: Mon, 06 Oct 1997 22:06:19 -0000 (GMT) From: Chris Dillon To: Richard Wackerbarth Subject: Re: Fwd: CVSup release identity Cc: stable@FreeBSD.ORG Sender: owner-freebsd-stable@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On 06-Oct-97 Richard Wackerbarth wrote: >>I have been following this debate since it started, and my own idea at >the >>beginning of it was very similar to the above. A time stamp is about as >>fine-grained as you can get, and is not dependant on how either CTM or >>cvsup work. After all, this has been how we have been describing just >how >>far along we are on the stable tree for a long time now. "And you >cvsupped >>when? 19:45 10/4/97? Oh, thats just before I made those >>changes." > >I have no objection to using timestamps to identify "progress" along a >branch. >However, you need to realize that the stamp must be applied at the time >that >the snapshot is taken from the master tree. Yes. For those that use cvsup, cvsupd could pass the timestamp to the client using the local time of the master server (therefore avoiding problems cropping up from incorrect local times). As for CTM, when the CTM deltas are made, the time stamp could be applied to them at that time in the same fashion. >We used to look at the timestamp placed on the kernel at compile time. >However, I don't care when you compile the source. (Although I can >conclude >that you are missing later changes.) What I want to know is WHICH version >of the master source you are using. I also do not care when YOU got the >source >from someone else. Since you do not have direct access to the master >source >by either ctm or cvsup, we need to stamp the sources at the time that >they >are extracted from the master source by the primary distributor. Anything >less increases the uncertainty interval. The more latency in the >distribution >mechanism, the higher the uncertainty. Agreed. >The only objection that I have to the use of timestamps as the identifier >is >that they may not be "user friendly". A user who gets a release CD knows >that >he has release "5.1.9". He doesn't realize that it was generated on >October >31 at >4:26:37 PM PDT. Similarly, users of CTM distributions know that they have >updated through delta 4726. > >Richard Wackerbarth But none of that has to change, does it? 5.1.9-RELEASE can still be called 5.1.9-RELEASE... Or am I misunderstanding what you're trying to get across here? :-) P.S. I've only been using FreeBSD for a bit over a year, and only been running 2.2-stable for a few months now.. If any of this sounds like uneducated dribble then maybe it is. :-) This is just what seems to make the most sense to me. --- Chris Dillon --- cdillon@tri-lakes.net --- Powered by FreeBSD, the best free OS on the planet ---- (http://www.freebsd.org) From owner-freebsd-stable Mon Oct 6 20:40:10 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id UAA21879 for stable-outgoing; Mon, 6 Oct 1997 20:40:10 -0700 (PDT) (envelope-from owner-freebsd-stable) Received: from shrimp.dataplex.net (shrimp.dataplex.net [208.2.87.3]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id UAA21874 for ; Mon, 6 Oct 1997 20:40:05 -0700 (PDT) (envelope-from rkw@dataplex.net) Received: from [208.2.87.4] (user4.dataplex.net [208.2.87.4]) by shrimp.dataplex.net (8.8.5/8.8.5) with ESMTP id WAA15178; Mon, 6 Oct 1997 22:40:00 -0500 (CDT) X-Sender: rkw@mail.dataplex.net Message-Id: In-Reply-To: References: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Mon, 6 Oct 1997 22:40:26 -0500 To: Chris Dillon From: Richard Wackerbarth Subject: Re: Fwd: CVSup release identity Cc: stable@freebsd.org Sender: owner-freebsd-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Chris Dillon writes: >Yes. For those that use cvsup, cvsupd could pass the timestamp to >the client using the local time of the master server (therefore avoiding >problems cropping up from incorrect local times). Remember that the cvsupd that YOU contact is NOT the master server. The stamp would need to be inserted ONLY when transferring from the master server. All other distribution systems, including the publicly accessable cvsupd servers and ctm would simply propogate the designation that they receive. This could be most readily done by having it as a string in a file. >>The only objection ... may not be "user friendly". I guess we could do the following: Before release: 2.2 (9710061501) At release: 2.2.0 (RELEASE) After release: 2.2.0 (9710061703) Another Release: 2.2.2 (RELEASE) And then: 2.2.2 (9710061905) That way, anything other than a release would have a timestamp and the number of the previous release from which it was derived. Richard Wackerbarth From owner-freebsd-stable Mon Oct 6 21:45:43 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id VAA25295 for stable-outgoing; Mon, 6 Oct 1997 21:45:43 -0700 (PDT) (envelope-from owner-freebsd-stable) Received: from bob.tri-lakes.net ([207.3.81.6]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id VAA25277 for ; Mon, 6 Oct 1997 21:45:14 -0700 (PDT) (envelope-from cdillon@tri-lakes.net) Received: from [207.3.81.152] by bob.tri-lakes.net (NTMail 3.02.13) with ESMTP id aa292188 for ; Mon, 6 Oct 1997 23:44:37 -0500 Message-ID: X-Mailer: XFMail 1.1 [p0] on FreeBSD Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: Date: Mon, 06 Oct 1997 23:35:57 -0000 (GMT) From: Chris Dillon To: Richard Wackerbarth Subject: Re: Fwd: CVSup release identity Cc: stable@FreeBSD.ORG Sender: owner-freebsd-stable@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On 07-Oct-97 Richard Wackerbarth wrote: >Chris Dillon writes: > >>Yes. For those that use cvsup, cvsupd could pass the timestamp to >>the client using the local time of the master server (therefore avoiding >>problems cropping up from incorrect local times). > >Remember that the cvsupd that YOU contact is NOT the master server. >The stamp would need to be inserted ONLY when transferring from the >master server. All other distribution systems, including the publicly >accessable cvsupd servers and ctm would simply propogate the designation >that they receive. This could be most readily done by having it as a >string in a file. Aaah, ok. I see your point now.. I am sufficiently uneducated in just what happens after somebody commits a piece of code. Apparently it isn't commited to something like cvsup.freebsd.org, or you would consider that the "master server", correct? How often are the distribution servers updated with the master code? If the update occurs instantly (i.e. propogated the instant it is committed or shortly thereafter), the above wouldn't be a problem, would it? Or do the distribution servers "cvsup" from the master servers in the same fashion we cvsup from the distribution servers? > >>>The only objection ... may not be "user friendly". > >I guess we could do the following: > >Before release: >2.2 (9710061501) > >At release: >2.2.0 (RELEASE) > >After release: >2.2.0 (9710061703) > >Another Release: >2.2.2 (RELEASE) > >And then: >2.2.2 (9710061905) > >That way, anything other than a release would have a timestamp and the >number of the previous release from which it was derived. > >Richard Wackerbarth Makes perfect sense to me. Who else likes this idea? :-) --- Chris Dillon --- cdillon@tri-lakes.net --- Powered by FreeBSD, the best free OS on the planet ---- (http://www.freebsd.org) From owner-freebsd-stable Tue Oct 7 01:45:46 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id BAA09876 for stable-outgoing; Tue, 7 Oct 1997 01:45:46 -0700 (PDT) (envelope-from owner-freebsd-stable) Received: from mail.cs.tu-berlin.de (root@mail.cs.tu-berlin.de [130.149.17.13]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id BAA09868; Tue, 7 Oct 1997 01:45:38 -0700 (PDT) (envelope-from wosch@cs.tu-berlin.de) Received: from panke.panke.de (anonymous213.ppp.cs.tu-berlin.de [130.149.17.213]) by mail.cs.tu-berlin.de (8.8.6/8.8.7) with ESMTP id KAA15218; Tue, 7 Oct 1997 10:39:05 +0200 (MET DST) Received: (from wosch@localhost) by panke.panke.de (8.8.5/8.6.12) id KAA00347; Tue, 7 Oct 1997 10:38:58 +0200 (MET DST) Date: Tue, 7 Oct 1997 10:38:58 +0200 (MET DST) Message-Id: <199710070838.KAA00347@panke.panke.de> From: Wolfram Schneider To: stable@freebsd.org cc: jordan@freebsd.org Subject: adduser login class support in 2.2.5? MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Should we add login classes to adduser in 2.2.5? This topic occurs often in -questions. -- Wolfram Schneider http://www.apfel.de/~wosch/ From owner-freebsd-stable Tue Oct 7 02:25:14 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id CAA12183 for stable-outgoing; Tue, 7 Oct 1997 02:25:14 -0700 (PDT) (envelope-from owner-freebsd-stable) Received: from labinfo.iet.unipi.it (labinfo.iet.unipi.it [131.114.9.5]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id CAA11304; Tue, 7 Oct 1997 02:13:48 -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 IAA07727; Tue, 7 Oct 1997 08:54:38 +0100 From: Luigi Rizzo Message-Id: <199710070754.IAA07727@labinfo.iet.unipi.it> Subject: snd971007.tgz To: multimedia@freebsd.org Date: Tue, 7 Oct 1997 08:54:37 +0100 (MET) X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-freebsd-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk [crossposted to -stable and hackers since people might be interested there as well -- sorry for the duplicates... reply go to multimedia only] New snap of the sound code at the following URL: http://www.iet.unipi.it/~luigi/snd971007.tgz http://www.iet.unipi.it/~luigi/pnp970924.tgz this implements AUTO-DMA mode, has been tested for several days on a 2.2.1 system. It seems to work quite well in full duplex with Crystal CS423x, Opti931 and even with the SB16 (and clones of WSS and SB16). It works in half duplex with the SBPro, although with some limitations. Compared to previous snapshots, this code does not suffer from the problems (clicks and deadlocks) which affected the previous driver with certain boards. I have added some code so that -current users can use the code by simply uncommenting a #define USE_POLL in file sound.h If there is sufficient positive feedback it might be possible to put this into 2.2.5 so please guy test this code. The code is still a bit verbose but this is done to ease debugging. If you have problems please supply, in plain ascii, the following data: - OS version; - card type (the more detail, the better it is) - dmesg output if relevant; - pnpinfo output if you have a PnP card. Thanks for your help. Luigi -----------------------------+-------------------------------------- Luigi Rizzo | Dip. di Ingegneria dell'Informazione email: luigi@iet.unipi.it | Universita' di Pisa tel: +39-50-568533 | via Diotisalvi 2, 56126 PISA (Italy) fax: +39-50-568522 | http://www.iet.unipi.it/~luigi/ _____________________________|______________________________________ From owner-freebsd-stable Tue Oct 7 03:37:54 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id DAA16102 for stable-outgoing; Tue, 7 Oct 1997 03:37:54 -0700 (PDT) (envelope-from owner-freebsd-stable) Received: from btp1da.phy.uni-bayreuth.de (btp1da.phy.uni-bayreuth.de [132.180.20.32]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id DAA16096 for ; Tue, 7 Oct 1997 03:37:50 -0700 (PDT) (envelope-from werner@btp1da.phy.uni-bayreuth.de) Received: (from werner@localhost) by btp1da.phy.uni-bayreuth.de (8.8.7/8.7.3) id MAA01414; Tue, 7 Oct 1997 12:37:38 +0200 (MEST) Message-ID: <19971007123738.53825@btp1da.phy.uni-bayreuth.de> Date: Tue, 7 Oct 1997 12:37:38 +0200 From: Werner Griessl To: stable@FreeBSD.ORG Cc: stable@FreeBSD.ORG Subject: Re: panic on 2.2-stable from today References: <19971006201941.41373@btp1da.phy.uni-bayreuth.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.84e In-Reply-To: <19971006201941.41373@btp1da.phy.uni-bayreuth.de>; from Werner Griessl on Mon, Oct 06, 1997 at 08:19:41PM +0200 Sender: owner-freebsd-stable@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Mon, Oct 06, 1997 at 08:19:41PM +0200, Werner Griessl wrote: > A 2.2-stable kernel after a make world and new kernel-build > from today (Mon Oct 6) panics for me with: > > kernel: type 12 trap, code 0 > stopped at _pmap_extract+0x28: movl 0(%edx,%eax,4),%edx > > Rebooting the system with the old kernel from Oct 1 everything > is fine. > > Werner > Found the problem for myself ! The snmpd from ports/ucd-snmp crashed the system. !!! NOTE: ucd-snmp needs recompiling with the newest 2.2-stable !!!! Werner From owner-freebsd-stable Tue Oct 7 03:57:26 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id DAA16789 for stable-outgoing; Tue, 7 Oct 1997 03:57:26 -0700 (PDT) (envelope-from owner-freebsd-stable) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id DAA16777; Tue, 7 Oct 1997 03:57:18 -0700 (PDT) (envelope-from bde@zeta.org.au) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.5/8.6.9) id UAA15356; Tue, 7 Oct 1997 20:51:53 +1000 Date: Tue, 7 Oct 1997 20:51:53 +1000 From: Bruce Evans Message-Id: <199710071051.UAA15356@godzilla.zeta.org.au> To: baum@actcom.co.il, stable@FreeBSD.ORG Subject: Re: EXT2FS code from -current to -stable Cc: current@FreeBSD.ORG Sender: owner-freebsd-stable@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >I was wondering - is it possible to merge ext2fs code >from -current to -stable, because -stable code is bugged >it can not sync while rebooting. >I heard it is fixed in current. No, the fix in -current introduced worse bugs. Now bitmaps are not written in ext2_sbupdate(), so they are not synced by sync() or fsync(). They are synced by unmount() and when they are recycled. Bruce From owner-freebsd-stable Tue Oct 7 04:34:49 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id EAA18713 for stable-outgoing; Tue, 7 Oct 1997 04:34:49 -0700 (PDT) (envelope-from owner-freebsd-stable) Received: from actcom.co.il (baum@actcom.co.il [192.114.47.1]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id EAA18705 for ; Tue, 7 Oct 1997 04:34:41 -0700 (PDT) (envelope-from baum@actcom.co.il) Received: from localhost by actcom.co.il with SMTP (8.8.6/actcom-0.2) id NAA02751 for ; Tue, 7 Oct 1997 13:33:57 +0200 (EET) (rfc931-sender: baum@localhost) Date: Tue, 7 Oct 1997 13:33:54 +0200 (EET) From: Alexander Indenbaum To: stable@FreeBSD.ORG Subject: disklabel problem - disklabel: ioctl DIOCSDINFO: No space left on device In-Reply-To: <199710071051.UAA15356@godzilla.zeta.org.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Hi! I am using -stable and sharing swap partition between Linux and FreeBSD. In order to do so I disklabel swap partition out of /etc/rc echo "LOCAL: Initializing Linux swap partition..." disklabel -w -r /dev/rwd0s5 linswap echo "Turning swap space on..." swapon -a Where linswap is defined in /etc/disktab linswap:ty=mfs:se#512:nt#128:rm#3600:\ :ns#63:nc#13:\ :pb#104769:oa#0:tb=swap:\ :pc#104769:oc#0:bc#4096:fc#512: Anyway, it worked fine since 2.2.0 till 2.2-stable from month or so before. In latest -stable ( from 06.10.97 ) I get message: 1:27pm schneider -> /home/baum# uname -a FreeBSD schneider.actcom.co.il 2.2-STABLE FreeBSD 2.2-STABLE #25: Tue Oct 7 11:52:32 IDT 1997 baum@schneider.actcom.co.il:/usr/src/sys/compile/BAUM i386 1:27pm schneider -> /home/baum# disklabel -w -r /dev/rwd0s5 linswap disklabel: ioctl DIOCSDINFO: No space left on device But when I booted 2.2.1 kernel it worked fine. So what do you think about it? Alexander Indenbaum baum@actcom.co.il From owner-freebsd-stable Tue Oct 7 04:52:18 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id EAA19508 for stable-outgoing; Tue, 7 Oct 1997 04:52:18 -0700 (PDT) (envelope-from owner-freebsd-stable) Received: from sos.freebsd.dk (sos.freebsd.dk [195.8.129.33]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id EAA19486; Tue, 7 Oct 1997 04:52:08 -0700 (PDT) (envelope-from sos@sos.freebsd.dk) Received: (from sos@localhost) by sos.freebsd.dk (8.8.7/8.7.3) id NAA03414; Tue, 7 Oct 1997 13:50:34 +0200 (MEST) From: Søren Schmidt Message-Id: <199710071150.NAA03414@sos.freebsd.dk> Subject: Re: EXT2FS code from -current to -stable In-Reply-To: <199710071051.UAA15356@godzilla.zeta.org.au> from Bruce Evans at "Oct 7, 97 08:51:53 pm" To: bde@zeta.org.au (Bruce Evans) Date: Tue, 7 Oct 1997 13:50:34 +0200 (MEST) Cc: baum@actcom.co.il, stable@FreeBSD.ORG, current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL30 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-stable@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk In reply to Bruce Evans who wrote: > >I was wondering - is it possible to merge ext2fs code > >from -current to -stable, because -stable code is bugged > >it can not sync while rebooting. > >I heard it is fixed in current. > > No, the fix in -current introduced worse bugs. Now bitmaps > are not written in ext2_sbupdate(), so they are not synced > by sync() or fsync(). They are synced by unmount() and when > they are recycled. > > Bruce Now we are talking about ext2fs, what about the version that OpenBSD has, its GPL free (yeah!), do they have a fix for this. -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Søren Schmidt (sos@FreeBSD.org) FreeBSD Core Team Even more code to hack -- will it ever end .. From owner-freebsd-stable Tue Oct 7 05:38:04 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id FAA22313 for stable-outgoing; Tue, 7 Oct 1997 05:38:04 -0700 (PDT) (envelope-from owner-freebsd-stable) Received: from silvia.HIP.Berkeley.EDU (ala-ca9-32.ix.netcom.com [207.93.143.96]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id FAA22303 for ; Tue, 7 Oct 1997 05:38:01 -0700 (PDT) (envelope-from asami@vader.cs.berkeley.edu) Received: (from asami@localhost) by silvia.HIP.Berkeley.EDU (8.8.7/8.6.9) id FAA16981; Tue, 7 Oct 1997 05:37:39 -0700 (PDT) Date: Tue, 7 Oct 1997 05:37:39 -0700 (PDT) Message-Id: <199710071237.FAA16981@silvia.HIP.Berkeley.EDU> To: rgrimes@GndRsh.aac.dev.com CC: dg@root.com, jkh@time.cdrom.com, andrsn@andrsn.stanford.edu, freebsd-stable@FreeBSD.ORG In-reply-to: <199710061520.IAA00369@GndRsh.aac.dev.com> (rgrimes@GndRsh.aac.dev.com) Subject: Re: CVSUP vs. SNAPS From: asami@cs.berkeley.edu (Satoshi Asami) Sender: owner-freebsd-stable@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk * Of all people to make this mistake. Okay, I got this old box, I need * to grab a port for it, but I need to know if I want the port from * the 2.2, 2.2.1 or 2.2.2 cdrom. Yea, I updated the box a couple times, * but it still should run any port from the correct cdrom, or for that * matter from the archives on the ftp site. And you don't even know how to figure out when the last source update was? You have a bigger problem than figuring out which CDROM you need, Rod. ;) (Hint: "sysctl kern.osreldate") Besides, the ports tree on the CDROM is not compatible with the -stable in the future (how can it be?). The compatibility goes in the opposite direction. * > Besides, if I show you a uname that says "3.0-CURRENT Fri Jan 18 * > 13:56:36 PST 1998", can you tell whether it's before or after 3.0R? * * Nope, not if Jordan insistes on continuing to equate a variable named * REVISION to a management tool called cvs and it's branch tags :-( You are missing the point. What I'm saying is that "3.0-CURRENT" is going to mean both pre- and post-3.0 release even with your proposed change. Satoshi From owner-freebsd-stable Tue Oct 7 05:49:20 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id FAA23066 for stable-outgoing; Tue, 7 Oct 1997 05:49:20 -0700 (PDT) (envelope-from owner-freebsd-stable) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id FAA23059 for ; Tue, 7 Oct 1997 05:49:16 -0700 (PDT) (envelope-from bde@zeta.org.au) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.5/8.6.9) id WAA19554; Tue, 7 Oct 1997 22:44:30 +1000 Date: Tue, 7 Oct 1997 22:44:30 +1000 From: Bruce Evans Message-Id: <199710071244.WAA19554@godzilla.zeta.org.au> To: baum@actcom.co.il, stable@FreeBSD.ORG Subject: Re: disklabel problem - disklabel: ioctl DIOCSDINFO: No space left on device Sender: owner-freebsd-stable@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >... >disklabel -w -r /dev/rwd0s5 linswap >... >Where linswap is defined in /etc/disktab >linswap:ty=mfs:se#512:nt#128:rm#3600:\ > :ns#63:nc#13:\ > :pb#104769:oa#0:tb=swap:\ > :pc#104769:oc#0:bc#4096:fc#512: > >Anyway, it worked fine since 2.2.0 till 2.2-stable from >month or so before. In latest -stable ( from 06.10.97 ) >I get message: >1:27pm schneider -> /home/baum# uname -a >FreeBSD schneider.actcom.co.il 2.2-STABLE FreeBSD 2.2-STABLE #25: Tue Oct >7 11:52:32 IDT 1997 >baum@schneider.actcom.co.il:/usr/src/sys/compile/BAUM i386 >1:27pm schneider -> /home/baum# disklabel -w -r /dev/rwd0s5 linswap >disklabel: ioctl DIOCSDINFO: No space left on device Your label is buggy. It specifies a device or partition larger than /dev/rwd0s5. Perhaps `nc' is too large. Also, the label specifies `oa' but not `ob' (this doesn't matter because the default for both is 0). >But when I booted 2.2.1 kernel it worked fine. 2.2.1 is buggy. Bruce From owner-freebsd-stable Tue Oct 7 06:39:38 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id GAA26171 for stable-outgoing; Tue, 7 Oct 1997 06:39:38 -0700 (PDT) (envelope-from owner-freebsd-stable) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id GAA26166; Tue, 7 Oct 1997 06:39:33 -0700 (PDT) (envelope-from bde@zeta.org.au) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.5/8.6.9) id XAA21776; Tue, 7 Oct 1997 23:33:59 +1000 Date: Tue, 7 Oct 1997 23:33:59 +1000 From: Bruce Evans Message-Id: <199710071333.XAA21776@godzilla.zeta.org.au> To: bde@zeta.org.au, sos@sos.freebsd.dk Subject: Re: EXT2FS code from -current to -stable Cc: baum@actcom.co.il, current@FreeBSD.ORG, stable@FreeBSD.ORG Sender: owner-freebsd-stable@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >Now we are talking about ext2fs, what about the version that OpenBSD >has, its GPL free (yeah!), do they have a fix for this. Do you mean the NetBSD version? :-) It should never have had this bug, since the bug is caused by semantic mismatch between BSD buffer handling and vestiges of Linux buffer handling in the GPL'ed part (the Linux and FreeBSD versions of ext2fs want to hang on to buffers for bitmaps, but BSD wants buffers to be released as soon as possible). I was waiting for the Lite2 merge, but that seems to have been done a few months ago, at least in the NetBSD version. Bruce From owner-freebsd-stable Tue Oct 7 07:01:46 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id HAA27518 for stable-outgoing; Tue, 7 Oct 1997 07:01:46 -0700 (PDT) (envelope-from owner-freebsd-stable) Received: from chassiron.ensta.fr (root@chassiron.ensta.fr [147.250.7.201]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id HAA27479; Tue, 7 Oct 1997 07:00:30 -0700 (PDT) (envelope-from bouyer@chassiron.ensta.fr) Received: (from bouyer@localhost) by chassiron.ensta.fr (8.8.6/8.8.5) id PAA12455; Tue, 7 Oct 1997 15:58:52 +0200 (MEST) Message-Id: <199710071358.PAA12455@chassiron.ensta.fr> Date: Tue, 7 Oct 1997 15:58:51 +0200 From: bouyer@chassiron.ensta.fr (Manuel Bouyer) To: sos@sos.freebsd.dk (=?iso-8859-1?Q?S=F8ren?= Schmidt) Cc: stable@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: EXT2FS code from -current to -stable References: <199710071051.UAA15356@godzilla.zeta.org.au> <199710071150.NAA03414@sos.freebsd.dk> X-Mailer: Mutt 0.48.1 Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit In-Reply-To: <199710071150.NAA03414@sos.freebsd.dk>; from Søren Schmidt on Oct 7, 1997 13:50:34 +0200 Sender: owner-freebsd-stable@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Oct 7, Søren Schmidt wrote > Now we are talking about ext2fs, what about the version that OpenBSD > has, its GPL free (yeah!), do they have a fix for this. > #define pedantic Please note that their ext2fs comes from NetBSD ... #undef pedantic -- Manuel Bouyer, LIP6, Universite Paris VI. email: bouyer@rp.lip6.fr bouyer@ensta.fr -- From owner-freebsd-stable Tue Oct 7 07:12:07 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id HAA28296 for stable-outgoing; Tue, 7 Oct 1997 07:12:07 -0700 (PDT) (envelope-from owner-freebsd-stable) Received: from krabi.mbp.ee (root@krabi.mbp.ee [194.204.12.83]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id HAA28246 for ; Tue, 7 Oct 1997 07:11:57 -0700 (PDT) (envelope-from root@krabi.mbp.ee) Received: from localhost by krabi.mbp.ee with esmtp id m0xIdAf-0008VtC (Debian Smail-3.2 1996-Jul-4 #2); Tue, 7 Oct 1997 20:11:45 +0300 (EEST) Date: Tue, 7 Oct 1997 19:46:17 +0300 (EEST) From: Superuser To: stãble@freebsd.org Subject: error in make world Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII ReSent-Date: Tue, 7 Oct 1997 20:11:22 +0300 (EEST) ReSent-From: Superuser ReSent-To: stable@freebsd.org ReSent-Message-ID: Sender: owner-freebsd-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi I'm relatively unexperienced FreeBSD user and for first time tried: cd /usr/src make world It went a long way, but suddenly bombed out saying: install -c -s -o root -g network -m 4550 ppp /usr/sbin install: unknown group network .... What should I do ? I have system ver 2.2-STABLE, cvsup running each night... _____________ Lauri Laupmaa mauri@mbp.ee From owner-freebsd-stable Tue Oct 7 07:50:35 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id HAA01085 for stable-outgoing; Tue, 7 Oct 1997 07:50:35 -0700 (PDT) (envelope-from owner-freebsd-stable) Received: from tyree.iii.co.uk (tyree.iii.co.uk [193.117.77.66]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id HAA01078 for ; Tue, 7 Oct 1997 07:50:31 -0700 (PDT) (envelope-from nik@smtphost.iii.co.uk) Received: from carrig.strand.iii.co.uk (carrig.strand.iii.co.uk [192.168.7.25]) by tyree.iii.co.uk (8.8.7/8.8.7) with ESMTP id PAA24440; Tue, 7 Oct 1997 15:47:10 +0100 (BST) Received: (from nik@localhost) by carrig.strand.iii.co.uk (8.8.7/8.8.7) id PAA20796; Tue, 7 Oct 1997 15:52:36 +0100 (BST) Message-ID: <19971007155234.44300@strand.iii.co.uk> Date: Tue, 7 Oct 1997 15:52:34 +0100 From: nik@iii.co.uk To: Superuser Cc: stable@FreeBSD.ORG Subject: Re: error in make world References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.76e In-Reply-To: ; from Superuser on Tue, Oct 07, 1997 at 07:46:17PM +0300 Organization: interactive investor Sender: owner-freebsd-stable@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Tue, Oct 07, 1997 at 07:46:17PM +0300, Superuser wrote: > I'm relatively unexperienced FreeBSD user and for first time tried: > > cd /usr/src > make world As an aside, have you looked at the tutorial at Admittedly, it won't have solved this particular problem. . . > It went a long way, but suddenly bombed out saying: > > install -c -s -o root -g network -m 4550 ppp /usr/sbin > install: unknown group network > .... > > What should I do ? > > I have system ver 2.2-STABLE, cvsup running each night... A new group was added to the group file, and then used as part of the installation. Of course, 'make world' will not install the new group file for you. Run 'diff' on /etc/group and /usr/src/etc/group to see what the differences are. As I recall, you need to add a 'network' group to /etc/group. You can restart the 'make world' with # cd /usr/src; make -DNOCLEAN world which will not wipe out the results of the previous build, or # cd /usr/src; make world if you want to start from the beginning. N -- --+==[ Nik Clayton is Just Another Perl Hacker at Interactive Investor ]==+-- And I'd have gotten away with it too, if it hadn't been for those pesky kids. From owner-freebsd-stable Tue Oct 7 07:52:27 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id HAA01265 for stable-outgoing; Tue, 7 Oct 1997 07:52:27 -0700 (PDT) (envelope-from owner-freebsd-stable) Received: from tyree.iii.co.uk (tyree.iii.co.uk [193.117.77.66]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id HAA01251 for ; Tue, 7 Oct 1997 07:52:23 -0700 (PDT) (envelope-from nik@smtphost.iii.co.uk) Received: from carrig.strand.iii.co.uk (carrig.strand.iii.co.uk [192.168.7.25]) by tyree.iii.co.uk (8.8.7/8.8.7) with ESMTP id PAA24722 for ; Tue, 7 Oct 1997 15:49:08 +0100 (BST) Received: (from nik@localhost) by carrig.strand.iii.co.uk (8.8.7/8.8.7) id PAA20812; Tue, 7 Oct 1997 15:54:33 +0100 (BST) Message-ID: <19971007155431.08874@strand.iii.co.uk> Date: Tue, 7 Oct 1997 15:54:31 +0100 From: nik@iii.co.uk To: stable@freebsd.org Subject: Re: error in make world Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.76e Organization: interactive investor Sender: owner-freebsd-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk D'oh! My last message didn't include the URL I was talking about. Sorry about that: http://www.freebsd.org/tutorials/upgrade/upgrade.html N -- --+==[ Nik Clayton is Just Another Perl Hacker at Interactive Investor ]==+-- And I'd have gotten away with it too, if it hadn't been for those pesky kids. From owner-freebsd-stable Tue Oct 7 08:06:33 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id IAA02188 for stable-outgoing; Tue, 7 Oct 1997 08:06:33 -0700 (PDT) (envelope-from owner-freebsd-stable) Received: from ns.mt.sri.com (SRI-56K-FR.mt.net [206.127.65.42]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id IAA02163; Tue, 7 Oct 1997 08:06:25 -0700 (PDT) (envelope-from nate@rocky.mt.sri.com) Received: from rocky.mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by ns.mt.sri.com (8.8.7/8.8.7) with ESMTP id JAA22678; Tue, 7 Oct 1997 09:04:17 -0600 (MDT) Received: (from nate@localhost) by rocky.mt.sri.com (8.7.5/8.7.3) id JAA05125; Tue, 7 Oct 1997 09:04:15 -0600 (MDT) Date: Tue, 7 Oct 1997 09:04:15 -0600 (MDT) Message-Id: <199710071504.JAA05125@rocky.mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Søren Schmidt Cc: bde@zeta.org.au (Bruce Evans), baum@actcom.co.il, stable@freebsd.org, current@freebsd.org Subject: Re: EXT2FS code from -current to -stable In-Reply-To: <199710071150.NAA03414@sos.freebsd.dk> References: <199710071051.UAA15356@godzilla.zeta.org.au> <199710071150.NAA03414@sos.freebsd.dk> X-Mailer: VM 6.29 under 19.15 XEmacs Lucid Sender: owner-freebsd-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk [ Ext2FS bugs ] > > Now we are talking about ext2fs, what about the version that OpenBSD > has, its GPL free (yeah!), do they have a fix for this. I think that version is from NetBSD originally. I remember someone committing code to NetBSD when I watched that sort of thing. Nate From owner-freebsd-stable Tue Oct 7 08:17:53 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id IAA02770 for stable-outgoing; Tue, 7 Oct 1997 08:17:53 -0700 (PDT) (envelope-from owner-freebsd-stable) Received: from ghpc8.ihf.rwth-aachen.de (ghpc8.ihf.RWTH-Aachen.DE [134.130.90.8]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id IAA02762 for ; Tue, 7 Oct 1997 08:17:45 -0700 (PDT) (envelope-from thomas@ghpc8.ihf.rwth-aachen.de) Received: from ghpc6.ihf.rwth-aachen.de (ghpc6.ihf.rwth-aachen.de [134.130.90.6]) by ghpc8.ihf.rwth-aachen.de (8.8.7/8.8.6) with ESMTP id RAA02201; Tue, 7 Oct 1997 17:17:22 +0200 (CEST) Received: (from thomas@localhost) by ghpc6.ihf.rwth-aachen.de (8.8.7/8.8.5) id RAA17129; Tue, 7 Oct 1997 17:17:21 +0200 (CEST) To: nik@iii.co.uk Cc: Superuser , stable@FreeBSD.ORG Subject: Re: error in make world References: <19971007155234.44300@strand.iii.co.uk> From: Thomas Gellekum Date: 07 Oct 1997 17:17:20 +0200 In-Reply-To: nik@iii.co.uk's message of Tue, 7 Oct 1997 15:52:34 +0100 Message-ID: <87yb45txfj.fsf@ghpc6.ihf.rwth-aachen.de> Lines: 47 X-Mailer: Gnus v5.4.37/XEmacs 19.15 Sender: owner-freebsd-stable@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk nik@iii.co.uk writes: > On Tue, Oct 07, 1997 at 07:46:17PM +0300, Superuser wrote: > > I'm relatively unexperienced FreeBSD user and for first time tried: > > > > cd /usr/src > > make world > > As an aside, have you looked at the tutorial at > > > > Admittedly, it won't have solved this particular problem. . . a secret tutorial > > > It went a long way, but suddenly bombed out saying: > > > > install -c -s -o root -g network -m 4550 ppp /usr/sbin > > install: unknown group network > > .... > > > > What should I do ? > > > > I have system ver 2.2-STABLE, cvsup running each night... > > A new group was added to the group file, and then used as part of the > installation. Of course, 'make world' will not install the new group file > for you. > > Run 'diff' on /etc/group and /usr/src/etc/group to see what the differences > are. As I recall, you need to add a 'network' group to /etc/group. > > You can restart the 'make world' with > > # cd /usr/src; make -DNOCLEAN world > > which will not wipe out the results of the previous build, or > > # cd /usr/src; make world > > if you want to start from the beginning. > > N > -- > --+==[ Nik Clayton is Just Another Perl Hacker at Interactive Investor ]==+-- > And I'd have gotten away with it too, if it hadn't been for those pesky kids. From owner-freebsd-stable Tue Oct 7 08:20:17 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id IAA03006 for stable-outgoing; Tue, 7 Oct 1997 08:20:17 -0700 (PDT) (envelope-from owner-freebsd-stable) Received: from ghpc8.ihf.rwth-aachen.de (ghpc8.ihf.RWTH-Aachen.DE [134.130.90.8]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id IAA02996 for ; Tue, 7 Oct 1997 08:20:14 -0700 (PDT) (envelope-from thomas@ghpc8.ihf.rwth-aachen.de) Received: from ghpc6.ihf.rwth-aachen.de (ghpc6.ihf.rwth-aachen.de [134.130.90.6]) by ghpc8.ihf.rwth-aachen.de (8.8.7/8.8.6) with ESMTP id RAA02211; Tue, 7 Oct 1997 17:20:11 +0200 (CEST) Received: (from thomas@localhost) by ghpc6.ihf.rwth-aachen.de (8.8.7/8.8.5) id RAA17136; Tue, 7 Oct 1997 17:20:10 +0200 (CEST) To: nik@iii.co.uk Cc: Superuser , stable@FreeBSD.ORG Subject: Re: error in make world References: <19971007155234.44300@strand.iii.co.uk> From: Thomas Gellekum Date: 07 Oct 1997 17:20:09 +0200 In-Reply-To: nik@iii.co.uk's message of Tue, 7 Oct 1997 15:52:34 +0100 Message-ID: <87wwjptxau.fsf@ghpc6.ihf.rwth-aachen.de> Lines: 18 X-Mailer: Gnus v5.4.37/XEmacs 19.15 Sender: owner-freebsd-stable@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Whoops, the first one was premature... nik@iii.co.uk writes: > Run 'diff' on /etc/group and /usr/src/etc/group to see what the differences > are. As I recall, you need to add a 'network' group to /etc/group. Yup. > You can restart the 'make world' with > > # cd /usr/src; make -DNOCLEAN world > > which will not wipe out the results of the previous build, or Just `make installworld' will work fine after the network group is defined. tg From owner-freebsd-stable Tue Oct 7 08:22:47 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id IAA03185 for stable-outgoing; Tue, 7 Oct 1997 08:22:47 -0700 (PDT) (envelope-from owner-freebsd-stable) Received: from ios.internet-ireland.ie (ios.internet-ireland.ie [195.17.130.2]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id IAA03176 for ; Tue, 7 Oct 1997 08:22:44 -0700 (PDT) (envelope-from cthulhu@ois.ie) Received: from gate.ois.ie (oisgw.ois.ie [195.17.130.66]) by ios.internet-ireland.ie (8.6.12/8.6.12) with ESMTP id QAA24832 for ; Tue, 7 Oct 1997 16:22:25 +0100 Received: from ithaqua.ois.ie (ithaqua.ois.ie [192.168.0.11]) by gate.ois.ie (8.8.7/8.6.12) with SMTP id PAA19607 for ; Tue, 7 Oct 1997 15:54:37 +0100 (IST) Received: by ithaqua.ois.ie (SMI-8.6/client-1.3) id PAA21554; Tue, 7 Oct 1997 15:54:36 +0100 Date: Tue, 7 Oct 1997 15:54:36 +0100 Message-Id: <199710071454.PAA21554@ithaqua.ois.ie> From: Adrian Colley To: freebsd-stable@FreeBSD.ORG Subject: Re: CVSUP vs. SNAPS In-Reply-To: <199710061505.IAA00297@GndRsh.aac.dev.com> References: <2674.875831475@time.cdrom.com> <199710061505.IAA00297@GndRsh.aac.dev.com> X-Mailer: VM 6.22 under 19.15p7 XEmacs Lucid Mime-Version: 1.0 (generated by tm-edit 7.106) Content-Type: text/plain; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk In his message to freebsd-stable, "Rodney W. Grimes" wrote: r> Looks like 5 to 1 in favor of what I stated, so what, your going r> to pull the Release Engineer Hat out and say NO? Well, if you do r> everytime I have to spend 15 minutes instead of 1 minute to figure r> out what someone is running so I can help them I am going to send r> you an invoice for that time instead of billing my client for it! *plonk* --adrian. (happy to forgo fine-grained release numbers until after 2.2.5) From owner-freebsd-stable Tue Oct 7 08:58:46 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id IAA05915 for stable-outgoing; Tue, 7 Oct 1997 08:58:46 -0700 (PDT) (envelope-from owner-freebsd-stable) Received: from h2o.journey.net (h2o.journey.net [207.227.162.60]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id IAA05907 for ; Tue, 7 Oct 1997 08:58:41 -0700 (PDT) (envelope-from listuser@h2o.journey.net) Received: from localhost (listuser@localhost) by h2o.journey.net (8.8.7/8.8.7) with SMTP id LAA04452; Tue, 7 Oct 1997 11:58:42 -0400 (EDT) Date: Tue, 7 Oct 1997 11:58:42 -0400 (EDT) From: listuser To: mbailey@journey.net cc: stable@FreeBSD.ORG Subject: Kernel panic and reboots in stable.. In-Reply-To: <19971007155234.44300@strand.iii.co.uk> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk I am running stable from last friday night. Did a make world and remade my kernel. The machine is a P5-133 with 96Megs of memory. It has 2 2gig drives and 2 4gig drives to hold our news spool. The machine is ROCK SOLID! until I start running INN from the ports collection and the machine panics and reboots saying something about ifree. The only odd thing that I have done was increase the Inodes on the two 4 gig drives. I think it was -i 256 to newfs.. If I leave INN running like clock work the machine reboots every 15 minutes. If I turn of the machines and run make worlds over and over and over again without an error. Anyone else out there seeing a similar problem. By the way the reboot is so fast that it is very hard to catch the information after the panic. --Matt From owner-freebsd-stable Tue Oct 7 09:10:09 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id JAA06646 for stable-outgoing; Tue, 7 Oct 1997 09:10:09 -0700 (PDT) (envelope-from owner-freebsd-stable) Received: from zerium.idgonline.no (root@oslo-3-4.newmedia.no [194.52.244.68]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id JAA06600; Tue, 7 Oct 1997 09:09:44 -0700 (PDT) (envelope-from hanspb@persbraten.vgs.no) Received: from localhost (hanspbie@zerium.newmedia.no [127.0.0.1]) by zerium.idgonline.no (8.8.7/8.8.5) with SMTP id SAA03338; Tue, 7 Oct 1997 18:09:28 +0200 Date: Tue, 7 Oct 1997 18:09:28 +0200 (MET DST) From: Hans Petter Bieker X-Sender: hanspbie@zerium.newmedia.no To: Superuser cc: stãble@FreeBSD.ORG, stable@FreeBSD.ORG Subject: Re: error in make world In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Tue, 7 Oct 1997, Superuser wrote: > I'm relatively unexperienced FreeBSD user and for first time tried: > > cd /usr/src > make world > > It went a long way, but suddenly bombed out saying: > > install -c -s -o root -g network -m 4550 ppp /usr/sbin > install: unknown group network # grep network /usr/src/etc/group >> /etc/group -- Linux; 64bit, multi-platform, multi-tasking, multi-user, fast and Free. Microsoft Windows 95 - From the makers of EDLIN and FAT drive formatting! "Who needs horror movies when we have Microsoft"? From owner-freebsd-stable Tue Oct 7 09:26:47 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id JAA07897 for stable-outgoing; Tue, 7 Oct 1997 09:26:47 -0700 (PDT) (envelope-from owner-freebsd-stable) Received: from sos.freebsd.dk (sos.freebsd.dk [195.8.129.33]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id JAA07715; Tue, 7 Oct 1997 09:24:35 -0700 (PDT) (envelope-from sos@sos.freebsd.dk) Received: (from sos@localhost) by sos.freebsd.dk (8.8.7/8.7.3) id SAA03948; Tue, 7 Oct 1997 18:23:47 +0200 (MEST) From: Søren Schmidt Message-Id: <199710071623.SAA03948@sos.freebsd.dk> Subject: Re: EXT2FS code from -current to -stable In-Reply-To: <199710071333.XAA21776@godzilla.zeta.org.au> from Bruce Evans at "Oct 7, 97 11:33:59 pm" To: bde@zeta.org.au (Bruce Evans) Date: Tue, 7 Oct 1997 18:23:47 +0200 (MEST) Cc: bde@zeta.org.au, baum@actcom.co.il, current@FreeBSD.ORG, stable@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL30 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-stable@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk In reply to Bruce Evans who wrote: > >Now we are talking about ext2fs, what about the version that OpenBSD > >has, its GPL free (yeah!), do they have a fix for this. > > Do you mean the NetBSD version? :-) It should never have had this bug, Sorry just saw it in OpenBSD (they are kind of the same to me anyways) > since the bug is caused by semantic mismatch between BSD buffer handling > and vestiges of Linux buffer handling in the GPL'ed part (the Linux and > FreeBSD versions of ext2fs want to hang on to buffers for bitmaps, but > BSD wants buffers to be released as soon as possible). > > I was waiting for the Lite2 merge, but that seems to have been done a > few months ago, at least in the NetBSD version. So, should we go for it ?? I might find a couple of spare hours to do it.. -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Søren Schmidt (sos@FreeBSD.org) FreeBSD Core Team Even more code to hack -- will it ever end .. From owner-freebsd-stable Tue Oct 7 09:56:44 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id JAA10395 for stable-outgoing; Tue, 7 Oct 1997 09:56:44 -0700 (PDT) (envelope-from owner-freebsd-stable) Received: from freebie.dcfinc.com (freebie.dcfinc.com [138.113.2.8]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id JAA10390 for ; Tue, 7 Oct 1997 09:56:41 -0700 (PDT) (envelope-from chad@freebie.dcfinc.com) Received: (from chad@localhost) by freebie.dcfinc.com (8.8.3/8.8.3a) id JAA07589; Tue, 7 Oct 1997 09:55:21 -0700 (MST) From: "Chad R. Larson" Message-Id: <199710071655.JAA07589@freebie.dcfinc.com> Subject: Re: Fwd: CVSup release identity To: cdillon@tri-lakes.net (Chris Dillon) Date: Tue, 7 Oct 1997 09:55:20 -0700 (MST) Cc: rkw@dataplex.net, stable@FreeBSD.ORG In-Reply-To: from Chris Dillon at "Oct 6, 97 11:35:57 pm" Reply-to: chad@dcfinc.com 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 X-Loop: FreeBSD.org Precedence: bulk > On 07-Oct-97 Richard Wackerbarth wrote: > >Chris Dillon writes: > >I guess we could do the following: > > > >Before release: > >2.2 (9710061501) > > > >At release: > >2.2.0 (RELEASE) > > > >After release: > >2.2.0 (9710061703) > > > >Another Release: > >2.2.2 (RELEASE) > > > >And then: > >2.2.2 (9710061905) > > > >That way, anything other than a release would have a timestamp and the > >number of the previous release from which it was derived. As someone pointed out, this still doesn't make clear the distinction of a SUP against 2.2-CURRENT and 2.2-STABLE (something my earlier suggestion also failed to do). I'll re-suggest an alpha-numeric counter instead of date/time, both for economy (fewer characters) and to avoid debate about time zones and daylight savings. But I'd add a character that denotes which CVS tag was used to retrieve the sources. Obvious characters would be 'C' (for current), 'R' (for release) and 'S' (for stable). The other 23 characters could (and should) be assigned to any other tags accessable to non-core team members. So, we'd see something like this: 2.2-CAB 2.2-SCD 2.2.5-R -crl -- Chad R. Larson (CRL22) Brother, can you paradigm? 602-953-1392 chad@dcfinc.com chad@anasazi.com crl22@aol.com DCF, Inc. - 14523 North 49th Place, Scottsdale, Arizona 85254 From owner-freebsd-stable Tue Oct 7 13:47:47 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id NAA21943 for stable-outgoing; Tue, 7 Oct 1997 13:47:47 -0700 (PDT) (envelope-from owner-freebsd-stable) Received: from david.siemens.de (david.siemens.de [139.23.36.11]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id NAA21938 for ; Tue, 7 Oct 1997 13:47:39 -0700 (PDT) (envelope-from Andre.Albsmeier@mchp.siemens.de) Received: from salomon.mchp.siemens.de (salomon.siemens.de [139.23.33.13]) by david.siemens.de (8.8.7/8.8.5) with ESMTP id WAA28961 for ; Tue, 7 Oct 1997 22:47:38 +0200 (MDT) Received: from curry.mchp.siemens.de (daemon@curry.mchp.siemens.de [146.180.31.23]) by salomon.mchp.siemens.de (8.8.7/8.8.5) with ESMTP id WAA02088 for ; Tue, 7 Oct 1997 22:47:37 +0200 (MDT) Received: (from daemon@localhost) by curry.mchp.siemens.de (8.8.7/8.8.7) id WAA03797 for ; Tue, 7 Oct 1997 22:47:37 +0200 (MET DST) From: Andre Albsmeier Message-Id: <199710072047.WAA13931@curry.mchp.siemens.de> Subject: Should we increase MSG_BSIZE in 2.2.5? To: freebsd-stable@freebsd.org Date: Tue, 7 Oct 1997 22:47:30 +0200 (CEST) X-Mailer: ELM [version 2.4ME+ PL31 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi, would it be a problem to increase MSG_BSIZE to 16k in msgbuf.h? Since the 2.2-STABLE kernel has got really chatty, especially when booting verbose, it might be a good idea to increase the default in 2.2.5... What do you think? -Andre From owner-freebsd-stable Tue Oct 7 14:03:53 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id OAA22765 for stable-outgoing; Tue, 7 Oct 1997 14:03:53 -0700 (PDT) (envelope-from owner-freebsd-stable) Received: from andrsn.stanford.edu (andrsn.Stanford.EDU [36.33.0.163]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id OAA22760; Tue, 7 Oct 1997 14:03:47 -0700 (PDT) (envelope-from andrsn@andrsn.stanford.edu) Received: from localhost (localhost.stanford.edu [127.0.0.1]) by andrsn.stanford.edu (8.8.7/8.6.12) with SMTP id NAA10847; Tue, 7 Oct 1997 13:54:47 -0700 (PDT) Date: Tue, 7 Oct 1997 13:54:46 -0700 (PDT) From: Annelise Anderson To: Superuser cc: stãble@FreeBSD.ORG, stable@FreeBSD.ORG Subject: Re: error in make world In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Tue, 7 Oct 1997, Superuser wrote: > Hi > > I'm relatively unexperienced FreeBSD user and for first time tried: > > cd /usr/src > make world > > It went a long way, but suddenly bombed out saying: > > install -c -s -o root -g network -m 4550 ppp /usr/sbin > install: unknown group network > .... > > What should I do ? > > I have system ver 2.2-STABLE, cvsup running each night... > > _____________ > Lauri Laupmaa > mauri@mbp.ee > > Add this line to /etc/group: network:*:69: and try it again.... You might want to do, instead of make world, make -DNOCLEAN world which might save quite a lot of time (some of the existing files that have been created won't be deleted). If I've got this wrong I'm sure someone else will correct me... Annelise From owner-freebsd-stable Tue Oct 7 14:30:19 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id OAA24580 for stable-outgoing; Tue, 7 Oct 1997 14:30:19 -0700 (PDT) (envelope-from owner-freebsd-stable) Received: from news1.gtn.com (news1.gtn.com [194.77.0.15]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id OAA24573; Tue, 7 Oct 1997 14:30:10 -0700 (PDT) (envelope-from andreas@klemm.gtn.com) Received: (from uucp@localhost) by news1.gtn.com (8.8.6/8.8.6) with UUCP id WAA00496; Tue, 7 Oct 1997 22:15:25 +0100 (MET) Received: (from andreas@localhost) by klemm.gtn.com (8.8.7/8.8.7) id XAA26384; Tue, 7 Oct 1997 23:10:03 +0200 (CEST) (envelope-from andreas) Message-ID: <19971007231003.14106@klemm.gtn.com> Date: Tue, 7 Oct 1997 23:10:03 +0200 From: Andreas Klemm To: stable@freebsd.org Cc: jkh@freebsd.org Subject: FreeBSD-2.2.5-BETA, /boot.help is missing Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.84 X-Disclaimer: A free society is one where it is safe to be unpopular X-Operating-System: FreeBSD 3.0-CURRENT SMP Sender: owner-freebsd-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I installed the last BETA at work. Good work, looks great ! During boot I noticed, that - /boot.help is missing And it would be great if someone chooses the graphical XFree86 config tool, that the VGA16 server will be included automatically. I always forget to install the ***** VGA16 server ;-) Then: someone other who has problems to use the PS/2 mouse ? 'though it works for me in Win95 (so hardware and IRQ 12 are ok), I can't get it running with XFree ... PS/2 doesn't seem to be configured ... /dev/psm0 exists with crw------- ... I'll try to take a closer look tomorrow... Andreas /// -- Andreas Klemm powered by ,,symmetric multiprocessor FreeBSD'' andreas@klemm.gtn.com - http://www.freebsd.org/~fsmp/SMP/SMP.html andreas@FreeBSD.ORG - http://www.freebsd.org/~fsmp/SMP/benches.html From owner-freebsd-stable Tue Oct 7 15:49:46 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id PAA29368 for stable-outgoing; Tue, 7 Oct 1997 15:49:46 -0700 (PDT) (envelope-from owner-freebsd-stable) Received: from dyson.iquest.net (dyson.iquest.net [198.70.144.127]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id PAA29359; Tue, 7 Oct 1997 15:49:38 -0700 (PDT) (envelope-from toor@dyson.iquest.net) Received: (from root@localhost) by dyson.iquest.net (8.8.6/8.8.5) id RAA02150; Tue, 7 Oct 1997 17:48:51 -0500 (EST) From: "John S. Dyson" Message-Id: <199710072248.RAA02150@dyson.iquest.net> Subject: Re: EXT2FS code from -current to -stable In-Reply-To: <199710071623.SAA03948@sos.freebsd.dk> from =?ISO-8859-1?Q?S=F8ren_Schmidt?= at "Oct 7, 97 06:23:47 pm" To: sos@sos.freebsd.dk (Søren Schmidt) Date: Tue, 7 Oct 1997 17:48:51 -0500 (EST) Cc: bde@zeta.org.au, baum@actcom.co.il, current@FreeBSD.ORG, stable@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL31 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-stable@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Søren Schmidt said: > > > > I was waiting for the Lite2 merge, but that seems to have been done a > > few months ago, at least in the NetBSD version. > > So, should we go for it ?? I might find a couple of spare hours to do it.. > > Yes!!! :-). -- John dyson@freebsd.org jdyson@nc.com From owner-freebsd-stable Tue Oct 7 16:20:06 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id QAA01339 for stable-outgoing; Tue, 7 Oct 1997 16:20:06 -0700 (PDT) (envelope-from owner-freebsd-stable) Received: from ptway.com (apollo.ptway.com [199.176.148.3]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id QAA01253 for ; Tue, 7 Oct 1997 16:19:57 -0700 (PDT) (envelope-from haskin@ptway.com) Received: from brianjr.haskin.org (209R1.ptway.com [199.176.148.76]) by ptway.com (8.7.1/3.4W4-PTWAY-sco-ODT3.0) with ESMTP id TAA07711; Tue, 7 Oct 1997 19:11:16 -0400 (EDT) Message-ID: <343AC343.4F346DEF@ptway.com> Date: Tue, 07 Oct 1997 19:18:27 -0400 From: Brian Haskin X-Mailer: Mozilla 4.01 [en] (Win95; I) MIME-Version: 1.0 To: Andreas Klemm CC: stable Subject: Re: FreeBSD-2.2.5-BETA, /boot.help is missing X-Priority: 3 (Normal) References: <19971007231003.14106@klemm.gtn.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Andreas Klemm wrote: > [snip] > Then: someone other who has problems to use the PS/2 mouse ? > 'though it works for me in Win95 (so hardware and IRQ 12 are ok), > I can't get it running with XFree ... PS/2 doesn't seem to be > configured ... /dev/psm0 exists with crw------- ... > > I'll try to take a closer look tomorrow... > > Andreas /// > [snip] Do you have this configured and enabled in the kernel (in the generic kernel by default it's disabled). Brian Haskin From owner-freebsd-stable Tue Oct 7 17:17:40 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id RAA04384 for stable-outgoing; Tue, 7 Oct 1997 17:17:40 -0700 (PDT) (envelope-from owner-freebsd-stable) Received: from fly.HiWAAY.net (root@fly.HiWAAY.net [208.147.154.56]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id RAA04379 for ; Tue, 7 Oct 1997 17:17:37 -0700 (PDT) (envelope-from dkelly@nospam.hiwaay.net) Received: from nospam.hiwaay.net (max19-204.HiWAAY.net [208.147.146.204]) by fly.HiWAAY.net (8.8.7/8.8.6) with ESMTP id TAA14684 for ; Tue, 7 Oct 1997 19:17:26 -0500 (CDT) Received: from localhost (localhost [127.0.0.1]) by nospam.hiwaay.net (8.8.7/8.8.4) with ESMTP id TAA04520 for ; Tue, 7 Oct 1997 19:09:37 -0500 (CDT) Message-Id: <199710080009.TAA04520@nospam.hiwaay.net> X-Mailer: exmh version 2.0zeta 7/24/97 To: freebsd-stable@FreeBSD.ORG Subject: pppd version in 2.2.5? From: dkelly@HiWAAY.net Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 07 Oct 1997 19:09:37 -0500 Sender: owner-freebsd-stable@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Discussions with Greg Lehey about pppd indicate -current has a kernel pppd that does automatic on-demand dialing and idle disconnect much like user-ppp. Is this supposed to be in 2.2.5 too? Am I holding my tongue wrong when I cvsup using "*default release=cvs tag=RELENG_2_2" (that's only part of my cvsup config). The only way I've found to determine pppd's version was to run it and read /var/log/messages: Oct 7 17:20:00 nospam pppd[3215]: pppd 2.2.0 started by dkelly, uid 928 And this is uname -a: FreeBSD nospam.hiwaay.net 2.2-STABLE FreeBSD 2.2-STABLE #0: Mon Oct 6 21:00:32 CDT 1997 root@nospam.hiwaay.net:/usr/src/sys/compile/PPRO166 i386 -- David Kelly N4HHE, dkelly@hiwaay.net ===================================================================== The human mind ordinarily operates at only ten percent of its capacity -- the rest is overhead for the operating system. From owner-freebsd-stable Tue Oct 7 17:32:39 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id RAA05091 for stable-outgoing; Tue, 7 Oct 1997 17:32:39 -0700 (PDT) (envelope-from owner-freebsd-stable) Received: from time.cdrom.com (time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id RAA05083; Tue, 7 Oct 1997 17:32:34 -0700 (PDT) (envelope-from jkh@time.cdrom.com) Received: from time.cdrom.com (localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.7/8.6.9) with ESMTP id RAA21435; Tue, 7 Oct 1997 17:31:45 -0700 (PDT) To: Andreas Klemm cc: stable@freebsd.org, jkh@freebsd.org Subject: Re: FreeBSD-2.2.5-BETA, /boot.help is missing In-reply-to: Your message of "Tue, 07 Oct 1997 23:10:03 +0200." <19971007231003.14106@klemm.gtn.com> Date: Tue, 07 Oct 1997 17:31:44 -0700 Message-ID: <21431.876270704@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > During boot I noticed, that > > - /boot.help is missing Already fixed. :) > And it would be great if someone chooses the graphical > XFree86 config tool, that the VGA16 server will be > included automatically. Hmmmm. I could add such a check. > Then: someone other who has problems to use the PS/2 mouse ? > 'though it works for me in Win95 (so hardware and IRQ 12 are ok), > I can't get it running with XFree ... PS/2 doesn't seem to be > configured ... /dev/psm0 exists with crw------- ... Hmmm - mine works fine! Jordan From owner-freebsd-stable Tue Oct 7 19:12:02 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id TAA09592 for stable-outgoing; Tue, 7 Oct 1997 19:12:02 -0700 (PDT) (envelope-from owner-freebsd-stable) Received: from hobbes.saturn-tech.com (drussell@drussell.internode.net [198.161.228.154]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id TAA09563 for ; Tue, 7 Oct 1997 19:11:58 -0700 (PDT) (envelope-from drussell@saturn-tech.com) Received: from localhost (drussell@localhost) by hobbes.saturn-tech.com (8.8.4/8.8.2) with SMTP id UAA18215; Tue, 7 Oct 1997 20:11:04 -0600 (MDT) Date: Tue, 7 Oct 1997 20:11:04 -0600 (MDT) From: Doug Russell To: "Rodney W. Grimes" cc: imp@village.org, dg@root.com, jkh@time.cdrom.com, andrsn@andrsn.stanford.edu, freebsd-stable@FreeBSD.ORG Subject: Re: CVSUP vs. SNAPS In-Reply-To: <199710061510.IAA00329@GndRsh.aac.dev.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Mon, 6 Oct 1997, Rodney W. Grimes wrote: > > > *PLEASE*PLEASE*PLEASE* listen to Rod. The kernels after 2.2.5-RELEASE > > > should be called 2.2.5-STABLE. > > > > Or we could always call it 2.2.x-STABLE, to indicate that it is the most > > recent of the 2.2 branch (which is therefore, the 2.2.x branch...) > > Won't do you any good, you wont know if your post 2.2.1, 2.2.2, 2.2.5, > kinda defeats the purpose of REVISION :-(. True, but it fixes the origional problem of user CONFUSION... (2.2 vs 2.2.0 problem...) You'd have to tack a revision on there somewhere to fix the problem of "exactly what revision IS this system anyway?" FreeBSD 2.2.x-STABLE (rrrrr) r = some revision identification scheme Later...... From owner-freebsd-stable Tue Oct 7 19:56:12 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id TAA12500 for stable-outgoing; Tue, 7 Oct 1997 19:56:12 -0700 (PDT) (envelope-from owner-freebsd-stable) Received: from rif.kconline.com (rif.kconline.com [207.51.167.9]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id TAA12493 for ; Tue, 7 Oct 1997 19:56:08 -0700 (PDT) (envelope-from rif@rif.kconline.com) Received: from localhost (rif@localhost) by rif.kconline.com (8.8.7/8.8.6) with SMTP id VAA17611 for ; Tue, 7 Oct 1997 21:56:04 -0500 (EST) Date: Tue, 7 Oct 1997 21:56:03 -0500 (EST) From: Jim Riffle To: freebsd-stable@freebsd.org Subject: Trobles with limits Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I recently upgraded a couple of my 2.2-Stable servers to 2.2.5-Beta and appear to be having troubles with maximum open files/processes. Sunday evening is when I cvsuped the source tree and made world. Both servers I upgraded are having serious problems when a lot of files or processes are open. My news server runs innd, which will die shortly after starting. This isn't too serious however, because restarting innd will make that machine happy. My web server, on the other hand, has big problems. Upon startup, everything will start and run okay until there are about 35 httpd processes. Once that happens, the cgi-bin programs will not work with errors that it cannot fork, fingerd will not fork (running with -p and a custom program), and after a while, named will die reporting too many open files. This sounds like it is a simple problem of needing to add CHILD_MAX and OPEN_MAX into my kernel config, however that doesn't seem to help. I had both of those set to 128 previously, and set them all the way to 512 to see if the problem would go away. I can get everything working and forking by starting everything over again from the shell, however every few hours during the busy times, the machine will spratically reboot (behavior I expect is a result of hitting a limit, which I can't seem to raise). I did have a old kernel around which was from about 2 months ago. I rebooted to that kernel, and the problem still persisted. So, it doesn't appear like the kernel is the problem (This kernel I ran problem free for months previous to upgrading). Anyone have any suggestions for me to try? Thanks, Jim From owner-freebsd-stable Tue Oct 7 20:21:39 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id UAA14033 for stable-outgoing; Tue, 7 Oct 1997 20:21:39 -0700 (PDT) (envelope-from owner-freebsd-stable) Received: from bob.tri-lakes.net ([207.3.81.6]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id UAA14027 for ; Tue, 7 Oct 1997 20:21:30 -0700 (PDT) (envelope-from cdillon@tri-lakes.net) Received: from [207.3.81.130] by bob.tri-lakes.net (NTMail 3.02.13) with ESMTP id sa292960 for ; Tue, 7 Oct 1997 22:21:34 -0500 Message-ID: X-Mailer: XFMail 1.1 [p0] on FreeBSD Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit MIME-Version: 1.0 In-Reply-To: <199710071655.JAA07589@freebie.dcfinc.com> Date: Tue, 07 Oct 1997 22:05:13 -0000 (GMT) From: Chris Dillon To: chad@dcfinc.com Subject: Re: Fwd: CVSup release identity Cc: stable@FreeBSD.ORG Sender: owner-freebsd-stable@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On 07-Oct-97 Chad R. Larson wrote: >> On 07-Oct-97 Richard Wackerbarth wrote: >> >Chris Dillon writes: Actually, Richard Wackerbarth wrote the following, not me. >> >I guess we could do the following: >> > >> >Before release: >> >2.2 (9710061501) >> > >> >At release: >> >2.2.0 (RELEASE) >> > >> >After release: >> >2.2.0 (9710061703) >> > >> >Another Release: >> >2.2.2 (RELEASE) >> > >> >And then: >> >2.2.2 (9710061905) >> > >> >That way, anything other than a release would have a timestamp and the >> >number of the previous release from which it was derived. > >As someone pointed out, this still doesn't make clear the distinction of >a >SUP against 2.2-CURRENT and 2.2-STABLE (something my earlier suggestion >also failed to do). 2.2-CURRENT? Thats a new branch to me... Unless you are speaking hypothetically of a branch which has not yet had its first release, which in that case, is still taken into account by the above example. >I'll re-suggest an alpha-numeric counter instead of date/time, both for >economy (fewer characters) and to avoid debate about time zones and >daylight savings. But I'd add a character that denotes which CVS tag >was used to retrieve the sources. Obvious characters would be 'C' (for >current), 'R' (for release) and 'S' (for stable). The other 23 >characters could (and should) be assigned to any other tags accessable >to non-core team members. What better alphanumeric incremented counter than time itself? Sure, its a few more numbers, but it is constantly being incremented, is pretty fine-grained, and much more informational. And time-zones aren't a problem when its the server supplying the timestamp, not the client. >So, we'd see something like this: > >2.2-CAB >2.2-SCD >2.2.5-R > > -crl It'd work, but... think of all the nasty letter combinations that will crop up. :-) Not to mention that the letter-combinations will be eventually recycled, possibly causing more confusion. It would take a century for the current two-digit-year timestamps to recycle. Make it a standard four-digit year and we won't have to worry about changing it again until the year 10000. :-) --- Chris Dillon --- cdillon@tri-lakes.net --- Powered by FreeBSD, the best free OS on the planet ---- (http://www.freebsd.org) From owner-freebsd-stable Tue Oct 7 20:37:17 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id UAA14925 for stable-outgoing; Tue, 7 Oct 1997 20:37:17 -0700 (PDT) (envelope-from owner-freebsd-stable) Received: from mail.wintek.com (mail.wintek.com [199.233.104.76]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id UAA14871; Tue, 7 Oct 1997 20:36:39 -0700 (PDT) (envelope-from csg@wintek.com) Received: from mail.wintek.com (localhost.wintek.com [127.0.0.1]) by mail.wintek.com (8.8.7/1.34wintek(3.6davy)) with ESMTP id DAA02328; Wed, 8 Oct 1997 03:36:37 GMT Message-Id: <199710080336.DAA02328@mail.wintek.com> To: freebsd-stable@freebsd.org cc: julian@freebsd.org Subject: Netatalk problems with 2.2.5-BETA? Date: Tue, 07 Oct 1997 22:36:37 -0500 From: "C. Stephen Gunn" Sender: owner-freebsd-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Are there any known problem with netatalk and 2.2.5-BETA? I just tried to bring up 1.4b2 from the ports to no avail. I also tried applying the patches available for 3.0-CURRENT which didn't work either. - Steve From owner-freebsd-stable Tue Oct 7 21:18:14 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id VAA16782 for stable-outgoing; Tue, 7 Oct 1997 21:18:14 -0700 (PDT) (envelope-from owner-freebsd-stable) Received: from mx2.cso.uiuc.edu (mx2.cso.uiuc.edu [128.174.5.23]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id VAA16769 for ; Tue, 7 Oct 1997 21:16:55 -0700 (PDT) (envelope-from igor@alecto.physics.uiuc.edu) Received: from alecto.physics.uiuc.edu (alecto.physics.uiuc.edu [128.174.83.167]) by mx2.cso.uiuc.edu (8.8.7/8.8.7) with SMTP id XAA20235 for <@mailhost.uiuc.edu:freebsd-stable@FreeBSD.ORG>; Tue, 7 Oct 1997 23:16:18 -0500 (CDT) Received: by alecto.physics.uiuc.edu (940816.SGI.8.6.9/940406.SGI) id XAA21020; Tue, 7 Oct 1997 23:04:01 -0500 From: igor@alecto.physics.uiuc.edu (Igor Roshchin) Message-Id: <199710080404.XAA21020@alecto.physics.uiuc.edu> Subject: Re: Trobles with limits To: rif@rif.kconline.com (Jim Riffle) Date: Tue, 7 Oct 1997 23:04:01 -0500 (CDT) Cc: freebsd-stable@FreeBSD.ORG In-Reply-To: from "Jim Riffle" at Oct 7, 97 09:56:03 pm X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-freebsd-stable@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > > I recently upgraded a couple of my 2.2-Stable servers to 2.2.5-Beta and > appear to be having troubles with maximum open files/processes. Sunday > evening is when I cvsuped the source tree and made world. > <..> I wonder, is not it better to increase the default maxusers which is currently set to be 10 (unless that was change just recently). All people I know, who have their computers on the network as any type of servers (ftp/httpd/...) reconfigure that number to a bigger one (I set it 32, but it can be smaller). Otherwise one gets the message that the limit of opened files is reached. (It is possible to change the formulae the values are calculated from the maxusers, but it doesn't seem to be reasonable) IgoR From owner-freebsd-stable Tue Oct 7 21:19:51 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id VAA16879 for stable-outgoing; Tue, 7 Oct 1997 21:19:51 -0700 (PDT) (envelope-from owner-freebsd-stable) Received: from biceps.gymnet.com (qmailr@biceps.gymnet.com [204.216.82.50]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id VAA16874 for ; Tue, 7 Oct 1997 21:19:47 -0700 (PDT) (envelope-from rwl@gymnet.com) Received: (qmail 22433 invoked from network); 8 Oct 1997 04:20:17 -0000 Received: from triceps.gymnet.com (HELO mail.gymnet.com) (204.216.82.51) by biceps.gymnet.com with SMTP; 8 Oct 1997 04:20:17 -0000 Date: Tue, 7 Oct 1997 21:19:33 -0800 From: Robert Luce X-Mailer: The Bat! (v1.00.95 Beta) Registered to Robert Luce Reply-To: Robert Luce Organization: Gymnet Communications Priority: Normal Message-ID: <5888.971007@gymnet.com> To: freebsd-stable@freebsd.org Subject: can't compile beta Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I cvsupped the latest source (tag=RELENG_2_2) 10/7/97 21:00 PDT and am getting the following compile error in the 2940UW support code: make -f ../../dev/aic7xxx/Makefile MAKESRCPATH=../../dev/aic7xxx Warning: Object directory not changed from original /usr/src/sys/compile/BICEPS yacc -d ../../dev/aic7xxx/aicasm_gram.y mv y.tab.c aicasm_gram.c cc -O -I. -c aicasm_gram.c lex -t ../../dev/aic7xxx/aicasm_scan.l > aicasm_scan.c cc -O -I. -c aicasm_scan.c ../../dev/aic7xxx/aicasm_scan.l: In function `yylex': ../../dev/aic7xxx/aicasm_scan.l:68: `T_DOWNLOAD' undeclared (first use this func tion) ../../dev/aic7xxx/aicasm_scan.l:68: (Each undeclared identifier is reported only once ../../dev/aic7xxx/aicasm_scan.l:68: for each function it appears in.) *** Error code 1 Stop. *** Error code 1 Stop. ---- Bob Luce "Il faut supporter deux ou trois chenilles System/News Administrator si on veut connaître les papillons.." - Antoine de Saint-Exupéry Finger rwl@gymnet.com for PGP Public Key Block From owner-freebsd-stable Tue Oct 7 23:31:00 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id XAA24331 for stable-outgoing; Tue, 7 Oct 1997 23:31:00 -0700 (PDT) (envelope-from owner-freebsd-stable) Received: from news1.gtn.com (news1.gtn.com [192.109.159.3]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id XAA24296 for ; Tue, 7 Oct 1997 23:30:40 -0700 (PDT) (envelope-from andreas@klemm.gtn.com) Received: (from uucp@localhost) by news1.gtn.com (8.8.6/8.8.6) with UUCP id HAA17902; Wed, 8 Oct 1997 07:15:44 +0100 (MET) Received: (from andreas@localhost) by klemm.gtn.com (8.8.7/8.8.7) id HAA22081; Wed, 8 Oct 1997 07:57:12 +0200 (CEST) (envelope-from andreas) Message-ID: <19971008075711.06995@klemm.gtn.com> Date: Wed, 8 Oct 1997 07:57:11 +0200 From: Andreas Klemm To: "Jordan K. Hubbard" Cc: stable@freebsd.org Subject: Re: FreeBSD-2.2.5-BETA, /boot.help is missing References: <19971007231003.14106@klemm.gtn.com> <21431.876270704@time.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.84 In-Reply-To: <21431.876270704@time.cdrom.com>; from Jordan K. Hubbard on Tue, Oct 07, 1997 at 05:31:44PM -0700 X-Disclaimer: A free society is one where it is safe to be unpopular X-Operating-System: FreeBSD 3.0-CURRENT SMP Sender: owner-freebsd-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Tue, Oct 07, 1997 at 05:31:44PM -0700, Jordan K. Hubbard wrote: > > During boot I noticed, that > > > > - /boot.help is missing > > Already fixed. :) Saw that at home, when browsing commit messages, thanks ;-) > > And it would be great if someone chooses the graphical > > XFree86 config tool, that the VGA16 server will be > > included automatically. > > Hmmmm. I could add such a check. Great ;-) > > Then: someone other who has problems to use the PS/2 mouse ? > > 'though it works for me in Win95 (so hardware and IRQ 12 are ok), > > I can't get it running with XFree ... PS/2 doesn't seem to be > > configured ... /dev/psm0 exists with crw------- ... > > Hmmm - mine works fine! Hmm, I'll take a close look at the boot messages ... Andreas /// -- Andreas Klemm powered by ,,symmetric multiprocessor FreeBSD'' andreas@klemm.gtn.com - http://www.freebsd.org/~fsmp/SMP/SMP.html andreas@FreeBSD.ORG - http://www.freebsd.org/~fsmp/SMP/benches.html From owner-freebsd-stable Tue Oct 7 23:31:23 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id XAA24386 for stable-outgoing; Tue, 7 Oct 1997 23:31:23 -0700 (PDT) (envelope-from owner-freebsd-stable) Received: from news1.gtn.com (news1.gtn.com [192.109.159.3]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id XAA24367 for ; Tue, 7 Oct 1997 23:31:15 -0700 (PDT) (envelope-from andreas@klemm.gtn.com) Received: (from uucp@localhost) by news1.gtn.com (8.8.6/8.8.6) with UUCP id HAA17802; Wed, 8 Oct 1997 07:15:37 +0100 (MET) Received: (from andreas@localhost) by klemm.gtn.com (8.8.7/8.8.7) id HAA22072; Wed, 8 Oct 1997 07:55:47 +0200 (CEST) (envelope-from andreas) Message-ID: <19971008075547.51045@klemm.gtn.com> Date: Wed, 8 Oct 1997 07:55:47 +0200 From: Andreas Klemm To: Brian Haskin Cc: stable Subject: Re: FreeBSD-2.2.5-BETA, /boot.help is missing References: <19971007231003.14106@klemm.gtn.com> <343AC343.4F346DEF@ptway.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.84 In-Reply-To: <343AC343.4F346DEF@ptway.com>; from Brian Haskin on Tue, Oct 07, 1997 at 07:18:27PM -0400 X-Disclaimer: A free society is one where it is safe to be unpopular X-Operating-System: FreeBSD 3.0-CURRENT SMP Sender: owner-freebsd-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Tue, Oct 07, 1997 at 07:18:27PM -0400, Brian Haskin wrote: > Andreas Klemm wrote: > > > [snip] > > Then: someone other who has problems to use the PS/2 mouse ? > > 'though it works for me in Win95 (so hardware and IRQ 12 are ok), > > I can't get it running with XFree ... PS/2 doesn't seem to be > > configured ... /dev/psm0 exists with crw------- ... > > > > I'll try to take a closer look tomorrow... > > > > Andreas /// > > > [snip] > > Do you have this configured and enabled in the kernel (in the generic > kernel by default it's disabled). That was true in the past. cvsup, checkout and see: GENERIC: device psm0 at isa? disable port "IO_KBD" conflicts tty irq 12 vecto r psmintr And yes, I also build a custom kernel. Andreas /// -- Andreas Klemm powered by ,,symmetric multiprocessor FreeBSD'' andreas@klemm.gtn.com - http://www.freebsd.org/~fsmp/SMP/SMP.html andreas@FreeBSD.ORG - http://www.freebsd.org/~fsmp/SMP/benches.html From owner-freebsd-stable Tue Oct 7 23:54:48 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id XAA25856 for stable-outgoing; Tue, 7 Oct 1997 23:54:48 -0700 (PDT) (envelope-from owner-freebsd-stable) Received: from silvia.HIP.Berkeley.EDU (ala-ca9-32.ix.netcom.com [207.93.143.96]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id XAA25851 for ; Tue, 7 Oct 1997 23:54:44 -0700 (PDT) (envelope-from asami@vader.cs.berkeley.edu) Received: (from asami@localhost) by silvia.HIP.Berkeley.EDU (8.8.7/8.6.9) id XAA05940; Tue, 7 Oct 1997 23:54:41 -0700 (PDT) Date: Tue, 7 Oct 1997 23:54:41 -0700 (PDT) Message-Id: <199710080654.XAA05940@silvia.HIP.Berkeley.EDU> To: stable@freebsd.org Subject: NFS server panic with latest -stable From: asami@cs.berkeley.edu (Satoshi Asami) Sender: owner-freebsd-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Here's another one. Kernel and world was built from yesterday (Monday)'s 2.2-stable sources. Network card is SMC 9332DST, this is the first time I saw "tulip_*" show up in the crashdump. Satoshi ------- ## echo bt | gdb -k kernel.8 vmcore.8 GDB is free software and you are welcome to distribute copies of it under certain conditions; type "show copying" to see the conditions. There is absolutely no warranty for GDB; type "show warranty" for details. GDB 4.16 (i386-unknown-freebsd), Copyright 1996 Free Software Foundation, Inc...(no debugging symbols found)... IdlePTD 205000 current pcb at 1e8ca0 panic: page fault #0 0xf0115103 in boot () (kgdb) #0 0xf0115103 in boot () #1 0xf01153c2 in panic () #2 0xf01be3b6 in trap_fatal () #3 0xf01bdea4 in trap_pfault () #4 0xf01bdb7f in trap () #5 0xf018aa7f in tulip_rx_intr () #6 0xf018b042 in tulip_intr_handler () #7 0xf018b105 in tulip_intr_normal () #8 0xf018e77d in pci_int () #9 0xf01b6c0a in vec10 () #10 0xf012fbe3 in biowait () #11 0xf012df9f in bread () #12 0xf019c96f in ffs_update () #13 0xf019ffd0 in ffs_fsync () #14 0xf019ec30 in ffs_sync () #15 0xf0134ee7 in sync () #16 0xf0114fcd in boot () #17 0xf01153c2 in panic () #18 0xf01be3b6 in trap_fatal () #19 0xf01bdea4 in trap_pfault () #20 0xf01bdb7f in trap () #21 0xf015cd67 in nfsrv_read () #22 0xf0174cc0 in nfssvc_nfsd () #23 0xf0174428 in nfssvc () #24 0xf01be5f3 in syscall () #25 0x2945 in ?? () Cannot access memory at address 0xefbfde50. From owner-freebsd-stable Wed Oct 8 00:16:22 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id AAA27356 for stable-outgoing; Wed, 8 Oct 1997 00:16:22 -0700 (PDT) (envelope-from owner-freebsd-stable) Received: from news1.gtn.com (news1.gtn.com [192.109.159.3]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id AAA27329 for ; Wed, 8 Oct 1997 00:16:09 -0700 (PDT) (envelope-from andreas@klemm.gtn.com) Received: (from uucp@localhost) by news1.gtn.com (8.8.6/8.8.6) with UUCP id IAA28210; Wed, 8 Oct 1997 08:00:27 +0100 (MET) Received: (from andreas@localhost) by klemm.gtn.com (8.8.7/8.8.7) id IAA23792; Wed, 8 Oct 1997 08:50:12 +0200 (CEST) (envelope-from andreas) Message-ID: <19971008085012.51101@klemm.gtn.com> Date: Wed, 8 Oct 1997 08:50:12 +0200 From: Andreas Klemm To: Robert Sowders Cc: stable@FreeBSD.ORG Subject: Re: FreeBSD-2.2.5-BETA, /boot.help is missing -Reply References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.84 In-Reply-To: ; from Robert Sowders on Tue, Oct 07, 1997 at 11:43:21PM -0700 X-Disclaimer: A free society is one where it is safe to be unpopular X-Operating-System: FreeBSD 3.0-CURRENT SMP Sender: owner-freebsd-stable@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Tue, Oct 07, 1997 at 11:43:21PM -0700, Robert Sowders wrote: > after boot run dmesg and see if psm0 is disabled. > if it is, look in your kernel source and remove the line disable from > the device psm0 line. then remake your kernel and reboot. > it should be there now at /dev/psm0. > kernel source at /usr/src/sys/i386/conf If that should be the case, could we then remove the disable token entirely ? Or is disable necessary to be able to disable the driver when autoprobing wasn't successfull ? -- Andreas Klemm powered by ,,symmetric multiprocessor FreeBSD'' andreas@klemm.gtn.com - http://www.freebsd.org/~fsmp/SMP/SMP.html andreas@FreeBSD.ORG - http://www.freebsd.org/~fsmp/SMP/benches.html From owner-freebsd-stable Wed Oct 8 01:00:26 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id BAA00925 for stable-outgoing; Wed, 8 Oct 1997 01:00:26 -0700 (PDT) (envelope-from owner-freebsd-stable) Received: from helium.vapornet.com (root@helium.vapornet.com [208.202.126.112]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id BAA00915 for ; Wed, 8 Oct 1997 01:00:16 -0700 (PDT) (envelope-from john@helium.vapornet.com) Received: from argon.vapornet.com (vapornet.xnet.com [205.243.141.107]) by helium.vapornet.com (8.8.7/VaporServer-v3.0+SpamNot) with ESMTP id DAA06411; Wed, 8 Oct 1997 03:00:14 -0500 (CDT) Received: by argon.vapornet.com (8.8.7/VaporClient-1.1) id DAA05325; Wed, 8 Oct 1997 03:00:12 -0500 (CDT) Date: Wed, 8 Oct 1997 03:00:12 -0500 (CDT) Message-Id: <199710080800.DAA05325@argon.vapornet.com> From: John Preisler MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: "C. Stephen Gunn" Cc: freebsd-stable@FreeBSD.ORG Subject: Netatalk problems with 2.2.5-BETA? In-Reply-To: <199710080336.DAA02328@mail.wintek.com> References: <199710080336.DAA02328@mail.wintek.com> X-Mailer: VM 6.22 under 19.15 XEmacs Lucid Sender: owner-freebsd-stable@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk the latest build magically broke netatalk so i did a send-pr on it but have heard nothing back. netatalk is definately broked for now in the 2.2 tree. -jrp C. Stephen Gunn writes: > > Are there any known problem with netatalk and 2.2.5-BETA? I just tried > to bring up 1.4b2 from the ports to no avail. I also tried applying > the patches available for 3.0-CURRENT which didn't work either. > > - Steve > From owner-freebsd-stable Wed Oct 8 01:05:01 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id BAA01377 for stable-outgoing; Wed, 8 Oct 1997 01:05:01 -0700 (PDT) (envelope-from owner-freebsd-stable) Received: from shrimp.dataplex.net (shrimp.dataplex.net [208.2.87.3]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id BAA01360 for ; Wed, 8 Oct 1997 01:04:55 -0700 (PDT) (envelope-from rkw@dataplex.net) Received: from [208.2.87.4] (user4.dataplex.net [208.2.87.4]) by shrimp.dataplex.net (8.8.5/8.8.5) with ESMTP id DAA15614; Wed, 8 Oct 1997 03:04:46 -0500 (CDT) X-Sender: rkw@mail.dataplex.net Message-Id: In-Reply-To: References: <199710071655.JAA07589@freebie.dcfinc.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Wed, 8 Oct 1997 03:01:12 -0500 To: Chris Dillon From: Richard Wackerbarth Subject: Re: Fwd: CVSup release identity Cc: chad@dcfinc.com, stable@FreeBSD.ORG Sender: owner-freebsd-stable@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk At 5:05 PM -0500 10/7/97, Chris Dillon wrote: >2.2-CURRENT? Thats a new branch to me... Unless you are speaking >hypothetically of a branch which has not yet had its first release, which >in that case, is still taken into account by the above example. NO. I am speaking posthumorously (sp?). 2.2-CURRENT was around back in the days when 2.1 was the "stable" branch and before 2.2.0 was released. >What better alphanumeric incremented counter than time itself? I agree. Encoding the time in some scheme to save a few characters is counterproductive. Use a scheme where the meaning is easy for humans. Besides, we save enough characters by dropping "-STABLE" to make up most of the difference. Richard Wackerbarth From owner-freebsd-stable Wed Oct 8 01:21:59 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id BAA02598 for stable-outgoing; Wed, 8 Oct 1997 01:21:59 -0700 (PDT) (envelope-from owner-freebsd-stable) Received: from silvia.HIP.Berkeley.EDU (ala-ca9-32.ix.netcom.com [207.93.143.96]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id BAA02591 for ; Wed, 8 Oct 1997 01:21:54 -0700 (PDT) (envelope-from asami@vader.cs.berkeley.edu) Received: (from asami@localhost) by silvia.HIP.Berkeley.EDU (8.8.7/8.6.9) id BAA06497; Wed, 8 Oct 1997 01:19:19 -0700 (PDT) Date: Wed, 8 Oct 1997 01:19:19 -0700 (PDT) Message-Id: <199710080819.BAA06497@silvia.HIP.Berkeley.EDU> To: obrien@NUXI.COM CC: stable@freebsd.org In-reply-to: <19971005182200.43771@dragon.nuxi.com> (obrien@NUXI.COM) Subject: Re: problem with packages-2.2.5/All/fetchmail-* From: asami@cs.berkeley.edu (Satoshi Asami) Sender: owner-freebsd-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk * I just installed the Oct 4th beta from releng22. * After installing fetchmail-4.2.8, I find that it wants * ``libopie.so.2.0'', which isn't on the system I just installed. Hmm. You're right, libopie is missing in 2.2-stable's lib/Makefile. Can someone add it? Satoshi From owner-freebsd-stable Wed Oct 8 01:39:35 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id BAA03455 for stable-outgoing; Wed, 8 Oct 1997 01:39:35 -0700 (PDT) (envelope-from owner-freebsd-stable) Received: from word.smith.net.au (vh1.gsoft.com.au [203.38.152.122]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id BAA03449 for ; Wed, 8 Oct 1997 01:39:31 -0700 (PDT) (envelope-from mike@word.smith.net.au) Received: from word.smith.net.au (localhost.gsoft.com.au [127.0.0.1]) by word.smith.net.au (8.8.7/8.8.5) with ESMTP id SAA01641; Wed, 8 Oct 1997 18:05:19 +0930 (CST) Message-Id: <199710080835.SAA01641@word.smith.net.au> X-Mailer: exmh version 2.0zeta 7/24/97 To: Andreas Klemm cc: Robert Sowders , stable@FreeBSD.ORG Subject: Re: FreeBSD-2.2.5-BETA, /boot.help is missing -Reply In-reply-to: Your message of "Wed, 08 Oct 1997 08:50:12 +0200." <19971008085012.51101@klemm.gtn.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 08 Oct 1997 18:05:17 +0930 From: Mike Smith Sender: owner-freebsd-stable@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > On Tue, Oct 07, 1997 at 11:43:21PM -0700, Robert Sowders wrote: > > after boot run dmesg and see if psm0 is disabled. > > if it is, look in your kernel source and remove the line disable from > > the device psm0 line. then remake your kernel and reboot. > > it should be there now at /dev/psm0. > > kernel source at /usr/src/sys/i386/conf > > If that should be the case, could we then remove the disable token > entirely ? Or is disable necessary to be able to disable the driver > when autoprobing wasn't successfull ? It's much easier just to boot with '-c' and say "enable psm0"; there is no need to rebuild your kernel. The ps/2 mouse probe is disabled, IIRC, because it causes problems with some keyboard controllers. mike From owner-freebsd-stable Wed Oct 8 02:26:46 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id CAA06361 for stable-outgoing; Wed, 8 Oct 1997 02:26:46 -0700 (PDT) (envelope-from owner-freebsd-stable) Received: from outmail.utsunomiya-u.ac.jp (outmail.utsunomiya-u.ac.jp [160.12.196.3]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id CAA06351 for ; Wed, 8 Oct 1997 02:26:43 -0700 (PDT) (envelope-from yokota@zodiac.mech.utsunomiya-u.ac.jp) Received: by outmail.utsunomiya-u.ac.jp id AA11121; Wed, 8 Oct 1997 18:25:23 +0900 Received: from zodiac.mech.utsunomiya-u.ac.jp (zodiac.mech.utsunomiya-u.ac.jp [160.12.42.1]) by zodiac.mech.utsunomiya-u.ac.jp (8.7.6+2.6Wbeta7/3.4W/zodiac-May96) with ESMTP id SAA17331; Wed, 8 Oct 1997 18:31:34 +0900 (JST) Message-Id: <199710080931.SAA17331@zodiac.mech.utsunomiya-u.ac.jp> To: Andreas Klemm Cc: Robert Sowders , stable@freebsd.org, yokota@zodiac.mech.utsunomiya-u.ac.jp Subject: Re: FreeBSD-2.2.5-BETA, /boot.help is missing -Reply In-Reply-To: Your message of "Wed, 08 Oct 1997 08:50:12 +0200." <19971008085012.51101@klemm.gtn.com> References: <19971008085012.51101@klemm.gtn.com> Date: Wed, 08 Oct 1997 18:31:33 +0900 From: Kazutaka YOKOTA Sender: owner-freebsd-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >On Tue, Oct 07, 1997 at 11:43:21PM -0700, Robert Sowders wrote: >> after boot run dmesg and see if psm0 is disabled. >> if it is, look in your kernel source and remove the line disable from >> the device psm0 line. then remake your kernel and reboot. >> it should be there now at /dev/psm0. >> kernel source at /usr/src/sys/i386/conf > >If that should be the case, could we then remove the disable token >entirely ? Or is disable necessary to be able to disable the driver >when autoprobing wasn't successfull ? The keyword "disable" means "do not probe the device". The probe routine of the device driver will not be called. You will see psm0: disabled, not probed in this case. If you don't put this keyword in your kernel configuration file, or you enable this device driver in the UserConfig, the kernel will call the probe routine in the device driver. If the device driver reports that device probe has failed, the kernel wont' attach the device. This action is alwasy taken if the probe fails. The keyword "disable" has nothing to do with this. You will see psm0: not found at 0x60 in this case. You may also see additional error messages. Please examine the boot message, or the output from `dmesg' to see which is the case with your system. Kazu From owner-freebsd-stable Wed Oct 8 03:00:40 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id DAA08287 for stable-outgoing; Wed, 8 Oct 1997 03:00:40 -0700 (PDT) (envelope-from owner-freebsd-stable) Received: from krabi.mbp.ee (krabi.mbp.ee [194.204.12.83]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id CAA08013 for ; Wed, 8 Oct 1997 02:55:17 -0700 (PDT) (envelope-from root@krabi.mbp.ee) Received: from localhost by krabi.mbp.ee with smtp id m0xIshE-0008VuC (Debian Smail-3.2 1996-Jul-4 #2); Wed, 8 Oct 1997 12:46:24 +0300 (EEST) Date: Wed, 8 Oct 1997 12:46:24 +0300 (EEST) From: Superuser To: stable@freebsd.org Subject: Re: error in make world -Reply In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Tue, 7 Oct 1997, Robert Sowders wrote: > add the group network to /etc/group file then make installworld. Thanks for all who replied! This fixed the problem _____________ Lauri Laupmaa mauri@mbp.ee From owner-freebsd-stable Wed Oct 8 05:05:41 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id FAA13370 for stable-outgoing; Wed, 8 Oct 1997 05:05:41 -0700 (PDT) (envelope-from owner-freebsd-stable) Received: from krabi.mbp.ee (root@krabi.mbp.ee [194.204.12.83]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id FAA13286 for ; Wed, 8 Oct 1997 05:03:22 -0700 (PDT) (envelope-from root@krabi.mbp.ee) Received: from localhost by krabi.mbp.ee with smtp id m0xIshE-0008VuC (Debian Smail-3.2 1996-Jul-4 #2); Wed, 8 Oct 1997 12:46:24 +0300 (EEST) Date: Wed, 8 Oct 1997 12:46:24 +0300 (EEST) From: Superuser To: stable@freebsd.org Subject: Re: error in make world -Reply In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Tue, 7 Oct 1997, Robert Sowders wrote: > add the group network to /etc/group file then make installworld. Thanks for all who replied! This fixed the problem _____________ Lauri Laupmaa mauri@mbp.ee From owner-freebsd-stable Wed Oct 8 07:18:20 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id HAA19788 for stable-outgoing; Wed, 8 Oct 1997 07:18:20 -0700 (PDT) (envelope-from owner-freebsd-stable) Received: from hetzels (172-21-61.ipt.aol.com [152.172.21.61]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id HAA19778; Wed, 8 Oct 1997 07:18:12 -0700 (PDT) (envelope-from hetzels@aol.com) From: "Scot W. Hetzel" To: "Stable" Cc: "Chad R. Larson" Subject: Re: Fwd: CVSup release identity Date: Wed, 8 Oct 1997 09:15:28 -0500 Message-ID: <01bcd3f4$a0e6ea20$LocalHost@hetzels> MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 4.71.1712.3 X-MimeOLE: Produced By Microsoft MimeOLE V4.71.1712.3 Sender: owner-freebsd-stable@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk -----Original Message----- From: Chad R. Larson >I'll re-suggest an alpha-numeric counter instead of date/time, both for >economy (fewer characters) and to avoid debate about time zones and >daylight savings. But I'd add a character that denotes which CVS tag I'm against an alpha-numeric counter, as a 2 digit counter only produces 1296 combinations. If you look at the number of CTM updates for CURRENT, they are in the 3000, thus we'll have exhausted the combination long before we start. As for a date/time stamp, there would be no debate about time zones or daylight savings as the date/time stamp is applied at the Master Source Repository server. Times zones or daylight savings isn't a problem as long as everyone agrees that job of the Master Source Repository server is to provide a timestamp to the source trees, and that it will use a constant time (ZULU) value. >was used to retrieve the sources. Obvious characters would be 'C' (for >current), 'R' (for release) and 'S' (for stable). The other 23 >characters could (and should) be assigned to any other tags accessable >to non-core team members. > >So, we'd see something like this: >2.2-CAB >2.2-SCD >2.2.5-R Also, your tag wouldn't be required if we did the following: # uname -r 2.2.2 (199710081259) # uname -v FreeBSD 2.2-STABLE ... According to the man page "uname -r" gives the Release Level, while "uname -v" shows the version, along with other information. "uname -v" could also indicate the development branch (CURRENT, RELEASE, or STABLE) for the source. Scot From owner-freebsd-stable Wed Oct 8 07:56:50 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id HAA22252 for stable-outgoing; Wed, 8 Oct 1997 07:56:50 -0700 (PDT) (envelope-from owner-freebsd-stable) Received: from ns.mt.sri.com (SRI-56K-FR.mt.net [206.127.65.42]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id HAA22245 for ; Wed, 8 Oct 1997 07:56:46 -0700 (PDT) (envelope-from nate@rocky.mt.sri.com) Received: from rocky.mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by ns.mt.sri.com (8.8.7/8.8.7) with ESMTP id IAA01724; Wed, 8 Oct 1997 08:55:32 -0600 (MDT) Received: (from nate@localhost) by rocky.mt.sri.com (8.7.5/8.7.3) id IAA10606; Wed, 8 Oct 1997 08:55:30 -0600 (MDT) Date: Wed, 8 Oct 1997 08:55:30 -0600 (MDT) Message-Id: <199710081455.IAA10606@rocky.mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Mike Smith Cc: Andreas Klemm , Robert Sowders , stable@freebsd.org Subject: psm driver (was Re: FreeBSD-2.2.5-BETA, /boot.help is missing) In-Reply-To: <199710080835.SAA01641@word.smith.net.au> References: <19971008085012.51101@klemm.gtn.com> <199710080835.SAA01641@word.smith.net.au> X-Mailer: VM 6.29 under 19.15 XEmacs Lucid Sender: owner-freebsd-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Mike Smith writes: [ psm0 is disabled by default in the kernel config file ] > > If that should be the case, could we then remove the disable token > > entirely ? Or is disable necessary to be able to disable the driver > > when autoprobing wasn't successfull ? > > It's much easier just to boot with '-c' and say "enable psm0"; there is > no need to rebuild your kernel. No kidding. > The ps/2 mouse probe is disabled, IIRC, because it causes problems with > some keyboard controllers. Actually, since Kazu's re-write of everything, I'll bet we could re-enable it by default, since syscons already uses the 'critical' code that used to cause lockups. I may enable it later today if I think about it again. :) Nate From owner-freebsd-stable Wed Oct 8 08:26:48 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id IAA23840 for stable-outgoing; Wed, 8 Oct 1997 08:26:48 -0700 (PDT) (envelope-from owner-freebsd-stable) Received: from shrimp.dataplex.net (shrimp.dataplex.net [208.2.87.3]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id IAA23832 for ; Wed, 8 Oct 1997 08:26:45 -0700 (PDT) (envelope-from rkw@dataplex.net) Received: from [204.69.236.50] (GATEWAY.SKIPSTONE.COM [198.214.10.129]) by shrimp.dataplex.net (8.8.5/8.8.5) with ESMTP id KAA01460; Wed, 8 Oct 1997 10:26:39 -0500 (CDT) X-Sender: rkw@mail.dataplex.net Message-Id: In-Reply-To: <01bcd3f4$a0e6ea20$LocalHost@hetzels> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Wed, 8 Oct 1997 10:26:38 -0500 To: "Scot W. Hetzel" From: Richard Wackerbarth Subject: Re: Fwd: CVSup release identity Cc: stable@FreeBSD.ORG Sender: owner-freebsd-stable@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk ># uname -r > >2.2.2 (199710081259) > ># uname -v > >FreeBSD 2.2-STABLE ... > >According to the man page "uname -r" gives the Release Level, while >"uname -v" shows the version, along with other information. "uname -v" >could also indicate the development branch (CURRENT, RELEASE, or STABLE) for >the source. Please realize that "CURRENT", "RELEASE", and "STABLE" are NOT different sub-branches. The branches are 2.1, 2.2, 3.0, etc. Each "-RELEASE" indicates a particular waypoint on its branch. "-CURRENT" and "-STABLE" are just a description of the intended status. I see some value in distinguishing between releases and interim patched versions. However, IMHO, "-CURRENT" and "-STABLE" should be dropped. All references to a particular branch need to be in terms of its invariant name, eg "2.2". Further, I would phase out the "stable" and "current" mailing lists in favor of lists designated by the particular branch's numeric name. That way, the purpose of a list would not need to change as development progresses. The transition can be handled by cloning existing mailing lists and using mail aliases to allow the deprecated names to continue to function as expected. Richard Wackerbarth From owner-freebsd-stable Wed Oct 8 09:02:07 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id JAA26119 for stable-outgoing; Wed, 8 Oct 1997 09:02:07 -0700 (PDT) (envelope-from owner-freebsd-stable) Received: from emout18.mail.aol.com (emout18.mx.aol.com [198.81.11.44]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id JAA26109 for ; Wed, 8 Oct 1997 09:02:03 -0700 (PDT) (envelope-from Hetzels@aol.com) From: Hetzels@aol.com Received: (from root@localhost) by emout18.mail.aol.com (8.7.6/8.7.3/AOL-2.0.0) id MAA28490; Wed, 8 Oct 1997 12:01:25 -0400 (EDT) Date: Wed, 8 Oct 1997 12:01:25 -0400 (EDT) Message-ID: <971008120031_912347238@emout18.mail.aol.com> To: rkw@dataplex.net cc: stable@freebsd.org Subject: Re: CVSup release identity Sender: owner-freebsd-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk In a message dated 97-10-08 11:26:45 EDT, rkw@dataplex.net writes: > ># uname -r > > > >2.2.2 (199710081259) > > > ># uname -v > > > >FreeBSD 2.2-STABLE ... > > > >According to the man page "uname -r" gives the Release Level, while > >"uname -v" shows the version, along with other information. "uname -v" > >could also indicate the development branch (CURRENT, RELEASE, or STABLE) > for > >the source. > > Please realize that "CURRENT", "RELEASE", and "STABLE" are NOT different > sub-branches. The branches are 2.1, 2.2, 3.0, etc. > > Each "-RELEASE" indicates a particular waypoint on its branch. > "-CURRENT" and "-STABLE" are just a description of the intended status. Yes, I realize that they are not sub-branches. But newvers.sh refers to them as branches, and I may have used the wrong term in describing them. > > I see some value in distinguishing between releases and interim patched > versions. However, IMHO, "-CURRENT" and "-STABLE" should be dropped. I don't agree on dropping the names. Keeping the names alows users to know exactly, what they are tracking (CURRENT or STABLE). Only, "uname -v" should say CURRENT, RELEASE, or STABLE, and "uname -r" will show the release level. > All references to a particular branch need to be in terms of its invariant > name, eg "2.2". Further, I would phase out the "stable" and "current" > mailing lists in favor of lists designated by the particular branch's > numeric name. I would leave the mailing lists alone. Why, because as users transition from one branch to the next (2.1 -> 2.2 -> 3.0), the number of individuals to help solve problems will decrease in the older mailing lists. Plus, it forces users to unsubscribe/resubscribe to the mailing lists (for example a user upgrades to 2.2 form 2.1. He then needs to unsubscribes from the 2.1 mailing list and is forced to resubscribe to 2.2.). Besides, the same questions will be asked in multiple mailing lists, instead of just in one (stable). Also, the development team dosen't have to track 3+ mailing lists, only 2). > That way, the purpose of a list would not need to change as development > progresses. The transition can be handled by cloning existing mailing lists > and using mail aliases to allow the deprecated names to continue to > function as expected. > > Richard Wackerbarth > Scot From owner-freebsd-stable Wed Oct 8 09:04:34 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id JAA26305 for stable-outgoing; Wed, 8 Oct 1997 09:04:34 -0700 (PDT) (envelope-from owner-freebsd-stable) Received: from hetzels (172-21-61.ipt.aol.com [152.172.21.61]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id JAA26295 for ; Wed, 8 Oct 1997 09:04:27 -0700 (PDT) (envelope-from hetzels@aol.com) From: "Scot W. Hetzel" To: Subject: Fw: Fwd: CVSup release identity Date: Wed, 8 Oct 1997 11:00:34 -0500 Message-ID: <01bcd403$4f815e40$LocalHost@hetzels> MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 4.71.1712.3 X-MimeOLE: Produced By Microsoft MimeOLE V4.71.1712.3 Sender: owner-freebsd-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk From: Chad R. Larson >I'll re-suggest an alpha-numeric counter instead of date/time, both for >economy (fewer characters) and to avoid debate about time zones and >daylight savings. But I'd add a character that denotes which CVS tag I'm against an alpha-numeric counter, as a 2 digit counter only produces 1296 combinations. If you look at the number of CTM updates for CURRENT, they are in the 3000, thus we'll have exhausted the combination long before we start. As for a date/time stamp, there would be no debate about time zones or daylight savings as the date/time stamp is applied at the Master Source Repository server. Times zones or daylight savings isn't a problem as long as everyone agrees that job of the Master Source Repository server is to provide a timestamp to the source trees, and that it will use a constant time (ZULU) value. >was used to retrieve the sources. Obvious characters would be 'C' (for >current), 'R' (for release) and 'S' (for stable). The other 23 >characters could (and should) be assigned to any other tags accessable >to non-core team members. > >So, we'd see something like this: >2.2-CAB >2.2-SCD >2.2.5-R Also, your tag wouldn't be required if we did the following: # uname -r 2.2.2 (199710081259) # uname -v FreeBSD 2.2-STABLE ... According to the man page "uname -r" gives the Release Level, while "uname -v" shows the version, along with other information. "uname -v" could also indicate the development branch (CURRENT, RELEASE, or STABLE) for the source. Scot From owner-freebsd-stable Wed Oct 8 09:12:51 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id JAA26859 for stable-outgoing; Wed, 8 Oct 1997 09:12:51 -0700 (PDT) (envelope-from owner-freebsd-stable) Received: from mail.wintek.com (mail.wintek.com [199.233.104.76]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id JAA26838 for ; Wed, 8 Oct 1997 09:12:39 -0700 (PDT) (envelope-from csg@wintek.com) Received: from mail.wintek.com (localhost.wintek.com [127.0.0.1]) by mail.wintek.com (8.8.7/1.34wintek(3.6davy)) with ESMTP id QAA08022; Wed, 8 Oct 1997 16:12:38 GMT Message-Id: <199710081612.QAA08022@mail.wintek.com> To: freebsd-stable@freebsd.org Subject: de0 success under 2.2.5-BETA Date: Wed, 08 Oct 1997 11:12:38 -0500 From: "C. Stephen Gunn" Sender: owner-freebsd-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk We have been running the de0 driver from 3.0-CURRENT under a very recent 2.2.5-BETA and don't see any problems. I applied the patches from 3.0-CURRENT to fix some memory buffer problems by hand to the versions available on www.3am-software.com and everything worked fine from there. We are using BayNetworks NetGear 10/100 PCI adaptors. They are based on the 21140A chipset. Actually they work too well, and we need to buy a 10/100 Switch now so they don't kill our network doing innocent things like ftp. Netatalk still seems to be broken, but that's now appears to be independant of the problems we had seen with the de0 drivers. Let me know if anybody wants more info on our "successful testing" - Steve -- C. Stephen Gunn Wintek Corporation E-mail: csg@wintek.com 427 N 6th Street Tel: +1 (765) 742-8428 Lafayette, IN 47901-1126 Fax: +1 (765) 742-0547 United States of America From owner-freebsd-stable Wed Oct 8 09:22:13 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id JAA27458 for stable-outgoing; Wed, 8 Oct 1997 09:22:13 -0700 (PDT) (envelope-from owner-freebsd-stable) Received: from shrimp.dataplex.net (shrimp.dataplex.net [208.2.87.3]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id JAA27447 for ; Wed, 8 Oct 1997 09:22:07 -0700 (PDT) (envelope-from rkw@dataplex.net) Received: from [204.69.236.50] (GATEWAY.SKIPSTONE.COM [198.214.10.129]) by shrimp.dataplex.net (8.8.5/8.8.5) with ESMTP id LAA01846; Wed, 8 Oct 1997 11:21:57 -0500 (CDT) X-Sender: rkw@mail.dataplex.net Message-Id: In-Reply-To: <971008120031_912347238@emout18.mail.aol.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Wed, 8 Oct 1997 11:21:53 -0500 To: Hetzels@aol.com From: Richard Wackerbarth Subject: Re: CVSup release identity Cc: stable@freebsd.org Sender: owner-freebsd-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >> I see some value in distinguishing between releases and interim patched >> versions. However, IMHO, "-CURRENT" and "-STABLE" should be dropped. > >I don't agree on dropping the names. Keeping the names alows users to know >exactly, what they are tracking (CURRENT or STABLE). Only, "uname -v" should >say CURRENT, RELEASE, or STABLE, and "uname -r" will show the release level. These names are needed only because you are insisting that they be used in place of the "2.2" style name. >> All references to a particular branch need to be in terms of its invariant >> name, eg "2.2". Further, I would phase out the "stable" and "current" >> mailing lists in favor of lists designated by the particular branch's >> numeric name. > >I would leave the mailing lists alone. Why, because as users transition from >one branch to the next (2.1 -> 2.2 -> 3.0), the number of individuals to help >solve problems will decrease in the older mailing lists. OTOH, the same thing already occurs. There are quite a few of the "current" crowd who never look at "stable". They also object to questions that belong on "stable" being asked on "current" or "hackers". My making the lists more explicit, the misposting should decrease. > Plus, it forces >users to unsubscribe/resubscribe to the mailing lists (for example a user >upgrades to 2.2 from 2.1. He then needs to unsubscribes from the 2.1 mailing >list and is forced to resubscribe to 2.2.) As if he won't have to subscribe to "stable" when the development branch moves to 4.0 ... I will argue that it makes more sense for the user to subscribe to a list when he changes systems rather than when someone else releases a new system. As for the creation of a new branch and the associated mailing list, that could be handled by administratively cloning the development list. Anyone who had no interest in following both lists could unsubscribe from the list that no longer interests them. >. Besides, the same questions will >be asked in multiple mailing lists, instead of just in one (stable). Also, >the development team dosen't have to track 3+ mailing lists, only 2). By that argument, we should merge stable and current and have only one list. :-) I don't agree. Lists are split because their content should be different. BTW, if, today, my system says that I am running 2.1-CURRENT, which list should I use? Richard Wackerbarth From owner-freebsd-stable Wed Oct 8 09:54:49 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id JAA29691 for stable-outgoing; Wed, 8 Oct 1997 09:54:49 -0700 (PDT) (envelope-from owner-freebsd-stable) Received: from mailhost2.BayNetworks.COM (ns2.BayNetworks.COM [134.177.3.16]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id JAA29685 for ; Wed, 8 Oct 1997 09:54:42 -0700 (PDT) (envelope-from bwithrow@BayNetworks.COM) Received: from ns4.BayNetworks.COM (screen2r.BayNetworks.COM [134.177.3.1]) by mailhost2.BayNetworks.COM (8.8.6/BNET-97/07/07-E) with ESMTP id JAA08509; Wed, 8 Oct 1997 09:54:05 -0700 (PDT) for Posted-Date: Wed, 8 Oct 1997 09:54:05 -0700 (PDT) Received: from pobox.engeast.BayNetworks.COM (pobox.engeast.baynetworks.com [192.32.151.199]) by ns4.BayNetworks.COM (8.8.6/8.8.6) with ESMTP id MAA24663 for ; Wed, 8 Oct 1997 12:53:36 -0400 (EDT) Received: from tuva.engeast.baynetworks.com (tuva [192.32.180.119]) by pobox.engeast.BayNetworks.COM (SMI-8.6/BNET-97/04/24-S) with ESMTP id MAA12795; Wed, 8 Oct 1997 12:53:36 -0400 for Received: from tuva.engeast.baynetworks.com (localhost [127.0.0.1]) by tuva.engeast.baynetworks.com (8.8.3/8.8.3) with ESMTP id MAA16702 for ; Wed, 8 Oct 1997 12:53:36 -0400 (EDT) Message-Id: <199710081653.MAA16702@tuva.engeast.baynetworks.com> X-Mailer: exmh version 2.0gamma 1/27/96 To: freebsd-stable@freebsd.org Subject: Install complaint Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 08 Oct 1997 12:53:36 -0400 From: Robert Withrow Sender: owner-freebsd-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk In the installer "distributions" area, if you enter a sub-distributions screen (say, for the DES distribution), when you return to the parent distribution you are at the top of the list again. This is *ANNOYING*. Can this be changed to return you to the item you were already at in the parent screen? -- Robert Withrow -- (+1 508 916 8256) BWithrow@BayNetworks.com From owner-freebsd-stable Wed Oct 8 10:07:22 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id KAA00810 for stable-outgoing; Wed, 8 Oct 1997 10:07:22 -0700 (PDT) (envelope-from owner-freebsd-stable) Received: from ns.mt.sri.com (SRI-56K-FR.mt.net [206.127.65.42]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id KAA00803 for ; Wed, 8 Oct 1997 10:07:13 -0700 (PDT) (envelope-from nate@rocky.mt.sri.com) Received: from rocky.mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by ns.mt.sri.com (8.8.7/8.8.7) with ESMTP id LAA02529; Wed, 8 Oct 1997 11:07:10 -0600 (MDT) Received: (from nate@localhost) by rocky.mt.sri.com (8.7.5/8.7.3) id LAA11045; Wed, 8 Oct 1997 11:07:08 -0600 (MDT) Date: Wed, 8 Oct 1997 11:07:08 -0600 (MDT) Message-Id: <199710081707.LAA11045@rocky.mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Richard Wackerbarth Cc: stable@freebsd.org Subject: Re: Fwd: CVSup release identity In-Reply-To: References: <01bcd3f4$a0e6ea20$LocalHost@hetzels> X-Mailer: VM 6.29 under 19.15 XEmacs Lucid Sender: owner-freebsd-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Ok folks, we've discussed this to death, and even had a couple of consensus's. But, nobody has come up with 'code' that implements any of this. It's all a moot point until someone comes up with a way to time-stamp things *IN CVS* on freefall. I suggest spending less time arguing, and more time coming up with a *solution*, and not a proposed solution. Changes to the tree, newvers.sh, etc.... Nate From owner-freebsd-stable Wed Oct 8 10:07:46 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id KAA00846 for stable-outgoing; Wed, 8 Oct 1997 10:07:46 -0700 (PDT) (envelope-from owner-freebsd-stable) Received: from mailhost3.BayNetworks.COM (ns4.BayNetworks.COM [192.32.253.7]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id KAA00837 for ; Wed, 8 Oct 1997 10:07:39 -0700 (PDT) (envelope-from bwithrow@BayNetworks.COM) Received: from ns4.BayNetworks.COM ([132.245.135.84] (may be forged)) by mailhost3.BayNetworks.COM (8.8.6/BNET-97/07/07-E) with ESMTP id NAA16415; Wed, 8 Oct 1997 13:16:07 -0400 (EDT) for Posted-Date: Wed, 8 Oct 1997 13:16:07 -0400 (EDT) Received: from pobox.engeast.BayNetworks.COM (pobox.engeast.baynetworks.com [192.32.151.199]) by ns4.BayNetworks.COM (8.8.6/8.8.6) with ESMTP id NAA24814 for ; Wed, 8 Oct 1997 13:04:15 -0400 (EDT) Received: from tuva.engeast.baynetworks.com (tuva [192.32.180.119]) by pobox.engeast.BayNetworks.COM (SMI-8.6/BNET-97/04/24-S) with ESMTP id NAA13766; Wed, 8 Oct 1997 13:04:14 -0400 for Received: from tuva.engeast.baynetworks.com (localhost [127.0.0.1]) by tuva.engeast.baynetworks.com (8.8.3/8.8.3) with ESMTP id NAA16759 for ; Wed, 8 Oct 1997 13:04:14 -0400 (EDT) Message-Id: <199710081704.NAA16759@tuva.engeast.baynetworks.com> X-Mailer: exmh version 2.0gamma 1/27/96 To: freebsd-stable@freebsd.org Subject: Packages-2.2.5 is missing INDEX file Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 08 Oct 1997 13:04:14 -0400 From: Robert Withrow Sender: owner-freebsd-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk The ftp.freebsd.org mirror of packages-2.2.5 is missing the INDEX file... -- Robert Withrow -- (+1 508 916 8256) BWithrow@BayNetworks.com From owner-freebsd-stable Wed Oct 8 10:32:44 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id KAA02691 for stable-outgoing; Wed, 8 Oct 1997 10:32:44 -0700 (PDT) (envelope-from owner-freebsd-stable) Received: from emout39.mail.aol.com (emout39.mx.aol.com [198.81.11.73]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id KAA02686 for ; Wed, 8 Oct 1997 10:32:42 -0700 (PDT) (envelope-from Hetzels@aol.com) From: Hetzels@aol.com Received: (from root@localhost) by emout39.mail.aol.com (8.7.6/8.7.3/AOL-2.0.0) id NAA12939; Wed, 8 Oct 1997 13:32:05 -0400 (EDT) Date: Wed, 8 Oct 1997 13:32:05 -0400 (EDT) Message-ID: <971008122733_-859415238@emout12.mail.aol.com> To: rkw@dataplex.net cc: stable@freebsd.org Subject: Re: CVSup release identity Sender: owner-freebsd-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk In a message dated 97-10-08 12:22:12 EDT, rkw@dataplex.net writes: > >I would leave the mailing lists alone. Why, because as users transition from > >one branch to the next (2.1 -> 2.2 -> 3.0), the number of individuals to > help > >solve problems will decrease in the older mailing lists. > OTOH, the same thing already occurs. There are quite a few of the "current" > crowd who never look at "stable". They also object to questions that belong > on "stable" being asked on "current" or "hackers". My making the lists more > explicit, the misposting should decrease. > > > Plus, it forces > >users to unsubscribe/resubscribe to the mailing lists (for example a user > >upgrades to 2.2 from 2.1. He then needs to unsubscribes from the 2.1 > mailing > >list and is forced to resubscribe to 2.2.) > > As if he won't have to subscribe to "stable" when the development branch > moves to 4.0 ... I will argue that it makes more sense for the user to > subscribe to a list when he changes systems rather than when someone else > releases a new system. As for the creation of a new branch and the > associated mailing list, that could be handled by administratively cloning > the development list. Anyone who had no interest in following both lists > could unsubscribe from the list that no longer interests them. > > > >. Besides, the same questions will > >be asked in multiple mailing lists, instead of just in one (stable). Also, > >the development team dosen't have to track 3+ mailing lists, only 2). > > By that argument, we should merge stable and current and have only one > list. :-) > I don't agree. Lists are split because their content should be different. > > BTW, if, today, my system says that I am running 2.1-CURRENT, which list > should I use? > > Richard Wackerbarth > Ok, why don't we leave the mailing lists alone for now, and get back to solving the problem with the source tree first. If you feel so strongly about this talk to the mailing list maintainers. Scot From owner-freebsd-stable Wed Oct 8 11:05:14 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id LAA04377 for stable-outgoing; Wed, 8 Oct 1997 11:05:14 -0700 (PDT) (envelope-from owner-freebsd-stable) Received: from mailhost3.BayNetworks.COM (ns4.BayNetworks.COM [192.32.253.7]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id LAA04367 for ; Wed, 8 Oct 1997 11:05:06 -0700 (PDT) (envelope-from bwithrow@BayNetworks.COM) Received: from ns4.BayNetworks.COM ([132.245.135.84] (may be forged)) by mailhost3.BayNetworks.COM (8.8.6/BNET-97/07/07-E) with ESMTP id OAA19082; Wed, 8 Oct 1997 14:11:51 -0400 (EDT) for Posted-Date: Wed, 8 Oct 1997 14:11:51 -0400 (EDT) Received: from pobox.engeast.BayNetworks.COM (pobox.engeast.baynetworks.com [192.32.151.199]) by ns4.BayNetworks.COM (8.8.6/8.8.6) with ESMTP id NAA25359 for ; Wed, 8 Oct 1997 13:58:23 -0400 (EDT) Received: from tuva.engeast.baynetworks.com (tuva [192.32.180.119]) by pobox.engeast.BayNetworks.COM (SMI-8.6/BNET-97/04/24-S) with ESMTP id NAA21289; Wed, 8 Oct 1997 13:57:48 -0400 for Received: from tuva.engeast.baynetworks.com (localhost [127.0.0.1]) by tuva.engeast.baynetworks.com (8.8.3/8.8.3) with ESMTP id NAA17095 for ; Wed, 8 Oct 1997 13:56:48 -0400 (EDT) Message-Id: <199710081756.NAA17095@tuva.engeast.baynetworks.com> X-Mailer: exmh version 2.0gamma 1/27/96 To: freebsd-stable@freebsd.org Subject: NFS Client option -- didn't take Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 08 Oct 1997 13:56:47 -0400 From: Robert Withrow Sender: owner-freebsd-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >From the oct 7'th beta, selecting NFS client during the installation didn't "take" in rc.conf. BTW, why is install modifying rc.conf instead of just writing the changes into rc.conf.local? -- Robert Withrow -- (+1 508 916 8256) BWithrow@BayNetworks.com From owner-freebsd-stable Wed Oct 8 11:37:23 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id LAA06453 for stable-outgoing; Wed, 8 Oct 1997 11:37:23 -0700 (PDT) (envelope-from owner-freebsd-stable) Received: from emout23.mail.aol.com (emout23.mx.aol.com [198.81.11.128]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id LAA06448 for ; Wed, 8 Oct 1997 11:37:20 -0700 (PDT) (envelope-from Hetzels@aol.com) From: Hetzels@aol.com Received: (from root@localhost) by emout23.mail.aol.com (8.7.6/8.7.3/AOL-2.0.0) id OAA21436; Wed, 8 Oct 1997 14:36:42 -0400 (EDT) Date: Wed, 8 Oct 1997 14:36:42 -0400 (EDT) Message-ID: <971008133941_1032265457@emout16.mail.aol.com> To: rkw@dataplex.net cc: stable@freebsd.org Subject: Re: CVSup release identity Sender: owner-freebsd-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk In a message dated 97-10-08 12:22:12 EDT, rkw@dataplex.net writes: > >> I see some value in distinguishing between releases and interim patched > >> versions. However, IMHO, "-CURRENT" and "-STABLE" should be dropped. > > > >I don't agree on dropping the names. Keeping the names alows users to know > >exactly, what they are tracking (CURRENT or STABLE). Only, "uname -v" > should > >say CURRENT, RELEASE, or STABLE, and "uname -r" will show the release level. > > > These names are needed only because you are insisting that they be used in > place of the "2.2" style name. > The only one I am really institing on is the "uname -r" output to show the correct release level. 2.2.x (199710081255) The "uname -v" output has room to indicate what the user is tracking (CURRENT, RELEASE, or STABLE). Currently, a "uname -v" shows: OS (FreeBSD) Version (2.2) Branch (STABLE) Kernel Version (0) Date the Kernel was compiled (Tue Oct 7 10:57:40 CDT 1997) Who Made the Kernel (root@www.my.domain.net) Location of the Kernel Compile Directory (/usr/src/sys/compile/GENERIC) Which of the following would you rather have: ----- #1) FreeBSD 2.2-STABLE #0: Tue Oct 7 10:57:40 CDT 1997 root@www.my.domain.net:/usr/src/sys/compile/GENERIC Currently, the standard. Indicates very clearly what the user is using. By checking with "uname -r", users will be able to view the release level for CURRENT, RELEASE, or STABLE systems. ----- #2) FreeBSD 2.2.x (199710081255) #0: Tue Oct 7 10:57:40 CDT 1997 root@www.my.domain.net:/usr/src/sys/compile/GENERIC FreeBSD 3.0 (199710081255) #0: Tue Oct 7 10:57:40 CDT 1997 root@www.my.domain.net:/usr/src/sys/compile/GENERIC This would indicate a CURRENT system, as it would only use 2 digit version numbers. This has the problem of duplicating the function of "uname -r". "uname -v" should not have to show the release level. ----- #3) FreeBSD 2.2.x #0: Tue Oct 7 10:57:40 CDT 1997 root@www.my.domain.net:/usr/src/sys/compile/GENERIC Simplifies the "uname -v" output, but doesn't indicate to the user if it is a RELEASE or a STABLE system up front. FreeBSD 3.0 #0: Tue Oct 7 10:57:40 CDT 1997 root@www.my.domain.net:/usr/src/sys/compile/GENERIC This would indicate a CURRENT system, as it would only use 2 digit version numbers. By checking with "uname -r", users will be able to view the release level for CURRENT, RELEASE, or STABLE systems. ----- #2 & #3 have the problem of determining if a user is using a STABLE or a RELEASE system. Now who is going to maintain a list of timestamps so that users can check. I would prefer #1, but number #3 has posibilities if only the difference between a RELEASE and STABLE system could be made more apparent. With out having to refer to a list. Unless RELEASE is used, then we might as well stick to using #1. Scot From owner-freebsd-stable Wed Oct 8 11:52:38 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id LAA07581 for stable-outgoing; Wed, 8 Oct 1997 11:52:38 -0700 (PDT) (envelope-from owner-freebsd-stable) Received: from emout17.mail.aol.com (emout17.mx.aol.com [198.81.11.43]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id LAA07576 for ; Wed, 8 Oct 1997 11:52:36 -0700 (PDT) (envelope-from Hetzels@aol.com) From: Hetzels@aol.com Received: (from root@localhost) by emout17.mail.aol.com (8.7.6/8.7.3/AOL-2.0.0) id OAA24766; Wed, 8 Oct 1997 14:52:04 -0400 (EDT) Date: Wed, 8 Oct 1997 14:52:04 -0400 (EDT) Message-ID: <971008145142_1343674759@emout17.mail.aol.com> To: nate@mt.sri.com cc: stable@freebsd.org Subject: Re: CVSup release identity Sender: owner-freebsd-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk In a message dated 97-10-08 14:24:22 EDT, nate@mt.sri.com writes: > Ok folks, we've discussed this to death, and even had a couple of > consensus's. But, nobody has come up with 'code' that implements any of > this. It's all a moot point until someone comes up with a way to > time-stamp things *IN CVS* on freefall. > > I suggest spending less time arguing, and more time coming up with a > *solution*, and not a proposed solution. Changes to the tree, > newvers.sh, etc.... > We're trying to come up with the solution but it basically, involves three areas. 1. Creation of a .timestamp file added to the source tree. 2. Create a new newvers.sh that sets the timestamp. a. "uname -r" should output the release level. And I believe that everyone is in agreement that it should use a timestamp instead of some counter. b. "uname -v" output. Currently, we're tring to decide if the CURRENT, RELEASE, STABLE tags should go or stay. I'm for keeping them as it makes it clear as to what the user is running. RKW, is for removing them. I believe that it is 2:1, not sure who's favor right now. I currently have a patch to newvers.sh that uses a .timestamp file. This will cause uname -r to show the release level + time stamp. 2. Master Source Repository The .timestamp file has to be created after each update to the source trees. --timestamp-- #!/bin/sh date "+%C%m%d%H%M" > .timestamp --timestamp -- How do we implement timestamp so that it updates the .timestamp file at the Master Source Repository? This is the only real question left. Scot From owner-freebsd-stable Wed Oct 8 12:00:25 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id MAA08082 for stable-outgoing; Wed, 8 Oct 1997 12:00:25 -0700 (PDT) (envelope-from owner-freebsd-stable) Received: from word.smith.net.au (ppp20.portal.net.au [202.12.71.120]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id MAA08072 for ; Wed, 8 Oct 1997 12:00:18 -0700 (PDT) (envelope-from mike@word.smith.net.au) Received: from word.smith.net.au (localhost [127.0.0.1]) by word.smith.net.au (8.8.7/8.8.5) with ESMTP id EAA01020; Thu, 9 Oct 1997 04:22:57 +0930 (CST) Message-Id: <199710081852.EAA01020@word.smith.net.au> X-Mailer: exmh version 2.0zeta 7/24/97 To: Robert Withrow cc: freebsd-stable@freebsd.org Subject: Re: NFS Client option -- didn't take In-reply-to: Your message of "Wed, 08 Oct 1997 13:56:47 -0400." <199710081756.NAA17095@tuva.engeast.baynetworks.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 09 Oct 1997 04:22:50 +0930 From: Mike Smith Sender: owner-freebsd-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >From the oct 7'th beta, selecting NFS client during the installation > didn't "take" in rc.conf. > > BTW, why is install modifying rc.conf instead of just writing the > changes into rc.conf.local? Because rc.conf.local violates the entire purpose of rc.conf. The default values for the variables in rc.conf are implicit in the rc.* scripts; rc.conf is where you overried these defaults as you wish. mike From owner-freebsd-stable Wed Oct 8 12:03:42 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id MAA08284 for stable-outgoing; Wed, 8 Oct 1997 12:03:42 -0700 (PDT) (envelope-from owner-freebsd-stable) Received: from ns.mt.sri.com (SRI-56K-FR.mt.net [206.127.65.42]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id MAA08279 for ; Wed, 8 Oct 1997 12:03:36 -0700 (PDT) (envelope-from nate@rocky.mt.sri.com) Received: from rocky.mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by ns.mt.sri.com (8.8.7/8.8.7) with ESMTP id NAA03346; Wed, 8 Oct 1997 13:03:34 -0600 (MDT) Received: (from nate@localhost) by rocky.mt.sri.com (8.7.5/8.7.3) id NAA11742; Wed, 8 Oct 1997 13:03:32 -0600 (MDT) Date: Wed, 8 Oct 1997 13:03:32 -0600 (MDT) Message-Id: <199710081903.NAA11742@rocky.mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Hetzels@aol.com Cc: nate@mt.sri.com, stable@freebsd.org Subject: Re: CVSup release identity In-Reply-To: <971008145142_1343674759@emout17.mail.aol.com> References: <971008145142_1343674759@emout17.mail.aol.com> X-Mailer: VM 6.29 under 19.15 XEmacs Lucid Sender: owner-freebsd-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > I suggest spending less time arguing, and more time coming up with a > > *solution*, and not a proposed solution. Changes to the tree, > > newvers.sh, etc.... > > > We're trying to come up with the solution but it basically, involves three > areas. > 1. Creation of a .timestamp file added to the source tree. Sure, the only thing that's disagreed upon is the format of the timestamp, and how often it's built. *THIS* is the crux of the matter, and if you can come up with *something*, then the rest is politics. > 2. Create a new newvers.sh that sets the timestamp. No, you want newvers.sh to *use* the timestamp. newvers.sh is used everytime you build a kernel, so you want to use the information from it. > a. "uname -r" should output the release level. And I believe that everyone > is in agreement that it should use a timestamp instead of some counter. That's a political issue. > b. "uname -v" output. Currently, we're tring to decide if the CURRENT, > RELEASE, STABLE tags should go or stay. > > I'm for keeping them as it makes it clear as to what the user is running. > > RKW, is for removing them. Once the solution is in the tree, we can argue about what it says. :) > I currently have a patch to newvers.sh that uses a .timestamp file. This > will cause uname -r to show the release level + time stamp. > > 2. Master Source Repository > > The .timestamp file has to be created after each update to the source > trees. OR at some regular interval. This time-stamp has to be part of the CVS tree *and* available to *all* kernel users. How do you do that? > How do we implement timestamp so that it updates the .timestamp file at the > Master Source Repository? > > This is the only real question left. That's the only real issue IMHO. The rest is politics, and can be argued about with no agreement until hell freezes over with no resolution. Give me *A* working solution, and then whoever can argue about making it a better solution. Something is almost always better than nothing, especially in this case. If you can come up with *a* good solution, and no-one can come up with an agreement on a 'better' solution, the good one will be 'good enough'. Talk is cheap, especially since people like me can get involved. :) :) Nate From owner-freebsd-stable Wed Oct 8 12:53:29 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id MAA10634 for stable-outgoing; Wed, 8 Oct 1997 12:53:29 -0700 (PDT) (envelope-from owner-freebsd-stable) Received: from emout15.mail.aol.com (emout15.mx.aol.com [198.81.11.41]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id MAA10627 for ; Wed, 8 Oct 1997 12:53:26 -0700 (PDT) (envelope-from Hetzels@aol.com) From: Hetzels@aol.com Received: (from root@localhost) by emout15.mail.aol.com (8.7.6/8.7.3/AOL-2.0.0) id PAA07459; Wed, 8 Oct 1997 15:52:54 -0400 (EDT) Date: Wed, 8 Oct 1997 15:52:54 -0400 (EDT) Message-ID: <971008155108_-1194179101@emout15.mail.aol.com> To: nate@mt.sri.com cc: stable@freebsd.org Subject: Re: CVSup release identity Sender: owner-freebsd-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk In a message dated 97-10-08 15:03:48 EDT, nate@mt.sri.com writes: > > > I suggest spending less time arguing, and more time coming up with a > > > *solution*, and not a proposed solution. Changes to the tree, > > > newvers.sh, etc.... > > > > > We're trying to come up with the solution but it basically, involves three > > areas. > > 1. Creation of a .timestamp file added to the source tree. > > Sure, the only thing that's disagreed upon is the format of the > timestamp, and how often it's built. *THIS* is the crux of the matter, > and if you can come up with *something*, then the rest is politics. This file is re-created at the Master Source Repository, every time someone updates the source tree. NOTE: There would be a different timestamp file in each Branch (3.0, 2.2, 2.1) that needs to be tracked. > > > 2. Create a new newvers.sh that sets the timestamp. > > No, you want newvers.sh to *use* the timestamp. newvers.sh is used > everytime you build a kernel, so you want to use the information from > it. What I meant to say is that newvers.sh uses the .timestamp file to set it in the kernel. > > > a. "uname -r" should output the release level. And I believe that > everyone > > is in agreement that it should use a timestamp instead of some counter. > > That's a political issue. > > > b. "uname -v" output. Currently, we're tring to decide if the CURRENT, > > RELEASE, STABLE tags should go or stay. > > > > I'm for keeping them as it makes it clear as to what the user is running. > > > > RKW, is for removing them. > > Once the solution is in the tree, we can argue about what it says. :) > > > I currently have a patch to newvers.sh that uses a .timestamp file. This > > will cause uname -r to show the release level + time stamp. > > > > 2. Master Source Repository > > > > The .timestamp file has to be created after each update to the source > > trees. > > OR at some regular interval. This time-stamp has to be part of the CVS > tree *and* available to *all* kernel users. How do you do that? > > > How do we implement timestamp so that it updates the .timestamp file at > the > > Master Source Repository? > > > > This is the only real question left. > > That's the only real issue IMHO. The rest is politics, and can be > argued about with no agreement until hell freezes over with no > resolution. Give me *A* working solution, and then whoever can argue > about making it a better solution. Something is almost always better > than nothing, especially in this case. If you can come up with *a* good > solution, and no-one can come up with an agreement on a 'better' > solution, the good one will be 'good enough'. > > Talk is cheap, especially since people like me can get involved. :) :) > This is the one solution I don't know how to solve, the rest was easy. 1. What is the Master Source Repository using to track the source code? (RCS?) 2. How do you go about implementing a hook in to the source tracking code so that it will automatically update the ".timestamp" file after each update to the source tree. pseudo code: Check out ".timestamp" date "+%C%m%d%H%M" > ".timestamp" Check in ".timestamp" 3. Would it update the timestamp file after each file is checked in or after the person updating the source tree has finished? Scot From owner-freebsd-stable Wed Oct 8 12:59:48 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id MAA10970 for stable-outgoing; Wed, 8 Oct 1997 12:59:48 -0700 (PDT) (envelope-from owner-freebsd-stable) Received: from ns.mt.sri.com (SRI-56K-FR.mt.net [206.127.65.42]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id MAA10964 for ; Wed, 8 Oct 1997 12:59:43 -0700 (PDT) (envelope-from nate@rocky.mt.sri.com) Received: from rocky.mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by ns.mt.sri.com (8.8.7/8.8.7) with ESMTP id NAA03737; Wed, 8 Oct 1997 13:59:41 -0600 (MDT) Received: (from nate@localhost) by rocky.mt.sri.com (8.7.5/8.7.3) id NAA12037; Wed, 8 Oct 1997 13:59:39 -0600 (MDT) Date: Wed, 8 Oct 1997 13:59:39 -0600 (MDT) Message-Id: <199710081959.NAA12037@rocky.mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Hetzels@aol.com Cc: nate@mt.sri.com, stable@freebsd.org Subject: Re: CVSup release identity In-Reply-To: <971008155108_-1194179101@emout15.mail.aol.com> References: <971008155108_-1194179101@emout15.mail.aol.com> X-Mailer: VM 6.29 under 19.15 XEmacs Lucid Sender: owner-freebsd-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > > 1. Creation of a .timestamp file added to the source tree. > > > > Sure, the only thing that's disagreed upon is the format of the > > timestamp, and how often it's built. *THIS* is the crux of the matter, > > and if you can come up with *something*, then the rest is politics. > > This file is re-created at the Master Source Repository, every time someone > updates the source tree. Or, at a regular time. (But, I think that's also a political issue. I don't think we need that fined grained of control, and it might be a significant 'confusion' point trying to determine the *exact* point.) > NOTE: There would be a different timestamp file in each Branch (3.0, 2.2, > 2.1) that needs to be tracked. Good point. >>> How do we implement timestamp so that it updates the .timestamp file at >>> the Master Source Repository? > > That's the only real issue IMHO. The rest is politics, and can be > > argued about with no agreement until hell freezes over with no > > resolution. Give me *A* working solution, and then whoever can argue > > about making it a better solution. Something is almost always better > > than nothing, especially in this case. If you can come up with *a* good > > solution, and no-one can come up with an agreement on a 'better' > > solution, the good one will be 'good enough'. > > This is the one solution I don't know how to solve, the rest was easy. Right, hence my jumping in. Talk is cheap, real solutions are harder. > 1. What is the Master Source Repository using to track the source code? > (RCS?) CVS. > 2. How do you go about implementing a hook in to the source tracking code so > that it will automatically update the ".timestamp" file after each update to > the source tree. > > pseudo code: > > Check out ".timestamp" > > date "+%C%m%d%H%M" > ".timestamp" > > Check in ".timestamp" You've got the sources, go to it. :) (Hint, look at all the files in CVSROOT.) > 3. Would it update the timestamp file after each file is checked in or after > the person updating the source tree has finished? Don't know, what do you think? Seriously, these are the *technical* issues that need to be resolved, the rest is political. Come up with a solution to them and *THEN* you'll see some folks who have up to this point mostly ignored things interested. Until then you're just practicing your typing skills. Nate From owner-freebsd-stable Wed Oct 8 13:32:44 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id NAA12911 for stable-outgoing; Wed, 8 Oct 1997 13:32:44 -0700 (PDT) (envelope-from owner-freebsd-stable) Received: from zibbi.mikom.csir.co.za (zibbi.mikom.csir.co.za [146.64.24.58]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id NAA12903 for ; Wed, 8 Oct 1997 13:32:37 -0700 (PDT) (envelope-from jhay@zibbi.mikom.csir.co.za) Received: (from jhay@localhost) by zibbi.mikom.csir.co.za (8.8.7/8.8.7) id WAA09091; Wed, 8 Oct 1997 22:30:24 +0200 (SAT) From: John Hay Message-Id: <199710082030.WAA09091@zibbi.mikom.csir.co.za> Subject: Re: NFS Client option -- didn't take In-Reply-To: <199710081852.EAA01020@word.smith.net.au> from Mike Smith at "Oct 9, 97 04:22:50 am" To: mike@smith.net.au (Mike Smith) Date: Wed, 8 Oct 1997 22:30:24 +0200 (SAT) Cc: freebsd-stable@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL31 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > >From the oct 7'th beta, selecting NFS client during the installation > > didn't "take" in rc.conf. > > > > BTW, why is install modifying rc.conf instead of just writing the > > changes into rc.conf.local? > > Because rc.conf.local violates the entire purpose of rc.conf. The > default values for the variables in rc.conf are implicit in the rc.* > scripts; rc.conf is where you overried these defaults as you wish. > I guess it depends on your point of view. The way I do boxes here is to keep the default rc.conf and make all changes in rc.conf.local. This means I can at any time update the rc.* scripts and I will get the new variables that were added to rc.conf with their default values. This makes life a lot easier than having to constantly merge the new rc.conf variables into my configured rc.conf. John -- John Hay -- John.Hay@mikom.csir.co.za From owner-freebsd-stable Wed Oct 8 15:26:52 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id PAA19076 for stable-outgoing; Wed, 8 Oct 1997 15:26:52 -0700 (PDT) (envelope-from owner-freebsd-stable) Received: from freebie.dcfinc.com (freebie.dcfinc.com [138.113.2.8]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id PAA19067 for ; Wed, 8 Oct 1997 15:26:43 -0700 (PDT) (envelope-from chad@freebie.dcfinc.com) Received: (from chad@localhost) by freebie.dcfinc.com (8.8.3/8.8.3a) id PAA09436; Wed, 8 Oct 1997 15:25:58 -0700 (MST) From: "Chad R. Larson" Message-Id: <199710082225.PAA09436@freebie.dcfinc.com> Subject: Re: Fwd: CVSup release identity To: hetzels@aol.com (Scot W. Hetzel) Date: Wed, 8 Oct 1997 15:25:57 -0700 (MST) Cc: stable@FreeBSD.ORG In-Reply-To: <01bcd3f4$a0e6ea20$LocalHost@hetzels> from "Scot W. Hetzel" at "Oct 8, 97 09:15:28 am" Reply-to: chad@dcfinc.com 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 X-Loop: FreeBSD.org Precedence: bulk > From: Chad R. Larson > >I'll re-suggest an alpha-numeric counter instead of date/time, both for > >economy (fewer characters) and to avoid debate about time zones and > >daylight savings. But I'd add a character that denotes which CVS tag > > I'm against an alpha-numeric counter, as a 2 digit counter only > produces 1296 combinations. If you look at the number of CTM updates > for CURRENT, they are in the 3000, thus we'll have exhausted the > combination long before we start. I yield on the format of the counter. It's more important to get =something= done than to chatter about it. But final statement: When I first proposed it, the two digit counter would use [A-Z][a-z][0-9] characters, for which there are over 6700 combinations. > > Scot > -crl -- Chad R. Larson (CRL22) Brother, can you paradigm? 602-953-1392 chad@dcfinc.com chad@anasazi.com crl22@aol.com DCF, Inc. - 14523 North 49th Place, Scottsdale, Arizona 85254 From owner-freebsd-stable Wed Oct 8 15:30:40 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id PAA19253 for stable-outgoing; Wed, 8 Oct 1997 15:30:40 -0700 (PDT) (envelope-from owner-freebsd-stable) Received: from baic.com (router.baic.com [206.14.192.1]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id PAA19247 for ; Wed, 8 Oct 1997 15:30:37 -0700 (PDT) (envelope-from wself@baic.com) Received: (from wself@localhost) by baic.com (8.8.7/8.8.5) id PAA22053; Wed, 8 Oct 1997 15:37:49 GMT Message-ID: <19971008153747.16093@baic.com> Date: Wed, 8 Oct 1997 15:37:47 +0000 From: Wayne Self To: stable@FreeBSD.ORG Subject: Re: CVSup release identity References: <971008155108_-1194179101@emout15.mail.aol.com> <199710081959.NAA12037@rocky.mt.sri.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.84 In-Reply-To: <199710081959.NAA12037@rocky.mt.sri.com>; from Nate Williams on Wed, Oct 08, 1997 at 01:59:39PM -0600 Sender: owner-freebsd-stable@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > 1. Creation of a .timestamp file added to the source tree. How about this idea? We leave the "identity crisis" alone until 2.2.5 is released? Tracking what's going on today, while in BETA, requires sifting through the growing number of "name game" messages. Is it possible to wait until 2.2.5 is out of BETA to start clogging the list with things that are not going to be heard until that time? -- wayne ----------------------------------------------------------------------- yes sir, according to uname, you havn't had your oil changed in a month. also, your daughter, according to uname, is about to have a birthday. uname says she wants a barbie. ----------------------------------------------------------------------- From owner-freebsd-stable Wed Oct 8 15:42:19 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id PAA19977 for stable-outgoing; Wed, 8 Oct 1997 15:42:19 -0700 (PDT) (envelope-from owner-freebsd-stable) Received: from freebie.dcfinc.com (freebie.dcfinc.com [138.113.2.8]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id PAA19970 for ; Wed, 8 Oct 1997 15:42:14 -0700 (PDT) (envelope-from chad@freebie.dcfinc.com) Received: (from chad@localhost) by freebie.dcfinc.com (8.8.3/8.8.3a) id PAA09491; Wed, 8 Oct 1997 15:40:25 -0700 (MST) From: "Chad R. Larson" Message-Id: <199710082240.PAA09491@freebie.dcfinc.com> Subject: Re: CVSup release identity To: Hetzels@aol.com Date: Wed, 8 Oct 1997 15:40:24 -0700 (MST) Cc: nate@mt.sri.com, stable@FreeBSD.ORG In-Reply-To: <971008145142_1343674759@emout17.mail.aol.com> from "Hetzels@aol.com" at "Oct 8, 97 02:52:04 pm" Reply-to: chad@dcfinc.com 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 X-Loop: FreeBSD.org Precedence: bulk > How do we implement timestamp so that it updates the .timestamp file at the > Master Source Repository? > > This is the only real question left. Sounds like a John Postel question to me. -crl -- Chad R. Larson (CRL22) Brother, can you paradigm? 602-953-1392 chad@dcfinc.com chad@anasazi.com crl22@aol.com DCF, Inc. - 14523 North 49th Place, Scottsdale, Arizona 85254 From owner-freebsd-stable Wed Oct 8 16:30:28 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id QAA22330 for stable-outgoing; Wed, 8 Oct 1997 16:30:28 -0700 (PDT) (envelope-from owner-freebsd-stable) Received: from gatekeeper.tsc.tdk.com (root@gatekeeper.tsc.tdk.com [207.113.159.21]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id QAA22325 for ; Wed, 8 Oct 1997 16:30:26 -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.4/8.8.4) with ESMTP id QAA17300; Wed, 8 Oct 1997 16:29:39 -0700 (PDT) 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 QAA06676; Wed, 8 Oct 1997 16:29:37 -0700 (PDT) Received: (from gdonl@localhost) by salsa.gv.tsc.tdk.com (8.8.5/8.8.5) id QAA06393; Wed, 8 Oct 1997 16:29:36 -0700 (PDT) From: Don Lewis Message-Id: <199710082329.QAA06393@salsa.gv.tsc.tdk.com> Date: Wed, 8 Oct 1997 16:29:36 -0700 In-Reply-To: Hetzels@aol.com "Re: CVSup release identity" (Oct 8, 12:01pm) X-Mailer: Mail User's Shell (7.2.6 alpha(3) 7/19/95) To: Hetzels@aol.com, rkw@dataplex.net Subject: Re: CVSup release identity Cc: stable@FreeBSD.ORG Sender: owner-freebsd-stable@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Oct 8, 12:01pm, Hetzels@aol.com wrote: } Subject: Re: CVSup release identity } In a message dated 97-10-08 11:26:45 EDT, rkw@dataplex.net writes: } > Further, I would phase out the "stable" and "current" } > mailing lists in favor of lists designated by the particular branch's } > numeric name. } } I would leave the mailing lists alone. Why, because as users transition from } one branch to the next (2.1 -> 2.2 -> 3.0), the number of individuals to help } solve problems will decrease in the older mailing lists. Plus, it forces } users to unsubscribe/resubscribe to the mailing lists (for example a user } upgrades to 2.2 form 2.1. He then needs to unsubscribes from the 2.1 mailing } list and is forced to resubscribe to 2.2.). Besides, the same questions will } be asked in multiple mailing lists, instead of just in one (stable). Also, } the development team dosen't have to track 3+ mailing lists, only 2). I'd keep the "current" mailing list, since there's always one of those, but I'd phase out the "stable" list. The problem is that there are currently two -stable branches and: When people post to the -stable list, they say they are running -stable, and their problem is ... It can sometimes take a while to figure out which -stable branch they're talking about. I'm currently following 2.1-stable, so all the folks who start using FreeBSD 2.2.x probably don't want my messages about 2.1 cluttering their inbox. As the number of users of 2.1 decrease, the traffic on it's list would also decrease, reducing the incentive for experienced users to unsubscribe. The only issue I see is how to populate the new list that is created when a branch is added. Probably the best thing to do is to announce the creation of the new list and let folks decide whether they want to subscribe or not. --- Truck From owner-freebsd-stable Wed Oct 8 17:10:23 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id RAA24616 for stable-outgoing; Wed, 8 Oct 1997 17:10:23 -0700 (PDT) (envelope-from owner-freebsd-stable) Received: from ns.mt.sri.com (SRI-56K-FR.mt.net [206.127.65.42]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id RAA24599 for ; Wed, 8 Oct 1997 17:10:15 -0700 (PDT) (envelope-from nate@rocky.mt.sri.com) Received: from rocky.mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by ns.mt.sri.com (8.8.7/8.8.7) with ESMTP id SAA05504; Wed, 8 Oct 1997 18:10:05 -0600 (MDT) Received: (from nate@localhost) by rocky.mt.sri.com (8.7.5/8.7.3) id SAA13568; Wed, 8 Oct 1997 18:10:00 -0600 (MDT) Date: Wed, 8 Oct 1997 18:10:00 -0600 (MDT) Message-Id: <199710090010.SAA13568@rocky.mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Wayne Self Cc: stable@freebsd.org Subject: Re: CVSup release identity In-Reply-To: <19971008153747.16093@baic.com> References: <971008155108_-1194179101@emout15.mail.aol.com> <199710081959.NAA12037@rocky.mt.sri.com> <19971008153747.16093@baic.com> X-Mailer: VM 6.29 under 19.15 XEmacs Lucid Sender: owner-freebsd-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Wayne Self writes: > > 1. Creation of a .timestamp file added to the source tree. > > How about this idea? > > We leave the "identity crisis" alone until 2.2.5 is released? The fact of the matter is that nothing will be implemented until after the release in any case. Nate From owner-freebsd-stable Wed Oct 8 17:13:06 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id RAA24785 for stable-outgoing; Wed, 8 Oct 1997 17:13:06 -0700 (PDT) (envelope-from owner-freebsd-stable) Received: from shrimp.dataplex.net (shrimp.dataplex.net [208.2.87.3]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id RAA24779 for ; Wed, 8 Oct 1997 17:13:03 -0700 (PDT) (envelope-from rkw@dataplex.net) Received: from [208.2.87.4] (user4.dataplex.net [208.2.87.4]) by shrimp.dataplex.net (8.8.5/8.8.5) with ESMTP id TAA09183; Wed, 8 Oct 1997 19:12:53 -0500 (CDT) X-Sender: rkw@mail.dataplex.net Message-Id: In-Reply-To: <199710082329.QAA06393@salsa.gv.tsc.tdk.com> References: Hetzels@aol.com "Re: CVSup release identity" (Oct 8, 12:01pm) Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Wed, 8 Oct 1997 19:14:08 -0500 To: Don Lewis From: Richard Wackerbarth Subject: Re: CVSup release identity Cc: stable@FreeBSD.ORG Sender: owner-freebsd-stable@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Don Lewis writes: >I'd keep the "current" mailing list, since there's always one of those, >but I'd phase out the "stable" list. My proposal would be to set up 2.1, 2.2, and 3.0 lists immediately. By announcement, etc. I would encourage EVERYONE to use the new designation. However, for legacy purposes, I would then make "stable" a mail alias for both 2.1 and 2.2. After a transition period, I would drop 2.1 from that alias. Eventually, we could "bounce" messages to "stable" with a note to post to either 2.1, 2.2, ... as appropriate. In a similar manner, I would make "current" an alias for 3.0. The initial membership of both 2.1 and 2.2 would be the present "stable" list. Participants would be notified to unsubscribe if they are not interested. The initial membership of 3.0 is the present "current" list. Each time that a new branch is officially created in the tree, I would create a new list for it. At that time, I would "seed" the list with everyone who was on the previous head list. Rather than calling the list associated with the head of the tree "current", I would chose a name such as "development" or "experimental". It would be created at the time of the 3.0 branch and, thereafter, be "permanent". Further branches would generate new lists 3.1, 4.0, etc. > The problem is that there are currently two -stable branches and: But there is only one "2.2" branch :-) Further, if you started running 2.2 before its first release, and are still running it, I see no reason why YOU should have to change lists. >The only issue I see is how to populate the new list that is created >when a branch is added. Clone the old list. Let people who don't want both unsubscribe. IMHO, it is better to send someone too much than to simply cut them off. One nice feature of this scheme is that when "stable" and "current" age into bounce status, they can supply customized messages directing the user to the appropriate list. "The current release of FreeBSD is 2.2.2. General questions should be addressed to ... Questions about the behavior of this particular release should be addressed to ..." Richard Wackerbarth From owner-freebsd-stable Wed Oct 8 17:23:46 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id RAA25301 for stable-outgoing; Wed, 8 Oct 1997 17:23:46 -0700 (PDT) (envelope-from owner-freebsd-stable) Received: from baic.com (router.baic.com [206.14.192.1]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id RAA25296 for ; Wed, 8 Oct 1997 17:23:42 -0700 (PDT) (envelope-from wself@baic.com) Received: (from wself@localhost) by baic.com (8.8.7/8.8.5) id RAA22237; Wed, 8 Oct 1997 17:30:15 GMT Message-ID: <19971008173013.16807@baic.com> Date: Wed, 8 Oct 1997 17:30:13 +0000 From: Wayne Self To: Nate Williams Cc: stable@freebsd.org Subject: Re: CVSup release identity References: <971008155108_-1194179101@emout15.mail.aol.com> <199710081959.NAA12037@rocky.mt.sri.com> <19971008153747.16093@baic.com> <199710090010.SAA13568@rocky.mt.sri.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.84 In-Reply-To: <199710090010.SAA13568@rocky.mt.sri.com>; from Nate Williams on Wed, Oct 08, 1997 at 06:10:00PM -0600 Sender: owner-freebsd-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk In reality, the fact of the matter is that the list is being cluttered with discussion of something that has _nothing_ to do with 2.2.5-BETA. - why waste time and energy in the beta phase playing with future releases? On Wed, Oct 08, 1997 at 06:10:00PM -0600, Nate Williams wrote: > > The fact of the matter is that nothing will be implemented until after > the release in any case. > > > Nate -- wayne ----------------------------------------------------------------------- From owner-freebsd-stable Wed Oct 8 17:40:55 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id RAA26175 for stable-outgoing; Wed, 8 Oct 1997 17:40:55 -0700 (PDT) (envelope-from owner-freebsd-stable) Received: from gatekeeper.tsc.tdk.com (root@gatekeeper.tsc.tdk.com [207.113.159.21]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id RAA26170 for ; Wed, 8 Oct 1997 17:40:53 -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.4/8.8.4) with ESMTP id RAA17916; Wed, 8 Oct 1997 17:40:41 -0700 (PDT) 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 RAA08079; Wed, 8 Oct 1997 17:40:40 -0700 (PDT) Received: (from gdonl@localhost) by salsa.gv.tsc.tdk.com (8.8.5/8.8.5) id RAA06632; Wed, 8 Oct 1997 17:40:39 -0700 (PDT) From: Don Lewis Message-Id: <199710090040.RAA06632@salsa.gv.tsc.tdk.com> Date: Wed, 8 Oct 1997 17:40:38 -0700 In-Reply-To: Richard Wackerbarth "Re: CVSup release identity" (Oct 8, 7:14pm) X-Mailer: Mail User's Shell (7.2.6 alpha(3) 7/19/95) To: Richard Wackerbarth , Don Lewis Subject: Re: CVSup release identity Cc: stable@FreeBSD.ORG Sender: owner-freebsd-stable@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Oct 8, 7:14pm, Richard Wackerbarth wrote: } Subject: Re: CVSup release identity } Don Lewis writes: } My proposal would be to set up 2.1, 2.2, and 3.0 lists immediately. } By announcement, etc. I would encourage EVERYONE to use the new } designation. However, for legacy purposes, I would then make "stable" } a mail alias for both 2.1 and 2.2. After a transition period, I would } drop 2.1 from that alias. Eventually, we could "bounce" messages to } "stable" with a note to post to either 2.1, 2.2, ... as appropriate. } In a similar manner, I would make "current" an alias for 3.0. } } The initial membership of both 2.1 and 2.2 would be the present "stable" list. } Participants would be notified to unsubscribe if they are not interested. } The initial membership of 3.0 is the present "current" list. Sounds reasonable. } Further, if you started running 2.2 before its first release, and are } still running it, I see no reason why YOU should have to change lists. True, unless you changed your supfile to track -current, in which case switching lists at the same time makes sense. } >The only issue I see is how to populate the new list that is created } >when a branch is added. } } Clone the old list. Let people who don't want both unsubscribe. IMHO, it } is better to send someone too much than to simply cut them off. That was my first thought, but I decided against it. I don't have a real strong opinion one way or another. --- Truck From owner-freebsd-stable Wed Oct 8 18:18:06 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id SAA28278 for stable-outgoing; Wed, 8 Oct 1997 18:18:06 -0700 (PDT) (envelope-from owner-freebsd-stable) Received: (from jmb@localhost) by hub.freebsd.org (8.8.7/8.8.7) id SAA28265; Wed, 8 Oct 1997 18:18:00 -0700 (PDT) (envelope-from jmb) From: "Jonathan M. Bresler" Message-Id: <199710090118.SAA28265@hub.freebsd.org> Subject: Re: CVSup release identity To: nate@mt.sri.com (Nate Williams) Date: Wed, 8 Oct 1997 18:17:59 -0700 (PDT) Cc: Hetzels@aol.com, nate@mt.sri.com, stable@freebsd.org In-Reply-To: <199710081903.NAA11742@rocky.mt.sri.com> from "Nate Williams" at Oct 8, 97 01:03:32 pm X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-freebsd-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Nate Williams wrote: > > > > I suggest spending less time arguing, and more time coming up with a > > > *solution*, and not a proposed solution. Changes to the tree, > > > newvers.sh, etc.... > > > > > We're trying to come up with the solution but it basically, involves three > > areas. > > 1. Creation of a .timestamp file added to the source tree. > > Sure, the only thing that's disagreed upon is the format of the > timestamp, and how often it's built. *THIS* is the crux of the matter, > and if you can come up with *something*, then the rest is politics. we need timestamps to track changes to the source. timestamp file is generated as a result of cvs commit. each commit changes the timestamp file. if 4 days go by without a commit ;) the timestamp file does not change timestamp is then incorporated into uname (hhmmm....every commit means a kernel recompile ;<) extend uname to write the timestamp into the kernel ala hostname. add this to /etc/rc.....??? doesnt matter how you get your bits, cvs ctm carrier pigeon. jmb From owner-freebsd-stable Wed Oct 8 19:54:20 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id TAA02750 for stable-outgoing; Wed, 8 Oct 1997 19:54:20 -0700 (PDT) (envelope-from owner-freebsd-stable) Received: from freebie.dcfinc.com (freebie.dcfinc.com [138.113.2.8]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id TAA02737; Wed, 8 Oct 1997 19:54:08 -0700 (PDT) (envelope-from chad@freebie.dcfinc.com) Received: (from chad@localhost) by freebie.dcfinc.com (8.8.3/8.8.3a) id TAA09758; Wed, 8 Oct 1997 19:53:24 -0700 (MST) From: "Chad R. Larson" Message-Id: <199710090253.TAA09758@freebie.dcfinc.com> Subject: Re: CVSup release identity To: jmb@FreeBSD.ORG (Jonathan M. Bresler) Date: Wed, 8 Oct 1997 19:53:23 -0700 (MST) Cc: nate@mt.sri.com, Hetzels@aol.com, stable@FreeBSD.ORG In-Reply-To: <199710090118.SAA28265@hub.freebsd.org> from "Jonathan M. Bresler" at "Oct 8, 97 06:17:59 pm" Reply-to: chad@dcfinc.com 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 X-Loop: FreeBSD.org Precedence: bulk > timestamp is then incorporated into uname > (hhmmm....every commit means a kernel recompile ;<) No, just every CVSup. -crl -- Chad R. Larson (CRL22) Brother, can you paradigm? 602-953-1392 chad@dcfinc.com chad@anasazi.com crl22@aol.com DCF, Inc. - 14523 North 49th Place, Scottsdale, Arizona 85254 From owner-freebsd-stable Wed Oct 8 23:08:20 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id XAA11026 for stable-outgoing; Wed, 8 Oct 1997 23:08:20 -0700 (PDT) (envelope-from owner-freebsd-stable) Received: from axe.cablenet.net (axe.cablenet.net [194.154.36.65]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id XAA11021 for ; Wed, 8 Oct 1997 23:08:17 -0700 (PDT) (envelope-from damian@axe.cablenet.net) Received: from axe (localhost [127.0.0.1]) by axe.cablenet.net (8.8.7/8.6.9) with SMTP id HAA05790; Thu, 9 Oct 1997 07:04:22 +0100 (BST) Message-ID: <343C73E6.2DDA173E@cablenet.net> Date: Thu, 09 Oct 1997 07:04:22 +0100 From: Damian Hamill Organization: CableNet Ltd X-Mailer: Mozilla 3.0 (X11; I; SunOS 4.1.4 sun4m) MIME-Version: 1.0 To: Mike Smith CC: freebsd-stable@freebsd.org Subject: Re: NFS Client option -- didn't take References: <199710081852.EAA01020@word.smith.net.au> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Mike Smith wrote: > > >From the oct 7'th beta, selecting NFS client during the installation > > didn't "take" in rc.conf. > > > > BTW, why is install modifying rc.conf instead of just writing the > > changes into rc.conf.local? > > Because rc.conf.local violates the entire purpose of rc.conf. The > default values for the variables in rc.conf are implicit in the rc.* > scripts; rc.conf is where you overried these defaults as you wish. > > mike There are a few problems with sysinstall and rc.conf though. I recently made a change using sysinstall (enabled NFS client & server) and all the lines in rc.conf had their comment appended again after the orignal comment and a double quotes i.e. nfs_client="NO" # enable nfs client became nfs_client="NO" # enable nfs client" enable nfs client I tend not to use sysinstall now and always edit rc.conf by hand. regards damian -- * Damian Hamill M.D. damian@cablenet.net * CableNet & The Landscape Channel * http://www.cablenet.net/ http://www.landscapetv.com/ From owner-freebsd-stable Thu Oct 9 01:50:30 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id BAA17974 for stable-outgoing; Thu, 9 Oct 1997 01:50:30 -0700 (PDT) (envelope-from owner-freebsd-stable) Received: from silvia.HIP.Berkeley.EDU (ala-ca8-03.ix.netcom.com [207.93.141.131]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id BAA17966; Thu, 9 Oct 1997 01:50:25 -0700 (PDT) (envelope-from asami@vader.cs.berkeley.edu) Received: (from asami@localhost) by silvia.HIP.Berkeley.EDU (8.8.7/8.6.9) id BAA04618; Thu, 9 Oct 1997 01:50:19 -0700 (PDT) Date: Thu, 9 Oct 1997 01:50:19 -0700 (PDT) Message-Id: <199710090850.BAA04618@silvia.HIP.Berkeley.EDU> To: bwithrow@BayNetworks.COM CC: freebsd-stable@FreeBSD.ORG, jkh@FreeBSD.ORG In-reply-to: <199710081704.NAA16759@tuva.engeast.baynetworks.com> (message from Robert Withrow on Wed, 08 Oct 1997 13:04:14 -0400) Subject: Re: Packages-2.2.5 is missing INDEX file From: asami@cs.berkeley.edu (Satoshi Asami) Sender: owner-freebsd-stable@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk * The ftp.freebsd.org mirror of packages-2.2.5 is missing the INDEX file... You're right. Jordan, can you set up the INDEX generation script to take care of that directory too? In case you forgot the routine, it should be copied over from ports-current/INDEX and then chopped up. Satoshi From owner-freebsd-stable Thu Oct 9 02:31:07 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id CAA19939 for stable-outgoing; Thu, 9 Oct 1997 02:31:07 -0700 (PDT) (envelope-from owner-freebsd-stable) Received: from emout07.mail.aol.com (emout07.mx.aol.com [198.81.11.22]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id CAA19934 for ; Thu, 9 Oct 1997 02:31:05 -0700 (PDT) (envelope-from Hetzels@aol.com) From: Hetzels@aol.com Received: (from root@localhost) by emout07.mail.aol.com (8.7.6/8.7.3/AOL-2.0.0) id FAA18481; Thu, 9 Oct 1997 05:30:33 -0400 (EDT) Date: Thu, 9 Oct 1997 05:30:33 -0400 (EDT) Message-ID: <971009053033_1565064832@emout07.mail.aol.com> To: nate@mt.sri.com cc: stable@freebsd.org Subject: Re: CVSup release identity Sender: owner-freebsd-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >> You've got the sources, go to it. :) (Hint, look at all the files in >> CVSROOT.) >> >$CVSROOT/CVSROOT/cvswrappers,v >$CVSROOT/CVSROOT/commitinfo,v >$CVSROOT/CVSROOT/modules,v Sorry, about this post. Acidently hit the wrong button. Was going to ask if the timestamp program goes into one of these as I currently don't have the CVSROOT on my computer. Tracking only via CTM. Scot From owner-freebsd-stable Thu Oct 9 02:57:31 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id CAA21135 for stable-outgoing; Thu, 9 Oct 1997 02:57:31 -0700 (PDT) (envelope-from owner-freebsd-stable) Received: from gate.mgt.msk.ru (mgtrep.24h.dialup.ru [194.87.18.139]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id CAA21125 for ; Thu, 9 Oct 1997 02:57:21 -0700 (PDT) (envelope-from tarkhil@mgt.msk.ru) Received: from asteroid.mgt.msk.ru (asteroid.mgt.msk.ru [192.168.133.145]) by gate.mgt.msk.ru (8.8.6/8.8.6) with ESMTP id NAA08385 for ; Thu, 9 Oct 1997 13:57:03 +0400 (MSD) Received: from asteroid.mgt.msk.ru (localhost.mgt.msk.ru [127.0.0.1]) by asteroid.mgt.msk.ru (8.8.7/8.8.6) with ESMTP id NAA01016 for ; Thu, 9 Oct 1997 13:56:36 +0400 (MSD) Message-Id: <199710090956.NAA01016@asteroid.mgt.msk.ru> To: stable@freebsd.org Reply-To: tarkhil@mgt.msk.ru Subject: panic: recursive lock in ufs boundary="==_Exmh_19534499960" Date: Thu, 09 Oct 1997 13:56:36 +0400 From: "Alexander B. Povolotsky" Sender: owner-freebsd-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk This is a multipart MIME message. --==_Exmh_19534499960 Content-Type: text/plain; charset=us-ascii Hello! I've attempted make release on machine like FreeBSD asteroid.mgt.msk.ru 2.2-STABLE FreeBSD 2.2-STABLE #0: Thu Oct 9 13:17:25 MSD 1997 root@asteroid.mgt.msk.ru:/net/unix/FreeBSD/src/sys/compile/ASTEROID i386 and it repeatedly crashed with "panic: recursive lock in ufs" during cpio or (in batch mode) df called from /usr/release/doFS.sf. Kernel config is attached. Maybe someone can help? --==_Exmh_19534499960 Content-Type: text/plain; name="ASTEROID"; charset=us-ascii Content-Description: ASTEROID Content-Disposition: attachment; filename="ASTEROID" machine "i386" ident ASTEROID maxusers 15 options CHILD_MAX=128 options OPEN_MAX=128 options INCLUDE_CONFIG_FILE # Include this file in kernel config kernel root on sd0 cpu "I586_CPU" # aka Pentium(tm) options "COMPAT_43" options SYSVSHM options SYSVSEM options SYSVMSG options "MD5" options UCONSOLE options USERCONFIG #boot -c editor options VISUAL_USERCONFIG #visual boot -c editor options INET #Internet communications protocols pseudo-device ether #Generic Ethernet pseudo-device loop #Network loopback device pseudo-device bpfilter 4 #Berkeley packet filter pseudo-device disc #Discard device pseudo-device tun 1 #Tunnel driver(user process ppp) options FFS #Fast filesystem options NFS #Network File System options "CD9660" #ISO 9660 filesystem options PROCFS #Process filesystem controller scbus0 #base SCSI code device ch0 #SCSI media changers device sd0 #SCSI disks device st0 #SCSI tapes device cd0 #SCSI CD-ROMs device worm0 at scbus? # SCSI worm device sctarg0 at scbus? # SCSI target pseudo-device pty 16 #Pseudo ttys - can go as high as 256 pseudo-device speaker #Play IBM BASIC-style noises out your speaker pseudo-device log #Kernel syslog interface (/dev/klog) pseudo-device gzip #Exec gzipped a.out's pseudo-device vn 2 #Vnode driver (turns a file into a device) pseudo-device snp 3 #Snoop device - to look at pty/vty/etc.. pseudo-device ccd 4 #Concatenated disk driver controller isa0 options "AUTO_EOI_1" device sc0 at isa0 port "IO_KBD" tty irq 1 flags 0xA vector scintr options MAXCONS=16 # number of virtual consoles device npx0 at isa0 port "IO_NPX" iosiz 0x0 flags 0x0 irq 13 vector npxintr controller wdc1 at isa0 port "IO_WD2" bio irq 15 vector wdintr options ATAPI #Enable ATAPI support for IDE bus options ATAPI_STATIC #Don't do it as an LKM device wcd0 controller fdc0 at isa0 port "IO_FD1" bio irq 6 drq 2 vector fdintr disk fd0 at fdc0 drive 0 device lpt0 at isa0 port? tty irq 7 vector lptintr device sio0 at isa0 port "IO_COM1" tty irq 4 vector siointr device sio1 at isa0 port "IO_COM2" tty irq 3 vector siointr device pca0 at isa0 port IO_TIMER1 tty controller pci0 controller ncr0 device fxp0 options COMPAT_LINUX options "SCSI_2_DEF" options SCSI_DELAY=8 # Be pessimistic about Joe SCSI device --==_Exmh_19534499960-- From owner-freebsd-stable Thu Oct 9 03:41:28 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id DAA23239 for stable-outgoing; Thu, 9 Oct 1997 03:41:28 -0700 (PDT) (envelope-from owner-freebsd-stable) Received: from gate.mgt.msk.ru (mgtrep.24h.dialup.ru [194.87.18.139]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id DAA23233 for ; Thu, 9 Oct 1997 03:41:19 -0700 (PDT) (envelope-from tarkhil@mgt.msk.ru) Received: from asteroid.mgt.msk.ru (asteroid.mgt.msk.ru [192.168.133.145]) by gate.mgt.msk.ru (8.8.6/8.8.6) with ESMTP id OAA08430 for ; Thu, 9 Oct 1997 14:41:03 +0400 (MSD) Received: from asteroid.mgt.msk.ru (localhost.mgt.msk.ru [127.0.0.1]) by asteroid.mgt.msk.ru (8.8.7/8.8.6) with ESMTP id OAA02333 for ; Thu, 9 Oct 1997 14:40:35 +0400 (MSD) Message-Id: <199710091040.OAA02333@asteroid.mgt.msk.ru> To: stable@freebsd.org Reply-To: tarkhil@mgt.msk.ru Subject: Version of FreeBSD for production server? Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 09 Oct 1997 14:40:34 +0400 From: "Alexander B. Povolotsky" Sender: owner-freebsd-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hello! I'll need very soon to set up production server (NFS/Appletalk file server will be it's main purpose). What version would you recommend me for maximum stability? Alex. From owner-freebsd-stable Thu Oct 9 06:42:20 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id GAA00607 for stable-outgoing; Thu, 9 Oct 1997 06:42:20 -0700 (PDT) (envelope-from owner-freebsd-stable) Received: from mailhost3.BayNetworks.COM (ns4.BayNetworks.COM [192.32.253.7]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id GAA00600 for ; Thu, 9 Oct 1997 06:42:12 -0700 (PDT) (envelope-from bwithrow@BayNetworks.COM) Received: from ns5.BayNetworks.COM (fw1.corpeast.baynetworks.com [192.32.253.1]) by mailhost3.BayNetworks.COM (8.8.6/BNET-97/07/07-E) with ESMTP id JAA13385; Thu, 9 Oct 1997 09:50:49 -0400 (EDT) for Posted-Date: Thu, 9 Oct 1997 09:50:49 -0400 (EDT) Received: from pobox.engeast.BayNetworks.COM (pobox.corpeast.baynetworks.com [192.32.151.199]) by ns5.BayNetworks.COM (8.8.6/8.8.6) with ESMTP id PAA27403 for ; Thu, 9 Oct 1997 15:37:18 +0200 (MET DST) Received: from tuva.engeast.baynetworks.com (tuva [192.32.180.119]) by pobox.engeast.BayNetworks.COM (SMI-8.6/BNET-97/04/24-S) with ESMTP id JAA28515; Thu, 9 Oct 1997 09:40:59 -0400 for Received: from tuva.engeast.baynetworks.com (localhost [127.0.0.1]) by tuva.engeast.baynetworks.com (8.8.3/8.8.3) with ESMTP id JAA19577 for ; Thu, 9 Oct 1997 09:40:59 -0400 (EDT) Message-Id: <199710091340.JAA19577@tuva.engeast.baynetworks.com> X-Mailer: exmh version 2.0gamma 1/27/96 To: freebsd-stable@FreeBSD.ORG Subject: Re: NFS Client option -- didn't take In-reply-to: Your message of "Thu, 09 Oct 1997 07:04:22 BST." <343C73E6.2DDA173E@cablenet.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 09 Oct 1997 09:40:58 -0400 From: Robert Withrow Sender: owner-freebsd-stable@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk damian@cablenet.net said: :- There are a few problems with sysinstall and rc.conf though. :- I tend not to use sysinstall now and always edit rc.conf by hand. This is what is bothering me. I want to widely deply 2.2.5 here, but I will have a support nightmare if everytime a user uses sysinstall it clobbers some critical aspect of the config. I already have this problem because sysinstall changes '' quoting in rc.conf to "" quoting, which breaks my config. I'm just trying to find something that I can depend on for wide distribution here. -- Robert Withrow -- (+1 508 916 8256) BWithrow@BayNetworks.com From owner-freebsd-stable Thu Oct 9 07:36:17 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id HAA03762 for stable-outgoing; Thu, 9 Oct 1997 07:36:17 -0700 (PDT) (envelope-from owner-freebsd-stable) Received: from silent.darkening.com (nonxstnt@iskh122.haninge.kth.se [130.237.83.122]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id HAA03730 for ; Thu, 9 Oct 1997 07:36:07 -0700 (PDT) (envelope-from nonxstnt@darkening.com) Received: from localhost (nonxstnt@localhost) by silent.darkening.com (8.8.7/8.8.7) with SMTP id QAA19989 for ; Thu, 9 Oct 1997 16:36:04 +0200 (CEST) Date: Thu, 9 Oct 1997 16:36:04 +0200 (CEST) From: nobody To: freebsd-stable@freebsd.org Subject: stable broken? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from QUOTED-PRINTABLE to 8bit by hub.freebsd.org id HAA03741 Sender: owner-freebsd-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I cvsupped about 30 minutes ago... cc -O -Wall -I/usr/src/lib/libvgl -c main.c -o main.o main.c: In function `VGLInit': main.c:131: `SW_VGA_MODEX' undeclared (first use this function) main.c:131: (Each undeclared identifier is reported only once main.c:131: for each function it appears in.) main.c: In function `VGLCheckSwitch': main.c:207: `SW_VGA_MODEX' undeclared (first use this function) *** Error code 1 any words of advice? --- thomas strömberg . system admin, royal institute of technology (stockholm) nobody@darkening.com . irc:nobody@EFnet . talk:nonxstnt@silent.darkening.com real coders don't use comments. It was hard to write; it should be hard to read From owner-freebsd-stable Thu Oct 9 07:57:52 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id HAA04974 for stable-outgoing; Thu, 9 Oct 1997 07:57:52 -0700 (PDT) (envelope-from owner-freebsd-stable) Received: from serf.xlrn.ucsb.edu (serf.xlrn.ucsb.edu [128.111.170.250]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id HAA04965 for ; Thu, 9 Oct 1997 07:57:42 -0700 (PDT) (envelope-from matt@xlrn.ucsb.edu) Received: from localhost (matt@localhost) by serf.xlrn.ucsb.edu (8.8.7/8.8.5) with SMTP id HAA00582; Thu, 9 Oct 1997 07:57:36 -0700 (PDT) Date: Thu, 9 Oct 1997 07:57:36 -0700 (PDT) From: Matthew M Groener To: stable@FreeBSD.ORG Subject: out of mbuf crash In-Reply-To: <199710090010.SAA13568@rocky.mt.sri.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk I have a consistent crash in 2.2.2 on Thursdays with the following last message in /var/log/messages: Sep 20 05:26:44 serf /kernel: Out of mbuf clusters - increase maxusers! Oct 2 05:23:58 serf /kernel: Out of mbuf clusters - increase maxusers! Sep 13 05:10:32 serf /kernel.old.old: Out of mbuf clusters - increase maxusers! Sep 4 04:07:50 serf /kernel: Out of mbuf clusters - increase maxusers! Oct 9 05:29:09 serf /kernel: Out of mbuf clusters - increase maxusers! I have checked that nothing unusual begins anywhere near this time in cron (users or root), and yet it's nearly consistent. I have increased maxusers in the kernel to 128 without success. Could this be a runaway process which continuously spawns processes (sometime before the crash time), until it runs out of mbuf space? I can check for processes Thursday morning, hoping to find them before I crash. Lastly, I am witholding migration to 2.2.5 until I hear word that netatalk works again (since I rely on this heavily). Any suggestions would be much appreciated. Cheers, -matt ------------------------------------------------------------------------ Matthew M. Groener, Systems Manager Phone: (805) 893-4906 U of C Santa Barbara Extension Pager: (805) 882-6170 matt@xlrn.ucsb.edu http://www.xlrn.ucsb.edu Fax: (805) 893-4943 ------------ "A radioactive cat has eighteen half-lives." From owner-freebsd-stable Thu Oct 9 08:01:50 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id IAA05225 for stable-outgoing; Thu, 9 Oct 1997 08:01:50 -0700 (PDT) (envelope-from owner-freebsd-stable) Received: from helios.whro.org (ns1162.whro.org [198.76.162.2]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id IAA05210 for ; Thu, 9 Oct 1997 08:01:43 -0700 (PDT) (envelope-from bboone@whro.org) Received: from blueprint.whro.org (lunar-107.whro.org [198.76.164.107]) by helios.whro.org (8.8.5/8.8.5) with SMTP id KAA22108; Thu, 9 Oct 1997 10:58:09 -0400 (EDT) Date: Thu, 9 Oct 1997 10:58:09 -0400 (EDT) Message-Id: <199710091458.KAA22108@helios.whro.org> X-Sender: bboone@mail.whro.org X-Mailer: Windows Eudora Light Version 1.5.2 Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" To: freebsd-stable@FreeBSD.ORG From: Bob Boone Subject: CVS and Popper.... Cc: bboone@virtualbob.com Sender: owner-freebsd-stable@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk I want to update from 2.2 release (july) to -stable, and to add qpop so I can get my mail out of the server more easily, SYSINSTALL has lots of ports -- but not the qpop 1.2.4 listed in the text of the website, nor Apache 1.2.4, nor any convenient way to get the CVS "port". When I tried to access the CVS port thru the hyperlink in the 16.3.2.2 Installation text (handbook) I got DNS or directory errors. Is this a temporary thing related to the code freeze, some other magic, or (dare I say) operator error ???? > > > > > Bob Bob Boone, Chief Engineer for Television WHRO-TV/FM 5200 Hampton Blvd. Norfolk, Va. 23508 Pager: (757) 860-3303 *** Ph: (757) 889-9466 *** Fx: (757) 489-4444 Internet: bboone@whro.org WebSite: http://www.whro.org ===================================================================== From owner-freebsd-stable Thu Oct 9 09:13:50 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id JAA09171 for stable-outgoing; Thu, 9 Oct 1997 09:13:50 -0700 (PDT) (envelope-from owner-freebsd-stable) Received: from ucet.ufl.edu (ronell.ucet.ufl.edu [128.227.243.237]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id JAA09166 for ; Thu, 9 Oct 1997 09:13:45 -0700 (PDT) (envelope-from northrup@ucet.ufl.edu) Received: from localhost (northrup@localhost) by ucet.ufl.edu (8.7.5/8.6.9) with SMTP id MAA38610 for ; Thu, 9 Oct 1997 12:13:33 -0400 Date: Thu, 9 Oct 1997 12:13:32 -0400 (EDT) From: Dylan Northrup To: stable@freebsd.org Subject: password question Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk We're intending on putting a FreeBSD box into production along some AIX boxes. Is there some sort of way that we can get compatability between the password generated by FreeBSD and the passwords on the AIX boxen? Currently we rdist the password files to the various machines. Previously we used yp/NIS, however the password maps were compromised and the idea of using NIS around here again has not been well received. Are they any ideas that would help with this problem (and, no, we can't just depricate the AIX boxes, no matter how much I'd love to)? -- Dylan Northrup <*> northrup@ucet.ufl.edu <*> http://www.ucet.ufl.edu/~northrup <*> --------------- Random B5 Quote "Sometimes you have to heal the family before you heal the patient." -- Dr. Franklin, "Believers" From owner-freebsd-stable Thu Oct 9 10:16:42 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id KAA13500 for stable-outgoing; Thu, 9 Oct 1997 10:16:42 -0700 (PDT) (envelope-from owner-freebsd-stable) Received: from freebie.dcfinc.com (freebie.dcfinc.com [138.113.2.8]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id KAA13475 for ; Thu, 9 Oct 1997 10:16:32 -0700 (PDT) (envelope-from chad@freebie.dcfinc.com) Received: (from chad@localhost) by freebie.dcfinc.com (8.8.3/8.8.3a) id KAA10548; Thu, 9 Oct 1997 10:14:05 -0700 (MST) From: "Chad R. Larson" Message-Id: <199710091714.KAA10548@freebie.dcfinc.com> Subject: Re: Version of FreeBSD for production server? To: tarkhil@mgt.msk.ru Date: Thu, 9 Oct 1997 10:14:03 -0700 (MST) Cc: stable@FreeBSD.ORG In-Reply-To: <199710091040.OAA02333@asteroid.mgt.msk.ru> from "Alexander B. Povolotsky" at "Oct 9, 97 02:40:34 pm" Reply-to: chad@dcfinc.com 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 X-Loop: FreeBSD.org Precedence: bulk > I'll need very soon to set up production server (NFS/Appletalk file server > will be it's main purpose). What version would you recommend me for maximum > stability? For maximum stablility, I'd recommend 2.1.7-RELEASE, or 2.1-STABLE. We've got machines that have never crashed or hung up. Uptime is controlled by operational needs for reboots. This one, for example: +--------------- | chad> uname -a | FreeBSD freebie.dcfinc.com 2.1-STABLE FreeBSD 2.1-STABLE #0: | Wed May 21 21:44:12 MST 1997 | chad@freefall.anasazi.com:/usr/src/sys/compile/FREEBIE i386 | | chad> uptime | 10:11AM up 133 days, 20:51, 1 user, load averages: 0.12, 0.07, 0.02 +--------------- > Alex. -crl -- Chad R. Larson (CRL22) Brother, can you paradigm? 602-953-1392 chad@dcfinc.com chad@anasazi.com crl22@aol.com DCF, Inc. - 14523 North 49th Place, Scottsdale, Arizona 85254 From owner-freebsd-stable Thu Oct 9 10:24:37 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id KAA14047 for stable-outgoing; Thu, 9 Oct 1997 10:24:37 -0700 (PDT) (envelope-from owner-freebsd-stable) Received: from GndRsh.aac.dev.com (GndRsh.aac.dev.com [198.145.92.241]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id KAA14039 for ; Thu, 9 Oct 1997 10:24:34 -0700 (PDT) (envelope-from rgrimes@GndRsh.aac.dev.com) Received: (from rgrimes@localhost) by GndRsh.aac.dev.com (8.8.5/8.7.3) id KAA03852; Thu, 9 Oct 1997 10:23:37 -0700 (PDT) From: "Rodney W. Grimes" Message-Id: <199710091723.KAA03852@GndRsh.aac.dev.com> Subject: Re: CVSUP vs. SNAPS In-Reply-To: <3107.876152040@time.cdrom.com> from "Jordan K. Hubbard" at "Oct 6, 97 08:34:00 am" To: jkh@time.cdrom.com (Jordan K. Hubbard) Date: Thu, 9 Oct 1997 10:23:36 -0700 (PDT) Cc: jfarmer@sabre.goldsword.com, kkennawa@physics.adelaide.edu.au, andrsn@andrsn.stanford.edu, dg@root.com, freebsd-stable@FreeBSD.ORG, jfarmer@goldsword.com X-Mailer: ELM [version 2.4ME+ PL25 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > Rod, give *me* a break. Done. I'll commit the corrections after you release the the Release Engineering lock on the RELENG_2_2 branch. -- Rod Grimes rgrimes@gndrsh.aac.dev.com Accurate Automation, Inc. Reliable computers for FreeBSD From owner-freebsd-stable Thu Oct 9 10:33:11 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id KAA14646 for stable-outgoing; Thu, 9 Oct 1997 10:33:11 -0700 (PDT) (envelope-from owner-freebsd-stable) Received: from GndRsh.aac.dev.com (GndRsh.aac.dev.com [198.145.92.241]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id KAA14637 for ; Thu, 9 Oct 1997 10:33:07 -0700 (PDT) (envelope-from rgrimes@GndRsh.aac.dev.com) Received: (from rgrimes@localhost) by GndRsh.aac.dev.com (8.8.5/8.7.3) id KAA03880; Thu, 9 Oct 1997 10:32:41 -0700 (PDT) From: "Rodney W. Grimes" Message-Id: <199710091732.KAA03880@GndRsh.aac.dev.com> Subject: Re: Fwd: CVSup release identity In-Reply-To: from Richard Wackerbarth at "Oct 6, 97 01:39:02 pm" To: rkw@dataplex.net (Richard Wackerbarth) Date: Thu, 9 Oct 1997 10:32:41 -0700 (PDT) Cc: murray@cdrom.com, stable@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL25 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > >On Mon, 6 Oct 1997, Richard Wackerbarth wrote: > >% Well, I would still get rid of the "-STABLE". I would also use Zulu time > >% and convert it all to a number. Thus > > > >Then what about -CURRENT?! -STABLE needs to stay there. > > No, it does not! You're only looking at 2 of many values, your making your decision based upon incomplete information. Values of ``BRANCH'' (to be renamed FLAVOR after the 2.2.5 release) are ALPHA, BETA, ..., RELEASE, STABLE, CURRENT. Now, tell me it can go away since you now have all the information and I't will after the 2.2.5 release. > The "current" branch is presently called "3.0". Okay, I'll buy that, it means we can set FLAVOR == CURRENT instead of FLAVOR == STABLE on the RELENG_2_1 and RELENG_2_2 branches. Now is that ever going to confuse the shit out of users :-) -- Rod Grimes rgrimes@gndrsh.aac.dev.com Accurate Automation, Inc. Reliable computers for FreeBSD From owner-freebsd-stable Thu Oct 9 11:10:02 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id LAA16995 for stable-outgoing; Thu, 9 Oct 1997 11:10:02 -0700 (PDT) (envelope-from owner-freebsd-stable) Received: from mail.uniserve.com (dns1-van.uniserve.com [204.244.163.48]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id LAA16937 for ; Thu, 9 Oct 1997 11:09:53 -0700 (PDT) (envelope-from tom@uniserve.com) Received: from shell.uniserve.com [204.244.210.252] by mail.uniserve.com with smtp (Exim 1.70 #1) id 0xJN1T-00031l-00; Thu, 9 Oct 1997 11:09:19 -0700 Date: Thu, 9 Oct 1997 11:09:16 -0700 (PDT) From: Tom To: chad@dcfinc.com cc: tarkhil@mgt.msk.ru, stable@freebsd.org Subject: Re: Version of FreeBSD for production server? In-Reply-To: <199710091714.KAA10548@freebie.dcfinc.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Thu, 9 Oct 1997, Chad R. Larson wrote: > > I'll need very soon to set up production server (NFS/Appletalk file server > > will be it's main purpose). What version would you recommend me for maximum > > stability? > > For maximum stablility, I'd recommend 2.1.7-RELEASE, or 2.1-STABLE. > We've got machines that have never crashed or hung up. Uptime is > controlled by operational needs for reboots. Except that netatalk hasn't been integrated 2.1. Deploying new 2.1 servers is like trapping yourself into a dead end. The 2.1 branch is not maintained very much, so you will have to patch yourself. What this means is that I'm not hurry to upgrade 2.1 systems, but anything new is 2.2 > This one, for example: > > +--------------- > | chad> uname -a > | FreeBSD freebie.dcfinc.com 2.1-STABLE FreeBSD 2.1-STABLE #0: > | Wed May 21 21:44:12 MST 1997 > | chad@freefall.anasazi.com:/usr/src/sys/compile/FREEBIE i386 > | > | chad> uptime > | 10:11AM up 133 days, 20:51, 1 user, load averages: 0.12, 0.07, 0.02 > +--------------- From a 2.2-stable system (P5-166): 11:01AM up 124 days, 20:41, 8 users, load averages: 0.08, 0.04, 0.00 This system operates as shell server for a bunch of users, some who run IRC bots and what not, so it gets abused pretty good. I need 2.2 on this system, because of the login.conf stuff, so I can impose CPU limits. > > Alex. > > -crl > -- > Chad R. Larson (CRL22) Brother, can you paradigm? > 602-953-1392 chad@dcfinc.com chad@anasazi.com crl22@aol.com > DCF, Inc. - 14523 North 49th Place, Scottsdale, Arizona 85254 > > Tom From owner-freebsd-stable Thu Oct 9 11:29:31 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id LAA18371 for stable-outgoing; Thu, 9 Oct 1997 11:29:31 -0700 (PDT) (envelope-from owner-freebsd-stable) Received: from helium.vapornet.com (root@helium.vapornet.com [208.202.126.112]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id LAA18366 for ; Thu, 9 Oct 1997 11:29:28 -0700 (PDT) (envelope-from john@helium.vapornet.com) Received: from argon.vapornet.com (vapornet.xnet.com [205.243.141.107]) by helium.vapornet.com (8.8.7/VaporServer-v3.0+SpamNot) with ESMTP id NAA11407; Thu, 9 Oct 1997 13:29:23 -0500 (CDT) Received: by argon.vapornet.com (8.8.7/VaporClient-1.1) id NAA07393; Thu, 9 Oct 1997 13:29:18 -0500 (CDT) Date: Thu, 9 Oct 1997 13:29:18 -0500 (CDT) Message-Id: <199710091829.NAA07393@argon.vapornet.com> From: John Preisler MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: chad@dcfinc.com Cc: tarkhil@mgt.msk.ru, stable@FreeBSD.ORG Subject: Re: Version of FreeBSD for production server? In-Reply-To: <199710091714.KAA10548@freebie.dcfinc.com> References: <199710091040.OAA02333@asteroid.mgt.msk.ru> <199710091714.KAA10548@freebie.dcfinc.com> X-Mailer: VM 6.22 under 19.15 XEmacs Lucid Sender: owner-freebsd-stable@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk netatalk requires a 2.2 kernel. -jrp Chad R. Larson writes: > > I'll need very soon to set up production server (NFS/Appletalk file server > > will be it's main purpose). What version would you recommend me for maximum > > stability? > > For maximum stablility, I'd recommend 2.1.7-RELEASE, or 2.1-STABLE. > We've got machines that have never crashed or hung up. Uptime is > controlled by operational needs for reboots. > > This one, for example: > > +--------------- > | chad> uname -a > | FreeBSD freebie.dcfinc.com 2.1-STABLE FreeBSD 2.1-STABLE #0: > | Wed May 21 21:44:12 MST 1997 > | chad@freefall.anasazi.com:/usr/src/sys/compile/FREEBIE i386 > | > | chad> uptime > | 10:11AM up 133 days, 20:51, 1 user, load averages: 0.12, 0.07, 0.02 > +--------------- > > > Alex. > > -crl > -- > Chad R. Larson (CRL22) Brother, can you paradigm? > 602-953-1392 chad@dcfinc.com chad@anasazi.com crl22@aol.com > DCF, Inc. - 14523 North 49th Place, Scottsdale, Arizona 85254 > From owner-freebsd-stable Thu Oct 9 11:49:07 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id LAA19829 for stable-outgoing; Thu, 9 Oct 1997 11:49:07 -0700 (PDT) (envelope-from owner-freebsd-stable) Received: from mail.uniserve.com (dns1-van.uniserve.com [204.244.163.48]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id LAA19824 for ; Thu, 9 Oct 1997 11:49:02 -0700 (PDT) (envelope-from tom@uniserve.com) Received: from shell.uniserve.com [204.244.210.252] by mail.uniserve.com with smtp (Exim 1.70 #1) id 0xJNde-0003Bh-00; Thu, 9 Oct 1997 11:48:46 -0700 Date: Thu, 9 Oct 1997 11:48:43 -0700 (PDT) From: Tom To: Dylan Northrup cc: stable@freebsd.org Subject: Re: password question In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Thu, 9 Oct 1997, Dylan Northrup wrote: > We're intending on putting a FreeBSD box into production along some AIX > boxes. Is there some sort of way that we can get compatability between > the password generated by FreeBSD and the passwords on the AIX boxen? What kind of passwords does AIX use? If it DES, you're set. > Currently we rdist the password files to the various machines. Previously > we used yp/NIS, however the password maps were compromised and the idea of > using NIS around here again has not been well received. You have to setup NIS carefully. NIS should only be used within a trusted cluster of machines, with no physical access for anyone except admins. FreeBSD NIS has some additional security stuff in it, but you have to disable them for compat with other systems. > Are they any ideas that would help with this problem (and, no, we can't > just depricate the AIX boxes, no matter how much I'd love to)? > > -- > Dylan Northrup <*> > northrup@ucet.ufl.edu <*> > http://www.ucet.ufl.edu/~northrup <*> > > --------------- > Random B5 Quote > "Sometimes you have to heal the family before you heal the patient." > -- Dr. Franklin, "Believers" Tom From owner-freebsd-stable Thu Oct 9 11:50:42 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id LAA19989 for stable-outgoing; Thu, 9 Oct 1997 11:50:42 -0700 (PDT) (envelope-from owner-freebsd-stable) Received: from mystique.hunter.com (mail.hunter.com [199.217.245.230] (may be forged)) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id LAA19974 for ; Thu, 9 Oct 1997 11:50:30 -0700 (PDT) (envelope-from KHamilton@Hunter.COM) Received: by mystique.hunter.com with Internet Mail Service (5.0.1458.49) id ; Thu, 9 Oct 1997 13:49:53 -0500 Message-ID: <92BD86195CB3D011832F0000C052D9E324665E@mystique.hunter.com> From: "Hamilton, Kent" To: Robert Luce , freebsd-stable@FreeBSD.ORG Subject: RE: can't compile beta Date: Thu, 9 Oct 1997 13:49:51 -0500 X-Priority: 3 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.0.1458.49) 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 LAA19975 Sender: owner-freebsd-stable@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk I'm also seeing this one. Anyone else? -- Kent Hamilton Work: KHamilton@Hunter.COM Sr Systems Admin URL: http://www.hunter.com/ Hunter Engineering Co. Home: KentH@HNS.St-Louis.Mo.US NIC Handle: KH91 URL: http://www2.hunter.com/~skh/ > -----Original Message----- > From: Robert Luce [SMTP:rwl@gymnet.com] > Sent: Wednesday, October 08, 1997 12:20 AM > To: freebsd-stable@FreeBSD.ORG > Subject: can't compile beta > > I cvsupped the latest source (tag=RELENG_2_2) 10/7/97 21:00 PDT and > am getting the following compile error in the 2940UW support code: > > make -f ../../dev/aic7xxx/Makefile MAKESRCPATH=../../dev/aic7xxx > Warning: Object directory not changed from original > /usr/src/sys/compile/BICEPS > yacc -d ../../dev/aic7xxx/aicasm_gram.y > mv y.tab.c aicasm_gram.c > cc -O -I. -c aicasm_gram.c > lex -t ../../dev/aic7xxx/aicasm_scan.l > aicasm_scan.c > cc -O -I. -c aicasm_scan.c > ../../dev/aic7xxx/aicasm_scan.l: In function `yylex': > ../../dev/aic7xxx/aicasm_scan.l:68: `T_DOWNLOAD' undeclared (first use > this func > tion) > ../../dev/aic7xxx/aicasm_scan.l:68: (Each undeclared identifier is > reported only > once > ../../dev/aic7xxx/aicasm_scan.l:68: for each function it appears in.) > *** Error code 1 > > Stop. > *** Error code 1 > > Stop. > > ---- > Bob Luce "Il faut supporter deux ou trois > chenilles > System/News Administrator si on veut connaître les > papillons.." > - Antoine de > Saint-Exupéry > Finger rwl@gymnet.com for PGP Public Key Block From owner-freebsd-stable Thu Oct 9 11:55:09 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id LAA20508 for stable-outgoing; Thu, 9 Oct 1997 11:55:09 -0700 (PDT) (envelope-from owner-freebsd-stable) Received: from shrimp.dataplex.net (shrimp.dataplex.net [208.2.87.3]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id LAA20499 for ; Thu, 9 Oct 1997 11:55:04 -0700 (PDT) (envelope-from rkw@dataplex.net) Received: from [204.69.236.50] (GATEWAY.SKIPSTONE.COM [198.214.10.129]) by shrimp.dataplex.net (8.8.5/8.8.5) with ESMTP id NAA00551; Thu, 9 Oct 1997 13:54:18 -0500 (CDT) X-Sender: rkw@mail.dataplex.net Message-Id: In-Reply-To: <199710091732.KAA03880@GndRsh.aac.dev.com> References: from Richard Wackerbarth at "Oct 6, 97 01:39:02 pm" Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Thu, 9 Oct 1997 13:53:48 -0500 To: "Rodney W. Grimes" From: Richard Wackerbarth Subject: Re: Fwd: CVSup release identity Cc: stable@FreeBSD.ORG Sender: owner-freebsd-stable@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >> >On Mon, 6 Oct 1997, Richard Wackerbarth wrote: >You're only looking at 2 of many values, your making your decision based >upon incomplete information. Values of ``BRANCH'' (to be renamed FLAVOR >after the 2.2.5 release) are ALPHA, BETA, ..., RELEASE, STABLE, CURRENT. I view it in a slightly different manner. I agree that ``BRANCH'' is a poor term. I think that we agree that the BRANCHes are really 2.1, 2.2, 3.0, etc. I also agree that there are values other than STABLE and CURRENT. However, these values represent a PHASE of development. For example, Development (pre-release) Alpha (testing) Beta Released Patched might be terms that describe the situation. (I'm not arguing the names, just look at the concept). The important thing is that any given branch can have only one phase at any given time. Further, there is fundamentally nothing sacred about the transition from one phase to another. If you have continuous access to the development tree, the quality of the code immediately before the transition is the same as it is immediately after the transition. The only thing that is important about the phase is that there are some implied expectations and protocol restrictions on the developers which are organizational policy. In addition, there are certain snapshots of the development progression. These are called releases. Someone packages them up and distributes them to users. These users cannot change them (without creating something else which is no longer the same and therefore should not have the same name). Anyone who assembles a system between these named snapshots simply has a version of the branch based on its contents at the time the snapshot was extracted. The development phase is not important. Only the point on the development timeline matters. (Did you build your system from sources that were extracted before or after some change that was introduced at xxxxx?) >Now, tell me it can go away since you now have all the information and >I't will after the 2.2.5 release. > >> The "current" branch is presently called "3.0". > >Okay, I'll buy that, it means we can set FLAVOR == CURRENT instead of >FLAVOR == STABLE on the RELENG_2_1 and RELENG_2_2 branches. Now is that >ever going to confuse the shit out of users :-) Yep! Anyone who builds a system from the head of a branch is building the "current" version of THAT branch (current as of a particular time). In this context, "CURRENT" is meaningless. Rather, we should be DELETING both of these designations. The only value in identifying a non-release system with anything other than the timestamp is that it may be easier to remember that a change occured between a pair of named releases rather than remembering that exactly when it occurred. However, this only helps to exclude systems that fall outside the named bounds. Between the bounds, you still have to look to the more specific timestamp. My proposed nomenclature is to designate the branch, the last release tag along that branch, and the timestamp of the extraction. Communication about a particular branch would be identified by the branch and not by the flavor. I can see it now. As we are in aa alpha period, all discussion should be on the "alpha" mailing list. Next week, please move the discussion to the "beta" list... I don't think so. If we were a much larger organization and the "users" had access to ONLY the released versions of development, you might make an argument for it. However, we are too small and everyone has access to "today's" version. One list per branch should be sufficient. Richard Wackerbarth From owner-freebsd-stable Thu Oct 9 12:40:24 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id MAA23867 for stable-outgoing; Thu, 9 Oct 1997 12:40:24 -0700 (PDT) (envelope-from owner-freebsd-stable) Received: from mx3.cso.uiuc.edu (mx3.cso.uiuc.edu [128.174.5.24]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id MAA23853 for ; Thu, 9 Oct 1997 12:40:19 -0700 (PDT) (envelope-from igor@alecto.physics.uiuc.edu) Received: from alecto.physics.uiuc.edu (alecto.physics.uiuc.edu [128.174.83.167]) by mx3.cso.uiuc.edu (8.8.7/8.8.7) with SMTP id OAA18621; Thu, 9 Oct 1997 14:39:47 -0500 (CDT) Received: by alecto.physics.uiuc.edu (940816.SGI.8.6.9/940406.SGI) id OAA18393; Thu, 9 Oct 1997 14:34:07 -0500 From: igor@alecto.physics.uiuc.edu (Igor Roshchin) Message-Id: <199710091934.OAA18393@alecto.physics.uiuc.edu> Subject: Re: Version of FreeBSD for production server? To: chad@dcfinc.com Date: Thu, 9 Oct 1997 14:34:06 -0500 (CDT) Cc: tarkhil@mgt.msk.ru, stable@FreeBSD.ORG In-Reply-To: <199710091714.KAA10548@freebie.dcfinc.com> from "Chad R. Larson" at Oct 9, 97 10:14:03 am X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-freebsd-stable@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk If you have ADAPTEC-2940, AFAIK, 2.2 has all the problems solved, while 2.1.7-RELEASE (and to the best of my knowledhe, 2.1-STABLE) still have them unsolved. I think though, the original question was rather about different stages of 2.2*[.-]* IgoR > > > I'll need very soon to set up production server (NFS/Appletalk file server > > will be it's main purpose). What version would you recommend me for maximum > > stability? > > For maximum stablility, I'd recommend 2.1.7-RELEASE, or 2.1-STABLE. > We've got machines that have never crashed or hung up. Uptime is > controlled by operational needs for reboots. > > This one, for example: > > +--------------- > | chad> uname -a > | FreeBSD freebie.dcfinc.com 2.1-STABLE FreeBSD 2.1-STABLE #0: > | Wed May 21 21:44:12 MST 1997 > | chad@freefall.anasazi.com:/usr/src/sys/compile/FREEBIE i386 > | > | chad> uptime > | 10:11AM up 133 days, 20:51, 1 user, load averages: 0.12, 0.07, 0.02 > +--------------- > > > Alex. > > -crl > -- > Chad R. Larson (CRL22) Brother, can you paradigm? > 602-953-1392 chad@dcfinc.com chad@anasazi.com crl22@aol.com > DCF, Inc. - 14523 North 49th Place, Scottsdale, Arizona 85254 > From owner-freebsd-stable Thu Oct 9 13:27:53 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id NAA27042 for stable-outgoing; Thu, 9 Oct 1997 13:27:53 -0700 (PDT) (envelope-from owner-freebsd-stable) Received: from ls.wustl.edu (ls.wustl.edu [128.252.251.249]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id NAA27036 for ; Thu, 9 Oct 1997 13:27:47 -0700 (PDT) (envelope-from drbrowns@ls.wustl.edu) Received: from localhost (drbrowns@localhost) by ls.wustl.edu (8.8.5/8.7.3) with SMTP id PAA11928; Thu, 9 Oct 1997 15:27:38 -0500 (CDT) Date: Thu, 9 Oct 1997 15:27:37 -0500 (CDT) From: "Daniel R. Brownstone" To: "Hamilton, Kent" cc: Robert Luce , freebsd-stable@FreeBSD.ORG Subject: RE: can't compile beta In-Reply-To: <92BD86195CB3D011832F0000C052D9E324665E@mystique.hunter.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from QUOTED-PRINTABLE to 8bit by hub.freebsd.org id NAA27037 Sender: owner-freebsd-stable@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Yes, I've received the same message. On Thu, 9 Oct 1997, Hamilton, Kent wrote: > I'm also seeing this one. Anyone else? > > -- > Kent Hamilton Work: KHamilton@Hunter.COM > Sr Systems Admin URL: http://www.hunter.com/ > Hunter Engineering Co. Home: KentH@HNS.St-Louis.Mo.US > NIC Handle: KH91 URL: http://www2.hunter.com/~skh/ > > > -----Original Message----- > > From: Robert Luce [SMTP:rwl@gymnet.com] > > Sent: Wednesday, October 08, 1997 12:20 AM > > To: freebsd-stable@FreeBSD.ORG > > Subject: can't compile beta > > > > I cvsupped the latest source (tag=RELENG_2_2) 10/7/97 21:00 PDT and > > am getting the following compile error in the 2940UW support code: > > > > make -f ../../dev/aic7xxx/Makefile MAKESRCPATH=../../dev/aic7xxx > > Warning: Object directory not changed from original > > /usr/src/sys/compile/BICEPS > > yacc -d ../../dev/aic7xxx/aicasm_gram.y > > mv y.tab.c aicasm_gram.c > > cc -O -I. -c aicasm_gram.c > > lex -t ../../dev/aic7xxx/aicasm_scan.l > aicasm_scan.c > > cc -O -I. -c aicasm_scan.c > > ../../dev/aic7xxx/aicasm_scan.l: In function `yylex': > > ../../dev/aic7xxx/aicasm_scan.l:68: `T_DOWNLOAD' undeclared (first use > > this func > > tion) > > ../../dev/aic7xxx/aicasm_scan.l:68: (Each undeclared identifier is > > reported only > > once > > ../../dev/aic7xxx/aicasm_scan.l:68: for each function it appears in.) > > *** Error code 1 > > > > Stop. > > *** Error code 1 > > > > Stop. > > > > ---- > > Bob Luce "Il faut supporter deux ou trois > > chenilles > > System/News Administrator si on veut connaître les > > papillons.." > > - Antoine de > > Saint-Exupéry > > Finger rwl@gymnet.com for PGP Public Key Block > --------------------------------------------------------------- Daniel R. Brownstone drbrowns@ls.wustl.edu Wash. U. School of Law Class of 1999 HOME: (314)-776-0102 PAGER: (314)-663-1367 *** THIS E-MAIL IS PROPRIETARY *** From owner-freebsd-stable Thu Oct 9 13:29:20 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id NAA27129 for stable-outgoing; Thu, 9 Oct 1997 13:29:20 -0700 (PDT) (envelope-from owner-freebsd-stable) Received: from dfw-ix3.ix.netcom.com (dfw-ix3.ix.netcom.com [206.214.98.3]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id NAA27123 for ; Thu, 9 Oct 1997 13:29:18 -0700 (PDT) (envelope-from wghhicks@ix.netcom.com) Received: (from smap@localhost) by dfw-ix3.ix.netcom.com (8.8.4/8.8.4) id PAA05808; Thu, 9 Oct 1997 15:27:15 -0500 (CDT) Received: from atl-ga17-14.ix.netcom.com(204.32.174.174) by dfw-ix3.ix.netcom.com via smap (V1.3) id rma005777; Thu Oct 9 15:26:44 1997 Message-ID: <343D3DD7.DEA0D05B@ix.netcom.com> Date: Thu, 09 Oct 1997 16:25:59 -0400 From: Jerry Hicks Reply-To: wghhicks@ix.netcom.com Organization: TerraEarth X-Mailer: Mozilla 4.03b8 [en] (X11; I; FreeBSD 2.2-STABLE i386) MIME-Version: 1.0 To: Tom CC: Dylan Northrup , stable@FreeBSD.ORG Subject: Re: password question References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > What kind of passwords does AIX use? If it DES, you're set. My guess would be Kerberos, considering its origin... From owner-freebsd-stable Thu Oct 9 13:31:27 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id NAA27317 for stable-outgoing; Thu, 9 Oct 1997 13:31:27 -0700 (PDT) (envelope-from owner-freebsd-stable) Received: from mail.uniserve.com (dns1-van.uniserve.com [204.244.163.48]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id NAA27310 for ; Thu, 9 Oct 1997 13:31:25 -0700 (PDT) (envelope-from tom@uniserve.com) Received: from shell.uniserve.com [204.244.210.252] by mail.uniserve.com with smtp (Exim 1.70 #1) id 0xJPEh-0003d3-00; Thu, 9 Oct 1997 13:31:07 -0700 Date: Thu, 9 Oct 1997 13:31:03 -0700 (PDT) From: Tom To: Jerry Hicks cc: Dylan Northrup , stable@freebsd.org Subject: Re: password question In-Reply-To: <343D3DD7.DEA0D05B@ix.netcom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Thu, 9 Oct 1997, Jerry Hicks wrote: > > What kind of passwords does AIX use? If it DES, you're set. > > My guess would be Kerberos, considering its origin... Kerberos is an authentication scheme not a password encryption format (in fact, I believe that Kerberos even uses DES for its internal password lists, but that is another matter). Tom From owner-freebsd-stable Thu Oct 9 13:54:57 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id NAA29010 for stable-outgoing; Thu, 9 Oct 1997 13:54:57 -0700 (PDT) (envelope-from owner-freebsd-stable) Received: from dfw-ix11.ix.netcom.com (dfw-ix11.ix.netcom.com [206.214.98.11]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id NAA29005 for ; Thu, 9 Oct 1997 13:54:53 -0700 (PDT) (envelope-from wghhicks@ix.netcom.com) Received: (from smap@localhost) by dfw-ix11.ix.netcom.com (8.8.4/8.8.4) id PAA10786; Thu, 9 Oct 1997 15:52:10 -0500 (CDT) Received: from atl-ga17-14.ix.netcom.com(204.32.174.174) by dfw-ix11.ix.netcom.com via smap (V1.3) id rma010619; Thu Oct 9 15:50:39 1997 Message-ID: <343D4372.848714B0@ix.netcom.com> Date: Thu, 09 Oct 1997 16:49:54 -0400 From: Jerry Hicks Reply-To: wghhicks@ix.netcom.com Organization: TerraEarth X-Mailer: Mozilla 4.03b8 [en] (X11; I; FreeBSD 2.2-STABLE i386) MIME-Version: 1.0 To: Tom CC: Dylan Northrup , stable@FreeBSD.ORG Subject: Re: password question References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Tom wrote: > > On Thu, 9 Oct 1997, Jerry Hicks wrote: > > > > What kind of passwords does AIX use? If it DES, you're set. > > > > My guess would be Kerberos, considering its origin... > > Kerberos is an authentication scheme not a password encryption format > (in fact, I believe that Kerberos even uses DES for its internal password > lists, but that is another matter). > > Tom Yeah, but doesn't the authentication scheme determine the encryption policy? From owner-freebsd-stable Thu Oct 9 14:11:04 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id OAA00234 for stable-outgoing; Thu, 9 Oct 1997 14:11:04 -0700 (PDT) (envelope-from owner-freebsd-stable) Received: from mail.uniserve.com (dns1-van.uniserve.com [204.244.163.48]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id OAA00229 for ; Thu, 9 Oct 1997 14:11:01 -0700 (PDT) (envelope-from tom@uniserve.com) Received: from shell.uniserve.com [204.244.210.252] by mail.uniserve.com with smtp (Exim 1.70 #1) id 0xJPqT-0003nb-00; Thu, 9 Oct 1997 14:10:09 -0700 Date: Thu, 9 Oct 1997 14:10:05 -0700 (PDT) From: Tom To: Jerry Hicks cc: Dylan Northrup , stable@freebsd.org Subject: Re: password question In-Reply-To: <343D4372.848714B0@ix.netcom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Thu, 9 Oct 1997, Jerry Hicks wrote: > Tom wrote: > > > > On Thu, 9 Oct 1997, Jerry Hicks wrote: > > > > > > What kind of passwords does AIX use? If it DES, you're set. > > > > > > My guess would be Kerberos, considering its origin... > > > > Kerberos is an authentication scheme not a password encryption format > > (in fact, I believe that Kerberos even uses DES for its internal password > > lists, but that is another matter). > > > > Tom > > Yeah, but doesn't the authentication scheme determine the encryption > policy? No, kerberos is a black box. If you happen to use that passwords are managed by kerberos, and only kerberos. What does /etc/passwd have in it? Does it have encrypted passwords? Tom From owner-freebsd-stable Thu Oct 9 18:16:51 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id SAA12768 for stable-outgoing; Thu, 9 Oct 1997 18:16:51 -0700 (PDT) (envelope-from owner-freebsd-stable) Received: from tok.qiv.com (QshS8WU1vBny6TxPIVDJ4009jpSXMUZs@[204.214.141.211]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id SAA12755 for ; Thu, 9 Oct 1997 18:16:37 -0700 (PDT) (envelope-from jdn@qiv.com) Received: (from uucp@localhost) by tok.qiv.com (8.8.6/8.8.5) with UUCP id UAA01004; Thu, 9 Oct 1997 20:15:18 -0500 (CDT) Received: from localhost (jdn@localhost) by acp.qiv.com (8.8.6/8.8.5) with SMTP id UAA00635; Thu, 9 Oct 1997 20:01:19 -0500 (CDT) X-Authentication-Warning: acp.qiv.com: jdn owned process doing -bs Date: Thu, 9 Oct 1997 20:01:19 -0500 (CDT) From: "Jay D. Nelson" To: Dylan Northrup cc: stable@FreeBSD.ORG Subject: Re: password question In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Thu, 9 Oct 1997, Dylan Northrup wrote: > We're intending on putting a FreeBSD box into production along some AIX > boxes. Is there some sort of way that we can get compatability between > the password generated by FreeBSD and the passwords on the AIX boxen? _If_ you've installed DES, FreeBSD can use AIX passwords and vica versa. Ala cut an encrypted password from /etc/security/passwd from the AIX box, paste in into a vipw session on FreeBSD, and go. That's how I converted our mail users from an aging AIX box ;) > Currently we rdist the password files to the various machines. Previously > we used yp/NIS, however the password maps were compromised and the idea of > using NIS around here again has not been well received. That dog won't hunt. The AIX and FreeBSD structure is different. Dust off your Perl chops, spend some time with `man pw` on your FreeBSD machine -- and for grins -- get ssh so you can automate it with security. (Perl > 5.004 and ssh compile cleanly on AIX 3x & 4x.) > Are they any ideas that would help with this problem (and, no, we can't > just depricate the AIX boxes, no matter how much I'd love to)? Give up on rdist -- it won't work. > -- > Dylan Northrup <*> > northrup@ucet.ufl.edu <*> > http://www.ucet.ufl.edu/~northrup <*> > > --------------- > Random B5 Quote > "Sometimes you have to heal the family before you heal the patient." > -- Dr. Franklin, "Believers" > -- Jay From owner-freebsd-stable Thu Oct 9 18:31:40 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id SAA13329 for stable-outgoing; Thu, 9 Oct 1997 18:31:40 -0700 (PDT) (envelope-from owner-freebsd-stable) Received: from set.spradley.dyn.ml.org (fcn104-100.tmi.net [207.170.104.100]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id SAA13322 for ; Thu, 9 Oct 1997 18:31:28 -0700 (PDT) (envelope-from tsprad@spradley.dyn.ml.org) Received: from set.spradley.dyn.ml.org (tsprad@localhost.sands.com [127.0.0.1]) by set.spradley.dyn.ml.org (8.8.5/8.8.5) with ESMTP id UAA09500; Thu, 9 Oct 1997 20:55:40 -0500 (CDT) Message-Id: <199710100155.UAA09500@set.spradley.dyn.ml.org> X-Mailer: exmh version 2.0zeta 7/24/97 To: Dylan Northrup cc: stable@FreeBSD.ORG Subject: Re: password question In-reply-to: Your message of "Thu, 09 Oct 1997 12:13:32 EDT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 09 Oct 1997 20:55:39 -0500 From: Ted Spradley Sender: owner-freebsd-stable@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > We're intending on putting a FreeBSD box into production along some AIX > boxes. Is there some sort of way that we can get compatability between > the password generated by FreeBSD and the passwords on the AIX boxen? I believe it's sufficient just to choose DES encryption at installation time. I have a FreeBSD box and a AIX box both as NIS clients to a Linux server, and that works for me. From owner-freebsd-stable Thu Oct 9 19:10:22 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id TAA15539 for stable-outgoing; Thu, 9 Oct 1997 19:10:22 -0700 (PDT) (envelope-from owner-freebsd-stable) Received: from andrsn.stanford.edu (andrsn.Stanford.EDU [36.33.0.163]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id TAA15534 for ; Thu, 9 Oct 1997 19:10:20 -0700 (PDT) (envelope-from andrsn@andrsn.stanford.edu) Received: from localhost (localhost.stanford.edu [127.0.0.1]) by andrsn.stanford.edu (8.8.7/8.6.12) with SMTP id TAA26750; Thu, 9 Oct 1997 19:08:17 -0700 (PDT) Date: Thu, 9 Oct 1997 19:08:16 -0700 (PDT) From: Annelise Anderson Reply-To: Annelise Anderson To: Bob Boone cc: freebsd-stable@FreeBSD.ORG, bboone@virtualbob.com Subject: Re: CVS and Popper.... In-Reply-To: <199710091458.KAA22108@helios.whro.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Thu, 9 Oct 1997, Bob Boone wrote: > I want to update from 2.2 release (july) to -stable, and to add qpop so I > can get my mail out of the server more easily, SYSINSTALL has lots of ports > -- but not the qpop 1.2.4 listed in the text of the website, nor Apache > 1.2.4, nor any convenient way to get the CVS "port". When I tried to access > the CVS port thru the hyperlink in the 16.3.2.2 Installation text (handbook) > I got DNS or directory errors. > > Is this a temporary thing related to the code freeze, some other magic, or > (dare I say) operator error ???? > > > > > > > Bob > There's popclient in the ports collection, but also fetchmail, which is supposed to be better. For a pop server there's popper. I've got both popclient and popper installed and they both work. popper installs as qpopper or qpop and is probably what you're talking about. Annelise From owner-freebsd-stable Thu Oct 9 23:22:40 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id XAA26870 for stable-outgoing; Thu, 9 Oct 1997 23:22:40 -0700 (PDT) (envelope-from owner-freebsd-stable) Received: from fragile.ideal.net.au (rob@fragile.ideal.net.au [203.20.241.5]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id XAA26864 for ; Thu, 9 Oct 1997 23:22:35 -0700 (PDT) (envelope-from rob@ideal.net.au) Received: from localhost (rob@localhost) by fragile.ideal.net.au (8.8.6/8.8.5) with SMTP id QAA23475 for ; Fri, 10 Oct 1997 16:22:29 +1000 (EST) Date: Fri, 10 Oct 1997 16:22:28 +1000 (EST) From: Rob Wise To: stable@freebsd.org Subject: make world problem 2.2.1-R -> RELENG_2_2 cvsupped yesterday Message-ID: X-WonK: Hmm MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk ===> usr.bin/xinstall cc -nostdinc -O -I/usr/obj/usr/src/tmp/usr/include -c /usr/src/usr.bin/xinstall/../../bin/ls/stat_flags.c cc -nostdinc -O -I/usr/obj/usr/src/tmp/usr/include -c /usr/src/usr.bin/xinstall/xinstall.c /usr/src/usr.bin/xinstall/xinstall.c:102: parse error before `_' *** Error code 1 Stop. Any ideas? Rob From owner-freebsd-stable Thu Oct 9 23:25:55 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id XAA27231 for stable-outgoing; Thu, 9 Oct 1997 23:25:55 -0700 (PDT) (envelope-from owner-freebsd-stable) Received: from gate.mgt.msk.ru (mgtrep.24h.dialup.ru [194.87.18.139]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id XAA27203; Thu, 9 Oct 1997 23:25:25 -0700 (PDT) (envelope-from tarkhil@mgt.msk.ru) Received: from asteroid.mgt.msk.ru (asteroid.mgt.msk.ru [192.168.133.145]) by gate.mgt.msk.ru (8.8.6/8.8.6) with ESMTP id KAA10363; Fri, 10 Oct 1997 10:24:55 +0400 (MSD) Received: from asteroid.mgt.msk.ru (localhost.mgt.msk.ru [127.0.0.1]) by asteroid.mgt.msk.ru (8.8.7/8.8.6) with ESMTP id KAA06724; Fri, 10 Oct 1997 10:24:20 +0400 (MSD) Message-Id: <199710100624.KAA06724@asteroid.mgt.msk.ru> To: hardware@freebsd.org cc: stable@freebsd.org, scsi@freebsd.org Reply-To: tarkhil@mgt.msk.ru Subject: Trouble with dump on ncr Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 10 Oct 1997 10:24:19 +0400 From: "Alexander B. Povolotsky" Sender: owner-freebsd-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hello! I'm trying to make dump, and constantly unable to do it. It looks like: DUMP: Date of this level 0 dump: Fri Oct 10 10:21:06 1997 DUMP: Date of last level 0 dump: the epoch DUMP: Dumping /dev/rsd0s1e (/var) to /var/async/tmp/test DUMP: mapping (Pass I) [regular files] DUMP: mapping (Pass II) [directories] DUMP: estimated 14328 tape blocks on 0.37 tape(s). DUMP: dumping (Pass III) [directories] DUMP: slave couldn't reopen disk: Device not configured DUMP: The ENTIRE dump is aborted. asteroid#/usr/FreeBSD-CVS/src 138_> Oct 10 10:21:06 asteroid /kernel: assertion "cp" failed: file "../../pci/ncr.c", line 6191 Oct 10 10:21:07 asteroid /kernel: assertion "cp" failed: file "../../pci/ncr.c", line 6191 Oct 10 10:21:07 asteroid /kernel: sd0(ncr0:0:0): COMMAND FAILED (4 28) @f0461000. Oct 10 10:21:07 asteroid /kernel: assertion "cp" failed: file "../../pci/ncr.c", line 6191 Oct 10 10:21:07 asteroid /kernel: sd0(ncr0:0:0): COMMAND FAILED (4 28) @f0461000. Oct 10 10:21:07 asteroid /kernel: assertion "cp" failed: file "../../pci/ncr.c", line 6191 Oct 10 10:21:07 asteroid /kernel: sd0(ncr0:0:0): COMMAND FAILED (4 28) @f063ec00 ... and so on. What should I do to fix it? Here is uname -a output: FreeBSD asteroid.mgt.msk.ru 2.2-STABLE FreeBSD 2.2-STABLE #0: Thu Oct 9 13:17:25 MSD 1997 root@asteroid.mgt.msk.ru:/net/unix/FreeBSD/src/sys/compile/ASTEROID i386 and part of dmesg: CPU: Pentium (133.64-MHz 586-class CPU) Origin = "GenuineIntel" Id = 0x526 Stepping=6 Features=0x1bf real memory = 33554432 (32768K bytes) avail memory = 31010816 (30284K bytes) Probing for devices on PCI bus 0: chip0 rev 1 on pci0:0 chip1 rev 1 on pci0:7:0 chip2 rev 0 on pci0:7:1 ncr0 rev 2 int a irq 11 on pci0:8 ncr0 waiting for scsi devices to settle (ncr0:0:0): 5.0 MB/s (200 ns, offset 8) (ncr0:0:0): "IBM DALS-3540 S60E" type 0 fixed SCSI 2 sd0(ncr0:0:0): Direct-Access sd0(ncr0:0:0): 10.0 MB/s (100 ns, offset 8) 516MB (1056768 512 byte sectors) (ncr0:1:0): 5.0 MB/s (200 ns, offset 8) (ncr0:1:0): "WDIGTL ENTERPRISE 1.61" type 0 fixed SCSI 2 sd1(ncr0:1:0): Direct-Access sd1(ncr0:1:0): 10.0 MB/s (100 ns, offset 8) 2077MB (4254819 512 byte sectors) Alex. From owner-freebsd-stable Fri Oct 10 01:20:31 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id BAA02267 for stable-outgoing; Fri, 10 Oct 1997 01:20:31 -0700 (PDT) (envelope-from owner-freebsd-stable) Received: from hawk.gnome.co.uk (gnome.gw.cerbernet.co.uk [193.243.224.22]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id BAA02259 for ; Fri, 10 Oct 1997 01:20:20 -0700 (PDT) (envelope-from jacs@hawk.gnome.co.uk) Received: from hawk.gnome.co.uk (localhost [127.0.0.1]) by hawk.gnome.co.uk (8.8.7/8.8.7) with ESMTP id JAA00634; Fri, 10 Oct 1997 09:19:34 +0100 (BST) Message-Id: <199710100819.JAA00634@hawk.gnome.co.uk> X-Mailer: exmh version 2.0zeta 7/24/97 To: "Daniel R. Brownstone" cc: "Hamilton, Kent" , Robert Luce , freebsd-stable@FreeBSD.ORG Subject: Re: can't compile beta In-reply-to: Your message of "Thu, 09 Oct 1997 15:27:37 CDT." Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Date: Fri, 10 Oct 1997 09:19:34 +0100 From: Chris Stenton Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by hub.freebsd.org id BAA02261 Sender: owner-freebsd-stable@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > Yes, I've received the same message. Yes I did. The problem is that someone added changes that are dated earlier than the versions you currently have on disk! Just delete the contents of ../../dev/aic7xxx and run Sup again. You will then have the correct versions. Someone needs to change the date stamps on these files on the sup server. Chris > > On Thu, 9 Oct 1997, Hamilton, Kent wrote: > > > I'm also seeing this one. Anyone else? > > > > -- > > Kent Hamilton Work: KHamilton@Hunter.COM > > Sr Systems Admin URL: http://www.hunter.com/ > > Hunter Engineering Co. Home: KentH@HNS.St-Louis.Mo.US > > NIC Handle: KH91 URL: http://www2.hunter.com/~skh/ > > > > > -----Original Message----- > > > From: Robert Luce [SMTP:rwl@gymnet.com] > > > Sent: Wednesday, October 08, 1997 12:20 AM > > > To: freebsd-stable@FreeBSD.ORG > > > Subject: can't compile beta > > > > > > I cvsupped the latest source (tag=RELENG_2_2) 10/7/97 21:00 PDT and > > > am getting the following compile error in the 2940UW support code: > > > > > > make -f ../../dev/aic7xxx/Makefile MAKESRCPATH=../../dev/aic7xxx > > > Warning: Object directory not changed from original > > > /usr/src/sys/compile/BICEPS > > > yacc -d ../../dev/aic7xxx/aicasm_gram.y > > > mv y.tab.c aicasm_gram.c > > > cc -O -I. -c aicasm_gram.c > > > lex -t ../../dev/aic7xxx/aicasm_scan.l > aicasm_scan.c > > > cc -O -I. -c aicasm_scan.c > > > ../../dev/aic7xxx/aicasm_scan.l: In function `yylex': > > > ../../dev/aic7xxx/aicasm_scan.l:68: `T_DOWNLOAD' undeclared (first use > > > this func > > > tion) > > > ../../dev/aic7xxx/aicasm_scan.l:68: (Each undeclared identifier is > > > reported only > > > once > > > ../../dev/aic7xxx/aicasm_scan.l:68: for each function it appears in.) > > > *** Error code 1 > > > > > > Stop. > > > *** Error code 1 > > > > > > Stop. > > > > > > ---- > > > Bob Luce "Il faut supporter deux ou trois > > > chenilles > > > System/News Administrator si on veut connaître les > > > papillons.." > > > - Antoine de > > > Saint-Exupéry > > > Finger rwl@gymnet.com for PGP Public Key Block > > > > --------------------------------------------------------------- > Daniel R. Brownstone drbrowns@ls.wustl.edu > Wash. U. School of Law Class of 1999 > HOME: (314)-776-0102 PAGER: (314)-663-1367 > *** THIS E-MAIL IS PROPRIETARY *** > From owner-freebsd-stable Fri Oct 10 01:20:45 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id BAA02294 for stable-outgoing; Fri, 10 Oct 1997 01:20:45 -0700 (PDT) (envelope-from owner-freebsd-stable) Received: from gatekeeper.tsc.tdk.com (root@gatekeeper.tsc.tdk.com [207.113.159.21]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id BAA02289 for ; Fri, 10 Oct 1997 01:20:41 -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.4/8.8.4) with ESMTP id BAA00710; Fri, 10 Oct 1997 01:20:01 -0700 (PDT) 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 BAA07882; Fri, 10 Oct 1997 01:19:59 -0700 (PDT) Received: (from gdonl@localhost) by salsa.gv.tsc.tdk.com (8.8.5/8.8.5) id BAA10480; Fri, 10 Oct 1997 01:19:57 -0700 (PDT) From: Don Lewis Message-Id: <199710100819.BAA10480@salsa.gv.tsc.tdk.com> Date: Fri, 10 Oct 1997 01:19:57 -0700 In-Reply-To: igor@alecto.physics.uiuc.edu (Igor Roshchin) "Re: Version of FreeBSD for production server?" (Oct 9, 2:34pm) X-Mailer: Mail User's Shell (7.2.6 alpha(3) 7/19/95) To: igor@alecto.physics.uiuc.edu (Igor Roshchin), chad@dcfinc.com Subject: Re: Version of FreeBSD for production server? Cc: tarkhil@mgt.msk.ru, stable@FreeBSD.ORG Sender: owner-freebsd-stable@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Oct 9, 2:34pm, Igor Roshchin wrote: } Subject: Re: Version of FreeBSD for production server? } If you have ADAPTEC-2940, AFAIK, 2.2 has all the problems solved, } while 2.1.7-RELEASE (and to the best of my knowledhe, 2.1-STABLE) still } have them unsolved. I ported the latest ahc driver from the 2.2 branch back to 2.1 about a month ago and convinced Justin to commit it to the tree. If you've fetched 2.1-stable since then, you should be in luck. That said, I'm planning on moving from 2.1 to 2.2 as soon as I can find the time (and a spare machine) to port my local changes to 2.2. --- Truck From owner-freebsd-stable Fri Oct 10 06:23:27 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id GAA13004 for stable-outgoing; Fri, 10 Oct 1997 06:23:27 -0700 (PDT) (envelope-from owner-freebsd-stable) Received: from baklava.alt.net (root@baklava.alt.net [207.14.113.9]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id GAA12994 for ; Fri, 10 Oct 1997 06:23:22 -0700 (PDT) (envelope-from ccaputo@alt.net) Received: from baklava.alt.net (ccaputo@baklava.alt.net [207.14.113.9]) by baklava.alt.net (8.8.5/8.7.3) with SMTP id GAA19694; Fri, 10 Oct 1997 06:23:20 -0700 (PDT) Date: Fri, 10 Oct 1997 06:23:19 -0700 (PDT) From: Chris Caputo To: freebsd-stable@freebsd.org Subject: 2.1-stable: "vnode_pager_input: I/O read error" messages Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi. Does anyone have any insight into what these messages really mean or what the fix is (besides going to 2.2-stable ;-)? They seem to come in spurts - none for a few days, then some for a few hours, then none for a few days, etc. This happens in vnode_pager_input(), which no longer appears to exist in 2.2-stable or current. It does not appear that we actually have a hardware problem (disks check out, controller checks out, etc.). Chris ... Oct 9 08:23:43 x /kernel: vnode_pager_input: I/O read error Oct 9 08:23:43 x /kernel: vm_fault: pager input (probably hardware) error, PID 14142 failure Oct 9 08:23:43 x /kernel: pid 14142 (in.nnrpd), uid 0: exited on signal 11 Oct 9 08:34:57 x /kernel: vnode_pager_input: I/O read error Oct 9 08:34:57 x /kernel: vm_fault: pager input (probably hardware) error, PID 17219 failure Oct 9 08:34:57 x /kernel: pid 17219 (in.nnrpd), uid 0: exited on signal 11 ... From owner-freebsd-stable Fri Oct 10 06:27:11 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id GAA13137 for stable-outgoing; Fri, 10 Oct 1997 06:27:11 -0700 (PDT) (envelope-from owner-freebsd-stable) Received: from ucet.ufl.edu (ronell.ucet.ufl.edu [128.227.243.237]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id GAA13131 for ; Fri, 10 Oct 1997 06:27:05 -0700 (PDT) (envelope-from northrup@ucet.ufl.edu) Received: from localhost (northrup@localhost) by ucet.ufl.edu (8.7.5/8.6.9) with SMTP id JAA84288 for ; Fri, 10 Oct 1997 09:26:59 -0400 Date: Fri, 10 Oct 1997 09:26:58 -0400 (EDT) From: Dylan Northrup To: stable@freebsd.org Subject: Re: password question In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Thanks to everyone for your help. I think I've got enough info to 'do the right thing' now. Again, my sincerest appreciation. -- Dylan Northrup <*> northrup@ucet.ufl.edu <*> http://www.ucet.ufl.edu/~northrup <*> --------------- Random B5 Quote "It is not yet time." 'And who decides that time? You? You put me in this position, you asked me to fight this damned war. Well, it's about time you let me fight this war my way." -- Kosh and Sheridan, "Interludes and Examinations" From owner-freebsd-stable Fri Oct 10 14:05:22 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id OAA08960 for stable-outgoing; Fri, 10 Oct 1997 14:05:22 -0700 (PDT) (envelope-from owner-freebsd-stable) Received: from bob.tri-lakes.net ([207.3.81.6]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id OAA08947 for ; Fri, 10 Oct 1997 14:05:14 -0700 (PDT) (envelope-from cdillon@tri-lakes.net) Received: from [204.185.3.157] by bob.tri-lakes.net (NTMail 3.02.13) with ESMTP id ga295600 for ; Fri, 10 Oct 1997 16:05:29 -0500 Message-ID: X-Mailer: XFMail 1.1 [p0] on FreeBSD Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: Date: Fri, 10 Oct 1997 16:00:04 -0000 (GMT) From: Chris Dillon To: Richard Wackerbarth Subject: Re: Fwd: CVSup release identity Cc: stable@FreeBSD.ORG Sender: owner-freebsd-stable@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On 08-Oct-97 Richard Wackerbarth wrote: >At 5:05 PM -0500 10/7/97, Chris Dillon wrote: >>2.2-CURRENT? Thats a new branch to me... Unless you are speaking >>hypothetically of a branch which has not yet had its first release, >which >>in that case, is still taken into account by the above example. > >NO. I am speaking posthumorously (sp?). 2.2-CURRENT was around back in >the >days when 2.1 was the "stable" branch and before 2.2.0 was released. Yes, of course.. the past-tense. What planet was my brain on? :-) >>What better alphanumeric incremented counter than time itself? >I agree. Encoding the time in some scheme to save a few characters >is counterproductive. Use a scheme where the meaning is easy for >humans. Besides, we save enough characters by dropping "-STABLE" >to make up most of the difference. Yes, time makes MUCH more sense to a human than some space-saving encoding scheme. >Richard Wackerbarth --- Chris Dillon --- cdillon@tri-lakes.net --- Powered by FreeBSD, the best free OS on the planet ---- (http://www.freebsd.org) From owner-freebsd-stable Fri Oct 10 19:35:43 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id TAA25170 for stable-outgoing; Fri, 10 Oct 1997 19:35:43 -0700 (PDT) (envelope-from owner-freebsd-stable) Received: from www.killercomputing.com (pulcher@www.killercomputing.com [199.233.181.45]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id TAA25161 for ; Fri, 10 Oct 1997 19:35:40 -0700 (PDT) (envelope-from pulcher@www.killercomputing.com) Received: (from pulcher@localhost) by www.killercomputing.com (8.8.7/8.8.5) id VAA08788 for freebsd-stable@freebsd.org; Fri, 10 Oct 1997 21:30:03 -0500 (CDT) From: Harold Pulcher Message-Id: <199710110230.VAA08788@www.killercomputing.com> Subject: Re: can't compile beta In-Reply-To: from "Daniel R. Brownstone" at "Oct 9, 97 03:27:37 pm" To: freebsd-stable@freebsd.org Date: Fri, 10 Oct 1997 21:30:01 -0500 (CDT) 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 X-Loop: FreeBSD.org Precedence: bulk Add me to the list. What have we all done wrong, or are we just the victims? :) harold Somebody with the name Daniel R. Brownstone said: > > Yes, I've received the same message. > > On Thu, 9 Oct 1997, Hamilton, Kent wrote: > > > I'm also seeing this one. Anyone else? > > From owner-freebsd-stable Fri Oct 10 20:27:48 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id UAA27189 for stable-outgoing; Fri, 10 Oct 1997 20:27:48 -0700 (PDT) (envelope-from owner-freebsd-stable) Received: from biceps.gymnet.com (biceps.gymnet.com [204.216.82.50]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id UAA27180 for ; Fri, 10 Oct 1997 20:27:45 -0700 (PDT) (envelope-from rwl@gymnet.com) Received: (qmail 1005 invoked from network); 11 Oct 1997 03:28:28 -0000 Received: from triceps.gymnet.com (HELO mail.gymnet.com) (204.216.82.51) by biceps.gymnet.com with SMTP; 11 Oct 1997 03:28:28 -0000 Date: Fri, 10 Oct 1997 20:27:28 -0800 From: Robert Luce X-Mailer: The Bat! (v1.00.95 Beta) Registered to Robert Luce Reply-To: Robert Luce Organization: Gymnet Communications Priority: Normal Message-ID: <15852.971010@gymnet.com> To: Harold Pulcher CC: freebsd-stable@freebsd.org Subject: Re: can't compile beta References: <199710110230.VAA08788@www.killercomputing.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Someone else reported (THANK YOU!) that someone had submitted revised files which had dates older than the files previously there.. so.. when you cvsup your system thinks your files are newer than the source. The answer is to delete the files in ../../dev/aic7xxx and then do a new cvsup. I've recompiled the kernel and my make world just finished. :) > Add me to the list. What have we all done wrong, or are we just > the victims? :) > harold > Somebody with the name Daniel R. Brownstone said: >> >> Yes, I've received the same message. >> >> On Thu, 9 Oct 1997, Hamilton, Kent wrote: >> >> > I'm also seeing this one. Anyone else? >> > ---- Bob Luce "Il faut supporter deux ou trois chenilles System/News Administrator si on veut connaître les papillons.." - Antoine de Saint-Exupéry Finger rwl@gymnet.com for PGP Public Key Block From owner-freebsd-stable Sat Oct 11 02:34:18 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id CAA10469 for stable-outgoing; Sat, 11 Oct 1997 02:34:18 -0700 (PDT) (envelope-from owner-freebsd-stable) Received: from word.smith.net.au (ppp20.portal.net.au [202.12.71.120]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id CAA10459 for ; Sat, 11 Oct 1997 02:34:10 -0700 (PDT) (envelope-from mike@word.smith.net.au) Received: from word.smith.net.au (localhost [127.0.0.1]) by word.smith.net.au (8.8.7/8.8.5) with ESMTP id TAA01078; Sat, 11 Oct 1997 19:01:15 +0930 (CST) Message-Id: <199710110931.TAA01078@word.smith.net.au> X-Mailer: exmh version 2.0zeta 7/24/97 To: Chris Caputo cc: freebsd-stable@freebsd.org Subject: Re: 2.1-stable: "vnode_pager_input: I/O read error" messages In-reply-to: Your message of "Fri, 10 Oct 1997 06:23:19 MST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 11 Oct 1997 19:01:14 +0930 From: Mike Smith Sender: owner-freebsd-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > Hi. Does anyone have any insight into what these messages really mean or > what the fix is (besides going to 2.2-stable ;-)? They seem to come in > spurts - none for a few days, then some for a few hours, then none for a > few days, etc. > > This happens in vnode_pager_input(), which no longer appears to exist in > 2.2-stable or current. > > It does not appear that we actually have a hardware problem (disks check > out, controller checks out, etc.). > > Chris > > .... > Oct 9 08:23:43 x /kernel: vnode_pager_input: I/O read error > Oct 9 08:23:43 x /kernel: vm_fault: pager input (probably hardware) error, PID 14142 failure > Oct 9 08:23:43 x /kernel: pid 14142 (in.nnrpd), uid 0: exited on signal 11 > Oct 9 08:34:57 x /kernel: vnode_pager_input: I/O read error > Oct 9 08:34:57 x /kernel: vm_fault: pager input (probably hardware) error, PID 17219 failure > Oct 9 08:34:57 x /kernel: pid 17219 (in.nnrpd), uid 0: exited on signal 11 > .... > > > From owner-freebsd-stable Sat Oct 11 02:36:25 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id CAA10611 for stable-outgoing; Sat, 11 Oct 1997 02:36:25 -0700 (PDT) (envelope-from owner-freebsd-stable) Received: from word.smith.net.au (ppp20.portal.net.au [202.12.71.120]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id CAA10606 for ; Sat, 11 Oct 1997 02:36:20 -0700 (PDT) (envelope-from mike@word.smith.net.au) Received: from word.smith.net.au (localhost [127.0.0.1]) by word.smith.net.au (8.8.7/8.8.5) with ESMTP id TAA01099; Sat, 11 Oct 1997 19:03:27 +0930 (CST) Message-Id: <199710110933.TAA01099@word.smith.net.au> X-Mailer: exmh version 2.0zeta 7/24/97 To: Chris Caputo cc: freebsd-stable@freebsd.org Subject: Re: 2.1-stable: "vnode_pager_input: I/O read error" messages In-reply-to: Your message of "Fri, 10 Oct 1997 06:23:19 MST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 11 Oct 1997 19:03:26 +0930 From: Mike Smith Sender: owner-freebsd-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Whoops, sorry about the blank preceeding this. > Hi. Does anyone have any insight into what these messages really mean or > what the fix is (besides going to 2.2-stable ;-)? They seem to come in > spurts - none for a few days, then some for a few hours, then none for a > few days, etc. The error message means exactly what it says; an I/O read error (probably hardware) has occurred. This normally means that (surprise, surprise) you have harware problems. Are there any error messages coming from your disk controller? Sometimes RAM faults can cause these symptoms as well. > It does not appear that we actually have a hardware problem (disks check > out, controller checks out, etc.). What do you mean by "check out"? mike From owner-freebsd-stable Sat Oct 11 15:02:25 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id PAA12624 for stable-outgoing; Sat, 11 Oct 1997 15:02:25 -0700 (PDT) (envelope-from owner-freebsd-stable) Received: from baklava.alt.net (root@baklava.alt.net [207.14.113.9]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id PAA12584 for ; Sat, 11 Oct 1997 15:02:16 -0700 (PDT) (envelope-from ccaputo@alt.net) Received: from baklava.alt.net (ccaputo@baklava.alt.net [207.14.113.9]) by baklava.alt.net (8.8.5/8.7.3) with SMTP id PAA24704 for ; Sat, 11 Oct 1997 15:02:14 -0700 (PDT) Date: Sat, 11 Oct 1997 15:02:14 -0700 (PDT) From: Chris Caputo Reply-To: Chris Caputo To: freebsd-stable@FreeBSD.ORG Subject: Re: 2.1-stable: "vnode_pager_input: I/O read error" messages In-Reply-To: <199710110933.TAA01099@word.smith.net.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Sat, 11 Oct 1997, Mike Smith wrote: > > Hi. Does anyone have any insight into what these messages really mean or > > what the fix is (besides going to 2.2-stable ;-)? They seem to come in > > spurts - none for a few days, then some for a few hours, then none for a > > few days, etc. > > The error message means exactly what it says; an I/O read error > (probably hardware) has occurred. > > This normally means that (surprise, surprise) you have harware problems. > Are there any error messages coming from your disk controller? Nope, no messages from the bt or sd device drivers. No other kernel messages besides these. No system crashes happening either. > Sometimes RAM faults can cause these symptoms as well. Possibly, but since the faults are isolated in a specific code area and come and go, I doubt it. > > It does not appear that we actually have a hardware problem (disks check > > out, controller checks out, etc.). > > What do you mean by "check out"? Meaning no SCSI errors spewed by the kernel and no problems using filesystems on them. Funny thing is the problem will happen for a few hours one day and than go for days without happening, and return, and then stop, etc. Thanks, Chris > > ... > > Oct 9 08:23:43 x /kernel: vnode_pager_input: I/O read error > > Oct 9 08:23:43 x /kernel: vm_fault: pager input (probably hardware) error, PID 14142 failure > > Oct 9 08:23:43 x /kernel: pid 14142 (in.nnrpd), uid 0: exited on signal 11 > > Oct 9 08:34:57 x /kernel: vnode_pager_input: I/O read error > > Oct 9 08:34:57 x /kernel: vm_fault: pager input (probably hardware) error, PID 17219 failure > > Oct 9 08:34:57 x /kernel: pid 17219 (in.nnrpd), uid 0: exited on signal 11 > > ... From owner-freebsd-stable Sat Oct 11 17:48:06 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id RAA19530 for stable-outgoing; Sat, 11 Oct 1997 17:48:06 -0700 (PDT) (envelope-from owner-freebsd-stable) Received: from freebie.lemis.com (gregl1.lnk.telstra.net [139.130.136.133]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id RAA19519 for ; Sat, 11 Oct 1997 17:48:00 -0700 (PDT) (envelope-from grog@freebie.lemis.com) Received: (from grog@localhost) by freebie.lemis.com (8.8.7/8.8.5) id KAA07741; Sun, 12 Oct 1997 10:17:51 +0930 (CST) Message-ID: <19971012101750.49489@lemis.com> Date: Sun, 12 Oct 1997 10:17:50 +0930 From: Greg Lehey To: "Jordan K. Hubbard" Cc: FreeBSD Stable Users Subject: Re: We are now in 2.2.5 BETA test. References: <2866.875879099.1@time.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.84e In-Reply-To: <2866.875879099.1@time.cdrom.com>; from Jordan K. Hubbard on Fri, Oct 03, 1997 at 04:44:59AM -0700 Organisation: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8250 Fax: +61-8-8388-8250 Mobile: +61-41-739-7062 WWW-Home-Page: http://www.lemis.com/~grog Fight-Spam-Now: http://www.cauce.org Sender: owner-freebsd-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Fri, Oct 03, 1997 at 04:44:59AM -0700, Jordan K. Hubbard wrote: Content-Description: Original Message > Yesterday, the 2.2-stable branch (tag name: RELENG_2_2) transitioned > to BETA status for the upcoming 2.2.5 release on the 20th of October. I've been tracking this, and haven't had any problems. But uname is still showing 2.2-STABLE. Shouldn't this be showing something like 2.2.5-BETA? It would make it a whole lot easier for people who don't trust CVS to verify :-) Greg From owner-freebsd-stable Sat Oct 11 23:45:43 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id XAA02355 for stable-outgoing; Sat, 11 Oct 1997 23:45:43 -0700 (PDT) (envelope-from owner-freebsd-stable) Received: from dfw-ix11.ix.netcom.com (dfw-ix11.ix.netcom.com [206.214.98.11]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id XAA02350 for ; Sat, 11 Oct 1997 23:45:39 -0700 (PDT) (envelope-from wghhicks@ix.netcom.com) Received: (from smap@localhost) by dfw-ix11.ix.netcom.com (8.8.4/8.8.4) id BAA29278 for ; Sun, 12 Oct 1997 01:45:07 -0500 (CDT) Received: from atl-ga6-14.ix.netcom.com(199.35.199.206) by dfw-ix11.ix.netcom.com via smap (V1.3) id rma029259; Sun Oct 12 01:44:24 1997 Message-ID: <344070AD.BEC41248@ix.netcom.com> Date: Sun, 12 Oct 1997 02:39:41 -0400 From: Jerry Hicks Reply-To: wghhicks@ix.netcom.com Organization: TerraEarth X-Mailer: Mozilla 4.03b8 [en] (X11; I; FreeBSD 2.2-STABLE i386) MIME-Version: 1.0 To: stable@freebsd.org Subject: ftp transfers crawling... Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Just me? Since about Wednesday's make world of 2.2-STABLE, I can't make *any* ftp download do better that 1K on my 28.8k modem . That's trying a lot of different sites. I'm using IJPPP. All was well before, no config changes have been made. Maybe Netcom... Anybody else notice anything? J. Hicks jerry_hicks@bigfoot.com