From owner-freebsd-current Sun Jul 28 00:21:49 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id AAA03807 for current-outgoing; Sun, 28 Jul 1996 00:21:49 -0700 (PDT) Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id AAA03795; Sun, 28 Jul 1996 00:21:32 -0700 (PDT) Received: from sax.sax.de by irz301.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id JAA11918; Sun, 28 Jul 1996 09:21:24 +0200 Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id JAA12289; Sun, 28 Jul 1996 09:21:24 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.7.5/8.6.9) id IAA07110; Sun, 28 Jul 1996 08:56:45 +0200 (MET DST) From: J Wunsch Message-Id: <199607280656.IAA07110@uriah.heep.sax.de> Subject: Re: New wierdness since latest VM kernel. To: freebsd-current@FreeBSD.org (FreeBSD-current users) Date: Sun, 28 Jul 1996 08:56:45 +0200 (MET DST) Cc: dyson@FreeBSD.org Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: from John Fieber at "Jul 27, 96 08:57:22 pm" 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 X-Mailer: ELM [version 2.4ME+ PL17 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk As John Fieber wrote: > > sgmlfmt -f html /usr/src/share/doc/handbook/handbook.sgml > > /usr/bin/sgmlfmt: 30: Syntax error: "{" unexpected (expecting "then") > > *** Error code 2 > > Actully, that would be perl, if it makes any difference. Not a big one, except that you might not even notice the failure if it _were_ a shell script. ;-) What one can see here is simply that execve() failed (the #! has obviously not been interpreted correctly by the kernel, perhaps imgact_shell has not been called?), so the invoking shell falls back to `old-style' and tries to interpret the script itself. -- 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-current Sun Jul 28 00:21:57 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id AAA03826 for current-outgoing; Sun, 28 Jul 1996 00:21:57 -0700 (PDT) Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id AAA03802 for ; Sun, 28 Jul 1996 00:21:47 -0700 (PDT) Received: from sax.sax.de by irz301.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id JAA11924; Sun, 28 Jul 1996 09:21:28 +0200 Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id JAA12294; Sun, 28 Jul 1996 09:21:28 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.7.5/8.6.9) id JAA07170; Sun, 28 Jul 1996 09:04:02 +0200 (MET DST) From: J Wunsch Message-Id: <199607280704.JAA07170@uriah.heep.sax.de> Subject: Re: Troubles with ccd in 2.1.5 To: freebsd-current@FreeBSD.org (FreeBSD-current users) Date: Sun, 28 Jul 1996 09:04:02 +0200 (MET DST) Cc: gavin@ormond.unimelb.edu.au (Gavin Cameron) Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <199607280159.LAA06597@gateway.ormond.unimelb.edu.au> from Gavin Cameron at "Jul 28, 96 11:59:30 am" 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 X-Mailer: ELM [version 2.4ME+ PL17 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk As Gavin Cameron wrote: > I'm having massive problems getting ccd to run on my 2.1.5 > machine. When I try to ccdconfig -C with the ccd.conf file below and > the 2 ~1Gig SCSI drives ( disklabels also shown below ). I end up > panicing my machine with the message: > vm_bounce_alloc: b_bufsize(0x0) < b_bcount(0x200) !! > panic: vm_bounce_alloc > Can someone see anything wrong with what I am trying to do? Perhaps nobody has ever tested ccd with bounce buffers? Do you really need them anyway? (I.e., do you have a machine with > 16 MB RAM and an ISA busmastering SCSI controller, like the AHA-1542?) (Redirected to -current, since this is a technical issue.) -- 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-current Sun Jul 28 03:20:56 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id DAA13636 for current-outgoing; Sun, 28 Jul 1996 03:20:56 -0700 (PDT) Received: from gateway.ormond.unimelb.edu.au (College.ormond.unimelb.edu.au [203.17.189.253]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id DAA13618 for ; Sun, 28 Jul 1996 03:20:45 -0700 (PDT) Received: (from gavin@localhost) by gateway.ormond.unimelb.edu.au (8.6.11/8.6.9) id RAA07186; Sun, 28 Jul 1996 17:27:26 +1000 From: Gavin Cameron Message-Id: <199607280727.RAA07186@gateway.ormond.unimelb.edu.au> Subject: Re: Troubles with ccd in 2.1.5 To: joerg_wunsch@uriah.heep.sax.de Date: Sun, 28 Jul 1996 17:27:09 +1000 (EST) Cc: freebsd-current@freebsd.org In-Reply-To: <199607280704.JAA07170@uriah.heep.sax.de> from "J Wunsch" at Jul 28, 96 09:04:02 am X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > > I'm having massive problems getting ccd to run on my 2.1.5 > > machine. When I try to ccdconfig -C with the ccd.conf file below and > > the 2 ~1Gig SCSI drives ( disklabels also shown below ). I end up > > panicing my machine with the message: > > > vm_bounce_alloc: b_bufsize(0x0) < b_bcount(0x200) !! > > panic: vm_bounce_alloc > > > Can someone see anything wrong with what I am trying to do? > > Perhaps nobody has ever tested ccd with bounce buffers? Do you really > need them anyway? (I.e., do you have a machine with > 16 MB RAM and > an ISA busmastering SCSI controller, like the AHA-1542?) Bingo... 32Meg and a 1542CF Gavin From owner-freebsd-current Sun Jul 28 03:51:25 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id DAA15142 for current-outgoing; Sun, 28 Jul 1996 03:51:25 -0700 (PDT) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id DAA15133 for ; Sun, 28 Jul 1996 03:51:19 -0700 (PDT) Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.12/8.6.9) id UAA15268 for current@freebsd.org; Sun, 28 Jul 1996 20:47:31 +1000 Date: Sun, 28 Jul 1996 20:47:31 +1000 From: Bruce Evans Message-Id: <199607281047.UAA15268@godzilla.zeta.org.au> To: current@freebsd.org Subject: `const char rcsid[]' vs -traditional Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Many sources no longer compile with non-ANSI compilers because they begin with const char rcsid[] = ... `const' is normally hidden for non-ANSI compilers by defining it as nothing in , but copyright and id strings are normally defined before including anything. Bruce From owner-freebsd-current Sun Jul 28 07:38:27 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id HAA24930 for current-outgoing; Sun, 28 Jul 1996 07:38:27 -0700 (PDT) Received: from kropotkin.gnu.ai.mit.edu (kropotkin.gnu.ai.mit.edu [128.52.46.40]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id HAA24922 for ; Sun, 28 Jul 1996 07:38:23 -0700 (PDT) Received: by kropotkin.gnu.ai.mit.edu (8.6.12/8.6.12GNU) id KAA12501; Sun, 28 Jul 1996 10:38:12 -0400 Date: Sun, 28 Jul 1996 10:38:12 -0400 Message-Id: <199607281438.KAA12501@kropotkin.gnu.ai.mit.edu> To: bde@zeta.org.au CC: current@freebsd.org In-reply-to: <199607281047.UAA15268@godzilla.zeta.org.au> (message from Bruce Evans on Sun, 28 Jul 1996 20:47:31 +1000) Subject: Re: `const char rcsid[]' vs -traditional From: Joel Ray Holveck Reply-to: joelh@gnu.ai.mit.edu Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > Many sources no longer compile with non-ANSI compilers because > they begin with const char rcsid[] = ... Why is this a concern? These sources are designed for use with one system--- BSD--- and that comes with an ANSI compiler. Admittedly, something like this is easy enough to fix so it probably should be, but in general, is portability between compilers a priority with FreeBSD? -- http://www.wp.com/piquan --- Joel Ray Holveck --- joelh@gnu.ai.mit.edu The number you have reached is an imaginary number. Please rotate your phone 90 degrees and try again. From owner-freebsd-current Sun Jul 28 08:16:04 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id IAA26386 for current-outgoing; Sun, 28 Jul 1996 08:16:04 -0700 (PDT) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id IAA26364 for ; Sun, 28 Jul 1996 08:15:59 -0700 (PDT) Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.12/8.6.9) id BAA23418; Mon, 29 Jul 1996 01:10:43 +1000 Date: Mon, 29 Jul 1996 01:10:43 +1000 From: Bruce Evans Message-Id: <199607281510.BAA23418@godzilla.zeta.org.au> To: bde@zeta.org.au, joelh@gnu.ai.mit.edu Subject: Re: `const char rcsid[]' vs -traditional Cc: current@freebsd.org Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > Many sources no longer compile with non-ANSI compilers because > > they begin with const char rcsid[] = ... >Why is this a concern? These sources are designed for use with one >system--- BSD--- and that comes with an ANSI compiler. Admittedly, They're designed to work with both K&R and ANSI compilers. >something like this is easy enough to fix so it probably should be, >but in general, is portability between compilers a priority with >FreeBSD? It is for 4.4BSD. It isn't currently for FreeBSD, because all supported systems (one :-) have an ANSI compiler. I only object to breaking backwards compatibility by being sloppy - it should be broken on purpose. Bruce From owner-freebsd-current Sun Jul 28 09:24:09 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id JAA29259 for current-outgoing; Sun, 28 Jul 1996 09:24:09 -0700 (PDT) Received: from kropotkin.gnu.ai.mit.edu (kropotkin.gnu.ai.mit.edu [128.52.46.40]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id JAA29253 for ; Sun, 28 Jul 1996 09:24:07 -0700 (PDT) Received: by kropotkin.gnu.ai.mit.edu (8.6.12/8.6.12GNU) id MAA12670; Sun, 28 Jul 1996 12:23:54 -0400 Date: Sun, 28 Jul 1996 12:23:54 -0400 Message-Id: <199607281623.MAA12670@kropotkin.gnu.ai.mit.edu> To: bde@zeta.org.au CC: current@freebsd.org In-reply-to: <199607281510.BAA23418@godzilla.zeta.org.au> (message from Bruce Evans on Mon, 29 Jul 1996 01:10:43 +1000) Subject: Re: `const char rcsid[]' vs -traditional From: Joel Ray Holveck Reply-to: joelh@gnu.ai.mit.edu Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >>> Many sources no longer compile with non-ANSI compilers because >>> they begin with const char rcsid[] = ... >> Why is this a concern? These sources are designed for use with >> one system--- BSD--- and that comes with an ANSI compiler. > They're designed to work with both K&R and ANSI compilers. Why is that? > I only object to breaking backwards compatibility by being sloppy - > it should be broken on purpose. I'll go along with that. -- http://www.wp.com/piquan --- Joel Ray Holveck --- joelh@gnu.ai.mit.edu The number you have reached is an imaginary number. Please rotate your phone 90 degrees and try again. From owner-freebsd-current Sun Jul 28 09:24:13 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id JAA29283 for current-outgoing; Sun, 28 Jul 1996 09:24:13 -0700 (PDT) Received: from spinner.DIALix.COM (spinner.DIALix.COM [192.203.228.67]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id JAA29267 for ; Sun, 28 Jul 1996 09:24:10 -0700 (PDT) Received: from spinner.DIALix.COM (localhost.DIALix.oz.au [127.0.0.1]) by spinner.DIALix.COM (8.7.5/8.7.3) with ESMTP id AAA01851 for ; Mon, 29 Jul 1996 00:24:06 +0800 (WST) Message-Id: <199607281624.AAA01851@spinner.DIALix.COM> To: current@freebsd.org Subject: DEVFS broken by last devsw_add_generic()/bdevvp() changes Date: Mon, 29 Jul 1996 00:24:05 +0800 From: Peter Wemm Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk It seems the last set of changes to the devsw creation routines and the subsequent bdevvp() change has broken ffs_mount when trying to mount the root filesystem on at least scsi disks. The "new" bdevvp() is returning 0, and ffs_mount is not checking it before passing it onto ffs_mountfs. This might be because of the slice code not knowing whether or not it's using the compatabilty slices or not, or simply because nothing has accessed the slices in the first place to cause the slice code to create the initial nodes in devfs. So, if you are using "options DEVFS", beware, you may not be able to boot anymore, regardless of whether you are mounting the filesystem. -Peter From owner-freebsd-current Sun Jul 28 12:50:21 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id MAA07083 for current-outgoing; Sun, 28 Jul 1996 12:50:21 -0700 (PDT) Received: from apocalypse.superlink.net (root@apocalypse.superlink.net [205.246.27.150]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id MAA07078 for ; Sun, 28 Jul 1996 12:50:17 -0700 (PDT) Received: (from marxx@localhost) by apocalypse.superlink.net (8.7.5/8.7.3) id MAA00268; Sun, 28 Jul 1996 12:02:14 -0400 (EDT) Date: Sun, 28 Jul 1996 12:02:11 -0400 (EDT) From: "Charles C. Figueiredo" To: current@freebsd.org Subject: libtcl Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk It seems there's another problem when making world, with libtcl. I've been trying to track it down, has anyone else encountered this problem, and have you fixed it? ------------------------------------------------------------------------------ Charles C. Figueiredo CCF13 marxx@doomsday.org ------------------------------------------------------------------------------ From owner-freebsd-current Sun Jul 28 13:03:29 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id NAA07436 for current-outgoing; Sun, 28 Jul 1996 13:03:29 -0700 (PDT) Received: from Kitten.mcs.com (Kitten.mcs.com [192.160.127.90]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id NAA07429 for ; Sun, 28 Jul 1996 13:03:25 -0700 (PDT) Received: from venus.mcs.com (root@Venus.mcs.com [192.160.127.92]) by Kitten.mcs.com (8.7.5/8.7.5) with SMTP id PAA10206; Sun, 28 Jul 1996 15:03:18 -0500 (CDT) Received: by venus.mcs.com (/\==/\ Smail3.1.28.1 #28.5) id ; Sun, 28 Jul 96 15:03 CDT Message-Id: Subject: Re: libtcl To: marxx@doomsday.org (Charles C. Figueiredo) Date: Sun, 28 Jul 1996 15:03:18 -0500 (CDT) From: "Karl Denninger, MCSNet" Cc: current@freebsd.org In-Reply-To: from "Charles C. Figueiredo" at Jul 28, 96 12:02:11 pm X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > It seems there's another problem when making world, with libtcl. > I've been trying to track it down, has anyone else encountered this > problem, and have you fixed it? > > ------------------------------------------------------------------------------ > Charles C. Figueiredo CCF13 marxx@doomsday.org > ------------------------------------------------------------------------------ I just ran a "make world" and "make release" last night, and got a working (confirmed at this point) build from -CURRENT. Nicely working at that. Now the stress testing begins. Where do I find the list of known-to-be-broken things in -CURRENT at this point (is there such a thing?) -STABLE has serious NFS and VM problems right now - those showed up about three months ago, as a kernel from before that time does NOT exhibit the same issues. Most of this appears to be fixed in -CURRENT, but is there anything that I need to be aware of in a production environment? (-STABLE, as of now, isn't in that environment for us). -- -- Karl Denninger (karl@MCS.Net)| MCSNet - The Finest Internet Connectivity http://www.mcs.net/~karl | T1 from $600 monthly; speeds to DS-3 available | 23 Chicagoland Prefixes, 13 ISDN, much more Voice: [+1 312 803-MCS1] | Email to "info@mcs.net" WWW: http://www.mcs.net/ Fax: [+1 312 248-9865] | Home of Chicago's only FULL Clarinet feed! From owner-freebsd-current Sun Jul 28 13:07:29 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id NAA07754 for current-outgoing; Sun, 28 Jul 1996 13:07:29 -0700 (PDT) Received: from haywire.DIALix.COM (root@haywire.DIALix.COM [192.203.228.65]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id NAA07745 for ; Sun, 28 Jul 1996 13:07:20 -0700 (PDT) Received: (from news@localhost) by haywire.DIALix.COM (8.7.5/8.7.3) id EAA27329 for freebsd-current@freebsd.org; Mon, 29 Jul 1996 04:07:16 +0800 (WST) Received: from GATEWAY by haywire.DIALix.COM with netnews for freebsd-current@freebsd.org (problems to: usenet@haywire.dialix.com) To: freebsd-current@freebsd.org Date: 28 Jul 1996 20:07:15 GMT From: peter@spinner.DIALix.COM (Peter Wemm) Message-ID: <4tgh9j$os4$1@haywire.DIALix.COM> Organization: DIALix Services, Perth, Australia. References: Subject: Re: New wierdness since latest VM kernel. Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk In article <199607280656.IAA07110@uriah.heep.sax.de>, j@uriah.heep.sax.de (J Wunsch) writes: > As John Fieber wrote: > >> > sgmlfmt -f html /usr/src/share/doc/handbook/handbook.sgml >> > /usr/bin/sgmlfmt: 30: Syntax error: "{" unexpected (expecting "then") >> > *** Error code 2 >> >> Actully, that would be perl, if it makes any difference. > > Not a big one, except that you might not even notice the failure if it > _were_ a shell script. ;-) > > What one can see here is simply that execve() failed (the #! has > obviously not been interpreted correctly by the kernel, perhaps > imgact_shell has not been called?), so the invoking shell falls back > to `old-style' and tries to interpret the script itself. Ouch, I saw this too, except "#! /bin/sh" was being ignored and tcsh was trying to start the bourne shell script under $SHELL (tcsh) It seems to be still happening right now.. :-( -Peter > -- > 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-current Sun Jul 28 13:14:01 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id NAA07964 for current-outgoing; Sun, 28 Jul 1996 13:14:01 -0700 (PDT) Received: from dyson.iquest.net (dyson.iquest.net [198.70.144.127]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id NAA07957 for ; Sun, 28 Jul 1996 13:13:56 -0700 (PDT) Received: (from root@localhost) by dyson.iquest.net (8.7.5/8.6.9) id PAA00488; Sun, 28 Jul 1996 15:13:42 -0500 (EST) From: "John S. Dyson" Message-Id: <199607282013.PAA00488@dyson.iquest.net> Subject: Re: libtcl To: karl@mcs.com (Karl Denninger MCSNet) Date: Sun, 28 Jul 1996 15:13:42 -0500 (EST) Cc: marxx@doomsday.org, current@freebsd.org In-Reply-To: from "Karl Denninger, MCSNet" at Jul 28, 96 03:03:18 pm X-Mailer: ELM [version 2.4 PL24 ME8] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > Where do I find the list of known-to-be-broken things in -CURRENT at this > point (is there such a thing?) -STABLE has serious NFS and VM problems right > now - those showed up about three months ago, as a kernel from before that > time does NOT exhibit the same issues. > > Most of this appears to be fixed in -CURRENT, but is there anything that I > need to be aware of in a production environment? (-STABLE, as of now, isn't > in that environment for us). > As of approx 25-Jul, I made a VM commit with some problems. In a production environment use a kernel just before that date. It will be fixed before the snap, but TODAY, use a kernel checked out like: cvs co -D24-Jul sys John From owner-freebsd-current Sun Jul 28 13:31:22 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id NAA08709 for current-outgoing; Sun, 28 Jul 1996 13:31:22 -0700 (PDT) Received: from Kitten.mcs.com (Kitten.mcs.com [192.160.127.90]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id NAA08704; Sun, 28 Jul 1996 13:31:19 -0700 (PDT) Received: from venus.mcs.com (root@Venus.mcs.com [192.160.127.92]) by Kitten.mcs.com (8.7.5/8.7.5) with SMTP id PAA11047; Sun, 28 Jul 1996 15:31:18 -0500 (CDT) Received: by venus.mcs.com (/\==/\ Smail3.1.28.1 #28.5) id ; Sun, 28 Jul 96 15:31 CDT Message-Id: Subject: Re: PPro Question To: mark@quickweb.com (Mark Mayo) Date: Sun, 28 Jul 1996 15:31:16 -0500 (CDT) From: "Karl Denninger, MCSNet" Cc: hackers@freebsd.org, current@freebsd.org In-Reply-To: from "Mark Mayo" at Jul 26, 96 03:49:50 pm X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > > Hi there - I was wondering if many people have experience with PPro > servers running FreeBSD. I just picked up a Digital Celebris XL 6150 > Pentium Pro (150MHz), and I installed FreeBSD 2.1R - no problems with the > install, the DEC uses an NCR on-board SCSI Bios / COntroller, and > everthing worked fine (the Celebris line use daughter cards to hold the > CPU and Ram so you can switch between ALpha's and PPro's..) > > I was wondering if the following 'time' result is reasonable (for a kernel > rebuild, all options - seemed like a good benchmark to me :-)). The > machine only has 16 MB of RAM. The reason I ask is that I'm curious if a > "normal" pentium 200 with SRAM would be faster.. > > Anyways, the results: > > $ time make > . > . > 183.8u 32.6s 5:20.20 67.9% 989+1207K 1380+59565io 61pf + 0w > > > Any experience/opinions of the Pentium Pro's would be greatly appreciated. We just picked up two PPro 200s, one with 64MB RAM, the other with 128MB. They "feel" about 2x as fast as a P166 with otherwise identical equipment. One of them is in production use as a news server, the other as our "codebase" machine (yes, we finally went out and built one). People who want to grab a -CURRENT release build can get it from codebase.mcs.net, log in as "FTP"; you'll be at the top of the "make release" tree. The normal "grab" files are under "R/ftp" from there. We'll normally keep a "snapshot" type build ("make release") in there and update it every few days, but I *cannot* promise that it will be there at any given point in time. I can also set up a SUP server for the CVS tree if people are interested. Would this help folks? We have *lots* of free cycles and net bandwidth, so we're not constrained at all. What I don't think I will be able to do right now though is keep all the other packages online (at least I can't *promise* they will be there). Functionally, I'm not even sure what I have to sup over here to get a "Complete" set of distributions if I want to be a mirror. Anyone? Give me a list and amount of disk required (will it fit on a 4G drive?) and I'll go grab it. No big deal; 4G disks are only about a kilobuck these days, and I have a bunch of them available to me. Dedicating a machine to serving sups and builds doesn't bother me at all; as long as it doesn't get plastered *too* badly I'll be happy to make it available to the world. If it does we'll have to figure out a way to choke it off to the point that I can still build my kernels and distributions for internal use. CAUTION! The 2.1.anything floppy boot images want a "root.flp" file in the release which IS NOT THERE on a 2.2 build. DO NOT ATTEMPT TO LOAD A 2.2 RELEASE WITH A 2.1.ANYTHING BOOT FLOPPY! IT WILL NOT WORK! Grab the current 2.2 "boot.flp"; that image will work properly. I found this out the hard way... -- -- Karl Denninger (karl@MCS.Net)| MCSNet - The Finest Internet Connectivity http://www.mcs.net/~karl | T1 from $600 monthly; speeds to DS-3 available | 23 Chicagoland Prefixes, 13 ISDN, much more Voice: [+1 312 803-MCS1] | Email to "info@mcs.net" WWW: http://www.mcs.net/ Fax: [+1 312 248-9865] | Home of Chicago's only FULL Clarinet feed! From owner-freebsd-current Sun Jul 28 13:37:20 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id NAA09166 for current-outgoing; Sun, 28 Jul 1996 13:37:20 -0700 (PDT) Received: from dyson.iquest.net (dyson.iquest.net [198.70.144.127]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id NAA09159 for ; Sun, 28 Jul 1996 13:37:12 -0700 (PDT) Received: (from root@localhost) by dyson.iquest.net (8.7.5/8.6.9) id PAA00164; Sun, 28 Jul 1996 15:36:42 -0500 (EST) From: "John S. Dyson" Message-Id: <199607282036.PAA00164@dyson.iquest.net> Subject: Re: New wierdness since latest VM kernel. To: peter@spinner.DIALix.COM (Peter Wemm) Date: Sun, 28 Jul 1996 15:36:42 -0500 (EST) Cc: freebsd-current@FreeBSD.org In-Reply-To: <4tgh9j$os4$1@haywire.DIALix.COM> from "Peter Wemm" at Jul 28, 96 08:07:15 pm X-Mailer: ELM [version 2.4 PL24 ME8] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk > > Ouch, I saw this too, except "#! /bin/sh" was being ignored and tcsh was > trying to start the bourne shell script under $SHELL (tcsh) > > It seems to be still happening right now.. :-( > It is possible that the pmap.c commit that I just made (1.111) might fix the problem. pmap_update was not occuring properly all of the time for kernel_pmap. It could cause sporadic problems. John From owner-freebsd-current Sun Jul 28 13:40:15 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id NAA09344 for current-outgoing; Sun, 28 Jul 1996 13:40:15 -0700 (PDT) Received: from frmug.org (frmug-gw.frmug.org [193.56.58.252]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id NAA09331 for ; Sun, 28 Jul 1996 13:40:09 -0700 (PDT) Received: (from uucp@localhost) by frmug.org (8.6.8/8.6.9) with UUCP id WAA17706 for current@FreeBSD.org; Sun, 28 Jul 1996 22:40:06 +0200 Received: from localhost (localhost [127.0.0.1]) by xp11.frmug.org (8.7.5/8.7.3/xp11-uucp-1.1) with ESMTP id VAA05567 for ; Sun, 28 Jul 1996 21:59:53 +0200 (MET DST) Message-Id: <199607281959.VAA05567@xp11.frmug.org> To: current@FreeBSD.org Subject: no prototype for zopen Date: Sun, 28 Jul 1996 21:59:52 +0200 From: "Philippe Charnier" Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk Hi, Zopen's prototype is no longer obtained from libc. cvs diff: Diffing . Index: compress.c =================================================================== RCS file: /home2h/FreeBSD.cvsroot/src/usr.bin/compress/compress.c,v retrieving revision 1.2 diff -u -r1.2 compress.c --- compress.c 1995/05/30 06:29:41 1.2 +++ compress.c 1996/07/06 09:26:26 @@ -66,6 +66,8 @@ void setfile __P((char *, struct stat *)); void usage __P((int)); +FILE *zopen __P((const char *, const char *, int)); + int eval, force, verbose; int Index: savecore.c =================================================================== RCS file: /home2h/FreeBSD.cvsroot/src/sbin/savecore/savecore.c,v retrieving revision 1.12 diff -u -r1.12 savecore.c --- savecore.c 1996/05/02 09:07:53 1.12 +++ savecore.c 1996/07/06 09:27:30 @@ -128,6 +128,8 @@ void usage __P((void)); void Write __P((int, void *, int)); +FILE *zopen __P((const char *, const char *, int)); + int main(argc, argv) int argc; ------ ------ Philippe Charnier charnier@lirmm.fr (smtp) charnier@xp11.frmug.org (uucp) ``a PC not running FreeBSD is like a venusian with no tentacles'' ------------------------------------------------------------------------ From owner-freebsd-current Sun Jul 28 13:40:15 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id NAA09345 for current-outgoing; Sun, 28 Jul 1996 13:40:15 -0700 (PDT) Received: from frmug.org (frmug-gw.frmug.org [193.56.58.252]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id NAA09330 for ; Sun, 28 Jul 1996 13:40:09 -0700 (PDT) Received: (from uucp@localhost) by frmug.org (8.6.8/8.6.9) with UUCP id WAA17703 for current@FreeBSD.org; Sun, 28 Jul 1996 22:40:05 +0200 Received: from localhost (localhost [127.0.0.1]) by xp11.frmug.org (8.7.5/8.7.3/xp11-uucp-1.1) with ESMTP id VAA04926 for ; Sun, 28 Jul 1996 21:54:26 +0200 (MET DST) Message-Id: <199607281954.VAA04926@xp11.frmug.org> To: current@FreeBSD.org Subject: no man for ree Date: Sun, 28 Jul 1996 21:54:24 +0200 From: "Philippe Charnier" Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk Hi, ree (aka ee) doesn't have a man page Index: Makefile =================================================================== RCS file: /home2h/FreeBSD.cvsroot/src/usr.bin/ee/Makefile,v retrieving revision 1.6 diff -u -r1.6 Makefile --- Makefile 1996/05/22 00:21:50 1.6 +++ Makefile 1996/07/28 19:48:41 @@ -4,6 +4,7 @@ PROG= ee SRCS= ee.c LINKS= ${BINDIR}/ee ${BINDIR}/ree +MLINKS= ee.1 ree.1 DPADD= ${LIBNCURSES} ${LIBMYTINFO} LDADD= -lncurses -lmytinfo ------ ------ Philippe Charnier charnier@lirmm.fr (smtp) charnier@xp11.frmug.org (uucp) ``a PC not running FreeBSD is like a venusian with no tentacles'' ------------------------------------------------------------------------ From owner-freebsd-current Sun Jul 28 13:50:51 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id NAA09813 for current-outgoing; Sun, 28 Jul 1996 13:50:51 -0700 (PDT) Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id NAA09805 for ; Sun, 28 Jul 1996 13:50:47 -0700 (PDT) Received: from sax.sax.de by irz301.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id WAA26639 for ; Sun, 28 Jul 1996 22:50:44 +0200 Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id WAA24514 for freebsd-current@FreeBSD.org; Sun, 28 Jul 1996 22:50:43 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.7.5/8.6.9) id WAA08630 for freebsd-current@FreeBSD.org; Sun, 28 Jul 1996 22:27:55 +0200 (MET DST) From: J Wunsch Message-Id: <199607282027.WAA08630@uriah.heep.sax.de> Subject: Re: `const char rcsid[]' vs -traditional To: freebsd-current@FreeBSD.org (FreeBSD-current users) Date: Sun, 28 Jul 1996 22:27:54 +0200 (MET DST) Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <199607281510.BAA23418@godzilla.zeta.org.au> from Bruce Evans at "Jul 29, 96 01:10:43 am" 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 X-Mailer: ELM [version 2.4ME+ PL17 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk As Bruce Evans wrote: > It is for 4.4BSD. It isn't currently for FreeBSD, because all supported > systems (one :-) have an ANSI compiler. I only object to breaking > backwards compatibility by being sloppy - it should be broken on purpose. I thought we basically agreed in -core when last discussing style(9) that maintaining -traditional K&R compatibility is not one of our major goals. -- 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-current Sun Jul 28 14:11:55 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id OAA10932 for current-outgoing; Sun, 28 Jul 1996 14:11:55 -0700 (PDT) Received: from time.cdrom.com (time.cdrom.com [204.216.27.226]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id OAA10927; Sun, 28 Jul 1996 14:11:52 -0700 (PDT) Received: from time.cdrom.com (localhost [127.0.0.1]) by time.cdrom.com (8.7.5/8.6.9) with ESMTP id OAA03149; Sun, 28 Jul 1996 14:11:23 -0700 (PDT) To: "Karl Denninger, MCSNet" cc: mark@quickweb.com (Mark Mayo), hackers@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: PPro Question In-reply-to: Your message of "Sun, 28 Jul 1996 15:31:16 CDT." Date: Sun, 28 Jul 1996 14:11:23 -0700 Message-ID: <3147.838588283@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > I can also set up a SUP server for the CVS tree if people are interested. > Would this help folks? We have *lots* of free cycles and net bandwidth, so > we're not constrained at all. What I don't think I will be able to do right That's be great - sup2 being down since Paul moved jobs has really hurt us since none of the others were ever as reliable as sup2, and now everyone's back to swamping freefall again. If I can ever get John to finally release cvsup, we could also deploy that on the box and serve cvs, -current and -stable all from the single repository and with no need to cvs update a checked-out tree, as we do now for -sup. I was actually just in the process of creating another sup2 with Paul Vixie, who'll site the server at DEC's NAP, but 3 "major" [cv]sup servers would be even better than 2, so please don't let that stop you. > Anyone? Give me a list and amount of disk required (will it fit on a > 4G drive?) and I'll go grab it. No big deal; 4G disks are only about a > kilobuck these days, and I have a bunch of them available to me. Dedicating Heck, if you can make the machine generally accessible to me via ssh, I'll set it all up myself. I was already planning to do this in Paul's case, and if I can set the 2 machines up fairly identically it would make these resources even easier to manage in the future. Jordan From owner-freebsd-current Sun Jul 28 14:12:39 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id OAA11043 for current-outgoing; Sun, 28 Jul 1996 14:12:39 -0700 (PDT) Received: from rocky.mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id OAA11035 for ; Sun, 28 Jul 1996 14:12:35 -0700 (PDT) Received: (from nate@localhost) by rocky.mt.sri.com (8.7.5/8.7.3) id PAA19564; Sun, 28 Jul 1996 15:12:29 -0600 (MDT) Date: Sun, 28 Jul 1996 15:12:29 -0600 (MDT) Message-Id: <199607282112.PAA19564@rocky.mt.sri.com> From: Nate Williams To: "Karl Denninger, MCSNet" Cc: current@freebsd.org Subject: Bugs in -current (was Re: libtcl) In-Reply-To: References: Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > Where do I find the list of known-to-be-broken things in -CURRENT at > this point (is there such a thing?) -STABLE has serious NFS and VM > problems right now - those showed up about three months ago, as a > kernel from before that time does NOT exhibit the same issues. '-stable' has no known VM bugs in it that I'm aware of that don't exist in -current. Many bugs were fixed in the weeks prior to the release. However, NFS bugs exist in both -stable and -current, although a set of patches were recently made to -current to fix some of them. As far as a list of 'known-to-be-broken' things, I'm not aware of any such list, except maybe one that appears on David Greenman's white-board. No such list is 'officially' kept except in the GNATS database and/or individual developers own mind. Nate From owner-freebsd-current Sun Jul 28 14:41:36 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id OAA12112 for current-outgoing; Sun, 28 Jul 1996 14:41:36 -0700 (PDT) Received: from pdx1 (pdx1.world.net [192.243.32.18]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id OAA12089; Sun, 28 Jul 1996 14:41:27 -0700 (PDT) Received: from suburbia.net (suburbia.net [203.4.184.1]) by pdx1 (8.6.9/8.6.9) with ESMTP id OAA06725; Sun, 28 Jul 1996 14:42:36 -0700 Received: (proff@localhost) by suburbia.net (8.7.4/Proff-950810) id HAA24022; Mon, 29 Jul 1996 07:40:35 +1000 From: Julian Assange Message-Id: <199607282140.HAA24022@suburbia.net> Subject: Re: PPro Question To: jkh@time.cdrom.com (Jordan K. Hubbard) Date: Mon, 29 Jul 1996 07:40:34 +1000 (EST) Cc: karl@mcs.com, mark@quickweb.com, hackers@FreeBSD.ORG, current@FreeBSD.ORG In-Reply-To: <3147.838588283@time.cdrom.com> from "Jordan K. Hubbard" at Jul 28, 96 02:11:23 pm X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > I was actually just in the process of creating another sup2 with Paul > Vixie, who'll site the server at DEC's NAP, but 3 "major" [cv]sup > servers would be even better than 2, so please don't let that stop you. > > Heck, if you can make the machine generally accessible to me via ssh, > I'll set it all up myself. I was already planning to do this in > Paul's case, and if I can set the 2 machines up fairly identically it > would make these resources even easier to manage in the future. > > Jordan Vixie may want to have a wee chat to Randal first ;\ -- "Of all tyrannies a tyranny sincerely exercised for the good of its victims may be the most oppressive. It may be better to live under robber barons than under omnipotent moral busybodies, The robber baron's cruelty may sometimes sleep, his cupidity may at some point be satiated; but those who torment us for own good will torment us without end, for they do so with the approval of their own conscience." - C.S. Lewis, _God in the Dock_ +---------------------+--------------------+----------------------------------+ |Julian Assange RSO | PO Box 2031 BARKER | Secret Analytic Guy Union | |proff@suburbia.net | VIC 3122 AUSTRALIA | finger for PGP key hash ID = | |proff@gnu.ai.mit.edu | FAX +61-3-98199066 | 0619737CCC143F6DEA73E27378933690 | +---------------------+--------------------+----------------------------------+ From owner-freebsd-current Sun Jul 28 18:17:04 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id SAA22268 for current-outgoing; Sun, 28 Jul 1996 18:17:04 -0700 (PDT) Received: from relay-4.mail.demon.net (relay-4.mail.demon.net [158.152.1.108]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id SAA22257 for ; Sun, 28 Jul 1996 18:17:01 -0700 (PDT) Received: from post.demon.co.uk ([158.152.1.72]) by relay-4.mail.demon.net id af29016; 29 Jul 96 1:16 GMT Received: from jraynard.demon.co.uk ([158.152.42.77]) by relay-3.mail.demon.net id aa18546; 29 Jul 96 2:13 +0100 Received: (from fcurrent@localhost) by jraynard.demon.co.uk (8.7.5/8.6.12) id BAA00218 for current@freebsd.org; Mon, 29 Jul 1996 01:11:11 GMT From: James Raynard Message-Id: <199607290111.BAA00218@jraynard.demon.co.uk> Subject: Can't boot new kernel To: current@freebsd.org Date: Mon, 29 Jul 1996 01:11:10 +0000 () X-Mailer: ELM [version 2.4 PL24 ME8a] Content-Type: text Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk [This is with a kernel compiled with code up to ctm-src.2036.gz] When booting without any options, the boot gets as far as "ahc0 waiting for SCSI devices to settle" and then hangs. If I give the -d option at the boot prompt, I get this on executing the "ret" statement at the end of _init386:- Fatal trap 12: page fault while in kernel mode Fault virtual address = 0xefc00000 Fault code = supervisor read, page not present instruction pointer = 0x8:0xf0174f75 stack pointer = 0x10:0xefbfff80 frame pointer = 0x10:0xefbfff8c code segment = base 0x0, limit 0xfffff, type 0x1b, DPL 0, pres 1, def32 1, gran 1 procecssor eflags = resume, IOPL = 0 current process = 0 () interrupt mask = net tty bio kernel: type 12 trap, code = 0 At this point, calling panic results in the "automatic reboot in 15 seconds" message being displayed, but it doesn't reboot. If I use the big red button, it comes up with a checksum error in the BIOS. dmesg from booting the old kernel gives:- FreeBSD 2.2-CURRENT #0: Sat Jul 27 14:30:43 1996 root@jraynard.demon.co.uk:/usr/src/sys/compile/JRAYNARD Calibrating clock(s) relative to mc146818A clock... i586 clock: 99624460 Hz, i8254 clock: 1193421 Hz CPU: Pentium (99.60-MHz 586-class CPU) Origin = "GenuineIntel" Id = 0x525 Stepping=5 Features=0x1bf real memory = 25165824 (24576K bytes) avail memory = 22691840 (22160K bytes) Probing for devices on PCI bus 0: chip0 rev 1 on pci0:0 chip1 rev 2 on pci0:7:0 piix0 rev 2 on pci0:7:1 ahc0 rev 0 int a irq 10 on pci0:8 ahc0: aic7870 Single Channel, SCSI Id=7, 16 SCBs ahc0 waiting for scsi devices to settle (ahc0:2:0): "MATSHITA CD-ROM CR-504 ST22" type 5 removable SCSI 2 cd0(ahc0:2:0): CD-ROM cd present [302551 x 2048 byte records] (ahc0:6:0): "CONNER CFP2105S 2.14GB 2B4B" type 0 fixed SCSI 2 sd0(ahc0:6:0): Direct-Access 2048MB (4194304 512 byte sectors) vga0 rev 0 on pci0:11 Probing for devices on the ISA bus: vt0 at 0x60-0x6f irq 1 on motherboard vt0: unkown s3, 80 col, color, 8 scr, mf2-kbd, [R3.20-b24] sio0 at 0x3f8-0x3ff irq 4 on isa sio0: type 16550A sio1 at 0x2f8-0x2ff irq 3 on isa sio1: type 16550A lpt0 at 0x378-0x37f irq 7 on isa lpt0: Interrupt-driven port lp0: TCP/IP capable interface fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa fdc0: NEC 765 fd0: 1.44MB 3.5in wdc0 at 0x1f0-0x1f7 irq 14 on isa wdc0: unit 0 (wd0): wd0: 327MB (670320 sectors), 665 cyls, 16 heads, 63 S/T, 512 B/S npx0 on motherboard npx0: INT 16 interface and my config file looks like this:- # # GENERIC -- Generic machine with WD/AHx/NCR/BTx family disks # # $Id: GENERIC,v 1.46.2.6 1995/10/25 17:29:51 jkh Exp $ # machine "i386" #cpu "I386_CPU" #cpu "I486_CPU" cpu "I586_CPU" ident JRAYNARD maxusers 10 #options MATH_EMULATE #Support for x87 emulation options INET #InterNETworking options FFS #Berkeley Fast Filesystem options NFS_NOSERVER #options NFS #Network Filesystem #options MSDOSFS #MSDOS Filesystem #options "CD9660" #ISO 9660 Filesystem #options PROCFS #Process filesystem options "COMPAT_43" #Compatible with BSD 4.3 options "SCSI_DELAY=7" #Be pessimistic about Joe SCSI device options BOUNCE_BUFFERS #include support for DMA bounce buffers #options UCONSOLE #Allow users to grab the console options "I586_FAST_BCOPY" options SYSVSHM options SYSVSEM options SYSVMSG config kernel root on wd0 dumps on wd0 options DDB options KTRACE controller isa0 controller pci0 controller fdc0 at isa? port "IO_FD1" bio irq 6 drq 2 vector fdintr disk fd0 at fdc0 drive 0 #disk fd1 at fdc0 drive 1 #tape ft0 at fdc0 drive 2 controller wdc0 at isa? port "IO_WD1" bio irq 14 vector wdintr disk wd0 at wdc0 drive 0 #disk wd1 at wdc0 drive 1 #controller wdc1 at isa? port "IO_WD2" bio irq 15 vector wdintr #disk wd2 at wdc1 drive 0 #disk wd3 at wdc1 drive 1 #options ATAPI #Enable ATAPI support for IDE bus #device wcd0 #IDE CD-ROM #controller ncr0 #controller ahc0 #controller bt0 at isa? port "IO_BT0" bio irq ? vector btintr #controller uha0 at isa? port "IO_UHA0" bio irq ? drq 5 vector uhaintr controller ahc1 #at isa? bio irq ? vector ahcintr #controller ahb0 at isa? bio irq ? vector ahbintr #controller aha0 at isa? port "IO_AHA0" bio irq ? drq 5 vector ahaintr #controller aic0 at isa? port 0x340 bio irq 11 vector aicintr #controller nca0 at isa? port 0x1f88 bio irq 10 vector ncaintr #controller nca1 at isa? port 0x350 bio irq 5 vector ncaintr #controller sea0 at isa? bio irq 5 iomem 0xc8000 iosiz 0x2000 vector seaintr controller scbus0 device sd0 #device st0 device cd0 #Only need one of these, the code dynamically grows #device wt0 at isa? port 0x300 bio irq 5 drq 1 vector wtintr #device mcd0 at isa? port 0x300 bio irq 10 vector mcdintr #device mcd1 at isa? port 0x340 bio irq 11 vector mcdintr #controller matcd0 at isa? port 0x230 bio #device scd0 at isa? port 0x230 bio # syscons is the default console driver, resembling an SCO console #device sc0 at isa? port "IO_KBD" tty irq 1 vector scintr # Enable this and PCVT_FREEBSD for pcvt vt220 compatible console driver device vt0 at isa? port "IO_KBD" tty irq 1 vector pcrint options "PCVT_FREEBSD=210" # pcvt running on FreeBSD 2.1 options "PCVT_INHIBIT_NUMLOCK" #options XSERVER # include code for XFree86 device npx0 at isa? port "IO_NPX" irq 13 vector npxintr device sio0 at isa? port "IO_COM1" tty irq 4 vector siointr device sio1 at isa? port "IO_COM2" tty irq 3 vector siointr #device sio2 at isa? port "IO_COM3" tty irq 5 vector siointr #device sio3 at isa? port "IO_COM4" tty irq 9 vector siointr device lpt0 at isa? port? tty irq 7 vector lptintr #device lpt1 at isa? port? tty #device lpt2 at isa? port? tty #device mse0 at isa? port 0x23c tty irq 5 vector mseintr # Order is important here due to intrusive probes, do *not* alphabetize # this list of network interfaces until the probes have been fixed. # Right now it appears that the ie0 must be probed before ep0. See # revision 1.20 of this file. #device de0 #device ed0 at isa? port 0x280 net irq 5 iomem 0xd8000 vector edintr #device ed1 at isa? port 0x300 net irq 5 iomem 0xd8000 vector edintr #device ie0 at isa? port 0x360 net irq 7 iomem 0xd0000 vector ieintr #device ep0 at isa? port 0x300 net irq 10 vector epintr #device ix0 at isa? port 0x300 net irq 10 iomem 0xd0000 iosiz 32768 vector ixintr #device le0 at isa? port 0x300 net irq 5 iomem 0xd0000 vector le_intr #device lnc0 at isa? port 0x280 net irq 10 drq 0 vector lncintr #device lnc1 at isa? port 0x300 net irq 10 drq 0 vector lncintr #device ze0 at isa? port 0x300 net irq 5 iomem 0xd8000 vector zeintr #device zp0 at isa? port 0x300 net irq 10 iomem 0xd8000 vector zpintr pseudo-device loop #pseudo-device ether pseudo-device log #pseudo-device sl 1 # ijppp uses tun instead of ppp device pseudo-device ppp 1 pseudo-device tun 1 pseudo-device pty 16 #pseudo-device gzip # Exec gzipped a.out's From owner-freebsd-current Sun Jul 28 18:32:28 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id SAA23052 for current-outgoing; Sun, 28 Jul 1996 18:32:28 -0700 (PDT) Received: from freefall.freebsd.org (localhost.cdrom.com [127.0.0.1]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id SAA23042; Sun, 28 Jul 1996 18:32:26 -0700 (PDT) Message-Id: <199607290132.SAA23042@freefall.freebsd.org> To: James Raynard cc: current@freebsd.org Subject: Re: Can't boot new kernel In-reply-to: Your message of "Mon, 29 Jul 1996 01:11:10 -0000." <199607290111.BAA00218@jraynard.demon.co.uk> Date: Sun, 28 Jul 1996 18:32:25 -0700 From: "Justin T. Gibbs" Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >[This is with a kernel compiled with code up to ctm-src.2036.gz] Did you blow away your old compile directory before doing this? -- Justin T. Gibbs =========================================== FreeBSD: Turning PCs into workstations =========================================== From owner-freebsd-current Sun Jul 28 19:23:23 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id TAA24857 for current-outgoing; Sun, 28 Jul 1996 19:23:23 -0700 (PDT) Received: from time.cdrom.com (time.cdrom.com [204.216.27.226]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id TAA24846; Sun, 28 Jul 1996 19:23:19 -0700 (PDT) Received: from time.cdrom.com (localhost [127.0.0.1]) by time.cdrom.com (8.7.5/8.6.9) with ESMTP id TAA03622; Sun, 28 Jul 1996 19:21:49 -0700 (PDT) To: Julian Assange cc: karl@mcs.com, mark@quickweb.com, hackers@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: PPro Question In-reply-to: Your message of "Mon, 29 Jul 1996 07:40:34 +1000." <199607282140.HAA24022@suburbia.net> Date: Sun, 28 Jul 1996 19:21:49 -0700 Message-ID: <3620.838606909@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > Vixie may want to have a wee chat to Randal first ;\ Huh? Jordan From owner-freebsd-current Mon Jul 29 00:38:57 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id AAA09868 for current-outgoing; Mon, 29 Jul 1996 00:38:57 -0700 (PDT) Received: from Campino.Informatik.RWTH-Aachen.DE (campino.Informatik.RWTH-Aachen.DE [137.226.225.2]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id AAA09856 for ; Mon, 29 Jul 1996 00:38:53 -0700 (PDT) Received: from gilberto.physik.rwth-aachen.de (gilberto.physik.rwth-aachen.de [137.226.31.2]) by Campino.Informatik.RWTH-Aachen.DE (RBI-Z-5/8.6.12) with ESMTP id JAA23185; Mon, 29 Jul 1996 09:34:05 +0200 Received: (from kuku@localhost) by gilberto.physik.rwth-aachen.de (8.6.11/8.6.9) id JAA25385; Mon, 29 Jul 1996 09:47:27 +0200 From: "Christoph P. Kukulies" Message-Id: <199607290747.JAA25385@gilberto.physik.rwth-aachen.de> Subject: Re: make world To: uh@sed.cs.fsu.edu (Gang-Ryung Uh) Date: Mon, 29 Jul 1996 09:47:26 +0200 (MET DST) Cc: freebsd-current@freebsd.org In-Reply-To: <199607272151.RAA17879@sed.cs.fsu.edu> from Gang-Ryung Uh at "Jul 27, 96 05:51:16 pm" Reply-To: Christoph Kukulies X-Mailer: ELM [version 2.4ME+ PL16 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > Hi, > > I have supped Jul27 1996 current src, and try to "make world" > I got following fatal error. Would you tell me what I am missing? > Thanks in advance. Most probably you will have to do: cd /usr/src make mk cd /usr/src/usr.bin/make make clean depend all install cp /usr/src/etc/make.conf /etc > > ================= > > -------------------------------------------------------------- > Cleaning up the source tree, and rebuilding the obj tree > -------------------------------------------------------------- > cd /usr/src && make cleandir > ===> include > usage: rm [-f | -i] [-dPRr] file ... > *** Error code 1 > > Stop. > *** Error code 1 > > Stop. > *** Error code 1 > > ============================== > > Gang-Ryung Uh > (uh@cs.fsu.edu) > --Chris Christoph P. U. Kukulies kuku@gil.physik.rwth-aachen.de From owner-freebsd-current Mon Jul 29 01:44:22 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id BAA13181 for current-outgoing; Mon, 29 Jul 1996 01:44:22 -0700 (PDT) Received: from clam.niwa.cri.nz (clam.niwa.cri.nz [131.203.56.8]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id BAA13171 for ; Mon, 29 Jul 1996 01:44:13 -0700 (PDT) Received: from frc.niwa.cri.nz (frc.niwa.cri.nz [131.203.59.1]) by clam.niwa.cri.nz (8.7.5/8.7.3) with ESMTP id UAA04956; Mon, 29 Jul 1996 20:47:55 +1200 (NZST) Received: from neptune.niwa.cri.nz (neptune.niwa.cri.nz [131.203.58.4]) by frc.niwa.cri.nz (8.7.3/8.7.3) with SMTP id UAA20784; Mon, 29 Jul 1996 20:43:09 +1200 (NZST) Date: Mon, 29 Jul 1996 20:43:12 +1200 (NZST) From: Wayne Knowles X-Sender: wdk@neptune.niwa.cri.nz To: James Raynard cc: current@freebsd.org Subject: Re: Can't boot new kernel In-Reply-To: <199607290111.BAA00218@jraynard.demon.co.uk> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Mon, 29 Jul 1996, James Raynard wrote: > When booting without any options, the boot gets as far as "ahc0 > waiting for SCSI devices to settle" and then hangs. If I give > the -d option at the boot prompt, I get this on executing the > "ret" statement at the end of _init386:- I had exactly the same problem over the weekend. I nuked the build directory and started over, and finally ended up re-rolling my CTM files to ctm-2009, but still couldn't get a bootable kernel. As a last resort I decided to create a new config file based on the GENERIC config, and it booted perfectly :-) The strange thing is the the new config I created was almost exactly the same as the previous (but the odrer of some devices in the config was different), and rebuilding the kernel based on the faulty config, it booted without a problem. My suspecion is that my 1 week old kernel was broken in some way, which caused the new kernel file to get courrupted in some way. I cannot give you an exact date or ctm patch level. You could try building a generic kernel, or grab a recent SNAP kernel to bootstrap from, then you should be back in business. Wayne -- _____ Wayne Knowles Title : Systems Manager / o \/ NIWA Fisheries Research Usenet: wdk@frc.niwa.cri.nz \/ v /\ PO. Box 14-901, Kilbirnie `---' Wellington, NEW ZEALAND From owner-freebsd-current Mon Jul 29 03:13:05 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id DAA17564 for current-outgoing; Mon, 29 Jul 1996 03:13:05 -0700 (PDT) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id DAA17556 for ; Mon, 29 Jul 1996 03:12:58 -0700 (PDT) Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.12/8.6.9) id UAA25661; Mon, 29 Jul 1996 20:08:20 +1000 Date: Mon, 29 Jul 1996 20:08:20 +1000 From: Bruce Evans Message-Id: <199607291008.UAA25661@godzilla.zeta.org.au> To: bde@zeta.org.au, joelh@gnu.ai.mit.edu Subject: Re: `const char rcsid[]' vs -traditional Cc: current@FreeBSD.ORG Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > >>> Many sources no longer compile with non-ANSI compilers because > >>> they begin with const char rcsid[] = ... > >> Why is this a concern? These sources are designed for use with > >> one system--- BSD--- and that comes with an ANSI compiler. > > They're designed to work with both K&R and ANSI compilers. >Why is that? I suppose it was because large parts of them were written when they had to work with both K&R and ANSI compilers. Bruce From owner-freebsd-current Mon Jul 29 03:24:32 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id DAA18208 for current-outgoing; Mon, 29 Jul 1996 03:24:32 -0700 (PDT) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id DAA18203 for ; Mon, 29 Jul 1996 03:24:23 -0700 (PDT) Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.12/8.6.9) id UAA26012; Mon, 29 Jul 1996 20:19:07 +1000 Date: Mon, 29 Jul 1996 20:19:07 +1000 From: Bruce Evans Message-Id: <199607291019.UAA26012@godzilla.zeta.org.au> To: charnier@xp11.frmug.org, current@FreeBSD.ORG Subject: Re: no prototype for zopen Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >Zopen's prototype is no longer obtained from libc. stdio.h Since it is used in more than one module it should be in a header. There aren't any suitable ones. Bruce From owner-freebsd-current Mon Jul 29 07:13:43 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id HAA27837 for current-outgoing; Mon, 29 Jul 1996 07:13:43 -0700 (PDT) Received: from potato.Dorm7.NCTU.edu.tw (potato.Dorm7.NCTU.edu.tw [140.113.187.20]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id HAA27829 for ; Mon, 29 Jul 1996 07:13:39 -0700 (PDT) Received: (from SPotato@localhost) by potato.Dorm7.NCTU.edu.tw (8.7.5/8.7.3) id WAA03875 for current@FreeBSD.ORG; Mon, 29 Jul 1996 22:09:39 +0800 (CST) From: Chao-Cheng Huang Message-Id: <199607291409.WAA03875@potato.Dorm7.NCTU.edu.tw> Subject: kernel can't be compiled To: current@FreeBSD.ORG Date: Mon, 29 Jul 1996 22:09:38 +0800 (CST) Reply-To: u8331056@cc.nctu.edu.tw X-Mailer: ELM [version 2.4ME+ PL19 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Hi, all: May somebody help me? I got the latest kernel source and make it. Some error happened when I make depend. The error message is: ../../i386/i386/pmap.c:2538: macro AILQ_NEXT' used with just one arg mkdep: compile failed. *** Error code 1 Stop. My pmap.c is v1.112. kernel config file is: ident GENERIC machine "i386" cpu "I486_CPU" maxusers 32 options INET options FFS options MFS options "COMPAT_43" options "SCSI_DELAY=3" options UCONSOLE options "MAXCONS=5" options USER_LDT options SYSVMSG,SYSVSEM,SYSVSHM options LKM options QUOTA options DEBUG config kernel root on wd0 dumps on wd0 controller isa0 controller pci0 controller fdc0 at isa? port "IO_FD1" bio irq 6 drq 2 vector fdintr disk fd0 at fdc0 drive 0 disk fd1 at fdc0 drive 1 controller wdc0 at isa? port "IO_WD1" bio irq 14 vector wdintr disk wd0 at wdc0 drive 0 disk wd1 at wdc0 drive 1 controller matcd0 at isa? port ? bio device sc0 at isa? port "IO_KBD" tty irq 1 vector scintr device npx0 at isa? port "IO_NPX" irq 13 vector npxintr device sio0 at isa? port "IO_COM1" tty irq 4 vector siointr device sio1 at isa? port "IO_COM2" tty irq 3 vector siointr device lpt0 at isa? port? tty irq 7 vector lptintr device ed0 at isa? port 0x300 net irq 3 iomem 0xd8000 vector edintr controller snd0 device sb0 at isa? port 0x220 irq 5 conflicts drq 1 vector sbintr device sbxvi0 at isa? drq 7 device sbmidi0 at isa? port 0x330 device opl0 at isa? port 0x388 pseudo-device loop pseudo-device ether pseudo-device bpfilter 4 pseudo-device log pseudo-device speaker pseudo-device gzip pseudo-device snp 4 pseudo-device vn 4 pseudo-device pty 64 -- _/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/ _/ Chao-cheng Huang(¶À¬Lµ{) Department Management Science 87G of NCTU _/ _/ E-mail: SPotato@potato.Dorm8.NCTU.edu.tw or u8331056@cc.nctu.edu.tw _/ _/ URL: telnet://potato.Dorm8.NCTU.edu.tw Phone:(035)712121 Ext. 78302 _/ _/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/ From owner-freebsd-current Mon Jul 29 07:30:38 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id HAA29075 for current-outgoing; Mon, 29 Jul 1996 07:30:38 -0700 (PDT) Received: from halloran-eldar.lcs.mit.edu (halloran-eldar.lcs.mit.edu [18.26.0.159]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id HAA29069 for ; Mon, 29 Jul 1996 07:30:36 -0700 (PDT) Received: by halloran-eldar.lcs.mit.edu; (5.65/1.1.8.2/19Aug95-0530PM) id AA20568; Mon, 29 Jul 1996 10:30:23 -0400 Date: Mon, 29 Jul 1996 10:30:23 -0400 From: Garrett Wollman Message-Id: <9607291430.AA20568@halloran-eldar.lcs.mit.edu> To: Bruce Evans Cc: current@freebsd.org Subject: `const char rcsid[]' vs -traditional In-Reply-To: <199607281047.UAA15268@godzilla.zeta.org.au> References: <199607281047.UAA15268@godzilla.zeta.org.au> Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk < said: > Many sources no longer compile with non-ANSI compilers because they > begin with > const char rcsid[] = ... So? -GAWollman -- Garrett A. Wollman | O Siem / We are all family / O Siem / We're all the same wollman@lcs.mit.edu | O Siem / The fires of freedom Opinions not those of| Dance in the burning flame MIT, LCS, ANA, or NSA| - Susan Aglukark and Chad Irschick From owner-freebsd-current Mon Jul 29 08:03:33 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id IAA02661 for current-outgoing; Mon, 29 Jul 1996 08:03:33 -0700 (PDT) Received: from halloran-eldar.lcs.mit.edu (halloran-eldar.lcs.mit.edu [18.26.0.159]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id IAA02654 for ; Mon, 29 Jul 1996 08:03:31 -0700 (PDT) Received: by halloran-eldar.lcs.mit.edu; (5.65/1.1.8.2/19Aug95-0530PM) id AA20901; Mon, 29 Jul 1996 11:03:24 -0400 Date: Mon, 29 Jul 1996 11:03:24 -0400 From: Garrett Wollman Message-Id: <9607291503.AA20901@halloran-eldar.lcs.mit.edu> To: Bruce Evans Cc: charnier@xp11.frmug.org, current@FreeBSD.org Subject: Re: no prototype for zopen In-Reply-To: <199607291019.UAA26012@godzilla.zeta.org.au> References: <199607291019.UAA26012@godzilla.zeta.org.au> Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk < said: >> Zopen's prototype is no longer obtained from libc. > stdio.h > Since it is used in more than one module it should be in a header. > There aren't any suitable ones. I'm aware of only one program which uses the zopen(3) interface to compress(1), and that's `savecore'. I don't think anyone would be hurt to simply remove the functionality in its entirety. Doesn't save much space, though... -r-xr-xr-x 1 bin bin 65536 Jul 3 16:42 /sbin/savecore* -rwxr-xr-x 1 root wheel 68919 Jul 29 11:00 obj/savecore* Furthermore, not being in any system libraries, it doesn't belong in any header files. Perhaps a zopen.h in the sources to compress if we should decide to keep it. (I would just as soon get rid of compress entirely.) -GAWollman -- Garrett A. Wollman | O Siem / We are all family / O Siem / We're all the same wollman@lcs.mit.edu | O Siem / The fires of freedom Opinions not those of| Dance in the burning flame MIT, LCS, ANA, or NSA| - Susan Aglukark and Chad Irschick From owner-freebsd-current Mon Jul 29 09:23:55 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id JAA08292 for current-outgoing; Mon, 29 Jul 1996 09:23:55 -0700 (PDT) Received: from trout.nosc.mil (trout.nosc.mil [128.49.16.7]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id JAA08287 for ; Mon, 29 Jul 1996 09:23:53 -0700 (PDT) Received: from cod.nosc.mil by trout.nosc.mil (4.1/SMI-4.1) id AA00753; Mon, 29 Jul 96 09:23:43 PDT Received: from [128.49.16.48] (aegis.nosc.mil) by cod.nosc.mil (4.1/SMI-4.1) id AA07063; Mon, 29 Jul 96 09:23:42 PDT X-Sender: gshaffer@cod.nosc.mil Message-Id: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Mon, 29 Jul 1996 09:21:40 -0700 To: current@FreeBSD.ORG From: gshaffer@nosc.mil (Greg Shaffer) Subject: Problem with current & XFree86 Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Yesterday I ctm'd the latest deltas for src-cur (up to src-cur.2035) and applied them the my systems which was current up to src-cur.2002. Prior to the update the system ran great without a burp for over a week (the only reason I took it down was to do the update!). Now when I try to bring up X & fvwm, the console locks up as the text for X server scrolls by with the configuration. The system does not respond to any input, I can't switch to other vt, etc, basicly I have to reset the machine. The system successfully completed a make world, I rebuild the kernel and I have not changed my XF86 configuration at all. My system is a P5-100/Zappa MB, 24MB RAM, AHA-2940, and ATI Mach64 video. Anybody else run into this problem? Greg Shaffer From owner-freebsd-current Mon Jul 29 09:35:19 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id JAA08811 for current-outgoing; Mon, 29 Jul 1996 09:35:19 -0700 (PDT) Received: from halloran-eldar.lcs.mit.edu (halloran-eldar.lcs.mit.edu [18.26.0.159]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id JAA08805 for ; Mon, 29 Jul 1996 09:35:17 -0700 (PDT) Received: by halloran-eldar.lcs.mit.edu; (5.65/1.1.8.2/19Aug95-0530PM) id AA21650; Mon, 29 Jul 1996 12:35:16 -0400 Date: Mon, 29 Jul 1996 12:35:16 -0400 From: Garrett Wollman Message-Id: <9607291635.AA21650@halloran-eldar.lcs.mit.edu> To: current@freebsd.org Subject: routed Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I am curious to see if anyone is having problems with the current version of routed... -GAWollman -- Garrett A. Wollman | O Siem / We are all family / O Siem / We're all the same wollman@lcs.mit.edu | O Siem / The fires of freedom Opinions not those of| Dance in the burning flame MIT, LCS, ANA, or NSA| - Susan Aglukark and Chad Irschick From owner-freebsd-current Mon Jul 29 11:06:12 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id LAA13197 for current-outgoing; Mon, 29 Jul 1996 11:06:12 -0700 (PDT) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id LAA13188 for ; Mon, 29 Jul 1996 11:06:09 -0700 (PDT) Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.12/8.6.9) id EAA08896; Tue, 30 Jul 1996 04:02:41 +1000 Date: Tue, 30 Jul 1996 04:02:41 +1000 From: Bruce Evans Message-Id: <199607291802.EAA08896@godzilla.zeta.org.au> To: bde@zeta.org.au, wollman@lcs.mit.edu Subject: Re: `const char rcsid[]' vs -traditional Cc: current@freebsd.org Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >> Many sources no longer compile with non-ANSI compilers because they >> begin with >> const char rcsid[] = ... >So? It's broken for non-ANSI compilers. The correct way to fix this is to move the declarations after the #includes so that happens to be included, but this is too large a change for me. It's inconsistent with the care taken in other parts of the sources. E.g., /usr/src/lib/libc/gen/getosreldate.c, which was written by someone named wollman, begins with a `const char rcsid[]' but then uses an ugly `#if __STDC__' to use a new-style header for ANSI compilers without (further) breaking things for non-ANSI compilers. Bruce From owner-freebsd-current Mon Jul 29 11:27:00 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id LAA14105 for current-outgoing; Mon, 29 Jul 1996 11:27:00 -0700 (PDT) Received: from halloran-eldar.lcs.mit.edu (halloran-eldar.lcs.mit.edu [18.26.0.159]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id LAA14100 for ; Mon, 29 Jul 1996 11:26:57 -0700 (PDT) Received: by halloran-eldar.lcs.mit.edu; (5.65/1.1.8.2/19Aug95-0530PM) id AA22390; Mon, 29 Jul 1996 14:26:51 -0400 Date: Mon, 29 Jul 1996 14:26:51 -0400 From: Garrett Wollman Message-Id: <9607291826.AA22390@halloran-eldar.lcs.mit.edu> To: Bruce Evans Cc: wollman@lcs.mit.edu, current@FreeBSD.ORG Subject: Re: `const char rcsid[]' vs -traditional In-Reply-To: <199607291802.EAA08896@godzilla.zeta.org.au> References: <199607291802.EAA08896@godzilla.zeta.org.au> Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk < said: >>> Many sources no longer compile with non-ANSI compilers because they >>> begin with >>> const char rcsid[] = ... >> So? > It's broken for non-ANSI compilers. I'm quite aware of this; indeed, I quoted precisely that in my reply to your original message. This doesn't answer the question of why anyone would care (Terry Lambert excluded). I certainly don't. > It's inconsistent with the care taken in other parts of the sources. > E.g., /usr/src/lib/libc/gen/getosreldate.c, which was written by someone > named wollman, begins with a `const char rcsid[]' but then uses an ugly > `#if __STDC__' to use a new-style header for ANSI compilers without > (further) breaking things for non-ANSI compilers. Don't ask me what I was thinking. If ever I have a need to go back and change that file, hopefully I'll have the sense to remove the nasty conditional. -GAWollman -- Garrett A. Wollman | O Siem / We are all family / O Siem / We're all the same wollman@lcs.mit.edu | O Siem / The fires of freedom Opinions not those of| Dance in the burning flame MIT, LCS, ANA, or NSA| - Susan Aglukark and Chad Irschick From owner-freebsd-current Mon Jul 29 11:57:31 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id LAA15831 for current-outgoing; Mon, 29 Jul 1996 11:57:31 -0700 (PDT) Received: from mantar.slip.netcom.com (mantar.slip.netcom.com [192.187.167.134]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id LAA15825 for ; Mon, 29 Jul 1996 11:57:24 -0700 (PDT) Received: from localhost (root@localhost) by mantar.slip.netcom.com (8.7.5/8.6.9) with SMTP id LAA15830; Mon, 29 Jul 1996 11:57:47 -0700 (PDT) Date: Mon, 29 Jul 1996 11:57:46 -0700 (PDT) From: Manfred Antar To: Greg Shaffer cc: current@FreeBSD.ORG Subject: Re: Problem with current & XFree86 In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk I also have a Mach_64 driver that won't work after a new kernel with supped files (current) sat july 27 11:00 pm. ============================== || mantar@netcom.com || || Ph. (415) 647-4843 || ============================== From owner-freebsd-current Mon Jul 29 12:04:01 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id MAA16202 for current-outgoing; Mon, 29 Jul 1996 12:04:01 -0700 (PDT) Received: from mantar.slip.netcom.com (mantar.slip.netcom.com [192.187.167.134]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id MAA16172 for ; Mon, 29 Jul 1996 12:03:58 -0700 (PDT) Received: from localhost (root@localhost) by mantar.slip.netcom.com (8.7.5/8.6.9) with SMTP id MAA17102; Mon, 29 Jul 1996 12:04:17 -0700 (PDT) Date: Mon, 29 Jul 1996 12:04:17 -0700 (PDT) From: Manfred Antar To: Garrett Wollman cc: current@FreeBSD.ORG Subject: Re: routed In-Reply-To: <9607291635.AA21650@halloran-eldar.lcs.mit.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Mon, 29 Jul 1996, Garrett Wollman wrote: > I am curious to see if anyone is having problems with the current > version of routed... > I havn't been able keep a stable connection with a Sparc2 thru a 3com 3c509 (BNC) for about a week now.i have to keep doing ifconfig ep0 and this only works for about 2 minutes if that.i tried a version of routed about i month old with same results so i figured it must be the ep driver in kernel ? ============================== || mantar@netcom.com || || Ph. (415) 647-4843 || ============================== From owner-freebsd-current Mon Jul 29 12:14:52 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id MAA16630 for current-outgoing; Mon, 29 Jul 1996 12:14:52 -0700 (PDT) Received: from pcnet1.pcnet.com (pcnet1.pcnet.com [204.213.232.3]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id MAA16625 for ; Mon, 29 Jul 1996 12:14:50 -0700 (PDT) Received: by pcnet1.pcnet.com (4.1/SMI-4.1) id AA00532; Mon, 29 Jul 96 14:56:04 EDT Date: Mon, 29 Jul 96 14:56:04 EDT From: eischen@vigrid.com (Daniel Eischen) Message-Id: <9607291856.AA00532@pcnet1.pcnet.com> To: current@FreeBSD.ORG, wollman@lcs.mit.edu Subject: Re: routed Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > I am curious to see if anyone is having problems with the current > version of routed... I had to disable it because it deleted PPP added routes. Is it still the plan to make it aware of PPP added routes? Dan Eischen eischen@pcnet.com From owner-freebsd-current Mon Jul 29 13:07:30 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id NAA19251 for current-outgoing; Mon, 29 Jul 1996 13:07:30 -0700 (PDT) Received: from relay-2.mail.demon.net (disperse.demon.co.uk [158.152.1.77]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id NAA19224 for ; Mon, 29 Jul 1996 13:07:08 -0700 (PDT) Received: from post.demon.co.uk ([158.152.1.72]) by relay-2.mail.demon.net id aa03219; 29 Jul 96 21:06 +0100 Received: from jraynard.demon.co.uk ([158.152.42.77]) by relay-3.mail.demon.net id aa05486; 29 Jul 96 21:04 +0100 Received: (from fcurrent@localhost) by jraynard.demon.co.uk (8.7.5/8.6.12) id UAA00746; Mon, 29 Jul 1996 20:03:18 GMT From: James Raynard Message-Id: <199607292003.UAA00746@jraynard.demon.co.uk> Subject: Re: Can't boot new kernel To: "Justin T. Gibbs" Date: Mon, 29 Jul 1996 20:03:18 +0000 () Cc: current@freebsd.org In-Reply-To: <199607290132.SAA23042@freefall.freebsd.org> from "Justin T. Gibbs" at Jul 28, 96 06:32:25 pm X-Mailer: ELM [version 2.4 PL24 ME8a] Content-Type: text Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > >[This is with a kernel compiled with code up to ctm-src.2036.gz] > > Did you blow away your old compile directory before doing this? Yep (config -g). From owner-freebsd-current Mon Jul 29 13:26:17 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id NAA20086 for current-outgoing; Mon, 29 Jul 1996 13:26:17 -0700 (PDT) Received: from terra.stack.urc.tue.nl (terra.stack.urc.tue.nl [131.155.140.128]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id NAA20051 for ; Mon, 29 Jul 1996 13:25:54 -0700 (PDT) Received: from xaa.stack.urc.tue.nl (uucp@localhost) by terra.stack.urc.tue.nl (8.7.5) with UUCP id WAA23766 for freebsd-current@freebsd.org; Mon, 29 Jul 1996 22:25:44 +0200 (MET DST) Received: (from xaa@localhost) by xaa.stack.urc.tue.nl (8.7.5/8.6.12) id TAA00426 for freebsd-current@freebsd.org; Mon, 29 Jul 1996 19:31:53 +0200 (MET DST) From: Mark Huizer Message-Id: <199607291731.TAA00426@xaa.stack.urc.tue.nl> Subject: kernel patch for sio.c (fwd) It helped for me... To: freebsd-current@freebsd.org Date: Mon, 29 Jul 1996 19:31:53 +0200 (MET DST) Reply-To: xaa@stack.urc.tue.nl 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-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk well well, at last I could use UUCP without PPP :-) Perhaps something to add to the current kernel? Mark ----- Forwarded message from Mark Huizer ----- |Newsgroups: comp.mail.uucp,comp.unix.bsd.freebsd.misc |Path: tuegate.tue.nl!surfnet.nl!swsbe6.switch.ch!swidir.switch.ch!01-newsfeed.univie.ac.at!news.iif.hu!isyshu!hole.news.pipex.net!pipex!tank.news.pipex.net!pipex!news.mathworks.com!news.kei.com!wang!uunet!in3.uu.net!DIALix!melbourne.DIALix.oz.au!seeware!usenet |From: mark@putte.seeware.DIALix.oz.au (Mark Hannon) |Subject: Re: Strange Taylor UUCP problem on Freebsd 2.1.0 |Content-Type: text/plain; charset=us-ascii |Sender: usenet@seeware.DIALix.oz.au (Charlie Root) |Nntp-Posting-Host: putte.seeware.dialix.oz.au |Organization: Private FreeBSD site |Message-ID: |References: <4ta4qr$80f@itesec.hsc.fr> |Mime-Version: 1.0 |Date: Sun, 28 Jul 1996 17:53:50 GMT |Lines: 116 |Xref: tuegate.tue.nl comp.mail.uucp:12172 comp.unix.bsd.freebsd.misc:26581 In article <4ta4qr$80f@itesec.hsc.fr>, archer@hsc.fr (Vincent Archer) writes: > Got a strange problem using Taylor UUCP 1.06 (coming straight out of the > FreeBSD 2.1 cdrom). I'm supposed to call from a Solaris 2.4 (HDB UUCP), > so I'm stuck to protocol "g". The BSD machine reported all kind of checksum > errors, ending the transfer after 10mn (for a single remote command!). > > I tried to recompile UUCP 1.06.1, and ended having two BSD machines, using > both the same uucico binary, and still gets the checksum errors on each > "g" protocol packet. > Hi, There is a problem with some 16550a serial controllers. It manifests itself in a failure to run UUCP whilst PPP/serial logins etc work fine. I have been using the following kernel patch for some months and all works well now. (Prior to that I had resorted to using and old 16450 ISA card prior to the patch). *** sio.c.orig Tue Jun 25 21:27:34 1996 --- sio.c Tue Jun 25 21:28:30 1996 *************** *** 211,216 **** --- 211,220 ---- struct termios lt_in; /* should be in struct tty */ struct termios lt_out; + #ifdef BROKEN_UART + speed_t current_ospeed; + #endif + bool_t do_timestamp; struct timeval timestamp; *************** *** 626,631 **** --- 630,639 ---- com->it_in.c_ispeed = com->it_in.c_ospeed = comdefaultrate; com->it_out = com->it_in; + #ifdef BROKEN_UART + com->current_ospeed = comdefaultrate; + #endif + /* attempt to determine UART type */ printf("sio%d: type", unit); *************** *** 1624,1629 **** --- 1632,1641 ---- int unit; int txtimeout; + #ifdef BROKEN_UART + bool_t setspeed; + #endif + /* do historical conversions */ if (t->c_ispeed == 0) t->c_ispeed = t->c_ospeed; *************** *** 1637,1642 **** --- 1649,1669 ---- unit = DEV_TO_UNIT(tp->t_dev); com = com_addr(unit); iobase = com->iobase; + + #ifdef BROKEN_UART + /* + * check if the baud rate is different from the currently + * selected one, if so then set new rate. If it is the same, + * don't touch the speed, it confuses the UMC chip heavily + */ + + if (com->current_ospeed != t->c_ospeed) { + setspeed = TRUE; + com->current_ospeed = t->c_ospeed; + } else + setspeed = FALSE; + #endif + s = spltty(); if (divisor == 0) (void)commctl(com, TIOCM_DTR, DMBIC); /* hang up line */ *************** *** 1727,1733 **** != (LSR_TSRE | LSR_TXRDY)) goto retry; ! if (divisor != 0) { outb(iobase + com_cfcr, cfcr | CFCR_DLAB); outb(iobase + com_dlbl, divisor & 0xFF); outb(iobase + com_dlbh, (u_int) divisor >> 8); --- 1754,1764 ---- != (LSR_TSRE | LSR_TXRDY)) goto retry; ! #ifdef BROKEN_UART ! if (divisor != 0 && setspeed) { ! #else ! if (divisor != 0) { ! #endif outb(iobase + com_cfcr, cfcr | CFCR_DLAB); outb(iobase + com_dlbl, divisor & 0xFF); outb(iobase + com_dlbh, (u_int) divisor >> 8); Regards, Mark -- +-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-+ | Mark Hannon,| FreeBSD - Free Unix for your PC| mark@seeware.DIALix.oz.au| | Melbourne, | PGP key available by fingering | epamha@epa.ericsson.se | | Australia | seeware@melbourne.DIALix.oz.au | | +-=-=-=-=-=-=-+-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-+ ----- End of forwarded message from Mark Huizer ----- ------------------------------------------------------------------------- - Mark Huizer - xaa@stack.urc.tue.nl - huizer@circlesoft.nl - ------------------------------------------------------------------------- - this is the end, my only friend the end - - it hurts to set you free, but you'll never follow me - ------------------------------------------------------------------------- From owner-freebsd-current Mon Jul 29 14:06:41 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id OAA22693 for current-outgoing; Mon, 29 Jul 1996 14:06:41 -0700 (PDT) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id OAA22682 for ; Mon, 29 Jul 1996 14:06:09 -0700 (PDT) Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.12/8.6.9) id HAA14363; Tue, 30 Jul 1996 07:05:13 +1000 Date: Tue, 30 Jul 1996 07:05:13 +1000 From: Bruce Evans Message-Id: <199607292105.HAA14363@godzilla.zeta.org.au> To: bde@zeta.org.au, wollman@lcs.mit.edu Subject: Re: no prototype for zopen Cc: charnier@xp11.frmug.org, current@FreeBSD.org Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk >I'm aware of only one program which uses the zopen(3) interface to >compress(1), and that's `savecore'. I don't think anyone would be That's one more than I was aware of yesterday :-). >hurt to simply remove the functionality in its entirety. Doesn't save >much space, though... It also probably saves less space in the output file than would gzipping the output. The only case where it helps is if the file system is too small to hold the initial output. >Furthermore, not being in any system libraries, it doesn't belong in >any header files. Perhaps a zopen.h in the sources to compress if we >should decide to keep it. (I would just as soon get rid of compress >entirely.) I think requiring a header for exported functions would be a good rule. We already have a similar rule for (often not even exported) path names. Bruce From owner-freebsd-current Mon Jul 29 15:18:28 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id PAA26753 for current-outgoing; Mon, 29 Jul 1996 15:18:28 -0700 (PDT) Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id PAA26744 for ; Mon, 29 Jul 1996 15:18:06 -0700 (PDT) Received: from sax.sax.de by irz301.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id AAA11559; Tue, 30 Jul 1996 00:14:09 +0200 Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id AAA02708; Tue, 30 Jul 1996 00:14:09 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.7.5/8.6.9) id WAA04252; Mon, 29 Jul 1996 22:10:29 +0200 (MET DST) From: J Wunsch Message-Id: <199607292010.WAA04252@uriah.heep.sax.de> Subject: Re: kernel can't be compiled To: freebsd-current@FreeBSD.org (FreeBSD-current users) Date: Mon, 29 Jul 1996 22:10:28 +0200 (MET DST) Cc: u8331056@cc.nctu.edu.tw Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <199607291409.WAA03875@potato.Dorm7.NCTU.edu.tw> from Chao-Cheng Huang at "Jul 29, 96 10:09:38 pm" 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 X-Mailer: ELM [version 2.4ME+ PL17 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk As Chao-Cheng Huang wrote: > > Hi, all: > > May somebody help me? I got the latest kernel source and make > it. Some error happened when I make depend. The error message is: > > ../../i386/i386/pmap.c:2538: macro TAILQ_NEXT' used with just one arg > mkdep: compile failed. > *** Error code 1 > > Stop. > > My pmap.c is v1.112. kernel config file is: Looks like this must be: VV--- here pv = TAILQ_NEXT(pv, pv->pv_list)) { #ifdef used_to_be printf(" -> pmap %x, va %x, flags %x", pv->pv_pmap, pv->pv_va, pv->pv_flags); #endif -- 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-current Mon Jul 29 15:48:39 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id PAA27958 for current-outgoing; Mon, 29 Jul 1996 15:48:39 -0700 (PDT) Received: from agora.rdrop.com (root@agora.rdrop.com [199.2.210.241]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id PAA27942 for ; Mon, 29 Jul 1996 15:48:27 -0700 (PDT) Received: by agora.rdrop.com (Smail3.1.29.1 #17) id m0ul16b-0008u7C; Mon, 29 Jul 96 15:48 PDT Message-Id: From: garyh@agora.rdrop.com (Gary Hanson) Subject: Adaptec 7880 support? To: freebsd-current@freebsd.org Date: Mon, 29 Jul 1996 15:48:05 -0700 (PDT) X-Mailer: ELM [version 2.4 PL24 ME8a] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I'll probably be getting a machine with onboard 7880 this week. [Free is a very good price.] In the list archives, I see that the 7880 is supported in current, but the driver is possibly buggy(?) There are no messages (that I found) more recent than March, so any updated status would be appreciated. I'd rather not run current (too many worms in the can right now); did 7880 support make it into 2.1.5? The 7880 isn't mentioned in the HARDWARE.TXT file for 2.1.5, but then, it isn't mentioned in HARDWARE.TXT for the most recent snap either. --Gary Hanson From owner-freebsd-current Mon Jul 29 16:16:05 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id QAA29233 for current-outgoing; Mon, 29 Jul 1996 16:16:05 -0700 (PDT) Received: from freefall.freebsd.org (localhost.cdrom.com [127.0.0.1]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id QAA29220; Mon, 29 Jul 1996 16:16:03 -0700 (PDT) Message-Id: <199607292316.QAA29220@freefall.freebsd.org> To: garyh@agora.rdrop.com (Gary Hanson) cc: freebsd-current@FreeBSD.ORG Subject: Re: Adaptec 7880 support? In-reply-to: Your message of "Mon, 29 Jul 1996 15:48:05 PDT." Date: Mon, 29 Jul 1996 16:16:02 -0700 From: "Justin T. Gibbs" Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > I'll probably be getting a machine with onboard 7880 this week. >[Free is a very good price.] In the list archives, I see that the 7880 >is supported in current, but the driver is possibly buggy(?) There >are no messages (that I found) more recent than March, so any updated >status would be appreciated. The 7880 is supported in both 2.1.5R and current. There aren't any known bugs in the driver. > --Gary Hanson -- Justin T. Gibbs =========================================== FreeBSD: Turning PCs into workstations =========================================== From owner-freebsd-current Mon Jul 29 18:51:24 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id SAA06271 for current-outgoing; Mon, 29 Jul 1996 18:51:24 -0700 (PDT) Received: from haywire.DIALix.COM (root@haywire.DIALix.COM [192.203.228.65]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id SAA06266 for ; Mon, 29 Jul 1996 18:51:20 -0700 (PDT) Received: (from news@localhost) by haywire.DIALix.COM (8.7.5/8.7.3) id JAA23138 for freebsd-current@freebsd.org; Tue, 30 Jul 1996 09:51:16 +0800 (WST) Received: from GATEWAY by haywire.DIALix.COM with netnews for freebsd-current@freebsd.org (problems to: usenet@haywire.dialix.com) To: freebsd-current@freebsd.org Date: 30 Jul 1996 01:51:15 GMT From: peter@spinner.DIALix.COM (Peter Wemm) Message-ID: <4tjpqj$cms$1@haywire.DIALix.COM> Organization: DIALix Services, Perth, Australia. References: <199607290111.BAA00218@jraynard.demon.co.uk> Subject: Re: Can't boot new kernel Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk In article <199607290132.SAA23042@freefall.freebsd.org>, gibbs@freefall.freebsd.org (Justin T. Gibbs) writes: >>[This is with a kernel compiled with code up to ctm-src.2036.gz] > > Did you blow away your old compile directory before doing this? > > -- > Justin T. Gibbs > =========================================== > FreeBSD: Turning PCs into workstations > =========================================== If you have "options DEVFS" in your config at the moment, remove it. The last commit that phk made that created a new bdevvp() doesn't work if you are using a scsi boot disk. -Peter From owner-freebsd-current Mon Jul 29 19:09:13 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id TAA07120 for current-outgoing; Mon, 29 Jul 1996 19:09:13 -0700 (PDT) Received: from Kitten.mcs.com (Kitten.mcs.com [192.160.127.90]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id TAA07115 for ; Mon, 29 Jul 1996 19:09:10 -0700 (PDT) Received: from venus.mcs.com (root@Venus.mcs.com [192.160.127.92]) by Kitten.mcs.com (8.7.5/8.7.5) with SMTP id VAA11467; Mon, 29 Jul 1996 21:09:07 -0500 (CDT) Received: by venus.mcs.com (/\==/\ Smail3.1.28.1 #28.5) id ; Mon, 29 Jul 96 21:09 CDT Message-Id: Subject: Re: Can't boot new kernel To: peter@spinner.DIALix.COM (Peter Wemm) Date: Mon, 29 Jul 1996 21:09:07 -0500 (CDT) From: "Karl Denninger, MCSNet" Cc: freebsd-current@FreeBSD.ORG In-Reply-To: <4tjpqj$cms$1@haywire.DIALix.COM> from "Peter Wemm" at Jul 30, 96 01:51:15 am X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > In article <199607290132.SAA23042@freefall.freebsd.org>, > gibbs@freefall.freebsd.org (Justin T. Gibbs) writes: > >>[This is with a kernel compiled with code up to ctm-src.2036.gz] > > > > Did you blow away your old compile directory before doing this? > > > > -- > > Justin T. Gibbs > > =========================================== > > FreeBSD: Turning PCs into workstations > > =========================================== > > If you have "options DEVFS" in your config at the moment, remove it. The > last commit that phk made that created a new bdevvp() doesn't work if you > are using a scsi boot disk. > > -Peter Uh, yeah. You get either a panic or lockup depending on exactly what else is in the kernel. -- -- Karl Denninger (karl@MCS.Net)| MCSNet - The Finest Internet Connectivity http://www.mcs.net/~karl | T1 from $600 monthly; speeds to DS-3 available | 23 Chicagoland Prefixes, 13 ISDN, much more Voice: [+1 312 803-MCS1] | Email to "info@mcs.net" WWW: http://www.mcs.net/ Fax: [+1 312 248-9865] | Home of Chicago's only FULL Clarinet feed! From owner-freebsd-current Mon Jul 29 19:16:39 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id TAA07614 for current-outgoing; Mon, 29 Jul 1996 19:16:39 -0700 (PDT) Received: from rosie.scsn.net (scsn.net [206.25.246.12]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id TAA07609 for ; Mon, 29 Jul 1996 19:16:36 -0700 (PDT) Received: from cola69.scsn.net ([206.25.247.69]) by rosie.scsn.net (post.office MTA v1.9.3b ID# 0-13529) with SMTP id AAA80; Mon, 29 Jul 1996 22:18:03 -0400 X-Sender: dmaddox@popmail.scsn.net X-Mailer: Windows Eudora Light Version 1.5.2 Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" To: peter@spinner.DIALix.COM (Peter Wemm) From: dmaddox@scsn.net (Donald J. Maddox) Subject: Re: Can't boot new kernel Cc: freebsd-current@freebsd.org Date: Mon, 29 Jul 1996 22:18:03 -0400 Message-ID: <19960730021802562.AAA80@cola69.scsn.net> Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk At 01:51 AM 7/30/96 GMT, you wrote: >If you have "options DEVFS" in your config at the moment, remove it. The >last commit that phk made that created a new bdevvp() doesn't work if you >are using a scsi boot disk. Well, I'm not booting from SCSI (although I do have SCSI drives in my system), but I still get a panic mounting root if 'OPTIONS DEVFS' is defined in my config... From owner-freebsd-current Mon Jul 29 20:30:52 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id UAA12360 for current-outgoing; Mon, 29 Jul 1996 20:30:52 -0700 (PDT) Received: from dyson.iquest.net (dyson.iquest.net [198.70.144.127]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id UAA12355 for ; Mon, 29 Jul 1996 20:30:48 -0700 (PDT) Received: (from root@localhost) by dyson.iquest.net (8.7.5/8.6.9) id WAA00274 for current@freebsd.org; Mon, 29 Jul 1996 22:30:40 -0500 (EST) From: "John S. Dyson" Message-Id: <199607300330.WAA00274@dyson.iquest.net> Subject: Just a note that libkvm/ps/etc need to be recompiled To: current@freebsd.org Date: Mon, 29 Jul 1996 22:30:40 -0500 (EST) X-Mailer: ELM [version 2.4 PL24 ME8] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Since I backed out the VM changes, if you have rebuilt libkvm/ps/etc, then you will have to rebuild them again... Sorry for the trouble, John From owner-freebsd-current Tue Jul 30 01:09:53 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id BAA28538 for current-outgoing; Tue, 30 Jul 1996 01:09:53 -0700 (PDT) Received: from fgate.flevel.co.uk (root@fgate.flevel.co.uk [194.6.101.2]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id BAA28533 for ; Tue, 30 Jul 1996 01:09:49 -0700 (PDT) Received: from localhost (dev@localhost) by fgate.flevel.co.uk (8.7.5/8.6.9) with SMTP id JAA25662 for ; Tue, 30 Jul 1996 09:12:15 +0100 (BST) Date: Tue, 30 Jul 1996 09:12:15 +0100 (BST) From: Developer To: freebsd-current@freebsd.org Subject: My SUP Keeps dying, PLEASE HELP!!!! Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Has anyone any idea how to fix this:- SUP Updating file distfiles/xdvi/xdvi-pl17+markpage+toc+printdvi.patch.gz SUP Updating file distfiles/xdvi/xdvi.tar.Z SUP Updating file distfiles/xdvik-18f.tar.gz SUP Updating file distfiles/xearth-1.0.tar.gz SUP: SCM GOAWAY We died trying to "gzip -c < distfiles/xemacs-19.14.tar.gz > /var/tmp/tmp.0.001226 " SUP: Premature EOF on network input SUP: Error receiving file from file server SUP: Upgrade of ports-distfiles-current aborted at Jul 30 01:12:58 1996 SUP: Aborted I`m using sup.FreeBSD.org as the freebsd Server BTW. Thanks in advance. Regards, Trefor S. From owner-freebsd-current Tue Jul 30 01:13:37 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id BAA28674 for current-outgoing; Tue, 30 Jul 1996 01:13:37 -0700 (PDT) Received: from apocalypse.superlink.net (root@apocalypse.superlink.net [205.246.27.150]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id BAA28669 for ; Tue, 30 Jul 1996 01:13:32 -0700 (PDT) Received: (from marxx@localhost) by apocalypse.superlink.net (8.7.5/8.7.3) id AAA01453; Tue, 30 Jul 1996 00:25:05 -0400 (EDT) Date: Tue, 30 Jul 1996 00:25:00 -0400 (EDT) From: "Charles C. Figueiredo" To: Manfred Antar cc: Garrett Wollman , current@freebsd.org Subject: Re: routed In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Mon, 29 Jul 1996, Manfred Antar wrote: > On Mon, 29 Jul 1996, Garrett Wollman wrote: > > > I am curious to see if anyone is having problems with the current > > version of routed... > > > I havn't been able keep a stable connection with a Sparc2 thru a 3com > 3c509 (BNC) for about a week now.i have to keep doing ifconfig ep0 and > this only works for about 2 minutes if that.i tried a version of routed > about i month old with same results so i figured it must be the ep driver > in kernel ? I'm having the same exact problem. Connections between my ss5 and my pc w/ a 3c509 in it die every minute. If I up and down the interface it'll work again. I tried running with and without routed. routed messes up my ppp :-). I do remember changes to if_ep.c lately. You'll also notice that arp entry for you sparc drops, and if you try adding manually it spews. I'm also wondering if this is the IPDIVERT option I compiled into the kernel or if it's just the actual ep0 driver that is broken... Charles > > ============================== > || mantar@netcom.com || > || Ph. (415) 647-4843 || > ============================== > > ------------------------------------------------------------------------------ Charles C. Figueiredo CCF13 marxx@doomsday.org ------------------------------------------------------------------------------ From owner-freebsd-current Tue Jul 30 01:44:55 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id BAA00562 for current-outgoing; Tue, 30 Jul 1996 01:44:55 -0700 (PDT) Received: from Campino.Informatik.RWTH-Aachen.DE (campino.Informatik.RWTH-Aachen.DE [137.226.225.2]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id BAA00551 for ; Tue, 30 Jul 1996 01:44:30 -0700 (PDT) Received: from gilberto.physik.rwth-aachen.de (gilberto.physik.rwth-aachen.de [137.226.31.2]) by Campino.Informatik.RWTH-Aachen.DE (RBI-Z-5/8.6.12) with ESMTP id KAA09933; Tue, 30 Jul 1996 10:39:09 +0200 Received: (from kuku@localhost) by gilberto.physik.rwth-aachen.de (8.6.11/8.6.9) id KAA29255; Tue, 30 Jul 1996 10:52:33 +0200 From: "Christoph P. Kukulies" Message-Id: <199607300852.KAA29255@gilberto.physik.rwth-aachen.de> Subject: Re: My SUP Keeps dying, PLEASE HELP!!!! To: dev@fgate.flevel.co.uk (Developer) Date: Tue, 30 Jul 1996 10:52:31 +0200 (MET DST) Cc: freebsd-current@FreeBSD.ORG In-Reply-To: from Developer at "Jul 30, 96 09:12:15 am" Reply-To: Christoph Kukulies X-Mailer: ELM [version 2.4ME+ PL16 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > Has anyone any idea how to fix this:- > > SUP Updating file distfiles/xdvi/xdvi-pl17+markpage+toc+printdvi.patch.gz > SUP Updating file distfiles/xdvi/xdvi.tar.Z > SUP Updating file distfiles/xdvik-18f.tar.gz > SUP Updating file distfiles/xearth-1.0.tar.gz > SUP: SCM GOAWAY We died trying to "gzip -c < distfiles/xemacs-19.14.tar.gz > > > /var/tmp/tmp.0.001226 Do you have enough space in /var/tmp? distfiles/xemacs-19.14.tar.gz is 13MB (and gzipping it superfluously requires another chunk of MBs in /tmp possibly). > " > SUP: Premature EOF on network input > SUP: Error receiving file from file server > SUP: Upgrade of ports-distfiles-current aborted at Jul 30 01:12:58 1996 > SUP: Aborted > > I`m using sup.FreeBSD.org as the freebsd Server BTW. > > Thanks in advance. > > Regards, > > Trefor S. > > > --Chris Christoph P. U. Kukulies kuku@gil.physik.rwth-aachen.de From owner-freebsd-current Tue Jul 30 02:20:28 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id CAA02188 for current-outgoing; Tue, 30 Jul 1996 02:20:28 -0700 (PDT) Received: from fgate.flevel.co.uk (root@fgate.flevel.co.uk [194.6.101.2]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id CAA02182 for ; Tue, 30 Jul 1996 02:20:23 -0700 (PDT) Received: from localhost (dev@localhost) by fgate.flevel.co.uk (8.7.5/8.6.9) with SMTP id KAA08089; Tue, 30 Jul 1996 10:22:08 +0100 (BST) Date: Tue, 30 Jul 1996 10:22:07 +0100 (BST) From: Developer To: "Christoph P. Kukulies" cc: freebsd-current@FreeBSD.ORG Subject: Re: My SUP Keeps dying, PLEASE HELP!!!! In-Reply-To: <199607300852.KAA29255@gilberto.physik.rwth-aachen.de> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Tue, 30 Jul 1996, Christoph P. Kukulies wrote: > > > > Has anyone any idea how to fix this:- > > > > SUP Updating file distfiles/xdvi/xdvi-pl17+markpage+toc+printdvi.patch.gz > > SUP Updating file distfiles/xdvi/xdvi.tar.Z > > SUP Updating file distfiles/xdvik-18f.tar.gz > > SUP Updating file distfiles/xearth-1.0.tar.gz > > SUP: SCM GOAWAY We died trying to "gzip -c < distfiles/xemacs-19.14.tar.gz > > > > > /var/tmp/tmp.0.001226 > > Do you have enough space in /var/tmp? > distfiles/xemacs-19.14.tar.gz is 13MB > (and gzipping it superfluously requires another chunk of MBs in /tmp > possibly). Yeh, /var/tmp is a soft link to /tmp which is a soft link to /var/news/tmp And the news drive is a 4.2GB drive that is only 50% full:) I think it looks like an error at the Server end, but I`m not sure?? > > SUP: Premature EOF on network input > > SUP: Error receiving file from file server > > SUP: Upgrade of ports-distfiles-current aborted at Jul 30 01:12:58 1996 > > SUP: Aborted > > > > I`m using sup.FreeBSD.org as the freebsd Server BTW. Thanks. Trefor S. From owner-freebsd-current Tue Jul 30 02:56:54 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id CAA03863 for current-outgoing; Tue, 30 Jul 1996 02:56:54 -0700 (PDT) Received: from Campino.Informatik.RWTH-Aachen.DE (campino.Informatik.RWTH-Aachen.DE [137.226.225.2]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id CAA03855 for ; Tue, 30 Jul 1996 02:56:33 -0700 (PDT) Received: from gilberto.physik.rwth-aachen.de (gilberto.physik.rwth-aachen.de [137.226.31.2]) by Campino.Informatik.RWTH-Aachen.DE (RBI-Z-5/8.6.12) with ESMTP id LAA10946; Tue, 30 Jul 1996 11:51:29 +0200 Received: (from kuku@localhost) by gilberto.physik.rwth-aachen.de (8.6.11/8.6.9) id MAA29399; Tue, 30 Jul 1996 12:04:48 +0200 From: "Christoph P. Kukulies" Message-Id: <199607301004.MAA29399@gilberto.physik.rwth-aachen.de> Subject: Re: My SUP Keeps dying, PLEASE HELP!!!! To: dev@fgate.flevel.co.uk (Developer) Date: Tue, 30 Jul 1996 12:04:47 +0200 (MET DST) Cc: kuku@gilberto.physik.rwth-aachen.de, freebsd-current@FreeBSD.ORG In-Reply-To: from Developer at "Jul 30, 96 10:22:07 am" Reply-To: Christoph Kukulies X-Mailer: ELM [version 2.4ME+ PL16 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > > On Tue, 30 Jul 1996, Christoph P. Kukulies wrote: > > > > > > > Has anyone any idea how to fix this:- > > > > > > SUP Updating file distfiles/xdvi/xdvi-pl17+markpage+toc+printdvi.patch.gz > > > SUP Updating file distfiles/xdvi/xdvi.tar.Z > > > SUP Updating file distfiles/xdvik-18f.tar.gz > > > SUP Updating file distfiles/xearth-1.0.tar.gz > > > SUP: SCM GOAWAY We died trying to "gzip -c < distfiles/xemacs-19.14.tar.gz > > > > > > > /var/tmp/tmp.0.001226 > > > > Do you have enough space in /var/tmp? > > distfiles/xemacs-19.14.tar.gz is 13MB > > (and gzipping it superfluously requires another chunk of MBs in /tmp > > possibly). > > Yeh, /var/tmp is a soft link to /tmp which is a soft link to > /var/news/tmp > > And the news drive is a 4.2GB drive that is only 50% full:) > > I think it looks like an error at the Server end, but I`m not sure?? Yes, after firing up my reply I realized that of course it's the server needing enough space for doing the compress - btw. gzip -c means 'use stdout' so it might as well be another resource problem (pipe? swap?). > > > > SUP: Premature EOF on network input > > > SUP: Error receiving file from file server > > > SUP: Upgrade of ports-distfiles-current aborted at Jul 30 01:12:58 1996 > > > SUP: Aborted > > > > > > I`m using sup.FreeBSD.org as the freebsd Server BTW. > > Thanks. > > Trefor S. > > > --Chris Christoph P. U. Kukulies kuku@gil.physik.rwth-aachen.de From owner-freebsd-current Tue Jul 30 03:37:20 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id DAA06753 for current-outgoing; Tue, 30 Jul 1996 03:37:20 -0700 (PDT) Received: from fgate.flevel.co.uk (root@fgate.flevel.co.uk [194.6.101.2]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id DAA06747 for ; Tue, 30 Jul 1996 03:37:15 -0700 (PDT) Received: from localhost (dev@localhost) by fgate.flevel.co.uk (8.7.5/8.6.9) with SMTP id LAA19527; Tue, 30 Jul 1996 11:38:20 +0100 (BST) Date: Tue, 30 Jul 1996 11:38:19 +0100 (BST) From: Developer To: "Christoph P. Kukulies" cc: freebsd-current@FreeBSD.ORG Subject: Re: My SUP Keeps dying, PLEASE HELP!!!! In-Reply-To: <199607301004.MAA29399@gilberto.physik.rwth-aachen.de> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Tue, 30 Jul 1996, Christoph P. Kukulies wrote: > > > > SUP Updating file distfiles/xdvi/xdvi-pl17+markpage+toc+printdvi.patch.gz > > > > SUP Updating file distfiles/xdvi/xdvi.tar.Z > > > > SUP Updating file distfiles/xdvik-18f.tar.gz > > > > SUP Updating file distfiles/xearth-1.0.tar.gz > > > > SUP: SCM GOAWAY We died trying to "gzip -c < distfiles/xemacs-19.14.tar.gz > > > > > > > > > /var/tmp/tmp.0.001226 > > > > > > Do you have enough space in /var/tmp? > > > distfiles/xemacs-19.14.tar.gz is 13MB > > > (and gzipping it superfluously requires another chunk of MBs in /tmp > > > possibly). > > > > Yeh, /var/tmp is a soft link to /tmp which is a soft link to > > /var/news/tmp > > > > And the news drive is a 4.2GB drive that is only 50% full:) > > > > I think it looks like an error at the Server end, but I`m not sure?? > > Yes, after firing up my reply I realized that of course it's the > server needing enough space for doing the compress - btw. gzip -c means > 'use stdout' so it might as well be another resource problem (pipe? swap?). Yeh, that makes sense.. I wonder if someone at Freefall could fix this problem? > > > > SUP: Premature EOF on network input > > > > SUP: Error receiving file from file server > > > > SUP: Upgrade of ports-distfiles-current aborted at Jul 30 01:12:58 1996 > > > > SUP: Aborted > > > > > > > > I`m using sup.FreeBSD.org as the freebsd Server BTW. Thanks.. Trefor S. From owner-freebsd-current Tue Jul 30 03:52:26 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id DAA07478 for current-outgoing; Tue, 30 Jul 1996 03:52:26 -0700 (PDT) Received: from time.cdrom.com (time.cdrom.com [204.216.27.226]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id DAA07472 for ; Tue, 30 Jul 1996 03:52:24 -0700 (PDT) Received: from time.cdrom.com (localhost [127.0.0.1]) by time.cdrom.com (8.7.5/8.6.9) with ESMTP id DAA25173; Tue, 30 Jul 1996 03:51:38 -0700 (PDT) To: Christoph Kukulies cc: dev@fgate.flevel.co.uk (Developer), freebsd-current@FreeBSD.ORG Subject: Re: My SUP Keeps dying, PLEASE HELP!!!! In-reply-to: Your message of "Tue, 30 Jul 1996 12:04:47 +0200." <199607301004.MAA29399@gilberto.physik.rwth-aachen.de> Date: Tue, 30 Jul 1996 03:51:38 -0700 Message-ID: <25171.838723898@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > Yes, after firing up my reply I realized that of course it's the > server needing enough space for doing the compress - btw. gzip -c means > 'use stdout' so it might as well be another resource problem (pipe? swap?). That also raises the issue - please don't specify "compress" when supping already compressed archives, like distfiles! :-) Jordan From owner-freebsd-current Tue Jul 30 04:36:58 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id EAA11778 for current-outgoing; Tue, 30 Jul 1996 04:36:58 -0700 (PDT) Received: from jraynard.demon.co.uk (jraynard.demon.co.uk [158.152.42.77]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id EAA11769 for ; Tue, 30 Jul 1996 04:36:53 -0700 (PDT) Received: (from fcurrent@localhost) by jraynard.demon.co.uk (8.6.12/8.6.12) id LAA01866; Tue, 30 Jul 1996 11:28:06 GMT From: James Raynard Message-Id: <199607301128.LAA01866@jraynard.demon.co.uk> Subject: Re: Can't boot new kernel To: wdk@frc.niwa.cri.nz (Wayne Knowles) Date: Tue, 30 Jul 1996 11:28:06 +0000 () Cc: current@freebsd.org In-Reply-To: from "Wayne Knowles" at Jul 29, 96 08:43:12 pm X-Mailer: ELM [version 2.4 PL24 ME8a] Content-Type: text Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > You could try building a generic kernel, or grab a recent SNAP > kernel to bootstrap from, then you should be back in business. Nope, I couldn't get a generic kernel to work either. I ended up re-installing 2.1.0 (ab)using the 'upgrade' option. Now I'm trying to upgrade back to -current, but I get cc -O2 -m486 -pipe -fno-strength-reduce -fomit-frame-pointer -I/usr/src/gnu/usr.bin/ld -I/usr/src/gnu/usr.bin/ld/i386 -c lib.c In file included from lib.c:21: /usr/include/ctype.h:121: warning: parameter names (without types) in function declaration /usr/include/ctype.h:122: parse error before `___tolower' /usr/include/ctype.h:122: warning: parameter names (without types) in function declaration /usr/include/ctype.h:122: warning: data definition has no type or storage class /usr/include/ctype.h:123: parse error before `___toupper' [...] The problem is that references a type (_BSD_CT_RUNE_T_) that is not defined anywhere in my source tree. In desperation, I tried #defining it to _BSD_RUNE_T_, but cc doesn't seem able to pick up the definition from , for some reason. Ideas? From owner-freebsd-current Tue Jul 30 05:26:43 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id FAA13261 for current-outgoing; Tue, 30 Jul 1996 05:26:43 -0700 (PDT) Received: from minnow.render.com (render.demon.co.uk [158.152.30.118]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id FAA13244 for ; Tue, 30 Jul 1996 05:26:29 -0700 (PDT) Received: from localhost (dfr@localhost) by minnow.render.com (8.6.12/8.6.9) with SMTP id NAA13158 for ; Tue, 30 Jul 1996 13:28:11 +0100 Date: Tue, 30 Jul 1996 13:28:11 +0100 (BST) From: Doug Rabson To: freebsd-current@freebsd.org Subject: NFS fixes for review Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I have some fixes for NFSv3 in -current but I thought it would be a good idea run them through a reviewer or two: 1. Use the B_CLUSTEROK flag in nfs_doio() to allow multiple buffers to be committed with a single rpc. 2. Fix readdirplus in the NFSv3 server so that it is not totally broken. 3. Some extremely primitive support for NFSv3 async mode which would ignore the stability status from the server and always assume that the data was stably written. This can improve performance for a client because it reduces pressure on the buffer cache since it doesn't have to keep B_DELWRI|B_NEEDCOMMIT buffers around. This should probably also attempt a commit rpc in nfs_flush (implementation of VOP_FSYNC) but the patch does not include this. To use this support, a trivial change to mount_nfs is also needed to allow the async option to be used for NFS mounts. 4. Use a dynamically sized array to coalesce commit requests in nfs_flush() instead of a fixed size stack buffer. This can improve performance for copying large files over NFSv3 since it reduces the number of commit rpcs sent over the wire. 5. Fix a precedence error in nfs_writebp() which prevented proper handling of B_DELWRI|B_NEEDCOMMIT buffers. Also add relavent VMIO calls to make this code actually work. This part has already been reviewed by Rick Macklem. 6. Add some debug printfs to make my life easier. 7. Import a minor fix from NetBSD to supply a definition of the NFSv3 mount protocol version. This is required for some NetBSD fixes to mount_nfs which I will commit seperately. Index: nfs_bio.c =================================================================== RCS file: /home/ncvs/src/sys/nfs/nfs_bio.c,v retrieving revision 1.24 diff -u -r1.24 nfs_bio.c --- nfs_bio.c 1996/07/16 10:19:43 1.24 +++ nfs_bio.c 1996/07/23 12:37:44 @@ -905,9 +905,11 @@ iomode = NFSV3WRITE_FILESYNC; bp->b_flags |= B_WRITEINPROG; error = nfs_writerpc(vp, uiop, cr, &iomode, &must_commit); - if (!error && iomode == NFSV3WRITE_UNSTABLE) + if (!error && iomode == NFSV3WRITE_UNSTABLE) { bp->b_flags |= B_NEEDCOMMIT; - else + if (bp->b_dirtyoff == 0 && bp->b_dirtyend == bp->b_bufsize) + bp->b_flags |= B_CLUSTEROK; + } else bp->b_flags &= ~B_NEEDCOMMIT; bp->b_flags &= ~B_WRITEINPROG; Index: nfs_serv.c =================================================================== RCS file: /home/ncvs/src/sys/nfs/nfs_serv.c,v retrieving revision 1.30 diff -u -r1.30 nfs_serv.c --- nfs_serv.c 1996/06/08 12:16:26 1.30 +++ nfs_serv.c 1996/07/25 14:34:18 @@ -2919,6 +2919,7 @@ nfsm_srvpostop_attr(getret, &at); return (0); } + vput(nvp); dirlen = len = NFSX_V3POSTOPATTR + NFSX_V3COOKIEVERF + 2 * NFSX_UNSIGNED; nfsm_reply(cnt); Index: nfs_vnops.c =================================================================== RCS file: /home/ncvs/src/sys/nfs/nfs_vnops.c,v retrieving revision 1.34 diff -u -r1.34 nfs_vnops.c --- nfs_vnops.c 1996/07/16 10:19:45 1.34 +++ nfs_vnops.c 1996/07/23 12:39:28 @@ -1210,7 +1210,10 @@ tsiz -= len; } nfsmout: - *iomode = committed; + if (vp->v_mount->mnt_flag & MNT_ASYNC) + *iomode = NFSV3WRITE_FILESYNC; + else + *iomode = committed; if (error) uiop->uio_resid = tsiz; return (error); @@ -2607,6 +2610,9 @@ int error = 0, wccflag = NFSV3_WCCRATTR; struct mbuf *mreq, *mrep, *md, *mb, *mb2; +#ifdef NFS_DEBUG + printf("nfs_commit(%x, %d, %d, %x, %x)\n", vp, (int) offset, cnt, cred, procp); +#endif if ((nmp->nm_flag & NFSMNT_HASWRITEVERF) == 0) return (0); nfsstats.rpccnt[NFSPROC_COMMIT]++; @@ -2757,13 +2763,14 @@ struct nfsmount *nmp = VFSTONFS(vp->v_mount); int s, error = 0, slptimeo = 0, slpflag = 0, retv, bvecpos; int passone = 1; - u_quad_t off = (u_quad_t)-1, endoff = 0, toff; + u_quad_t off, endoff, toff; struct ucred* wcred = NULL; -#ifndef NFS_COMMITBVECSIZ -#define NFS_COMMITBVECSIZ 20 -#endif - struct buf *bvec[NFS_COMMITBVECSIZ]; + struct buf **bvec = NULL; + int bvecsize = 0, bveccount; +#ifdef NFS_DEBUG + printf("nfs_flush(%x, %x, %d, %x, %d)\n", vp, cred, waitfor, p, commit); +#endif if (nmp->nm_flag & NFSMNT_INT) slpflag = PCATCH; if (!commit) @@ -2776,12 +2783,41 @@ * job. */ again: + off = (u_quad_t)-1; + endoff = 0; bvecpos = 0; if (NFS_ISV3(vp) && commit) { s = splbio(); + /* + * Count up how many buffers waiting for a commit. + */ + bveccount = 0; + for (bp = vp->v_dirtyblkhd.lh_first; bp; bp = nbp) { + nbp = bp->b_vnbufs.le_next; + if ((bp->b_flags & (B_BUSY | B_DELWRI | B_NEEDCOMMIT)) + == (B_DELWRI | B_NEEDCOMMIT)) + bveccount++; + } + /* + * Allocate space to remember the list of bufs to commit. It is + * important to use M_NOWAIT here to avoid a race with nfs_write. + * If we can't get memory (for whatever reason), we will end up + * committing the buffers one-by-one in the loop below. + */ + if (bveccount > bvecsize) { + if (bvec != NULL) + free(bvec, M_TEMP); + bvec = (struct buf **) + malloc(bveccount * sizeof(struct buf *), + M_TEMP, M_NOWAIT); + if (bvec == NULL) + bvecsize = 0; + else + bvecsize = bveccount; + } for (bp = vp->v_dirtyblkhd.lh_first; bp; bp = nbp) { nbp = bp->b_vnbufs.le_next; - if (bvecpos >= NFS_COMMITBVECSIZ) + if (bvecpos >= bvecsize) break; if ((bp->b_flags & (B_BUSY | B_DELWRI | B_NEEDCOMMIT)) != (B_DELWRI | B_NEEDCOMMIT)) @@ -2822,10 +2858,14 @@ * one call for all of them, otherwise commit each one * separately. */ - if (wcred != NOCRED) + if (wcred != NOCRED) { +#ifdef NFS_DEBUG +printf("nfs_flush: calling nfs_commit(%x, %d, %d, %x, %x)\n", + vp, (int) off, (int) (endoff - off), wcred, p); +#endif retv = nfs_commit(vp, off, (int)(endoff - off), wcred, p); - else { + } else { retv = 0; for (i = 0; i < bvecpos; i++) { off_t off, size; @@ -2879,8 +2919,10 @@ "nfsfsync", slptimeo); splx(s); if (error) { - if (nfs_sigintr(nmp, (struct nfsreq *)0, p)) - return (EINTR); + if (nfs_sigintr(nmp, (struct nfsreq *)0, p)) { + error = EINTR; + goto done; + } if (slpflag == PCATCH) { slpflag = 0; slptimeo = 2 * hz; @@ -2892,6 +2934,9 @@ panic("nfs_fsync: not dirty"); if ((passone || !commit) && (bp->b_flags & B_NEEDCOMMIT)) continue; +#ifdef NFS_DEBUG +printf("nfs_flush: writing bp=%x, bp->b_flags=%x\n", bp, bp->b_flags); +#endif bremfree(bp); if (passone || !commit) bp->b_flags |= (B_BUSY|B_ASYNC); @@ -2912,8 +2957,10 @@ error = tsleep((caddr_t)&vp->v_numoutput, slpflag | (PRIBIO + 1), "nfsfsync", slptimeo); if (error) { - if (nfs_sigintr(nmp, (struct nfsreq *)0, p)) - return (EINTR); + if (nfs_sigintr(nmp, (struct nfsreq *)0, p)) { + error = EINTR; + goto done; + } if (slpflag == PCATCH) { slpflag = 0; slptimeo = 2 * hz; @@ -2928,6 +2975,9 @@ error = np->n_error; np->n_flag &= ~NWRITEERR; } +done: + if (bvec) + free(bvec, M_TEMP); return (error); } @@ -3129,8 +3179,9 @@ * an actual write will have to be scheduled via. VOP_STRATEGY(). * If B_WRITEINPROG is already set, then push it with a write anyhow. */ - if (oldflags & (B_NEEDCOMMIT | B_WRITEINPROG) == B_NEEDCOMMIT) { + if ((oldflags & (B_NEEDCOMMIT | B_WRITEINPROG)) == B_NEEDCOMMIT) { off = ((u_quad_t)bp->b_blkno) * DEV_BSIZE + bp->b_dirtyoff; + vfs_busy_pages(bp, 1); bp->b_flags |= B_WRITEINPROG; retv = nfs_commit(bp->b_vp, off, bp->b_dirtyend-bp->b_dirtyoff, bp->b_wcred, bp->b_proc); @@ -3139,8 +3190,10 @@ bp->b_dirtyoff = bp->b_dirtyend = 0; bp->b_flags &= ~B_NEEDCOMMIT; biodone(bp); - } else if (retv == NFSERR_STALEWRITEVERF) + } else if (retv == NFSERR_STALEWRITEVERF) { nfs_clearcommit(bp->b_vp->v_mount); + vfs_unbusy_pages(bp); + } } if (retv) { if (force) Index: nfsnode.h =================================================================== RCS file: /home/ncvs/src/sys/nfs/nfsnode.h,v retrieving revision 1.15 diff -u -r1.15 nfsnode.h --- nfsnode.h 1995/12/17 21:12:37 1.15 +++ nfsnode.h 1996/07/30 11:55:07 @@ -137,7 +137,7 @@ #define NUPD 0x0200 /* Special file updated */ #define NCHG 0x0400 /* Special file times changed */ #define NLOCKED 0x0800 /* node is locked */ -#define NWANTED 0x0100 /* someone wants to lock */ +#define NWANTED 0x1000 /* someone wants to lock */ /* * Convert between nfsnode pointers and vnode pointers Index: rpcv2.h =================================================================== RCS file: /home/ncvs/src/sys/nfs/rpcv2.h,v retrieving revision 1.4 diff -u -r1.4 rpcv2.h --- rpcv2.h 1995/06/27 11:07:02 1.4 +++ rpcv2.h 1996/07/17 14:16:14 @@ -90,6 +90,7 @@ /* RPC Prog definitions */ #define RPCPROG_MNT 100005 #define RPCMNT_VER1 1 +#define RPCMNT_VER3 3 #define RPCMNT_MOUNT 1 #define RPCMNT_DUMP 2 #define RPCMNT_UMOUNT 3 -- Doug Rabson, Microsoft RenderMorphics Ltd. Mail: dfr@render.com Phone: +44 171 251 4411 FAX: +44 171 251 0939 From owner-freebsd-current Tue Jul 30 06:31:25 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id GAA15846 for current-outgoing; Tue, 30 Jul 1996 06:31:25 -0700 (PDT) Received: from Campino.Informatik.RWTH-Aachen.DE (campino.Informatik.RWTH-Aachen.DE [137.226.225.2]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id GAA15841 for ; Tue, 30 Jul 1996 06:31:18 -0700 (PDT) Received: from gilberto.physik.rwth-aachen.de (gilberto.physik.rwth-aachen.de [137.226.31.2]) by Campino.Informatik.RWTH-Aachen.DE (RBI-Z-5/8.6.12) with ESMTP id PAA13687; Tue, 30 Jul 1996 15:25:38 +0200 Received: (from kuku@localhost) by gilberto.physik.rwth-aachen.de (8.6.11/8.6.9) id PAA00284; Tue, 30 Jul 1996 15:39:02 +0200 From: "Christoph P. Kukulies" Message-Id: <199607301339.PAA00284@gilberto.physik.rwth-aachen.de> Subject: Re: Can't boot new kernel To: fcurrent@jraynard.demon.co.uk (James Raynard) Date: Tue, 30 Jul 1996 15:39:01 +0200 (MET DST) Cc: wdk@frc.niwa.cri.nz, current@freebsd.org In-Reply-To: <199607301128.LAA01866@jraynard.demon.co.uk> from James Raynard at "Jul 30, 96 11:28:06 am" Reply-To: Christoph Kukulies X-Mailer: ELM [version 2.4ME+ PL16 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > > > You could try building a generic kernel, or grab a recent SNAP > > kernel to bootstrap from, then you should be back in business. > > Nope, I couldn't get a generic kernel to work either. I ended up > re-installing 2.1.0 (ab)using the 'upgrade' option. Now I'm trying > to upgrade back to -current, but I get > > cc -O2 -m486 -pipe -fno-strength-reduce -fomit-frame-pointer -I/usr/src/gnu/usr.bin/ld -I/usr/src/gnu/usr.bin/ld/i386 -c lib.c > In file included from lib.c:21: > /usr/include/ctype.h:121: warning: parameter names (without types) in function declaration > /usr/include/ctype.h:122: parse error before `___tolower' > /usr/include/ctype.h:122: warning: parameter names (without types) in function declaration > /usr/include/ctype.h:122: warning: data definition has no type or storage class > /usr/include/ctype.h:123: parse error before `___toupper' > [...] > > The problem is that references a type (_BSD_CT_RUNE_T_) that > is not defined anywhere in my source tree. In desperation, I tried > #defining it to _BSD_RUNE_T_, but cc doesn't seem able to pick up the > definition from , for some reason. > > Ideas? > > I had this problem recently with my 2.2-current tree. Somehow I had a wrong ctype.h (and/or ansi.h). I deleted my /usr/src tree and resupped everything. I'm healed now :-) --Chris Christoph P. U. Kukulies kuku@gil.physik.rwth-aachen.de From owner-freebsd-current Tue Jul 30 07:11:17 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id HAA18170 for current-outgoing; Tue, 30 Jul 1996 07:11:17 -0700 (PDT) Received: from mantar.slip.netcom.com (mantar.slip.netcom.com [192.187.167.134]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id HAA18162 for ; Tue, 30 Jul 1996 07:11:13 -0700 (PDT) From: root@mantar.slip.netcom.com Received: by mantar.slip.netcom.com (IBM OS/2 SENDMAIL VERSION 1.3.2)/1.0) id AA0067; Tue, 30 Jul 96 07:10:24 -0700 Message-Id: <9607301410.AA0067@mantar.slip.netcom.com> References: In-Reply-To: Date: Tue, 30 Jul 96 06:32:43 PST Reply-To: Manfred Antar To: marxx@doomsday.org, root@mantar.slip.netcom.com Cc: wollman@lcs.mit.edu, current@freebsd.org Subject: Re: routed Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk as of last night it was working fine again! i did a make world monday at 8am pacific and built a new kernel (had to delete kernel compile directory) i'll test it some more today and see what happens ============================= | mantar@netcom.com | | Ph. (415) 647-4843 | ============================= From owner-freebsd-current Tue Jul 30 11:37:56 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id LAA25364 for current-outgoing; Tue, 30 Jul 1996 11:37:56 -0700 (PDT) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id LAA25355 for ; Tue, 30 Jul 1996 11:37:51 -0700 (PDT) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id LAA00327; Tue, 30 Jul 1996 11:34:56 -0700 From: Terry Lambert Message-Id: <199607301834.LAA00327@phaeton.artisoft.com> Subject: Re: eeprom To: graichen@axp5.physik.fu-berlin.de (Thomas Graichen) Date: Tue, 30 Jul 1996 11:34:56 -0700 (MST) Cc: current@FreeBSD.org In-Reply-To: <199607182053.WAA03200@mordillo> from "Thomas Graichen" at Jul 18, 96 10:53:03 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk > do we need this in the tree ? :-) (usr.sbin/eeprom) > > EEPROM(8) FreeBSD System Manager's Manual EEPROM(8) > > NAME > eeprom - openprom control utility Yes, to support openboot. It also looks like the correct interface to set GRUB parameters from a running system instead of a boot configuration menu. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-current Tue Jul 30 11:45:43 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id LAA26610 for current-outgoing; Tue, 30 Jul 1996 11:45:43 -0700 (PDT) Received: from utgard.bga.com (utgard.bga.com [205.238.129.45]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id LAA26589 for ; Tue, 30 Jul 1996 11:45:39 -0700 (PDT) Received: (from faulkner@localhost) by utgard.bga.com (8.7.5/8.7.3) id NAA24193 for current@freebsd.org; Tue, 30 Jul 1996 13:46:31 -0500 (CDT) Message-Id: <199607301846.NAA24193@utgard.bga.com> Subject: new_rkey.c in DES. func name change breaks KERBEROS To: current@freebsd.org Date: Tue, 30 Jul 1996 13:46:31 -0459 (CDT) From: "Boyd R. Faulkner" X-Mailer: ELM [version 2.4 PL25 ME8b] Content-Type: text Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi, in new_rkey.c, des_init_random_number_generator has become des_init_random_num_generator and kerberos doesn't know about it. ===> usr.sbin/kdb_init cc -O2 -m486 -pipe -DKERBEROS -DDEBUG -I/usr/src/eBones/usr.sbin/kdb_init/../../../secure/lib/libdes -I/usr/src/eBones/usr.sbin/kdb_init/../../include -Wall -I/usr/src/eBones/usr.sbin/kdb_init/../../../secure/lib/libdes -I/usr/src/eBones/usr.sbin/kdb_init/../../include -Wall -o kdb_init kdb_init.o -L/usr/obj/usr/src/eBones/usr.sbin/kdb_init/../../lib/libkdb -lkdb -L/usr/obj/usr/src/eBones/usr.sbin/kdb_init/../../lib/libkrb -lkrb -L/usr/obj/usr/src/eBones/usr.sbin/kdb_init/../../../secure/lib/libdes -ldes kdb_init.o: Undefined symbol `_des_init_random_number_generator' referenced from text segment There are more. Quite a few actually. Thanks, Boyd -- _____________________________________________________________________________ Boyd Faulkner "The fates lead him who will; faulkner@asgard.bga.com Him who won't, they drag." http://asgard.bga.com/~faulkner Old Roman Saying -- Source: Joseph Campbell _____________________________________________________________________________ From owner-freebsd-current Tue Jul 30 12:43:48 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id MAA01221 for current-outgoing; Tue, 30 Jul 1996 12:43:48 -0700 (PDT) Received: from hermes.algonet.se (mail.algonet.se [193.12.207.206]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id MAA01214 for ; Tue, 30 Jul 1996 12:43:45 -0700 (PDT) Received: from (johang@kairos.algonet.se [193.12.207.150]) by hermes.algonet.se (8.7.4/hdw.1.0) with SMTP id VAA19323; Tue, 30 Jul 1996 21:43:04 +0200 (MET DST) Message-Id: <199607301943.VAA19323@hermes.algonet.se> Comments: Authenticated sender is From: "Johan Granlund" To: "Charles C. Figueiredo" , Garrett Wollman , current@FreeBSD.ORG Date: Tue, 30 Jul 1996 22:35:32 +0000 MIME-Version: 1.0 Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Subject: 3com3c509 (was: routed) Priority: normal X-mailer: Pegasus Mail for Windows (v2.33) Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > On Mon, 29 Jul 1996, Manfred Antar wrote: > > > On Mon, 29 Jul 1996, Garrett Wollman wrote: > > I havn't been able keep a stable connection with a Sparc2 thru a > > 3com 3c509 (BNC) for about a week now.i have to keep doing > > ifconfig ep0 and this only works for about 2 minutes if that.i > > tried a version of routed about i month old with same results so i > > figured it must be the ep driver in kernel ? > > I'm having the same exact problem. Connections between my ss5 and > my > pc w/ a 3c509 in it die every minute. If I up and down the interface > it'll work again. I tried running with and without routed. routed > messes up my ppp :-). I do remember changes to if_ep.c One more voice. The problems started for me with the patch to the ep driver just prior to the release of V2.1.5. I have an old 3c509 (bootprom socket, not PNP aware) running at I/O=300 and INT=15. device ep0 at isa? port 0x300 net irq 15 vector epintr I get "no more bufferspace" or something similar. Ping from the BSD machine is not working but i get a response when sending a ping from another machine. Cheers /Johan > Charles > > > > > ============================== > > || mantar@netcom.com || > > || Ph. (415) 647-4843 || > > ============================== > > > > > > > -------------------------------------------------------------------- > --------- Charles C. Figueiredo CCF13 > marxx@doomsday.org > -------------------------------------------------------------------- > --------- > > ___________________________________________________________ Internet: Johang@Algonet.se I don't even speak for myself From owner-freebsd-current Tue Jul 30 13:23:46 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id NAA03941 for current-outgoing; Tue, 30 Jul 1996 13:23:46 -0700 (PDT) Received: from jraynard.demon.co.uk (jraynard.demon.co.uk [158.152.42.77]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id NAA03934 for ; Tue, 30 Jul 1996 13:23:40 -0700 (PDT) Received: (from fcurrent@localhost) by jraynard.demon.co.uk (8.6.12/8.6.12) id PAA03553; Tue, 30 Jul 1996 15:54:24 GMT From: James Raynard Message-Id: <199607301554.PAA03553@jraynard.demon.co.uk> Subject: Can't boot new kernel To: freebsd-current@freebsd.org Date: Tue, 30 Jul 1996 15:54:23 +0000 () X-Mailer: ELM [version 2.4 PL24 ME8a] Content-Type: text Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I wrote: > The problem is that references a type (_BSD_CT_RUNE_T_) that > is not defined anywhere in my source tree. In desperation, I tried > #defining it to _BSD_RUNE_T_, but cc doesn't seem able to pick up the > definition from , for some reason. Ahem. It seems my /usr/include/sys somehow got linked to /sys/sys, so when I re-installed 2.1.0 it clobbered my copy of -current's . I've re-installed /usr/src and everything seems to be working again... From owner-freebsd-current Tue Jul 30 13:30:22 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id NAA04505 for current-outgoing; Tue, 30 Jul 1996 13:30:22 -0700 (PDT) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id NAA04479; Tue, 30 Jul 1996 13:30:15 -0700 (PDT) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id NAA00470; Tue, 30 Jul 1996 13:27:59 -0700 From: Terry Lambert Message-Id: <199607302027.NAA00470@phaeton.artisoft.com> Subject: Re: anyone working on upgrading the msdosfs to NetBSD levels? To: rnordier@iafrica.com (Robert Nordier) Date: Tue, 30 Jul 1996 13:27:59 -0700 (MST) Cc: jkh@time.cdrom.com, pst@shockwave.com, hackers@FreeBSD.ORG, current@FreeBSD.ORG In-Reply-To: <199607221808.UAA00225@eac.iafrica.com> from "Robert Nordier" at Jul 22, 96 08:08:11 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > The FAT fs primitives are done and tested and I'm currently working > on VFAT support. > > Microsoft is shortly to be introducing a FAT32 filesystem to Windows > 95 which will increase maximum filesystem size from 2 (or 4, for > NT) gigabytes to 2 terabytes. The new filesystem makes use of > 32-bit (as opposed to 12-bit and 16-bit) FAT entries and will > require a fundamentally different handling of boot record, FATs, > and root directory, so I'm busy on provision for this also. I have a beta copy of this in house right now. It is intended solely for the OEM market. I think it will require a reinstall to share the disk in any case, since FIPS/PARTED/etc. doesn't understand the disk layout. In general, you will only ever see it on preinstalled systems. > The changes required for FAT32 support would probably be rather > difficult to graft onto the msdosfs at this stage: possibly another > factor supporting the decision to re-implement DOS/Win filesystem > support on FreeBSD. A reimplementation of the current/NetBSD code would be necessary to handle VFAT32. It is not *that* different than FAT, since it has to support Drivespace compression, which under Windows95 uses an undocumented ioctl() to get a block list back for a file (that's how their swap file is allowed to be non-contiguous, as well). > FAT32 is supposedly due for public release in the fall. I'm > currently working towards a similar release date for the new > filesystem. I think it's ready now. The limiting factor is going to be MS's OEM release date. Don't expect to install VFAT32 yourself, since NT can't mount VFAT32 partitions, and MS wants everyone to move to NT (Windows95 has always been billed as a transition product). Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-current Tue Jul 30 13:34:05 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id NAA04909 for current-outgoing; Tue, 30 Jul 1996 13:34:05 -0700 (PDT) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id NAA04872; Tue, 30 Jul 1996 13:33:49 -0700 (PDT) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id NAA00494; Tue, 30 Jul 1996 13:32:27 -0700 From: Terry Lambert Message-Id: <199607302032.NAA00494@phaeton.artisoft.com> Subject: Re: anyone working on upgrading the msdosfs to NetBSD levels? To: phk@critter.tfs.com (Poul-Henning Kamp) Date: Tue, 30 Jul 1996 13:32:27 -0700 (MST) Cc: rnordier@iafrica.com, bde@zeta.org.au, current@FreeBSD.org, hackers@FreeBSD.org In-Reply-To: <3900.838135055@critter.tfs.com> from "Poul-Henning Kamp" at Jul 23, 96 05:17:35 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk > > DRIVE DOS START DOS END > > cyl head sect || cyl head sect cyl head sect size > >------------------------------------------------------------------- > >wd0 | 525 | 64 | 63 || 0 | 1 | 1 | 126 | 63 | 63 | 512001 > >wd0 | 2099 | 64 | 63 || 0 | 1 | 1 | 189 | 63 | 63 | 766017 > > same drive || 250 | 0 | 1 | 523 | 63 | 63 | 1104768 > >wd0 | 788 | 64 | 63 || 0 | 1 | 1 | 787 | 63 | 63 | 3177153 > >wd0 | 621 | 64 | 63 || 0 | 1 | 1 | 619 | 63 | 63 | 2499777 > > This could be because the drives in question have a version of then > "OnTrack" diskmanager that we don't recognize". I don't think so... there are several other vendors doing the same thing. One issue is that you would see only one partition on such a drive -- and the partition ID would identify the software to itself. Since there is more than one partition listed, this can't be the problem. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-current Tue Jul 30 14:05:31 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id OAA06844 for current-outgoing; Tue, 30 Jul 1996 14:05:31 -0700 (PDT) Received: from shadows.aeon.net (shadows.aeon.net [194.100.41.1]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id OAA06832 for ; Tue, 30 Jul 1996 14:05:22 -0700 (PDT) Received: (from freebsd@localhost) by shadows.aeon.net (8.7.5/8.6.9) id AAA27959; Wed, 31 Jul 1996 00:00:36 +0300 (EET DST) From: Mr Operating System Message-Id: <199607302100.AAA27959@shadows.aeon.net> Subject: Re: A couple of problems!! To: kuku@gilberto.physik.rwth-aachen.de (Christoph P. Kukulies) Date: Wed, 31 Jul 1996 00:00:35 +0300 (EET DST) Cc: freebsd-current@freebsd.org In-Reply-To: <199607241110.NAA03054@gilberto.physik.rwth-aachen.de> from "Christoph P. Kukulies" at "Jul 24, 96 01:10:50 pm" 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-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > I'm back from a two weeks vacation and wading through the 4500 mail > messages I found some people pointing out problems with sup.de.freebsd.org > (my responsibility). I'm hoping getting things fixed soon. it works now? i think that atleast i was having a serious probs with it... =( i guess i gotta try it out, tho i assume sup will last eternally coz it's been about two weeks when i was using my machine last time... (vacation far away from computers) > sups often didn't finish since some US supservers were out of order or > connections were slow. Also the volume (gcc changes ?) was tremendous. > sup often never finished so that supscan wasn't run. ah, understandable... we should have dedicated lines between sup servers, but ofcourse, it's not possible... doesnt stop us from dreaming... =) > --Chris Christoph P. U. Kukulies kuku@gil.physik.rwth-aachen.de mickey From owner-freebsd-current Tue Jul 30 14:20:35 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id OAA07954 for current-outgoing; Tue, 30 Jul 1996 14:20:35 -0700 (PDT) Received: from eac.iafrica.com (196-7-192-139.iafrica.com [196.7.192.139]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id OAA07939; Tue, 30 Jul 1996 14:20:08 -0700 (PDT) Received: (from rnordier@localhost) by eac.iafrica.com (8.6.12/8.6.12) id XAA00293; Tue, 30 Jul 1996 23:17:47 +0200 From: Robert Nordier Message-Id: <199607302117.XAA00293@eac.iafrica.com> Subject: Re: anyone working on upgrading the msdosfs to NetBSD levels? To: terry@lambert.org (Terry Lambert) Date: Tue, 30 Jul 1996 23:17:46 +0200 (SAT) Cc: hackers@freebsd.org, current@freebsd.org In-Reply-To: <199607302027.NAA00470@phaeton.artisoft.com> from "Terry Lambert" at Jul 30, 96 01:27:59 pm X-Mailer: ELM [version 2.4 PL24 ME8a] Content-Type: text Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Terry Lambert wrote: > > Microsoft is shortly to be introducing a FAT32 filesystem to Windows > > 95 which will increase maximum filesystem size from 2 (or 4, for > > NT) gigabytes to 2 terabytes. The new filesystem makes use of > > 32-bit (as opposed to 12-bit and 16-bit) FAT entries and will > > require a fundamentally different handling of boot record, FATs, > > and root directory, so I'm busy on provision for this also. > > I have a beta copy of this in house right now. It is intended > solely for the OEM market. I think it will require a reinstall > to share the disk in any case, since FIPS/PARTED/etc. doesn't > understand the disk layout. In general, you will only ever see > it on preinstalled systems. [...] > > I think it's ready now. The limiting factor is going to be MS's OEM > release date. > > Don't expect to install VFAT32 yourself, since NT can't mount VFAT32 > partitions, and MS wants everyone to move to NT (Windows95 has always > been billed as a transition product). Good to have your comments, Terry. Would it be correct to say you consider VFAT32 support not worth the effort, or am I reading too much between the lines? -- Robert Nordier From owner-freebsd-current Tue Jul 30 15:07:52 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id PAA11908 for current-outgoing; Tue, 30 Jul 1996 15:07:52 -0700 (PDT) Received: from clam.niwa.cri.nz (clam.niwa.cri.nz [131.203.56.8]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id PAA11900 for ; Tue, 30 Jul 1996 15:07:46 -0700 (PDT) Received: from frc.niwa.cri.nz (frc.niwa.cri.nz [131.203.59.1]) by clam.niwa.cri.nz (8.7.5/8.7.3) with ESMTP id KAA29791; Wed, 31 Jul 1996 10:11:59 +1200 (NZST) Received: from neptune.niwa.cri.nz (neptune.niwa.cri.nz [131.203.58.4]) by frc.niwa.cri.nz (8.7.3/8.7.3) with SMTP id KAA29490; Wed, 31 Jul 1996 10:06:53 +1200 (NZST) Date: Wed, 31 Jul 1996 10:06:59 +1200 (NZST) From: Wayne Knowles X-Sender: wdk@neptune.niwa.cri.nz To: James Raynard cc: current@freebsd.org Subject: Re: Can't boot new kernel In-Reply-To: <199607301128.LAA01866@jraynard.demon.co.uk> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > Nope, I couldn't get a generic kernel to work either. I ended up > re-installing 2.1.0 (ab)using the 'upgrade' option. Now I'm trying > to upgrade back to -current, but I get > > > The problem is that references a type (_BSD_CT_RUNE_T_) that > is not defined anywhere in my source tree. In desperation, I tried > #defining it to _BSD_RUNE_T_, but cc doesn't seem able to pick up the > definition from , for some reason. With a current build tree /usr/include/sys is a symbolic link to the sys/sys directory of your -current tree. The 2.1 install would have downgraded your -current header files to 2.1 Hopefully re-supping the src-sys tree will bring it back. Also, I spent a bit of time working out why I had kernels that froze at the "waiting for SCSI devices to settle" phase. The diffs between the 2 build directories showed me that aic7xxx_seq.h was very different. Looking further I noticed: zl2bkc 1% make depend [ Compile stuff for genassym deleted - it all went OK ] ./genassym >assym.s rm -f param.c cp ../../conf/param.c . sh ../../kern/vnode_if.sh ../../kern/vnode_if.src cc -Wall -o aic7xxx_asm ../../dev/aic7xxx/aic7xxx_asm.c ./aic7xxx_asm -o aic7xxx_seq.h ../../dev/aic7xxx/aic7xxx.seq 0 out of 448 instructions used. ^^ Problem - The sequencer script for the Adaptec 2940 (hope I am using the right terminology) did not compile, and when the kernel went to reset the SCSI bus, the 2940 did not have any code to run! I haven't had time to work out why aic7xxx_asm failed to build the sequencer code (the source files were correct), and it doesn't seem to be related to the VM Code bugs that recently crept into the kernel. I will try and get to the bottom of it over the next few days. It does hilight a problem: aic7xxx_asm should have returned an exit code causing make to stop Comments?? -- _____ Wayne Knowles Title : Systems Manager / o \/ NIWA Fisheries Research Usenet: wdk@frc.niwa.cri.nz \/ v /\ PO. Box 14-901, Kilbirnie `---' Wellington, NEW ZEALAND From owner-freebsd-current Tue Jul 30 15:25:02 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id PAA13257 for current-outgoing; Tue, 30 Jul 1996 15:25:02 -0700 (PDT) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id PAA13249; Tue, 30 Jul 1996 15:24:58 -0700 (PDT) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id PAA00825; Tue, 30 Jul 1996 15:23:50 -0700 From: Terry Lambert Message-Id: <199607302223.PAA00825@phaeton.artisoft.com> Subject: Re: anyone working on upgrading the msdosfs to NetBSD levels? To: rnordier@iafrica.com (Robert Nordier) Date: Tue, 30 Jul 1996 15:23:50 -0700 (MST) Cc: terry@lambert.org, hackers@freebsd.org, current@freebsd.org In-Reply-To: <199607302117.XAA00293@eac.iafrica.com> from "Robert Nordier" at Jul 30, 96 11:17:46 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > I have a beta copy of this in house right now. It is intended > > solely for the OEM market. I think it will require a reinstall > > to share the disk in any case, since FIPS/PARTED/etc. doesn't > > understand the disk layout. In general, you will only ever see > > it on preinstalled systems. > [...] > > > > I think it's ready now. The limiting factor is going to be MS's OEM > > release date. > > > > Don't expect to install VFAT32 yourself, since NT can't mount VFAT32 > > partitions, and MS wants everyone to move to NT (Windows95 has always > > been billed as a transition product). > > Good to have your comments, Terry. > > Would it be correct to say you consider VFAT32 support not worth the > effort, or am I reading too much between the lines? The installation I have will "upgrade" an existing system. Whether VFAT32 becomes rampant will depend on whether they give it as an option. Right now, an upgrade kills NT, and the sector-based allocation table that replaces the partition table kills NT on dual-boot systems. I believe that they would have to release or announce NT support before they would be willing to let people use the version I have. The current estimate for Windows95's life cycle is 2 years before there is a unification of NT/95 to get a single Win32 based OS. If they release the VFAT32 for 95 without releasing it for NT, then the life cycle for Windows95 grows to 2 years + (the "+" being the delay in the NT release to allow upgrades). NT already has a problem with DriveSpace drives, and there are a lot of shops running NT on FAT FS's because FAT is actually *faster* than NTFS. I don't think Microsoft will kill NT on purpose. On the other hand, support for it can't hurt. The replacement for the partition table is bound to make it into NT even if nothing else does. I think the partition translation problem is logically seperate from the FAT FS itself (I think it will go into physical-to-logical device mapping in DEVFS), so it would be possible to support it without supporting the VFAT32 FS proper. Expect to need support for it in no less than a year, if ever. If I were writing a VFATFS, I would macro the calls to do the actual reads/writes and stick device range checking in a function layer that you can expect to go away in a later incarnation. Return "EINVAL" and do the logical to physical offset translation in your layer. All new FS's should expect to work on a "device" that is totally committed to the FS and looks like it starts at offset 0, and return EINVAL or EFAULT for out of range operations on the device. If this were there now, then the MSDOSFS would be incapable of corrupting non-MSDOSFS disk areas with the current code. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-current Wed Jul 31 02:24:04 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id CAA17609 for current-outgoing; Wed, 31 Jul 1996 02:24:04 -0700 (PDT) Received: from who.cdrom.com (who.cdrom.com [204.216.27.3]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id CAA17573; Wed, 31 Jul 1996 02:23:56 -0700 (PDT) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by who.cdrom.com (8.7.5/8.6.11) with SMTP id BAA01243 ; Wed, 31 Jul 1996 01:44:40 -0700 (PDT) Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.12/8.6.9) id SAA12179; Wed, 31 Jul 1996 18:37:27 +1000 Date: Wed, 31 Jul 1996 18:37:27 +1000 From: Bruce Evans Message-Id: <199607310837.SAA12179@godzilla.zeta.org.au> To: rnordier@iafrica.com, terry@lambert.org Subject: Re: anyone working on upgrading the msdosfs to NetBSD levels? Cc: current@FreeBSD.ORG, hackers@FreeBSD.ORG Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >All new FS's should expect to work on a "device" that is totally >committed to the FS and looks like it starts at offset 0, and return >EINVAL or EFAULT for out of range operations on the device. If >this were there now, then the MSDOSFS would be incapable of >corrupting non-MSDOSFS disk areas with the current code. It's always been there. Broken code can only write outside the range by corrupting the device number. Bruce From owner-freebsd-current Wed Jul 31 02:47:19 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id CAA19051 for current-outgoing; Wed, 31 Jul 1996 02:47:19 -0700 (PDT) Received: from bunyip.cc.uq.oz.au (daemon@bunyip.cc.uq.oz.au [130.102.2.1]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id CAA19046 for ; Wed, 31 Jul 1996 02:47:13 -0700 (PDT) Received: (from daemon@localhost) by bunyip.cc.uq.oz.au (8.7.5/8.7.3) id TAA29504 for freebsd-current@freebsd.org; Wed, 31 Jul 1996 19:47:09 +1000 Received: from orion.devetir.qld.gov.au by pandora.devetir.qld.gov.au (8.6.10/DEVETIR-E0.3a) with ESMTP id TAA15315 for ; Wed, 31 Jul 1996 19:48:24 +1000 Received: by orion.devetir.qld.gov.au (8.6.10/DEVETIR-0.3) id TAA00654; Wed, 31 Jul 1996 19:47:55 +1000 Date: Wed, 31 Jul 1996 19:47:55 +1000 From: Stephen McKay Message-Id: <199607310947.TAA00654@orion.devetir.qld.gov.au> To: freebsd-current@freebsd.org cc: syssgm@devetir.qld.gov.au Subject: Re: `const char rcsid[]' vs -traditional X-Newsreader: NN version 6.5.0 #1 (NOV) Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Bruce Evans wrote: >Many sources no longer compile with non-ANSI compilers because they >begin with > > const char rcsid[] = ... > >`const' is normally hidden for non-ANSI compilers by defining it as >nothing in , but copyright and id strings are normally >defined before including anything. I find: static const char rcsid[] = ... How long will it be before the ANSI compilers start discarding unreferenced static data? Or is "rcsid" already a special case in gcc? :-) Should we switch to #ident? It doesn't do anything useful on 2.1.5, but we could fix that. #ident "$Id: frobble.c,v ..." What does the C standard say about #ident? Has anyone put a copy of the standard on the web? Stephen. From owner-freebsd-current Wed Jul 31 04:42:23 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id EAA24391 for current-outgoing; Wed, 31 Jul 1996 04:42:23 -0700 (PDT) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id EAA24383 for ; Wed, 31 Jul 1996 04:42:13 -0700 (PDT) Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.12/8.6.9) id VAA24793; Wed, 31 Jul 1996 21:34:37 +1000 Date: Wed, 31 Jul 1996 21:34:37 +1000 From: Bruce Evans Message-Id: <199607311134.VAA24793@godzilla.zeta.org.au> To: freebsd-current@FreeBSD.ORG, syssgm@devetir.qld.gov.au Subject: Re: `const char rcsid[]' vs -traditional Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >I find: > static const char rcsid[] = ... >How long will it be before the ANSI compilers start discarding unreferenced >static data? Or is "rcsid" already a special case in gcc? :-) There's nothing to stop ANSI compilers from discarding unreferenced data, but declaring static variables as `const' is a documented way of stopping gcc from discarding them. At least, the following macro is a documented way for gcc-2.6.3: #define USE(var) \ static void *const use_##var = (&use_##var, &var, 0) This method also works for functions. It is used in MAKE_SET() in . Unfortunately, gcc with maximal warnings generates many warnings for this macro. E.g., when it is applied to static int x; USE(x); z.c:4: warning: initialization makes pointer from integer without a cast z.c:4: initializer element is not constant There are even more warnings (which actually occur thousands of times for compiling the kernel) for gcc-2.7.2. The USE() macro is no longer documented for gcc-2.7.2; you are supposed to use the `unused' attribute instead: static const int x __attribute__((__unused__)); The `unused' attribute doesn't work for gcc-2.6.3 so it will need to be used in a macro that expands to the attribute version only for recent versions of gcc. The `unused' attribute doesn't work completely for functions: static void x(void) __attribute__((__unused__)); static void x(void) {} This works right for -O2 but the function still gets deleted for -O3. The function probably needs to referenced via a pointer to keep it. MAKE_SET() fails to do this for the function pointer arg because the function pointer arg is only referenced in assembler. >Should we switch to #ident? It doesn't do anything useful on 2.1.5, but >we could fix that. > #ident "$Id: frobble.c,v ..." >What does the C standard say about #ident? Has anyone put a copy of the >standard on the web? #ident is a syntax error. The standard won't be put on the web until its owners figure out how to charge for it there :-(. Anyway, we shouldn't use #ident because it is impossible to hide the details in a macro. Bruce From owner-freebsd-current Wed Jul 31 04:47:45 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id EAA24517 for current-outgoing; Wed, 31 Jul 1996 04:47:45 -0700 (PDT) Received: from proxy.siemens.at (proxy.siemens.at [192.138.228.19]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id EAA24511 for ; Wed, 31 Jul 1996 04:47:33 -0700 (PDT) Received: from sol1.gud.siemens.co.at (sol-f.gud.siemens-austria) by proxy.siemens.at with SMTP id AA13265 (5.67a/IDA-1.5 for ); Wed, 31 Jul 1996 13:45:45 +0200 Received: from ws2301.gud.siemens.co.at by sol1.gud.siemens.co.at with smtp (Smail3.1.28.1 #7 for ) id m0ulZig-00022qC; Wed, 31 Jul 96 13:45 MET DST Received: by ws2301.gud.siemens.co.at (1.37.109.16/1.37) id AA008933391; Wed, 31 Jul 1996 13:43:11 +0200 From: "Hr.Ladavac" Message-Id: <199607311143.AA008933391@ws2301.gud.siemens.co.at> Subject: Re: `const char rcsid[]' vs -traditional To: syssgm@devetir.qld.gov.au (Stephen McKay) Date: Wed, 31 Jul 1996 13:43:11 +0200 (MESZ) Cc: freebsd-current@freebsd.org, syssgm@devetir.qld.gov.au In-Reply-To: <199607310947.TAA00654@orion.devetir.qld.gov.au> from "Stephen McKay" at Jul 31, 96 07:47:55 pm X-Mailer: ELM [version 2.4 PL24 ME8a] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk In his e-mail Stephen McKay wrote: > > Should we switch to #ident? It doesn't do anything useful on 2.1.5, but > we could fix that. > > #ident "$Id: frobble.c,v ..." > > What does the C standard say about #ident? Has anyone put a copy of the > standard on the web? Nothing, as far as I know. Which makes it non-standard (there are ANSI conformant preprocessors which ignore #ident with disgust. HP's, for instance.) /Marino > > Stephen. > From owner-freebsd-current Wed Jul 31 07:35:09 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id HAA02456 for current-outgoing; Wed, 31 Jul 1996 07:35:09 -0700 (PDT) Received: from fgate.flevel.co.uk (root@fgate.flevel.co.uk [194.6.101.2]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id HAA02409; Wed, 31 Jul 1996 07:34:56 -0700 (PDT) Received: from localhost (trefor@localhost) by fgate.flevel.co.uk (8.7.5/8.6.9) with SMTP id PAA26280; Wed, 31 Jul 1996 15:36:57 +0100 (BST) Date: Wed, 31 Jul 1996 15:36:56 +0100 (BST) From: "Trefor S." To: freebsd-hackers@freebsd.org, freebsd-current@freebsd.org, freebsd-chat@freebsd.org Subject: FreeBSD Accounts Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk If anyone is interested in accounts on FreeBSD systems take a look at this url: http://www.flevel.co.uk/services/netaccs.html Regards, Trefor S. From owner-freebsd-current Wed Jul 31 10:14:08 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id KAA10908 for current-outgoing; Wed, 31 Jul 1996 10:14:08 -0700 (PDT) Received: from cornus.FSL.ORST.EDU (root@FSL.ORST.EDU [128.193.112.105]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id KAA10903 for ; Wed, 31 Jul 1996 10:14:06 -0700 (PDT) Received: from picea.FSL.ORST.EDU (hernanw@picea.FSL.ORST.EDU [128.193.112.3]) by cornus.FSL.ORST.EDU (8.6.9/8.6.9) with ESMTP id KAA04310 for ; Wed, 31 Jul 1996 10:14:05 -0700 Received: (from hernanw@localhost) by picea.FSL.ORST.EDU (8.7/8.6.9) id KAA28450; Wed, 31 Jul 1996 10:14:04 -0700 (PDT) Date: Wed, 31 Jul 1996 10:14:04 -0700 (PDT) From: Wayne Hernandez To: freebsd-current@freebsd.org Subject: compile time Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk How long is a "make world" supposed to take? I have seen that it should take 3 hours on a P5-166, but on a P5-133 with 32 megs of ram the other day I got the following: 1938.277u 466.434s 59.38.84 67.1% 846+774k 11312+8744/io 2642pf +0w Started: 10:18 pm Finished: 11:18 pm All I have for compile options is "CFLAGS= -O2 -m486 -pipe". Nice, but hard to believe. This had to be make -k world since it bombs at usr.bin/tclsh. Wayne From owner-freebsd-current Wed Jul 31 10:31:31 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id KAA11658 for current-outgoing; Wed, 31 Jul 1996 10:31:31 -0700 (PDT) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id KAA11632; Wed, 31 Jul 1996 10:31:23 -0700 (PDT) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id KAA02343; Wed, 31 Jul 1996 10:29:46 -0700 From: Terry Lambert Message-Id: <199607311729.KAA02343@phaeton.artisoft.com> Subject: Re: anyone working on upgrading the msdosfs to NetBSD levels? To: bde@zeta.org.au (Bruce Evans) Date: Wed, 31 Jul 1996 10:29:45 -0700 (MST) Cc: rnordier@iafrica.com, terry@lambert.org, current@FreeBSD.org, hackers@FreeBSD.org In-Reply-To: <199607310837.SAA12179@godzilla.zeta.org.au> from "Bruce Evans" at Jul 31, 96 06:37:27 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk > >All new FS's should expect to work on a "device" that is totally > >committed to the FS and looks like it starts at offset 0, and return > >EINVAL or EFAULT for out of range operations on the device. If > >this were there now, then the MSDOSFS would be incapable of > >corrupting non-MSDOSFS disk areas with the current code. > > It's always been there. Broken code can only write outside the range > by corrupting the device number. The sd and od strategy rotutines do not error out. I am not sure I trust dscheck() entirely (since corruption occurs). Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-current Wed Jul 31 10:53:02 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id KAA13199 for current-outgoing; Wed, 31 Jul 1996 10:53:02 -0700 (PDT) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id KAA13191; Wed, 31 Jul 1996 10:53:00 -0700 (PDT) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id KAA02396; Wed, 31 Jul 1996 10:51:54 -0700 From: Terry Lambert Message-Id: <199607311751.KAA02396@phaeton.artisoft.com> Subject: Re: Opinions? NT VS UNIX, NT SUCKS SOMETIMES To: craig@ProGroup.COM (Craig Shaver) Date: Wed, 31 Jul 1996 10:51:54 -0700 (MST) Cc: freebsd-chat@FreeBSD.ORG, current@FreeBSD.ORG In-Reply-To: <199607192240.PAA06649@seabass.progroup.com> from "Craig Shaver" at Jul 19, 96 03:40:44 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > The NT's sat there and refused to run anything until > some user logged in! Apparently there is no way to have a program > automatically run unless you log in and then you have something in that > little "start" window. Nice design for a *server*! I guess if someone > uses NT for a server and the power goes down in the middle of the night, > then *someone* will have to be there to log in and start all of the server > processes. (snort, snicker, guffaw, ;^) In the registry: My Computer\ HKEY_LOCAL_MACHINE\ SOFTWARE\ Microsoft\ Windows\ CurrentVersion\ RunServices Edit New -> String Value MyAgent "C:\path_to_my-agent.exe" Will start a program each time the NT system starts. It's a bit more flexible than editing /etc/rc* on BSD. Registering the service so that the program is not killed by the first logoff is left as an exercise for the student. 8^). Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-current Wed Jul 31 11:32:25 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id LAA15342 for current-outgoing; Wed, 31 Jul 1996 11:32:25 -0700 (PDT) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id LAA15337; Wed, 31 Jul 1996 11:32:23 -0700 (PDT) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id LAA02458; Wed, 31 Jul 1996 11:29:45 -0700 From: Terry Lambert Message-Id: <199607311829.LAA02458@phaeton.artisoft.com> Subject: Re: anyone working on upgrading the msdosfs to NetBSD levels? To: rnordier@iafrica.com (Robert Nordier) Date: Wed, 31 Jul 1996 11:29:44 -0700 (MST) Cc: jkh@time.cdrom.com, pst@shockwave.com, hackers@freebsd.org, current@freebsd.org In-Reply-To: <199607221808.UAA00225@eac.iafrica.com> from "Robert Nordier" at Jul 22, 96 08:08:11 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > The FAT fs primitives are done and tested and I'm currently working > on VFAT support. Before you get too far on that, I have the algorithm it uses to avoid short name name space collisions. It's not pretty, but it works, and I think that was all Microsoft really cared about. Unfortunately, since the struct nameidata is not yet treated as an opaque object in a lot of places, it's not possible to do the lookup in multiple name spaces correctly in the vfs_lookup.c, where it belongs. I'm also not sure about the long name space storage which is in ISO-10646/16 (16 bit Unicode), since it is not possible to pass Unicode across the lookup interface (this will be a problem for any NTFS as well -- Linux is unfortunately way ahead of BSD here). The long names are case sensitive on storage and case insensitive on lookup. I don't know how you could emulate this for a DOS client (for instance) reading for a BSD mounted FS mapped to a DOS drive letter by the emulator. My opinion is that lookup changes are required, including adding a bit priority vector and name space identifier parameter to the VOP_LOOKUP. I can't help with the Unicode stuff given the current state of the BSD VFS; my suggestion is to punt, and treat the high byte as zero in all cases, converting it to ISO-8859-1 (Latin 1). This will damage utility for anyone outside the Latin 1 scope, but that can't be helped without the underlying VFS changes (appologies to non-Latin 1 using countries up front). If you get to where you need to work on name collision, let me know, and I can describe the algorithm in a couple of pages. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-current Wed Jul 31 11:36:18 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id LAA15592 for current-outgoing; Wed, 31 Jul 1996 11:36:18 -0700 (PDT) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id LAA15587 for ; Wed, 31 Jul 1996 11:36:16 -0700 (PDT) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id LAA02474; Wed, 31 Jul 1996 11:35:21 -0700 From: Terry Lambert Message-Id: <199607311835.LAA02474@phaeton.artisoft.com> Subject: Re: 2.2 SNAP soon? To: jkh@time.cdrom.com (Jordan K. Hubbard) Date: Wed, 31 Jul 1996 11:35:21 -0700 (MST) Cc: current@FreeBSD.org In-Reply-To: <2757.838090989@time.cdrom.com> from "Jordan K. Hubbard" at Jul 22, 96 08:03:09 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk > Now that 2.1.5 is off my plate, I can focus my attentions on 2.2 again > and am wondering if we're about due for another SNAP. If we're going > to switch compilers anytime soon, I'd also like that to happen before > the SNAP since this is going to be another CD version (the last was on > May 1st, 1996) - shall we shoot for August 1st, thereabouts? Anybody > got any burning issues they'd like to deal with before I do this? Have you rolled all the 2.1.5 release changes (if any) back into 2.2? Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-current Wed Jul 31 11:39:18 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id LAA15718 for current-outgoing; Wed, 31 Jul 1996 11:39:18 -0700 (PDT) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id LAA15713 for ; Wed, 31 Jul 1996 11:39:16 -0700 (PDT) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id LAA02488; Wed, 31 Jul 1996 11:38:39 -0700 From: Terry Lambert Message-Id: <199607311838.LAA02488@phaeton.artisoft.com> Subject: Re: Using clustered writes for NFSv3 To: dfr@render.com (Doug Rabson) Date: Wed, 31 Jul 1996 11:38:39 -0700 (MST) Cc: current@FreeBSD.ORG In-Reply-To: from "Doug Rabson" at Jul 23, 96 02:13:45 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > In NFSv3, when a buffer is written to a server, normally the server > doesn't write the data to stable storage immediately. Instead, it informs > the client that the data is written but 'unstable'. The client can later > commit the data to stable storage in a seperate call. [ ... ] > By a stroke of luck, the existing code for clustered writes in vfs_bio.c > and vfs_cluster.c can be made to work for NFSv3 as well. I needed to > tweak cluster_wbuild a little to copy over the B_NEEDCOMMIT flag and to > set the b_dirtyoff and b_dirtyend fields of the cluster appropriately. Oh, Doug, you stud, you! PLEASE someone, commit this change! Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-current Wed Jul 31 11:56:41 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id LAA16476 for current-outgoing; Wed, 31 Jul 1996 11:56:41 -0700 (PDT) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id LAA16470 for ; Wed, 31 Jul 1996 11:56:39 -0700 (PDT) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id LAA02534; Wed, 31 Jul 1996 11:54:31 -0700 From: Terry Lambert Message-Id: <199607311854.LAA02534@phaeton.artisoft.com> Subject: Re: cvs commit: src/sys/dev/ccd ccd.c src/sys/dev/vn vn.c src/sys/sys conf.h src/sys/i386/isa fd.c mcd.c scd.c wcd.c wd.c wt.c sOR To: jkh@time.cdrom.com (Jordan K. Hubbard) Date: Wed, 31 Jul 1996 11:54:31 -0700 (MST) Cc: gibbs@freefall.freebsd.org, joerg_wunsch@uriah.heep.sax.de, freebsd-current@freebsd.org In-Reply-To: <1430.838366976@time.cdrom.com> from "Jordan K. Hubbard" at Jul 26, 96 00:42:56 am X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > Persistence would allow you to change the permissions on a device and > > have them stick. If a device was not availible, it wouldn't show up > > in /dev, but if it came back (say after replacing faulty hardware) > > any permission changes you made in the past would show up as soon as > > the device did. > > It would also allow you to make links, like: > > ln -s /dev/cuaa0 /dev/mouse > > Which get recreated automagically when devfs is next mounted. Yes, > you could accomplish the same effect with a handful of commands in > /etc/rc.local, but the point is to make it transparent and so obey the > principle of least astonishment. Use an rc file for now, and wait for a union mount over root for later if you *must* have persistance. The union would need to be slightly modified -- a "markup union" to allow you to change permissions, etc.. The union is also where you would make symlinks. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-current Wed Jul 31 12:09:14 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id MAA17051 for current-outgoing; Wed, 31 Jul 1996 12:09:14 -0700 (PDT) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id MAA17043 for ; Wed, 31 Jul 1996 12:09:12 -0700 (PDT) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id MAA02568; Wed, 31 Jul 1996 12:08:06 -0700 From: Terry Lambert Message-Id: <199607311908.MAA02568@phaeton.artisoft.com> Subject: Re: cvs commit: src/sys/dev/ccd ccd.c src/sys/dev/vn vn.c src/sys/sys conf.h src/sys/i386/isa fd.c mcd.c scd.c wcd.c wd.c wt.c sOR To: jkh@time.cdrom.com (Jordan K. Hubbard) Date: Wed, 31 Jul 1996 12:08:06 -0700 (MST) Cc: phk@critter.tfs.com, wollman@lcs.mit.edu, current@FreeBSD.ORG, imp@village.org In-Reply-To: <20261.838411794@time.cdrom.com> from "Jordan K. Hubbard" at Jul 26, 96 01:09:54 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > There are a couple of fine points still not resolved. > > There is >still< no way to generally specify a policy: > > "Make all disks foo.bar mode 0640" > > You wouldn't be losing anything though - we don't have this now! :-) > You could still make the foo.bar devices underneath and chmod them > 640, which is not as elegant, no, but still gives the "traditional" > UNIX user a solution which makes sense. I wouldn't leave this as a > sticking point since the proposal solves so many of the problems > people have been complaining about so far, it should just be done. Actually, for a real "markup" FS, you could do this automatically by creating a placeholder (empty file/directory, depending on overlay type) whenever a chmod/chown/etc. takes place. > > Why would we even care about the type of node apart from "Directory" or > > "Not Directory" ? Ie, we could mount devfs on a FS that doesn't support > > c/b devs at all (msdos, hfs ...) > > I suppose that's true too! If you found a regular file named fd0a > with perms 700 then you'd just borrow the perms and ignore the type? Yes. Death to the specfs! Death to the struct fileops! Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-current Wed Jul 31 13:03:24 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id NAA21733 for current-outgoing; Wed, 31 Jul 1996 13:03:24 -0700 (PDT) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id NAA21721 for ; Wed, 31 Jul 1996 13:03:19 -0700 (PDT) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id NAA02651; Wed, 31 Jul 1996 13:02:18 -0700 From: Terry Lambert Message-Id: <199607312002.NAA02651@phaeton.artisoft.com> Subject: Re: Just a note that libkvm/ps/etc need to be recompiled To: toor@dyson.iquest.net (John S. Dyson) Date: Wed, 31 Jul 1996 13:02:18 -0700 (MST) Cc: current@FreeBSD.org In-Reply-To: <199607300330.WAA00274@dyson.iquest.net> from "John S. Dyson" at Jul 29, 96 10:30:40 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk > Since I backed out the VM changes, if you have rebuilt libkvm/ps/etc, then > you will have to rebuild them again... There doesn't seem to be a good reason for using the kvm interface instead of procfs. Unfortunately, to commit to that, procfs would have to become mandatory, since a shared interface would be hard. Would not being able to run ps on a kernel dump be bad? Or would it be worth supporting both interfaces? Either way, you'd need a libkvm that matched the kernel, but it would save every day use from all of these recompiles (w and so on, too). Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-current Wed Jul 31 13:06:31 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id NAA22035 for current-outgoing; Wed, 31 Jul 1996 13:06:31 -0700 (PDT) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id NAA22026 for ; Wed, 31 Jul 1996 13:06:27 -0700 (PDT) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id NAA02674; Wed, 31 Jul 1996 13:05:53 -0700 From: Terry Lambert Message-Id: <199607312005.NAA02674@phaeton.artisoft.com> Subject: Re: `const char rcsid[]' vs -traditional To: wollman@lcs.mit.edu (Garrett Wollman) Date: Wed, 31 Jul 1996 13:05:53 -0700 (MST) Cc: bde@zeta.org.au, wollman@lcs.mit.edu, current@FreeBSD.ORG In-Reply-To: <9607291826.AA22390@halloran-eldar.lcs.mit.edu> from "Garrett Wollman" at Jul 29, 96 02:26:51 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > It's broken for non-ANSI compilers. > > I'm quite aware of this; indeed, I quoted precisely that in my reply > to your original message. This doesn't answer the question of why > anyone would care (Terry Lambert excluded). I certainly don't. Is anyone else trying to use lcc? Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-current Wed Jul 31 13:16:27 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id NAA22606 for current-outgoing; Wed, 31 Jul 1996 13:16:27 -0700 (PDT) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id NAA22601 for ; Wed, 31 Jul 1996 13:16:24 -0700 (PDT) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id NAA02705; Wed, 31 Jul 1996 13:14:50 -0700 From: Terry Lambert Message-Id: <199607312014.NAA02705@phaeton.artisoft.com> Subject: Re: DEVFS broken by last devsw_add_generic()/bdevvp() changes To: peter@spinner.DIALix.COM (Peter Wemm) Date: Wed, 31 Jul 1996 13:14:50 -0700 (MST) Cc: current@FreeBSD.ORG In-Reply-To: <199607281624.AAA01851@spinner.DIALix.COM> from "Peter Wemm" at Jul 29, 96 00:24:05 am X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > It seems the last set of changes to the devsw creation routines and the > subsequent bdevvp() change has broken ffs_mount when trying to mount the > root filesystem on at least scsi disks. > > The "new" bdevvp() is returning 0, and ffs_mount is not checking it before > passing it onto ffs_mountfs. > > This might be because of the slice code not knowing whether or not it's > using the compatabilty slices or not, or simply because nothing has accessed > the slices in the first place to cause the slice code to create the > initial nodes in devfs. If an I/O is out of range on a wd, the wd strategy returns an error. If an I/O is out of range on an sd or od, the strategy does not error (there is a "goto done;" without an error being set). Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-current Wed Jul 31 18:30:40 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id SAA18580 for current-outgoing; Wed, 31 Jul 1996 18:30:40 -0700 (PDT) Received: from ice.fit.qut.edu.au (ice.fit.qut.edu.au [131.181.2.9]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id SAA18575; Wed, 31 Jul 1996 18:30:35 -0700 (PDT) Received: (from tony@localhost) by ice.fit.qut.edu.au (8.7.5/8.7.3) id LAA21976; Thu, 1 Aug 1996 11:30:58 +1000 (EST) Date: Thu, 1 Aug 1996 11:30:56 +1000 (EST) From: Tony Jago To: freebsd-current@freebsd.org Subject: NFS Diskless Dispare... Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Sender: T.Jago@fit.qut.edu.au Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi there all, I have been attempting to run a diskless freebsd system in a student lab enviroment. The way the system is setup is that the client boots his PC with the netboot.com binary. This mounts a read-only root file system which does some basic configuration and then sends a message to the server which gets the server to setup a read-write file system for that client only. The client then mounts this new file system read-write and then does a chroot to this file system and keeps booting. /usr, /dev etc. are mounted read-only. This all works file when there are only a few machines booting but as the load increases problems start to occurr. I will list them below: 1. The inability to mount file systems. The clients start barfing with something like "RPC mount timeout". This problem goes away after a while as the clients retry. I think its the mountd getting too many requests at once. Each client mounts 9 file systems. 2. Files permissions are read incorrectly. Files that should be able to be executed are giving "permission denied" messages. Sometimes even the kernel can't be loaded by netboot.com but if you persist by typing "autoboot" it will magically start to work. Machines fail to boot correctly as programms called in /etc/rc don't start (permission denied). 3. Pageing in of binaries cause the system to panic. Vnode_pager does not seem to like it when it can't page in executables, even when the file systems are hard mounted. Typically init can't be paged in and it Segment faults. This of course causes the kernel to panic. Other programs such as X often fall over but don't cause the system to panic. When this happens it happens to a number of machines in the room at exactly the same time. Perhaps this could be linked in with problem 2??? The system is currently running split over 2 servers. I am running NFS version 2 with hard mounts. I tryed NFSv3 (both TCP and UDP) for a while but it was even worse. The servers have 16 nfsd's running and the clients have 4 nfsiod's. The most stable configuration I have found at this stage has been 2.2-960612-SNAP but I am open to suggestions. I would also like to hear any success/failure stories from others running FreeBSD diskless systems. Thanks for taking the time to read to the bottom of this message. --- Tony Jago, System Administrator, E-Mail: T.Jago@fit.qut.edu.au Faculty of Information Technology, Web: http://www.fit.qut.edu.au/staff/~tony Queensland University of Technology. Box 2434, Brisbane 4001, AUSTRALIA. "We need more horsepower!" Phone: +61 7 3864-2573 Fax: +61 7 3864-1959 From owner-freebsd-current Thu Aug 1 02:42:18 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id CAA06976 for current-outgoing; Thu, 1 Aug 1996 02:42:18 -0700 (PDT) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id CAA06971 for ; Thu, 1 Aug 1996 02:42:13 -0700 (PDT) Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.12/8.6.9) id TAA18475; Thu, 1 Aug 1996 19:36:47 +1000 Date: Thu, 1 Aug 1996 19:36:47 +1000 From: Bruce Evans Message-Id: <199608010936.TAA18475@godzilla.zeta.org.au> To: peter@spinner.DIALix.COM, terry@lambert.org Subject: Re: DEVFS broken by last devsw_add_generic()/bdevvp() changes Cc: current@FreeBSD.ORG Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >If an I/O is out of range on a wd, the wd strategy returns an error. >If an I/O is out of range on an sd or od, the strategy does not error >(there is a "goto done;" without an error being set). Actually, they all "goto done;" and this is correct. dscheck() sets the error flag if necessary. There is no error for EOF. Bruce From owner-freebsd-current Thu Aug 1 02:57:03 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id CAA07461 for current-outgoing; Thu, 1 Aug 1996 02:57:03 -0700 (PDT) Received: from minnow.render.com (render.demon.co.uk [158.152.30.118]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id CAA07456 for ; Thu, 1 Aug 1996 02:57:01 -0700 (PDT) Received: from minnow.render.com (minnow.render.com [193.195.178.1]) by minnow.render.com (8.6.12/8.6.9) with SMTP id KAA21109; Thu, 1 Aug 1996 10:50:23 +0100 Date: Thu, 1 Aug 1996 10:50:22 +0100 (BST) From: Doug Rabson To: Terry Lambert cc: current@FreeBSD.ORG Subject: Re: Using clustered writes for NFSv3 In-Reply-To: <199607311838.LAA02488@phaeton.artisoft.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Wed, 31 Jul 1996, Terry Lambert wrote: > > In NFSv3, when a buffer is written to a server, normally the server > > doesn't write the data to stable storage immediately. Instead, it informs > > the client that the data is written but 'unstable'. The client can later > > commit the data to stable storage in a seperate call. > > [ ... ] > > > By a stroke of luck, the existing code for clustered writes in vfs_bio.c > > and vfs_cluster.c can be made to work for NFSv3 as well. I needed to > > tweak cluster_wbuild a little to copy over the B_NEEDCOMMIT flag and to > > set the b_dirtyoff and b_dirtyend fields of the cluster appropriately. > > Oh, Doug, you stud, you! Oh! I'm blushing! > > PLEASE someone, commit this change! Already done. -- Doug Rabson, Microsoft RenderMorphics Ltd. Mail: dfr@render.com Phone: +44 171 251 4411 FAX: +44 171 251 0939 From owner-freebsd-current Thu Aug 1 03:13:05 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id DAA08301 for current-outgoing; Thu, 1 Aug 1996 03:13:05 -0700 (PDT) Received: from time.cdrom.com (time.cdrom.com [204.216.27.226]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id DAA08296 for ; Thu, 1 Aug 1996 03:13:03 -0700 (PDT) Received: from time.cdrom.com (localhost [127.0.0.1]) by time.cdrom.com (8.7.5/8.6.9) with ESMTP id DAA07104; Thu, 1 Aug 1996 03:12:38 -0700 (PDT) To: Tony Jago cc: freebsd-current@freebsd.org Subject: Re: NFS Diskless Dispare... In-reply-to: Your message of "Thu, 01 Aug 1996 11:30:56 +1000." Date: Thu, 01 Aug 1996 03:12:38 -0700 Message-ID: <7102.838894358@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > 1. The inability to mount file systems. The clients start barfing with > something like "RPC mount timeout". This problem goes away after a > while as the clients retry. I think its the mountd getting too many > requests at once. Each client mounts 9 file systems. I think that this is a more generic NFS bug in -current. I can reproduce this, even causing mountd to silently exit (no core, no syslog msg) with just one client and some fierce AMD-assisted pounding on a 2.2-current NFS server. Debugging this will be challenging, so all the help we can get will be useful. If you can add some extra logging to strategic spots in your mountd, perhaps, and analyse the data generated you might even find the fix yourself. > 2. Files permissions are read incorrectly. Files that should be able to > be executed are giving "permission denied" messages. Sometimes even > the kernel can't be loaded by netboot.com but if you persist by > typing "autoboot" it will magically start to work. Machines fail to > boot correctly as programms called in /etc/rc don't start > (permission denied). Probably more NFS bogosity. > 3. Pageing in of binaries cause the system to panic. Vnode_pager does > not seem to like it when it can't page in executables, even when the See #2. :-) > version 2 with hard mounts. I tryed NFSv3 (both TCP and UDP) for a while > but it was even worse. The servers have 16 nfsd's running and the That's not surprising. > clients have 4 nfsiod's. The most stable configuration I have found at > this stage has been 2.2-960612-SNAP but I am open to suggestions. 2.1.5? Its NFS is still unstable, but I don't believe anywhere near the state it's in with -current. Jordan From owner-freebsd-current Thu Aug 1 03:53:24 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id DAA09720 for current-outgoing; Thu, 1 Aug 1996 03:53:24 -0700 (PDT) Received: from minnow.render.com (render.demon.co.uk [158.152.30.118]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id DAA09715 for ; Thu, 1 Aug 1996 03:53:19 -0700 (PDT) Received: from minnow.render.com (minnow.render.com [193.195.178.1]) by minnow.render.com (8.6.12/8.6.9) with SMTP id LAA21550; Thu, 1 Aug 1996 11:54:03 +0100 Date: Thu, 1 Aug 1996 11:54:03 +0100 (BST) From: Doug Rabson To: "Jordan K. Hubbard" cc: Tony Jago , freebsd-current@FreeBSD.ORG Subject: Re: NFS Diskless Dispare... In-Reply-To: <7102.838894358@time.cdrom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Thu, 1 Aug 1996, Jordan K. Hubbard wrote: > > 1. The inability to mount file systems. The clients start barfing with > > something like "RPC mount timeout". This problem goes away after a > > while as the clients retry. I think its the mountd getting too many > > requests at once. Each client mounts 9 file systems. > > I think that this is a more generic NFS bug in -current. I can > reproduce this, even causing mountd to silently exit (no core, no > syslog msg) with just one client and some fierce AMD-assisted pounding > on a 2.2-current NFS server. Debugging this will be challenging, so > all the help we can get will be useful. If you can add some extra > logging to strategic spots in your mountd, perhaps, and analyse the > data generated you might even find the fix yourself. Ouch! This would be pretty hard to reproduce here since I only have one system which runs -current and most of the time that machine is in Win95 :-(. Try compiling mountd with DEBUG_FLAGS=-g, then attaching gdb to it with 'attach pid'. If it doesn't fault, set a breakpoint in _exit. > > > 2. Files permissions are read incorrectly. Files that should be able to > > be executed are giving "permission denied" messages. Sometimes even > > the kernel can't be loaded by netboot.com but if you persist by > > typing "autoboot" it will magically start to work. Machines fail to > > boot correctly as programms called in /etc/rc don't start > > (permission denied). > > Probably more NFS bogosity. I think for diskless root filesystems, you must export the fs with -root=0, otherwise lots of stuff will break. > > > 3. Pageing in of binaries cause the system to panic. Vnode_pager does > > not seem to like it when it can't page in executables, even when the > > See #2. :-) Probably paging from a file which root can't access (see above). > > > version 2 with hard mounts. I tryed NFSv3 (both TCP and UDP) for a while > > but it was even worse. The servers have 16 nfsd's running and the > > That's not surprising. > > > clients have 4 nfsiod's. The most stable configuration I have found at > > this stage has been 2.2-960612-SNAP but I am open to suggestions. > > 2.1.5? Its NFS is still unstable, but I don't believe anywhere near > the state it's in with -current. I think some of the stability problems with NFS are due to its lack of vnode locking primitives. This might be addressed by the lite2 fs work but if not, I will try to get something in after that work is merged. -- Doug Rabson, Microsoft RenderMorphics Ltd. Mail: dfr@render.com Phone: +44 171 251 4411 FAX: +44 171 251 0939 From owner-freebsd-current Thu Aug 1 05:45:00 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id FAA13659 for current-outgoing; Thu, 1 Aug 1996 05:45:00 -0700 (PDT) Received: from dyson.iquest.net (dyson.iquest.net [198.70.144.127]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id FAA13654 for ; Thu, 1 Aug 1996 05:44:57 -0700 (PDT) Received: (from root@localhost) by dyson.iquest.net (8.7.5/8.6.9) id HAA05038; Thu, 1 Aug 1996 07:43:56 -0500 (EST) From: "John S. Dyson" Message-Id: <199608011243.HAA05038@dyson.iquest.net> Subject: Re: Just a note that libkvm/ps/etc need to be recompiled To: terry@lambert.org (Terry Lambert) Date: Thu, 1 Aug 1996 07:43:55 -0500 (EST) Cc: current@FreeBSD.ORG In-Reply-To: <199607312002.NAA02651@phaeton.artisoft.com> from "Terry Lambert" at Jul 31, 96 01:02:18 pm X-Mailer: ELM [version 2.4 PL24 ME8] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > Either way, you'd need a libkvm that matched the kernel, but it would > save every day use from all of these recompiles (w and so on, too). > That certainly has not been well thought out. I do think that the system is much less useful without procfs. It is useful even in many embedded applications. Perhaps ps/libkvm/etc need to be thought out better. But remember, -current isn't targeted for everyday use :-). John From owner-freebsd-current Thu Aug 1 06:46:58 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id GAA15373 for current-outgoing; Thu, 1 Aug 1996 06:46:58 -0700 (PDT) Received: from fgate.flevel.co.uk (root@fgate.flevel.co.uk [194.6.101.2]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id GAA15368 for ; Thu, 1 Aug 1996 06:46:54 -0700 (PDT) Received: from localhost (dev@localhost) by fgate.flevel.co.uk (8.7.5/8.6.9) with SMTP id OAA11692; Thu, 1 Aug 1996 14:48:22 +0100 (BST) Date: Thu, 1 Aug 1996 14:48:21 +0100 (BST) From: Developer To: "John S. Dyson" cc: Terry Lambert , current@freebsd.org Subject: Re: Just a note that libkvm/ps/etc need to be recompiled In-Reply-To: <199608011243.HAA05038@dyson.iquest.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Thu, 1 Aug 1996, John S. Dyson wrote: > > > > Either way, you'd need a libkvm that matched the kernel, but it would > > save every day use from all of these recompiles (w and so on, too). > > > That certainly has not been well thought out. I do think that the > system is much less useful without procfs. It is useful even in many embedded > applications. Perhaps ps/libkvm/etc need to be thought out better. > > But remember, -current isn't targeted for everyday use :-). I wonder if it might be an idea to have a kernel call that gets the proc structure size, that way libkvm/ps/w etc wouldn`t have to be re-compiled when the structure changed? Regards, Trefor S. From owner-freebsd-current Thu Aug 1 07:08:12 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id HAA16161 for current-outgoing; Thu, 1 Aug 1996 07:08:12 -0700 (PDT) Received: from halloran-eldar.lcs.mit.edu (halloran-eldar.lcs.mit.edu [18.26.0.159]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id HAA16154 for ; Thu, 1 Aug 1996 07:08:10 -0700 (PDT) Received: by halloran-eldar.lcs.mit.edu; (5.65/1.1.8.2/19Aug95-0530PM) id AA09584; Thu, 1 Aug 1996 10:07:51 -0400 Date: Thu, 1 Aug 1996 10:07:51 -0400 From: Garrett Wollman Message-Id: <9608011407.AA09584@halloran-eldar.lcs.mit.edu> To: Developer Cc: current@freebsd.org Subject: Re: Just a note that libkvm/ps/etc need to be recompiled In-Reply-To: References: <199608011243.HAA05038@dyson.iquest.net> Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk < said: > I wonder if it might be an idea to have a kernel call that gets the proc > structure size, that way libkvm/ps/w etc wouldn`t have to be re-compiled > when the structure changed? The actual size of the structure makes little difference, it's where the fields are placed in it that is of importance. (You could always make it self-encoding for size...) -GAWollman -- Garrett A. Wollman | O Siem / We are all family / O Siem / We're all the same wollman@lcs.mit.edu | O Siem / The fires of freedom Opinions not those of| Dance in the burning flame MIT, LCS, ANA, or NSA| - Susan Aglukark and Chad Irschick From owner-freebsd-current Thu Aug 1 08:59:24 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id IAA22168 for current-outgoing; Thu, 1 Aug 1996 08:59:24 -0700 (PDT) Received: from fgate.flevel.co.uk (root@fgate.flevel.co.uk [194.6.101.2]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id IAA22160 for ; Thu, 1 Aug 1996 08:59:18 -0700 (PDT) Received: from localhost (dev@localhost) by fgate.flevel.co.uk (8.7.5/8.6.9) with SMTP id RAA12643; Thu, 1 Aug 1996 17:01:38 +0100 (BST) Date: Thu, 1 Aug 1996 17:01:37 +0100 (BST) From: Developer To: Garrett Wollman cc: current@freebsd.org Subject: Re: Just a note that libkvm/ps/etc need to be recompiled In-Reply-To: <9608011407.AA09584@halloran-eldar.lcs.mit.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Thu, 1 Aug 1996, Garrett Wollman wrote: > < said: > > > I wonder if it might be an idea to have a kernel call that gets the proc > > structure size, that way libkvm/ps/w etc wouldn`t have to be re-compiled > > when the structure changed? > > The actual size of the structure makes little difference, it's where > the fields are placed in it that is of importance. (You could always > make it self-encoding for size...) Well, that is true - but still at the moment adding extra fields causes you to have to re-compile ps/w/libkvm etc... even if they are not required externally. I actually went through this one myself, Ive added the ability to filter ranges of IP addresses and certian ports on different users. Regards, Trefor S. From owner-freebsd-current Thu Aug 1 09:01:56 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id JAA22330 for current-outgoing; Thu, 1 Aug 1996 09:01:56 -0700 (PDT) Received: from walkabout.asstdc.com.au (root@walkabout.asstdc.com.au [202.12.127.73]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id JAA22325 for ; Thu, 1 Aug 1996 09:01:53 -0700 (PDT) Received: (from imb@localhost) by walkabout.asstdc.com.au (8.7.5/BSD4.4) id CAA01219 for current@freebsd.org; Fri, 2 Aug 1996 02:01:49 +1000 (EST) From: michael butler Message-Id: <199608011601.CAA01219@walkabout.asstdc.com.au> Subject: 3Com (589b) troubles To: current@freebsd.org Date: Fri, 2 Aug 1996 02:01:48 +1000 (EST) X-Comment: Phone 0419-240-180, International +61-419-240-180 X-Comment: finger imb@asstdc.com.au for PGP public key 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-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Once more, a recent change to the ep driver has broken the 3c589. Intermittently, most often when running "trafshow", it'll just drop the link activity light on my hub and go deaf :-( Hitting ^C to exit "trafshow" is enough to make it go again, michael From owner-freebsd-current Thu Aug 1 09:09:22 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id JAA22650 for current-outgoing; Thu, 1 Aug 1996 09:09:22 -0700 (PDT) Received: from crh.cl.msu.edu (crh.cl.msu.edu [35.8.1.24]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id JAA22642 for ; Thu, 1 Aug 1996 09:09:14 -0700 (PDT) Received: (from henrich@localhost) by crh.cl.msu.edu (8.7.5/8.7.3) id MAA03941 for freebsd-current@freebsd.org; Thu, 1 Aug 1996 12:09:13 -0400 (EDT) From: Charles Henrich Message-Id: <199608011609.MAA03941@crh.cl.msu.edu> Subject: XFqcam on 2.2 hurts much more than on 2.1 To: freebsd-current@freebsd.org Date: Thu, 1 Aug 1996 12:09:13 -0400 (EDT) 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-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I have been running xfqcam which polls the lpt port for images in a tight loop (I think), under 2.1 this process ran happily snarfing up all spare cycles, but having virtually zero impact on any other system resources, including interactive response. Under 2.2 running this same program wreaks havoc on virtually everything else running, slowing performance waaayyy down. Anyone know why this might be? -Crh Charles Henrich Michigan State University henrich@msu.edu http://pilot.msu.edu/~henrich From owner-freebsd-current Thu Aug 1 10:40:04 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id KAA27313 for current-outgoing; Thu, 1 Aug 1996 10:40:04 -0700 (PDT) Received: from rocky.mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id KAA27191; Thu, 1 Aug 1996 10:39:27 -0700 (PDT) Received: (from nate@localhost) by rocky.mt.sri.com (8.7.5/8.7.3) id LAA07374; Thu, 1 Aug 1996 11:39:15 -0600 (MDT) Date: Thu, 1 Aug 1996 11:39:15 -0600 (MDT) Message-Id: <199608011739.LAA07374@rocky.mt.sri.com> From: Nate Williams To: michael butler Cc: current@freebsd.org, committers@freebsd.org Subject: if_ep.c driver brokeness (was Re: 3Com (589b) troubles) In-Reply-To: <199608011601.CAA01219@walkabout.asstdc.com.au> References: <199608011601.CAA01219@walkabout.asstdc.com.au> Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > Once more, a recent change to the ep driver has broken the 3c589. > Intermittently, most often when running "trafshow", it'll just drop the link > activity light on my hub and go deaf :-( Hitting ^C to exit "trafshow" is > enough to make it go again, Actually, this change broke the ep driver for almost every card. If nobody stands up and says anything in the next day or so, I'm going to back out the change, since it was already backed out of -stable. Nate From owner-freebsd-current Thu Aug 1 10:51:15 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id KAA27884 for current-outgoing; Thu, 1 Aug 1996 10:51:15 -0700 (PDT) Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id KAA27879 for ; Thu, 1 Aug 1996 10:51:12 -0700 (PDT) Received: from sax.sax.de by irz301.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id TAA06810 for ; Thu, 1 Aug 1996 19:51:04 +0200 Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id TAA04055 for freebsd-current@FreeBSD.org; Thu, 1 Aug 1996 19:51:04 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.7.5/8.6.9) id TAA19056 for freebsd-current@FreeBSD.org; Thu, 1 Aug 1996 19:29:29 +0200 (MET DST) From: J Wunsch Message-Id: <199608011729.TAA19056@uriah.heep.sax.de> Subject: Re: `const char rcsid[]' vs -traditional To: freebsd-current@FreeBSD.org (FreeBSD-current users) Date: Thu, 1 Aug 1996 19:29:29 +0200 (MET DST) Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <199607311134.VAA24793@godzilla.zeta.org.au> from Bruce Evans at "Jul 31, 96 09:34:37 pm" 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 X-Mailer: ELM [version 2.4ME+ PL17 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk As Bruce Evans wrote: > > #ident "$Id: frobble.c,v ..." > > >What does the C standard say about #ident? > #ident is a syntax error. What about ``#pragma ident''? > Anyway, we shouldn't use #ident because it is impossible to hide the details > in a macro. Of course, this cannot be solved with #pragma either. We definately need more sections in the object file (and thus likely ELF format) in order to move the #ident's out of the .text section, without omitting them from the binary file. Maybe we could abuse __attribute__ to force data or code into different sections? -- 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-current Thu Aug 1 10:52:28 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id KAA28149 for current-outgoing; Thu, 1 Aug 1996 10:52:28 -0700 (PDT) Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id KAA28134 for ; Thu, 1 Aug 1996 10:52:12 -0700 (PDT) Received: from sax.sax.de by irz301.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id TAA06825 for ; Thu, 1 Aug 1996 19:51:10 +0200 Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id TAA04063 for freebsd-current@FreeBSD.org; Thu, 1 Aug 1996 19:51:10 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.7.5/8.6.9) id TAA19423 for freebsd-current@FreeBSD.org; Thu, 1 Aug 1996 19:47:32 +0200 (MET DST) From: J Wunsch Message-Id: <199608011747.TAA19423@uriah.heep.sax.de> Subject: Re: Just a note that libkvm/ps/etc need to be recompiled To: freebsd-current@FreeBSD.org (FreeBSD-current users) Date: Thu, 1 Aug 1996 19:47:31 +0200 (MET DST) Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <199607312002.NAA02651@phaeton.artisoft.com> from Terry Lambert at "Jul 31, 96 01:02:18 pm" 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 X-Mailer: ELM [version 2.4ME+ PL17 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk As Terry Lambert wrote: > There doesn't seem to be a good reason for using the kvm interface > instead of procfs. Unfortunately, to commit to that, procfs would > have to become mandatory, since a shared interface would be hard. procfs is already semi-mandatory. ps(1) will omit certain information if procfs is not mounted (like the start time). -- 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-current Thu Aug 1 11:04:57 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id LAA28724 for current-outgoing; Thu, 1 Aug 1996 11:04:57 -0700 (PDT) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id LAA28717 for ; Thu, 1 Aug 1996 11:04:55 -0700 (PDT) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id LAA04239; Thu, 1 Aug 1996 11:02:12 -0700 From: Terry Lambert Message-Id: <199608011802.LAA04239@phaeton.artisoft.com> Subject: Re: NFS Diskless Dispare... To: dfr@render.com (Doug Rabson) Date: Thu, 1 Aug 1996 11:02:12 -0700 (MST) Cc: jkh@time.cdrom.com, tony@fit.qut.edu.au, freebsd-current@FreeBSD.ORG In-Reply-To: from "Doug Rabson" at Aug 1, 96 11:54:03 am X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > > 1. The inability to mount file systems. The clients start barfing with > > > something like "RPC mount timeout". This problem goes away after a > > > while as the clients retry. I think its the mountd getting too many > > > requests at once. Each client mounts 9 file systems. Mountd is far from being concurrent enough. At one time, back in the 1.1.5.1 days, I had it hacked up sufficiently to allow NFS access by 20 or so X terminals, all at the same time. I think this is kludgable by hacking the timeout up for now. Mountd wants a bit of a rewrite once real threading is generally available. > > I think that this is a more generic NFS bug in -current. I can > > reproduce this, even causing mountd to silently exit (no core, no > > syslog msg) with just one client and some fierce AMD-assisted pounding > > on a 2.2-current NFS server. I think the exit is a seperate problem. I'd be curious about what you could find out from a trace of the process started before it dies. > > > 2. Files permissions are read incorrectly. Files that should be able to > > > be executed are giving "permission denied" messages. Sometimes even > > > the kernel can't be loaded by netboot.com but if you persist by > > > typing "autoboot" it will magically start to work. Machines fail to > > > boot correctly as programms called in /etc/rc don't start > > > (permission denied). > > > > Probably more NFS bogosity. [ ... ] > I think for diskless root filesystems, you must export the fs with > -root=0, otherwise lots of stuff will break. [ this is true, but it's not the cause ] > > > 3. Pageing in of binaries cause the system to panic. Vnode_pager does > > > not seem to like it when it can't page in executables, even when the > > > > See #2. :-) > > Probably paging from a file which root can't access (see above). Actually, I think it's the problem in vop_bmap for nfs that David noted the other day. > > 2.1.5? Its NFS is still unstable, but I don't believe anywhere near > > the state it's in with -current. > > I think some of the stability problems with NFS are due to its lack of > vnode locking primitives. This might be addressed by the lite2 fs work > but if not, I will try to get something in after that work is merged. The NFS, procfs, and several other non-boot-critical FS's didn't have the new primitives in the patch sets we've seen so far. I don't think they will have much positive effect on this problem, but there are three or four other problems that will clear up (mostly two client race conditions). Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-current Thu Aug 1 11:05:59 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id LAA28796 for current-outgoing; Thu, 1 Aug 1996 11:05:59 -0700 (PDT) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id LAA28791 for ; Thu, 1 Aug 1996 11:05:58 -0700 (PDT) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id LAA04259; Thu, 1 Aug 1996 11:04:18 -0700 From: Terry Lambert Message-Id: <199608011804.LAA04259@phaeton.artisoft.com> Subject: Re: DEVFS broken by last devsw_add_generic()/bdevvp() changes To: bde@zeta.org.au (Bruce Evans) Date: Thu, 1 Aug 1996 11:04:18 -0700 (MST) Cc: peter@spinner.DIALix.COM, terry@lambert.org, current@FreeBSD.ORG In-Reply-To: <199608010936.TAA18475@godzilla.zeta.org.au> from "Bruce Evans" at Aug 1, 96 07:36:47 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > >If an I/O is out of range on a wd, the wd strategy returns an error. > >If an I/O is out of range on an sd or od, the strategy does not error > >(there is a "goto done;" without an error being set). > > Actually, they all "goto done;" and this is correct. dscheck() sets > the error flag if necessary. There is no error for EOF. My problem with od and sd are that they silently fail. I don't disagree that they should be allowed to fail, only that they do so silently. There seems to be a possible cascade failure for residuals in excess of the block size from a silent failure... maybe I'm reading things wrong? Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-current Thu Aug 1 11:14:38 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id LAA29084 for current-outgoing; Thu, 1 Aug 1996 11:14:38 -0700 (PDT) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id LAA29079 for ; Thu, 1 Aug 1996 11:14:37 -0700 (PDT) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id LAA04278; Thu, 1 Aug 1996 11:12:52 -0700 From: Terry Lambert Message-Id: <199608011812.LAA04278@phaeton.artisoft.com> Subject: Re: Just a note that libkvm/ps/etc need to be recompiled To: wollman@lcs.mit.edu (Garrett Wollman) Date: Thu, 1 Aug 1996 11:12:52 -0700 (MST) Cc: dev@fgate.flevel.co.uk, current@freebsd.org In-Reply-To: <9608011407.AA09584@halloran-eldar.lcs.mit.edu> from "Garrett Wollman" at Aug 1, 96 10:07:51 am X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > I wonder if it might be an idea to have a kernel call that gets the proc > > structure size, that way libkvm/ps/w etc wouldn`t have to be re-compiled > > when the structure changed? > > The actual size of the structure makes little difference, it's where > the fields are placed in it that is of importance. (You could always > make it self-encoding for size...) Agreed... it's not simply that new fields are being added to the end of the structure; basic structure contents have changes on more than one occasion. Maybe this would work if we had "one final" change in element ordering to put the pieces necessary for ps, w, etc., in an "exposed interface" area in the structure, so that basic structure content changes would not effect the utilities. Even then, this is not a portable approach to the problem; the structure size and the array offset size are often different on many architectures because of structure alignment and packing differences. The structure size and the structure array element offset interval would both need to be read from the kernel. I wonder at the utility of treating a kernel dump as a /dev/kmem image for things like ps and w, anyway... if there is none, then a procfs soloution would seem to be the right way to go. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-current Thu Aug 1 11:21:22 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id LAA29506 for current-outgoing; Thu, 1 Aug 1996 11:21:22 -0700 (PDT) Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id LAA29483; Thu, 1 Aug 1996 11:21:04 -0700 (PDT) Received: from sax.sax.de by irz301.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id UAA07598; Thu, 1 Aug 1996 20:21:02 +0200 Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id UAA04395; Thu, 1 Aug 1996 20:21:01 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.7.5/8.6.9) id TAA19568; Thu, 1 Aug 1996 19:52:51 +0200 (MET DST) From: J Wunsch Message-Id: <199608011752.TAA19568@uriah.heep.sax.de> Subject: Re: if_ep.c driver brokeness (was Re: 3Com (589b) troubles) To: nate@mt.sri.com (Nate Williams) Date: Thu, 1 Aug 1996 19:52:51 +0200 (MET DST) Cc: imb@asstdc.com.au, current@freebsd.org, committers@freebsd.org Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <199608011739.LAA07374@rocky.mt.sri.com> from Nate Williams at "Aug 1, 96 11:39:15 am" 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 X-Mailer: ELM [version 2.4ME+ PL17 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk As Nate Williams wrote: > Actually, this change broke the ep driver for almost every card. If The interesting thing is that there are also (few? many?) people where it actually improved things. Anyway, a better fix is certainly needed (one that satisfies all people, not just a few only), so back it out and suggest another one. :) -- 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-current Thu Aug 1 11:22:13 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id LAA29574 for current-outgoing; Thu, 1 Aug 1996 11:22:13 -0700 (PDT) Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id LAA29567 for ; Thu, 1 Aug 1996 11:22:05 -0700 (PDT) Received: from sax.sax.de by irz301.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id UAA07608; Thu, 1 Aug 1996 20:21:10 +0200 Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id UAA04399; Thu, 1 Aug 1996 20:21:09 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.7.5/8.6.9) id UAA19845; Thu, 1 Aug 1996 20:09:33 +0200 (MET DST) From: J Wunsch Message-Id: <199608011809.UAA19845@uriah.heep.sax.de> Subject: Re: NFS Diskless Dispare... To: freebsd-current@FreeBSD.org (FreeBSD-current users) Date: Thu, 1 Aug 1996 20:09:33 +0200 (MET DST) Cc: tony@fit.qut.edu.au Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: from Doug Rabson at "Aug 1, 96 11:54:03 am" 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 X-Mailer: ELM [version 2.4ME+ PL17 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk As Doug Rabson wrote: > > > 2. Files permissions are read incorrectly. Files that should be able to > > > be executed are giving "permission denied" messages. > > Probably more NFS bogosity. > > I think for diskless root filesystems, you must export the fs with > -root=0, otherwise lots of stuff will break. I don't think that's Tony's problem. Note that he writes that everything works well if only a few machines boot diskless (i can basically confirm this, but my single scratch box is about all i have to test). > > > 3. Pageing in of binaries cause the system to panic. Vnode_pager does > > > not seem to like it when it can't page in executables, even when the > > > > See #2. :-) > > Probably paging from a file which root can't access (see above). No, rather that the normal NFS retries are not in effect (or something like this) when the pagein is requested by the vnode pager (as opposed to a userland program). I have noticed some similar bogosity once with Data General DG/UX, but for write access, and they have never been able to resolve this. (mmap()ed files were only written correctly in 1 out of 10 attempts, and SIGBUS'ed the other 9 processes. Alas, the ELF ld(1) mmap'ed its output file.) -- 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-current Thu Aug 1 11:23:44 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id LAA29718 for current-outgoing; Thu, 1 Aug 1996 11:23:44 -0700 (PDT) Received: from rocky.mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id LAA29702; Thu, 1 Aug 1996 11:23:33 -0700 (PDT) Received: (from nate@localhost) by rocky.mt.sri.com (8.7.5/8.7.3) id MAA07672; Thu, 1 Aug 1996 12:23:18 -0600 (MDT) Date: Thu, 1 Aug 1996 12:23:18 -0600 (MDT) Message-Id: <199608011823.MAA07672@rocky.mt.sri.com> From: Nate Williams To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) Cc: nate@mt.sri.com (Nate Williams), imb@asstdc.com.au, current@freebsd.org, committers@freebsd.org Subject: Re: if_ep.c driver brokeness (was Re: 3Com (589b) troubles) In-Reply-To: <199608011752.TAA19568@uriah.heep.sax.de> References: <199608011739.LAA07374@rocky.mt.sri.com> <199608011752.TAA19568@uriah.heep.sax.de> Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > Actually, this change broke the ep driver for almost every card. If > > The interesting thing is that there are also (few? many?) people where > it actually improved things. It appears to be 'few'. > Anyway, a better fix is certainly needed > (one that satisfies all people, not just a few only), so back it out > and suggest another one. :) I have no way of testing it, so I'm not the one to find it. :) Nate From owner-freebsd-current Thu Aug 1 11:36:23 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id LAA00362 for current-outgoing; Thu, 1 Aug 1996 11:36:23 -0700 (PDT) Received: from walkabout.asstdc.com.au (root@walkabout.asstdc.com.au [202.12.127.73]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id LAA00357 for ; Thu, 1 Aug 1996 11:36:18 -0700 (PDT) Received: (from imb@localhost) by walkabout.asstdc.com.au (8.7.5/BSD4.4) id EAA00216 Fri, 2 Aug 1996 04:35:07 +1000 (EST) From: michael butler Message-Id: <199608011835.EAA00216@walkabout.asstdc.com.au> Subject: Re: if_ep.c driver brokeness (was Re: 3Com (589b) troubles) To: joerg_wunsch@uriah.heep.sax.de Date: Fri, 2 Aug 1996 04:35:06 +1000 (EST) Cc: nate@mt.sri.com, current@freebsd.org In-Reply-To: <199608011752.TAA19568@uriah.heep.sax.de> from J Wunsch at "Aug 1, 96 07:52:51 pm" X-Comment: Phone 0419-240-180, International +61-419-240-180 X-Comment: finger imb@asstdc.com.au for PGP public key 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-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > The interesting thing is that there are also (few? many?) people where > it actually improved things. Anyway, a better fix is certainly needed > (one that satisfies all people, not just a few only), so back it out > and suggest another one. :) What we _really_ need is for people to explain which cards do better with which version .. at least then we might be able to use the appropriate IRQ strategy according to which card is detected. Just having people stick their hand up and say "it's busted" without specifying what broke is unhelpful, michael From owner-freebsd-current Thu Aug 1 11:49:10 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id LAA01111 for current-outgoing; Thu, 1 Aug 1996 11:49:10 -0700 (PDT) Received: from freefall.freebsd.org (localhost.cdrom.com [127.0.0.1]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id LAA01105; Thu, 1 Aug 1996 11:49:08 -0700 (PDT) Message-Id: <199608011849.LAA01105@freefall.freebsd.org> To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) cc: nate@mt.sri.com (Nate Williams), imb@asstdc.com.au, current@freebsd.org, committers@freebsd.org Subject: Re: if_ep.c driver brokeness (was Re: 3Com (589b) troubles) In-reply-to: Your message of "Thu, 01 Aug 1996 19:52:51 +0200." <199608011752.TAA19568@uriah.heep.sax.de> Date: Thu, 01 Aug 1996 11:49:08 -0700 From: "Justin T. Gibbs" Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >As Nate Williams wrote: > >> Actually, this change broke the ep driver for almost every card. If > >The interesting thing is that there are also (few? many?) people where >it actually improved things. Anyway, a better fix is certainly needed >(one that satisfies all people, not just a few only), so back it out >and suggest another one. :) I suggest we find someone to rewrite the driver from scratch. It *really* needs it. I would, but my queue currently looks like: Generic SCSI layer enhancements Advansys device driver Revamp of the Buslogic driver Cleanup of our device configuration code. >-- >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. ;-) -- Justin T. Gibbs =========================================== FreeBSD: Turning PCs into workstations =========================================== From owner-freebsd-current Thu Aug 1 13:21:40 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id NAA08291 for current-outgoing; Thu, 1 Aug 1996 13:21:40 -0700 (PDT) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id NAA08247 for ; Thu, 1 Aug 1996 13:21:36 -0700 (PDT) Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.12/8.6.9) id GAA09015; Fri, 2 Aug 1996 06:20:04 +1000 Date: Fri, 2 Aug 1996 06:20:04 +1000 From: Bruce Evans Message-Id: <199608012020.GAA09015@godzilla.zeta.org.au> To: bde@zeta.org.au, terry@lambert.org Subject: Re: DEVFS broken by last devsw_add_generic()/bdevvp() changes Cc: current@FreeBSD.ORG, peter@spinner.DIALix.COM Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >> Actually, they all "goto done;" and this is correct. dscheck() sets >> the error flag if necessary. There is no error for EOF. >My problem with od and sd are that they silently fail. I don't disagree >that they should be allowed to fail, only that they do so silently. >There seems to be a possible cascade failure for residuals in excess of >the block size from a silent failure... maybe I'm reading things wrong? You probably have the bug back to front. The residual needs to be set if dscheck() returns an error (not if dscheck() returns EOF). sd and od set it correctly but wd doesn't set it at all. Not setting it has bad effects in at least physio() - a wrong b_resid gives a wrong uio_resid. It should probably be set in dscheck(). We no longer use the stupid b_cylin[der] alias for b_resid (it is set but not used) so dscheck() could set b_resid = b_bcount in all cases. Bruce From owner-freebsd-current Thu Aug 1 13:29:41 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id NAA14130 for current-outgoing; Thu, 1 Aug 1996 13:29:41 -0700 (PDT) Received: from mail13.digital.com (mail13.digital.com [192.208.46.30]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id NAA14036 for ; Thu, 1 Aug 1996 13:29:32 -0700 (PDT) Received: from muggsy.lkg.dec.com by mail13.digital.com (8.7.5/UNX 1.2/1.0/WV) id QAA05184; Thu, 1 Aug 1996 16:13:55 -0400 (EDT) Received: from whydos.lkg.dec.com by muggsy.lkg.dec.com (5.65/DEC-Ultrix/4.3) with SMTP id AA00741; Thu, 1 Aug 1996 16:13:50 -0400 Received: from localhost.lkg.dec.com (localhost.lkg.dec.com [127.0.0.1]) by whydos.lkg.dec.com (8.6.12/8.6.12) with SMTP id QAA04574 for ; Thu, 1 Aug 1996 16:19:21 GMT Message-Id: <199608011619.QAA04574@whydos.lkg.dec.com> X-Authentication-Warning: whydos.lkg.dec.com: Host localhost.lkg.dec.com didn't use HELO protocol X-Mailer: exmh version 1.6.5 12/11/95 To: freebsd-current@freebsd.org Subject: TCP (+ Path MTU) bug / FDDI enchancements Mime-Version: 1.0 Content-Type: multipart/mixed ; boundary="===_0_Thu_Aug__1_16:08:29__1996" Date: Thu, 01 Aug 1996 16:19:21 +0000 From: Matt Thomas Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk This is a multipart MIME message. --===_0_Thu_Aug__1_16:08:29__1996 Content-Type: text/plain; charset=us-ascii [I'm sending this to -current rather than -bugs since I though it might be interesting to folks on -current.] I've updated my FDDI drivers to work under 2.2-current. In testing them I found my FDDI performance to be "only" ~50Mb/s. The code added to use sendpipe/recvpipe to fill the TCP sockbuf highwater marks overrides any size specified by the SO_RCVBUF and SO_SNDBUF socket options. This is not good since FDDI requires large windows so that the maximum amount of data can be transferred per token rotation. I've included a fix but I don't think it is the correct fix (nor could I figure out what the correct fix should be). However, the fix does restore the ttcp performance to a reasonable 85Mb/s. BTW, if I reduce the MTU of the FDDI interface to 1500, the performance drops to ~67Mb/s which is almost exactly what I get over 100baseTX. Which means the it is the per packet costs and not the per byte costs that take over at 1500 bytes / packet. I also updated if_ether.c so that it will initialize the mtu of FDDI interface routes to have a maximum MTU of 4352 (instead of the 4470 now used by FreeBSD). I also included a change which toggles the mtu of an ARP route between 1500 and 4352 depending on whether there is an FDDI/Ethernet bridge between the local system and the remote system. This requires changes to mbuf.h (included) and if_fddisubr.c and if_fddi.h (will be provided separately). Even though 2.2 includes some Path MTU support, there are a number of changes needed in ip_output() to support it. ip_output always bases its MTU decisions on the MTU of the interface. This is incorrect when Path MTU has been implemented. In that case you want to use the MTU of the path. This requires using a separate variable for storing the MTU and initializing it appropriately from the interface / route (whichever is less). Note that this has implications for ATM since a classic IP over ATM will use a 9180 (RFC 1577) but if SVCs are used can negotiate an MTU of up to 65535 bytes. Thus is would be best that for a RFC1577 implentation that supports SVCs to use 65535 as the if_mtu and make the ATMARP code initialize the MTU of an interface route to 9180. An alternative to define an IFF_VARMTU flag and test for that in ip_output(). Since the diffs are small, I've attached (gzip'ed) to this message. I'd appreciate if some one could get them into the -current and/or the -stable streams. --===_0_Thu_Aug__1_16:08:29__1996 Content-Type: application/octet-stream Content-Description: 2.2-960612-SNAP-diffs.gz Content-Transfer-Encoding: base64 H4sICCPWADIAAzIuMi1kaWZmcwCVWOtTIkkS/4x/RV5cxBzIs1EUYSHGHXHWW3UMdeZm70tH 2V0NtfZruwuVW92//TKrqh9A6zqE0lD5qHxV5q9ot9sQcinwvyud2BZhvJQdpxMlYl67XSzh eDkHsMCyRvt7I2sPrKOjg51ms1kltSnQHw16WuDjR2j3e4O91iE0zfPjxx2owS7IBYc0cu65 hLul5/GkBS53Es5SrmhBmnYUZ3cH/ik8l3twffvNvrk6u5rttGvCg3odBVPxPw4TSGR7mkg7 CZ46+G+nPHRjEfMGTCbQa+w0f4gfnp/RtPY0jew0dDvpnb0Qj0zCPyZAXhNzGjMHubu78P37 d20jrgoPLa4Vu1QoGSMH2ZIx/USONkygDg51oNRTBUrG7am0A/aU8jkqRF5UsBaQ63cFJOHO w48EZJ2/FJDEedgKCDH/UEDKSjYDMlUBgT932lii6SrtBkjpLLYqs3cw6h2N9vpFZRbMG3xY k9awKEirv986giY9rL4KM1pNghDfy4WbgOezedoC5qcRiBACWy1opzDsWP61C/vnT8c3t7Va 76ln9Xo11EBl0cVQcPHAXWAp+CK8b/v8gftwl0TMdVgqN5Rc5Er6f68kWPpSZEqahZLzs8tf e6QEDVFKSAZ8tuIJpDF3hCcc5VOFnEVy/R+X65Pc/jvkQEVXB9CJYoFePS54SJ9XIpxjcE3Q kbdd7PHpy9Vvp+fHn29q9Qv76tfbX06uny/s2Rd6V5F/NsFrlC17t9SziZp5WubZbxh7VTXI Vcw3sn5rn17PZui7ytUiWvou3HGIQvASzjEQOjntUncVsR0tZXV37R2O9vdHexXdtSS1JjAc 9azRwCqK+eiodQBNfDcNI5XJ0pHagd2AWkZPnbBQwsLHuOMZxFMW4YEznCJuZAxIb0HkeS3g SRIlyIuyTUUK5HJcaKe+zVw3wQEAu24qSyQR2sIjGuwKlikWaX4AxvoIDg7JbGswzOyu1eaR jOCOuSRUe6E34cVog2DtqWCoNSZjamgJLXrYGIVnG7tqgr7GtpQ+Ei29VGxKAqGdf62jydiH cIkMbZEyFYMX4D5Onz+1iYdDZeKw1xoaE7VRTG3PZCRYPcF+lmA/080TVxvjwvBNorZf9V3t xDpD1nqRVnTpGuBr22WgXdbFlylvNs3usGGYPn4fcF6c2p+Pb2f/Of6toWLuqtjUq9LaWFcx Z5I/stXYTCoLg0ITvWX1THDUQdGbiyCi0XD59fycGjlttJYfpOO3ILLzjkaEMQ6xXH6TThHN VFJY3sNnts7KqJJZpaSyqGj9RdtevdUDruNWbathttEuponTSVVhwUQTKIVICJQUkl9R1jCx He5T3fWPirrTR8ONQp6djayQyO5p2W4dnOozorTQgBHqwL4oGBESjggjiQ+9/RFORQuae71+ C2GfMkAFYNu7CZxdHp+cXNvHl7qcCh7c/ezYvjm7rAvWKI7aOEcFzTfMr7S+u6th4zeeCG+F CBHhxyOHBXvgwMIVOAsWOvhR4tj2sYlhW6bxwu58hJMR/LHkS641qBchTEQshD6x0ZlPXsLm AQ9lanCnAVWZJQTjhPeHTW20CcZZ+tItG4skqwHTSQax3iFdltLdY00C0R/yZeWctebZ5Zef v57ejDd6J+Vwz6Jx0NzrH73VXXGCYUn9SwUseixBlICnKZvj6CMJnkcFJ7eKiXZraeP4S2Sj 5Mh6JtHc5lu8hmfNpYubzzdn/51t+qQsVo7t95Vjg37mWFYWZx6kAWWeh9FyvgAPFeLk4YmH sLQFDgvh9yX6RuUPrkCEJf1VZz3PFWb+NNn26Q3ewqfS+gQWMgrTKplGeXbh4H2VF2lrvOky 0NNZReXwQEVleJCnW8SpZLKDDxtdl5RCMxzKUX1Bz7WF9XIBtxVSaMCHv+CQ+qBh2SbpzqB8 h6FxvDKXxaZryMizOZ7DpAoYDUaDg9HeoAIY5UKbt068DJRA/sAicN+kx74KCnW70PGXLt65 tKLOYrq9aLs+rTe31hUarBBJEKfxinUyOE0UYYOk/Qi3ZQzBfmDJa8TM+y0TM7LnuiLbVKNW oDaMN6p69ZjHy2fBeXJezen6mlMDIzWgLKw66yBrLyRJEIGaveurYBWXyqy4aHVcxS5wCj1t 86tlLWAo/CnGs4ucUgS8Ix/wLu6MKRLqOnx6cnJ2dnVx+1UNQWwN9MDmcIO9nRo+UlRjIL6i O6g+h+hpQxzlHhfCWSB4RWCcpjRyQqVGH5OO4ermcKTCWzUkT/HWQDt++KBF8FXfwHw+BloD tG82GmBu3W8IqBlpbuYVpGnhTENDglqVgoKLgpjf12t3CWf3a5PiOMS+qgYsnsRH7LIyWWEg IOE4WVOcDR2KBJXH/lDdSAYIEfsZgMEc60Sz8hWkzhHZswS72SLHzbmjOtONv0s+zk3UIO17 zuOiEMztjhzXVaAnhFmmjKZYEgxHgVzgF/zD1K5XRYtSHRrZElpwWEC/TyVqyjAl1J3RkQzp h6xEuHPeAbiJjKSbRHFee5GuH9UxqOisQa9HT/YQCTefs0yKKNuY6cLN9a47gbAtd4T04xKp NLIohABIoFVoOW0TRgmOSFA/JmAEBKVT/Qq3wgQGWuGjEc5MRRUdvdTNxjlzMGsOlnmnusjf V9wGH2gY2J4G+R3F+JfRyzWxXuGz219m16RP81UXeMZk8Ly+4L2iclKw57tXKt046Pq6UNmD Xre+OJ9vmb99PunXiXw16z4v9P5SZsmqRF/K1q+BE/iLLoLXs3/PPt2qc+fjQfSZzdJ7BHkK V5jDaAiLyHcpJP8HQAqNMTYWAAA= --===_0_Thu_Aug__1_16:08:29__1996 Content-Type: text/plain; charset=us-ascii Matt Thomas Internet: matt@3am-software.com 3am Software Foundry WWW URL: http://www.3am-software.com/bio/matt.html Westford, MA Disclaimer: I disavow all knowledge of this message --===_0_Thu_Aug__1_16:08:29__1996-- From owner-freebsd-current Thu Aug 1 13:56:49 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id NAA28341 for current-outgoing; Thu, 1 Aug 1996 13:56:49 -0700 (PDT) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id NAA28333 for ; Thu, 1 Aug 1996 13:56:45 -0700 (PDT) Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.12/8.6.9) id GAA10007; Fri, 2 Aug 1996 06:52:06 +1000 Date: Fri, 2 Aug 1996 06:52:06 +1000 From: Bruce Evans Message-Id: <199608012052.GAA10007@godzilla.zeta.org.au> To: freebsd-current@FreeBSD.org, j@uriah.heep.sax.de Subject: Re: `const char rcsid[]' vs -traditional Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk >> >What does the C standard say about #ident? >> #ident is a syntax error. >What about ``#pragma ident''? It is implementation-defined, and old implementations of gcc define it as exec'ing /usr/games/hack ... :-). This was to make the point that #pragma is useless. Bruce From owner-freebsd-current Thu Aug 1 15:02:57 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id PAA02367 for current-outgoing; Thu, 1 Aug 1996 15:02:57 -0700 (PDT) Received: from whistle.com (s205m131.whistle.com [207.76.205.131]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id PAA02362 for ; Thu, 1 Aug 1996 15:02:55 -0700 (PDT) Received: (from smap@localhost) by whistle.com (8.7.5/8.6.12) id PAA29337; Thu, 1 Aug 1996 15:02:25 -0700 (PDT) Received: from bubba.whistle.com(207.76.205.7) by whistle.com via smap (V1.3) id sma029333; Thu Aug 1 15:02:23 1996 Received: (from archie@localhost) by bubba.whistle.com (8.6.12/8.6.12) id PAA03676; Thu, 1 Aug 1996 15:02:23 -0700 From: Archie Cobbs Message-Id: <199608012202.PAA03676@bubba.whistle.com> Subject: Re: Just a note that libkvm/ps/etc need to be recompiled To: joerg_wunsch@uriah.heep.sax.de Date: Thu, 1 Aug 1996 15:02:23 -0700 (PDT) Cc: freebsd-current@FreeBSD.org In-Reply-To: <199608011747.TAA19423@uriah.heep.sax.de> from "J Wunsch" at Aug 1, 96 07:47:31 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk > > There doesn't seem to be a good reason for using the kvm interface > > instead of procfs. Unfortunately, to commit to that, procfs would > > have to become mandatory, since a shared interface would be hard. > > procfs is already semi-mandatory. ps(1) will omit certain information > if procfs is not mounted (like the start time). IMHO, making procfs mandatory would be a good thing. -Archie ___________________________________________________________________________ Archie L. Cobbs, archie@whistle.com * Whistle Communications Corporation From owner-freebsd-current Thu Aug 1 17:28:02 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id RAA07767 for current-outgoing; Thu, 1 Aug 1996 17:28:02 -0700 (PDT) Received: from prozac.neuron.net (prozac.neuron.net [165.254.1.213]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id RAA07746 for ; Thu, 1 Aug 1996 17:27:58 -0700 (PDT) Received: (from amir@localhost) by prozac.neuron.net (8.7.5/8.6.12) id UAA07308; Thu, 1 Aug 1996 20:37:29 -0400 (EDT) From: "Amir Y. Rosenblatt" Message-Id: <199608020037.UAA07308@prozac.neuron.net> Subject: Re: if_ep.c driver brokeness (was Re: 3Com (589b) troubles) To: imb@asstdc.com.au (michael butler) Date: Thu, 1 Aug 1996 20:37:29 -0400 (EDT) Cc: joerg_wunsch@uriah.heep.sax.de, nate@mt.sri.com, current@FreeBSD.ORG In-Reply-To: <199608011835.EAA00216@walkabout.asstdc.com.au> from "michael butler" at Aug 2, 96 04:35:06 am X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > The interesting thing is that there are also (few? many?) people where > > it actually improved things. Anyway, a better fix is certainly needed > > (one that satisfies all people, not just a few only), so back it out > > and suggest another one. :) > > What we _really_ need is for people to explain which cards do better with > which version .. at least then we might be able to use the appropriate IRQ > strategy according to which card is detected. Just having people stick their > hand up and say "it's busted" without specifying what broke is unhelpful, OK -- I have a 3c509B-TP. When the change was added, it began being very problematic. basically after a fairly small amount of data passes over it (like a single small web page or opening a mailbox index) it would stop passing data and start dishing out "no buffer space" messages. I would have posted earlier but the problem had already been mentioned. -Amir From owner-freebsd-current Thu Aug 1 17:32:46 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id RAA07892 for current-outgoing; Thu, 1 Aug 1996 17:32:46 -0700 (PDT) Received: from research.gate.nec.co.jp (research.gate.nec.co.jp [202.32.8.49]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id RAA07887; Thu, 1 Aug 1996 17:32:42 -0700 (PDT) Received: from sbl-gw.sbl.cl.nec.co.jp by research.gate.nec.co.jp (8.7.5+2.6Wbeta6/950912) with ESMTP id JAA05494; Fri, 2 Aug 1996 09:32:26 +0900 (JST) Received: from sirius.sbl.cl.nec.co.jp by sbl-gw.sbl.cl.nec.co.jp (8.7.5+2.6Wbeta6/3.3W6) with ESMTP id JAA24279; Fri, 2 Aug 1996 09:32:24 +0900 (JST) X-Authentication-Warning: sbl-gw.sbl.cl.nec.co.jp: Host nao@sirius [133.207.68.90] claimed to be sirius.sbl.cl.nec.co.jp Received: by sirius.sbl.cl.nec.co.jp (8.7.5+2.6Wbeta6/3.3W6) with UUCP id JAA05631; Fri, 2 Aug 1996 09:32:24 +0900 (JST) Date: Fri, 2 Aug 1996 09:32:24 +0900 (JST) From: Naoki Hamada Message-Id: <199608020032.JAA05631@sirius.sbl.cl.nec.co.jp> References: <199608011849.LAA01105@freefall.freebsd.org> To: gibbs@freefall.freebsd.org CC: joerg_wunsch@uriah.heep.sax.de, nate@mt.sri.com, imb@asstdc.com.au, current@freebsd.org, committers@freebsd.org In-reply-to: "Justin T. Gibbs"'s message of "Thu, 01 Aug 1996 11:49:08 -0700" <199608011849.LAA01105@freefall.freebsd.org> Subject: Re: if_ep.c driver brokeness (was Re: 3Com (589b) troubles) Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >I suggest we find someone to rewrite the driver from scratch. It *really* >needs it. I would, but my queue currently looks like: I can do that. BTW, the current problem with the ep driver seems to be based on some confusion. It was an ad hoc fix for some 3C590 adapters, so it was not the ep driver but the vx driver that should be patched. -nao From owner-freebsd-current Thu Aug 1 18:42:37 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id SAA10815 for current-outgoing; Thu, 1 Aug 1996 18:42:37 -0700 (PDT) Received: from genesis.atrad.adelaide.edu.au (genesis.atrad.adelaide.edu.au [129.127.96.120]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id SAA10807 for ; Thu, 1 Aug 1996 18:42:30 -0700 (PDT) Received: from msmith@localhost by genesis.atrad.adelaide.edu.au (8.6.12/8.6.9) id LAA27739; Fri, 2 Aug 1996 11:21:44 +0930 From: Michael Smith Message-Id: <199608020151.LAA27739@genesis.atrad.adelaide.edu.au> Subject: Re: Termcap problems To: dev@fgate.flevel.co.uk (Developer) Date: Fri, 2 Aug 1996 11:21:43 +0930 (CST) Cc: freebsd-current@freebsd.org In-Reply-To: from "Developer" at Jul 22, 96 09:47:43 am MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Developer stands accused of saying: > > > I`m having a little problem with the termcap. If the xwindow width is > particular sizes (Not sure which ones, but always larger than 80 char) > then commands (like ls) think the window width is different (wider) than > it actually is, and so the formatting really messes up. > > Any ideas would be great. stty -tabs > Regards, > > Trefor S. > > > -- ]] Mike Smith, Software Engineer msmith@atrad.adelaide.edu.au [[ ]] Genesis Software genesis@atrad.adelaide.edu.au [[ ]] High-speed data acquisition and (GSM mobile) 0411-222-496 [[ ]] realtime instrument control (ph/fax) +61-8-267-3039 [[ ]] Collector of old Unix hardware. "Where are your PEZ?" The Tick [[ From owner-freebsd-current Thu Aug 1 18:53:05 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id SAA11279 for current-outgoing; Thu, 1 Aug 1996 18:53:05 -0700 (PDT) Received: from genesis.atrad.adelaide.edu.au (genesis.atrad.adelaide.edu.au [129.127.96.120]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id SAA11266 for ; Thu, 1 Aug 1996 18:53:02 -0700 (PDT) Received: from msmith@localhost by genesis.atrad.adelaide.edu.au (8.6.12/8.6.9) id LAA27767; Fri, 2 Aug 1996 11:31:59 +0930 From: Michael Smith Message-Id: <199608020201.LAA27767@genesis.atrad.adelaide.edu.au> Subject: Re: 2.2 SNAP soon? To: jkh@time.cdrom.com (Jordan K. Hubbard) Date: Fri, 2 Aug 1996 11:31:58 +0930 (CST) Cc: current@freebsd.org In-Reply-To: <2757.838090989@time.cdrom.com> from "Jordan K. Hubbard" at Jul 22, 96 08:03:09 pm MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Jordan K. Hubbard stands accused of saying: > > Now that 2.1.5 is off my plate, I can focus my attentions on 2.2 again > and am wondering if we're about due for another SNAP. If we're going > to switch compilers anytime soon, I'd also like that to happen before > the SNAP since this is going to be another CD version (the last was on > May 1st, 1996) - shall we shoot for August 1st, thereabouts? Anybody > got any burning issues they'd like to deal with before I do this? I'd like the 'de' driver fixed if if hasn't been in the last two weeks; while onsite in sweden I tried cutting a new -current kernel to replace the kernel on one of the radar controller systems that was basically being ground into the mud by the scientists, and discovered that the 'de' driver was not working with the SMC cards we have. It was a relatively simple process to retrofit an earlier version, but I'm not sure if this problem received any general airplay as I've been a little, er, busy 8( Incidentally this system is still being pounded _very_ hard and is still dying, albeit a little less rapidly; if anyone can fill me in on what's happened in -current land in the last few weeks (offline might be best), I'd like to try anything that might improve the life of the system. > Jordan -- ]] Mike Smith, Software Engineer msmith@atrad.adelaide.edu.au [[ ]] Genesis Software genesis@atrad.adelaide.edu.au [[ ]] High-speed data acquisition and (GSM mobile) 0411-222-496 [[ ]] realtime instrument control (ph/fax) +61-8-267-3039 [[ ]] Collector of old Unix hardware. "Where are your PEZ?" The Tick [[ From owner-freebsd-current Thu Aug 1 21:18:15 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id VAA17696 for current-outgoing; Thu, 1 Aug 1996 21:18:15 -0700 (PDT) Received: from genesis.atrad.adelaide.edu.au (genesis.atrad.adelaide.edu.au [129.127.96.120]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id VAA17691 for ; Thu, 1 Aug 1996 21:18:10 -0700 (PDT) Received: from msmith@localhost by genesis.atrad.adelaide.edu.au (8.6.12/8.6.9) id NAA28503; Fri, 2 Aug 1996 13:57:30 +0930 From: Michael Smith Message-Id: <199608020427.NAA28503@genesis.atrad.adelaide.edu.au> Subject: Re: Termcap problems To: joerg_wunsch@uriah.heep.sax.de Date: Fri, 2 Aug 1996 13:57:30 +0930 (CST) Cc: freebsd-current@FreeBSD.org, dev@fgate.flevel.co.uk In-Reply-To: <199607222015.WAA05286@uriah.heep.sax.de> from "J Wunsch" at Jul 22, 96 10:15:08 pm MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk J Wunsch stands accused of saying: > > > I`m having a little problem with the termcap. If the xwindow width is > > particular sizes (Not sure which ones, but always larger than 80 char) > > then commands (like ls) think the window width is different (wider) than > > it actually is, and so the formatting really messes up. > > What makes you think they thought of a different size? > > Programs like ls usually get the window geometry out of the struct > winsize. The problem appears to be tab-related, and probably xterm's fault at that. Once I found that 'stty -tabs' made the problem disappear, I stopped being interested in the cause. I suspect it would be a good one for someone who wants to learn about the tty subsystem to pursue 8) > cheers, J"org -- ]] Mike Smith, Software Engineer msmith@atrad.adelaide.edu.au [[ ]] Genesis Software genesis@atrad.adelaide.edu.au [[ ]] High-speed data acquisition and (GSM mobile) 0411-222-496 [[ ]] realtime instrument control (ph/fax) +61-8-267-3039 [[ ]] Collector of old Unix hardware. "Where are your PEZ?" The Tick [[ From owner-freebsd-current Thu Aug 1 21:26:25 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id VAA18043 for current-outgoing; Thu, 1 Aug 1996 21:26:25 -0700 (PDT) Received: from time.cdrom.com (time.cdrom.com [204.216.27.226]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id VAA18033 for ; Thu, 1 Aug 1996 21:26:23 -0700 (PDT) Received: from time.cdrom.com (localhost [127.0.0.1]) by time.cdrom.com (8.7.5/8.6.9) with ESMTP id VAA10699 for ; Thu, 1 Aug 1996 21:26:00 -0700 (PDT) To: current@freebsd.org Subject: 2.2-960801-SNAP is released Date: Thu, 01 Aug 1996 21:25:59 -0700 Message-ID: <10694.838959959@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk ftp://ftp.freebsd.org/pub/FreeBSD/2.2-960801-SNAP/ See ftp://ftp.freebsd.org/pub/FreeBSD/2.2-960801-SNAP/RELNOTES.TXT for the usual details. Jordan From owner-freebsd-current Thu Aug 1 22:11:46 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id WAA19915 for current-outgoing; Thu, 1 Aug 1996 22:11:46 -0700 (PDT) Received: from root.com (implode.root.com [198.145.90.17]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id WAA19910 for ; Thu, 1 Aug 1996 22:11:40 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by root.com (8.7.5/8.6.5) with SMTP id WAA10069; Thu, 1 Aug 1996 22:11:08 -0700 (PDT) Message-Id: <199608020511.WAA10069@root.com> X-Authentication-Warning: implode.root.com: Host localhost [127.0.0.1] didn't use HELO protocol To: Michael Smith cc: jkh@time.cdrom.com (Jordan K. Hubbard), current@freebsd.org Subject: Re: 2.2 SNAP soon? In-reply-to: Your message of "Fri, 02 Aug 1996 11:31:58 +0930." <199608020201.LAA27767@genesis.atrad.adelaide.edu.au> From: David Greenman Reply-To: dg@root.com Date: Thu, 01 Aug 1996 22:11:08 -0700 Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >Jordan K. Hubbard stands accused of saying: >> >> Now that 2.1.5 is off my plate, I can focus my attentions on 2.2 again >> and am wondering if we're about due for another SNAP. If we're going >> to switch compilers anytime soon, I'd also like that to happen before >> the SNAP since this is going to be another CD version (the last was on >> May 1st, 1996) - shall we shoot for August 1st, thereabouts? Anybody >> got any burning issues they'd like to deal with before I do this? > >I'd like the 'de' driver fixed if if hasn't been in the last two weeks; It hasn't yet been fixed. It's still in my inbox. -DG David Greenman Core-team/Principal Architect, The FreeBSD Project From owner-freebsd-current Thu Aug 1 22:54:00 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id WAA21489 for current-outgoing; Thu, 1 Aug 1996 22:54:00 -0700 (PDT) Received: from time.cdrom.com (time.cdrom.com [204.216.27.226]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id WAA21484 for ; Thu, 1 Aug 1996 22:53:58 -0700 (PDT) Received: from time.cdrom.com (localhost [127.0.0.1]) by time.cdrom.com (8.7.5/8.6.9) with ESMTP id WAA11244; Thu, 1 Aug 1996 22:53:11 -0700 (PDT) To: Doug Rabson cc: Tony Jago , freebsd-current@FreeBSD.ORG Subject: Re: NFS Diskless Dispare... In-reply-to: Your message of "Thu, 01 Aug 1996 11:54:03 BST." Date: Thu, 01 Aug 1996 22:53:10 -0700 Message-ID: <11241.838965190@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > Ouch! This would be pretty hard to reproduce here since I only have one > system which runs -current and most of the time that machine is in Win95 > :-(. Try compiling mountd with DEBUG_FLAGS=-g, then attaching gdb to it > with 'attach pid'. If it doesn't fault, set a breakpoint in _exit. Yeah, I'm a little tied up in CD/release engineering at the moment and haven't had the time to chase up the NFS stuff, but once that's off my plate.. > I think for diskless root filesystems, you must export the fs with > -root=0, otherwise lots of stuff will break. Tony, you had things set up this way already, right? Jordan From owner-freebsd-current Thu Aug 1 23:35:50 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id XAA22855 for current-outgoing; Thu, 1 Aug 1996 23:35:50 -0700 (PDT) Received: from ice.fit.qut.edu.au (tony@ice.fit.qut.edu.au [131.181.2.9]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id XAA22850; Thu, 1 Aug 1996 23:35:46 -0700 (PDT) Received: (from tony@localhost) by ice.fit.qut.edu.au (8.7.5/8.7.3) id QAA03514; Fri, 2 Aug 1996 16:36:35 +1000 (EST) Date: Fri, 2 Aug 1996 16:36:33 +1000 (EST) From: Tony Jago To: "Jordan K. Hubbard" cc: Doug Rabson , freebsd-current@FreeBSD.ORG Subject: Re: NFS Diskless Dispare... In-Reply-To: <11241.838965190@time.cdrom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Sender: T.Jago@fit.qut.edu.au Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Thu, 1 Aug 1996, Jordan K. Hubbard wrote: > Date: Thu, 01 Aug 1996 22:53:10 -0700 > From: "Jordan K. Hubbard" > To: Doug Rabson > Cc: Tony Jago , freebsd-current@FreeBSD.ORG > Subject: Re: NFS Diskless Dispare... > > > Ouch! This would be pretty hard to reproduce here since I only have one > > system which runs -current and most of the time that machine is in Win95 > > :-(. Try compiling mountd with DEBUG_FLAGS=-g, then attaching gdb to it > > with 'attach pid'. If it doesn't fault, set a breakpoint in _exit. > > Yeah, I'm a little tied up in CD/release engineering at the moment > and haven't had the time to chase up the NFS stuff, but once that's > off my plate.. > > > I think for diskless root filesystems, you must export the fs with > > -root=0, otherwise lots of stuff will break. > > Tony, you had things set up this way already, right? > > Jordan > Yes. I have -maproot=0:0 --- Tony Jago, System Administrator, E-Mail: T.Jago@fit.qut.edu.au Faculty of Information Technology, Web: http://www.fit.qut.edu.au/staff/~tony Queensland University of Technology. Box 2434, Brisbane 4001, AUSTRALIA. "We need more horsepower!" Phone: +61 7 3864-2573 Fax: +61 7 3864-1959 From owner-freebsd-current Fri Aug 2 01:31:11 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id BAA26872 for current-outgoing; Fri, 2 Aug 1996 01:31:11 -0700 (PDT) Received: from fgate.flevel.co.uk (root@fgate.flevel.co.uk [194.6.101.2]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id BAA26863 for ; Fri, 2 Aug 1996 01:31:06 -0700 (PDT) Received: from localhost (dev@localhost) by fgate.flevel.co.uk (8.7.5/8.6.9) with SMTP id JAA19219; Fri, 2 Aug 1996 09:27:30 +0100 (BST) Date: Fri, 2 Aug 1996 09:27:29 +0100 (BST) From: Developer To: Michael Smith cc: joerg_wunsch@uriah.heep.sax.de, freebsd-current@FreeBSD.org Subject: Re: Termcap problems In-Reply-To: <199608020427.NAA28503@genesis.atrad.adelaide.edu.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk On Fri, 2 Aug 1996, Michael Smith wrote: > > Programs like ls usually get the window geometry out of the struct > > winsize. > > The problem appears to be tab-related, and probably xterm's fault at that. > Once I found that 'stty -tabs' made the problem disappear, I stopped being > interested in the cause. I suspect it would be a good one for someone > who wants to learn about the tty subsystem to pursue 8) Thanks very much - it work fine after setting that option:) Regards, Trefor S. From owner-freebsd-current Fri Aug 2 02:36:49 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id CAA29613 for current-outgoing; Fri, 2 Aug 1996 02:36:49 -0700 (PDT) Received: from minnow.render.com (render.demon.co.uk [158.152.30.118]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id CAA29608 for ; Fri, 2 Aug 1996 02:36:43 -0700 (PDT) Received: from minnow.render.com (minnow.render.com [193.195.178.1]) by minnow.render.com (8.6.12/8.6.9) with SMTP id KAA25179; Fri, 2 Aug 1996 10:33:26 +0100 Date: Fri, 2 Aug 1996 10:33:24 +0100 (BST) From: Doug Rabson To: Terry Lambert cc: jkh@time.cdrom.com, tony@fit.qut.edu.au, freebsd-current@FreeBSD.ORG Subject: Re: NFS Diskless Dispare... In-Reply-To: <199608011802.LAA04239@phaeton.artisoft.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Thu, 1 Aug 1996, Terry Lambert wrote: > Mountd is far from being concurrent enough. At one time, back in > the 1.1.5.1 days, I had it hacked up sufficiently to allow NFS > access by 20 or so X terminals, all at the same time. I think > this is kludgable by hacking the timeout up for now. Mountd wants > a bit of a rewrite once real threading is generally available. Wouldn't that need to wait until a threaded rpc library was available... > > > > > I think that this is a more generic NFS bug in -current. I can > > > reproduce this, even causing mountd to silently exit (no core, no > > > syslog msg) with just one client and some fierce AMD-assisted pounding > > > on a 2.2-current NFS server. > > I think the exit is a seperate problem. I'd be curious about what > you could find out from a trace of the process started before it dies. > > > > > 2. Files permissions are read incorrectly. Files that should be able to > > > > be executed are giving "permission denied" messages.. Sometimes even > > > > the kernel can't be loaded by netboot.com but if you persist by > > > > typing "autoboot" it will magically start to work. Machines fail to > > > > boot correctly as programms called in /etc/rc don't start > > > > (permission denied). > > > > > > Probably more NFS bogosity. > > [ ... ] > > > I think for diskless root filesystems, you must export the fs with > > -root=0, otherwise lots of stuff will break. > > [ this is true, but it's not the cause ] > > > > > 3. Pageing in of binaries cause the system to panic. Vnode_pager does > > > > not seem to like it when it can't page in executables, even when the > > > > > > See #2. :-) > > > > Probably paging from a file which root can't access (see above). > > Actually, I think it's the problem in vop_bmap for nfs that David noted > the other day. Which problem is this? I have always been slightly worried about the hacky nature of the nfs_bmap code (basically just multiplies b_lblkno by 16 or so, depending on the fs blocksize). The higher level fs code seems to try to figure out whether to call VOP_BMAP by comparing b_blkno to b_lblkno and mapping if they are equal. For NFS, they will always be equal for the first block of the file. I didn't think it would be a problem since it would just call nfs_bmap a bit more often for that block. > > > > 2.1.5? Its NFS is still unstable, but I don't believe anywhere near > > > the state it's in with -current. > > > > I think some of the stability problems with NFS are due to its lack of > > vnode locking primitives. This might be addressed by the lite2 fs work > > but if not, I will try to get something in after that work is merged. > > The NFS, procfs, and several other non-boot-critical FS's didn't have > the new primitives in the patch sets we've seen so far. I don't think > they will have much positive effect on this problem, but there are three > or four other problems that will clear up (mostly two client race > conditions). I think the worst races would be between VOP_READ or VOP_WRITE and vclean. I think that you could cause real damage with one of those :-). -- Doug Rabson, Microsoft RenderMorphics Ltd. Mail: dfr@render.com Phone: +44 171 251 4411 FAX: +44 171 251 0939 From owner-freebsd-current Fri Aug 2 02:41:48 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id CAA29861 for current-outgoing; Fri, 2 Aug 1996 02:41:48 -0700 (PDT) Received: from minnow.render.com (render.demon.co.uk [158.152.30.118]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id CAA29841 for ; Fri, 2 Aug 1996 02:41:43 -0700 (PDT) Received: from minnow.render.com (minnow.render.com [193.195.178.1]) by minnow.render.com (8.6.12/8.6.9) with SMTP id KAA25196; Fri, 2 Aug 1996 10:40:20 +0100 Date: Fri, 2 Aug 1996 10:40:19 +0100 (BST) From: Doug Rabson To: Tony Jago cc: "Jordan K. Hubbard" , freebsd-current@freebsd.org Subject: Re: NFS Diskless Dispare... In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Fri, 2 Aug 1996, Tony Jago wrote: > > On Thu, 1 Aug 1996, Jordan K. Hubbard wrote: > > > Date: Thu, 01 Aug 1996 22:53:10 -0700 > > From: "Jordan K. Hubbard" > > To: Doug Rabson > > Cc: Tony Jago , freebsd-current@FreeBSD.ORG > > Subject: Re: NFS Diskless Dispare... > > > > > Ouch! This would be pretty hard to reproduce here since I only have one > > > system which runs -current and most of the time that machine is in Win95 > > > :-(. Try compiling mountd with DEBUG_FLAGS=-g, then attaching gdb to it > > > with 'attach pid'. If it doesn't fault, set a breakpoint in _exit. > > > > Yeah, I'm a little tied up in CD/release engineering at the moment > > and haven't had the time to chase up the NFS stuff, but once that's > > off my plate.. > > > > > I think for diskless root filesystems, you must export the fs with > > > -root=0, otherwise lots of stuff will break. > > > > Tony, you had things set up this way already, right? > > > > Jordan > > > > Yes. I have -maproot=0:0 Exactly which files have permission problems? Try creating a file (as root) on those filesystems and make sure that the new file is owned by root and not nobody. If I could see some kind of log of the system booting, I might be able to see more of what is happening. Is that possible? -- Doug Rabson, Microsoft RenderMorphics Ltd. Mail: dfr@render.com Phone: +44 171 251 4411 FAX: +44 171 251 0939 From owner-freebsd-current Fri Aug 2 04:26:12 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id EAA03289 for current-outgoing; Fri, 2 Aug 1996 04:26:12 -0700 (PDT) Received: from tatooine.vader.org (tatooine.vader.org [194.159.100.200]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id EAA03284 for ; Fri, 2 Aug 1996 04:26:09 -0700 (PDT) Received: (from chris@localhost) by tatooine.vader.org (8.7.5/8.7.3) id MAA11221 for freebsd-current@freebsd.org; Fri, 2 Aug 1996 12:26:07 +0100 (BST) From: Chris Dabrowski Message-Id: <199608021126.MAA11221@tatooine.vader.org> Subject: Sup failing for sup.freebsd.org To: freebsd-current@freebsd.org Date: Fri, 2 Aug 1996 12:26:07 +0100 (BST) Reply-To: chris@vader.org 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-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Is anyone else experiencing problems with sup? For the last couple of days I haven't been able to keep up with -CURRENT: root@tatooine.vader.org:/home/chris $ /usr/sbin/sup -v /usr/local/etc/sup/standard-supfile SUP 9.26 (4.3 BSD) for file /usr/local/etc/sup/standard-supfile at Aug 2 11:22:09 SUP: Can't connect to server for supfilesrv: Operation timed out SUP: Will retry in 86 seconds SUP: Can't connect to server for supfilesrv: Operation timed out SUP: Will retry in 49 seconds SUP: Can't connect to server for supfilesrv: Operation timed out SUP: Will retry in 73 seconds SUP: Can't connect to server for supfilesrv: Operation timed out SUP: Will retry in 188 seconds SUP: Can't connect to server for supfilesrv: Operation timed out SUP: Will retry in 416 seconds I can ping and traceroute to sup.freebsd.org fine: root@tatooine.vader.org:/home/chris $ traceroute sup.freebsd.org traceroute to freefall.FreeBSD.org (204.216.27.4), 30 hops max, 40 byte packets 1 demon.router.vader.org (194.159.100.254) 2.823 ms 2.733 ms 2.733 ms 2 core-a.router.demon.net (194.159.252.252) 4.642 ms 4.279 ms 4.403 ms 3 204.6.105.1 (204.6.105.1) 103.513 ms 227.925 ms 105.448 ms 4 t16.sc.psi.net (38.1.3.26) 180.380 ms 181.223 ms 183.667 ms 5 t16.sc.psi.net (38.1.3.26) 179.590 ms 189.985 ms 231.581 ms 6 T3-CRL-SFO-01-H3/0.US.CRL.NET (149.20.64.19) 180.957 ms 180.517 ms 180.527 ms 7 E0-CRL-SFO-02-E0/0.US.CRL.NET (165.113.55.2) 190.164 ms 183.831 ms 178.344 ms 8 T1-CDROM-00-EX.US.CRL.NET (165.113.118.2) 198.548 ms 298.326 ms 193.358 ms 9 freefall.FreeBSD.ORG (204.216.27.4) 186.624 ms 189.401 ms 186.834 ms The connection never gets beyond SYS_SENT: chris@tatooine.vader.org:/home/chris $ netstat Active Internet connections Proto Recv-Q Send-Q Local Address Foreign Address (state) tcp 0 0 tatooine.ndm-server freefall.FreeBSD.supfi SYN_SENT This is the supfile I am using: root@tatooine.vader.org:/home/chris $ cat /usr/local/etc/sup/standard-supfile src-base release=current host=sup.FreeBSD.org hostbase=/home base=/usr prefix=/usr/src delete old use-rel-suffix src-bin release=current host=sup.FreeBSD.org hostbase=/home base=/usr prefix=/usr/src delete old use-rel-suffix src-contrib release=current host=sup.FreeBSD.org hostbase=/home base=/usr prefix=/usr/src delete old use-rel-suffix [...snip...] Many thanks, Chris -- Chris Dabrowski chris@vader.org From owner-freebsd-current Fri Aug 2 07:18:46 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id HAA09228 for current-outgoing; Fri, 2 Aug 1996 07:18:46 -0700 (PDT) Received: from luke.pmr.com (luke.pmr.com [206.224.65.132]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id HAA09221 for ; Fri, 2 Aug 1996 07:18:44 -0700 (PDT) Received: (from bob@localhost) by luke.pmr.com (8.7.5/8.6.9) id JAA12202; Fri, 2 Aug 1996 09:18:20 -0500 (CDT) From: Bob Willcox Message-Id: <199608021418.JAA12202@luke.pmr.com> Subject: Re: Sup failing for sup.freebsd.org To: chris@vader.org Date: Fri, 2 Aug 1996 09:18:19 -0500 (CDT) Cc: freebsd-current@freebsd.org In-Reply-To: <199608021126.MAA11221@tatooine.vader.org> from Chris Dabrowski at "Aug 2, 96 12:26:07 pm" X-Mailer: ELM [version 2.4ME+ PL11 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Chris Dabrowski wrote: > Is anyone else experiencing problems with sup? For the last couple of > days I haven't been able to keep up with -CURRENT: I am seeing the same problem. [ ... further on problem info deleted .. ] -- Bob Willcox politics, n: bob@luke.pmr.com A strife of interests masquerading as a contest of Austin, TX principles. The conduct of public affairs for private advantage. -- Ambrose Bierce From owner-freebsd-current Fri Aug 2 07:46:10 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id HAA11198 for current-outgoing; Fri, 2 Aug 1996 07:46:10 -0700 (PDT) Received: from Campino.Informatik.RWTH-Aachen.DE (campino.Informatik.RWTH-Aachen.DE [137.226.225.2]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id HAA11186 for ; Fri, 2 Aug 1996 07:46:02 -0700 (PDT) Received: from gilberto.physik.rwth-aachen.de (gilberto.physik.rwth-aachen.de [137.226.31.2]) by Campino.Informatik.RWTH-Aachen.DE (RBI-Z-5/8.6.12) with ESMTP id QAA05282; Fri, 2 Aug 1996 16:41:20 +0200 Received: (from kuku@localhost) by gilberto.physik.rwth-aachen.de (8.6.11/8.6.9) id QAA25943; Fri, 2 Aug 1996 16:54:40 +0200 From: "Christoph P. Kukulies" Message-Id: <199608021454.QAA25943@gilberto.physik.rwth-aachen.de> Subject: Re: Sup failing for sup.freebsd.org To: chris@vader.org Date: Fri, 2 Aug 1996 16:54:39 +0200 (MET DST) Cc: freebsd-current@freebsd.org In-Reply-To: <199608021126.MAA11221@tatooine.vader.org> from Chris Dabrowski at "Aug 2, 96 12:26:07 pm" Reply-To: Christoph Kukulies X-Mailer: ELM [version 2.4ME+ PL16 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > Is anyone else experiencing problems with sup? For the last couple of > days I haven't been able to keep up with -CURRENT: [...] I see this here too. My last working sup was Jul 30th. At the moment my sup logs show these timeouts, too. > SUP: Can't connect to server for supfilesrv: Operation timed out > SUP: Will retry in 416 seconds > > I can ping and traceroute to sup.freebsd.org fine: [...] > Many thanks, > > Chris > -- > Chris Dabrowski > chris@vader.org > --Chris Christoph P. U. Kukulies kuku@gil.physik.rwth-aachen.de From owner-freebsd-current Fri Aug 2 09:17:45 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id JAA14871 for current-outgoing; Fri, 2 Aug 1996 09:17:45 -0700 (PDT) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id JAA14866 for ; Fri, 2 Aug 1996 09:17:43 -0700 (PDT) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id JAA05802; Fri, 2 Aug 1996 09:15:22 -0700 From: Terry Lambert Message-Id: <199608021615.JAA05802@phaeton.artisoft.com> Subject: Re: NFS Diskless Dispare... To: dfr@render.com (Doug Rabson) Date: Fri, 2 Aug 1996 09:15:21 -0700 (MST) Cc: terry@lambert.org, jkh@time.cdrom.com, tony@fit.qut.edu.au, freebsd-current@FreeBSD.ORG In-Reply-To: from "Doug Rabson" at Aug 2, 96 10:33:24 am X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > Mountd is far from being concurrent enough. At one time, back in > > the 1.1.5.1 days, I had it hacked up sufficiently to allow NFS > > access by 20 or so X terminals, all at the same time. I think > > this is kludgable by hacking the timeout up for now. Mountd wants > > a bit of a rewrite once real threading is generally available. > > Wouldn't that need to wait until a threaded rpc library was available... Not really; it could be done with non-blocking I/O and an automaton with a context record per connection. > > Actually, I think it's the problem in vop_bmap for nfs that David noted > > the other day. > > Which problem is this? I have always been slightly worried about the > hacky nature of the nfs_bmap code (basically just multiplies b_lblkno by > 16 or so, depending on the fs blocksize). The higher level fs code seems > to try to figure out whether to call VOP_BMAP by comparing b_blkno to > b_lblkno and mapping if they are equal. For NFS, they will always be > equal for the first block of the file. I didn't think it would be a > problem since it would just call nfs_bmap a bit more often for that block. I think the bmap code can fail in some cases because of the recent vm changes; I can't rememebr for sure. It was an answer to one of the questions about NFS in -current... it was in the remote boot discussion about paging from an NFS mounted init. Sorry, I didn't save it; I thought the suggested fix was going to go in immediately because of who posted it. > > > I think some of the stability problems with NFS are due to its lack of > > > vnode locking primitives. This might be addressed by the lite2 fs work > > > but if not, I will try to get something in after that work is merged. > > > > The NFS, procfs, and several other non-boot-critical FS's didn't have > > the new primitives in the patch sets we've seen so far. I don't think > > they will have much positive effect on this problem, but there are three > > or four other problems that will clear up (mostly two client race > > conditions). > > I think the worst races would be between VOP_READ or VOP_WRITE and vclean. > I think that you could cause real damage with one of those :-). I had a vclean patch to deal with the "free vnode isn't" error a long time ago... it was a serious kludge, IMO, since it fixed the symptom instead of the problem (which is that vclean is a bad idea). I think the patch would also save us from the race conditions as well. Are you maybe thinking of client side nfsnodes? Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-current Fri Aug 2 10:06:36 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id KAA16694 for current-outgoing; Fri, 2 Aug 1996 10:06:36 -0700 (PDT) Received: from minnow.render.com (render.demon.co.uk [158.152.30.118]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id KAA16687 for ; Fri, 2 Aug 1996 10:06:33 -0700 (PDT) Received: from minnow.render.com (minnow.render.com [193.195.178.1]) by minnow.render.com (8.6.12/8.6.9) with SMTP id SAA28686; Fri, 2 Aug 1996 18:06:44 +0100 Date: Fri, 2 Aug 1996 18:06:44 +0100 (BST) From: Doug Rabson To: Terry Lambert cc: jkh@time.cdrom.com, tony@fit.qut.edu.au, freebsd-current@freebsd.org Subject: Re: NFS Diskless Dispare... In-Reply-To: <199608021615.JAA05802@phaeton.artisoft.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Fri, 2 Aug 1996, Terry Lambert wrote: > > [snip] > > > > I think the worst races would be between VOP_READ or VOP_WRITE and vclean. > > I think that you could cause real damage with one of those :-). > > I had a vclean patch to deal with the "free vnode isn't" error a long > time ago... it was a serious kludge, IMO, since it fixed the symptom > instead of the problem (which is that vclean is a bad idea). I think > the patch would also save us from the race conditions as well. Are you > maybe thinking of client side nfsnodes? I was thinking of an NFS client race where a process could be sleeping in NFS waiting for an rpc reply and vclean could cut in and start tearing thing up. If vclean manages to sleep part way through, then interesting things could start to happen... -- Doug Rabson, Microsoft RenderMorphics Ltd. Mail: dfr@render.com Phone: +44 171 251 4411 FAX: +44 171 251 0939 From owner-freebsd-current Fri Aug 2 11:05:08 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id LAA19939 for current-outgoing; Fri, 2 Aug 1996 11:05:08 -0700 (PDT) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id LAA19934 for ; Fri, 2 Aug 1996 11:05:05 -0700 (PDT) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id LAA05977; Fri, 2 Aug 1996 11:03:10 -0700 From: Terry Lambert Message-Id: <199608021803.LAA05977@phaeton.artisoft.com> Subject: Re: NFS Diskless Dispare... To: dfr@render.com (Doug Rabson) Date: Fri, 2 Aug 1996 11:03:10 -0700 (MST) Cc: terry@lambert.org, jkh@time.cdrom.com, tony@fit.qut.edu.au, freebsd-current@freebsd.org In-Reply-To: from "Doug Rabson" at Aug 2, 96 06:06:44 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > > > > > I think the worst races would be between VOP_READ or VOP_WRITE and vclean. > > > I think that you could cause real damage with one of those :-). > > > > I had a vclean patch to deal with the "free vnode isn't" error a long > > time ago... it was a serious kludge, IMO, since it fixed the symptom > > instead of the problem (which is that vclean is a bad idea). I think > > the patch would also save us from the race conditions as well. Are you > > maybe thinking of client side nfsnodes? > > I was thinking of an NFS client race where a process could be sleeping in > NFS waiting for an rpc reply and vclean could cut in and start tearing > thing up. If vclean manages to sleep part way through, then interesting > things could start to happen... I think they would have differnt PID's. Are you concerned about the (vp->v_flag & VXLOCK) == 0 or the !VOP_LOCK() case? The kernel is not currently reeentrant, and I think any underlying FS from an export will cause the block on the server. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-current Fri Aug 2 11:51:56 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id LAA22507 for current-outgoing; Fri, 2 Aug 1996 11:51:56 -0700 (PDT) Received: from minnow.render.com (render.demon.co.uk [158.152.30.118]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id LAA22496 for ; Fri, 2 Aug 1996 11:51:47 -0700 (PDT) Received: from minnow.render.com (minnow.render.com [193.195.178.1]) by minnow.render.com (8.6.12/8.6.9) with SMTP id TAA01130; Fri, 2 Aug 1996 19:52:35 +0100 Date: Fri, 2 Aug 1996 19:52:35 +0100 (BST) From: Doug Rabson To: Terry Lambert cc: jkh@time.cdrom.com, tony@fit.qut.edu.au, freebsd-current@freebsd.org Subject: Re: NFS Diskless Dispare... In-Reply-To: <199608021803.LAA05977@phaeton.artisoft.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Fri, 2 Aug 1996, Terry Lambert wrote: > > > > > > > > I think the worst races would be between VOP_READ or VOP_WRITE and vclean. > > > > I think that you could cause real damage with one of those :-). > > > > > > I had a vclean patch to deal with the "free vnode isn't" error a long > > > time ago... it was a serious kludge, IMO, since it fixed the symptom > > > instead of the problem (which is that vclean is a bad idea). I think > > > the patch would also save us from the race conditions as well. Are you > > > maybe thinking of client side nfsnodes? > > > > I was thinking of an NFS client race where a process could be sleeping in > > NFS waiting for an rpc reply and vclean could cut in and start tearing > > thing up. If vclean manages to sleep part way through, then interesting > > things could start to happen... > > I think they would have differnt PID's. Are you concerned about the > (vp->v_flag & VXLOCK) == 0 or the !VOP_LOCK() case? > > The kernel is not currently reeentrant, and I think any underlying > FS from an export will cause the block on the server. I am thinking of the VXLOCK case. I have been trying to construct a scenario where the nfs client code ends up with an nfsnode which has been freed by vclean() due to the lack of node locks. I haven't managed it yet but I am sure there is one. There is definately a problem with multiple processes appending to a file over NFS due to nfs_write not being serialised by the lock. -- Doug Rabson, Microsoft RenderMorphics Ltd. Mail: dfr@render.com Phone: +44 171 251 4411 FAX: +44 171 251 0939 From owner-freebsd-current Fri Aug 2 13:35:23 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id NAA28790 for current-outgoing; Fri, 2 Aug 1996 13:35:23 -0700 (PDT) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id NAA28784 for ; Fri, 2 Aug 1996 13:35:18 -0700 (PDT) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id NAA06190; Fri, 2 Aug 1996 13:33:09 -0700 From: Terry Lambert Message-Id: <199608022033.NAA06190@phaeton.artisoft.com> Subject: Re: NFS Diskless Dispare... To: dfr@render.com (Doug Rabson) Date: Fri, 2 Aug 1996 13:33:09 -0700 (MST) Cc: terry@lambert.org, jkh@time.cdrom.com, tony@fit.qut.edu.au, freebsd-current@freebsd.org In-Reply-To: from "Doug Rabson" at Aug 2, 96 07:52:35 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > The kernel is not currently reeentrant, and I think any underlying > > FS from an export will cause the block on the server. > > I am thinking of the VXLOCK case. I have been trying to construct a > scenario where the nfs client code ends up with an nfsnode which has been > freed by vclean() due to the lack of node locks. I haven't managed it yet > but I am sure there is one. I think the client side locking is maybe broken. There are a lot of evil things in the NFS client code, and you are right about the VXLOCK. I'd like to see each vnode reference treated as a counting semaphore increment, including the directory name cache references for the things. The vclean code is evil and redundant and redundant, but without moving the vnode allocation to per FS vnodes (I've mentioned this before), there is very little you can do. It's a buffer cache lose to say "no" to a page that's in core, but which does not have a vnode referencing it, so you have to reload it from disk even though a perectly good copy is already in memory. 8-(. > There is definately a problem with multiple processes appending to a file > over NFS due to nfs_write not being serialised by the lock. This is a non-problem. The file offset is maintained on the client and enforced in the uio... the offsets are part of the uio, so it is roughly equivalent to write( channel, buf, size, channel_offset). They should be atomic. I think the problem is that a previous append is not forcing an update to the file length for multiple appends. It's a protocol problem that's really only resolvable with advisory locking: client 1: get file size -> <- size is xxx :server client 2: get file size -> <- size is xxx :server client 1: write at offset xxx -> client 2: [ERROR case] write at offset xxx -> I hesitate to implement in-band reliance on a working locking implementation; I'd prefer an out-of-band contention resoloution of some kind by the clients. Technically, you could argue the same potential problem exists in a local machine for writev() interleaving by two processes. The length of the file baing appended will monotonically increase, but the write order is not guaranteed to not be mixed. I think the same soloution is applicable: out of band semaphoring between the contending processes. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-current Fri Aug 2 16:16:56 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id QAA09432 for current-outgoing; Fri, 2 Aug 1996 16:16:56 -0700 (PDT) Received: from pahtoh.cwu.edu (root@pahtoh.cwu.edu [198.104.65.27]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id QAA09427 for ; Fri, 2 Aug 1996 16:16:55 -0700 (PDT) Received: from tahoma.cwu.edu (skynyrd@tahoma.cwu.edu [198.104.67.25]) by pahtoh.cwu.edu (8.6.13/8.6.9) with ESMTP id QAA29623; Fri, 2 Aug 1996 16:16:45 -0700 Received: (from skynyrd@localhost) by tahoma.cwu.edu (8.6.13/8.6.9) id QAA05148; Fri, 2 Aug 1996 16:16:43 -0700 Date: Fri, 2 Aug 1996 16:16:42 -0700 (PDT) From: Chris Timmons To: "Christoph P. Kukulies" cc: chris@vader.org, freebsd-current@FreeBSD.ORG Subject: Re: Sup failing for sup.freebsd.org In-Reply-To: <199608021454.QAA25943@gilberto.physik.rwth-aachen.de> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk sup5 has been working fine during this period; tried that? On Fri, 2 Aug 1996, Christoph P. Kukulies wrote: > > Is anyone else experiencing problems with sup? For the last couple of > > days I haven't been able to keep up with -CURRENT: > [...] > > I see this here too. My last working sup was Jul 30th. At the moment my sup > logs show these timeouts, too. > > > > SUP: Can't connect to server for supfilesrv: Operation timed out > > SUP: Will retry in 416 seconds > > > > I can ping and traceroute to sup.freebsd.org fine: > > [...] > > > Many thanks, > > > > Chris > > -- > > Chris Dabrowski > > chris@vader.org > > > > --Chris Christoph P. U. Kukulies kuku@gil.physik.rwth-aachen.de > From owner-freebsd-current Fri Aug 2 21:07:34 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id VAA23442 for current-outgoing; Fri, 2 Aug 1996 21:07:34 -0700 (PDT) Received: from plaut.de (inet.plaut.de [194.39.177.166]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id VAA23437 for ; Fri, 2 Aug 1996 21:07:30 -0700 (PDT) Received: from totum.plaut.de (totum.plaut.de [194.39.177.9]) by plaut.de (8.6.12/8.6.12) with ESMTP id EAA21271 for ; Sat, 3 Aug 1996 04:53:39 +0200 Received: from localhost (root@localhost) by totum.plaut.de (8.7.5/8.7.3) with SMTP id GAA10315 for ; Sat, 3 Aug 1996 06:07:27 +0200 (MET DST) Date: Sat, 3 Aug 1996 06:07:26 +0200 (MET DST) From: Michael Reifenberger To: FreeBSD-Current Subject: Mirrored Root? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi, I tried to make my rootdev a mirrored ccd: o options "CCD_OFFSET=0" in the kernelconfigfile o disklabel sd0/sd1 to have equal a-partitions. o disklabel sd0/sd1 to have h-partitions with same geometry as the a-ones. o reboot o booting from sd0a in singleuser. o dd if=/dev/rsd0h of=/dev/rsd1h o ccdconfig ccd0 1 0x04 /dev/sd0h /dev/sd1h o fsck /dev/rccd0c (no problems so far) o mount /dev/ccd0c / this fails because mount complaints about: "Specified device does not match mounted device" could this be fixed? Bye! ---- Michael Reifenberger Plaut Software GmbH, R/3 Basis From owner-freebsd-current Fri Aug 2 21:46:40 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id VAA25985 for current-outgoing; Fri, 2 Aug 1996 21:46:40 -0700 (PDT) Received: from ki.net (root@ki.net [205.150.102.1]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id VAA25977 for ; Fri, 2 Aug 1996 21:46:38 -0700 (PDT) Received: from localhost (scrappy@localhost) by ki.net (8.7.5/8.7.5) with SMTP id AAA09071 for ; Sat, 3 Aug 1996 00:46:34 -0400 (EDT) Date: Sat, 3 Aug 1996 00:46:32 -0400 (EDT) From: "Marc G. Fournier" To: current@freebsd.org Subject: Problem with 2.2-960801-SNAP Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Has anyone else experienced a problem were your arrow keys won't work inside of the 'labeller'? It works fine for me at the other menus, just not when trying to sub-partition my drive... I get an error of 'Invalid key 1- Type F1 or ? for help'... Also, not sure if this is a problem or not, but when I went to partition the drive, I used 'A' for all the drive, as I usually do, but couldn't set it "bootable"...I *thought* I used to be able to, so either this is broken, or the default is bootable when you make the whole drive dedicated to FreeBSD... Marc G. Fournier scrappy@ki.net Systems Administrator @ ki.net scrappy@freebsd.org From owner-freebsd-current Fri Aug 2 22:19:43 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id WAA27794 for current-outgoing; Fri, 2 Aug 1996 22:19:43 -0700 (PDT) Received: from time.cdrom.com (time.cdrom.com [204.216.27.226]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id WAA27789 for ; Fri, 2 Aug 1996 22:19:41 -0700 (PDT) Received: from time.cdrom.com (localhost [127.0.0.1]) by time.cdrom.com (8.7.5/8.6.9) with ESMTP id WAA03679; Fri, 2 Aug 1996 22:19:03 -0700 (PDT) To: "Marc G. Fournier" cc: current@freebsd.org Subject: Re: Problem with 2.2-960801-SNAP In-reply-to: Your message of "Sat, 03 Aug 1996 00:46:32 EDT." Date: Fri, 02 Aug 1996 22:19:03 -0700 Message-ID: <3677.839049543@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > Has anyone else experienced a problem were your arrow keys won't > work inside of the 'labeller'? It works fine for me at the > other menus, just not when trying to sub-partition my drive... Oh geeze, looks like something's definitely messed up there! I'll generate another boot.flp forthwith. Jordan From owner-freebsd-current Fri Aug 2 22:25:44 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id WAA28136 for current-outgoing; Fri, 2 Aug 1996 22:25:44 -0700 (PDT) Received: from ki.net (root@ki.net [205.150.102.1]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id WAA28129 for ; Fri, 2 Aug 1996 22:25:41 -0700 (PDT) Received: from localhost (scrappy@localhost) by ki.net (8.7.5/8.7.5) with SMTP id BAA18314; Sat, 3 Aug 1996 01:25:38 -0400 (EDT) Date: Sat, 3 Aug 1996 01:25:37 -0400 (EDT) From: "Marc G. Fournier" To: "Jordan K. Hubbard" cc: current@freebsd.org Subject: Re: Problem with 2.2-960801-SNAP In-Reply-To: <3677.839049543@time.cdrom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Fri, 2 Aug 1996, Jordan K. Hubbard wrote: > > Has anyone else experienced a problem were your arrow keys won't > > work inside of the 'labeller'? It works fine for me at the > > other menus, just not when trying to sub-partition my drive... > > Oh geeze, looks like something's definitely messed up there! > I'll generate another boot.flp forthwith. > Great, other then that, things installed fine (terrible to have to reboot if you mess up in labeller *grin*)...so running the new SNAP right now... Marc G. Fournier scrappy@ki.net Systems Administrator @ ki.net scrappy@freebsd.org From owner-freebsd-current Fri Aug 2 23:32:22 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id XAA04364 for current-outgoing; Fri, 2 Aug 1996 23:32:22 -0700 (PDT) Received: from wgrobez1.remote.louisville.edu (root@wgrobez1.remote.louisville.edu [136.165.243.183]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id XAA04358 for ; Fri, 2 Aug 1996 23:32:18 -0700 (PDT) Received: from localhost (wangel@localhost) by wgrobez1.remote.louisville.edu (8.7.5/8.6.12) with SMTP id CAA00240 for ; Sat, 3 Aug 1996 02:32:03 -0400 (EDT) Date: Sat, 3 Aug 1996 02:32:03 -0400 (EDT) From: Gary Roberts To: freebsd-current@freebsd.org Subject: FlashPoint LT In-Reply-To: <199608021454.QAA25943@gilberto.physik.rwth-aachen.de> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Does FreeBSD support the Buslogic FlashPoint LT ? If it does, how do I 'assign' it a driver in the kernel config file:) I got my AHA-1522 to work, but I'd much rather use the Buslogic FlashPoint Thanks Gary From owner-freebsd-current Sat Aug 3 01:14:28 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id BAA09430 for current-outgoing; Sat, 3 Aug 1996 01:14:28 -0700 (PDT) Received: from iworks.InterWorks.org (deischen@iworks.interworks.org [128.255.18.10]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id BAA09423 for ; Sat, 3 Aug 1996 01:14:24 -0700 (PDT) Received: by iworks.InterWorks.org (1.37.109.8/16.2) id AA01246; Sat, 3 Aug 1996 03:12:41 -0500 Message-Id: <9608030812.AA01246@iworks.InterWorks.org> Date: Sat, 3 Aug 1996 03:12:41 -0500 From: "Daniel M. Eischen" To: freebsd-current@FreeBSD.org, wangel@wgrobez1.remote.louisville.edu Subject: Re: FlashPoint LT Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk > Does FreeBSD support the Buslogic FlashPoint LT ? > > If it does, how do I 'assign' it a driver in the kernel config file:) > > I got my AHA-1522 to work, but I'd much rather use the Buslogic FlashPoint BusLogic will not release programming information on the FlashPoint SCSI controller. They have given the Linux BusLogic driver author good support for their other SCSI controllers. There is an upgrade plan (instigated by the Linux driver author) to replace the FlashPoint with one of their other controllers that are supported by Linux. I believe the upgrade cost to a better controller is in the $25-45 (US) range. Contact BusLogic and tell them you're running Linux. The FreeBSD BusLogic driver is (I believe) scheduled for revamping, so an upgrade to one of the other BusLogic controllers should be worthwhile. Dan Eischen deischen@iworks.InterWorks.org From owner-freebsd-current Sat Aug 3 01:36:02 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id BAA11369 for current-outgoing; Sat, 3 Aug 1996 01:36:02 -0700 (PDT) Received: from Campino.Informatik.RWTH-Aachen.DE (campino.Informatik.RWTH-Aachen.DE [137.226.225.2]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id BAA11345 for ; Sat, 3 Aug 1996 01:35:57 -0700 (PDT) Received: from gilberto.physik.rwth-aachen.de (gilberto.physik.rwth-aachen.de [137.226.31.2]) by Campino.Informatik.RWTH-Aachen.DE (RBI-Z-5/8.6.12) with ESMTP id KAA14018; Sat, 3 Aug 1996 10:31:36 +0200 Received: (from kuku@localhost) by gilberto.physik.rwth-aachen.de (8.6.11/8.6.9) id KAA29106; Sat, 3 Aug 1996 10:44:55 +0200 From: "Christoph P. Kukulies" Message-Id: <199608030844.KAA29106@gilberto.physik.rwth-aachen.de> Subject: Re: Sup failing for sup.freebsd.org To: skynyrd@tahoma.cwu.edu (Chris Timmons) Date: Sat, 3 Aug 1996 10:44:53 +0200 (MET DST) Cc: kuku@gilberto.physik.rwth-aachen.de, chris@vader.org, freebsd-current@FreeBSD.ORG In-Reply-To: from Chris Timmons at "Aug 2, 96 04:16:42 pm" Reply-To: Christoph Kukulies X-Mailer: ELM [version 2.4ME+ PL16 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > > sup5 has been working fine during this period; tried that? I'm afraid switching supservers results in everything getting resupped since time stamps differ from one supserver to another and I don't want to have another sup storm at the moment. Someone may correct me if I'm wrong. Also there have been too many inponderabilities with supservers recently so that I remain with freefall. [about supserver connection time outs] > > > > > Many thanks, > > > > > > Chris > > > -- > > > Chris Dabrowski > > > chris@vader.org > > > > > > --Chris Christoph P. U. Kukulies kuku@gil.physik.rwth-aachen.de From owner-freebsd-current Sat Aug 3 01:39:55 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id BAA11800 for current-outgoing; Sat, 3 Aug 1996 01:39:55 -0700 (PDT) Received: from MindBender.HeadCandy.com (root@mindbender.headcandy.com [199.238.225.168]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id BAA11794 for ; Sat, 3 Aug 1996 01:39:48 -0700 (PDT) Received: from localhost.HeadCandy.com (michaelv@localhost.HeadCandy.com [127.0.0.1]) by MindBender.HeadCandy.com (8.7.5/8.7.3) with SMTP id BAA26559; Sat, 3 Aug 1996 01:39:39 -0700 (PDT) Message-Id: <199608030839.BAA26559@MindBender.HeadCandy.com> X-Authentication-Warning: MindBender.HeadCandy.com: Host michaelv@localhost.HeadCandy.com [127.0.0.1] didn't use HELO protocol To: "Daniel M. Eischen" cc: freebsd-current@freebsd.org, wangel@wgrobez1.remote.louisville.edu Subject: Re: FlashPoint LT In-reply-to: Your message of Sat, 03 Aug 96 03:12:41 -0500. <9608030812.AA01246@iworks.InterWorks.org> Date: Sat, 03 Aug 1996 01:39:39 -0700 From: "Michael L. VanLoon -- HeadCandy.com" Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >> Does FreeBSD support the Buslogic FlashPoint LT ? >BusLogic will not release programming information on the FlashPoint SCSI >controller. They have given the Linux BusLogic driver author good support >for their other SCSI controllers. Actually, the API to their older cards is quite open, and anyone can get the documents -- they did nothing special (as far as I know -- I have the Technical Reference Manual myself) for the Linux folks in this respect. >There is an upgrade plan (instigated >by the Linux driver author) to replace the FlashPoint with one of their >other controllers that are supported by Linux. I believe the upgrade >cost to a better controller is in the $25-45 (US) range. Contact BusLogic >and tell them you're running Linux. I think it would be better to specifically make the point that you are running free "unix" and it is *not* Linux. I really dislike the fad of Linux being used as the generic term for free "unix". Then point out that FreeBSD (and NetBSD) has supported their older cards very faithfully through the years, and you would like it if FreeBSD could continue to support their cards. After that is said, say that FreeBSD is "like" Linux, and the same deal that works for Linux will work for you. >The FreeBSD BusLogic driver is (I believe) scheduled for revamping, so >an upgrade to one of the other BusLogic controllers should be worthwhile. But even without revamping, it could arguably be the most stable SCSI driver in the source tree. It just won't be quite as efficient, or quite as fast if you have really high-end hard drives. ----------------------------------------------------------------------------- Michael L. VanLoon michaelv@HeadCandy.com --< Free your mind and your machine -- NetBSD free un*x >-- NetBSD working ports: 386+PC, Mac 68k, Amiga, Atari 68k, HP300, Sun3, Sun4/4c/4m, DEC MIPS, DEC Alpha, PC532, VAX, MVME68k, arm32... NetBSD ports in progress: PICA, others... Roll your own Internet access -- Seattle People's Internet cooperative. If you're in the Seattle area, ask me how. ----------------------------------------------------------------------------- From owner-freebsd-current Sat Aug 3 05:50:50 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id FAA04945 for current-outgoing; Sat, 3 Aug 1996 05:50:50 -0700 (PDT) Received: from mexico.brainstorm.eu.org (root@mexico.brainstorm.eu.org [193.56.58.253]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id FAA04939 for ; Sat, 3 Aug 1996 05:50:46 -0700 (PDT) Received: from brasil.brainstorm.eu.org (brasil.brainstorm.eu.org [193.56.58.33]) by mexico.brainstorm.eu.org (8.7.5/8.7.3) with ESMTP id OAA25814 for ; Sat, 3 Aug 1996 14:50:37 +0200 Received: (from uucp@localhost) by brasil.brainstorm.eu.org (8.6.12/8.6.12) with UUCP id OAA09407 for freebsd-current@FreeBSD.ORG; Sat, 3 Aug 1996 14:50:16 +0200 Received: (from roberto@localhost) by keltia.freenix.fr (8.8.Alpha.7/keltia-uucp-2.9) id OAA12325; Sat, 3 Aug 1996 14:49:11 +0200 (MET DST) Message-Id: <199608031249.OAA12325@keltia.freenix.fr> Date: Sat, 3 Aug 1996 14:49:09 +0200 From: roberto@keltia.freenix.fr (Ollivier Robert) To: freebsd-current@FreeBSD.ORG (FreeBSD Current Users' list) Subject: Make bootstrap order X-Mailer: Mutt 0.38 Mime-Version: 1.0 Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk The bootstrap target in src/Makefile has the wrong order for lex/tsort because lex has a library (libln.a) and bsd.lib.mk has been modified to use 'tsort -q'. Tsort has not been build yet... tsort should be before lex. Index: Makefile =================================================================== RCS file: /spare/FreeBSD-current/src/Makefile,v retrieving revision 1.92 diff -u -2 -r1.92 Makefile --- Makefile 1996/08/03 06:44:46 1.92 +++ Makefile 1996/08/03 12:46:00 @@ -346,7 +346,7 @@ cd ${.CURDIR}/usr.bin/xinstall && ${MAKE} depend && \ ${MAKE} ${MK_FLAGS} all install ${CLEANDIR} ${OBJDIR} - cd ${.CURDIR}/usr.bin/lex && ${MAKE} bootstrap && ${MAKE} depend && \ - ${MAKE} ${MK_FLAGS} all install ${CLEANDIR} ${OBJDIR} cd ${.CURDIR}/usr.bin/tsort && ${MAKE} depend && \ + ${MAKE} ${MK_FLAGS} all install ${CLEANDIR} ${OBJDIR} + cd ${.CURDIR}/usr.bin/lex && ${MAKE} bootstrap && ${MAKE} depend && \ ${MAKE} ${MK_FLAGS} all install ${CLEANDIR} ${OBJDIR} -- Ollivier ROBERT -=- The daemon is FREE! -=- roberto@keltia.freenix.fr FreeBSD keltia.freenix.fr 2.2-CURRENT #17: Fri Aug 2 20:40:17 MET DST 1996 From owner-freebsd-current Sat Aug 3 06:22:11 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id GAA07183 for current-outgoing; Sat, 3 Aug 1996 06:22:11 -0700 (PDT) Received: from pcnet1.pcnet.com (root@pcnet1.pcnet.com [204.213.232.3]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id GAA07178 for ; Sat, 3 Aug 1996 06:22:09 -0700 (PDT) Received: from rigel (ts3-pt24.pcnet.com) by pcnet1.pcnet.com (4.1/SMI-4.1) id AA07240; Sat, 3 Aug 96 09:18:04 EDT Message-Id: <3203539D.41C67EA6@iworks.InterWorks.org> Date: Sat, 03 Aug 1996 09:26:53 -0400 From: "Daniel M. Eischen" X-Mailer: Mozilla 3.0b5aGold (X11; I; FreeBSD 2.2-CURRENT i386) Mime-Version: 1.0 To: michaelv@HeadCandy.com Cc: freebsd-current@freebsd.org, wangel@wgrobez1.remote.louisville.edu Subject: Re: FlashPoint LT Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > >> Does FreeBSD support the Buslogic FlashPoint LT ? > > >BusLogic will not release programming information on the FlashPoint SCSI > >controller. They have given the Linux BusLogic driver author good support > >for their other SCSI controllers. > > Actually, the API to their older cards is quite open, and anyone can > get the documents -- they did nothing special (as far as I know -- I > have the Technical Reference Manual myself) for the Linux folks in > this respect. Well, BusLogic senior management have met with the Linux driver author regarding Linux and free software support for the FlashPoint. BusLogic also used the Linux driver author for Beta-testing the BT-948/958 with Linux before the products were brought to market. The author has also received support from the BusLogic technical staff. > >There is an upgrade plan (instigated > >by the Linux driver author) to replace the FlashPoint with one of their > >other controllers that are supported by Linux. I believe the upgrade > >cost to a better controller is in the $25-45 (US) range. Contact BusLogic > >and tell them you're running Linux. > > I think it would be better to specifically make the point that you are > running free "unix" and it is *not* Linux. I really dislike the fad > of Linux being used as the generic term for free "unix". Then point > out that FreeBSD (and NetBSD) has supported their older cards very > faithfully through the years, and you would like it if FreeBSD could > continue to support their cards. After that is said, say that FreeBSD > is "like" Linux, and the same deal that works for Linux will work for > you. I agree :). I just thought it would be easier to get an upgrade if you mentioned "Linux". > > >The FreeBSD BusLogic driver is (I believe) scheduled for revamping, so > >an upgrade to one of the other BusLogic controllers should be worthwhile. > > But even without revamping, it could arguably be the most stable SCSI > driver in the source tree. It just won't be quite as efficient, or > quite as fast if you have really high-end hard drives. From owner-freebsd-current Sat Aug 3 07:44:23 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id HAA12935 for current-outgoing; Sat, 3 Aug 1996 07:44:23 -0700 (PDT) Received: from freefall.freebsd.org (localhost.cdrom.com [127.0.0.1]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id HAA12930; Sat, 3 Aug 1996 07:44:20 -0700 (PDT) Message-Id: <199608031444.HAA12930@freefall.freebsd.org> To: "Michael L. VanLoon -- HeadCandy.com" cc: "Daniel M. Eischen" , freebsd-current@FreeBSD.ORG, wangel@wgrobez1.remote.louisville.edu Subject: Re: FlashPoint LT In-reply-to: Your message of "Sat, 03 Aug 1996 01:39:39 PDT." <199608030839.BAA26559@MindBender.HeadCandy.com> Date: Sat, 03 Aug 1996 07:44:19 -0700 From: "Justin T. Gibbs" Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > >>> Does FreeBSD support the Buslogic FlashPoint LT ? > >>BusLogic will not release programming information on the FlashPoint SCSI >>controller. They have given the Linux BusLogic driver author good support >>for their other SCSI controllers. > >Actually, the API to their older cards is quite open, and anyone can >get the documents -- they did nothing special (as far as I know -- I >have the Technical Reference Manual myself) for the Linux folks in >this respect. Lets just say that Leonard N. Zubkoff has some very close ties to Buslogic. He gets every new Buslogic adapter long before its released (6-8 months), has access to their firmware engineers and testing lab, etc, etc. I've actually talked to him in person about working on the Buslogic driver for *BSD, and he may pass come of his contacts on to me, but its not clear yet. >>There is an upgrade plan (instigated >>by the Linux driver author) to replace the FlashPoint with one of their >>other controllers that are supported by Linux. I believe the upgrade >>cost to a better controller is in the $25-45 (US) range. Contact BusLogic >>and tell them you're running Linux. > >I think it would be better to specifically make the point that you are >running free "unix" and it is *not* Linux. I really dislike the fad >of Linux being used as the generic term for free "unix". Then point >out that FreeBSD (and NetBSD) has supported their older cards very >faithfully through the years, and you would like it if FreeBSD could >continue to support their cards. After that is said, say that FreeBSD >is "like" Linux, and the same deal that works for Linux will work for >you. Although the program was initialy created for Linux users, it applies to any freely availible Unix. The person you talk to may not understand what FreeBSD or NetBSD is when you talk to them, but they will allow you to take advantage of this offer once you explain your situation. >>The FreeBSD BusLogic driver is (I believe) scheduled for revamping, so >>an upgrade to one of the other BusLogic controllers should be worthwhile. > >But even without revamping, it could arguably be the most stable SCSI >driver in the source tree. It just won't be quite as efficient, or >quite as fast if you have really high-end hard drives. I wouldn't be so sure. I did some initial code review a while back after my discussions with Leonard (who also looked at the BSD driver before writing his own) and there are definitely some race conditions. It may be that not supporting tagged queueing is sufficient enough of a handicap to prevent problems though. >----------------------------------------------------------------------------- > Michael L. VanLoon michaelv@HeadCandy.com > --< Free your mind and your machine -- NetBSD free un*x >-- > NetBSD working ports: 386+PC, Mac 68k, Amiga, Atari 68k, HP300, Sun3, > Sun4/4c/4m, DEC MIPS, DEC Alpha, PC532, VAX, MVME68k, arm32... > NetBSD ports in progress: PICA, others... > > Roll your own Internet access -- Seattle People's Internet cooperative. > If you're in the Seattle area, ask me how. >----------------------------------------------------------------------------- -- Justin T. Gibbs =========================================== FreeBSD: Turning PCs into workstations =========================================== From owner-freebsd-current Sat Aug 3 09:11:44 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id JAA18548 for current-outgoing; Sat, 3 Aug 1996 09:11:44 -0700 (PDT) Received: from moonpie.w8hd.org (moonpie.w8hd.org [198.252.159.14]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id JAA18543 for ; Sat, 3 Aug 1996 09:11:39 -0700 (PDT) Received: from localhost (kimc@localhost) by moonpie.w8hd.org (8.7.5/8.6.12) with SMTP id MAA14372 for ; Sat, 3 Aug 1996 12:11:37 -0400 (EDT) X-Authentication-Warning: moonpie.w8hd.org: kimc owned process doing -bs Date: Sat, 3 Aug 1996 12:11:37 -0400 (EDT) From: Kim Culhan To: current@FreeBSD.org Subject: make world failure Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk This is from -current sup'd at ~1400 UTC this date: cc -O -c /usr/src/usr.bin/lex/lib/libyywrap.c -o libyywrap.o building standard ln library tsort: illegal option -- q usage: tsort [-dl] [file] ar: no archive members specified usage: ar -d [-Tv] archive file ... ar -m [-Tv] archive file ... ar -m [-abiTv] position archive file ... ar -p [-Tv] archive [file ...] ar -q [-cTv] archive file ... ar -r [-cuTv] archive file ... ar -r [-abciuTv] position archive file ... ar -t [-Tv] archive [file ...] ar -x [-ouTv] archive [file ...] *** Error code 1 Stop. regards kim -- kimc@w8hd.org From owner-freebsd-current Sat Aug 3 09:17:24 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id JAA18812 for current-outgoing; Sat, 3 Aug 1996 09:17:24 -0700 (PDT) Received: from relay-2.mail.demon.net (disperse.demon.co.uk [158.152.1.77]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id JAA18797 for ; Sat, 3 Aug 1996 09:17:21 -0700 (PDT) Received: from post.demon.co.uk ([158.152.1.72]) by relay-2.mail.demon.net id ab16426; 3 Aug 96 17:16 +0100 Received: from nlsys.demon.co.uk ([158.152.125.33]) by relay-3.mail.demon.net id aa06181; 3 Aug 96 17:15 +0100 Received: from localhost (dfr@localhost) by nlsys.demon.co.uk (8.7.5/8.6.9) with SMTP id RAA01578; Sat, 3 Aug 1996 17:14:33 +0100 (BST) Date: Sat, 3 Aug 1996 17:14:32 +0100 (BST) From: Doug Rabson Reply-To: Doug Rabson To: Terry Lambert cc: Doug Rabson , jkh@time.cdrom.com, tony@fit.qut.edu.au, freebsd-current@freebsd.org Subject: Re: NFS Diskless Dispare... In-Reply-To: <199608022033.NAA06190@phaeton.artisoft.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Fri, 2 Aug 1996, Terry Lambert wrote: > > > The kernel is not currently reeentrant, and I think any underlying > > > FS from an export will cause the block on the server. > > > > I am thinking of the VXLOCK case. I have been trying to construct a > > scenario where the nfs client code ends up with an nfsnode which has been > > freed by vclean() due to the lack of node locks. I haven't managed it yet > > but I am sure there is one. > > I think the client side locking is maybe broken. There are a lot of > evil things in the NFS client code, and you are right about the VXLOCK. > > I'd like to see each vnode reference treated as a counting semaphore > increment, including the directory name cache references for the things. In lite2, there is a fallback implementation of VOP_LOCK which nfs uses. This allows multiple locking processes but keeps a count of how are locking the vnode. Vclean() blocks until this count drains back to zero and then takes an exclusive lock on the vnode. I think this should improve the robustness somewhat. I am not quite convinced that this is the main cause of the current nfs instabilities as I can't come up with a killer scenario which doesn't involve forcibly unmounting an active NFS client filesystem which doesn't normally happen in real life. I just grepped for uses of VOP_LOCK in the kernel and there seem to be a few places in the vm system which appear to be using the vnode lock to protect critical sections of code. Have a look at vm_object_terminate() and vm_object_page_clean() and tell me what would happen if the VOP_LOCK is not exclusive. > > The vclean code is evil and redundant and redundant, but without moving > the vnode allocation to per FS vnodes (I've mentioned this before), there > is very little you can do. It's a buffer cache lose to say "no" to a > page that's in core, but which does not have a vnode referencing it, > so you have to reload it from disk even though a perectly good copy > is already in memory. 8-(. You have to start reusing vnodes sometime. Whether it means reusing them within a filesystem or across a global pool, it has to happen. Even reusing a vnode within a filesystem would involve something similar to vclean() surely. I don't understand the VM system well enough to judge whether dropping a few valid pages from old vnodes is a real problem in performance terms. > > > > There is definately a problem with multiple processes appending to a file > > over NFS due to nfs_write not being serialised by the lock. > > This is a non-problem. The file offset is maintained on the client > and enforced in the uio... the offsets are part of the uio, so it is > roughly equivalent to write( channel, buf, size, channel_offset). They > should be atomic. I think the problem is that a previous append is > not forcing an update to the file length for multiple appends. It's a > protocol problem that's really only resolvable with advisory locking: > > client 1: get file size -> > <- size is xxx :server > client 2: get file size -> > <- size is xxx :server > client 1: > write at offset xxx -> > client 2: [ERROR case] > write at offset xxx -> Consider the following timeline: client 1 client 2 enter nfs_write for an append write set uio->uio_offset to np->n_size prepare to write first block update np->n_size for first partial write sleep waiting for a buf enter nfs_write for an append set uio->uio_offset to np->n_size prepare to write first block update np->n_size get buf write block and wait for reply wake up, finish writing first buf write second buf overlapping client2's first buf. The problem is that for an append write which stretches across more than one buf, the operation is not atomic due to the lack of serialising the calls to write which would normally be enforced by the locks. This is a real world problem. Karl Denninger had this problem last year with an http server updating log files across NFS. He eventually moved the logs to a local disk. > > I hesitate to implement in-band reliance on a working locking > implementation; I'd prefer an out-of-band contention resoloution of > some kind by the clients. > > Technically, you could argue the same potential problem exists in a > local machine for writev() interleaving by two processes. The length > of the file baing appended will monotonically increase, but the write > order is not guaranteed to not be mixed. I think the same soloution > is applicable: out of band semaphoring between the contending processes. The write order for writev can be mixed but having data written by two normal write syscalls from two different processes mixed up is something which can and should be fixed IMHO. -- Doug Rabson Mail: dfr@nlsys.demon.co.uk Phone: +44 181 951 1891 From owner-freebsd-current Sat Aug 3 09:26:47 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id JAA19488 for current-outgoing; Sat, 3 Aug 1996 09:26:47 -0700 (PDT) Received: from moonpie.w8hd.org (moonpie.w8hd.org [198.252.159.14]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id JAA19482 for ; Sat, 3 Aug 1996 09:26:44 -0700 (PDT) Received: from localhost (kimc@localhost) by moonpie.w8hd.org (8.7.5/8.6.12) with SMTP id MAA14391 for ; Sat, 3 Aug 1996 12:26:43 -0400 (EDT) X-Authentication-Warning: moonpie.w8hd.org: kimc owned process doing -bs Date: Sat, 3 Aug 1996 12:26:43 -0400 (EDT) From: Kim Culhan To: current@FreeBSD.org Subject: fetch/main.c error Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk This also from -current sup'd at ~1400 UTC this date: ===> fetch cc -O -Wall -c /usr/src/usr.bin/fetch/main.c /usr/src/usr.bin/fetch/main.c: In function `ftpget': /usr/src/usr.bin/fetch/main.c:225: too many arguments to function `ftpLogin' *** Error code 1 Stop. regards kim -- kimc@w8hd.org From owner-freebsd-current Sat Aug 3 09:31:15 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id JAA19797 for current-outgoing; Sat, 3 Aug 1996 09:31:15 -0700 (PDT) Received: from moonpie.w8hd.org (moonpie.w8hd.org [198.252.159.14]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id JAA19790 for ; Sat, 3 Aug 1996 09:31:13 -0700 (PDT) Received: from localhost (kimc@localhost) by moonpie.w8hd.org (8.7.5/8.6.12) with SMTP id MAA14398 for ; Sat, 3 Aug 1996 12:31:11 -0400 (EDT) X-Authentication-Warning: moonpie.w8hd.org: kimc owned process doing -bs Date: Sat, 3 Aug 1996 12:31:11 -0400 (EDT) From: Kim Culhan To: current@FreeBSD.org Subject: make world failed -old tsort Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk Able to bootstrap past previously mentioned make world failure, installed -current tsort first. Sorry to bother the list.. regards kim -- kimc@w8hd.org From owner-freebsd-current Sat Aug 3 09:33:33 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id JAA19944 for current-outgoing; Sat, 3 Aug 1996 09:33:33 -0700 (PDT) Received: from spooky.eis.net.au (root@spooky.eis.net.au [203.12.171.2]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id JAA19936 for ; Sat, 3 Aug 1996 09:33:29 -0700 (PDT) Received: (from ernie@localhost) by spooky.eis.net.au (8.7.5/8.6.12) id CAA08124 for freebsd-current@freebsd.org; Sun, 4 Aug 1996 02:32:51 +1000 (EST) From: Ernie Elu Message-Id: <199608031632.CAA08124@spooky.eis.net.au> Subject: Re: Sup failing for sup.freebsd.org To: freebsd-current@freebsd.org Date: Sun, 4 Aug 1996 02:32:50 +1000 (EST) In-Reply-To: <199608030844.KAA29106@gilberto.physik.rwth-aachen.de> from "Christoph P. Kukulies" at "Aug 3, 96 10:44:53 am" X-Mailer: ELM [version 2.4ME+ PL15 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > sup5 has been working fine during this period; tried that? > > I'm afraid switching supservers results in everything getting resupped > since time stamps differ from one supserver to another and I don't want > to have another sup storm at the moment. Someone may correct > me if I'm wrong. Also there have been too many inponderabilities with > supservers recently so that I remain with freefall. I even had a worse experience that took me a week to figure out, one of the files on sup.au.freebsd.org in the /etc dir was truncated to about 25% of it's correct length and causing make world to fail. I only found it after ftping to ftp.freebsd.org and manually checking the file lengths on the -current files there. The point it the sup.au.freebsd.org files were unreliable in that instance and I would be keen to know if there is any work around? I lost a lot of hours chasing that but I would prefer to use that site to keep the load off sup.freebsd.org which is the only site I trust at the moment. - Ernie. From owner-freebsd-current Sat Aug 3 10:00:53 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id KAA21770 for current-outgoing; Sat, 3 Aug 1996 10:00:53 -0700 (PDT) Received: from fgate.flevel.co.uk (root@fgate.flevel.co.uk [194.6.101.2]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id KAA21763 for ; Sat, 3 Aug 1996 10:00:46 -0700 (PDT) Received: from localhost (dev@localhost) by fgate.flevel.co.uk (8.7.5/8.6.9) with SMTP id SAA28446 for ; Sat, 3 Aug 1996 18:04:00 +0100 (BST) Date: Sat, 3 Aug 1996 18:04:00 +0100 (BST) From: Developer To: freebsd-current@freebsd.org Subject: Linux Willows? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Could someone explain what Linux Willow is and where to get a copy of it from? Thanks. Trefor S. From owner-freebsd-current Sat Aug 3 10:12:54 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id KAA22826 for current-outgoing; Sat, 3 Aug 1996 10:12:54 -0700 (PDT) Received: from walkabout.asstdc.com.au (root@walkabout.asstdc.com.au [202.12.127.73]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id KAA22818 for ; Sat, 3 Aug 1996 10:12:50 -0700 (PDT) Received: (from imb@localhost) by walkabout.asstdc.com.au (8.7.5/BSD4.4) id DAA00918 Sun, 4 Aug 1996 03:12:40 +1000 (EST) From: michael butler Message-Id: <199608031712.DAA00918@walkabout.asstdc.com.au> Subject: Re: Sup failing for sup.freebsd.org To: ernie@spooky.eis.net.au (Ernie Elu) Date: Sun, 4 Aug 1996 03:12:39 +1000 (EST) Cc: freebsd-current@freebsd.org In-Reply-To: <199608031632.CAA08124@spooky.eis.net.au> from Ernie Elu at "Aug 4, 96 02:32:50 am" X-Comment: Phone 0419-240-180, International +61-419-240-180 X-Comment: finger imb@asstdc.com.au for PGP public key 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-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > I even had a worse experience that took me a week to figure out, one of the > files on sup.au.freebsd.org in the /etc dir was truncated to about 25% of > it's correct length and causing make world to fail. I only found it after > ftping to ftp.freebsd.org and manually checking the file lengths on the > -current files there. Whilst I have been caught out by SUP this way before :-( Closer to home, you could've tried ftp.asstdc.com.au:/pub/FreeBSD-current .. or ftp2.au.freebsd.org or .. I'm sure there are more .. > The point it the sup.au.freebsd.org files were unreliable in that instance > and I would be keen to know if there is any work around? I lost a lot of > hours chasing that but I would prefer to use that site to keep the load off > sup.freebsd.org which is the only site I trust at the moment. .. or sup2.au.freebsd.org which is also connected via Telstra in Paddington. It's at least as reliable .. that is, when guys don't throw petrol down Telstra cable pits and set them alight :-( michael From owner-freebsd-current Sat Aug 3 12:14:05 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id MAA01888 for current-outgoing; Sat, 3 Aug 1996 12:14:05 -0700 (PDT) Received: (from dyson@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id MAA01882; Sat, 3 Aug 1996 12:14:04 -0700 (PDT) From: John Dyson Message-Id: <199608031914.MAA01882@freefall.freebsd.org> Subject: Re: NFS Diskless Dispare... To: dfr@render.com Date: Sat, 3 Aug 1996 12:14:04 -0700 (PDT) Cc: terry@lambert.org, jkh@time.cdrom.com, tony@fit.qut.edu.au, freebsd-current@freebsd.org In-Reply-To: from "Doug Rabson" at Aug 3, 96 05:14:32 pm X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > I just grepped for uses of VOP_LOCK in the kernel and there seem to be a > few places in the vm system which appear to be using the vnode lock to > protect critical sections of code. Have a look at vm_object_terminate() > and vm_object_page_clean() and tell me what would happen if the VOP_LOCK > is not exclusive. > Don't do a vm_object_page_clean if VOP_LOCK is not exclusive :-). Don't even think about it... I sure don't want to :-). > > You have to start reusing vnodes sometime. Whether it means reusing them > within a filesystem or across a global pool, it has to happen. Even > reusing a vnode within a filesystem would involve something similar to > vclean() surely. I don't understand the VM system well enough to judge > whether dropping a few valid pages from old vnodes is a real problem in > performance terms. > If the vnode is on the free queue, there had better not be any processes using it at the time (the vm_object holds a reference.) If you need to get a free vnode, you should probably first check the vnode free list and then perhaps try to check the cached VM objects. Vnode backed cached VM objects should be able to be terminated at any time (in process context.) A side-effect of the object termination is that the vnode will be pretty much available for re-use. John From owner-freebsd-current Sat Aug 3 12:42:49 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id MAA04827 for current-outgoing; Sat, 3 Aug 1996 12:42:49 -0700 (PDT) Received: from quagmire.ki.net (root@quagmire.ki.net [205.150.102.51]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id MAA04816 for ; Sat, 3 Aug 1996 12:42:46 -0700 (PDT) Received: from localhost (scrappy@localhost) by quagmire.ki.net (8.7.5/8.7.5) with SMTP id PAA07771 for ; Sat, 3 Aug 1996 15:42:52 -0400 (EDT) Date: Sat, 3 Aug 1996 15:42:52 -0400 (EDT) From: "Marc G. Fournier" To: current@freebsd.org Subject: NIS Setup Question Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi... Just installed 2.2-960801-SNAP last night, and moved most of the load/administrative functions off of my 2.1-STABLE box over to it, including NIS... Now, for some reason that I've yet to figure, NIS doesn't work right. I'm running 'rpc.yypasswdd -m /etc/master.passwd -s -f', so that updates go properly to my /etc/master.passwd file, but if I try to change a pasword on one of my client machines, I get, in /var/log/messages on the server machine: Aug 3 15:35:24 quagmire rpc.yppasswdd[7708]: /var/yp/master.passwd: No such file or directory But I don't want it in /var/yp, and I'm explicitly telling it, according to the man page (or how I interpreted the man page, at least), to use /etc/master.passwd... Have I missed something, or did NIS get broken at some point? Thanks... Marc G. Fournier scrappy@ki.net Systems Administrator @ ki.net scrappy@freebsd.org From owner-freebsd-current Sat Aug 3 12:55:51 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id MAA06464 for current-outgoing; Sat, 3 Aug 1996 12:55:51 -0700 (PDT) Received: from vector.jhs.no_domain (slip139-92-42-176.ut.nl.ibm.net [139.92.42.176]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id MAA06438 for ; Sat, 3 Aug 1996 12:55:34 -0700 (PDT) Received: (from jhs@localhost) by vector.jhs.no_domain (8.7.5/8.6.9) id VAA19947; Sat, 3 Aug 1996 21:54:39 +0200 (MET DST) Date: Sat, 3 Aug 1996 21:54:39 +0200 (MET DST) Message-Id: <199608031954.VAA19947@vector.jhs.no_domain> To: current@freebsd.org Subject: rdist to freefall - fails with: version numbers don't match From: "Julian H. Stacey" Reply-To: "Julian H. Stacey" Organization: Vector Systems Ltd. Address: Holz Strasse 27d, 80469 Munich, Germany Phone: +49.89.268616 Fax: +49.89.2608126 Web: http://www.freebsd.org/~jhs/ Mailer: EXMH 1.6.7, PGP available Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Running `rdist' from my home box FreeBSD 2.2-CURRENT #0: Sun Jul 7 13:53:04 MSZ 1996 jhs@vector:/usr2/src/sys/compile/VECTOR to freefall FreeBSD 2.1.5-RELEASE #0: Wed Jul 17 08:04:27 PDT 1996 davidg@freefall.freebsd.org:/f/src/sys/compile/FREEFALL Fails like this: updating host freefall.cdrom.com rdist: connection failed: version numbers don't match rdist: got unexpected input:rdist: Crdist: Vrdist: Srdist: .... my same home box to 2 other boxes out on the net Succeed: gil.physik.rwth-aachen.de FreeBSD 2.1.0-RELEASE #0: Thu Dec 14 17:51:20 1995 kuku@blues.physik.rwth-aachen.de:/usr/src/sys/compile/GIL blues.physik.rwth-aachen.de: FreeBSD 2.2-CURRENT #0: Sat Jun 22 11:09:53 MET DST 1996 kuku@isdn-kukulies.dialup.rwth-aachen.de:\ /usr/src/sys/compile/BLUES my home current box to my home 2.1.0 box also succeeds. I've just done a cd src/usr.bin/rdist ; make ; make install, doesnt help, still fails, admittedly i havent reinstalled my include/ in a few weeks This is the first day Ive ever used rdist, seems a nice tool, shame it fails to freefall though, unfortunately I cant test it on thud, as my login there disappeared time of the last crash, way back when. Seems I'd better go read the rdist source (docmd.c), meantime this is a heads up, & comments are welcome, Thanks :-) Julian -- Julian H. Stacey jhs@freebsd.org http://www.freebsd.org/~jhs/ From owner-freebsd-current Sat Aug 3 13:10:30 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id NAA07684 for current-outgoing; Sat, 3 Aug 1996 13:10:30 -0700 (PDT) Received: from grumble.grondar.za (root@grumble.grondar.za [196.7.18.130]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id NAA07673 for ; Sat, 3 Aug 1996 13:10:25 -0700 (PDT) Received: from grumble.grondar.za (mark@localhost.grondar.za [127.0.0.1]) by grumble.grondar.za (8.7.5/8.7.3) with ESMTP id WAA00690; Sat, 3 Aug 1996 22:09:34 +0200 (SAT) Message-Id: <199608032009.WAA00690@grumble.grondar.za> To: "Marc G. Fournier" cc: current@freebsd.org Subject: Re: NIS Setup Question Date: Sat, 03 Aug 1996 22:09:31 +0200 From: Mark Murray Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk "Marc G. Fournier" wrote: > Now, for some reason that I've yet to figure, NIS doesn't > work right. > > I'm running 'rpc.yypasswdd -m /etc/master.passwd -s -f', so > that updates go properly to my /etc/master.passwd file, but if I try > to change a pasword on one of my client machines, I get, in > /var/log/messages on the server machine: RTFM - the right one! rpc.yppasswdd -t /etc/master.passwd -s -f ^ M -- Mark Murray 46 Harvey Rd, Claremont, Cape Town 7700, South Africa +27 21 61-3768 GMT+0200 Finger mark@grondar.za for PGP key From owner-freebsd-current Sat Aug 3 13:22:19 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id NAA08660 for current-outgoing; Sat, 3 Aug 1996 13:22:19 -0700 (PDT) Received: from quagmire.ki.net (root@quagmire.ki.net [205.150.102.51]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id NAA08648 for ; Sat, 3 Aug 1996 13:22:14 -0700 (PDT) Received: from localhost (scrappy@localhost) by quagmire.ki.net (8.7.5/8.7.5) with SMTP id QAA11718; Sat, 3 Aug 1996 16:22:02 -0400 (EDT) Date: Sat, 3 Aug 1996 16:22:01 -0400 (EDT) From: "Marc G. Fournier" To: Mark Murray cc: current@freebsd.org Subject: Re: NIS Setup Question In-Reply-To: <199608032009.WAA00690@grumble.grondar.za> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Sat, 3 Aug 1996, Mark Murray wrote: > "Marc G. Fournier" wrote: > > Now, for some reason that I've yet to figure, NIS doesn't > > work right. > > > > I'm running 'rpc.yypasswdd -m /etc/master.passwd -s -f', so > > that updates go properly to my /etc/master.passwd file, but if I try > > to change a pasword on one of my client machines, I get, in > > /var/log/messages on the server machine: > > RTFM - the right one! > > rpc.yppasswdd -t /etc/master.passwd -s -f > ^ First, thanks for pointing this out... Second, which is the right one? I just installed 2.2-SNAP from scratch, and the only 'man' that comes up is for yppasswdd *shrug* And finally...with -t, that is working now, which I thought would fix the problem I was having in the first place...I can't login to the NIS client machine (2.1-STABLE) Pointer to "the right RTFM" would be helpful, since it would probably answer more then just th eimmediate question, but... I can successfully change a users password from the client machine, but login fails. Both machines are using DES encryption vs MD5, which is the first thing I checked...does that even affect things if you use NIS? Since password changing does work, I would have thought that the rest would by default, but it seems I'm wrong on this? Oh, 'ls ~' resolves correctly also, only login doesn't seem to be working... So, either a pointer to the manual to read for this, or a pointer to what I should be looking at would be great... Thanks... Marc G. Fournier scrappy@ki.net Systems Administrator @ ki.net scrappy@freebsd.org From owner-freebsd-current Sat Aug 3 13:32:44 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id NAA10716 for current-outgoing; Sat, 3 Aug 1996 13:32:44 -0700 (PDT) Received: from grumble.grondar.za (root@grumble.grondar.za [196.7.18.130]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id NAA10620 for ; Sat, 3 Aug 1996 13:32:19 -0700 (PDT) Received: from grumble.grondar.za (mark@localhost.grondar.za [127.0.0.1]) by grumble.grondar.za (8.7.5/8.7.3) with ESMTP id WAA00812; Sat, 3 Aug 1996 22:31:47 +0200 (SAT) Message-Id: <199608032031.WAA00812@grumble.grondar.za> To: "Marc G. Fournier" cc: current@freebsd.org Subject: Re: NIS Setup Question Date: Sat, 03 Aug 1996 22:31:46 +0200 From: Mark Murray Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk "Marc G. Fournier" wrote: > > RTFM - the right one! > > > > rpc.yppasswdd -t /etc/master.passwd -s -f > > ^ > > First, thanks for pointing this out... Pleasure :-) > Second, which is the right one? I just installed 2.2-SNAP > from scratch, and the only 'man' that comes up is for yppasswdd *shrug* Er, the man page for rpc.yppasswdd? ^^^^ > And finally...with -t, that is working now, which I thought > would fix the problem I was having in the first place...I can't > login to the NIS client machine (2.1-STABLE) I can't duplicate this - I only have current. > Pointer to "the right RTFM" would be helpful, since it would > probably answer more then just th eimmediate question, but... When you do upgrades, it helps to go throug your system every now and then and delete cruft. That way, man -k cannot lie to you :-) In this case, the man pages for yppasswdd are no longer required, as is yppasswdd. Commit mail told us this... > I can successfully change a users password from the client > machine, but login fails. Both machines are using DES encryption > vs MD5, which is the first thing I checked...does that even affect > things if you use NIS? Since password changing does work, I would > have thought that the rest would by default, but it seems I'm > wrong on this? ??Dunno? > Oh, 'ls ~' resolves correctly also, only login > doesn't seem to be working... What does your "+" entry in your passwd file look like? > So, either a pointer to the manual to read for this, or > a pointer to what I should be looking at would be great... man -k yp Ignore the old stuff... M -- Mark Murray 46 Harvey Rd, Claremont, Cape Town 7700, South Africa +27 21 61-3768 GMT+0200 Finger mark@grondar.za for PGP key From owner-freebsd-current Sat Aug 3 13:44:05 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id NAA13151 for current-outgoing; Sat, 3 Aug 1996 13:44:05 -0700 (PDT) Received: from quagmire.ki.net (root@quagmire.ki.net [205.150.102.51]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id NAA13112 for ; Sat, 3 Aug 1996 13:44:01 -0700 (PDT) Received: from localhost (scrappy@localhost) by quagmire.ki.net (8.7.5/8.7.5) with SMTP id QAA12648; Sat, 3 Aug 1996 16:43:59 -0400 (EDT) Date: Sat, 3 Aug 1996 16:43:57 -0400 (EDT) From: "Marc G. Fournier" To: Mark Murray cc: current@freebsd.org Subject: Re: NIS Setup Question In-Reply-To: <199608032031.WAA00812@grumble.grondar.za> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Sat, 3 Aug 1996, Mark Murray wrote: > > Second, which is the right one? I just installed 2.2-SNAP > > from scratch, and the only 'man' that comes up is for yppasswdd *shrug* > > Er, the man page for rpc.yppasswdd? > ^^^^ the one that comes back: quagmire# man rpc.yppasswdd No manual entry for rpc.yppasswdd quagmire# uname -a FreeBSD quagmire.ki.net 2.2-960801-SNAP FreeBSD 2.2-960801-SNAP #0: Sat Aug 3 05:37:17 EDT 1996 scrappy@quagmire.ki.net:/usr/src/sys/compile/quagmire i386 quagmire# > > Pointer to "the right RTFM" would be helpful, since it would > > probably answer more then just th eimmediate question, but... > > When you do upgrades, it helps to go throug your system every now > and then and delete cruft. That way, man -k cannot lie to > you :-) > > In this case, the man pages for yppasswdd are no longer required, > as is yppasswdd. Commit mail told us this... > In this case, i didn't upgrade, I installed from -SNAP, onto a brand new drive..no rpc.yppasswdd man page, only yppasswdd :( > What does your "+" entry in your passwd file look like? +:+:::::::: Marc G. Fournier scrappy@ki.net Systems Administrator @ ki.net scrappy@freebsd.org From owner-freebsd-current Sat Aug 3 13:56:27 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id NAA14429 for current-outgoing; Sat, 3 Aug 1996 13:56:27 -0700 (PDT) Received: from grumble.grondar.za (root@grumble.grondar.za [196.7.18.130]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id NAA14413 for ; Sat, 3 Aug 1996 13:56:21 -0700 (PDT) Received: from grumble.grondar.za (mark@localhost.grondar.za [127.0.0.1]) by grumble.grondar.za (8.7.5/8.7.3) with ESMTP id WAA01311; Sat, 3 Aug 1996 22:55:43 +0200 (SAT) Message-Id: <199608032055.WAA01311@grumble.grondar.za> To: "Marc G. Fournier" cc: Mark Murray , current@freebsd.org Subject: Re: NIS Setup Question Date: Sat, 03 Aug 1996 22:55:42 +0200 From: Mark Murray Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk "Marc G. Fournier" wrote: > > Er, the man page for rpc.yppasswdd? > > ^^^^ > > the one that comes back: > > quagmire# man rpc.yppasswdd > No manual entry for rpc.yppasswdd > quagmire# uname -a > FreeBSD quagmire.ki.net 2.2-960801-SNAP FreeBSD 2.2-960801-SNAP #0: Sat Aug 3 05:37:17 EDT 1996 scrappy@quagmire.ki.net:/usr/src/sys/compile/quagmire i386 Problem with the SNAP? Dunno. I run -current, and I have that man page. What does man -k nis give? > > What does your "+" entry in your passwd file look like? > > +:+:::::::: ^ WTF is this? man 5 passwd explains what this should look like... M -- Mark Murray 46 Harvey Rd, Claremont, Cape Town 7700, South Africa +27 21 61-3768 GMT+0200 Finger mark@grondar.za for PGP key From owner-freebsd-current Sat Aug 3 14:05:33 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id OAA15065 for current-outgoing; Sat, 3 Aug 1996 14:05:33 -0700 (PDT) Received: from quagmire.ki.net (root@quagmire.ki.net [205.150.102.51]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id OAA15053 for ; Sat, 3 Aug 1996 14:05:29 -0700 (PDT) Received: from localhost (scrappy@localhost) by quagmire.ki.net (8.7.5/8.7.5) with SMTP id RAA12990; Sat, 3 Aug 1996 17:05:29 -0400 (EDT) Date: Sat, 3 Aug 1996 17:05:28 -0400 (EDT) From: "Marc G. Fournier" To: Mark Murray cc: current@freebsd.org Subject: Re: NIS Setup Question In-Reply-To: <199608032055.WAA01311@grumble.grondar.za> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Sat, 3 Aug 1996, Mark Murray wrote: > "Marc G. Fournier" wrote: > > Problem with the SNAP? Dunno. I run -current, and I have that man page. > What does man -k nis give? > Might be...man -k lists yppasswdd and not rpc.yppasswd, but there is no yppasswdd program, only rpc.yppasswd *shrug* > > > What does your "+" entry in your passwd file look like? > > > > +:+:::::::: > ^ > > WTF is this? > Ack..%^%#$^@^%@$^..that was it :( Fixed now, thanks... Marc G. Fournier scrappy@ki.net Systems Administrator @ ki.net scrappy@freebsd.org From owner-freebsd-current Sat Aug 3 15:53:14 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id PAA23303 for current-outgoing; Sat, 3 Aug 1996 15:53:14 -0700 (PDT) Received: from vector.jhs.no_domain (slip139-92-42-168.ut.nl.ibm.net [139.92.42.168]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id PAA23289 for ; Sat, 3 Aug 1996 15:53:03 -0700 (PDT) Received: from vector.jhs.no_domain (localhost [127.0.0.1]) by vector.jhs.no_domain (8.7.5/8.6.9) with ESMTP id AAA23680 for ; Sun, 4 Aug 1996 00:20:59 +0200 (MET DST) Message-Id: <199608032220.AAA23680@vector.jhs.no_domain> To: current@FreeBSD.org Subject: Re: rdist to freefall - fails with: version numbers don't match From: "Julian H. Stacey" Reply-To: "Julian H. Stacey" Organization: Vector Systems Ltd. Address: Holz Strasse 27d, 80469 Munich, Germany Phone: +49.89.268616 Fax: +49.89.2608126 Web: http://www.freebsd.org/~jhs/ Mailer: EXMH 1.6.7, PGP available In-reply-to: Your message of "Sat, 03 Aug 1996 21:54:39 +0200." <199608031954.VAA19947@vector.jhs.no_domain> Date: Sun, 04 Aug 1996 00:20:57 +0200 Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk Hi, Reference my own previous: > Running `rdist' from my home box ... > to freefall ... > Fails like this: ... > my same home box to 2 other boxes out on the net Succeed: ... Solution (Sigh ;-) My .cshrc was emitting a line (actually a printenv of a CVS var), ... that was enough to upset rdist. I discovered this after xxgdb said socket fail or some such; perhaps a rather unobvious error message for a normal user, & one we could improve on, but I feel silly not spotting it straight off ! Who's guarding the conical cap ? ... my turn for a short while :-) Here's a patch to apply, hopefully it's acceptable ? *** old/src/usr.bin/rdist/rdist.1 Sat Aug 3 23:55:31 1996 --- new/src/usr.bin/rdist/rdist.1 Sun Aug 4 00:15:02 1996 *************** *** 411,413 **** --- 411,438 ---- There should be a `force' option to allow replacement of non-empty directories by regular files or symlinks. A means of updating file modes and owners of otherwise identical files is also needed. + .Pp + .Nm Rdist + relies on + .Nm rsh(1) + type remote services executing succesfully & in silence. + If you try something like + .Bd -literal -offset indent + rsh freefall.freebsd.org hostname + .Ed + .sp + & get extra output before the program ( + .Nm hostname(1) + ) output, such as + .Bd -literal -offset indent + Text_perhaps_initiated_from_~/.cshrc_or_similar + freefall.freebsd.org + .Ed + .sp + then the unexpected extra text will cause + .Nm rdist + to fail with the (obscure) error message: + .Bd -literal -offset indent + rdist: connection failed: version numbers don't match + .Ed + .sp Julian -- Julian H. Stacey jhs@freebsd.org http://www.freebsd.org/~jhs/ From owner-freebsd-current Sat Aug 3 16:53:55 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id QAA26765 for current-outgoing; Sat, 3 Aug 1996 16:53:55 -0700 (PDT) Received: from time.cdrom.com (time.cdrom.com [204.216.27.226]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id QAA26760 for ; Sat, 3 Aug 1996 16:53:48 -0700 (PDT) Received: from time.cdrom.com (localhost [127.0.0.1]) by time.cdrom.com (8.7.5/8.6.9) with ESMTP id QAA28978; Sat, 3 Aug 1996 16:52:40 -0700 (PDT) To: Kim Culhan cc: current@FreeBSD.org Subject: Re: make world failure In-reply-to: Your message of "Sat, 03 Aug 1996 12:11:37 EDT." Date: Sat, 03 Aug 1996 16:52:39 -0700 Message-ID: <28976.839116359@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk "make bootstrap" > > This is from -current sup'd at ~1400 UTC this date: > > cc -O -c /usr/src/usr.bin/lex/lib/libyywrap.c -o libyywrap.o > building standard ln library > tsort: illegal option -- q > usage: tsort [-dl] [file] > ar: no archive members specified > usage: ar -d [-Tv] archive file ... > ar -m [-Tv] archive file ... > ar -m [-abiTv] position archive file ... > ar -p [-Tv] archive [file ...] > ar -q [-cTv] archive file ... > ar -r [-cuTv] archive file ... > ar -r [-abciuTv] position archive file ... > ar -t [-Tv] archive [file ...] > ar -x [-ouTv] archive [file ...] > *** Error code 1 > > Stop. > > > regards > kim > > -- > kimc@w8hd.org > > From owner-freebsd-current Sat Aug 3 16:55:30 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id QAA26806 for current-outgoing; Sat, 3 Aug 1996 16:55:30 -0700 (PDT) Received: from time.cdrom.com (time.cdrom.com [204.216.27.226]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id QAA26799 for ; Sat, 3 Aug 1996 16:55:21 -0700 (PDT) Received: from time.cdrom.com (localhost [127.0.0.1]) by time.cdrom.com (8.7.5/8.6.9) with ESMTP id QAA28991; Sat, 3 Aug 1996 16:54:16 -0700 (PDT) To: Kim Culhan cc: current@FreeBSD.org Subject: Re: fetch/main.c error In-reply-to: Your message of "Sat, 03 Aug 1996 12:26:43 EDT." Date: Sat, 03 Aug 1996 16:54:15 -0700 Message-ID: <28989.839116455@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk I'm not sure if it's worth adding libftpio to the bootstrap targets, but you need to remake it first. If you'd done a normal `make world', this would have happened automatically. Jordan > > This also from -current sup'd at ~1400 UTC this date: > > ===> fetch > cc -O -Wall -c /usr/src/usr.bin/fetch/main.c > /usr/src/usr.bin/fetch/main.c: In function `ftpget': > /usr/src/usr.bin/fetch/main.c:225: too many arguments to function > `ftpLogin' > *** Error code 1 > > Stop. > > > regards > kim > > -- > kimc@w8hd.org > > From owner-freebsd-current Sat Aug 3 16:56:09 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id QAA26881 for current-outgoing; Sat, 3 Aug 1996 16:56:09 -0700 (PDT) Received: from time.cdrom.com (time.cdrom.com [204.216.27.226]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id QAA26875 for ; Sat, 3 Aug 1996 16:56:02 -0700 (PDT) Received: from time.cdrom.com (localhost [127.0.0.1]) by time.cdrom.com (8.7.5/8.6.9) with ESMTP id QAA29008; Sat, 3 Aug 1996 16:54:50 -0700 (PDT) To: Kim Culhan cc: current@FreeBSD.org Subject: Re: make world failed -old tsort In-reply-to: Your message of "Sat, 03 Aug 1996 12:31:11 EDT." Date: Sat, 03 Aug 1996 16:54:50 -0700 Message-ID: <29006.839116490@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk You should subscribe to cvs-all - then you'd have seen me talking about this openly in my commit messages. Jordan > > Able to bootstrap past previously mentioned make world failure, > installed -current tsort first. > > Sorry to bother the list.. > > regards > kim > > -- > kimc@w8hd.org > > From owner-freebsd-current Sat Aug 3 20:11:53 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id UAA07406 for current-outgoing; Sat, 3 Aug 1996 20:11:53 -0700 (PDT) Received: from genesis.atrad.adelaide.edu.au (genesis.atrad.adelaide.edu.au [129.127.96.120]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id UAA07401 for ; Sat, 3 Aug 1996 20:11:49 -0700 (PDT) Received: from msmith@localhost by genesis.atrad.adelaide.edu.au (8.6.12/8.6.9) id MAA06694 for current@freebsd.org; Sun, 4 Aug 1996 12:52:44 +0930 From: Michael Smith Message-Id: <199608040322.MAA06694@genesis.atrad.adelaide.edu.au> Subject: problem with -current system grinding to a halt... To: current@freebsd.org Date: Sun, 4 Aug 1996 12:52:44 +0930 (CST) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I commented about this a day or few ago, but at that point I was still chasing other possibilities, so here I go again 8) I have a reasonably -curent system that, under moderate load is dying after about 18-20 hours of uptime. The system itself is a P120 on a Triton board with 64M and an NCR PCI controller : FreeBSD mstradar.esrange.ssc.se 2.2-CURRENT FreeBSD 2.2-CURRENT #0: Mon Jul 15 13:16:26 MET DST 1996 msmith@spore.atrad.adelaide.edu.au:/usr/work/radarsys/compile/MSTRADAR i386 The system is being pushed fairly lightly, although there are some long-lived processes that accumulate a lot of CPU (and have largeish swap footprints). These large processes are all Linux a.out binaries (IDL). Symptoms are that the system remains pingable, and you can often get through the telnet login sequence to the point where /usr/bin/login is invoked but no further. As I type, the system just died under me again; I was watching the output of 'systat -vmstat', quit and typed 'w' to check the load. I got this : mstradar:/home/radar>w 5:04AM up 19:28, 2 users, load averages: 0.00, 0.00, 0.00 USER TTY FROM LOGIN@ IDLE WHAT and then nothing more. There have been no console or syslog messages to date from any of the times that this has happened. Any suggestions as to where to start looking would be appreciated; unfortunately due to the rather remote location of the system I can't play DDB with it 8( Help? -- ]] Mike Smith, Software Engineer msmith@atrad.adelaide.edu.au [[ ]] Genesis Software genesis@atrad.adelaide.edu.au [[ ]] High-speed data acquisition and (GSM mobile) 0411-222-496 [[ ]] realtime instrument control (ph/fax) +61-8-267-3039 [[ ]] Collector of old Unix hardware. "Where are your PEZ?" The Tick [[ From owner-freebsd-current Sat Aug 3 20:41:37 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id UAA08621 for current-outgoing; Sat, 3 Aug 1996 20:41:37 -0700 (PDT) Received: from skynet.ctr.columbia.edu (skynet.ctr.columbia.edu [128.59.64.70]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id UAA08614 for ; Sat, 3 Aug 1996 20:41:29 -0700 (PDT) Received: (from wpaul@localhost) by skynet.ctr.columbia.edu (8.6.12/8.6.9) id XAA03565; Sat, 3 Aug 1996 23:41:16 -0400 From: Bill Paul Message-Id: <199608040341.XAA03565@skynet.ctr.columbia.edu> Subject: Re: NIS Setup Question To: scrappy@ki.net (Marc G. Fournier) Date: Sat, 3 Aug 1996 23:41:14 -0400 (EDT) Cc: current@freebsd.org In-Reply-To: from "Marc G. Fournier" at Aug 3, 96 05:05:28 pm X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Of all the gin joints in all the towns in all the world, Marc G. Fournier had to walk into mine and say: > On Sat, 3 Aug 1996, Mark Murray wrote: > > > "Marc G. Fournier" wrote: > > > > Problem with the SNAP? Dunno. I run -current, and I have that man page. > > What does man -k nis give? It should give nothing. Man -k nis will only be of interest if and when I finish NIS+. > Might be...man -k lists yppasswdd and not rpc.yppasswd, but > there is no yppasswdd program, only rpc.yppasswd *shrug* You have hosed your man pages or you need to re-run makewhatis (or, less likely, somebody screwed up the building of man pages in the distribution -- can't verify this as I haven't tried the SNAP yet). I promise you that there is an rpc.yppasswdd(8) man page. The original yppasswdd program in 2.1.x was called yppasswdd because that's what Olaf Kirch, the guy who wrote it, decided to name it. Since it wasn't my program, I preserved the name given to it by the author. Later, when I wrote my own server from scratch, I chose to call it rpc.yppasswdd, thus the program name and man page name are now different in -current. I tried to avoid changing the option flags from the old version, but I got stuck because I wanted to use the -m flag for 'multidomain' mode, but I had used it previously for a pointer to the 'master.passwd' template file in the old version. Finally I just said 'the heck with it' and I used -m for multidomain mode and substituted -t for the old -m (-t for 'specify Template file'). If you ever find the rpc.yppasswdd(8) man page, you may be surprised by all the new things it does. > > > > What does your "+" entry in your passwd file look like? > > > > > > +:+:::::::: > > ^ > > > > WTF is this? > > > Ack..%^%#$^@^%@$^..that was it :( Fixed now, thanks... *sigh* I keep telling people to read the damn passwd(5) man page and yet nobody ever seems to do it. It even says in big letters not to do stuff like this and everything. -Bill -- ============================================================================= -Bill Paul (212) 854-6020 | System Manager, Master of Unix-Fu Work: wpaul@ctr.columbia.edu | Center for Telecommunications Research Home: wpaul@skynet.ctr.columbia.edu | Columbia University, New York City ============================================================================= "If you're ever in trouble, go to the CTR. Ask for Bill. He will help you." ============================================================================= From owner-freebsd-current Sat Aug 3 21:31:51 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id VAA10674 for current-outgoing; Sat, 3 Aug 1996 21:31:51 -0700 (PDT) Received: from mexico.brainstorm.eu.org (root@mexico.brainstorm.eu.org [193.56.58.253]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id VAA10650 for ; Sat, 3 Aug 1996 21:31:46 -0700 (PDT) Received: from brasil.brainstorm.eu.org (brasil.brainstorm.eu.org [193.56.58.33]) by mexico.brainstorm.eu.org (8.7.5/8.7.3) with ESMTP id GAA26565; Sun, 4 Aug 1996 06:31:43 +0200 Received: (from uucp@localhost) by brasil.brainstorm.eu.org (8.6.12/8.6.12) with UUCP id GAA17627; Sun, 4 Aug 1996 06:31:21 +0200 Received: (from roberto@localhost) by keltia.freenix.fr (8.8.Alpha.7/keltia-uucp-2.9) id BAA16783; Sun, 4 Aug 1996 01:23:30 +0200 (MET DST) Message-Id: <199608032323.BAA16783@keltia.freenix.fr> Date: Sun, 4 Aug 1996 01:23:30 +0200 From: roberto@keltia.freenix.fr (Ollivier Robert) To: ernie@spooky.eis.net.au (Ernie Elu) Cc: freebsd-current@freebsd.org Subject: Re: Sup failing for sup.freebsd.org In-Reply-To: <199608031632.CAA08124@spooky.eis.net.au>; from Ernie Elu on Aug 4, 1996 2:32:50 +1000 References: <199608031632.CAA08124@spooky.eis.net.au> X-Mailer: Mutt 0.38 Mime-Version: 1.0 Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk According to Ernie Elu: > The point it the sup.au.freebsd.org files were unreliable in that instance > and I would be keen to know if there is any work around? I lost a lot of One way to possibly solve this is not to use SUP but try RSYNC. Instead of just looking at the file's date, it looks at the file itself and only send the diffs. It may be more relieable than SUP. I don't know about the load on the server though. I think it is worth the try... -- Ollivier ROBERT -=- The daemon is FREE! -=- roberto@keltia.freenix.fr FreeBSD keltia.freenix.fr 2.2-CURRENT #17: Fri Aug 2 20:40:17 MET DST 1996 From owner-freebsd-current Sat Aug 3 21:46:18 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id VAA11305 for current-outgoing; Sat, 3 Aug 1996 21:46:18 -0700 (PDT) Received: from time.cdrom.com (time.cdrom.com [204.216.27.226]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id VAA11300 for ; Sat, 3 Aug 1996 21:46:13 -0700 (PDT) Received: from time.cdrom.com (localhost [127.0.0.1]) by time.cdrom.com (8.7.5/8.6.9) with ESMTP id VAA29833; Sat, 3 Aug 1996 21:44:35 -0700 (PDT) To: roberto@keltia.freenix.fr (Ollivier Robert) cc: ernie@spooky.eis.net.au (Ernie Elu), freebsd-current@freebsd.org Subject: Re: Sup failing for sup.freebsd.org In-reply-to: Your message of "Sun, 04 Aug 1996 01:23:30 +0200." <199608032323.BAA16783@keltia.freenix.fr> Date: Sat, 03 Aug 1996 21:44:35 -0700 Message-ID: <29831.839133875@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > One way to possibly solve this is not to use SUP but try RSYNC. Instead of > just looking at the file's date, it looks at the file itself and only send > the diffs. It may be more relieable than SUP. I don't know about the load > on the server though. Or use cvsup. Jordan