From owner-freebsd-stable Sun Sep 28 00:31:07 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id AAA15346 for stable-outgoing; Sun, 28 Sep 1997 00:31:07 -0700 (PDT) Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id AAA15335 for ; Sun, 28 Sep 1997 00:31:04 -0700 (PDT) Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.7/8.6.9) with ESMTP id AAA29329; Sun, 28 Sep 1997 00:30:48 -0700 (PDT) To: "Jamil J. Weatherbee" cc: stable@FreeBSD.ORG Subject: Re: 2nd Notice: 4 days to code freeze in RELENG_2_2 branch. In-reply-to: Your message of "Sat, 27 Sep 1997 23:21:00 PDT." Date: Sun, 28 Sep 1997 00:30:48 -0700 Message-ID: <29326.875431848@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-stable@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk I know of none. > > > Have the floppy driver problems been repaired?? > > From owner-freebsd-stable Sun Sep 28 03:42:08 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id DAA25115 for stable-outgoing; Sun, 28 Sep 1997 03:42:08 -0700 (PDT) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id DAA25109 for ; Sun, 28 Sep 1997 03:42:02 -0700 (PDT) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.5/8.6.9) id UAA15728; Sun, 28 Sep 1997 20:39:18 +1000 Date: Sun, 28 Sep 1997 20:39:18 +1000 From: Bruce Evans Message-Id: <199709281039.UAA15728@godzilla.zeta.org.au> To: jfarmer@sabre.goldsword.com, mdean@best.com Subject: Re: bad144 Cc: freebsd-stable@freebsd.org, jfarmer@goldsword.com Sender: owner-freebsd-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >I am not really worried what bad144 thinks, I worried that if it returns >errors so will freebsd in general since it does run under freebsd and uses >freebsd system calls I assume. It seems to be just another application bug. Untested fix: diff -c2 bad144.c~ bad144.c *** bad144.c~ Fri Sep 5 13:13:13 1997 --- bad144.c Fri Sep 5 13:13:23 1997 *************** *** 145,149 **** } ! lseek(f, curr_sec * ss, L_SET); if ((n = read(f, buf, ss)) != ss) { --- 145,149 ---- } ! lseek(f, (off_t)ss * curr_sec, SEEK_SET); if ((n = read(f, buf, ss)) != ss) { >> Why use bad144 at all? It's a relic left over from the VAX/PDP-11 days... >> Search the archives, this has come up several times. It the drive checks >> good with the vendors utilities (for IDE and SCSI) then it's good. >> >> bad144 had it's day when drives _didn't_ do automatic bad block >> replacement. >> >> John (Yes, I'm old enought to have had to deal with such beasts. >> My first Unix box was a PDP-11/34 with Version 6.... And >> _big_ RK-05 drives, all of 2.5mb each...) For FreeBSD, bad144 should only be necessary for MFM and ESDI drives. Bruce From owner-freebsd-stable Sun Sep 28 08:39:06 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id IAA09503 for stable-outgoing; Sun, 28 Sep 1997 08:39:06 -0700 (PDT) Received: from sabre.goldsword.com (sabre.goldsword.com [199.170.202.32]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id IAA09480 for ; Sun, 28 Sep 1997 08:38:40 -0700 (PDT) Received: (from jfarmer@localhost) by sabre.goldsword.com (8.8.7/8.7.3) id LAA19834; Sun, 28 Sep 1997 11:41:08 -0400 (EDT) Date: Sun, 28 Sep 1997 11:41:08 -0400 (EDT) From: "John T. Farmer" Message-Id: <199709281541.LAA19834@sabre.goldsword.com> To: bde@zeta.org.au, jfarmer@sabre.goldsword.com, mdean@best.com Subject: Re: bad144 Cc: freebsd-stable@FreeBSD.ORG, jfarmer@goldsword.com Sender: owner-freebsd-stable@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Sun, 28 Sep 1997 20:39:18 +1000 Bruce Evans said: >>> Why use bad144 at all? It's a relic left over from the VAX/PDP-11 days... >>> Search the archives, this has come up several times. It the drive checks >>> good with the vendors utilities (for IDE and SCSI) then it's good. >>> >>> bad144 had it's day when drives _didn't_ do automatic bad block >>> replacement. >>> >>> John (Yes, I'm old enought to have had to deal with such beasts. >>> My first Unix box was a PDP-11/34 with Version 6.... And >>> _big_ RK-05 drives, all of 2.5mb each...) > >For FreeBSD, bad144 should only be necessary for MFM and ESDI drives. > >Bruce Smacks side of head. Of course! Most ESDI & MFM drives _didn't_ do bad-block replacement. (The last time I installed an Unix system on an ESDI drive was Xenix on a Dell 386/25. 386/33's had been shipping for all of a month...) John ------------------------------------------------------------------------- John T. Farmer Proprietor, GoldSword Systems jfarmer@goldsword.com Public Internet Access in East Tennessee dial-in (423)470-9953 for info, e-mail to info@goldsword.com Network Design, Internet Services & Servers, Consulting From owner-freebsd-stable Sun Sep 28 10:13:02 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id KAA13630 for stable-outgoing; Sun, 28 Sep 1997 10:13:02 -0700 (PDT) Received: from fly.HiWAAY.net (fly.HiWAAY.net [208.147.154.56]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id KAA13615 for ; Sun, 28 Sep 1997 10:12:46 -0700 (PDT) Received: from nospam.hiwaay.net (tnt2-228.HiWAAY.net [208.147.148.228]) by fly.HiWAAY.net (8.8.7/8.8.6) with ESMTP id MAA28326; Sun, 28 Sep 1997 12:11:59 -0500 (CDT) Received: from localhost (localhost [127.0.0.1]) by nospam.hiwaay.net (8.8.7/8.8.4) with ESMTP id MAA20059; Sun, 28 Sep 1997 12:06:48 -0500 (CDT) Message-Id: <199709281706.MAA20059@nospam.hiwaay.net> X-Mailer: exmh version 2.0zeta 7/24/97 To: "Jamil J. Weatherbee" cc: stable@FreeBSD.ORG From: dkelly@hiwaay.net Subject: Re: 2nd Notice: 4 days to code freeze in RELENG_2_2 branch. In-reply-to: Message from "Jamil J. Weatherbee" of "Sat, 27 Sep 1997 23:21:00 PDT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 28 Sep 1997 12:06:47 -0500 Sender: owner-freebsd-stable@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Jamil J. Weatherbee writes: > > Have the floppy driver problems been repaired?? When someone else mentioned trouble with floppies and FreeBSD I thought to try the floppy on my then 1-week old Asus P6NP5 and had repeatable problems with good media. Jumped into the discussion. And proably ran fdformat 100 times. Flipped most every BIOS setup parameter, to no avail. Then somebody suggested, "Load BIOS Defaults". And all my problems dissappeared. All I can guess is that something was set in the BIOS's BB-ram that reconfigured hardware, but that something isn't reachable thru the provided human interface. Yet it was reset by "Load Defaults". So once again, *I'm* a happy camper. And learned more that I wanted to in the process. -- 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 Sun Sep 28 12:55:11 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id MAA19743 for stable-outgoing; Sun, 28 Sep 1997 12:55:11 -0700 (PDT) Received: from counterintelligence.ml.org (mdean.vip.best.com [206.86.94.101]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id MAA19735 for ; Sun, 28 Sep 1997 12:55:06 -0700 (PDT) Received: from localhost (jamil@localhost) by counterintelligence.ml.org (8.8.7/8.8.5) with SMTP id MAA03012; Sun, 28 Sep 1997 12:54:39 -0700 (PDT) Date: Sun, 28 Sep 1997 12:54:39 -0700 (PDT) From: "Jamil J. Weatherbee" To: "Jordan K. Hubbard" cc: stable@FreeBSD.ORG Subject: Re: 2nd Notice: 4 days to code freeze in RELENG_2_2 branch. In-Reply-To: <29326.875431848@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 Give me a break Jordan, It was a really big issue on the mailing list about 2 weeks ago. On Sun, 28 Sep 1997, Jordan K. Hubbard wrote: > I know of none. > > > > > > > Have the floppy driver problems been repaired?? > > > > > > From owner-freebsd-stable Sun Sep 28 13:31:08 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id NAA21148 for stable-outgoing; Sun, 28 Sep 1997 13:31:08 -0700 (PDT) Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id NAA21143 for ; Sun, 28 Sep 1997 13:31:05 -0700 (PDT) Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.7/8.6.9) with ESMTP id NAA03993; Sun, 28 Sep 1997 13:30:50 -0700 (PDT) To: "Jamil J. Weatherbee" cc: stable@FreeBSD.ORG Subject: Re: 2nd Notice: 4 days to code freeze in RELENG_2_2 branch. In-reply-to: Your message of "Sun, 28 Sep 1997 12:54:39 PDT." Date: Sun, 28 Sep 1997 13:30:50 -0700 Message-ID: <3989.875478650@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-stable@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Give *me* a break, Jamil. I repeat: I know of no outstanding problems. I know that you and others made a lot of *noise* about this in the mailing lists a couple of weeks ago, but I saw nothing in the way of conclusive proof being offered and, as far as I'm concerned, there are no problems with the floppy driver. One of your compatriots recently posted, in fact, that going back to his more conservative default BIOS settings fixed things - a case of "pilot error" if ever I saw one. Offer conclusive proof or be content to let this issue die. I have absolutely no plans on doing anything with 2.2.5's floppy driver unless you can do anything more constructive than make "a really big issue on the mailing list about it." Jordan > > Give me a break Jordan, It was a really big issue on the mailing list > about 2 weeks ago. > > On Sun, 28 Sep 1997, Jordan K. Hubbard wrote: > > > I know of none. > > > > > > > > > > > Have the floppy driver problems been repaired?? > > > > > > > > > > > From owner-freebsd-stable Sun Sep 28 14:55:19 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id OAA25568 for stable-outgoing; Sun, 28 Sep 1997 14:55:19 -0700 (PDT) Received: from gatekeeper.tseinc.com ([209.83.134.9]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id OAA25562 for ; Sun, 28 Sep 1997 14:55:06 -0700 (PDT) Received: (from nobody@localhost) by gatekeeper.tseinc.com (8.8.5/8.8.5) id QAA05564 for ; Sun, 28 Sep 1997 16:54:34 -0500 (CDT) Message-Id: <199709282154.QAA05564@gatekeeper.tseinc.com> X-Authentication-Warning: gatekeeper.tseinc.com: nobody set sender to using -f Received: from ws2.tse.com(192.168.1.12) by gatekeeper.tseinc.com via smap (V1.3) id sma005558; Sun Sep 28 16:54:15 1997 From: "Jay L. West" To: Subject: CVSUP woes for stable branch Date: Sun, 28 Sep 1997 16:54:15 -0500 X-MSMail-Priority: Normal X-Priority: 3 X-Mailer: Microsoft Internet Mail 4.70.1155 MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Maybe someone can shed some light on this... I installed 2.2.2-Release via FTP. All went well. I then grabbed the staticly linked copy of CVSup, and the supfile from www.freebsd.org. I ran cvsup supfile intending to go to -stable, and it appeared to bring down a fairly small number of files. I tried a make world, but the makefile no longer includes that option. So... I just did a make depend and make and make install. Rebooted the system, and whammo - wouldn't reboot. It kept complaining about page fault panic or such, and just kept autobooting, running fsck, then autobooting etc. I ran cvsup pointed at sup.freebsd.org on sunday, September 28 at around 9:00am. Anyone have any ideas? Thanks in advance! Jay West (jlwest@tseinc.com) Unix *IS* user friendly; It's just selective about who it calls a friend! From owner-freebsd-stable Sun Sep 28 15:48:53 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id PAA28040 for stable-outgoing; Sun, 28 Sep 1997 15:48:53 -0700 (PDT) Received: from bastuba.partitur.se ([193.219.246.194]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id PAA28027 for ; Sun, 28 Sep 1997 15:48:47 -0700 (PDT) Received: from [10.0.0.4] (dialup172-4-33.swipnet.se [130.244.172.225]) by bastuba.partitur.se (8.8.5/8.8.5) with ESMTP id AAA28171 for ; Mon, 29 Sep 1997 00:48:43 +0200 (CEST) X-Sender: girgen@mbox.partitur.se Message-Id: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Mon, 29 Sep 1997 00:48:35 +0200 To: freebsd-stable@FreeBSD.ORG From: Palle Girgensohn Subject: Stable kernels crashes on two machines. WAS: CVSUP woes for stable branch Sender: owner-freebsd-stable@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Jay West (jlwest@tseinc.com) wrote: >Maybe someone can shed some light on this... > >I installed 2.2.2-Release via FTP. All went well. I then >grabbed the staticly linked copy of CVSup, and the >supfile from www.freebsd.org. I ran cvsup supfile intending >to go to -stable, and it appeared to bring down a fairly small >number of files. I tried a make world, but the makefile no longer >includes that option. So... I just did a make depend and make >and make install. Rebooted the system, and whammo - wouldn't >reboot. It kept complaining about page fault panic or such, and >just kept autobooting, running fsck, then autobooting etc. > >I ran cvsup pointed at sup.freebsd.org on sunday, September 28 >at around 9:00am. > >Anyone have any ideas? > >Thanks in advance! > >Jay West (jlwest@tseinc.com) > >Unix *IS* user friendly; It's just selective about who it calls a friend! I have a similar problem. After installing 2.2.2 Release, I fetched the stable-src and ports, compiled cvsup port (not statically linked here...) and recompiled the kernel. Then I rebooted, and everything went black. This was done remote... :( I pinged to check, but it never came up. I went to the box today and it "kept autobooting, running fsck, then autobooting etc.". This was with a PPro 200. I also did the same thing with a 486 dx2/66 at home. I installed Release 222 and cvsup (dynamically linked, but version 15.0) from a CD this time (as opposed to ftp above). This kernel doesn't work either, but not in the same way, and it does give me a few lines of explanation before i dies: rc.i386 configuring syscons: keymap keyrate font8x16 font8x14 font 8x8 screensaver Fatal trap 12: page fault while in kernel mode fault virtual address = 0x0 fault code = supervisor read, page not present instruction pointer = 0x8:0x0 stack pointer = 0x10:0xefbffd74 frame pointer = 0x10:0xefbffd7c 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 = 137 (modload) interrupt mask = panic: page fault syncing disk... 30 30 27 21 7 done Automatic reboot in 15 secs..... Any ideas? The setups are quite different, and have different config files. Regards, Palle ________________________________________________________________________ Palle Girgensohn Partitur Informationsteknik AB girgen@partitur.se http://www.partitur.se/ From owner-freebsd-stable Sun Sep 28 15:56:44 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id PAA28397 for stable-outgoing; Sun, 28 Sep 1997 15:56:44 -0700 (PDT) Received: from gatekeeper.tseinc.com ([209.83.134.9]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id PAA28386 for ; Sun, 28 Sep 1997 15:56:18 -0700 (PDT) Received: (from nobody@localhost) by gatekeeper.tseinc.com (8.8.5/8.8.5) id RAA05713; Sun, 28 Sep 1997 17:55:34 -0500 (CDT) Message-Id: <199709282255.RAA05713@gatekeeper.tseinc.com> X-Authentication-Warning: gatekeeper.tseinc.com: nobody set sender to using -f Received: from ws2.tse.com(192.168.1.12) by gatekeeper.tseinc.com via smap (V1.3) id sma005707; Sun Sep 28 17:54:36 1997 From: "Jay L. West" To: "Palle Girgensohn" , <>, freebsd-stable@freebsd.org Subject: Re: Stable kernels crashes on two machines. WAS: CVSUP woes forstable branch Date: Sun, 28 Sep 1997 17:54:36 -0500 X-MSMail-Priority: Normal X-Priority: 3 X-Mailer: Microsoft Internet Mail 4.70.1155 MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk That jogged my memory; yes, that's exactly the message I was getting. Also, I was doing this remotely as well, just like you. > Fatal trap 12: page fault while in kernel mode > fault virtual address = 0x0 > fault code = supervisor read, page not present > instruction pointer = 0x8:0x0 > stack pointer = 0x10:0xefbffd74 > frame pointer = 0x10:0xefbffd7c > 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 = 137 (modload) > interrupt mask = > panic: page fault > > syncing disk... 30 30 27 21 7 done > Automatic reboot in 15 secs..... Also, my supfile did have 2.2, not 2.1. Perhaps I should stick with release? :( Jay West From owner-freebsd-stable Sun Sep 28 16:00:03 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id QAA28671 for stable-outgoing; Sun, 28 Sep 1997 16:00:03 -0700 (PDT) Received: from gatekeeper.tseinc.com ([209.83.134.9]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id PAA28612 for ; Sun, 28 Sep 1997 15:59:57 -0700 (PDT) Received: (from nobody@localhost) by gatekeeper.tseinc.com (8.8.5/8.8.5) id RAA05726 for ; Sun, 28 Sep 1997 17:59:35 -0500 (CDT) Message-Id: <199709282259.RAA05726@gatekeeper.tseinc.com> X-Authentication-Warning: gatekeeper.tseinc.com: nobody set sender to using -f Received: from ws2.tse.com(192.168.1.12) by gatekeeper.tseinc.com via smap (V1.3) id sma005723; Sun Sep 28 17:59:24 1997 From: "Jay L. West" To: Subject: Freebsd CVSUP woes.... Date: Sun, 28 Sep 1997 17:59:24 -0500 X-MSMail-Priority: Normal X-Priority: 3 X-Mailer: Microsoft Internet Mail 4.70.1155 MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk That jogged my memory; yes, that's exactly the message I was getting. Also, I was doing this remotely as well, just like you. > Fatal trap 12: page fault while in kernel mode > fault virtual address = 0x0 > fault code = supervisor read, page not present > instruction pointer = 0x8:0x0 > stack pointer = 0x10:0xefbffd74 > frame pointer = 0x10:0xefbffd7c > 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 = 137 (modload) > interrupt mask = > panic: page fault > > syncing disk... 30 30 27 21 7 done > Automatic reboot in 15 secs..... Also, my supfile did have 2.2, not 2.1. Perhaps I should stick with release? :( Jay West ------------------------------------------------------------------------ Unix *IS* user friendly; It's just selective about who it's friends are! ------------------------------------------------------------------------ From owner-freebsd-stable Sun Sep 28 17:04:49 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id RAA02168 for stable-outgoing; Sun, 28 Sep 1997 17:04:49 -0700 (PDT) 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 RAA02155 for ; Sun, 28 Sep 1997 17:04:44 -0700 (PDT) Received: from localhost (listuser@localhost) by h2o.journey.net (8.8.7/8.8.7) with SMTP id UAA01821; Sun, 28 Sep 1997 20:03:46 -0400 (EDT) Date: Sun, 28 Sep 1997 20:03:46 -0400 (EDT) From: listuser To: "Jay L. West" cc: freebsd-stable@FreeBSD.ORG Subject: Re: CVSUP woes for stable branch In-Reply-To: <199709282154.QAA05564@gatekeeper.tseinc.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 Exact same thing I got yesterday I thought I was doing something wrong. I went to releng22.freebsd.org and pulled down yesterdays build and all seems OK now. --Matt > includes that option. So... I just did a make depend and make > and make install. Rebooted the system, and whammo - wouldn't > reboot. It kept complaining about page fault panic or such, and > just kept autobooting, running fsck, then autobooting etc. > From owner-freebsd-stable Sun Sep 28 18:13:50 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id SAA05755 for stable-outgoing; Sun, 28 Sep 1997 18:13:50 -0700 (PDT) Received: from bastuba.partitur.se ([193.219.246.194]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id SAA05744; Sun, 28 Sep 1997 18:13:44 -0700 (PDT) Received: from [10.0.0.4] (dialup72-3-6.swipnet.se [130.244.72.134]) by bastuba.partitur.se (8.8.5/8.8.5) with ESMTP id DAA28516; Mon, 29 Sep 1997 03:13:36 +0200 (CEST) X-Sender: girgen@mbox.partitur.se Message-Id: In-Reply-To: <199709282354.QAA01634@hub.freebsd.org> References: from "Palle Girgensohn" at Sep 29, 97 00:48:35 am Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Mon, 29 Sep 1997 03:11:17 +0200 To: "Jonathan M. Bresler" From: Palle Girgensohn Subject: Re: Stable kernels crashes on two machines. WAS: CVSUP woes for Cc: freebsd-stable@FreeBSD.ORG Sender: owner-freebsd-stable@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >Palle Girgensohn wrote: >> >> After installing 2.2.2 Release, I fetched the stable-src and ports, >> compiled cvsup port (not statically linked here...) and recompiled the >> kernel. Then I rebooted, and everything went black. This was done remote... >> :( I pinged to check, but it never came up. I went to the box today and it >> "kept autobooting, running fsck, then autobooting etc.". >> >> This was with a PPro 200. I also did the same thing with a 486 dx2/66 at >> home. I installed Release 222 and cvsup (dynamically linked, but version >> 15.0) from a CD this time (as opposed to ftp above). This kernel doesn't >> work either, but not in the same way, and it does give me a few lines of >> explanation before i dies: >> >> rc.i386 configuring syscons: keymap keyrate font8x16 font8x14 font 8x8 >> screensaver > > please remove the screensaver and try again. > there were problems with the screensaver recently. > please let me know what happens >jmb That made it. I guessed it, but forgot to check. silly... thanks! I'm not sure this accounts for both machines though... I'll check that tomorrow. btw, is the screensaver problem fixed now? regards, palle ________________________________________________________________________ Palle Girgensohn Partitur Informationsteknik AB girgen@partitur.se http://www.partitur.se/ From owner-freebsd-stable Sun Sep 28 18:48:15 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id SAA07291 for stable-outgoing; Sun, 28 Sep 1997 18:48:15 -0700 (PDT) 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 SAA07285; Sun, 28 Sep 1997 18:48:08 -0700 (PDT) Received: by outmail.utsunomiya-u.ac.jp id AA04037; Mon, 29 Sep 1997 10:46:27 +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 KAA18749; Mon, 29 Sep 1997 10:52:37 +0900 (JST) Message-Id: <199709290152.KAA18749@zodiac.mech.utsunomiya-u.ac.jp> To: Palle Girgensohn Cc: "Jonathan M. Bresler" , freebsd-stable@freebsd.org, yokota@zodiac.mech.utsunomiya-u.ac.jp Subject: Re: Stable kernels crashes on two machines. WAS: CVSUP woes for In-Reply-To: Your message of "Mon, 29 Sep 1997 03:11:17 +0200." References: from "Palle Girgensohn" at Sep 29, 97 00:48:35 am Date: Mon, 29 Sep 1997 10:52:36 +0900 From: Kazutaka YOKOTA Sender: owner-freebsd-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >>> rc.i386 configuring syscons: keymap keyrate font8x16 font8x14 font 8x8 >>> screensaver >> >> please remove the screensaver and try again. >> there were problems with the screensaver recently. >> please let me know what happens >>jmb > >That made it. I guessed it, but forgot to check. silly... thanks! > >I'm not sure this accounts for both machines though... I'll check that >tomorrow. > >btw, is the screensaver problem fixed now? > >regards, >palle BOTH screen saver LKMs and the kernel need to be updated... Do `make world' and rebuild the kernel. All should be fine. Kazu From owner-freebsd-stable Sun Sep 28 20:40:52 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id UAA12778 for stable-outgoing; Sun, 28 Sep 1997 20:40:52 -0700 (PDT) Received: from austin.polstra.com (austin.polstra.com [206.213.73.10]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id UAA12772 for ; Sun, 28 Sep 1997 20:40:49 -0700 (PDT) Received: from austin.polstra.com (jdp@localhost) by austin.polstra.com (8.8.7/8.8.5) with ESMTP id UAA22137; Sun, 28 Sep 1997 20:40:42 -0700 (PDT) Message-Id: <199709290340.UAA22137@austin.polstra.com> To: jlwest@tseinc.com Subject: Re: CVSUP woes for stable branch In-Reply-To: <199709282154.QAA05564@gatekeeper.tseinc.com> References: <199709282154.QAA05564@gatekeeper.tseinc.com> Organization: Polstra & Co., Seattle, WA Cc: stable@freebsd.org Date: Sun, 28 Sep 1997 20:40:42 -0700 From: John Polstra Sender: owner-freebsd-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk In article <199709282154.QAA05564@gatekeeper.tseinc.com>, Jay L. West wrote: > Maybe someone can shed some light on this... > > I installed 2.2.2-Release via FTP. All went well. I then > grabbed the staticly linked copy of CVSup, and the > supfile from www.freebsd.org. I ran cvsup supfile intending > to go to -stable, and it appeared to bring down a fairly small > number of files. I tried a make world, but the makefile no longer > includes that option. You are saying that /usr/src/Makefile no longer contained a "world" target after you did the update? Please send me the bad Makefile, if you still have it. > I ran cvsup pointed at sup.freebsd.org on sunday, September 28 > at around 9:00am. Please send me your supfile, and also the output from running "cvsup -v" on your system. Thanks, John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Self-knowledge is always bad news." -- John Barth From owner-freebsd-stable Sun Sep 28 22:28:00 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id WAA17735 for stable-outgoing; Sun, 28 Sep 1997 22:28:00 -0700 (PDT) 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 WAA17712 for ; Sun, 28 Sep 1997 22:27:50 -0700 (PDT) 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 JAA13470; Mon, 29 Sep 1997 09:27:13 +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 JAA17599; Mon, 29 Sep 1997 09:26:17 +0400 (MSD) Message-Id: <199709290526.JAA17599@asteroid.mgt.msk.ru> To: "Jay D. Nelson" cc: stable@FreeBSD.ORG Reply-To: tarkhil@mgt.msk.ru Subject: Re: 2nd Notice: 4 days to code freeze in RELENG_2_2 branch. In-reply-to: Your message of "Fri, 26 Sep 1997 19:59:00 CDT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 29 Sep 1997 09:26:15 +0400 From: "Alexander B. Povolotsky" Sender: owner-freebsd-stable@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > next release? Even though UUCP died years ago, I'm converting more Disagree. It still works in some places. For instance, it's the only link from my home to thew world... Alex. From owner-freebsd-stable Sun Sep 28 22:31:42 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id WAA17941 for stable-outgoing; Sun, 28 Sep 1997 22:31:42 -0700 (PDT) Received: from usr08.primenet.com (tlambert@usr08.primenet.com [206.165.6.208]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id WAA17933; Sun, 28 Sep 1997 22:31:39 -0700 (PDT) Received: (from tlambert@localhost) by usr08.primenet.com (8.8.5/8.8.5) id WAA16168; Sun, 28 Sep 1997 22:31:28 -0700 (MST) From: Terry Lambert Message-Id: <199709290531.WAA16168@usr08.primenet.com> Subject: Re: 'fxp' driver/hardware lossage (was Re: Alexander B. Povol's mail) To: rgrimes@GndRsh.aac.dev.com (Rodney W. Grimes) Date: Mon, 29 Sep 1997 05:31:28 +0000 (GMT) Cc: tlambert@primenet.com, sthaug@nethelp.no, hackers@FreeBSD.ORG, stable@FreeBSD.ORG In-Reply-To: <199709280656.XAA20941@GndRsh.aac.dev.com> from "Rodney W. Grimes" at Sep 27, 97 11:56:53 pm X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-freebsd-stable@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > Ah, Terry, do you realize who you quoted above? Please reread > what I wrote, I don't think you can find a NIC that meets my > spec without getting a ``good one''. Yes; I'll note the subtle distinction between "prevent" and "not fail as a result of". If you are spending money, since hubs cost more than cards, unless you already have a significant amount of bad cards to hubs, and the price of replacing the cards is higher than the marginal cost of upgrading the card to a switch, you might as well go for "not fail as a result of" instead, and save the money. The problem is specific to the fxp cards; don't buy fxp cards, and you don't have the problem. Upgrade your hubs to switches, and you don't have the problem. Is it really cheaper to buy switched than new cards? Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-stable Sun Sep 28 23:05:57 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id XAA19881 for stable-outgoing; Sun, 28 Sep 1997 23:05:57 -0700 (PDT) Received: from leech.mpg.uni-jena.de (leech.mpg.uni-jena.de [141.35.24.98]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id XAA19876 for ; Sun, 28 Sep 1997 23:05:53 -0700 (PDT) Received: by leech.mpg.uni-jena.de (NX5.67f2/NX3.0M) id AA03408; Mon, 29 Sep 97 07:04:46 GMT Message-Id: <9709290704.AA03408@leech.mpg.uni-jena.de> Content-Type: text/plain Mime-Version: 1.0 (NeXT Mail 3.3 v118.2) Received: by NeXT.Mailer (1.118.2) From: Heiko Schafberg Date: Mon, 29 Sep 97 07:04:45 GMT To: freebsd-stable@FreeBSD.ORG Sender: owner-freebsd-stable@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk unsubscribe freebsd-stable@FreeBSD.ORG Heiko Schafberg hei@leech.mpg.uni-jena.de From owner-freebsd-stable Sun Sep 28 23:57:23 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id XAA22940 for stable-outgoing; Sun, 28 Sep 1997 23:57:23 -0700 (PDT) Received: from micro.internexus.net (root@internexus.net [206.152.14.2]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id XAA22933 for ; Sun, 28 Sep 1997 23:57:20 -0700 (PDT) Received: from c.f.ains (ppp40.internexus.net [206.152.14.231]) by micro.internexus.net (8.8.7/8.8.4) with SMTP id CAA04169 for ; Mon, 29 Sep 1997 02:57:17 -0400 Message-Id: <3.0.3.32.19970929020829.00734238@mail.internexus.net> X-Sender: compatriot@mail.internexus.net X-Mailer: QUALCOMM Windows Eudora Pro Version 3.0.3 (32) Date: Mon, 29 Sep 1997 02:08:29 -0400 To: stable@FreeBSD.ORG From: cliff ainsworth III Subject: help help I'm being repressed In-Reply-To: <199709290340.UAA22137@austin.polstra.com> References: <199709282154.QAA05564@gatekeeper.tseinc.com> <199709282154.QAA05564@gatekeeper.tseinc.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-stable@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Morning all, enterprise class newbie users here.... We have been trying to install FreeBSD for many weeks now. We know it is a very easy install as we have read it many a time. So we know that it is probably something very simple that we are missing. Machine 1 specs, P-75, eide, 16 megs ram, 365 meg eide hard drive, Creative Labs 32PnP, Creative Labs 8x cd-rom, Ms-dos 6.22 is the only OS and it is not being used accept for this installation. We are installing from a cd-rom. We have made a boot-disc to install of off. We keep getting a message stating "no cd-rom devices found, please check that your systems configuration is correct and that the cd-rom drive is of a supported type. For more info, consult the hardware guide." Do we need to reset any IRQS???. Just not really sure what we are missing here. But we do know this should be the most straight forward of installations. Machine 2 specs, P-200 pro, 32 megs ram, 3 physical eide hard drives, a 2 gig-wd0, 4 gig wd1 and 4 gig wd2., Windows NT 3.51, Windows Nt4.0 spk 3, Windows NT Server 4.0 and Win95 OSes on it., Creative Labs AWE64 Gold card, Teac 6x cd-rom, Number Nine 128 bit series 1 video card. After several attempts to get the Windoze NT loader to recognize the attempted installation we gave up. Eventually went with System Commander 2.x and it recognized it fine. On this machine the cd-rom works fine and installs fine but it doesn't run. We where getting one of the error messages in the book (I cannot remember which one at the moment) We are trying to install FreeBSD on the third physical hard drive "wd2". I am a bit fuzzy on what we did as its been a few weeks at this point. We want to leave the first two (wd0 and wd1) physical hard drives alone and leave all of the microsloth programs there and put all the FreeBSD stuff on the third drive which is completely empty. The Walnut Creek book really doesn't go into multiple hard drive installations with multiple OSes on them. We feel this is a simple problem, but at the moment not obvious. How do we set it, I guess to boot off the c drive/wd0 and run off wd2. I believe I worded that correctly, forgive me if I haven't. We also have a genuine DEC VT100 and Vt220, I am sure can be hooked via LAN with FreeBSD and I also heard they can be run through a PCs serial port. Any ideas. have a great week and thanx in advance -cliff ------------------------------------------------------------------------------ CLIFFSWORLD homepage------------ "Open Throttle" automotive e-zine- Quake-Clan "RIP" homepage------------- p.o. box 1055, Maywood NJ, 07607-7055 fone 201-843-0936 PGP v5.0 public key available "never drive faster than your guardian angels can fly" From owner-freebsd-stable Mon Sep 29 01:25:29 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id BAA27014 for stable-outgoing; Mon, 29 Sep 1997 01:25:29 -0700 (PDT) Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id BAA27002 for ; Mon, 29 Sep 1997 01:25:21 -0700 (PDT) Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.7/8.6.9) with ESMTP id BAA10547; Mon, 29 Sep 1997 01:25:10 -0700 (PDT) To: cliff ainsworth III cc: stable@FreeBSD.ORG Subject: Re: help help I'm being repressed In-reply-to: Your message of "Mon, 29 Sep 1997 02:08:29 EDT." <3.0.3.32.19970929020829.00734238@mail.internexus.net> Date: Mon, 29 Sep 1997 01:25:10 -0700 Message-ID: <10543.875521510@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-stable@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > We have been trying to install FreeBSD for many weeks now. We know it is a ^^^^^^^ Actually noting _which version_ of FreeBSD you're trying to install in any of the following text would have been a big help. ;-( Jordan From owner-freebsd-stable Mon Sep 29 01:57:31 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id BAA28632 for stable-outgoing; Mon, 29 Sep 1997 01:57:31 -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 BAA28626 for ; Mon, 29 Sep 1997 01:57:26 -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 CAA00819; Mon, 29 Sep 1997 02:00:09 -0700 (PDT) Message-Id: <199709290900.CAA00819@implode.root.com> To: cliff ainsworth III cc: stable@FreeBSD.ORG Subject: Re: help help I'm being repressed In-reply-to: Your message of "Mon, 29 Sep 1997 02:08:29 EDT." <3.0.3.32.19970929020829.00734238@mail.internexus.net> From: David Greenman Reply-To: dg@root.com Date: Mon, 29 Sep 1997 02:00:09 -0700 Sender: owner-freebsd-stable@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Which version of FreeBSD are you trying to install? 2.1.x had problems seeing certain IDE CDROM drives, 2.2.x is much better, but probably still has problems with some. -DG David Greenman Core-team/Principal Architect, The FreeBSD Project From owner-freebsd-stable Mon Sep 29 02:44:57 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id CAA01069 for stable-outgoing; Mon, 29 Sep 1997 02:44:57 -0700 (PDT) Received: from home.shvetc.marka.net.ua (home.shvetc.marka.net.ua [193.193.219.253]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id CAA01063 for ; Mon, 29 Sep 1997 02:44:46 -0700 (PDT) Received: (from root@localhost) by home.shvetc.marka.net.ua (8.8.7/8.8.5) id MAA00892 for freebsd-stable@freebsd.org; Mon, 29 Sep 1997 12:44:27 +0300 (EEST) Date: Mon, 29 Sep 1997 12:44:27 +0300 (EEST) From: Eugene Shvetc Message-Id: <199709290944.MAA00892@home.shvetc.marka.net.ua> To: freebsd-stable@freebsd.org Subject: HELP, please ! Sender: owner-freebsd-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Is anybody know why after few run of slattach SLIP device stop work with error: ioctl(TIOCSETD): Device not configured ??? This error also appear after few reconnect of SLIP device... If any know what is it, please write me mail directly at eugene@shvetc.marka.net.ua Beforehand gratefull. Thanks. From owner-freebsd-stable Mon Sep 29 04:01:36 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id EAA04377 for stable-outgoing; Mon, 29 Sep 1997 04:01:36 -0700 (PDT) Received: from indigo.ie (aoife.indigo.ie [194.125.133.9]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id EAA04357; Mon, 29 Sep 1997 04:01:27 -0700 (PDT) Received: from indigo.ie (localhost [127.0.0.1]) by indigo.ie (8.8.5/8.8.5/INDIGO-HUB) with ESMTP id MAA16750; Mon, 29 Sep 1997 12:01:25 +0100 (BST) Message-Id: <199709291101.MAA16750@indigo.ie> To: scsi@freebsd.org, stable@freebsd.org Subject: Kernel disk hangs under load with 2.2-STABLE From: Alan Judge Date: Mon, 29 Sep 1997 12:01:24 +0100 Sender: owner-freebsd-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk [Posting to both scsi and stable, since I'm not sure which is at fault and if there is a hang bug in 2.2-STABLE, it would be good to find it.] I have a machine running squid (with the data stored on a CCD striped set of disks). Since it's a major web cache, the disks get a fairly steady and sometimes heavy load. The machine doesn't do anything else and squid is the only large process (RSS of 120MB on a 256MB machine). The kernel is 2.2-STABLE, cvsuped last Tuesday; hardware is dual Adaptec 2940UWs with Quantum Atlas II UW disks. No unusual config options other than increases of NBUF and NMBCLUSTERS. Every so often (about once in two to three days), the squid process hangs and shows up in D state in ps. The process cannot be killed and commands that are disk related sometimes hang. The only cure is to reboot, and the reboot is usually not clean (syncing disks, .... giving up). Oddly, reducing the size of the web cache (which indirectly reduces squids RSS and the proportion of the CCD array in use) reduces the frequency of the hangs. I know that's probably not enough info to find a bug. Any suggestions on how to start debugging this? What commands should I try? How do I find what squid is stuck waiting for? Should I bring up gdb or DDB and look at something? -- Alan Judge Phone: +353-1-6046901 Indigo Network Operations Centre Fax: +353-1-6046948 From owner-freebsd-stable Mon Sep 29 04:01:56 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id EAA04424 for stable-outgoing; Mon, 29 Sep 1997 04:01:56 -0700 (PDT) Received: from relay.ucb.crimea.ua (relay.ucb.crimea.ua [194.93.177.113]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id EAA04335; Mon, 29 Sep 1997 04:01:00 -0700 (PDT) Received: (from ru@localhost) by relay.ucb.crimea.ua (8.8.7/8.8.7) id NAA20681; Mon, 29 Sep 1997 13:56:05 +0300 (EEST) From: Ruslan Ermilov Message-Id: <199709291056.NAA20681@relay.ucb.crimea.ua> Subject: kern/4090 (was: HELP, please !) In-Reply-To: <199709290944.MAA00892@home.shvetc.marka.net.ua> from Eugene Shvetc at "Sep 29, 97 12:44:27 pm" To: eugene@home.shvetc.marka.net.ua (Eugene Shvetc) Date: Mon, 29 Sep 1997 13:56:05 +0300 (EEST) Cc: freebsd-stable@FreeBSD.ORG, ache@FreeBSD.ORG X-My-Interests: Unix,Oracle,Networking 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 There are still errors in if_sl.c concerning static unit feature. There was an kern/4090 pr originated by me and it was closed by Andrey Chernov due to my report that problem has resolved. My report was wrong - the problem still exists. Once Eugene Shvetc wrote: > Is anybody know why after few run of slattach SLIP device stop work > with error: ioctl(TIOCSETD): Device not configured ??? > This error also appear after few reconnect of SLIP device... > > If any know what is it, please write me mail directly at > eugene@shvetc.marka.net.ua > > Beforehand gratefull. > Thanks. > -- Ruslan A. Ermilov System Administrator ru@ucb.crimea.ua United Commercial Bank +380-652-247647 Simferopol, Crimea 2426679 ICQ Network, UIN From owner-freebsd-stable Mon Sep 29 04:56:03 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id EAA06647 for stable-outgoing; Mon, 29 Sep 1997 04:56:03 -0700 (PDT) Received: from Big.LITech.Lviv.UA (root@Big.LITech.Lviv.UA [193.232.65.2]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id EAA06613 for ; Mon, 29 Sep 1997 04:55:43 -0700 (PDT) Received: from ah.litech.lviv.ua (Ah.LITech.Lviv.UA [193.232.65.1]) by Big.LITech.Lviv.UA (8.8.5/8.7.3) with SMTP id OAA01872; Mon, 29 Sep 1997 14:53:38 +0300 (EET DST) Date: Mon, 29 Sep 1997 14:53:37 +0300 (EEST) From: "Bohdan Kmit'" To: Palle Girgensohn cc: freebsd-stable@FreeBSD.ORG Subject: Re: Stable kernels crashes on two machines. WAS: CVSUP woes for stable branch 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, 29 Sep 1997, Palle Girgensohn wrote: > Jay West (jlwest@tseinc.com) wrote: > > >Maybe someone can shed some light on this... > > > >I installed 2.2.2-Release via FTP. All went well. I then > >grabbed the staticly linked copy of CVSup, and the > >supfile from www.freebsd.org. I ran cvsup supfile intending > >to go to -stable, and it appeared to bring down a fairly small > >number of files. I tried a make world, but the makefile no longer > >includes that option. So... I just did a make depend and make > >and make install. Rebooted the system, and whammo - wouldn't > >reboot. It kept complaining about page fault panic or such, and > >just kept autobooting, running fsck, then autobooting etc. > > > >I ran cvsup pointed at sup.freebsd.org on sunday, September 28 > >at around 9:00am. > > > >Anyone have any ideas? > > > >Thanks in advance! > > > >Jay West (jlwest@tseinc.com) > > > >Unix *IS* user friendly; It's just selective about who it calls a friend! > > I have a similar problem. > > After installing 2.2.2 Release, I fetched the stable-src and ports, > compiled cvsup port (not statically linked here...) and recompiled the > kernel. Then I rebooted, and everything went black. This was done remote... > :( I pinged to check, but it never came up. I went to the box today and it > "kept autobooting, running fsck, then autobooting etc.". > > This was with a PPro 200. I also did the same thing with a 486 dx2/66 at > home. I installed Release 222 and cvsup (dynamically linked, but version > 15.0) from a CD this time (as opposed to ftp above). This kernel doesn't > work either, but not in the same way, and it does give me a few lines of > explanation before i dies: > > rc.i386 configuring syscons: keymap keyrate font8x16 font8x14 font 8x8 > screensaver > > Fatal trap 12: page fault while in kernel mode > fault virtual address = 0x0 > fault code = supervisor read, page not present > instruction pointer = 0x8:0x0 > stack pointer = 0x10:0xefbffd74 > frame pointer = 0x10:0xefbffd7c > 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 = 137 (modload) > interrupt mask = > panic: page fault > > syncing disk... 30 30 27 21 7 done > Automatic reboot in 15 secs..... > > > Any ideas? The setups are quite different, and have different config files. > > Regards, > Palle > > > ________________________________________________________________________ > Palle Girgensohn Partitur Informationsteknik AB > girgen@partitur.se http://www.partitur.se/ > > > I had this problem too on two boxes. Solution was simple -- all lkm's recompilation. Look like interface beetwen kernel and lkm changed. Hope this help. With regards, Bohdan. --------------------------------------------------------------- Bohdan Kmit' | +380 (322) 742339 Laboratory of Information Technologies | L'viv, Ukraine | mit@LITech.Lviv.UA --------------------------------------------------------------- From owner-freebsd-stable Mon Sep 29 06:17:30 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id GAA09486 for stable-outgoing; Mon, 29 Sep 1997 06:17:30 -0700 (PDT) Received: from micro.internexus.net (root@internexus.net [206.152.14.2]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id GAA09480 for ; Mon, 29 Sep 1997 06:17:27 -0700 (PDT) Received: from c.f.ains (ppp40.internexus.net [206.152.14.231]) by micro.internexus.net (8.8.7/8.8.4) with SMTP id JAA18188 for ; Mon, 29 Sep 1997 09:17:24 -0400 Message-Id: <3.0.3.32.19970929091843.007023e0@mail.internexus.net> X-Sender: compatriot@mail.internexus.net X-Mailer: QUALCOMM Windows Eudora Pro Version 3.0.3 (32) Date: Mon, 29 Sep 1997 09:18:43 -0400 To: stable@FreeBSD.ORG From: cliff ainsworth III Subject: Re: help help I'm being repressed In-Reply-To: <199709290900.CAA00819@implode.root.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-stable@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk of all the particulars I forgot the most important................... 2.2.2 stable thanks, I'll also send it questions@freebsd.org -cliff ------------------------------------------------------------------------------ CLIFFSWORLD homepage------------ "Open Throttle" automotive e-zine- Quake-Clan "RIP" homepage------------- p.o. box 1055, Maywood NJ, 07607-7055 fone 201-843-0936 PGP v5.0 public key available "never drive faster than your guardian angels can fly" From owner-freebsd-stable Mon Sep 29 07:44:12 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id HAA14446 for stable-outgoing; Mon, 29 Sep 1997 07:44:12 -0700 (PDT) Received: from gate.corp.wrgrace.com (wrgrace.com [208.221.196.2]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id HAA14441 for ; Mon, 29 Sep 1997 07:44:09 -0700 (PDT) From: David.Botton@grace.com Received: from wrgicon.corp.wrgrace.com by gate.corp.wrgrace.com via smtpd (for hub.FreeBSD.ORG [204.216.27.18]) with SMTP; 29 Sep 1997 14:44:05 UT Received: by corp.wrgrace.com; id KAA21609; Mon, 29 Sep 1997 10:41:46 -0400 (EDT) Received: by grace.com; ID AA143754681; Mon, 29 Sep 1997 10:51:21 -0400 X-Openmail-Hops: 1 Date: Mon, 29 Sep 97 10:51:10 -0400 Message-Id: Subject: Re: help help I'm being repressed Mime-Version: 1.0 To: cliff@cliffsworld.com, stable@FreeBSD.ORG Content-Type: text/plain; charset=US-ASCII; name="Re:" Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Machine 1: If the CD-ROM is connected to the Sound Blaster card you are out of luck since the IDE interface on the card is a 3rd IDE (even if you only have one) and is not supported. Machine 2: FreeBSD needs (at least when I had tried the same thing once) to boot off of one of the 2 first BIOS Drives. You could try moving the HD around to try it. A possible solution could be to use a DOS based loader (I used to use one on Linux, but I haven't tried any of the FreeBSD type of loaders), perhaps some one else here can explain how to copy the kernel to the C drive and run the loader app. David Botton ---------- From: cliff To: stable Subject: Re: help help I'm being repressed Date: Monday, September 29, 1997 6:18AM <> of all the particulars I forgot the most important................... 2.2.2 stable thanks, I'll also send it questions@freebsd.org -cliff ------------------------------------------------------------------------------ CLIFFSWORLD homepage------------ "Open Throttle" automotive e-zine- Quake-Clan "RIP" homepage------------- p.o. box 1055, Maywood NJ, 07607-7055 fone 201-843-0936 PGP v5.0 public key available "never drive faster than your guardian angels can fly" From owner-freebsd-stable Mon Sep 29 08:26:45 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id IAA16474 for stable-outgoing; Mon, 29 Sep 1997 08:26:45 -0700 (PDT) Received: from word.smith.net.au (ppp20.portal.net.au [202.12.71.120]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id IAA16469 for ; Mon, 29 Sep 1997 08:26:39 -0700 (PDT) Received: from word.smith.net.au (localhost.smith.net.au [127.0.0.1]) by word.smith.net.au (8.8.7/8.8.5) with ESMTP id AAA00664; Tue, 30 Sep 1997 00:53:37 +0930 (CST) Message-Id: <199709291523.AAA00664@word.smith.net.au> X-Mailer: exmh version 2.0zeta 7/24/97 To: David.Botton@grace.com cc: cliff@cliffsworld.com, stable@FreeBSD.ORG Subject: Re: help help I'm being repressed In-reply-to: Your message of "Mon, 29 Sep 1997 10:51:10 -0400." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 30 Sep 1997 00:53:35 +0930 From: Mike Smith Sender: owner-freebsd-stable@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > Machine 1: > If the CD-ROM is connected to the Sound Blaster card you are out of > luck since the IDE interface on the card is a 3rd IDE (even if you only > have one) and is not supported. This is not correct; simply adjust the address and interrupt assignments of the second IDE controller channel (wdc1) to match that of the card, and it will work. mike From owner-freebsd-stable Mon Sep 29 08:35:35 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id IAA17034 for stable-outgoing; Mon, 29 Sep 1997 08:35:35 -0700 (PDT) Received: from gate.corp.wrgrace.com (wrgrace.com [208.221.196.2]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id IAA17019 for ; Mon, 29 Sep 1997 08:35:31 -0700 (PDT) From: David.Botton@grace.com Received: from wrgicon.corp.wrgrace.com by gate.corp.wrgrace.com via smtpd (for hub.FreeBSD.ORG [204.216.27.18]) with SMTP; 29 Sep 1997 15:35:28 UT Received: by corp.wrgrace.com; id LAA22075; Mon, 29 Sep 1997 11:33:19 -0400 (EDT) Received: by grace.com; ID AA249817774; Mon, 29 Sep 1997 11:42:54 -0400 X-Openmail-Hops: 1 Date: Mon, 29 Sep 97 11:42:42 -0400 Message-Id: <776A02A8@MHS> Subject: Re: help help I'm being repressed Mime-Version: 1.0 To: mike@smith.net.au Cc: cliff@cliffsworld.com, stable@FreeBSD.ORG Content-Type: text/plain; charset=US-ASCII; name="Re:" Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Thanks, I didn't know you could change the channel on the SBs, but If he already has 2 channels (like that found on most motherboards) he wouldn't be able to change it unless he can disable one of the channels on the MB or card. DB ---------- From: mike To: Botton, David Cc: cliff; stable Subject: Re: help help I'm being repressed Date: Monday, September 29, 1997 8:23AM <> > Machine 1: > If the CD-ROM is connected to the Sound Blaster card you are out of > luck since the IDE interface on the card is a 3rd IDE (even if you only > have one) and is not supported. This is not correct; simply adjust the address and interrupt assignments of the second IDE controller channel (wdc1) to match that of the card, and it will work. mike From owner-freebsd-stable Mon Sep 29 08:51:06 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id IAA17998 for stable-outgoing; Mon, 29 Sep 1997 08:51:06 -0700 (PDT) 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 IAA17988 for ; Mon, 29 Sep 1997 08:51:03 -0700 (PDT) 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 KAA15664 for <@mailhost.uiuc.edu:freebsd-stable@freebsd.org>; Mon, 29 Sep 1997 10:50:30 -0500 (CDT) Received: by alecto.physics.uiuc.edu (940816.SGI.8.6.9/940406.SGI) for freebsd-stable@freebsd.org id KAA21781; Mon, 29 Sep 1997 10:45:06 -0500 From: igor@alecto.physics.uiuc.edu (Igor Roshchin) Message-Id: <199709291545.KAA21781@alecto.physics.uiuc.edu> Subject: Re: Stable kernels crashes on two machines. WAS: CVSUP woes for stable branch To: freebsd-stable@freebsd.org Date: Mon, 29 Sep 1997 10:45:05 -0500 (CDT) In-Reply-To: from "Bohdan Kmit'" at Sep 29, 97 02:53:37 pm X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-freebsd-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > On Mon, 29 Sep 1997, Palle Girgensohn wrote: > > > Jay West (jlwest@tseinc.com) wrote: > > > > >Maybe someone can shed some light on this... > > > > > >I installed 2.2.2-Release via FTP. All went well. I then > > >grabbed the staticly linked copy of CVSup, and the > > >supfile from www.freebsd.org. I ran cvsup supfile intending > > >to go to -stable, and it appeared to bring down a fairly small > > >number of files. I tried a make world, but the makefile no longer > > >includes that option. So... I just did a make depend and make > > >and make install. Rebooted the system, and whammo - wouldn't > > >reboot. It kept complaining about page fault panic or such, and > > >just kept autobooting, running fsck, then autobooting etc. > > > > > >I ran cvsup pointed at sup.freebsd.org on sunday, September 28 > > >at around 9:00am. > > > > > >Anyone have any ideas? > > > > > >Thanks in advance! > > > > > >Jay West (jlwest@tseinc.com) > > > > > >Unix *IS* user friendly; It's just selective about who it calls a friend! > > > > I have a similar problem. > > > > After installing 2.2.2 Release, I fetched the stable-src and ports, > > compiled cvsup port (not statically linked here...) and recompiled the > > kernel. Then I rebooted, and everything went black. This was done remote... > > :( I pinged to check, but it never came up. I went to the box today and it > > "kept autobooting, running fsck, then autobooting etc.". > > > > This was with a PPro 200. I also did the same thing with a 486 dx2/66 at > > home. I installed Release 222 and cvsup (dynamically linked, but version > > 15.0) from a CD this time (as opposed to ftp above). This kernel doesn't > > work either, but not in the same way, and it does give me a few lines of > > explanation before i dies: > > > > rc.i386 configuring syscons: keymap keyrate font8x16 font8x14 font 8x8 > > screensaver > > > > Fatal trap 12: page fault while in kernel mode > > fault virtual address = 0x0 > > fault code = supervisor read, page not present > > instruction pointer = 0x8:0x0 > > stack pointer = 0x10:0xefbffd74 > > frame pointer = 0x10:0xefbffd7c > > 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 = 137 (modload) > > interrupt mask = > > panic: page fault > > > > syncing disk... 30 30 27 21 7 done > > Automatic reboot in 15 secs..... > > > > > > Any ideas? The setups are quite different, and have different config files. > > > > Regards, > > Palle > > > > > > ________________________________________________________________________ > > Palle Girgensohn Partitur Informationsteknik AB > > girgen@partitur.se http://www.partitur.se/ > > > > > > > > > I had this problem too on two boxes. Solution was simple -- > all lkm's recompilation. Look like interface beetwen kernel and lkm > changed. > > Hope this help. > > With regards, > Bohdan. > > --------------------------------------------------------------- > Bohdan Kmit' | +380 (322) 742339 > Laboratory of Information Technologies | > L'viv, Ukraine | mit@LITech.Lviv.UA > --------------------------------------------------------------- > > Is that true ? What is the correct sequence than ? I had about the same problem about two weeks ago (did not have time to get back to it since) - First: Installation from the the CD-ROM: 2.2.2-RELEASE FreeBSD 2.2.2-RELEASE #0: Tue May 20 10:45:24 GMT 1997 jkh@tim e.cdrom.com:/usr/src/sys/compile/GENERIC i386 Then I took the source tree and cvsup-ed the changes. Compiled kernel (generic one) did not want to boot and every time was stuck at the message "starting network, hostname.." (or something like that) IgoR From owner-freebsd-stable Mon Sep 29 10:29:55 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id KAA24431 for stable-outgoing; Mon, 29 Sep 1997 10:29:55 -0700 (PDT) Received: from Big.LITech.Lviv.UA (root@Big.LITech.Lviv.UA [193.232.65.2]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id KAA24415 for ; Mon, 29 Sep 1997 10:29:23 -0700 (PDT) Received: from ah.litech.lviv.ua (Ah.LITech.Lviv.UA [193.232.65.1]) by Big.LITech.Lviv.UA (8.8.5/8.7.3) with SMTP id UAA20226; Mon, 29 Sep 1997 20:28:30 +0300 (EET DST) Date: Mon, 29 Sep 1997 20:28:29 +0300 (EEST) From: "Bohdan Kmit'" To: Igor Roshchin cc: freebsd-stable@FreeBSD.ORG Subject: Re: Stable kernels crashes on two machines. WAS: CVSUP woes for stable branch In-Reply-To: <199709291545.KAA21781@alecto.physics.uiuc.edu> 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, 29 Sep 1997, Igor Roshchin wrote: > > > > > > I had this problem too on two boxes. Solution was simple -- > > all lkm's recompilation. Look like interface beetwen kernel and lkm > > changed. > > > > Hope this help. > > > > With regards, > > Bohdan. > > > > --------------------------------------------------------------- > > Bohdan Kmit' | +380 (322) 742339 > > Laboratory of Information Technologies | > > L'viv, Ukraine | mit@LITech.Lviv.UA > > --------------------------------------------------------------- > > > > > > > Is that true ? What is the correct sequence than ? > > I had about the same problem about two weeks ago > (did not have time to get back to it since) - > First: Installation from the the CD-ROM: > 2.2.2-RELEASE FreeBSD 2.2.2-RELEASE #0: Tue May 20 10:45:24 GMT 1997 jkh@tim > e.cdrom.com:/usr/src/sys/compile/GENERIC i386 > > Then I took the source tree and cvsup-ed the changes. > > Compiled kernel (generic one) did not want to boot > and every time was stuck at the message "starting network, hostname.." > (or something like that) > > > IgoR > > To be more precise -- kernel panicing where screen saver module was loaded. You can boot is single user mode (-s), remount root filesystem in readwrite mode, edit /etc/rc.conf then reboot in multiuser. Hope this help. With regards, Bohdan. --------------------------------------------------------------- Bohdan Kmit' | +380 (322) 742339 Laboratory of Information Technologies | L'viv, Ukraine | mit@LITech.Lviv.UA --------------------------------------------------------------- From owner-freebsd-stable Mon Sep 29 10:46:16 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id KAA25365 for stable-outgoing; Mon, 29 Sep 1997 10:46:16 -0700 (PDT) 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 KAA25356 for ; Mon, 29 Sep 1997 10:46:14 -0700 (PDT) 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 MAA28020; Mon, 29 Sep 1997 12:45:39 -0500 (CDT) Received: by alecto.physics.uiuc.edu (940816.SGI.8.6.9/940406.SGI) id MAA03023; Mon, 29 Sep 1997 12:40:15 -0500 From: igor@alecto.physics.uiuc.edu (Igor Roshchin) Message-Id: <199709291740.MAA03023@alecto.physics.uiuc.edu> Subject: Re: Stable kernels crashes on two machines. WAS: CVSUP woes for stable branch To: mit@LITech.Lviv.UA (Bohdan Kmit') Date: Mon, 29 Sep 1997 12:40:15 -0500 (CDT) Cc: freebsd-stable@FreeBSD.ORG In-Reply-To: from "Bohdan Kmit'" at Sep 29, 97 08:28:29 pm X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-freebsd-stable@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > On Mon, 29 Sep 1997, Igor Roshchin wrote: > > > > > > > > > > I had this problem too on two boxes. Solution was simple -- > > > all lkm's recompilation. Look like interface beetwen kernel and lkm > > > changed. > > > > > > Hope this help. > > > > > > With regards, > > > Bohdan. > > > > > > --------------------------------------------------------------- > > > Bohdan Kmit' | +380 (322) 742339 > > > Laboratory of Information Technologies | > > > L'viv, Ukraine | mit@LITech.Lviv.UA > > > --------------------------------------------------------------- > > > > > > > > > > > > Is that true ? What is the correct sequence than ? > > > > I had about the same problem about two weeks ago > > (did not have time to get back to it since) - > > First: Installation from the the CD-ROM: > > 2.2.2-RELEASE FreeBSD 2.2.2-RELEASE #0: Tue May 20 10:45:24 GMT 1997 jkh@tim > > e.cdrom.com:/usr/src/sys/compile/GENERIC i386 > > > > Then I took the source tree and cvsup-ed the changes. > > > > Compiled kernel (generic one) did not want to boot > > and every time was stuck at the message "starting network, hostname.." > > (or something like that) > > > > > > IgoR > > > > > > To be more precise -- kernel panicing where screen saver module was > loaded. You can boot is single user mode (-s), remount root filesystem in > readwrite mode, edit /etc/rc.conf then reboot in multiuser. > > Hope this help. > > With regards, > Bohdan. > I don't think so, because I have saver="NO" # screen saver desired: blank/green/snake/star/NO. in my /etc/rc.conf IgoR From owner-freebsd-stable Mon Sep 29 10:49:49 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id KAA25612 for stable-outgoing; Mon, 29 Sep 1997 10:49:49 -0700 (PDT) Received: from palrel3.hp.com (palrel3.hp.com [156.153.255.219]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id KAA25606; Mon, 29 Sep 1997 10:49:46 -0700 (PDT) Received: from srmail.sr.hp.com (srmail.sr.hp.com [15.4.45.14]) by palrel3.hp.com (8.8.5/8.8.5tis) with ESMTP id KAA03060; Mon, 29 Sep 1997 10:49:34 -0700 (PDT) Received: from mina.sr.hp.com by srmail.sr.hp.com with ESMTP (1.37.109.16/15.5+ECS 3.3) id AA175415373; Mon, 29 Sep 1997 10:49:33 -0700 Received: from mina.sr.hp.com by mina.sr.hp.com with SMTP (1.37.109.16/15.5+ECS 3.3) id AA280885372; Mon, 29 Sep 1997 10:49:32 -0700 Message-Id: <199709291749.AA280885372@mina.sr.hp.com> To: hardware@FreeBSD.ORG, stable@FreeBSD.ORG Subject: Re: K6 Update & AMD Statement Reply-To: darrylo@sr.hp.com In-Reply-To: Your message of "Sat, 27 Sep 1997 12:43:35 EDT." <199709271643.MAA17859@sabre.goldsword.com> Mime-Version: 1.0 (generated by tm-edit 7.106) Content-Type: text/plain; charset=US-ASCII Date: Mon, 29 Sep 1997 10:49:32 -0700 From: Darryl Okahata Sender: owner-freebsd-stable@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk "John T. Farmer" wrote: > On Sat, 27 Sep 1997 18:04:53 +0200 Poul-Henning Kamp said: > >I have a K6/233 here which has by now completed 50 or more make worlds, > >no complaints. > > > >It is marked: > > AMD-K6-233ANR > > 3.2V CORE / 3.3V I/O > > B 9731EJBW > ^^^^^^^^ > > This is what I'm told is the important part. The stepping must be 9731 or > later. This looks like a date code (when the IC was manufactured), and not a stepping. If it is a date code, "9731" would be the 31st week of 1997, which is the last week in July. -- Darryl Okahata Internet: darrylo@sr.hp.com DISCLAIMER: this message is the author's personal opinion and does not constitute the support, opinion, or policy of Hewlett-Packard, or of the little green men that have been following him all day. From owner-freebsd-stable Mon Sep 29 10:55:45 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id KAA26033 for stable-outgoing; Mon, 29 Sep 1997 10:55:45 -0700 (PDT) Received: from Big.LITech.Lviv.UA (root@Big.LITech.Lviv.UA [193.232.65.2]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id KAA26018 for ; Mon, 29 Sep 1997 10:55:38 -0700 (PDT) Received: from ah.litech.lviv.ua (Ah.LITech.Lviv.UA [193.232.65.1]) by Big.LITech.Lviv.UA (8.8.5/8.7.3) with SMTP id UAA21287; Mon, 29 Sep 1997 20:55:11 +0300 (EET DST) Date: Mon, 29 Sep 1997 20:55:11 +0300 (EEST) From: "Bohdan Kmit'" To: Igor Roshchin cc: freebsd-stable@FreeBSD.ORG Subject: Re: Stable kernels crashes on two machines. WAS: CVSUP woes for stable branch In-Reply-To: <199709291740.MAA03023@alecto.physics.uiuc.edu> 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, 29 Sep 1997, Igor Roshchin wrote: > > I don't think so, because I have > saver="NO" # screen saver desired: blank/green/snake/star/NO. > in my /etc/rc.conf > > IgoR > In my case panic was caused by screen saver module (the only one loaded in my config). Try to recompile all lkms - this can help, I thik. With regards, Bohdan. --------------------------------------------------------------- Bohdan Kmit' | +380 (322) 742339 Laboratory of Information Technologies | L'viv, Ukraine | mit@LITech.Lviv.UA --------------------------------------------------------------- From owner-freebsd-stable Mon Sep 29 15:43:03 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id PAA15717 for stable-outgoing; Mon, 29 Sep 1997 15:43:03 -0700 (PDT) Received: from ramsack.baldcom.net (RAMSACK.BALDCOM.NET [205.232.46.4]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id PAA15712 for ; Mon, 29 Sep 1997 15:42:59 -0700 (PDT) Received: from [205.232.46.135] by ramsack.baldcom.net with ESMTP (SMTPD32-4.02) id AF6D1290030; Mon, 29 Sep 1997 18:45:01 EST5EDT Message-Id: In-Reply-To: <10543.875521510@time.cdrom.com> References: Your message of "Mon, 29 Sep 1997 02:08:29 EDT." <3.0.3.32.19970929020829.00734238@mail.internexus.net> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Mon, 29 Sep 1997 18:39:49 +0100 To: stable@FreeBSD.ORG From: Ken McKittrick Subject: make depend fails Sender: owner-freebsd-stable@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Hello Make depend fails on a recently cvsup'd as of 9-29 2.2-Stable. The system has two PCI SCSI controllers Adaptec 2940UW and 3940UW. I following the Compiling a custom kernel directions from the FreeBSD handbook. What am am i doing wrong? Sincerely Ken Here's the make depend # cd ../../compile/ZONE # make depend cc -c -O -Wreturn-type -Wcomment -Wredundant-decls -Wimplicit -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -nostdinc -I- -I. -I. ./.. -I../../../include -DAPM_BROKEN_STATCLOCK -DNSWAPDEV=4 -DFAILSAFE -DCOMPAT_ 43 -DMSDOSFS -DNFS -DFFS -DINET -DKERNEL -DMAXUSERS=40 -UKERNEL ../../i386/i386/ genassym.c cc -O -Wreturn-type -Wcomment -Wredundant-decls -Wimplicit -Wnested-externs -Ws trict-prototypes -Wmissing-prototypes -Wpointer-arith -nostdinc -I- -I. -I../. . -I../../../include -DAPM_BROKEN_STATCLOCK -DNSWAPDEV=4 -DFAILSAFE -DCOMPAT_43 -DMSDOSFS -DNFS -DFFS -DINET -DKERNEL -DMAXUSERS=40 genassym.o -o genassym ./genassym >assym.s rm -f param.c cp ../../conf/param.c . sh ../../kern/vnode_if.sh ../../kern/vnode_if.src make -f ../../dev/aic7xxx/Makefile MAKESRCPATH=../../dev/aic7xxx Warning: Object directory not changed from original /usr/src/sys/compile/ZONE yacc -d ../../dev/aic7xxx/aicasm_gram.y mv y.tab.c aicasm_gram.c cc -O -pipe -I. -c aicasm_gram.c lex -t ../../dev/aic7xxx/aicasm_scan.l > aicasm_scan.c cc -O -pipe -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. ------------------------------------------------------------ Ken McKittrick SysAdmin, Network Engineer agent47@baldcom.net FreeBSD, NT and the Mac OS http://zone.baldcom.net (315) 698-3400 "Virtute non Verbis" (Deeds not Words) 1/108th Mech Infantry From owner-freebsd-stable Mon Sep 29 16:55:31 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id QAA19079 for stable-outgoing; Mon, 29 Sep 1997 16:55:31 -0700 (PDT) Received: from counterintelligence.ml.org (mdean.vip.best.com [206.86.94.101]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id QAA19074 for ; Mon, 29 Sep 1997 16:55:27 -0700 (PDT) Received: from localhost (jamil@localhost) by counterintelligence.ml.org (8.8.7/8.8.5) with SMTP id QAA00178 for ; Mon, 29 Sep 1997 16:54:38 -0700 (PDT) Date: Mon, 29 Sep 1997 16:54:38 -0700 (PDT) From: "Jamil J. Weatherbee" To: freebsd-stable@freebsd.org Subject: Natd Problems 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 enabled natd to do translation for a lan of windows machines, I have noticed that netscape 3.1 works fine but communicator 4.0 half opens web pages and never finishes consistently, is there an explanation for this? I tested this on many different machines on the network. From owner-freebsd-stable Mon Sep 29 18:42:55 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id SAA23801 for stable-outgoing; Mon, 29 Sep 1997 18:42:55 -0700 (PDT) Received: from pluto.plutotech.com (root@mail.plutotech.com [206.168.67.137]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id SAA23793 for ; Mon, 29 Sep 1997 18:42:51 -0700 (PDT) Received: from narnia.plutotech.com (narnia.plutotech.com [206.168.67.130]) by pluto.plutotech.com (8.8.5/8.8.5) with ESMTP id TAA23710; Mon, 29 Sep 1997 19:42:41 -0600 (MDT) Message-Id: <199709300142.TAA23710@pluto.plutotech.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: Ken McKittrick cc: stable@FreeBSD.ORG Subject: Re: make depend fails In-reply-to: Your message of "Mon, 29 Sep 1997 18:39:49 BST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 29 Sep 1997 19:42:14 -0600 From: "Justin T. Gibbs" Sender: owner-freebsd-stable@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >Hello > >Make depend fails on a recently cvsup'd as of 9-29 2.2-Stable. The system >has two PCI SCSI controllers Adaptec 2940UW and 3940UW. > >I following the Compiling a custom kernel directions from the FreeBSD handbook >. > >What am am i doing wrong? I don't know. I just checked out a 2.2-stable sys tree and the assembler built and assembled the sequencer code just fine. >Sincerely >Ken -- Justin T. Gibbs =========================================== FreeBSD: Turning PCs into workstations =========================================== From owner-freebsd-stable Mon Sep 29 19:02:58 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id TAA24826 for stable-outgoing; Mon, 29 Sep 1997 19:02:58 -0700 (PDT) Received: from word.smith.net.au (ppp20.portal.net.au [202.12.71.120]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id TAA24821 for ; Mon, 29 Sep 1997 19:02:49 -0700 (PDT) Received: from word.smith.net.au (localhost.smith.net.au [127.0.0.1]) by word.smith.net.au (8.8.7/8.8.5) with ESMTP id LAA02184; Tue, 30 Sep 1997 11:29:59 +0930 (CST) Message-Id: <199709300159.LAA02184@word.smith.net.au> X-Mailer: exmh version 2.0zeta 7/24/97 To: David.Botton@grace.com cc: mike@smith.net.au, cliff@cliffsworld.com, stable@FreeBSD.ORG Subject: Re: help help I'm being repressed In-reply-to: Your message of "Mon, 29 Sep 1997 11:42:42 -0400." <776A02A8@MHS> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 30 Sep 1997 11:29:57 +0930 From: Mike Smith Sender: owner-freebsd-stable@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > Thanks, I didn't know you could change the channel on the SBs, but If > he already has 2 channels (like that found on most motherboards) he > wouldn't be able to change it unless he can disable one of the channels > on the MB or card. You fail to understand. Use Userconfig (ie. boot with -c as documented in the installation instructions) to modify the base address and IRQ settings assigned to the 'wdc1' driver such that the IDE interface on the SB card is found instead of the second onboard IDE channel. This really belongs on -questions. > DB > > ---------- > From: mike > To: Botton, David > Cc: cliff; stable > Subject: Re: help help I'm being repressed > Date: Monday, September 29, 1997 8:23AM > > <> > > Machine 1: > > If the CD-ROM is connected to the Sound Blaster card you are out of > > luck since the IDE interface on the card is a 3rd IDE (even if you only > > have one) and is not supported. > > This is not correct; simply adjust the address and interrupt > assignments of the second IDE controller channel (wdc1) to match that > of the card, and it will work. > > mike > > > From owner-freebsd-stable Mon Sep 29 21:46:10 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id VAA01886 for stable-outgoing; Mon, 29 Sep 1997 21:46:10 -0700 (PDT) Received: from gras-varg.worldgate.com (skafte@gras-varg.worldgate.com [198.161.84.12]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id VAA01855; Mon, 29 Sep 1997 21:45:55 -0700 (PDT) Received: (from skafte@localhost) by gras-varg.worldgate.com (8.8.7/8.6.12) id WAA06419; Mon, 29 Sep 1997 22:45:54 -0600 (MDT) Message-ID: <19970929224553.56867@worldgate.com> Date: Mon, 29 Sep 1997 22:45:53 -0600 From: Greg Skafte To: freebsd-stable@freebsd.org Cc: Freebsd-hackers@freebsd.org Subject: libncurses ..... Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.84 Organization: WorldGate Inc. X-PGP-Fingerprint: 42 9C 2C A8 4D 2B C9 C4 7D B6 00 B0 50 47 20 97 X-URL: http://gras-varg.worldgate.com/~skafte Sender: owner-freebsd-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Outta curiosity for libncurses why are we using 1.8.6 instead of the current 4.1 in 2.2-stable ..... -- Email: skafte@worldgate.com Voice: +403 413 1910 Fax: +403 421 4929 #575 Sun Life Place * 10123 99 Street * Edmonton, AB * Canada * T5J 3H1 -- -- When things can't get any worse, they simplify themselves by getting a whole lot worse then complicated. A complete and utter disaster is the simplest thing in the world; it's preventing one that's complex. (Janet Morris) From owner-freebsd-stable Mon Sep 29 23:34:10 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id XAA06430 for stable-outgoing; Mon, 29 Sep 1997 23:34:10 -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 XAA06421 for ; Mon, 29 Sep 1997 23:34:03 -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 HAA12801; Tue, 30 Sep 1997 07:31:20 +0100 (BST) Message-Id: <199709300631.HAA12801@awfulhak.demon.co.uk> X-Mailer: exmh version 2.0zeta 7/24/97 To: "Jamil J. Weatherbee" cc: freebsd-stable@FreeBSD.ORG Subject: Re: Natd Problems In-reply-to: Your message of "Mon, 29 Sep 1997 16:54:38 PDT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 30 Sep 1997 07:31:19 +0100 From: Brian Somers Sender: owner-freebsd-stable@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > I recently enabled natd to do translation for a lan of windows machines, I > have noticed that netscape 3.1 works fine but communicator 4.0 half opens > web pages and never finishes consistently, is there an explanation for > this? I tested this on many different machines on the network. I take it we're talking natd 1.10 (from after Sep 7 in -stable). You'll need to give details of your config. You could also try the -v switch and see if anything obvious is happening. -- Brian , , Don't _EVER_ lose your sense of humour.... From owner-freebsd-stable Mon Sep 29 23:57:29 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id XAA07564 for stable-outgoing; Mon, 29 Sep 1997 23:57:29 -0700 (PDT) Received: from palrel1.hp.com (palrel1.hp.com [156.153.255.235]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id XAA07559 for ; Mon, 29 Sep 1997 23:57:27 -0700 (PDT) Received: from postbox.india.hp.com (postbox.india.hp.com [15.10.45.1]) by palrel1.hp.com (8.8.6/8.8.5tis) with ESMTP id XAA13301 for ; Mon, 29 Sep 1997 23:57:21 -0700 (PDT) Message-Id: <199709300657.XAA13301@palrel1.hp.com> Received: from localhost by postbox.india.hp.com with ESMTP (1.39.111.2/16.2) id AA233712380; Tue, 30 Sep 1997 12:23:00 +0530 To: freebsd-stable@freebsd.org Subject: 2.2-STABLE usr.sbin/wlconfig uses net/if_var.h Date: Tue, 30 Sep 1997 12:22:59 +0530 From: A Joseph Koshy Sender: owner-freebsd-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi, 2.2-STABLE as of yesterday: "make world"s been falling over regularly in usr.sbin/wlconfig and I finally got around to examining the problem. "wlconfig.c" seems to be including . However, this file doesn't seem part of the 2.2 branch, could someone pl. fix? Koshy My personal opinions only. From owner-freebsd-stable Tue Sep 30 01:05:33 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id BAA11506 for stable-outgoing; Tue, 30 Sep 1997 01:05:33 -0700 (PDT) Received: from GndRsh.aac.dev.com (GndRsh.aac.dev.com [198.145.92.241]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id BAA11496 for ; Tue, 30 Sep 1997 01:05:26 -0700 (PDT) Received: (from rgrimes@localhost) by GndRsh.aac.dev.com (8.8.5/8.7.3) id AAA23122; Tue, 30 Sep 1997 00:58:46 -0700 (PDT) From: "Rodney W. Grimes" Message-Id: <199709300758.AAA23122@GndRsh.aac.dev.com> Subject: Re: 2.2-STABLE usr.sbin/wlconfig uses net/if_var.h In-Reply-To: <199709300657.XAA13301@palrel1.hp.com> from A Joseph Koshy at "Sep 30, 97 12:22:59 pm" To: koshy@india.hp.com (A Joseph Koshy) Date: Tue, 30 Sep 1997 00:58:45 -0700 (PDT) Cc: 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 > > Hi, > > 2.2-STABLE as of yesterday: > > "make world"s been falling over regularly in usr.sbin/wlconfig and I finally > got around to examining the problem. "wlconfig.c" seems to be including > . However, this file doesn't seem part of the 2.2 branch, > could someone pl. fix? Some how you have the 3.0-current version of usr.sbin/wlconfig/wlconfig.c, what is the $Id$ in your version of the file? It should be 1.4.2.1. -- Rod Grimes rgrimes@gndrsh.aac.dev.com Accurate Automation, Inc. Reliable computers for FreeBSD From owner-freebsd-stable Tue Sep 30 06:16:09 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id GAA24663 for stable-outgoing; Tue, 30 Sep 1997 06:16:09 -0700 (PDT) Received: from unix.nmarcom.com (root@host-034.nmarcom.com [207.181.124.34]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id GAA24655 for ; Tue, 30 Sep 1997 06:16:04 -0700 (PDT) Received: from [207.181.124.43] (host-043.nmarcom.com [207.181.124.43]) by unix.nmarcom.com (8.8.7/8.8.5) with ESMTP id JAA14845 for ; Tue, 30 Sep 1997 09:15:55 -0400 (EDT) X-Sender: thelab@mail.nmarcom.com Message-Id: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Tue, 30 Sep 1997 09:15:57 -0400 To: freebsd-stable@freebsd.org From: Will Mitayai Keeso Rowe Subject: make world fails on sendmail.cf Sender: owner-freebsd-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hallo! Last night before i left work at 5:15 EDT i ran a make update ; make world on 2.2-STABLE, and got the following error: ===> usr.sbin/sendmail/cf/cf rm -f freebsd.cf (cd /usr/src/usr.sbin/sendmail/cf/cf && m4 ../m4/cf.m4 freebsd.mc) > freebsd.cf m4: eval: major botch *** Error code 1 Stop. *** Error code 1 Stop. *** Error code 1 Stop. *** Error code 1 Stop. *** Error code 1 Stop. *** Error code 1 Stop. [unix:root]/usr/src# The odd thing, though, is that i have got this error mant times before, so it makes me think that there is something odd about my machine, a former 2.2.2-RELEASE system. Does anyone have any ideas based on their experiences? Is there a fix that i'm forgetting? -Mit From owner-freebsd-stable Tue Sep 30 15:05:47 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id PAA24901 for stable-outgoing; Tue, 30 Sep 1997 15:05:47 -0700 (PDT) Received: from gdi.uoregon.edu (gdi.uoregon.edu [128.223.170.30]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id PAA24892; Tue, 30 Sep 1997 15:05:41 -0700 (PDT) Received: from localhost (dwhite@localhost) by gdi.uoregon.edu (8.8.5/8.8.5) with SMTP id PAA23264; Tue, 30 Sep 1997 15:05:38 -0700 (PDT) Date: Tue, 30 Sep 1997 15:05:38 -0700 (PDT) From: Doug White Reply-To: Doug White To: Jay Richmond cc: freebsd-questions@FreeBSD.ORG, freebsd-stable@FreeBSD.ORG Subject: Re: booting new kernel... problems In-Reply-To: <01IO5PIHPMPQ8X1ORL@RoseVC.Rose-Hulman.Edu> 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, 28 Sep 1997, Jay Richmond wrote: > I built a new 2.2-stable kernel as of today and everything compiled > fine... Then when I tried to reboot, I got the following messages: > > Boot: > > dosdev= 80, biosdrive = 0, unit = 0, maj = 4 > > Invalid format! > > after that it goes in a countinuous loop... have I done something wrong > here? or is there something I should be doing? i can boot the old > kernel just fine by using /kernel.old iused the same config file that i > used for the old kernel (which was also a recent 2.2-stable kernel). Did you run `make install' to copy the kernel over? You might mention when you grabbed the sources last. Doug White | University of Oregon Internet: dwhite@resnet.uoregon.edu | Residence Networking Assistant http://gladstone.uoregon.edu/~dwhite | Computer Science Major From owner-freebsd-stable Tue Sep 30 17:35:00 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id RAA03759 for stable-outgoing; Tue, 30 Sep 1997 17:35:00 -0700 (PDT) Received: from gate.usaor.net (root@gate.usaor.net [204.157.146.1]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id RAA03746 for ; Tue, 30 Sep 1997 17:34:57 -0700 (PDT) Received: from drbovill.usaor.net (rs1ip43.usaor.net [209.114.136.43]) by gate.usaor.net (8.8.5/8.8.5) with ESMTP id UAA22669 for ; Tue, 30 Sep 1997 20:34:51 -0400 (EDT) Message-ID: <34319AA2.71BEE1F0@usaor.net> Date: Tue, 30 Sep 1997 20:34:42 -0400 From: Family Reply-To: almighty1@thepentagon.com Organization: My Company X-Mailer: Mozilla 4.01 [en] (Win95; I) MIME-Version: 1.0 To: freebsd-stable@FreeBSD.ORG Subject: (no subject) X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk subscribe freebsd-stable From owner-freebsd-stable Tue Sep 30 18:05:19 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id SAA05789 for stable-outgoing; Tue, 30 Sep 1997 18:05:19 -0700 (PDT) Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id SAA05777 for ; Tue, 30 Sep 1997 18:05:12 -0700 (PDT) Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.7/8.6.9) with ESMTP id SAA10639 for ; Tue, 30 Sep 1997 18:05:12 -0700 (PDT) To: freebsd-stable@freebsd.org Subject: Final notice: 2.2 branch code freeze is coming up. Date: Tue, 30 Sep 1997 18:05:12 -0700 Message-ID: <10635.875667912@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Code freeze for the RELENG_2_2 branch will be at 23:59 PST 9/30/97 (how's *that* for pedantic! :), approximately 6 hours from now. At some point during the 48 hour period thereafter, one scenario might be that I tag the tree for 2.2.5-BETA, roll a release from it and put it up at ftp.freebsd.org. We'd then go into our 20 day BETA period, during which time everyone would obviously be encouraged to install and test that release as much as possible. I say "one scenario" because there's also something rather different about this BETA period vs previous release BETAs and that's the existance of the ftp://releng22.freebsd.org/pub/FreeBSD/2.2-YYMMDD-RELENG ~daily releases. As people find bugs in 2.2.5-BETA and those are fixed, that progress will be reflected in the ongoing 2.2 snapshots available from the server and it would obviously make more sense for people to to install the snaps over 2.2.5-BETA if given the chance since why would you want to stumble over bugs already fixed? This holds especially true once we get close to 2.2-971015-RELENG or so since we're going to be in the final week's countdown to release and will want to give those last few releases very close scrutiny indeed. So, this all sort of raises the very obvious question and that is "Just what the heck is an official 2.2.5-BETA release good for if it's only going to be rendered essentially obsolete 24 hours later when the 2.2 SNAP server cranks out another full release? Why not just point at the 2.2.5-971001-RELENG snapshot and say "There, that's the BETA. Testers, please start your engines!" If people have connectivity problems to releng22.freebsd.org up there in Canada, I could even buffer up the last few day's worth of 2.2 SNAPs on ftp.freebsd.org. Comments? Jordan From owner-freebsd-stable Tue Sep 30 18:43:40 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id SAA07837 for stable-outgoing; Tue, 30 Sep 1997 18:43:40 -0700 (PDT) Received: from shasta.wstein.com (joes@shasta.wstein.com [207.173.11.132]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id SAA07830 for ; Tue, 30 Sep 1997 18:43:34 -0700 (PDT) Received: (from joes@localhost) by shasta.wstein.com (8.8.7/8.8.7) id SAA02110; Tue, 30 Sep 1997 18:43:23 -0700 (PDT) From: Joseph Stein Message-Id: <199710010143.SAA02110@shasta.wstein.com> Subject: Re: Final notice: 2.2 branch code freeze is coming up. In-Reply-To: <10635.875667912@time.cdrom.com> from "Jordan K. Hubbard" at "Sep 30, 97 06:05:12 pm" To: jkh@time.cdrom.com (Jordan K. Hubbard) Date: Tue, 30 Sep 1997 18:43:22 -0700 (PDT) Cc: freebsd-stable@FreeBSD.ORG 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 > So, this all sort of raises the very obvious question and that is > "Just what the heck is an official 2.2.5-BETA release good for if it's > only going to be rendered essentially obsolete 24 hours later when the > 2.2 SNAP server cranks out another full release? Why not just point > at the 2.2.5-971001-RELENG snapshot and say "There, that's the BETA. > Testers, please start your engines!" So, you call the releases at releng22.freebsd.org 2.2.5-971001-BETA ?? My $.02 joe From owner-freebsd-stable Tue Sep 30 18:54:34 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id SAA08324 for stable-outgoing; Tue, 30 Sep 1997 18:54:34 -0700 (PDT) Received: from counterintelligence.ml.org (mdean.vip.best.com [206.86.94.101]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id SAA08315 for ; Tue, 30 Sep 1997 18:54:28 -0700 (PDT) Received: from localhost (jamil@localhost) by counterintelligence.ml.org (8.8.7/8.8.5) with SMTP id SAA00232; Tue, 30 Sep 1997 18:54:09 -0700 (PDT) Date: Tue, 30 Sep 1997 18:54:09 -0700 (PDT) From: "Jamil J. Weatherbee" To: Brian Somers cc: freebsd-stable@FreeBSD.ORG Subject: Re: Natd Problems In-Reply-To: <199709300631.HAA12801@awfulhak.demon.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 The configuration is whichever natd is in stable (You should remove the port) updated I think 2 or 3 days ago. I have a single ethernet card to a 192.168.1.x net and firewall type="open" with rule added in rc.local I have a ppp connection running over a modem via pppd which has worked fine for quite some time for the local machine. in rc.local: natd -l -s -a mymachine.com ipfw add 1100 divert natd all from any to any via ppp0 Let me mention that this problem only appears in machines on the local net using netscape 4.x, 3.x, telnet, ping, traceroute, ftp etc. work fine. On Tue, 30 Sep 1997, Brian Somers wrote: > > > > I recently enabled natd to do translation for a lan of windows machines, I > > have noticed that netscape 3.1 works fine but communicator 4.0 half opens > > web pages and never finishes consistently, is there an explanation for > > this? I tested this on many different machines on the network. > > I take it we're talking natd 1.10 (from after Sep 7 in -stable). > > You'll need to give details of your config. You could also try the > -v switch and see if anything obvious is happening. > > -- > Brian , , > > Don't _EVER_ lose your sense of humour.... > > > From owner-freebsd-stable Tue Sep 30 19:32:53 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id TAA10189 for stable-outgoing; Tue, 30 Sep 1997 19:32:53 -0700 (PDT) Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id TAA10183 for ; Tue, 30 Sep 1997 19:32:51 -0700 (PDT) Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.7/8.6.9) with ESMTP id TAA11449; Tue, 30 Sep 1997 19:32:42 -0700 (PDT) To: Joseph Stein cc: freebsd-stable@FreeBSD.ORG Subject: Re: Final notice: 2.2 branch code freeze is coming up. In-reply-to: Your message of "Tue, 30 Sep 1997 18:43:22 PDT." <199710010143.SAA02110@shasta.wstein.com> Date: Tue, 30 Sep 1997 19:32:42 -0700 Message-ID: <11445.875673162@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-stable@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk That's actually a pretty good idea - I'll do that during the BETA period no matter what we decide. ;) Jordan > > So, this all sort of raises the very obvious question and that is > > "Just what the heck is an official 2.2.5-BETA release good for if it's > > only going to be rendered essentially obsolete 24 hours later when the > > 2.2 SNAP server cranks out another full release? Why not just point > > at the 2.2.5-971001-RELENG snapshot and say "There, that's the BETA. > > Testers, please start your engines!" > > So, you call the releases at releng22.freebsd.org > > 2.2.5-971001-BETA > > ?? > > My $.02 > > joe From owner-freebsd-stable Tue Sep 30 23:27:44 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id XAA21259 for stable-outgoing; Tue, 30 Sep 1997 23:27:44 -0700 (PDT) Received: from silvia.HIP.Berkeley.EDU (wck-ca5-08.ix.netcom.com [199.35.213.168]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id XAA21253; Tue, 30 Sep 1997 23:27:41 -0700 (PDT) Received: (from asami@localhost) by silvia.HIP.Berkeley.EDU (8.8.7/8.6.9) id XAA03370; Tue, 30 Sep 1997 23:27:29 -0700 (PDT) Date: Tue, 30 Sep 1997 23:27:29 -0700 (PDT) Message-Id: <199710010627.XAA03370@silvia.HIP.Berkeley.EDU> To: jkh@time.cdrom.com CC: freebsd-stable@freebsd.org, ports@freebsd.org Reply-to: ports@freebsd.org In-reply-to: <10635.875667912@time.cdrom.com> (jkh@time.cdrom.com) Subject: Re: Final notice: 2.2 branch code freeze is coming up. From: asami@cs.berkeley.edu (Satoshi Asami) Sender: owner-freebsd-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk * Code freeze for the RELENG_2_2 branch will be at 23:59 PST 9/30/97 * (how's *that* for pedantic! :), approximately 6 hours from now. I am now going to start a final "make world" on the package building machine and then start building the packages for 2.2.5R. They will appear in the directory "packages-2.2.5" on wcarchive, so test them early and often. The ports freeze date will be announced later. Satoshi From owner-freebsd-stable Wed Oct 1 00:05:38 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id AAA23840 for stable-outgoing; Wed, 1 Oct 1997 00:05:38 -0700 (PDT) Received: from mh1.cts.com (root@mh1.cts.com [205.163.24.66]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id AAA23832 for ; Wed, 1 Oct 1997 00:05:34 -0700 (PDT) Received: from io.cts.com (io.cts.com [198.68.174.34]) by mh1.cts.com (8.8.5/8.8.5) with ESMTP id AAA01079 for ; Wed, 1 Oct 1997 00:05:33 -0700 (PDT) Apparently-To: Received: (from mdavis@localhost) by io.cts.com (8.8.5/8.8.5) id AAA14481 for freebsd-stable@freebsd.org; Wed, 1 Oct 1997 00:05:36 -0700 (PDT) From: Morgan Davis Message-Id: <199710010705.AAA14481@io.cts.com> Subject: de driver and 2.2.5 beta q's To: freebsd-stable@freebsd.org Date: Wed, 1 Oct 1997 00:05:35 -0700 (PDT) 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 Please note this dmesg snippet: FreeBSD 2.2.2-RELEASE #0: Tue Jun 10 11:54:28 PDT 1997 ... CPU: Pentium (120.00-MHz 586-class CPU) Origin = "GenuineIntel" Id = 0x525 Stepping=5 Features=0x1bf real memory = 67108864 (65536K bytes) avail memory = 62558208 (61092K bytes) Probing for devices on PCI bus 0: chip0 rev 1 on pci0:0 chip1 rev 2 on pci0:7:0 chip2 rev 2 on pci0:7:1 de0 rev 18 int a irq 12 on pci0:9 de0: SMC 9332 21140 [10-100Mb/s] pass 1.2 de0: address 00:00:c0:ad:51:dc de0: enabling 10baseT port de1 rev 32 int a irq 10 on pci0:10 de1: 21140A [10-100Mb/s] pass 2.0 de1: address 00:e0:29:05:d8:a5 de1: enabling 100baseTX port de0 works great. de1 doesn't. They're both SMC cards, but the de1 card is the newer rev (which you can find everywhere). The de0 card is no longer being produced. Upon power-up, both cards' link status and activity lights are on. As soon as the de1 card is initialized by FreeBSD, all its lights go off and it becomes useless. Putting two of the 21140-based cards (the older ones) in the machine works great, yielding > 1MB/s throughput. Putting two of the 21140A cards in the machine gives you two dead cards at init time. So it's not the combo of old and new that's a problem. It's the presence of 21140A, period. Next, I tried some Cogent cards (which also use the de driver). These had problems, too, but communicated somewhat. Unfortunately, they were only good for about 100K/s throughput, and netstat showed lots of Ierrs. This is reproducable in several machines (which I've swapped through several motherboards and other peripheral cards to see if there is some kind of conflict). All the machines being tested are running 2.2.2-RELEASE. All these cards work fine in other non-FreeBSD systems. Verdict? The 2.2.2-RELEASE de driver is Trouble except with anything other the older SMC cards. Since 2.2.5 is 20-some days off, are there any interim patches to the de driver code that fixes this problem? If so, I would appreciate pointers for downloading, compiling and installing them. This message also serves notice if this problem has not already been addressed for the 2.2.5 release. I'd be happy to cvsup a 2.2.5 beta. Just tell me which tag to use and I'll try it. On that note, will a 2.2.2 system cvsup to 2.2.5 with little changes to /etc, or are there lots of changes to be aware of when contemplating a beta overlay? --Morgan From owner-freebsd-stable Wed Oct 1 01:18:06 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id BAA27841 for stable-outgoing; Wed, 1 Oct 1997 01:18:06 -0700 (PDT) Received: from mail.san.rr.com (san.rr.com [204.210.0.1]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id BAA27834 for ; Wed, 1 Oct 1997 01:18:03 -0700 (PDT) Received: from dt5h1n61.san.rr.com (dt5h1n61.san.rr.com [204.210.31.97]) by mail.san.rr.com (8.8.7/8.8.7) with SMTP id BAA14397; Wed, 1 Oct 1997 01:17:32 -0700 (PDT) Message-Id: <199710010817.BAA14397@mail.san.rr.com> From: "Studded" To: "freebsd-stable@FreeBSD.ORG" Cc: "Jordan K. Hubbard" Date: Wed, 01 Oct 97 01:17:29 -0700 Reply-To: "Studded" Priority: Normal X-Mailer: PMMail 1.92 For OS/2 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Subject: Re: Final notice: 2.2 branch code freeze is coming up. Sender: owner-freebsd-stable@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Tue, 30 Sep 1997 18:05:12 -0700, Jordan K. Hubbard wrote: >If people have connectivity >problems to releng22.freebsd.org up there in Canada, I could even >buffer up the last few day's worth of 2.2 SNAPs on ftp.freebsd.org. I like this idea, with the caveat that perhaps the one on ftp.freebsd.org would be one or two days old so that people d/l'ing them have a reasonable chance of avoiding *new* bugs as opposed to the very valid situation that Jordan mentioned of not stumbling over old ones that are already fixed. You should probably also have a pointer in a text file telling people how to get the very latest from the 22releng machine. And the 2.2.5-date-BETA idea that Joseph came up with is a very good one as well. :) And speaking of bugs.... I get the impression that the (now) 2.2.5-beta code is pretty stable at this point? I ask beause I've got a production machine (dedicated for ircd) coming back on line wednesday or thursday that I could put the beta code on as long as there aren't any last-minute oddities that have snuck in there. :) regards, Doug Do thou amend thy face, and I'll amend my life. -Shakespeare, "Henry V" From owner-freebsd-stable Wed Oct 1 01:38:16 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id BAA28803 for stable-outgoing; Wed, 1 Oct 1997 01:38:16 -0700 (PDT) Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id BAA28792 for ; Wed, 1 Oct 1997 01:38:13 -0700 (PDT) Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.7/8.6.9) with ESMTP id BAA24698; Wed, 1 Oct 1997 01:38:12 -0700 (PDT) To: "Studded" cc: "freebsd-stable@FreeBSD.ORG" Subject: Re: Final notice: 2.2 branch code freeze is coming up. In-reply-to: Your message of "Wed, 01 Oct 1997 01:17:29 PDT." <199710010817.BAA14397@mail.san.rr.com> Date: Wed, 01 Oct 1997 01:38:11 -0700 Message-ID: <24694.875695091@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-stable@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > I like this idea, with the caveat that perhaps the one on > ftp.freebsd.org would be one or two days old so that people d/l'ing > them have a reasonable chance of avoiding *new* bugs as opposed to the > very valid situation that Jordan mentioned of not stumbling over old > ones that are already fixed. You should probably also have a pointer I think I can manage about 4 complete releases there, so that should give people a more than reasonable range. Remember also that these are supposed to be coming from a *frozen* branch: If there are any new bugs added at any point during this test cycle, many people will be annoyed. :-) > in a text file telling people how to get the very latest from the > 22releng machine. And the 2.2.5-date-BETA idea that Joseph came up > with is a very good one as well. :) Done. > And speaking of bugs.... I get the impression that the (now) > 2.2.5-beta code is pretty stable at this point? I ask beause I've got I sure hope so! ;-) Jordan From owner-freebsd-stable Wed Oct 1 05:35:47 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id FAA10575 for stable-outgoing; Wed, 1 Oct 1997 05:35:47 -0700 (PDT) Received: from limes.NIC.DTAG.DE (limes.NIC.DTAG.DE [194.25.1.113]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id FAA10552 for ; Wed, 1 Oct 1997 05:35:33 -0700 (PDT) Received: from kronos.NIC.DTAG.DE (kronos.NIC.DTAG.DE [194.25.1.92]) by limes.NIC.DTAG.DE (8.8.5/8.8.3) with ESMTP id OAA29131 for ; Wed, 1 Oct 1997 14:32:10 +0200 (MET DST) Received: from Reineke.Malepartus.de (Reineke.Malepartus.de [194.25.4.66]) by kronos.NIC.DTAG.DE (8.8.5/8.7.1) with ESMTP id OAA24051 for ; Wed, 1 Oct 1997 14:34:56 +0200 (MET DST) Received: from Reineke.Malepartus.de (localhost.Malepartus.de [127.0.0.1]) by Reineke.Malepartus.de (8.8.7/8.8.5) with ESMTP id OAA13268 for ; Wed, 1 Oct 1997 14:34:50 +0200 (MEST) Message-Id: <199710011234.OAA13268@Reineke.Malepartus.de> From: Burkard Meyendriesch Subject: automated application of CTM deltas To: freebsd-stable@FreeBSD.ORG Reply-To: bum@malepartus.de X-Mailer: MH 6.8.3 X-organization: The home of Reineke Fuchs X-GPOS: 52.0844N 7.9081E X-phone: +49 5484 96097 X-pgp-fingerprint: DF 83 04 CD B5 D1 10 43 57 4C AD 9A B1 02 28 17 X-face: "[-;]oI+8gP9>*J%knDN8d%DuhvJS2Lj4L\bRb7gz(pcT?2Zh6_Vam_6csAum3$<&lhAFd^ jt|!&Ut1C~Vg*E/q}+#cbFg-GU]c.bB8Ad,L'W$'9{^0y'AzM4#hS[C[F-1'|O;Kg3Vrq5q6dsU*TmJ@}+QPM\ b[^9Rhd,UoMpRpd5k[X=h.Dom*kbT`cNQ MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <13265.875709289.1@Reineke.Malepartus.de> Date: Wed, 01 Oct 1997 14:34:50 +0200 Sender: owner-freebsd-stable@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Hi, on my FreeBSD 2.2.5 box I use slocal for the distribution of my incoming email. To process the incoming source tree deltas from owner-ctm-src-2_2 I use the following entry in .maildelivery: From owner-ctm-src-2_2 ^ ? "/usr/sbin/ctm_rmail -f -p /usr/ctm/pieces \ -l /usr/ctm/log -d /usr/ctm/deltas -b /usr/ctm/src-2_2" After every invocation of ctm_rmail the log file entries look like: 1997-10-01 01:14 src-2.2.0454.gz 1/1 stored 1997-10-01 01:14 src-2.2.0454.gz complete 1997-10-01 01:14 ctm: ctm: not found Is there anything wrong with the environment of slocal? What can I do to get ctm_rmail working completely? Any hints welcome Burkard From owner-freebsd-stable Wed Oct 1 13:48:54 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id NAA06887 for stable-outgoing; Wed, 1 Oct 1997 13:48:54 -0700 (PDT) Received: from GndRsh.aac.dev.com (GndRsh.aac.dev.com [198.145.92.241]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id NAA06879 for ; Wed, 1 Oct 1997 13:48:47 -0700 (PDT) Received: (from rgrimes@localhost) by GndRsh.aac.dev.com (8.8.5/8.7.3) id NAA24653; Wed, 1 Oct 1997 13:48:07 -0700 (PDT) From: "Rodney W. Grimes" Message-Id: <199710012048.NAA24653@GndRsh.aac.dev.com> Subject: Re: de driver and 2.2.5 beta q's In-Reply-To: <199710010705.AAA14481@io.cts.com> from Morgan Davis at "Oct 1, 97 00:05:35 am" To: mdavis@io.cts.com (Morgan Davis) Date: Wed, 1 Oct 1997 13:48:07 -0700 (PDT) Cc: 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 note this dmesg snippet: > > FreeBSD 2.2.2-RELEASE #0: Tue Jun 10 11:54:28 PDT 1997 ^^^^^^^^^^^^^^^^^ You are running a 2.2.2-RELEASE system, your mail subject said 2.2.5 beta, you would find that if you loaded 2.2.2-stable as over 60 days ago this problem was fixed: revision 1.54.2.6 date: 1997/08/02 17:44:50; author: rgrimes; state: Exp; lines: +6 -3 Add support for the newer SMC 9332BDT cards that have a different OUI (00:E0:29) to the older driver in 2.2, the new driver in 3.0 should already handle this with the new PHY code. Reviewed by: Several of my customers > ... ... > de0 rev 18 int a irq 12 on pci0:9 > de0: SMC 9332 21140 [10-100Mb/s] pass 1.2 ^^^^^^^^ > de0: address 00:00:c0:ad:51:dc ^^^^^^^^ > de0: enabling 10baseT port > de1 rev 32 int a irq 10 on pci0:10 > de1: 21140A [10-100Mb/s] pass 2.0 ^^^^^^^ > de1: address 00:e0:29:05:d8:a5 ^^^^^^^^ > de1: enabling 100baseTX port After the above commit your new card will be identified as an SMC9332BDT, which it is. Your older card is an SMC9332DST. -- Rod Grimes rgrimes@gndrsh.aac.dev.com Accurate Automation, Inc. Reliable computers for FreeBSD From owner-freebsd-stable Wed Oct 1 19:12:22 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id TAA24142 for stable-outgoing; Wed, 1 Oct 1997 19:12:22 -0700 (PDT) Received: from word.smith.net.au (ppp20.portal.net.au [202.12.71.120]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id TAA24112 for ; Wed, 1 Oct 1997 19:12:11 -0700 (PDT) Received: from word.smith.net.au (localhost.smith.net.au [127.0.0.1]) by word.smith.net.au (8.8.7/8.8.5) with ESMTP id LAA02253 for ; Thu, 2 Oct 1997 11:39:28 +0930 (CST) Message-Id: <199710020209.LAA02253@word.smith.net.au> X-Mailer: exmh version 2.0zeta 7/24/97 To: stable@freebsd.org Subject: Crossbuild problem with 2.2.5-BETA Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 02 Oct 1997 11:39:26 +0930 From: Mike Smith Sender: owner-freebsd-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Well, I thought I'd hop on the bandwagon and do some testing for the 2.2.5-BETA cycle, as I have a plethora of machines here to set up. In preparation for a 'make release' then I ran a buildworld on the -stable source tree, checked out in a suitable build arena on a -current box. It appears that there are still some problems with building a tree that's not in /usr/src however - is this something I shouldn't be trying to do, or should it work? The one that bit me was this line in : #include "/usr/src/lib/libc/i386/DEFS.h" /* XXX blech */ /* * In the !KERNEL case, this header is only (ab)used in lib/msun/i387. * Use it to generate code to select between the generic math functions * and the i387 ones. */ The -current DEFS.h goes on to include , which doesn't exist in -stable. Ideas? mike From owner-freebsd-stable Wed Oct 1 20:15:57 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id UAA27428 for stable-outgoing; Wed, 1 Oct 1997 20:15:57 -0700 (PDT) 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 UAA27410 for ; Wed, 1 Oct 1997 20:15:49 -0700 (PDT) Received: from localhost (localhost.stanford.edu [127.0.0.1]) by andrsn.stanford.edu (8.8.7/8.6.12) with SMTP id UAA02471 for ; Wed, 1 Oct 1997 20:11:19 -0700 (PDT) Date: Wed, 1 Oct 1997 20:11:19 -0700 (PDT) From: Annelise Anderson To: freebsd-stable@freebsd.org Subject: CVSUP vs. SNAPS 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've been updating 2.2-STABLE via cvsup with the following file: src-all release=cvs host=cvsup.FreeBSD.org hostbase=/home base=/usr prefix=/usr delete use-rel-suffix compress tag=RELENG_2_2 so I assume this is equivalent to installing a SNAP from releng22.freebsd.org? Thanks for clarifying this-- Annelise From owner-freebsd-stable Wed Oct 1 20:48:07 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id UAA28881 for stable-outgoing; Wed, 1 Oct 1997 20:48:07 -0700 (PDT) Received: from bunyip.cc.uq.edu.au (daemon@bunyip.cc.uq.edu.au [130.102.2.1]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id UAA28836 for ; Wed, 1 Oct 1997 20:47:54 -0700 (PDT) Received: (from daemon@localhost) by bunyip.cc.uq.edu.au (8.8.7/8.8.7) id NAA12580; Thu, 2 Oct 1997 13:44:57 +1000 Received: from localhost.dtir.qld.gov.au (localhost.dtir.qld.gov.au [127.0.0.1]) by ogre.dtir.qld.gov.au (8.8.7/8.8.7) with SMTP id NAA13343; Thu, 2 Oct 1997 13:22:16 +1000 (EST) Message-Id: <199710020322.NAA13343@ogre.dtir.qld.gov.au> X-Authentication-Warning: ogre.dtir.qld.gov.au: localhost.dtir.qld.gov.au [127.0.0.1] didn't use HELO protocol To: Burkard Meyendriesch cc: freebsd-stable@freebsd.org, syssgm@dtir.qld.gov.au Subject: Re: automated application of CTM deltas References: <199710011234.OAA13268@Reineke.Malepartus.de> In-Reply-To: <199710011234.OAA13268@Reineke.Malepartus.de> from Burkard Meyendriesch at "Wed, 01 Oct 1997 12:34:50 +0000" Date: Thu, 02 Oct 1997 13:22:16 +1000 From: Stephen McKay Sender: owner-freebsd-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Wednesday, 1st October 1997, Burkard Meyendriesch wrote: >on my FreeBSD 2.2.5 box I use slocal for the distribution of my incoming >email. To process the incoming source tree deltas from owner-ctm-src-2_2 >I use the following entry in .maildelivery: > > From owner-ctm-src-2_2 ^ ? "/usr/sbin/ctm_rmail -f -p /usr/ctm/pieces \ > -l /usr/ctm/log -d /usr/ctm/deltas -b /usr/ctm/src-2_2" > >After every invocation of ctm_rmail the log file entries look like: > > 1997-10-01 01:14 src-2.2.0454.gz 1/1 stored > 1997-10-01 01:14 src-2.2.0454.gz complete > 1997-10-01 01:14 ctm: ctm: not found > >Is there anything wrong with the environment of slocal? What can I do >to get ctm_rmail working completely? ctm (and gunzip) must be in your PATH. I am guessing that your path is defaulting to /bin:/usr/bin when running slocal. You should be able to add PATH=/bin:/sbin:/usr/bin:/usr/sbin to your .forward to set PATh before slocal runs, or into your .maildelivery file to set it for just ctm_rmail. Have a look at the ctm_rmail man page for how I do this using procmail. You should be able to do something very similar if you don't like my previous suggestion. Stephen. From owner-freebsd-stable Wed Oct 1 21:18:16 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id VAA00628 for stable-outgoing; Wed, 1 Oct 1997 21:18:16 -0700 (PDT) Received: from austin.polstra.com (austin.polstra.com [206.213.73.10]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id VAA00609 for ; Wed, 1 Oct 1997 21:18:11 -0700 (PDT) Received: from austin.polstra.com (jdp@localhost) by austin.polstra.com (8.8.7/8.8.5) with ESMTP id VAA23398; Wed, 1 Oct 1997 21:18:03 -0700 (PDT) Message-Id: <199710020418.VAA23398@austin.polstra.com> To: andrsn@andrsn.stanford.edu Subject: Re: CVSUP vs. SNAPS In-Reply-To: References: Organization: Polstra & Co., Seattle, WA Cc: stable@freebsd.org Date: Wed, 01 Oct 1997 21:18:02 -0700 From: John Polstra Sender: owner-freebsd-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk In article , Annelise Anderson wrote: > I've been updating 2.2-STABLE via cvsup with the following file: > > src-all release=cvs host=cvsup.FreeBSD.org hostbase=/home base=/usr > prefix=/usr delete use-rel-suffix compress tag=RELENG_2_2 > > so I assume this is equivalent to installing a SNAP from > releng22.freebsd.org? Well, it's the same provided you run CVSup exactly at the same time as the "cvs checkout" for the SNAP is run. :-) Otherwise, it can be slightly different. If you know when the files for the SNAPs are checked out each day, you can use the "date=" option in the supfile along with tag=RELENG_2_2 to get very close to the exact version of everything used in the SNAP. John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Self-knowledge is always bad news." -- John Barth From owner-freebsd-stable Wed Oct 1 22:44:20 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id WAA05041 for stable-outgoing; Wed, 1 Oct 1997 22:44:20 -0700 (PDT) Received: from time.cdrom.com (time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id WAA05034 for ; Wed, 1 Oct 1997 22:44:16 -0700 (PDT) Received: from time.cdrom.com (localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.7/8.6.9) with ESMTP id WAA04652; Wed, 1 Oct 1997 22:43:39 -0700 (PDT) To: Annelise Anderson cc: freebsd-stable@FreeBSD.ORG Subject: Re: CVSUP vs. SNAPS In-reply-to: Your message of "Wed, 01 Oct 1997 20:11:19 PDT." Date: Wed, 01 Oct 1997 22:43:39 -0700 Message-ID: <4649.875771019@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-stable@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > I've been updating 2.2-STABLE via cvsup with the following file: > > src-all release=cvs host=cvsup.FreeBSD.org hostbase=/home base=/usr > prefix=/usr delete use-rel-suffix compress tag=RELENG_2_2 Looks good. > so I assume this is equivalent to installing a SNAP from > releng22.freebsd.org? Assuming that we're talking about the same day in each case, yes. ;-) Jordan From owner-freebsd-stable Wed Oct 1 23:35:50 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id XAA07535 for stable-outgoing; Wed, 1 Oct 1997 23:35:50 -0700 (PDT) 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 XAA07528 for ; Wed, 1 Oct 1997 23:35:48 -0700 (PDT) Received: from localhost (localhost.stanford.edu [127.0.0.1]) by andrsn.stanford.edu (8.8.7/8.6.12) with SMTP id XAA02927 for ; Wed, 1 Oct 1997 23:28:13 -0700 (PDT) Date: Wed, 1 Oct 1997 23:28:12 -0700 (PDT) From: Annelise Anderson To: freebsd-stable@freebsd.org Subject: Re: CVSUP vs. SNAPS In-Reply-To: <4649.875771019@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 On Wed, 1 Oct 1997, Jordan K. Hubbard wrote: > > I've been updating 2.2-STABLE via cvsup with the following file: > > > > src-all release=cvs host=cvsup.FreeBSD.org hostbase=/home base=/usr > > prefix=/usr delete use-rel-suffix compress tag=RELENG_2_2 > > Looks good. > > > so I assume this is equivalent to installing a SNAP from > > releng22.freebsd.org? > > Assuming that we're talking about the same day in each case, > yes. ;-) > > Jordan Thanks--also thanks to John Polstra. I got the sources after the "freeze" time and did a make world and built a new kernel, but it still says 2.2-STABLE, so I wasn't sure. Annelise From owner-freebsd-stable Thu Oct 2 00:58:26 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id AAA11163 for stable-outgoing; Thu, 2 Oct 1997 00:58:26 -0700 (PDT) Received: from time.cdrom.com (time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id AAA11156 for ; Thu, 2 Oct 1997 00:58:24 -0700 (PDT) Received: from time.cdrom.com (localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.7/8.6.9) with ESMTP id AAA03513; Thu, 2 Oct 1997 00:57:47 -0700 (PDT) To: Annelise Anderson cc: freebsd-stable@FreeBSD.ORG Subject: Re: CVSUP vs. SNAPS In-reply-to: Your message of "Wed, 01 Oct 1997 23:28:12 PDT." Date: Thu, 02 Oct 1997 00:57:47 -0700 Message-ID: <3503.875779067@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-stable@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > Thanks--also thanks to John Polstra. I got the sources after the > "freeze" time and did a make world and built a new kernel, but it > still says 2.2-STABLE, so I wasn't sure. It will say 2.2-STABLE at all times unless there's a specific release in progress, then it will be set to that release name for all of a day or so before going back to 2.2-STABLE. Jordan From owner-freebsd-stable Thu Oct 2 06:58:47 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id GAA26852 for stable-outgoing; Thu, 2 Oct 1997 06:58:47 -0700 (PDT) Received: from GndRsh.aac.dev.com (GndRsh.aac.dev.com [198.145.92.241]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id GAA26846 for ; Thu, 2 Oct 1997 06:58:44 -0700 (PDT) Received: (from rgrimes@localhost) by GndRsh.aac.dev.com (8.8.5/8.7.3) id GAA28556; Thu, 2 Oct 1997 06:58:03 -0700 (PDT) From: "Rodney W. Grimes" Message-Id: <199710021358.GAA28556@GndRsh.aac.dev.com> Subject: Re: CVSUP vs. SNAPS In-Reply-To: <3503.875779067@time.cdrom.com> from "Jordan K. Hubbard" at "Oct 2, 97 00:57:47 am" To: jkh@time.cdrom.com (Jordan K. Hubbard) Date: Thu, 2 Oct 1997 06:58:03 -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 > > Thanks--also thanks to John Polstra. I got the sources after the > > "freeze" time and did a make world and built a new kernel, but it > > still says 2.2-STABLE, so I wasn't sure. > > It will say 2.2-STABLE at all times unless there's a specific release > in progress, then it will be set to that release name for all of a day > or so before going back to 2.2-STABLE. 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). Going DOWN in version numbers is not something I would call good release engineering/customer relations work. If you go back to 2.2-STABLE I have know way to know that the person has something before the 2.2.5 RELEASE point. 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! -- Rod Grimes rgrimes@gndrsh.aac.dev.com Accurate Automation, Inc. Reliable computers for FreeBSD From owner-freebsd-stable Thu Oct 2 07:58:04 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id HAA00243 for stable-outgoing; Thu, 2 Oct 1997 07:58:04 -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 HAA00237 for ; Thu, 2 Oct 1997 07:57:59 -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 IAA20880; Thu, 2 Oct 1997 08:00:17 -0700 (PDT) Message-Id: <199710021500.IAA20880@implode.root.com> To: "Rodney W. Grimes" cc: jkh@time.cdrom.com (Jordan K. Hubbard), andrsn@andrsn.stanford.edu, freebsd-stable@FreeBSD.ORG Subject: Re: CVSUP vs. SNAPS In-reply-to: Your message of "Thu, 02 Oct 1997 06:58:03 PDT." <199710021358.GAA28556@GndRsh.aac.dev.com> From: David Greenman Reply-To: dg@root.com Date: Thu, 02 Oct 1997 08:00:17 -0700 Sender: owner-freebsd-stable@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >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). > >Going DOWN in version numbers is not something I would call good >release engineering/customer relations work. If you go back to >2.2-STABLE I have know way to know that the person has something >before the 2.2.5 RELEASE point. > >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! The problem you're having is that the "2.2" release is actually called 2.2.0 (that's what the tag is in the repository), so 2.2.5 is not going down. We should perhaps make this more clear in the product literature, but I really don't think that most people are confused over this issue. -DG David Greenman Core-team/Principal Architect, The FreeBSD Project From owner-freebsd-stable Thu Oct 2 08:08:16 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id IAA00867 for stable-outgoing; Thu, 2 Oct 1997 08:08:16 -0700 (PDT) Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id IAA00862 for ; Thu, 2 Oct 1997 08:08:13 -0700 (PDT) Received: from harmony [10.0.0.6] by rover.village.org with esmtp (Exim 1.71 #1) id 0xGmrK-00005U-00; Thu, 2 Oct 1997 09:08:10 -0600 Received: from harmony.village.org (localhost [127.0.0.1]) by harmony.village.org (8.8.7/8.8.3) with ESMTP id JAA00956; Thu, 2 Oct 1997 09:09:01 -0600 (MDT) Message-Id: <199710021509.JAA00956@harmony.village.org> To: "Rodney W. Grimes" Subject: Re: CVSUP vs. SNAPS Cc: jkh@time.cdrom.com (Jordan K. Hubbard), andrsn@andrsn.stanford.edu, freebsd-stable@freebsd.org In-reply-to: Your message of "Thu, 02 Oct 1997 06:58:03 PDT." <199710021358.GAA28556@GndRsh.aac.dev.com> References: <199710021358.GAA28556@GndRsh.aac.dev.com> Date: Thu, 02 Oct 1997 09:09:01 -0600 From: Warner Losh Sender: owner-freebsd-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk In message <199710021358.GAA28556@GndRsh.aac.dev.com> "Rodney W. Grimes" writes: : 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 From owner-freebsd-stable Thu Oct 2 08:10:26 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id IAA01094 for stable-outgoing; Thu, 2 Oct 1997 08:10:26 -0700 (PDT) Received: from GndRsh.aac.dev.com (GndRsh.aac.dev.com [198.145.92.241]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id IAA01089 for ; Thu, 2 Oct 1997 08:10:23 -0700 (PDT) Received: (from rgrimes@localhost) by GndRsh.aac.dev.com (8.8.5/8.7.3) id IAA28884; Thu, 2 Oct 1997 08:09:41 -0700 (PDT) From: "Rodney W. Grimes" Message-Id: <199710021509.IAA28884@GndRsh.aac.dev.com> Subject: Re: CVSUP vs. SNAPS In-Reply-To: <199710021500.IAA20880@implode.root.com> from David Greenman at "Oct 2, 97 08:00:17 am" To: dg@root.com Date: Thu, 2 Oct 1997 08:09:41 -0700 (PDT) Cc: 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 > >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). > > > >Going DOWN in version numbers is not something I would call good > >release engineering/customer relations work. If you go back to > >2.2-STABLE I have know way to know that the person has something > >before the 2.2.5 RELEASE point. > > > >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! > > The problem you're having is that the "2.2" release is actually called > 2.2.0 (that's what the tag is in the repository), so 2.2.5 is not going down. I didn't say 2.2.5 was going down, I said going from 2.2.5 BACK to 2.2 after release was going down. > We should perhaps make this more clear in the product literature, but I > really don't think that most people are confused over this issue. 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! -- Rod Grimes rgrimes@gndrsh.aac.dev.com Accurate Automation, Inc. Reliable computers for FreeBSD From owner-freebsd-stable Thu Oct 2 08:26:27 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id IAA02117 for stable-outgoing; Thu, 2 Oct 1997 08:26:27 -0700 (PDT) Received: from ns.ase.dowjones.com (ns.ase.dowjones.com [206.112.106.2]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id IAA02109 for ; Thu, 2 Oct 1997 08:26:24 -0700 (PDT) Received: from umber (umber.ase.dowjones.com [206.112.106.116]) by ns.ase.dowjones.com (8.8.7/8.8.5) with SMTP id KAA02529 for ; Thu, 2 Oct 1997 10:26:21 -0500 (CDT) Message-Id: <3.0.1.32.19971002102621.009a3790@mail.sstar.com> X-Sender: jim.king@mail.sstar.com X-Mailer: Windows Eudora Light Version 3.0.1 (32) Date: Thu, 02 Oct 1997 10:26:21 -0500 To: freebsd-stable@freebsd.org From: Jim King Subject: DE21140-AE in 2.2.5 Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk 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? From owner-freebsd-stable Thu Oct 2 08:42:02 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id IAA03117 for stable-outgoing; Thu, 2 Oct 1997 08:42:02 -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 IAA03100 for ; Thu, 2 Oct 1997 08:41:58 -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 IAA21048; Thu, 2 Oct 1997 08:44:23 -0700 (PDT) Message-Id: <199710021544.IAA21048@implode.root.com> To: "Rodney W. Grimes" cc: jkh@time.cdrom.com, andrsn@andrsn.stanford.edu, freebsd-stable@FreeBSD.ORG Subject: Re: CVSUP vs. SNAPS In-reply-to: Your message of "Thu, 02 Oct 1997 08:09:41 PDT." <199710021509.IAA28884@GndRsh.aac.dev.com> From: David Greenman Reply-To: dg@root.com Date: Thu, 02 Oct 1997 08:44:23 -0700 Sender: owner-freebsd-stable@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >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. -DG David Greenman Core-team/Principal Architect, The FreeBSD Project From owner-freebsd-stable Thu Oct 2 09:43:23 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id JAA07297 for stable-outgoing; Thu, 2 Oct 1997 09:43:23 -0700 (PDT) Received: from david-relay.siemens.de (david-relay.siemens.de [139.23.36.13]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id JAA07282 for ; Thu, 2 Oct 1997 09:43:17 -0700 (PDT) Received: from salomon.mchp.siemens.de (salomon.siemens.de [139.23.33.13]) by david-relay.siemens.de (8.8.7/8.8.7) with ESMTP id SAA02599 for ; Thu, 2 Oct 1997 18:40:04 +0200 (MET DST) 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 SAA02096 for ; Thu, 2 Oct 1997 18:43:11 +0200 (MDT) Received: (from daemon@localhost) by curry.mchp.siemens.de (8.8.7/8.8.7) id SAA10795 for ; Thu, 2 Oct 1997 18:43:11 +0200 (MET DST) From: Andre Albsmeier Message-Id: <199710021642.SAA25772@curry.mchp.siemens.de> Subject: Apache works but dies with signal 11, why? To: freebsd-ports@freebsd.org, freebsd-stable@freebsd.org Date: Thu, 2 Oct 1997 18:42:57 +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, I'm posting this to -STABLE and -PORTS since I don't know where the problem lies actually. I have a funny problem with apache on 2.2-STABLE (most up to date version): Everything works, but when apache exits (it is run from inetd), it always dies with signal 11 when work is done. This happens on all three 2.2-STABLE machines which are webservers and run great otherwise. This is now going on for 8 weeks when I installed it for the first time... Until now, I couldn't figure out what it is... I have tried the port and the compiled package, always the same. My inetd.conf line is: http stream tcp nowait nobody /usr/local/sbin/httpd httpd Any clues? Thanks, -Andre From owner-freebsd-stable Thu Oct 2 09:44:15 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id JAA07418 for stable-outgoing; Thu, 2 Oct 1997 09:44:15 -0700 (PDT) Received: from adelphi.physics.adelaide.edu.au (adelphi.physics.adelaide.edu.au [129.127.36.247]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id JAA07401 for ; Thu, 2 Oct 1997 09:44:05 -0700 (PDT) Received: from bragg by adelphi.physics.adelaide.edu.au (5.65/AndrewR-930902) id AA27722; Fri, 3 Oct 1997 02:13:24 +0930 From: Kristian Kennaway Received: by bragg; (5.65/1.1.8.2/05Aug95-0227PM) id AA24574; Fri, 3 Oct 1997 02:13:23 +0930 Message-Id: <9710021643.AA24574@bragg> Subject: Re: CVSUP vs. SNAPS To: dg@root.com Date: Fri, 3 Oct 1997 02:13:23 +0930 (CST) Cc: rgrimes@GndRsh.aac.dev.com, jkh@time.cdrom.com, andrsn@andrsn.stanford.edu, freebsd-stable@FreeBSD.ORG In-Reply-To: <199710021500.IAA20880@implode.root.com> from "David Greenman" at Oct 2, 97 08:00:17 am X-Mailer: ELM [version 2.4 PL23] 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 > The problem you're having is that the "2.2" release is actually called > 2.2.0 (that's what the tag is in the repository), so 2.2.5 is not going down. > We should perhaps make this more clear in the product literature, but I > really don't think that most people are confused over this issue. Actually, I found this very far from clear; at about the time 2.2.2 was released, I gained the ability to track the source tree via cvsup. I looked long and hard at the documentation on my system and the webpages, even searched the mail archives, but I could not find an obvious answer as to which branch to track to remain stable. It seemed to me, as others have noted, that 2.2.2 is "greater" than 2.2 from a numerical standpoint, and that hence it should be the release to track to remain stable with the source tree. I should also note that at that time the web documentation still referred to 2.1 as the stable branch, and 2.2 as current, which did not help to ease my confusion. I should HOPE this has changed by now :) It took a question or two to the mailing list to straighten me out and point me to 2.2-stable as the release to track. (I think I may have been trying to track 2.2.2-stable or something). So if my opinion counts for anything in this debate, it goes for the 2.2.5-stable branch name. :) Kris From owner-freebsd-stable Thu Oct 2 10:01:59 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id KAA08741 for stable-outgoing; Thu, 2 Oct 1997 10:01:59 -0700 (PDT) Received: from time.cdrom.com (time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id KAA08724 for ; Thu, 2 Oct 1997 10:01:53 -0700 (PDT) Received: from time.cdrom.com (localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.7/8.6.9) with ESMTP id KAA11921; Thu, 2 Oct 1997 10:01:00 -0700 (PDT) To: "Rodney W. Grimes" cc: andrsn@andrsn.stanford.edu, freebsd-stable@FreeBSD.ORG Subject: Re: CVSUP vs. SNAPS In-reply-to: Your message of "Thu, 02 Oct 1997 06:58:03 PDT." <199710021358.GAA28556@GndRsh.aac.dev.com> Date: Thu, 02 Oct 1997 10:01:00 -0700 Message-ID: <11918.875811660@time.cdrom.com> From: "Jordan K. Hubbard" 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. Jordan From owner-freebsd-stable Thu Oct 2 10:05:14 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id KAA08999 for stable-outgoing; Thu, 2 Oct 1997 10:05:14 -0700 (PDT) Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id KAA08959 for ; Thu, 2 Oct 1997 10:04:57 -0700 (PDT) Received: from harmony [10.0.0.6] by rover.village.org with esmtp (Exim 1.71 #1) id 0xGofm-0000A3-00; Thu, 2 Oct 1997 11:04:22 -0600 Received: from harmony.village.org (localhost [127.0.0.1]) by harmony.village.org (8.8.7/8.8.3) with ESMTP id LAA02207; Thu, 2 Oct 1997 11:05:20 -0600 (MDT) Message-Id: <199710021705.LAA02207@harmony.village.org> To: dg@root.com Subject: Re: CVSUP vs. SNAPS Cc: "Rodney W. Grimes" , jkh@time.cdrom.com, andrsn@andrsn.stanford.edu, freebsd-stable@freebsd.org In-reply-to: Your message of "Thu, 02 Oct 1997 08:44:23 PDT." <199710021544.IAA21048@implode.root.com> References: <199710021544.IAA21048@implode.root.com> Date: Thu, 02 Oct 1997 11:05:19 -0600 From: Warner Losh Sender: owner-freebsd-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk In message <199710021544.IAA21048@implode.root.com> David Greenman 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. This reminds me of the joke about a helicopter pilot, fog and Microsoft support. While it is true that 2.2 does refer to the branch name, it is *NOT* specific enough. The release name for the 2.2 stable branch should be the last release on that branch followed by -STABLE. I've got several systems around here that are nearly impossible to determine what rev is on them because they all say 2.2-STABLE, even though some of them are from the 2.2.0 time frame, and others are 2 hours old. If I can't tell the difference, then autoconfig scripts that use uname can't either. *PLEASE*PLEASE*PLEASE* listen to Rod. The kernels after 2.2.5-RELEASE should be called 2.2.5-STABLE. Warner From owner-freebsd-stable Thu Oct 2 10:13:24 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id KAA09491 for stable-outgoing; Thu, 2 Oct 1997 10:13:24 -0700 (PDT) Received: from time.cdrom.com (time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id KAA09486 for ; Thu, 2 Oct 1997 10:13:19 -0700 (PDT) Received: from time.cdrom.com (localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.7/8.6.9) with ESMTP id KAA12052; Thu, 2 Oct 1997 10:12:09 -0700 (PDT) To: Warner Losh cc: "Rodney W. Grimes" , andrsn@andrsn.stanford.edu, freebsd-stable@FreeBSD.ORG Subject: Re: CVSUP vs. SNAPS In-reply-to: Your message of "Thu, 02 Oct 1997 09:09:01 MDT." <199710021509.JAA00956@harmony.village.org> Date: Thu, 02 Oct 1997 10:12:09 -0700 Message-ID: <12048.875812329@time.cdrom.com> From: "Jordan K. Hubbard" 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 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. 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 From owner-freebsd-stable Thu Oct 2 10:26:14 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id KAA10101 for stable-outgoing; Thu, 2 Oct 1997 10:26:14 -0700 (PDT) Received: from time.cdrom.com (time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id KAA10094 for ; Thu, 2 Oct 1997 10:26:07 -0700 (PDT) Received: from time.cdrom.com (localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.7/8.6.9) with ESMTP id KAA12164; Thu, 2 Oct 1997 10:24:56 -0700 (PDT) To: Kristian Kennaway cc: dg@root.com, rgrimes@GndRsh.aac.dev.com, andrsn@andrsn.stanford.edu, freebsd-stable@FreeBSD.ORG Subject: Re: CVSUP vs. SNAPS In-reply-to: Your message of "Fri, 03 Oct 1997 02:13:23 +0930." <9710021643.AA24574@bragg> Date: Thu, 02 Oct 1997 10:24:56 -0700 Message-ID: <12160.875813096@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-stable@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > I should also note that at that time the web documentation still referred > to 2.1 as the stable branch, and 2.2 as current, which did not help to > ease my confusion. I should HOPE this has changed by now :) It should be, though if you find any instances where it's still not, please point them out to www@freebsd.org! :) > So if my opinion counts for anything in this debate, it goes for the > 2.2.5-stable branch name. :) But the branch is called RELENG_2_2 - that is physically the name of the tag. There is no RELENG_2_2_5 branch tag, which is what your suggestion would imply and cause even more confusion. 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 intend on doing absolutely nothing different than "usual" at this late stage in the game. Jordan From owner-freebsd-stable Thu Oct 2 10:59:27 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id KAA12078 for stable-outgoing; Thu, 2 Oct 1997 10:59:27 -0700 (PDT) Received: from david-relay.siemens.de (david-relay.siemens.de [139.23.36.13]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id KAA12073 for ; Thu, 2 Oct 1997 10:59:23 -0700 (PDT) Received: from salomon.mchp.siemens.de (salomon.siemens.de [139.23.33.13]) by david-relay.siemens.de (8.8.7/8.8.7) with ESMTP id TAA03511 for ; Thu, 2 Oct 1997 19:56:14 +0200 (MET DST) 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 TAA10098 for ; Thu, 2 Oct 1997 19:59:20 +0200 (MDT) Received: (from daemon@localhost) by curry.mchp.siemens.de (8.8.7/8.8.7) id TAA11196 for ; Thu, 2 Oct 1997 19:59:18 +0200 (MET DST) From: Andre Albsmeier Message-Id: <199710021759.TAA26440@curry.mchp.siemens.de> Subject: Re: Apache works but dies with signal 11, why? In-Reply-To: from Tom at "Oct 2, 97 10:50:23 am" To: tom@sdf.com (Tom) Date: Thu, 2 Oct 1997 19:59:06 +0200 (CEST) Cc: freebsd-ports@FreeBSD.ORG, 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 > > On Thu, 2 Oct 1997, Andre Albsmeier wrote: > > > Hi, > > > > I'm posting this to -STABLE and -PORTS since I don't know > > where the problem lies actually. > > > > I have a funny problem with apache on 2.2-STABLE (most up to > > date version): > > > > Everything works, but when apache exits (it is run from inetd), > > it always dies with signal 11 when work is done. This happens > > Does Apache even work from inetd anymore? As I recall, you used to have > to add stuff in the config files to do this. But I thought that inetd > support was going to be dropped. > Yes, I have to change the config file (ServerType inetd). I also have it running on a Sun (4.1.3_U1) from inetd without any problems. > I would run it daemon mode. It is considerable faster, and places less > load on your system. Yes, but the servers are used rather seldom and only in our local network. So I didn't want to have a daemon running when it is only used 20-30 times a day... I think, I am doing something wrong because nobody else complains about that (Or are there no other users running it from inetd ?). It's the same configuration as on the Sun (apart from some directory configuration). Thanks, -Andre From owner-freebsd-stable Thu Oct 2 11:37:49 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id LAA14192 for stable-outgoing; Thu, 2 Oct 1997 11:37:49 -0700 (PDT) Received: from scanner.worldgate.com (scanner.worldgate.com [198.161.84.3]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id LAA14185; Thu, 2 Oct 1997 11:37:35 -0700 (PDT) Received: from znep.com (uucp@localhost) by scanner.worldgate.com (8.8.7/8.8.7) with UUCP id MAA15339; Thu, 2 Oct 1997 12:32:18 -0600 (MDT) Received: from localhost (marcs@localhost) by alive.znep.com (8.7.5/8.7.3) with SMTP id MAA21294; Thu, 2 Oct 1997 12:35:31 -0600 (MDT) Date: Thu, 2 Oct 1997 12:35:30 -0600 (MDT) From: Marc Slemko To: Andre Albsmeier cc: freebsd-ports@FreeBSD.ORG, freebsd-stable@FreeBSD.ORG Subject: Re: Apache works but dies with signal 11, why? In-Reply-To: <199710021642.SAA25772@curry.mchp.siemens.de> 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, 2 Oct 1997, Andre Albsmeier wrote: > Hi, > > I'm posting this to -STABLE and -PORTS since I don't know > where the problem lies actually. > > I have a funny problem with apache on 2.2-STABLE (most up to > date version): > > Everything works, but when apache exits (it is run from inetd), > it always dies with signal 11 when work is done. This happens > on all three 2.2-STABLE machines which are webservers and run > great otherwise. This is now going on for 8 weeks when I > installed it for the first time... > Until now, I couldn't figure out what it is... > > I have tried the port and the compiled package, always the same. > > My inetd.conf line is: > > http stream tcp nowait nobody /usr/local/sbin/httpd httpd Don't run Apache from inetd mode. It really occupise few resources running standalone and various features make it more and more difficult to have it work properly from inetd mode. See http://bugs.apache.org/index/full/592 for a patch that fixes this particular problem. -- Marc Slemko | Apache team member marcs@znep.com | marc@apache.org From owner-freebsd-stable Thu Oct 2 11:45:42 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id LAA14696 for stable-outgoing; Thu, 2 Oct 1997 11:45:42 -0700 (PDT) Received: from david-relay.siemens.de (david-relay.siemens.de [139.23.36.13]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id LAA14688 for ; Thu, 2 Oct 1997 11:45:35 -0700 (PDT) Received: from salomon.mchp.siemens.de (salomon.siemens.de [139.23.33.13]) by david-relay.siemens.de (8.8.7/8.8.7) with ESMTP id UAA03860 for ; Thu, 2 Oct 1997 20:42:17 +0200 (MET DST) 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 UAA14510 for ; Thu, 2 Oct 1997 20:45:24 +0200 (MDT) Received: (from daemon@localhost) by curry.mchp.siemens.de (8.8.7/8.8.7) id UAA11492 for ; Thu, 2 Oct 1997 20:45:23 +0200 (MET DST) From: Andre Albsmeier Message-Id: <199710021845.UAA26794@curry.mchp.siemens.de> Subject: Re: Apache works but dies with signal 11, why? In-Reply-To: from Marc Slemko at "Oct 2, 97 12:35:30 pm" To: marcs@znep.com (Marc Slemko) Date: Thu, 2 Oct 1997 20:45:09 +0200 (CEST) Cc: freebsd-ports@FreeBSD.ORG, 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 > > My inetd.conf line is: > > > > http stream tcp nowait nobody /usr/local/sbin/httpd httpd > > Don't run Apache from inetd mode. It really occupise few resources > running standalone and various features make it more and more difficult to > have it work properly from inetd mode. > > See http://bugs.apache.org/index/full/592 for a patch that fixes this > particular problem. Wow, that seems to be it. Will try it and as well will consider running standalone as many people have told me know... Thanks to all who responded so quickly (10-15 min, this is the record) -Andre From owner-freebsd-stable Thu Oct 2 11:59:47 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id LAA15427 for stable-outgoing; Thu, 2 Oct 1997 11:59:47 -0700 (PDT) Received: from super-g.inch.com (super-g.com [207.240.140.161]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id LAA15417 for ; Thu, 2 Oct 1997 11:59:31 -0700 (PDT) Received: from localhost (spork@localhost) by super-g.inch.com (8.8.7/8.8.5) with SMTP id PAA07664; Thu, 2 Oct 1997 15:24:45 -0400 (EDT) Date: Thu, 2 Oct 1997 15:24:45 -0400 (EDT) From: spork X-Sender: spork@super-g.inch.com To: "Rodney W. Grimes" cc: Morgan Davis , freebsd-stable@FreeBSD.ORG Subject: Re: de driver and 2.2.5 beta q's In-Reply-To: <199710012048.NAA24653@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 Is there any chance of the problem with the genuine de cards locking up when the link drops being fixed in 2.2.5? I cvsup-ed two days ago, and I still see the problem. To recap, if you have a Digital card, de0 rev 32 int a irq 12 on pci0:10 de0: DEC DE500-AA 21140A [10-100Mb/s] pass 2.0 de0: address 00:00:f8:03:66:e9 running 10M and you down the link by unplugging it, moving it to another hub port, rebooting the hub, etc. it will not come back on it's own. As a workaround I've been using the 3am driver. Is there a reason this hasn't been integrated? I've not seen any negative feedback about the other driver, and it handles the above situation properly. Thanks, Charles On Wed, 1 Oct 1997, Rodney W. Grimes wrote: > > Please note this dmesg snippet: > > > > FreeBSD 2.2.2-RELEASE #0: Tue Jun 10 11:54:28 PDT 1997 > ^^^^^^^^^^^^^^^^^ > > You are running a 2.2.2-RELEASE system, your mail subject said > 2.2.5 beta, you would find that if you loaded 2.2.2-stable as > over 60 days ago this problem was fixed: > > revision 1.54.2.6 > date: 1997/08/02 17:44:50; author: rgrimes; state: Exp; lines: +6 -3 > Add support for the newer SMC 9332BDT cards that have a different > OUI (00:E0:29) to the older driver in 2.2, the new driver in 3.0 > should already handle this with the new PHY code. > Reviewed by: Several of my customers > > > ... > ... > > de0 rev 18 int a irq 12 on pci0:9 > > de0: SMC 9332 21140 [10-100Mb/s] pass 1.2 > ^^^^^^^^ > > de0: address 00:00:c0:ad:51:dc > ^^^^^^^^ > > de0: enabling 10baseT port > > de1 rev 32 int a irq 10 on pci0:10 > > de1: 21140A [10-100Mb/s] pass 2.0 > ^^^^^^^ > > de1: address 00:e0:29:05:d8:a5 > ^^^^^^^^ > > de1: enabling 100baseTX port > > After the above commit your new card will be identified as > an SMC9332BDT, which it is. Your older card is an SMC9332DST. > > > > -- > Rod Grimes rgrimes@gndrsh.aac.dev.com > Accurate Automation, Inc. Reliable computers for FreeBSD > From owner-freebsd-stable Thu Oct 2 12:29:26 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id MAA17210 for stable-outgoing; Thu, 2 Oct 1997 12:29:26 -0700 (PDT) Received: from ptway.com (apollo.ptway.com [199.176.148.3]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id MAA17198 for ; Thu, 2 Oct 1997 12:29:20 -0700 (PDT) Received: from brianjr.haskin.org (123R1.ptway.com [199.176.148.66]) by ptway.com (8.7.1/3.4W4-PTWAY-sco-ODT3.0) with ESMTP id PAA09433; Thu, 2 Oct 1997 15:21:19 -0400 (EDT) Message-ID: <3433F5B8.B1179585@ptway.com> Date: Thu, 02 Oct 1997 15:27:52 -0400 From: Brian Haskin X-Mailer: Mozilla 4.01 [en] (Win95; I) MIME-Version: 1.0 To: "Jordan K. Hubbard" CC: freebsd-stable Subject: Re: CVSUP vs. SNAPS X-Priority: 3 (Normal) References: <11918.875811660@time.cdrom.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk Jordan K. Hubbard wrote: > > > 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. > > Jordan Why this seems rather logical and easy to follow at least to me a newbie. Brian Haskin From owner-freebsd-stable Thu Oct 2 12:45:49 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id MAA18277 for stable-outgoing; Thu, 2 Oct 1997 12:45:49 -0700 (PDT) Received: from hub.org (hub.org [207.107.138.200]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id MAA18272 for ; Thu, 2 Oct 1997 12:45:44 -0700 (PDT) Received: from localhost (scrappy@localhost) by hub.org (8.8.5/8.7.5) with SMTP id PAA11262 for ; Thu, 2 Oct 1997 15:45:14 -0400 (EDT) Date: Thu, 2 Oct 1997 15:45:13 -0400 (EDT) From: The Hermit Hacker To: stable@freebsd.org Subject: Recent panic...gdb output ... ? 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 Anyone know how to get more data out of this, if possible? The system rebooted itself the other day, and this seems to be all that gdb wants to show :( # gdb -k kernel.4 vmcore.4 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 1b3000 current pcb at 19acc8 panic: vm_page_alloc: invalid allocation class #0 0xf010e7b3 in boot () (kgdb) where #0 0xf010e7b3 in boot () #1 0xf010ea72 in panic () #2 0xf016cfbe in vm_page_alloc () #3 0xf0128f61 in allocbuf () #4 0xf0128aa8 in getblk () #5 0xf015b81b in ffs_sbupdate () #6 0xf015b36f in ffs_sync () #7 0xf012e32b in sync () #8 0xf010e67d in boot () #9 0xf010ea72 in panic () #10 0xf016cfbe in vm_page_alloc () #11 0xf0129b63 in vm_hold_load_pages () #12 0xf0128d10 in allocbuf () #13 0xf0128aa8 in getblk () #14 0xf012751d in bread () #15 0xf015a0f3 in ffs_blkatoff () #16 0xf015dc02 in ufs_lookup () #17 0xf012bab5 in lookup () #18 0xf012b5f7 in namei () #19 0xf01313ed in vn_open () #20 0xf012e903 in open () #21 0xf0179f73 in syscall () #22 0x10099341 in ?? () #23 0x5885 in ?? () #24 0xef1f in ?? () #25 0x10fbd in ?? () #26 0xb2c8 in ?? () #27 0xe586 in ?? () #28 0x1095 in ?? () (kgdb) quit # Marc G. Fournier scrappy@hub.org Systems Administrator @ hub.org scrappy@freebsd.org From owner-freebsd-stable Thu Oct 2 13:01:43 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id NAA19129 for stable-outgoing; Thu, 2 Oct 1997 13:01:43 -0700 (PDT) Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id NAA19113 for ; Thu, 2 Oct 1997 13:01:36 -0700 (PDT) Received: from harmony [10.0.0.6] by rover.village.org with esmtp (Exim 1.71 #1) id 0xGrRE-0000Ex-00; Thu, 2 Oct 1997 14:01:32 -0600 Received: from harmony.village.org (localhost [127.0.0.1]) by harmony.village.org (8.8.7/8.8.3) with ESMTP id OAA03804; Thu, 2 Oct 1997 14:02:25 -0600 (MDT) Message-Id: <199710022002.OAA03804@harmony.village.org> To: "Jordan K. Hubbard" Subject: Re: CVSUP vs. SNAPS Cc: "Rodney W. Grimes" , andrsn@andrsn.stanford.edu, freebsd-stable@freebsd.org In-reply-to: Your message of "Thu, 02 Oct 1997 10:01:00 PDT." <11918.875811660@time.cdrom.com> References: <11918.875811660@time.cdrom.com> Date: Thu, 02 Oct 1997 14:02:24 -0600 From: Warner Losh Sender: owner-freebsd-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk In message <11918.875811660@time.cdrom.com> "Jordan K. Hubbard" writes: : > 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. Why? It makes perfect sense to me. Warner From owner-freebsd-stable Thu Oct 2 13:06:08 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id NAA19504 for stable-outgoing; Thu, 2 Oct 1997 13:06:08 -0700 (PDT) Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id NAA19498 for ; Thu, 2 Oct 1997 13:06:01 -0700 (PDT) Received: from harmony [10.0.0.6] by rover.village.org with esmtp (Exim 1.71 #1) id 0xGrVW-0000F8-00; Thu, 2 Oct 1997 14:05:58 -0600 Received: from harmony.village.org (localhost [127.0.0.1]) by harmony.village.org (8.8.7/8.8.3) with ESMTP id OAA03840; Thu, 2 Oct 1997 14:06:57 -0600 (MDT) Message-Id: <199710022006.OAA03840@harmony.village.org> To: "Jordan K. Hubbard" Subject: Re: CVSUP vs. SNAPS Cc: "Rodney W. Grimes" , andrsn@andrsn.stanford.edu, freebsd-stable@freebsd.org In-reply-to: Your message of "Thu, 02 Oct 1997 10:12:09 PDT." <12048.875812329@time.cdrom.com> References: <12048.875812329@time.cdrom.com> Date: Thu, 02 Oct 1997 14:06:57 -0600 From: Warner Losh Sender: owner-freebsd-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk In message <12048.875812329@time.cdrom.com> "Jordan K. Hubbard" writes: : 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 :). Ummm, yes. I understand that. I'm saying that the kernel shouldn't identify merely which branch it is on (2.2), but should also identify which major release was the most recent on that branch (2.2.5). : 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. I don't agree. I don't think it implies anything of the sort. You take the first two digits of the release, bolt RELENG_ to the front of them, and you have RELENG_2_2. That's what you ahve to do now when you upgrade from a 2.2.5-RELEASE system anyway. I fail to see the consistancy here. Warner From owner-freebsd-stable Thu Oct 2 13:39:28 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id NAA21327 for stable-outgoing; Thu, 2 Oct 1997 13:39:28 -0700 (PDT) Received: from sabre.goldsword.com (sabre.goldsword.com [199.170.202.32]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id NAA21322 for ; Thu, 2 Oct 1997 13:39:25 -0700 (PDT) Received: (from jfarmer@localhost) by sabre.goldsword.com (8.8.7/8.7.3) id QAA03980; Thu, 2 Oct 1997 16:41:37 -0400 (EDT) Date: Thu, 2 Oct 1997 16:41:37 -0400 (EDT) From: "John T. Farmer" Message-Id: <199710022041.QAA03980@sabre.goldsword.com> To: jkh@time.cdrom.com, kkennawa@physics.adelaide.edu.au Subject: Re: CVSUP vs. SNAPS Cc: andrsn@andrsn.stanford.edu, dg@root.com, freebsd-stable@FreeBSD.ORG, jfarmer@goldsword.com, rgrimes@GndRsh.aac.dev.com Sender: owner-freebsd-stable@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Thu, 02 Oct 1997 10:24:56 -0700 "Jordan K. Hubbard" said: > [Others said...] >> I should also note that at that time the web documentation still referred >> to 2.1 as the stable branch, and 2.2 as current, which did not help to >> ease my confusion. I should HOPE this has changed by now :) > >It should be, though if you find any instances where it's still not, >please point them out to www@freebsd.org! :) > >> So if my opinion counts for anything in this debate, it goes for the >> 2.2.5-stable branch name. :) > >But the branch is called RELENG_2_2 - that is physically the name of >the tag. There is no RELENG_2_2_5 branch tag, which is what your >suggestion would imply and cause even more confusion. > >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 >intend on doing absolutely nothing different than "usual" at this late >stage in the game. > Well, I suspect that Rod thought he had "a genuine effect" back at the 2.1 stage!! Of course , I remember the _same_ argument occuring at the 2.1.5 to 2.1.7 beta/release stage... I think the fact that the argument occurs at _every_ major release point should point out that the terms Jordan wants to use are at odds with a substantial number of users. Heck, having the labeling roll back like that is at odds with _everything_ I've been taught & have taught about life-cycle management in my 17+ year career... If it's the Beta release for the 2.2.5 version, then it should be labeled as the 2.2.5 Beta. The branch label & tags should reflect that. Effectively when you go into the beta cycle, ALL commits to the 2.2-STABLE tree should stop, UNLESS you can guarantee simultaneous commits to BOTH trees. Because, if you insist on continuing the old tree along with the new, they are seperate branches. Yes, yes, I know that they're the same code, but the labeling _MUST_ be different. Otherwise you can never be certain what you're dealing with. But it another way: will there _ever_ be another release based on 2.2.2? No. The date you declared the 2.2.5 beta test period to be in effect has frozen 2.2.2 in time, with only severe bug fixes to be applied. Any new releases from the 2.x strain _will_be_ based on 2.2.5. Remember, cvs, branch labels and tags are there to support release engineering & management, not to force you into a one-size fits none mold. John ------------------------------------------------------------------------- John T. Farmer Proprietor, GoldSword Systems jfarmer@goldsword.com Public Internet Access in East Tennessee dial-in (423)470-9953 for info, e-mail to info@goldsword.com Network Design, Internet Services & Servers, Consulting From owner-freebsd-stable Thu Oct 2 14:03:14 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id OAA22879 for stable-outgoing; Thu, 2 Oct 1997 14:03:14 -0700 (PDT) Received: from hetzels (171-158-235.ipt.aol.com [152.171.158.235]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id OAA22863; Thu, 2 Oct 1997 14:03:03 -0700 (PDT) From: "Scot W. Hetzel" To: "Stable" , "Current" Subject: CTM patch level added to newvers.sh Date: Thu, 2 Oct 1997 15:07:13 -0500 Message-ID: <01bccf6e$c649aa80$0400000a@hetzels> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 4.71.1712.3 X-MimeOLE: Produced By Microsoft MimeOLE V4.71.1712.3 Sender: owner-freebsd-stable@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk I am currently tracking 2.2-STABLE and use the following patch to newvers.sh to have my kernel indicate what CTM patch was used to create it. example: Copyright (c) 1992-1997 FreeBSD Inc. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 2.2-STABLE (0448) #0: Fri Sep 26 21:16:21 CDT 1997 ^^^^^^^ Last CTM update applied 0448. The CTM value will only be shown if the user is using STABLE or CURRENT and has the .ctm_status file in the src directory. Could the attched patch be applied to the src tree for both CURRENT's and STABLE's newvers.sh? Also, is there a better way of locating the .ctm_status file (look at variable S1)? Thanks, Scot ------cut here---- *** /sys/conf/newvers.sh.orig Thu Jun 5 18:01:42 1997 --- /sys/conf/newvers.sh Thu Oct 2 14:55:05 1997 *************** *** 39,47 **** --- 39,62 ---- BRANCH="STABLE" RELEASE="${REVISION}-${BRANCH}" SNAPDATE="" + + #Location of .ctm_status file + S1="../../.." + CTM_STATUS="${S1}/.ctm_status" + if [ "X${SNAPDATE}" != "X" ]; then RELEASE="${RELEASE}-${SNAPDATE}" fi + + #Add CTM patch level for the STABLE or CURRENT Branches + #Only if we are using CTM (.ctm_status exists in the source directory) + if [ "${BRANCH}" = "STABLE" ] || [ "${BRANCH}" = "CURRENT" ]; then + if [ -f ${CTM_STATUS} ]; then + sCTM=`awk '{ printf "%04d", $2 }' ${CTM_STATUS}` + RELEASE="${RELEASE} (${sCTM})" + fi + fi + VERSION="${TYPE} ${RELEASE}" RELDATE="222001" ------cut here---- From owner-freebsd-stable Thu Oct 2 15:19:08 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id PAA27194 for stable-outgoing; Thu, 2 Oct 1997 15:19:08 -0700 (PDT) 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 PAA27185 for ; Thu, 2 Oct 1997 15:19:02 -0700 (PDT) Received: from localhost (murray@localhost) by pooh.cdrom.com (8.8.7/8.7.3) with SMTP id PAA06946; Thu, 2 Oct 1997 15:17:55 -0700 (PDT) Date: Thu, 2 Oct 1997 15:17:54 -0700 (PDT) From: Murray Stokely To: Brian Haskin cc: freebsd-stable@freebsd.org Subject: Re: CVSUP vs. SNAPS In-Reply-To: <3433F5B8.B1179585@ptway.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, 2 Oct 1997, Brian Haskin wrote: % > > 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). % % Why this seems rather logical and easy to follow at least to me a % newbie. Why? If we were in the 2.2.2-STABLE branch right now, it might make some sense. But we're not. We're in 2.2-STABLE. It's a development branch, not a specific release, and the naming scheme fits the development paradigm rather well I think. There is no 2.2.5 branch where a -stable tree could be tracked, its just a specific release from the 2.2 branch. So 2.2.5-stable wouldn't make any sense. Murray Stokely From owner-freebsd-stable Thu Oct 2 15:29:43 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id PAA27869 for stable-outgoing; Thu, 2 Oct 1997 15:29:43 -0700 (PDT) Received: from vader.cs.berkeley.edu (vader.CS.Berkeley.EDU [128.32.38.234]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id PAA27856 for ; Thu, 2 Oct 1997 15:29:33 -0700 (PDT) Received: (from asami@localhost) by vader.cs.berkeley.edu (8.8.6/8.7.3) id PAA24859; Thu, 2 Oct 1997 15:29:21 -0700 (PDT) Date: Thu, 2 Oct 1997 15:29:21 -0700 (PDT) Message-Id: <199710022229.PAA24859@vader.cs.berkeley.edu> To: stable@freebsd.org Subject: panic (dup alloc) in RELENG_2_2 From: asami@cs.berkeley.edu (Satoshi Asami) Sender: owner-freebsd-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk This is on the package building machine (kernel/world from right around the freeze time). Adaptec 3940U, several IBM DCHS09Y (9GB) disks on a ccd. Core file available upon request. Satoshi ------- ## gdb -k kernel.25 vmcore.25 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 1f8000 current pcb at 1de3e0 panic: ffs_valloc: dup alloc #0 0xf0111393 in boot () (kgdb) bt #0 0xf0111393 in boot () #1 0xf0111652 in panic () #2 0xf01903bb in ffs_valloc () #3 0xf019c24e in ufs_makeinode () #4 0xf0199d15 in ufs_create () #5 0xf0133edc in vn_open () #6 0xf013175f in open () #7 0xf01b47d3 in syscall () #8 0x2b305 in ?? () #9 0x14e5 in ?? () #10 0x1c3d in ?? () #11 0x36b4 in ?? () #12 0xdaed in ?? () #13 0x107e in ?? () (kgdb) quit From owner-freebsd-stable Thu Oct 2 15:33:08 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id PAA28162 for stable-outgoing; Thu, 2 Oct 1997 15:33:08 -0700 (PDT) Received: from time.cdrom.com (time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id PAA28152 for ; Thu, 2 Oct 1997 15:33:03 -0700 (PDT) Received: from time.cdrom.com (localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.7/8.6.9) with ESMTP id PAA02689; Thu, 2 Oct 1997 15:31:15 -0700 (PDT) To: "John T. Farmer" cc: kkennawa@physics.adelaide.edu.au, andrsn@andrsn.stanford.edu, dg@root.com, freebsd-stable@FreeBSD.ORG, jfarmer@goldsword.com, rgrimes@GndRsh.aac.dev.com Subject: Re: CVSUP vs. SNAPS In-reply-to: Your message of "Thu, 02 Oct 1997 16:41:37 EDT." <199710022041.QAA03980@sabre.goldsword.com> Date: Thu, 02 Oct 1997 15:31:15 -0700 Message-ID: <2674.875831475@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-stable@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > Of course , I remember the _same_ argument occuring at the 2.1.5 to > 2.1.7 beta/release stage... I think the fact that the argument occurs > at _every_ major release point should point out that the terms Jordan > wants to use are at odds with a substantial number of users. Heck, > having the labeling roll back like that is at odds with _everything_ > I've been taught & have taught about life-cycle management in my 17+ year > career... That may be, but 2 weeks before release is still the wrong time to bring it up. Where were y'all 6 weeks ago with this burning issue? :-) Again, we can discuss this until we're all blue but it won't change the fact that I'm not going to alter my release strategy during a BETA cycle. I'm not deaf to the arguments that this situation is confusing to new users needs to be revisited, I'm simply saying that now is *not* the time to be contemplating such things nor is throwing something like this in my lap at the last minute very much appreciated by yours truly! ;-) > If it's the Beta release for the 2.2.5 version, then it should be > labeled as the 2.2.5 Beta. The branch label & tags should reflect > that. Effectively when you go into the beta cycle, ALL commits to > the 2.2-STABLE tree should stop, UNLESS you can guarantee simultaneous > commits to BOTH trees. Because, if you insist on continuing the 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. ;-) Jordan From owner-freebsd-stable Thu Oct 2 16:01:22 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id QAA29446 for stable-outgoing; Thu, 2 Oct 1997 16:01:22 -0700 (PDT) Received: from time.cdrom.com (time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id QAA29440 for ; Thu, 2 Oct 1997 16:01:16 -0700 (PDT) Received: from time.cdrom.com (localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.7/8.6.9) with ESMTP id QAA25511; Thu, 2 Oct 1997 16:00:24 -0700 (PDT) To: Murray Stokely cc: Brian Haskin , freebsd-stable@FreeBSD.ORG Subject: Re: CVSUP vs. SNAPS In-reply-to: Your message of "Thu, 02 Oct 1997 15:17:54 PDT." Date: Thu, 02 Oct 1997 16:00:24 -0700 Message-ID: <25507.875833224@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-stable@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > On Thu, 2 Oct 1997, Brian Haskin wrote: > % > > 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). > % > % Why this seems rather logical and easy to follow at least to me a > % newbie. > > Why? If we were in the 2.2.2-STABLE branch right now, it might make > some sense. But we're not. We're in 2.2-STABLE. It's a development > branch, not a specific release, and the naming scheme fits the > development paradigm rather well I think. > > There is no 2.2.5 branch where a -stable tree could be tracked, its > just a specific release from the 2.2 branch. So 2.2.5-stable wouldn't > make any sense. Thanks for summarizing my position so succinctly, Murray. ;-) Jordan From owner-freebsd-stable Thu Oct 2 16:20:51 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id QAA00647 for stable-outgoing; Thu, 2 Oct 1997 16:20:51 -0700 (PDT) Received: from dfw-ix7.ix.netcom.com (dfw-ix7.ix.netcom.com [206.214.98.7]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id QAA00635 for ; Thu, 2 Oct 1997 16:20:39 -0700 (PDT) Received: (from smap@localhost) by dfw-ix7.ix.netcom.com (8.8.4/8.8.4) id SAA19926 for ; Thu, 2 Oct 1997 18:20:01 -0500 (CDT) Received: from det-mi24-08.ix.netcom.com(207.220.155.104) by dfw-ix7.ix.netcom.com via smap (V1.3) id rma019901; Thu Oct 2 18:19:57 1997 Message-Id: <3.0.1.16.19971001221807.3b17136e@popd.ix.netcom.com> X-Sender: fredpenn@popd.ix.netcom.com X-Mailer: Windows Eudora Light Version 3.0.1 (16) X-Priority: 1 (Highest) Date: Wed, 01 Oct 1997 22:18:07 -0400 To: freebsd-stable@FreeBSD.ORG From: Fred Penn Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-stable@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk unsubscribe freebsd-stable From owner-freebsd-stable Thu Oct 2 16:23:09 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id QAA00787 for stable-outgoing; Thu, 2 Oct 1997 16:23:09 -0700 (PDT) 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 QAA00779 for ; Thu, 2 Oct 1997 16:23:00 -0700 (PDT) Received: (from chad@localhost) by freebie.dcfinc.com (8.8.3/8.8.3a) id QAA29319; Thu, 2 Oct 1997 16:19:07 -0700 (MST) From: "Chad R. Larson" Message-Id: <199710022319.QAA29319@freebie.dcfinc.com> Subject: Re: CVSUP vs. SNAPS To: imp@village.org (Warner Losh) Date: Thu, 2 Oct 1997 16:19:06 -0700 (MST) Cc: dg@root.com, rgrimes@GndRsh.aac.dev.com, jkh@time.cdrom.com, andrsn@andrsn.stanford.edu, freebsd-stable@FreeBSD.ORG In-Reply-To: <199710021705.LAA02207@harmony.village.org> from Warner Losh at "Oct 2, 97 11:05:19 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 > I've got several systems around here that are nearly > impossible to determine what rev is on them because they all say > 2.2-STABLE, even though some of them are from the 2.2.0 time frame, > and others are 2 hours old. If I can't tell the difference, then > autoconfig scripts that use uname can't either. Ah, but that's a different problem (and one I raised a couple of weeks ago). There should be some easy way (perhaps through "uname") to know where along the STABLE continuum a particular system resides. +--------------- | 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 +--------------- I had suggested incrementing the number after the octithorpe (the #0 above). I was told that number gets incremented if you rebuild your kernel, which may be true but doesn't address the problem. -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 2 16:24:17 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id QAA00888 for stable-outgoing; Thu, 2 Oct 1997 16:24:17 -0700 (PDT) Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id QAA00881 for ; Thu, 2 Oct 1997 16:24:05 -0700 (PDT) Received: from harmony [10.0.0.6] by rover.village.org with esmtp (Exim 1.71 #1) id 0xGub1-0000LZ-00; Thu, 2 Oct 1997 17:23:51 -0600 Received: from harmony.village.org (localhost [127.0.0.1]) by harmony.village.org (8.8.7/8.8.3) with ESMTP id RAA06176; Thu, 2 Oct 1997 17:24:50 -0600 (MDT) Message-Id: <199710022324.RAA06176@harmony.village.org> To: chad@dcfinc.com Subject: Re: CVSUP vs. SNAPS Cc: dg@root.com, rgrimes@GndRsh.aac.dev.com, jkh@time.cdrom.com, andrsn@andrsn.stanford.edu, freebsd-stable@freebsd.org In-reply-to: Your message of "Thu, 02 Oct 1997 16:19:06 PDT." <199710022319.QAA29319@freebie.dcfinc.com> References: <199710022319.QAA29319@freebie.dcfinc.com> Date: Thu, 02 Oct 1997 17:24:50 -0600 From: Warner Losh Sender: owner-freebsd-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk In message <199710022319.QAA29319@freebie.dcfinc.com> "Chad R. Larson" writes: : There should be some easy way (perhaps through "uname") to know where : along the STABLE continuum a particular system resides. uname -r should do this: -r Write the current release level of the operating system to stan- dard output. That's why I'm arguing for going to 2.2.5-STABLE after the release process happens. The docs don't say the current branch of the operating system, but rather say the current release level. For branches with releases on them, that implies to me what I'm arguing for. Warner From owner-freebsd-stable Thu Oct 2 16:35:07 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id QAA01514 for stable-outgoing; Thu, 2 Oct 1997 16:35:07 -0700 (PDT) Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id QAA01495 for ; Thu, 2 Oct 1997 16:34:56 -0700 (PDT) Received: from harmony [10.0.0.6] by rover.village.org with esmtp (Exim 1.71 #1) id 0xGulg-0000M4-00; Thu, 2 Oct 1997 17:34:52 -0600 Received: from harmony.village.org (localhost [127.0.0.1]) by harmony.village.org (8.8.7/8.8.3) with ESMTP id RAA06331; Thu, 2 Oct 1997 17:35:52 -0600 (MDT) Message-Id: <199710022335.RAA06331@harmony.village.org> To: chad@dcfinc.com Subject: Re: CVSUP vs. SNAPS Cc: dg@root.com, rgrimes@GndRsh.aac.dev.com, jkh@time.cdrom.com, andrsn@andrsn.stanford.edu, freebsd-stable@freebsd.org In-reply-to: Your message of "Thu, 02 Oct 1997 16:31:50 PDT." <199710022331.QAA29397@freebie.dcfinc.com> References: <199710022331.QAA29397@freebie.dcfinc.com> Date: Thu, 02 Oct 1997 17:35:52 -0600 From: Warner Losh 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). Warner From owner-freebsd-stable Thu Oct 2 16:36:49 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id QAA01668 for stable-outgoing; Thu, 2 Oct 1997 16:36:49 -0700 (PDT) Received: from dfw-ix7.ix.netcom.com (dfw-ix7.ix.netcom.com [206.214.98.7]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id QAA01656 for ; Thu, 2 Oct 1997 16:36:42 -0700 (PDT) Received: (from smap@localhost) by dfw-ix7.ix.netcom.com (8.8.4/8.8.4) id SAA21582 for ; Thu, 2 Oct 1997 18:36:09 -0500 (CDT) Received: from det-mi24-08.ix.netcom.com(207.220.155.104) by dfw-ix7.ix.netcom.com via smap (V1.3) id rma021568; Thu Oct 2 18:35:47 1997 Message-Id: <3.0.1.16.19971002190226.3ae749b8@popd.ix.netcom.com> X-Sender: fredpenn@popd.ix.netcom.com X-Mailer: Windows Eudora Light Version 3.0.1 (16) X-Priority: 1 (Highest) Date: Thu, 02 Oct 1997 19:02:26 -0400 To: freebsd-stable@FreeBSD.ORG From: Fred Penn Subject: Unsubscribe Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-stable@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Unsubscribe From owner-freebsd-stable Thu Oct 2 16:36:53 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id QAA01680 for stable-outgoing; Thu, 2 Oct 1997 16:36:53 -0700 (PDT) Received: from dfw-ix7.ix.netcom.com (dfw-ix7.ix.netcom.com [206.214.98.7]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id QAA01665 for ; Thu, 2 Oct 1997 16:36:46 -0700 (PDT) Received: (from smap@localhost) by dfw-ix7.ix.netcom.com (8.8.4/8.8.4) id SAA21602 for ; Thu, 2 Oct 1997 18:36:12 -0500 (CDT) Received: from det-mi24-08.ix.netcom.com(207.220.155.104) by dfw-ix7.ix.netcom.com via smap (V1.3) id rma021568; Thu Oct 2 18:35:49 1997 Message-Id: <3.0.1.16.19971002190538.3aaf6daa@popd.ix.netcom.com> X-Sender: fredpenn@popd.ix.netcom.com X-Mailer: Windows Eudora Light Version 3.0.1 (16) X-Priority: 1 (Highest) Date: Thu, 02 Oct 1997 19:05:38 -0400 To: stable@FreeBSD.ORG From: Fred Penn Subject: Unsubscribe Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-stable@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Unsubscribe From owner-freebsd-stable Thu Oct 2 16:50:51 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id QAA02212 for stable-outgoing; Thu, 2 Oct 1997 16:50:51 -0700 (PDT) Received: from alice.pcug.co.uk (Alice.PCUG.CO.UK [192.68.174.72]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id QAA02203 for ; Thu, 2 Oct 1997 16:50:42 -0700 (PDT) From: jake@pcug.co.uk Received: (qmail 24701 invoked by uid 1000); 2 Oct 1997 23:48:26 -0000 Message-ID: <19971002234826.24700.qmail@alice.pcug.co.uk> Subject: games 22-stable world failure To: stable@freebsd.org Date: Fri, 3 Oct 1997 00:48:26 +0100 (BST) 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 cvsup'ed recently to RELENG_2_2 is it just me ? doing make world with an empty /usr/obj how is this happening.. ===> games ===> games/adventure cc -nostdinc -o setup /usr/src/games/adventure/setup.c /usr/src/games/adventure/setup.c:60: No include path in which to find stdio.h *** Error code 1 Stop. *** Error code 1 Stop. *** Error code 1 Stop. *** Error code 1 Stop. *** Error code 1 Stop. No nostdinc appears when I make in the games dir by hand. for now -DNOGAMES is my medication. thanks. jake From owner-freebsd-stable Thu Oct 2 16:58:38 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id QAA02555 for stable-outgoing; Thu, 2 Oct 1997 16:58:38 -0700 (PDT) Received: from vinyl.quickweb.com (vinyl.quickweb.com [209.112.4.14]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id QAA02546 for ; Thu, 2 Oct 1997 16:58:31 -0700 (PDT) Received: (from mark@localhost) by vinyl.quickweb.com (8.8.7/8.6.12) id TAA17941; Thu, 2 Oct 1997 19:58:22 -0400 (EDT) Message-ID: <19971002195822.55220@vinyl.quickweb.com> Date: Thu, 2 Oct 1997 19:58:22 -0400 From: Mark Mayo To: "Jordan K. Hubbard" Cc: Murray Stokely , Brian Haskin , freebsd-stable@FreeBSD.ORG Subject: Re: CVSUP vs. SNAPS References: <25507.875833224@time.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.81e In-Reply-To: <25507.875833224@time.cdrom.com>; from Jordan K. Hubbard on Thu, Oct 02, 1997 at 04:00:24PM -0700 Sender: owner-freebsd-stable@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Thu, Oct 02, 1997 at 04:00:24PM -0700, Jordan K. Hubbard wrote: > > On Thu, 2 Oct 1997, Brian Haskin wrote: > > % > > 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). > > % > > % Why this seems rather logical and easy to follow at least to me a > > % newbie. > > > > Why? If we were in the 2.2.2-STABLE branch right now, it might make > > some sense. But we're not. We're in 2.2-STABLE. It's a development > > branch, not a specific release, and the naming scheme fits the > > development paradigm rather well I think. > > > > There is no 2.2.5 branch where a -stable tree could be tracked, its > > just a specific release from the 2.2 branch. So 2.2.5-stable wouldn't > > make any sense. > > Thanks for summarizing my position so succinctly, Murray. ;-) I'd have to agree! I think all that needs to be explained better is the notion of a "branch" and a "release" - i.e. a release is just a snapshot of the 2.2 development branch. I think many newbies aren't familiar with the branch terminology due to the fact that in the Windows world users just don't get to "touch" the development process so directly :-) My $.02, -Mark > > Jordan -- ------------------------------------------------------------------------ Mark Mayo mark@vmunix.com RingZero Comp. http://www.vmunix.com/mark finger mark@quickweb.com for my PGP key and GCS code ------------------------------------------------------------------------ Win95/NT - 32 bit extensions and a graphical shell for a 16 bit patch to an an 8 bit operating system originally coded for a 4 bit microprocessor, written by a 2 bit company that can't stand 1 bit of competition. -UGU From owner-freebsd-stable Thu Oct 2 16:59:28 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id QAA02619 for stable-outgoing; Thu, 2 Oct 1997 16:59:28 -0700 (PDT) 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 QAA02604 for ; Thu, 2 Oct 1997 16:59:17 -0700 (PDT) Received: (from chad@localhost) by freebie.dcfinc.com (8.8.3/8.8.3a) id QAA29397; Thu, 2 Oct 1997 16:31:52 -0700 (MST) From: "Chad R. Larson" Message-Id: <199710022331.QAA29397@freebie.dcfinc.com> Subject: Re: CVSUP vs. SNAPS To: imp@village.org (Warner Losh) Date: Thu, 2 Oct 1997 16:31:50 -0700 (MST) Cc: chad@dcfinc.com, dg@root.com, rgrimes@GndRsh.aac.dev.com, jkh@time.cdrom.com, andrsn@andrsn.stanford.edu, freebsd-stable@FreeBSD.ORG In-Reply-To: <199710022324.RAA06176@harmony.village.org> from Warner Losh at "Oct 2, 97 05:24:50 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 > In message <199710022319.QAA29319@freebie.dcfinc.com> "Chad R. Larson" writes: > : There should be some easy way (perhaps through "uname") to know where > : along the STABLE continuum a particular system resides. > > uname -r should do this: > -r Write the current release level of the operating system to stan- > dard output. > Wow. I got a comment before the list server even got my original back to me. On the ball, Warner. > That's why I'm arguing for going to 2.2.5-STABLE after the release > process happens. The docs don't say the current branch of the > operating system, but rather say the current release level. For > branches with releases on them, that implies to me what I'm arguing > for. But that still doesn't solve the problem we were discussing above. That is, how can you determine where along a continuum your machine resides. 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. -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 2 19:29:10 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id TAA10055 for stable-outgoing; Thu, 2 Oct 1997 19:29:10 -0700 (PDT) Received: from radford.i-plus.net (root@Radford.i-Plus.net [206.99.237.6]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id TAA10050 for ; Thu, 2 Oct 1997 19:29:05 -0700 (PDT) Received: from totally.nutty.net (insane@totally.nutty.net [206.99.237.44]) by radford.i-plus.net (8.8.6/8.8.5) with SMTP id WAA22818; Thu, 2 Oct 1997 22:25:45 -0400 (EDT) Reply-To: "Troy Settle" From: "Troy Settle" To: "spork" Cc: Subject: Re: de driver and 2.2.5 beta q's Date: Thu, 2 Oct 1997 22:33:16 -0400 Message-ID: <01bccfa4$b48a9b20$2ced63ce@totally.nutty.net> 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: spork To: Rodney W. Grimes Cc: Morgan Davis ; freebsd-stable@FreeBSD.ORG Date: Thursday, October 02, 1997 3:20 PM Subject: Re: de driver and 2.2.5 beta q's >Is there any chance of the problem with the genuine de cards locking up >when the link drops being fixed in 2.2.5? > >I cvsup-ed two days ago, and I still see the problem. Ah... but did you make world and a new kernel? Your original post had something about 2.2.2-RELEASE in it. >> > >> > FreeBSD 2.2.2-RELEASE #0: Tue Jun 10 11:54:28 PDT 1997 >> ^^^^^^^^^^^^^^^^^ >> >> You are running a 2.2.2-RELEASE system, your mail subject said >> 2.2.5 beta, you would find that if you loaded 2.2.2-stable as >> over 60 days ago this problem was fixed: >> >> revision 1.54.2.6 >> date: 1997/08/02 17:44:50; author: rgrimes; state: Exp; lines: +6 -3 >> Add support for the newer SMC 9332BDT cards that have a different >> OUI (00:E0:29) to the older driver in 2.2, the new driver in 3.0 >> should already handle this with the new PHY code. >> Reviewed by: Several of my customers From owner-freebsd-stable Thu Oct 2 19:51:29 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id TAA11096 for stable-outgoing; Thu, 2 Oct 1997 19:51:29 -0700 (PDT) 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 TAA11089 for ; Thu, 2 Oct 1997 19:51:26 -0700 (PDT) Received: from localhost (matt@localhost) by serf.xlrn.ucsb.edu (8.8.7/8.8.5) with SMTP id TAA13208 for ; Thu, 2 Oct 1997 19:51:25 -0700 (PDT) Date: Thu, 2 Oct 1997 19:51:24 -0700 (PDT) From: Matthew M Groener To: freebsd-stable@FreeBSD.ORG Subject: Re: CVSUP vs. SNAPS--STOP!!!! In-Reply-To: <19971002195822.55220@vinyl.quickweb.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 think everyone has heard very iteration without mention one fact: 1. Let Jordan get back to finishing the "freeze" code, and let's deal with it later. I'd much rather get 2.2.5 code on deadline! Please help contribute to this aim. -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 From owner-freebsd-stable Thu Oct 2 22:34:09 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id WAA18747 for stable-outgoing; Thu, 2 Oct 1997 22:34:09 -0700 (PDT) Received: from 586quick166.saturn-tech.com ([207.229.19.32]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id WAA18729 for ; Thu, 2 Oct 1997 22:34:04 -0700 (PDT) Received: from localhost (drussell@localhost) by 586quick166.saturn-tech.com (8.8.7/8.8.4) with SMTP id XAA02374; Thu, 2 Oct 1997 23:32:11 -0600 (MDT) X-Authentication-Warning: 586quick166.saturn-tech.com: drussell owned process doing -bs Date: Thu, 2 Oct 1997 23:32:11 -0600 (MDT) From: Doug Russell To: Warner Losh cc: dg@root.com, "Rodney W. Grimes" , jkh@time.cdrom.com, andrsn@andrsn.stanford.edu, freebsd-stable@FreeBSD.ORG Subject: Re: CVSUP vs. SNAPS In-Reply-To: <199710021705.LAA02207@harmony.village.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, 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...) ?? Later...... From owner-freebsd-stable Thu Oct 2 23:22:19 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id XAA22347 for stable-outgoing; Thu, 2 Oct 1997 23:22:19 -0700 (PDT) Received: from silvia.HIP.Berkeley.EDU (ala-ca14-03.ix.netcom.com [204.32.168.67]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id XAA22342 for ; Thu, 2 Oct 1997 23:22:15 -0700 (PDT) Received: (from asami@localhost) by silvia.HIP.Berkeley.EDU (8.8.7/8.6.9) id XAA12545; Thu, 2 Oct 1997 23:21:55 -0700 (PDT) Date: Thu, 2 Oct 1997 23:21:55 -0700 (PDT) Message-Id: <199710030621.XAA12545@silvia.HIP.Berkeley.EDU> To: dg@root.com CC: rgrimes@GndRsh.aac.dev.com, jkh@time.cdrom.com, andrsn@andrsn.stanford.edu, freebsd-stable@freebsd.org In-reply-to: <199710021544.IAA21048@implode.root.com> (message from David Greenman on Thu, 02 Oct 1997 08:44:23 -0700) Subject: Re: CVSUP vs. SNAPS From: asami@cs.berkeley.edu (Satoshi Asami) Sender: owner-freebsd-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk * No, "2.2" refers to the branch, not to a release. I think we make that * pretty clear. Yep. Besides, what are we going to call 3.0-CURRENT before the 3.0 release then? (2.9999-CURRENT? :) It's going to be 3.0-CURRENT for a while after the release, and we'll have the same "problem". That is not going to be solved by confusing the release and branch names. Satoshi From owner-freebsd-stable Fri Oct 3 00:15:56 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id AAA26112 for stable-outgoing; Fri, 3 Oct 1997 00:15:56 -0700 (PDT) Received: from dog.farm.org (gw-serial2.farm.org [207.111.140.45]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id AAA26107 for ; Fri, 3 Oct 1997 00:15:51 -0700 (PDT) Received: (from dk@localhost) by dog.farm.org (8.7.5/dk#3) id AAA05220; Fri, 3 Oct 1997 00:17:57 -0700 (PDT) Date: Fri, 3 Oct 1997 00:17:57 -0700 (PDT) From: Dmitry Kohmanyuk Message-Id: <199710030717.AAA05220@dog.farm.org> To: ccaputo@alt.net (Chris Caputo) Cc: freebsd-stable@freebsd.org Subject: Re: Another NFS bogon in 2.2-stable? Newsgroups: cs-monolit.gated.lists.freebsd.stable Organization: FARM Computing Association Reply-To: dk+@ua.net X-Newsreader: TIN [version 1.2 PL2] Sender: owner-freebsd-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk In article you wrote: > We are definitely seeing problems with nfsv2 and either tcp or udp > connections. We have tried the -r=1024 fix for udp and that didn't help. > We use the 2.2-stable box as an NFS client to a NetApp NFS server. After > a little while, the FreeBSD box gets into a state where any command that > causes NFS activity hangs, including a simple "df". Once in this state, > the command can not be killed, even with "kill -9" from root. Which version of Data ONTAP (NetApp OS) are you running?? I have 4.1d talking to 2.2-stable clients and have never had this problem with nfsv2 (with nfsv3, you get problems, like you cannot build the kernel on NFS /usr/src/sys because vnode_if.c is built with 4K block of zero bytes. (If you remove this file, and type make again, it works.) I have default mount options, and use NetApp for /usr/cvs , /home , and other actively-used filesystems. > I am gonna start comparing the 2.2-stable sources with 3.0-current sources > to see if there are any obvious fixes. If anyone has any other ideas, > please let me know. We have an immediate desire to get beyond this. ;-) -- old unix hackers don't die, they just turn into zombie processes -- net.someone From owner-freebsd-stable Fri Oct 3 01:19:00 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id BAA29724 for stable-outgoing; Fri, 3 Oct 1997 01:19:00 -0700 (PDT) Received: from super.win.or.jp (super.win.or.jp [202.26.1.170]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id BAA29717 for ; Fri, 3 Oct 1997 01:18:56 -0700 (PDT) Received: from master.interwave.or.jp ([210.148.178.62]) by super.win.or.jp (8.8.7/8.8.7) with ESMTP id RAA21864 for ; Fri, 3 Oct 1997 17:18:38 +0900 (JST) Message-Id: <199710030818.RAA21864@super.win.or.jp> From: "Shizuo Daibo" To: Subject: Unsubscribe Date: Fri, 3 Oct 1997 17:19:16 +0900 X-MSMail-Priority: Normal X-Priority: 3 X-Mailer: Microsoft Internet Mail 4.70.1161 MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-2022-JP Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Unsubscribe From owner-freebsd-stable Fri Oct 3 02:09:17 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id CAA02189 for stable-outgoing; Fri, 3 Oct 1997 02:09:17 -0700 (PDT) Received: from silvia.HIP.Berkeley.EDU (ala-ca14-03.ix.netcom.com [204.32.168.67]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id CAA02166; Fri, 3 Oct 1997 02:09:09 -0700 (PDT) Received: (from asami@localhost) by silvia.HIP.Berkeley.EDU (8.8.7/8.6.9) id CAA14082; Fri, 3 Oct 1997 02:09:07 -0700 (PDT) Date: Fri, 3 Oct 1997 02:09:07 -0700 (PDT) Message-Id: <199710030909.CAA14082@silvia.HIP.Berkeley.EDU> To: ports@freebsd.org, stable@freebsd.org Subject: please test packages-2.2.5 From: asami@cs.berkeley.edu (Satoshi Asami) Sender: owner-freebsd-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Most of the packages for the CDROM have been built and are on ftp://ftp.freebsd.org/pub/FreeBSD/packages-2.2.5/ Please test and let us know ASAP if something is wrong. Satoshi From owner-freebsd-stable Fri Oct 3 03:05:31 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id DAA04932 for stable-outgoing; Fri, 3 Oct 1997 03:05:31 -0700 (PDT) Received: from relay0.jaring.my (root@relay0.jaring.my [192.228.128.122]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id DAA04923 for ; Fri, 3 Oct 1997 03:05:17 -0700 (PDT) Received: (from root@localhost) by relay0.jaring.my (8.8.7/8.8.7) with UUCP id RAA14984 for freebsd-stable@freebsd.org; Fri, 3 Oct 1997 17:21:21 +0800 (MYT) Received: (from phang@localhost) by dgate.po.my (8.8.7/8.6.12) id RAA01772 for freebsd-stable@freebsd.org; Fri, 3 Oct 1997 17:32:40 +0800 (MYT) 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 Date: Fri, 03 Oct 1997 17:29:13 +0800 (MYT) From: kkphang To: freebsd-stable@freebsd.org Subject: Re: ctm src-2.20456 failes Sender: owner-freebsd-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Sorry guys, false alarm. It is my mistake. Missing src-2.2.0455 out there. Sorry.. Cheers, ~phang - -- Kok Khang Phang phone: 603 4913505 fax: 603 4913505 From owner-freebsd-stable Fri Oct 3 03:54:31 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id DAA06672 for stable-outgoing; Fri, 3 Oct 1997 03:54:31 -0700 (PDT) Received: from relay0.jaring.my (root@relay0.jaring.my [192.228.128.122]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id DAA06649 for ; Fri, 3 Oct 1997 03:54:19 -0700 (PDT) Received: (from root@localhost) by relay0.jaring.my (8.8.7/8.8.7) with UUCP id RAA13719 for freebsd-stable@freebsd.org; Fri, 3 Oct 1997 17:11:00 +0800 (MYT) Received: (from phang@localhost) by dgate.po.my (8.8.7/8.6.12) id RAA01668 for freebsd-stable@freebsd.org; Fri, 3 Oct 1997 17:21:36 +0800 (MYT) 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 Date: Fri, 03 Oct 1997 17:15:41 +0800 (MYT) From: kkphang To: freebsd-stable@freebsd.org Subject: ctm src-2.2.0456 failed Sender: owner-freebsd-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk These is the error messages. # ctm -v /opt/src-2.2/*.gz Working on Delta number 450 is already applied; ignoring. Working on Delta number 451 is already applied; ignoring. Working on Delta number 452 is already applied; ignoring. Working on Delta number 453 is already applied; ignoring. Working on Delta number 454 is already applied; ignoring. Working on FS: .ctm_status md5 mismatch. Could have forced. FN: release/sysinstall/help/relnotes.hlp md5 mismatch. FN: release/sysinstall/help/relnotes.hlp edit fails. ctm: exit(120) # ll /opt/src-2.2 total 67 -rw-r--r-- 1 root wheel 4576 Oct 3 16:46 src-2.2.0450.gz -rw-r--r-- 1 root wheel 1050 Oct 3 16:46 src-2.2.0451.gz -rw-r--r-- 1 root wheel 3586 Oct 3 16:46 src-2.2.0452.gz -rw-r--r-- 1 root wheel 273 Oct 3 16:46 src-2.2.0453.gz -rw-r--r-- 1 root wheel 14596 Oct 3 16:46 src-2.2.0454.gz -rw-r--r-- 1 root wheel 13186 Oct 3 16:46 src-2.2.0456.gz -rw-r--r-- 1 root wheel 4100 Oct 3 16:46 src-2.2.0457.gz # Any body out there have the same problem, or just me. Cheers, ~phang - -- Kok Khang Phang phone: 603 4913505 fax: 603 4913505 From owner-freebsd-stable Fri Oct 3 04:02:09 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id EAA07034 for stable-outgoing; Fri, 3 Oct 1997 04:02:09 -0700 (PDT) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id EAA07011 for ; Fri, 3 Oct 1997 04:02:03 -0700 (PDT) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.5/8.6.9) id UAA12663; Fri, 3 Oct 1997 20:52:50 +1000 Date: Fri, 3 Oct 1997 20:52:50 +1000 From: Bruce Evans Message-Id: <199710031052.UAA12663@godzilla.zeta.org.au> To: mike@smith.net.au, stable@FreeBSD.ORG Subject: Re: Crossbuild problem with 2.2.5-BETA Sender: owner-freebsd-stable@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >It appears that there are still some problems with building a tree >that's not in /usr/src however - is this something I shouldn't be >trying to do, or should it work? > >The one that bit me was this line in : > >#include "/usr/src/lib/libc/i386/DEFS.h" /* XXX blech */ >... >The -current DEFS.h goes on to include , which doesn't >exist in -stable. > >Ideas? This is still broken in -stable. See -current for fixes (use asm.h, etc.). -stable still has -I/sys in the Makefiles in ps, iostat, pstat, pciconf, netstat and sysinstall. -stable still has -I/${DESTDIR}sys in the Makefiles in libkvm, libscsi, libipx and libutil. Bruce From owner-freebsd-stable Fri Oct 3 04:45:49 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id EAA08642 for stable-outgoing; Fri, 3 Oct 1997 04:45:49 -0700 (PDT) Received: from time.cdrom.com (time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id EAA08611; Fri, 3 Oct 1997 04:45:28 -0700 (PDT) Received: from time.cdrom.com (localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.7/8.6.9) with ESMTP id EAA02871; Fri, 3 Oct 1997 04:45:00 -0700 (PDT) To: stable@freebsd.org cc: committers@freebsd.org Subject: We are now in 2.2.5 BETA test. Date: Fri, 03 Oct 1997 04:44:59 -0700 Message-ID: <2866.875879099@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk 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. Daily snapshots of the 2.2-stable branch continue to be made on ftp://releng22.freebsd.org/pub/FreeBSD, though each release is now titled 2.2.5-YYMMDD-BETA instead of the usual 2.2-YYMMDD-RELENG during this testing period. These snapshots should now essentially be considered a "floating BETA", each new tester being expected to install the latest one available (and some number of these snaps will also be mirrored at ftp.freebsd.org during the BETA cycle) and reporting whatever bugs they find in it so we can fix them for the next 24 hour period. It is my hope that this slightly different model of BETA testing will allow us to converge more quickly on a quality 2.2.5 release, these daily snapshots (hopefully) also helping to make sure that nothing gets broken at the last minute. We are now also in code freeze for the 2.2-stable branch, code freeze meaning that the riskier areas of the system (primarily the kernel and some of the more "core" utilities) are strictly off-limits and you need to talk to me first before contemplating any serious changes in those areas. Straight-forward bug fixes and non-critical changes (e.g. to things like docs) are fine, as are some of the "this has worked for ages in -current and somebody simply forgot to bring it over!" sorts of things. I don't mean to sound too permissive during a code freeze, and if you break the tree I *will* yell at you, but that latter category is actually something of a worry since there really is a *lot* of stuff which constitutes some simple and obvious bug fix or enhancement and really should have been brought over before now, but everyone simply missed it in the rush. There's so much of this kind of stuff that I really wouldn't mind some of it making it in if it could also happen in the very earliest days of the BETA (noting the "critical section" rule I stated before, obviously) so we could still get some adequate testing in for it. Otherwise there's always 2.2.6, so don't get cocky and push the envelope, either. ;) Release of 2.2.5 is scheduled for the 20th of October. I'll also be making the CD release for this a 4 CD set (finally!) so we'll have a pretty good collection of stuff available. It should be a good release if we can put the next 17 days to good use. Test away, ladies and gentlemen! :-) Jordan From owner-freebsd-stable Fri Oct 3 06:22:30 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id GAA12961 for stable-outgoing; Fri, 3 Oct 1997 06:22:30 -0700 (PDT) Received: from emout04.mail.aol.com (emout04.mx.aol.com [198.81.11.95]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id GAA12954 for ; Fri, 3 Oct 1997 06:22:26 -0700 (PDT) From: Hetzels@aol.com Received: (from root@localhost) by emout04.mail.aol.com (8.7.6/8.7.3/AOL-2.0.0) id JAA12559; Fri, 3 Oct 1997 09:21:54 -0400 (EDT) Date: Fri, 3 Oct 1997 09:21:54 -0400 (EDT) Message-ID: <971003092057_519245415@emout04.mail.aol.com> To: chad@dcfinc.com cc: freebsd-stable@freebsd.org Subject: Re: CVSUP vs. SNAPS Sender: owner-freebsd-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk In a message dated 97-10-02 20:37:36 EDT, chad@freebie.dcfinc.com writes: > > > I've got several systems around here that are nearly > > impossible to determine what rev is on them because they all say > > 2.2-STABLE, even though some of them are from the 2.2.0 time frame, > > and others are 2 hours old. If I can't tell the difference, then > > autoconfig scripts that use uname can't either. > > Ah, but that's a different problem (and one I raised a couple of weeks ago). > > There should be some easy way (perhaps through "uname") to know where > along the STABLE continuum a particular system resides. > I've come up with a fix for this problem that uses the CTM number to indicate the systems current status. See my message "CTM patch level added to newvers.sh" for the patch. Scot W. Hetzel From owner-freebsd-stable Fri Oct 3 06:45:36 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id GAA14207 for stable-outgoing; Fri, 3 Oct 1997 06:45:36 -0700 (PDT) Received: from postman.opengroup.org (postman.opengroup.org [130.105.1.152]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id GAA14191; Fri, 3 Oct 1997 06:45:28 -0700 (PDT) Received: from opengroup.org (brunel.camb.opengroup.org [130.105.3.10]) by postman.opengroup.org (8.8.6/8.8.6) with ESMTP id JAA18983; Fri, 3 Oct 1997 09:44:24 -0400 (EDT) Message-Id: <199710031344.JAA18983@postman.opengroup.org> X-Mailer: exmh version 2.0zeta 7/24/97 To: "Jordan K. Hubbard" Cc: stable@FreeBSD.ORG, committers@FreeBSD.ORG Subject: Re: We are now in 2.2.5 BETA test. In-reply-to: Message from "Jordan K. Hubbard" <2866.875879099@time.cdrom.com> . X-Face: "UZ!}1W2N?eJdN(`1%|/OOPqJ).Idk?UyvWw'W-%`Gto8^IkEm>.g1O$[.;~}8E=Ire0|lO .o>:NlJS1@vO9bVmswRoq3j DdX9YGSeJ5a(mfX[1u>Z63G5_^+'8LVqjqvn X-Url: http://www.osf.org/~loverso/ Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 03 Oct 1997 09:44:15 -0400 From: John Robert LoVerso Sender: owner-freebsd-stable@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > We are now also in code freeze for the 2.2-stable branch, code freeze > meaning that the riskier areas of the system (primarily the kernel and > some of the more "core" utilities) are strictly off-limits and you > need to talk to me first before contemplating any serious changes in > those areas. Technically, this is a "code slush", not a "code freeze". John From owner-freebsd-stable Fri Oct 3 07:50:54 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id HAA18829 for stable-outgoing; Fri, 3 Oct 1997 07:50:54 -0700 (PDT) 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 HAA18824 for ; Fri, 3 Oct 1997 07:50:51 -0700 (PDT) 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 HAA06951; Fri, 3 Oct 1997 07:50:34 -0700 (PDT) Date: Fri, 3 Oct 1997 07:50:34 -0700 (PDT) From: Chris Caputo To: dk+@ua.net cc: freebsd-stable@freebsd.org Subject: Re: Another NFS bogon in 2.2-stable? In-Reply-To: <199710030717.AAA05220@dog.farm.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 Hi. We are running "NetApp Release 4.1cD3: Wed Jul 23 20:07:56 PDT 1997". Are you heavily using the NFS server? We had several hundred processes accessing the NFS filesystems when the problem started happening. With light load there wasn't a problem. Our fix was to go back to 2.1-stable and fix some bugs in that NFS implementation. The same bug fixes may help 2.2-stable but we don't have the luxury of being able to test that right now. Chris On Fri, 3 Oct 1997, Dmitry Kohmanyuk wrote: > In article you wrote: > > We are definitely seeing problems with nfsv2 and either tcp or udp > > connections. We have tried the -r=1024 fix for udp and that didn't help. > > > We use the 2.2-stable box as an NFS client to a NetApp NFS server. After > > a little while, the FreeBSD box gets into a state where any command that > > causes NFS activity hangs, including a simple "df". Once in this state, > > the command can not be killed, even with "kill -9" from root. > > Which version of Data ONTAP (NetApp OS) are you running?? > > I have 4.1d talking to 2.2-stable clients and have never had this problem > with nfsv2 (with nfsv3, you get problems, like you cannot build the kernel > on NFS /usr/src/sys because vnode_if.c is built with 4K block of zero bytes. > (If you remove this file, and type make again, it works.) > I have default mount options, and use NetApp for /usr/cvs , /home , and > other actively-used filesystems. > > > I am gonna start comparing the 2.2-stable sources with 3.0-current sources > > to see if there are any obvious fixes. If anyone has any other ideas, > > please let me know. We have an immediate desire to get beyond this. ;-) > > -- > old unix hackers don't die, they just turn into zombie processes -- net.someone > From owner-freebsd-stable Fri Oct 3 08:04:39 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id IAA19564 for stable-outgoing; Fri, 3 Oct 1997 08:04:39 -0700 (PDT) Received: from luke.pmr.com (luke.pmr.com [207.170.114.132]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id IAA19552 for ; Fri, 3 Oct 1997 08:04:33 -0700 (PDT) Received: (from bob@localhost) by luke.pmr.com (8.8.7/8.8.6) id KAA26050; Fri, 3 Oct 1997 10:04:13 -0500 (CDT) Message-ID: <19971003100413.33095@pmr.com> Date: Fri, 3 Oct 1997 10:04:13 -0500 From: Bob Willcox To: stable list Subject: fork errors - resource temporarily unavailable Reply-To: Bob Willcox Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.84 Sender: owner-freebsd-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Every since I upgraded my system to 2.2-STABLE a couple of months ago I have been having this temporary but re-occuring problem with procmail getting EAGAIN errors when trying to fork one or more of the programs that I have specified in my .procmailrc file. I believe my limits are sufficiently high: Resource limits (current): cputime infinity secs filesize infinity kb datasize-cur 32768 kb stacksize 8192 kb coredumpsize 8192 kb memoryuse-cur 32768 kb memorylocked 10240 kb maxprocesses 512 openfiles-cur 512 as I never have more than about 150 or so processes running on my system, yet procmail (and only procmail!) intermittantly has this problem. Note that I have upgraded my system a few times since I first started seeing this problem (right now I'm running 2.2-stable as of about 5 days ago), yet the problem persists. Any help or advice will be greatly appreciated. Thanks, -- Bob Willcox Deliberation, n.: The act of examining one's bread bob@luke.pmr.com to determine which side it is buttered on. Austin, TX -- Ambrose Bierce, "The Devil's Dictionary" From owner-freebsd-stable Fri Oct 3 08:08:49 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id IAA19824 for stable-outgoing; Fri, 3 Oct 1997 08:08:49 -0700 (PDT) Received: from ns.ase.dowjones.com (ns.ase.dowjones.com [206.112.106.2]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id IAA19815 for ; Fri, 3 Oct 1997 08:08:46 -0700 (PDT) Received: from umber (umber.ase.dowjones.com [206.112.106.116]) by ns.ase.dowjones.com (8.8.7/8.8.5) with SMTP id KAA00452 for ; Fri, 3 Oct 1997 10:08:38 -0500 (CDT) Message-Id: <3.0.1.32.19971003100838.009a26e0@mail.sstar.com> X-Sender: jim.king@mail.sstar.com X-Mailer: Windows Eudora Light Version 3.0.1 (32) Date: Fri, 03 Oct 1997 10:08:38 -0500 To: freebsd-stable@freebsd.org From: Jim King Subject: Still no luck with 21140-AE Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk My Netgear FA310TX card (DEC 21140-AE) is also not liked by the 10/3 boot floppy: FreeBSD 2.2.5-971003-BETA #0: Fri Oct 3 12:55:57 GMT 1997 root@make.ican.net:/usr/src/sys/compile/BOOTMFS CPU: Pentium Pro (199.31-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x619 Stepping=9 Features=0xfbff,MTRR,PGE,MCA,C MOV> real memory = 100663296 (98304K bytes) avail memory = 93368320 (91180K bytes) Probing for devices on PCI bus 0: chip0 rev 2 on pci0:0 chip1 rev 1 on pci0:7:0 chip2 rev 0 on pci0:7:1 vga0 rev 6 int a irq 10 on pci0:15 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 the "enabling 100baseTX" message shows on the console the link light on the hub goes OUT, and doesn't come back on until I exit the install. I've tried various link options with ifconfig with no luck. I also tried connecting to a 10BaseT hub - same results. The -current boot floppy seems to work OK with this card. *************************************************************************** * All opinions expressed herein fully | * * represent the views of my dogs: | Jim King * * Shortstop: "Bark!" | jim.king@mail.sstar.com * * Bunny: "Bark!" | http://www.sstar.com/jim_king/ * *************************************************************************** From owner-freebsd-stable Fri Oct 3 09:10:52 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id JAA24242 for stable-outgoing; Fri, 3 Oct 1997 09:10:52 -0700 (PDT) Received: from super-g.inch.com (super-g.com [207.240.140.161]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id JAA24207 for ; Fri, 3 Oct 1997 09:10:38 -0700 (PDT) Received: from localhost (spork@localhost) by super-g.inch.com (8.8.7/8.8.5) with SMTP id MAA24248; Fri, 3 Oct 1997 12:37:01 -0400 (EDT) Date: Fri, 3 Oct 1997 12:37:01 -0400 (EDT) From: spork X-Sender: spork@super-g.inch.com To: Troy Settle cc: freebsd-stable@FreeBSD.ORG Subject: Re: de driver and 2.2.5 beta q's In-Reply-To: <01bccfa4$b48a9b20$2ced63ce@totally.nutty.net> 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 Yes, you have someone else's mail quoted below, I'm EDT, not PDT... Anyhow, I still see the same behaviour. Cable is unplugged. Cable is plugged back in, and the link stays down. Someone has to go to console and type ifconfig de0 down, ifconfig de0 up... The 3am patch doesn't have this problem, yet it hasn't been integrated. I don't mind patching this stuff up, but I'm curious as to why the fix hasn't made it in. I can only imagine the confusion this would cause someone who is unaware of the problem. I recall the Digital card was once touted as "the" card to buy before the Intel got that label. That's why I bought 5 ;) I'm happy to test, I've got three machines on the bench that I can cvsup again today, and I'll plug and unplug til the sun goes down. Thanks, Charles On Thu, 2 Oct 1997, Troy Settle wrote: > > -----Original Message----- > From: spork > To: Rodney W. Grimes > Cc: Morgan Davis ; freebsd-stable@FreeBSD.ORG > > Date: Thursday, October 02, 1997 3:20 PM > Subject: Re: de driver and 2.2.5 beta q's > > > >Is there any chance of the problem with the genuine de cards locking up > >when the link drops being fixed in 2.2.5? > > > >I cvsup-ed two days ago, and I still see the problem. > > > Ah... but did you make world and a new kernel? Your original post had > something about 2.2.2-RELEASE in it. > > >> > > >> > FreeBSD 2.2.2-RELEASE #0: Tue Jun 10 11:54:28 PDT 1997 > >> ^^^^^^^^^^^^^^^^^ > >> > >> You are running a 2.2.2-RELEASE system, your mail subject said > >> 2.2.5 beta, you would find that if you loaded 2.2.2-stable as > >> over 60 days ago this problem was fixed: > >> > >> revision 1.54.2.6 > >> date: 1997/08/02 17:44:50; author: rgrimes; state: Exp; lines: +6 -3 > >> Add support for the newer SMC 9332BDT cards that have a different > >> OUI (00:E0:29) to the older driver in 2.2, the new driver in 3.0 > >> should already handle this with the new PHY code. > >> Reviewed by: Several of my customers > > From owner-freebsd-stable Fri Oct 3 09:56:56 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id JAA27455 for stable-outgoing; Fri, 3 Oct 1997 09:56:56 -0700 (PDT) Received: from austin.polstra.com (austin.polstra.com [206.213.73.10]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id JAA27445 for ; Fri, 3 Oct 1997 09:56:52 -0700 (PDT) Received: from austin.polstra.com (jdp@localhost) by austin.polstra.com (8.8.7/8.8.5) with ESMTP id JAA05874; Fri, 3 Oct 1997 09:56:29 -0700 (PDT) Message-Id: <199710031656.JAA05874@austin.polstra.com> To: kkennawa@physics.adelaide.edu.au Subject: Re: CVSUP vs. SNAPS In-Reply-To: <9710021643.AA24574@bragg> References: <9710021643.AA24574@bragg> Organization: Polstra & Co., Seattle, WA Cc: stable@freebsd.org Date: Fri, 03 Oct 1997 09:56:28 -0700 From: John Polstra Sender: owner-freebsd-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk In article <9710021643.AA24574@bragg>, Kristian Kennaway wrote: > > I should also note that at that time the web documentation still referred > to 2.1 as the stable branch, and 2.2 as current, which did not help to > ease my confusion. Uh, excuse me, but at that time, officially, 2.1 still WAS the stable branch. That was the case for quite some time after a lot of people started using 2.2. And I don't think the documentation ever referred to 2.2 as current. More likely, it referred to "current" or perhaps "3.0" as current. > I should HOPE this has changed by now :) I updated the web documentation as soon as it was decided publicly that "stable" now refers to the -2.2. branch. Again, the actual change came long after most people starting thinking of -2.2 as the "stable" branch. John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Self-knowledge is always bad news." -- John Barth From owner-freebsd-stable Fri Oct 3 10:01:14 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id KAA27798 for stable-outgoing; Fri, 3 Oct 1997 10:01:14 -0700 (PDT) Received: from austin.polstra.com (austin.polstra.com [206.213.73.10]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id KAA27792 for ; Fri, 3 Oct 1997 10:01:09 -0700 (PDT) Received: from austin.polstra.com (jdp@localhost) by austin.polstra.com (8.8.7/8.8.5) with ESMTP id JAA05912; Fri, 3 Oct 1997 09:59:47 -0700 (PDT) Message-Id: <199710031659.JAA05912@austin.polstra.com> To: mark@quickweb.com Subject: Re: CVSUP vs. SNAPS In-Reply-To: <19971002195822.55220@vinyl.quickweb.com> References: <25507.875833224@time.cdrom.com> <19971002195822.55220@vinyl.quickweb.com> Organization: Polstra & Co., Seattle, WA Cc: stable@freebsd.org Date: Fri, 03 Oct 1997 09:59:47 -0700 From: John Polstra Sender: owner-freebsd-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk In article <19971002195822.55220@vinyl.quickweb.com>, Mark Mayo wrote: > > I'd have to agree! I think all that needs to be explained better is > the notion of a "branch" and a "release" - i.e. a release is just a > snapshot of the 2.2 development branch. I think many newbies aren't > familiar with the branch terminology due to the fact that in the > Windows world users just don't get to "touch" the development process > so directly :-) Here is what the CVSup documentation in the Handbook says: The "tag=" field names a symbolic tag in the repository. There are two kinds of tags, revision tags and branch tags. A revision tag refers to a specific revision. Its meaning stays the same from day to day. A branch tag, on the other hand, refers to the latest revision on a given line of development, at any given time. Because a branch tag does not refer to a specific revision, it may mean something different tomorrow than it means today. It then goes on to list, separately, the relevant branch tags and revision tags. Could it be that the problem is simply that people don't _read_ the documentation which already exists? John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Self-knowledge is always bad news." -- John Barth From owner-freebsd-stable Fri Oct 3 14:02:50 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id OAA12606 for stable-outgoing; Fri, 3 Oct 1997 14:02:50 -0700 (PDT) Received: from GndRsh.aac.dev.com (GndRsh.aac.dev.com [198.145.92.241]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id OAA12595 for ; Fri, 3 Oct 1997 14:02:46 -0700 (PDT) Received: (from rgrimes@localhost) by GndRsh.aac.dev.com (8.8.5/8.7.3) id OAA00264; Fri, 3 Oct 1997 14:01:57 -0700 (PDT) From: "Rodney W. Grimes" Message-Id: <199710032101.OAA00264@GndRsh.aac.dev.com> Subject: Re: CVSUP vs. SNAPS In-Reply-To: <199710021544.IAA21048@implode.root.com> from David Greenman at "Oct 2, 97 08:44:23 am" To: dg@root.com Date: Fri, 3 Oct 1997 14:01:57 -0700 (PDT) Cc: 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 > >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??? -- Rod Grimes rgrimes@gndrsh.aac.dev.com Accurate Automation, Inc. Reliable computers for FreeBSD From owner-freebsd-stable Fri Oct 3 14:05:53 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id OAA12795 for stable-outgoing; Fri, 3 Oct 1997 14:05:53 -0700 (PDT) Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id OAA12693 for ; Fri, 3 Oct 1997 14:04:11 -0700 (PDT) Received: from harmony [10.0.0.6] by rover.village.org with esmtp (Exim 1.71 #1) id 0xHEtH-0000sa-00; Fri, 3 Oct 1997 15:04:03 -0600 Received: from harmony.village.org (localhost [127.0.0.1]) by harmony.village.org (8.8.7/8.8.3) with ESMTP id PAA12733; Fri, 3 Oct 1997 15:03:48 -0600 (MDT) Message-Id: <199710032103.PAA12733@harmony.village.org> To: John Polstra Subject: Re: CVSUP vs. SNAPS Cc: mark@quickweb.com, stable@freebsd.org In-reply-to: Your message of "Fri, 03 Oct 1997 09:59:47 PDT." <199710031659.JAA05912@austin.polstra.com> References: <199710031659.JAA05912@austin.polstra.com> <25507.875833224@time.cdrom.com> <19971002195822.55220@vinyl.quickweb.com> Date: Fri, 03 Oct 1997 15:03:48 -0600 From: Warner Losh Sender: owner-freebsd-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk In message <199710031659.JAA05912@austin.polstra.com> John Polstra writes: : Could it be that the problem is simply that people don't _read_ the : documentation which already exists? Actually, I think it all revolves around the definition of "revision" personally. I have read the docs, and have been around for years. I know what the definitions are. I'm just saying that it would be more useful to change them a little... Jordan, when's the first day that you'll listen to new arguments on this :-) Warner From owner-freebsd-stable Fri Oct 3 15:10:04 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id PAA15989 for stable-outgoing; Fri, 3 Oct 1997 15:10:04 -0700 (PDT) Received: from bofh.noc.best.net (rone@ennui.org [205.149.163.54]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id PAA15972 for ; Fri, 3 Oct 1997 15:10:01 -0700 (PDT) Received: (from rone@localhost) by bofh.noc.best.net (8.8.7/8.7.3) id PAA15020 for stable@freebsd.org; Fri, 3 Oct 1997 15:09:51 -0700 (PDT) From: Ron Echeverri Message-Id: <199710032209.PAA15020@bofh.noc.best.net> Subject: Re: CVSUP vs. SNAPS In-Reply-To: <199710032101.OAA00264@GndRsh.aac.dev.com> from "Rodney W. Grimes" at "Oct 3, 97 02:01:57 pm" To: stable@freebsd.org Date: Fri, 3 Oct 1997 15:09:51 -0700 (PDT) X-GmbH: Gesellschaft mit beschränkter Haftung 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 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. rone -- Ron Echeverri Systems/Usenet Administration "This is _my_ ISP, _i_ do the Best Internet Communications, Inc. ass-kicking around here!" -rpwhite From owner-freebsd-stable Fri Oct 3 15:30:18 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id PAA17012 for stable-outgoing; Fri, 3 Oct 1997 15:30:18 -0700 (PDT) Received: from smtp.northlink.com (root@prescott.northlink.com [209.75.160.32]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id PAA17005 for ; Fri, 3 Oct 1997 15:30:14 -0700 (PDT) Received: from Emry (pm3-3.northlink.com [209.75.160.127]) by smtp.northlink.com (8.8.6/8.7.3) with SMTP id PAA26147 for ; Fri, 3 Oct 1997 15:30:04 -0700 (MST) Message-Id: <199710032230.PAA26147@smtp.northlink.com> Comments: Authenticated sender is From: "Wilton Hughes" To: stable@FreeBSD.ORG Date: Fri, 3 Oct 1997 15:20:03 -0700 Subject: unsubscribe Reply-to: Wilton Hughes Priority: normal X-mailer: Pegasus Mail for Windows (v2.23) Sender: owner-freebsd-stable@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Wilton Hughes 520-776-8272 3682 Estate Drive Prescott, Arizona 86303-7523 Wilton Hughes From owner-freebsd-stable Fri Oct 3 15:54:51 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id PAA18330 for stable-outgoing; Fri, 3 Oct 1997 15:54:51 -0700 (PDT) Received: from time.cdrom.com (time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id PAA18313 for ; Fri, 3 Oct 1997 15:54:43 -0700 (PDT) Received: from time.cdrom.com (localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.7/8.6.9) with ESMTP id PAA24380; Fri, 3 Oct 1997 15:53:39 -0700 (PDT) To: Warner Losh cc: John Polstra , mark@quickweb.com, stable@FreeBSD.ORG Subject: Re: CVSUP vs. SNAPS In-reply-to: Your message of "Fri, 03 Oct 1997 15:03:48 MDT." <199710032103.PAA12733@harmony.village.org> Date: Fri, 03 Oct 1997 15:53:39 -0700 Message-ID: <24377.875919219@time.cdrom.com> From: "Jordan K. Hubbard" 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. ;) Jordan From owner-freebsd-stable Fri Oct 3 16:55:43 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id QAA20965 for stable-outgoing; Fri, 3 Oct 1997 16:55:43 -0700 (PDT) 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 QAA20958 for ; Fri, 3 Oct 1997 16:55:40 -0700 (PDT) Received: (from chad@localhost) by freebie.dcfinc.com (8.8.3/8.8.3a) id QAA00960; Fri, 3 Oct 1997 16:54:49 -0700 (MST) From: "Chad R. Larson" Message-Id: <199710032354.QAA00960@freebie.dcfinc.com> Subject: Re: CVSUP vs. SNAPS To: Hetzels@aol.com Date: Fri, 3 Oct 1997 16:54:47 -0700 (MST) Cc: stable@freebsd.org In-Reply-To: <971003092057_519245415@emout04.mail.aol.com> from "Hetzels@aol.com" at "Oct 3, 97 09:21:54 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 > I've come up with a fix for this problem that uses the CTM number to > indicate the systems current status. See my message "CTM patch level > added to newvers.sh" for the patch. And certainly in the correct spirit of things. However, I have a T1 to the internet, and use CVSup to track the -STABLE branch. Something perhaps a little more universal is needed. Perhaps a hack to CVSup to collect some serialized number, or date/time stamp which can be built into the kernel (part of the uname structure)? Of course, that doesn't cover folks who update the kernel seperately from all the utilities. Or who update one subsystem (sendmail, perhaps). Those people can check the ID of the source files, I guess. And they should know what parts they have mucked with. -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 Fri Oct 3 17:21:17 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id RAA22441 for stable-outgoing; Fri, 3 Oct 1997 17:21:17 -0700 (PDT) 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 RAA22434 for ; Fri, 3 Oct 1997 17:21:13 -0700 (PDT) Received: (from chad@localhost) by freebie.dcfinc.com (8.8.3/8.8.3a) id RAA01013; Fri, 3 Oct 1997 17:19:56 -0700 (MST) From: "Chad R. Larson" Message-Id: <199710040019.RAA01013@freebie.dcfinc.com> Subject: Re: CVSup release identity To: bob@luke.pmr.com Date: Fri, 3 Oct 1997 17:19:55 -0700 (MST) Cc: freebsd-stable@FreeBSD.ORG In-Reply-To: <19971003100413.33095@pmr.com> from Bob Willcox at "Oct 3, 97 10:04:13 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 > Bob Willcox writes (from another thread): > Note that I have upgraded my system a few times since I first started > seeing this problem (right now I'm running 2.2-stable as of about 5 > days ago), yet the problem persists. This is exactly the ambiguity we're discussing. He says,"as of about 5 days ago." Wouldn't it be better for the guy trying to fix things if his uname returned something like "2.2-STABLE-AA"? If we used [0-9A-Z][0-9A-Z] it would recycle every 1300 (or so) commits. If we allowed lower-case characters as well, we could run that out to 3844 commits. How many commits are done in, say, a week? Or year? I guess what I'm suggesting is that CVS should increment a variable, and create a file containing the variable each time a change is committed to a particular branch. CVSup and CTM would always have that file as part of a fetch, and newvers.sh would know how to pick up and jam that data into vers.c. Comments? -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 Fri Oct 3 19:57:48 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id TAA28746 for stable-outgoing; Fri, 3 Oct 1997 19:57:48 -0700 (PDT) Received: from spring.spider.net.hk (root@spring.spider.net.hk [202.73.0.2]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id TAA28738 for ; Fri, 3 Oct 1997 19:57:41 -0700 (PDT) Received: from spider.net.hk (cat.spider.net.hk [202.73.0.10]) by spring.spider.net.hk (8.8.7/8.7.3) with ESMTP id LAA14201 for ; Sat, 4 Oct 1997 11:02:46 +0800 Message-ID: <3435B0A0.4758162E@spider.net.hk> Date: Sat, 04 Oct 1997 10:57:36 +0800 From: Geoffrey NG Organization: Spider Net (HK) Limited X-Mailer: Mozilla 4.03 [en] (Win95; I) MIME-Version: 1.0 To: freebsd-stable@FreeBSD.ORG Subject: (no subject) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk subscribe freebsd-stable From owner-freebsd-stable Fri Oct 3 23:35:12 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id XAA00898 for stable-outgoing; Fri, 3 Oct 1997 23:35:12 -0700 (PDT) Received: from dfw-ix7.ix.netcom.com (dfw-ix7.ix.netcom.com [206.214.98.7]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id XAA00880 for ; Fri, 3 Oct 1997 23:35:07 -0700 (PDT) Received: (from smap@localhost) by dfw-ix7.ix.netcom.com (8.8.4/8.8.4) id XAA08337 for ; Fri, 3 Oct 1997 23:39:13 -0500 (CDT) Received: from sjx-ca28-20.ix.netcom.com(204.31.235.116) by dfw-ix7.ix.netcom.com via smap (V1.3) id rma008330; Fri Oct 3 23:38:53 1997 Received: (from asami@localhost) by blimp.mimi.com (8.8.7/8.6.9) id VAA00973; Fri, 3 Oct 1997 21:38:51 -0700 (PDT) Date: Fri, 3 Oct 1997 21:38:51 -0700 (PDT) Message-Id: <199710040438.VAA00973@blimp.mimi.com> To: stable@freebsd.org In-reply-to: <199710022229.PAA24859@vader.cs.berkeley.edu> (asami@cs.berkeley.edu) Subject: Re: panic (dup alloc) in RELENG_2_2 From: asami@cs.berkeley.edu (Satoshi Asami) Sender: owner-freebsd-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Here's another one. A slightly older RELENG_2_2. 200MHz P6 with 96 MB of memory. It is an NFS server of our cluster (as you can see below). Satoshi ------- ## gdb -k kernel.4 vmcore.4 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 1e8a28 panic: ufs_ihashget: recursive lock not expected -- pid %d #0 0xf0114e53 in boot () (kgdb) bt #0 0xf0114e53 in boot () #1 0xf0115112 in panic () #2 0xf01a0501 in ufs_ihashget () #3 0xf019e673 in ffs_vget () #4 0xf01a31d7 in ufs_check_export () #5 0xf019e93b in ffs_fhtovp () #6 0xf01734bc in nfsrv_fhtovp () #7 0xf015d120 in nfsrv_write () #8 0xf0174730 in nfssvc_nfsd () #9 0xf0173e98 in nfssvc () #10 0xf01bde73 in syscall () #11 0x2945 in ?? () #12 0x107e in ?? () From owner-freebsd-stable Sat Oct 4 01:02:14 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id BAA05085 for stable-outgoing; Sat, 4 Oct 1997 01:02:14 -0700 (PDT) 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 BAA05069 for ; Sat, 4 Oct 1997 01:02:06 -0700 (PDT) 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 IAA01458 for ; Sat, 4 Oct 1997 08:56:52 +0100 (BST) Message-Id: <199710040756.IAA01458@hawk.gnome.co.uk> X-Mailer: exmh version 2.0zeta 7/24/97 To: stable@freebsd.org Subject: unable to compile latest kernel Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 04 Oct 1997 08:56:51 +0100 From: Chris Stenton Sender: owner-freebsd-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I have just suped the latest updates to stable and performed a "make world" and then tried to recompile my kernel and get the following error. make -f ../../dev/aic7xxx/Makefile MAKESRCPATH=../../dev/aic7xxx Warning: Object directory not changed from original /sys/compile/GNOME 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 function) ../../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 Chris From owner-freebsd-stable Sat Oct 4 07:05:32 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id HAA16961 for stable-outgoing; Sat, 4 Oct 1997 07:05:32 -0700 (PDT) Received: from emout20.mail.aol.com (emout20.mx.aol.com [198.81.11.46]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id HAA16945 for ; Sat, 4 Oct 1997 07:05:28 -0700 (PDT) From: Hetzels@aol.com Received: (from root@localhost) by emout20.mail.aol.com (8.7.6/8.7.3/AOL-2.0.0) id KAA06959 for freebsd-stable@freebsd.org; Sat, 4 Oct 1997 10:01:43 -0400 (EDT) Date: Sat, 4 Oct 1997 10:01:43 -0400 (EDT) Message-ID: <971004100142_1343217230@emout20.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 In a message dated 97-10-04 03:47:06 EDT, chad@freebie.dcfinc.com (Chad R. Larson) writes: > I guess what I'm suggesting is that CVS should increment a variable, and > create a file containing the variable each time a change is committed to > a particular branch. CVSup and CTM would always have that file as part > of a fetch, and newvers.sh would know how to pick up and jam that data > into vers.c. > Such as my patch to newvers.sh (I posted to STABLE & CURRENT a couple of days ago) that I use to track the CTM delta number with. 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. Scot From owner-freebsd-stable Sat Oct 4 10:02:29 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id KAA23867 for stable-outgoing; Sat, 4 Oct 1997 10:02:29 -0700 (PDT) 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 KAA23857 for ; Sat, 4 Oct 1997 10:02:20 -0700 (PDT) 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 RAA04686; Sat, 4 Oct 1997 17:42:52 +0100 (BST) Message-Id: <199710041642.RAA04686@hawk.gnome.co.uk> X-Mailer: exmh version 2.0zeta 7/24/97 To: gibbs@narnia.plutotech.com (Justin T. Gibbs) cc: stable@freebsd.org Subject: Re: unable to compile latest kernel In-reply-to: Your message of "Sat, 04 Oct 1997 09:55:52 MDT." <199710041555.JAA13686@narnia.plutotech.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 04 Oct 1997 17:42:51 +0100 From: Chris Stenton Sender: owner-freebsd-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > In article <199710040756.IAA01458@hawk.gnome.co.uk>, > Chris Stenton writes: > > > > I have just suped the latest updates to stable and performed a "make world" > > and then tried to recompile my kernel and get the following error. > > Perform a make -f ../../dev/aic7xxx/Makefile MAKESRCPATH=$S/dev/aic7xxx clean > from your kernel compile directory > > and just in case, a: > > cd /usr/src/sys/dev/aic7xxx;make clean > Justin, Did not work. I got the same error. What I did was delete dev/aic7xxx and rerun sup. This worked. The directory before I did the delete had: -rw-rw-r-- 1 root wheel 511 Sep 28 03:07 Makefile -rw-r--r-- 1 root wheel 23147 Sep 28 03:07 aic7xxx.reg -rw-r--r-- 1 root wheel 34605 Sep 28 03:07 aic7xxx.seq -rwxrwxr-x 1 root wheel 48868 Apr 3 1997 aic7xxx_asm -rw-r--r-- 1 root wheel 5973 Apr 2 1997 aic7xxx_asm.o -rw-r--r-- 1 root wheel 11889 Sep 3 05:25 aicasm.c -rw-r--r-- 1 root wheel 2476 Mar 16 1997 aicasm.h -rw-r--r-- 1 root wheel 27650 Sep 28 03:07 aicasm_gram.y -rw-r--r-- 1 root wheel 6683 Sep 28 03:07 aicasm_scan.l -rw-r--r-- 1 root wheel 11023 Sep 28 03:07 aicasm_symbol.c -rw-r--r-- 1 root wheel 3601 Sep 28 03:07 aicasm_symbol.h -rw-r--r-- 1 root wheel 53315 Apr 2 1997 gram.c -rw-r--r-- 1 root wheel 26328 Apr 2 1997 gram.o -rw-r--r-- 1 root wheel 60159 Apr 2 1997 scan.c -rw-r--r-- 1 root wheel 15666 Apr 2 1997 scan.o -rw-r--r-- 1 root wheel 2810 Sep 28 03:07 sequencer.h -rw-r--r-- 1 root wheel 3378 Apr 2 1997 symbol.o After it has: -rw-r--r-- 1 root wheel 511 Sep 27 20:46 Makefile -rw-r--r-- 1 root wheel 23147 Sep 27 20:46 aic7xxx.reg -rw-r--r-- 1 root wheel 34605 Sep 27 20:46 aic7xxx.seq -rw-r--r-- 1 root wheel 11889 Sep 3 05:25 aicasm.c -rw-r--r-- 1 root wheel 2476 Mar 16 1997 aicasm.h -rw-r--r-- 1 root wheel 27650 Sep 27 20:46 aicasm_gram.y -rw-r--r-- 1 root wheel 6683 Sep 27 20:46 aicasm_scan.l -rw-r--r-- 1 root wheel 11023 Sep 27 20:46 aicasm_symbol.c -rw-r--r-- 1 root wheel 3601 Sep 27 20:46 aicasm_symbol.h -rw-r--r-- 1 root wheel 2810 Sep 27 20:47 sequencer.h A number of points ... The time stamps on some files have gone backwards and some files are not there at all! How can this occur under cvs and sup? Chris From owner-freebsd-stable Sat Oct 4 10:55:20 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id KAA27344 for stable-outgoing; Sat, 4 Oct 1997 10:55:20 -0700 (PDT) Received: from ns.mt.sri.com (SRI-56K-FR.mt.net [206.127.65.42]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id KAA27339 for ; Sat, 4 Oct 1997 10:55:16 -0700 (PDT) Received: from rocky.mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by ns.mt.sri.com (8.8.7/8.8.7) with ESMTP id LAA28561; Sat, 4 Oct 1997 11:55:00 -0600 (MDT) Received: (from nate@localhost) by rocky.mt.sri.com (8.7.5/8.7.3) id LAA23480; Sat, 4 Oct 1997 11:54:54 -0600 (MDT) Date: Sat, 4 Oct 1997 11:54:54 -0600 (MDT) Message-Id: <199710041754.LAA23480@rocky.mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: "Jordan K. Hubbard" Cc: "Rodney W. Grimes" , andrsn@andrsn.stanford.edu, freebsd-stable@freebsd.org Subject: Re: CVSUP vs. SNAPS In-Reply-To: <11918.875811660@time.cdrom.com> References: <199710021358.GAA28556@GndRsh.aac.dev.com> <11918.875811660@time.cdrom.com> X-Mailer: VM 6.29 under 19.15 XEmacs Lucid 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. Why? I agree with Rod (and so does Warner if I read things right.) Nate From owner-freebsd-stable Sat Oct 4 11:07:03 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id LAA28194 for stable-outgoing; Sat, 4 Oct 1997 11:07:03 -0700 (PDT) Received: from ns.mt.sri.com (SRI-56K-FR.mt.net [206.127.65.42]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id LAA28186 for ; Sat, 4 Oct 1997 11:07:00 -0700 (PDT) Received: from rocky.mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by ns.mt.sri.com (8.8.7/8.8.7) with ESMTP id MAA28650; Sat, 4 Oct 1997 12:06:35 -0600 (MDT) Received: (from nate@localhost) by rocky.mt.sri.com (8.7.5/8.7.3) id MAA23536; Sat, 4 Oct 1997 12:06:31 -0600 (MDT) Date: Sat, 4 Oct 1997 12:06:31 -0600 (MDT) Message-Id: <199710041806.MAA23536@rocky.mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: "Jordan K. Hubbard" Cc: Warner Losh , "Rodney W. Grimes" , andrsn@andrsn.stanford.edu, freebsd-stable@freebsd.org Subject: Re: CVSUP vs. SNAPS In-Reply-To: <12048.875812329@time.cdrom.com> References: <199710021509.JAA00956@harmony.village.org> <12048.875812329@time.cdrom.com> X-Mailer: VM 6.29 under 19.15 XEmacs Lucid Sender: owner-freebsd-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > 2.2 is the branch ID [ Arguements about what CVS does ] That's *irrelevant* to what goes out the door. Just because the release engineering process uses a TAG of 'foo', doesn't mean that a release can't be called 'bar'. I'm with Rod on this one. With the 3.0 release, I think we should call the original release '3.0.0' if we plan on having multiple releases. How CVS fits in this is really irrelevant, since the users don't care for the most part how it's done, and CVS will support whatever we want it to do. There is a *huge* different from a 2.2-stable box that was built slightl after '2.2-RELEASE', and one built today. It would be nice (and trivial to do) to have the branch tag change *AFTER* 2.2.5 to say '2.2.5-stable'. But, it doesn't have to happen until *after* the bits are set down for 2.2.5, so arguments now are only wasting time. We can always argue for it after 2.2.5 is done. :) :) Nate ps. I note that the 'tag' used to denote '2.2-RELEASE' is "RELENG_2_2_0_RELEASE" and *NOT* "RELENG_2_2_RELEASE", which is what Jordan is arguing about. Even internally the tags seem to support what Rod and others are arguing for, we just want to make that information available to the kernel. From owner-freebsd-stable Sat Oct 4 11:16:27 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id LAA28845 for stable-outgoing; Sat, 4 Oct 1997 11:16:27 -0700 (PDT) Received: from ns.mt.sri.com (SRI-56K-FR.mt.net [206.127.65.42]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id LAA28824; Sat, 4 Oct 1997 11:16:22 -0700 (PDT) Received: from rocky.mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by ns.mt.sri.com (8.8.7/8.8.7) with ESMTP id MAA28728; Sat, 4 Oct 1997 12:16:19 -0600 (MDT) Received: (from nate@localhost) by rocky.mt.sri.com (8.7.5/8.7.3) id MAA23555; Sat, 4 Oct 1997 12:16:13 -0600 (MDT) Date: Sat, 4 Oct 1997 12:16:13 -0600 (MDT) Message-Id: <199710041816.MAA23555@rocky.mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: "Scot W. Hetzel" Cc: "Stable" , "Current" Subject: Re: CTM patch level added to newvers.sh In-Reply-To: <01bccf6e$c649aa80$0400000a@hetzels> References: <01bccf6e$c649aa80$0400000a@hetzels> X-Mailer: VM 6.29 under 19.15 XEmacs Lucid Sender: owner-freebsd-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > I am currently tracking 2.2-STABLE and use the following patch to newvers.sh > to have my kernel indicate what CTM patch was used to create it. We need a solution that isn't specific to the transport medium, or in more specific terms a solution that works irregardless of how you got the bits. Nate From owner-freebsd-stable Sat Oct 4 11:19:46 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id LAA29016 for stable-outgoing; Sat, 4 Oct 1997 11:19:46 -0700 (PDT) Received: from bsd3.nyct.net (myj@bsd3.nyct.net [204.141.86.7]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id LAA29011 for ; Sat, 4 Oct 1997 11:19:44 -0700 (PDT) Received: from localhost (myj@localhost) by bsd3.nyct.net (8.8.7/8.8.5) with SMTP id OAA04960; Sat, 4 Oct 1997 14:19:19 -0400 (EDT) X-Authentication-Warning: bsd3.nyct.net: myj owned process doing -bs Date: Sat, 4 Oct 1997 14:19:19 -0400 (EDT) From: Paul Sandys To: Bob Willcox cc: stable list Subject: Re: fork errors - resource temporarily unavailable In-Reply-To: <19971003100413.33095@pmr.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 Fri, 3 Oct 1997, Bob Willcox wrote: > Date: Fri, 3 Oct 1997 10:04:13 -0500 > From: Bob Willcox > Reply-To: Bob Willcox > To: stable list > Subject: fork errors - resource temporarily unavailable > > Every since I upgraded my system to 2.2-STABLE a couple of months ago I > have been having this temporary but re-occuring problem with procmail > getting EAGAIN errors when trying to fork one or more of the programs > that I have specified in my .procmailrc file. I believe my limits are > sufficiently high: > > Resource limits (current): > cputime infinity secs > filesize infinity kb > datasize-cur 32768 kb > stacksize 8192 kb > coredumpsize 8192 kb > memoryuse-cur 32768 kb > memorylocked 10240 kb > maxprocesses 512 > openfiles-cur 512 I had same problem here. I tracked it down to sendmail being started from /etc/rc scripts with limits of 32 processes or so. My theory is, that at the moment procmail changes UID to yours, it still checks against limits from startup. I cured this by unlimiting all resources in my /etc/rc. Starting sendmail from unlimited shell also fixes the problem. This also brings the question about default limits processing. These are limits on my RELENG_2_2 machine during boot: Resource limits (current): cputime infinity secs filesize 65536 kb datasize-cur 16384 kb stacksize-cur 8192 kb coredumpsize 0 kb memoryuse-cur 65536 kb memorylocked-cur 65536 kb maxprocesses 32 openfiles-cur 64 At the same time, I've got following lines in my kernel config file: options "CHILD_MAX=1024" options "OPEN_MAX=1024" options "FD_SETSIZE=1024" I believed, that above will raise my default limits, but it doesn't seem to be happening. > > as I never have more than about 150 or so processes running on my > system, yet procmail (and only procmail!) intermittantly has this > problem. > > Note that I have upgraded my system a few times since I first started > seeing this problem (right now I'm running 2.2-stable as of about 5 days > ago), yet the problem persists. > > Any help or advice will be greatly appreciated. > > Thanks, > -- > Bob Willcox Deliberation, n.: The act of examining one's bread > bob@luke.pmr.com to determine which side it is buttered on. > Austin, TX -- Ambrose Bierce, "The Devil's Dictionary" > P. <-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-> < myj@nyct.net Paul Sandys | New York Connect http://www.nyct.net > < network operations manager | Total Solution provider > <-------------------------------------------------------------------------> < " BRINGING NEW YORK THE INTERNET SERVICES IT DESERVES " > <-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-> From owner-freebsd-stable Sat Oct 4 11:32:58 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id LAA29714 for stable-outgoing; Sat, 4 Oct 1997 11:32:58 -0700 (PDT) Received: from emout19.mail.aol.com (emout19.mx.aol.com [198.81.11.45]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id LAA29709; Sat, 4 Oct 1997 11:32:55 -0700 (PDT) From: Hetzels@aol.com Received: (from root@localhost) by emout19.mail.aol.com (8.7.6/8.7.3/AOL-2.0.0) id OAA10221; Sat, 4 Oct 1997 14:32:23 -0400 (EDT) Date: Sat, 4 Oct 1997 14:32:23 -0400 (EDT) Message-ID: <971004143220_-729141990@emout19.mail.aol.com> To: nate@mt.sri.com cc: stable@freebsd.org, current@freebsd.org Subject: Re: CTM patch level added to newvers.sh Sender: owner-freebsd-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk In a message dated 97-10-04 14:16:27 EDT, nate@mt.sri.com writes: > > I am currently tracking 2.2-STABLE and use the following patch to newvers.sh > > to have my kernel indicate what CTM patch was used to create it. > > We need a solution that isn't specific to the transport medium, or in > more specific terms a solution that works irregardless of how you got > the bits. > I agree. One method I would like to see is that the .ctm_status file becomes a permanant part of the src tree. (Why?) Because CTM deltas are created at least once every day. Also, when a site is upgrading a RELEASE system to a STABLE system, via CTM, they don't have to ask "What CTM version is my RELEASE?"! They would know by looking at the .ctm_status file. As for CVS, since each site can download different parts of the source tree, it is more difficult to assign a general number to their version. Unless they download the entire sources and then the .ctm_status file would be updated to the latest #. NOTE: the # may/may not be compatible with the latest CTM delta, as the src is always updated between CTM delta's. But, at least this would give people an idea as to how far off from the sources they are at for both CTM/CVS. Scot From owner-freebsd-stable Sat Oct 4 14:25:49 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id OAA07345 for stable-outgoing; Sat, 4 Oct 1997 14:25:49 -0700 (PDT) Received: from synertec.ene.UnB.br (synertec.ene.UnB.br [164.41.46.50]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id OAA07337 for ; Sat, 4 Oct 1997 14:25:32 -0700 (PDT) Received: from localhost (freebsd@localhost) by synertec.ene.UnB.br (8.8.7/8.8.6) with SMTP id SAA09807 for ; Sat, 4 Oct 1997 18:24:45 -0300 (EST) Date: Sat, 4 Oct 1997 18:24:44 -0300 (EST) From: FreeBSD To: stable@freebsd.org Subject: strptime prototype missing in time.h 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 The subject says it all! From owner-freebsd-stable Sat Oct 4 14:37:26 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id OAA08289 for stable-outgoing; Sat, 4 Oct 1997 14:37:26 -0700 (PDT) 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 OAA08284 for ; Sat, 4 Oct 1997 14:37:24 -0700 (PDT) Received: (from chad@localhost) by freebie.dcfinc.com (8.8.3/8.8.3a) id OAA03593; Sat, 4 Oct 1997 14:36:43 -0700 (MST) From: "Chad R. Larson" Message-Id: <199710042136.OAA03593@freebie.dcfinc.com> Subject: Re: CVSup release identity To: Hetzels@aol.com Date: Sat, 4 Oct 1997 14:36:41 -0700 (MST) Cc: freebsd-stable@FreeBSD.ORG In-Reply-To: <971004100142_1343217230@emout20.mail.aol.com> from "Hetzels@aol.com" at "Oct 4, 97 10:01:43 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 > 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. As someone else said, there is a large difference between a 2.2-STABLE system updated the day after the CD-ROM was released, and one updated yesterday. But how is one to know where they are? We see regular requests from folks trying to help out some other stuck person, asking more detail about what versions they are running. I'd like "uname -r" to return something like "2.2-STABLE-AB" where the AB gets bumped on each and every commit. How to make that happen seems pretty well understood. -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 Sat Oct 4 14:56:26 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id OAA08986 for stable-outgoing; Sat, 4 Oct 1997 14:56:26 -0700 (PDT) Received: from hod.tera.com (hod.tera.com [207.108.223.22]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id OAA08981 for ; Sat, 4 Oct 1997 14:56:21 -0700 (PDT) Received: from athena.tera.com (athena.tera.com [207.108.223.153]) by hod.tera.com (8.7.5/8.7.3) with ESMTP id OAA10500; Sat, 4 Oct 1997 14:55:29 -0700 (PDT) From: Gary Kline Received: (from kline@localhost) by athena.tera.com (8.7.5/8.7.3) id OAA25074; Sat, 4 Oct 1997 14:55:28 -0700 (PDT) Message-Id: <199710042155.OAA25074@athena.tera.com> Subject: Re: CVSUP vs. SNAPS In-Reply-To: <199710041806.MAA23536@rocky.mt.sri.com> from Nate Williams at "Oct 4, 97 12:06:31 pm" To: nate@mt.sri.com (Nate Williams) Date: Sat, 4 Oct 1997 14:55:28 -0700 (PDT) Cc: jkh@time.cdrom.com, imp@village.org, rgrimes@gndrsh.aac.dev.com, andrsn@andrsn.stanford.edu, freebsd-stable@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL23 (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 According to Nate Williams: > > How CVS fits in this is really irrelevant, since the users don't care > for the most part how it's done, and CVS will support whatever we want > it to do. > > There is a *huge* different from a 2.2-stable box that was built slightl > after '2.2-RELEASE', and one built today. It would be nice (and trivial > to do) to have the branch tag change *AFTER* 2.2.5 to say > '2.2.5-stable'. > > But, it doesn't have to happen until *after* the bits are set down for > 2.2.5, so arguments now are only wasting time. We can always argue for > it after 2.2.5 is done. :) :) > > > Nate > > ps. I note that the 'tag' used to denote '2.2-RELEASE' is > "RELENG_2_2_0_RELEASE" and *NOT* "RELENG_2_2_RELEASE", which is what > Jordan is arguing about. Even internally the tags seem to support what > Rod and others are arguing for, we just want to make that information > available to the kernel. > This view wins over Jordon's for the evidence presented in the first paragraph. The CVS//RCS intrinsics have meaning solely to the people who use it--FreeBSD.org in our case. The user-community sees things from a different perspective; and here, as elsewhere, perception is the _only_ thing that counts. gary kline From owner-freebsd-stable Sat Oct 4 18:56:56 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id SAA19001 for stable-outgoing; Sat, 4 Oct 1997 18:56:56 -0700 (PDT) Received: from time.cdrom.com (time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id SAA18996 for ; Sat, 4 Oct 1997 18:56:53 -0700 (PDT) Received: from time.cdrom.com (localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.7/8.6.9) with ESMTP id SAA06137; Sat, 4 Oct 1997 18:55:53 -0700 (PDT) To: FreeBSD cc: stable@FreeBSD.ORG Subject: Re: strptime prototype missing in time.h In-reply-to: Your message of "Sat, 04 Oct 1997 18:24:44 -0300." Date: Sat, 04 Oct 1997 18:55:53 -0700 Message-ID: <6133.876016553@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-stable@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk This isn't quite the right place to report such things (send-pr(1) is the way to go, even for short stuff) but thanks for pointing this out - fixed! Jordan > The subject says it all! > > From owner-freebsd-stable Sat Oct 4 20:08:33 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id UAA21421 for stable-outgoing; Sat, 4 Oct 1997 20:08:33 -0700 (PDT) Received: from obie.softweyr.ml.org ([199.104.124.49]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id UAA21414 for ; Sat, 4 Oct 1997 20:08:27 -0700 (PDT) Received: (from wes@localhost) by obie.softweyr.ml.org (8.7.5/8.6.12) id VAA07177; Sat, 4 Oct 1997 21:13:29 -0600 (MDT) Date: Sat, 4 Oct 1997 21:13:29 -0600 (MDT) Message-Id: <199710050313.VAA07177@obie.softweyr.ml.org> From: Wes Peters To: Jim King CC: stable@freebsd.org Subject: DE21140-AE in 2.2.5 In-Reply-To: <3.0.1.32.19971002102621.009a3790@mail.sstar.com> References: <3.0.1.32.19971002102621.009a3790@mail.sstar.com> Sender: owner-freebsd-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk 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? -- "Where am I, and what am I doing in this handbasket?" Wes Peters Softweyr LLC http://www.xmission.com/~softweyr softweyr@xmission.com