From owner-freebsd-stable Sun Feb 16 13:28:31 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id NAA28396 for stable-outgoing; Sun, 16 Feb 1997 13:28:31 -0800 (PST) Received: from relay.nuxi.com (nuxi.ucdavis.edu [128.120.37.176]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id NAA28071; Sun, 16 Feb 1997 13:20:38 -0800 (PST) Received: from dragon.nuxi.com (reqb-055.ucdavis.edu [128.120.254.55]) by relay.nuxi.com (8.8.4/8.6.12) with ESMTP id NAA03127; Sun, 16 Feb 1997 13:20:44 -0800 (PST) Received: (from obrien@localhost) by dragon.nuxi.com (8.8.5/8.7.3) id VAA08208; Sun, 16 Feb 1997 21:20:31 GMT Message-ID: <19970216132031.XX10822@dragon.nuxi.com> Date: Sun, 16 Feb 1997 13:20:31 -0800 From: obrien@NUXI.com (David O'Brien) To: freebsd-security@freebsd.org, stable@freebsd.org Cc: core@freebsd.org Subject: (fwd) Re: Shell Access X-Mailer: Mutt 0.60_p2-3,5,8-9 Mime-Version: 1.0 X-Disclaimer: Mutt Bites! Organization: The NUXI *BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk This is from CalWeb ISP in Sacramento CA. They were running 2.1-STABLE on the shell account machines. They are now running 2.2-970207-GAMMA. This ISP's resonce to the setlocale vulnerability was to shut off shell accounts for several days (and w/o notice to it's customers). -- forwarded message -- Path: calweb!not-for-mail From: rdugaue@calweb.com (Robert Du Gaue) Newsgroups: calweb.general Subject: Re: Shell Access Date: 7 Feb 1997 15:49:30 GMT Organization: CalWeb Internet Services, Inc. Lines: 19 Message-ID: <5dfiua$j37$1@news.calweb.com> References: <32FADDA2.8FF@calweb.com> NNTP-Posting-Host: web1.calweb.com X-Newsreader: TIN [UNIX 1.3 950824BETA PL0] Xref: calweb calweb.general:634 Steve Phariss (rebo@calweb.com) wrote: : Can we have more details on the shell access??? : : Motd 02/07/97: : : > 02/07/97 Shell logins are disabled until a new security : > release is made available. We appologize : > for the inconvenience. : > : : Any idea how long till access is going to be restored? A new security release for the OS is expected within the next couple of days (rumor has it 'anytime', maybe today). -------------------------------------------------------------------------- Robert Du Gaue - rdugaue@calweb.com http://www.calweb.com President, CalWeb Internet Services Inc. (916) 641-9320 -------------------------------------------------------------------------- -- end of forwarded message -- From owner-freebsd-stable Sun Feb 16 17:01:24 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id RAA10436 for stable-outgoing; Sun, 16 Feb 1997 17:01:24 -0800 (PST) Received: from relay.nuxi.com (nuxi.ucdavis.edu [128.120.37.176]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id QAA10284; Sun, 16 Feb 1997 16:59:00 -0800 (PST) Received: from dragon.nuxi.com ([207.211.82.25]) by relay.nuxi.com (8.8.4/8.6.12) with ESMTP id QAA03837; Sun, 16 Feb 1997 16:59:11 -0800 (PST) Received: (from obrien@localhost) by dragon.nuxi.com (8.8.5/8.7.3) id AAA08697; Mon, 17 Feb 1997 00:58:30 GMT Message-ID: <19970216165828.NN28029@dragon.nuxi.com> Date: Sun, 16 Feb 1997 16:58:28 -0800 From: obrien@NUXI.com (David O'Brien) To: freebsd-security@freebsd.org, stable@freebsd.org Cc: core@freebsd.org Subject: Re: (fwd) Re: Shell Access References: <19970216132031.XX10822@dragon.nuxi.com> X-Mailer: Mutt 0.60_p2-3,5,8-9 Mime-Version: 1.0 X-Disclaimer: Mutt Bites! Organization: The NUXI *BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 In-Reply-To: <19970216132031.XX10822@dragon.nuxi.com>; from David O'Brien on Feb 16, 1997 13:20:31 -0800 Sender: owner-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk David O'Brien writes: > This is from CalWeb ISP in Sacramento CA. They were running 2.1-STABLE > on the shell account machines. They are now running 2.2-970207-GAMMA. > > This ISP's resonce to the setlocale vulnerability was to shut off shell > accounts for several days (and w/o notice to it's customers). Looking at this again, I'm afraid it could be a slant agaist CalWeb. It wasn't. Rather I was just passing along what one ISP felt nessicary to do in responce to things. I've also heard, the accounts were turned for about 24 hours. > -- forwarded message -- > Path: calweb!not-for-mail > From: rdugaue@calweb.com (Robert Du Gaue) > Newsgroups: calweb.general > Subject: Re: Shell Access > Date: 7 Feb 1997 15:49:30 GMT > Organization: CalWeb Internet Services, Inc. > Lines: 19 > Message-ID: <5dfiua$j37$1@news.calweb.com> > References: <32FADDA2.8FF@calweb.com> > NNTP-Posting-Host: web1.calweb.com > X-Newsreader: TIN [UNIX 1.3 950824BETA PL0] > Xref: calweb calweb.general:634 > > Steve Phariss (rebo@calweb.com) wrote: > : Can we have more details on the shell access??? > : > : Motd 02/07/97: > : > : > 02/07/97 Shell logins are disabled until a new security > : > release is made available. We appologize > : > for the inconvenience. > : > > : > : Any idea how long till access is going to be restored? > > A new security release for the OS is expected within the next > couple of days (rumor has it 'anytime', maybe today). > > -------------------------------------------------------------------------- > Robert Du Gaue - rdugaue@calweb.com http://www.calweb.com > President, CalWeb Internet Services Inc. (916) 641-9320 > -------------------------------------------------------------------------- > -- end of forwarded message -- From owner-freebsd-stable Mon Feb 17 05:32:16 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id FAA15421 for stable-outgoing; Mon, 17 Feb 1997 05:32:16 -0800 (PST) Received: from florence.pavilion.net (florence.pavilion.net [194.242.128.25]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id FAA15414 for ; Mon, 17 Feb 1997 05:32:12 -0800 (PST) Received: (from joe@localhost) by florence.pavilion.net (8.8.5/8.8.5) id NAA06897; Mon, 17 Feb 1997 13:31:41 GMT Message-ID: Date: Mon, 17 Feb 1997 13:31:40 +0000 From: joe@pavilion.net (Josef Karthauser) To: freebsd-stable@freebsd.org Subject: cant compile usr.bin/fetch X-Mailer: Mutt 0.58.1 Mime-Version: 1.0 Sender: owner-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hiya, I've just started following the -stable source tree and have pulled down using CVSup. It seems that I'm getting a problem in usr.bin/fetch: ===> usr.bin/fetch cc -O -Wall -c /usr/src/usr.bin/fetch/main.c /usr/src/usr.bin/fetch/main.c: In function `ftpget': /usr/src/usr.bin/fetch/main.c:304: too many arguments to function `ftpLogin' /usr/src/usr.bin/fetch/main.c:307: warning: implicit declaration of function `ftpErrString' /usr/src/usr.bin/fetch/main.c:347: warning: passing arg 3 of `ftpGet' from incompatible pointer type /usr/src/usr.bin/fetch/main.c: In function `ftperr': /usr/src/usr.bin/fetch/main.c:569: warning: initialization makes pointer from integer without a cast *** Error code 1 Am I doing something wrong or is there a problem? Joe. -- Josef Karthauser Technical Manager Email: joe@pavilion.net Pavilion Internet plc. [Tel: +44 1273 607072 Fax: +44 1273 607073] From owner-freebsd-stable Mon Feb 17 06:33:23 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id GAA18084 for stable-outgoing; Mon, 17 Feb 1997 06:33:23 -0800 (PST) Received: from loki.csc.ncsu.edu (loki.csc.ncsu.edu [152.1.61.106]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id GAA18078 for ; Mon, 17 Feb 1997 06:33:19 -0800 (PST) Received: (from fwang2@localhost) by loki.csc.ncsu.edu (8.8.4/EC02Jan97) id JAA09227 for stable@freebsd.org; Mon, 17 Feb 1997 09:33:12 -0500 (EST) From: "Feiyi Wang" Message-Id: <9702170933.ZM9225@eos.ncsu.edu> Date: Mon, 17 Feb 1997 09:33:08 -0500 X-Mailer: Z-Mail (3.2.1 10oct95) To: stable@freebsd.org Subject: help with 2.1.5 R Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi, folks, I am new in FreeBSD, I am now in hurry to looking for FreeBSD 2.1.5 Release, But It seems there is only 2.1.6 exist in all ftp sites. Also I am not clear what is relationship of 2.1.5 Release and stable version (even after FAQ) and how to install a stable one, the directory structure is quite different from 2.1.6 Release. If anybody can help, I really appreciate it. -- Feiyi From owner-freebsd-stable Mon Feb 17 07:29:09 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id HAA21673 for stable-outgoing; Mon, 17 Feb 1997 07:29:09 -0800 (PST) Received: from solar.os.com (craigs@solar.os.com [199.232.136.65]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id HAA21663 for ; Mon, 17 Feb 1997 07:29:06 -0800 (PST) Received: (from craigs@localhost) by solar.os.com (8.7/8.7.0) id KAA15640; Mon, 17 Feb 1997 10:27:57 -0500 Date: Mon, 17 Feb 1997 10:27:57 -0500 From: Craig Shrimpton Subject: Re: cant compile usr.bin/fetch To: Josef Karthauser cc: freebsd-stable@freebsd.org In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Mon, 17 Feb 1997, Josef Karthauser wrote: > Hiya, > > I've just started following the -stable source tree and have pulled down > using CVSup. It seems that I'm getting a problem in usr.bin/fetch: > > ===> usr.bin/fetch > cc -O -Wall -c /usr/src/usr.bin/fetch/main.c > /usr/src/usr.bin/fetch/main.c: In function `ftpget': > /usr/src/usr.bin/fetch/main.c:304: too many arguments to function `ftpLogin' > /usr/src/usr.bin/fetch/main.c:307: warning: implicit declaration of function `ftpErrString' > /usr/src/usr.bin/fetch/main.c:347: warning: passing arg 3 of `ftpGet' from incompatible pointer type > /usr/src/usr.bin/fetch/main.c: In function `ftperr': > /usr/src/usr.bin/fetch/main.c:569: warning: initialization makes pointer from integer without a cast > *** Error code 1 > > There's a new header file. Do a make includes and then remake the libs. Or, if you have a few hours to kill, do a make world. -Craig +-----------------------------------+------------------------------------+ | Craig Shrimpton | e-mail: craigs@os.com | | Orbit Systems | information: info@os.com | | Worcester, MA 508.753.8776 | http://www.os.com/ | +-----------------------------------+------------------------------------+ From owner-freebsd-stable Mon Feb 17 09:54:14 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id JAA01068 for stable-outgoing; Mon, 17 Feb 1997 09:54:14 -0800 (PST) Received: from mailhost.anasazi.com (mailhost.anasazi.com [138.113.128.2]) by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id JAA01048 for ; Mon, 17 Feb 1997 09:54:07 -0800 (PST) Received: from chad.anasazi.com by mailhost.anasazi.com (5.65/3.7) id AA17943; Mon, 17 Feb 97 10:53:29 -0700 Received: by chad.anasazi.com (5.65/3.7) id AA02197; Mon, 17 Feb 97 10:53:27 -0700 From: chad@anasazi.com (Chad R. Larson) Message-Id: <9702171753.AA02197@chad.anasazi.com> Subject: Re: help with 2.1.5 R To: fwang2@eos.ncsu.edu (Feiyi Wang) Date: Mon, 17 Feb 1997 10:53:25 -0700 (MST) Cc: stable@freebsd.org In-Reply-To: <9702170933.ZM9225@eos.ncsu.edu> from "Feiyi Wang" at Feb 17, 97 09:33:08 am Reply-To: chad@anasazi.com X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > Hi, folks, > I am new in FreeBSD, I am now in hurry to looking for FreeBSD 2.1.5 > Release, But It seems there is only 2.1.6 exist in all ftp sites. > Also I am not clear what is relationship of 2.1.5 Release and stable > version (even after FAQ) and how to install a stable one, the > directory structure is quite different from 2.1.6 Release. 2.1.5-RELEASE was supposed to be the last release down the 2.1 tree, but Jordan found some of what he termed "anoying" bugs in the installation process and rolled a 2.1.6 in about November. The -stable SUP tree started with 2.1.6 and has any bug fixes or minor improvements that are well tested (hence "stable"). When I first went against the stable tree, it took me to 2.1.6.1-RELEASE. Lately, there was a fairly large security hole uncovered in the POSIX locale code. The fix for that resulted in 2.1.7, which is what you'll get running SUP against the -stable tree now. (By the way, the 2.1.6 you find on the ftp mirror sites should be shot in the head by now). -crl -- Chad R. Larson (CRL22) Brother, can you paradigm? 602-870-3330 chad@anasazi.com chad@anasaz.UUCP chad@dcfinc.com Anasazi, Inc. - 7500 North Dreamy Draw Drive, Suite 120, Phoenix, Az 85020 From owner-freebsd-stable Mon Feb 17 14:32:43 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id OAA20912 for stable-outgoing; Mon, 17 Feb 1997 14:32:43 -0800 (PST) Received: from kirk.edmweb.com (kirk.edmweb.com [204.244.190.1]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id OAA20907 for ; Mon, 17 Feb 1997 14:32:41 -0800 (PST) Received: from bitbucket (bluesmoke.edmweb.com [204.244.190.8]) by kirk.edmweb.com (8.8.5/8.7.3) with ESMTP id OAA14961; Mon, 17 Feb 1997 14:32:28 -0800 (PST) Received: from localhost by bitbucket with smtp id m0vwbbx-000CEdC (Debian Smail-3.2 1996-Jul-4 #2); Mon, 17 Feb 1997 14:32:17 -0800 (PST) Date: Mon, 17 Feb 1997 14:32:15 -0800 (PST) From: Steve Reid X-Sender: steve@bluesmoke Reply-To: Steve Reid To: "Chad R. Larson" cc: stable@freebsd.org Subject: Re: help with 2.1.5 R In-Reply-To: <9702171753.AA02197@chad.anasazi.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > (By the way, the 2.1.6 you find on the ftp mirror sites should be > shot in the head by now). Looks like it has, at least on some mirrors. On ftp.freebsd.org (aka wcarchive) the pub/FreeBSD/2.1.6-RELEASE directory has been chmod'ed 000. But there is no 2.1.7-RELEASE directory... It seems to be only on freefall.freebsd.org. From owner-freebsd-stable Mon Feb 17 16:38:53 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id QAA28884 for stable-outgoing; Mon, 17 Feb 1997 16:38:53 -0800 (PST) Received: from time.cdrom.com (time.cdrom.com [204.216.27.226]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id QAA28878 for ; Mon, 17 Feb 1997 16:38:43 -0800 (PST) Received: from time.cdrom.com (localhost [127.0.0.1]) by time.cdrom.com (8.8.5/8.6.9) with ESMTP id QAA28288; Mon, 17 Feb 1997 16:37:47 -0800 (PST) To: Steve Reid cc: "Chad R. Larson" , stable@freebsd.org Subject: Re: help with 2.1.5 R In-reply-to: Your message of "Mon, 17 Feb 1997 14:32:15 PST." Date: Mon, 17 Feb 1997 16:37:47 -0800 Message-ID: <28284.856226267@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > Looks like it has, at least on some mirrors. On ftp.freebsd.org (aka > wcarchive) the pub/FreeBSD/2.1.6-RELEASE directory has been chmod'ed > 000. But there is no 2.1.7-RELEASE directory... It seems to be only on > freefall.freebsd.org. 2.1.7 is not *quite* ready yet, though I expect to have a release build later this evening which we can go with (and will show up in the proper location on ftp.freebsd.org). What you see there on freefall were just test bits for my own use. Watch the -announcement list for details. Jordan From owner-freebsd-stable Mon Feb 17 18:20:28 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id SAA04511 for stable-outgoing; Mon, 17 Feb 1997 18:20:28 -0800 (PST) Received: from mailhost.anasazi.com (mailhost.anasazi.com [138.113.128.2]) by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id SAA04504 for ; Mon, 17 Feb 1997 18:20:23 -0800 (PST) Received: from chad.anasazi.com by mailhost.anasazi.com (5.65/3.7) id AA04573; Mon, 17 Feb 97 19:19:47 -0700 Received: by chad.anasazi.com (5.65/3.7) id AA02973; Mon, 17 Feb 97 19:19:45 -0700 From: chad@anasazi.com (Chad R. Larson) Message-Id: <9702180219.AA02973@chad.anasazi.com> Subject: stable migration path To: freebsd-stable@freebsd.org Date: Mon, 17 Feb 1997 19:19:44 -0700 (MST) Reply-To: chad@anasazi.com X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I've got a couple of machines here that are using SUP to track the stable world (and now call themselves 2.1.7). I just loaded up another one with 2.2-GAMMA. Should it track the -current tree? What will be the migration plan as -stable becomes 2.2 and -current becomes 3.0? -crl -- Chad R. Larson (CRL22) Brother, can you paradigm? 602-870-3330 chad@anasazi.com chad@anasaz.UUCP chad@dcfinc.com Anasazi, Inc. - 7500 North Dreamy Draw Drive, Suite 120, Phoenix, Az 85020 From owner-freebsd-stable Mon Feb 17 20:22:20 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id UAA14201 for stable-outgoing; Mon, 17 Feb 1997 20:22:20 -0800 (PST) Received: from eel.dataplex.net (eel.dataplex.net [208.2.87.2]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id UAA14178 for ; Mon, 17 Feb 1997 20:22:07 -0800 (PST) Received: from [208.2.87.3] (shrimp [208.2.87.3]) by eel.dataplex.net (8.7.5/8.6.9) with ESMTP id WAA20116; Mon, 17 Feb 1997 22:21:58 -0600 (CST) X-Sender: rkw@mail.dataplex.net Message-Id: In-Reply-To: <9702180219.AA02973@chad.anasazi.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Mon, 17 Feb 1997 22:20:05 -0600 To: chad@anasazi.com From: Richard Wackerbarth Subject: Re: stable migration path Cc: stable@freebsd.org Sender: owner-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >I've got a couple of machines here that are using SUP to track the >stable world (and now call themselves 2.1.7). I just loaded up another >one with 2.2-GAMMA. Should it track the -current tree? > >What will be the migration plan as -stable becomes 2.2 and -current >becomes 3.0? I hope that they will create 2.1 and 2.2 targets so that you can switch to those long before "stable" changes. That way, YOU will have control over the time that you switch. After all, that 2.2 machine won't be changing just because someone decides to bless 2.2 and call it "stable". "current" will always basically be un-numbered because 3.0 has not been split off of the trunk yet. And when it does, "current" will become 3.1 or 4.0 or whatever. From owner-freebsd-stable Mon Feb 17 20:52:41 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id UAA16474 for stable-outgoing; Mon, 17 Feb 1997 20:52:41 -0800 (PST) Received: from time.cdrom.com (time.cdrom.com [204.216.27.226]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id UAA16468 for ; Mon, 17 Feb 1997 20:52:39 -0800 (PST) Received: from time.cdrom.com (localhost [127.0.0.1]) by time.cdrom.com (8.8.5/8.6.9) with ESMTP id UAA29406; Mon, 17 Feb 1997 20:52:32 -0800 (PST) To: chad@anasazi.com cc: freebsd-stable@freebsd.org Subject: Re: stable migration path In-reply-to: Your message of "Mon, 17 Feb 1997 19:19:44 MST." <9702180219.AA02973@chad.anasazi.com> Date: Mon, 17 Feb 1997 20:52:32 -0800 Message-ID: <29403.856241552@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > I've got a couple of machines here that are using SUP to track the > stable world (and now call themselves 2.1.7). I just loaded up another > one with 2.2-GAMMA. Should it track the -current tree? No, it should track the RELENG_2_2 tag. > What will be the migration plan as -stable becomes 2.2 and -current > becomes 3.0? -stable won't become 2.2 until 2.2.x (where x is at least 1 and probably more like 2 or 3). At that time, we'll announce cut-over plans for folks after we've tested the upgrade picture at that time using the latest 2.1.x and 2.2.x bits. Jordan From owner-freebsd-stable Tue Feb 18 02:37:25 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id CAA25151 for stable-outgoing; Tue, 18 Feb 1997 02:37:25 -0800 (PST) Received: from florence.pavilion.net (florence.pavilion.net [194.242.128.25]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id CAA25144 for ; Tue, 18 Feb 1997 02:37:19 -0800 (PST) Received: (from joe@localhost) by florence.pavilion.net (8.8.5/8.8.5) id KAA17639 for freebsd-stable@freebsd.org; Tue, 18 Feb 1997 10:36:46 GMT Resent-Message-Id: <199702181036.KAA17639@florence.pavilion.net> Received: from harry.sales.pavilion.net (harry.sales.pavilion.net [194.242.128.46]) by florence.pavilion.net (8.8.5/8.8.5) with SMTP id KAA16156 for ; Tue, 18 Feb 1997 10:00:27 GMT Date: Tue, 18 Feb 1997 10:00:27 GMT Message-Id: <1.5.4.16.19970218100300.368f2b2a@mailhost.pavilion.co.uk> X-Sender: pavilion-sandra@mailhost.pavilion.co.uk X-Mailer: Windows Eudora Light Version 1.5.4 (16) Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" To: hostmaster@pavilion.net From: Sandra Goddard Subject: alias for domain Resent-From: joe@pavilion.net Resent-Date: Tue, 18 Feb 1997 10:36:46 +0000 Resent-To: freebsd-stable@freebsd.org Sender: owner-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hello Whoever gets this !! There is a domain name being registered today for digital-trust.org.uk. Please set up an alias on this domain when it has been completed. The alias to be: info@digital-trust.org.uk to be delivered to dwilcox@pavilion.co.uk Cheers S. ---------------------------------------- Sandra Goddard Pavilion Internet plc 24 Old Steine, Brighton BN1 1EL Tel: (01273) 607072 Fax: (01273) 607073 ---------------------------------------- From owner-freebsd-stable Tue Feb 18 02:41:40 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id CAA25287 for stable-outgoing; Tue, 18 Feb 1997 02:41:40 -0800 (PST) Received: from florence.pavilion.net (florence.pavilion.net [194.242.128.25]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id CAA25280 for ; Tue, 18 Feb 1997 02:41:29 -0800 (PST) Received: (from joe@localhost) by florence.pavilion.net (8.8.5/8.8.5) id KAA17760; Tue, 18 Feb 1997 10:40:55 GMT Message-ID: Date: Tue, 18 Feb 1997 10:40:55 +0000 From: joe@pavilion.net (Josef Karthauser) To: freebsd-stable@freebsd.org Subject: oops sorry, and a query about perl X-Mailer: Mutt 0.58.1 Mime-Version: 1.0 Sender: owner-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi, Oops I've just forwarded a message about a mail alias to this list, this is _not_ a good week. Now for what I really wanted to ask. How can I get the stable tree to not install perl? We've got version 5 on this system and it keeps getting stomped on by the version 4 contained in stable. Any help would be much appreciated. Joe. -- Josef Karthauser Technical Manager Email: joe@pavilion.net Pavilion Internet plc. [Tel: +44 1273 607072 Fax: +44 1273 607073] From owner-freebsd-stable Tue Feb 18 03:16:48 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id DAA26877 for stable-outgoing; Tue, 18 Feb 1997 03:16:48 -0800 (PST) Received: from time.cdrom.com (time.cdrom.com [204.216.27.226]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id DAA26868 for ; Tue, 18 Feb 1997 03:16:37 -0800 (PST) Received: from time.cdrom.com (localhost [127.0.0.1]) by time.cdrom.com (8.8.5/8.6.9) with ESMTP id DAA03225; Tue, 18 Feb 1997 03:15:59 -0800 (PST) To: joe@pavilion.net (Josef Karthauser) cc: freebsd-stable@freebsd.org Subject: Re: oops sorry, and a query about perl In-reply-to: Your message of "Tue, 18 Feb 1997 10:40:55 GMT." Date: Tue, 18 Feb 1997 03:15:59 -0800 Message-ID: <3221.856264559@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > Now for what I really wanted to ask. How can I get the stable > tree to not install perl? We've got version 5 on this system > and it keeps getting stomped on by the version 4 contained in > stable. Not quite an answer, but a question - why are you installing perl5 in /usr/bin? If you use the ports version, it goes into /usr/local/bin and a generation of FreeBSD perl programmers have sort of made that into a full convention for perl4 vs perl5. Jordan From owner-freebsd-stable Tue Feb 18 13:08:56 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id NAA01556 for stable-outgoing; Tue, 18 Feb 1997 13:08:56 -0800 (PST) Received: from Central.KeyWest.MPGN.COM (root@Central.TanSoft.COM [206.175.4.1]) by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id NAA01551 for ; Tue, 18 Feb 1997 13:08:51 -0800 (PST) Received: from devious.Tansoft.com (Devious.TanSoft.COM [206.175.4.10]) by Central.KeyWest.MPGN.COM (8.6.9/8.6.9) with SMTP id QAA28289 for ; Tue, 18 Feb 1997 16:08:44 -0500 Message-Id: <3.0.32.19970218160844.007e69b0@central.TanSoft.COM> X-Sender: rwm@central.TanSoft.COM X-Mailer: Windows Eudora Pro Version 3.0 (32) Date: Tue, 18 Feb 1997 16:08:45 -0500 To: stable@freebsd.org From: Rob Miracle Subject: Problems with 3COM Etherlink III PCMCIA card Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk We wanted to install FreeBSD on a laptop, so I get the list of network cards and see that the 3Com is supported. I download the FreeBSD 2.2-Gamma floppy, and try to install it. It doesn't see the card at all, yet it passes its DOS diagnostics. Any ideas? Thanks Rob From owner-freebsd-stable Tue Feb 18 13:46:11 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id NAA03497 for stable-outgoing; Tue, 18 Feb 1997 13:46:11 -0800 (PST) Received: from rocky.mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id NAA03488 for ; Tue, 18 Feb 1997 13:46:07 -0800 (PST) Received: (from nate@localhost) by rocky.mt.sri.com (8.7.5/8.7.3) id OAA19045; Tue, 18 Feb 1997 14:45:58 -0700 (MST) Date: Tue, 18 Feb 1997 14:45:58 -0700 (MST) Message-Id: <199702182145.OAA19045@rocky.mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Rob Miracle Cc: stable@freebsd.org Subject: Re: Problems with 3COM Etherlink III PCMCIA card In-Reply-To: <3.0.32.19970218160844.007e69b0@central.TanSoft.COM> References: <3.0.32.19970218160844.007e69b0@central.TanSoft.COM> Sender: owner-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > We wanted to install FreeBSD on a laptop, so I get the list of network > cards and see that the 3Com is supported. I download the FreeBSD 2.2-Gamma > floppy, and try to install it. It doesn't see the card at all, yet it > passes its DOS diagnostics. Any ideas? Do the DOS parameters match what the FreeBSD drivers expects? Nate From owner-freebsd-stable Tue Feb 18 13:51:39 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id NAA03735 for stable-outgoing; Tue, 18 Feb 1997 13:51:39 -0800 (PST) Received: from Central.KeyWest.MPGN.COM (root@Central.TanSoft.COM [206.175.4.1]) by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id NAA03729 for ; Tue, 18 Feb 1997 13:51:35 -0800 (PST) Received: from devious.Tansoft.com (Devious.TanSoft.COM [206.175.4.10]) by Central.KeyWest.MPGN.COM (8.6.9/8.6.9) with SMTP id QAA29254; Tue, 18 Feb 1997 16:51:25 -0500 Message-Id: <3.0.32.19970218165125.008013a0@central.TanSoft.COM> X-Sender: rwm@central.TanSoft.COM X-Mailer: Windows Eudora Pro Version 3.0 (32) Date: Tue, 18 Feb 1997 16:51:26 -0500 To: Nate Williams From: Rob Miracle Subject: Re: Problems with 3COM Etherlink III PCMCIA card Cc: stable@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Yes. The card specificlly is a 3C589D. Thanks At 02:45 PM 2/18/97 -0700, you wrote: >> We wanted to install FreeBSD on a laptop, so I get the list of network >> cards and see that the 3Com is supported. I download the FreeBSD 2.2-Gamma >> floppy, and try to install it. It doesn't see the card at all, yet it >> passes its DOS diagnostics. Any ideas? > >Do the DOS parameters match what the FreeBSD drivers expects? > > >Nate > > From owner-freebsd-stable Tue Feb 18 13:56:15 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id NAA04188 for stable-outgoing; Tue, 18 Feb 1997 13:56:15 -0800 (PST) Received: from rocky.mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id NAA04177 for ; Tue, 18 Feb 1997 13:56:11 -0800 (PST) Received: (from nate@localhost) by rocky.mt.sri.com (8.7.5/8.7.3) id OAA19063; Tue, 18 Feb 1997 14:55:50 -0700 (MST) Date: Tue, 18 Feb 1997 14:55:50 -0700 (MST) Message-Id: <199702182155.OAA19063@rocky.mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Rob Miracle Cc: Nate Williams , stable@freebsd.org Subject: Re: Problems with 3COM Etherlink III PCMCIA card In-Reply-To: <3.0.32.19970218165125.008013a0@central.TanSoft.COM> References: <3.0.32.19970218165125.008013a0@central.TanSoft.COM> Sender: owner-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > Yes. The card specificlly is a 3C589D. > > Thanks Hmm, I haven't yet heard a 'working' report from a 3C589D, so I don't know if the 'zp' driver works with it. I have heard that the ep driver works, but it's a nightmare to setup right now (my fault). What are the parameters that *DOS* (w/out card-services running) states that the card is configured for? Nate From owner-freebsd-stable Tue Feb 18 16:37:15 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id QAA14232 for stable-outgoing; Tue, 18 Feb 1997 16:37:15 -0800 (PST) Received: from mail.ptd.net (srv1.ptd.net [204.186.0.131]) by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id QAA14227 for ; Tue, 18 Feb 1997 16:37:13 -0800 (PST) Received: (qmail 9417 invoked from network); 19 Feb 1997 00:31:37 -0000 Received: from cs4-8.pot.ptd.net (204.186.34.56) by postoffice.ptd.net with SMTP; 19 Feb 1997 00:31:37 -0000 Received: by cs4-8.pot.ptd.net with Microsoft Mail id <01BC1DD3.189EDA60@cs4-8.pot.ptd.net>; Tue, 18 Feb 1997 19:36:54 -0500 Message-ID: <01BC1DD3.189EDA60@cs4-8.pot.ptd.net> From: Nick Folino To: "'FreeBSD-Stable'" Subject: Problems with freebsd stable Date: Tue, 18 Feb 1997 19:36:39 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by freefall.freebsd.org id QAA14228 Sender: owner-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I'm running FreeBSD 2.1.5R. I just sup'd the complete -stable src and can't seem to get it to compile. This is what's been happening: If I run a make world it stop's and tells me it doesn't know how to make cleandir...so I do a make world -DNOCLEANDIR..that solves the first problem.. then it dies trying to install lib\libmd\md2.3 which it can't find, problem is there's no obj....so i do a make obj....now i can get further but now cc dies with a sig 11 or it just dumps core randomly..... Can anyone help me get this going? Nick From owner-freebsd-stable Wed Feb 19 01:43:29 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id BAA15354 for stable-outgoing; Wed, 19 Feb 1997 01:43:29 -0800 (PST) Received: from florence.pavilion.net (florence.pavilion.net [194.242.128.25]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id BAA15349 for ; Wed, 19 Feb 1997 01:43:25 -0800 (PST) Received: (from joe@localhost) by florence.pavilion.net (8.8.5/8.8.5) id JAA25532; Wed, 19 Feb 1997 09:42:52 GMT Message-ID: Date: Wed, 19 Feb 1997 09:42:52 +0000 From: joe@pavilion.net (Josef Karthauser) To: freebsd-stable@freebsd.org Subject: migrating stable onto my machines X-Mailer: Mutt 0.58.1 Mime-Version: 1.0 Sender: owner-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi, Has anybody got a good method for upgrading machines on a network... let me clarify. We've got five or six machines all running freebsd-stable's of one variety or other. One of them now tracks the -stable tree, but I want to be able to update the others without them theirselves having to also have a copy of the source tree on them. I guess a sort of remote make install would work. Clues recieved on a postcard will be placed into hat and drawn next week for a free pint of beer. :) Joe p.s. I'd prefer a reply by e-mail however ;) -- Josef Karthauser Technical Manager Email: joe@pavilion.net Pavilion Internet plc. [Tel: +44 1273 607072 Fax: +44 1273 607073] From owner-freebsd-stable Wed Feb 19 06:29:01 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id GAA25301 for stable-outgoing; Wed, 19 Feb 1997 06:29:01 -0800 (PST) Received: from stingray.ivision.co.uk (stingray.ivision.co.uk [194.154.62.8]) by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id GAA25296 for ; Wed, 19 Feb 1997 06:28:52 -0800 (PST) Received: from stingray.ivision.co.uk [194.154.62.8] by stingray.ivision.co.uk with smtp (Exim 0.53 #1) id E0vxD0V-0005pQ-00; Wed, 19 Feb 1997 14:28:27 +0000 Date: Wed, 19 Feb 1997 14:28:27 +0000 (GMT) From: Jasper Wallace To: Josef Karthauser cc: freebsd-stable@freebsd.org Subject: Re: migrating stable onto my machines In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Wed, 19 Feb 1997, Josef Karthauser wrote: > Hi, > > Has anybody got a good method for upgrading machines on > a network... let me clarify. We've got five or six machines > all running freebsd-stable's of one variety or other. One of > them now tracks the -stable tree, but I want to be able to > update the others without them theirselves having to also have > a copy of the source tree on them. I guess a sort of remote > make install would work. I've got to do this on our network in the next week or so, and my curent thoughts are: nfs mounted /usr from the machine tracking -stable or rdist > Clues recieved on a postcard will be placed into hat and > drawn next week for a free pint of beer. :) any jobs going down there, my contract runs out in 3 weeks. (pavillion are in surry right? I'm not confusing you with someone in southampton?) -- Jasper Wallace-Internet Vision | Caving-Acorn-RiscBSD-Chocolate-Banks-Fish My opinions != IVisions's | PovRay-FVWM-Perl-C-Mono-Food-Wired-? E-Mail:jasper@ivision.co.uk | This is the Internet, untamed and free, Tel: +44 171 589 4500 (work) | Where you can be anything you want to be From owner-freebsd-stable Wed Feb 19 20:47:29 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id UAA16309 for stable-outgoing; Wed, 19 Feb 1997 20:47:29 -0800 (PST) Received: from androcles.com (androcles.com [204.57.240.10]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id UAA16304 for ; Wed, 19 Feb 1997 20:47:25 -0800 (PST) Received: (from dhh@localhost) by androcles.com (8.7.6/8.6.12) id UAA04588; Wed, 19 Feb 1997 20:47:13 -0800 (PST) Message-ID: X-Mailer: XFMail 1.0 [p0] on FreeBSD Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: Date: Wed, 19 Feb 1997 20:46:48 -0800 (PST) From: "Duane H. Hesser" To: (Josef Karthauser) Subject: RE: migrating stable onto my machines Cc: freebsd-stable@freebsd.org Sender: owner-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk How about 'rdist' On 19-Feb-97 Josef Karthauser wrote: >Hi, > >Has anybody got a good method for upgrading machines on >a network... let me clarify. We've got five or six machines >all running freebsd-stable's of one variety or other. One of >them now tracks the -stable tree, but I want to be able to >update the others without them theirselves having to also have >a copy of the source tree on them. I guess a sort of remote >make install would work. > >Clues recieved on a postcard will be placed into hat and >drawn next week for a free pint of beer. :) > >Joe > >p.s. I'd prefer a reply by e-mail however ;) >-- >Josef Karthauser >Technical Manager Email: joe@pavilion.net >Pavilion Internet plc. [Tel: +44 1273 607072 Fax: +44 1273 607073] Duane H. Hesser dhh@androcles.com From owner-freebsd-stable Thu Feb 20 04:27:05 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id EAA09311 for stable-outgoing; Thu, 20 Feb 1997 04:27:05 -0800 (PST) Received: from florence.pavilion.net (florence.pavilion.net [194.242.128.25]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id EAA09302 for ; Thu, 20 Feb 1997 04:27:01 -0800 (PST) Received: (from joe@localhost) by florence.pavilion.net (8.8.5/8.8.5) id MAA11401; Thu, 20 Feb 1997 12:26:28 GMT Message-ID: Date: Thu, 20 Feb 1997 12:26:28 +0000 From: joe@pavilion.net (Josef Karthauser) To: freebsd-stable@freebsd.org Subject: gzip: stdout: Broken pipe X-Mailer: Mutt 0.58.1 Mime-Version: 1.0 Sender: owner-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hiya, Wow, what a lot of questions I'm asking this week. I've started getting errors during gunzips: core# pkg_add ghostscript-2.6.2.tgz gzip: stdout: Broken pipe tar: child returned status 1 ^CTar extract of /tmp/ghostscript-2.6.2.tgz failed! Unable to extract `/tmp/ghostscript-2.6.2.tgz'! I'm not sure when they started. It seems to work properly from the serial console if I log on as root, but breaks if I su from an xterm. I'm running bash as my main shell, and root's is the default csh. Has anybody else had this problem? Joe -- Josef Karthauser Technical Manager Email: joe@pavilion.net Pavilion Internet plc. [Tel: +44 1273 607072 Fax: +44 1273 607073] From owner-freebsd-stable Thu Feb 20 08:20:29 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id IAA20165 for stable-outgoing; Thu, 20 Feb 1997 08:20:29 -0800 (PST) Received: from stingray.ivision.co.uk (stingray.ivision.co.uk [194.154.62.8]) by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id IAA20153 for ; Thu, 20 Feb 1997 08:20:19 -0800 (PST) Received: from stingray.ivision.co.uk [194.154.62.8] by stingray.ivision.co.uk with smtp (Exim 0.53 #1) id E0vxbE7-0001dC-00; Thu, 20 Feb 1997 16:20:07 +0000 Date: Thu, 20 Feb 1997 16:20:07 +0000 (GMT) From: Jasper Wallace To: freebsd-stable@freebsd.org Subject: 2.1.7-RELEASE Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk the 2.1.7-RELEASE directory has appeared on the ftp site - but there hasn't been an announcement on freebsd-announce. I assume it will be appearing soon and it's safe to use the 2.1.7-RELEASE at the moment? -- Jasper Wallace-Internet Vision | Caving-Acorn-RiscBSD-Chocolate-Banks-Fish My opinions != IVisions's | PovRay-FVWM-Perl-C-Mono-Food-Wired-? E-Mail:jasper@ivision.co.uk | This is the Internet, untamed and free, Tel: +44 171 589 4500 (work) | Where you can be anything you want to be From owner-freebsd-stable Thu Feb 20 09:05:41 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id JAA23271 for stable-outgoing; Thu, 20 Feb 1997 09:05:41 -0800 (PST) Received: from eel.dataplex.net (eel.dataplex.net [208.2.87.2]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id JAA23265 for ; Thu, 20 Feb 1997 09:05:38 -0800 (PST) Received: from [204.69.236.50] (GATEWAY.SKIPSTONE.COM [198.214.10.129]) by eel.dataplex.net (8.7.5/8.6.9) with SMTP id LAA04533; Thu, 20 Feb 1997 11:05:32 -0600 (CST) Date: 20 Feb 97 11:06:10 -0600 Subject: Re: 2.1.7-RELEASE From: "Richard Wackerbarth" To: freebsd-stable@freebsd.org, "Jasper Wallace" X-Mailer: Cyberdog/2.0a2 MIME-Version: 1.0 Message-Id: Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Thu, Feb 20, 1997 10:20 AM, Jasper Wallace wrote: > >the 2.1.7-RELEASE directory has appeared on the ftp site - but there hasn't >been an announcement on freebsd-announce. I assume it will be appearing soon >and it's safe to use the 2.1.7-RELEASE at the moment? Some channels take a little longer than others. If the permissions allow you in, Jordan has finished his testing. Last night he said that the CD was burned. I therefore assume it is a go. From owner-freebsd-stable Thu Feb 20 09:10:24 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id JAA23606 for stable-outgoing; Thu, 20 Feb 1997 09:10:24 -0800 (PST) Received: from superior.truenorth.org (ppp010-sm2.sirius.com [205.134.231.10]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id JAA23545 for ; Thu, 20 Feb 1997 09:09:30 -0800 (PST) Received: (from jgrosch@localhost) by superior.truenorth.org (8.8.3/8.7.3) id JAA10567; Thu, 20 Feb 1997 09:08:04 -0800 (PST) From: Josef Grosch Message-Id: <199702201708.JAA10567@superior.truenorth.org> Subject: Re: 2.1.7-RELEASE In-Reply-To: from Jasper Wallace at "Feb 20, 97 04:20:07 pm" To: jasper@ivision.co.uk (Jasper Wallace) Date: Thu, 20 Feb 1997 09:07:51 -0800 (PST) Cc: freebsd-stable@freebsd.org Reply-To: jgrosch@sirius.com X-Mailer: ELM [version 2.4ME+ PL28 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > >the 2.1.7-RELEASE directory has appeared on the ftp site - but there hasn't >been an announcement on freebsd-announce. I assume it will be appearing soon >and it's safe to use the 2.1.7-RELEASE at the moment? > Jasper, Jordan sent out an announcement this morning. I could send you a copy if you need one. Josef -- Josef Grosch | Laugh while you can, monkey boy ! | FreeBSD 2.1.6 jgrosch@sirius.com | - John Warfin - | UNIX for the masses From owner-freebsd-stable Thu Feb 20 09:31:15 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id JAA25080 for stable-outgoing; Thu, 20 Feb 1997 09:31:15 -0800 (PST) Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id JAA25068 for ; Thu, 20 Feb 1997 09:31:12 -0800 (PST) Received: from time.cdrom.com (jkh@localhost [127.0.0.1]) by time.cdrom.com (8.8.5/8.6.9) with ESMTP id JAA03466; Thu, 20 Feb 1997 09:30:39 -0800 (PST) To: Jasper Wallace cc: freebsd-stable@FreeBSD.ORG Subject: Re: 2.1.7-RELEASE In-reply-to: Your message of "Thu, 20 Feb 1997 16:20:07 GMT." Date: Thu, 20 Feb 1997 09:30:37 -0800 Message-ID: <3462.856459837@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-stable@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > the 2.1.7-RELEASE directory has appeared on the ftp site - but there hasn't > been an announcement on freebsd-announce. I assume it will be appearing soon > and it's safe to use the 2.1.7-RELEASE at the moment? Yes, an announcement was sent out (albeit with an incorrect core team and developer roster - D'oh!). It's safe, dive in! Jordan From owner-freebsd-stable Thu Feb 20 15:27:47 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id PAA15114 for stable-outgoing; Thu, 20 Feb 1997 15:27:47 -0800 (PST) Received: from who.cdrom.com (who.cdrom.com [204.216.27.3]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id PAA15102 for ; Thu, 20 Feb 1997 15:27:44 -0800 (PST) Received: from kachina.jetcafe.org (jetcafe.org [207.155.21.2]) by who.cdrom.com (8.7.5/8.6.11) with ESMTP id OAA25708 for ; Thu, 20 Feb 1997 14:59:36 -0800 (PST) Received: from [127.0.0.1] ([127.0.0.1]) by kachina.jetcafe.org (8.7.5/8.7.3) with SMTP id OAA24626 for ; Thu, 20 Feb 1997 14:59:34 -0800 (PST) Message-Id: <199702202259.OAA24626@kachina.jetcafe.org> X-Authentication-Warning: kachina.jetcafe.org: Host [127.0.0.1] didn't use HELO protocol To: freebsd-stable@freebsd.org Subject: Re: 2.1.7-RELEASE Date: Thu, 20 Feb 1997 14:59:33 -0800 From: Dave Hayes Sender: owner-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Is there an expected date for the RELENG_2_1 branch (yes I am now using CVSup) to be stable enough to do a make world? ------ Dave Hayes - Altadena CA, USA - dave@jetcafe.org Freedom Knight of Usenet - http://www.jetcafe.org/~dave/usenet A great deal of thought is only a substitute for the thoughts which the individual would really find useful at the time. From owner-freebsd-stable Thu Feb 20 17:02:43 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id RAA22392 for stable-outgoing; Thu, 20 Feb 1997 17:02:43 -0800 (PST) Received: from who.cdrom.com (who.cdrom.com [204.216.27.3]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id RAA22352 for ; Thu, 20 Feb 1997 17:02:33 -0800 (PST) Received: from root.com (implode.root.com [198.145.90.17]) by who.cdrom.com (8.7.5/8.6.11) with ESMTP id JAA24457 for ; Thu, 20 Feb 1997 09:35:51 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by root.com (8.8.5/8.6.5) with SMTP id JAA00828; Thu, 20 Feb 1997 09:36:18 -0800 (PST) Message-Id: <199702201736.JAA00828@root.com> X-Authentication-Warning: implode.root.com: localhost [127.0.0.1] didn't use HELO protocol To: Jasper Wallace cc: freebsd-stable@freebsd.org Subject: Re: 2.1.7-RELEASE In-reply-to: Your message of "Thu, 20 Feb 1997 16:20:07 GMT." From: David Greenman Reply-To: dg@root.com Date: Thu, 20 Feb 1997 09:36:18 -0800 Sender: owner-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >the 2.1.7-RELEASE directory has appeared on the ftp site - but there hasn't >been an announcement on freebsd-announce. I assume it will be appearing soon >and it's safe to use the 2.1.7-RELEASE at the moment? There was an announcement...perhaps your copy got delayed or something. I've attached a copy of it... -DG David Greenman Core-team/Principal Architect, The FreeBSD Project FreeBSD 2.1.7 is now available in: ftp://ftp.freebsd.org/pub/FreeBSD/2.1.7-RELEASE And shortly from its various mirror sites, a list of which may be obtained from: http://www.freebsd.org/handbook/mirrors.html This is a security release to FreeBSD 2.1.6, fixing at least several security holes and addressing a number of outstanding problem reports in that release. FreeBSD 2.1.7 will also be available on CDROM from Walnut Creek CDROM, hopefully shipping within the next 3-4 weeks. If you are a customer of Walnut Creek CDROM and you purchased the 2.1.6 release (either by subscription or by retail) then you are entitled to a *free upgrade*. All you need to do is send mail to orders@cdrom.com (or call 1-800 786-9907 / +1 510 674-0783 Intl), indicate that you would like the free 2.1.7 upgrade and provide your name and address information so that a replacement can be shipped. Walnut Creek CDROM customers will also receive a letter explaining these details. Those puzzled by the near-simultaneous release of 2.1.7 and 2.2 should also look at http://www.freebsd.org/branch.html for the reasons behind this release schedule. CDROM subscription customers should see this page for information on Walnut Creek CDROM's plans for these releases. If you are a commercial user of FreeBSD who would like to take advantage of recent bug fixes without making the jump to our more ambitious 2.2 release (or delay that jump until 2.2 has had more time to mature), or if you're simply looking for the lowest-impact upgrade from 2.1.5, then 2.1.7-RELEASE is for you. Following are the release notes for 2.1.7: RELEASE NOTES FreeBSD 2.1.7 RELEASE 0. What is this release? ------------------------ FreeBSD 2.1.7R is the follow-on release to 2.1.6R and focuses primarily on fixing bugs and closing security holes, the most notable being the setlocale() bug (see ftp://freefall.freebsd.org/pub/CERT) in 2.1.6R. For more information on our bleeding-edge development, please see http://www.freebsd.org/handbook/current.html. 0. What's New since 2.1.6-RELEASE? ---------------------------------- Since the setlocale() security hole forced us to do another release along the 2.1-STABLE branch, we focused on pulling in a lot of additional bug fixes and security enhancements as well, taking also some time to upgrade sysinstall to deal with the MSDOSFS installation bugs which have hosed so many people & to upgrade a few selected utilities. Aside from these, there are few functional changes in 2.1.7R. 1. What's New since 2.1.0-RELEASE? ---------------------------------- Quite a few things have changed since the last major release of FreeBSD. To make it easier to identify specific changes, we've broken them into several major categories: Device Drivers: --------------- Support for the Adaptec AIC7850 on-board SCSI adapter. Support for Specialix SI and XIO serial cards. Support for the Stallion EasyIO, EasyConnection 8/32 and EasyConnection 8/64, as well as the older Onboard and Brumby serial cards. Support for the Intel EtherExpress Pro/100B PCI ethernet card. Support for the 3COM 3C590 and 3C595 ethernet cards. Real PCI Buslogic support (new driver and probing order). Support for the ARNET (now Digiboard) Sync 570i high-speed serial card. Better support for the Matrox Meteor frame grabber card. Support for the Connectix Quickcam. Kernel features: ---------------- Various VM system enhancements and more than a few bugs fixed. A concatenated disk driver for simple types of RAID applications. See the man page for ccd(4) for more information. Real PCI bus probing (before ISA) and support for various PCI bridges. The Linux emulation is now good enough to run the Linux version of Netscape, with JAVA support (as well as a number of other Linux utilities). Userland code updates: ---------------------- The system installation tool has been revamped with slightly different menu behavior and a number of bugs have been fixed. It's hoped that this installation will be more intuitive for new users than previous ones (feedback welcomed, of course) as well as more useful in the post-install scenario (I know, I keep saying this :-). Many improvements to the NIS code. The ncftp program is no longer part of the default system - it has been replaced by a library (/usr/src/lib/libftpio) and a more powerful program which uses it called ``fetch'' (/usr/src/usr.bin/fetch). You may find ncftp as part of the ports collection (in /usr/ports/net/ncftp) if you still wish to use it, though fetch is slightly more capable in that it can fetch from both FTP and HTTP servers (ftp://... or http://... URLs). See the man page for more details. 2. Technical overview --------------------- FreeBSD is a freely available, full source 4.4 BSD Lite based release for Intel i386/i486/Pentium (or compatible) based PC's. It is based primarily on software from U.C. Berkeley's CSRG group, with some enhancements from NetBSD, 386BSD, and the Free Software Foundation. Since our release of FreeBSD 2.0 over a year ago, the performance, feature set and stability of FreeBSD has improved dramatically. The largest change is a revamped VM system with a merged VM/file buffer cache that not only increases performance but reduces FreeBSD's memory footprint, making a 5MB configuration a more acceptable minimum. Other enhancements include full NIS client and server support, transaction TCP support, dial-on-demand PPP, an improved SCSI subsystem, early ISDN support, support for FDDI and Fast Ethernet (100Mbit) adapters, improved support for the Adaptec 2940 (WIDE and narrow) and 3940 SCSI adaptors along with many hundreds of bug fixes. We've taken the comments and suggestions of many of our users to heart and have attempted to provide what we hope is a more sane and easily understood installation process. Your feedback on this (constantly evolving) process is especially welcome! In addition to the base distributions, FreeBSD offers a new ported software collection with over 390 commonly sought-after programs. The list of ports ranges from http (WWW) servers, to games, languages, editors and almost everything in between. The entire ports collection requires only 10MB of storage, all ports being expressed as "deltas" to their original sources. This makes it much easier for us to update ports and greatly reduces the disk space demands made by the ports collection. To compile a port, you simply change to the directory of the program you wish to install, type make and let the system do the rest. The full original distribution for each port you build is retrieved dynamically off of CDROM or a local ftp site, so you need only enough disk space to build the ports you want. (Almost) every port is also provided as a pre-compiled "package" which can be installed with a simple command (pkg_add). See also the new Packages option in the Configuration menu for an especially convenient interface to the package collection. A number of additional documents which you may find helpful in the process of installing and using FreeBSD may now also be found in the /usr/share/doc directory. You may view the manuals with any HTML capable browser by saying: To read the handbook: file:/usr/share/doc/handbook/handbook.html To read the FAQ: file:/usr/share/doc/FAQ/freebsd-faq.html You can also visit the master (and most frequently updated) copies at http://www.freebsd.org. The core of FreeBSD does not contain DES code which would inhibit its being exported outside the United States. There is an add-on package to the core distribution, for use only in the United States, that contains the programs that normally use DES. The auxiliary packages provided separately can be used by anyone. A freely (from outside the U.S.) exportable distribution of DES for our non-U.S. users also exists at ftp://ftp.internat.freebsd.org/pub/FreeBSD. If password security for FreeBSD is all you need and you have no requirement for copying encrypted passwords from different hosts (Suns, DEC machines, etc) into FreeBSD password entries, then FreeBSD's MD5 based security may be all you require! We feel that our default security model is more than a match for DES, and without any messy export issues to deal with. If you're outside (or even inside) the U.S., give it a try! This snapshot also includes support for mixed password files - either DES or MD5 passwords will be accepted, making it easier to transition from one scheme to the other. 3. Supported Configurations --------------------------- FreeBSD currently runs on a wide variety of ISA, VLB, EISA and PCI bus based PC's, ranging from 386sx to Pentium class machines (though the 386sx is not recommended). Support for generic IDE or ESDI drive configurations, various SCSI controller, network and serial cards is also provided. What follows is a list of all disk controllers and ethernet cards currently known to work with FreeBSD. Other configurations may also work, but we have simply not received any confirmation of this. 3.1. Disk Controllers --------------------- WD1003 (any generic MFM/RLL) WD1007 (any generic IDE/ESDI) IDE ATA Adaptec 152x series ISA SCSI controllers Adaptec 154x series ISA SCSI controllers Adaptec 174x series EISA SCSI controller in standard and enhanced mode. Adaptec 274X/284X/2940/3940 (Narrow/Wide/Twin) series ISA/EISA/PCI SCSI controllers. Adaptec AIC-6260 and AIC-6360 based boards, which includes Adaptec AIC7850 on-board SCSI controllers. the AHA-152x and SoundBlaster SCSI cards. ** Note: You cannot boot from the SoundBlaster cards as they have no on-board BIOS, such being necessary for mapping the boot device into the system BIOS I/O vectors. They're perfectly usable for external tapes, CDROMs, etc, however. The same goes for any other AIC-6x60 based card without a boot ROM. Some systems DO have a boot ROM, which is generally indicated by some sort of message when the system is first powered up or reset, and in such cases you *will* also be able to boot from them. Check your system/board documentation for more details. [Note that Buslogic was formerly known as "Bustec"] Buslogic 545S & 545c Buslogic 445S/445c VLB SCSI controller Buslogic 742A, 747S, 747c EISA SCSI controller. Buslogic 946c PCI SCSI controller Buslogic 956c PCI SCSI controller NCR 53C810 and 53C825 PCI SCSI controller. NCR5380/NCR53400 ("ProAudio Spectrum") SCSI controller. DTC 3290 EISA SCSI controller in 1542 emulation mode. UltraStor 14F, 24F and 34F SCSI controllers. Seagate ST01/02 SCSI controllers. Future Domain 8xx/950 series SCSI controllers. WD7000 SCSI controller. With all supported SCSI controllers, full support is provided for SCSI-I & SCSI-II peripherals, including Disks, tape drives (including DAT) and CD ROM drives. The following CD-ROM type systems are supported at this time: (cd) SCSI interface (also includes ProAudio Spectrum and SoundBlaster SCSI) (mcd) Mitsumi proprietary interface (all models) (matcd) Matsushita/Panasonic (Creative SoundBlaster) proprietary interface (562/563 models) (scd) Sony proprietary interface (all models) (wcd) ATAPI IDE interface (experimental and should be considered ALPHA quality!). 3.2. Ethernet cards ------------------- Allied-Telesis AT1700 and RE2000 cards SMC Elite 16 WD8013 ethernet interface, and most other WD8003E, WD8003EBT, WD8003W, WD8013W, WD8003S, WD8003SBT and WD8013EBT based clones. SMC Elite Ultra is also supported. DEC EtherWORKS III NICs (DE203, DE204, and DE205) DEC EtherWORKS II NICs (DE200, DE201, DE202, and DE422) DEC DC21040, DC21041, or DC21140 based NICs (SMC???? DE???) DEC FDDI (DEFPA/DEFEA) NICs Fujitsu MB86960A/MB86965A Intel EtherExpress (not recommended due to driver instability) Intel EtherExpress Pro/100B PCI Fast Ethernet Isolan AT 4141-0 (16 bit) Isolink 4110 (8 bit) Novell NE1000, NE2000, and NE2100 ethernet interface. 3Com 3C501 cards 3Com 3C503 Etherlink II 3Com 3c505 Etherlink/+ 3Com 3C507 Etherlink 16/TP 3Com 3C509, 3C579, 3C589 (PCMCIA), 3C590 & 3C595 (PCI) Etherlink III Toshiba ethernet cards PCMCIA ethernet cards from IBM and National Semiconductor are also supported. Note that NO token ring cards are supported at this time as we're still waiting for someone to donate a driver for one of them. Any takers? 3.3. Misc --------- AST 4 port serial card using shared IRQ. ARNET 8 port serial card using shared IRQ. ARNET (now Digiboard) Sync 570/i high-speed serial. Boca BB1004 4-Port serial card (Modems NOT supported) Boca IOAT66 6-Port serial card (Modems supported) Boca BB1008 8-Port serial card (Modems NOT supported) Boca BB2016 16-Port serial card (Modems supported) Cyclades Cyclom-y Serial Board. STB 4 port card using shared IRQ. SDL Communications Riscom/8 Serial Board. Adlib, SoundBlaster, SoundBlaster Pro, ProAudioSpectrum, Gravis UltraSound and Roland MPU-401 sound cards. FreeBSD currently does NOT support IBM's microchannel (MCA) bus. 4. Obtaining FreeBSD -------------------- You may obtain FreeBSD in a variety of ways: 4.1. FTP/Mail You can ftp FreeBSD and any or all of its optional packages from `ftp.freebsd.org' - the official FreeBSD release site. For other locations that mirror the FreeBSD software see the file MIRROR.SITES. Please ftp the distribution from the site closest (in networking terms) to you. Additional mirror sites are always welcome! Contact admin@freebsd.org for more details if you'd like to become an official mirror site. If you do not have access to the internet and electronic mail is your only recourse, then you may still fetch the files by sending mail to `ftpmail@decwrl.dec.com' - putting the keyword "help" in your message to get more information on how to fetch files using this mechanism. Please do note, however, that this will end up sending many *tens of megabytes* through the mail and should only be employed as an absolute LAST resort! 4.2. CDROM FreeBSD 2.1-RELEASE and these 2.2 SNAPSHOT CDs may be ordered on CDROM from: Walnut Creek CDROM 4041 Pike Lane, Suite D Concord CA 94520 1-800-786-9907, +1-510-674-0783, +1-510-674-0821 (fax) Or via the internet from orders@cdrom.com or http://www.cdrom.com. Their current catalog can be obtained via ftp as: ftp://ftp.cdrom.com/cdrom/catalog. Cost per -RELEASE CD is $39.95 or $24.95 with a FreeBSD subscription. FreeBSD 2.2-SNAP CDs are $29.95 or $14.95 with a FreeBSD-SNAP subscription (-RELEASE and -SNAP subscriptions are entirely seperate). With a subscription, you will automatically receive updates as they are released. Your credit card will be billed when each disk is shipped and you may cancel your subscription at any time without further obligation. Walnut Creek CDROM also sells a full line of FreeBSD related merchandise such as T-shirts ($14.95, available in "child", Large and XL sizes), coffee mugs ($9.95), tattoos ($0.25 each) and posters ($3.00). Shipping (per order not per disc) is $5 in the US, Canada or Mexico and $9.00 overseas. They accept Visa, Mastercard, Discover, American Express or checks in U.S. Dollars and ship COD within the United States. California residents please add 8.25% sales tax. Should you be dissatisfied for any reason, the CD comes with an unconditional return policy. Reporting problems, making suggestions, submitting code ------------------------------------------------------- Your suggestions, bug reports and contributions of code are always valued - please do not hesitate to report any problems you may find (preferably with a fix attached, if you can!). The preferred method to submit bug reports from a machine with internet mail connectivity is to use the send-pr command. Bug reports will be dutifully filed by our faithful bugfiler program and you can be sure that we'll do our best to respond to all reported bugs as soon as possible. Bugs filed in this way are also visible on our WEB site in the support section and are therefore valuable both as bug reports and as "signposts" for other users concerning potential problems to watch out for. If, for some reason, you are unable to use the send-pr command to submit a bug report, you can try to send it to: bugs@FreeBSD.org Otherwise, for any questions or suggestions, please send mail to: questions@FreeBSD.org Additionally, being a volunteer effort, we are always happy to have extra hands willing to help - there are already far more desired enhancements than we'll ever be able to manage by ourselves! To contact us on technical matters, or with offers of help, please send mail to: hackers@FreeBSD.org Please note that these mailing lists can experience *significant* amounts of traffic and if you have slow or expensive mail access and are only interested in keeping up with significant FreeBSD events, you may find it preferable to subscribe instead to: announce@FreeBSD.org All but the freebsd-bugs groups can be freely joined by anyone wishing to do so. Send mail to MajorDomo@FreeBSD.org and include the keyword `help' on a line by itself somewhere in the body of the message. This will give you more information on joining the various lists, accessing archives, etc. There are a number of mailing lists targeted at special interest groups not mentioned here, so send mail to majordomo and ask about them! 6. Acknowledgements ------------------- FreeBSD represents the cumulative work of many dozens, if not hundreds, of individuals from around the world who have worked very hard to bring you this release. It would be very difficult, if not impossible, to enumerate everyone who's contributed to FreeBSD, but nonetheless we shall try (in alphabetical order, of course). If you've contributed something substantive to us and your name is not mentioned here, please be assured that its omission is entirely accidental. Please contact hackers@FreeBSD.org for any desired updates to the lists that follow: The Computer Systems Research Group (CSRG), U.C. Berkeley. Bill Jolitz, for his initial work with 386BSD. The FreeBSD Core Team (in alphabetical order by last name): Satoshi Asami Andrey A. Chernov John Dyson Bruce Evans Justin Gibbs David Greenman Jordan K. Hubbard Poul-Henning Kamp Rich Murphey Gary Palmer Søren Schmidt Peter Wemm Garrett A. Wollman Jörg Wunsch The FreeBSD Development Team, excluding core team members (in alphabetical order by last name): Ugen J.S. Antsilevich Torsten Blum Gary Clark II Adam David Peter Dufault Frank Durda IV Julian Elischer Sean Eric Fagan Stefan Esser Bill Fenner John Fieber Marc G. Fournier Lars Fredriksen Thomas Gellekum Thomas Graichen Rod Grimes John Hay Eric L. Hernes Jeffrey Hsu Gary Jennejohn Andreas Klemm L Jonas Olsson Scott Mace Atsushi Murai Mark Murray Alex Nash Sujal Patel Bill Paul Joshua Peck Macdonald John Polstra Mike Pritchard Doug Rabson James Raynard Geoff Rehmet Martin Renters Paul Richards Ollivier Robert Dima Ruban Wolfram Schneider Andreas Schulz Karl Strickland Paul Traina Guido van Rooij Steven Wallace Nate Williams Jean-Marc Zucconi Additional FreeBSD helpers and beta testers: Coranth Gryphon Dave Rivers Kaleb S. Keithley Michael Smith Terry Lambert David Dawes Troy Curtis Special mention to: Walnut Creek CDROM, without whose help (and continuing support) this release would never have been possible. Dermot McDonnell for his donation of a Toshiba XM3401B CDROM drive. Chuck Robey for his donation of a floppy tape streamer for testing. Larry Altneu and Wilko Bulte for providing us with Wangtek and Archive QIC-02 tape drives for testing and driver hacking. CalWeb Internet Services for the loan of a P6/200 machine for speedy package building. Everyone at Montana State University for their initial support. And to the many thousands of FreeBSD users and testers all over the world, without whom this release simply would not have been possible. We sincerely hope you enjoy this release of FreeBSD! The FreeBSD Core Team $Id: relnotes.hlp,v 1.1.2.32 1997/02/17 08:32:05 jkh Exp $ LocalWords: Adaptec From owner-freebsd-stable Thu Feb 20 19:21:12 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id TAA02509 for stable-outgoing; Thu, 20 Feb 1997 19:21:12 -0800 (PST) Received: from kirk.edmweb.com (kirk.edmweb.com [204.244.190.1]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id TAA02502 for ; Thu, 20 Feb 1997 19:21:09 -0800 (PST) Received: from bitbucket (bluesmoke.edmweb.com [204.244.190.8]) by kirk.edmweb.com (8.8.5/8.7.3) with ESMTP id TAA00167 for ; Thu, 20 Feb 1997 19:20:56 -0800 (PST) Received: from localhost by bitbucket with smtp id m0vxlXR-000CGlC (Debian Smail-3.2 1996-Jul-4 #2); Thu, 20 Feb 1997 19:20:25 -0800 (PST) Date: Thu, 20 Feb 1997 19:20:23 -0800 (PST) From: Steve Reid X-Sender: steve@bluesmoke To: freebsd-stable@freebsd.org Subject: file src-2.1.0.284xEmpty.gz ? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Is the file ftp://ftp.freebsd.org/pub/FreeBSD/FreeBSD-stable/ctm/src-2.1.0284xEmpty.gz a valid base CTM file? I ask because it doesn't have the usual *A.gz suffix. I'm reluctant to download a 28 meg file with the word "Empty" in the filename without checking first. From owner-freebsd-stable Thu Feb 20 21:20:25 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id VAA03198 for stable-outgoing; Thu, 20 Feb 1997 21:20:25 -0800 (PST) Received: from cray.svaar.no (cray.svaar.no [194.19.7.150]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id VAA03193 for ; Thu, 20 Feb 1997 21:20:20 -0800 (PST) Received: (from peter@localhost) by cray.svaar.no (8.8.5/8.7.3) id GAA02039; Fri, 21 Feb 1997 06:20:12 +0100 (MET) Date: Fri, 21 Feb 1997 06:20:12 +0100 (MET) Message-Id: <199702210520.GAA02039@cray.svaar.no> From: Peter Svaar To: freebsd-stable@freebsd.org Subject: subscribe Sender: owner-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk subscribe peter@svaar.no subscribe -- From owner-freebsd-stable Fri Feb 21 02:38:56 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id CAA18125 for stable-outgoing; Fri, 21 Feb 1997 02:38:56 -0800 (PST) Received: from eel.dataplex.net (eel.dataplex.net [208.2.87.2]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id CAA18120 for ; Fri, 21 Feb 1997 02:38:53 -0800 (PST) Received: from [208.2.87.3] (shrimp [208.2.87.3]) by eel.dataplex.net (8.7.5/8.6.9) with ESMTP id EAA15587; Fri, 21 Feb 1997 04:38:45 -0600 (CST) X-Sender: rkw@mail.dataplex.net Message-Id: In-Reply-To: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Fri, 21 Feb 1997 04:36:43 -0600 To: Steve Reid From: Richard Wackerbarth Subject: Re: file src-2.1.0.284xEmpty.gz ? Cc: freebsd-stable@freebsd.org Sender: owner-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk At 9:20 PM -0600 2/20/97, Steve Reid wrote: >Is the file >ftp://ftp.freebsd.org/pub/FreeBSD/FreeBSD-stable/ctm/src-2.1.0284xEmpty.gz >a valid base CTM file? > >I ask because it doesn't have the usual *A.gz suffix. I'm reluctant to >download a 28 meg file with the word "Empty" in the filename without >checking first. Yes it is. When the new README file gets posted, you'll see the designation change. It was done so that we could handle things like src-2.2.0300x2.1.7R or src-2.2.0300x2.1.0525 the allow crossovers from multiple places. In the long run, I think that it will be easier than trying to sort out names such as 2.2.0300J and the like. From owner-freebsd-stable Fri Feb 21 12:53:01 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id MAA22026 for stable-outgoing; Fri, 21 Feb 1997 12:53:01 -0800 (PST) Received: from thompson.ebay.com (thompson.ebay.com [206.184.213.42]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id MAA22018 for ; Fri, 21 Feb 1997 12:52:59 -0800 (PST) Received: from pete.ebay.com ([205.215.226.130]) by thompson.ebay.com (8.8.5/8.6.12) with SMTP id MAA16125 for ; Fri, 21 Feb 1997 12:52:54 -0800 (PST) Received: by pete.ebay.com with Microsoft Mail id <01BC1FF5.EB538860@pete.ebay.com>; Fri, 21 Feb 1997 12:51:13 -0800 Message-ID: <01BC1FF5.EB538860@pete.ebay.com> From: pete helme To: "'freebsd-stable@freebsd.org'" Subject: SCSI idle hangs and reboots with 2.1.7 Date: Fri, 21 Feb 1997 12:51:11 -0800 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by freefall.freebsd.org id MAA22020 Sender: owner-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk We're running a heavily loaded web server which was running fine on 2.1.5, when we upgraded to 2.1.6 and then 2.1.7, things went sour and we're now getting frequent hangs and reboots. The only evidence we have of what's happening is the following, which would be scrolling by on the console when the machine could no longer be accessed on the net: Feb 18 10:18:07 calculus /kernel: sd0(ahc0:0:0): timed out while idle, LASTPHASE == 0x1, SCSISIGI == 0x0 Feb 18 10:35:28 calculus /kernel: SEQADDR == 0xd Feb 18 10:35:28 calculus /kernel: Clearing bus reset Feb 18 10:35:28 calculus /kernel: Clearing 'in-reset' flag Feb 18 10:35:28 calculus /kernel: sd1(ahc0:1:0): timed out while idle, LASTPHASE == 0x1, SCSISIGI == 0x0 Feb 18 10:35:28 calculus /kernel: SEQADDR == 0x10 Feb 18 10:35:28 calculus /kernel: sd1(ahc0:1:0): timed out while idle, LASTPHASE == 0x1, SCSISIGI == 0x0 Feb 18 10:35:28 calculus /kernel: SEQADDR == 0xc Feb 18 10:35:28 calculus /kernel: ahc0: Issued Channel A Bus Reset. 2 SCBs aborted Feb 18 10:35:28 calculus /kernel: Clearing bus reset Feb 18 10:35:28 calculus /kernel: Clearing 'in-reset' flag Feb 18 10:35:29 calculus /kernel: sd1(ahc0:1:0): timed out while idle, LASTPHASE == 0x1, SCSISIGI == 0x0 Feb 18 10:38:48 calculus /kernel: SEQADDR == 0xd Feb 18 10:38:49 calculus /kernel: sd1(ahc0:1:0): timed out while idle, LASTPHASE == 0x1, SCSISIGI == 0x0 Feb 18 10:38:49 calculus /kernel: SEQADDR == 0x8 Feb 18 10:38:49 calculus /kernel: ahc0: Issued Channel A Bus Reset. 2 SCBs aborted Feb 18 10:57:59 calculus /kernel: Clearing bus reset When we first upgraded to 2.1.6 we were getting hangs a couple of times a day. When we'd run in and look at the server, we'd see stuff like the above scrolling on the console. The server could be pinged, but we couldn't telnet into it. It was essentially dead and we'd have to reboot. Usually 12 hours later the same thing would happen and we'd have to reboot the machine again. On one occasion we couldn't even ping the machine and it was completely stuck. We've upgraded to the "final" 2.1.7 and things appear to be better, but we still get the occasional reboots at least once a day. Now it doesn't get stuck, but usually reboots itself after a few minutes of the idle. Here's the latest syslog snippet: Feb 21 02:12:51 calculus /kernel: sd0(ahc0:0:0): timed out while idle, LASTPHASE == 0x1, SCSISIGI == 0x0 Feb 21 02:12:51 calculus /kernel: SEQADDR == 0x8 Feb 21 02:15:58 calculus /kernel: FreeBSD 2.1.7-RELEASE #0: Thu Feb 20 18:07:36 PST 1997 As you can see, we got the idle report again and it rebooted itself a couple of minutes later. We thought maybe it was the SCSI chain, so we swapped the Adaptec 2940 for one in a different machine, that made no difference. We also checked the cable and it seems fine. The idle is not always happening on the same device, drives 0 & 1 have been seen with these idle errors so we doubt it's the drives themselves. Again it was working fine last week before we upgraded the OS. We've been getting a lot of these rtq_reallyold messages too: Feb 20 19:22:11 calculus /kernel: in_rtqtimo: adjusted rtq_reallyold to 10 ...but we've heard they are innocuous. We did see at least one instance though were there was one of these messages and then, in the same second in the log, the SCSI idles started. We've tried running Apache 1.1.3 and 1.2b4 and 1.2b6 and that hasn't made any difference with the crashes. We did remove some kernel changes we made to SOMAXCON and TCP options to make it a more generic kernel, but that hasn't gotten rid of the SCSI idles. This is running on a Pentium Pro 200 machine with 128 MBs. A couple of our other machines which have had the 2.1.7 upgrades appear to be OK. If anyone has any ideas what's going on, please let us know! Thanks. pete@ebay.com From owner-freebsd-stable Fri Feb 21 15:38:23 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id PAA03661 for stable-outgoing; Fri, 21 Feb 1997 15:38:23 -0800 (PST) Received: from dns.pinpt.com (dns.pinpt.com [205.179.195.1]) by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id PAA03652 for ; Fri, 21 Feb 1997 15:38:20 -0800 (PST) Received: from journeyman (gatemaster.pinpt.com [205.179.195.65]) by dns.pinpt.com (8.6.12/8.6.12) with SMTP id PAA01056; Fri, 21 Feb 1997 15:36:33 -0800 Date: Fri, 21 Feb 97 15:35:59 Pacific Standard Time From: "Sean J. Schluntz" Subject: Re: Problems with 3COM Etherlink III PCMCIA card To: Nate Williams , Rob Miracle Cc: Nate Williams , stable@freebsd.org X-Mailer: Chameleon ATX 6.0, Standards Based IntraNet Solutions, NetManage Inc. X-Priority: 3 (Normal) References: <199702182155.OAA19063@rocky.mt.sri.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > Yes. The card specificlly is a 3C589D. > > > > Thanks > > Hmm, I haven't yet heard a 'working' report from a 3C589D, so I don't > know if the 'zp' driver works with it. I have heard that the ep driver > works, but it's a nightmare to setup right now (my fault). > > What are the parameters that *DOS* (w/out card-services running) states > that the card is configured for? I had no problem with the 2.2-SNAP from about November (Or what ever one was on line then.) It let me load the system through FTP with out a problem. -Sean (If you need more info I can get the new boot floppy and see what happens.) ---------------------------------------------------------------------- Sean J. Schluntz Manager, Support Services ph. 408.997.6900 x222 PinPoint Software Corporation fx. 408.323.2300 6155 Almaden Expressway, Suite 100 San Jose, CA. 95120 http://www.pinpt.com/ Local Time Sent: 02/21/97 15:35:59 ---------------------------------------------------------------------- From owner-freebsd-stable Fri Feb 21 15:42:31 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id PAA03930 for stable-outgoing; Fri, 21 Feb 1997 15:42:31 -0800 (PST) Received: from rocky.mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id PAA03925 for ; Fri, 21 Feb 1997 15:42:27 -0800 (PST) Received: (from nate@localhost) by rocky.mt.sri.com (8.7.5/8.7.3) id QAA04438; Fri, 21 Feb 1997 16:42:21 -0700 (MST) Date: Fri, 21 Feb 1997 16:42:21 -0700 (MST) Message-Id: <199702212342.QAA04438@rocky.mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: "Sean J. Schluntz" Cc: Nate Williams , Rob Miracle , stable@freebsd.org Subject: Re: Problems with 3COM Etherlink III PCMCIA card In-Reply-To: References: <199702182155.OAA19063@rocky.mt.sri.com> Sender: owner-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > > Yes. The card specificlly is a 3C589D. > > > Hmm, I haven't yet heard a 'working' report from a 3C589D, so I don't > > know if the 'zp' driver works with it. I have heard that the ep driver > > works, but it's a nightmare to setup right now (my fault). > > > > What are the parameters that *DOS* (w/out card-services running) states > > that the card is configured for? > > I had no problem with the 2.2-SNAP from about November (Or what ever one was > on line then.) It let me load the system through FTP with out a problem. Really? Rob couldn't get the CIS tuple from the 589D to be valid. Nate From owner-freebsd-stable Fri Feb 21 16:23:30 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id QAA07367 for stable-outgoing; Fri, 21 Feb 1997 16:23:30 -0800 (PST) Received: from dns.pinpt.com (dns.pinpt.com [205.179.195.1]) by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id QAA07360 for ; Fri, 21 Feb 1997 16:23:28 -0800 (PST) Received: from journeyman (gatemaster.pinpt.com [205.179.195.65]) by dns.pinpt.com (8.6.12/8.6.12) with SMTP id QAA01398; Fri, 21 Feb 1997 16:21:40 -0800 Date: Fri, 21 Feb 97 16:18:54 Pacific Standard Time From: "Sean J. Schluntz" Subject: Re: Problems with 3COM Etherlink III PCMCIA card To: "Sean J. Schluntz" , Nate Williams Cc: Nate Williams , Rob Miracle , stable@freebsd.org X-Mailer: Chameleon ATX 6.0, Standards Based IntraNet Solutions, NetManage Inc. X-Priority: 3 (Normal) References: <199702212342.QAA04438@rocky.mt.sri.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > > > Yes. The card specificlly is a 3C589D. > > > > > Hmm, I haven't yet heard a 'working' report from a 3C589D, so I don't > > > know if the 'zp' driver works with it. I have heard that the ep driver > > > works, but it's a nightmare to setup right now (my fault). > > > > > > What are the parameters that *DOS* (w/out card-services running) states > > > that the card is configured for? > > > > I had no problem with the 2.2-SNAP from about November (Or what ever one was > > on line then.) It let me load the system through FTP with out a problem. > > Really? Rob couldn't get the CIS tuple from the 589D to be valid. Hmm.. ... ze: pcmcia slot1: 3Com Corporation~3C589~TP/BNC LAN Card Ver. 2a~000002~ ... zp0 at 0x300-0x30f irq 10 maddr 0xd8000 in isa zp0: aui/bnc/utp address 00:a0:24:aa:11:a7 ... That's with the 2.2-GAMMA boot.flp. Default Kernal boot from the menu, no mods. Looks like when I did it before (Though this time I don't have a bracket to put the spare HD in my laptop to do a full install, but last time it worked great!) -Sean ---------------------------------------------------------------------- Sean J. Schluntz Manager, Support Services ph. 408.997.6900 x222 PinPoint Software Corporation fx. 408.323.2300 6155 Almaden Expressway, Suite 100 San Jose, CA. 95120 http://www.pinpt.com/ Local Time Sent: 02/21/97 16:18:55 ---------------------------------------------------------------------- From owner-freebsd-stable Fri Feb 21 18:16:51 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id SAA13932 for stable-outgoing; Fri, 21 Feb 1997 18:16:51 -0800 (PST) Received: from Central.KeyWest.MPGN.COM (rwm@Central.TanSoft.COM [206.175.4.1]) by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id SAA13926 for ; Fri, 21 Feb 1997 18:16:46 -0800 (PST) Received: (from rwm@localhost) by Central.KeyWest.MPGN.COM (8.6.9/8.6.9) id VAA10745; Fri, 21 Feb 1997 21:16:37 -0500 From: Rob Miracle Message-Id: <199702220216.VAA10745@Central.KeyWest.MPGN.COM> Subject: Re: Problems with 3COM Etherlink III PCMCIA card To: schluntz@pinpt.com (Sean J. Schluntz) Date: Fri, 21 Feb 1997 21:16:37 -0500 (EST) Cc: stable@freebsd.org, nate@mt.sri.com In-Reply-To: from "Sean J. Schluntz" at Feb 21, 97 04:18:54 pm X-Mailer: ELM [version 2.4 PL23] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > > > > Yes. The card specificlly is a 3C589D. > > > > > > > Hmm, I haven't yet heard a 'working' report from a 3C589D, so I don't > > > > > > I had no problem with the 2.2-SNAP from about November (Or what ever one > > Really? Rob couldn't get the CIS tuple from the 589D to be valid. > > ... > ze: pcmcia slot1: 3Com Corporation~3C589~TP/BNC LAN Card Ver. 2a~000002~ > ... > zp0 at 0x300-0x30f irq 10 maddr 0xd8000 in isa > zp0: aui/bnc/utp address 00:a0:24:aa:11:a7 > ... > That's with the 2.2-GAMMA boot.flp. Default Kernal boot from the menu, no > mods. Looks like when I did it before (Though this time I don't have a > bracket to put the spare HD in my laptop to do a full install, but last time > it worked great!) Are you sure this is the D card? A C card popped in and worked great. Of course we could have just gotten a bad run of cards. We had two of them that behaved the same way. We even had problems getting them to run with Win95. Rob -- Rob Miracle rwm@mpgn.com for webmaster@mpgn.com From owner-freebsd-stable Sat Feb 22 00:53:30 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id AAA11821 for stable-outgoing; Sat, 22 Feb 1997 00:53:30 -0800 (PST) Received: from mh1.cts.com (root@mh1.cts.com [205.163.24.66]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id AAA11799 for ; Sat, 22 Feb 1997 00:53:27 -0800 (PST) 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 AAA20865 for ; Sat, 22 Feb 1997 00:53:25 -0800 (PST) Received: (from mdavis@localhost) by io.cts.com (8.8.5/8.6.9) id AAA21597 for stable@freebsd.org; Sat, 22 Feb 1997 00:53:33 -0800 (PST) From: Morgan Davis Message-Id: <199702220853.AAA21597@io.cts.com> Subject: Random dives out of make world To: stable@freebsd.org Date: Sat, 22 Feb 1997 00:53:33 -0800 (PST) X-Mailer: ELM [version 2.4ME+ PL19 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk What might cause a system with the latest -stable sources to bomb out of a "make world" at random places with "internal compiler error: signal 11" and other such errors? This system is a freshly installed 2.1.6 which has the -stable branch via cvsup. It is lightly used, only for telnetting out at this point, so no other crashing. I managed to get it up to 2.1.7 by continual "make all install" attempts until in /usr/src it finally completed. But even after 2.1.7, I still get: pid 23979 (cc1), uid 0: exited on signal 11 Here's a dmesg if this helps pinpoint a trouble spot I should focus on. Would a kernel config file help, too? (based on generic -- it's all rather vanilla). Thanks for any assistance. --Morgan ----- Forwarded message from Morgan Davis ----- >From mdavis@freek.cts.com Wed Feb 19 00:01:03 1997 Date: Wed, 19 Feb 1997 00:00:53 -0800 (PST) From: Morgan Davis Message-Id: <199702190800.AAA23996@freek.cts.com> To: mdavis@io.cts.com FreeBSD 2.1.7-RELEASE #0: Fri Feb 14 15:54:55 PST 1997 mdavis@freek.cts.com:/usr/src/sys/compile/FREEK CPU: 120-MHz Pentium 735\\90 or 815\\100 (Pentium-class CPU) Origin = "GenuineIntel" Id = 0x525 Stepping=5 Features=0x1bf real memory = 67108864 (65536K bytes) avail memory = 62996480 (61520K 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 DC21140 [10-100Mb/s] pass 1.2 de0: address 00:00:c0:b5:51:dc de0: enabling 10baseT port de1 rev 18 int a irq 10 on pci0:10 de1: SMC 9332 DC21140 [10-100Mb/s] pass 1.2 de1: address 00:00:c0:ad:51:dc de1: enabling 10baseT port bt0 rev 0 int a irq 11 on pci0:11 bt0: Bt946C/ 0-(32bit) bus bt0: reading board settings, busmastering, int=11 bt0: version 4.25J, fast sync, parity, 32 mbxs, 32 ccbs bt0: targ 0 sync rate=10.00MB/s(100ns), offset=15 bt0: targ 1 sync rate=10.00MB/s(100ns), offset=15 bt0: targ 2 sync rate=10.00MB/s(100ns), offset=15 bt0: targ 6 sync rate= 5.00MB/s(200ns), offset=08 bt0: Using Strict Round robin scheme bt0 waiting for scsi devices to settle (bt0:0:0): "SEAGATE ST32430N 0300" type 0 fixed SCSI 2 sd0(bt0:0:0): Direct-Access 2049MB (4197405 512 byte sectors) (bt0:1:0): "SEAGATE ST32430N 0300" type 0 fixed SCSI 2 sd1(bt0:1:0): Direct-Access 2049MB (4197405 512 byte sectors) (bt0:2:0): "SEAGATE ST32430N 0510" type 0 fixed SCSI 2 sd2(bt0:2:0): Direct-Access 2049MB (4197405 512 byte sectors) (bt0:6:0): "SONY SDT-5200 3.26" type 1 removable SCSI 2 st0(bt0:6:0): Sequential-Access density code 0x13, drive empty Probing for devices on the ISA bus: sc0 at 0x60-0x6f irq 1 on motherboard sc0: VGA color <16 virtual consoles, flags=0x0> sio0 at 0x3f8-0x3ff irq 4 on isa sio0: type 16550A sio1 at 0x2f8-0x2ff irq 3 on isa sio1: type 16550A fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa fdc0: NEC 72065B fd0: 1.44MB 3.5in bt: unit number (1) too high bt1 not found at 0x330 npx0 on motherboard npx0: INT 16 interface pid 16220 (cc1), uid 0: exited on signal 11 pid 20490 (cc1), uid 0: exited on signal 11 pid 23979 (cc1), uid 0: exited on signal 11 ----- End of forwarded message from Morgan Davis ----- From owner-freebsd-stable Sat Feb 22 02:26:16 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id CAA28860 for stable-outgoing; Sat, 22 Feb 1997 02:26:16 -0800 (PST) Received: from kachina.jetcafe.org (jetcafe.org [207.155.21.2]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id CAA28855 for ; Sat, 22 Feb 1997 02:26:12 -0800 (PST) Received: from [127.0.0.1] ([127.0.0.1]) by kachina.jetcafe.org (8.7.5/8.7.3) with SMTP id CAA29886 for ; Sat, 22 Feb 1997 02:26:11 -0800 (PST) Message-Id: <199702221026.CAA29886@kachina.jetcafe.org> X-Authentication-Warning: kachina.jetcafe.org: Host [127.0.0.1] didn't use HELO protocol To: freebsd-stable@freebsd.org Subject: Make World failures Date: Sat, 22 Feb 1997 02:26:10 -0800 From: Dave Hayes Sender: owner-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I've been trying to get "make world" to finish. My CVSup tag is RELENG_2_1, which should pick up stable (right?). I'm getting the following problems: ===> xditview ... cc -O -I/usr/X11R6/include -DFONTPATH=\"/usr/share/groff_font\" -DHAVE_UNISTD_H=1 -DHAVE_DIRENT_H=1 -DHAVE_LIMITS_H=1 -DHAVE_STDLIB_H=1 -DHAVE_SYS_DIR_H=1 -DHAVE_CC_LIMITS_H=1 -DHAVE_CC_UNISTD_H=1 -DSTDLIB_H_DECLARES_GETOPT=1 -DUNISTD_H_DECLARES_GETOPT=1 -DSTDLIB_H_DECLARES_PUTENV=1 -DSTDIO_H_DECLARES_POPEN=1 -DSTDIO_H_DECLARE_PCLOSE=1 -DRETSIGTYPE=void -DHAVE_MMAP=1 -DHAVE_RENAME=1 -DHAVE_MKSTEMP=1 -DHAVE_SYS_SIGLIST=1 -o gxditview xditview.o Dvi.o draw.o font.o lex.o page.o parse.o XFontName.o DviChar.o device.o -L/usr/X11R6/lib -lXaw -lXmu -lXt -lXext -lX11 -lm Shell.o: Undefined symbol `_SmcCloseConnection' referenced from text segment Shell.o: Undefined symbol `_SmcModifyCallbacks' referenced from text segment Shell.o: Undefined symbol `_SmcClientID' referenced from text segment Shell.o: Undefined symbol `_SmcOpenConnection' referenced from text segment Shell.o: Undefined symbol `_SmcGetIceConnection' referenced from text segment Shell.o: Undefined symbol `_IceConnectionNumber' referenced from text segment Shell.o: Undefined symbol `_SmcSetProperties' referenced from text segment Shell.o: Undefined symbol `_SmcSetProperties' referenced from text segment Shell.o: Undefined symbol `_SmcDeleteProperties' referenced from text segment Shell.o: Undefined symbol `_SmcGetIceConnection' referenced from text segment Shell.o: Undefined symbol `_IceProcessMessages' referenced from text segment Shell.o: Undefined symbol `_SmcSaveYourselfDone' referenced from text segment Shell.o: Undefined symbol `_SmcInteractDone' referenced from text segment Shell.o: Undefined symbol `_SmcSaveYourselfDone' referenced from text segment Shell.o: Undefined symbol `_SmcInteractRequest' referenced from text segment Shell.o: Undefined symbol `_SmcInteractDone' referenced from text segment Shell.o: Undefined symbol `_SmcRequestSaveYourselfPhase2' referenced from text segment Shell.o: Undefined symbol `_SmcSaveYourselfDone' referenced from text segment *** Error code 1 Output of uname -a: FreeBSD 2.1.6-RELEASE #0: Sun Nov 24 23:31:18 1996 \ jkh@whisker.cdrom.com:/usr/src/sys/compile/GENERIC i386 Is it me or the tree? -------- Dave Hayes - Altadena CA, USA - dave@jetcafe.org Freedom Knight of Usenet - http://www.jetcafe.org/~dave/usenet A person was frighteningly ugly. Once he was asked how could he go on living with such a terrible face. "Why should I be unhappy?", answered the man. "I never see my own face; let others worry." From owner-freebsd-stable Sat Feb 22 11:01:26 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id LAA02566 for stable-outgoing; Sat, 22 Feb 1997 11:01:26 -0800 (PST) Received: from destiny.erols.com (someone@destiny.erols.com [207.96.73.65]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id LAA02559 for ; Sat, 22 Feb 1997 11:01:21 -0800 (PST) Received: from localhost (jdowdal@localhost) by destiny.erols.com (8.8.5/8.6.12) with SMTP id OAA07942; Sat, 22 Feb 1997 14:00:53 -0500 (EST) Date: Sat, 22 Feb 1997 14:00:52 -0500 (EST) From: John Dowdal To: Morgan Davis cc: stable@freebsd.org Subject: Re: Random dives out of make world In-Reply-To: <199702220853.AAA21597@io.cts.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Sat, 22 Feb 1997, Morgan Davis wrote: > What might cause a system with the latest -stable sources to bomb out > of a "make world" at random places with "internal compiler error: > signal 11" and other such errors? This system is a freshly installed > 2.1.6 which has the -stable branch via cvsup. It is lightly used, > only for telnetting out at this point, so no other crashing. I > managed to get it up to 2.1.7 by continual "make all install" attempts > until in /usr/src it finally completed. But even after 2.1.7, I still > get: > > pid 23979 (cc1), uid 0: exited on signal 11 > > Here's a dmesg if this helps pinpoint a trouble spot I should focus > on. Would a kernel config file help, too? (based on generic -- it's > all rather vanilla). > When it dies, do you see the message "cc1 received fatal signal 11" (or a similar message)? If so, it is a memory/cache problem, or you may have an overclocked or overheated CPU. John From owner-freebsd-stable Sat Feb 22 11:05:33 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id LAA02711 for stable-outgoing; Sat, 22 Feb 1997 11:05:33 -0800 (PST) Received: from mercury.uniserve.com (mercury.uniserve.com [204.191.197.248]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id LAA02706 for ; Sat, 22 Feb 1997 11:05:29 -0800 (PST) Received: from haven.uniserve.com (haven.uniserve.com [198.53.215.121]) by mercury.uniserve.com (8.8.2/8.8.2) with SMTP id KAA20445; Sat, 22 Feb 1997 10:48:37 -0800 (PST) Date: Sat, 22 Feb 1997 11:09:10 -0800 (PST) From: Tom Samplonius To: Morgan Davis cc: stable@freebsd.org Subject: Re: Random dives out of make world In-Reply-To: <199702220853.AAA21597@io.cts.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Sat, 22 Feb 1997, Morgan Davis wrote: > What might cause a system with the latest -stable sources to bomb out > of a "make world" at random places with "internal compiler error: > signal 11" and other such errors? This system is a freshly installed Probably bad hardware. Check RAM and cache. I always recommend people use parity RAM and parity/ecc mb. Tom From owner-freebsd-stable Sat Feb 22 12:24:31 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id MAA15464 for stable-outgoing; Sat, 22 Feb 1997 12:24:31 -0800 (PST) Received: from mh1.cts.com (root@mh1.cts.com [205.163.24.66]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id MAA15459 for ; Sat, 22 Feb 1997 12:24:29 -0800 (PST) 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 MAA05914 for ; Sat, 22 Feb 1997 12:24:19 -0800 (PST) Received: (from root@localhost) by io.cts.com (8.8.5/8.6.9) id MAA23086 for stable@freebsd.org; Sat, 22 Feb 1997 12:24:17 -0800 (PST) From: Morgan Davis Message-Id: <199702222024.MAA23086@io.cts.com> Subject: Re: Random dives out of make world To: stable@freebsd.org Date: Sat, 22 Feb 1997 12:24:17 -0800 (PST) In-Reply-To: <199702220853.AAA21597@io.cts.com> from Morgan Davis at "Feb 22, 97 00:53:33 am" X-Mailer: ELM [version 2.4ME+ PL19 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk A couple days ago, I wrote: > What might cause a system with the latest -stable sources to bomb out > of a "make world" at random places with "internal compiler error: > signal 11" and other such errors? > ... I received a lot of good suggestions on this. The consensus is either bad RAM, too aggressive BIOS settings for RAM speed, overheated CPU, or some other hardware problem like SCSI termination. Before reporting this problem, I also thought it was bad RAM. So I swapped in a new set of EDO SIMMs, but with no change in behavior. So now I'll check the BIOS settings next -- that's probably the culprit. Thanks again for the quick and excellent advice I received from many of you. --Morgan From owner-freebsd-stable Sat Feb 22 12:29:32 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id MAA15913 for stable-outgoing; Sat, 22 Feb 1997 12:29:32 -0800 (PST) Received: from mail.ptd.net (srv1.ptd.net [204.186.0.131]) by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id MAA15908 for ; Sat, 22 Feb 1997 12:29:29 -0800 (PST) Received: (qmail 8240 invoked from network); 22 Feb 1997 20:23:59 -0000 Received: from cs4-7.pot.ptd.net (HELO synergy) (204.186.34.55) by postoffice.ptd.net with SMTP; 22 Feb 1997 20:23:59 -0000 Received: by synergy with Microsoft Mail id <01BC20D5.2D8D7760@synergy>; Sat, 22 Feb 1997 15:29:22 -0500 Message-ID: <01BC20D5.2D8D7760@synergy> From: Nick Folino To: "'FreeBSD-Stable'" Subject: RE: Random dives out of make world Date: Sat, 22 Feb 1997 15:28:39 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by freefall.freebsd.org id MAA15909 Sender: owner-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk ---------- From: John Dowdal[SMTP:jdowdal@destiny.erols.com] Sent: Saturday, February 22, 1997 9:00 AM To: Morgan Davis Cc: stable@FreeBSD.ORG Subject: Re: Random dives out of make world On Sat, 22 Feb 1997, Morgan Davis wrote: > What might cause a system with the latest -stable sources to bomb out > of a "make world" at random places with "internal compiler error: > signal 11" and other such errors? This system is a freshly installed > 2.1.6 which has the -stable branch via cvsup. It is lightly used, > only for telnetting out at this point, so no other crashing. I > managed to get it up to 2.1.7 by continual "make all install" attempts > until in /usr/src it finally completed. But even after 2.1.7, I still > get: > > pid 23979 (cc1), uid 0: exited on signal 11 > > Here's a dmesg if this helps pinpoint a trouble spot I should focus > on. Would a kernel config file help, too? (based on generic -- it's > all rather vanilla). > When it dies, do you see the message "cc1 received fatal signal 11" (or a similar message)? If so, it is a memory/cache problem, or you may have an overclocked or overheated CPU. John I've had the same problems with a fresh 2.1.7 sup....no one knows why it's happening....now I'm sure it's not my computer if others are having the same problems. Could the 2.1.7 source be corrupted? Nick P.S. I haven't been able to get it to compile at all on my Pentium 100, but it finally worked out on my Nexgen P90. From owner-freebsd-stable Sat Feb 22 13:31:33 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id NAA20145 for stable-outgoing; Sat, 22 Feb 1997 13:31:33 -0800 (PST) Received: from ohio.river.org (ohio.river.org [199.4.65.219]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id NAA20137 for ; Sat, 22 Feb 1997 13:31:30 -0800 (PST) Received: (from dhawk@localhost) by ohio.river.org (8.7.3/8.7.3) id NAA27089 for freebsd-stable@freebsd.org; Sat, 22 Feb 1997 13:30:45 -0800 (PST) From: David Hawkins Message-Id: <199702222130.NAA27089@ohio.river.org> Subject: 'make world' clobber /etc? DES? To: freebsd-stable@freebsd.org Date: Sat, 22 Feb 1997 13:30:45 -0800 (PST) X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I've got a 2.1.0 Freebsd system. I've just used 'sup' to get all the files here to do an upgrade to 2.1.7 but I want to make absolutely sure about two points: 1. will 'make world' overwrite my existing /etc -- I'd hate to lose my password file, for example. Or does 'make world' just do binaries? 2. I want to make sure I'm still using DES after the upgrade. I have a DES password file because I upgraded from Linux originally. Just wanted to get reassured on those two points. Thanks! later, david -- David Hawkins -- dhawk@river.org http://www.river.org Do you know what a pessimist is? A person who thinks everybody as nasty as himself, and hates them for it. -- George Bernard Shaw From owner-freebsd-stable Sat Feb 22 15:27:26 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id PAA28586 for stable-outgoing; Sat, 22 Feb 1997 15:27:26 -0800 (PST) Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id PAA28572 for ; Sat, 22 Feb 1997 15:27:23 -0800 (PST) Received: from time.cdrom.com (jkh@localhost [127.0.0.1]) by time.cdrom.com (8.8.5/8.6.9) with ESMTP id PAA12292; Sat, 22 Feb 1997 15:27:14 -0800 (PST) To: Nick Folino cc: "'FreeBSD-Stable'" Subject: Re: Random dives out of make world In-reply-to: Your message of "Sat, 22 Feb 1997 15:28:39 EST." <01BC20D5.2D8D7760@synergy> Date: Sat, 22 Feb 1997 15:27:14 -0800 Message-ID: <12289.856654034@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-stable@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > I've had the same problems with a fresh 2.1.7 sup....no one knows >why it's ha ppening....now I'm sure it's not my computer if others are >having the same prob lems. Could the 2.1.7 source be corrupted? If it were, I think I'd have had more failure reports than just 2. :-) I've been compiling and running from the 2.1.7 sources for weeks now. This is quite mysterious. Jordan From owner-freebsd-stable Sat Feb 22 15:31:56 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id PAA29177 for stable-outgoing; Sat, 22 Feb 1997 15:31:56 -0800 (PST) Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id PAA29169 for ; Sat, 22 Feb 1997 15:31:53 -0800 (PST) Received: from time.cdrom.com (jkh@localhost [127.0.0.1]) by time.cdrom.com (8.8.5/8.6.9) with ESMTP id PAA12315; Sat, 22 Feb 1997 15:31:43 -0800 (PST) To: David Hawkins cc: freebsd-stable@freebsd.org Subject: Re: 'make world' clobber /etc? DES? In-reply-to: Your message of "Sat, 22 Feb 1997 13:30:45 PST." <199702222130.NAA27089@ohio.river.org> Date: Sat, 22 Feb 1997 15:31:43 -0800 Message-ID: <12311.856654303@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > 1. will 'make world' overwrite my existing /etc -- I'd hate to lose my > password file, for example. Or does 'make world' just do binaries? Make world will not touch your /etc. This means that it's also more than possible to get it *waaaay* out of date with the new startup mechanisms expected by whatever you're upgrading to, so be sure and very carefully merge all of this by hand. It's not fun, but it's gotta be done. And no, don't ask me for a list of files - you'll have to sort of intuit that for yourself based on what you've changed locally. :-) > 2. I want to make sure I'm still using DES after the upgrade. I have a > DES password file because I upgraded from Linux originally. Then make sure that you have /usr/src/secure and that you build from it (I believe it's pulled in automagically if it exists, but I haven't checked). Jordan From owner-freebsd-stable Sat Feb 22 17:29:42 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id RAA06765 for stable-outgoing; Sat, 22 Feb 1997 17:29:42 -0800 (PST) Received: from ohio.river.org (ohio.river.org [199.4.65.219]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id RAA06760 for ; Sat, 22 Feb 1997 17:29:38 -0800 (PST) Received: (from dhawk@localhost) by ohio.river.org (8.7.3/8.7.3) id RAA02631 for freebsd-stable@freebsd.org; Sat, 22 Feb 1997 17:28:54 -0800 (PST) From: David Hawkins Message-Id: <199702230128.RAA02631@ohio.river.org> Subject: Problem with 'make world' To: freebsd-stable@freebsd.org Date: Sat, 22 Feb 1997 17:28:54 -0800 (PST) X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Current OS: 2.1.0 FreeBSD Target OS: 2.1.7 FreeBSD Since I wanted to see what kind of /etc 'make world' would build I set DESTDIR to a directory on a filesystem with tons of space. It bombed pretty quickly after creating: bin dev etc lkm mnt proc root sbin sys tmp usr var with the following error message: (after 318 lines of make output) missing: ./ufs/ufs (created) missing: ./vm (created) cd /users/extradir/; rm -f /users/extradir/sys; ln -s usr/src/sys sys cd /users/extradir/usr/share/locale; for l in da_DK de_AT de_CH de_DE en_AU en_CA en_GB en_US es_ES fi_FI fr_BE fr_CA fr_CH fr_FR is_IS it_CH it_IT nl_BE nl_NL no_NO pt_PT sv_SE ; do rm -f $l.ISO_8859-1; ln -s lt_LN.ISO_8859-1 $l.ISO_8859-1; done rm: da_DK.ISO_8859-1: is a directory *** Error code 1 Stop. *** Error code 1 Stop. Question: Would I have the same problem if I did a regular make world without $DESTDIR? The problem is that the machine is remote (60 miles away) so If I Screw Up we're down until Monday afternoon. At the same time we're a little nervous because we were cracked last week. Thanks! later, david -- David Hawkins -- dhawk@river.org Do you know what a pessimist is? A person who thinks everybody as nasty as himself, and hates them for it. -- George Bernard Shaw