From owner-freebsd-stable Sun Sep 14 03:41:48 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id DAA04984 for stable-outgoing; Sun, 14 Sep 1997 03:41:48 -0700 (PDT) Received: from pooh.cdrom.com (pooh.cdrom.com [204.216.28.222]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id DAA04979 for ; Sun, 14 Sep 1997 03:41:45 -0700 (PDT) Received: from localhost (murray@localhost) by pooh.cdrom.com (8.8.7/8.7.3) with SMTP id DAA26149 for ; Sun, 14 Sep 1997 03:40:10 -0700 (PDT) Date: Sun, 14 Sep 1997 03:40:09 -0700 (PDT) From: Murray Stokely To: freebsd-stable@freebsd.org Subject: building aferstep Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk cc -o afterstep -m486 -O2 -L/usr/X11R6/lib afterstep.o configure.o events.o borders.o menus.o functions.o resize.o add_window.o pager.o move.o icons.o windows.o module.o placement.o decorations.o colormaps.o misc.o style.o stepgfx.o hashtable.o -L/usr/X11R6/lib -lXpm -lXExExt -lXext -lX11 -lafterstep -L../lib -lgnumalloc ld: -lXExExt: no match *** Error code 1 Stop. Where can I find this missing library? Murray Stokely From owner-freebsd-stable Sun Sep 14 07:10:37 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id HAA11196 for stable-outgoing; Sun, 14 Sep 1997 07:10:37 -0700 (PDT) Received: from as5200-port-254.no.neosoft.com (as5200-port-254.no.neosoft.com [206.27.167.254]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id HAA11177 for ; Sun, 14 Sep 1997 07:10:33 -0700 (PDT) Received: (from conrads@localhost) by as5200-port-254.no.neosoft.com (8.8.7/8.8.6) id JAA01033 for stable@freebsd.org; Sun, 14 Sep 1997 09:11:27 -0500 (CDT) Message-ID: X-Mailer: XFMail 1.2-alpha [p0] on FreeBSD Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 Date: Sun, 14 Sep 1997 09:11:26 -0500 (CDT) Organization: NeoSoft, Inc. From: Conrad Sabatier To: stable@freebsd.org Subject: Error message while cvsup'ing RELENG_2_2 Sender: owner-freebsd-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Here's one I've never encountered before: Cannot calculate checksum for "/usr/ports/games/angband/pkg/PLIST": Device not configured Clues, anyone? -- Conrad Sabatier | FreeBSD -- UNIX for your PC http://www.neosoft.com/~conrads | Why settle for less than the best? Spambots, use this: biteme@f-u.org | http://www.freebsd.org From owner-freebsd-stable Sun Sep 14 13:31:56 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id NAA28666 for stable-outgoing; Sun, 14 Sep 1997 13:31:56 -0700 (PDT) Received: from venus.net (venus.net [205.243.72.10]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id NAA28661 for ; Sun, 14 Sep 1997 13:31:53 -0700 (PDT) Received: from localhost (ve1-p2.venus.net [205.243.75.5]) by venus.net (8.7.1/8.7.3) with SMTP id QAA00249 for ; Sun, 14 Sep 1997 16:37:16 -0400 (EDT) Date: Sun, 14 Sep 1997 15:31:35 -0500 (EST) From: Andre LeClaire X-Sender: leclaire@localhost To: stable@FreeBSD.ORG Subject: Re: Monochrome screen saver In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk "OK, so you didn't get any answers to your question. Cheer up, things could be worse.", I told myself last week. So I cheered up, and - sure enough - things got worse. After cvsup'ing RELENG_2_2 and make world'ing yesterday, now I get a message at boot time: rc.i386 configuring syscons: blank_time screensavermodload: error initializing module: Invalid argument Any help would be greatly appreciated. Andre On Fri, 5 Sep 1997, Andre LeClaire wrote: > Is it possible to configure the blank screen saver in 2.2-STABLE to work > with a Monochrome Display Adapter, or does it only work with VGA? I've > tried it with a (true blue, vintage 1982) IBM full length card and a > couple of clone monochrome graphics adapters without success. From owner-freebsd-stable Sun Sep 14 13:34:17 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id NAA28802 for stable-outgoing; Sun, 14 Sep 1997 13:34:17 -0700 (PDT) Received: from pooh.cdrom.com (pooh.cdrom.com [204.216.28.222]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id NAA28772 for ; Sun, 14 Sep 1997 13:34:15 -0700 (PDT) Received: from localhost (murray@localhost) by pooh.cdrom.com (8.8.7/8.7.3) with SMTP id NAA28027 for ; Sun, 14 Sep 1997 13:32:37 -0700 (PDT) Date: Sun, 14 Sep 1997 13:32:36 -0700 (PDT) From: Murray Stokely To: freebsd-stable@FreeBSD.ORG Subject: Re: building aferstep In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Just to give a little more information. I'm running 2.2-stable (originally from 2.2.2) and I removed my entire /usr/ports tree then re-cvsuped it with the same result. On Sun, 14 Sep 1997, Murray Stokely wrote: % cc -o afterstep -m486 -O2 -L/usr/X11R6/lib afterstep.o % configure.o events.o borders.o menus.o functions.o resize.o % add_window.o pager.o move.o icons.o windows.o module.o placement.o % decorations.o colormaps.o misc.o style.o stepgfx.o hashtable.o % -L/usr/X11R6/lib -lXpm -lXExExt -lXext -lX11 -lafterstep -L../lib % -lgnumalloc % ld: -lXExExt: no match % *** Error code 1 % % Stop. % % Where can I find this missing library? Murray Stokely From owner-freebsd-stable Sun Sep 14 15:24:17 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id PAA05998 for stable-outgoing; Sun, 14 Sep 1997 15:24:17 -0700 (PDT) Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id PAA05990 for ; Sun, 14 Sep 1997 15:24:10 -0700 (PDT) Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.7/8.6.9) with ESMTP id PAA18801; Sun, 14 Sep 1997 15:24:08 -0700 (PDT) To: Murray Stokely cc: freebsd-stable@FreeBSD.ORG Subject: Re: building aferstep In-reply-to: Your message of "Sun, 14 Sep 1997 13:32:36 PDT." Date: Sun, 14 Sep 1997 15:24:08 -0700 Message-ID: <18798.874275848@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-stable@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk You have an old version of XFree86. Upgrade it and this will stop. :-) > Just to give a little more information. I'm running 2.2-stable > (originally from 2.2.2) and I removed my entire /usr/ports tree then > re-cvsuped it with the same result. > > On Sun, 14 Sep 1997, Murray Stokely wrote: > % cc -o afterstep -m486 -O2 -L/usr/X11R6/lib afterstep.o > % configure.o events.o borders.o menus.o functions.o resize.o > % add_window.o pager.o move.o icons.o windows.o module.o placement.o > % decorations.o colormaps.o misc.o style.o stepgfx.o hashtable.o > % -L/usr/X11R6/lib -lXpm -lXExExt -lXext -lX11 -lafterstep -L../lib > % -lgnumalloc > % ld: -lXExExt: no match > % *** Error code 1 > % > % Stop. > % > % Where can I find this missing library? > > Murray Stokely > From owner-freebsd-stable Mon Sep 15 00:21:09 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id AAA07726 for stable-outgoing; Mon, 15 Sep 1997 00:21:09 -0700 (PDT) Received: from echonyc.com (echonyc.com [198.67.15.2]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id AAA07716 for ; Mon, 15 Sep 1997 00:21:04 -0700 (PDT) Received: from localhost (benedict@localhost) by echonyc.com (8.8.7/8.8.7) with SMTP id DAA04666 for ; Mon, 15 Sep 1997 03:21:01 -0400 (EDT) Date: Mon, 15 Sep 1997 03:21:01 -0400 (EDT) From: Snob Art Genre To: stable@freebsd.org Subject: Make buildworld fails in /usr/bin/tip . . . Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk . . . with "don't know how to make uucplock.c". I cvsup'd a few hours ago. Ben "You have your mind on computers, it seems." From owner-freebsd-stable Mon Sep 15 01:43:21 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id BAA14329 for stable-outgoing; Mon, 15 Sep 1997 01:43:21 -0700 (PDT) Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id BAA14324 for ; Mon, 15 Sep 1997 01:43:19 -0700 (PDT) Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.7/8.6.9) with ESMTP id BAA14412; Mon, 15 Sep 1997 01:43:14 -0700 (PDT) To: Snob Art Genre cc: stable@FreeBSD.ORG Subject: Re: Make buildworld fails in /usr/bin/tip . . . In-reply-to: Your message of "Mon, 15 Sep 1997 03:21:01 EDT." Date: Mon, 15 Sep 1997 01:43:14 -0700 Message-ID: <14408.874312994@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-stable@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Sorry, fixed. I tested the merge from -current but didn't know that tip also depended on it. Jordan > . . . with "don't know how to make uucplock.c". I cvsup'd a few hours > ago. > > > > Ben > > "You have your mind on computers, it seems." > From owner-freebsd-stable Mon Sep 15 02:56:32 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id CAA18435 for stable-outgoing; Mon, 15 Sep 1997 02:56:32 -0700 (PDT) Received: from avatar.dorm12.nctu.edu.tw (Avatar.Dorm12.NCTU.edu.tw [140.113.124.5]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id CAA18424 for ; Mon, 15 Sep 1997 02:56:18 -0700 (PDT) Received: (from root@localhost) by avatar.dorm12.nctu.edu.tw (8.8.7/8.6.12) id RAA00313 for freebsd-stable@freebsd.org; Mon, 15 Sep 1997 17:58:21 GMT From: Avatarf Message-Id: <199709151758.RAA00313@avatar.dorm12.nctu.edu.tw> Subject: About NCR Driver... To: freebsd-stable@freebsd.org Date: Mon, 15 Sep 1997 17:58:21 +0000 (GMT) Reply-To: chro@ccca.nctu.edu.tw X-Mailer: ELM [version 2.4ME+ PL31H (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi, everytime after I reboot,a strange message appears to ncr0 (Takram DC-390F). Here is the dmesg: ncr0 rev 3 int a irq 12 on pci0:11 (ncr0:0:0): "IBM DCAS-32160W S65A" type 0 fixed SCSI 2 sd0(ncr0:0:0): Direct-Access sd0(ncr0:0:0): WIDE SCSI (16 bit) enabled sd0(ncr0:0:0): 40.0 MB/s (50 ns, offset 15) 2063MB (4226725 512 byte sectors) (ncr0:1:0): "MICROP 4110-09NB_Nov18F TN0F" type 0 fixed SCSI 2 sd1(ncr0:1:0): Direct-Access sd1(ncr0:1:0): 10.0 MB/s (100 ns, offset 15) 1002MB (2053880 512 byte sectors) [deleted] assertion "cp" failed: file "../../pci/ncr.c", line 6191 assertion "cp" failed: file "../../pci/ncr.c", line 6191 sd0(ncr0:0:0): COMMAND FAILED (4 28) @f0df7000. What did it mean? how to fix it? And when I run ncrcontrol. it shows the error message: ncrcontrol: incompatible with kernel. Rebuild! but the program and kernel source are installed at the same time!! (all 2.2-970913-RELENG) kernel config contains: controller ncr0 controller scbus0 device sd0 options SCSI_NCR_DFLT_TAGS=8 How to fix it? thanks a lot for answer! From owner-freebsd-stable Mon Sep 15 03:12:41 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id DAA19190 for stable-outgoing; Mon, 15 Sep 1997 03:12:41 -0700 (PDT) Received: from btp1da.phy.uni-bayreuth.de (btp1da.phy.uni-bayreuth.de [132.180.20.32]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id DAA19181 for ; Mon, 15 Sep 1997 03:12:33 -0700 (PDT) Received: (from werner@localhost) by btp1da.phy.uni-bayreuth.de (8.8.7/8.7.3) id MAA19270; Mon, 15 Sep 1997 12:12:16 +0200 (MEST) Message-ID: <19970915121216.55876@btp1da.phy.uni-bayreuth.de> Date: Mon, 15 Sep 1997 12:12:16 +0200 From: Werner Griessl To: "Jordan K. Hubbard" Cc: stable@freebsd.org Subject: Re: Make buildworld fails in /usr/bin/tip . . . References: <14408.874312994@time.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.81e In-Reply-To: <14408.874312994@time.cdrom.com>; from Jordan K. Hubbard on Mon, Sep 15, 1997 at 01:43:14AM -0700 Sender: owner-freebsd-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Mon, Sep 15, 1997 at 01:43:14AM -0700, Jordan K. Hubbard wrote: > Sorry, fixed. I tested the merge from -current but didn't know that > tip also depended on it. > > Jordan > > > . . . with "don't know how to make uucplock.c". I cvsup'd a few hours > > ago. > > > > > > > > Ben > > > > "You have your mind on computers, it seems." > > > But now it fails with: rm -f .depend mkdep -f .depend -a -I/usr/obj/spare/F/src/tmp/usr/include/rpcsvc -I/usr/obj/spare/F/src/tmp/usr/include klm_prot_xdr.c mount_xdr.c nfs_prot_xdr.c nlm_prot_xdr.c rex_xdr.c rnusers_xdr.c rquota_xdr.c rstat_xdr.c rwall_xdr.c sm_inter_xdr.c spray_xdr.c yppasswd_xdr.c ypxfrd_xdr.c klm_prot_xdr.c:6: klm_prot.h: No such file or directory mount_xdr.c:6: mount.h: No such file or directory nfs_prot_xdr.c:6: nfs_prot.h: No such file or directory nlm_prot_xdr.c:6: nlm_prot.h: No such file or directory rex_xdr.c:6: rex.h: No such file or directory rnusers_xdr.c:6: rnusers.h: No such file or directory rquota_xdr.c:6: rquota.h: No such file or directory rstat_xdr.c:6: rstat.h: No such file or directory rwall_xdr.c:6: rwall.h: No such file or directory sm_inter_xdr.c:6: sm_inter.h: No such file or directory spray_xdr.c:6: spray.h: No such file or directory yppasswd_xdr.c:6: yppasswd.h: No such file or directory ypxfrd_xdr.c:6: ypxfrd.h: No such file or directory mkdep: compile failed. *** Error code 1 Werner From owner-freebsd-stable Mon Sep 15 03:19:42 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id DAA19456 for stable-outgoing; Mon, 15 Sep 1997 03:19:42 -0700 (PDT) Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id DAA19451 for ; Mon, 15 Sep 1997 03:19:38 -0700 (PDT) Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.7/8.6.9) with ESMTP id DAA15897; Mon, 15 Sep 1997 03:19:34 -0700 (PDT) To: Werner Griessl cc: stable@freebsd.org Subject: Re: Make buildworld fails in /usr/bin/tip . . . In-reply-to: Your message of "Mon, 15 Sep 1997 12:12:16 +0200." <19970915121216.55876@btp1da.phy.uni-bayreuth.de> Date: Mon, 15 Sep 1997 03:19:34 -0700 Message-ID: <15892.874318774@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > But now it fails with: No, that's a different problem - you are trying to build from an improperly bootstrapped tree. Use the world target. Jordan From owner-freebsd-stable Mon Sep 15 05:38:18 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id FAA26243 for stable-outgoing; Mon, 15 Sep 1997 05:38:18 -0700 (PDT) Received: from hawk.gnome.co.uk (gnome.gw.cerbernet.co.uk [193.243.224.22]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id FAA26234 for ; Mon, 15 Sep 1997 05:38:13 -0700 (PDT) Received: from hawk.gnome.co.uk (localhost [127.0.0.1]) by hawk.gnome.co.uk (8.8.7/8.8.7) with ESMTP id NAA03193; Mon, 15 Sep 1997 13:25:28 +0100 (BST) Message-Id: <199709151225.NAA03193@hawk.gnome.co.uk> X-Mailer: exmh version 2.0zeta 7/24/97 To: "Jordan K. Hubbard" cc: Werner Griessl , stable@FreeBSD.ORG Subject: Re: Make buildworld fails in /usr/bin/tip . . . In-reply-to: Your message of "Mon, 15 Sep 1997 03:19:34 PDT." <15892.874318774@time.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 15 Sep 1997 13:25:28 +0100 From: Chris Stenton Sender: owner-freebsd-stable@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > But now it fails with: > > No, that's a different problem - you are trying to build from an > improperly bootstrapped tree. Use the world target. > > Jordan I have just done a :- make includes make world and get the same problem as Werner Griessl. Chris From owner-freebsd-stable Mon Sep 15 06:42:11 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id GAA29271 for stable-outgoing; Mon, 15 Sep 1997 06:42:11 -0700 (PDT) Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id GAA29265 for ; Mon, 15 Sep 1997 06:42:08 -0700 (PDT) Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.7/8.6.9) with ESMTP id GAA25528; Mon, 15 Sep 1997 06:42:10 -0700 (PDT) To: freebsd-stable@freebsd.org Cc: Werner Griessl Subject: Re: Make buildworld fails in /usr/bin/tip . . . In-reply-to: Your message of "Mon, 15 Sep 1997 15:27:09 +0200." <19970915152709.35331@btp1da.phy.uni-bayreuth.de> Date: Mon, 15 Sep 1997 06:42:10 -0700 Message-ID: <25523.874330930@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk My apologies, folks, I just verified it with a make release - this isn't Werner's fault at all (es tut mir leid, Werner!) As far as I can figure it out, the new -current behavior of turning on a new flag (compatMake) by default in make is having deleterious and unforseen side-effects on the rest of the build tree. I'll have it fixed shortly! Jordan > On Mon, Sep 15, 1997 at 03:23:29AM -0700, Jordan K. Hubbard wrote: > > Perhaps you have something spammed in the source tree? > > > > I haven't even *touched* the rpc headers so it would make no sense > > for them to be blowing up now. > > > > Jordan > > > > > On Mon, Sep 15, 1997 at 03:19:34AM -0700, Jordan K. Hubbard wrote: > > > > > But now it fails with: > > > > > > > > No, that's a different problem - you are trying to build from an > > > > improperly bootstrapped tree. Use the world target. > > > > > > > > Jordan > > > > > > Was a "make world" ! > > > Werner > > > > > > > Same problem after a fresh cvsup ! > Werner > From owner-freebsd-stable Mon Sep 15 19:42:25 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id TAA14864 for stable-outgoing; Mon, 15 Sep 1997 19:42:25 -0700 (PDT) Received: from austin.polstra.com (austin.polstra.com [206.213.73.10]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id TAA14859 for ; Mon, 15 Sep 1997 19:42:23 -0700 (PDT) Received: from austin.polstra.com (jdp@localhost) by austin.polstra.com (8.8.7/8.8.5) with ESMTP id TAA29148; Mon, 15 Sep 1997 19:42:05 -0700 (PDT) Message-Id: <199709160242.TAA29148@austin.polstra.com> To: conrads@neosoft.com Subject: Re: Error message while cvsup'ing RELENG_2_2 In-Reply-To: References: Organization: Polstra & Co., Seattle, WA Cc: stable@freebsd.org Date: Mon, 15 Sep 1997 19:42:05 -0700 From: John Polstra Sender: owner-freebsd-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk In article , Conrad Sabatier wrote: > Here's one I've never encountered before: > > Cannot calculate checksum for "/usr/ports/games/angband/pkg/PLIST": Device > not configured Gads, that's a new one! What happens when you run this command? /sbin/md5 /usr/ports/games/angband/pkg/PLIST Also, what is the output of "ls -l /usr/ports/games/angband/pkg/PLIST" and "ls -Ll /usr/ports/games/angband/pkg/PLIST" ? John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Self-knowledge is always bad news." -- John Barth From owner-freebsd-stable Mon Sep 15 21:14:29 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id VAA19478 for stable-outgoing; Mon, 15 Sep 1997 21:14:29 -0700 (PDT) Received: from bofh.noc.best.net (rone@ennui.org [205.149.163.54]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id VAA19473 for ; Mon, 15 Sep 1997 21:14:26 -0700 (PDT) Received: (from rone@localhost) by bofh.noc.best.net (8.8.7/8.7.3) id VAA10933 for stable@freebsd.org; Mon, 15 Sep 1997 21:14:22 -0700 (PDT) From: Ron Echeverri Message-Id: <199709160414.VAA10933@bofh.noc.best.net> Subject: ATAPI code changed? To: stable@freebsd.org Date: Mon, 15 Sep 1997 21:14:22 -0700 (PDT) X-GmbH: Gesellschaft mit beschränkter Haftung X-Mailer: ELM [version 2.4ME+ PL31 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk All of a sudden, around Sep 11, workman started coredumping on me as soon as i run it. I cvsuped late on Sep 12 and made world and rebuilt the kernel, with no improvement. cdcontrol and cdplay work fine, and of course, i'm able to use the same CD-ROM unit with Wimp95. Did something happen or should i just email the port maintainer to see if he wants a coredump to work with? thanks, rone -- Ron Echeverri Systems/Usenet Administration "This is _my_ ISP, _i_ do the Best Internet Communications, Inc. ass-kicking around here!" -rpwhite From owner-freebsd-stable Mon Sep 15 21:46:53 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id VAA22282 for stable-outgoing; Mon, 15 Sep 1997 21:46:53 -0700 (PDT) Received: from silvia.HIP.Berkeley.EDU (ala-ca13-17.ix.netcom.com [204.32.168.49]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id VAA22266 for ; Mon, 15 Sep 1997 21:46:27 -0700 (PDT) Received: (from asami@localhost) by silvia.HIP.Berkeley.EDU (8.8.7/8.6.9) id VAA24992; Mon, 15 Sep 1997 21:45:11 -0700 (PDT) Date: Mon, 15 Sep 1997 21:45:11 -0700 (PDT) Message-Id: <199709160445.VAA24992@silvia.HIP.Berkeley.EDU> To: jkh@time.cdrom.com CC: murray@cdrom.com, freebsd-stable@FreeBSD.ORG In-reply-to: <18798.874275848@time.cdrom.com> (jkh@time.cdrom.com) Subject: Re: building aferstep From: asami@cs.berkeley.edu (Satoshi Asami) Sender: owner-freebsd-stable@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk * You have an old version of XFree86. Upgrade it and this * will stop. :-) * > % -L/usr/X11R6/lib -lXpm -lXExExt -lXext -lX11 -lafterstep -L../lib * > % -lgnumalloc * > % ld: -lXExExt: no match Or rather, your imake config files are older than your set of X libraries. Also, note the "-lgnumalloc" in the command line -- that shouldn't apply for 2.2-stable (it's only for pre-2.2 releases). That problem should also go away when you upgrade your imake config files to match you X libraries. Satoshi From owner-freebsd-stable Tue Sep 16 01:46:09 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id BAA12047 for stable-outgoing; Tue, 16 Sep 1997 01:46:09 -0700 (PDT) Received: from kanin.arnes.si (kanin.arnes.si [193.2.1.66]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id BAA12042 for ; Tue, 16 Sep 1997 01:46:03 -0700 (PDT) Received: from irc.arnes.si by kanin.arnes.si with SMTP using DNS (PP) id <25323-0@kanin.arnes.si>; Tue, 16 Sep 1997 10:45:30 +0200 Received: by tosc.arnes.si with SMTP id <4310-143>; Tue, 16 Sep 1997 10:47:27 +0100 X-Mailer: exmh version 1.6.9 8/22/96 To: stable@FreeBSD.ORG Subject: route Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 16 Sep 1997 10:47:17 +0200 From: Uros Juvan Message-Id: <97Sep16.104727mest.4310-143+154@tosc.arnes.si> Sender: owner-freebsd-stable@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Hello. I'm running 2.2.1 and I just noticed strange routes in my routing table. netstat -nr reported things like: gateway UGHDM 0 4119 ep0 ^ - Created dynamically (by redirect) This and similar routes apeared in the routing table by themself even without routed being ran. I'm connected to the same hubI(UTP!) as ppp user's router is. Can somebody explain that please? Thanx, Uros Juvan ARNES From owner-freebsd-stable Tue Sep 16 04:57:36 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id EAA20058 for stable-outgoing; Tue, 16 Sep 1997 04:57:36 -0700 (PDT) Received: from as5200-port-254.no.neosoft.com (as5200-port-254.no.neosoft.com [206.27.167.254]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id EAA20050 for ; Tue, 16 Sep 1997 04:57:31 -0700 (PDT) Received: (from conrads@localhost) by as5200-port-254.no.neosoft.com (8.8.7/8.8.6) id GAA18078; Tue, 16 Sep 1997 06:58:10 -0500 (CDT) Message-ID: X-Mailer: XFMail 1.2-alpha [p0] on FreeBSD Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <199709160242.TAA29148@austin.polstra.com> Date: Tue, 16 Sep 1997 06:58:09 -0500 (CDT) Organization: NeoSoft, Inc. From: Conrad Sabatier To: John Polstra Subject: Re: Error message while cvsup'ing RELENG_2_2 Cc: stable@freebsd.org Sender: owner-freebsd-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On 16-Sep-97 John Polstra wrote: >In article , >Conrad Sabatier wrote: >> Here's one I've never encountered before: >> >> Cannot calculate checksum for "/usr/ports/games/angband/pkg/PLIST": >> Device not configured > >Gads, that's a new one! What happens when you run this command? > > /sbin/md5 /usr/ports/games/angband/pkg/PLIST root:/usr/home/conrads# /sbin/md5 /usr/ports/games/angband/pkg/PLIST /usr/ports/games/angband/pkg/PLIST: Device not configured >Also, what is the output of "ls -l /usr/ports/games/angband/pkg/PLIST" >and "ls -Ll /usr/ports/games/angband/pkg/PLIST" ? A-ha! I think we've found it! root:/usr/home/conrads# ls -l /usr/ports/games/angband/pkg/PLIST br-srw--w- 1 8426901 8085310 52, 0x3934003a Dec 3 05:07 /usr/ports/games/angband/pkg/PLIST I had a nasty system crash about a week ago. fsck had to do some rather extensive cleaning up (thank goodness no serious damage). I'll just delete and regrab it on the next sup. Thanks! -- Conrad Sabatier | FreeBSD -- UNIX for your PC http://www.neosoft.com/~conrads | Why settle for less than the best? Spambots, use this: biteme@f-u.org | http://www.freebsd.org From owner-freebsd-stable Tue Sep 16 05:47:51 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id FAA21887 for stable-outgoing; Tue, 16 Sep 1997 05:47:51 -0700 (PDT) Received: from btp1da.phy.uni-bayreuth.de (btp1da.phy.uni-bayreuth.de [132.180.20.32]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id FAA21881 for ; Tue, 16 Sep 1997 05:47:45 -0700 (PDT) Received: (from werner@localhost) by btp1da.phy.uni-bayreuth.de (8.8.7/8.7.3) id OAA02914; Tue, 16 Sep 1997 14:47:31 +0200 (MEST) Message-ID: <19970916144730.59623@btp1da.phy.uni-bayreuth.de> Date: Tue, 16 Sep 1997 14:47:30 +0200 From: Werner Griessl To: "Jordan K. Hubbard" Cc: stable@freebsd.org Subject: Re: Make buildworld fails in /usr/bin/tip . . . References: <19970915152709.35331@btp1da.phy.uni-bayreuth.de> <25523.874330930@time.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.81e In-Reply-To: <25523.874330930@time.cdrom.com>; from Jordan K. Hubbard on Mon, Sep 15, 1997 at 06:42:10AM -0700 Sender: owner-freebsd-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Mon, Sep 15, 1997 at 06:42:10AM -0700, Jordan K. Hubbard wrote: > My apologies, folks, I just verified it with a make release - this > isn't Werner's fault at all (es tut mir leid, Werner!) keine Ursache > > As far as I can figure it out, the new -current behavior of turning on > a new flag (compatMake) by default in make is having deleterious and > unforseen side-effects on the rest of the build tree. I'll have it > fixed shortly! > > Jordan > > > > On Mon, Sep 15, 1997 at 03:23:29AM -0700, Jordan K. Hubbard wrote: > > > Perhaps you have something spammed in the source tree? > > > > > > I haven't even *touched* the rpc headers so it would make no sense > > > for them to be blowing up now. > > > > > > Jordan > > > > > > > On Mon, Sep 15, 1997 at 03:19:34AM -0700, Jordan K. Hubbard wrote: > > > > > > But now it fails with: > > > > > > > > > > No, that's a different problem - you are trying to build from an > > > > > improperly bootstrapped tree. Use the world target. > > > > > > > > > > Jordan > > > > > > > > Was a "make world" ! > > > > Werner > > > > > > > > > > > Same problem after a fresh cvsup ! > > Werner > > > stable world is working again Thanks for the fix ! Werner From owner-freebsd-stable Tue Sep 16 07:28:09 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id HAA26399 for stable-outgoing; Tue, 16 Sep 1997 07:28:09 -0700 (PDT) Received: from netcom1.netcom.com (mvh@netcom23.netcom.com [192.100.81.137]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id HAA26390 for ; Tue, 16 Sep 1997 07:28:05 -0700 (PDT) Received: (from mvh@localhost) by netcom1.netcom.com (8.8.7/8.8.7) id HAA03725; Tue, 16 Sep 1997 07:28:04 -0700 (PDT) Date: Tue, 16 Sep 1997 07:28:04 -0700 (PDT) Message-Id: <199709161428.HAA03725@netcom1.netcom.com> From: "Michael V. Harding" To: stable@freebsd.org Subject: silo overflows... Sender: owner-freebsd-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I don't know if this is a 'stable' question, but I am getting silo overflows after upgrading to a K6 / Asus TX-97 combo and upgrading to -stable. Is there something different about this setup? Should I turn off bus mastering? Anyone else seen this? I would be surprised if the TX chipset was messed up. Also, how do I turn down the threshold in sio.c? I looked at the code but wasn't able to determine what to hack to set the threshold to 8 bytes. Thanks! Mike Harding From owner-freebsd-stable Tue Sep 16 07:35:29 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id HAA26904 for stable-outgoing; Tue, 16 Sep 1997 07:35:29 -0700 (PDT) Received: from austin.polstra.com (austin.polstra.com [206.213.73.10]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id HAA26893 for ; Tue, 16 Sep 1997 07:35:26 -0700 (PDT) Received: from austin.polstra.com (jdp@localhost) by austin.polstra.com (8.8.7/8.8.5) with ESMTP id HAA03314; Tue, 16 Sep 1997 07:35:18 -0700 (PDT) Message-Id: <199709161435.HAA03314@austin.polstra.com> To: Conrad Sabatier cc: stable@freebsd.org Subject: Re: Error message while cvsup'ing RELENG_2_2 In-reply-to: Your message of "Tue, 16 Sep 1997 06:58:09 CDT." Date: Tue, 16 Sep 1997 07:35:18 -0700 From: John Polstra Sender: owner-freebsd-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > >> Cannot calculate checksum for "/usr/ports/games/angband/pkg/PLIST": > >> Device not configured > > > >Gads, that's a new one! What happens when you run this command? > > > > /sbin/md5 /usr/ports/games/angband/pkg/PLIST > > root:/usr/home/conrads# /sbin/md5 /usr/ports/games/angband/pkg/PLIST > /usr/ports/games/angband/pkg/PLIST: Device not configured :-) > A-ha! I think we've found it! > > root:/usr/home/conrads# ls -l /usr/ports/games/angband/pkg/PLIST > br-srw--w- 1 8426901 8085310 52, 0x3934003a Dec 3 05:07 > /usr/ports/games/angband/pkg/PLIST > > I had a nasty system crash about a week ago. fsck had to do some rather > extensive cleaning up (thank goodness no serious damage). Was the filesystem mounted async at the time of the crash? I'm just curious. John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Self-knowledge is always bad news." -- John Barth From owner-freebsd-stable Tue Sep 16 09:34:51 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id JAA04132 for stable-outgoing; Tue, 16 Sep 1997 09:34:51 -0700 (PDT) Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id JAA04120 for ; Tue, 16 Sep 1997 09:34:46 -0700 (PDT) Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.7/8.6.9) with ESMTP id JAA21289 for ; Tue, 16 Sep 1997 09:34:53 -0700 (PDT) To: freebsd-stable@freebsd.org Subject: 14 day countdown to BETA Date: Tue, 16 Sep 1997 09:34:53 -0700 Message-ID: <21281.874427693@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Unless I hear great howls of protest, I'm going to tag and release FreeBSD 2.2.5-BETA on September 30th and declare a 2.2 code freeze during the 15 day BETA period which will ensue. "This is your branch. This is your branch in code freeze. Any questions?" Jordan From owner-freebsd-stable Tue Sep 16 10:35:05 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id KAA07863 for stable-outgoing; Tue, 16 Sep 1997 10:35:05 -0700 (PDT) Received: from freebie.dcfinc.com (freebie.dcfinc.com [138.113.2.8]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id KAA07842 for ; Tue, 16 Sep 1997 10:34:59 -0700 (PDT) Received: (from chad@localhost) by freebie.dcfinc.com (8.8.3/8.8.3a) id KAA04462; Tue, 16 Sep 1997 10:34:03 -0700 (MST) From: "Chad R. Larson" Message-Id: <199709161734.KAA04462@freebie.dcfinc.com> Subject: Re: route To: uros.juvan@arnes.si (Uros Juvan) Date: Tue, 16 Sep 1997 10:34:02 -0700 (MST) Cc: stable@FreeBSD.ORG In-Reply-To: <97Sep16.104727mest.4310-143+154@tosc.arnes.si> from Uros Juvan at "Sep 16, 97 10:47:17 am" Reply-to: chad@dcfinc.com X-Mailer: ELM [version 2.4ME+ PL22 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > I'm running 2.2.1 and I just noticed strange routes in my routing table. > netstat -nr reported things like: > gateway UGHDM 0 4119 ep0 > ^ - Created dynamically (by redirect) > > This and similar routes apeared in the routing table by themself even without > routed being ran. You've received an "ICMP Redirect" message. They will generate a route without you running any kind of routing daemon. The redirect message is issued by a router when it believes there is a better route to your destination than itself. The router may know that because of his own use of routing protocols, or the network manager may have loaded static routes into the router. The redirect message says, "I'll handle this packet for you, but in the future you'd be better off sending packets to this host over there." -crl -- Chad R. Larson (CRL22) Brother, can you paradigm? 602-953-1392 chad@dcfinc.com chad@anasazi.com crl22@aol.com DCF, Inc. - 14523 North 49th Place, Scottsdale, Arizona 85254 From owner-freebsd-stable Tue Sep 16 10:48:57 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id KAA08699 for stable-outgoing; Tue, 16 Sep 1997 10:48:57 -0700 (PDT) Received: from GndRsh.aac.dev.com (GndRsh.aac.dev.com [198.145.92.241] (may be forged)) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id KAA08690 for ; Tue, 16 Sep 1997 10:48:51 -0700 (PDT) Received: (from rgrimes@localhost) by GndRsh.aac.dev.com (8.8.5/8.7.3) id KAA06915; Tue, 16 Sep 1997 10:48:29 -0700 (PDT) From: "Rodney W. Grimes" Message-Id: <199709161748.KAA06915@GndRsh.aac.dev.com> Subject: Re: 14 day countdown to BETA In-Reply-To: <21281.874427693@time.cdrom.com> from "Jordan K. Hubbard" at "Sep 16, 97 09:34:53 am" To: jkh@time.cdrom.com (Jordan K. Hubbard) Date: Tue, 16 Sep 1997 10:48:29 -0700 (PDT) Cc: freebsd-stable@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL25 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > Unless I hear great howls of protest, I'm going to tag and release > FreeBSD 2.2.5-BETA on September 30th and declare a 2.2 code freeze > during the 15 day BETA period which will ensue. Great howl of protest: `` Declare the freeze Sept 20, already 5 days past when it was suppose to happen, put the tree into ``must be acked by RELENG before commiting to branch mode until Sept 30, then lock it down to ONLY RELENG can commit after Sept 30.'' During the must be ack'ed phase does not mean cdiff's have to be sent and reviewed, just a ``I'm want to merge this, or fix this type of messages.'' 15 days is too short a BETA period, given the tree won't be buildable for more than 50% of the time up until the real code freeze. (3 of my last 4 releng_2_2 cvssup/buildworld's have failed, and yes, I know, I'm even the cause of one of them!) > "This is your branch. This is your branch in code freeze. Any questions?" :-) -- Rod Grimes rgrimes@gndrsh.aac.dev.com Accurate Automation, Inc. Reliable computers for FreeBSD From owner-freebsd-stable Tue Sep 16 12:18:24 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id MAA14238 for stable-outgoing; Tue, 16 Sep 1997 12:18:24 -0700 (PDT) Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id MAA14227 for ; Tue, 16 Sep 1997 12:18:18 -0700 (PDT) Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.7/8.6.9) with ESMTP id MAA01555; Tue, 16 Sep 1997 12:18:16 -0700 (PDT) To: "Rodney W. Grimes" cc: freebsd-stable@FreeBSD.ORG Subject: Re: 14 day countdown to BETA In-reply-to: Your message of "Tue, 16 Sep 1997 10:48:29 PDT." <199709161748.KAA06915@GndRsh.aac.dev.com> Date: Tue, 16 Sep 1997 12:18:15 -0700 Message-ID: <1551.874437495@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-stable@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > Great howl of protest: > `` Declare the freeze Sept 20, already 5 days past when it was suppose > to happen, put the tree into ``must be acked by RELENG before commiting > to branch mode until Sept 30, then lock it down to ONLY RELENG can > commit after Sept 30.'' Do you really think that 10 days of "sort of restricted" committing is going to make any substantive difference? I'm kinda skeptical. Essentially, the only difference I can see between your scenario and mine is that I get out the acknowledge-my-ack-or-die stick in 4 days time and start lock-stepping with everyone over each change until the 30th, after which we're talking the same thing. The only problems I see are that a) 4 days is really not enough time for everyone to finish their merging and b) I don't see much substantive difference between "you must acknowledge my ack" and "if I see you put in something dodgy, I'll make you fix it or take it back out." > 15 days is too short a BETA period, given the tree won't be buildable > for more than 50% of the time up until the real code freeze. (3 of my Hmmmm. On the other hand, I'd hate to be distributing 2.2.2 at COMDEX but that's essentially what we're going to be doing unless we get this release out on schedule (and we'll already be a month behind our quarterly release target just releasing in late October as it is). And no, I'm not simply gating our release technology off of the major trade show schedule, I'm simply saying that hawking 6-month old wares at the industry's largest U.S. trade show is not going to be a recipe for success and we should gauge very carefully the effects of additional delay into November. November is also the christmas rush season and it's more than likely that if we decide to do the CDs in November, customers won't see them until January because trying to get our CDs back in December will only elicit howls of laughter from the replication house ("You want it *when*?!"). This not to say that if 2.2.5 were looking majorly broken in October that I'd release it anyway - certainly not. I'm simply saying that pushing it out past the end of October is going to have unpleasant side-effects of its own and we should really try not to do that. Jordan From owner-freebsd-stable Tue Sep 16 12:43:40 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id MAA15310 for stable-outgoing; Tue, 16 Sep 1997 12:43:40 -0700 (PDT) Received: from GndRsh.aac.dev.com (GndRsh.aac.dev.com [198.145.92.241] (may be forged)) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id MAA15300 for ; Tue, 16 Sep 1997 12:43:36 -0700 (PDT) Received: (from rgrimes@localhost) by GndRsh.aac.dev.com (8.8.5/8.7.3) id MAA07276; Tue, 16 Sep 1997 12:43:25 -0700 (PDT) From: "Rodney W. Grimes" Message-Id: <199709161943.MAA07276@GndRsh.aac.dev.com> Subject: Re: 14 day countdown to BETA In-Reply-To: <1551.874437495@time.cdrom.com> from "Jordan K. Hubbard" at "Sep 16, 97 12:18:15 pm" To: jkh@time.cdrom.com (Jordan K. Hubbard) Date: Tue, 16 Sep 1997 12:43:24 -0700 (PDT) Cc: freebsd-stable@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL25 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > Great howl of protest: > > `` Declare the freeze Sept 20, already 5 days past when it was suppose > > to happen, put the tree into ``must be acked by RELENG before commiting > > to branch mode until Sept 30, then lock it down to ONLY RELENG can > > commit after Sept 30.'' > > Do you really think that 10 days of "sort of restricted" committing > is going to make any substantive difference? I'm kinda skeptical. Your the boss, ultimately, your decision. I'll follow where you lead it... -- Rod Grimes rgrimes@gndrsh.aac.dev.com Accurate Automation, Inc. Reliable computers for FreeBSD From owner-freebsd-stable Tue Sep 16 17:24:30 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id RAA29790 for stable-outgoing; Tue, 16 Sep 1997 17:24:30 -0700 (PDT) Received: from as5200-port-254.no.neosoft.com (as5200-port-254.no.neosoft.com [206.27.167.254]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id RAA29785 for ; Tue, 16 Sep 1997 17:24:25 -0700 (PDT) Received: (from conrads@localhost) by as5200-port-254.no.neosoft.com (8.8.7/8.8.6) id TAA17954; Tue, 16 Sep 1997 19:25:07 -0500 (CDT) Message-ID: X-Mailer: XFMail 1.2-alpha [p0] on FreeBSD Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <199709161435.HAA03314@austin.polstra.com> Date: Tue, 16 Sep 1997 19:25:06 -0500 (CDT) Organization: NeoSoft, Inc. From: Conrad Sabatier To: John Polstra Subject: Re: Error message while cvsup'ing RELENG_2_2 Cc: stable@freebsd.org Sender: owner-freebsd-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On 16-Sep-97 John Polstra wrote: > >> A-ha! I think we've found it! >> >> root:/usr/home/conrads# ls -l /usr/ports/games/angband/pkg/PLIST >> br-srw--w- 1 8426901 8085310 52, 0x3934003a Dec 3 05:07 >> /usr/ports/games/angband/pkg/PLIST >> >> I had a nasty system crash about a week ago. fsck had to do some rather >> extensive cleaning up (thank goodness no serious damage). > >Was the filesystem mounted async at the time of the crash? I'm just >curious. Um, I'm really not sure what that is, to be honest. :-) I just do a normal mount on startup from fstab: # Device Mountpoint FStype Options Dump Pass# /dev/wd1a / ufs rw 1 1 /dev/wd1s1f /usr ufs rw 1 1 /dev/wd1s1e /var ufs rw 1 1 proc /proc procfs rw 0 0 /dev/wcd0c /cdrom cd9660 ro,noauto 0 0 /dev/wd0s1 /c msdos rw 0 0 /dev/wd1s1b none swap sw 0 0 /dev/wd0s2b none swap sw 0 0 -- Conrad Sabatier | FreeBSD -- UNIX for your PC http://www.neosoft.com/~conrads | Why settle for less than the best? Spambots, use this: biteme@f-u.org | http://www.freebsd.org From owner-freebsd-stable Tue Sep 16 21:08:11 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id VAA12019 for stable-outgoing; Tue, 16 Sep 1997 21:08:11 -0700 (PDT) Received: from silvia.HIP.Berkeley.EDU (wck-ca6-02.ix.netcom.com [199.35.213.194]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id VAA12014 for ; Tue, 16 Sep 1997 21:08:06 -0700 (PDT) Received: (from asami@localhost) by silvia.HIP.Berkeley.EDU (8.8.7/8.6.9) id VAA12718; Tue, 16 Sep 1997 21:08:03 -0700 (PDT) Date: Tue, 16 Sep 1997 21:08:03 -0700 (PDT) Message-Id: <199709170408.VAA12718@silvia.HIP.Berkeley.EDU> To: stable@FreeBSD.ORG In-reply-to: <199709151225.NAA03193@hawk.gnome.co.uk> (message from Chris Stenton on Mon, 15 Sep 1997 13:25:28 +0100) Subject: Re: Make buildworld fails in /usr/bin/tip . . . From: asami@cs.berkeley.edu (Satoshi Asami) Sender: owner-freebsd-stable@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Not to pick on you Chris, but this misinformation is getting posted far too often. * make includes * make world Let me just point (for the umpteenth time) out that there is no reason to do a "make includes" before "make world" now. If there is, it is a bug. Please let us know. And please do not post an encouragement to run a "make includes" to the mailing lists. The days that it was a solution are long gone. Satoshi From owner-freebsd-stable Tue Sep 16 22:27:47 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id WAA16743 for stable-outgoing; Tue, 16 Sep 1997 22:27:47 -0700 (PDT) Received: from GndRsh.aac.dev.com (GndRsh.aac.dev.com [198.145.92.241]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id WAA16737 for ; Tue, 16 Sep 1997 22:27:44 -0700 (PDT) Received: (from rgrimes@localhost) by GndRsh.aac.dev.com (8.8.5/8.7.3) id WAA08086; Tue, 16 Sep 1997 22:27:32 -0700 (PDT) From: "Rodney W. Grimes" Message-Id: <199709170527.WAA08086@GndRsh.aac.dev.com> Subject: Re: Make buildworld fails in /usr/bin/tip . . . In-Reply-To: <199709170408.VAA12718@silvia.HIP.Berkeley.EDU> from Satoshi Asami at "Sep 16, 97 09:08:03 pm" To: asami@cs.berkeley.edu (Satoshi Asami) Date: Tue, 16 Sep 1997 22:27:31 -0700 (PDT) Cc: stable@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL25 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > Not to pick on you Chris, but this misinformation is getting posted > far too often. > > * make includes > * make world > > Let me just point (for the umpteenth time) out that there is no reason > to do a "make includes" before "make world" now. If there is, it is a > bug. Please let us know. And please do not post an encouragement to > run a "make includes" to the mailing lists. The days that it was a > solution are long gone. > Not to be a butt head or anything, but I have to disagree, it _is_ the solution after I ftp /usr/lib from a just finished make world box and want /usr/include updated to match the /usr/src tarball I just extracted. Now you know why I was so asinine about ``make includes'' DTRT. -- Rod Grimes rgrimes@gndrsh.aac.dev.com Accurate Automation, Inc. Reliable computers for FreeBSD From owner-freebsd-stable Tue Sep 16 22:33:25 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id WAA17238 for stable-outgoing; Tue, 16 Sep 1997 22:33:25 -0700 (PDT) Received: from silvia.HIP.Berkeley.EDU (wck-ca6-02.ix.netcom.com [199.35.213.194]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id WAA17232 for ; Tue, 16 Sep 1997 22:33:22 -0700 (PDT) Received: (from asami@localhost) by silvia.HIP.Berkeley.EDU (8.8.7/8.6.9) id WAA16408; Tue, 16 Sep 1997 22:33:08 -0700 (PDT) Date: Tue, 16 Sep 1997 22:33:08 -0700 (PDT) Message-Id: <199709170533.WAA16408@silvia.HIP.Berkeley.EDU> To: rgrimes@GndRsh.aac.dev.com CC: stable@FreeBSD.ORG In-reply-to: <199709170527.WAA08086@GndRsh.aac.dev.com> (rgrimes@GndRsh.aac.dev.com) Subject: Re: Make buildworld fails in /usr/bin/tip . . . From: asami@cs.berkeley.edu (Satoshi Asami) Sender: owner-freebsd-stable@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk * > Let me just point (for the umpteenth time) out that there is no reason * > to do a "make includes" before "make world" now. If there is, it is a ^^^^^^^^^^^^^^^^^^ * Not to be a butt head or anything, but I have to disagree, it _is_ * the solution after I ftp /usr/lib from a just finished make world * box and want /usr/include updated to match the /usr/src tarball * I just extracted. Read my mail again, especially the underlined part. I am merely pointing out that "make includes" should not fix whatever problem "make world" is having that day. Satoshi From owner-freebsd-stable Tue Sep 16 23:47:10 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id XAA22979 for stable-outgoing; Tue, 16 Sep 1997 23:47:10 -0700 (PDT) Received: from adelphi.physics.adelaide.edu.au (adelphi.physics.adelaide.edu.au [129.127.36.247]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id XAA22787 for ; Tue, 16 Sep 1997 23:44:46 -0700 (PDT) Received: from bragg by adelphi.physics.adelaide.edu.au (5.65/AndrewR-930902) id AA03674; Mon, 15 Sep 1997 23:11:16 +0930 From: Kristian Kennaway Received: by bragg; (5.65/1.1.8.2/05Aug95-0227PM) id AA01622; Mon, 15 Sep 1997 23:11:16 +0930 Message-Id: <9709151341.AA01622@bragg> Subject: Re: Make buildworld fails in /usr/bin/tip . . . To: jacs@gnome.co.uk (Chris Stenton) Date: Mon, 15 Sep 1997 23:11:16 +0930 (CST) Cc: jkh@time.cdrom.com, werner@btp1da.phy.uni-bayreuth.de, stable@FreeBSD.ORG In-Reply-To: <199709151225.NAA03193@hawk.gnome.co.uk> from "Chris Stenton" at Sep 15, 97 01:25:28 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-freebsd-stable@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > > But now it fails with: > > > > No, that's a different problem - you are trying to build from an > > improperly bootstrapped tree. Use the world target. > > > > Jordan > > I have just done a :- > > make includes > make world > > and get the same problem as Werner Griessl. Ditto with my regular practise of cvsup, followed by make world. Kris From owner-freebsd-stable Wed Sep 17 01:08:53 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id BAA28107 for stable-outgoing; Wed, 17 Sep 1997 01:08:53 -0700 (PDT) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id BAA28098 for ; Wed, 17 Sep 1997 01:08:49 -0700 (PDT) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.5/8.6.9) id SAA07950; Wed, 17 Sep 1997 18:07:04 +1000 Date: Wed, 17 Sep 1997 18:07:04 +1000 From: Bruce Evans Message-Id: <199709170807.SAA07950@godzilla.zeta.org.au> To: asami@cs.berkeley.edu, rgrimes@GndRsh.aac.dev.com Subject: Re: Make buildworld fails in /usr/bin/tip . . . Cc: stable@FreeBSD.ORG Sender: owner-freebsd-stable@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >> Let me just point (for the umpteenth time) out that there is no reason >> to do a "make includes" before "make world" now. If there is, it is a >> ... >Not to be a butt head or anything, but I have to disagree, it _is_ >the solution after I ftp /usr/lib from a just finished make world >box and want /usr/include updated to match the /usr/src tarball >I just extracted. In that case, you should merge my fixes for this from -current to -stable :-). `make includes' never actually installed _all_ the includes. It still misses ss/ss_err.h in some cases because of a see-no-evil ifdef in libss/Makefile. Bruce From owner-freebsd-stable Wed Sep 17 01:36:44 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id BAA29918 for stable-outgoing; Wed, 17 Sep 1997 01:36:44 -0700 (PDT) Received: from GndRsh.aac.dev.com (GndRsh.aac.dev.com [198.145.92.241]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id BAA29909 for ; Wed, 17 Sep 1997 01:36:41 -0700 (PDT) Received: (from rgrimes@localhost) by GndRsh.aac.dev.com (8.8.5/8.7.3) id BAA08321; Wed, 17 Sep 1997 01:36:23 -0700 (PDT) From: "Rodney W. Grimes" Message-Id: <199709170836.BAA08321@GndRsh.aac.dev.com> Subject: Re: Make buildworld fails in /usr/bin/tip . . . In-Reply-To: <199709170807.SAA07950@godzilla.zeta.org.au> from Bruce Evans at "Sep 17, 97 06:07:04 pm" To: bde@zeta.org.au (Bruce Evans) Date: Wed, 17 Sep 1997 01:36:22 -0700 (PDT) Cc: asami@cs.berkeley.edu, stable@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL25 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > >> Let me just point (for the umpteenth time) out that there is no reason > >> to do a "make includes" before "make world" now. If there is, it is a > >> ... > >Not to be a butt head or anything, but I have to disagree, it _is_ > >the solution after I ftp /usr/lib from a just finished make world > >box and want /usr/include updated to match the /usr/src tarball > >I just extracted. > > In that case, you should merge my fixes for this from -current to > -stable :-). I'm waiting on on buildworld that has a src/Makefile -j1.144 -j1.145 to complete before commiting. [Note you have to hand patch this in, the cvs update -j won't work due to the fact Jordan backed out my change in the RELENG_2_2 branch only. :-(] > `make includes' never actually installed _all_ the > includes. It still misses ss/ss_err.h in some cases because of > a see-no-evil ifdef in libss/Makefile. > Yea, I know, I run into that every time I bootstrap a kerberous system with ``MAKE_EBONES=yes && make world''. Keep meaning to fix it, but I forget about it until the next time :-(. I'll go look at it right now and see what I come up with... > Bruce > -- Rod Grimes rgrimes@gndrsh.aac.dev.com Accurate Automation, Inc. Reliable computers for FreeBSD From owner-freebsd-stable Wed Sep 17 07:12:49 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id HAA13848 for stable-outgoing; Wed, 17 Sep 1997 07:12:49 -0700 (PDT) Received: from mailhost3.BayNetworks.COM (ns4.BayNetworks.COM [192.32.253.7]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id HAA13840 for ; Wed, 17 Sep 1997 07:12:46 -0700 (PDT) Received: from mailhost.BayNetworks.COM ([132.245.135.115] (may be forged)) by mailhost3.BayNetworks.COM (8.8.6/BNET-97/07/07-E) with ESMTP id KAA10861; Wed, 17 Sep 1997 10:21:12 -0400 (EDT) for Received: from pobox.engeast.BayNetworks.COM (pobox.engeast.baynetworks.com [192.32.151.199]) by mailhost.BayNetworks.COM (8.8.6/BNET-97/07/07-I) with ESMTP id KAA01267; Wed, 17 Sep 1997 10:12:13 -0400 (EDT) for Posted-Date: Wed, 17 Sep 1997 10:12:13 -0400 (EDT) Received: from tuva.engeast.baynetworks.com (tuva [192.32.180.119]) by pobox.engeast.BayNetworks.COM (SMI-8.6/BNET-97/04/24-S) with ESMTP id KAA18491; Wed, 17 Sep 1997 10:12:11 -0400 for Received: from tuva.engeast.baynetworks.com (localhost [127.0.0.1]) by tuva.engeast.baynetworks.com (8.8.3/8.8.3) with ESMTP id KAA09701; Wed, 17 Sep 1997 10:12:11 -0400 (EDT) Message-Id: <199709171412.KAA09701@tuva.engeast.baynetworks.com> X-Mailer: exmh version 2.0gamma 1/27/96 To: freebsd-stable@freebsd.org cc: bwithrow@tuva.engeast Subject: Minor problems with upcomming 2.2.5 Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 17 Sep 1997 10:12:11 -0400 From: Robert Withrow Sender: owner-freebsd-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I have great hopes of deploying FBSD 2.2.5 widely here in this SUNOS shop. To do this I would need to be able to have people install and run FBSD essentially ``out of the box''. To date this has not been possible for any prior version of FBSD due to various problems in the installation and in the code, stimulated by our environment---the largest problem areas have been with NFS and AMD, heavily used here. My testing of the September 14'th releng release is very encouraging. For one thing, it is the *first* version I have tested that has working AMD/NFS (for our environment) out-of-the-box! There are a few problems that I need to solve, and I hope the fixes can be integrated into the upcomming 2.2.5 release. 1) XFree86-3.3.1 won't install using the sysinstall program, either during or after the initial installation. I think Jordan is working on this. 2) I need the following patch to be made to rc.network. This is because *all* of our AMD maps are in NIS. Thus my rc.conf.local has a line like this: amd_flags='-c 3600 -l syslog `ypcat -k amd.master`' NOTE THE "'" quoting? That is *necessary* because NIS is not up at the time when rc.conf.local is sourced! The patch addes the necessary extra level of evaluation at the correct time (when AMD is being started and NIS is already up): *** rc.network~ Sun Sep 14 08:32:10 1997 --- rc.network Tue Sep 16 15:17:47 1997 *************** *** 186,192 **** if [ "X${amd_enable}" = X"YES" ]; then echo -n ' amd' ! amd -p ${amd_flags} > /var/run/amd.pid 2> /dev/null fi if [ "X${rwhod_enable}" = X"YES" ]; then --- 186,192 ---- if [ "X${amd_enable}" = X"YES" ]; then echo -n ' amd' ! eval amd -p ${amd_flags} > /var/run/amd.pid 2> /dev/null fi if [ "X${rwhod_enable}" = X"YES" ]; then 3) AMD uses up all process slots when it starts up in the GENERIC kernel because, I think, our master map has about 160 mounts, with about 140 of them being direct mounts. (I know the direct mounts suck, but I can't change the maps, because I need to interop with the SUNOS systems.) I have been dealing with this by building a kernel with "maxusers 30" but it whould be nice not to require the user to do that. I can imagine a few solutions: a) Have AMD throttle its process creation at startup. b) Have GENERIC go out with more process slots. c) Find a way to have a custom kernel be installed automatically, instead of GENERIC. Ideas? 4) I need to have passwd and group have the NIS ditties in them. I don't know how to cause this to happen at installation time. 5) I need to have other files be replaced at installation time with site specific ones. I want to have this be automatic. I don't yet know how to do this.. Thanks for any help you can offer... -- Robert Withrow -- (+1 508 916 8256) BWithrow@BayNetworks.com From owner-freebsd-stable Wed Sep 17 08:09:19 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id IAA17560 for stable-outgoing; Wed, 17 Sep 1997 08:09:19 -0700 (PDT) Received: from obie.softweyr.ml.org ([199.104.124.49]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id IAA17536 for ; Wed, 17 Sep 1997 08:09:13 -0700 (PDT) Received: (from wes@localhost) by obie.softweyr.ml.org (8.7.5/8.6.12) id JAA02121; Wed, 17 Sep 1997 09:12:11 -0600 (MDT) Date: Wed, 17 Sep 1997 09:12:11 -0600 (MDT) Message-Id: <199709171512.JAA02121@obie.softweyr.ml.org> From: Wes Peters To: Robert Withrow CC: stable@freebsd.org Subject: Minor problems with upcomming 2.2.5 In-Reply-To: <199709171412.KAA09701@tuva.engeast.baynetworks.com> References: <199709171412.KAA09701@tuva.engeast.baynetworks.com> Sender: owner-freebsd-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Robert Withrow writes: > I have great hopes of deploying FBSD 2.2.5 widely here in this SUNOS shop. > To do this I would need to be able to have people install and run > FBSD essentially ``out of the box''. To date this has not been possible > for any prior version of FBSD due to various problems in the installation > and in the code, stimulated by our environment---the largest problem > areas have been with NFS and AMD, heavily used here. I don't know that this is really something the FreeBSD team should concern themselves with -- customizing FreeBSD for your site. It seems to me the appropriate way to handle this would be to install the FreeBSD release on a "virgin" machine at your site, configure it exactly how you need it, including building a new kernel, etc., then create your own distribution media from that. You could, for instance, put all of the files on a machine and do ftp installs on all other machines. I've seen the procedure for making your own distribution set documented somewhere, but don't remember where. A search of the archives on the web site should help. > 2) I need the following patch to be made to rc.network. This is because > *all* of our AMD maps are in NIS. Thus my rc.conf.local has a line like > this: > > amd_flags='-c 3600 -l syslog `ypcat -k amd.master`' > > NOTE THE "'" quoting? That is *necessary* because NIS is not up at the > time when rc.conf.local is sourced! The patch addes the necessary extra > level of evaluation at the correct time (when AMD is being started and > NIS is already up): > > *** rc.network~ Sun Sep 14 08:32:10 1997 > --- rc.network Tue Sep 16 15:17:47 1997 > *************** > *** 186,192 **** > > if [ "X${amd_enable}" = X"YES" ]; then > echo -n ' amd' > ! amd -p ${amd_flags} > /var/run/amd.pid 2> /dev/null > fi > > if [ "X${rwhod_enable}" = X"YES" ]; then > --- 186,192 ---- > > if [ "X${amd_enable}" = X"YES" ]; then > echo -n ' amd' > ! eval amd -p ${amd_flags} > /var/run/amd.pid 2> /dev/null > fi > > if [ "X${rwhod_enable}" = X"YES" ]; then Sounds like this patch is needed for any setup using nis to distribute the amd maps to work. I don't think many FreeBSD users are heavily using amd and nis, so this is good test data. -- "Where am I, and what am I doing in this handbasket?" Wes Peters Softweyr LLC http://www.xmission.com/~softweyr softweyr@xmission.com From owner-freebsd-stable Wed Sep 17 08:17:11 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id IAA18245 for stable-outgoing; Wed, 17 Sep 1997 08:17:11 -0700 (PDT) Received: from mx1.cso.uiuc.edu (mx1.cso.uiuc.edu [128.174.5.37]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id IAA18240 for ; Wed, 17 Sep 1997 08:17:08 -0700 (PDT) Received: from alecto.physics.uiuc.edu (alecto.physics.uiuc.edu [128.174.83.167]) by mx1.cso.uiuc.edu (8.8.7/8.8.6) with SMTP id KAA12422; Wed, 17 Sep 1997 10:16:35 -0500 (CDT) Received: by alecto.physics.uiuc.edu (940816.SGI.8.6.9/940406.SGI) id KAA23225; Wed, 17 Sep 1997 10:11:33 -0500 From: igor@alecto.physics.uiuc.edu (Igor Roshchin) Message-Id: <199709171511.KAA23225@alecto.physics.uiuc.edu> Subject: Re: Error message while cvsup'ing RELENG_2_2 To: conrads@neosoft.com (Conrad Sabatier) Date: Wed, 17 Sep 1997 10:11:33 -0500 (CDT) Cc: jdp@polstra.com, stable@FreeBSD.ORG In-Reply-To: from "Conrad Sabatier" at Sep 16, 97 07:25:06 pm X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-freebsd-stable@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > > On 16-Sep-97 John Polstra wrote: > > > >> A-ha! I think we've found it! > >> > >> root:/usr/home/conrads# ls -l /usr/ports/games/angband/pkg/PLIST > >> br-srw--w- 1 8426901 8085310 52, 0x3934003a Dec 3 05:07 > >> /usr/ports/games/angband/pkg/PLIST > >> > >> I had a nasty system crash about a week ago. fsck had to do some rather > >> extensive cleaning up (thank goodness no serious damage). > > > >Was the filesystem mounted async at the time of the crash? I'm just > >curious. > > Um, I'm really not sure what that is, to be honest. :-) I just do a > normal mount on startup from fstab: > > > # Device Mountpoint FStype Options Dump Pass# > /dev/wd1a / ufs rw 1 1 > /dev/wd1s1f /usr ufs rw 1 1 > /dev/wd1s1e /var ufs rw 1 1 > proc /proc procfs rw 0 0 > /dev/wcd0c /cdrom cd9660 ro,noauto 0 0 > /dev/wd0s1 /c msdos rw 0 0 > /dev/wd1s1b none swap sw 0 0 > /dev/wd0s2b none swap sw 0 0 > > -- Since it was interesting for somebody - I had (two times) similar crashes - I mean with similar consequencies - after fsck I've got some files which became "special files" - (br-w..., cr-w... ) and once one of them happened to be /var/log/messages So, my system even could not tell me error messages. I had to go into single user mode and clean the inodes these files were using, because regular "rm" would not work on them THough, this happened on 2.1-STABLE with SCSI drives (I blamed on the well known bug in the driver for adaptec scsi cards) Sorry for such "off-topic". IgoR From owner-freebsd-stable Wed Sep 17 10:20:22 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id KAA25999 for stable-outgoing; Wed, 17 Sep 1997 10:20:22 -0700 (PDT) Received: from lafcol (lafcol.lafayette.edu [139.147.8.5]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id KAA25965; Wed, 17 Sep 1997 10:20:10 -0700 (PDT) Received: from bishop by lafcol (SMI-8.6/SMI-SVR4) id NAA08892; Wed, 17 Sep 1997 13:18:56 -0400 Message-Id: <3.0.32.19970917131842.00980410@lafcol.lafayette.edu> X-Sender: knollm@lafcol.lafayette.edu X-Mailer: Windows Eudora Pro Version 3.0 (32) Date: Wed, 17 Sep 1997 13:19:46 -0400 To: stable@freebsd.org, ports@freebsd.org From: Michael Knoll Subject: UNIXDED Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I have tried unixded(dedicated quake servers) for FreeBD, including the port(games/quakeserver) and all versions crash with a signal 11. I tried both the BSDi binaries, and the linux binaries. The QuakeWorld server for BSDi also crashes with a signal 11, but the QuakeWorld server for Linux perofrms fine. I'm not sure if this is a ports issue, or a stable issue, becuase I know a system admin runninng release that got both the linux and BSDi binaries working fine. Does anyone know what is going on? Why can't I get this port working? Thanks Michael From owner-freebsd-stable Wed Sep 17 10:56:50 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id KAA28394 for stable-outgoing; Wed, 17 Sep 1997 10:56:50 -0700 (PDT) Received: from mx3.cso.uiuc.edu (mx3.cso.uiuc.edu [128.174.5.24]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id KAA28385 for ; Wed, 17 Sep 1997 10:56:45 -0700 (PDT) Received: from alecto.physics.uiuc.edu (alecto.physics.uiuc.edu [128.174.83.167]) by mx3.cso.uiuc.edu (8.8.7/8.8.6) with SMTP id MAA27243 for <@mailhost.uiuc.edu:stable@freebsd.org>; Wed, 17 Sep 1997 12:55:59 -0500 (CDT) Received: by alecto.physics.uiuc.edu (940816.SGI.8.6.9/940406.SGI) for stable@freebsd.org id MAA00640; Wed, 17 Sep 1997 12:50:54 -0500 From: igor@alecto.physics.uiuc.edu (Igor Roshchin) Message-Id: <199709171750.MAA00640@alecto.physics.uiuc.edu> Subject: Default partitioning To: stable@freebsd.org Date: Wed, 17 Sep 1997 12:50:54 -0500 (CDT) X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-freebsd-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Mentioning the new release reminded me about a few questions/suggestions I have been having in mind for a long time. These are not the major issues, but still... 1. Standard /etc/crontab has an entry which does not always work! TO be more exact, it does not work once an year, and probably works twice a day also once an year. I am talking about : 0 2 * * * root /etc/daily 2>&1 | sendmail root Since the time switch from xST to xDT and back happen to be at 2 am, we have the problem mentioned above. I always change this time to some other. IMO, it is better to have nothing in the crontab to be run between 1 and 3 am. 2. Standard partitioning - when you install FreeBSD on a new box you have a choice to use some "Standard" partitioning. (here I use partion=slice - just FreeBSD's partitions/slices) Working with the systems which sometimes were installed by people who were not very knowledgable (or, I'd better say who knew less than me) about partitions and why do you need to have all those separate. So, by default one would get something like: Filesystem 1K-blocks Used Avail Capacity Mounted on /dev/wd0a 31775 16373 12860 56% / /dev/wd0s1f 1008815 325777 602333 35% /usr /dev/wd0s1e 29727 1811 25538 7% /var I think it is much more logical for the people who have disk which is big enough (say 1Gb and bigger) to have separate partition for /home rather than having /home on /usr Having /home on a separate partition would allow to mount that partition with -nosuid option (which is rather logical -- why would one want to have their users to have suid programs in their home directories) There are other reasons why one might want to have /home on a separate partition. Possible solution ? - One of them I can see is to make a new option there : default for a small disk (as it is now), and default for larger (>= 1G) disk. Regards! IgoR From owner-freebsd-stable Wed Sep 17 15:05:02 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id PAA14273 for stable-outgoing; Wed, 17 Sep 1997 15:05:02 -0700 (PDT) Received: from mailhost3.BayNetworks.COM (ns4.BayNetworks.COM [192.32.253.7]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id PAA14254 for ; Wed, 17 Sep 1997 15:04:56 -0700 (PDT) Received: from mailhost.BayNetworks.COM ([132.245.135.115] (may be forged)) by mailhost3.BayNetworks.COM (8.8.6/BNET-97/07/07-E) with ESMTP id SAA26423 Received: from pobox.engeast.BayNetworks.COM (pobox.engeast.baynetworks.com [192.32.151.199]) by mailhost.BayNetworks.COM (8.8.6/BNET-97/07/07-I) with ESMTP id SAA28285 Posted-Date: Wed, 17 Sep 1997 18:03:50 -0400 (EDT) Received: from tuva.engeast.baynetworks.com (tuva [192.32.180.119]) by pobox.engeast.BayNetworks.COM (SMI-8.6/BNET-97/04/24-S) with ESMTP id SAA25514; Wed, 17 Sep 1997 18:03:50 -0400 for Received: from tuva.engeast.baynetworks.com (localhost [127.0.0.1]) by tuva.engeast.baynetworks.com (8.8.3/8.8.3) with ESMTP id SAA11430; Wed, 17 Sep 1997 18:03:50 -0400 (EDT) Message-Id: <199709172203.SAA11430@tuva.engeast.baynetworks.com> X-Mailer: exmh version 2.0gamma 1/27/96 To: Wes Peters cc: Robert Withrow , stable@freebsd.org Subject: Re: Minor problems with upcomming 2.2.5 In-reply-to: Your message of "Wed, 17 Sep 1997 09:12:11 MDT." <199709171512.JAA02121@obie.softweyr.ml.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 17 Sep 1997 18:03:49 -0400 From: Robert Withrow Sender: owner-freebsd-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk softweyr@xmission.com said: :- I don't know that this is really something the FreeBSD team should :- concern themselves with -- customizing FreeBSD for your site. To be clear, that is *not* what I am asking. I think FreeBSD *should* be able to be installed, out of the box, and, with configuration, be able to run at this site. This has *not* been the case in the past because: 1) The installation process had bugs, and so you would have to fixup things post-install. 2) Certain modules in the kernel had to be replaced or patched, due to bugs. I'm not complaining... I understand these things happen. I'm simply saying that I can't ask users to patch and re-build kernels, and work around bugs in the installation disks. They tell me to get lost. ;-) So, my goal is two fold: 1) Help FreeBSD to get to the state where it *does* install and run without problems at this site, needing only local configuration. 2) Learn how to automatically provide this local customization for users. Only the first of these needs any attention from the FreeBSD team. Thanks! -- Robert Withrow -- (+1 508 916 8256) BWithrow@BayNetworks.com From owner-freebsd-stable Wed Sep 17 15:20:13 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id PAA15269 for stable-outgoing; Wed, 17 Sep 1997 15:20:13 -0700 (PDT) Received: from room101.sysc.com (jayrich@richmojm2.student.rose-hulman.edu [137.112.206.126]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id PAA15252; Wed, 17 Sep 1997 15:20:05 -0700 (PDT) Received: from localhost (jayrich@localhost) by room101.sysc.com (8.8.5/8.8.5) with SMTP id RAA00537; Wed, 17 Sep 1997 17:19:21 -0500 (EST) Date: Wed, 17 Sep 1997 17:19:21 -0500 (EST) From: "Jay M. Richmond" To: freebsd-stable@freebsd.org cc: freebsd-bugs@freebsd.org Subject: ATAPI CD-ROM functionality still missing from 2.2-stable Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hello-- A couple weeks ago I brought up the fact that ATAPI support in the 2.2-stable kernel was broken for me ... i received some other e-mail's from people that claimed that their cvsup'ed kernels lacked this functionality as well... i bring this back up again because i receieved no response from the freebsd team and i just tried a cvsup'ed 2.2-stable kernel as of today-- if there's something else i should be doing, please forgive my ignorance and let me know... (via e-mail, i don't subscribe to this list).. thanks. here's what happens: # mount -t cd9660 /dev/wcd0a /mnt/cdrom cd9660: /dev/wcd0a: Input/output error this happens with either /dev/wcd0a or /dev/wcd0c here's what /var/log/messages says: Sep 17 15:57:02 room101 /kernel: wdc1 at 0x170-0x177 irq 15 on isa Sep 17 15:57:02 room101 /kernel: wdc1: unit 1 (atapi): , removable, intr, dma, iordis Sep 17 15:57:02 room101 /kernel: wcd0: 1377Kb/sec, 256Kb cache, audio play, 255 volume levels, ejectable tray Sep 17 15:57:02 room101 /kernel: wcd0: no disc inside, unlocked thanks for your time & reply, jay __ Jay Richmond Owner, BDIC Consulting Group Box 1229 http://bdic.sysc.com Rose-Hulman Institute of Technology (317) 407-7701 5500 Wabash Avenue Rose-Hulman Terre Haute, IN 47803 (812) 877-8772 -----BEGIN PGP PUBLIC KEY BLOCK----- Version: 2.6.2 mQCNAzQe9IMAAAEEAKVCBVhfVHCyNOsNvCwXbamYDslPoBoUgllJxGWrjYr8+XOS mAIo6VNyR6E0Q57SICfxAlw8CfrW3jSFZxCalyAr7f4SU/ioF7qOx9AEeRePKbQD XQYT/eUirjo4h1TzQPWMrlGtnehTJfX4LKLeu8WRsMog/6LMzxBohdeuTAY9AAUR tCJKYXkgTS4gUmljaG1vbmQgPGpheXJpY2hAc3lzYy5jb20+ =PTZq -----END PGP PUBLIC KEY BLOCK----- From owner-freebsd-stable Wed Sep 17 18:21:41 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id SAA24714 for stable-outgoing; Wed, 17 Sep 1997 18:21:41 -0700 (PDT) Received: from uop.cs.uop.edu (uop.cs.uop.edu [138.9.200.1]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id SAA24704 for ; Wed, 17 Sep 1997 18:21:37 -0700 (PDT) Received: (from bford@localhost) by uop.cs.uop.edu (8.8.5/8.7.3) id SAA01555 for freebsd-stable@freebsd.org; Wed, 17 Sep 1997 18:21:31 -0700 (PDT) From: Bret Ford Message-Id: <199709180121.SAA01555@uop.cs.uop.edu> Subject: PPP issues To: freebsd-stable@freebsd.org Date: Wed, 17 Sep 1997 18:21:29 -0700 (PDT) X-Anon-Password: foobiebletch MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Greetings, I've been tracking FreeBSD-stable for a couple of weeks now, and I've have two difficulties. I have an 486DX/2 66mhz that I'm using as a gateway to the internet for the machines at our house. An ISDN interface, running at 230K, is connected to a Byterunner card with 2 16650 UARTS. Using user PPP with -alias, 2 desktops and a portable over our little LAN are sharing the ISDN adapter and generally, everything is great. However, I'm getting periodic "silo overflow" messages. I notice them, in particular, when I'm cvsup'ing the source tree. An initial patch of 2.2.2-RELEASE yielded a couple hundred such errors, but nothing fatal. Am I missing a kernel parameter, or other change to the source tree, that might resolve this problem? The other problem I've had has occured only in FreeBSD-stable. Under -release, I was able to do "ppp -alias provider >& /dev/null &" to start a session. When trying that under -stable, I get a message from ppp saying "exception detected." and no connection. Is this a "feature" that has been corrected? This generally isn't a problem, because the dumb terminal I use as a console from com1 on the Byterunner generally isn't fiddled with while we're connected. Thanks for any help ye can give. (BTW, to the FreeBSD wizards in the dev. team: Kudos on a great OS!) Bret Ford From owner-freebsd-stable Wed Sep 17 18:50:34 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id SAA26183 for stable-outgoing; Wed, 17 Sep 1997 18:50:34 -0700 (PDT) Received: from room101.sysc.com (jayrich@richmojm2.student.rose-hulman.edu [137.112.206.126]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id SAA26177 for ; Wed, 17 Sep 1997 18:50:27 -0700 (PDT) Received: from localhost (jayrich@localhost) by room101.sysc.com (8.8.7/8.8.5) with SMTP id UAA00924 for ; Wed, 17 Sep 1997 20:49:39 -0500 (EST) Date: Wed, 17 Sep 1997 20:49:34 -0500 (EST) From: "Jay M. Richmond" To: freebsd-stable@freebsd.org Subject: anyone else ? atapi headaches? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk is anyone else besides those I've talked to having problems with their atapi cd-rom (input/output errors when mounting)...? or are there people with cd-rom's that are working fine out there... i'm talking about a recently cvsup'ed 2.2-stable kernel... thanks, jay __ Jay Richmond Owner, BDIC Consulting Group Box 1229 http://bdic.sysc.com Rose-Hulman Institute of Technology (317) 407-7701 5500 Wabash Avenue Rose-Hulman Terre Haute, IN 47803 (812) 877-8772 -----BEGIN PGP PUBLIC KEY BLOCK----- Version: 2.6.2 mQCNAzQe9IMAAAEEAKVCBVhfVHCyNOsNvCwXbamYDslPoBoUgllJxGWrjYr8+XOS mAIo6VNyR6E0Q57SICfxAlw8CfrW3jSFZxCalyAr7f4SU/ioF7qOx9AEeRePKbQD XQYT/eUirjo4h1TzQPWMrlGtnehTJfX4LKLeu8WRsMog/6LMzxBohdeuTAY9AAUR tCJKYXkgTS4gUmljaG1vbmQgPGpheXJpY2hAc3lzYy5jb20+ =PTZq -----END PGP PUBLIC KEY BLOCK----- From owner-freebsd-stable Wed Sep 17 19:01:06 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id TAA26663 for stable-outgoing; Wed, 17 Sep 1997 19:01:06 -0700 (PDT) Received: from helium.vapornet.com (root@helium.vapornet.com [208.202.126.112]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id TAA26652 for ; Wed, 17 Sep 1997 19:01:02 -0700 (PDT) Received: from argon.vapornet.com (chicago1-3.ebs.net [207.19.130.67]) by helium.vapornet.com (8.8.7/VaporServer-v3.0+SpamNot) with ESMTP id VAA00504 for ; Wed, 17 Sep 1997 21:01:26 -0500 (CDT) Received: by argon.vapornet.com (8.8.7/VaporClient-1.1) id VAA00693; Wed, 17 Sep 1997 21:01:04 -0500 (CDT) Date: Wed, 17 Sep 1997 21:01:04 -0500 (CDT) Message-Id: <199709180201.VAA00693@argon.vapornet.com> From: John Preisler MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: freebsd-stable@freebsd.org Subject: problem with ipfirewall changes X-Mailer: VM 6.22 under 19.15 XEmacs Lucid Sender: owner-freebsd-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk danny 1997/09/14 16:35:27 PDT Modified files: (Branch: RELENG_2_2) etc rc.conf rc.firewall rc.network Log: MFC - firewall initialization cosmetics. Revision Changes Path 1.1.2.20 +4 -2 src/etc/rc.conf 1.6.2.3 +56 -44 src/etc/rc.firewall 1.1.2.10 +32 -5 src/etc/rc.network made world overnight last night. Everything went fine except where rc.network decides whether i'm running ipfirewall in the kernel or loadable module. this clip from dmesg shows that kernel firewall support gets loaded as I configured it, but rc.network forces the module to load anyway. changing root device to sd0a IP packet filtering initialized, divert disabled, logging limited to 50 packets/entry de0: enabling 10baseT port IP packet filtering initialized, divert disabled, logging disabled rfork() call disabled Type Id Off Loadaddr Size Info Rev Module Name MISC 0 0 f634d000 000c f634f018 1 ipfw_mod also rc.i386 also tries to launch moused even though rc.conf says moused="NO" Console message complains of -t being bogus flag -jrp From owner-freebsd-stable Wed Sep 17 20:40:59 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id UAA02133 for stable-outgoing; Wed, 17 Sep 1997 20:40:59 -0700 (PDT) Received: from venus.net (venus.net [205.243.72.10]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id UAA02128 for ; Wed, 17 Sep 1997 20:40:56 -0700 (PDT) Received: from localhost (ve1-p1.venus.net [205.243.75.4]) by venus.net (8.7.1/8.7.3) with SMTP id XAA22119; Wed, 17 Sep 1997 23:46:22 -0400 (EDT) Date: Wed, 17 Sep 1997 22:40:43 -0500 (EST) From: Andre LeClaire X-Sender: leclaire@localhost To: "Jay M. Richmond" cc: freebsd-stable@FreeBSD.ORG Subject: Re: anyone else ? atapi headaches? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > is anyone else besides those I've talked to having problems with their > atapi cd-rom (input/output errors when mounting)...? or are there people > with cd-rom's that are working fine out there... > > i'm talking about a recently cvsup'ed 2.2-stable kernel... Well, I just tried mount /cdrom (actually hadn't tried it in a while), and got "cd9660: /dev/wcd0c: Device not configured"! So I looked at dmesg, and noticed "wdc1 not found at 0x170". This after cvsup this morning and make world today. Andre From owner-freebsd-stable Wed Sep 17 20:47:54 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id UAA02416 for stable-outgoing; Wed, 17 Sep 1997 20:47:54 -0700 (PDT) Received: from room101.sysc.com (jayrich@richmojm2.student.rose-hulman.edu [137.112.206.126]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id UAA02403 for ; Wed, 17 Sep 1997 20:47:46 -0700 (PDT) Received: from localhost (jayrich@localhost) by room101.sysc.com (8.8.7/8.8.5) with SMTP id WAA01124; Wed, 17 Sep 1997 22:46:46 -0500 (EST) Date: Wed, 17 Sep 1997 22:46:45 -0500 (EST) From: "Jay M. Richmond" To: Andre LeClaire cc: freebsd-stable@FreeBSD.ORG Subject: Re: anyone else ? atapi headaches? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk I also try to compile mount_cd9660 and get errors about ssector... --jay __ Jay Richmond Owner, BDIC Consulting Group Box 1229 http://bdic.sysc.com Rose-Hulman Institute of Technology (317) 407-7701 5500 Wabash Avenue Rose-Hulman Terre Haute, IN 47803 (812) 877-8772 -----BEGIN PGP PUBLIC KEY BLOCK----- Version: 2.6.2 mQCNAzQe9IMAAAEEAKVCBVhfVHCyNOsNvCwXbamYDslPoBoUgllJxGWrjYr8+XOS mAIo6VNyR6E0Q57SICfxAlw8CfrW3jSFZxCalyAr7f4SU/ioF7qOx9AEeRePKbQD XQYT/eUirjo4h1TzQPWMrlGtnehTJfX4LKLeu8WRsMog/6LMzxBohdeuTAY9AAUR tCJKYXkgTS4gUmljaG1vbmQgPGpheXJpY2hAc3lzYy5jb20+ =PTZq -----END PGP PUBLIC KEY BLOCK----- On Wed, 17 Sep 1997, Andre LeClaire wrote: > > is anyone else besides those I've talked to having problems with their > > atapi cd-rom (input/output errors when mounting)...? or are there people > > with cd-rom's that are working fine out there... > > > > i'm talking about a recently cvsup'ed 2.2-stable kernel... > > Well, I just tried mount /cdrom (actually hadn't tried it in a while), and > got "cd9660: /dev/wcd0c: Device not configured"! So I looked at dmesg, > and noticed "wdc1 not found at 0x170". This after cvsup this morning and > make world today. > > Andre > > From owner-freebsd-stable Wed Sep 17 23:32:08 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id XAA10981 for stable-outgoing; Wed, 17 Sep 1997 23:32:08 -0700 (PDT) Received: from awfulhak.demon.co.uk (awfulhak.demon.co.uk [158.152.17.1]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id XAA10957 for ; Wed, 17 Sep 1997 23:31:59 -0700 (PDT) Received: from gate.lan.awfulhak.org (localhost [127.0.0.1]) by awfulhak.demon.co.uk (8.8.5/8.8.5) with ESMTP id HAA10549; Thu, 18 Sep 1997 07:28:58 +0100 (BST) Message-Id: <199709180628.HAA10549@awfulhak.demon.co.uk> X-Mailer: exmh version 2.0zeta 7/24/97 To: Bret Ford cc: freebsd-stable@FreeBSD.ORG Subject: Re: PPP issues In-reply-to: Your message of "Wed, 17 Sep 1997 18:21:29 PDT." <199709180121.SAA01555@uop.cs.uop.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 18 Sep 1997 07:28:58 +0100 From: Brian Somers Sender: owner-freebsd-stable@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk [.....] > The other problem I've had has occured only in FreeBSD-stable. > Under -release, I was able to do "ppp -alias provider >& /dev/null &" [.....] Mmmm, "ppp -alias provider" *never* did anything except give you an interactive session. Do you mean "ppp -alias -auto provider" ? > Bret Ford -- Brian , , Don't _EVER_ lose your sense of humour.... From owner-freebsd-stable Thu Sep 18 02:03:33 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id CAA20335 for stable-outgoing; Thu, 18 Sep 1997 02:03:33 -0700 (PDT) Received: from salmon.maths.tcd.ie (mmdf@salmon.maths.tcd.ie [134.226.81.11]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id CAA20330 for ; Thu, 18 Sep 1997 02:03:29 -0700 (PDT) Received: from graves.maths.tcd.ie by salmon.maths.tcd.ie with SMTP id aa12120; 18 Sep 97 10:03 +0100 To: "Jay M. Richmond" cc: freebsd-stable@freebsd.org Subject: Re: anyone else ? atapi headaches? In-reply-to: Your message of "Wed, 17 Sep 1997 20:49:34 CDT." Date: Thu, 18 Sep 1997 10:03:26 +0100 From: David Malone Message-ID: <9709181003.aa12120@salmon.maths.tcd.ie> Sender: owner-freebsd-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > is anyone else besides those I've talked to having problems with their > atapi cd-rom (input/output errors when mounting)...? or are there people > with cd-rom's that are working fine out there... Last time I checked my ATAPI CD rom worked fine (last week sometime I think). I think you also said that you tried to recompile mount_cd9660 and it failed. Joerg did mail to the list recently saying that if you rebuild mount_cd9660 you would have to rebuild the kernel. The reverse may well apply. You may have to do enough of a buildworld to make cd9660 compile before you can get it to work. I'm not sure if you have ever got this drive to work, you didn't say. About the time of 2.2.2 there was a statement (by Jordan?) that said if people had ATAPI problems they wanted fixing they should provide a drive just like the one they were having problems with to whoever was in charge of the ATAPI code at the time, and then maybe they would be able to fix it. Mind you - if you've had the drive working, that may mean someone has just accidently broken something - in which case the above mightn't apply. David. From owner-freebsd-stable Thu Sep 18 06:38:32 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id GAA06062 for stable-outgoing; Thu, 18 Sep 1997 06:38:32 -0700 (PDT) Received: from cyber3.servtech.com (root@cyber3.servtech.com [199.1.22.25]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id GAA06057 for ; Thu, 18 Sep 1997 06:38:28 -0700 (PDT) Received: from pr-comm.com (root@prcomm.roc.servtech.com [204.181.3.14]) by cyber3.servtech.com (8.8.6/8.8.5) with ESMTP id JAA06679 for ; Thu, 18 Sep 1997 09:38:19 -0400 (EDT) Received: from pr-comm.com (housley@localhost [127.0.0.1]) by pr-comm.com (8.8.7/8.8.7) with ESMTP id JAA03122 for ; Thu, 18 Sep 1997 09:38:06 -0400 (EDT) Message-ID: <34212EBC.4C9A9791@pr-comm.com> Date: Thu, 18 Sep 1997 09:38:04 -0400 From: "James E. Housley" Organization: PR Communications, Inc. X-Mailer: Mozilla 4.02b7 [en] (X11; I; FreeBSD 2.2-STABLE i386) MIME-Version: 1.0 To: freebsd-stable@FreeBSD.ORG Subject: Problem with new rc.firewall Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk I am using ctm-src-2_2 to keep current. The last update I compiled include src/etc/rc.firewall: Revision Path 1.6.2.3 src/etc/rc.firewall I have my own firewall configuration so I edited the file to be of the form: add deny all from 192.168.0.0:255.255.0.0 to any in via tun0 add deny all from 204.181.2.0:255.255.255.0 to any in via tun0 etc... the file is: -rw-r--r-- 1 root wheel 1943 Sep 17 15:03 firewall.ocean rc.conf: firewall_enable="YES" firewall_type="/etc/firewall.ocean" firewall_quiet="NO" If I, as root, do a /sbin/ipfw /etc/firewall.ocean it loads the rules correctly. However when the machine boots I get: usage: ipfw [options] flush add [number] rule delete number ... list [number] show [number] zero [number ...] rule: action proto src dst extras... action: {allow|permit|accept|pass|deny|drop|reject|unreach code| reset|count|skipto num|divert port|tee port} [log] proto: {ip|tcp|udp|icmp|} src: from [not] {any|ip[{/bits|:mask}]} [{port|port-port},[port],...] dst: to [not] {any|ip[{/bits|:mask}]} [{port|port-port},[port],...] extras: fragment in out {xmit|recv|via} {iface|ip|any} {established|setup} tcpflags [!]{syn|fin|rst|ack|psh|urg},... ipoptions [!]{ssrr|lsrr|rr|ts},... icmptypes {type[,type]}... Also I think this is wrong: elif [ "${firewall_type}" != "NONE" -a -r "${firewall_type}" ]; then - $fwcmd ${firewall} + $fwcmd ${firewall_type} fi I changed it but it still didn't work as expected. Jim -- -------------------------------------------+------------------------- James E. Housley | PGP: 1024/03983B4D PR Communications, Inc. | 2C 3F 3A 0D A8 D8 C3 13 www.servtech.com/public/pr-comm | 7C F0 B5 BF 27 8B 92 FE From owner-freebsd-stable Thu Sep 18 07:25:21 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id HAA08787 for stable-outgoing; Thu, 18 Sep 1997 07:25:21 -0700 (PDT) Received: from uop.cs.uop.edu (uop.cs.uop.edu [138.9.200.1]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id HAA08780 for ; Thu, 18 Sep 1997 07:25:18 -0700 (PDT) Received: from heather.my.domain (user227.pop2.cwia.com [208.135.61.227]) by uop.cs.uop.edu (8.8.5/8.7.3) with SMTP id HAA09487 for ; Thu, 18 Sep 1997 07:25:12 -0700 (PDT) Message-Id: <199709181425.HAA09487@uop.cs.uop.edu> From: "Bret Ford" To: Subject: Re: PPP issues Date: Thu, 18 Sep 1997 07:24:52 -0700 MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 4.71.1008.3 X-MimeOle: Produced By Microsoft MimeOLE Engine V4.71.1008.3 Sender: owner-freebsd-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >[.....] >> The other problem I've had has occured only in FreeBSD-stable. >> Under -release, I was able to do "ppp -alias provider >& /dev/null &" >[.....] > >Mmmm, "ppp -alias provider" *never* did anything except give you an >interactive session. Do you mean "ppp -alias -auto provider" ? > No, I haven't tried it as anything other than an interactive session. I had previously been able to chuck the output into null, as above. Haven't ventured into -auto, -background, etc. Bret Ford From owner-freebsd-stable Thu Sep 18 08:19:39 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id IAA12279 for stable-outgoing; Thu, 18 Sep 1997 08:19:39 -0700 (PDT) Received: from venus.net (venus.net [205.243.72.10]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id IAA12274 for ; Thu, 18 Sep 1997 08:19:36 -0700 (PDT) Received: from localhost (ve1-p0.venus.net [205.243.75.3]) by venus.net (8.7.1/8.7.3) with SMTP id LAA03425; Thu, 18 Sep 1997 11:24:59 -0400 (EDT) Date: Thu, 18 Sep 1997 10:19:22 -0500 (EST) From: Andre LeClaire X-Sender: leclaire@localhost To: "Jay M. Richmond" cc: freebsd-stable@FreeBSD.ORG Subject: Re: anyone else ? atapi headaches? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > > is anyone else besides those I've talked to having problems with their > > > atapi cd-rom (input/output errors when mounting)...? or are there people > > > with cd-rom's that are working fine out there... > > > > > > i'm talking about a recently cvsup'ed 2.2-stable kernel... > > > > Well, I just tried mount /cdrom (actually hadn't tried it in a while), and > > got "cd9660: /dev/wcd0c: Device not configured"! So I looked at dmesg, > > and noticed "wdc1 not found at 0x170". This after cvsup this morning and > > make world today. > > I also try to compile mount_cd9660 and get errors about ssector... Upon further investigation, my problem was self-inflicted. I had swapped some memory with another computer I was working on, and must have bumped the ribbon cable from the cdrom drive to the motherboard. So, I am glad to report my ATAPI cdrom is working fine now. It's a Mitsumi FX410A quad speed drive, and I've been using it with FreeBSD since 2.1.5. It's set up as the master drive on the second ide controller. I have seen some messages from people who had trouble getting FreeBSD to work with certain ATAPI drives, though. What model do you have? Andre From owner-freebsd-stable Thu Sep 18 09:03:39 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id JAA15206 for stable-outgoing; Thu, 18 Sep 1997 09:03:39 -0700 (PDT) Received: from room101.sysc.com (jayrich@richmojm2.student.rose-hulman.edu [137.112.206.126]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id JAA15185 for ; Thu, 18 Sep 1997 09:03:24 -0700 (PDT) Received: from localhost (jayrich@localhost) by room101.sysc.com (8.8.7/8.8.5) with SMTP id LAA16545; Thu, 18 Sep 1997 11:02:38 -0500 (EST) Date: Thu, 18 Sep 1997 11:02:38 -0500 (EST) From: "Jay M. Richmond" To: Andre LeClaire cc: freebsd-stable@FreeBSD.ORG Subject: Re: anyone else ? atapi headaches? .solved. In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Fortunately, I was able to fix the problem by recompiling mount_cd9660... apparently I only upgraded the kernel and should have upgraded this as well... thanks for all the help guys. -jay __ Jay Richmond Owner, BDIC Consulting Group Box 1229 http://bdic.sysc.com Rose-Hulman Institute of Technology (317) 407-7701 5500 Wabash Avenue Rose-Hulman Terre Haute, IN 47803 (812) 877-8772 -----BEGIN PGP PUBLIC KEY BLOCK----- Version: 2.6.2 mQCNAzQe9IMAAAEEAKVCBVhfVHCyNOsNvCwXbamYDslPoBoUgllJxGWrjYr8+XOS mAIo6VNyR6E0Q57SICfxAlw8CfrW3jSFZxCalyAr7f4SU/ioF7qOx9AEeRePKbQD XQYT/eUirjo4h1TzQPWMrlGtnehTJfX4LKLeu8WRsMog/6LMzxBohdeuTAY9AAUR tCJKYXkgTS4gUmljaG1vbmQgPGpheXJpY2hAc3lzYy5jb20+ =PTZq -----END PGP PUBLIC KEY BLOCK----- On Thu, 18 Sep 1997, Andre LeClaire wrote: > > > > is anyone else besides those I've talked to having problems with their > > > > atapi cd-rom (input/output errors when mounting)...? or are there people > > > > with cd-rom's that are working fine out there... > > > > > > > > i'm talking about a recently cvsup'ed 2.2-stable kernel... > > > > > > Well, I just tried mount /cdrom (actually hadn't tried it in a while), and > > > got "cd9660: /dev/wcd0c: Device not configured"! So I looked at dmesg, > > > and noticed "wdc1 not found at 0x170". This after cvsup this morning and > > > make world today. > > > > I also try to compile mount_cd9660 and get errors about ssector... > > Upon further investigation, my problem was self-inflicted. I had swapped > some memory with another computer I was working on, and must have bumped > the ribbon cable from the cdrom drive to the motherboard. So, I am glad > to report my ATAPI cdrom is working fine now. It's a Mitsumi FX410A quad > speed drive, and I've been using it with FreeBSD since 2.1.5. It's set up > as the master drive on the second ide controller. > I have seen some messages from people who had trouble getting FreeBSD to > work with certain ATAPI drives, though. What model do you have? > > Andre > > From owner-freebsd-stable Thu Sep 18 09:35:29 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id JAA17458 for stable-outgoing; Thu, 18 Sep 1997 09:35:29 -0700 (PDT) Received: from ime.net (root@ime.net [209.90.192.3]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id JAA17452 for ; Thu, 18 Sep 1997 09:35:22 -0700 (PDT) Received: from shell.ime.net (rstan@shell.ime.net [209.90.192.5]) by ime.net (8.8.7/8.8.7) with SMTP id MAA13231 for ; Thu, 18 Sep 1997 12:35:20 -0400 (EDT) Date: Thu, 18 Sep 1997 12:35:19 -0400 (EDT) From: Richard Stanaford To: freebsd-stable@freebsd.org Subject: First reboot after installation... Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hello all, Please be aware that I am not currently subscribed to this list. If you respond please be sure to CC it to my email, rstan@ime.net with instruction on how to subscribe. :) Thank you. I am having a problem with FreeBSD 2.2.2. I had elected to do the FTP installation and things seem to go fine. Using the holographic shell on tty4, I even go through the file system as it is being built and everything looks fine. I chose to do the minimal installation and then I would add XFree86, doc, sources, and so on at a later time. I get to the point where the download is completed and I am told that my machine will reboot and start FreeBSD from the hard disk. As my machine is booting up, the devices are probed as you would expect. But then I see this message : /etc/rc: Can't open /etc/rc init: /etc/spwd.db: No such file or directory Enter pathname of shell or RETURN for sh: Uhm... what is that? :) Then, when I perform a "df" to see my disk utilization, all I see is : root_device "some stuff about usage" / My mount points are gone. I have tried this both with Win95 and FreeBSD sharing the HD, and with FreeBSD claiming the entire disk, both with the same results. Any info would be appreciated. Thank you, - Richard From owner-freebsd-stable Thu Sep 18 11:28:15 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id LAA25660 for stable-outgoing; Thu, 18 Sep 1997 11:28:15 -0700 (PDT) Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id LAA25651 for ; Thu, 18 Sep 1997 11:28:12 -0700 (PDT) Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.7/8.6.9) with ESMTP id LAA11060; Thu, 18 Sep 1997 11:28:17 -0700 (PDT) To: Richard Stanaford Cc: freebsd-stable@freebsd.org Subject: Re: First reboot after installation... In-reply-to: Your message of "Thu, 18 Sep 1997 12:35:19 EDT." Date: Thu, 18 Sep 1997 11:28:16 -0700 Message-ID: <11057.874607296@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk You must have somehow not selected the bin dist or your root or /usr were too small and overflowed. I can think of no other rational explanation for that error. This should have also gone to -questions, not -stable. This mailing list is _not_ for the discussion of installation problems. Thanks. Jordan > > Hello all, > > Please be aware that I am not currently subscribed to this list. If you > respond please be sure to CC it to my email, rstan@ime.net with > instruction on how to subscribe. :) Thank you. > > I am having a problem with FreeBSD 2.2.2. I had elected to do the > FTP installation and things seem to go fine. Using the holographic shell > on tty4, I even go through the file system as it is being built and > everything looks fine. I chose to do the minimal installation and then I > would add XFree86, doc, sources, and so on at a later time. I get to the > point where the download is completed and I am told that my machine will > reboot and start FreeBSD from the hard disk. As my machine is booting up, > the devices are probed as you would expect. But then I see this message : > > /etc/rc: Can't open /etc/rc > init: /etc/spwd.db: No such file or directory > Enter pathname of shell or RETURN for sh: > > Uhm... what is that? :) Then, when I perform a "df" to see my disk > utilization, all I see is : > > root_device "some stuff about usage" / > > My mount points are gone. I have tried this both with Win95 and FreeBSD > sharing the HD, and with FreeBSD claiming the entire disk, both with the > same results. Any info would be appreciated. > > Thank you, > - Richard > > From owner-freebsd-stable Thu Sep 18 14:08:18 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id OAA06859 for stable-outgoing; Thu, 18 Sep 1997 14:08:18 -0700 (PDT) Received: from austin.polstra.com (austin.polstra.com [206.213.73.10]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id OAA06853 for ; Thu, 18 Sep 1997 14:08:15 -0700 (PDT) Received: from austin.polstra.com (jdp@localhost) by austin.polstra.com (8.8.7/8.8.5) with ESMTP id OAA09275; Thu, 18 Sep 1997 14:06:18 -0700 (PDT) Message-Id: <199709182106.OAA09275@austin.polstra.com> To: Conrad Sabatier cc: stable@freebsd.org Subject: Re: Error message while cvsup'ing RELENG_2_2 In-reply-to: Your message of "Tue, 16 Sep 1997 19:25:06 CDT." Date: Thu, 18 Sep 1997 14:06:18 -0700 From: John Polstra Sender: owner-freebsd-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > >Was the filesystem mounted async at the time of the crash? I'm > >just curious. > > Um, I'm really not sure what that is, to be honest. :-) It is a special option you can use to mount a filesystem. It makes operations on the files and directories substantially faster, but it also creates a real risk of losing data (maybe a lot of data) if there is a power failure or system crash. I personally don't recommend using it. > I just do a normal mount on startup from fstab: > > > # Device Mountpoint FStype Options Dump Pass# > /dev/wd1a / ufs rw 1 1 > /dev/wd1s1f /usr ufs rw 1 1 > /dev/wd1s1e /var ufs rw 1 1 > proc /proc procfs rw 0 0 > /dev/wcd0c /cdrom cd9660 ro,noauto 0 0 > /dev/wd0s1 /c msdos rw 0 0 > /dev/wd1s1b none swap sw 0 0 > /dev/wd0s2b none swap sw 0 0 You're not using async mounts, then. (Good!) They are enabled by adding "async" to the list of options. John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Self-knowledge is always bad news." -- John Barth From owner-freebsd-stable Thu Sep 18 15:07:08 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id PAA11145 for stable-outgoing; Thu, 18 Sep 1997 15:07:08 -0700 (PDT) Received: from vinyl.quickweb.com (vinyl.quickweb.com [206.222.77.8]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id PAA11130 for ; Thu, 18 Sep 1997 15:06:59 -0700 (PDT) Received: (from mark@localhost) by vinyl.quickweb.com (8.8.5/8.6.12) id SAA15795; Thu, 18 Sep 1997 18:06:32 -0400 (EDT) Message-ID: <19970918180632.16270@vinyl.quickweb.com> Date: Thu, 18 Sep 1997 18:06:32 -0400 From: Mark Mayo To: John Polstra Cc: Conrad Sabatier , stable@FreeBSD.ORG Subject: Re: Error message while cvsup'ing RELENG_2_2 References: <199709182106.OAA09275@austin.polstra.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.81e In-Reply-To: <199709182106.OAA09275@austin.polstra.com>; from John Polstra on Thu, Sep 18, 1997 at 02:06:18PM -0700 Sender: owner-freebsd-stable@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Thu, Sep 18, 1997 at 02:06:18PM -0700, John Polstra wrote: > > >Was the filesystem mounted async at the time of the crash? I'm > > >just curious. > > > > Um, I'm really not sure what that is, to be honest. :-) > > It is a special option you can use to mount a filesystem. It makes > operations on the files and directories substantially faster, but it > also creates a real risk of losing data (maybe a lot of data) if > there is a power failure or system crash. I personally don't > recommend using it. If you're using a UPS, I don't see the risk in using the async option. >From my own experience, it does make a *dramatic* difference in FS performance. In the end though, I mount without async on servers since I'm too afraid of what would happen in a big crash. On my workstation I use async all the time though - I've experimented with power failures and async and like you said, you will probably loose any files that were being written to when the power died. But a power failure while the system is inactive seems to cause no damage (for example, I leave my machine on all the time at home, and sometimes there are small power failures at night). Now that I have a UPS at home, I feel much better though :-) Still, every day I think about mounting -async on the servers.. The server machines I look after aren't terribly busy, and in the 2 years or so I've been using FreeBSD on them I've never had a system crash. That combined with the gigantic UPS's that power the machines makes be think that the chances of something actually going wrong and loosing data on an async mounted FS is very, very small. Probably more likely that something would physically go wrong with the machine or HD causing data loss - and that's what the backup tapes are for! :-) cya, -mark > John D. Polstra & Co., Inc. Seattle, Washington USA > "Self-knowledge is always bad news." -- John Barth -- ------------------------------------------------------------------------ Mark Mayo mark@quickweb.com RingZero Comp. http://vinyl.quickweb.com/mark finger mark@quickweb.com for my PGP key and GCS code ------------------------------------------------------------------------ "The newest book, The Dilbert Future, took a broader view, describing how idiots will threaten every aspect of business, technology and society in the future." --Scott Adams From owner-freebsd-stable Thu Sep 18 18:52:48 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id SAA28023 for stable-outgoing; Thu, 18 Sep 1997 18:52:48 -0700 (PDT) Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id SAA28015 for ; Thu, 18 Sep 1997 18:52:44 -0700 (PDT) Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.7/8.6.9) with ESMTP id SAA17272; Thu, 18 Sep 1997 18:52:52 -0700 (PDT) To: Robert Withrow cc: freebsd-stable@FreeBSD.ORG, bwithrow@tuva.engeast Subject: Re: Minor problems with upcomming 2.2.5 In-reply-to: Your message of "Wed, 17 Sep 1997 10:12:11 EDT." <199709171412.KAA09701@tuva.engeast.baynetworks.com> Date: Thu, 18 Sep 1997 18:52:51 -0700 Message-ID: <17268.874633971@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-stable@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > 1) XFree86-3.3.1 won't install using the sysinstall program, either during > or after the initial installation. I think Jordan is working on this. This is fixed. > > 2) I need the following patch to be made to rc.network. This is because > *all* of our AMD maps are in NIS. Thus my rc.conf.local has a line like > this: I don't think we'll do that - what you're proposing is essentially the substitution of a set of options chosen to work in the _widest_ number of scenarios for one which only works well with NIS, a minority. I'd suggest an install script which sets amd_flags directly (which will get it put into your new rc.conf) or copies over a localized copy with fetch, or something. You can call arbitrary commands from scripts if you're careful about the ordering (e.g. call complex commands only _after_ bin is installed ;). > a) Have AMD throttle its process creation at startup. > b) Have GENERIC go out with more process slots. > c) Find a way to have a custom kernel be installed automatically, > instead of GENERIC. It's possible to have a custom kernel installed automatically, you just have to have a little post-installation step of your own in the installation script. The other two options don't strike me as winners this late in the game. Jordan From owner-freebsd-stable Thu Sep 18 22:20:46 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id WAA12130 for stable-outgoing; Thu, 18 Sep 1997 22:20:46 -0700 (PDT) Received: from ns.mt.sri.com (SRI-56K-FR.mt.net [206.127.65.42]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id WAA12120 for ; Thu, 18 Sep 1997 22:20:41 -0700 (PDT) Received: from rocky.mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by ns.mt.sri.com (8.8.7/8.8.7) with ESMTP id XAA12972; Thu, 18 Sep 1997 23:20:38 -0600 (MDT) Received: (from nate@localhost) by rocky.mt.sri.com (8.7.5/8.7.3) id XAA16476; Thu, 18 Sep 1997 23:20:35 -0600 (MDT) Date: Thu, 18 Sep 1997 23:20:35 -0600 (MDT) Message-Id: <199709190520.XAA16476@rocky.mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: "Jordan K. Hubbard" Cc: Robert Withrow , freebsd-stable@freebsd.org, bwithrow@tuva.engeast Subject: Re: Minor problems with upcomming 2.2.5 In-Reply-To: <17268.874633971@time.cdrom.com> References: <199709171412.KAA09701@tuva.engeast.baynetworks.com> <17268.874633971@time.cdrom.com> X-Mailer: VM 6.29 under 19.15 XEmacs Lucid Sender: owner-freebsd-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > a) Have AMD throttle its process creation at startup. > > b) Have GENERIC go out with more process slots. > > c) Find a way to have a custom kernel be installed automatically, > > instead of GENERIC. > > It's possible to have a custom kernel installed automatically, you > just have to have a little post-installation step of your own in the > installation script. The other two options don't strike me as winners > this late in the game. Actually, I think having more process slots is *a good thing* nowadays. Even on my (now ailing) lowly single-user 486/66 box with 16MB, I bump up maxusers. Nate From owner-freebsd-stable Thu Sep 18 22:57:44 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id WAA14875 for stable-outgoing; Thu, 18 Sep 1997 22:57:44 -0700 (PDT) Received: from leech.mpg.uni-jena.de (leech.mpg.uni-jena.de [141.35.24.98]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id WAA14868 for ; Thu, 18 Sep 1997 22:57:39 -0700 (PDT) Received: by leech.mpg.uni-jena.de (NX5.67f2/NX3.0M) id AA11001; Fri, 19 Sep 97 06:56:28 GMT Message-Id: <9709190656.AA11001@leech.mpg.uni-jena.de> Content-Type: text/plain Mime-Version: 1.0 (NeXT Mail 3.3 v118.2) Received: by NeXT.Mailer (1.118.2) From: Heiko Schafberg Date: Fri, 19 Sep 97 06:56:27 GMT To: stable@FreeBSD.ORG Subject: Re: Error message while cvsup'ing RELENG_2_2 References: <199709182106.OAA09275@austin.polstra.com> Sender: owner-freebsd-stable@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Hi folks One short question: What mean the option numbers 0, 1 ore 2 in the fstab? It`s not the right place I know but it`s important. Thank`s Heiko From owner-freebsd-stable Fri Sep 19 01:22:57 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id BAA24407 for stable-outgoing; Fri, 19 Sep 1997 01:22:57 -0700 (PDT) Received: from mailgate.greenhills.co.uk (mailgate.greenhills.co.uk [195.11.194.180]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id BAA24395 for ; Fri, 19 Sep 1997 01:22:51 -0700 (PDT) Received: (qmail 10792 invoked by uid 982); 19 Sep 1997 08:20:36 -0000 Message-ID: <19970919092036.25119@webcrawler.com> Date: Fri, 19 Sep 1997 09:20:36 +0100 From: Martijn Koster To: Martijn Koster Cc: freebsd-stable@FreeBSD.ORG Subject: Re: [mak@webcrawler.com: malloc.c problems in 2.2 stable?] References: <19970912064740.36419@webcrawler.com> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary=NzB8fVQJ5HfG6fxh X-Mailer: Mutt 0.76 In-Reply-To: <19970912064740.36419@webcrawler.com>; from Martijn Koster on Fri, Sep 12, 1997 at 06:47:40AM +0100 Sender: owner-freebsd-stable@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk --NzB8fVQJ5HfG6fxh Content-Type: text/plain; charset=us-ascii On Fri, Sep 12, 1997 at 06:47:40AM +0100, Martijn Koster wrote: > I've justed finished tracking down swap filling on one of my > 2.2-stable production machines to procmail (delivering an only 8M > message), then to realloc. > A search of the mailing lists turned up John Fieber > 's suggestions in June of moving to 3.0-current > malloc.c, and that indeed fixed things. Cool! Nope, it improves things, but doesn't fix the problem completely. Procmail reallocs an area of memory in steps of 16K when reading a message, and the FreeBSD malloc doesn't cope with that -- way before you'd expect to you run out of swap. For example a 64M machine with 128M swap fills up before it gets to reallocing 21M). phk@freebsd.org explains that this should not be considered a malloc bug, but an ineffective allocation strategy on the part of procmail which should be fixed (suggestions and details appended). I agree with the latter, but not necessarily with the former. I had a look at the procmail, the code is in question is in src/pipes.c:readdyn(), and isn't pretty. I ran out of time, and am giving up. I'll report to the procmail mailing list, maybe they can do something, but I won't be holding my breath. -- Martijn Koster, m.koster@pobox.com --NzB8fVQJ5HfG6fxh Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename=phk2 >From phk@critter.freebsd.dk Thu Sep 18 14:32:51 1997 Return-Path: Delivered-To: m.koster@greenhills.co.uk Received: (qmail 7055 invoked from network); 18 Sep 1997 14:32:50 -0000 Received: from punt-2b.mail.demon.net (HELO relay-6.mail.demon.net) (194.217.242.6) by mindy.greenhills.co.uk with SMTP; 18 Sep 1997 14:32:50 -0000 Received: from punt-2.mail.demon.net by mailstore for m.koster@greenhills.co.uk id 874591153:12:05626:2; Thu, 18 Sep 97 14:59:13 BST Received: from mail.webcrawler.com ([204.62.245.201]) by punt-2.mail.demon.net id aa0526954; 18 Sep 97 14:58 BST Received: (qmail 11312 invoked by uid 982); 18 Sep 1997 13:54:49 -0000 Delivered-To: mak@webcrawler.com Received: (qmail 11309 invoked from network); 18 Sep 1997 13:54:47 -0000 Received: from critter.freebsd.dk (195.8.129.26) by mail.webcrawler.com with SMTP; 18 Sep 1997 13:54:47 -0000 Received: from critter.freebsd.dk (localhost.cybercity.dk [127.0.0.1]) by critter.freebsd.dk (8.8.7/8.8.7) with ESMTP id PAA03511; Thu, 18 Sep 1997 15:57:51 +0200 (CEST) To: Martijn Koster cc: Andre Albsmeier Subject: Re: procmail dies, why? In-reply-to: Your message of "Thu, 18 Sep 1997 14:25:43 BST." <19970918142543.12647@webcrawler.com> Date: Thu, 18 Sep 1997 15:57:51 +0200 Message-ID: <3509.874591071@critter.freebsd.dk> From: Poul-Henning Kamp Status: RO X-Status: A Content-Length: 5001 Lines: 180 There isn't much that can be done in this case, it's a singular stupid way of allocating memory. I would need to do page flipping AND be very lucky to be able to make this work decently. A far better way to do the job is to: mul = 16 size = 64K; malloc (size) while (not enough) /* don't mess around */ size *= mul realloc(size) if (mul > 2) mul <<= 1; Don't worry about overallocation, it's practically free until you actually access the memory. even doing malloc (32M) right away would be cheaper than the current stuff. But even smarter would be to pipe the stuff into a temporary file and them mmap it... Procmail is stupid, and should be fixed. Poul-Henning In message <19970918142543.12647@webcrawler.com>, Martijn Koster writes: > >[phk: we briefly discussed this last week. Can I once again ask for help?] > > >On Thu, Sep 18, 1997 at 01:27:24PM +0200, Andre Albsmeier wrote: > >> I have here 8 2.2-STABLE machines and all behave equal. realloc or >> procmail screws up the machine although with the new malloc.c >> the system doesn't crash any more. > >You are right; malloc 1.32 improves the situation, but something is >still weird. > >Poul -- can you reproduce this? Any ideas what's up? > >When I run rea.c with 100M argument on -stable (with malloc.c-1.32) on >a 64M machine (132.96-MHz 586-class CPU), I get to 21M, when the >machine has run out of swap (138M). One -current on a 64M machine >(199.43-MHz 686-class CPU) I get to 25M, by then the machine has run >out of swap (138M). This process takes some 12 minutes (!). > >This code runs fine up to 100M on Irix 6.2 (Indy, 96M, 2 secs) and >Solaris 2.5 (Sparc5, 64M, 10 secs). This doesn't make FreeBSD look >good :-( > >Below is all the information I think may be relevant for reproduction. > >-- Martijn > >mak@pitch$ cat rea.c >#include >#include >#include > >int >main(int argc, char* argv[]) >{ > size_t size = 0; > char *p = NULL; > int max = 8404992; > > if (argc > 2) { > fprintf(stderr, "Usage: %s maxmem\n", argv[0]); > exit(-1); > } > if (argc > 1) > max = atoi(argv[1]); > > while(1) { > > size += 16384; > if (size > max) > break; > > fprintf(stderr, "realloc(%u)\n", size); > if ((p = realloc(p, size)) == NULL) { > fprintf(stderr, "out of memory\n"); > exit(-1); > } > } > > { > int c; > printf("done. press return to quit\n"); > read(0, &c, 1); > } >} >mak@pitch$ uname -a >FreeBSD pitch.webcrawler.com 2.2-STABLE FreeBSD 2.2-STABLE #0: Tue Sep 9 16:0 >4:50 PDT 1997 mak@pitch.webcrawler.com:/usr/src/sys/compile/PITCH i386 >mak@pitch$ dmesg | grep 'real memory' >real memory = 67108864 (65536K bytes) >mak@pitch$ grep '\$Id' /usr/src/lib/libc/stdlib/malloc.c > * $Id: malloc.c,v 1.32 1997/08/31 05:59:39 phk Exp $ >mak@pitch$ ls -l /etc/malloc.conf >ls: /etc/malloc.conf: No such file or directory >mak@pitch$ cc -c /usr/src/lib/libc/stdlib/malloc.c >mak@pitch$ cc -c rea.c >mak@pitch$ cc -o rea rea.o malloc.o >mak@pitch$ sudo su >Password: ># bash >bash-2.00# for i in -c -d -f -l -m -n -p -s -t -u -v >> do >> echo $i >> ulimit $i unlimited >> done >-c >-d >-f >-l >-m >-p >bash: ulimit: cannot modify limit: Invalid argument >-s >-t >-u >-v >bash: ulimit: cannot modify limit: Invalid argument >bash-2.00# ulimit -a >core file size (blocks) unlimited >data seg size (kbytes) 131072 >file size (blocks) unlimited >max locked memory (kbytes) unlimited >max memory size (kbytes) unlimited >open files 360 >pipe size (512 bytes) 1 >stack size (kbytes) 65536 >cpu time (seconds) unlimited >max user processes 179 >virtual memory (kbytes) 196608 >bash-2.00# ./rea 104857600 ># ... many lines of output >realloc(21823488) >out of memory >bash-2.00# > ># At the time, top showed: > > PID USERNAME PRI NICE SIZE RES STATE TIME WCPU CPU COMMAND >13061 root -18 0 42756K 34196K swread 13:10 21.51% 21.51% rea >11882 mak 10 0 776K 436K wait 0:23 0.84% 0.84% bash >last pid: 16331; load averages: 1.50, 1.70, 1.36 22:32:54 >32 processes: 1 running, 31 sleeping > >Mem: 26M Active, 9660K Inact, 19M Wired, 5876K Cache, 7616K Buf, 532K Free >Swap: 138M Total, 137M Used, 1684K Free, 99% Inuse > > > PID USERNAME PRI NICE SIZE RES STATE TIME WCPU CPU COMMAND >13061 root -18 0 42756K 35776K swread 13:10 20.56% 20.56% rea >11882 mak 10 0 776K 436K wait 0:23 0.88% 0.88% bash >head: Cannot allocate memory >kvm_open: Cannot allocate memory >kvm_open: Cannot allocate memory >head: Cannot allocate memory >head: Cannot allocate memory >kvm_open: Cannot allocate memory >kvm_open: Cannot allocate memory >head: Cannot allocate memory > -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." --NzB8fVQJ5HfG6fxh-- From owner-freebsd-stable Fri Sep 19 03:21:01 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id DAA01632 for stable-outgoing; Fri, 19 Sep 1997 03:21:01 -0700 (PDT) Received: from fty-ss20.cisco.com (fty-ss20.cisco.com [171.69.162.81]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id DAA01626 for ; Fri, 19 Sep 1997 03:20:57 -0700 (PDT) Received: by fty-ss20.cisco.com (8.8.5/1.34) id KAA04869; Fri, 19 Sep 1997 10:20:10 GMT Date: Fri, 19 Sep 1997 10:20:10 GMT From: Frank Terhaar-Yonkers Message-Id: <199709191020.KAA04869@fty-ss20.cisco.com> To: freebsd-stable@FreeBSD.ORG Subject: need a libc.so.3.0 as from about 2 weeks ago X-Face: ,fjtWiMPydUaSQl%8[eTg`u:^BXt&T)Sny(6w\*U"5D9H[Z$kG%Q/z;Z=NwrPiXf-aMF3R) Rsand$,]26-8>5@HD(A3A79gN|0%NHsdek4mT8E,>j+\w!~d2#nH;~NV!5a0"`5$Cj8d\or(Jy/JQ_ |uc;C[filmZ(~#lre*l:|O%d/PJFy`.5w8)sMZ-)QI3TaV"j'k X-Mailer: [XMailTool v3.1.0] Sender: owner-freebsd-stable@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk I supped this morning, rebuilt the libs, installed and now a lot of utilities are failing with "ld.so failed: Undefined symbol "SYS_issetugid". I'm stuck. Did I miss something about this incompatibility? - Frank \\\\////\\\\////\\\\\////\\\\\////\\\\////\\\\////\\\\////\\\\////\\\\////\\\\ Frank Terhaar-Yonkers Cisco Systems, Inc. Engineering Services, W2 F3 5 7025 Kit Creek Road PO Box 14987 Research Triangle Park, North Carolina 27709 fty@cisco.com voice (919)472-2101 FAX (919)472-2940 pager (800)796-7363 pin 1008366 -or- fty@airnote.net From owner-freebsd-stable Fri Sep 19 04:29:01 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id EAA05023 for stable-outgoing; Fri, 19 Sep 1997 04:29:01 -0700 (PDT) Received: from awfulhak.demon.co.uk (awfulhak.demon.co.uk [158.152.17.1]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id EAA05016 for ; Fri, 19 Sep 1997 04:28:54 -0700 (PDT) Received: from gate.lan.awfulhak.org (localhost [127.0.0.1]) by awfulhak.demon.co.uk (8.8.5/8.8.5) with ESMTP id LAA25082; Fri, 19 Sep 1997 11:44:37 +0100 (BST) Message-Id: <199709191044.LAA25082@awfulhak.demon.co.uk> X-Mailer: exmh version 2.0zeta 7/24/97 To: "Bret Ford" cc: freebsd-stable@FreeBSD.ORG Subject: Re: PPP issues In-reply-to: Your message of "Thu, 18 Sep 1997 07:24:52 PDT." <199709181425.HAA09487@uop.cs.uop.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 19 Sep 1997 11:44:37 +0100 From: Brian Somers Sender: owner-freebsd-stable@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > >[.....] > >> The other problem I've had has occured only in FreeBSD-stable. > >> Under -release, I was able to do "ppp -alias provider >& /dev/null &" > >[.....] > > > >Mmmm, "ppp -alias provider" *never* did anything except give you an > >interactive session. Do you mean "ppp -alias -auto provider" ? > > > No, I haven't tried it as anything other than an interactive session. I > had > previously been able to chuck the output into null, as above. Haven't > ventured into -auto, -background, etc. So what's "ppp -alias provider >&/dev/null &" supposed to do that "ppp -alias -background provider" won't ? > Bret Ford -- Brian , , Don't _EVER_ lose your sense of humour.... From owner-freebsd-stable Fri Sep 19 04:57:29 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id EAA06458 for stable-outgoing; Fri, 19 Sep 1997 04:57:29 -0700 (PDT) Received: from bunyip.cc.uq.edu.au (daemon@bunyip.cc.uq.edu.au [130.102.2.1]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id EAA06453 for ; Fri, 19 Sep 1997 04:57:20 -0700 (PDT) Received: (from daemon@localhost) by bunyip.cc.uq.edu.au (8.8.7/8.8.7) id VAA25917 for freebsd-stable@freebsd.org; Fri, 19 Sep 1997 21:56:49 +1000 Received: from troll.dtir.qld.gov.au by ogre.dtir.qld.gov.au (8.7.5/DEVETIR-E0.3a) with ESMTP id VAA18160 for ; Fri, 19 Sep 1997 21:51:30 +1000 (EST) Received: from localhost (syssgm@localhost) by troll.dtir.qld.gov.au (8.8.5/8.8.5) with SMTP id VAA29237; Fri, 19 Sep 1997 21:51:26 +1000 (EST) Message-Id: <199709191151.VAA29237@troll.dtir.qld.gov.au> X-Authentication-Warning: troll.dtir.qld.gov.au: syssgm@localhost didn't use HELO protocol To: freebsd-stable@freebsd.org cc: syssgm@dtir.qld.gov.au Subject: No-go with read-only src tree Date: Fri, 19 Sep 1997 21:51:26 +1000 From: Stephen McKay Sender: owner-freebsd-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I can't recall any actual claim that a read only source tree can be used for a 'make buildworld', but I tried anyway. I started with a 2.2.2 box and it fell over trying to build 'make'. After 'make install' in share/mk it got much further. It seems to me like this could work with a few tweaks. The next death spot (somewhere after "Rebuilding tools needed to build the libraries"): cd /src/2.2-stable/usr.bin/lex/lib && /usr/obj/src/2.2-stable/tmp/usr/bin/make depend && /usr/obj/src/2.2-stable/tmp/usr/bin/make -DNOINFO -DNOMAN -DNOPROFILE all install cleandir obj rm -f .depend mkdep -f .depend -a -I/usr/obj/src/2.2-stable/tmp/usr/include libmain.c libyywrap.c /usr/bin/mkdep: cannot create .depend: read-only file system *** Error code 2 Stop. *** Error code 1 Stop. *** Error code 1 Stop. It seems that back in the "Bootstrapping flex" part in "Rebuilding bootstrap tools", the "make ... all install cleandir obj" command rebuilds the obj dir for lex, but not lex/lib. As the last step of the bootstrap, I see: /usr/obj/src/2.2-stable/usr.bin/lex created for /src/2.2-stable/usr.bin/lex but I DON'T see the expected lex/lib equivalent. I reckon this is solvable. I'll be building 2.2-stable pretty regularly until release date, and I'm keen on building from read-only source. If no Makefile Master fixes this, I'll be adding something creative of my own. :-) Stephen. From owner-freebsd-stable Fri Sep 19 05:44:37 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id FAA09096 for stable-outgoing; Fri, 19 Sep 1997 05:44:37 -0700 (PDT) Received: from echonyc.com (echonyc.com [198.67.15.2]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id FAA09080 for ; Fri, 19 Sep 1997 05:44:31 -0700 (PDT) Received: from localhost (benedict@localhost) by echonyc.com (8.8.7/8.8.7) with SMTP id IAA00402; Fri, 19 Sep 1997 08:44:18 -0400 (EDT) Date: Fri, 19 Sep 1997 08:44:18 -0400 (EDT) From: Snob Art Genre To: Stephen McKay cc: freebsd-stable@FreeBSD.ORG Subject: Re: No-go with read-only src tree In-Reply-To: <199709191151.VAA29237@troll.dtir.qld.gov.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk It's trivial . . . just fix unionfs. :-) On Fri, 19 Sep 1997, Stephen McKay wrote: > I can't recall any actual claim that a read only source tree can be used > for a 'make buildworld', but I tried anyway. I started with a 2.2.2 box > and it fell over trying to build 'make'. After 'make install' in share/mk > it got much further. It seems to me like this could work with a few tweaks. > > The next death spot (somewhere after "Rebuilding tools needed to build the > libraries"): > > cd /src/2.2-stable/usr.bin/lex/lib && /usr/obj/src/2.2-stable/tmp/usr/bin/make depend && /usr/obj/src/2.2-stable/tmp/usr/bin/make -DNOINFO -DNOMAN -DNOPROFILE all install cleandir obj > rm -f .depend > mkdep -f .depend -a -I/usr/obj/src/2.2-stable/tmp/usr/include libmain.c libyywrap.c > /usr/bin/mkdep: cannot create .depend: read-only file system > *** Error code 2 > > Stop. > *** Error code 1 > > Stop. > *** Error code 1 > > Stop. > > > It seems that back in the "Bootstrapping flex" part in "Rebuilding bootstrap > tools", the "make ... all install cleandir obj" command rebuilds the obj > dir for lex, but not lex/lib. > > As the last step of the bootstrap, I see: > > /usr/obj/src/2.2-stable/usr.bin/lex created for /src/2.2-stable/usr.bin/lex > > but I DON'T see the expected lex/lib equivalent. > > I reckon this is solvable. I'll be building 2.2-stable pretty regularly > until release date, and I'm keen on building from read-only source. If > no Makefile Master fixes this, I'll be adding something creative of my > own. :-) > > Stephen. > Ben "You have your mind on computers, it seems." From owner-freebsd-stable Fri Sep 19 06:43:33 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id GAA12481 for stable-outgoing; Fri, 19 Sep 1997 06:43:33 -0700 (PDT) Received: from echonyc.com (echonyc.com [198.67.15.2]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id GAA12473 for ; Fri, 19 Sep 1997 06:43:29 -0700 (PDT) Received: from localhost (benedict@localhost) by echonyc.com (8.8.7/8.8.7) with SMTP id JAA12289; Fri, 19 Sep 1997 09:43:23 -0400 (EDT) Date: Fri, 19 Sep 1997 09:43:23 -0400 (EDT) From: Snob Art Genre To: Heiko Schafberg cc: stable@FreeBSD.ORG Subject: Re: Error message while cvsup'ing RELENG_2_2 In-Reply-To: <9709190656.AA11001@leech.mpg.uni-jena.de> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk man 5 fstab On Fri, 19 Sep 1997, Heiko Schafberg wrote: > Hi folks > > One short question: What mean the option numbers 0, 1 ore 2 in the fstab? > It`s not the right place I know but it`s important. > Thank`s > > Heiko > Ben "You have your mind on computers, it seems." From owner-freebsd-stable Fri Sep 19 12:48:24 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id MAA03375 for stable-outgoing; Fri, 19 Sep 1997 12:48:24 -0700 (PDT) Received: from mail.san.rr.com (mail-atm.san.rr.com [204.210.0.1]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id MAA03368 for ; Fri, 19 Sep 1997 12:48:20 -0700 (PDT) Received: from dt5h1n61.san.rr.com (dt5h1n61.san.rr.com [204.210.31.97]) by mail.san.rr.com (8.8.7/8.8.7) with SMTP id MAA22800 for ; Fri, 19 Sep 1997 12:47:48 -0700 (PDT) Message-Id: <199709191947.MAA22800@mail.san.rr.com> From: "Studded" To: "freebsd-stable@freebsd.org" Date: Fri, 19 Sep 97 12:47:33 -0700 Reply-To: "Studded" Priority: Normal X-Mailer: PMMail 1.92 For OS/2 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Subject: >8 char usernames going into 2.2.5? Sender: owner-freebsd-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I remember a discussion a while back that the changes to allow user names of greater than 8 characters that are presently working in current would be back-ported to 2.2.x RSN. I'm wondering if this change will be made in time for the 2.2.5 release. Curious, Doug (who would really like to see this done :) Do thou amend thy face, and I'll amend my life. -Shakespeare, "Henry V" From owner-freebsd-stable Fri Sep 19 13:20:59 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id NAA05575 for stable-outgoing; Fri, 19 Sep 1997 13:20:59 -0700 (PDT) Received: from mail.uniserve.com (dns1-van.uniserve.com [204.244.163.48]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id NAA05570 for ; Fri, 19 Sep 1997 13:20:56 -0700 (PDT) Received: from shell.uniserve.com [204.244.210.252] by mail.uniserve.com with smtp (Exim 1.70 #1) id 0xC9Xm-00023G-00; Fri, 19 Sep 1997 13:20:50 -0700 Date: Fri, 19 Sep 1997 13:20:47 -0700 (PDT) From: Tom To: Studded cc: "freebsd-stable@freebsd.org" Subject: Re: >8 char usernames going into 2.2.5? In-Reply-To: <199709191947.MAA22800@mail.san.rr.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Fri, 19 Sep 1997, Studded wrote: > I remember a discussion a while back that the changes to allow > user names of greater than 8 characters that are presently working in > current would be back-ported to 2.2.x RSN. I'm wondering if this > change will be made in time for the 2.2.5 release. Better than that, I've been hand patching 2.2-stable for some time now to support longer usernames > Curious, > > Doug (who would really like to see this done :) So would I. > Do thou amend thy face, > and I'll amend my life. > -Shakespeare, "Henry V" > > Tom From owner-freebsd-stable Fri Sep 19 13:45:34 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id NAA06917 for stable-outgoing; Fri, 19 Sep 1997 13:45:34 -0700 (PDT) Received: from Central.KeyWest.MPGN.COM (Central.TanSoft.COM [208.194.145.1]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id NAA06900 for ; Fri, 19 Sep 1997 13:45:29 -0700 (PDT) Received: from devious.Tansoft.com (Devious.TanSoft.COM [208.194.145.10]) by Central.KeyWest.MPGN.COM (8.6.9/8.6.9) with SMTP id QAA16628 for ; Fri, 19 Sep 1997 16:44:57 -0400 Message-Id: <3.0.3.32.19970919164456.0081b100@central.TanSoft.COM> X-Sender: rwm@central.TanSoft.COM X-Mailer: QUALCOMM Windows Eudora Pro Version 3.0.3 (32) Date: Fri, 19 Sep 1997 16:44:56 -0400 To: freebsd-stable@freebsd.org From: Rob Miracle Subject: Re: >8 char usernames going into 2.2.5? In-Reply-To: References: <199709191947.MAA22800@mail.san.rr.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > Better than that, I've been hand patching 2.2-stable for some time now >to support longer usernames >> Doug (who would really like to see this done :) What about something really useful, like 4 byte UIDs? Rob From owner-freebsd-stable Fri Sep 19 14:17:30 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id OAA09401 for stable-outgoing; Fri, 19 Sep 1997 14:17:30 -0700 (PDT) Received: from mail.uniserve.com (dns1-van.uniserve.com [204.244.163.48]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id OAA09396 for ; Fri, 19 Sep 1997 14:17:27 -0700 (PDT) Received: from shell.uniserve.com [204.244.210.252] by mail.uniserve.com with smtp (Exim 1.70 #1) id 0xCAQW-0002Fe-00; Fri, 19 Sep 1997 14:17:24 -0700 Date: Fri, 19 Sep 1997 14:17:20 -0700 (PDT) From: Tom To: Rob Miracle cc: freebsd-stable@freebsd.org Subject: Re: >8 char usernames going into 2.2.5? In-Reply-To: <3.0.3.32.19970919164456.0081b100@central.TanSoft.COM> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Fri, 19 Sep 1997, Rob Miracle wrote: > > Better than that, I've been hand patching 2.2-stable for some time now > >to support longer usernames > > >> Doug (who would really like to see this done :) > > What about something really useful, like 4 byte UIDs? Really useful? Like who has over 65,000 users in /etc/passwd anyhow? Besides, once you get over 65K users, long usernames will be even more important because the namespace will rather congested. I have 13007 users on one server, and namespace problems are already quite severe with 8 character usernames. > Rob Tom From owner-freebsd-stable Fri Sep 19 15:15:06 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id PAA13010 for stable-outgoing; Fri, 19 Sep 1997 15:15:06 -0700 (PDT) Received: from mail.san.rr.com (mail-atm.san.rr.com [204.210.0.1]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id PAA13005 for ; Fri, 19 Sep 1997 15:15:03 -0700 (PDT) Received: from dt5h1n61.san.rr.com (dt5h1n61.san.rr.com [204.210.31.97]) by mail.san.rr.com (8.8.7/8.8.7) with SMTP id PAA16435 for ; Fri, 19 Sep 1997 15:14:32 -0700 (PDT) Message-Id: <199709192214.PAA16435@mail.san.rr.com> From: "Studded" To: "freebsd-stable@freebsd.org" Date: Fri, 19 Sep 97 15:14:20 -0700 Reply-To: "Studded" Priority: Normal X-Mailer: PMMail 1.92 For OS/2 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Subject: Re: >8 char usernames going into 2.2.5? Sender: owner-freebsd-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Fri, 19 Sep 1997 16:44:56 -0400, Rob Miracle wrote: >What about something really useful, like 4 byte UIDs? I'm not in a position to comment on the usefulness/possibility of doing that. I have seen numerous requests for longer user names on the -questions list, so I *am* in a position to say that this is an oft-requested feature, and from what I've seen would not be too difficult to implement. Also, as tom@uniserve.com already stated quite well, you run out of usable (humanly) usernames with only 8 chars available long before you run out of UID's. While I'm askin', it would be nice if some chars besides letters and numbers could sneak in there too. The one I would like most is - (the dash) but I know there are other requests. (And yes, I know about aliases. :) Thanks for your input, Doug Do thou amend thy face, and I'll amend my life. -Shakespeare, "Henry V" From owner-freebsd-stable Fri Sep 19 15:30:01 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id PAA14122 for stable-outgoing; Fri, 19 Sep 1997 15:30:01 -0700 (PDT) Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id PAA14089 for ; Fri, 19 Sep 1997 15:29:58 -0700 (PDT) Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.7/8.6.9) with ESMTP id PAA19932; Fri, 19 Sep 1997 15:30:11 -0700 (PDT) To: "Studded" cc: "freebsd-stable@freebsd.org" Subject: Re: >8 char usernames going into 2.2.5? In-reply-to: Your message of "Fri, 19 Sep 1997 12:47:33 PDT." <199709191947.MAA22800@mail.san.rr.com> Date: Fri, 19 Sep 1997 15:30:11 -0700 Message-ID: <19929.874708211@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-stable@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > I remember a discussion a while back that the changes to allow > user names of greater than 8 characters that are presently working in > current would be back-ported to 2.2.x RSN. I'm wondering if this > change will be made in time for the 2.2.5 release. Hmm, I'm not sure who told you that but it was definitely never our intention to go to >8 character usernames in the 2.2-stable branch. There is too much potential upheaval associated with that change and so we've decided to take our lumps all at once with 3.0. Jordan From owner-freebsd-stable Fri Sep 19 15:49:07 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id PAA15815 for stable-outgoing; Fri, 19 Sep 1997 15:49:07 -0700 (PDT) Received: from mail.uniserve.com (dns1-van.uniserve.com [204.244.163.48]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id PAA15794 for ; Fri, 19 Sep 1997 15:48:34 -0700 (PDT) Received: from shell.uniserve.com [204.244.210.252] by mail.uniserve.com with smtp (Exim 1.70 #1) id 0xCBqf-0002cQ-00; Fri, 19 Sep 1997 15:48:29 -0700 Date: Fri, 19 Sep 1997 15:48:01 -0700 (PDT) From: Tom To: Studded cc: "freebsd-stable@freebsd.org" Subject: Re: >8 char usernames going into 2.2.5? In-Reply-To: <199709192214.PAA16435@mail.san.rr.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Fri, 19 Sep 1997, Studded wrote: ... > While I'm askin', it would be nice if some chars besides > letters and numbers could sneak in there too. The one I would like > most is - (the dash) but I know there are other requests. (And yes, I > know about aliases. :) That is the foolish "adduser" imposing restrictions on you. "-" works perfectly fine in userids. I use "-", and "_" in usernames regularly, but I use a rather strange "adduser" that predates the one in FreeBSD. "adduser" is in perl. Just fix it.. err... _modify_ it :) > Thanks for your input, > > Doug > > Do thou amend thy face, > and I'll amend my life. > -Shakespeare, "Henry V" > > Tom From owner-freebsd-stable Fri Sep 19 17:02:08 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id RAA19619 for stable-outgoing; Fri, 19 Sep 1997 17:02:08 -0700 (PDT) Received: from echonyc.com (echonyc.com [198.67.15.2]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id RAA19612 for ; Fri, 19 Sep 1997 17:02:05 -0700 (PDT) Received: from localhost (benedict@localhost) by echonyc.com (8.8.7/8.8.7) with SMTP id UAA22604; Fri, 19 Sep 1997 20:01:41 -0400 (EDT) Date: Fri, 19 Sep 1997 20:01:41 -0400 (EDT) From: Snob Art Genre To: Tom cc: Studded , "freebsd-stable@freebsd.org" Subject: Re: >8 char usernames going into 2.2.5 In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk I asked Wolfram Schneider (?) about this when I was using 2.1 and he said this was fixed in the 2.2 adduser. Underscore is AFAIK not supposed to be allowed in usernames. Hyphen is, which makes qmail's default use of hyphen as a separator in email addresses rather annoying -- to their credit, though, it's configurable. On Fri, 19 Sep 1997, Tom wrote: > > On Fri, 19 Sep 1997, Studded wrote: > > ... > > While I'm askin', it would be nice if some chars besides > > letters and numbers could sneak in there too. The one I would like > > most is - (the dash) but I know there are other requests. (And yes, I > > know about aliases. :) > > That is the foolish "adduser" imposing restrictions on you. "-" works > perfectly fine in userids. I use "-", and "_" in usernames regularly, but > I use a rather strange "adduser" that predates the one in FreeBSD. > > "adduser" is in perl. Just fix it.. err... _modify_ it :) > > > Thanks for your input, > > > > Doug > > > > Do thou amend thy face, > > and I'll amend my life. > > -Shakespeare, "Henry V" > > > > > > Tom > > Ben "You have your mind on computers, it seems." From owner-freebsd-stable Fri Sep 19 17:18:27 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id RAA20481 for stable-outgoing; Fri, 19 Sep 1997 17:18:27 -0700 (PDT) Received: from mail.uniserve.com (dns1-van.uniserve.com [204.244.163.48]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id RAA20472 for ; Fri, 19 Sep 1997 17:18:23 -0700 (PDT) Received: from shell.uniserve.com [204.244.210.252] by mail.uniserve.com with smtp (Exim 1.70 #1) id 0xCDFb-00030c-00; Fri, 19 Sep 1997 17:18:19 -0700 Date: Fri, 19 Sep 1997 17:18:14 -0700 (PDT) From: Tom To: Snob Art Genre cc: Studded , "freebsd-stable@freebsd.org" Subject: Re: >8 char usernames going into 2.2.5 In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Fri, 19 Sep 1997, Snob Art Genre wrote: > Underscore is AFAIK not supposed to be allowed in usernames. Hyphen is, Huh? Why not? Tom From owner-freebsd-stable Fri Sep 19 17:39:19 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id RAA21554 for stable-outgoing; Fri, 19 Sep 1997 17:39:19 -0700 (PDT) Received: from mail.uniserve.com (dns1-van.uniserve.com [204.244.163.48]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id RAA21534 for ; Fri, 19 Sep 1997 17:39:16 -0700 (PDT) Received: from shell.uniserve.com [204.244.210.252] by mail.uniserve.com with smtp (Exim 1.70 #1) id 0xCDZg-00035x-00; Fri, 19 Sep 1997 17:39:04 -0700 Date: Fri, 19 Sep 1997 17:39:00 -0700 (PDT) From: Tom To: "Jordan K. Hubbard" cc: Studded , "freebsd-stable@freebsd.org" Subject: Re: >8 char usernames going into 2.2.5? In-Reply-To: <19929.874708211@time.cdrom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Fri, 19 Sep 1997, Jordan K. Hubbard wrote: > > I remember a discussion a while back that the changes to allow > > user names of greater than 8 characters that are presently working in > > current would be back-ported to 2.2.x RSN. I'm wondering if this > > change will be made in time for the 2.2.5 release. > > Hmm, I'm not sure who told you that but it was definitely never our > intention to go to >8 character usernames in the 2.2-stable branch. > There is too much potential upheaval associated with that change and > so we've decided to take our lumps all at once with 3.0. > > Jordan I'd like to register strong disagreement with the above. The change itself, is simple. It is going to affect packages that read/alter utmp/wtmp/lastlog. However, since the packages will be re-built everything will be ok, as long as people don't use old packages. I think we should get this change behind us. It is only get to get worse. I'm also rather annoyned that BSDI has had 16 characters usernames for over two years, and FreeBSD doesn't yet have a single release that does. It makes FreeBSD look antiquated. Tom From owner-freebsd-stable Fri Sep 19 17:50:10 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id RAA22106 for stable-outgoing; Fri, 19 Sep 1997 17:50:10 -0700 (PDT) Received: from gaylord.async.vt.edu (gaylord.async.vt.edu [128.173.18.131]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id RAA22101 for ; Fri, 19 Sep 1997 17:50:05 -0700 (PDT) Received: (from gaylord@localhost) by gaylord.async.vt.edu (8.8.5/8.8.5) id UAA02854; Fri, 19 Sep 1997 20:45:56 -0400 (EDT) From: Clark Gaylord Message-Id: <199709200045.UAA02854@gaylord.async.vt.edu> Subject: Re: silo overflows... In-Reply-To: <199709171730.KAA00227@netcom1.netcom.com> from "Michael V. Harding" at "Sep 17, 97 10:30:41 am" To: mvh@netcom.com (Michael V. Harding) Date: Fri, 19 Sep 1997 20:45:55 -0400 (EDT) Cc: ceharris@vt.edu (Carl Harris), freebsd-stable@freebsd.org X-Mailer: ELM [version 2.4ME+ PL31 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Mike -- Well, I just moved my modem to sio2. Fired up X, did a bunch of 'scaping, ftpin, and X/Tk stuff and no silo overflows. I think we may have a weiner. Hope you have similar luck. ... and that mine holds :-) Clark Gaylord > It's possible that we have a similar situation. I'm running a generic > S3 Virge chip, but my modem is on sio2. The silo overrun can happen > when there is a long interrupt latency - and the S3 drivers may be > disabling interrupts. Not in general a problem. I moved my modem > connect to 56K and most of my problems have gone away, although this > is just a bandaid. > > I am, however, having video artifacts, which I never used to have. > Gargh. > > Thanks for your input, > > Mike Harding > > From: Clark Gaylord > Date: Wed, 17 Sep 1997 00:22:26 -0400 (EDT) > X-Mailer: ELM [version 2.4ME+ PL31 (25)] > MIME-Version: 1.0 > Content-Type: text/plain; charset=US-ASCII > Content-Transfer-Encoding: 7bit > X-UIDL: da785a37a99dab659b933b8fbfbebca9 > > I have seen this a lot w/ 2.2.1+, but the problem seems to only happen > to me when I run X. So long as I do everything in telnet/vtty, all is > fine. My setup is: > Mylex MTI386 (DX33) > Adaptec 1542 > Diamond Stealth24 > 28.8 external modem > serial mouse > > I experience occassional mouse com port silo overflows and lots (hundreds) > of modem cort silo overflows. I changed my serial port twice, and nothing > worked. The other factoid I uncovered recently is possible incompatibilities > between sio3 and S3 video chipsets. I have not moved modem to sio2, though > this is something I plan to do. > > In general, though, silo overruns indicate interupt conflicts, faulty > hardware, don't they? > > -- > Clark K. Gaylord > Blacksburg, Virginia USA > cgaylord@vt.edu > gaylord@usit.net > > > I don't know if this is a 'stable' question, but I am getting silo > > overflows after upgrading to a K6 / Asus TX-97 combo and upgrading to > > -stable. Is there something different about this setup? Should I > > turn off bus mastering? Anyone else seen this? I would be surprised > > if the TX chipset was messed up. > > > > Also, how do I turn down the threshold in sio.c? I looked at the code > > but wasn't able to determine what to hack to set the threshold to 8 > > bytes. > > > > Thanks! > > > > Mike Harding > > > > > > > > > > > -- Clark K. Gaylord Blacksburg, Virginia USA cgaylord@vt.edu gaylord@usit.net From owner-freebsd-stable Fri Sep 19 18:48:13 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id SAA24666 for stable-outgoing; Fri, 19 Sep 1997 18:48:13 -0700 (PDT) Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id SAA24659 for ; Fri, 19 Sep 1997 18:48:08 -0700 (PDT) Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.7/8.6.9) with ESMTP id SAA21123; Fri, 19 Sep 1997 18:47:59 -0700 (PDT) To: Tom cc: Studded , "freebsd-stable@freebsd.org" Subject: Re: >8 char usernames going into 2.2.5? In-reply-to: Your message of "Fri, 19 Sep 1997 17:39:00 PDT." Date: Fri, 19 Sep 1997 18:47:59 -0700 Message-ID: <21119.874720079@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-stable@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > I'd like to register strong disagreement with the above. The change > itself, is simple. It is going to affect packages that read/alter > utmp/wtmp/lastlog. However, since the packages will be re-built > everything will be ok, as long as people don't use old packages. I think > we should get this change behind us. It is only get to get worse. Trust me, no matter how strong your disagreement with the above, there are plenty of folks who will disagree even more strongly with the idea of changing it. They don't want to have to update or convert in-place all their log data (and some people have utmp/wtmp logs which are archived for months and used to produce billing data) and for them, 2.2-stable represents the place to be when you don't want to suffer from mid-stream changes like that. 16 character usernames have been part of 3.0 for some time and is not even difficult to add to 2.2 on an as-needed basis (sheesh, you alter two header files and make the world - how hard can that be? ;), so I don't think it's quite fair to make it sound like BSDI has had the feature for 2 years and FreeBSD users have just been totally SOL on the matter. We make our sources available at no extra charge, eh? :-) Jordan From owner-freebsd-stable Fri Sep 19 19:15:29 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id TAA25886 for stable-outgoing; Fri, 19 Sep 1997 19:15:29 -0700 (PDT) Received: from gatekeeper.tsc.tdk.com (root@gatekeeper.tsc.tdk.com [207.113.159.21]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id TAA25881 for ; Fri, 19 Sep 1997 19:15:26 -0700 (PDT) Received: from sunrise.gv.tsc.tdk.com (root@sunrise.gv.tsc.tdk.com [192.168.241.191]) by gatekeeper.tsc.tdk.com (8.8.4/8.8.4) with ESMTP id TAA09235; Fri, 19 Sep 1997 19:14:59 -0700 (PDT) Received: from salsa.gv.tsc.tdk.com (salsa.gv.tsc.tdk.com [192.168.241.194]) by sunrise.gv.tsc.tdk.com (8.8.5/8.8.5) with ESMTP id TAA05834; Fri, 19 Sep 1997 19:14:58 -0700 (PDT) Received: (from gdonl@localhost) by salsa.gv.tsc.tdk.com (8.8.5/8.8.5) id TAA09566; Fri, 19 Sep 1997 19:14:57 -0700 (PDT) From: Don Lewis Message-Id: <199709200214.TAA09566@salsa.gv.tsc.tdk.com> Date: Fri, 19 Sep 1997 19:14:57 -0700 In-Reply-To: Tom "Re: >8 char usernames going into 2.2.5?" (Sep 19, 5:39pm) X-Mailer: Mail User's Shell (7.2.6 alpha(3) 7/19/95) To: Tom , "Jordan K. Hubbard" Subject: Re: >8 char usernames going into 2.2.5? Cc: Studded , "freebsd-stable@freebsd.org" Sender: owner-freebsd-stable@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Sep 19, 5:39pm, Tom wrote: } Subject: Re: >8 char usernames going into 2.2.5? } I'd like to register strong disagreement with the above. The change } itself, is simple. It is going to affect packages that read/alter } utmp/wtmp/lastlog. And anything that calls getpw* } However, since the packages will be re-built } everything will be ok, as long as people don't use old packages. This also means that folks who don't upgrade to 2.2.5 can't install new packages. --- Truck From owner-freebsd-stable Fri Sep 19 19:46:11 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id TAA27287 for stable-outgoing; Fri, 19 Sep 1997 19:46:11 -0700 (PDT) Received: from counterintelligence.ml.org (mdean.vip.best.com [206.86.94.101]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id TAA27268 for ; Fri, 19 Sep 1997 19:46:06 -0700 (PDT) Received: from localhost (jamil@localhost) by counterintelligence.ml.org (8.8.7/8.8.5) with SMTP id TAA00348; Fri, 19 Sep 1997 19:45:02 -0700 (PDT) Date: Fri, 19 Sep 1997 19:45:02 -0700 (PDT) From: "Jamil J. Weatherbee" To: Rob Miracle cc: freebsd-stable@FreeBSD.ORG Subject: Re: >8 char usernames going into 2.2.5? In-Reply-To: <3.0.3.32.19970919164456.0081b100@central.TanSoft.COM> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk What about something really, really useful like a tar that will tarball the dev files with 32bit minor numbers? On Fri, 19 Sep 1997, Rob Miracle wrote: > > Better than that, I've been hand patching 2.2-stable for some time now > >to support longer usernames > > >> Doug (who would really like to see this done :) > > What about something really useful, like 4 byte UIDs? > > Rob > > From owner-freebsd-stable Fri Sep 19 19:46:34 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id TAA27339 for stable-outgoing; Fri, 19 Sep 1997 19:46:34 -0700 (PDT) Received: from shell.futuresouth.com (shell.futuresouth.com [207.141.254.20]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id TAA27331 for ; Fri, 19 Sep 1997 19:46:28 -0700 (PDT) Received: (from tim@localhost) by shell.futuresouth.com (8.8.5/8.8.5) id VAA24561; Fri, 19 Sep 1997 21:46:20 -0500 (CDT) Message-ID: <19970919214620.01498@futuresouth.com> Date: Fri, 19 Sep 1997 21:46:20 -0500 From: Tim Tsai To: Studded Cc: "freebsd-stable@freebsd.org" Subject: Re: >8 char usernames going into 2.2.5? References: <199709192214.PAA16435@mail.san.rr.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.76 Sender: owner-freebsd-stable@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > While I'm askin', it would be nice if some chars besides > letters and numbers could sneak in there too. The one I would like > most is - (the dash) but I know there are other requests. (And yes, I > know about aliases. :) Having recently converted a garbage :-) bin full of Sun Solaris boxes to FreeBSD, I am happy to report that "." works in most places. chown doesn't like it, obviously, but in those few cases I just use the uid (but then again, there are users who has strictly numeric user names!!!). While it'd have been nice to enforce the rules to start with, there were several hundred existing users who violated the rules one way or the other and it'd have been too much of a headache to contact each user directly. Tim From owner-freebsd-stable Fri Sep 19 21:42:56 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id VAA03051 for stable-outgoing; Fri, 19 Sep 1997 21:42:56 -0700 (PDT) Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id VAA03046 for ; Fri, 19 Sep 1997 21:42:54 -0700 (PDT) Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.7/8.6.9) with ESMTP id VAA11924; Fri, 19 Sep 1997 21:43:01 -0700 (PDT) To: "Jamil J. Weatherbee" cc: Rob Miracle , freebsd-stable@FreeBSD.ORG Subject: Re: >8 char usernames going into 2.2.5? In-reply-to: Your message of "Fri, 19 Sep 1997 19:45:02 PDT." Date: Fri, 19 Sep 1997 21:43:00 -0700 Message-ID: <11916.874730580@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-stable@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Because it would be really, really stupid to make a version of tar which generated tarballs that couldn't be read anywhere else. If you want robust formats, use cpio with -H newc or pax or something. The format of the tar file is already fixed by historical convention, as has been pointed out here numerous times, and copying device files with it is just silly. It's the wrong tool for the job and you should use cpio, pax, dump or any of a number of more suitable backup-with-full-fidelity utilities. Jordan > > What about something really, really useful like a tar that will tarball > the dev files with 32bit minor numbers? > > On Fri, 19 Sep 1997, Rob Miracle wrote: > > > > Better than that, I've been hand patching 2.2-stable for some time now > > >to support longer usernames > > > > >> Doug (who would really like to see this done :) > > > > What about something really useful, like 4 byte UIDs? > > > > Rob > > > > > From owner-freebsd-stable Fri Sep 19 23:56:49 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id XAA18168 for stable-outgoing; Fri, 19 Sep 1997 23:56:49 -0700 (PDT) Received: from counterintelligence.ml.org (mdean.vip.best.com [206.86.94.101]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id XAA18163 for ; Fri, 19 Sep 1997 23:56:46 -0700 (PDT) Received: from localhost (jamil@localhost) by counterintelligence.ml.org (8.8.7/8.8.5) with SMTP id XAA00789; Fri, 19 Sep 1997 23:55:37 -0700 (PDT) Date: Fri, 19 Sep 1997 23:55:37 -0700 (PDT) From: "Jamil J. Weatherbee" To: "Jordan K. Hubbard" cc: Rob Miracle , freebsd-stable@FreeBSD.ORG Subject: Re: >8 char usernames going into 2.2.5? In-Reply-To: <11916.874730580@time.cdrom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Well, I use dump for now. But know that you mention it can someone explain the major differnces between Linux NFS and FreeBSD NFS. besides that one is in userspace etc. my problem is that being able to only put permissions on one node in a filesystem is a bit restrictive and inflexible. On Fri, 19 Sep 1997, Jordan K. Hubbard wrote: > Because it would be really, really stupid to make a version of tar > which generated tarballs that couldn't be read anywhere else. > > If you want robust formats, use cpio with -H newc or pax or something. > The format of the tar file is already fixed by historical convention, > as has been pointed out here numerous times, and copying device files > with it is just silly. It's the wrong tool for the job and you should > use cpio, pax, dump or any of a number of more suitable > backup-with-full-fidelity utilities. > > Jordan > > > > > What about something really, really useful like a tar that will tarball > > the dev files with 32bit minor numbers? > > > > On Fri, 19 Sep 1997, Rob Miracle wrote: > > > > > > Better than that, I've been hand patching 2.2-stable for some time now > > > >to support longer usernames > > > > > > >> Doug (who would really like to see this done :) > > > > > > What about something really useful, like 4 byte UIDs? > > > > > > Rob > > > > > > > > > > From owner-freebsd-stable Sat Sep 20 00:40:56 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id AAA25817 for stable-outgoing; Sat, 20 Sep 1997 00:40:56 -0700 (PDT) Received: from sabre.goldsword.com (sabre.goldsword.com [199.170.202.32]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id AAA25808 for ; Sat, 20 Sep 1997 00:40:52 -0700 (PDT) Received: (from jfarmer@localhost) by sabre.goldsword.com (8.7.5/8.7.3) id DAA28038; Sat, 20 Sep 1997 03:44:06 -0400 (EDT) Date: Sat, 20 Sep 1997 03:44:06 -0400 (EDT) From: "John T. Farmer" Message-Id: <199709200744.DAA28038@sabre.goldsword.com> To: jkh@time.cdrom.com, tom@uniserve.com Subject: Re: >8 char usernames going into 2.2.5? Cc: freebsd-stable@FreeBSD.ORG, jfarmer@goldsword.com, Studded@dal.net Sender: owner-freebsd-stable@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Fri, 19 Sep 1997 17:39:00 -0700 (PDT) Tom said: >On Fri, 19 Sep 1997, Jordan K. Hubbard wrote: >> > [Org. author's name lost...] >> > I remember a discussion a while back that the changes to allow >> > user names of greater than 8 characters that are presently working in >> > current would be back-ported to 2.2.x RSN. I'm wondering if this >> > change will be made in time for the 2.2.5 release. >> >> Hmm, I'm not sure who told you that but it was definitely never our >> intention to go to >8 character usernames in the 2.2-stable branch. >> There is too much potential upheaval associated with that change and >> so we've decided to take our lumps all at once with 3.0. >> >> Jordan > > I'd like to register strong disagreement with the above. The change >itself, is simple. It is going to affect packages that read/alter >utmp/wtmp/lastlog. However, since the packages will be re-built >everything will be ok, as long as people don't use old packages. I think >we should get this change behind us. It is only get to get worse. > > I'm also rather annoyned that BSDI has had 16 characters usernames for >over two years, and FreeBSD doesn't yet have a single release that does. >It makes FreeBSD look antiquated. > I have to agree with Tom. My clients _don't_ want to hear "You can have longer aliases but login names must be 8 charsacters or less." They don't care how it's implemented, they don't want to have to think about it. I recall discussions about this running back to the days of 2.1.5, etc. At that time, the arguement was "let's put 2.1.x to bed & put this on the list for -current (then 2.2...)." The point being, this is a change that has been talked about _forever_ and it's always been "a later release." I know the core team is under pressure to to get 2.2.5 out the door, but would it not be possible for one of the _several_ individuals who have done the mods to their system to submit a patch kit to the core team for testing & possible inclusion? John (Who's been there, booting the box out the door, patching all the way...) ------------------------------------------------------------------------- John T. Farmer Proprietor, GoldSword Systems jfarmer@goldsword.com Public Internet Access in East Tennessee dial-in (423)470-9953 for info, e-mail to info@goldsword.com Network Design, Internet Services & Servers, Consulting From owner-freebsd-stable Sat Sep 20 00:46:00 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id AAA26779 for stable-outgoing; Sat, 20 Sep 1997 00:46:00 -0700 (PDT) Received: from mail.uniserve.com (dns1-van.uniserve.com [204.244.163.48]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id AAA26760 for ; Sat, 20 Sep 1997 00:45:56 -0700 (PDT) Received: from shell.uniserve.com [204.244.210.252] by mail.uniserve.com with smtp (Exim 1.70 #1) id 0xCKEa-0004bV-00; Sat, 20 Sep 1997 00:45:44 -0700 Date: Sat, 20 Sep 1997 00:45:37 -0700 (PDT) From: Tom To: "John T. Farmer" cc: jkh@time.cdrom.com, freebsd-stable@freebsd.org, jfarmer@goldsword.com, Studded@dal.net Subject: Re: >8 char usernames going into 2.2.5? In-Reply-To: <199709200744.DAA28038@sabre.goldsword.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Sat, 20 Sep 1997, John T. Farmer wrote: > I have to agree with Tom. My clients _don't_ want to hear "You can have > longer aliases but login names must be 8 charsacters or less." They > don't care how it's implemented, they don't want to have to think about > it. If it that important, make the change yourself. I've been doing this change since before 2.1. I think this is finally starting to annoy me enough to put together a release of 2.2-stable with longer usernames. > I know the core team is under pressure to to get 2.2.5 out the door, > but would it not be possible for one of the _several_ individuals > who have done the mods to their system to submit a patch kit to > the core team for testing & possible inclusion? Why? The changes are in -current NOW. You can make the changes too, see utmp.h, and param.h. I know them well, as I've patching them for 2+ years now! > John (Who's been there, booting the box out the door, > patching all the way...) > > ------------------------------------------------------------------------- > John T. Farmer Proprietor, GoldSword Systems > jfarmer@goldsword.com Public Internet Access in East Tennessee > dial-in (423)470-9953 for info, e-mail to info@goldsword.com > Network Design, Internet Services & Servers, Consulting > Tom From owner-freebsd-stable Sat Sep 20 02:35:48 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id CAA18586 for stable-outgoing; Sat, 20 Sep 1997 02:35:48 -0700 (PDT) Received: from mail.san.rr.com (mail-atm.san.rr.com [204.210.0.1]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id CAA18570 for ; Sat, 20 Sep 1997 02:35:44 -0700 (PDT) Received: from dt5h1n61.san.rr.com (dt5h1n61.san.rr.com [204.210.31.97]) by mail.san.rr.com (8.8.7/8.8.7) with SMTP id CAA27068; Sat, 20 Sep 1997 02:33:58 -0700 (PDT) Message-Id: <199709200933.CAA27068@mail.san.rr.com> From: "Studded" To: "Jordan K. Hubbard" , "Tom" Cc: "freebsd-stable@FreeBSD.ORG" Date: Sat, 20 Sep 97 02:33:46 -0700 Reply-To: "Studded" Priority: Normal X-Mailer: PMMail 1.92 For OS/2 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Subject: Re: >8 char usernames going into 2.2.5? Sender: owner-freebsd-stable@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Sat, 20 Sep 1997 00:45:37 -0700 (PDT), Tom wrote: > Why? The changes are in -current NOW. You can make the changes too, >see utmp.h, and param.h. I know them well, as I've patching them for 2+ >years now! Perhaps you could write up a detailed list of instructions and post it to -questions? Also, what kind of problems have you encountered/overcome? Things that may seem obvious to you might be missed by a new person or non-programmer, so the more details the better. :) On Fri, 19 Sep 1997 18:47:59 -0700, Jordan K. Hubbard wrote: >Trust me, no matter how strong your disagreement with the above, there >are plenty of folks who will disagree even more strongly with the idea >of changing it. They don't want to have to update or convert in-place >all their log data (and some people have utmp/wtmp logs which are >archived for months and used to produce billing data) and for them, >2.2-stable represents the place to be when you don't want to suffer >from mid-stream changes like that. This may sound like a smart-ass question, but it's not intended to be. If I have a system that only allows 8 char usernames, and someone offers me a system that allows 16, what's going to break if *I* stick with the 8 chars I've always used? (And does this same argument hold true for the packages?) Also, aren't these few people with the systems you're talking about who are smart enough to cobble the things together in the first place also smart enough to change it *back* to 8 if the change is so easy? I'm a firm believer in backwards compatibility, and I understand the importance of supporting things that have "always worked." However the rc* changes that are being made in the 2.2 branch seem like a pretty big change to me, much bigger than what we're talking about with the length of usernames. I know quite a few people (myself included) who skipped the 2.2.2 fias... errr.. release altogether who will be seeing the changes in rc* for the first time with 2.2.5, so a good percentage of those who are upgrading will get all the changes at once if we do usernames now. Not to mention the fact that the move from -current to -release is an awful long way off to wait for a feature that is so frequently requested. Finally, my thanks to those who corrected me regarding allowable chars in usernames. Is there a canonical list available somewhere? Also, is someone planning to correct adduser? These may seem like trivial things, especially to people who know how to make the improvements themselves. However it's just this kind of stuff (like flexibility and accuracy in the available tools) that both make FreeBSD more user-friendly, AND flatten the learning/frustration curve for new users. Glad to see so much interest, Doug Do thou amend thy face, and I'll amend my life. -Shakespeare, "Henry V" From owner-freebsd-stable Sat Sep 20 04:02:49 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id EAA29692 for stable-outgoing; Sat, 20 Sep 1997 04:02:49 -0700 (PDT) Received: from seagull.cdrom.com (root@seagull.cdrom.com [204.216.27.14]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id EAA29656; Sat, 20 Sep 1997 04:01:38 -0700 (PDT) Received: from cons.org (knight.cons.org [194.233.237.86]) by seagull.cdrom.com (8.8.6/8.6.6) with ESMTP id EAA20704 ; Sat, 20 Sep 1997 04:01:23 -0700 (PDT) Received: (from cracauer@localhost) by cons.org (8.8.5/8.7.3) id NAA24791; Sat, 20 Sep 1997 13:01:53 +0200 (CEST) Message-ID: <19970920130153.53560@cons.org> Date: Sat, 20 Sep 1997 13:01:53 +0200 From: Martin Cracauer To: freebsd-stable@freebsd.org Cc: joerg@freebsd.org Subject: 2.2-stable problems Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.81 Sender: owner-freebsd-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Folks, [CC: to Joerg as wormcontrol meister] updating a 2.2.2 machine to 2.2-stable last week, I have two problems: 1) 'wormcontrol fixate' always fails with wormcontrol: ioctl(WORMIOFIXATION): Invalid argument The burner (Plasmon RF4100 1.26) worked without problems under 2.2.2. 2) I got an Adaptec 2940 hang with lots of console messages. I'm sorry to send such an undetailed report, but I'm under serious time pressure and this machine is a production system that had been rebootet immedeatly (by someone else before I could write the messages down). And is now being downgraded... I just though I should send this notice and ask that we do a 2.2.4 release instead of a 2.2.5, so that we don't damage the reputation of our .5 release ;-) Martin -- %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% Martin Cracauer http://www.cons.org/cracauer cracauer@wavehh.hanse.de (batched, preferred for large mails) Tel.: (daytime) +4940 41478712 Fax.: (daytime) +4940 41478715 Tel.: (private) +4940 5221829 Fax.: (private) +4940 5228536 Paper: (private) Waldstrasse 200, 22846 Norderstedt, Germany From owner-freebsd-stable Sat Sep 20 04:25:41 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id EAA00679 for stable-outgoing; Sat, 20 Sep 1997 04:25:41 -0700 (PDT) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id EAA00667; Sat, 20 Sep 1997 04:25:34 -0700 (PDT) Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id NAA12467; Sat, 20 Sep 1997 13:25:28 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.8.7/8.8.5) id NAA23701; Sat, 20 Sep 1997 13:23:12 +0200 (MET DST) Message-ID: <19970920132312.OX18440@uriah.heep.sax.de> Date: Sat, 20 Sep 1997 13:23:12 +0200 From: j@uriah.heep.sax.de (J Wunsch) To: cracauer@cons.org (Martin Cracauer) Cc: freebsd-stable@freebsd.org, jmz@freebsd.org Subject: Re: 2.2-stable problems References: <19970920130153.53560@cons.org> X-Mailer: Mutt 0.60_p2-3,5,8-9 Mime-Version: 1.0 X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <19970920130153.53560@cons.org>; from Martin Cracauer on Sep 20, 1997 13:01:53 +0200 Sender: owner-freebsd-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk As Martin Cracauer wrote: > Folks, [CC: to Joerg as wormcontrol meister] > > updating a 2.2.2 machine to 2.2-stable last week, I have two problems: > > 1) 'wormcontrol fixate' always fails with > wormcontrol: ioctl(WORMIOFIXATION): Invalid argument > > The burner (Plasmon RF4100 1.26) worked without problems under 2.2.2. I've also noticed this last week after an upgrade. I've already told Jean-Marc about it, but didn't investigate yet. Manual fixation worked around the problem for me... -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-stable Sat Sep 20 06:04:42 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id GAA03897 for stable-outgoing; Sat, 20 Sep 1997 06:04:42 -0700 (PDT) Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id GAA03891 for ; Sat, 20 Sep 1997 06:04:38 -0700 (PDT) Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.7/8.6.9) with ESMTP id GAA27013; Sat, 20 Sep 1997 06:04:44 -0700 (PDT) To: "John T. Farmer" cc: tom@uniserve.com, freebsd-stable@FreeBSD.ORG, jfarmer@goldsword.com, Studded@dal.net Subject: Re: >8 char usernames going into 2.2.5? In-reply-to: Your message of "Sat, 20 Sep 1997 03:44:06 EDT." <199709200744.DAA28038@sabre.goldsword.com> Date: Sat, 20 Sep 1997 06:04:44 -0700 Message-ID: <27009.874760684@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-stable@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > I know the core team is under pressure to to get 2.2.5 out the door, Our decision to avoid this change has nothing to do with time pressures. It has to do with prudence. > but would it not be possible for one of the _several_ individuals > who have done the mods to their system to submit a patch kit to > the core team for testing & possible inclusion? Here, enjoy. :-) Index: sys/sys/param.h =================================================================== RCS file: /home/ncvs/src/sys/sys/param.h,v retrieving revision 1.15.2.2 diff -u -r1.15.2.2 param.h --- param.h 1996/12/15 09:54:28 1.15.2.2 +++ param.h 1997/09/20 13:04:06 @@ -65,7 +65,7 @@ #define MAXCOMLEN 16 /* max command name remembered */ #define MAXINTERP 32 /* max interpreter file name length */ -#define MAXLOGNAME 12 /* max login name length */ +#define MAXLOGNAME 17 /* max login name length */ #define MAXUPRC CHILD_MAX /* max simultaneous processes */ #define NCARGS ARG_MAX /* max bytes for an exec function */ #define NGROUPS NGROUPS_MAX /* max number groups */ Index: include/utmp.h =================================================================== RCS file: /home/ncvs/src/include/utmp.h,v retrieving revision 1.2 diff -u -r1.2 utmp.h --- utmp.h 1996/10/27 18:13:35 1.2 +++ utmp.h 1997/09/20 13:03:42 @@ -46,7 +46,7 @@ #define _PATH_WTMP "/var/log/wtmp" #define _PATH_LASTLOG "/var/log/lastlog" -#define UT_NAMESIZE 8 /* see MAXLOGNAME in */ +#define UT_NAMESIZE 16 /* see MAXLOGNAME in */ #define UT_LINESIZE 8 #define UT_HOSTSIZE 16 From owner-freebsd-stable Sat Sep 20 06:22:32 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id GAA04660 for stable-outgoing; Sat, 20 Sep 1997 06:22:32 -0700 (PDT) Received: from salmon.maths.tcd.ie (mmdf@salmon.maths.tcd.ie [134.226.81.11]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id GAA04653 for ; Sat, 20 Sep 1997 06:22:27 -0700 (PDT) Received: from graves.maths.tcd.ie by salmon.maths.tcd.ie with SMTP id aa15726; 20 Sep 97 14:22 +0100 To: Studded cc: freebsd-stable@freebsd.org Subject: Re: >8 char usernames going into 2.2.5? In-reply-to: Your message of "Sat, 20 Sep 1997 02:33:46 PDT." <199709200933.CAA27068@mail.san.rr.com> Date: Sat, 20 Sep 1997 14:22:21 +0100 From: David Malone Message-ID: <9709201422.aa15726@salmon.maths.tcd.ie> Sender: owner-freebsd-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > If I have a system that only allows 8 char usernames, and someone offers me > a system that allows 16, what's going to break if *I* stick with the 8 > chars I've always used? (And does this same argument hold true for the > packages?) Both utmp and wtmp have a 8 characters allocaked for usernames, and this number is compiled into all programs that read or write these files. The structure in this file should corrispond exactly to the structure detailed in utmp (5). If you change the size of the structure all these programs will break. These programs are likely to include people's local accounting scripts and the like. Breaking these would not be acceptable to many people. > Also, aren't these few people with the systems you're > talking about who are smart enough to cobble the things together in > the first place also smart enough to change it *back* to 8 if the > change is so easy? 2.2.5 is more of an upgrade - 3.0 will be a whole new release. 2.2.5 as it stands is essentially a binary "drop in" replacement for 2.2.? - the only binaries that I can think of that are not interchangeable are kernel related ones. > worked." However the rc* changes that are being made in the 2.2 branch > seem like a pretty big change to me, much bigger than what we're > talking about with the length of usernames. If you install via the "make world" route you probably won't have to deal with the rc.* changes. I've done several 2.2-STABLE upgrades, and haven't touched the rc.* files yet and everything still works fine. I suspect the same is true of the sysinstall upgrade route, as it doesn't change much (anything?) in /etc. David. From owner-freebsd-stable Sat Sep 20 07:31:03 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id HAA07338 for stable-outgoing; Sat, 20 Sep 1997 07:31:03 -0700 (PDT) Received: from seagull.cdrom.com (root@seagull.cdrom.com [204.216.27.14]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id HAA07330; Sat, 20 Sep 1997 07:31:00 -0700 (PDT) Received: from cons.org (knight.cons.org [194.233.237.86]) by seagull.cdrom.com (8.8.6/8.6.6) with ESMTP id HAA21012 ; Sat, 20 Sep 1997 07:30:56 -0700 (PDT) Received: (from cracauer@localhost) by cons.org (8.8.5/8.7.3) id QAA25048; Sat, 20 Sep 1997 16:31:22 +0200 (CEST) Message-ID: <19970920163121.26878@cons.org> Date: Sat, 20 Sep 1997 16:31:21 +0200 From: Martin Cracauer To: Joerg Wunsch Cc: Martin Cracauer , freebsd-stable@freebsd.org, jmz@freebsd.org Subject: Re: 2.2-stable problems References: <19970920130153.53560@cons.org> <19970920132312.OX18440@uriah.heep.sax.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.81 In-Reply-To: <19970920132312.OX18440@uriah.heep.sax.de>; from J Wunsch on Sat, Sep 20, 1997 at 01:23:12PM +0200 Sender: owner-freebsd-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk In <19970920132312.OX18440@uriah.heep.sax.de>, J Wunsch wrote: > As Martin Cracauer wrote: > > > Folks, [CC: to Joerg as wormcontrol meister] > > > > updating a 2.2.2 machine to 2.2-stable last week, I have two problems: > > > > 1) 'wormcontrol fixate' always fails with > > wormcontrol: ioctl(WORMIOFIXATION): Invalid argument > > > > The burner (Plasmon RF4100 1.26) worked without problems under 2.2.2. > > I've also noticed this last week after an upgrade. I've already told > Jean-Marc about it, but didn't investigate yet. > > Manual fixation worked around the problem for me... Manual? I thought the ioctl(fd, WORMIOCFIXATION, &f) (used in wormcontrol.c) is the only interface we have to the burner and that apparently got out of sync with the kernel. What other way to go? I think a friend of mine has some old Roentgenlaser, built after a famous old german book. Which track do I need to shoot at? I think that beast can burn holes in steel, should be sufficient :-] BTW, as expected booting a 2.2.2-kernel on a 2.2-stable world made wormcontrol work again. Martin -- %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% Martin Cracauer http://www.cons.org/cracauer cracauer@wavehh.hanse.de (batched, preferred for large mails) Tel.: (daytime) +4940 41478712 Fax.: (daytime) +4940 41478715 Tel.: (private) +4940 5221829 Fax.: (private) +4940 5228536 Paper: (private) Waldstrasse 200, 22846 Norderstedt, Germany From owner-freebsd-stable Sat Sep 20 07:54:19 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id HAA08452 for stable-outgoing; Sat, 20 Sep 1997 07:54:19 -0700 (PDT) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id HAA08446; Sat, 20 Sep 1997 07:54:16 -0700 (PDT) Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id QAA13822; Sat, 20 Sep 1997 16:54:12 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.8.7/8.8.5) id QAA29157; Sat, 20 Sep 1997 16:40:14 +0200 (MET DST) Message-ID: <19970920164012.XF09580@uriah.heep.sax.de> Date: Sat, 20 Sep 1997 16:40:12 +0200 From: j@uriah.heep.sax.de (J Wunsch) To: cracauer@cons.org (Martin Cracauer) Cc: freebsd-stable@freebsd.org, jmz@freebsd.org Subject: Re: 2.2-stable problems References: <19970920130153.53560@cons.org> <19970920132312.OX18440@uriah.heep.sax.de> <19970920163121.26878@cons.org> X-Mailer: Mutt 0.60_p2-3,5,8-9 Mime-Version: 1.0 X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <19970920163121.26878@cons.org>; from Martin Cracauer on Sep 20, 1997 16:31:21 +0200 Sender: owner-freebsd-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk As Martin Cracauer wrote: > > Manual fixation worked around the problem for me... > > Manual? > > I thought the ioctl(fd, WORMIOCFIXATION, &f) (used in wormcontrol.c) is > the only interface we have to the burner and that apparently got out > of sync with the kernel. Of course not. :) scsi -f /dev/rworm0.ctl -c "xxxxx" does essentially the same... Sorry, don't know offhand what the xxxxx must be, the manual's at work right now. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-stable Sat Sep 20 08:41:34 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id IAA10901 for stable-outgoing; Sat, 20 Sep 1997 08:41:34 -0700 (PDT) Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id IAA10895; Sat, 20 Sep 1997 08:41:32 -0700 (PDT) Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.7/8.6.9) with ESMTP id IAA28334; Sat, 20 Sep 1997 08:41:40 -0700 (PDT) To: Martin Cracauer cc: Joerg Wunsch , freebsd-stable@FreeBSD.ORG, jmz@FreeBSD.ORG Subject: Re: 2.2-stable problems In-reply-to: Your message of "Sat, 20 Sep 1997 16:31:21 +0200." <19970920163121.26878@cons.org> Date: Sat, 20 Sep 1997 08:41:40 -0700 Message-ID: <28330.874770100@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-stable@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > What other way to go? I think a friend of mine has some old > Roentgenlaser, built after a famous old german book. Which track do I > need to shoot at? I think that beast can burn holes in steel, should > be sufficient :-] Please send me the plans - this sounds interesting. :-) > BTW, as expected booting a 2.2.2-kernel on a 2.2-stable world made > wormcontrol work again. Hmmmm. This should probably be fixed before 2.2.5 goes out. Any ideas? :) Jordan From owner-freebsd-stable Sat Sep 20 09:19:17 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id JAA12814 for stable-outgoing; Sat, 20 Sep 1997 09:19:17 -0700 (PDT) Received: from david.siemens.de (david.siemens.de [139.23.36.11]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id JAA12804 for ; Sat, 20 Sep 1997 09:19:12 -0700 (PDT) Received: from salomon.mchp.siemens.de (salomon.siemens.de [139.23.33.13]) by david.siemens.de (8.8.7/8.8.5) with ESMTP id SAA07159 for ; Sat, 20 Sep 1997 18:19:00 +0200 (MDT) Received: from curry.mchp.siemens.de (daemon@curry.mchp.siemens.de [146.180.31.23]) by salomon.mchp.siemens.de (8.8.7/8.8.5) with ESMTP id SAA02124 for ; Sat, 20 Sep 1997 18:19:09 +0200 (MDT) Received: (from daemon@localhost) by curry.mchp.siemens.de (8.8.7/8.8.7) id SAA13191 for ; Sat, 20 Sep 1997 18:19:08 +0200 (MET DST) From: Andre Albsmeier Message-Id: <199709201618.SAA01148@curry.mchp.siemens.de> Subject: fsck runs out of memory during boot To: freebsd-stable@freebsd.org Date: Sat, 20 Sep 1997 18:18:58 +0200 (CEST) X-Mailer: ELM [version 2.4ME+ PL31 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi, after installing the newest version of 2.2-STABLE, one of my machines doesn't boot properly anymore. I think it's fsck which runs out of memory. I have no idea what has changed and how to prevent this problem. I have attached the output during boot and the df of the disks (which is rather much :-)). I am fsck'ing the root with passno of 1 and the rest with 2. The rest is all together 60GB so perhaps this is simply to much for fsck... The machine has 64M phys. and 150M swap... Any hints? Thanks, -Andre ----- boot output ----- ccd0-2: Concatenated disk drivers swapon: adding /dev/sd0b as swap device Automatic reboot in progress... /dev/rsd0a: clean, 234610 free (9626 frags, 28123 blocks, 2.6% fragmentation) /dev/rsd10c: clean, 842274 free (386 frags, 105236 blocks, 0.0% fragmentation) /dev/rsd12c: clean, 470238 free (822 frags, 58677 blocks, 0.1% fragmentation) /dev/rsd13c: clean, 509037 free (309 frags, 63591 blocks, 0.0% fragmentation) /dev/rsd11c: clean, 155358 free (1406 frags, 19244 blocks, 0.1% fragmentation) /dev/rccd0c: clean, 3642368 free (15392 frags, 453372 blocks, 0.2% fragmentation ) cannot alloc 8340482 bytes for lncntp /dev/rccd1c: CAN'T CHECK FILE SYSTEM. /dev/rccd1c: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY. /dev/rccd2c: clean, 1759345 free (10417 frags, 218616 blocks, 0.1% fragmentation ) cannot alloc 10629122 bytes for lncntp /dev/rsd5c: CAN'T CHECK FILE SYSTEM. /dev/rsd5c: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY. THE FOLLOWING FILE SYSTEMS HAD AN UNEXPECTED INCONSISTENCY: /dev/rccd1c (/people), /dev/rsd5c (/hold) Automatic file system check failed... help! Enter root password, or ^D to go multi-user ----- df ----- Filesystem 1K-blocks Used Avail Capacity Mounted on /dev/sd0a 373519 115034 228604 33% / /dev/sd5c 21985903 1 20227030 0% /hold /dev/ccd0c 8148667 4508890 2987884 60% /server /dev/ccd1c 17251511 1775830 14095561 11% /people /dev/ccd2c 8136763 6377418 1108404 85% /pc /dev/sd10c 985535 143261 763432 16% /pc2/mac /dev/sd11c 985535 830177 76516 92% /pc2/share /dev/sd12c 1341165 870927 362945 71% /pc2/prog /dev/sd13c 2016793 1507756 347694 81% /pc2/cd From owner-freebsd-stable Sat Sep 20 09:55:57 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id JAA15080 for stable-outgoing; Sat, 20 Sep 1997 09:55:57 -0700 (PDT) Received: from mail.uniserve.com (dns1-van.uniserve.com [204.244.163.48]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id JAA15075 for ; Sat, 20 Sep 1997 09:55:53 -0700 (PDT) Received: from shell.uniserve.com [204.244.210.252] by mail.uniserve.com with smtp (Exim 1.70 #1) id 0xCSoC-0006Ku-00; Sat, 20 Sep 1997 09:55:04 -0700 Date: Sat, 20 Sep 1997 09:55:01 -0700 (PDT) From: Tom To: Andre Albsmeier cc: freebsd-stable@freebsd.org Subject: Re: fsck runs out of memory during boot In-Reply-To: <199709201618.SAA01148@curry.mchp.siemens.de> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Sat, 20 Sep 1997, Andre Albsmeier wrote: > Hi, > > after installing the newest version of 2.2-STABLE, one of my > machines doesn't boot properly anymore. I think it's fsck which > runs out of memory. I have no idea what has changed and how to The "daemon" class in login.conf is supposed to control what limits are given to things run out of rc. I found that modifying "daemon" was ineffective for the fsck problem. I stuck a "csh -c limit" line into rc just before the fsck so the current limits would be printed during boot. I eventutally just changed the "default" class. Tom From owner-freebsd-stable Sat Sep 20 10:08:54 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id KAA15914 for stable-outgoing; Sat, 20 Sep 1997 10:08:54 -0700 (PDT) Received: from netcom1.netcom.com (mvh@netcom13.netcom.com [192.100.81.125]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id KAA15909 for ; Sat, 20 Sep 1997 10:08:47 -0700 (PDT) Received: (from mvh@localhost) by netcom1.netcom.com (8.8.7/8.8.7) id KAA26843; Sat, 20 Sep 1997 10:08:45 -0700 (PDT) Date: Sat, 20 Sep 1997 10:08:45 -0700 (PDT) Message-Id: <199709201708.KAA26843@netcom1.netcom.com> From: "Michael V. Harding" To: freebsd-stable@FreeBSD.ORG Subject: Longer passwords in 2.2.5 Sender: owner-freebsd-stable@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Let's put these instructions in the handbook, FAQ, O.K.? It would be nice to know it was there if I need it in the future... Also, are there any side effects if I change this on a running system? Would I need to flush 'wtmp', etc? I have a system with about 100 e-mail (pop) clients - what would I need to do to make passwords longer on a live system? -- Mike Harding From owner-freebsd-stable Sat Sep 20 10:26:17 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id KAA16930 for stable-outgoing; Sat, 20 Sep 1997 10:26:17 -0700 (PDT) Received: from ns.mt.sri.com (SRI-56K-FR.mt.net [206.127.65.42]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id KAA16922 for ; Sat, 20 Sep 1997 10:26:14 -0700 (PDT) Received: from rocky.mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by ns.mt.sri.com (8.8.7/8.8.7) with ESMTP id LAA27468; Sat, 20 Sep 1997 11:25:56 -0600 (MDT) Received: (from nate@localhost) by rocky.mt.sri.com (8.7.5/8.7.3) id LAA24051; Sat, 20 Sep 1997 11:25:54 -0600 (MDT) Date: Sat, 20 Sep 1997 11:25:54 -0600 (MDT) Message-Id: <199709201725.LAA24051@rocky.mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Tom Cc: "Jordan K. Hubbard" , "freebsd-stable@freebsd.org" Subject: Re: >8 char usernames going into 2.2.5? In-Reply-To: References: <19929.874708211@time.cdrom.com> X-Mailer: VM 6.29 under 19.15 XEmacs Lucid Sender: owner-freebsd-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Jordan writes: > it was definitely never our > intention to go to >8 character usernames in the 2.2-stable branch. > > I'd like to register strong disagreement with the above. And I'd like to register my full support that it stay. So, who wins? :) (It's a change that goes against the charter of -stable, so it should stay out.) Nate From owner-freebsd-stable Sat Sep 20 10:26:29 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id KAA16955 for stable-outgoing; Sat, 20 Sep 1997 10:26:29 -0700 (PDT) Received: from cabri.obs-besancon.fr (cabri.obs-besancon.fr [193.52.184.3]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id KAA16950 for ; Sat, 20 Sep 1997 10:26:22 -0700 (PDT) Received: by cabri.obs-besancon.fr (5.57/Ultrix3.0-C) id AA21491; Sat, 20 Sep 97 19:27:19 +0100 Date: Sat, 20 Sep 97 19:27:19 +0100 Message-Id: <9709201827.AA21491@cabri.obs-besancon.fr> From: Jean-Marc Zucconi To: cracauer@cons.org Cc: joerg_wunsch@uriah.heep.sax.de, cracauer@cons.org, freebsd-stable@freebsd.org In-Reply-To: <19970920163121.26878@cons.org> (message from Martin Cracauer on Sat, 20 Sep 1997 16:31:21 +0200) Subject: Re: 2.2-stable problems X-Mailer: Emacs Mime-Version: 1.0 (generated by tm-edit 7.106) Content-Type: text/plain; charset=US-ASCII Sender: owner-freebsd-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >>>>> Martin Cracauer writes: > In <19970920132312.OX18440@uriah.heep.sax.de>, J Wunsch wrote: >> As Martin Cracauer wrote: >> >> > Folks, [CC: to Joerg as wormcontrol meister] >> > >> > updating a 2.2.2 machine to 2.2-stable last week, I have two problems: >> > >> > 1) 'wormcontrol fixate' always fails with >> > wormcontrol: ioctl(WORMIOFIXATION): Invalid argument >> > >> > The burner (Plasmon RF4100 1.26) worked without problems under 2.2.2. >> >> I've also noticed this last week after an upgrade. I've already told >> Jean-Marc about it, but didn't investigate yet. >> >> Manual fixation worked around the problem for me... > Manual? > I thought the ioctl(fd, WORMIOCFIXATION, &f) (used in wormcontrol.c) is > the only interface we have to the burner and that apparently got out > of sync with the kernel. Try scsi -f /dev/rworm0.ctl -s 3600 -c "e9 0 0 0 0 0 0 0 1 0" if this does not work, then try scsi -f /dev/rworm0.ctl -s 3600 -c "35 0 0 0 0 0 0 0 0 0" followed by scsi -f /dev/rworm0.ctl -s 3600 -c "e9 0 0 0 0 0 0 0 1 0" > What other way to go? I think a friend of mine has some old > Roentgenlaser, built after a famous old german book. Which track do I > need to shoot at? I think that beast can burn holes in steel, should > be sufficient :-] > BTW, as expected booting a 2.2.2-kernel on a 2.2-stable world made > wormcontrol work again. So this means that the the bug is in wormcontrol rather than in the driver ?? Jean-Marc _____________________________________________________________________________ Jean-Marc Zucconi Observatoire de Besancon F 25010 Besancon cedex PGP Key: finger jmz@cabri.obs-besancon.fr From owner-freebsd-stable Sat Sep 20 10:26:40 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id KAA16986 for stable-outgoing; Sat, 20 Sep 1997 10:26:40 -0700 (PDT) Received: from sabre.goldsword.com (sabre.goldsword.com [199.170.202.32]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id KAA16981 for ; Sat, 20 Sep 1997 10:26:37 -0700 (PDT) Received: (from jfarmer@localhost) by sabre.goldsword.com (8.7.5/8.7.3) id NAA28866; Sat, 20 Sep 1997 13:29:47 -0400 (EDT) Date: Sat, 20 Sep 1997 13:29:47 -0400 (EDT) From: "John T. Farmer" Message-Id: <199709201729.NAA28866@sabre.goldsword.com> To: jfarmer@sabre.goldsword.com, tom@uniserve.com Subject: Re: >8 char usernames going into 2.2.5? Cc: freebsd-stable@FreeBSD.ORG, jfarmer@goldsword.com, jkh@time.cdrom.com, Studded@dal.net Sender: owner-freebsd-stable@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Sat, 20 Sep 1997 00:45:37 -0700 (PDT) Tom said: >On Sat, 20 Sep 1997, John T. Farmer wrote: >> I have to agree with Tom. My clients _don't_ want to hear "You can have >> longer aliases but login names must be 8 charsacters or less." They >> don't care how it's implemented, they don't want to have to think about >> it. > > If it that important, make the change yourself. I've been doing this >change since before 2.1. I think this is finally starting to annoy me >enough to put together a release of 2.2-stable with longer usernames. > >> I know the core team is under pressure to to get 2.2.5 out the door, >> but would it not be possible for one of the _several_ individuals >> who have done the mods to their system to submit a patch kit to >> the core team for testing & possible inclusion? > > Why? The changes are in -current NOW. You can make the changes too, >see utmp.h, and param.h. I know them well, as I've patching them for 2+ >years now! Hummmmm. Teach me to respond at 3 "in the blessed am" morning! I have a new mail server for a client here on the table. Since they're one of the ones asking about usernames, etc., I think it's time to do a make world! (Got some other kernel kustomizing to do also.) I see in other followups, there is an issue about remaining compatible such that packages would build/work properly for all 2.2.x versions. My understanding was that this wasn't necessarily guaranteed? John ------------------------------------------------------------------------- John T. Farmer Proprietor, GoldSword Systems jfarmer@goldsword.com Public Internet Access in East Tennessee dial-in (423)470-9953 for info, e-mail to info@goldsword.com Network Design, Internet Services & Servers, Consulting From owner-freebsd-stable Sat Sep 20 10:31:15 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id KAA17254 for stable-outgoing; Sat, 20 Sep 1997 10:31:15 -0700 (PDT) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id KAA17249 for ; Sat, 20 Sep 1997 10:31:12 -0700 (PDT) Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id TAA16257; Sat, 20 Sep 1997 19:31:09 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.8.7/8.8.5) id TAA00533; Sat, 20 Sep 1997 19:30:31 +0200 (MET DST) Message-ID: <19970920193031.DH29972@uriah.heep.sax.de> Date: Sat, 20 Sep 1997 19:30:31 +0200 From: j@uriah.heep.sax.de (J Wunsch) To: jmz@cabri.obs-besancon.fr (Jean-Marc Zucconi) Cc: cracauer@cons.org, freebsd-stable@freebsd.org Subject: Re: 2.2-stable problems References: <19970920163121.26878@cons.org> <9709201827.AA21491@cabri.obs-besancon.fr> X-Mailer: Mutt 0.60_p2-3,5,8-9 Mime-Version: 1.0 X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <9709201827.AA21491@cabri.obs-besancon.fr>; from Jean-Marc Zucconi on Sep 20, 1997 19:27:19 +0100 Sender: owner-freebsd-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk As Jean-Marc Zucconi wrote: > > BTW, as expected booting a 2.2.2-kernel on a 2.2-stable world made > > wormcontrol work again. > > So this means that the the bug is in wormcontrol rather than in the > driver ?? No. wormcontrol is just a stub wiring the worm(4) ioctls into userland. The bug must be in the kernel, but i didn't have the time to track it down yet either. I agree that it's a show-stopper for 2.2.5. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-stable Sat Sep 20 10:42:02 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id KAA17817 for stable-outgoing; Sat, 20 Sep 1997 10:42:02 -0700 (PDT) Received: from ns.mt.sri.com (SRI-56K-FR.mt.net [206.127.65.42]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id KAA17806 for ; Sat, 20 Sep 1997 10:41:57 -0700 (PDT) Received: from rocky.mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by ns.mt.sri.com (8.8.7/8.8.7) with ESMTP id LAA27548; Sat, 20 Sep 1997 11:41:45 -0600 (MDT) Received: (from nate@localhost) by rocky.mt.sri.com (8.7.5/8.7.3) id LAA24087; Sat, 20 Sep 1997 11:41:44 -0600 (MDT) Date: Sat, 20 Sep 1997 11:41:44 -0600 (MDT) Message-Id: <199709201741.LAA24087@rocky.mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: "Studded" Cc: "Jordan K. Hubbard" , "freebsd-stable@FreeBSD.ORG" Subject: Re: >8 char usernames going into 2.2.5? In-Reply-To: <199709200933.CAA27068@mail.san.rr.com> References: <199709200933.CAA27068@mail.san.rr.com> X-Mailer: VM 6.29 under 19.15 XEmacs Lucid Sender: owner-freebsd-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > I'm a firm believer in backwards compatibility, and I > understand the importance of supporting things that have "always > worked." However the rc* changes that are being made in the 2.2 branch > seem like a pretty big change to me, much bigger than what we're > talking about with the length of usernames. Bullocks. 1) You don't have to use the rc changes, and the system will work *FINE*, w/out any modification (and with them). 2) Programs that once worked will still continue to work (see above), but with the username changes, programs that worked fine under a previous release will now corrupt your system files /var/run/*tmp. Programs that use the size of usernames (read, almost all useful programs) will need to be re-compiled/re-installed. It's a 'big deal', although it's a simple change. If it's such a big deal to you, do it yourself, but don't screw me over just because you're too lazy to take the time to do it. 'Principle of least suprise.' Nate From owner-freebsd-stable Sat Sep 20 10:45:06 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id KAA18015 for stable-outgoing; Sat, 20 Sep 1997 10:45:06 -0700 (PDT) Received: from sabre.goldsword.com (sabre.goldsword.com [199.170.202.32]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id KAA18008 for ; Sat, 20 Sep 1997 10:45:02 -0700 (PDT) Received: (from jfarmer@localhost) by sabre.goldsword.com (8.7.5/8.7.3) id NAA28912; Sat, 20 Sep 1997 13:48:16 -0400 (EDT) Date: Sat, 20 Sep 1997 13:48:16 -0400 (EDT) From: "John T. Farmer" Message-Id: <199709201748.NAA28912@sabre.goldsword.com> To: jkh@time.cdrom.com Subject: Re: >8 char usernames going into 2.2.5? Cc: freebsd-stable@FreeBSD.ORG, jfarmer@goldsword.com, Studded@dal.net, tom@uniserve.com Sender: owner-freebsd-stable@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk [Contents of patch listing deleted (but saved on my machine!)] Jordan, Thanks. Since the machine that is of most concern here is a client's new mail server, there's no historical files to worry about (as someone pointed out...). I'll worry about my mail server later! (First have to get Merit Radius to understand > 8 char names...) John ------------------------------------------------------------------------- John T. Farmer Proprietor, GoldSword Systems jfarmer@goldsword.com Public Internet Access in East Tennessee dial-in (423)470-9953 for info, e-mail to info@goldsword.com Network Design, Internet Services & Servers, Consulting From owner-freebsd-stable Sat Sep 20 11:59:46 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id LAA21841 for stable-outgoing; Sat, 20 Sep 1997 11:59:46 -0700 (PDT) Received: from david.siemens.de (david.siemens.de [139.23.36.11]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id LAA21836 for ; Sat, 20 Sep 1997 11:59:44 -0700 (PDT) Received: from salomon.mchp.siemens.de (salomon.siemens.de [139.23.33.13]) by david.siemens.de (8.8.7/8.8.5) with ESMTP id UAA02321 for ; Sat, 20 Sep 1997 20:59:32 +0200 (MDT) Received: from curry.mchp.siemens.de (daemon@curry.mchp.siemens.de [146.180.31.23]) by salomon.mchp.siemens.de (8.8.7/8.8.5) with ESMTP id UAA11653 for ; Sat, 20 Sep 1997 20:59:40 +0200 (MDT) Received: (from daemon@localhost) by curry.mchp.siemens.de (8.8.7/8.8.7) id UAA13567 for ; Sat, 20 Sep 1997 20:59:39 +0200 (MET DST) From: Andre Albsmeier Message-Id: <199709201859.UAA16138@curry.mchp.siemens.de> Subject: Re: fsck runs out of memory during boot In-Reply-To: from Tom at "Sep 20, 97 09:55:01 am" To: tom@uniserve.com (Tom) Date: Sat, 20 Sep 1997 20:59:37 +0200 (CEST) Cc: freebsd-stable@freebsd.org X-Mailer: ELM [version 2.4ME+ PL31 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > On Sat, 20 Sep 1997, Andre Albsmeier wrote: > > > Hi, > > > > after installing the newest version of 2.2-STABLE, one of my > > machines doesn't boot properly anymore. I think it's fsck which > > runs out of memory. I have no idea what has changed and how to > > The "daemon" class in login.conf is supposed to control what limits are > given to things run out of rc. > > I found that modifying "daemon" was ineffective for the fsck problem. I > stuck a "csh -c limit" line into rc just before the fsck so the current > limits would be printed during boot. I eventutally just changed the > "default" class. Well, I fiddled with "daemon" as well but it didn't work... Will try the limit in rc on monday. Thanks, -Andre From owner-freebsd-stable Sat Sep 20 13:07:03 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id NAA24556 for stable-outgoing; Sat, 20 Sep 1997 13:07:03 -0700 (PDT) Received: from nevis.oss.uswest.net (nevis.oss.uswest.net [204.147.85.3]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id NAA24548 for ; Sat, 20 Sep 1997 13:07:01 -0700 (PDT) Received: (from greg@localhost) by nevis.oss.uswest.net (8.8.5/8.8.2) id PAA09359; Sat, 20 Sep 1997 15:06:59 -0500 (CDT) From: "Greg Rowe" Message-Id: <9709201506.ZM9357@nevis.oss.uswest.net> Date: Sat, 20 Sep 1997 15:06:59 -0500 In-Reply-To: "Jordan K. Hubbard" "Re: >8 char usernames going into 2.2.5?" (Sep 20, 6:04am) References: <27009.874760684@time.cdrom.com> X-Mailer: Z-Mail (3.2.1 10oct95) To: "Jordan K. Hubbard" , freebsd-stable@FreeBSD.ORG Subject: Re: >8 char usernames going into 2.2.5? Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-stable@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk This seems to work fine (at least on 2.2-STABLE with a "make world") except when I try and use telnet or rlogin with a 16 character username. FTP is OK, and 15 character or less un's are OK (yes I have 17 for MAXLOGNAME). A 16 character username returns: login: setlogin(testtesttesttest): Invalid argument login: setlogin(testtesttesttest): Invalid argument login: setusercontext() failed - exiting login: setusercontext() failed - exiting I only noticed one other person in the mail archives seeing this problem. Is anyone else encountering it ??? Thanks Greg On Sep 20, 6:04am, Jordan K. Hubbard wrote: > Subject: Re: >8 char usernames going into 2.2.5? > > I know the core team is under pressure to to get 2.2.5 out the door, > > Our decision to avoid this change has nothing to do with time > pressures. It has to do with prudence. > > > but would it not be possible for one of the _several_ individuals > > who have done the mods to their system to submit a patch kit to > > the core team for testing & possible inclusion? > > Here, enjoy. :-) > > Index: sys/sys/param.h > =================================================================== > RCS file: /home/ncvs/src/sys/sys/param.h,v > retrieving revision 1.15.2.2 > diff -u -r1.15.2.2 param.h > --- param.h 1996/12/15 09:54:28 1.15.2.2 > +++ param.h 1997/09/20 13:04:06 > @@ -65,7 +65,7 @@ > > #define MAXCOMLEN 16 /* max command name remembered */ > #define MAXINTERP 32 /* max interpreter file name length */ > -#define MAXLOGNAME 12 /* max login name length */ > +#define MAXLOGNAME 17 /* max login name length */ > #define MAXUPRC CHILD_MAX /* max simultaneous processes */ > #define NCARGS ARG_MAX /* max bytes for an exec function */ > #define NGROUPS NGROUPS_MAX /* max number groups */ > Index: include/utmp.h > =================================================================== > RCS file: /home/ncvs/src/include/utmp.h,v > retrieving revision 1.2 > diff -u -r1.2 utmp.h > --- utmp.h 1996/10/27 18:13:35 1.2 > +++ utmp.h 1997/09/20 13:03:42 > @@ -46,7 +46,7 @@ > #define _PATH_WTMP "/var/log/wtmp" > #define _PATH_LASTLOG "/var/log/lastlog" > > -#define UT_NAMESIZE 8 /* see MAXLOGNAME in */ > +#define UT_NAMESIZE 16 /* see MAXLOGNAME in */ > #define UT_LINESIZE 8 > #define UT_HOSTSIZE 16 > >-- End of excerpt from Jordan K. Hubbard -- Greg Rowe US WEST - !NTERACT "NT disaster recovery isn't all that difficult. Just follow the simple install instructions that come with the FreeBSD CD......" From owner-freebsd-stable Sat Sep 20 13:51:02 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id NAA26366 for stable-outgoing; Sat, 20 Sep 1997 13:51:02 -0700 (PDT) Received: from mail.uniserve.com (dns1-van.uniserve.com [204.244.163.48]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id NAA26359 for ; Sat, 20 Sep 1997 13:50:57 -0700 (PDT) Received: from shell.uniserve.com [204.244.210.252] by mail.uniserve.com with smtp (Exim 1.70 #1) id 0xCWRR-00078S-00; Sat, 20 Sep 1997 13:47:49 -0700 Date: Sat, 20 Sep 1997 13:47:45 -0700 (PDT) From: Tom To: "Michael V. Harding" cc: freebsd-stable@freebsd.org Subject: Re: Longer passwords in 2.2.5 In-Reply-To: <199709201708.KAA26843@netcom1.netcom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Sat, 20 Sep 1997, Michael V. Harding wrote: > Let's put these instructions in the handbook, FAQ, O.K.? It would be > nice to know it was there if I need it in the future... > > Also, are there any side effects if I change this on a running system? > Would I need to flush 'wtmp', etc? I have a system with about 100 > e-mail (pop) clients - what would I need to do to make passwords > longer on a live system? Longer passwords? If you use md5 passwords in passwd, they are already pretty long. If you use DES, you are stuck with its limits. > -- Mike Harding > > Tom From owner-freebsd-stable Sat Sep 20 14:31:04 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id OAA28174 for stable-outgoing; Sat, 20 Sep 1997 14:31:04 -0700 (PDT) Received: from counterintelligence.ml.org (mdean.vip.best.com [206.86.94.101]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id OAA28169 for ; Sat, 20 Sep 1997 14:31:01 -0700 (PDT) Received: from localhost (jamil@localhost) by counterintelligence.ml.org (8.8.7/8.8.5) with SMTP id OAA00468 for ; Sat, 20 Sep 1997 14:30:56 -0700 (PDT) Date: Sat, 20 Sep 1997 14:30:56 -0700 (PDT) From: "Jamil J. Weatherbee" To: freebsd-stable@freebsd.org Subject: PPPD man page Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk the man page talks about "Under Linux" in the section about LCP From owner-freebsd-stable Sat Sep 20 14:33:09 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id OAA28261 for stable-outgoing; Sat, 20 Sep 1997 14:33:09 -0700 (PDT) Received: from counterintelligence.ml.org (mdean.vip.best.com [206.86.94.101]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id OAA28252 for ; Sat, 20 Sep 1997 14:33:06 -0700 (PDT) Received: from localhost (jamil@localhost) by counterintelligence.ml.org (8.8.7/8.8.5) with SMTP id OAA00474 for ; Sat, 20 Sep 1997 14:33:02 -0700 (PDT) Date: Sat, 20 Sep 1997 14:33:02 -0700 (PDT) From: "Jamil J. Weatherbee" To: freebsd-stable@freebsd.org Subject: pppd man page Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk also if you read the sections on "silent" and "passive" those are essentially the same thing but I think the description of passive is wrong From owner-freebsd-stable Sat Sep 20 17:03:08 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id RAA03226 for stable-outgoing; Sat, 20 Sep 1997 17:03:08 -0700 (PDT) Received: from smtp.gte.net (smtp.gte.net [207.115.153.29]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id RAA03218 for ; Sat, 20 Sep 1997 17:03:03 -0700 (PDT) Received: from gte.net (1Cust74.max8.raleigh.nc.ms.uu.net [153.36.6.202]) by smtp.gte.net (SMI-8.6/SMI-SVR4) with ESMTP id TAA02778 for ; Sat, 20 Sep 1997 19:02:24 -0500 (CDT) Message-ID: <342463FB.25E721D5@gte.net> Date: Sat, 20 Sep 1997 20:02:05 -0400 From: "Michael E. Mercer" X-Mailer: Mozilla 4.03b8 [en] (X11; I; FreeBSD 2.2.2-RELEASE i386) MIME-Version: 1.0 To: freebsd-stable@FreeBSD.ORG Subject: subscribe freebsd-stable Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk subscribe freebsd-stable From owner-freebsd-stable Sat Sep 20 17:37:09 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id RAA04602 for stable-outgoing; Sat, 20 Sep 1997 17:37:09 -0700 (PDT) Received: from mail.san.rr.com (san.rr.com [204.210.0.1]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id RAA04596 for ; Sat, 20 Sep 1997 17:37:07 -0700 (PDT) Received: from dt5h1n61.san.rr.com (dt5h1n61.san.rr.com [204.210.31.97]) by mail.san.rr.com (8.8.7/8.8.7) with SMTP id RAA16518; Sat, 20 Sep 1997 17:36:03 -0700 (PDT) Message-Id: <199709210036.RAA16518@mail.san.rr.com> From: "Studded" To: "Nate Williams" Cc: "freebsd-stable@FreeBSD.ORG" Date: Sat, 20 Sep 97 17:35:51 -0700 Reply-To: "Studded" Priority: Normal X-Mailer: PMMail 1.92 For OS/2 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Subject: Re: >8 char usernames going into 2.2.5? Sender: owner-freebsd-stable@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Sat, 20 Sep 1997 11:41:44 -0600 (MDT), Nate Williams wrote: >> I'm a firm believer in backwards compatibility, and I >> understand the importance of supporting things that have "always >> worked." However the rc* changes that are being made in the 2.2 branch >> seem like a pretty big change to me, much bigger than what we're >> talking about with the length of usernames. > >Bullocks. I'd appreciate it if you stuck to the facts, and leave the hostility in your little corner of the world. >1) You don't have to use the rc changes, and the system will work > *FINE*, w/out any modification (and with them). There are several nasty surprises if you don't update the files in /etc (especially the rc* files) depending on your setup. For instance you can't make the world if you don't update group, and rc.firewall has changed a lot. There are some other changes to ipfw that make it incompatible with 2.2.2 kernels. Things will probably work for most people if you don't make the changes, but to assume that everything will work "fine" for everybody even if they don't make the changes is both foolish and dangerous. >2) Programs that once worked will still continue to work (see above), > but with the username changes, programs that worked fine under a > previous release will now corrupt your system files /var/run/*tmp. Maybe this is one of those programmer things, but I'm obviously missing something here. If the change is made, won't the corresponding changes in *tmp be made too? I keep hearing that all that is needed is to make the changes in the two source files, then make the world. After that is done, it seems that all of the system binaries, files, etc. would understand the new format, yes? I have seen a few reports that telnet and ftp have trouble with 16 chars, although 15 works, so maybe it's not so simple? >Programs that use the size of usernames (read, almost all useful >programs) will need to be re-compiled/re-installed. It's a 'big deal', >although it's a simple change. At least some of which would have to be recompiled anyway. And the apps that my servers are set up for couldn't give a rat's .. well, you know about the possible size of the login names on the system, so please don't overgeneralize. >If it's such a big deal to you, do it yourself, but don't screw me over >just because you're too lazy to take the time to do it. Once again, the hostility is not necessary. Also, I resent you assuming that I'm lazy, given that *I* don't need 16 char usernames. The boxes I administer have 4-5 users each, and aren't publicly accessible. The reason I am pushing for this is that I've identified a trend both on the -questions list and amongst the people that I've convinced to try FreeBSD. This is an often requested feature, and given that 2.2.5 is going to be "it" for the next year or so, it seems shortsighted not to make the change now. I don't think it's going too far out on a limb to say that the number of people running custom apps that would fall over if the number of possible chars in a username could be 16 instead of 8 is very small compared to the number of people that will be trying FreeBSD for the first time in the next year. Not to mention the large number of people with systems in place that also want the change. If I am missing something obvious, can someone explain it to me? My basic question is this: I have a system that *depends* on usernames only having 8 chars. Along comes 2.2.5 that allows (gasp!) 16. How does that hurt me if I continue to use just the 8 I've been using all along? And/or, why don't we ask the few people who depend on only 8 being available to make the change in the source files and make the world, rather than handicapping the many who want the 16 char usernames available? Doug Do thou amend thy face, and I'll amend my life. -Shakespeare, "Henry V" From owner-freebsd-stable Sat Sep 20 17:45:10 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id RAA04959 for stable-outgoing; Sat, 20 Sep 1997 17:45:10 -0700 (PDT) Received: from mail.san.rr.com (san.rr.com [204.210.0.1]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id RAA04954 for ; Sat, 20 Sep 1997 17:45:07 -0700 (PDT) Received: from dt5h1n61.san.rr.com (dt5h1n61.san.rr.com [204.210.31.97]) by mail.san.rr.com (8.8.7/8.8.7) with SMTP id RAA18858; Sat, 20 Sep 1997 17:44:04 -0700 (PDT) Message-Id: <199709210044.RAA18858@mail.san.rr.com> From: "Studded" To: "Jordan K. Hubbard" Cc: "freebsd-stable@FreeBSD.ORG" Date: Sat, 20 Sep 97 17:43:53 -0700 Reply-To: "Studded" Priority: Normal X-Mailer: PMMail 1.92 For OS/2 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Subject: Re: >8 char usernames going into 2.2.5? Sender: owner-freebsd-stable@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Sat, 20 Sep 1997 06:04:44 -0700, Jordan K. Hubbard wrote: >Here, enjoy. :-) Errr.. ok, but can I ask some questions first? :) >Index: sys/sys/param.h >========================================================= >RCS file: /home/ncvs/src/sys/sys/param.h,v >-#define MAXLOGNAME 12 /* max login name length */ >+#define MAXLOGNAME 17 /* max login name length */ >Index: include/utmp.h >========================================================= >RCS file: /home/ncvs/src/include/utmp.h,v >-#define UT_NAMESIZE 8 /* see MAXLOGNAME in */ >+#define UT_NAMESIZE 16 /* see MAXLOGNAME in */ Ok, why is there a discrepancy here? If you told me that the change was easy to make, and all I had to do was change the numbers in those two files, the first thing I'd do is ask myself why they were already different, then I'd make them both 16. Obviously I'd be wrong, but can someone explain to a non-programmer why I want the value in param.h to be higher than the one in utmp.h? Thanks, Doug Do thou amend thy face, and I'll amend my life. -Shakespeare, "Henry V" From owner-freebsd-stable Sat Sep 20 19:31:58 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id TAA08205 for stable-outgoing; Sat, 20 Sep 1997 19:31:58 -0700 (PDT) Received: from echonyc.com (echonyc.com [198.67.15.2]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id TAA08191 for ; Sat, 20 Sep 1997 19:31:52 -0700 (PDT) Received: from localhost (benedict@localhost) by echonyc.com (8.8.7/8.8.7) with SMTP id WAA25567; Sat, 20 Sep 1997 22:31:40 -0400 (EDT) Date: Sat, 20 Sep 1997 22:31:39 -0400 (EDT) From: Snob Art Genre To: Tom cc: Studded , "freebsd-stable@freebsd.org" Subject: Re: >8 char usernames going into 2.2.5 In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Fri, 19 Sep 1997, Tom wrote: > On Fri, 19 Sep 1997, Snob Art Genre wrote: > > > Underscore is AFAIK not supposed to be allowed in usernames. Hyphen is, > > Huh? Why not? I don't remember where I read it. Hey people, is this in some RFC somewhere or am I making it up? > Tom > > Ben "You have your mind on computers, it seems." From owner-freebsd-stable Sat Sep 20 19:57:00 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id TAA09131 for stable-outgoing; Sat, 20 Sep 1997 19:57:00 -0700 (PDT) Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id TAA09126 for ; Sat, 20 Sep 1997 19:56:57 -0700 (PDT) Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.7/8.6.9) with ESMTP id TAA01002; Sat, 20 Sep 1997 19:57:09 -0700 (PDT) To: "Jamil J. Weatherbee" cc: freebsd-stable@FreeBSD.ORG Subject: Re: pppd man page In-reply-to: Your message of "Sat, 20 Sep 1997 14:33:02 PDT." Date: Sat, 20 Sep 1997 19:57:08 -0700 Message-ID: <973.874810628@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-stable@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > also if you read the sections on "silent" and "passive" those are > essentially the same thing but I think the description of passive is wrong Please don't report bugs (even doc bugs) here since most such traffic becomes subject to the Somebody Else's Problem effect and the end result is that nobody commits it and the mail itself is lost in the mailing list archives and never referred back to again. The message might just as well have never been for all the good it ever does. This unfortunate pessimism on my part is the direct result of past experience, the problem of bug reports falling through the cracks becoming so acute that we went and adopted the rather unwieldy GNATs system as the lesser of two evils. Sure, PRs can still sometimes sit unresolved for up to 2 years or more (that being the last drop-the-ball duration record that I remember :), but they nonetheless stay open and the GNATs system continues to annoy various people about that fact throughout the duration. It's not at all uncommon to see various folks take periodic it's-really-time-to-clean-the-refridgerator breaks to go through their assigned PRs and, in the process, clear up a number of issues which would *never* have been dealt with otherwise. The PR system is not perfect, but it beats total apathy any day. Please, file such issues as PRs! :-) Jordan P.S. send-pr(1) or http://www.freebsd.org/send-pr.html - your choice. From owner-freebsd-stable Sat Sep 20 20:04:19 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id UAA09445 for stable-outgoing; Sat, 20 Sep 1997 20:04:19 -0700 (PDT) Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id UAA09437 for ; Sat, 20 Sep 1997 20:04:15 -0700 (PDT) Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.7/8.6.9) with ESMTP id UAA01635; Sat, 20 Sep 1997 20:04:29 -0700 (PDT) To: "Studded" cc: "Nate Williams" , "freebsd-stable@FreeBSD.ORG" Subject: Re: >8 char usernames going into 2.2.5? In-reply-to: Your message of "Sat, 20 Sep 1997 17:35:51 PDT." <199709210036.RAA16518@mail.san.rr.com> Date: Sat, 20 Sep 1997 20:04:29 -0700 Message-ID: <1631.874811069@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-stable@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Look, it's very simple. The decision has been made, you're free to set the values to whatever you want, this discussion has become unproductive and is now over. Jordan From owner-freebsd-stable Sat Sep 20 20:13:31 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id UAA09872 for stable-outgoing; Sat, 20 Sep 1997 20:13:31 -0700 (PDT) Received: from mail.uniserve.com (dns1-van.uniserve.com [204.244.163.48]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id UAA09861 for ; Sat, 20 Sep 1997 20:13:28 -0700 (PDT) Received: from shell.uniserve.com [204.244.210.252] by mail.uniserve.com with smtp (Exim 1.70 #1) id 0xCcSV-0001M0-00; Sat, 20 Sep 1997 20:13:19 -0700 Date: Sat, 20 Sep 1997 20:13:13 -0700 (PDT) From: Tom To: Snob Art Genre cc: Studded , "freebsd-stable@freebsd.org" Subject: Re: >8 char usernames going into 2.2.5 In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Sat, 20 Sep 1997, Snob Art Genre wrote: > On Fri, 19 Sep 1997, Tom wrote: > > > On Fri, 19 Sep 1997, Snob Art Genre wrote: > > > > > Underscore is AFAIK not supposed to be allowed in usernames. Hyphen is, > > > > Huh? Why not? > > I don't remember where I read it. Hey people, is this in some RFC > somewhere or am I making it up? RFC? Why? Is there an RFC that says what you should eat for breakfast? :) It is local issue, not under the realm of any RFC. The only RFCs that may vaguely apply are RFC821, 822, and 1122 in regards to the local part of e-mail addresses, since usernames make up the local part of e-mail addresses on Unix systems. In this case, RFC 821 and RFC 822 are quite flexible. With proper quoting you can even put spaces in the local part (ex. "my name"@domain.com). Basically the set of all possible Unix usernames is a subset of the set of all RFC821/822 local parts. The only other thing about "_" is hostnames. "_" are NOT allowed in hostnames. This is probably what you are thinking about. Tom From owner-freebsd-stable Sat Sep 20 20:26:25 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id UAA10552 for stable-outgoing; Sat, 20 Sep 1997 20:26:25 -0700 (PDT) Received: from postman.opengroup.org (postman.opengroup.org [130.105.1.152]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id UAA10544 for ; Sat, 20 Sep 1997 20:26:21 -0700 (PDT) Received: from loverso.southborough.ma.us (simplon.osf.org [130.105.7.200]) by postman.opengroup.org (8.8.6/8.8.6) with ESMTP id XAA32321; Sat, 20 Sep 1997 23:25:55 -0400 (EDT) Received: from localhost.loverso.southborough.ma.us (localhost.loverso.southborough.ma.us [127.0.0.1]) by loverso.southborough.ma.us (8.7.5/8.6.9) with SMTP id XAA14160; Sat, 20 Sep 1997 23:25:40 -0400 (EDT) Message-Id: <199709210325.XAA14160@loverso.southborough.ma.us> X-Authentication-Warning: loverso.southborough.ma.us: Host localhost.loverso.southborough.ma.us [127.0.0.1] didn't use HELO protocol To: Snob Art Genre Cc: Tom , Studded , "freebsd-stable@freebsd.org" Subject: Re: >8 char usernames going into 2.2.5 In-reply-to: Message from Snob Art Genre . X-Face: "UZ!}1W2N?eJdN(`1%|/OOPqJ).Idk?UyvWw'W-%`Gto8^IkEm>.g1O$[.;~}8E=Ire0|lO .o>:NlJS1@vO9bVmswRoq3j DdX9YGSeJ5a(mfX[1u>Z63G5_^+'8LVqjqvn X-Url: http://www.osf.org/~loverso/ Date: Sat, 20 Sep 1997 23:25:40 -0400 From: John Robert LoVerso Sender: owner-freebsd-stable@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk The set of valid characters in usernames have nothing to do with what an Internet RFC covers. John From owner-freebsd-stable Sat Sep 20 21:26:51 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id VAA12463 for stable-outgoing; Sat, 20 Sep 1997 21:26:51 -0700 (PDT) Received: from zeus.xtalwind.net (xtal32.xtalwind.net [205.160.242.83]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id VAA12458 for ; Sat, 20 Sep 1997 21:26:47 -0700 (PDT) Received: from localhost (zeus.xtalwind.net [127.0.0.1]) by zeus.xtalwind.net (8.8.7/8.8.5) with SMTP id AAA05717; Sun, 21 Sep 1997 00:25:30 -0400 (EDT) Date: Sun, 21 Sep 1997 00:25:30 -0400 (EDT) From: jack X-Sender: jack@zeus.xtalwind.net To: "Jordan K. Hubbard" cc: freebsd-stable@FreeBSD.ORG Subject: send-pr (was pppd man page) In-Reply-To: <973.874810628@time.cdrom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Sat, 20 Sep 1997, Jordan K. Hubbard wrote: > Please, file such issues as PRs! :-) How does one check on outstanding PRs? I *think* I filed one a few releases ago about upgrade installs wiping out /etc/{hosts resolv.conf ppp/options and??}. Same bug just bit me from a released rolled from RELENG_2_2 from the CVS tree of two or three days ago. (I won't mention the fact that the release was rolled because we need 16 character usernames. :-} ) -------------------------------------------------------------------------- Jack O'Neill Finger jacko@diamond.xtalwind.net or jack@xtalwind.net http://www.xtalwind.net/~jacko/pubpgp.html #include for my PGP key. PGP Key fingerprint = F6 C4 E6 D4 2F 15 A7 67 FD 09 E9 3C 5F CC EB CD -------------------------------------------------------------------------- From owner-freebsd-stable Sat Sep 20 21:31:15 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id VAA12700 for stable-outgoing; Sat, 20 Sep 1997 21:31:15 -0700 (PDT) Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id VAA12695 for ; Sat, 20 Sep 1997 21:31:11 -0700 (PDT) Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.7/8.6.9) with ESMTP id VAA08135; Sat, 20 Sep 1997 21:31:30 -0700 (PDT) To: jack cc: freebsd-stable@FreeBSD.ORG Subject: Re: send-pr (was pppd man page) In-reply-to: Your message of "Sun, 21 Sep 1997 00:25:30 EDT." Date: Sat, 20 Sep 1997 21:31:30 -0700 Message-ID: <8131.874816290@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-stable@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > On Sat, 20 Sep 1997, Jordan K. Hubbard wrote: > > > Please, file such issues as PRs! :-) > > How does one check on outstanding PRs? I *think* I filed one a few As documented on the support page (http://www.freebsd.org/support.html) you can use http://www.freebsd.org/cgi/query-pr-summary.cgi to print a GNATs summary at any time. Jordan From owner-freebsd-stable Sat Sep 20 21:52:39 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id VAA13426 for stable-outgoing; Sat, 20 Sep 1997 21:52:39 -0700 (PDT) Received: from ns.mt.sri.com (SRI-56K-FR.mt.net [206.127.65.42]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id VAA13421 for ; Sat, 20 Sep 1997 21:52:31 -0700 (PDT) Received: from rocky.mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by ns.mt.sri.com (8.8.7/8.8.7) with ESMTP id WAA01349; Sat, 20 Sep 1997 22:52:29 -0600 (MDT) Received: (from nate@localhost) by rocky.mt.sri.com (8.7.5/8.7.3) id WAA25682; Sat, 20 Sep 1997 22:52:27 -0600 (MDT) Date: Sat, 20 Sep 1997 22:52:27 -0600 (MDT) Message-Id: <199709210452.WAA25682@rocky.mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: "Studded" Cc: "Nate Williams" , "freebsd-stable@FreeBSD.ORG" Subject: Re: >8 char usernames going into 2.2.5? In-Reply-To: <199709210036.RAA16518@mail.san.rr.com> References: <199709210036.RAA16518@mail.san.rr.com> X-Mailer: VM 6.29 under 19.15 XEmacs Lucid Sender: owner-freebsd-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > >> I'm a firm believer in backwards compatibility, and I > >> understand the importance of supporting things that have "always > >> worked." However the rc* changes that are being made in the 2.2 branch > >> seem like a pretty big change to me, much bigger than what we're > >> talking about with the length of usernames. > > > >Bullocks. > > I'd appreciate it if you stuck to the facts, and leave the > hostility in your little corner of the world. I'd appreciate if you stuck to the facts, and not spread dis-information around. > >1) You don't have to use the rc changes, and the system will work > > *FINE*, w/out any modification (and with them). > > There are several nasty surprises if you don't update the files > in /etc (especially the rc* files) depending on your setup. For > instance you can't make the world if you don't update group, and > rc.firewall has changed a lot. And your point is? > There are some other changes to ipfw > that make it incompatible with 2.2.2 kernels. And your point is? > Things will probably > work for most people if you don't make the changes, but to assume that > everything will work "fine" for everybody even if they don't make the > changes is both foolish and dangerous. None of the changes to rc.* are required. *NONE* If you want to build the world, add one line to /etc/group. But, you don't even have to build the world to update. If you want to update 'normally', then sysinstall will do it for you. > >2) Programs that once worked will still continue to work (see above), > > but with the username changes, programs that worked fine under a > > previous release will now corrupt your system files /var/run/*tmp. > > Maybe this is one of those programmer things, but I'm obviously > missing something here. If the change is made, won't the corresponding > changes in *tmp be made too? Yes, but old binaries don't change. Your popper daemon, xterm, top, and *tons* of other programs use the old (shorter) definitions. > I keep hearing that all that is needed is > to make the changes in the two source files, then make the world. > After that is done, it seems that all of the system binaries, files, > etc. would understand the new format, yes? All the system binaries are updated, but almost any 'working' system uses more than the system binaries. > >programs) will need to be re-compiled/re-installed. It's a 'big deal', > >although it's a simple change. > > At least some of which would have to be recompiled anyway. A very minor few. > Once again, the hostility is not necessary. Also, I resent you > assuming that I'm lazy, given that *I* don't need 16 char usernames. Then don't go off telling everyone that it *should* be done, when you have absolutely no idea what it affects. It's not hostility that I'm showing, merely frustration that you were told 'no', and yet w/out knowing the facts or what it affects, you still continue to whine about it. My response to you used the exact same tone you used on the list, so if you perceive it as hostile, better go check how you respond first. Nate From owner-freebsd-stable Sat Sep 20 23:50:40 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id XAA17153 for stable-outgoing; Sat, 20 Sep 1997 23:50:40 -0700 (PDT) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id XAA17141 for ; Sat, 20 Sep 1997 23:50:34 -0700 (PDT) Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id IAA22184 for stable@freebsd.org; Sun, 21 Sep 1997 08:50:33 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.8.7/8.8.5) id IAA07536; Sun, 21 Sep 1997 08:39:31 +0200 (MET DST) Message-ID: <19970921083931.CS53038@uriah.heep.sax.de> Date: Sun, 21 Sep 1997 08:39:31 +0200 From: j@uriah.heep.sax.de (J Wunsch) To: stable@freebsd.org Subject: Another NFS bogon in 2.2-stable? X-Mailer: Mutt 0.60_p2-3,5,8-9 Mime-Version: 1.0 X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) Sender: owner-freebsd-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk (Please drop me a Cc of this conversation, i'm not subscribed to this list.) Did anybody else notice that shutting down a 2.2-stable machine that has NFS file systems mounted never yields a clean shutdown? My 2.2 scratchbox always jams with a `2 2 2 2 2 giving up' display, and comes up again with the clean flag not set in the UFS filesystems. If i shutdown to single-user, manually umount the NFS filesystems, and then type `halt', all works as expected. The machine is not the fastest on earth (386/40), maybe this is what uncovers this problem? -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-)