From owner-freebsd-current  Sun Mar 17 00:15:49 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id AAA29056
          for current-outgoing; Sun, 17 Mar 1996 00:15:49 -0800 (PST)
Received: from grumble.grondar.za (root@grumble.grondar.za [196.7.18.130])
          by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id AAA29048
          for <current@freebsd.org>; Sun, 17 Mar 1996 00:15:42 -0800 (PST)
Received: from grumble.grondar.za (mark@localhost [127.0.0.1]) by grumble.grondar.za (8.7.5/8.7.3) with ESMTP id KAA20400 for <current@freebsd.org>; Sun, 17 Mar 1996 10:15:29 +0200 (SAT)
Message-Id: <199603170815.KAA20400@grumble.grondar.za>
To: current@freebsd.org
Subject: /dev/random - an idea/proposal
Date: Sun, 17 Mar 1996 10:15:27 +0200
From: Mark Murray <mark@grondar.za>
Sender: owner-current@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

Hi

I am not completely happy with my current method of selecting the
interrupts for /dev/random right now. (There is rndcontrol(8) with
some command-line switches, and sysconfig has a line to edit). It
is too easy to overlook, and I am very keen that /dev/random be seen
to provide a decent source of entropy.

I would like some way to be able to choose these at kernel build
time - ie at the time the system manager configures her kernel,
she nominates that a particular device's interrupts should be used.

This I would like to do by adding a keyword "random", syntactically
similar to "conflicts" to the config(8) grammar. This will then set
that device's interrupt on by default at boot time. This will not
interfere with rndcontrol(8), and the sysconfig section can/could
be removed/ignored (or at least it would be 'safer' to do so).

Comments? Flames? Praise? Ca$h?

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  Sun Mar 17 04:16:52 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id EAA11221
          for current-outgoing; Sun, 17 Mar 1996 04:16:52 -0800 (PST)
Received: from news1.gtn.com (news1.gtn.com [192.109.159.3])
          by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id EAA11215
          for <current@FreeBSD.org>; Sun, 17 Mar 1996 04:16:49 -0800 (PST)
Received: (from uucp@localhost) by news1.gtn.com (8.7.2/8.7.2) id NAA27725; Sun, 17 Mar 1996 13:00:19 +0100 (MET)
Received: from knobel.gun.de (localhost [127.0.0.1]) by knobel.gun.de (8.7.5/8.7.3) with SMTP id LAA00384; Sun, 17 Mar 1996 11:48:33 +0100 (MET)
Date: Sun, 17 Mar 1996 11:48:33 +0100 (MET)
From: Andreas Klemm <andreas@knobel.gun.de>
To: Bill Fenner <fenner@parc.xerox.com>
cc: current@FreeBSD.org
Subject: Re: mrouted: can't enable multicast routing in kernel: Operation not supported 
In-Reply-To: <96Mar14.164317pst.177478@crevenia.parc.xerox.com>
Message-ID: <Pine.BSF.3.91.960317114729.202A-100000@knobel.gun.de>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-current@FreeBSD.org
X-Loop: FreeBSD.org
Precedence: bulk

On Thu, 14 Mar 1996, Bill Fenner wrote:

> Did you accidentally remove "options MROUTING" from your kernel?  Perhaps 
> because of the new opt_<option>.h files and not having a sufficiently recent 
> config?

I wasn't as current as I ought to be ;-) I fixed it now by grabbing
the newest /etc/sysconfig.

	Andreas ///

--
andreas@knobel.gun.de         /\/\___      Wiechers & Partner Datentechnik GmbH
   Andreas Klemm          ___/\/\/         $$  Support Unix - aklemm@wup.de  $$
pgp p-key  http://www-swiss.ai.mit.edu/~bal/pks-toplev.html  >>> powered by <<<
ftp://sunsite.unc.edu/pub/Linux/system/Printing/aps-491.tgz  >>>    FreeBSD <<<
"Ich bleibe bei der Aussage und trotze den Flames. :-)"    Ulli Horlacher 02/96


From owner-freebsd-current  Sun Mar 17 10:22:20 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id KAA26762
          for current-outgoing; Sun, 17 Mar 1996 10:22:20 -0800 (PST)
Received: from rich.isdn.bcm.tmc.edu (root@RICH.ISDN.BCM.TMC.EDU [128.249.250.34])
          by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id KAA26757
          for <current@FreeBSD.org>; Sun, 17 Mar 1996 10:22:17 -0800 (PST)
Received: (from rich@localhost) by rich.isdn.bcm.tmc.edu (8.6.12/8.6.12) id MAA02841; Sun, 17 Mar 1996 12:22:10 -0600
Date: Sun, 17 Mar 1996 12:22:10 -0600
Message-Id: <199603171822.MAA02841@rich.isdn.bcm.tmc.edu>
From: Rich Murphey <rich@rich.isdn.bcm.tmc.edu>
To: graichen@omega.physik.fu-berlin.de
CC: current@FreeBSD.org
In-reply-to: <4ib6oq$32h@mordillo.physik.fu-berlin.de>
	(graichen@omega.physik.fu-berlin.de)
Subject: Re: Mathematica under FreeBSD
Reply-to: rich@lamprey.utmb.edu
Sender: owner-current@FreeBSD.org
X-Loop: FreeBSD.org
Precedence: bulk

|From: graichen@omega.physik.fu-berlin.de (Thomas Graichen)
|: I run 'Mathematica 2.2 for Linux (x86)' on
|: FreeBSD-stable and everything including the x front end
|: (mathematica and mathbook) work just fine.  Rich
|
|could you please send a short report about what is required to get ot working
|?

Sorry if this is a repeat from what was mentioned on
FreeBSD-hackers, but since you asked here, here's the
scoop..

Each of the programs (math, mathematica and mathbook) are shell
scripts which in turn invoke the binaries.  In each of these I added
the following at the head of the script:

RESOLV_HOST_CONF=/compat/linux/etc/host.conf; export RESOLV_HOST_CONF
XKEYSYMDB=/usr/site/math22/lib/X11/XKeysymDB; export XKEYSYMDB

where /compat/linux/etc/host.conf can be created using:

echo 'order bind,hosts' > /compat/linux/etc/host.conf 

or just 'order hosts' if you aren't using DNS.

/usr/site/math22/lib/X11/XKeysymDB is a file that came
with mathematica.  Your directory layout may be
different and you'll have to find it and adjust
accordingly.

The binaries are staticly linked, so you don't have to
obtain any runtime libraries for them.

Rich

From owner-freebsd-current  Sun Mar 17 10:59:52 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id KAA28896
          for current-outgoing; Sun, 17 Mar 1996 10:59:52 -0800 (PST)
Received: from vector.jhs.local (slip139-92-18-129.pt.uk.ibm.net [139.92.18.129])
          by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id KAA28880
          Sun, 17 Mar 1996 10:59:25 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by vector.jhs.local (8.7.3/8.6.9) with SMTP id WAA03007; Sat, 9 Mar 1996 22:16:22 +0100 (MET)
Message-Id: <199603092116.WAA03007@vector.jhs.local>
X-Authentication-Warning: vector.jhs.local: Host localhost [127.0.0.1] didn't use HELO protocol
To: Terry Lambert <terry@lambert.org>
cc: handy@sag.space.lockheed.com (Brian N. Handy), freebsd-current@FreeBSD.org
Subject: Re: Whee! Page Fault! 
From: "Julian H. Stacey" <jhs@FreeBSD.org>
Reply-To: "Julian H. Stacey" <jhs@FreeBSD.org>
Organization: Vector Systems Ltd.
Address: Holz Strasse 27d, 80469 Munich, Germany
Phone: +49.89.268616
Fax: +49.89.2608126 (pending modem change)
Web: http://www.freebsd.org/~jhs/
Mailer: EXMH version 1.6.5  95 12 11,  PGP available
In-reply-to: Your message of "Wed, 06 Mar 1996 12:32:28 MST."
             <199603061932.MAA11620@phaeton.artisoft.com> 
Date: Sat, 09 Mar 1996 22:16:21 +0100
Sender: owner-current@FreeBSD.org
X-Loop: FreeBSD.org
Precedence: bulk

THIS MAIL WAS DELAYED BY A MAIILER CONFIGURATION PROBLEM - SORRY ....

Hi, Reference:
> From: Terry Lambert <terry@lambert.org> 
> Subject: Re: Whee! Page Fault! 

> > I did an 'ls' on the CD and got a page fault, kernel panic, a window of
> > goodies flies by and I reboot.  I haven't had a kernel panic in so long, I
> > figured maybe I'd better report this one to someone.  SOOOO...here's what
> > we'll put here: 
> 
> [ ... ]
> 
> Off hand, I suspect the CD9660 FS of being unstable, but maybe that's
> just me being prejudiced against grody code...
> 
FYI
I just got a repeatable system freeze while doing (on a simtel cd-rom)
	cd /cd/_/msdos/memutils
	vi descript.ion
Curiously though this worked fine:
	tar cvf - . | ( cd /usr3/tmp/memutil ; tar xf - )
	cd /usr3/tmp/memutil
	vi descript.ion
I'm running current from maybe 6/8 weeks back.
I have no more detail to provide, sorry 
(this err. was on my stable (no not `Stable') `good' system,
my other unstable `sick' freebsd box is consuming my free time,
so have no time to investigate)

Julian
--
Julian H. Stacey	jhs@freebsd.org  	http://www.freebsd.org/~jhs/

From owner-freebsd-current  Sun Mar 17 12:54:24 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id MAA04945
          for current-outgoing; Sun, 17 Mar 1996 12:54:24 -0800 (PST)
Received: from veda.is (root@ubiq.veda.is [193.4.230.60])
          by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id MAA04930
          Sun, 17 Mar 1996 12:54:14 -0800 (PST)
Received: (from adam@localhost) by veda.is (8.7.4/8.7.3) id UAA07726; Sun, 17 Mar 1996 20:54:02 GMT
From: Adam David <adam@veda.is>
Message-Id: <199603172054.UAA07726@veda.is>
Subject: March 14th kernel, page faults
To: freebsd-current@freebsd.org
Date: Sun, 17 Mar 1996 20:54:00 +0000 (GMT)
Cc: dyson@freebsd.org
X-Mailer: ELM [version 2.4ME+ PL10 (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 5 crash dumps from 3 days running the March 14th kernel. It is always
a pagefault that takes it out.

(kgdb) bt
#0  boot (howto=256) at ../../i386/i386/machdep.c:935
#1  0xf01125b6 in panic (fmt=0xf0173e2c "page fault")
    at ../../kern/subr_prf.c:127
#2  0xf017495e in trap_fatal (frame=0xefbffeec) at ../../i386/i386/trap.c:758
#3  0xf01744d0 in trap_pfault (frame=0xefbffeec, usermode=0)
    at ../../i386/i386/trap.c:680
#4  0xf017415b in trap (frame={tf_es = 262160, tf_ds = -2147483632,
      tf_edi = -2147483648, tf_esi = -272642048, tf_ebp = -272629964,
      tf_isp = -272629996, tf_ebx = -266342240, tf_edx = -259002524,
      tf_ecx = -203251712, tf_eax = 0, tf_trapno = 12, tf_err = 5439488,
      tf_eip = -266915382, tf_cs = -266731512, tf_eflags = 66118,
      tf_esp = -266513952, tf_ss = 348}) at ../../i386/i386/trap.c:319
#5  0xf016d181 in calltrap ()
#6  0xf016a4dc in vm_pageout_scan () at ../../vm/vm_pageout.c:706
#7  0xf016a900 in vm_pageout () at ../../vm/vm_pageout.c:896
#8  0xf01045a6 in kproc_start (udata=0xf0195730) at ../../kern/init_main.c:255
#9  0xf0104544 in main (framep=0xefbfffb8) at ../../kern/init_main.c:205
(kgdb)

What else do you need?

--
Adam David <adam@veda.is>

From owner-freebsd-current  Sun Mar 17 13:35:50 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id NAA07656
          for current-outgoing; Sun, 17 Mar 1996 13:35:50 -0800 (PST)
Received: from ki.net (root@ki.net [142.77.249.8])
          by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id NAA07617
          Sun, 17 Mar 1996 13:34:47 -0800 (PST)
Received: (from scrappy@localhost) by ki.net (8.7.4/8.7.4) id QAA00531; Sun, 17 Mar 1996 16:34:24 -0500 (EST)
Date: Sun, 17 Mar 1996 16:34:23 -0500 (EST)
From: "Marc G. Fournier" <scrappy@ki.net>
To: stable@freebsd.org
cc: current@freebsd.org
Subject: pmap_clear_reference panic in -stable...
Message-ID: <Pine.BSF.3.91.960317163115.263A-100000@ki.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-current@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk


Hi...

	Not sure if there is active development going on in -stable, or
if its just stuff brought over from -current, so I'm sending this to
both addresses.

	Using the March 15th -stable sources to build the following kernel,
I arrived at the office to a system panic, as detailed in my PR submitted.

	I'm unable to get any savecore core dump using a -stable kernel, but
-current has been giving me one, so is there a bug with -stable that is
preventing this from working?  All I'm able to give is DDB output, and
the only thing in DDB that I know to "give" is the 'trace' output...is there
something else I can do in DDB to give more information for PRs?

	Here's the PR...

----[ PR ]----

>Submitter-Id:   current-users
>Originator:     Marc G. Fournier
>Organization:   <Organization of PR author (multiple lines)>
>Confidential:   no
>Synopsis:       PANIC: pagedaemon/_pmap_clear_reference+0xb2
>Severity:       critical
>Priority:       high
>Category:       kern
>Release:        FreeBSD 2.1-STABLE i386
>Class:          sw-bug 
>Environment: 


FreeBSD 2.1-STABLE #4: Sat Mar 16 17:16:06 EST 1996
    scrappy@ki.net:/usr/src/sys/compile/kinet
CPU: i486 DX4 (486-class CPU)
  Origin = "GenuineIntel"  Id = 0x480  Stepping=0
  Features=0x3<FPU,VME>
real memory  = 16777216 (16384K bytes)
avail memory = 14704640 (14360K bytes)
Probing for devices on PCI bus 0:
chip0 <SiS 85c496> rev 49 on pci0:5
ncr0 <ncr 53c810 scsi> rev 2 int a irq 12 on pci0:11
ncr0 waiting for scsi devices to settle
(ncr0:0:0): "CONNER CFP1060S 1.05GB 243F" type 0 fixed SCSI 2
sd0(ncr0:0:0): Direct-Access 
sd0(ncr0:0:0): FAST SCSI-2 100ns (10 Mb/sec) offset 8.
1013MB (2074880 512 byte sectors)
(ncr0:1:0): "QUANTUM LPS340S 020B" type 0 fixed SCSI 2
sd1(ncr0:1:0): Direct-Access 
sd1(ncr0:1:0): FAST SCSI-2 100ns (10 Mb/sec) offset 8.
327MB (670506 512 byte sectors)
(ncr0:2:0): "QUANTUM LP240S GM240S01X 4.6" type 0 fixed SCSI 2
sd2(ncr0:2:0): Direct-Access 
sd2(ncr0:2:0): FAST SCSI-2 100ns (10 Mb/sec) offset 8.
234MB (479350 512 byte sectors)
(ncr0:3:0): "CONNER CFA540S 13B0" type 0 fixed SCSI 2
sd3(ncr0:3:0): Direct-Access 
sd3(ncr0:3:0): FAST SCSI-2 100ns (10 Mb/sec) offset 8.
515MB (1056708 512 byte sectors)
vga0 <VGA-compatible display device> rev 0 on pci0:15
Probing for devices on the ISA bus:
ed0 at 0x280-0x29f irq 5 maddr 0xd8000 msize 16384 on isa
ed0: address 00:00:c0:86:44:79, type WD8013EPC (16 bit) 
vt0 at 0x60-0x6f irq 1 on motherboard
vt0: generic, 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 72065B
fd0: 1.44MB 3.5in
aha0 not found at 0x330
npx0 on motherboard
npx0: INT 16 interface

>Description: 

Am currently unable to gain a "savecore" core dump after ddb in -stable, so
all I have to give is this DDB output.  

Fatal trap 12: page fault while in kernel mode
fault virtual address	= 0xf48e1000
fault code		= supervisor read, page not present
instruction pointer	= 0x8:0xf019c666
code segment		= base 0x0, limit 0xfffff, type 0x1b
			= DPL 0, pres 1, def32 1, gran 1
processor eflags	= interrupt enabled, resume, IOPL = 0
current process		= 2 (pagedaemon)
interrupts enabled	= net tty bio
Stopped at _pmap_clear_reference+0xb2: cmpl $0,0(%edx,%eax,4)
db>tra
_pmap_clear_reference(333000) at pmap_clear_reference+0xb2
_vm_pageout_scan() at vm_pageout_scan+0x38e
_vm_pageout() at vm_pageout+0x1b8
_main() at main+0x46f
begin at begin+0x6b

>How-To-Repeat: 

	<Code/input/activities to reproduce the problem (multiple lines)>

>Fix: 
	
	<How to correct or work around the problem, if known (multiple lines)>

---[ end PR ]---

Marc G. Fournier | POP Mail  Telnet Acct  DNS Hosting
System           |  WWW Services   Database Services  | Knowledge, 
  Administrator  |                                    | Information and
 scrappy@ki.net  |      WWW: http://www.ki.net        | Communications, Inc


From owner-freebsd-current  Sun Mar 17 13:54:10 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id NAA09154
          for current-outgoing; Sun, 17 Mar 1996 13:54:10 -0800 (PST)
Received: from ki.net (root@ki.net [142.77.249.8])
          by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id NAA09061
          for <current@freebsd.org>; Sun, 17 Mar 1996 13:52:43 -0800 (PST)
Received: (from scrappy@localhost) by ki.net (8.7.4/8.7.4) id QAA00899; Sun, 17 Mar 1996 16:46:28 -0500 (EST)
Date: Sun, 17 Mar 1996 16:46:27 -0500 (EST)
From: "Marc G. Fournier" <scrappy@ki.net>
To: Bill Paul <wpaul@skynet.ctr.columbia.edu>
cc: current@freebsd.org
Subject: Re: chpass in -current breaks make
In-Reply-To: <199603170112.UAA14013@skynet.ctr.columbia.edu>
Message-ID: <Pine.BSF.3.91.960317164552.263C-100000@ki.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-current@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

On Sat, 16 Mar 1996, Bill Paul wrote:

> Please: this has already been addressed in this list several times.
> 
> You are using the old rpcgen and the old /usr/include/rpcsvc/*.h
> header files. Build and install the _new_ rpcgen and use it to build
> and install /usr/include/rpcsvc/*.h. Then everything will compile
> normally.
>
	Apologies...I had installed the new rpcgen, but failed to re
install the include files :(

Marc G. Fournier | POP Mail  Telnet Acct  DNS Hosting
System           |  WWW Services   Database Services  | Knowledge, 
  Administrator  |                                    | Information and
 scrappy@ki.net  |      WWW: http://www.ki.net        | Communications, Inc


From owner-freebsd-current  Sun Mar 17 14:50:55 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id OAA11775
          for current-outgoing; Sun, 17 Mar 1996 14:50:55 -0800 (PST)
Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11])
          by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id OAA11764
          Sun, 17 Mar 1996 14:50:51 -0800 (PST)
Received: from sax.sax.de by irz301.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id XAA06551; Sun, 17 Mar 1996 23:50:45 +0100
Received: by sax.sax.de (8.6.11/8.6.12-s1) with UUCP
	id XAA27653; Sun, 17 Mar 1996 23:50:45 +0100
Received: (from j@localhost) by uriah.heep.sax.de (8.7.4/8.6.9) id XAA22844; Sun, 17 Mar 1996 23:49:33 +0100 (MET)
From: J Wunsch <j@uriah.heep.sax.de>
Message-Id: <199603172249.XAA22844@uriah.heep.sax.de>
Subject: Re: March 14th kernel, page faults
To: adam@veda.is (Adam David)
Date: Sun, 17 Mar 1996 23:49:33 +0100 (MET)
Cc: freebsd-current@freebsd.org, dyson@freebsd.org
Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch)
In-Reply-To: <199603172054.UAA07726@veda.is> from "Adam David" at Mar 17, 96 08:54:00 pm
X-Phone: +49-351-2012 669
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

As Adam David wrote:
> I have 5 crash dumps from 3 days running the March 14th kernel. It is always
> a pagefault that takes it out.
> 
> (kgdb) bt
> #0  boot (howto=256) at ../../i386/i386/machdep.c:935
> #1  0xf01125b6 in panic (fmt=0xf0173e2c "page fault")
>     at ../../kern/subr_prf.c:127
> #2  0xf017495e in trap_fatal (frame=0xefbffeec) at ../../i386/i386/trap.c:758
> #3  0xf01744d0 in trap_pfault (frame=0xefbffeec, usermode=0)
>     at ../../i386/i386/trap.c:680
> #4  0xf017415b in trap (frame={tf_es = 262160, tf_ds = -2147483632,
>       tf_edi = -2147483648, tf_esi = -272642048, tf_ebp = -272629964,
>       tf_isp = -272629996, tf_ebx = -266342240, tf_edx = -259002524,
>       tf_ecx = -203251712, tf_eax = 0, tf_trapno = 12, tf_err = 5439488,
>       tf_eip = -266915382, tf_cs = -266731512, tf_eflags = 66118,
>       tf_esp = -266513952, tf_ss = 348}) at ../../i386/i386/trap.c:319
> #5  0xf016d181 in calltrap ()

> What else do you need?

up 5
frame frame->tf_ebp frame->tf_eip

should get you to the failing piece of 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. ;-)

From owner-freebsd-current  Sun Mar 17 16:45:30 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id QAA18596
          for current-outgoing; Sun, 17 Mar 1996 16:45:30 -0800 (PST)
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id QAA18581
          Sun, 17 Mar 1996 16:45:28 -0800 (PST)
Date: Sun, 17 Mar 1996 16:45:28 -0800 (PST)
Message-Id: <199603180045.QAA18581@freefall.freebsd.org>
To: freebsd-current
From: Majordomo@FreeBSD.ORG
Subject: Welcome to freebsd-current
Reply-To: Majordomo@FreeBSD.ORG
Sender: owner-current@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

--

Welcome to the freebsd-current mailing list!

If you ever want to remove yourself from this mailing list,
you can send mail to "Majordomo@FreeBSD.ORG" with the following command
in the body of your email message:

    unsubscribe freebsd-current freebsd-current

Here's the general information for the list you've
subscribed to, in case you don't already have it:

FREEBSD-CURRENT                 Discussions about the use of FreeBSD-current
This is the mailing list for users of freebsd-current.  It includes
warnings about new features coming out in -current that will affect the
users, and instructions on steps that must be taken to remain -current.
Anyone running "current" must subscribe to this list.

From owner-freebsd-current  Sun Mar 17 17:09:39 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id RAA19780
          for current-outgoing; Sun, 17 Mar 1996 17:09:39 -0800 (PST)
Received: (from jmb@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id RAA19773
          for freebsd-current; Sun, 17 Mar 1996 17:09:38 -0800 (PST)
From: "Jonathan M. Bresler" <jmb>
Message-Id: <199603180109.RAA19773@freefall.freebsd.org>
Subject: icurrent subscribed to current--fixed
To: freebsd-current
Date: Sun, 17 Mar 1996 17:09:37 -0800 (PST)
X-Mailer: ELM [version 2.4 PL24]
Content-Type: text
Sender: owner-current@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

	mea culpa.  i have corrected my mistake.
	freebsd-current is not subscribed to freebsd-current.
	please disregard the announcement from majordomo

-- 
Jonathan M. Bresler           FreeBSD Postmaster             jmb@FreeBSD.ORG
FreeBSD--4.4BSD Unix for PC clones, source included. http://www.freebsd.org/

From owner-freebsd-current  Sun Mar 17 22:24:03 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id WAA02406
          for current-outgoing; Sun, 17 Mar 1996 22:24:03 -0800 (PST)
Received: from grumble.grondar.za (root@grumble.grondar.za [196.7.18.130])
          by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id WAA02359
          for <current@freebsd.org>; Sun, 17 Mar 1996 22:23:53 -0800 (PST)
Received: from grumble.grondar.za (mark@localhost [127.0.0.1]) by grumble.grondar.za (8.7.5/8.7.3) with ESMTP id IAA03506 for <current@freebsd.org>; Mon, 18 Mar 1996 08:23:30 +0200 (SAT)
Message-Id: <199603180623.IAA03506@grumble.grondar.za>
To: current@freebsd.org
Subject: Firewall setup...
Date: Mon, 18 Mar 1996 08:23:29 +0200
From: Mark Murray <mark@grondar.za>
Sender: owner-current@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

Hi

As I have a leased line to the net, andas my home net is frequently
unsupervised, I am pretty paranoid about security. So, I have decided
to add one more layer of protection, a firewall. I _love_ the FreeBSD
firewall setup! It took me about an hour from having never setup such
a thing before to having the rudiments working pretty well:

> 00200 deny all from 10.0.0.0/8 to any
> 00300 deny all from 172.16.0.0/16 to any
> 00400 deny all from 192.168.0.0/16 to any
> 00500 deny all from any to 10.0.0.0/8
> 00600 deny all from any to 172.16.0.0/16
> 00700 deny all from any to 192.168.0.0/16
> 00800 deny all from any to 127.0.0.0/8 via tun0
> 00900 deny all from any to 127.0.0.0/8 via ed0
> 01000 deny all from any to 0.0.0.0/8
> 01100 deny all from 127.0.0.0/8 to any via tun0
> 01200 deny all from 127.0.0.0/8 to any via ed0
> 01300 deny all from 0.0.0.0/8 to any

It is however not that clear how to do the last bit. I would like
to zap spoofing -

> 01350 accept all from any to 196.7.18.0/24 via tun0
> 01350 accept all from 196.7.18.0/24 to any via tun0

If my firewall machine has 2 interfaces - tun0=196.7.18.65
and ed0=196.7.18.129 with a netmask of 0xfffffff0, how do I prevent
packets claiming to be from 196.7.18/24 from coming into tun0?
The above 2 lines are necessary for me to communicate with the world.

Are there any other "standard" anti spoofing rules that can be
applied? I am basically running my firewall as a serious filter, rather
than as a closed-to-the-world firewall.

> 01500 accept all from any to any via ed0
> 01700 accept all from any to any via lo0
> 65535 deny all from any to any

(I based most of this on a script by PST about 2 months ago(?), but
that was before PHK's reorg of the sorting rules, and the sytax has
changed quite a bit since then.)

Thanks!

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  Sun Mar 17 22:28:49 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id WAA02486
          for current-outgoing; Sun, 17 Mar 1996 22:28:49 -0800 (PST)
Received: from neon.Glock.COM (root@neon.glock.com [198.82.228.159])
          by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id WAA02480
          Sun, 17 Mar 1996 22:28:47 -0800 (PST)
Received: (from mmead@localhost) by neon.Glock.COM (8.7.4/8.7.3) id BAA00389; Mon, 18 Mar 1996 01:28:45 -0500 (EST)
From: "matthew c. mead" <mmead@Glock.COM>
Message-Id: <199603180628.BAA00389@neon.Glock.COM>
Subject: a little more jaz drive info
To: scsi@freebsd.org
Date: Mon, 18 Mar 1996 01:28:45 -0500 (EST)
Cc: current@freebsd.org
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

    Ok, I booted under a 2.1.0R kernel, and found that both my
SyQuest EZ135 Drive and my JAZ drive now are able to be mounted,
unmounted, ejected, and inserted multiple times.  It's pretty clear
now that there's some sort of subtle problem with telling removeable
scsi devices they're no longer being used once they're umounted
under -current.  This is probably something we want to fix for the
snapshot coming this week, so if someone could help me out with
what files to start looking through in the /sys/scsi directory,
I'll see if I can turn anything up.  Thanks for listening to all
this spam!


-matt

PS - I've CC'd this to current@freebsd.org because I believe it
to be important to the development issues being discussed there.
If repliers want to remove the CC feel free.

-- 
Matthew C. Mead

mmead@Glock.COM
http://www.Glock.COM/~mmead/

From owner-freebsd-current  Sun Mar 17 22:48:31 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id WAA03172
          for current-outgoing; Sun, 17 Mar 1996 22:48:31 -0800 (PST)
Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19])
          by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id WAA03167
          for <current@freebsd.org>; Sun, 17 Mar 1996 22:48:28 -0800 (PST)
Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.12/8.6.9) id RAA10248; Mon, 18 Mar 1996 17:44:15 +1100
Date: Mon, 18 Mar 1996 17:44:15 +1100
From: Bruce Evans <bde@zeta.org.au>
Message-Id: <199603180644.RAA10248@godzilla.zeta.org.au>
To: current@freebsd.org, mark@grondar.za
Subject: Re: /dev/random - an idea/proposal
Sender: owner-current@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

>I am not completely happy with my current method of selecting the
>interrupts for /dev/random right now. (There is rndcontrol(8) with
>some command-line switches, and sysconfig has a line to edit). It
>is too easy to overlook, and I am very keen that /dev/random be seen
>to provide a decent source of entropy.

Neither am I, for the opposite reasons :-).  The default sysconfig
setting of rand_irqs is almost useless except to print an annoying
message to announce rndcontrol (add_keyboard_randomness() calls
add_timer_randomness() a nearly constant number of usec before
add_interrupt_randomness() for the keyboard interrupt calls
add_timer_randomness()).

>I would like some way to be able to choose these at kernel build
>time - ie at the time the system manager configures her kernel,
>she nominates that a particular device's interrupts should be used.

>This I would like to do by adding a keyword "random", syntactically
>similar to "conflicts" to the config(8) grammar. This will then set

This would be far too much trouble.  As well as hacking config, you
would have to:
- fix the problems that stop "conflicts" from working for PCI and
  EISA devices
- update userconfig and dset to support the new flag

A kernel option to set a bitmap of the interrupts used to generate
randomness would be easier to implement, but it would be easier to
overlook than rndcontrol(8).

Bruce

From owner-freebsd-current  Mon Mar 18 00:10:23 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id AAA06555
          for current-outgoing; Mon, 18 Mar 1996 00:10:23 -0800 (PST)
Received: from mail.rwth-aachen.de (mail.RWTH-Aachen.DE [137.226.144.9])
          by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id AAA06550
          for <freebsd-current@freefall.FreeBSD.org>; Mon, 18 Mar 1996 00:10:15 -0800 (PST)
Received: from gilberto.physik.rwth-aachen.de (gilberto.physik.rwth-aachen.de)
 by mail.rwth-aachen.de (PMDF V5.0-4 #13110)
 id <01I2H8VZ456O0019OX@mail.rwth-aachen.de> for
 freebsd-current@freefall.FreeBSD.org; Mon, 18 Mar 1996 09:13:14 +0100
Received: (from kuku@localhost) by gilberto.physik.rwth-aachen.de
 (8.6.11/8.6.9) id JAA12192 for freebsd-current@freefall.cdrom.com; Mon,
 18 Mar 1996 09:08:49 +0100
Date: Mon, 18 Mar 1996 09:08:49 +0100
From: "Christoph P. Kukulies" <kuku@gilberto.physik.rwth-aachen.de>
Subject: ldconfig -m after world build
To: freebsd-current@freefall.FreeBSD.org
Message-id: <199603180808.JAA12192@gilberto.physik.rwth-aachen.de>
Content-transfer-encoding: 7BIT
Sender: owner-current@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

Suggestion:

Add an ldconfig -m after the world has been built in the /usr/src/Makefile.

It would do no harm in a running 2.2 system and results in friendlier
rlogin behaviour after a 2.1->2.2 migration. Maybe it would be
already appropriate after the libs have been installed during world build.

--Chris Christoph P. U. Kukulies kuku@gil.physik.rwth-aachen.de

From owner-freebsd-current  Mon Mar 18 00:14:41 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id AAA06774
          for current-outgoing; Mon, 18 Mar 1996 00:14:41 -0800 (PST)
Received: from tfs.com (tfs.com [140.145.250.1])
          by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id AAA06769
          for <current@freebsd.org>; Mon, 18 Mar 1996 00:14:39 -0800 (PST)
Received: from critter.tfs.com by tfs.com (smail3.1.28.1) with SMTP
	id m0tya5K-0003w1C; Mon, 18 Mar 96 00:14 PST
Received: from localhost.tfs.com (localhost.tfs.com [127.0.0.1]) by critter.tfs.com (8.6.12/8.6.12) with SMTP id HAA07211; Mon, 18 Mar 1996 07:03:34 GMT
X-Authentication-Warning: critter.tfs.com: Host localhost.tfs.com didn't use HELO protocol
To: Mark Murray <mark@grondar.za>
cc: current@freebsd.org
Subject: Re: Firewall setup... 
In-reply-to: Your message of "Mon, 18 Mar 1996 08:23:29 +0200."
             <199603180623.IAA03506@grumble.grondar.za> 
Date: Mon, 18 Mar 1996 07:03:33 +0000
Message-ID: <7209.827132613@critter.tfs.com>
From: Poul-Henning Kamp <phk@critter.tfs.com>
Sender: owner-current@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

> It is however not that clear how to do the last bit. I would like
> to zap spoofing -
> 
> > 01350 accept all from any to 196.7.18.0/24 via tun0
> > 01350 accept all from 196.7.18.0/24 to any via tun0
> 
> If my firewall machine has 2 interfaces - tun0=196.7.18.65
> and ed0=196.7.18.129 with a netmask of 0xfffffff0, how do I prevent
> packets claiming to be from 196.7.18/24 from coming into tun0?
> The above 2 lines are necessary for me to communicate with the world.
    01355 deny all from 196.7.18/24 to any in via tun0
					   ^^
If it doesn't work, yell.

--
Poul-Henning Kamp           | phk@FreeBSD.ORG       FreeBSD Core-team.
http://www.freebsd.org/~phk | phk@login.dknet.dk    Private mailbox.
whois: [PHK]                | phk@ref.tfs.com       TRW Financial Systems, Inc.
Future will arrive by its own means, progress not so.

From owner-freebsd-current  Mon Mar 18 02:40:03 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id CAA14956
          for current-outgoing; Mon, 18 Mar 1996 02:40:03 -0800 (PST)
Received: from phoenix.csie.nctu.edu.tw (root@phoenix.csie.nctu.edu.tw [140.113.17.171])
          by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id CAA14905
          for <freebsd-current@FreeBSD.ORG>; Mon, 18 Mar 1996 02:40:00 -0800 (PST)
Received: from FreeBSD.csie.NCTU.edu.tw (root@freebsd.csie.nctu.edu.tw [140.113.235.250]) by phoenix.csie.nctu.edu.tw (8.6.11/8.6.4) with ESMTP id SAA00483 for <freebsd-current@FreeBSD.ORG>; Mon, 18 Mar 1996 18:40:13 +0800
Received: (from jdli@localhost) by FreeBSD.csie.NCTU.edu.tw (8.7.3/8.7.3) id SAA01078 for freebsd-current@FreeBSD.ORG; Mon, 18 Mar 1996 18:40:04 +0800 (CST)
From: Jian-Da Li <jdli@FreeBSD.csie.NCTU.edu.tw>
Message-Id: <199603181040.SAA01078@FreeBSD.csie.NCTU.edu.tw>
Subject: YP/NIS Problem
To: freebsd-current@FreeBSD.ORG
Date: Mon, 18 Mar 1996 18:40:04 +0800 (CST)
X-Mailer: ELM [version 2.4ME+ PL11 (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 :

	I am setting up a self-nis client/server. (ie. the host runs both
	ypbind and ypserv)

	I am running a CURRENT at 96/02/10, and have these problems :
	1. "ypcat SOMETHING" reports correct info, but will complain
	   "No such map XXX.byXXX. Reason: No more records in map database"
	   in the final line.
	   But those files are in /vay/yp/NIS_DOMAIN/
	2. NIS is out of work in chroot environment.
	   When I chroot someone, he can't resolve NIS anymore.
	   ypwhich works, but not others.  id, passwd, ypcat die.
	   But I am sure that $CHROOT/etc/*passwd are set correctly.
	3. root change yp-user's password needs OLD password.
	   (I remembered that this has been fixed)
	4. Should I upgrade my NIS-related files to the most recently
	   current ?!  If yes, which files I should compile ?!
	   	       (yp*, libc ?!, passwd ?)

	Thanks for your help.
-- 

                                             李 建 達 (Jian-Da Li) 交大資工
                                             E-Mail : jdli@csie.nctu.edu.tw

From owner-freebsd-current  Mon Mar 18 06:07:54 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id GAA23551
          for current-outgoing; Mon, 18 Mar 1996 06:07:54 -0800 (PST)
Received: from gw3.att.com ([204.179.186.34])
          by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id GAA23545
          Mon, 18 Mar 1996 06:07:51 -0800 (PST)
From: ejc@nasvr1.cb.att.com
Received: from nasvr1.cb.att.com (naserver1.cb.att.com) by ig4.att.att.com id AA17006; Mon, 18 Mar 96 08:59:59 EST
Received: by nasvr1.cb.att.com (5.x/EMS-1.1 Sol2)
	id AA26557; Mon, 18 Mar 1996 09:05:02 -0500
Cc: freebsd-hackers@freebsd.org, dob@nasvr1.cb.att.com
Received: from ginger.cb.att.com by nasvr1.cb.att.com (5.x/EMS-1.1 Sol2)
	id AA26548; Mon, 18 Mar 1996 09:04:55 -0500
Received: by ginger.cb.att.com (5.x/EMS-1.1 Sol2)
	id AA19081; Mon, 18 Mar 1996 09:08:23 -0500
Date: Mon, 18 Mar 1996 09:08:23 -0500
Message-Id: <9603181408.AA19081@ginger.cb.att.com>
To: freebsd-current@freebsd.org
Subject: ibcs2  panicing under -current
Original-Cc: freebsd-hackers@freebsd.org, dob@nasvr1
X-Sun-Charset: US-ASCII
Sender: owner-current@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

Hello
	I have been trying to install the Word Perfect demo for the last
two weeks.  At this point I figured it's time to call in the big guns.
The installation starts without any problems or error messages.  Five or six
xwindows come up asking questions about the type of installation I want to do, 
The last window is the install window I click install, the progress window
comes up and the system hard panics.  

	I have done a clean install of -current as of 3-17-96 making sure
there were no old libraries, and making sure /etc up to date.

The system panic I receive in DDB is:
-------------------------------------
fatal trap 12: page fault while in kernel mode
fault virtual address	: 0x0
fault code 		= supervisor write, protection violation
instruction pointer	= 0x8 : 0x1
code segment		= base 0x0, limit 0xfffff, type 0x1b
			= dpl 0, pres 1, def32 1, gran 1
processor eflags	= interrupt enabled, resume, iopl = 0
current process		= 717 (xwpinstall)
interrupt mask		=
kernel: type 12 trap, code = 0
stopped at 0x1: addl %eax,0(%eax, %eax,1)

The strange thing is in the shell where I was doing the install from, there
were a few error messages before the system locked up.

cat: dir.list: No such file or directory
grep: perms.list: No such file or directory
installloop: not found in perms.list

These files all exist in the install directory.

We did a identical install on another FreeBSD machine and it worked fine.  The
only difference was it failed on a 486 but worked on a pentium machine, I know
it's grabbing at straws at this point but we are tapped out of ideas.  It failed
on a AMD/133 and a Intel DX2/66.  If anybody has any ideas, I would love to hear
them.

Peace, thanks,

Eric

dmesg
-----
FreeBSD 2.2-CURRENT #0: Sun Mar 17 16:37:31  1996
    ejc@gargoyle.bazzle.net:/var/usr/src/sys/compile/gargoyle
CPU: i486DX (486-class CPU)
  Origin = "AuthenticAMD"  Id = 0x4e4
real memory  = 33554432 (32768K bytes)
avail memory = 30543872 (29828K bytes)
Probing for devices on PCI bus 0:
chip0 <Intel 82424ZX (Saturn) cache DRAM controller> rev 4 on pci0:0
chip1 <Intel 82378ZB PCI-ISA bridge> rev 3 on pci0:2
ncr0 <ncr 53c825 wide scsi> rev 2 int a irq 11 on pci0:5
ncr0 waiting for scsi devices to settle
(ncr0:0:0): "SEAGATE ST15150W 0020" type 0 fixed SCSI 2
sd0(ncr0:0:0): Direct-Access 
sd0(ncr0:0:0): WIDE SCSI (16 bit) enabled.
 
sd0(ncr0:0:0): FAST SCSI-2 100ns (10 Mb/sec) offset 8.
4095MB (8388315 512 byte sectors)
(ncr0:1:0): "QUANTUM LP240S GM240S01X 6.4" type 0 fixed SCSI 2
sd1(ncr0:1:0): Direct-Access 
sd1(ncr0:1:0): FAST SCSI-2 100ns (10 Mb/sec) offset 8.
234MB (479350 512 byte sectors)
(ncr0:2:0): "PLEXTOR CD-ROM DM-XX28 3.08" type 5 removable SCSI 2
cd0(ncr0:2:0): CD-ROM 
cd0(ncr0:2:0): asynchronous.
cd present [325252 x 2048 byte records]
vga0 <VGA-compatible display device> rev 1 on pci0:6
Probing for devices on the ISA bus:
sc0 at 0x60-0x6f irq 1 on motherboard
sc0: VGA color <16 virtual consoles, flags=0x0>
sio0 at 0x3f8-0x3ff irq 4 on isa
sio0: type 16550A
sio1 at 0x2f8-0x2ff irq 3 on isa
sio1: type 16550A
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 72065B
fd0: 1.44MB 3.5in
npx0 on motherboard
npx0: INT 16 interface
new masks: bio c0000840, tty c003009a, net c003009a

From owner-freebsd-current  Mon Mar 18 07:47:29 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id HAA29928
          for current-outgoing; Mon, 18 Mar 1996 07:47:29 -0800 (PST)
Received: from skiddaw.elsevier.co.uk (skiddaw.elsevier.co.uk [193.131.222.60])
          by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id HAA29917
          for <freebsd-current@freebsd.org>; Mon, 18 Mar 1996 07:47:22 -0800 (PST)
Received: from snowdon.elsevier.co.uk (snowdon.elsevier.co.uk [193.131.197.164]) by skiddaw.elsevier.co.uk (8.6.13/8.6.12) with ESMTP id PAA29664 for <freebsd-current@freebsd.org>; Mon, 18 Mar 1996 15:45:18 GMT
Received: from tees by snowdon with SMTP (PP); Mon, 18 Mar 1996 15:40:46 +0000
Received: (from dpr@localhost) by tees (SMI-8.6/8.6.12) id PAA04484 
          for freebsd-current@freebsd.org; Mon, 18 Mar 1996 15:45:38 GMT
Date: Mon, 18 Mar 1996 15:45:38 GMT
From: Paul Richards <p.richards@elsevier.co.uk>
Message-Id: <199603181545.PAA04484@tees>
To: freebsd-current@freebsd.org
Subject: Re: Whee! Page Fault!
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-MD5: JWks7ZrxE4Sv3/LpQCo2gA==
Sender: owner-current@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

> 
> FYI
> I just got a repeatable system freeze while doing (on a simtel cd-rom)
> 	cd /cd/_/msdos/memutils
> 	vi descript.ion
> Curiously though this worked fine:
> 	tar cvf - . | ( cd /usr3/tmp/memutil ; tar xf - )
> 	cd /usr3/tmp/memutil
> 	vi descript.ion
> I'm running current from maybe 6/8 weeks back.
> I have no more detail to provide, sorry 
> (this err. was on my stable (no not `Stable') `good' system,
> my other unstable `sick' freebsd box is consuming my free time,
> so have no time to investigate)


I had numerous hangs yesterday and two of them were certainly caused by my
accessing the cdrom. In fact, accessing the cdrom froze the system every time
but I'm not sure it's the only cause since I wasn't using the cdrom the
first time it happened.

From owner-freebsd-current  Mon Mar 18 08:53:30 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id IAA05528
          for current-outgoing; Mon, 18 Mar 1996 08:53:30 -0800 (PST)
Received: from sxt2.space.lockheed.com (sxt2.space.lockheed.com [192.68.162.109])
          by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id IAA05523
          for <freebsd-current@freebsd.org>; Mon, 18 Mar 1996 08:53:29 -0800 (PST)
Received: by sxt2.space.lockheed.com (5.65/DEC-Ultrix/4.3)
	id AA18501; Mon, 18 Mar 1996 08:47:31 -0800
Date: Mon, 18 Mar 1996 08:47:30 -0800 (PST)
From: "Brian N. Handy" <handy@sxt2.space.lockheed.com>
To: Paul Richards <p.richards@elsevier.co.uk>
Cc: freebsd-current@freebsd.org
Subject: Re: Whee! Page Fault!
In-Reply-To: <199603181545.PAA04484@tees>
Message-Id: <Pine.ULT.3.91.960318084334.18478A-100000@sxt2.space.lockheed.com>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-current@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

On Mon, 18 Mar 1996, Paul Richards wrote:
> [CDrom is sick]
> 
> I had numerous hangs yesterday and two of them were certainly caused by my
> accessing the cdrom. In fact, accessing the cdrom froze the system every time
> but I'm not sure it's the only cause since I wasn't using the cdrom the
> first time it happened.

Bruce Evans posted a patch to the cd9660 driver that solved my problem.  
I haven't had any problem with it since.  I've been told that this patch 
is now in -current.

Brian

From owner-freebsd-current  Mon Mar 18 09:13:10 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id JAA06910
          for current-outgoing; Mon, 18 Mar 1996 09:13:10 -0800 (PST)
Received: from who.cdrom.com (who.cdrom.com [204.216.27.3])
          by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id JAA06905
          for <freebsd-current@freebsd.org>; Mon, 18 Mar 1996 09:13:08 -0800 (PST)
Received: from marble.eps.nagoya-u.ac.jp (marble.eps.nagoya-u.ac.jp [133.6.57.68])
          by who.cdrom.com (8.6.12/8.6.11) with ESMTP id JAA09472
          for <freebsd-current@freebsd.org>; Mon, 18 Mar 1996 09:13:07 -0800
Received: from marble.eps.nagoya-u.ac.jp (localhost [127.0.0.1]) by marble.eps.nagoya-u.ac.jp (8.7.4+2.6Wbeta6/3.3W9) with ESMTP id CAA00868; Tue, 19 Mar 1996 02:09:12 +0900 (JST)
Message-Id: <199603181709.CAA00868@marble.eps.nagoya-u.ac.jp>
To: p.richards@elsevier.co.uk
Cc: freebsd-current@freebsd.org
Subject: Re: Whee! Page Fault!
In-Reply-To: Your message of "Mon, 18 Mar 1996 15:45:38 GMT"
References: <199603181545.PAA04484@tees>
X-Mailer: Mew beta version 0.96 on Emacs 19.28.1, Mule 2.3
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Date: Tue, 19 Mar 1996 02:09:09 +0900
From: KATO Takenori <kato@eclogite.eps.nagoya-u.ac.jp>
Sender: owner-current@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

> but I'm not sure it's the only cause since I wasn't using the cdrom the
> first time it happened.

I don't access CDROM, but I also have numerous panics, and couldn't
boot FreeBSD-current box.  For example, After fsck in rc, my 5x86 box
shows following messages: 

  panic: freeing held page, count=1
  Debugger("panic")
  Stopped at     _Debugger+0x2a: movb    $0,_in_Debugger.110
  _Debugger(f0b48800,5800,1,0,f0b48864) at _Debugger+0x2a
  _trap_pfault(0,0,1,1,0) at _trap_pfault+0x10a
  (null)(10000,10,2,0,1) at 0
  (null)(0,0,0,0,0) at 0

and

  v_page_free: pindex(14), busy(0), PG_BUSY(0)
  panic: vm_page_free: freeing free page

I changed the code in vm_map_simplify_entry into revision 1.37 of
vm_map.c by following patch:

--------------------
*** vm_map.c.orig	Tue Mar 19 01:15:37 1996
--- vm_map.c	Tue Mar 19 01:15:20 1996
***************
*** 844,898 ****
  	 * neighbors.
  	 */
  
! 	if (entry->is_sub_map || entry->is_a_map || entry->wired_count)
  		return;
  
! 	prev = entry->prev;
! 	if (prev != &map->header) {
  		prevsize = prev->end - prev->start;
! 		if ( prev->end == entry->start &&
! 		     prev->object.vm_object == entry->object.vm_object &&
! 		     prev->offset + prevsize == entry->offset &&
! 		     prev->protection == entry->protection &&
! 		     prev->max_protection == entry->max_protection &&
! 		     prev->inheritance == entry->inheritance &&
! 		     prev->needs_copy == entry->needs_copy &&
! 		     prev->copy_on_write == entry->copy_on_write &&
! 		     prev->is_a_map == FALSE &&
! 		     prev->is_sub_map == FALSE &&
! 		     prev->wired_count == 0) {
! 			if (map->first_free == prev)
! 				map->first_free = entry;
! 			vm_map_entry_unlink(map, prev);
! 			entry->start = prev->start;
! 			entry->offset = prev->offset;
! 			vm_object_deallocate(prev->object.vm_object);
! 			vm_map_entry_dispose(map, prev);
! 		}
! 	}
! 
! 	next = entry->next;
! 	if (next != &map->header) {
  		nextsize = next->end - next->start;
  		esize = entry->end - entry->start;
! 		if (entry->end == next->start &&
! 		    next->object.vm_object == entry->object.vm_object &&
! 		    entry->offset + esize == next->offset &&
! 		    next->protection == entry->protection &&
! 		    next->max_protection == entry->max_protection &&
! 		    next->inheritance == entry->inheritance &&
! 		    next->needs_copy == entry->needs_copy &&
! 		    next->copy_on_write == entry->copy_on_write &&
! 		    next->is_a_map == FALSE &&
! 		    next->is_sub_map == FALSE &&
! 		    next->wired_count == 0) {
! 			if (map->first_free == next)
! 				map->first_free = entry;
! 			vm_map_entry_unlink(map, next);
! 			entry->end = next->end;
! 			vm_object_deallocate(next->object.vm_object);
! 			vm_map_entry_dispose(map, next);
! 	        }
  	}
  }
  
--- 848,904 ----
  	 * neighbors.
  	 */
  
! 	if (entry->is_sub_map)
  		return;
+ 	if (entry->is_a_map) {
+ 		return;
+ 	} else {
+ 		if (entry->wired_count)
+ 			return;
  
! 		prev = entry->prev;
  		prevsize = prev->end - prev->start;
! 		next = entry->next;
  		nextsize = next->end - next->start;
  		esize = entry->end - entry->start;
! 
! 		if (prev != &map->header &&
! 			prev->end == entry->start &&
! 			prev->is_a_map == FALSE &&
! 			prev->is_sub_map == FALSE &&
! 			prev->object.vm_object == entry->object.vm_object &&
! 			prev->protection == entry->protection &&
! 			prev->max_protection == entry->max_protection &&
! 			prev->inheritance == entry->inheritance &&
! 			prev->needs_copy == entry->needs_copy &&
! 			prev->copy_on_write == entry->copy_on_write &&
! 			prev->offset + prevsize == entry->offset &&
! 			prev->wired_count == 0) {
! 				vm_map_entry_unlink(map, prev);
! 				entry->start = prev->start;
! 				entry->offset = prev->offset;
! 				vm_object_deallocate(prev->object.vm_object);
! 				vm_map_entry_dispose(map, prev);
! 				esize = entry->end - entry->start;
! 		}
! 
! 		if (next != &map->header &&
! 			entry->end == next->start &&
! 			next->is_a_map == FALSE &&
! 			next->is_sub_map == FALSE &&
! 			next->object.vm_object == entry->object.vm_object &&
! 			next->protection == entry->protection &&
! 			next->max_protection == entry->max_protection &&
! 			next->inheritance == entry->inheritance &&
! 			next->needs_copy == entry->needs_copy &&
! 			next->copy_on_write == entry->copy_on_write &&
! 			entry->offset + esize == next->offset &&
! 			next->wired_count == 0) {
! 				vm_map_entry_unlink(map, next);
! 				entry->end = next->end;
! 				vm_object_deallocate(next->object.vm_object);
! 				vm_map_entry_dispose(map, next);
! 		}
  	}
  }
  
--------------------

After applying this patch, my FreeBSD box works without panic for 12
hours until now.

----
KATO Takenori <kato@eclogite.eps.nagoya-u.ac.jp>
Dept. Earth Planet. Sci., Nagoya Univ.,  Nagoya, 464-01, Japan
Voice: +81-52-789-2529   Fax: +81-52-789-3033

From owner-freebsd-current  Mon Mar 18 11:37:06 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id LAA24979
          for current-outgoing; Mon, 18 Mar 1996 11:37:06 -0800 (PST)
Received: from alpha.xerox.com (alpha.Xerox.COM [13.1.64.93])
          by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id LAA24969
          for <freebsd-current@freebsd.org>; Mon, 18 Mar 1996 11:37:03 -0800 (PST)
Received: from gemini.sdsp.mc.xerox.com ([13.231.132.20]) by alpha.xerox.com with SMTP id <15431(6)>; Mon, 18 Mar 1996 11:36:17 PST
Received: from gnu.mc.xerox.com (gnu.sdsp.mc.xerox.com) by gemini.sdsp.mc.xerox.com (4.1/SMI-4.1)
	id AA08446; Mon, 18 Mar 96 14:36:21 EST
Received: by gnu.mc.xerox.com (4.1/SMI-4.1)
	id AA25032; Mon, 18 Mar 96 14:36:18 EST
Message-Id: <9603181936.AA25032@gnu.mc.xerox.com>
X-Mailer: exmh version 1.6.4 10/10/95
To: Michael Smith <msmith@atrad.adelaide.edu.au>
Cc: coredump@nervosa.com (invalid opcode), jdp@polstra.com,
        freebsd-current@freebsd.org
Subject: Re: Elfkit release 1.1 is now available 
In-Reply-To: Your message of "Fri, 15 Mar 1996 23:12:28 PST."
             <199603160712.RAA16527@genesis.atrad.adelaide.edu.au> 
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Mon, 18 Mar 1996 11:36:10 PST
From: "Marty Leisner" <leisner@sdsp.mc.xerox.com>
Sender: owner-current@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk


With the ELF stuff:
	1) should I be able to do reasonable cross-development from a linux paltform?
	2) is there a difference between linux-elf and freebsd-elf?
	Or is it just i386-elf?


-- 
marty
leisner@sdsp.mc.xerox.com  
Member of the League for Programming Freedom



From owner-freebsd-current  Mon Mar 18 12:35:27 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id MAA09446
          for current-outgoing; Mon, 18 Mar 1996 12:35:27 -0800 (PST)
Received: from grumble.grondar.za (root@grumble.grondar.za [196.7.18.130])
          by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id MAA09078
          for <current@freebsd.org>; Mon, 18 Mar 1996 12:34:06 -0800 (PST)
Received: from grumble.grondar.za (mark@localhost [127.0.0.1]) by grumble.grondar.za (8.7.5/8.7.3) with ESMTP id WAA06095; Mon, 18 Mar 1996 22:32:17 +0200 (SAT)
Message-Id: <199603182032.WAA06095@grumble.grondar.za>
To: Bruce Evans <bde@zeta.org.au>
cc: current@freebsd.org, mark@grondar.za
Subject: Re: /dev/random - an idea/proposal 
Date: Mon, 18 Mar 1996 22:32:16 +0200
From: Mark Murray <mark@grondar.za>
Sender: owner-current@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

Bruce Evans wrote:
> >I am not completely happy with my current method of selecting the
> >interrupts for /dev/random right now. (There is rndcontrol(8) with
> >some command-line switches, and sysconfig has a line to edit). It
> >is too easy to overlook, and I am very keen that /dev/random be seen
> >to provide a decent source of entropy.
> 
> Neither am I, for the opposite reasons :-).  The default sysconfig
> setting of rand_irqs is almost useless except to print an annoying
> message to announce rndcontrol (add_keyboard_randomness() calls
> add_timer_randomness() a nearly constant number of usec before
> add_interrupt_randomness() for the keyboard interrupt calls
> add_timer_randomness()).

I had a hard time understanding this. It took a few re-reads
and I'm still only half-way :-(.

Could you please spell this out a bit better? What I think you are
saying is invalid. (I suspect you do not like the fact that two
calls to add_*_randomness happen on top of each other (a nearly
constant time apart) but are ignoring the fact that individual
keystrokes will occur at random times apart, which is the whole
purpose of using this interrupt.)

What is a better solution?

> >I would like some way to be able to choose these at kernel build
> >time - ie at the time the system manager configures her kernel,
> >she nominates that a particular device's interrupts should be used.
> 
> >This I would like to do by adding a keyword "random", syntactically
> >similar to "conflicts" to the config(8) grammar. This will then set
> 
> This would be far too much trouble.  As well as hacking config, you
> would have to:
> 
> - fix the problems that stop "conflicts" from working for PCI and
>   EISA devices
> 
> - update userconfig and dset to support the new flag
> 
> A kernel option to set a bitmap of the interrupts used to generate
> randomness would be easier to implement, but it would be easier to
> overlook than rndcontrol(8).

Thats not much use, then. I am looking for a solution that is elegant.
That implies the positive ideals of useful, reasonably obvious, and
clean, as well as being an improvement on what we have now.

Suggestions?

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  Mon Mar 18 14:37:52 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id OAA06257
          for current-outgoing; Mon, 18 Mar 1996 14:37:52 -0800 (PST)
Received: from alpha.xerox.com (alpha.Xerox.COM [13.1.64.93])
          by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id OAA06244
          Mon, 18 Mar 1996 14:37:44 -0800 (PST)
Received: from crevenia.parc.xerox.com ([13.2.116.11]) by alpha.xerox.com with SMTP id <15673(7)>; Mon, 18 Mar 1996 14:37:01 PST
Received: from localhost ([127.0.0.1]) by crevenia.parc.xerox.com with SMTP id <177478>; Mon, 18 Mar 1996 14:36:48 -0800
X-Mailer: exmh version 1.6.4 10/10/95
To: "Jordan K. Hubbard" <jkh@time.cdrom.com>
cc: current@freebsd.org, peter@freebsd.org
Subject: Re: Very strange packet-forwarding behavior! 
In-reply-to: Your message of "Fri, 15 Mar 1996 22:13:06 PST."
             <1093.826956786@time.cdrom.com> 
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Mon, 18 Mar 1996 14:36:41 PST
From: Bill Fenner <fenner@parc.xerox.com>
Message-Id: <96Mar18.143648pst.177478@crevenia.parc.xerox.com>
Sender: owner-current@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

In message <1093.826956786@time.cdrom.com> Jordan wrote:
>With ssh eating the line, however, everything else grinds to a screeching 
halt. 
>...  It's like ssh is not only eating all the
>bandwidth, it's eating it at such a "high priority" that absolutely
>nothing else can get through, not even pings.

ssh can potentially set IPTOS_LOWDELAY if you are either using "ssh 
remotehost" (e.g. no command) *or* if X forwarding succeeds.  Try using "ssh 
-x".

  Bill


From owner-freebsd-current  Mon Mar 18 14:42:19 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id OAA07590
          for current-outgoing; Mon, 18 Mar 1996 14:42:19 -0800 (PST)
Received: from ibp.ibp.fr (ibp.ibp.fr [132.227.60.30])
          by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id OAA07573
          for <freebsd-current@freebsd.org>; Mon, 18 Mar 1996 14:42:16 -0800 (PST)
Received: from blaise.ibp.fr (blaise.ibp.fr [132.227.60.1])
	by ibp.ibp.fr (8.6.12/jtpda-5.0) with ESMTP id XAA10548
	; Mon, 18 Mar 1996 23:42:07 +0100
Received: from (uucp@localhost)
	by blaise.ibp.fr (8.6.12/jtpda-5.0) with UUCP id XAA12206
	; Mon, 18 Mar 1996 23:42:06 +0100
Received: (from roberto@localhost) by keltia.freenix.fr (8.7.5/keltia-uucp-2.7) id XAA01030; Mon, 18 Mar 1996 23:08:00 +0100 (MET)
From: Ollivier Robert <roberto@keltia.freenix.fr>
Message-Id: <199603182208.XAA01030@keltia.freenix.fr>
Subject: Re: Ok, perl5 is out, but is the menu stuff ok?
To: mark@grondar.za (Mark Murray)
Date: Mon, 18 Mar 1996 23:08:00 +0100 (MET)
Cc: joerg_wunsch@uriah.heep.sax.de, freebsd-current@freebsd.org
In-Reply-To: <199603161750.TAA07222@grumble.grondar.za> from Mark Murray at "Mar 16, 96 07:50:49 pm"
X-Operating-System: FreeBSD 2.2-CURRENT ctm#1787
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

It seems that Mark Murray said:
> Perl 4 is rather aged by all accounts. If all anyone is going to
> do when they get FreeBSD is barf and install perl5, is that not an
> indication that we should catch up?

If we want to catch u, then  we should ditch Perl  4 from the tree and only
use the Perl 5 port. There are obvious advantages in having at least a part
of Perl in the tree (adduser comes to mind) but:

1. a full fledged Perl 5 in the tree will be too big IMO,

2. a cut-down Perl 5 will  be a nightmare  to maintain and will be missing
   some useful things like extentions.
 
If I  had to choose  between the two,  I'd take the  former. A  full one or
nothing. I'd rather avoid both if possible.
-- 
Ollivier ROBERT    -=- The daemon is FREE! -=-    roberto@keltia.frmug.fr.net
   FreeBSD keltia.freenix.fr 2.2-CURRENT #7: Mon Mar 18 21:28:18 MET 1996

From owner-freebsd-current  Mon Mar 18 15:00:38 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id PAA10145
          for current-outgoing; Mon, 18 Mar 1996 15:00:38 -0800 (PST)
Received: from phoenix.csie.nctu.edu.tw (root@phoenix.csie.nctu.edu.tw [140.113.17.171])
          by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id PAA10137
          for <freebsd-current@Freebsd.ORG>; Mon, 18 Mar 1996 15:00:36 -0800 (PST)
Received: from FreeBSD.csie.NCTU.edu.tw (root@freebsd.csie.nctu.edu.tw [140.113.235.250]) by phoenix.csie.nctu.edu.tw (8.6.11/8.6.4) with ESMTP id HAA25464 for <freebsd-current@Freebsd.ORG>; Tue, 19 Mar 1996 07:00:52 +0800
Received: (from jdli@localhost) by FreeBSD.csie.NCTU.edu.tw (8.7.3/8.7.3) id HAA25365 for freebsd-current@Freebsd.ORG; Tue, 19 Mar 1996 07:00:44 +0800 (CST)
From: Jian-Da Li <jdli@FreeBSD.csie.NCTU.edu.tw>
Message-Id: <199603182300.HAA25365@FreeBSD.csie.NCTU.edu.tw>
Subject: portmap keep on forking !!
To: freebsd-current@Freebsd.ORG
Date: Tue, 19 Mar 1996 07:00:43 +0800 (CST)
X-Mailer: ELM [version 2.4ME+ PL11 (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 :

	I am running a machine with 960210-CURRENT.  I found that the
	system is keep on forking new portmap every second, like this :

daemon      73  0.0  2.0   180  280  ??  Ss    9:44PM    1:33.48 portmap
daemon   25216  0.0  1.8   200  248  ??  S     6:57AM    0:00.01 portmap
daemon   25218  0.0  1.8   200  248  ??  S     6:57AM    0:00.01 portmap
daemon   25219  0.0  1.8   200  248  ??  S     6:57AM    0:00.01 portmap

	Those new forked portmap will die soon, and keep always 3-4 portmap
	running (plus original portmap).

	Any idea ?!	Thanks in advance.

	Here is a list of "rpcinfo -p"

   program vers proto   port
    100000    2   tcp    111  portmapper
    100000    2   udp    111  portmapper
    100004    2   udp    677  ypserv
    100004    2   tcp    679  ypserv
    100009    1   udp    680  yppasswdd
    100007    2   udp    683  ypbind
    100007    2   tcp    685  ypbind
    100005    1   udp    695  mountd
    100005    3   udp    695  mountd
    100005    1   tcp    696  mountd
    100005    3   tcp    696  mountd
    100003    2   udp   2049  nfs
    100003    3   udp   2049  nfs
    100003    2   tcp   2049  nfs
    100003    3   tcp   2049  nfs
    100001    1   udp  20023  rstatd
    100001    2   udp  20023  rstatd
    100001    3   udp  20023  rstatd
    100002    1   udp  20024  rusersd
    100002    2   udp  20024  rusersd
    100008    1   udp  20025  walld
    100012    1   udp  20026  sprayd


-- 

                                             李 建 達 (Jian-Da Li) 交大資工
                                             E-Mail : jdli@csie.nctu.edu.tw

From owner-freebsd-current  Mon Mar 18 16:23:10 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id QAA15923
          for current-outgoing; Mon, 18 Mar 1996 16:23:10 -0800 (PST)
Received: from cabri.obs-besancon.fr (cabri.obs-besancon.fr [193.52.184.3])
          by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id QAA15916
          for <freebsd-current@freebsd.org>; Mon, 18 Mar 1996 16:23:05 -0800 (PST)
Received: by cabri.obs-besancon.fr (5.57/Ultrix3.0-C)
	id AA00289; Tue, 19 Mar 96 01:25:02 +0100
Date: Tue, 19 Mar 96 01:25:02 +0100
Message-Id: <9603190025.AA00289@cabri.obs-besancon.fr>
From: Jean-Marc Zucconi <jmz@cabri.obs-besancon.fr>
To: roberto@keltia.freenix.fr
Cc: mark@grondar.za, joerg_wunsch@uriah.heep.sax.de,
        freebsd-current@freebsd.org
In-Reply-To: <199603182208.XAA01030@keltia.freenix.fr> (message from Ollivier
	Robert on Mon, 18 Mar 1996 23:08:00 +0100 (MET))
Subject: Re: Ok, perl5 is out, but is the menu stuff ok?
X-Mailer: Emacs
Sender: owner-current@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

>>>>> Ollivier Robert writes:

 > It seems that Mark Murray said:
 >> Perl 4 is rather aged by all accounts. If all anyone is going to
 >> do when they get FreeBSD is barf and install perl5, is that not an
 >> indication that we should catch up?

 > If we want to catch u, then  we should ditch Perl  4 from the tree and only
 > use the Perl 5 port. There are obvious advantages in having at least a part
 > of Perl in the tree (adduser comes to mind) but:

 > 1. a full fledged Perl 5 in the tree will be too big IMO,

I don't think this is a good argument:

- disks are cheap
- you already have perl in /usr/bin  AND  in /usr/local/bin! So
removing perl4 and keeping perl5 in /usr/bin will give you more room
on your disks :-)

 > 2. a cut-down Perl 5 will  be a nightmare  to maintain and will be missing
 >    some useful things like extentions.

I agree. The problem I see with extensions is that non standard
extensions (eg Tk) will not install in /usr/local. However it may be
possible to make the site_perl directory a link /usr/local/something.

 > If I  had to choose  between the two,  I'd take the  former. A  full one or
 > nothing. I'd rather avoid both if possible.

Jean-Marc

 > -- 
 > Ollivier ROBERT    -=- The daemon is FREE! -=-    roberto@keltia.frmug.fr.net
 >    FreeBSD keltia.freenix.fr 2.2-CURRENT #7: Mon Mar 18 21:28:18 MET 1996
 _____________________________________________________________________________
 Jean-Marc Zucconi       Observatoire de Besancon       F 25010 Besancon cedex
                   PGP Key: finger jmz@cabri.obs-besancon.fr
 =============================================================================

From owner-freebsd-current  Mon Mar 18 17:41:22 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id RAA20491
          for current-outgoing; Mon, 18 Mar 1996 17:41:22 -0800 (PST)
Received: from ki.net (ki.net [142.77.249.8])
          by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id RAA20477
          for <current@freebsd.org>; Mon, 18 Mar 1996 17:41:15 -0800 (PST)
Received: (from scrappy@localhost) by ki.net (8.7.4/8.7.4) id UAA00714; Mon, 18 Mar 1996 20:40:46 -0500 (EST)
Date: Mon, 18 Mar 1996 20:40:45 -0500 (EST)
From: "Marc G. Fournier" <scrappy@ki.net>
To: current@freebsd.org
Subject: PR Appendum: ed PANIC
Message-ID: <Pine.BSF.3.91.960318203745.29884I-100000@ki.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-current@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk


Hi...

	Got a crash again today when I came into the office, on my -current
machine.  I submitted a PR for it, but at the time I hadn't had a core file
to work with.  After todays, I do, so I tried to "operate" on it, using 
what is detailed in the handbook as a guide, only to come up with...which
looks nothing like what I expected, so figure I did something wrong.

	I've kept the core file, in case there is something else I should
try to do?  Hope this helps some to debug the problem...


Script started on Mon Mar 18 20:23:58 1996
freebsd# cd /usr/debug
freebsd# ls
kernel-sym.0	kernel-sym.1	typescript
freebsd# gdb -k
GDB is free software and you are welcome to distribute copies of it
 under certain conditions; type "show copying" to see the conditions.
There is absolutely no warranty for GDB; type "show warranty" for details.
GDB 4.13 (i386-unknown-freebsd), Copyright 1994 Free Software Foundation, Inc.
(kgdb) symbol-file kernel-sym.1
Reading symbols from kernel-sym.1...done.
(kgdb) exec-file /var/crash/kernel.1
(kgdb) core-file /var/crash/vmcore.1
IdlePTD 20b000
current pcb at 1d8d84
panic: from debugger
#0  boot (howto=0) at ../../i386/i386/machdep.c:935
935					dumppcb.pcb_ptd = rcr3();
(kgdb) where
#0  boot (howto=0) at ../../i386/i386/machdep.c:935
(kgdb) list
930			cngetc();
931		} else {
932			if (howto & RB_DUMP) {
933				if (!cold) {
934					savectx(&dumppcb);
935					dumppcb.pcb_ptd = rcr3();
936					dumpsys();
937				}
938	
939				if (PANIC_REBOOT_WAIT_TIME != 0) {
(kgdb) bt
#0  boot (howto=0) at ../../i386/i386/machdep.c:935
(kgdb) up 10
#0  boot (howto=0) at ../../i386/i386/machdep.c:935
935					dumppcb.pcb_ptd = rcr3();
(kgdb) up 10
#0  boot (howto=0) at ../../i386/i386/machdep.c:935
935					dumppcb.pcb_ptd = rcr3();
(kgdb) list
930			cngetc();
931		} else {
932			if (howto & RB_DUMP) {
933				if (!cold) {
934					savectx(&dumppcb);
935					dumppcb.pcb_ptd = rcr3();
936					dumpsys();
937				}
938	
939				if (PANIC_REBOOT_WAIT_TIME != 0) {
(kgdb) where
#0  boot (howto=0) at ../../i386/i386/machdep.c:935
(kgdb) quit
freebsd# gdb -k kernel-sym.1 /var/crash/vmcore.1 
GDB is free software and you are welcome to distribute copies of it
 under certain conditions; type "show copying" to see the conditions.
There is absolutely no warranty for GDB; type "show warranty" for details.
GDB 4.13 (i386-unknown-freebsd), 
Copyright 1994 Free Software Foundation, Inc...
IdlePTD 20b000
current pcb at 1d8d84
panic: from debugger
#0  boot (howto=0) at ../../i386/i386/machdep.c:935
935					dumppcb.pcb_ptd = rcr3();
(kgdb) quit
freebsd# exit
exit

Script done on Mon Mar 18 20:33:05 1996

Marc G. Fournier | POP Mail  Telnet Acct  DNS Hosting
System           |  WWW Services   Database Services  | Knowledge, 
  Administrator  |                                    | Information and
 scrappy@ki.net  |      WWW: http://www.ki.net        | Communications, Inc


From owner-freebsd-current  Mon Mar 18 18:12:09 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id SAA22438
          for current-outgoing; Mon, 18 Mar 1996 18:12:09 -0800 (PST)
Received: from mramirez.sy.yale.edu (mramirez.sy.yale.edu [130.132.57.207])
          by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id SAA22432
          for <freebsd-current@FreeBSD.org>; Mon, 18 Mar 1996 18:12:06 -0800 (PST)
Received: (from mrami@localhost) by mramirez.sy.yale.edu (8.6.12/8.6.9) id VAA06924; Mon, 18 Mar 1996 21:11:01 -0500
Date: Mon, 18 Mar 1996 21:11:00 -0500 (EST)
From: Marc Ramirez <mrami@mramirez.sy.yale.edu>
Reply-To: mrami@minerva.cis.yale.edu
To: Marty Leisner <leisner@sdsp.mc.xerox.com>
cc: Michael Smith <msmith@atrad.adelaide.edu.au>,
        invalid opcode <coredump@nervosa.com>, jdp@polstra.com,
        freebsd-current@FreeBSD.org
Subject: Re: Elfkit release 1.1 is now available 
In-Reply-To: <9603181936.AA25032@gnu.mc.xerox.com>
Message-ID: <Pine.BSF.3.91.960318211018.1468D-100000@mramirez.sy.yale.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-current@FreeBSD.org
X-Loop: FreeBSD.org
Precedence: bulk

On Mon, 18 Mar 1996, Marty Leisner wrote:

> 
> With the ELF stuff:
> 	2) is there a difference between linux-elf and freebsd-elf?
> 	Or is it just i386-elf?

There is a difference: different syscall numbers.

Marc.

--
BULLWINKLE: "You just leave that to my pal.  He's the brains of the
            outfit."
GENERAL:    "What does that make YOU?"
BULLWINKLE: "What else?  An executive..."
	-- Jay Ward


From owner-freebsd-current  Mon Mar 18 18:21:57 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id SAA23057
          for current-outgoing; Mon, 18 Mar 1996 18:21:57 -0800 (PST)
Received: from dyson.iquest.net (dyson.iquest.net [198.70.144.127])
          by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id SAA23052
          for <freebsd-current@freebsd.org>; Mon, 18 Mar 1996 18:21:43 -0800 (PST)
Received: (from root@localhost) by dyson.iquest.net (8.6.11/8.6.9) id VAA02956; Mon, 18 Mar 1996 21:13:45 GMT
From: "John S. Dyson" <toor@dyson.iquest.net>
Message-Id: <199603182113.VAA02956@dyson.iquest.net>
Subject: Re: Whee! Page Fault!
To: kato@eclogite.eps.nagoya-u.ac.jp (KATO Takenori)
Date: Mon, 18 Mar 1996 21:13:44 +0000 ()
Cc: p.richards@elsevier.co.uk, freebsd-current@freebsd.org
In-Reply-To: <199603181709.CAA00868@marble.eps.nagoya-u.ac.jp> from "KATO Takenori" at Mar 19, 96 02:09:09 am
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

> 
> I changed the code in vm_map_simplify_entry into revision 1.37 of
> vm_map.c by following patch:
> 
Alan Cox suggested the "meat" of that patch, and THANKS!!!

John

From owner-freebsd-current  Mon Mar 18 18:44:47 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id SAA24798
          for current-outgoing; Mon, 18 Mar 1996 18:44:47 -0800 (PST)
Received: from austin.polstra.com (austin.polstra.com [206.213.73.10])
          by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id SAA24793
          for <freebsd-current@freebsd.org>; Mon, 18 Mar 1996 18:44:44 -0800 (PST)
Received: from austin.polstra.com (jdp@localhost) by austin.polstra.com (8.6.12/8.6.12) with ESMTP id SAA04211; Mon, 18 Mar 1996 18:38:23 -0800
Message-Id: <199603190238.SAA04211@austin.polstra.com>
To: "Marty Leisner" <leisner@sdsp.mc.xerox.com>
cc: Michael Smith <msmith@atrad.adelaide.edu.au>,
        coredump@nervosa.com (invalid opcode), freebsd-current@freebsd.org
Subject: Re: Elfkit release 1.1 is now available 
In-reply-to: Your message of "Mon, 18 Mar 1996 11:36:10 PST."
             <9603181936.AA25032@gnu.mc.xerox.com> 
Date: Mon, 18 Mar 1996 18:38:23 -0800
From: John Polstra <jdp@polstra.com>
Sender: owner-current@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

Marty asked:

> With the ELF stuff:
> 	1) should I be able to do reasonable cross-development from a linux paltform?

You mean, using the standard Linux compiler, right?  (The tools in
elfkit are configured to run under FreeBSD, not under Linux.)

> 	2) is there a difference between linux-elf and freebsd-elf?
> 	Or is it just i386-elf?

For the binutils stuff (assembler and linker):  The configuration
target, i386-*-freebsdelf, is virtually identical to i386-*-elf.
There's really only one difference:  The load address for executables is
set to 0x08048000, instead of the 0x08000000 that binutils uses for the
other ELF targets.  Why?  Because that's what the SVR4/i386 ABI
specification says it should be.  (And that's what it really is, under
SVR4.)  I don't know why 0x08000000 was used for Linux and friends.

Aside from that, I added a couple of command-line options, to make the
tools more compatible with the standard FreeBSD tools.  For "as", the
"-k" option is accepted but ignored.  The FreeBSD assembler uses "-k" to
specify that PIC code should be generated.  For "ld", "-Bshareable" is
accepted as an alias for "-shared".

For gcc, the i386-*-freebsdelf differs from the Linux ELF target in
additional ways.  Among the differences are:

    * The predefines for cpp ("FreeBSD" instead of "linux")
    * The type of wchar_t (int instead of long int)
    * The LINK_SPEC

I hope this answers your questions.  If not, let me know.
--
   John Polstra                                       jdp@polstra.com
   John D. Polstra & Co., Inc.                Seattle, Washington USA
   "Self-knowledge is always bad news."                 -- John Barth

From owner-freebsd-current  Mon Mar 18 19:32:16 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id TAA28261
          for current-outgoing; Mon, 18 Mar 1996 19:32:16 -0800 (PST)
Received: from desiree.teleport.com (desiree.teleport.com [192.108.254.21])
          by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id TAA28126
          Mon, 18 Mar 1996 19:31:55 -0800 (PST)
Received: from linda.teleport.com (mrl@linda.teleport.com [192.108.254.12]) by desiree.teleport.com (8.6.12/8.6.9) with ESMTP id TAA07798; Mon, 18 Mar 1996 19:31:49 -0800
From: Mostyn/Annabella <mrl@teleport.com>
Received: (mrl@localhost) by linda.teleport.com (8.6.12/8.6.12) id TAA04150; Mon, 18 Mar 1996 19:31:49 -0800
Message-Id: <199603190331.TAA04150@linda.teleport.com>
Subject: SCSI death in -current with DAT
To: gibbs@freefall.freebsd.org
Date: Mon, 18 Mar 1996 19:31:48 -0800 (PST)
Cc: current@freebsd.org, mrl@teleport.com
X-Mailer: ELM [version 2.4 PL25]
Content-Type: text
Sender: owner-current@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

Hi,

Under current, an ARCHIVE Python DAT (Conner - a modern one, a couple
of months old, is detected to have "variable blocks" and times out
bringing an Adaptec 2940UW to its knees.  Afterwards, the machine
won't even see a disk on reboot (via the reset button) and needs a
power-cycle to reset the controller.

Under 2.1R, the DAT is identified as having fixed 512-byte blocks and
works perfectly!

The DAT is on the non-wide cable on the 2940UW and a wide disk is the
subject of a tar.

A tar cf /dev/rst0 usr was used and the syslog messages during "death"
,using current, are -

st0(ahc0:0:0): timed out in dataout phase, SCSISIGI = 0x48
st0(ahc0:0:0): BUS DEVICE RESET message queued.
st0(ahc0:0:0): timed out in command phase, SCSISIGI = 0x84
ahc0: Issued Channel A Bus Reset #1. 1 SCBs aborted
sd0(ahc0:5:0): UNIT ATTENTION asc:29.2
, retries: 4
st0(ahc0:0:0): timed out in dataout phase, SCSISIGI = 0x0
ahc0: Issued Channel A Bus Reset #2. 1 SCBs aborted
st0(ahc0:0:0): timed out in dataout phase, SCSISIGI = 0x0
ahc0: Issued Channel A Bus Reset #2. 1 SCBs aborted

DEATH

can escape to ddb but nothing else - power cycle required.

This, with a St. Patrick's Day -current.


--> -current boot messages -

 ahc0 <Adaptec 2940 Ultra SCSI host adapter> rev 0 int a irq 11 on pci0:12
 ahc0: aic7880 Wide Channel, SCSI Id=7, 16 SCBs
 ahc0 waiting for scsi devices to settle
 (ahc0:0:0): "ARCHIVE Python 28388-XXX 5.45" type 1 removable SCSI 2
 st0(ahc0:0:0): Sequential-Access density code 0x0, variable blocks, write-enabled
						    ^^^^^^^^^^^^^^^
 (ahc0:1:0): "TOSHIBA CD-ROM XM-3701TA 3055" type 5 removable SCSI 2
 cd0(ahc0:1:0): CD-ROM 
 cd0(ahc0:1:0): NOT READY asc:3a,0 Medium not present
 can't get the size
 (ahc0:5:0): "Quantum XP32150W 81HB" type 0 fixed SCSI 2
 sd0(ahc0:5:0): Direct-Access 2050MB (4199760 512 byte sectors)
 sd0(ahc0:5:0): with 3907 cyls, 10 heads, and an average 107 sectors/track
 (ahc0:6:0): "Quantum XP32150W 81HB" type 0 fixed SCSI 2
 sd1(ahc0:6:0): Direct-Access 2050MB (4199760 512 byte sectors)
 sd1(ahc0:6:0): with 3907 cyls, 10 heads, and an average 107 sectors/track

--> 2.1R boot messages -

 ahc0 <Adaptec 2940 Ultra SCSI host adapter> rev 0 int a irq 11 on pci0:12
 de0: enabling 10baseT/UTP port
 ahc0: aic7870 Ultra Wide Channel, SCSI Id=7, aic7870, 255 SCBs
 ahc0 waiting for scsi devices to settle
 (ahc0:0:0): "ARCHIVE Python 28388-XXX 5.45" type 1 removable SCSI 2
 st0(ahc0:0:0): Sequential-Access density code 0x13, 512-byte blocks, write-enabled
						     ^^^^^^^^^^^^^^^
 (ahc0:1:0): "TOSHIBA CD-ROM XM-3701TA 3055" type 5 removable SCSI 2
 cd0(ahc0:1:0): CD-ROM 
 cd0(ahc0:1:0): NOT READY asc:3a,0 Medium not present
 can't get the size
 
 (ahc0:5:0): "Quantum XP32150W 81HB" type 0 fixed SCSI 2
 sd0(ahc0:5:0): Direct-Access 2050MB (4199760 512 byte sectors)
 (ahc0:6:0): "Quantum XP32150W 81HB" type 0 fixed SCSI 2
 sd1(ahc0:6:0): Direct-Access 2050MB (4199760 512 byte sectors)

I could force fixed blocks by hand in st.c but I'd prefer a genuine fix.

Mostyn Lewis

From owner-freebsd-current  Mon Mar 18 19:38:42 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id TAA28941
          for current-outgoing; Mon, 18 Mar 1996 19:38:42 -0800 (PST)
Received: from neon.Glock.COM (root@neon.glock.com [198.82.228.159])
          by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id TAA28921
          for <current@freebsd.org>; Mon, 18 Mar 1996 19:38:32 -0800 (PST)
Received: (from mmead@localhost) by neon.Glock.COM (8.7.4/8.7.3) id WAA05953 for current@freebsd.org; Mon, 18 Mar 1996 22:37:58 -0500 (EST)
From: "matthew c. mead" <mmead@Glock.COM>
Message-Id: <199603190337.WAA05953@neon.Glock.COM>
Subject: warning about des stuff in (cd /usr/src; make)
To: current@freebsd.org
Date: Mon, 18 Mar 1996 22:37:57 -0500 (EST)
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'm getting these two warnings when build /usr/src:

bdes.o: WARNING!  des_setkey(3) not present in the system!
bdes.o: WARNING!  des_cipher(3) not present in the system!

    Should I be getting them?  I'm supping the security stuff
with these two lines:

src-eBones release=current host=sup.FreeBSD.org hostbase=/home base=/usr prefix=/usr/src delete old use-rel-suffix
rc-secure release=current host=sup.FreeBSD.org hostbase=/home base=/usr prefix=/usr/src delete old use-rel-suffix


-matt

-- 
Matthew C. Mead

mmead@Glock.COM
http://www.Glock.COM/~mmead/

From owner-freebsd-current  Mon Mar 18 20:23:04 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id UAA03357
          for current-outgoing; Mon, 18 Mar 1996 20:23:04 -0800 (PST)
Received: from rocky.sri.MT.net (rocky.sri.MT.net [204.182.243.10])
          by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id UAA03347
          for <current@freebsd.org>; Mon, 18 Mar 1996 20:22:59 -0800 (PST)
Received: (from nate@localhost) by rocky.sri.MT.net (8.6.12/8.6.12) id VAA02814; Mon, 18 Mar 1996 21:25:46 -0700
Date: Mon, 18 Mar 1996 21:25:46 -0700
From: Nate Williams <nate@sri.MT.net>
Message-Id: <199603190425.VAA02814@rocky.sri.MT.net>
To: "matthew c. mead" <mmead@Glock.COM>
Cc: current@freebsd.org
Subject: Re: warning about des stuff in (cd /usr/src; make)
In-Reply-To: <199603190337.WAA05953@neon.Glock.COM>
References: <199603190337.WAA05953@neon.Glock.COM>
Sender: owner-current@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

>     I'm getting these two warnings when build /usr/src:
> 
> bdes.o: WARNING!  des_setkey(3) not present in the system!
> bdes.o: WARNING!  des_cipher(3) not present in the system!
> 
>     Should I be getting them?  I'm supping the security stuff
> with these two lines:

Ignore them.  It's a weirdness on the part of the linker having to do
with warning symbols.



Nate

From owner-freebsd-current  Mon Mar 18 22:02:10 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id WAA08797
          for current-outgoing; Mon, 18 Mar 1996 22:02:10 -0800 (PST)
Received: from news1.gtn.com (news1.gtn.com [192.109.159.3])
          by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id WAA08792
          for <current@freebsd.org>; Mon, 18 Mar 1996 22:02:07 -0800 (PST)
Received: (from uucp@localhost) by news1.gtn.com (8.7.2/8.7.2) id GAA25675 for current@freebsd.org; Tue, 19 Mar 1996 06:45:22 +0100 (MET)
Received: from knobel.gun.de (localhost [127.0.0.1]) by knobel.gun.de (8.7.5/8.7.3) with SMTP id GAA00315 for <current@freebsd.org>; Tue, 19 Mar 1996 06:46:42 +0100 (MET)
Date: Tue, 19 Mar 1996 06:46:42 +0100 (MET)
From: Andreas Klemm <andreas@knobel.gun.de>
To: current@freebsd.org
Subject: Re: Nvi alpha version 1.57 now available.
In-Reply-To: <199603181752.MAA21465@mongoose.bostic.com>
Message-ID: <Pine.BSF.3.91.960319064319.213B-100000@knobel.gun.de>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-current@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

On Mon, 18 Mar 1996, Keith Bostic wrote:

> Alpha version 1.57 of nex/nvi is now available for anonymous ftp from
> ftp.cs.berkeley.edu:ucb/4bsd/nvi.ALPHA.1.57.tar.gz, or alternatively,
> from bostic.com:pub/nvi.ALPHA.1.57.tar.gz.

Should be added to the ports collection first ... if there isn't 
any other taker, I'll prepare the port and send it to Satoshi.

Or should it go directly into the main -current source tree after 
a short period of testing ?

	Andreas ///

--
andreas@knobel.gun.de         /\/\___      Wiechers & Partner Datentechnik GmbH
   Andreas Klemm          ___/\/\/         $$  Support Unix - aklemm@wup.de  $$
pgp p-key  http://www-swiss.ai.mit.edu/~bal/pks-toplev.html  >>> powered by <<<
ftp://sunsite.unc.edu/pub/Linux/system/Printing/aps-491.tgz  >>>    FreeBSD <<<
"Ich bleibe bei der Aussage und trotze den Flames. :-)"    Ulli Horlacher 02/96


From owner-freebsd-current  Tue Mar 19 02:17:39 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id CAA19171
          for current-outgoing; Tue, 19 Mar 1996 02:17:39 -0800 (PST)
Received: (from dima@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id CAA19164
          Tue, 19 Mar 1996 02:17:36 -0800 (PST)
Message-Id: <199603191017.CAA19164@freefall.freebsd.org>
Subject: Re: Nvi alpha version 1.57 now available.
To: andreas@knobel.gun.de (Andreas Klemm)
Date: Tue, 19 Mar 1996 02:17:35 -0800 (PST)
Cc: current@FreeBSD.org
In-Reply-To: <Pine.BSF.3.91.960319064319.213B-100000@knobel.gun.de> from "Andreas Klemm" at Mar 19, 96 06:46:42 am
From: dima@FreeBSD.org (Dima Ruban)
X-Class: Fast
Organization: HackerDome
X-Mailer: ELM [version 2.4 PL24]
Content-Type: text
Sender: owner-current@FreeBSD.org
X-Loop: FreeBSD.org
Precedence: bulk

Andreas Klemm writes:
> 
> On Mon, 18 Mar 1996, Keith Bostic wrote:
> 
> > Alpha version 1.57 of nex/nvi is now available for anonymous ftp from
> > ftp.cs.berkeley.edu:ucb/4bsd/nvi.ALPHA.1.57.tar.gz, or alternatively,
> > from bostic.com:pub/nvi.ALPHA.1.57.tar.gz.
> 
> Should be added to the ports collection first ... if there isn't 
> any other taker, I'll prepare the port and send it to Satoshi.
> 
> Or should it go directly into the main -current source tree after 
> a short period of testing ?

Please wait fro next release. I sent localization patches to bostic,
which I promissed him to send. they're going to be in nest release.

> 
> 	Andreas ///
> 
> --
> andreas@knobel.gun.de         /\/\___      Wiechers & Partner Datentechnik GmbH
>    Andreas Klemm          ___/\/\/         $$  Support Unix - aklemm@wup.de  $$
> pgp p-key  http://www-swiss.ai.mit.edu/~bal/pks-toplev.html  >>> powered by <<<
> ftp://sunsite.unc.edu/pub/Linux/system/Printing/aps-491.tgz  >>>    FreeBSD <<<
> "Ich bleibe bei der Aussage und trotze den Flames. :-)"    Ulli Horlacher 02/96
> 
> 

-- dima

From owner-freebsd-current  Tue Mar 19 02:22:47 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id CAA19387
          for current-outgoing; Tue, 19 Mar 1996 02:22:47 -0800 (PST)
Received: (from dima@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id CAA19365
          Tue, 19 Mar 1996 02:22:41 -0800 (PST)
Message-Id: <199603191022.CAA19365@freefall.freebsd.org>
Subject: new sup server
To: hackers@freebsd.org
Date: Tue, 19 Mar 1996 02:22:40 -0800 (PST)
Cc: current@freebsd.org
From: dima@freebsd.org (Dima Ruban)
X-Class: Fast
Organization: HackerDome
X-Mailer: ELM [version 2.4 PL24]
Content-Type: text
Sender: owner-current@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

Hi there!

New sup server for current/stable/cvs is operational and ready.
Please use it. (This server is on T3, so it should work
pretty fast). Questions and/or comments to dima@best.net.
Oops, almost forgot. This is sup5.freebsd.org

Enjoy.

-- dima

From owner-freebsd-current  Tue Mar 19 02:36:14 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id CAA20223
          for current-outgoing; Tue, 19 Mar 1996 02:36:14 -0800 (PST)
Received: from time.cdrom.com (time.cdrom.com [204.216.27.226])
          by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id CAA20217
          Tue, 19 Mar 1996 02:36:12 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by time.cdrom.com (8.7.5/8.6.9) with SMTP id CAA00403; Tue, 19 Mar 1996 02:36:00 -0800 (PST)
To: Bill Fenner <fenner@parc.xerox.com>
cc: current@freebsd.org, peter@freebsd.org
Subject: Re: Very strange packet-forwarding behavior! 
In-reply-to: Your message of "Mon, 18 Mar 1996 14:36:41 PST."
             <96Mar18.143648pst.177478@crevenia.parc.xerox.com> 
Date: Tue, 19 Mar 1996 02:36:00 -0800
Message-ID: <401.827231760@time.cdrom.com>
From: "Jordan K. Hubbard" <jkh@time.cdrom.com>
Sender: owner-current@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

> ssh can potentially set IPTOS_LOWDELAY if you are either using "ssh 
> remotehost" (e.g. no command) *or* if X forwarding succeeds.  Try using "ssh 
> -x".

Thanks for the tip!

Now if I could only figure out how to get RCVS to use a command with
arguments for the rsh.. :-)

						Jordan

From owner-freebsd-current  Tue Mar 19 02:50:04 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id CAA20845
          for current-outgoing; Tue, 19 Mar 1996 02:50:04 -0800 (PST)
Received: from nixpbe.pdb.sni.de (mail.sni.de [192.109.2.33])
          by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id CAA20794
          for <current@FreeBSD.org>; Tue, 19 Mar 1996 02:49:52 -0800 (PST)
Received: (from nerv@localhost) by nixpbe.pdb.sni.de (8.6.12/8.6.12) id LAA00676 for current@FreeBSD.org; Tue, 19 Mar 1996 11:49:03 +0100
Message-Id: <199603191049.LAA00676@nixpbe.pdb.sni.de>
Subject: How to develop software and track current?
To: hackers@FreeBSD.org (FreeBSD hackers)
Date: Tue, 19 Mar 96 11:46:24 MET
From: Greg Lehey <lehey.pad@sni.de>
Cc: current@FreeBSD.org (Users of FreeBSD -current)
X-Mailer: xmail 2.4 (based on ELM 2.2 PL16)
Sender: owner-current@FreeBSD.org
X-Loop: FreeBSD.org
Precedence: bulk

I'm currently about to start some active work on the ISDN software,
and I face a problem: I'm also tracking -current.  How to I ensure
that I get my updates to -current and also maintain the modifications
I make to the ISDN software?  The problem is compounded by the fact
that I don't get on very well with cvs, so if the following text
contains nonsense, please be nice :-) I can see a number of
possibilities:

1.  Create a new cvs tag, say "2.2-CURRENT-grog", and put all my
    changes there.  The problem I anticipate here are that I won't be
    able to automatically track the ctm updates.

2.  Check my changes in to 2.2-CURRENT every evening.  This seems to
    have a number of potential problems: first, if I forget to check
    in, I lose my updates, and secondly, somebody else might check in
    files which I have changed.  Presumably the latter action would
    cause the cvs update to blow up.

3.  Create a new directory outside the control of cvs.  This sounds
    like a real kludge.

This is obviously a problem that a lot of people have already solved,
at least to their own satisfaction.  If we can come up with a clean,
consistent way of doing it, I'll gladly contribute some documentation
on the subject.

Greg

From owner-freebsd-current  Tue Mar 19 03:08:10 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id DAA21585
          for current-outgoing; Tue, 19 Mar 1996 03:08:10 -0800 (PST)
Received: from sequent.kiae.su (sequent.kiae.su [144.206.136.6])
          by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id DAA21482
          Tue, 19 Mar 1996 03:07:54 -0800 (PST)
Received: by sequent.kiae.su id AA16648
  (5.65.kiae-2 ); Tue, 19 Mar 1996 14:07:26 +0300
Received: by sequent.KIAE.su (UUMAIL/2.0); Tue, 19 Mar 96 14:07:25 +0300
Received: (from ache@localhost) by astral.msk.su (8.7.5/8.7.3) id OAA01163; Tue, 19 Mar 1996 14:03:08 +0300 (MSK)
Message-Id: <199603191103.OAA01163@astral.msk.su>
Subject: Re: Nvi alpha version 1.57 now available.
To: dima@FreeBSD.org (Dima Ruban)
Date: Tue, 19 Mar 1996 14:03:08 +0300 (MSK)
Cc: andreas@knobel.gun.de, current@FreeBSD.org
In-Reply-To: <199603191017.CAA19164@freefall.freebsd.org> from "Dima Ruban" at "Mar 19, 96 02:17:35 am"
From: =?KOI8-R?Q?=E1=CE=C4=D2=C5=CA_=FE=C5=D2=CE=CF=D7?= (aka Andrey A. Chernov, Black Mage) <ache@astral.msk.su>
X-Class: Fast
X-Mailer: ELM [version 2.4ME+ PL13 (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

> Please wait fro next release. I sent localization patches to bostic,
> which I promissed him to send. they're going to be in nest release.

Just for note: it needs to call setlocale() as early as possible
and make shure all is*() ctype operations range is 'unsigned char'
range and EOF only.

-- 
Andrey A. Chernov        : And I rest so composedly,  /Now, in my bed,
ache@astral.msk.su       : That any beholder  /Might fancy me dead -
http://dt.demos.su/~ache : Might start at beholding me,  /Thinking me dead.
RELCOM Team,FreeBSD Team :         E.A.Poe         From "For Annie" 1849

From owner-freebsd-current  Tue Mar 19 05:36:36 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id FAA28064
          for current-outgoing; Tue, 19 Mar 1996 05:36:36 -0800 (PST)
Received: from who.cdrom.com (who.cdrom.com [204.216.27.3])
          by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id FAA27915
          Tue, 19 Mar 1996 05:35:54 -0800 (PST)
Received: from neon.Glock.COM (root@neon.glock.com [198.82.228.159])
          by who.cdrom.com (8.6.12/8.6.11) with ESMTP id FAA26774
          ; Tue, 19 Mar 1996 05:35:47 -0800
Received: (from mmead@localhost) by neon.Glock.COM (8.7.4/8.7.3) id IAA04177; Tue, 19 Mar 1996 08:34:18 -0500 (EST)
From: "matthew c. mead" <mmead@Glock.COM>
Message-Id: <199603191334.IAA04177@neon.Glock.COM>
Subject: Re: new sup server
To: dima@freebsd.org (Dima Ruban)
Date: Tue, 19 Mar 1996 08:34:18 -0500 (EST)
Cc: hackers@freebsd.org, current@freebsd.org
In-Reply-To: <199603191022.CAA19365@freefall.freebsd.org> from "Dima Ruban" at Mar 19, 96 02:22:40 am
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

Dima Ruban writes:

> Hi there!
> 
> New sup server for current/stable/cvs is operational and ready.
> Please use it. (This server is on T3, so it should work
> pretty fast). Questions and/or comments to dima@best.net.
> Oops, almost forgot. This is sup5.freebsd.org
> 
> Enjoy.

	How much lag behind freefall is it?


-matt

-- 
Matthew C. Mead

mmead@Glock.COM
http://www.Glock.COM/~mmead/

From owner-freebsd-current  Tue Mar 19 08:25:21 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id IAA12527
          for current-outgoing; Tue, 19 Mar 1996 08:25:21 -0800 (PST)
Received: from halloran-eldar.lcs.mit.edu (halloran-eldar.lcs.mit.edu [18.26.0.159])
          by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id IAA12520
          for <current@FreeBSD.org>; Tue, 19 Mar 1996 08:25:11 -0800 (PST)
Received: by halloran-eldar.lcs.mit.edu; (5.65/1.1.8.2/19Aug95-0530PM)
	id AA32720; Tue, 19 Mar 1996 11:23:33 -0500
Date: Tue, 19 Mar 1996 11:23:33 -0500
From: "Garrett A. Wollman" <wollman@lcs.mit.edu>
Message-Id: <9603191623.AA32720@halloran-eldar.lcs.mit.edu>
To: Greg Lehey <lehey.pad@sni.de>
Cc: current@FreeBSD.org (Users of FreeBSD -current)
Subject: How to develop software and track current?
In-Reply-To: <199603191049.LAA00676@nixpbe.pdb.sni.de>
References: <199603191049.LAA00676@nixpbe.pdb.sni.de>
Sender: owner-current@FreeBSD.org
X-Loop: FreeBSD.org
Precedence: bulk

<<On Tue, 19 Mar 96 11:46:24 MET, Greg Lehey <lehey.pad@sni.de> said:

> I'm currently about to start some active work on the ISDN software,
> and I face a problem: I'm also tracking -current.  How to I ensure
> that I get my updates to -current and also maintain the modifications
> I make to the ISDN software?

1) You make your modifications in a checked-out source tree, and sup
the cvs tree.  To integrate changes, use `cvs -q update -dP'.

2) You make your modifications in the source tree, and sup same.  You
keep a list of modified files, and a set of programs allow you to
hide/unhide them from sup and determine when they need to be ftp'd to
freefall to be merged.

I don't have the disk space for (1), so I do (2).  (I could probably
/get/ the disk space, but it's more pain than I want to deal with
right now.)  (1) is a lot easier, /if/ you have the disk space.

-GAWollman

--
Garrett A. Wollman   | Shashish is simple, it's discreet, it's brief. ... 
wollman@lcs.mit.edu  | Shashish is the bonding of hearts in spite of distance.
Opinions not those of| It is a bond more powerful than absence.  We like people
MIT, LCS, ANA, or NSA| who like Shashish.  - Claude McKenzie + Florent Vollant

From owner-freebsd-current  Tue Mar 19 08:28:00 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id IAA12605
          for current-outgoing; Tue, 19 Mar 1996 08:28:00 -0800 (PST)
Received: from halloran-eldar.lcs.mit.edu (halloran-eldar.lcs.mit.edu [18.26.0.159])
          by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id IAA12596
          for <current@FreeBSD.ORG>; Tue, 19 Mar 1996 08:27:55 -0800 (PST)
Received: by halloran-eldar.lcs.mit.edu; (5.65/1.1.8.2/19Aug95-0530PM)
	id AA32692; Tue, 19 Mar 1996 11:27:00 -0500
Date: Tue, 19 Mar 1996 11:27:00 -0500
From: "Garrett A. Wollman" <wollman@lcs.mit.edu>
Message-Id: <9603191627.AA32692@halloran-eldar.lcs.mit.edu>
To: Joerg Wunsch <joerg@freefall.freebsd.org>
Cc: FreeBSD-Current Mailing List <current@FreeBSD.ORG>
Subject: cvs commit:  src/gnu/usr.bin/cpio copyin.c
In-Reply-To: <199603182308.PAA10754@freefall.freebsd.org>
References: <199603182308.PAA10754@freefall.freebsd.org>
Sender: owner-current@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

<<On Mon, 18 Mar 1996 15:08:31 -0800 (PST), Joerg Wunsch <joerg@freefall.freebsd.org> said:

> joerg       96/03/18 15:08:30
>   Modified:    gnu/usr.bin/cpio  copyin.c
>   Log:
>   Fix an infinite loop for empty files in the archive, and handle
>   sparsely stored linked files correctly.
  
Perhaps it's again time to look at implementing a cpio interface to
pax(1) so that we can get rid of the duplicate functionality?  (pax
already knows how to read cpio archives.)

-GAWollman

--
Garrett A. Wollman   | Shashish is simple, it's discreet, it's brief. ... 
wollman@lcs.mit.edu  | Shashish is the bonding of hearts in spite of distance.
Opinions not those of| It is a bond more powerful than absence.  We like people
MIT, LCS, ANA, or NSA| who like Shashish.  - Claude McKenzie + Florent Vollant

From owner-freebsd-current  Tue Mar 19 08:57:22 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id IAA14986
          for current-outgoing; Tue, 19 Mar 1996 08:57:22 -0800 (PST)
Received: from localhost.cdrom.com (localhost.cdrom.com [127.0.0.1])
          by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id IAA14981
          Tue, 19 Mar 1996 08:57:20 -0800 (PST)
Message-Id: <199603191657.IAA14981@freefall.freebsd.org>
X-Authentication-Warning: freefall.freebsd.org: Host localhost.cdrom.com [127.0.0.1] didn't use HELO protocol
To: Mostyn/Annabella <mrl@teleport.com>
cc: current@freebsd.org
Subject: Re: aic7xxx driver problem with wide and narrow busses attached.
In-reply-to: Your message of "Mon, 18 Mar 1996 19:31:48 PST."
             <199603190331.TAA04150@linda.teleport.com> 
Date: Tue, 19 Mar 1996 08:57:20 -0800
From: "Justin T. Gibbs" <gibbs@freefall.freebsd.org>
Sender: owner-current@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk


Disable parity detection in SCSI-Select.  I'm still trying to 
track down why this happens on machines that have both a 
Wide and narrow bus attached.  (Hey Rod... care to lend me
a wide disk again? 8-)

I'll turn parity error checking off again in the driver for now.

>Mostyn Lewis

--
Justin T. Gibbs
===========================================
  FreeBSD: Turning PCs into workstations
===========================================

From owner-freebsd-current  Tue Mar 19 09:47:43 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id JAA18119
          for current-outgoing; Tue, 19 Mar 1996 09:47:43 -0800 (PST)
Received: from sequent.kiae.su (sequent.kiae.su [144.206.136.6])
          by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id JAA18107
          for <current@freebsd.org>; Tue, 19 Mar 1996 09:47:31 -0800 (PST)
Received: by sequent.kiae.su id AA17792
  (5.65.kiae-2  for current@freebsd.org); Tue, 19 Mar 1996 20:39:06 +0300
Received: by sequent.KIAE.su (UUMAIL/2.0); Tue, 19 Mar 96 20:39:06 +0300
Received: (from ache@localhost) by astral.msk.su (8.7.5/8.7.3) id UAA04871 for current@freebsd.org; Tue, 19 Mar 1996 20:26:28 +0300 (MSK)
To: current@freebsd.org
Message-Id: <KH1vkJnyjI@astral.msk.su>
Organization: Olahm Ha-Yetzirah
Date: Tue, 19 Mar 1996 20:26:25 +0300 (MSK)
X-Mailer: Mail/@ [v2.42 FreeBSD]
From: =?KOI8-R?Q?=E1=CE=C4=D2=C5=CA_=FE=C5=D2=CE=CF=D7?=
    (aka Andrey A. Chernov, Black Mage) <ache@astral.msk.su>
X-Class: Fast
Subject: qcam module compile error
Lines: 12
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

ld -r  -o tmp.o qcam.o
symorder -c symb.tmp tmp.o
symorder: 1 symbol not found:
_qcam_mod
*** Error code 1

Stop.
-- 
Andrey A. Chernov        : And I rest so composedly,  /Now, in my bed,
ache@astral.msk.su       : That any beholder  /Might fancy me dead -
http://dt.demos.su/~ache : Might start at beholding me,  /Thinking me dead.
RELCOM Team,FreeBSD Team :         E.A.Poe         From "For Annie" 1849

From owner-freebsd-current  Tue Mar 19 10:46:32 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id KAA21661
          for current-outgoing; Tue, 19 Mar 1996 10:46:32 -0800 (PST)
Received: from rocky.sri.MT.net (rocky.sri.MT.net [204.182.243.10])
          by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id KAA21655
          Tue, 19 Mar 1996 10:46:29 -0800 (PST)
Received: (from nate@localhost) by rocky.sri.MT.net (8.6.12/8.6.12) id LAA04511; Tue, 19 Mar 1996 11:49:10 -0700
Date: Tue, 19 Mar 1996 11:49:10 -0700
From: Nate Williams <nate@sri.MT.net>
Message-Id: <199603191849.LAA04511@rocky.sri.MT.net>
To: "Garrett A. Wollman" <wollman@lcs.mit.edu>
Cc: Joerg Wunsch <joerg@freefall.freebsd.org>,
        FreeBSD-Current Mailing List <current@FreeBSD.ORG>
Subject: Re: cvs commit:  src/gnu/usr.bin/cpio copyin.c
In-Reply-To: <9603191627.AA32692@halloran-eldar.lcs.mit.edu>
References: <199603182308.PAA10754@freefall.freebsd.org>
	<9603191627.AA32692@halloran-eldar.lcs.mit.edu>
Sender: owner-current@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

> >   Modified:    gnu/usr.bin/cpio  copyin.c
> >   Log:
> >   Fix an infinite loop for empty files in the archive, and handle
> >   sparsely stored linked files correctly.
>   
> Perhaps it's again time to look at implementing a cpio interface to
> pax(1) so that we can get rid of the duplicate functionality?  (pax
> already knows how to read cpio archives.)

And tar as well.  I believe BSDi uses pax for both cpio and tar in their
releases.



Nate

From owner-freebsd-current  Tue Mar 19 11:19:43 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id LAA23370
          for current-outgoing; Tue, 19 Mar 1996 11:19:43 -0800 (PST)
Received: from GndRsh.aac.dev.com (GndRsh.aac.dev.com [198.145.92.241])
          by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id LAA23365
          Tue, 19 Mar 1996 11:19:40 -0800 (PST)
Received: (from rgrimes@localhost) by GndRsh.aac.dev.com (8.6.12/8.6.12) id LAA21274; Tue, 19 Mar 1996 11:19:35 -0800
From: "Rodney W. Grimes" <rgrimes@GndRsh.aac.dev.com>
Message-Id: <199603191919.LAA21274@GndRsh.aac.dev.com>
Subject: Re: aic7xxx driver problem with wide and narrow busses attached.
To: gibbs@freefall.freebsd.org (Justin T. Gibbs)
Date: Tue, 19 Mar 1996 11:19:35 -0800 (PST)
Cc: mrl@teleport.com, current@Freebsd.Org
In-Reply-To: <199603191657.IAA14981@freefall.freebsd.org> from "Justin T. Gibbs" at Mar 19, 96 08:57:20 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

> 
> 
> Disable parity detection in SCSI-Select.  I'm still trying to 
> track down why this happens on machines that have both a 
> Wide and narrow bus attached.  (Hey Rod... care to lend me
> a wide disk again? 8-)
> 
I'll have to do some house cleaning... my spare wide drive is a bit
full of data right now:
/dev/sd1a     2088244  1936934   -15750   101%    /B

> I'll turn parity error checking off again in the driver for now.

I'll slap a narrow disk on my 2940W and see if I can duplicate it
here, if it does duplicate I'll see about getting this data rolled
out to other disks and get it down to you for a debug session...

Should I be able to duplicate this in -stable, or does this problem
only seem to be occuring with -current?

-- 
Rod Grimes                                      rgrimes@gndrsh.aac.dev.com
Accurate Automation Company                 Reliable computers for FreeBSD

From owner-freebsd-current  Tue Mar 19 11:29:02 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id LAA24073
          for current-outgoing; Tue, 19 Mar 1996 11:29:02 -0800 (PST)
Received: from halloran-eldar.lcs.mit.edu (halloran-eldar.lcs.mit.edu [18.26.0.159])
          by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id LAA24068
          for <current@FreeBSD.ORG>; Tue, 19 Mar 1996 11:29:00 -0800 (PST)
Received: by halloran-eldar.lcs.mit.edu; (5.65/1.1.8.2/19Aug95-0530PM)
	id AA01087; Tue, 19 Mar 1996 14:28:43 -0500
Date: Tue, 19 Mar 1996 14:28:43 -0500
From: "Garrett A. Wollman" <wollman@lcs.mit.edu>
Message-Id: <9603191928.AA01087@halloran-eldar.lcs.mit.edu>
To: Nate Williams <nate@sri.MT.net>
Cc: FreeBSD-Current Mailing List <current@FreeBSD.ORG>
Subject: Re: cvs commit:  src/gnu/usr.bin/cpio copyin.c
In-Reply-To: <199603191849.LAA04511@rocky.sri.MT.net>
References: <199603182308.PAA10754@freefall.freebsd.org>
	<9603191627.AA32692@halloran-eldar.lcs.mit.edu>
	<199603191849.LAA04511@rocky.sri.MT.net>
Sender: owner-current@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

<<On Tue, 19 Mar 1996 11:49:10 -0700, Nate Williams <nate@sri.MT.net> said:

> And tar as well.  I believe BSDi uses pax for both cpio and tar in their
> releases.

I think there are good reasons for keeping GNU tar as the standard
tar(1) (if only because it /is/ the standard tar(1)).

-GAWollman

--
Garrett A. Wollman   | Shashish is simple, it's discreet, it's brief. ... 
wollman@lcs.mit.edu  | Shashish is the bonding of hearts in spite of distance.
Opinions not those of| It is a bond more powerful than absence.  We like people
MIT, LCS, ANA, or NSA| who like Shashish.  - Claude McKenzie + Florent Vollant

From owner-freebsd-current  Tue Mar 19 12:06:05 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id MAA26310
          for current-outgoing; Tue, 19 Mar 1996 12:06:05 -0800 (PST)
Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211])
          by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id MAA26304
          Tue, 19 Mar 1996 12:06:01 -0800 (PST)
Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id NAA24594; Tue, 19 Mar 1996 13:00:35 -0700
From: Terry Lambert <terry@lambert.org>
Message-Id: <199603192000.NAA24594@phaeton.artisoft.com>
Subject: Re: How to develop software and track current?
To: lehey.pad@sni.de (Greg Lehey)
Date: Tue, 19 Mar 1996 13:00:34 -0700 (MST)
Cc: hackers@FreeBSD.org, current@FreeBSD.org
In-Reply-To: <199603191049.LAA00671@nixpbe.pdb.sni.de> from "Greg Lehey" at Mar 19, 96 11:46: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

> I'm currently about to start some active work on the ISDN software,
> and I face a problem: I'm also tracking -current.  How to I ensure
> that I get my updates to -current and also maintain the modifications
> I make to the ISDN software?  The problem is compounded by the fact
> that I don't get on very well with cvs, so if the following text
> contains nonsense, please be nice :-) I can see a number of
> possibilities:
> 
> 1.  Create a new cvs tag, say "2.2-CURRENT-grog", and put all my
>     changes there.  The problem I anticipate here are that I won't be
>     able to automatically track the ctm updates.
> 
> 2.  Check my changes in to 2.2-CURRENT every evening.  This seems to
>     have a number of potential problems: first, if I forget to check
>     in, I lose my updates, and secondly, somebody else might check in
>     files which I have changed.  Presumably the latter action would
>     cause the cvs update to blow up.
> 
> 3.  Create a new directory outside the control of cvs.  This sounds
>     like a real kludge.
> 
> This is obviously a problem that a lot of people have already solved,
> at least to their own satisfaction.  If we can come up with a clean,
> consistent way of doing it, I'll gladly contribute some documentation
> on the subject.

Soloutions 1 & 2 are only available if you have commit priviledges.

Soloution 3 is silly.

The typical way you do this without committing is to sup the CVS tree
on a nightly basis.

You checkout a local copy of the tree, and build there.

You make your mods in the checked out tree.

You use "cvs update" and "cvs diff".

You submit patch sets vs. a merged tree as you see opportunities to
have them reviewed by people who do have commit privs.

When they are committed. the local diffs involved go away after the
update following the commit.


					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 Mar 19 12:06:36 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id MAA26386
          for current-outgoing; Tue, 19 Mar 1996 12:06:36 -0800 (PST)
Received: (from dima@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id MAA26365
          Tue, 19 Mar 1996 12:06:33 -0800 (PST)
Message-Id: <199603192006.MAA26365@freefall.freebsd.org>
Subject: Re: new sup server
To: mmead@Glock.COM (matthew c. mead)
Date: Tue, 19 Mar 1996 12:06:33 -0800 (PST)
Cc: dima@freebsd.org, hackers@freebsd.org, current@freebsd.org
In-Reply-To: <199603191334.IAA04177@neon.Glock.COM> from "matthew c. mead" at Mar 19, 96 08:34:18 am
From: dima@freebsd.org (Dima Ruban)
X-Class: Fast
Organization: HackerDome
X-Mailer: ELM [version 2.4 PL24]
Content-Type: text
Sender: owner-current@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

matthew c. mead writes:
> 
> Dima Ruban writes:
> 
> > Hi there!
> > 
> > New sup server for current/stable/cvs is operational and ready.
> > Please use it. (This server is on T3, so it should work
> > pretty fast). Questions and/or comments to dima@best.net.
> > Oops, almost forgot. This is sup5.freebsd.org
> > 
> > Enjoy.
> 
> 	How much lag behind freefall is it?


I'm running SUP 2 times a day, 12pm and 12am

> 
> 
> -matt
> 
> -- 
> Matthew C. Mead
> 
> mmead@Glock.COM
> http://www.Glock.COM/~mmead/
> 

-- dima

From owner-freebsd-current  Tue Mar 19 12:44:40 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id MAA29636
          for current-outgoing; Tue, 19 Mar 1996 12:44:40 -0800 (PST)
Received: from desiree.teleport.com (desiree.teleport.com [192.108.254.21])
          by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id MAA29625
          Tue, 19 Mar 1996 12:44:30 -0800 (PST)
Received: from linda.teleport.com (mrl@linda.teleport.com [192.108.254.12]) by desiree.teleport.com (8.6.12/8.6.9) with ESMTP id LAA16052; Tue, 19 Mar 1996 11:34:07 -0800
From: Mostyn/Annabella <mrl@teleport.com>
Received: (mrl@localhost) by linda.teleport.com (8.6.12/8.6.12) id LAA25294; Tue, 19 Mar 1996 11:34:07 -0800
Message-Id: <199603191934.LAA25294@linda.teleport.com>
Subject: Re: SCSI death in -current with DAT
To: gibbs@freefall.freebsd.org (Justin T. Gibbs)
Date: Tue, 19 Mar 1996 11:34:07 -0800 (PST)
Cc: current@freebsd.org, mrl@teleport.com, joerg_wunsch@uriah.heep.sax.de
In-Reply-To: <199603191708.JAA15782@freefall.freebsd.org> from "Justin T. Gibbs" at Mar 19, 96 09:08:20 am
X-Mailer: ELM [version 2.4 PL25]
Content-Type: text
Sender: owner-current@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

> 
> Its an aic7xxx driver problem related to parity checking which I
> recently enabled.  It seems that you get harmless parity errors
> when you have both a wide and narrow bus attached to the controller
> at one time.  I'm still investigating, but people seeing this problem
> should just disable parity checking in SCSI-Select.
              ^^^^^^^^^^^^^^^^^^^^^^^

Thank you very much. With parity switched off by the controller,
the DAT worked fine backing up a wide drive using a March 17th
-current system.

J"org, thank you for the fixed-block setup for the DAT - I didn't
use it but I'll keep it just in case.

Regards,
Mostyn Lewis

From owner-freebsd-current  Tue Mar 19 13:24:24 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id NAA02404
          for current-outgoing; Tue, 19 Mar 1996 13:24:24 -0800 (PST)
Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11])
          by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id NAA02387
          Tue, 19 Mar 1996 13:24:13 -0800 (PST)
Received: from sax.sax.de by irz301.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id VAA18130; Tue, 19 Mar 1996 21:51:46 +0100
Received: by sax.sax.de (8.6.11/8.6.12-s1) with UUCP
	id VAA02651; Tue, 19 Mar 1996 21:51:46 +0100
Received: (from j@localhost) by uriah.heep.sax.de (8.7.4/8.6.9) id VAA03933; Tue, 19 Mar 1996 21:50:31 +0100 (MET)
From: J Wunsch <j@uriah.heep.sax.de>
Message-Id: <199603192050.VAA03933@uriah.heep.sax.de>
Subject: Re: cvs commit:  src/gnu/usr.bin/cpio copyin.c
To: wollman@lcs.mit.edu (Garrett A. Wollman)
Date: Tue, 19 Mar 1996 21:50:31 +0100 (MET)
Cc: joerg@freefall.freebsd.org, current@FreeBSD.ORG
Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch)
In-Reply-To: <9603191627.AA32692@halloran-eldar.lcs.mit.edu> from "Garrett A. Wollman" at Mar 19, 96 11:27:00 am
X-Phone: +49-351-2012 669
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

As Garrett A. Wollman wrote:

> Perhaps it's again time to look at implementing a cpio interface to
> pax(1) so that we can get rid of the duplicate functionality?  (pax
> already knows how to read cpio archives.)

I've tried pax for the cited archive, and it proved to be even more
broken (about the same as SysV cpio :-).  So i decided to pick the
cpio fix instead.

-- 
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  Tue Mar 19 14:20:18 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id OAA05645
          for current-outgoing; Tue, 19 Mar 1996 14:20:18 -0800 (PST)
Received: from alpha.xerox.com (alpha.Xerox.COM [13.1.64.93])
          by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id OAA05617
          for <freebsd-current@freebsd.org>; Tue, 19 Mar 1996 14:20:12 -0800 (PST)
Received: from gemini.sdsp.mc.xerox.com ([13.231.132.20]) by alpha.xerox.com with SMTP id <16319(9)>; Tue, 19 Mar 1996 14:19:20 PST
Received: from gnu.mc.xerox.com (gnu.sdsp.mc.xerox.com) by gemini.sdsp.mc.xerox.com (4.1/SMI-4.1)
	id AA25618; Tue, 19 Mar 96 17:19:26 EST
Received: by gnu.mc.xerox.com (4.1/SMI-4.1)
	id AA08984; Tue, 19 Mar 96 17:19:25 EST
Message-Id: <9603192219.AA08984@gnu.mc.xerox.com>
X-Mailer: exmh version 1.6.4 10/10/95
To: John Polstra <jdp@polstra.com>
Cc: Michael Smith <msmith@atrad.adelaide.edu.au>,
        coredump@nervosa.com (invalid opcode), freebsd-current@freebsd.org
Subject: Re: Elfkit release 1.1 is now available 
In-Reply-To: Your message of "Mon, 18 Mar 1996 18:38:23 PST."
             <199603190238.SAA04211@austin.polstra.com> 
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Tue, 19 Mar 1996 14:19:20 PST
From: "Marty Leisner" <leisner@sdsp.mc.xerox.com>
Sender: owner-current@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk


I'm crosscompiling from Linux to djgpp and i386-pe...

With the right scripts/specs files (i.e. I have a script
to run the crosscompilers) , cross compilation is not  a big deal..

A common set of binutils is very useful...when I configure the
binutils for linux-a.out and bsd-a.out it gets confused (most of the time
it auto guesses...)

When will the changes be rolled into binutils?
-- 
marty
leisner@sdsp.mc.xerox.com  
Member of the League for Programming Freedom



From owner-freebsd-current  Tue Mar 19 14:38:54 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id OAA06728
          for current-outgoing; Tue, 19 Mar 1996 14:38:54 -0800 (PST)
Received: from mail.think.com (Mail1.Think.COM [131.239.33.245])
          by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id OAA06719
          for <current@freefall.freebsd.org>; Tue, 19 Mar 1996 14:38:48 -0800 (PST)
Received: from Early-Bird-1.Think.COM by mail.think.com; Tue, 19 Mar 96 17:38:47 -0500
Received: from compound (fergus-29.dialup.cfa.org) by Early-Bird.Think.COM; Tue, 19 Mar 96 17:38:43 EST
Received: (from alk@localhost) by compound (8.6.12/8.6.112) id QAA18506; Tue, 19 Mar 1996 16:39:06 -0600
Date: Tue, 19 Mar 1996 16:39:06 -0600
Message-Id: <199603192239.QAA18506@compound>
From: Tony Kimball <alk@Think.COM>
To: current@freefall.freebsd.org
In-Reply-To: <199603191919.LAA23380@freefall.freebsd.org>
	(owner-current-digest@freefall.freebsd.org)
Subject: perl4
Sender: owner-current@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk



   I don't think this is a good argument:
   - - you already have perl in /usr/bin  AND  in /usr/local/bin!

So remove them both from the base distribution.  p4 can be made a
package at zero-maintenance cost.  How much breaks, and how hard is
it to fix?

./bin/makewhatis: a /usr/bin/perl script text
./bin/catman: a /usr/bin/perl script text
./bin/killall: a /usr/bin/perl script text
./bin/sgmlfmt: a /usr/bin/perl script text
./bin/which: a /usr/bin/perl script text
./sbin/adduser: a /usr/bin/perl script text
./sbin/kbdmap: a /usr/bin/perl script text
./sbin/vidfont: a /usr/bin/perl script text
./sbin/spkrtest: a /usr/bin/perl script text

Not much.  Eliminate it, and that reduces the installed base OS size
by 4MB, meaning more installations, more market share, better
differentiation from bloated commercial systems.

If I write C versions of these scripts, will that suffice
to break perl off into a package?

//alk










From owner-freebsd-current  Tue Mar 19 14:40:54 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id OAA06951
          for current-outgoing; Tue, 19 Mar 1996 14:40:54 -0800 (PST)
Received: from GndRsh.aac.dev.com (GndRsh.aac.dev.com [198.145.92.241])
          by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id OAA06944
          for <freebsd-current@FreeBSD.org>; Tue, 19 Mar 1996 14:40:49 -0800 (PST)
Received: (from rgrimes@localhost) by GndRsh.aac.dev.com (8.6.12/8.6.12) id OAA21620; Tue, 19 Mar 1996 14:38:42 -0800
From: "Rodney W. Grimes" <rgrimes@GndRsh.aac.dev.com>
Message-Id: <199603192238.OAA21620@GndRsh.aac.dev.com>
Subject: Re: 2.2-960226-SNAP now on ftp.freebsd.org
To: bde@zeta.org.au (Bruce Evans)
Date: Tue, 19 Mar 1996 14:38:41 -0800 (PST)
Cc: joerg_wunsch@uriah.heep.sax.de, freebsd-current@FreeBSD.org
In-Reply-To: <199603061643.DAA29892@godzilla.zeta.org.au> from "Bruce Evans" at Mar 7, 96 03:43:14 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

> 
> >> Don't forget /.profile, for the single-user shell.
> 
> >/.profile is a hardlink to /root/.profile.
> 
> Yuck.  I've never installed it.

It is very handy when booted single user as the root shell in that
case has a home directory of / instead of /root.  I am pretty sure
that was the reason that CSRG added this link when they moved root's
home directory from / to /root.

This also applies to /.cshrc -> /root/.cshrc (hard link) same reason,
only when you ask for the single user shell to be /bin/csh.

> The system-wide profile /etc/profile isn't installed.  It should be
> installed and contain only comments in it, like /etc/csh.login.

WHAT???:
SkyRsh# ls -lag /etc/prof*
-rw-r--r--  1 root  wheel  570 Mar 16 16:03 /etc/profile
SkyRsh# more !$
more /etc/prof*
# System-wide .profile file for sh(1).
# Uncomment this to give you the default 4.2 behavior, where disk 
# information is shown in K-Blocks
# BLOCKSIZE=K; export BLOCKSIZE
# Uncomment next line if you want to setup your 8-bit locale at program
# startup automatically
# See also rc and csh.login
# ENABLE_STARTUP_LOCALE=; export ENABLE_STARTUP_LOCALE
# Uncomment next line to activate russian locale
# LANG=ru_SU.KOI8-R; export LANG
# Uncomment next line to activate italian locale
# LANG=it_IT.ISO_8859-1; export LANG
# For full locales list check /usr/share/locale/*
SkyRsh# 

Looks installed to me, and infact only contains comments.  

> Perhaps something like /etc/csh.cshrc should be implemented using
> $ENV.

Oh, you mean it is not used by /bin/sh???


-- 
Rod Grimes                                      rgrimes@gndrsh.aac.dev.com
Accurate Automation Company                 Reliable computers for FreeBSD

From owner-freebsd-current  Tue Mar 19 14:49:13 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id OAA07639
          for current-outgoing; Tue, 19 Mar 1996 14:49:13 -0800 (PST)
Received: from genesis.atrad.adelaide.edu.au (genesis.atrad.adelaide.edu.au [129.127.96.120])
          by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id OAA07617
          Tue, 19 Mar 1996 14:48:57 -0800 (PST)
Received: from msmith@localhost by genesis.atrad.adelaide.edu.au (8.6.12/8.6.9) id JAA02582; Wed, 20 Mar 1996 09:33:11 +1030
From: Michael Smith <msmith@atrad.adelaide.edu.au>
Message-Id: <199603192303.JAA02582@genesis.atrad.adelaide.edu.au>
Subject: Re: How to develop software and track current?
To: lehey.pad@sni.de (Greg Lehey)
Date: Wed, 20 Mar 1996 09:33:10 +1030 (CST)
Cc: hackers@FreeBSD.org, current@FreeBSD.org
In-Reply-To: <199603191049.LAA00671@nixpbe.pdb.sni.de> from "Greg Lehey" at Mar 19, 96 11:46:24 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

Greg Lehey stands accused of saying:
> 
> 3.  Create a new directory outside the control of cvs.  This sounds
>     like a real kludge.

This is how I do it.  I take a snapshot of the kernel as it stands at a
given point, park it somewhere, then symlink out of it into a
seperate directory that holds the files I'm actually working on.

> Greg

-- 
]] 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  Tue Mar 19 15:03:04 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id PAA08790
          for current-outgoing; Tue, 19 Mar 1996 15:03:04 -0800 (PST)
Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211])
          by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id PAA08784
          for <freebsd-current@FreeBSD.ORG>; Tue, 19 Mar 1996 15:02:59 -0800 (PST)
Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id PAA25010; Tue, 19 Mar 1996 15:53:46 -0700
From: Terry Lambert <terry@lambert.org>
Message-Id: <199603192253.PAA25010@phaeton.artisoft.com>
Subject: Re: Elfkit release 1.1 is now available
To: mrami@minerva.cis.yale.edu
Date: Tue, 19 Mar 1996 15:53:46 -0700 (MST)
Cc: leisner@sdsp.mc.xerox.com, msmith@atrad.adelaide.edu.au,
        coredump@nervosa.com, jdp@polstra.com, freebsd-current@FreeBSD.ORG
In-Reply-To: <Pine.BSF.3.91.960318211018.1468D-100000@mramirez.sy.yale.edu> from "Marc Ramirez" at Mar 18, 96 09:11:00 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

> > With the ELF stuff:
> > 	2) is there a difference between linux-elf and freebsd-elf?
> > 	Or is it just i386-elf?
> 
> There is a difference: different syscall numbers.

This is a function of the library code, not the ELF code.  The magic
numbers for the linker should be, I think, different because of the
system call ABI, but that sould be a linker thing...


					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 Mar 19 15:05:48 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id PAA08996
          for current-outgoing; Tue, 19 Mar 1996 15:05:48 -0800 (PST)
Received: from GndRsh.aac.dev.com (GndRsh.aac.dev.com [198.145.92.241])
          by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id PAA08991
          Tue, 19 Mar 1996 15:05:44 -0800 (PST)
Received: (from rgrimes@localhost) by GndRsh.aac.dev.com (8.6.12/8.6.12) id PAA21675; Tue, 19 Mar 1996 15:05:17 -0800
From: "Rodney W. Grimes" <rgrimes@GndRsh.aac.dev.com>
Message-Id: <199603192305.PAA21675@GndRsh.aac.dev.com>
Subject: Re: SCSI death in -current with DAT
To: mrl@teleport.com (Mostyn/Annabella)
Date: Tue, 19 Mar 1996 15:05:17 -0800 (PST)
Cc: gibbs@freefall.freebsd.org, current@FreeBSD.ORG, mrl@teleport.com,
        joerg_wunsch@uriah.heep.sax.de
In-Reply-To: <199603191934.LAA25294@linda.teleport.com> from "Mostyn/Annabella" at Mar 19, 96 11:34:07 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

> 
> > 
> > Its an aic7xxx driver problem related to parity checking which I
> > recently enabled.  It seems that you get harmless parity errors
> > when you have both a wide and narrow bus attached to the controller
> > at one time.  I'm still investigating, but people seeing this problem
> > should just disable parity checking in SCSI-Select.
>               ^^^^^^^^^^^^^^^^^^^^^^^
> 
> Thank you very much. With parity switched off by the controller,
> the DAT worked fine backing up a wide drive using a March 17th
> -current system.
> 
> J"org, thank you for the fixed-block setup for the DAT - I didn't
> use it but I'll keep it just in case.

The Archive/Conner Python 28388 DAT drives are variable block length capable
drives, this patch is not needed, and should not be applied to any system.


-- 
Rod Grimes                                      rgrimes@gndrsh.aac.dev.com
Accurate Automation Company                 Reliable computers for FreeBSD

From owner-freebsd-current  Tue Mar 19 15:41:57 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id PAA11331
          for current-outgoing; Tue, 19 Mar 1996 15:41:57 -0800 (PST)
Received: from ki.net (root@ki.net [142.77.249.8])
          by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id PAA11315
          for <current@freebsd.org>; Tue, 19 Mar 1996 15:41:41 -0800 (PST)
Received: (from scrappy@localhost) by ki.net (8.7.4/8.7.4) id PAA03033; Tue, 19 Mar 1996 15:28:10 -0500 (EST)
Date: Tue, 19 Mar 1996 15:28:08 -0500 (EST)
From: "Marc G. Fournier" <scrappy@ki.net>
To: current@freebsd.org
Subject: NIS problem
Message-ID: <Pine.BSF.3.91.960319152223.249A-100000@ki.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-current@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk


Hi...

	I'm not sure if its something I'm forgetting to run, or if
its a bug somewhere, but I can't seem to get login's working on my
-current machine with NIS running.

	I've set the appropriate settings in sysconfig, and am running
ypbind -s on that machine, but try as I might, I can't login to that
machine unless the user entry is in the password file on that machine.

	If I run chsh userid, it will grab the NIS data though.

	Someone asked if maybe I had md5 instead of des encryption
installed, so that the encryption mechanisms are different, but an 
md5 encrypted password is a substantially "longer" string then a des
encrypted one, so as far as I can see, both are using des.

	The ypserver is a -stable box, if that means anything?  I know
there were some changes recently to -current's des, but I wouldn't have
assumed that those would have affected it in such a way as to produce
this sort of problem...would it?

Thanks...

Marc G. Fournier | POP Mail  Telnet Acct  DNS Hosting
System           |  WWW Services   Database Services  | Knowledge, 
  Administrator  |                                    | Information and
 scrappy@ki.net  |      WWW: http://www.ki.net        | Communications, Inc


From owner-freebsd-current  Tue Mar 19 15:42:36 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id PAA11380
          for current-outgoing; Tue, 19 Mar 1996 15:42:36 -0800 (PST)
Received: from ki.net (root@ki.net [142.77.249.8])
          by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id PAA11345
          Tue, 19 Mar 1996 15:41:59 -0800 (PST)
Received: (from scrappy@localhost) by ki.net (8.7.4/8.7.4) id PAA03872; Tue, 19 Mar 1996 15:31:12 -0500 (EST)
Date: Tue, 19 Mar 1996 15:31:08 -0500 (EST)
From: "Marc G. Fournier" <scrappy@ki.net>
To: current@freebsd.org
cc: stable@freebsd.org
Subject: Sendmail 8.6.12 -> 8.7.5
Message-ID: <Pine.BSF.3.91.960319152817.249B-100000@ki.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-current@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk


Hi...

	Just wondering if there is any reason why Sendmail 8.7.5 hasn't
been migrated/commited to the -stable source tree?  If there is none, 
can someone do it?  I'm currently running 8.7.4 on my -stable machine,
and doing a 'make world' with the current sources is kinda difficult if
I don't want to wipe out my current sendmail :(

Thanks...

Marc G. Fournier | POP Mail  Telnet Acct  DNS Hosting
System           |  WWW Services   Database Services  | Knowledge, 
  Administrator  |                                    | Information and
 scrappy@ki.net  |      WWW: http://www.ki.net        | Communications, Inc


From owner-freebsd-current  Tue Mar 19 16:23:47 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id QAA14172
          for current-outgoing; Tue, 19 Mar 1996 16:23:47 -0800 (PST)
Received: from ki.net (root@ki.net [142.77.249.8])
          by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id QAA14161
          for <current@freebsd.org>; Tue, 19 Mar 1996 16:23:35 -0800 (PST)
Received: (from scrappy@localhost) by ki.net (8.7.4/8.7.4) id TAA16055; Tue, 19 Mar 1996 19:22:24 -0500 (EST)
Date: Tue, 19 Mar 1996 19:22:23 -0500 (EST)
From: "Marc G. Fournier" <scrappy@ki.net>
To: current@freebsd.org
Subject: system running with DEVFS
Message-ID: <Pine.BSF.3.91.960319191330.249G-100000@ki.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-current@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk


Hi...

	I don't know if anyone is actually using devfs yet, as mounted
onto /dev, but this afternoon I decided to try, and after some minor 
modifications to pcvt_drv.c, got my system up and running.

	One thing I'm curious about, though, is:

freebsd# ls -lt /devfs/log /dev/log
srw-rw-rw-  1 root  wheel         0 Mar 19 19:11 /dev/log
crw-------  2 root  wheel    7,   0 Mar 19 19:11 /devfs/log

	The two log devices seem to be created differently, but I'm 
wondering if it is something that should be worried about, or if it 
doesn't matter?  I'm assuming that the "correct" mode is the one in
/dev/log...but would like to confirm before I attempt to fix subr_log.c
to duplicate this properly.

	And there was a day I swore I wouldn't hack a kernel...:)

	Oh, what is dev_t?  I've looked through all the include files
trying to find it, and can't find where it is actually defined, altho
it is used an awful lot.  Which include file should I be looking in?

Thanks...

Marc G. Fournier | POP Mail  Telnet Acct  DNS Hosting
System           |  WWW Services   Database Services  | Knowledge, 
  Administrator  |                                    | Information and
 scrappy@ki.net  |      WWW: http://www.ki.net        | Communications, Inc


From owner-freebsd-current  Tue Mar 19 17:13:43 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id RAA17578
          for current-outgoing; Tue, 19 Mar 1996 17:13:43 -0800 (PST)
Received: from cabri.obs-besancon.fr (cabri.obs-besancon.fr [193.52.184.3])
          by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id RAA17569
          for <current@freefall.freebsd.org>; Tue, 19 Mar 1996 17:13:39 -0800 (PST)
Received: by cabri.obs-besancon.fr (5.57/Ultrix3.0-C)
	id AA09006; Wed, 20 Mar 96 02:15:43 +0100
Date: Wed, 20 Mar 96 02:15:43 +0100
Message-Id: <9603200115.AA09006@cabri.obs-besancon.fr>
From: Jean-Marc Zucconi <jmz@cabri.obs-besancon.fr>
To: alk@think.com
Cc: current@freefall.freebsd.org
In-Reply-To: <199603192239.QAA18506@compound> (message from Tony Kimball on
	Tue, 19 Mar 1996 16:39:06 -0600)
Subject: Re: perl4
X-Mailer: Emacs
Sender: owner-current@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

>>>>> Tony Kimball writes:

 >    I don't think this is a good argument:
 >    - - you already have perl in /usr/bin  AND  in /usr/local/bin!

 > So remove them both from the base distribution.  p4 can be made a
 > package at zero-maintenance cost.  How much breaks, and how hard is
 > it to fix?

 > ./bin/makewhatis: a /usr/bin/perl script text
 > ./bin/catman: a /usr/bin/perl script text
 > ./bin/killall: a /usr/bin/perl script text
 > ./bin/sgmlfmt: a /usr/bin/perl script text
 > ./bin/which: a /usr/bin/perl script text
 > ./sbin/adduser: a /usr/bin/perl script text
 > ./sbin/kbdmap: a /usr/bin/perl script text
 > ./sbin/vidfont: a /usr/bin/perl script text
 > ./sbin/spkrtest: a /usr/bin/perl script text

 > Not much.  Eliminate it, and that reduces the installed base OS size
 > by 4MB, meaning more installations, more market share, better
 > differentiation from bloated commercial systems.

 > If I write C versions of these scripts, will that suffice
 > to break perl off into a package?

If you really want reduce size, you may also consider the opposite
approach and replace all programs in /usr/bin with perl scripts
$ du -ks /usr/bin
11647   /usr/bin

:-)

Jean-Marc

 > //alk
 _____________________________________________________________________________
 Jean-Marc Zucconi       Observatoire de Besancon       F 25010 Besancon cedex
                   PGP Key: finger jmz@cabri.obs-besancon.fr
 =============================================================================

From owner-freebsd-current  Tue Mar 19 17:24:41 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id RAA18468
          for current-outgoing; Tue, 19 Mar 1996 17:24:41 -0800 (PST)
Received: from ref.tfs.com (ref.tfs.com [140.145.254.251])
          by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id RAA18457
          Tue, 19 Mar 1996 17:24:33 -0800 (PST)
Received: (from julian@localhost) by ref.tfs.com (8.7.3/8.6.9) id JAA02581; Tue, 19 Mar 1996 09:58:58 -0800 (PST)
Message-Id: <199603191758.JAA02581@ref.tfs.com>
Subject: Re: new sup server
To: mmead@Glock.COM (matthew c. mead)
Date: Tue, 19 Mar 1996 09:58:57 -0800 (PST)
From: "JULIAN Elischer" <julian@ref.tfs.com>
Cc: dima@freebsd.org, hackers@freebsd.org, current@freebsd.org
In-Reply-To: <199603191334.IAA04177@neon.Glock.COM> from "matthew c. mead" at Mar 19, 96 08:34:18 am
X-Mailer: ELM [version 2.4 PL25 ME8b]
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 fact what is the lag behing all the servers..
can we find out the update schedules for them?
it helps US shedule OUR updates..

julian
> 
> Dima Ruban writes:
> 
> > Hi there!
> > 
> > New sup server for current/stable/cvs is operational and ready.
> > Please use it. (This server is on T3, so it should work
> > pretty fast). Questions and/or comments to dima@best.net.
> > Oops, almost forgot. This is sup5.freebsd.org
> > 
> > Enjoy.
> 
> 	How much lag behind freefall is it?
> 
> 
> -matt
> 
> -- 
> Matthew C. Mead
> 
> mmead@Glock.COM
> http://www.Glock.COM/~mmead/
> 


From owner-freebsd-current  Tue Mar 19 17:42:19 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id RAA19804
          for current-outgoing; Tue, 19 Mar 1996 17:42:19 -0800 (PST)
Received: from GndRsh.aac.dev.com (GndRsh.aac.dev.com [198.145.92.241])
          by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id RAA19785
          Tue, 19 Mar 1996 17:42:09 -0800 (PST)
Received: (from rgrimes@localhost) by GndRsh.aac.dev.com (8.6.12/8.6.12) id RAA21881; Tue, 19 Mar 1996 17:40:31 -0800
From: "Rodney W. Grimes" <rgrimes@GndRsh.aac.dev.com>
Message-Id: <199603200140.RAA21881@GndRsh.aac.dev.com>
Subject: Re: Sendmail 8.6.12 -> 8.7.5
To: scrappy@ki.net (Marc G. Fournier)
Date: Tue, 19 Mar 1996 17:40:30 -0800 (PST)
Cc: current@freebsd.org, stable@freebsd.org
In-Reply-To: <Pine.BSF.3.91.960319152817.249B-100000@ki.net> from "Marc G. Fournier" at Mar 19, 96 03:31:08 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

> 
> 
> Hi...
> 
> 	Just wondering if there is any reason why Sendmail 8.7.5 hasn't
> been migrated/commited to the -stable source tree?  If there is none, 
> can someone do it?  I'm currently running 8.7.4 on my -stable machine,
> and doing a 'make world' with the current sources is kinda difficult if
> I don't want to wipe out my current sendmail :(
> 
> Thanks...

This is a way to work around your current situation:
cd /usr/src/usr.bin
cp Makefile makefile
vi makefile # nuke sendmail from the SUBDIR list

Now your upgraded sendmail will not get touched by a make world, nor
will your modified makefile get spammed by a sup or cvs update.  Just
don't forget to rm the makefile copy when sendmail does get upgraded.



-- 
Rod Grimes                                      rgrimes@gndrsh.aac.dev.com
Accurate Automation Company                 Reliable computers for FreeBSD

From owner-freebsd-current  Tue Mar 19 17:48:45 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id RAA20068
          for current-outgoing; Tue, 19 Mar 1996 17:48:45 -0800 (PST)
Received: from mail.think.com (Mail1.Think.COM [131.239.33.245])
          by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id RAA20058
          for <current@freefall.freebsd.org>; Tue, 19 Mar 1996 17:48:43 -0800 (PST)
Received: from Early-Bird-1.Think.COM by mail.think.com; Tue, 19 Mar 96 20:48:32 -0500
Received: from compound (fergus-29.dialup.cfa.org) by Early-Bird.Think.COM; Tue, 19 Mar 96 20:48:29 EST
Received: (from alk@localhost) by compound (8.6.12/8.6.112) id TAA11754; Tue, 19 Mar 1996 19:48:55 -0600
Date: Tue, 19 Mar 1996 19:48:55 -0600
Message-Id: <199603200148.TAA11754@compound>
From: Tony Kimball <alk@Think.COM>
To: jmz@cabri.obs-besancon.fr
In-Reply-To: <9603200115.AA09006@cabri.obs-besancon.fr> (message from
	Jean-Marc Zucconi on Wed, 20 Mar 96 02:15:43 +0100)
Cc: current@freefall.freebsd.org
Subject: Re: perl4
Sender: owner-current@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk


   replace all programs in /usr/bin with perl scripts
   $ du -ks /usr/bin
   11647   /usr/bin

Not a bad idea, except I think it would take a while longer to do.
(And a great while longer to stabilize to a reasonable confidence
level.) Of course 1.3M of that 11.6M is perl.






From owner-freebsd-current  Tue Mar 19 18:23:15 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id SAA21720
          for current-outgoing; Tue, 19 Mar 1996 18:23:15 -0800 (PST)
Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211])
          by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id SAA21705
          Tue, 19 Mar 1996 18:22:52 -0800 (PST)
Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id TAA25663; Tue, 19 Mar 1996 19:16:05 -0700
From: Terry Lambert <terry@lambert.org>
Message-Id: <199603200216.TAA25663@phaeton.artisoft.com>
Subject: Re: new sup server
To: julian@ref.tfs.com (JULIAN Elischer)
Date: Tue, 19 Mar 1996 19:16:05 -0700 (MST)
Cc: mmead@Glock.COM, dima@FreeBSD.ORG, hackers@FreeBSD.ORG,
        current@FreeBSD.ORG
In-Reply-To: <199603191758.JAA02581@ref.tfs.com> from "JULIAN Elischer" at Mar 19, 96 09:58:57 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

> In fact what is the lag behing all the servers..
> can we find out the update schedules for them?
> it helps US shedule OUR updates..

If they updated 3 times a day, you wouldn't care which server you got
if all you updated was once a day.

Lag time is only required for 2 or less updates a day by the secondary.


					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 Mar 19 18:24:41 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id SAA21883
          for current-outgoing; Tue, 19 Mar 1996 18:24:41 -0800 (PST)
Received: from who.cdrom.com (who.cdrom.com [204.216.27.3])
          by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id SAA21876
          for <freebsd-current@freebsd.org>; Tue, 19 Mar 1996 18:24:39 -0800 (PST)
Received: from bunyip.cc.uq.oz.au (pp@bunyip.cc.uq.oz.au [130.102.2.1])
          by who.cdrom.com (8.6.12/8.6.11) with SMTP id SAA12846
          for <freebsd-current@freebsd.org>; Tue, 19 Mar 1996 18:23:18 -0800
Received: from bunyip.cc.uq.oz.au by bunyip.cc.uq.oz.au 
          id <27125-0@bunyip.cc.uq.oz.au>; Wed, 20 Mar 1996 12:17:13 +1000
Received: from orion.devetir.qld.gov.au 
          by pandora.devetir.qld.gov.au (8.6.10/DEVETIR-E0.3a) with ESMTP 
          id MAA03745; Wed, 20 Mar 1996 12:17:00 +1000
Received: by orion.devetir.qld.gov.au (8.6.10/DEVETIR-0.3) id MAA11101;
          Wed, 20 Mar 1996 12:17:53 +1000
Date: Wed, 20 Mar 1996 12:17:53 +1000
From: Stephen McKay <syssgm@devetir.qld.gov.au>
Message-Id: <199603200217.MAA11101@orion.devetir.qld.gov.au>
To: Andreas Klemm <andreas@knobel.gun.de>
cc: freebsd-current@freebsd.org, syssgm@devetir.qld.gov.au
Subject: Re: Nvi alpha version 1.57 now available.
X-Newsreader: NN version 6.5.0 #1 (NOV)
Sender: owner-current@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

Andreas Klemm <andreas@knobel.gun.de> wrote:

>On Mon, 18 Mar 1996, Keith Bostic wrote:
>
>> Alpha version 1.57 of nex/nvi is now available for anonymous ftp from
>> ftp.cs.berkeley.edu:ucb/4bsd/nvi.ALPHA.1.57.tar.gz, or alternatively,
>> from bostic.com:pub/nvi.ALPHA.1.57.tar.gz.
>
>Should be added to the ports collection first ... if there isn't 
>any other taker, I'll prepare the port and send it to Satoshi.
>
>Or should it go directly into the main -current source tree after 
>a short period of testing ?

I think it's still a little bit under baked.  I fetched 1.57 yesterday
and under Solaris 2.3 'cw' doesn't work (it executes the replacement text
as commands!), and under BSD/386 1.1, cursor positioning is sometimes
random.

These couple instant oddities made me shelve 1.57 and return to 1.56 (which
has a sluggish flavour, but otherwise works).  If I manage to track down
the underlying bugs (there were a lot of compiler warnings about char vs
unsigned char, for example), I'll let Keith know.

Stephen.

From owner-freebsd-current  Tue Mar 19 18:30:28 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id SAA22137
          for current-outgoing; Tue, 19 Mar 1996 18:30:28 -0800 (PST)
Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19])
          by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id SAA22132
          for <freebsd-current@FreeBSD.org>; Tue, 19 Mar 1996 18:30:19 -0800 (PST)
Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.12/8.6.9) id NAA13275; Wed, 20 Mar 1996 13:28:43 +1100
Date: Wed, 20 Mar 1996 13:28:43 +1100
From: Bruce Evans <bde@zeta.org.au>
Message-Id: <199603200228.NAA13275@godzilla.zeta.org.au>
To: bde@zeta.org.au, rgrimes@GndRsh.aac.dev.com
Subject: Re: 2.2-960226-SNAP now on ftp.freebsd.org
Cc: freebsd-current@FreeBSD.org, joerg_wunsch@uriah.heep.sax.de
Sender: owner-current@FreeBSD.org
X-Loop: FreeBSD.org
Precedence: bulk

>> >/.profile is a hardlink to /root/.profile.

>It is very handy when booted single user as the root shell in that
>case has a home directory of / instead of /root.  I am pretty sure
>that was the reason that CSRG added this link when they moved root's
>home directory from / to /root.

Why didn't they set HOME=/root?

>> The system-wide profile /etc/profile isn't installed.  It should be
>> installed and contain only comments in it, like /etc/csh.login.

>WHAT???:
>SkyRsh# ls -lag /etc/prof*
>-rw-r--r--  1 root  wheel  570 Mar 16 16:03 /etc/profile

Oops.  I must have been looking at the Lite2 part of the diff.

>> Perhaps something like /etc/csh.cshrc should be implemented using
>> $ENV.

>Oh, you mean it is not used by /bin/sh???

/bin/sh certainly doesn't source csh files.

Bruce

From owner-freebsd-current  Tue Mar 19 18:52:21 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id SAA23233
          for current-outgoing; Tue, 19 Mar 1996 18:52:21 -0800 (PST)
Received: from GndRsh.aac.dev.com (GndRsh.aac.dev.com [198.145.92.241])
          by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id SAA23111
          for <freebsd-current@FreeBSD.org>; Tue, 19 Mar 1996 18:51:48 -0800 (PST)
Received: (from rgrimes@localhost) by GndRsh.aac.dev.com (8.6.12/8.6.12) id SAA21958; Tue, 19 Mar 1996 18:47:41 -0800
From: "Rodney W. Grimes" <rgrimes@GndRsh.aac.dev.com>
Message-Id: <199603200247.SAA21958@GndRsh.aac.dev.com>
Subject: Re: 2.2-960226-SNAP now on ftp.freebsd.org
To: bde@zeta.org.au (Bruce Evans)
Date: Tue, 19 Mar 1996 18:47:41 -0800 (PST)
Cc: bde@zeta.org.au, freebsd-current@FreeBSD.org,
        joerg_wunsch@uriah.heep.sax.de
In-Reply-To: <199603200228.NAA13275@godzilla.zeta.org.au> from "Bruce Evans" at Mar 20, 96 01:28:43 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

> 
> >> >/.profile is a hardlink to /root/.profile.
> 
> >It is very handy when booted single user as the root shell in that
> >case has a home directory of / instead of /root.  I am pretty sure
> >that was the reason that CSRG added this link when they moved root's
> >home directory from / to /root.
> 
> Why didn't they set HOME=/root?

You mean to have the kernel set this before it execs /bin/sh, I suppose
you could do that.

> >> The system-wide profile /etc/profile isn't installed.  It should be
> >> installed and contain only comments in it, like /etc/csh.login.
> 
> >WHAT???:
> >SkyRsh# ls -lag /etc/prof*
> >-rw-r--r--  1 root  wheel  570 Mar 16 16:03 /etc/profile
> 
> Oops.  I must have been looking at the Lite2 part of the diff.
> 
> >> Perhaps something like /etc/csh.cshrc should be implemented using
> >> $ENV.
> 
> >Oh, you mean it is not used by /bin/sh???
> 
> /bin/sh certainly doesn't source csh files.

I meant that /bin/sh does not read /etc/profile, is that what you are
talking about.


-- 
Rod Grimes                                      rgrimes@gndrsh.aac.dev.com
Accurate Automation Company                 Reliable computers for FreeBSD

From owner-freebsd-current  Tue Mar 19 19:03:48 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id TAA23992
          for current-outgoing; Tue, 19 Mar 1996 19:03:48 -0800 (PST)
Received: from austin.polstra.com (austin.polstra.com [206.213.73.10])
          by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id TAA23977
          for <freebsd-current@freebsd.org>; Tue, 19 Mar 1996 19:03:41 -0800 (PST)
Received: from austin.polstra.com (jdp@localhost) by austin.polstra.com (8.6.12/8.6.12) with ESMTP id SAA12961; Tue, 19 Mar 1996 18:58:37 -0800
Message-Id: <199603200258.SAA12961@austin.polstra.com>
To: "Marty Leisner" <leisner@sdsp.mc.xerox.com>
cc: Michael Smith <msmith@atrad.adelaide.edu.au>,
        coredump@nervosa.com (invalid opcode), freebsd-current@freebsd.org
Subject: Re: Elfkit release 1.1 is now available 
In-reply-to: Your message of "Tue, 19 Mar 1996 14:19:20 PST."
             <9603192219.AA08984@gnu.mc.xerox.com> 
Date: Tue, 19 Mar 1996 18:58:37 -0800
From: John Polstra <jdp@polstra.com>
Sender: owner-current@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

> When will the changes be rolled into binutils?

Real Soon Now.  I'm just revising my patches slightly, to make them more
palatable to the GNU folks.  Then I'll send them in (gcc, too).  Maybe
even tomorrow.

-- John

From owner-freebsd-current  Tue Mar 19 19:45:15 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id TAA26965
          for current-outgoing; Tue, 19 Mar 1996 19:45:15 -0800 (PST)
Received: from precipice.shockwave.com (precipice.shockwave.com [171.69.108.33])
          by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id TAA26958
          for <current@FreeBSD.ORG>; Tue, 19 Mar 1996 19:45:11 -0800 (PST)
Received: from localhost.shockwave.com (localhost.shockwave.com [127.0.0.1]) by precipice.shockwave.com (8.7.4/8.7.3) with SMTP id TAA09098; Tue, 19 Mar 1996 19:45:01 -0800 (PST)
Message-Id: <199603200345.TAA09098@precipice.shockwave.com>
To: =?KOI8-R?Q?=E1=CE=C4=D2=C5=CA_=FE=C5=D2=CE=CF=D7?= (aka Andrey A.
    Chernov, Black Mage) <ache@astral.msk.su>
cc: current@FreeBSD.ORG
Subject: Re: qcam module compile error 
In-reply-to: Your message of "Tue, 19 Mar 1996 20:26:25 +0300."
             <KH1vkJnyjI@astral.msk.su> 
Date: Tue, 19 Mar 1996 19:45:00 -0800
From: Paul Traina <pst@shockwave.com>
Sender: owner-current@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

Yep.. not done, that's why I didn't link it in to the top level makefile.
I've actually got all the code written but the (*^(* panics.  I don't see
why the damned joystick works and this doesn't. :-(

  From: =?KOI8-R?Q?=E1=CE=C4=D2=C5=CA_=FE=C5=D2=CE=CF=D7?=
	(aka Andrey A. Chernov, Black Mage) <ache@astral.msk.su>
  Subject: qcam module compile error
  ld -r  -o tmp.o qcam.o
  symorder -c symb.tmp tmp.o
  symorder: 1 symbol not found:
  _qcam_mod
  *** Error code 1
  
  Stop.
  -- 
  Andrey A. Chernov        : And I rest so composedly,  /Now, in my bed,
  ache@astral.msk.su       : That any beholder  /Might fancy me dead -
  http://dt.demos.su/~ache : Might start at beholding me,  /Thinking me dead.
  RELCOM Team,FreeBSD Team :         E.A.Poe         From "For Annie" 1849

From owner-freebsd-current  Tue Mar 19 19:47:41 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id TAA27042
          for current-outgoing; Tue, 19 Mar 1996 19:47:41 -0800 (PST)
Received: from precipice.shockwave.com (precipice.shockwave.com [171.69.108.33])
          by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id TAA27036
          for <current@freefall.freebsd.org>; Tue, 19 Mar 1996 19:47:37 -0800 (PST)
Received: from localhost.shockwave.com (localhost.shockwave.com [127.0.0.1]) by precipice.shockwave.com (8.7.4/8.7.3) with SMTP id TAA09181; Tue, 19 Mar 1996 19:47:24 -0800 (PST)
Message-Id: <199603200347.TAA09181@precipice.shockwave.com>
To: Tony Kimball <alk@Think.COM>
cc: current@freefall.freebsd.org
Subject: Re: perl4 
In-reply-to: Your message of "Tue, 19 Mar 1996 16:39:06 CST."
             <199603192239.QAA18506@compound> 
Date: Tue, 19 Mar 1996 19:47:24 -0800
From: Paul Traina <pst@shockwave.com>
Sender: owner-current@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk


  From: Tony Kimball <alk@Think.COM>
  Subject: perl4
  
  
     I don't think this is a good argument:
     - - you already have perl in /usr/bin  AND  in /usr/local/bin!
  
  So remove them both from the base distribution.  p4 can be made a
  package at zero-maintenance cost.  How much breaks, and how hard is
  it to fix?
  
  ./bin/makewhatis: a /usr/bin/perl script text
  ./bin/catman: a /usr/bin/perl script text
  ./bin/killall: a /usr/bin/perl script text
  ./bin/sgmlfmt: a /usr/bin/perl script text
  ./bin/which: a /usr/bin/perl script text
  ./sbin/adduser: a /usr/bin/perl script text
  ./sbin/kbdmap: a /usr/bin/perl script text
  ./sbin/vidfont: a /usr/bin/perl script text
  ./sbin/spkrtest: a /usr/bin/perl script text
  
  Not much.  Eliminate it, and that reduces the installed base OS size
  by 4MB, meaning more installations, more market share, better
  differentiation from bloated commercial systems.
  
  If I write C versions of these scripts, will that suffice
  to break perl off into a package?

Hear hear!  This is a good thing(TM)!  By the way, which is inherantly
broken when executed as any sort of script.  It needs to be a shell builtin
or it needs to die.

Paul

From owner-freebsd-current  Tue Mar 19 20:28:16 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id UAA00192
          for current-outgoing; Tue, 19 Mar 1996 20:28:16 -0800 (PST)
Received: from ki.net (ki.net [142.77.249.8])
          by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id UAA29941
          for <current@freebsd.org>; Tue, 19 Mar 1996 20:27:46 -0800 (PST)
Received: (from scrappy@localhost) by ki.net (8.7.4/8.7.4) id XAA08821; Tue, 19 Mar 1996 23:25:49 -0500 (EST)
Date: Tue, 19 Mar 1996 23:25:43 -0500 (EST)
From: "Marc G. Fournier" <scrappy@ki.net>
To: current@freebsd.org
Subject: PATCH: create ttyv* devices for devfs in pcvt
Message-ID: <Pine.BSF.3.91.960319231835.255A-100000@ki.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-current@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk


Hi...

	Came back to the office tonight figuring to clean up my
mods to pcvt_drv.c, and then check out syscons.c, and figured out that
syscons.c already has devfs support in it *sigh*  And all that work I
went to trying to figure out how to do it, and I could have just copied
the syscons stuff :(

	Ah well, a learning experience :)

	Well, here is a context diff of the changes I made to pcvt_drv.c
in order that the ttyv* devices get created properly in devfs, so that
you can use devfs on a system with pcvt.  If someone can check it over,
and commit it to the tree?  Or tell me I really don't know what I'm doing?


*** pcvt_drv.c.orig	Tue Mar 19 16:52:00 1996
--- pcvt_drv.c	Tue Mar 19 23:07:24 1996
***************
*** 82,87 ****
--- 82,94 ----
  #define EXTERN			/* allocate mem */
  
  #include "pcvt_hdr.h"		/* global include */
+ #ifdef DEVFS
+   #include <sys/devfsext.h>
+   #if !defined(MAXCONS)
+     #define MAXCONS 16
+   #endif
+   static void *pcvt_devfs_token[MAXCONS];
+ #endif /*DEVFS*/
  
  extern int getchar __P((void));
  
***************
*** 101,108 ****
  
  #if PCVT_FREEBSD > 205
  static struct kern_devconf kdc_vt[];
! static inline void
! vt_registerdev(struct isa_device *id, const char *name);
  static char vt_description[];
  #define VT_DESCR_LEN 40
  #endif /* PCVT_FREEBSD > 205 */
--- 108,114 ----
  
  #if PCVT_FREEBSD > 205
  static struct kern_devconf kdc_vt[];
! static inline void vt_registerdev(struct isa_device *id, const char *name);
  static char vt_description[];
  #define VT_DESCR_LEN 40
  #endif /* PCVT_FREEBSD > 205 */
***************
*** 162,167 ****
--- 168,177 ----
  {
  #endif /* PCVT_NETBSD > 9 */
  
+ #ifdef DEVFS
+       char dev_name[10];
+ 	int vt;
+ #endif /*DEVFS*/
  	int i;
  
  	vt_coldmalloc();		/* allocate memory for screens */
***************
*** 332,337 ****
--- 342,355 ----
  
  	cdevsw_add(&dev, &pcdevsw, NULL);
  	}
+ 
+ #ifdef DEVFS	
+ 	for(vt = 0; vt < MAXCONS; vt++) {
+           pcvt_devfs_token[vt] = 
+ 		devfs_add_devswf(&pcdevsw, vt,
+                                  DV_CHR, 0, 0, 0600, "ttyv%n", vt );
+ 	}
+ #endif DEVFS
  #endif /* PCVT_FREEBSD > 205 */
  
  #if PCVT_NETBSD > 9


Marc G. Fournier | POP Mail  Telnet Acct  DNS Hosting
System           |  WWW Services   Database Services  | Knowledge, 
  Administrator  |                                    | Information and
 scrappy@ki.net  |      WWW: http://www.ki.net        | Communications, Inc


From owner-freebsd-current  Tue Mar 19 20:29:31 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id UAA00256
          for current-outgoing; Tue, 19 Mar 1996 20:29:31 -0800 (PST)
Received: from ki.net (root@ki.net [142.77.249.8])
          by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id UAA00234
          for <current@freebsd.org>; Tue, 19 Mar 1996 20:29:08 -0800 (PST)
Received: (from scrappy@localhost) by ki.net (8.7.4/8.7.4) id XAA09298; Tue, 19 Mar 1996 23:28:42 -0500 (EST)
Date: Tue, 19 Mar 1996 23:28:40 -0500 (EST)
From: "Marc G. Fournier" <scrappy@ki.net>
To: current@freebsd.org
Subject: DEVFS vs "regular /dev"
Message-ID: <Pine.BSF.3.91.960319232652.255B-100000@ki.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-current@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk


Hi...

	Just curious, but what is the advantage (and disadvantage, if any?)
of using devfs vs "regular /dev"?  My first thought would be that its
memory based instead of file system based, giving better performance, but
that's just a guess.

	Comments?


Marc G. Fournier | POP Mail  Telnet Acct  DNS Hosting
System           |  WWW Services   Database Services  | Knowledge, 
  Administrator  |                                    | Information and
 scrappy@ki.net  |      WWW: http://www.ki.net        | Communications, Inc


From owner-freebsd-current  Tue Mar 19 22:06:11 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id WAA05936
          for current-outgoing; Tue, 19 Mar 1996 22:06:11 -0800 (PST)
Received: from ki.net (root@ki.net [142.77.249.8])
          by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id WAA05882
          for <current@freebsd.org>; Tue, 19 Mar 1996 22:05:23 -0800 (PST)
Received: (from scrappy@localhost) by ki.net (8.7.4/8.7.4) id BAA16915; Wed, 20 Mar 1996 01:04:56 -0500 (EST)
Date: Wed, 20 Mar 1996 01:04:55 -0500 (EST)
From: "Marc G. Fournier" <scrappy@ki.net>
To: current@freebsd.org
Subject: PATCH/DEVFS: /dev/dump & /dev/klog
Message-ID: <Pine.BSF.3.91.960320005955.255D-100000@ki.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-current@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk


Hi...

	Still a couple of modifications to make this run completely on devfs, 
but here is a patch that gets ps to work properly (needs /dev/drum) and a fix 
for subr_log.c.

	subr_log.c was creating a character device for /dev/log, when it
should have been creating /dev/klog.  /dev/log, according to /dev/log
as installed, and according to the syslogd man page, is a socket, not a
device.

	The modifications aren't major or anything,  but if I'm doing
something wrong, or omitting something, please let me know.  I think I'm
doing this right...


---[ /usr/src/sys/vm/vm_swap.c ]-----

*** /home/staff/scrappy/vm_swap.c	Wed Mar 20 00:58:45 1996
--- vm_swap.c	Wed Mar 20 00:50:39 1996
***************
*** 52,57 ****
--- 52,61 ----
  #include <vm/swap_pager.h>
  
  #include <miscfs/specfs/specdev.h>
+ #ifdef DEVFS
+   #include <sys/devfsext.h>
+   static void *drum_devfs_token;
+ #endif /*DEVFS*/
  
  static void swstrategy __P((struct buf *));
  
***************
*** 297,302 ****
--- 301,311 ----
  		dev = makedev(BDEV_MAJOR,0);
  		bdevsw_add(&dev,&sw_bdevsw,NULL);
  		sw_devsw_installed = 1;
+ #ifdef DEVFS
+           drum_devfs_token =
+                 devfs_add_devsw("/", "drum", &sw_cdevsw, 0,
+                                  DV_CHR, 0, 0, 0640 );
+ #endif /*DEVFS*/ 
      	}
  }
  
----[ /usr/src/sys/kern/subr_log.c ]-----


*** subr_log.c.orig	Tue Mar 19 23:38:48 1996
--- subr_log.c	Tue Mar 19 23:39:14 1996
***************
*** 255,261 ****
  		log_devsw_installed = 1;
  #ifdef DEVFS
  		log_devfs_token = devfs_add_devsw(
! 			"/", "log", &log_cdevsw, 0, DV_CHR, 0, 0, 0600);
  #endif
      	}
  }
--- 255,261 ----
  		log_devsw_installed = 1;
  #ifdef DEVFS
  		log_devfs_token = devfs_add_devsw(
! 			"/", "klog", &log_cdevsw, 0, DV_CHR, 0, 0, 0600);
  #endif
      	}
  }


Marc G. Fournier | POP Mail  Telnet Acct  DNS Hosting
System           |  WWW Services   Database Services  | Knowledge, 
  Administrator  |                                    | Information and
 scrappy@ki.net  |      WWW: http://www.ki.net        | Communications, Inc


From owner-freebsd-current  Tue Mar 19 22:38:50 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id WAA07245
          for current-outgoing; Tue, 19 Mar 1996 22:38:50 -0800 (PST)
Received: from grumble.grondar.za (root@grumble.grondar.za [196.7.18.130])
          by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id WAA07240
          for <current@freebsd.org>; Tue, 19 Mar 1996 22:38:32 -0800 (PST)
Received: from grumble.grondar.za (mark@localhost [127.0.0.1]) by grumble.grondar.za (8.7.5/8.7.3) with ESMTP id IAA10967 for <current@freebsd.org>; Wed, 20 Mar 1996 08:38:00 +0200 (SAT)
Message-Id: <199603200638.IAA10967@grumble.grondar.za>
To: current@freebsd.org
Subject: Firewalls and all...
Date: Wed, 20 Mar 1996 08:37:59 +0200
From: Mark Murray <mark@grondar.za>
Sender: owner-current@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

Hi

I am having some problems with a firewall I built the other night. I got
it right at that time, but right now I can't figure something out (I am
running -CURRENT)

My firewall has an ethernet card (ed0), iijppp (tun0) and a simple set of
filters mainly designed to stop spoofing and other silly things. Iijpp
has to play games with the modem to start the connection. Althouh I have
a leased line, I have cheap modems that need to be tickled to establish
the connection)

I have to boot the thing with a lot of manual intervention. If the
firewall startup calls are kluged into /etc/netstart, then at boot
time mountd and sendmail freeze up, and a ^c is needed to unwedge them.
Also logging in is broken; I get a login: prompt but no passwd prompt.
This has something to do with the fact that ypserv/ypbind do not get
loaded :-), but I do not understad why root cannot get in.

My current boot procedure is to boot the machine with no firewall
rules, and load those after it has started. Then I load by hand
all the daemons that have failed: mountd, ypserv, ypbind, rpc.yppasswdd
and one or two others.

Life is slightly complicated by the fact that this machine also runs
my nameserver.

Question: does anybody run a similar setup? And if so, how do you clean
boot it? I would be interested in the sort of setup that could be put
into /etc/sysconfig and /etc/netstart for all to use.

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  Tue Mar 19 22:44:19 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id WAA07614
          for current-outgoing; Tue, 19 Mar 1996 22:44:19 -0800 (PST)
Received: from alpha.xerox.com (alpha.Xerox.COM [13.1.64.93])
          by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id WAA07609
          for <freebsd-current@freebsd.org>; Tue, 19 Mar 1996 22:44:17 -0800 (PST)
Received: from crevenia.parc.xerox.com ([13.2.116.11]) by alpha.xerox.com with SMTP id <15587(15)>; Tue, 19 Mar 1996 22:43:41 PST
Received: from localhost by crevenia.parc.xerox.com with SMTP id <177478>; Tue, 19 Mar 1996 22:43:33 -0800
To: freebsd-current@freebsd.org
Subject: Re: Nvi alpha version 1.57 now available. 
In-reply-to: Your message of "Tue, 19 Mar 96 18:17:53 PST."
             <199603200217.MAA11101@orion.devetir.qld.gov.au> 
Date: Tue, 19 Mar 1996 22:43:25 PST
From: Bill Fenner <fenner@parc.xerox.com>
Message-Id: <96Mar19.224333pst.177478@crevenia.parc.xerox.com>
Sender: owner-current@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

I'll second the "leave 1.57 alone for now", since at least under
SunOS, using "script" causes core dumps.

  Bill

From owner-freebsd-current  Tue Mar 19 23:02:00 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id XAA08479
          for current-outgoing; Tue, 19 Mar 1996 23:02:00 -0800 (PST)
Received: from silvia.HIP.Berkeley.EDU (silvia.HIP.Berkeley.EDU [136.152.64.181])
          by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id XAA08470
          Tue, 19 Mar 1996 23:01:56 -0800 (PST)
Received: (from asami@localhost) by silvia.HIP.Berkeley.EDU (8.7.5/8.6.9) id XAA02504; Tue, 19 Mar 1996 23:01:49 -0800 (PST)
Date: Tue, 19 Mar 1996 23:01:49 -0800 (PST)
Message-Id: <199603200701.XAA02504@silvia.HIP.Berkeley.EDU>
To: jehamby@lightside.com
CC: sos@FreeBSD.ORG, current@FreeBSD.ORG
In-reply-to: <Pine.AUX.3.91.960311064509.9350A-100000@covina.lightside.com> (message from Jake Hamby on Mon, 11 Mar 1996 06:51:26 -0800 (PST))
Subject: Re: Native & Linux ELF support finally there...
From: asami@cs.berkeley.edu (Satoshi Asami)
Sender: owner-current@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

 * GNAT (GNU/NYU Ada Translator, this will be tricky since my plan is to run 
 *   the Linux version of the Ada part with a FreeBSD-native GCC 2.7.2), in 
 *   the hopes of building a package/port of the latest GNAT (GNAT is written 
 *   in itself, so you need a binary before you can build it) :-(  :-(

There exists a gnat port/package for FreeBSD.  There is no package for 
2.2-current (I just haven't gotten around to build it yet) but there
is one under packages-2.1 on the ftp site.

Satoshi

From owner-freebsd-current  Tue Mar 19 23:07:05 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id XAA08761
          for current-outgoing; Tue, 19 Mar 1996 23:07:05 -0800 (PST)
Received: from localhost.cdrom.com (localhost.cdrom.com [127.0.0.1])
          by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id XAA08756
          Tue, 19 Mar 1996 23:07:02 -0800 (PST)
Message-Id: <199603200707.XAA08756@freefall.freebsd.org>
X-Authentication-Warning: freefall.freebsd.org: Host localhost.cdrom.com [127.0.0.1] didn't use HELO protocol
To: "Rodney W. Grimes" <rgrimes@GndRsh.aac.dev.com>
cc: mrl@teleport.com, current@Freebsd.Org
Subject: Re: aic7xxx driver problem with wide and narrow busses attached. 
In-reply-to: Your message of "Tue, 19 Mar 1996 11:19:35 PST."
             <199603191919.LAA21274@GndRsh.aac.dev.com> 
Date: Tue, 19 Mar 1996 23:07:01 -0800
From: "Justin T. Gibbs" <gibbs@freefall.freebsd.org>
Sender: owner-current@Freebsd.Org
X-Loop: FreeBSD.org
Precedence: bulk

>> 
>> 
>> Disable parity detection in SCSI-Select.  I'm still trying to 
>> track down why this happens on machines that have both a 
>> Wide and narrow bus attached.  (Hey Rod... care to lend me
>> a wide disk again? 8-)
>> 
>I'll have to do some house cleaning... my spare wide drive is a bit
>full of data right now:
>/dev/sd1a     2088244  1936934   -15750   101%    /B
>
>> I'll turn parity error checking off again in the driver for now.
>
>I'll slap a narrow disk on my 2940W and see if I can duplicate it
>here, if it does duplicate I'll see about getting this data rolled
>out to other disks and get it down to you for a debug session...

It may only occur on the 7880 based controllers.  Do you have any
older 2940Ws around?

>Should I be able to duplicate this in -stable, or does this problem
>only seem to be occuring with -current?

I only enabled parity checking for the aic78X0 family recently in
-current.  I didn't even think much about it since it was an
oversight that it wasn't enabled before and it has been enabled
for some time on the aic7770 chips.  The setting tracks what is
set in SCSI-Select so its easy to change.  I should have the -current
driver pulled back into -stable soon (minus the parity stuff).  I'll
send you a private patch to enable the parity once I do this.

>-- 
>Rod Grimes                                      rgrimes@gndrsh.aac.dev.com
>Accurate Automation Company                 Reliable computers for FreeBSD

--
Justin T. Gibbs
===========================================
  FreeBSD: Turning PCs into workstations
===========================================

From owner-freebsd-current  Tue Mar 19 23:25:00 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id XAA09996
          for current-outgoing; Tue, 19 Mar 1996 23:25:00 -0800 (PST)
Received: from news1.gtn.com (news1.gtn.com [192.109.159.3])
          by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id XAA09989
          for <freebsd-current@freebsd.org>; Tue, 19 Mar 1996 23:24:53 -0800 (PST)
Received: (from uucp@localhost) by news1.gtn.com (8.7.2/8.7.2) id IAA26966; Wed, 20 Mar 1996 08:00:30 +0100 (MET)
Received: from knobel.gun.de (localhost [127.0.0.1]) by knobel.gun.de (8.7.5/8.7.3) with SMTP id HAA02716; Wed, 20 Mar 1996 07:50:08 +0100 (MET)
Date: Wed, 20 Mar 1996 07:50:07 +0100 (MET)
From: Andreas Klemm <andreas@knobel.gun.de>
To: Stephen McKay <syssgm@devetir.qld.gov.au>
cc: freebsd-current@freebsd.org, syssgm@devetir.qld.gov.au
Subject: Re: Nvi alpha version 1.57 now available.
In-Reply-To: <199603200217.MAA11101@orion.devetir.qld.gov.au>
Message-ID: <Pine.BSF.3.91.960320074744.2502A-100000@knobel.gun.de>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-current@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

On Wed, 20 Mar 1996, Stephen McKay wrote:

> I think it's still a little bit under baked.  I fetched 1.57 yesterday
> and under Solaris 2.3 'cw' doesn't work (it executes the replacement text
> as commands!), and under BSD/386 1.1, cursor positioning is sometimes
> random.
> 
> These couple instant oddities made me shelve 1.57 and return to 1.56 (which
> has a sluggish flavour, but otherwise works).  If I manage to track down
> the underlying bugs (there were a lot of compiler warnings about char vs
> unsigned char, for example), I'll let Keith know.

Ok, seems to be a bit too early.  Let's wait for the final version 1.57.

	Andreas ///

--
andreas@knobel.gun.de         /\/\___      Wiechers & Partner Datentechnik GmbH
   Andreas Klemm          ___/\/\/         $$  Support Unix - aklemm@wup.de  $$
pgp p-key  http://www-swiss.ai.mit.edu/~bal/pks-toplev.html  >>> powered by <<<
ftp://sunsite.unc.edu/pub/Linux/system/Printing/aps-491.tgz  >>>    FreeBSD <<<
"Ich bleibe bei der Aussage und trotze den Flames. :-)"    Ulli Horlacher 02/96


From owner-freebsd-current  Tue Mar 19 23:31:35 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id XAA10553
          for current-outgoing; Tue, 19 Mar 1996 23:31:35 -0800 (PST)
Received: from GndRsh.aac.dev.com (GndRsh.aac.dev.com [198.145.92.241])
          by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id XAA10538
          Tue, 19 Mar 1996 23:31:28 -0800 (PST)
Received: (from rgrimes@localhost) by GndRsh.aac.dev.com (8.6.12/8.6.12) id XAA22233; Tue, 19 Mar 1996 23:31:18 -0800
From: "Rodney W. Grimes" <rgrimes@GndRsh.aac.dev.com>
Message-Id: <199603200731.XAA22233@GndRsh.aac.dev.com>
Subject: Re: aic7xxx driver problem with wide and narrow busses attached.
To: gibbs@freefall.freebsd.org (Justin T. Gibbs)
Date: Tue, 19 Mar 1996 23:31:17 -0800 (PST)
Cc: mrl@teleport.com, current@Freebsd.Org
In-Reply-To: <199603200707.XAA08756@freefall.freebsd.org> from "Justin T. Gibbs" at Mar 19, 96 11:07:01 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

> 
> >> 
> >> 
> >> Disable parity detection in SCSI-Select.  I'm still trying to 
> >> track down why this happens on machines that have both a 
> >> Wide and narrow bus attached.  (Hey Rod... care to lend me
> >> a wide disk again? 8-)
> >> 
> >I'll have to do some house cleaning... my spare wide drive is a bit
> >full of data right now:
> >/dev/sd1a     2088244  1936934   -15750   101%    /B
> >
> >> I'll turn parity error checking off again in the driver for now.
> >
> >I'll slap a narrow disk on my 2940W and see if I can duplicate it
> >here, if it does duplicate I'll see about getting this data rolled
> >out to other disks and get it down to you for a debug session...
> 
> It may only occur on the 7880 based controllers.  Do you have any
> older 2940Ws around?

The only 2940W I have is:
ahc0 <Adaptec 2940 SCSI host adapter> rev 3 int a irq 11 on pci0:12
ahc0: aic7870 Wide Channel, SCSI Id=7, 16 SCBs

I don't currently have any 2940UW's.

> >Should I be able to duplicate this in -stable, or does this problem
> >only seem to be occuring with -current?
> 
> I only enabled parity checking for the aic78X0 family recently in
> -current.  I didn't even think much about it since it was an
> oversight that it wasn't enabled before and it has been enabled
> for some time on the aic7770 chips.  The setting tracks what is
> set in SCSI-Select so its easy to change.  I should have the -current
> driver pulled back into -stable soon (minus the parity stuff).  I'll
> send you a private patch to enable the parity once I do this.

Okay, but make sure that commit message to -stable clearly states that if
you suddenly see SCSI problems on aic7xxx based systems to turn off parity
in the SCSI-Select menu and report the problem.


-- 
Rod Grimes                                      rgrimes@gndrsh.aac.dev.com
Accurate Automation Company                 Reliable computers for FreeBSD

From owner-freebsd-current  Tue Mar 19 23:33:36 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id XAA10898
          for current-outgoing; Tue, 19 Mar 1996 23:33:36 -0800 (PST)
Received: from skynet.ctr.columbia.edu (skynet.ctr.columbia.edu [128.59.64.70])
          by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id XAA10873
          for <current@freebsd.org>; Tue, 19 Mar 1996 23:33:31 -0800 (PST)
Received: (from wpaul@localhost) by skynet.ctr.columbia.edu (8.6.12/8.6.9) id CAA10198; Wed, 20 Mar 1996 02:31:54 -0500
From: Bill Paul <wpaul@skynet.ctr.columbia.edu>
Message-Id: <199603200731.CAA10198@skynet.ctr.columbia.edu>
Subject: Re: NIS problem
To: scrappy@ki.net (Marc G. Fournier)
Date: Wed, 20 Mar 1996 02:31:52 -0500 (EST)
Cc: current@freebsd.org
In-Reply-To: <Pine.BSF.3.91.960319152223.249A-100000@ki.net> from "Marc G. Fournier" at Mar 19, 96 03:28:08 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:

> Hi...
> 
> 	I'm not sure if its something I'm forgetting to run, or if
> its a bug somewhere, but I can't seem to get login's working on my
> -current machine with NIS running.

Well, since you didn't actually describe what you did to set up
NIS on your client, it's hard for me to tell where the problem may lie.
 
> 	I've set the appropriate settings in sysconfig, and am running
> ypbind -s on that machine, but try as I might, I can't login to that
> machine unless the user entry is in the password file on that machine.

There's stuff missing here. Editing sysconfig is not all there is
to it (though I'm sure people would like it to be that way :). You
need to add +::::::::: to the end of /etc/master.passwd and rebuild
the password databases (with vipw, preferable). You also want to
add +::: to the end of /etc/group.

Read the passwd(5) man page when modifying /etc/master.passwd. Don't
get clever with the magic '+' entries unless you know what you're
doing. Don't use +:*::::::::. Don't use +::0:0::::::. Don't use
any combination thereof. This is not SunOS. Don't expect everything
to work the same.
 
> 	If I run chsh userid, it will grab the NIS data though.

This could mean that you used one of the bad + entries I mentioned.
 
> 	Someone asked if maybe I had md5 instead of des encryption
> installed, so that the encryption mechanisms are different, but an 
> md5 encrypted password is a substantially "longer" string then a des
> encrypted one, so as far as I can see, both are using des.

I take this to mean that the encrypted passwords in your local
/etc/master.passwd file appear to be in DES format (the MD5 hash
passwords all start with a $1$, and yes they are long. DES passwords
are always 13 characters (11 ciphertext plus 2 salt)). If so, then
this is correct, assuing the passwords in the passwd maps are also
in DES format.
 
> 	The ypserver is a -stable box, if that means anything?

It shouldn't matter.

> I know
> there were some changes recently to -current's des, but I wouldn't have
> assumed that those would have affected it in such a way as to produce
> this sort of problem...would it?

Again, as long as you're running the same kind of encryption format
on both client and server, it shouldn't make any difference.

I need more details. Please show me exactly what + lines you've
added to /etc/master.passwd. Also, try using 'id nisuser' to see if
the system actually recognizes the user (without the added local
master.passwd entry, that is).

-Bill

-- 
=============================================================================
-Bill Paul            (212) 854-6020 | System Manager
Work:         wpaul@ctr.columbia.edu | Center for Telecommunications Research
Home:  wpaul@skynet.ctr.columbia.edu | Columbia University, New York City
=============================================================================
License error: The license for this .sig file has expired. You must obtain
a new license key before any more witty phrases will appear in this space.
=============================================================================

From owner-freebsd-current  Wed Mar 20 00:02:30 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id AAA12511
          for current-outgoing; Wed, 20 Mar 1996 00:02:30 -0800 (PST)
Received: from main.gbdata.com (tty10.com6.houston.net [198.66.103.203])
          by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id AAA12502
          for <current@freefall.freebsd.org>; Wed, 20 Mar 1996 00:02:26 -0800 (PST)
Received: (from gclarkii@localhost) by main.gbdata.com (8.6.12/8.6.9) id CAA10056; Wed, 20 Mar 1996 02:02:17 -0600
From: Gary Clark II <gclarkii@main.gbdata.com>
Message-Id: <199603200802.CAA10056@main.gbdata.com>
Subject: Re: perl4
To: alk@Think.COM (Tony Kimball)
Date: Wed, 20 Mar 1996 02:02:16 -0600 (CST)
Cc: current@freefall.freebsd.org
In-Reply-To: <199603192239.QAA18506@compound> from "Tony Kimball" at Mar 19, 96 04:39:06 pm
X-Mailer: ELM [version 2.4 PL24]
Content-Type: text
Sender: owner-current@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

Hello,

WARNING: slight flamage ahead....

Tony Kimball wrote:
> 
> 
> 
>    I don't think this is a good argument:
>    - - you already have perl in /usr/bin  AND  in /usr/local/bin!
> 
Perl 4 is ONLY in /usr/bin. You might have added perl5 to the system
or made a copy.


> So remove them both from the base distribution.  p4 can be made a
> package at zero-maintenance cost.  How much breaks, and how hard is
> it to fix?
Perl IS the sys admin language of choice.  Many systems now ship perl
with the distribution like we do.  Thats why I brought it in.

> 
> ./bin/makewhatis: a /usr/bin/perl script text
> ./bin/catman: a /usr/bin/perl script text
> ./bin/killall: a /usr/bin/perl script text
> ./bin/sgmlfmt: a /usr/bin/perl script text
> ./bin/which: a /usr/bin/perl script text
> ./sbin/adduser: a /usr/bin/perl script text
> ./sbin/kbdmap: a /usr/bin/perl script text
> ./sbin/vidfont: a /usr/bin/perl script text
> ./sbin/spkrtest: a /usr/bin/perl script text
> 
> Not much.  Eliminate it, and that reduces the installed base OS size
> by 4MB, meaning more installations, more market share, better
> differentiation from bloated commercial systems.
Huh?  If 4 megs made that BIG of a difference, we would have taken over
a LONG time ago.

> 
> If I write C versions of these scripts, will that suffice
> to break perl off into a package?
Not really, not unless you will also re-write ALL future scripts also.
I'm in the process of a total rewrite for adduser to expand it into
a sysadmin system (add user, delete user, groups, change user attributes, etc).
This will be a curses based system.

> 
> //alk
> 

Gary

P.S. Sorry for the slight flamage, but I still belive we need perl.

-- 
Gary Clark II   (N5VMF) |    I speak only for myself and "maybe" my company 
gclarkii@GBData.COM     |          Member of the FreeBSD Doc Team 
  Providing Internet and ISP startups mail info@GBData.COM for information
   FreeBSD FAQ at ftp://ftp.FreeBSD.ORG/pub/FreeBSD/docs/freebsd-faq.ascii 

From owner-freebsd-current  Wed Mar 20 00:08:22 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id AAA12957
          for current-outgoing; Wed, 20 Mar 1996 00:08:22 -0800 (PST)
Received: from tfs.com (tfs.com [140.145.250.1])
          by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id AAA12950
          for <current@freebsd.org>; Wed, 20 Mar 1996 00:08:19 -0800 (PST)
Received: from critter.tfs.com by tfs.com (smail3.1.28.1) with SMTP
	id m0tzIwL-0003voC; Wed, 20 Mar 96 00:08 PST
Received: from localhost.tfs.com (localhost.tfs.com [127.0.0.1]) by critter.tfs.com (8.6.12/8.6.12) with SMTP id IAA11535; Wed, 20 Mar 1996 08:08:12 GMT
X-Authentication-Warning: critter.tfs.com: Host localhost.tfs.com didn't use HELO protocol
To: Mark Murray <mark@grondar.za>
cc: current@freebsd.org
Subject: Re: Firewalls and all... 
In-reply-to: Your message of "Wed, 20 Mar 1996 08:37:59 +0200."
             <199603200638.IAA10967@grumble.grondar.za> 
Date: Wed, 20 Mar 1996 08:08:10 +0000
Message-ID: <11533.827309290@critter.tfs.com>
From: Poul-Henning Kamp <phk@critter.tfs.com>
Sender: owner-current@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

> Question: does anybody run a similar setup? And if so, how do you clean
> boot it? I would be interested in the sort of setup that could be put
> into /etc/sysconfig and /etc/netstart for all to use.

Add you rules at the top of /etc/netstart.

Changes to sysconfig is in the pipe-line.

--
Poul-Henning Kamp           | phk@FreeBSD.ORG       FreeBSD Core-team.
http://www.freebsd.org/~phk | phk@login.dknet.dk    Private mailbox.
whois: [PHK]                | phk@ref.tfs.com       TRW Financial Systems, Inc.
Future will arrive by its own means, progress not so.

From owner-freebsd-current  Wed Mar 20 00:32:27 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id AAA13949
          for current-outgoing; Wed, 20 Mar 1996 00:32:27 -0800 (PST)
Received: from relay1.oleane.net (Relay1.OLEANE.NET [194.2.1.1])
          by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id AAA13941
          for <current@freebsd.org>; Wed, 20 Mar 1996 00:32:13 -0800 (PST)
Received: from ocegr.fr (hydra.dtsmtp.ocegr.fr [194.2.64.3]) by relay1.oleane.net (8.6.10/8.6.9) with SMTP id JAA03546; Wed, 20 Mar 1996 09:31:09 +0100
Received: from apus by ocegr.fr (5.0/SMI-SVR4)
	id AA23967; Wed, 20 Mar 1996 09:34:33 +0100
Message-Id: <9603200834.AA23967@ocegr.fr>
To: current@freebsd.org
Cc: Stephen McKay <syssgm@devetir.qld.gov.au>
From: Gert-Jan.Vons@ocegr.fr
Reply-To: Gert-Jan.Vons@ocegr.fr
Subject: Re: Nvi alpha version 1.57 now available.
Date: Wed, 20 Mar 1996 09:34:31 +0100
Sender: owner-current@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk


Stephen McKay <syssgm@devetir.qld.gov.au> wrote:

 |>> Alpha version 1.57 of nex/nvi is now available for anonymous ftp from
 |>> ftp.cs.berkeley.edu:ucb/4bsd/nvi.ALPHA.1.57.tar.gz, or alternatively,
 |>> from bostic.com:pub/nvi.ALPHA.1.57.tar.gz.
 |
 |I think it's still a little bit under baked.  I fetched 1.57 yesterday
 |and under Solaris 2.3 'cw' doesn't work (it executes the replacement text
 |as commands!), and under BSD/386 1.1, cursor positioning is sometimes
 |random.

This version is running fine under fbsd2.1.0 release, no serious
problems yet. I had the same problem under SunOS/Solaris, but Keith
told me it was due to the Sun compiler. Recompiling v_txt.c without
any optimisation fixed the cw problem.

There is one jumping cursor problem when you hit ESC followed by a 'l'
or a 'b', it jumps to the status line.

But note this is ALPHA software, and not one of Keith's public
releases...

	Gert-Jan

---------------------------------------------------------------------------
J.G. Vons, Oce engineering Creteil, France | E-mail: Gert-Jan.Vons@ocegr.fr

From owner-freebsd-current  Wed Mar 20 01:21:38 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id BAA16247
          for current-outgoing; Wed, 20 Mar 1996 01:21:38 -0800 (PST)
Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11])
          by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id BAA16226
          for <freebsd-current@FreeBSD.org>; Wed, 20 Mar 1996 01:21:31 -0800 (PST)
Received: from sax.sax.de by irz301.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id KAA03039; Wed, 20 Mar 1996 10:20:45 +0100
Received: by sax.sax.de (8.6.11/8.6.12-s1) with UUCP
	id KAA08082; Wed, 20 Mar 1996 10:20:43 +0100
Received: (from j@localhost) by uriah.heep.sax.de (8.7.4/8.6.9) id KAA07520; Wed, 20 Mar 1996 10:03:38 +0100 (MET)
From: J Wunsch <j@uriah.heep.sax.de>
Message-Id: <199603200903.KAA07520@uriah.heep.sax.de>
Subject: Re: SCSI death in -current with DAT
To: freebsd-current@FreeBSD.org (FreeBSD-current users)
Date: Wed, 20 Mar 1996 10:03:37 +0100 (MET)
Cc: mrl@teleport.com
Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch)
In-Reply-To: <199603192305.PAA21675@GndRsh.aac.dev.com> from "Rodney W. Grimes" at Mar 19, 96 03:05:17 pm
X-Phone: +49-351-2012 669
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

As Rodney W. Grimes wrote:

> > J"org, thank you for the fixed-block setup for the DAT - I didn't
> > use it but I'll keep it just in case.
> 
> The Archive/Conner Python 28388 DAT drives are variable block length capable
> drives, this patch is not needed, and should not be applied to any system.

I would have been surprised if it were not capable of this.

-- 
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  Wed Mar 20 01:22:08 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id BAA16319
          for current-outgoing; Wed, 20 Mar 1996 01:22:08 -0800 (PST)
Received: (from dima@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id BAA16293
          Wed, 20 Mar 1996 01:22:04 -0800 (PST)
Message-Id: <199603200922.BAA16293@freefall.freebsd.org>
Subject: Re: new sup server
To: julian@ref.tfs.com (JULIAN Elischer)
Date: Wed, 20 Mar 1996 01:22:04 -0800 (PST)
Cc: mmead@Glock.COM, dima@freebsd.org, hackers@freebsd.org,
        current@freebsd.org
In-Reply-To: <199603191758.JAA02581@ref.tfs.com> from "JULIAN Elischer" at Mar 19, 96 09:58:57 am
From: dima@freebsd.org (Dima Ruban)
X-Class: Fast
Organization: HackerDome
X-Mailer: ELM [version 2.4 PL24]
Content-Type: text
Sender: owner-current@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

JULIAN Elischer writes:
> 
> In fact what is the lag behing all the servers..
> can we find out the update schedules for them?
> it helps US shedule OUR updates..

As I've said, sup5.freebsd.org (burka.rdy.com) updates
2 time a day. 12pm and 12am. Usually it takes around
40 minutes to update everything.

> julian
> > 
> > Dima Ruban writes:
> > 
> > > Hi there!
> > > 
> > > New sup server for current/stable/cvs is operational and ready.
> > > Please use it. (This server is on T3, so it should work
> > > pretty fast). Questions and/or comments to dima@best.net.
> > > Oops, almost forgot. This is sup5.freebsd.org
> > > 
> > > Enjoy.
> > 
> > 	How much lag behind freefall is it?
> > 
> > 
> > -matt
> > 
> > -- 
> > Matthew C. Mead
> > 
> > mmead@Glock.COM
> > http://www.Glock.COM/~mmead/
> > 
> 
> 

-- dima

From owner-freebsd-current  Wed Mar 20 01:22:43 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id BAA16411
          for current-outgoing; Wed, 20 Mar 1996 01:22:43 -0800 (PST)
Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11])
          by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id BAA16228
          for <freebsd-current@FreeBSD.org>; Wed, 20 Mar 1996 01:21:31 -0800 (PST)
Received: from sax.sax.de by irz301.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id KAA03043 for <freebsd-current@FreeBSD.org>; Wed, 20 Mar 1996 10:20:47 +0100
Received: by sax.sax.de (8.6.11/8.6.12-s1) with UUCP
	id KAA08083 for freebsd-current@FreeBSD.org; Wed, 20 Mar 1996 10:20:47 +0100
Received: (from j@localhost) by uriah.heep.sax.de (8.7.4/8.6.9) id KAA07672 for freebsd-current@FreeBSD.org; Wed, 20 Mar 1996 10:13:14 +0100 (MET)
From: J Wunsch <j@uriah.heep.sax.de>
Message-Id: <199603200913.KAA07672@uriah.heep.sax.de>
Subject: Re: perl4
To: freebsd-current@FreeBSD.org (FreeBSD-current users)
Date: Wed, 20 Mar 1996 10:13:13 +0100 (MET)
Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch)
In-Reply-To: <199603200347.TAA09181@precipice.shockwave.com> from "Paul Traina" at Mar 19, 96 07:47:24 pm
X-Phone: +49-351-2012 669
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

As Paul Traina wrote:

>   If I write C versions of these scripts, will that suffice
>   to break perl off into a package?
> 
> Hear hear!  This is a good thing(TM)!

It ain't, but we've been there before. :)

>  By the way, which is inherantly
> broken when executed as any sort of script.  It needs to be a shell builtin
> or it needs to die.

Huh?  #!/bin/sh, #!/bin/csh aren't shell builtins either.  In fact,
all these scripts are acceptable to execve(2), and the shell won't
even notice the difference to a binary executable.

-- 
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  Wed Mar 20 01:24:43 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id BAA16655
          for current-outgoing; Wed, 20 Mar 1996 01:24:43 -0800 (PST)
Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11])
          by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id BAA16448
          for <freebsd-current@FreeBSD.org>; Wed, 20 Mar 1996 01:22:59 -0800 (PST)
Received: from sax.sax.de by irz301.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id KAA03034; Wed, 20 Mar 1996 10:20:41 +0100
Received: by sax.sax.de (8.6.11/8.6.12-s1) with UUCP
	id KAA08079; Wed, 20 Mar 1996 10:20:41 +0100
Received: (from j@localhost) by uriah.heep.sax.de (8.7.4/8.6.9) id KAA07487; Wed, 20 Mar 1996 10:01:43 +0100 (MET)
From: J Wunsch <j@uriah.heep.sax.de>
Message-Id: <199603200901.KAA07487@uriah.heep.sax.de>
Subject: Re: perl4
To: freebsd-current@FreeBSD.org (FreeBSD-current users)
Date: Wed, 20 Mar 1996 10:01:42 +0100 (MET)
Cc: alk@Think.COM (Tony Kimball)
Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch)
In-Reply-To: <199603192239.QAA18506@compound> from "Tony Kimball" at Mar 19, 96 04:39:06 pm
X-Phone: +49-351-2012 669
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

As Tony Kimball wrote:

> ./bin/makewhatis: a /usr/bin/perl script text
> ./bin/catman: a /usr/bin/perl script text
> ./bin/killall: a /usr/bin/perl script text
> ./bin/sgmlfmt: a /usr/bin/perl script text
> ./bin/which: a /usr/bin/perl script text
> ./sbin/adduser: a /usr/bin/perl script text
> ./sbin/kbdmap: a /usr/bin/perl script text
> ./sbin/vidfont: a /usr/bin/perl script text
> ./sbin/spkrtest: a /usr/bin/perl script text
> 
> Not much.  Eliminate it, and that reduces the installed base OS size
> by 4MB, meaning more installations, more market share, better
> differentiation from bloated commercial systems.

Yuck.  Nobody is eager in replacing them.  Doing regexp and string
operations in C is the least one does volunteerily, given that nice
tools like Perl are available for it.  It's not only that these things
must be written (which you was kindly offering), they also must be
*maintained*.

I've recently written a 700-line Perl script that implements a mini
Webserver.  Nobody in the world would have made me writing this sort
of things in C...

-- 
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  Wed Mar 20 01:25:54 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id BAA16742
          for current-outgoing; Wed, 20 Mar 1996 01:25:54 -0800 (PST)
Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11])
          by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id BAA16252
          for <freebsd-current@FreeBSD.org>; Wed, 20 Mar 1996 01:21:39 -0800 (PST)
Received: from sax.sax.de by irz301.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id KAA03047 for <freebsd-current@FreeBSD.org>; Wed, 20 Mar 1996 10:20:49 +0100
Received: by sax.sax.de (8.6.11/8.6.12-s1) with UUCP
	id KAA08086 for freebsd-current@FreeBSD.org; Wed, 20 Mar 1996 10:20:48 +0100
Received: (from j@localhost) by uriah.heep.sax.de (8.7.4/8.6.9) id KAA07568 for freebsd-current@FreeBSD.org; Wed, 20 Mar 1996 10:08:20 +0100 (MET)
From: J Wunsch <j@uriah.heep.sax.de>
Message-Id: <199603200908.KAA07568@uriah.heep.sax.de>
Subject: Re: system running with DEVFS
To: freebsd-current@FreeBSD.org (FreeBSD-current users)
Date: Wed, 20 Mar 1996 10:08:19 +0100 (MET)
Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch)
In-Reply-To: <Pine.BSF.3.91.960319191330.249G-100000@ki.net> from "Marc G. Fournier" at Mar 19, 96 07:22:23 pm
X-Phone: +49-351-2012 669
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

As Marc G. Fournier wrote:

> 	One thing I'm curious about, though, is:
> 
> freebsd# ls -lt /devfs/log /dev/log
> srw-rw-rw-  1 root  wheel         0 Mar 19 19:11 /dev/log
> crw-------  2 root  wheel    7,   0 Mar 19 19:11 /devfs/log
> 
> 	The two log devices seem to be created differently, but I'm 
> wondering if it is something that should be worried about, or if it 
> doesn't matter?  I'm assuming that the "correct" mode is the one in
> /dev/log...but would like to confirm before I attempt to fix subr_log.c
> to duplicate this properly.

/dev/log is the "Unix domain socket" (s/Unix/Posix/, or s/Unix/Local/
if you like it better) for syslog.  Being a socket, it can only be
created at run-time by the application opening the socket.

Most likely, it should be /var/run/log instead (like /var/run/printer).

/devfs/log is an error.  It should be /devfs/klog instead:

j@uriah 1016% ls -l /dev/*log*
crw-------  1 root  wheel    7,   0 Feb 10  1995 /dev/klog
srw-rw-rw-  1 root  wheel         0 Mar 16 00:55 /dev/log=

-- 
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  Wed Mar 20 01:49:19 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id BAA18694
          for current-outgoing; Wed, 20 Mar 1996 01:49:19 -0800 (PST)
Received: (from dima@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id BAA18683
          for current@freebsd.org; Wed, 20 Mar 1996 01:49:16 -0800 (PST)
Message-Id: <199603200949.BAA18683@freefall.freebsd.org>
Subject: X11R6.1
To: current@freebsd.org
Date: Wed, 20 Mar 1996 01:49:16 -0800 (PST)
From: dima@freebsd.org (Dima Ruban)
X-Class: Fast
Organization: HackerDome
X-Mailer: ELM [version 2.4 PL24]
Content-Type: text
Sender: owner-current@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

Hey guys!

What about to add X11R6.1 to ldconfig search paths in /etc/rc?
Anybody has anything against it? If not, I'll commit it.

-- dima

From owner-freebsd-current  Wed Mar 20 05:11:17 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id FAA01786
          for current-outgoing; Wed, 20 Mar 1996 05:11:17 -0800 (PST)
Received: from neon.Glock.COM (root@neon.glock.com [198.82.228.159])
          by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id FAA01780
          Wed, 20 Mar 1996 05:11:15 -0800 (PST)
Received: (from mmead@localhost) by neon.Glock.COM (8.7.4/8.7.3) id IAA00599; Wed, 20 Mar 1996 08:11:14 -0500 (EST)
From: "matthew c. mead" <mmead@Glock.COM>
Message-Id: <199603201311.IAA00599@neon.Glock.COM>
Subject: Re: X11R6.1
To: dima@FreeBSD.ORG (Dima Ruban)
Date: Wed, 20 Mar 1996 08:11:14 -0500 (EST)
Cc: current@FreeBSD.ORG
In-Reply-To: <199603200949.BAA18683@freefall.freebsd.org> from "Dima Ruban" at Mar 20, 96 01:49:16 am
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

Dima Ruban writes:

> Hey guys!

> What about to add X11R6.1 to ldconfig search paths in /etc/rc?
> Anybody has anything against it? If not, I'll commit it.

	Is R6.1 out yet?  For site customizations I usually do
this in /etc/rc.local:

if [ -x /sbin/ldconfig ]; then
	_LDC=""
	if [ -d /usr/local/X11R6/lib ]; then
	    _LDC="${_LDC} /usr/local/X11R6/lib"
	fi
	echo 'adding to ldconfig path:' ${_LDC}
	ldconfig -m ${_LDC}
fi



-matt

-- 
Matthew C. Mead

mmead@Glock.COM
http://www.Glock.COM/~mmead/

From owner-freebsd-current  Wed Mar 20 05:16:27 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id FAA01971
          for current-outgoing; Wed, 20 Mar 1996 05:16:27 -0800 (PST)
Received: from osti.rmt.utk.edu (OSTI.RMT.UTK.EDU [128.169.24.17])
          by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id FAA01966
          Wed, 20 Mar 1996 05:16:22 -0800 (PST)
Received: (from wolpert@localhost) by osti.rmt.utk.edu (8.7.3/8.6.12) id IAA05954; Wed, 20 Mar 1996 08:25:53 -0500 (EST)
Date: Wed, 20 Mar 1996 08:25:53 -0500 (EST)
Message-Id: <199603201325.IAA05954@osti.rmt.utk.edu>
From: Edward Wolpert <wolpert@osti.rmt.utk.edu>
To: dima@freebsd.org
CC: current@freebsd.org
In-reply-to: <199603200949.BAA18683@freefall.freebsd.org> (dima@freebsd.org)
Subject: Re: X11R6.1
Sender: owner-current@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

] Date: Wed, 20 Mar 1996 01:49:16 -0800 (PST)
] From: dima@freebsd.org (Dima Ruban)
] X-Class: Fast
] Organization: HackerDome
] X-Mailer: ELM [version 2.4 PL24]
] Content-Type: text
] Sender: owner-current@freebsd.org
] X-Loop: FreeBSD.org
] Precedence: bulk
] 
] Hey guys!
] 
] What about to add X11R6.1 to ldconfig search paths in /etc/rc?
] Anybody has anything against it? If not, I'll commit it.
] 
] -- dima
] 

This may be a silly question, but shouldn't /usr/X11 be a sym link to
/usr/X11R6.1 and keep /usr/X11 in the ldconfig search path?  That way
one just updates the link rather than the /etc/rc file...

Just a question...

-- 
               Virtually,
               Edward Wolpert

 ------------------------------  "Nothingness is the worm at the
|wolpert@utk.edu               |  heart of being."  -Sartre
|wolpert@osti.rmt.utk.edu      | 
 ------------------------------                         Fnord!
[DC 92 17 C1 7A 42 06 73  66 9D A9 00 52 07 6B 3B]

From owner-freebsd-current  Wed Mar 20 05:29:28 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id FAA02268
          for current-outgoing; Wed, 20 Mar 1996 05:29:28 -0800 (PST)
Received: from neon.Glock.COM (root@neon.glock.com [198.82.228.159])
          by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id FAA02263
          for <current@freebsd.org>; Wed, 20 Mar 1996 05:29:26 -0800 (PST)
Received: (from mmead@localhost) by neon.Glock.COM (8.7.4/8.7.3) id IAA00770; Wed, 20 Mar 1996 08:29:25 -0500 (EST)
From: "matthew c. mead" <mmead@Glock.COM>
Message-Id: <199603201329.IAA00770@neon.Glock.COM>
Subject: Re: cvs-all-digest V1 #300
To: current@freebsd.org
Date: Wed, 20 Mar 1996 08:29:25 -0500 (EST)
In-Reply-To: <199603191927.LAA23880@freefall.freebsd.org> from "owner-cvs-all-digest@freefall.freebsd.org" at Mar 19, 96 11:27:18 am
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

owner-cvs-all-digest@freefall.freebsd.org writes:

> From: John Dyson <dyson>
> Date: Mon, 18 Mar 1996 21:13:24 -0800 (PST)
> Subject: cvs commit:  src/sys/miscfs/specfs spec_vnops.c src/sys/vm vnode_pager.c
> 
> dyson       96/03/18 21:13:24
> 
>   Modified:    sys/miscfs/specfs  spec_vnops.c
>                sys/vm    vnode_pager.c
>   Log:
>   Fix the problem that unmounting filesystems that are backed by a VMIO
>   device have reference count problems.  We mark the underlying object
>   ono-persistent, and account for the reference count that the VM system
>   maintainsfor the special device close.  This should fix the removable
>   device problem.
>   
>   Revision  Changes    Path
>   1.29      +3 -2      src/sys/miscfs/specfs/spec_vnops.c
>   1.59      +5 -2      src/sys/vm/vnode_pager.c
> 
> ------------------------------

	I've thoroughly tested this code change, and from what I
can tell, it fixes all the problems I've found using a JAZ drive,
save one.  The one that it doesn't fix is if you mount a UFS
filesystem on the JAZ drive and allow it to sleep, then before
waking it up via a standard filesystem call you fsck the raw
device (ok, ok, so I did this by accident the first time... :-),
then try to use the mounted ufs, you cannot unmount it or use it
until you reboot.  The solution to that problem is to not try to
fsck it while it's mounted.  Other than that, the unsleep code
and the unmount/unlocking for ejection code works great.


-matt

--
Matthew C. Mead

mmead@Glock.COM
http://www.Glock.COM/~mmead/

From owner-freebsd-current  Wed Mar 20 06:34:04 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id GAA05200
          for current-outgoing; Wed, 20 Mar 1996 06:34:04 -0800 (PST)
Received: from mail.think.com (Mail1.Think.COM [131.239.33.245])
          by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id GAA05175
          for <current@freefall.freebsd.org>; Wed, 20 Mar 1996 06:34:00 -0800 (PST)
Received: from Early-Bird-1.Think.COM by mail.think.com; Wed, 20 Mar 96 09:33:32 -0500
Received: from compound (fergus-29.dialup.cfa.org) by Early-Bird.Think.COM; Wed, 20 Mar 96 09:33:29 EST
Received: (from alk@localhost) by compound (8.6.12/8.6.112) id IAA19341; Wed, 20 Mar 1996 08:34:00 -0600
Date: Wed, 20 Mar 1996 08:34:00 -0600
Message-Id: <199603201434.IAA19341@compound>
From: Tony Kimball <alk@Think.COM>
To: gclarkii@main.gbdata.com
Cc: current@freefall.freebsd.org
In-Reply-To: <199603200802.CAA10056@main.gbdata.com> (message from Gary Clark
	II on Wed, 20 Mar 1996 02:02:16 -0600 (CST))
Subject: Re: perl4
Sender: owner-current@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

   From: Gary Clark II <gclarkii@main.gbdata.com>

   Perl IS the sys admin language of choice.  Many systems now ship perl
   with the distribution like we do.  Thats why I brought it in.

The fact is not at issue.  The relationship between the fact 
and the decision is being questioned.

   > If I write C versions of these scripts, will that suffice
   > to break perl off into a package?

   Not really, not unless you will also re-write ALL future scripts also.
   I'm in the process of a total rewrite for adduser to expand it into
   a sysadmin system (add user, delete user, groups, change user attributes, etc).
   This will be a curses based system.

It can go into the perl package:  A perl4 version in the perl4
package, if you want to support perl4; a perl5 version in the perl5
package, if you want to support perl5.  It's a good thing.  I
encourage and commend you.  It does not belong in the base OS
distribution.  

   P.S. Sorry for the slight flamage, but I still belive we need perl.

I absolutely agree that we need perl (or more accurately that "FreeBSD
needs perl").  I claim that it does not belong in the base OS, because
it is not tightly coupled, and because most perl users will use the
most recent version, and *not* the version shipped, so it is a legacy,
baggage.

Making the base OS small is a Good Thing.  Making it independent of
the choice of perl version level is a Good Thing.  The point is to
give users the freedom to choose, rather than forcing them to remove
perl by hand in order to eliminate an abhorrent redundancy.  Would you
require that XF86 be bundled as well?  Mi genoito!

My cause is just, because my cause is the cause of freedom.  My
detractors are the agents of totalitarianism.  I regret only that
I have but one life to give in the cause of component orthogonality.




From owner-freebsd-current  Wed Mar 20 06:41:27 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id GAA05634
          for current-outgoing; Wed, 20 Mar 1996 06:41:27 -0800 (PST)
Received: from snake.hut.fi (root@snake.hut.fi [193.167.6.99])
          by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id GAA05629
          for <freebsd-current@freebsd.org>; Wed, 20 Mar 1996 06:41:22 -0800 (PST)
Received: from lk-hp-20.hut.fi (lk-hp-20.hut.fi [130.233.247.33]) by snake.hut.fi (8.7.3/8.7.3) with ESMTP id QAA27563 for <freebsd-current@freebsd.org>; Wed, 20 Mar 1996 16:41:16 +0200 (EET)
From: Juha Inkari <inkari@snakemail.hut.fi>
Received: (inkari@localhost) by lk-hp-20.hut.fi (8.6.12/8.6.7) id QAA05944 for freebsd-current@freebsd.org; Wed, 20 Mar 1996 16:41:15 +0200
Message-Id: <199603201441.QAA05944@lk-hp-20.hut.fi>
Subject: GNU tar 1.11.2
To: freebsd-current@freebsd.org
Date: Wed, 20 Mar 1996 16:41:15 +0200 (EET)
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


I just found, that a command:

tar -C /tmp -xsf foo.tar

drops core. This is because tar seems to assume, that when s flag is
used, there are more arguments to come, and ends up calling strlen(0)
(see patch below).

I looked up GNU tar 1.11.8 (dated May 1995), and the code indeed seems
to have changed a bit. It doesn't work correctly either, but gives a
"Missing file name after -C".

However, is anyone considered bumping the tar version from 1.11.2
(March 1993) to 1.11.8 for any reason whatever ?

----------------------------------------------
*** tar.orig/tar.c	Thu Oct 26 12:59:43 1995
--- tar/tar.c	Wed Mar 20 15:51:04 1996
***************
*** 1010,1027 ****
  		}
  	      namebuf->change_dir = chdir_name;
  	    }
! 	  namebuf->length = strlen (p);
! 	  if (namebuf->length >= namelen)
! 	    {
! 	      namebuf = (struct name *) ck_realloc (namebuf, sizeof (struct name) + namebuf->length);
! 	      namelen = namebuf->length;
! 	    }
! 	  strncpy (namebuf->name, p, namebuf->length);
! 	  namebuf->name[namebuf->length] = 0;
! 	  namebuf->next = (struct name *) NULL;
! 	  namebuf->found = 0;
! 	  namelist = namebuf;
! 	  namelast = namelist;
  	}
        return;
      }
--- 1010,1030 ----
  		}
  	      namebuf->change_dir = chdir_name;
  	    }
!           if (p)
!             {
!               namebuf->length = strlen (p);
!               if (namebuf->length >= namelen)
!                 {
!                   namebuf = (struct name *) ck_realloc (namebuf, sizeof (struct name) + namebuf->length);
!                   namelen = namebuf->length;
!                 }
!               strncpy (namebuf->name, p, namebuf->length);
!               namebuf->name[namebuf->length] = 0;
!               namebuf->next = (struct name *) NULL;
!               namebuf->found = 0;
!               namelist = namebuf;
!               namelast = namelist;
!            }
  	}
        return;
      }

----------------------------------------------

From owner-freebsd-current  Wed Mar 20 06:42:21 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id GAA05665
          for current-outgoing; Wed, 20 Mar 1996 06:42:21 -0800 (PST)
Received: from rf900.physics.usyd.edu.au (rf900.physics.usyd.edu.au [129.78.129.109])
          by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id GAA05660
          Wed, 20 Mar 1996 06:42:16 -0800 (PST)
Received: (from dawes@localhost) by rf900.physics.usyd.edu.au (8.6.11/8.6.9) id XAA10969; Wed, 20 Mar 1996 23:56:33 +1100
From: David Dawes <dawes@rf900.physics.usyd.edu.au>
Message-Id: <199603201256.XAA10969@rf900.physics.usyd.edu.au>
Subject: Re: X11R6.1
To: dima@freebsd.org (Dima Ruban)
Date: Wed, 20 Mar 1996 23:56:32 +1100 (EST)
Cc: current@freebsd.org
In-Reply-To: <199603200949.BAA18683@freefall.freebsd.org> from "Dima Ruban" at Mar 20, 96 01:49:16 am
X-Mailer: ELM [version 2.4 PL23]
Content-Type: text
Sender: owner-current@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

>What about to add X11R6.1 to ldconfig search paths in /etc/rc?
>Anybody has anything against it? If not, I'll commit it.

Although /usr/X11R6.1 is the default ProjectRoot setting for the X
Consortium's R6.1, XFree86 is planning to keep using /usr/X11R6 (as
we've done for the R6.1-based 3.1.2D beta release).  We decided to do
this to avoid the need for these and similar changes.

David

From owner-freebsd-current  Wed Mar 20 07:34:39 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id HAA09053
          for current-outgoing; Wed, 20 Mar 1996 07:34:39 -0800 (PST)
Received: from FSL.ORST.EDU (root@FSL.ORST.EDU [128.193.112.105])
          by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id HAA09046
          Wed, 20 Mar 1996 07:34:32 -0800 (PST)
Received: from picea.FSL.ORST.EDU (hernanw@picea.FSL.ORST.EDU [128.193.112.3]) by FSL.ORST.EDU (8.6.9/8.6.9) with ESMTP id HAA01211; Wed, 20 Mar 1996 07:34:27 -0800
Received: (from hernanw@localhost) by picea.FSL.ORST.EDU (8.7/8.6.9) id HAA01787; Wed, 20 Mar 1996 07:34:26 -0800 (PST)
Date: Wed, 20 Mar 1996 07:34:25 -0800 (PST)
From: Wayne Hernandez <hernanw@FSL.ORST.EDU>
To: JULIAN Elischer <julian@ref.tfs.com>
cc: hackers@FreeBSD.ORG, current@FreeBSD.ORG
Subject: Re: new sup server
In-Reply-To: <199603191758.JAA02581@ref.tfs.com>
Message-ID: <Pine.SUN.3.91.960320073226.1731A-100000@picea.FSL.ORST.EDU>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-current@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk



On Tue, 19 Mar 1996, JULIAN Elischer wrote:

> In fact what is the lag behing all the servers..
> can we find out the update schedules for them?
> it helps US shedule OUR updates..
> 
> julian

For sup3.freebsd.org, I'm updating at 2 a.m. and 2 p.m. pst/pdt.

Wayne


From owner-freebsd-current  Wed Mar 20 07:41:12 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id HAA09867
          for current-outgoing; Wed, 20 Mar 1996 07:41:12 -0800 (PST)
Received: from rocky.sri.MT.net (rocky.sri.MT.net [204.182.243.10])
          by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id HAA09849
          Wed, 20 Mar 1996 07:41:08 -0800 (PST)
Received: (from nate@localhost) by rocky.sri.MT.net (8.6.12/8.6.12) id IAA07669; Wed, 20 Mar 1996 08:44:00 -0700
Date: Wed, 20 Mar 1996 08:44:00 -0700
From: Nate Williams <nate@sri.MT.net>
Message-Id: <199603201544.IAA07669@rocky.sri.MT.net>
To: dima@FreeBSD.ORG (Dima Ruban)
Cc: current@FreeBSD.ORG
Subject: Re: X11R6.1
In-Reply-To: <199603200949.BAA18683@freefall.freebsd.org>
References: <199603200949.BAA18683@freefall.freebsd.org>
Sender: owner-current@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

> What about to add X11R6.1 to ldconfig search paths in /etc/rc?
> Anybody has anything against it? If not, I'll commit it.

Why is it needed?  Is it going to be a standard path for things, or will
the /usr/X11R6 path suffice for all X11R6 binaries?

(I'm partial to the latter)


Nate

From owner-freebsd-current  Wed Mar 20 07:50:23 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id HAA10475
          for current-outgoing; Wed, 20 Mar 1996 07:50:23 -0800 (PST)
Received: from time.cdrom.com (time.cdrom.com [204.216.27.226])
          by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id HAA10470
          for <current@freefall.freebsd.org>; Wed, 20 Mar 1996 07:50:20 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by time.cdrom.com (8.7.5/8.6.9) with SMTP id HAA00561; Wed, 20 Mar 1996 07:49:50 -0800 (PST)
To: Tony Kimball <alk@Think.COM>
cc: gclarkii@main.gbdata.com, current@freefall.freebsd.org
Subject: Re: perl4 
In-reply-to: Your message of "Wed, 20 Mar 1996 08:34:00 CST."
             <199603201434.IAA19341@compound> 
Date: Wed, 20 Mar 1996 07:49:50 -0800
Message-ID: <559.827336990@time.cdrom.com>
From: "Jordan K. Hubbard" <jkh@time.cdrom.com>
Sender: owner-current@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

> I absolutely agree that we need perl (or more accurately that "FreeBSD
> needs perl").  I claim that it does not belong in the base OS, because
> it is not tightly coupled, and because most perl users will use the
> most recent version, and *not* the version shipped, so it is a legacy,
> baggage.

You apparently miss the point that perl is *used* by the base system
and making things dependent on a package, something for which there's
not even a support framework (e.g. you *can't* depend on a port or
package from the base system), simply would not work.  Here's a list
of the utilities/libs which currently rely on perl being present to
either build at all or not fall over at run time:

/usr/src/gnu/usr.bin/cvs
/usr/src/secure/lib/libdes
/usr/src/sys/pci/locate.pl
/usr/src/usr.bin/killall
/usr/src/usr.bin/sgmlfmt
/usr/src/usr.bin/sgmls
/usr/src/usr.bin/which
/usr/src/usr.sbin/kbdmap
/usr/src/usr.sbin/spkrtest
/usr/src/usr.sbin/tzsetup
/usr/src/usr.sbin/xntpd

> perl by hand in order to eliminate an abhorrent redundancy.  Would you
> require that XF86 be bundled as well?  Mi genoito!

Of course not, it's not required for anything.  Perl is.  Case
dismissed.

					Jordan

From owner-freebsd-current  Wed Mar 20 08:20:23 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id IAA12431
          for current-outgoing; Wed, 20 Mar 1996 08:20:23 -0800 (PST)
Received: from rocky.sri.MT.net (rocky.sri.MT.net [204.182.243.10])
          by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id IAA12426
          for <freebsd-current@freebsd.org>; Wed, 20 Mar 1996 08:20:18 -0800 (PST)
Received: (from nate@localhost) by rocky.sri.MT.net (8.6.12/8.6.12) id JAA07794; Wed, 20 Mar 1996 09:23:04 -0700
Date: Wed, 20 Mar 1996 09:23:04 -0700
From: Nate Williams <nate@sri.MT.net>
Message-Id: <199603201623.JAA07794@rocky.sri.MT.net>
To: Juha Inkari <inkari@snakemail.hut.fi>
Cc: freebsd-current@freebsd.org
Subject: Re: GNU tar 1.11.2
In-Reply-To: <199603201441.QAA05944@lk-hp-20.hut.fi>
References: <199603201441.QAA05944@lk-hp-20.hut.fi>
Sender: owner-current@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

> I just found, that a command:
> 
> tar -C /tmp -xsf foo.tar
> 
> drops core. This is because tar seems to assume, that when s flag is
> used, there are more arguments to come, and ends up calling strlen(0)
> (see patch below).
> 
> I looked up GNU tar 1.11.8 (dated May 1995), and the code indeed seems
> to have changed a bit. It doesn't work correctly either, but gives a
> "Missing file name after -C".
> 
> However, is anyone considered bumping the tar version from 1.11.2
> (March 1993) to 1.11.8 for any reason whatever ?

I looked at it a while back, and the new GNU tar contains a lot of stuff
that I don't think we need, but one of the international folks (ie;
8-bit clean) like Andrey comment.


Nate

From owner-freebsd-current  Wed Mar 20 08:25:43 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id IAA12701
          for current-outgoing; Wed, 20 Mar 1996 08:25:43 -0800 (PST)
Received: from mail.think.com (Mail1.Think.COM [131.239.33.245])
          by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id IAA12696
          for <current@freefall.freebsd.org>; Wed, 20 Mar 1996 08:25:39 -0800 (PST)
Received: from Early-Bird-1.Think.COM by mail.think.com; Wed, 20 Mar 96 11:24:51 -0500
Received: from compound (fergus-29.dialup.cfa.org) by Early-Bird.Think.COM; Wed, 20 Mar 96 11:24:47 EST
Received: (from alk@localhost) by compound (8.6.12/8.6.112) id KAA20041; Wed, 20 Mar 1996 10:25:24 -0600
Date: Wed, 20 Mar 1996 10:25:24 -0600
Message-Id: <199603201625.KAA20041@compound>
From: Tony Kimball <alk@Think.COM>
To: jkh@time.cdrom.com
Cc: gclarkii@main.gbdata.com, current@freefall.freebsd.org
In-Reply-To: <559.827336990@time.cdrom.com> (jkh@time.cdrom.com)
Subject: Re: perl4
Sender: owner-current@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk


   Of course not, it's not required for anything.  Perl is.  

And in case you missed it, I offer to fix that by my sweat.

   Case dismissed.

Appeal filed.

From owner-freebsd-current  Wed Mar 20 08:36:53 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id IAA13432
          for current-outgoing; Wed, 20 Mar 1996 08:36:53 -0800 (PST)
Received: from time.cdrom.com (time.cdrom.com [204.216.27.226])
          by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id IAA13422
          for <current@freefall.freebsd.org>; Wed, 20 Mar 1996 08:36:51 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by time.cdrom.com (8.7.5/8.6.9) with SMTP id IAA00990; Wed, 20 Mar 1996 08:36:01 -0800 (PST)
To: Tony Kimball <alk@Think.COM>
cc: gclarkii@main.gbdata.com, current@freefall.freebsd.org
Subject: Re: perl4 
In-reply-to: Your message of "Wed, 20 Mar 1996 10:25:24 CST."
             <199603201625.KAA20041@compound> 
Date: Wed, 20 Mar 1996 08:36:01 -0800
Message-ID: <988.827339761@time.cdrom.com>
From: "Jordan K. Hubbard" <jkh@time.cdrom.com>
Sender: owner-current@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

>    Of course not, it's not required for anything.  Perl is.  
> 
> And in case you missed it, I offer to fix that by my sweat.
> 
>    Case dismissed.
> 
> Appeal filed.

You're saying you're willing to re-write all of the offending
utilities in C, including the test scripts for xntpd and sendmail?

Isn't this something of a waste of effort just to get rid of one lousy
package?  I mean, I appreciate the hardship you're willing to go
through just to improve the purity of our codebase, but I wonder if
such energies wouldn't be more profitably applied to something that's
more seriously broken.

					Jordan

From owner-freebsd-current  Wed Mar 20 08:54:35 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id IAA14818
          for current-outgoing; Wed, 20 Mar 1996 08:54:35 -0800 (PST)
Received: from ref.tfs.com (ref.tfs.com [140.145.254.251])
          by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id IAA14806
          for <current@freebsd.org>; Wed, 20 Mar 1996 08:54:33 -0800 (PST)
Received: (from julian@localhost) by ref.tfs.com (8.7.3/8.6.9) id AAA15977; Wed, 20 Mar 1996 00:11:40 -0800 (PST)
Message-Id: <199603200811.AAA15977@ref.tfs.com>
Subject: Re: PATCH/DEVFS: /dev/dump & /dev/klog
To: scrappy@ki.net (Marc G. Fournier)
Date: Wed, 20 Mar 1996 00:11:39 -0800 (PST)
From: "JULIAN Elischer" <julian@ref.tfs.com>
Cc: current@freebsd.org
In-Reply-To: <Pine.BSF.3.91.960320005955.255D-100000@ki.net> from "Marc G. Fournier" at Mar 20, 96 01:04:55 am
X-Mailer: ELM [version 2.4 PL25 ME8b]
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 only one comment, which is that
 there is a new devfs registration routine that uses a singl argument 
 for a name rather than the dir/make pair..
 check devfsext.h
It is devfs_ddd_devswf() and it has a printf style 
format string to define the device name
this is now the preferred registration routine, though
what you have is just fine...




> 
> 
> Hi...
> 
> 	Still a couple of modifications to make this run completely on devfs, 
> but here is a patch that gets ps to work properly (needs /dev/drum) and a fix 
> for subr_log.c.
> 
> 	subr_log.c was creating a character device for /dev/log, when it
> should have been creating /dev/klog.  /dev/log, according to /dev/log
> as installed, and according to the syslogd man page, is a socket, not a
> device.
> 
> 	The modifications aren't major or anything,  but if I'm doing
> something wrong, or omitting something, please let me know.  I think I'm
> doing this right...
> 
> 
> ---[ /usr/src/sys/vm/vm_swap.c ]-----
> 
> *** /home/staff/scrappy/vm_swap.c	Wed Mar 20 00:58:45 1996
> --- vm_swap.c	Wed Mar 20 00:50:39 1996
> ***************
> *** 52,57 ****
> --- 52,61 ----
>   #include <vm/swap_pager.h>
>   
>   #include <miscfs/specfs/specdev.h>
> + #ifdef DEVFS
> +   #include <sys/devfsext.h>
> +   static void *drum_devfs_token;
> + #endif /*DEVFS*/
>   
>   static void swstrategy __P((struct buf *));
>   
> ***************
> *** 297,302 ****
> --- 301,311 ----
>   		dev = makedev(BDEV_MAJOR,0);
>   		bdevsw_add(&dev,&sw_bdevsw,NULL);
>   		sw_devsw_installed = 1;
> + #ifdef DEVFS
> +           drum_devfs_token =
> +                 devfs_add_devsw("/", "drum", &sw_cdevsw, 0,
> +                                  DV_CHR, 0, 0, 0640 );
> + #endif /*DEVFS*/ 
>       	}
>   }
>   
> ----[ /usr/src/sys/kern/subr_log.c ]-----
> 
> 
> *** subr_log.c.orig	Tue Mar 19 23:38:48 1996
> --- subr_log.c	Tue Mar 19 23:39:14 1996
> ***************
> *** 255,261 ****
>   		log_devsw_installed = 1;
>   #ifdef DEVFS
>   		log_devfs_token = devfs_add_devsw(
> ! 			"/", "log", &log_cdevsw, 0, DV_CHR, 0, 0, 0600);
>   #endif
>       	}
>   }
> --- 255,261 ----
>   		log_devsw_installed = 1;
>   #ifdef DEVFS
>   		log_devfs_token = devfs_add_devsw(
> ! 			"/", "klog", &log_cdevsw, 0, DV_CHR, 0, 0, 0600);
>   #endif
>       	}
>   }
> 
> 
> Marc G. Fournier | POP Mail  Telnet Acct  DNS Hosting
> System           |  WWW Services   Database Services  | Knowledge, 
>   Administrator  |                                    | Information and
>  scrappy@ki.net  |      WWW: http://www.ki.net        | Communications, Inc
> 
> 


From owner-freebsd-current  Wed Mar 20 08:54:35 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id IAA14826
          for current-outgoing; Wed, 20 Mar 1996 08:54:35 -0800 (PST)
Received: from ref.tfs.com (ref.tfs.com [140.145.254.251])
          by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id IAA14810
          for <current@freebsd.org>; Wed, 20 Mar 1996 08:54:33 -0800 (PST)
Received: (from julian@localhost) by ref.tfs.com (8.7.3/8.6.9) id SAA15459; Tue, 19 Mar 1996 18:48:12 -0800 (PST)
Message-Id: <199603200248.SAA15459@ref.tfs.com>
Subject: Re: system running with DEVFS
To: scrappy@ki.net (Marc G. Fournier)
Date: Tue, 19 Mar 1996 18:48:12 -0800 (PST)
From: "JULIAN Elischer" <julian@ref.tfs.com>
Cc: current@freebsd.org
In-Reply-To: <Pine.BSF.3.91.960319191330.249G-100000@ki.net> from "Marc G. Fournier" at Mar 19, 96 07:22:23 pm
X-Mailer: ELM [version 2.4 PL25 ME8b]
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 don't know if anyone is actually using devfs yet, as mounted
> onto /dev, but this afternoon I decided to try, and after some minor 
> modifications to pcvt_drv.c, got my system up and running.
> 

what mods?

> 	One thing I'm curious about, though, is:
> 
> freebsd# ls -lt /devfs/log /dev/log

> srw-rw-rw-  1 root  wheel         0 Mar 19 19:11 /dev/log
 this is a socket..
> crw-------  2 root  wheel    7,   0 Mar 19 19:11 /devfs/log
and this is something totally different
but I have no idea which is correct....

> 
> to duplicate this properly.
 you can't make a socket with devfs
 It's not a device....
> 
> 


From owner-freebsd-current  Wed Mar 20 08:59:50 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id IAA15282
          for current-outgoing; Wed, 20 Mar 1996 08:59:50 -0800 (PST)
Received: from mail.think.com (Mail1.Think.COM [131.239.33.245])
          by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id IAA15277
          for <current@freefall.freebsd.org>; Wed, 20 Mar 1996 08:59:48 -0800 (PST)
Received: from Early-Bird-1.Think.COM by mail.think.com; Wed, 20 Mar 96 11:59:23 -0500
Received: from compound (fergus-29.dialup.cfa.org) by Early-Bird.Think.COM; Wed, 20 Mar 96 11:59:19 EST
Received: (from alk@localhost) by compound (8.6.12/8.6.112) id KAA20250; Wed, 20 Mar 1996 10:59:52 -0600
Date: Wed, 20 Mar 1996 10:59:52 -0600
Message-Id: <199603201659.KAA20250@compound>
From: Tony Kimball <alk@Think.COM>
To: jkh@time.cdrom.com
Cc: gclarkii@main.gbdata.com, current@freefall.freebsd.org
In-Reply-To: <988.827339761@time.cdrom.com> (jkh@time.cdrom.com)
Subject: Re: perl4
Sender: owner-current@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk


   You're saying you're willing to re-write all of the offending
   utilities in C, including the test scripts for xntpd and sendmail?

Do the test scripts really need to be part of the base OS?

I would argue that since they are coupled to the perl release, they
should be part of the perl package.  You select your perl installation
just like you select des or kerberos or neither.  Selecting neither
limits your function, but the system is still intact and fully
operational as such. (I may be abusing the vernacular "package" here?)

   Isn't this something of a waste of effort just to get rid of one lousy
   package?  I mean, I appreciate the hardship you're willing to go
   through just to improve the purity of our codebase, but I wonder if
   such energies wouldn't be more profitably applied to something that's
   more seriously broken.

Yes, a reality check.  You're right.  I'd like to contribute something
to FreeBSD besides a subscription.  From the 2.2 TODO list, fsdb and
making iostat find the disks seem about right, for my interests and
skill level.  I'll go that way.





From owner-freebsd-current  Wed Mar 20 09:47:11 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id JAA20188
          for current-outgoing; Wed, 20 Mar 1996 09:47:11 -0800 (PST)
Received: from alpha.xerox.com (alpha.Xerox.COM [13.1.64.93])
          by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id JAA20183
          for <freebsd-current@freebsd.org>; Wed, 20 Mar 1996 09:47:02 -0800 (PST)
Received: from gemini.sdsp.mc.xerox.com ([13.231.132.20]) by alpha.xerox.com with SMTP id <15081(4)>; Wed, 20 Mar 1996 09:38:00 PST
Received: from gnu.mc.xerox.com (gnu.sdsp.mc.xerox.com) by gemini.sdsp.mc.xerox.com (4.1/SMI-4.1)
	id AA06765; Wed, 20 Mar 96 12:38:07 EST
Received: by gnu.mc.xerox.com (4.1/SMI-4.1)
	id AA10379; Wed, 20 Mar 96 12:38:05 EST
Message-Id: <9603201738.AA10379@gnu.mc.xerox.com>
To: Juha Inkari <inkari@snakemail.hut.fi>
Cc: freebsd-current@freebsd.org
Subject: Re: GNU tar 1.11.2 
In-Reply-To: Your message of "Wed, 20 Mar 1996 06:41:15 PST."
             <199603201441.QAA05944@lk-hp-20.hut.fi> 
Date: Wed, 20 Mar 1996 09:38:04 PST
From: "Marty Leisner" <leisner@sdsp.mc.xerox.com>
Sender: owner-current@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk


This is probably the wrong media to report general tar problems...
(gnu.utils.bug is much better).

I've done some fixes to 1.11.2 with this regard, 1.11.8 worked fine...

I think tar 1.11.8 is considered beta...

marty

From owner-freebsd-current  Wed Mar 20 10:12:17 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id KAA21902
          for current-outgoing; Wed, 20 Mar 1996 10:12:17 -0800 (PST)
Received: from ki.net (ki.net [142.77.249.8])
          by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id KAA21895
          for <current@freebsd.org>; Wed, 20 Mar 1996 10:12:10 -0800 (PST)
Received: (from scrappy@localhost) by ki.net (8.7.4/8.7.4) id NAA29605; Wed, 20 Mar 1996 13:10:47 -0500 (EST)
Date: Wed, 20 Mar 1996 13:10:45 -0500 (EST)
From: "Marc G. Fournier" <scrappy@ki.net>
To: Bill Paul <wpaul@skynet.ctr.columbia.edu>
cc: current@freebsd.org
Subject: Re: NIS problem
In-Reply-To: <199603200731.CAA10198@skynet.ctr.columbia.edu>
Message-ID: <Pine.BSF.3.91.960320130756.29377C-100000@ki.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-current@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

On Wed, 20 Mar 1996, Bill Paul wrote:

> > 	I've set the appropriate settings in sysconfig, and am running
> > ypbind -s on that machine, but try as I might, I can't login to that
> > machine unless the user entry is in the password file on that machine.
> 
> There's stuff missing here. Editing sysconfig is not all there is
> to it (though I'm sure people would like it to be that way :). You
> need to add +::::::::: to the end of /etc/master.passwd and rebuild

	That did it...I had put +:+:::::::: in my master.passwd file ;(
Works now, thanks.

> Read the passwd(5) man page when modifying /etc/master.passwd. Don't
> get clever with the magic '+' entries unless you know what you're
> doing. Don't use +:*::::::::. Don't use +::0:0::::::. Don't use
> any combination thereof. This is not SunOS. Don't expect everything
> to work the same.
>
	Ack...I looked through every YP man page I could find, but didn't
even think to look at passwd(5)...sorry for wasting time :(

	It works now, thanks ...


Marc G. Fournier | POP Mail  Telnet Acct  DNS Hosting
System           |  WWW Services   Database Services  | Knowledge, 
  Administrator  |                                    | Information and
 scrappy@ki.net  |      WWW: http://www.ki.net        | Communications, Inc


From owner-freebsd-current  Wed Mar 20 10:51:10 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id KAA24420
          for current-outgoing; Wed, 20 Mar 1996 10:51:10 -0800 (PST)
Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11])
          by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id KAA24408
          for <freebsd-current@FreeBSD.org>; Wed, 20 Mar 1996 10:50:59 -0800 (PST)
Received: from sax.sax.de by irz301.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id TAA22771 for <freebsd-current@FreeBSD.org>; Wed, 20 Mar 1996 19:50:44 +0100
Received: by sax.sax.de (8.6.11/8.6.12-s1) with UUCP
	id TAA13856 for freebsd-current@FreeBSD.org; Wed, 20 Mar 1996 19:50:43 +0100
Received: (from j@localhost) by uriah.heep.sax.de (8.7.4/8.6.9) id TAA08825 for freebsd-current@FreeBSD.org; Wed, 20 Mar 1996 19:01:32 +0100 (MET)
From: J Wunsch <j@uriah.heep.sax.de>
Message-Id: <199603201801.TAA08825@uriah.heep.sax.de>
Subject: Re: X11R6.1
To: freebsd-current@FreeBSD.org (FreeBSD-current users)
Date: Wed, 20 Mar 1996 19:01:32 +0100 (MET)
In-Reply-To: <199603200949.BAA18683@freefall.freebsd.org> from "Dima Ruban" at Mar 20, 96 01:49:16 am
X-Phone: +49-351-2012 669
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

As Dima Ruban wrote:

> What about to add X11R6.1 to ldconfig search paths in /etc/rc?
> Anybody has anything against it? If not, I'll commit it.

XFree86(tm) will continue to install into /usr/X11R6, even with the
R6.1 changes.  So i don't see any need to add it _by default_.

-- 
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  Wed Mar 20 11:25:36 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id LAA26107
          for current-outgoing; Wed, 20 Mar 1996 11:25:36 -0800 (PST)
Received: from main.statsci.com (main.statsci.com [198.145.127.110])
          by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id LAA26097
          for <freebsd-current@FreeBSD.org>; Wed, 20 Mar 1996 11:25:34 -0800 (PST)
Received: from statsci.com by main.statsci.com with smtp
	(Smail3.1.29.1 #3) id m0tzTV8-000r3sC; Wed, 20 Mar 96 11:24 PST
Message-Id: <m0tzTV8-000r3sC@main.statsci.com>
To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch)
cc: freebsd-current@FreeBSD.org (FreeBSD-current users)
Subject: Re: perl4 
In-reply-to: Your message of "Wed, 20 Mar 1996 10:13:13 +0100."
             <199603200913.KAA07672@uriah.heep.sax.de> 
Reply-to: scott@statsci.com
Date: Wed, 20 Mar 1996 11:24:52 -0800
From: Scott Blachowicz <scott@statsci.com>
Sender: owner-current@FreeBSD.org
X-Loop: FreeBSD.org
Precedence: bulk

J Wunsch <j@uriah.heep.sax.de> wrote:

> > By the way, which is inherantly broken when executed as any sort of
> > script.  It needs to be a shell builtin or it needs to die.

> Huh?  #!/bin/sh, #!/bin/csh aren't shell builtins either.  In fact, all
> these scripts are acceptable to execve(2), and the shell won't even
> notice the difference to a binary executable.

I think the point was more that if you define the purpose of 'which' to be
"tell me what would be run if I use this command", then it has to be a
shell builtin in order to find shell-local functions and aliases.

Scott Blachowicz  Ph: 206/283-8802x240   Mathsoft (Data Analysis Products Div)
                                         1700 Westlake Ave N #500
scott@statsci.com                        Seattle, WA USA   98109
Scott.Blachowicz@seaslug.org

From owner-freebsd-current  Wed Mar 20 11:44:52 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id LAA27143
          for current-outgoing; Wed, 20 Mar 1996 11:44:52 -0800 (PST)
Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211])
          by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id LAA26991
          for <current@FreeBSD.org>; Wed, 20 Mar 1996 11:41:05 -0800 (PST)
Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id MAA27577; Wed, 20 Mar 1996 12:33:42 -0700
From: Terry Lambert <terry@lambert.org>
Message-Id: <199603201933.MAA27577@phaeton.artisoft.com>
Subject: Re: DEVFS vs "regular /dev"
To: scrappy@ki.net (Marc G. Fournier)
Date: Wed, 20 Mar 1996 12:33:42 -0700 (MST)
Cc: current@FreeBSD.org
In-Reply-To: <Pine.BSF.3.91.960319232652.255B-100000@ki.net> from "Marc G. Fournier" at Mar 19, 96 11:28: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

> 	Just curious, but what is the advantage (and disadvantage, if any?)
> of using devfs vs "regular /dev"?  My first thought would be that its
> memory based instead of file system based, giving better performance, but
> that's just a guess.

1)	You don't need to make most things work when porting to
	a new platform to get a minimally running setup.

2)	Devices which don't probe as being there don't get nodes;
	all the device files in a devfs are "live".

3)	When you add a new device, you don't have to MAKEDEV.

4)	You can remote boot from systems other than FreeBSD that
	don't understand > 16 bit minor device numbers (since
	otherwise you couldn't make a FreeBSD /dev on those boxes
	and it would be impossible).

5)	When you load a kernel module, the device for it is automatically
	there.

6)	When you unload a kernel module, the device for it automatically
	goes away (no more stale devices).

7)	It provides a framework which allows cloning devices (like pty's)
	which require automatic node generation.  No more configuring
	fixed numbers of the things into the kernel.

8)	It provides a framework for "miniport drivers".  This means that
	physical to logical device mapping can be handled on a case by
	case basis.  This "magically" provides:

	A)	The ability to dedicate a whole device to a single FS.

	B)	The ability to dedicate a partition to a single FS.

	C)	The ability to disklabel a whole device.

	D)	The ability to disklabel partitions.

	E)	The ability to dedicate an extended partition to a
		single FS.

	F)	The ability to disklabel an extended partition.

	G)	The ability to recognize foreign disklabels (OSF, Sun,
		etc.)

	H)	The ability to recognize foreign partitioning schemes
		and/or artition ID's.

	I)	The ability to interpose media perfection at any logical
		device by using layering.  This means, for instance,
		that you could have a BAD144 type sector sparing that
		"knew" how to avoid the 1024 cylinder limit and "knew"
		how to work on the disklabel as well as the slices.

	J)	The ability to interpose compression in the same way.

	K)	The ability to interpose volume spanning the same way,
		including disk concatenation, striping, mirroring, and
		soft RAID implementations.

It is a *SERIOUS* enabling technology.  The sooner it is standard, the
better, IMO.

This assumes that the file system abstractions currently in place
change as well, since the /dev FS can't be mounted *after* the / FS
has been mounted as an inferior FS -- the /dev has to be there as
an overlay mount (translucent FS), and that means FS changes to allow
translucence and to divorce volume mappings from the need for a mount
point (basically, a shadow / and /dev on which the devfs /dev is mounted
and the real / is mounted over top of the shadow /).


					Regards,
					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 Mar 20 11:52:44 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id LAA27647
          for current-outgoing; Wed, 20 Mar 1996 11:52:44 -0800 (PST)
Received: from marble.eps.nagoya-u.ac.jp (marble.eps.nagoya-u.ac.jp [133.6.57.68])
          by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id LAA27641
          for <current@freebsd.org>; Wed, 20 Mar 1996 11:52:42 -0800 (PST)
Received: from marble.eps.nagoya-u.ac.jp (localhost [127.0.0.1]) by marble.eps.nagoya-u.ac.jp (8.7.4+2.6Wbeta6/3.3W9) with ESMTP id EAA01318 for <current@freebsd.org>; Thu, 21 Mar 1996 04:52:36 +0900 (JST)
Message-Id: <199603201952.EAA01318@marble.eps.nagoya-u.ac.jp>
To: current@freebsd.org
Subject: comment for CPU_686 in cputypes.h
X-Mailer: Mew beta version 0.96 on Emacs 19.28.1, Mule 2.3
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Date: Thu, 21 Mar 1996 04:52:33 +0900
From: KATO Takenori <kato@eclogite.eps.nagoya-u.ac.jp>
Sender: owner-current@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

In /sys/i386/include/cputypes.h, comment for CPU_586 is:

	/* P.....m (I hate lawyers; It's TM) */

but that for CPU_686 is:

	/* Pentium Pro */

It is not consistent with the comment for CPU_586.


Is using TM in source code illegal?  I hope the answer, NO.


----
KATO Takenori <kato@eclogite.eps.nagoya-u.ac.jp>
Dept. Earth Planet. Sci., Nagoya Univ.,  Nagoya, 464-01, Japan
Voice: +81-52-789-2529   Fax: +81-52-789-3033


From owner-freebsd-current  Wed Mar 20 12:14:09 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id MAA00419
          for current-outgoing; Wed, 20 Mar 1996 12:14:09 -0800 (PST)
Received: from onyx.nervosa.com (root@[192.187.228.86])
          by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id MAA00413
          for <freebsd-current@FreeBSD.ORG>; Wed, 20 Mar 1996 12:14:06 -0800 (PST)
Received: from onyx.nervosa.com (coredump@onyx.nervosa.com [10.0.0.1]) by onyx.nervosa.com (8.7.5/8.7.3) with SMTP id MAA28857; Wed, 20 Mar 1996 12:12:45 -0800 (PST)
Date: Wed, 20 Mar 1996 12:12:43 -0800 (PST)
From: invalid opcode <coredump@nervosa.com>
To: Juha Inkari <inkari@snakemail.hut.fi>
cc: freebsd-current@FreeBSD.ORG
Subject: Re: GNU tar 1.11.2
In-Reply-To: <199603201441.QAA05944@lk-hp-20.hut.fi>
Message-ID: <Pine.BSF.3.91.960320121216.28494A-100000@onyx.nervosa.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-current@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

On Wed, 20 Mar 1996, Juha Inkari wrote:

> I just found, that a command:
> tar -C /tmp -xsf foo.tar
> drops core. This is because tar seems to assume, that when s flag is
> used, there are more arguments to come, and ends up calling strlen(0)
> (see patch below).
> ----------------------------------------------

I noticed it always complains unless you specify -C last.

== Chris Layne ======================================== Nervosa Computing ==
== coredump@nervosa.com ================ http://www.nervosa.com/~coredump ==


From owner-freebsd-current  Wed Mar 20 12:19:14 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id MAA00903
          for current-outgoing; Wed, 20 Mar 1996 12:19:14 -0800 (PST)
Received: from ki.net (root@ki.net [142.77.249.8])
          by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id MAA00595
          for <current@freebsd.org>; Wed, 20 Mar 1996 12:15:49 -0800 (PST)
Received: (from scrappy@localhost) by ki.net (8.7.4/8.7.4) id PAA05142; Wed, 20 Mar 1996 15:15:23 -0500 (EST)
Date: Wed, 20 Mar 1996 15:15:21 -0500 (EST)
From: "Marc G. Fournier" <scrappy@ki.net>
To: current@freebsd.org
Subject: DEVFS PATCH: New, more complete patch
Message-ID: <Pine.BSF.3.91.960320150709.3864D-100000@ki.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-current@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk


Hi...

	After making changes to a couple of things pointed out to me
by Julian and by Joerg, here is a single patch against the current
source tree (as of 6am this morning).

	to apply, cd to /usr/src/sys and run patch -p < patchfile

	What is changed:

		uses devfs_add_devswf instead of devfs_add_devsw
		cleaned up #ifdef indentations (was informed it is not
			appropriate in a kernel source

	There is a patch for sys/syslog.h as well, changing the path for
_PATH_LOG to be /var/run/log instead of /dev/log, since its a socket, not
a device (suggested by Joerg), so don't forget to recompile syslogd before
rebooting with devfs mounted as /dev.

	Right now, my machine is running using devfs mounted onto /dev
instead of the "normal /dev", and I've yet to hit a command that is missing
a device (syslogd, ps, pstat, vmstat all seem to work fine).  

	Here is what is currently supported by devfs, according to what
it has probed on my machine:

bpf0		ptyp9		rfd0		ttyp5		ttypt
bpf1		ptypa		rfd0.1440	ttyp6		ttypu
bpf2		ptypb		rsd0		ttyp7		ttypv
bpf3		ptypc		rsd0a		ttyp8		ttyv0
console		ptypd		rsd0b		ttyp9		ttyv1
drum		ptype		rsd0c		ttypa		ttyv2
fd		ptypf		rsd0e		ttypb		ttyv3
fd0		ptypg		rsd0f		ttypc		ttyv4
fd0.1440	ptyph		sd0		ttypd		ttyv5
io		ptypi		sd0a		ttype		ttyv6
klog		ptypj		sd0b		ttypf		ttyv7
kmem		ptypk		sd0c		ttypg		ttyv8
lkm		ptypl		sd0e		ttyph		ttyv9
mem		ptypm		sd0f		ttypi		ttyva
null		ptypn		spkr		ttypj		ttyvb
ptyp0		ptypo		stderr		ttypk		ttyvc
ptyp1		ptypp		stdin		ttypl		ttyvd
ptyp2		ptypq		stdout		ttypm		ttyve
ptyp3		ptypr		tty		ttypn		ttyvf
ptyp4		ptyps		ttyp0		ttypo		urandom
ptyp5		ptypt		ttyp1		ttypp		zero
ptyp6		ptypu		ttyp2		ttypq
ptyp7		ptypv		ttyp3		ttypr
ptyp8		random		ttyp4		ttyps
		

----[ cd /usr/src/sys; patch -p < <this patch> ]----

*** /usr/src.orig/sys/i386/isa/pcvt/pcvt_drv.c	Mon Jan 15 23:00:09 1996
--- i386/isa/pcvt/pcvt_drv.c	Wed Mar 20 13:28:39 1996
***************
*** 82,87 ****
--- 82,94 ----
  #define EXTERN			/* allocate mem */
  
  #include "pcvt_hdr.h"		/* global include */
+ #ifdef DEVFS
+ #include <sys/devfsext.h>
+ #if !defined(MAXCONS)
+ #define MAXCONS 16
+ #endif
+ static void *pcvt_devfs_token[MAXCONS];
+ #endif /*DEVFS*/
  
  extern int getchar __P((void));
  
***************
*** 101,108 ****
  
  #if PCVT_FREEBSD > 205
  static struct kern_devconf kdc_vt[];
! static inline void
! vt_registerdev(struct isa_device *id, const char *name);
  static char vt_description[];
  #define VT_DESCR_LEN 40
  #endif /* PCVT_FREEBSD > 205 */
--- 108,114 ----
  
  #if PCVT_FREEBSD > 205
  static struct kern_devconf kdc_vt[];
! static inline void vt_registerdev(struct isa_device *id, const char *name);
  static char vt_description[];
  #define VT_DESCR_LEN 40
  #endif /* PCVT_FREEBSD > 205 */
***************
*** 162,167 ****
--- 168,176 ----
  {
  #endif /* PCVT_NETBSD > 9 */
  
+ #ifdef DEVFS
+ 	int vt;
+ #endif /*DEVFS*/
  	int i;
  
  	vt_coldmalloc();		/* allocate memory for screens */
***************
*** 332,337 ****
--- 341,354 ----
  
  	cdevsw_add(&dev, &pcdevsw, NULL);
  	}
+ 
+ #ifdef DEVFS	
+ 	for(vt = 0; vt < MAXCONS; vt++) {
+           pcvt_devfs_token[vt] = 
+ 		devfs_add_devswf(&pcdevsw, vt,
+                                  DV_CHR, 0, 0, 0600, "ttyv%n", vt );
+ 	}
+ #endif DEVFS
  #endif /* PCVT_FREEBSD > 205 */
  
  #if PCVT_NETBSD > 9
*** /usr/src.orig/sys/kern/subr_log.c	Thu Dec 14 04:57:44 1995
--- kern/subr_log.c	Wed Mar 20 13:34:12 1996
***************
*** 254,261 ****
  		cdevsw_add(&dev,&log_cdevsw,NULL);
  		log_devsw_installed = 1;
  #ifdef DEVFS
! 		log_devfs_token = devfs_add_devsw(
! 			"/", "log", &log_cdevsw, 0, DV_CHR, 0, 0, 0600);
  #endif
      	}
  }
--- 254,262 ----
  		cdevsw_add(&dev,&log_cdevsw,NULL);
  		log_devsw_installed = 1;
  #ifdef DEVFS
! 		log_devfs_token = 
! 			devfs_add_devswf(&log_cdevsw, 0, DV_CHR, 0, 0, 
! 				 	 0600, "klog");
  #endif
      	}
  }
*** /usr/src.orig/sys/sys/syslog.h	Sun Aug 21 00:42:00 1994
--- sys/sys/syslog.h	Wed Mar 20 13:14:04 1996
***************
*** 37,43 ****
  #ifndef _SYS_SYSLOG_H_
  #define _SYS_SYSLOG_H_
  
! #define	_PATH_LOG	"/dev/log"
  
  /*
   * priorities/facilities are encoded into a single 32-bit quantity, where the
--- 37,43 ----
  #ifndef _SYS_SYSLOG_H_
  #define _SYS_SYSLOG_H_
  
! #define	_PATH_LOG	"/var/run/log"
  
  /*
   * priorities/facilities are encoded into a single 32-bit quantity, where the
*** /usr/src.orig/sys/vm/vm_swap.c	Sun Mar  3 16:46:20 1996
--- vm/vm_swap.c	Wed Mar 20 13:38:49 1996
***************
*** 52,57 ****
--- 52,61 ----
  #include <vm/swap_pager.h>
  
  #include <miscfs/specfs/specdev.h>
+ #ifdef DEVFS
+ #include <sys/devfsext.h>
+ static void *drum_devfs_token;
+ #endif /*DEVFS*/
  
  static void swstrategy __P((struct buf *));
  
***************
*** 297,302 ****
--- 301,310 ----
  		dev = makedev(BDEV_MAJOR,0);
  		bdevsw_add(&dev,&sw_bdevsw,NULL);
  		sw_devsw_installed = 1;
+ #ifdef DEVFS
+           drum_devfs_token =
+                 devfs_add_devswf(&sw_cdevsw, 0, DV_CHR, 0, 0, 0640, "drum" );
+ #endif /*DEVFS*/ 
      	}
  }
  
Marc G. Fournier | POP Mail  Telnet Acct  DNS Hosting
System           |  WWW Services   Database Services  | Knowledge, 
  Administrator  |                                    | Information and
 scrappy@ki.net  |      WWW: http://www.ki.net        | Communications, Inc


From owner-freebsd-current  Wed Mar 20 12:47:56 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id MAA02744
          for current-outgoing; Wed, 20 Mar 1996 12:47:56 -0800 (PST)
Received: from halloran-eldar.lcs.mit.edu (halloran-eldar.lcs.mit.edu [18.26.0.159])
          by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id MAA02739
          for <current@freebsd.org>; Wed, 20 Mar 1996 12:47:53 -0800 (PST)
Received: by halloran-eldar.lcs.mit.edu; (5.65/1.1.8.2/19Aug95-0530PM)
	id AA11200; Wed, 20 Mar 1996 15:47:32 -0500
Date: Wed, 20 Mar 1996 15:47:32 -0500
From: "Garrett A. Wollman" <wollman@lcs.mit.edu>
Message-Id: <9603202047.AA11200@halloran-eldar.lcs.mit.edu>
To: KATO Takenori <kato@eclogite.eps.nagoya-u.ac.jp>
Cc: current@freebsd.org
Subject: comment for CPU_686 in cputypes.h
In-Reply-To: <199603201952.EAA01318@marble.eps.nagoya-u.ac.jp>
References: <199603201952.EAA01318@marble.eps.nagoya-u.ac.jp>
Sender: owner-current@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

<<On Thu, 21 Mar 1996 04:52:33 +0900, KATO Takenori <kato@eclogite.eps.nagoya-u.ac.jp> said:

> In /sys/i386/include/cputypes.h, comment for CPU_586 is:
> 	/* P.....m (I hate lawyers; It's TM) */

> but that for CPU_686 is:

> 	/* Pentium Pro */

> It is not consistent with the comment for CPU_586.


> Is using TM in source code illegal?  I hope the answer, NO.

No, not at all.  Unless you are competing against the trademark owner,
you don't even have to give recognition to the mark (although their
lawyers are certainly entitled to ask you to do so).

-GAWollman

--
Garrett A. Wollman   | Shashish is simple, it's discreet, it's brief. ... 
wollman@lcs.mit.edu  | Shashish is the bonding of hearts in spite of distance.
Opinions not those of| It is a bond more powerful than absence.  We like people
MIT, LCS, ANA, or NSA| who like Shashish.  - Claude McKenzie + Florent Vollant

From owner-freebsd-current  Wed Mar 20 13:32:00 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id NAA05633
          for current-outgoing; Wed, 20 Mar 1996 13:32:00 -0800 (PST)
Received: from ki.net (root@ki.net [142.77.249.8])
          by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id NAA05551
          for <current@freebsd.org>; Wed, 20 Mar 1996 13:30:16 -0800 (PST)
Received: (from scrappy@localhost) by ki.net (8.7.4/8.7.4) id QAA07137; Wed, 20 Mar 1996 16:29:11 -0500 (EST)
Date: Wed, 20 Mar 1996 16:29:10 -0500 (EST)
From: "Marc G. Fournier" <scrappy@ki.net>
To: JULIAN Elischer <julian@ref.tfs.com>, current@freebsd.org
Subject: PATCH: small, syntax changes for devfs
Message-ID: <Pine.BSF.3.91.960320162140.3864F-100000@ki.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-current@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk


Hi again...

	The following patch makes small changes to the DEVFS code in:

		- scsi/sd.c
		- kern/subr_diskslice.c
		- kern/tty_snoop.c
		- kern/tty_tty.c
		- kern/kern_lkm.c

	The main change is to use devfs_add_devswf instead of devfs_add_devsw,
but there are several #ifdef's added around devfs specific defines that
exist in alot of the devfs code, but were missing in these files.

	Question...is it safe to put "printf" statements inside of the
kernel in arbitrary places?  I'm trying to figure out why set_ds_labeldevs()
isn't creating slice devices in /devfs, and figure that putting in a few
extra printf's might help figure it out, but just wondering if this would
break anything. :)



*** /usr/src.orig/sys/kern/kern_lkm.c	Fri Dec 15 22:53:40 1995
--- kern/kern_lkm.c	Wed Mar 20 16:10:27 1996
***************
*** 906,912 ****
--- 906,914 ----
  }
  
  static lkm_devsw_installed = 0;
+ #ifdef DEVFS
  static void	*lkmc_devfs_token;
+ #endif
  
  static void 	lkm_drvinit(void *unused)
  {
***************
*** 917,924 ****
  		cdevsw_add(&dev,&lkmc_cdevsw, NULL);
  		lkm_devsw_installed = 1;
  #ifdef DEVFS
! 		lkmc_devfs_token = devfs_add_devsw( "/", "lkm", &lkmc_cdevsw, 0,
! 					DV_CHR, 0, 0, 0660);
  #endif
      	}
  }
--- 919,927 ----
  		cdevsw_add(&dev,&lkmc_cdevsw, NULL);
  		lkm_devsw_installed = 1;
  #ifdef DEVFS
! 		lkmc_devfs_token = 
! 			devfs_add_devswf(&lkmc_cdevsw, 0, DV_CHR, 0, 0, 
! 					 0660, "lkm");
  #endif
      	}
  }
*** /usr/src.orig/sys/scsi/sd.c	Sun Mar 10 04:49:21 1996
--- scsi/sd.c	Wed Mar 20 15:33:56 1996
***************
*** 195,201 ****
  	struct disk_parms *dp;
  #ifdef DEVFS
  	int	mynor;
- 	char	name[32];
  #endif
  
  	struct scsi_data *sd = sc_link->sd;
--- 195,200 ----
***************
*** 239,249 ****
  
  #ifdef DEVFS
  	mynor = dkmakeminor(unit, WHOLE_DISK_SLICE, RAW_PART);
! 	sprintf(name, "rsd%d", unit);
! 	sd->b_devfs_token = devfs_add_devsw("/", name + 1, &sd_bdevsw, mynor,
! 					    DV_BLK, 0, 0, 0640);
! 	sd->c_devfs_token = devfs_add_devsw("/", name, &sd_cdevsw, mynor,
! 					    DV_CHR, 0, 0, 0640);
  #endif
  
  	return 0;
--- 238,247 ----
  
  #ifdef DEVFS
  	mynor = dkmakeminor(unit, WHOLE_DISK_SLICE, RAW_PART);
! 	sd->b_devfs_token = devfs_add_devswf(&sd_bdevsw, mynor,
! 					    DV_BLK, 0, 0, 0640, "sd%d", unit);
! 	sd->c_devfs_token = devfs_add_devswf(&sd_cdevsw, mynor,
! 					    DV_CHR, 0, 0, 0640, "rsd%d", unit);
  #endif
  
  	return 0;
*** /usr/src.orig/sys/kern/subr_diskslice.c	Sun Jan 28 04:44:59 1996
--- kern/subr_diskslice.c	Wed Mar 20 16:04:27 1996
***************
*** 660,671 ****
  #ifdef DEVFS
  	if (slice >= BASE_SLICE && sp->ds_bdev == NULL && sp->ds_size != 0) {
  		mynor = minor(dkmodpart(dev, RAW_PART));
! 		sprintf(devname, "r%s",
! 			dsname(dname, unit, slice, RAW_PART, partname));
! 		sp->ds_bdev = devfs_add_devsw("/", devname + 1, bdevsw,
! 					      mynor, DV_BLK, 0, 0, 0640);
! 		sp->ds_cdev = devfs_add_devsw("/", devname, cdevsw,
! 					      mynor, DV_CHR, 0, 0, 0640);
  	}
  #endif
  	if (sp->ds_label == NULL) {
--- 660,673 ----
  #ifdef DEVFS
  	if (slice >= BASE_SLICE && sp->ds_bdev == NULL && sp->ds_size != 0) {
  		mynor = minor(dkmodpart(dev, RAW_PART));
! 		sp->ds_bdev = 
! 			devfs_add_devswf(bdevsw, mynor, DV_BLK, 0, 0, 0640,
! 					 dsname(dname, unit, slice, RAW_PART,
! 					        partname));
! 		sp->ds_cdev = 
! 			devfs_add_devswf(cdevsw, mynor, DV_CHR, 0, 0, 0640, 
! 					 "r%s", dsname(dname, unit, slice, 
! 						       RAW_PART, partname));
  	}
  #endif
  	if (sp->ds_label == NULL) {
***************
*** 970,980 ****
  		} else {
  			mynor = minor(dkmodpart(dev, part));
  			sp->ds_bdevs[part] =
! 				devfs_add_devsw("/", devname+1, ssp->dss_bdevsw,
! 						mynor, DV_BLK, 0, 0, 0640);
  			sp->ds_cdevs[part] =
! 				devfs_add_devsw("/", devname, ssp->dss_cdevsw,
! 						mynor, DV_CHR, 0, 0, 0640);
  		}
  	}
  }
--- 972,982 ----
  		} else {
  			mynor = minor(dkmodpart(dev, part));
  			sp->ds_bdevs[part] =
! 				devfs_add_devswf(ssp->dss_bdevsw, mynor, DV_BLK,
! 					 	 0, 0, 0640, devname+1);
  			sp->ds_cdevs[part] =
! 				devfs_add_devswf(ssp->dss_cdevsw, mynor, DV_CHR,
! 						 0, 0, 0640, devname);
  		}
  	}
  }
*** /usr/src.orig/sys/kern/tty_snoop.c	Thu Dec 14 04:57:48 1995
--- kern/tty_snoop.c	Wed Mar 20 16:09:35 1996
***************
*** 509,523 ****
  	return 0;
  }
  
  static	void	*snp_devfs_token[NSNP];
  static snp_devsw_installed = 0;
  
  static void
  snp_drvinit(void *unused)
  {
  	dev_t dev;
! 	char	name[32];
  	int	i;
  
  	if( ! snp_devsw_installed ) {
  		dev = makedev(CDEV_MAJOR, 0);
--- 509,526 ----
  	return 0;
  }
  
+ #ifdef DEVFS
  static	void	*snp_devfs_token[NSNP];
+ #endif
  static snp_devsw_installed = 0;
  
  static void
  snp_drvinit(void *unused)
  {
  	dev_t dev;
! #ifdef DEVFS
  	int	i;
+ #endif
  
  	if( ! snp_devsw_installed ) {
  		dev = makedev(CDEV_MAJOR, 0);
***************
*** 525,534 ****
  		snp_devsw_installed = 1;
  #ifdef DEVFS
  		for ( i = 0 ; i < NSNP ; i++) {
- 			sprintf(name,"snp%d",i);
  			snp_devfs_token[i] =
! 				devfs_add_devsw( "/", name, &snp_cdevsw, i,
! 							DV_CHR, 0, 0, 0600);
  		}
  #endif
      	}
--- 528,536 ----
  		snp_devsw_installed = 1;
  #ifdef DEVFS
  		for ( i = 0 ; i < NSNP ; i++) {
  			snp_devfs_token[i] =
! 				devfs_add_devswf(&snp_cdevsw, i, DV_CHR, 0, 0, 
! 						0600, "snp%d", i);
  		}
  #endif
      	}
*** /usr/src.orig/sys/kern/tty_tty.c	Fri Dec 22 10:57:42 1995
--- kern/tty_tty.c	Wed Mar 20 16:09:41 1996
***************
*** 173,179 ****
--- 173,181 ----
  }
  
  static ctty_devsw_installed = 0;
+ #ifdef DEVFS
  static 	void	*ctty_devfs_token;
+ #endif
  
  static void
  ctty_drvinit(void *unused)
***************
*** 185,192 ****
  		cdevsw_add(&dev,&ctty_cdevsw,NULL);
  		ctty_devsw_installed = 1;
  #ifdef DEVFS
! 		ctty_devfs_token = devfs_add_devsw( "/", "tty",
! 				&ctty_cdevsw, 0, DV_CHR, 0, 0, 0666);
  #endif
      	}
  }
--- 187,195 ----
  		cdevsw_add(&dev,&ctty_cdevsw,NULL);
  		ctty_devsw_installed = 1;
  #ifdef DEVFS
! 		ctty_devfs_token = 
! 			devfs_add_devswf(&ctty_cdevsw, 0, DV_CHR, 0, 0, 
! 					0666, "tty");
  #endif
      	}
  }


Marc G. Fournier | POP Mail  Telnet Acct  DNS Hosting
System           |  WWW Services   Database Services  | Knowledge, 
  Administrator  |                                    | Information and
 scrappy@ki.net  |      WWW: http://www.ki.net        | Communications, Inc


From owner-freebsd-current  Wed Mar 20 14:23:40 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id OAA09773
          for current-outgoing; Wed, 20 Mar 1996 14:23:40 -0800 (PST)
Received: from ki.net (root@ki.net [142.77.249.8])
          by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id OAA09597
          for <current@freebsd.org>; Wed, 20 Mar 1996 14:20:43 -0800 (PST)
Received: (from scrappy@localhost) by ki.net (8.7.4/8.7.4) id RAA08072; Wed, 20 Mar 1996 17:17:20 -0500 (EST)
Date: Wed, 20 Mar 1996 17:17:18 -0500 (EST)
From: "Marc G. Fournier" <scrappy@ki.net>
To: JULIAN Elischer <julian@ref.tfs.com>
cc: current@freebsd.org
Subject: Re: PATCH: small, syntax changes for devfs
In-Reply-To: <199603202159.NAA17420@ref.tfs.com>
Message-ID: <Pine.BSF.3.91.960320171313.3864I-100000@ki.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-current@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

On Wed, 20 Mar 1996, JULIAN Elischer wrote:

> you can put printf's almost anywhere.
> set_ds_labeldevs doesn't make nodes?
> I seem to have all the nodes on my systems...
>
	For some reason, I'm getting all my /dev/sd0[abcef] devices, but
none of the /dev/sd0s1[abcef] devices.  Looking at the code, I can't find
any reason for it not to make the devices, which is why I'm going to shove
in a few printf's and see what code is not being executed.

> >   	if (slice >= BASE_SLICE && sp->ds_bdev == NULL && sp->ds_size != 0) {
> >   		mynor = minor(dkmodpart(dev, RAW_PART));
> > ! 		sp->ds_bdev = 
> > ! 			devfs_add_devswf(bdevsw, mynor, DV_BLK, 0, 0, 0640,
> > ! 					 dsname(dname, unit, slice, RAW_PART,
> > ! 					        partname));
> 
> better to use %s than just the string..
> (what if we want a device with a % in it ? :)
>
	Ah...so always have a "format string" in devfs_add_devswf then?
regardless of whether it is truely needed or not? :)

Marc G. Fournier | POP Mail  Telnet Acct  DNS Hosting
System           |  WWW Services   Database Services  | Knowledge, 
  Administrator  |                                    | Information and
 scrappy@ki.net  |      WWW: http://www.ki.net        | Communications, Inc


From owner-freebsd-current  Wed Mar 20 14:44:56 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id OAA11478
          for current-outgoing; Wed, 20 Mar 1996 14:44:56 -0800 (PST)
Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211])
          by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id OAA11473
          for <current@FreeBSD.ORG>; Wed, 20 Mar 1996 14:44:53 -0800 (PST)
Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id PAA27947; Wed, 20 Mar 1996 15:33:17 -0700
From: Terry Lambert <terry@lambert.org>
Message-Id: <199603202233.PAA27947@phaeton.artisoft.com>
Subject: Re: DEVFS vs "regular /dev"
To: julian@ref.tfs.com (JULIAN Elischer)
Date: Wed, 20 Mar 1996 15:33:17 -0700 (MST)
Cc: terry@lambert.org, scrappy@ki.net, current@FreeBSD.ORG
In-Reply-To: <199603202100.NAA17319@ref.tfs.com> from "JULIAN Elischer" at Mar 20, 96 01:00: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

> all good but one question.....
> 
> > 
> > > 	Just curious, but what is the advantage (and disadvantage, if any?)
> > > of using devfs vs "regular /dev"?  My first thought would be that its
> > > memory based instead of file system based, giving better performance, but
> > > that's just a guess.
> > 
> [.... tons of reasons ]
> 
> > 
> > This assumes that the file system abstractions currently in place
> > change as well, since the /dev FS can't be mounted *after* the / FS
> > has been mounted as an inferior FS --
> why not?
> you don't need a mounted /dev to mount root.
> that's done specially.

So you don't need a mounted root to have a mounted /dev, of course!

This makes it possible to remount root r/w without unmounting the
devfs (and so still needing /dev).

> > the /dev has to be there as
> > an overlay mount (translucent FS), and that means FS changes to allow
> > translucence and to divorce volume mappings from the need for a mount
> > point (basically, a shadow / and /dev on which the devfs /dev is mounted
> > and the real / is mounted over top of the shadow /).
> 
> I think that's not needed

Root remount, again.  If you divorce the mappings, you can mount root
over and over despite devfs being mounted by default.

The other alternative is to put the device files in a POSIX name space
escape.  I felt this would be too "un-UNIX-like"; can you imagine having
no /dev directory and using "//dev/..." to access devices?  That's
pretty much the alternative.

It would mean you couldn't have a machine named "dev" if you used POSIX
escapes for a network namespace (unless you shoved it down to "//net/dev",
of course...).

If you want to get more specific, it also lets us build a disk image
in the kernel data segment for "sh" and/or "init" to get up with no
disk and no NFS capability during a port.

It would be nice to not have to have working drivers to run.  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 Mar 20 14:49:58 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id OAA11837
          for current-outgoing; Wed, 20 Mar 1996 14:49:58 -0800 (PST)
Received: from dtr.com ([204.119.17.55])
          by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id OAA11788
          for <current@freefall.freebsd.org>; Wed, 20 Mar 1996 14:48:31 -0800 (PST)
Received: (from bmk@localhost) by dtr.com (8.6.12/8.6.9) id OAA02668; Wed, 20 Mar 1996 14:41:45 -0800
Message-Id: <199603202241.OAA02668@dtr.com>
Subject: Re: perl4
To: alk@Think.COM (Tony Kimball)
Date: Wed, 20 Mar 1996 14:41:45 -0800 (PST)
Cc: gclarkii@main.gbdata.com, current@freefall.freebsd.org
In-Reply-To: <199603201434.IAA19341@compound> from "Tony Kimball" at Mar 20, 96 08:34:00 am
From: "Brant M. Katkansky" <bmk@transport.com>
Reply-To: bmk@transport.com
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 absolutely agree that we need perl (or more accurately that "FreeBSD
> needs perl").  I claim that it does not belong in the base OS, because
> it is not tightly coupled, and because most perl users will use the
> most recent version, and *not* the version shipped, so it is a legacy,
> baggage.

> Making the base OS small is a Good Thing.  Making it independent of
> the choice of perl version level is a Good Thing.  The point is to
> give users the freedom to choose, rather than forcing them to remove
> perl by hand in order to eliminate an abhorrent redundancy.  Would you
> require that XF86 be bundled as well?  Mi genoito!

I'd have to agree in principle.  Perl doesn't belong in the base OS -
it's too much of a moving target.  However, since Perl *is* part of 
FreeBSD, and certain aspects of the base OS depend on Perl, we can hardly 
go back now.  I'm not even going to attempt to argue this issue, because
it isn't going to happen.

I use perl5 for all of the perl scripts that I write, but keep perl4
on the system so that legacy scripts (esp. those shipped with FreeBSD)
will still run.

The way I see it, we have several options:

* Leave things the way they are, and keep perl4 as the standard perl.
Perl5 can be installed in /usr/local as a package.

* Ship perl5 with the base OS.  Not good, it adds bloat to the base
release and may break a lot of existing scripts.

* Remove perl from the base OS and let this be a local policy matter.
Realistically, this isn't going to happen.

* Ship perl4 with the base OS, and provide an option in the install to
replace perl4 with perl5.  Still could have the potential of busting
some legacy scripts, but as long as the installer is informed of this, I
see no problems with this - as long as replacements for the
FreeBSD-supplied scripts are supplied.  Could be a real maintenance
nightmare.

As long as we have tools in the base release that depend on perl4, I
would have to go with the first or last option.


From owner-freebsd-current  Wed Mar 20 16:10:15 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id QAA15818
          for current-outgoing; Wed, 20 Mar 1996 16:10:15 -0800 (PST)
Received: from Root.COM (implode.Root.COM [198.145.90.17])
          by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id QAA15813
          for <current@freebsd.org>; Wed, 20 Mar 1996 16:10:13 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by Root.COM (8.6.12/8.6.5) with SMTP id QAA03902; Wed, 20 Mar 1996 16:10:05 -0800
Message-Id: <199603210010.QAA03902@Root.COM>
X-Authentication-Warning: implode.Root.COM: Host localhost didn't use HELO protocol
To: Terry Lambert <terry@lambert.org>
cc: julian@ref.tfs.com (JULIAN Elischer), scrappy@ki.net, current@freebsd.org
Subject: Re: DEVFS vs "regular /dev" 
In-reply-to: Your message of "Wed, 20 Mar 1996 15:33:17 MST."
             <199603202233.PAA27947@phaeton.artisoft.com> 
From: David Greenman <davidg@Root.COM>
Reply-To: davidg@Root.COM
Date: Wed, 20 Mar 1996 16:10:05 -0800
Sender: owner-current@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

>> > This assumes that the file system abstractions currently in place
>> > change as well, since the /dev FS can't be mounted *after* the / FS
>> > has been mounted as an inferior FS --
>> why not?
>> you don't need a mounted /dev to mount root.
>> that's done specially.
>
>So you don't need a mounted root to have a mounted /dev, of course!

   That's silly. The root filesystem is mounted long before /dev would be, and
as Julian points out, /dev is not required for this (in the same way that /dev
is not required when it is disk resident - you'd have a chicken and egg
problem as /dev *is* on the root filesystem).

>This makes it possible to remount root r/w without unmounting the
>devfs (and so still needing /dev).

   Remounting r/w is not precluded by having /dev mounted (or any other
filesystem). Remonting r/w involves changing mount flags, nothing more.

-DG

David Greenman
Core-team/Principal Architect, The FreeBSD Project

From owner-freebsd-current  Wed Mar 20 16:24:35 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id QAA17108
          for current-outgoing; Wed, 20 Mar 1996 16:24:35 -0800 (PST)
Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211])
          by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id QAA17096
          for <current@freebsd.org>; Wed, 20 Mar 1996 16:24:28 -0800 (PST)
Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id RAA28244; Wed, 20 Mar 1996 17:14:31 -0700
From: Terry Lambert <terry@lambert.org>
Message-Id: <199603210014.RAA28244@phaeton.artisoft.com>
Subject: Re: DEVFS vs "regular /dev"
To: davidg@Root.COM
Date: Wed, 20 Mar 1996 17:14:31 -0700 (MST)
Cc: terry@lambert.org, julian@ref.tfs.com, scrappy@ki.net, current@freebsd.org
In-Reply-To: <199603210010.QAA03902@Root.COM> from "David Greenman" at Mar 20, 96 04:10:05 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

> >So you don't need a mounted root to have a mounted /dev, of course!
> 
>    That's silly. The root filesystem is mounted long before /dev would be, and
> as Julian points out, /dev is not required for this (in the same way that /dev
> is not required when it is disk resident - you'd have a chicken and egg
> problem as /dev *is* on the root filesystem).

Well, the alternative is a (possible) mis-recognition of root ("Can't
mount root"), which I think it would fix as well (making the mount
independent of its location in the hierarchy would also fix that one).

> >This makes it possible to remount root r/w without unmounting the
> >devfs (and so still needing /dev).
> 
>    Remounting r/w is not precluded by having /dev mounted (or any other
> filesystem). Remonting r/w involves changing mount flags, nothing more.

Well, then it isn't a real issue for that; never mind.  I was going
down my old "objections to devfs" list and the workarounds for each
one of them.

The real reason I want it, is, as I've said before, nomadic computing.

If a resource is available, it doesn't matter which one it is if
you can make them identical.  I'd still like to address resources
by resource name instead of machine name.

I'll give my standard example: a portable computer with a 2Mb/S IR
interface that wants to access locally available identical resources
from the office server in two offices.

For instance, floating licenses for products.


					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 Mar 20 20:14:38 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id UAA05058
          for current-outgoing; Wed, 20 Mar 1996 20:14:38 -0800 (PST)
Received: from rover.village.org (rover.village.org [204.144.255.49])
          by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id UAA05048
          for <current@FreeBSD.org>; Wed, 20 Mar 1996 20:14:18 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by rover.village.org (8.6.11/8.6.6) with SMTP id VAA06465; Wed, 20 Mar 1996 21:12:53 -0700
Message-Id: <199603210412.VAA06465@rover.village.org>
To: "Jordan K. Hubbard" <jkh@time.cdrom.com>
Subject: Re: AMD doesn't like SNAP! (panic: unwire: page not in pmap) 
Cc: "Rodney W. Grimes" <rgrimes@gndrsh.aac.dev.com>, current@FreeBSD.org
In-reply-to: Your message of Sat, 09 Mar 1996 21:04:27 PST
Date: Wed, 20 Mar 1996 21:12:52 -0700
From: Warner Losh <imp@village.org>
Sender: owner-current@FreeBSD.org
X-Loop: FreeBSD.org
Precedence: bulk

: Sigh..  A Rod's Tips page at http://www.freebsd.org/handbook/hw.html
: SURE WOULD BE NICE, yup!  Save lots of people lots of trouble..  :-)

An idea occurred to me while eating sushi and driking coffee with a
friend (you know who you are) the other night.  Why not take the
archives, grep out all of Rod's mail, organize it into a tips page,
put his name on it and then let him correct all the mistake we've made
:-)

Seriously, if someone were to go back through the FreeBSD archives and
concentrate all of the advice Rod has given out over the years on
mother boards and the like, I think we'd have a nice addition to the
hardware part of the handbook.

Jordan, are the archives back on line?

Warner

From owner-freebsd-current  Wed Mar 20 20:17:05 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id UAA05281
          for current-outgoing; Wed, 20 Mar 1996 20:17:05 -0800 (PST)
Received: from rover.village.org (rover.village.org [204.144.255.49])
          by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id UAA05274
          for <freebsd-current@FreeBSD.ORG>; Wed, 20 Mar 1996 20:16:59 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by rover.village.org (8.6.11/8.6.6) with SMTP id VAA06476; Wed, 20 Mar 1996 21:16:23 -0700
Message-Id: <199603210416.VAA06476@rover.village.org>
To: "Jordan K. Hubbard" <jkh@time.cdrom.com>
Subject: Re: New kernel 
Cc: freebsd-current@FreeBSD.ORG
In-reply-to: Your message of Sun, 10 Mar 1996 18:28:23 PST
Date: Wed, 20 Mar 1996 21:16:23 -0700
From: Warner Losh <imp@village.org>
Sender: owner-current@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

: How about PASSIVE_AGGRESSIVE?  The kernel doesn't actually panic, but
: corrupts your files occasionally when you're away on vacation. :-)

Nah, that's been in there since 2.0R if you are silly enough, like me,
to run with flakey disks.. :-)

Warner


From owner-freebsd-current  Wed Mar 20 20:21:19 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id UAA05573
          for current-outgoing; Wed, 20 Mar 1996 20:21:19 -0800 (PST)
Received: from rover.village.org (rover.village.org [204.144.255.49])
          by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id UAA05557
          Wed, 20 Mar 1996 20:20:58 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by rover.village.org (8.6.11/8.6.6) with SMTP id VAA06487; Wed, 20 Mar 1996 21:20:43 -0700
Message-Id: <199603210420.VAA06487@rover.village.org>
To: sos@FreeBSD.org
Subject: Re: Native & Linux ELF support finally there... 
Cc: current@FreeBSD.org (FreeBSD current)
In-reply-to: Your message of Mon, 11 Mar 1996 08:16:33 +0100
Date: Wed, 20 Mar 1996 21:20:43 -0700
From: Warner Losh <imp@village.org>
Sender: owner-current@FreeBSD.org
X-Loop: FreeBSD.org
Precedence: bulk

: After a hectic week, Peter Wemm and I are proud to announce that
: FreeBSD-current now has ELF support. This means that we are now
: able to run native FreeBSD ELF binaries (generated with John
: Polstras Elfkit-1.0.1) and Linux ELF binaries, and yes Linux
: QUAKE finally works, at least as far as Peter & I has tried it
: (Hey I dont have time to play)

A while back someone asked me if they could do the following sick
thing:

Compile FreeBSD kernel, put it on a linux box, run lilo pointed at
this kernel, and reboot and have their "Linux" box suddenly be a
"FreeBSD" box running all their Linux stuff.

Is that now possible?  Or are there too many kernel things that would
preclude this (eg no ps, netstat, etc)?

Why do this?  Well the machine in question was a network hub that was
too overloaded with Linux and he wanted to run FreeBSD on it.  Yet he
couldn't bring it down long enough to install all of FreeBSD....

Warner

P.S.  This is my sick and twisted way of saying "Cool!"

From owner-freebsd-current  Wed Mar 20 20:31:07 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id UAA08155
          for current-outgoing; Wed, 20 Mar 1996 20:31:07 -0800 (PST)
Received: from ambrisko.roble.com (ambrisko@netcom5.netcom.com [192.100.81.113])
          by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id UAA08098
          for <freebsd-current@freebsd.org>; Wed, 20 Mar 1996 20:30:56 -0800 (PST)
Received: from freebsd.ambrisko.com (freebsd [1.1.1.1]) by  ambrisko.roble.com (8.6.12/8.6.9) with ESMTP id UAA24134 for <freebsd-current@freebsd.org>; Wed, 20 Mar 1996 20:25:56 -0800
Received: (from ambrisko@localhost) by freebsd.ambrisko.com (8.6.12/8.6.9) id UAA13939 for freebsd-current@freebsd.org; Wed, 20 Mar 1996 20:24:40 -0800
Message-Id: <199603210424.UAA13939@freebsd.ambrisko.com>
Subject: Dual biosboot patches
To: freebsd-current@freebsd.org
Date: Wed, 20 Mar 1996 20:24:39 -0800 (PST)
From: "Doug Ambrisko" <ambrisko@ambrisko.roble.com>
X-Mailer: ELM [version 2.4 PL25 ME8b]
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

Here are the patches to support the bios boot prompt messages on both
the serial and graphics console at the same time.  Input and output is 
echoed to both devices.  At this time no probe is done for com1 which could
be a problem.  This code should work okay with a mouse on COM1 since it 
filters out any non-printable ascii characters. 

Doug A.

*** Makefile	Fri Mar  8 01:43:54 1996
--- makefile	Sun Mar 17 19:27:24 1996
***************
*** 3,10 ****
  
  PROG=	boot
  # Order is very important on the SRCS line for this prog
! SRCS=	start.S table.c boot2.S boot.c asm.S bios.S serial.S
! SRCS+=  probe_keyboard.c io.c disk.c sys.c
  
  BINDIR=		/usr/mdec
  BINMODE=	444
--- 3,10 ----
  
  PROG=	boot
  # Order is very important on the SRCS line for this prog
! SRCS=	start.S table.c boot2.S boot.c asm.S bios.S serial.S
! SRCS+=  probe_keyboard.c io.c disk.c sys.c
  
  BINDIR=		/usr/mdec
  BINMODE=	444
***************
*** 15,20 ****
--- 15,21 ----
  
  # Probe the keyboard and use the serial console if the keyboard isn't found.
  #CFLAGS+=	-DPROBE_KEYBOARD
+ CFLAGS+=	-DDUAL_PROMPT
  
  # Force use of the serial console (after probing the keyboard if
  # PROBE_KEYBOARD is defined).
*** boot.c	Fri Mar  8 01:43:54 1996
--- boot.mod.c	Sun Mar 17 21:40:41 1996
***************
*** 75,80 ****
--- 75,83 ----
  {
  	int ret;
  
+ #ifdef DUAL_PROMPT
+ 	init_serial();
+ #endif
  #ifdef PROBE_KEYBOARD
  	if (probe_keyboard()) {
  		init_serial();
*** io.c	Fri Mar  8 01:43:54 1996
--- io.mod.c	Sun Mar 17 21:35:49 1996
***************
*** 121,126 ****
--- 121,134 ----
  void
  putchar(int c)
  {
+ #ifdef DUAL_PROMPT
+ 	if (c == '\n') {
+ 		serial_putc('\r');
+ 		putc('\r');
+ 	}
+ 	serial_putc(c);
+ 	putc(c);
+ #else
  	if (c == '\n') {
  		if (loadflags & RB_SERIAL)
  			serial_putc('\r');
***************
*** 131,136 ****
--- 139,145 ----
  		serial_putc(c);
  	else
  		putc(c);
+ #endif
  }
  
  int
***************
*** 139,145 ****
  	int c;
  
  loop:
! 	if ((c = ((loadflags & RB_SERIAL) ? serial_getc() : getc())) == '\r')
  		c = '\n';
  	if (c == '\b') {
  		if (in_buf != 0) {
--- 148,168 ----
  	int c;
  
  loop:
! #ifdef DUAL_PROMPT
! 	if(serial_ischar()){
! 	       c=serial_getc();
! 	       /* ignore bad characters that may come from the mouse */
! 	       if (!( (c>=32 && c<=127) || 
! 	              c == '\n' ||  c == '\r' || c == 8 )) goto loop;
! 	} else if(ischar()) {
! 	       c=getc();
! 	} else {
! 	       goto loop;
! 	}
! #else
! 	c = ((loadflags & RB_SERIAL) ? serial_getc() : getc())
! #endif
!         if (c == '\r')
  		c = '\n';
  	if (c == '\b') {
  		if (in_buf != 0) {
***************
*** 199,205 ****
--- 222,232 ----
  	for (initial_bios_tick = bios_tick;
  	     bios_tick - initial_bios_tick < BOOTWAIT / BIOS_TICK_MS;)
  #endif
+ #ifdef DUAL_PROMPT
+ 		if (serial_ischar() || ischar())
+ #else
  		if ((loadflags & RB_SERIAL) ? serial_ischar() : ischar())
+ #endif
  			for (;;) {
  				switch(*ptr = getchar(ptr - buf) & 0xff) {
  				      case '\n':
***************
*** 217,223 ****
--- 244,254 ----
  #error "TIMEOUT without BOOTWAIT"
  #endif
  				for (initial_bios_tick = bios_tick;;) {
+ #ifdef DUAL_PROMPT
+ 				        if (serial_ischar() || ischar())
+ #else
  					if ((loadflags & RB_SERIAL) ?
+ #endif
  					    serial_ischar() : ischar())
  						break;
  					if (bios_tick - initial_bios_tick >=

From owner-freebsd-current  Wed Mar 20 21:12:40 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id VAA20670
          for current-outgoing; Wed, 20 Mar 1996 21:12:40 -0800 (PST)
Received: (from dima@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id VAA20661
          Wed, 20 Mar 1996 21:12:37 -0800 (PST)
Message-Id: <199603210512.VAA20661@freefall.freebsd.org>
Subject: Re: X11R6.1
To: mmead@Glock.COM (matthew c. mead)
Date: Wed, 20 Mar 1996 21:12:36 -0800 (PST)
Cc: current@freebsd.org
In-Reply-To: <199603201311.IAA00599@neon.Glock.COM> from "matthew c. mead" at Mar 20, 96 08:11:14 am
From: dima@freebsd.org (Dima Ruban)
X-Class: Fast
Organization: HackerDome
X-Mailer: ELM [version 2.4 PL24]
Content-Type: text
Sender: owner-current@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

matthew c. mead writes:
> 
> Dima Ruban writes:
> 
> > Hey guys!
> 
> > What about to add X11R6.1 to ldconfig search paths in /etc/rc?
> > Anybody has anything against it? If not, I'll commit it.
> 
> 	Is R6.1 out yet?  For site customizations I usually do

Yes, it it.

> this in /etc/rc.local:


I don't think, this thing should go to /etc/rc.local. Early or late this
thing will be standard for the system, so there's no reason to put it
in /etc/rc.local

> 
> if [ -x /sbin/ldconfig ]; then
> 	_LDC=""
> 	if [ -d /usr/local/X11R6/lib ]; then
> 	    _LDC="${_LDC} /usr/local/X11R6/lib"
> 	fi
> 	echo 'adding to ldconfig path:' ${_LDC}
> 	ldconfig -m ${_LDC}
> fi
> 
> 
> 
> -matt
> 
> -- 
> Matthew C. Mead
> 
> mmead@Glock.COM
> http://www.Glock.COM/~mmead/
> 

-- dima

From owner-freebsd-current  Wed Mar 20 21:18:48 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id VAA21017
          for current-outgoing; Wed, 20 Mar 1996 21:18:48 -0800 (PST)
Received: (from dima@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id VAA21010
          Wed, 20 Mar 1996 21:18:47 -0800 (PST)
Message-Id: <199603210518.VAA21010@freefall.freebsd.org>
Subject: Re: X11R6.1
To: nate@sri.MT.net (Nate Williams)
Date: Wed, 20 Mar 1996 21:18:46 -0800 (PST)
Cc: dima@FreeBSD.ORG, current@FreeBSD.ORG
In-Reply-To: <199603201544.IAA07669@rocky.sri.MT.net> from "Nate Williams" at Mar 20, 96 08:44:00 am
From: dima@FreeBSD.ORG (Dima Ruban)
X-Class: Fast
Organization: HackerDome
X-Mailer: ELM [version 2.4 PL24]
Content-Type: text
Sender: owner-current@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

Nate Williams writes:
> 
> > What about to add X11R6.1 to ldconfig search paths in /etc/rc?
> > Anybody has anything against it? If not, I'll commit it.
> 
> Why is it needed?  Is it going to be a standard path for things, or will

Becasue X11R6.1 is out.
And this is good question about standard. This is default
(standard) project root for X11R6.1, but as I've heard, XFree86 
guys are going to stay with /usr/X11R6 path.

So, this is basically up to us to decide.

> the /usr/X11R6 path suffice for all X11R6 binaries?
> 
> (I'm partial to the latter)
> 
> 
> Nate
> 

-- dima

From owner-freebsd-current  Wed Mar 20 21:19:10 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id VAA21049
          for current-outgoing; Wed, 20 Mar 1996 21:19:10 -0800 (PST)
Received: from neon.Glock.COM (root@neon.glock.com [198.82.228.159])
          by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id VAA21044
          for <current@freebsd.org>; Wed, 20 Mar 1996 21:19:05 -0800 (PST)
Received: (from mmead@localhost) by neon.Glock.COM (8.7.4/8.7.3) id AAA00371 for current@freebsd.org; Thu, 21 Mar 1996 00:19:03 -0500 (EST)
From: "matthew c. mead" <mmead@Glock.COM>
Message-Id: <199603210519.AAA00371@neon.Glock.COM>
Subject: kernel locking hangs system?
To: current@freebsd.org
Date: Thu, 21 Mar 1996 00:19:03 -0500 (EST)
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 just supped everything this evening and did a make install.
Of course, /var/mail was set mode 755 owned by bin.bin ... I
tried to run elm which tried to acquire a kernel lock on
/var/mail/mmead, and it hung the system.  I ended up doing a
reset button reboot.  It hung all *character* input from the
keyboard.  I could still move the mouse around in X and play with
any programs that were totally graphical, but none that used the
keyboard.  Just thought I would let you guys know.


-matt

-- 
Matthew C. Mead

mmead@Glock.COM
http://www.Glock.COM/~mmead/

From owner-freebsd-current  Wed Mar 20 21:39:40 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id VAA22670
          for current-outgoing; Wed, 20 Mar 1996 21:39:40 -0800 (PST)
Received: from neon.Glock.COM (root@neon.glock.com [198.82.228.159])
          by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id VAA22654
          Wed, 20 Mar 1996 21:39:37 -0800 (PST)
Received: (from mmead@localhost) by neon.Glock.COM (8.7.4/8.7.3) id AAA00749; Thu, 21 Mar 1996 00:39:35 -0500 (EST)
From: "matthew c. mead" <mmead@Glock.COM>
Message-Id: <199603210539.AAA00749@neon.Glock.COM>
Subject: Re: X11R6.1
To: dima@freebsd.org (Dima Ruban)
Date: Thu, 21 Mar 1996 00:39:35 -0500 (EST)
Cc: current@freebsd.org
In-Reply-To: <199603210512.VAA20661@freefall.freebsd.org> from "Dima Ruban" at Mar 20, 96 09:12:36 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

Dima Ruban writes:

> > 	Is R6.1 out yet?  For site customizations I usually do

> Yes, it it.

	Kewl!

> > this in /etc/rc.local:

> I don't think, this thing should go to /etc/rc.local. Early or late this
> thing will be standard for the system, so there's no reason to put it
> in /etc/rc.local

> > if [ -x /sbin/ldconfig ]; then
> > 	_LDC=""
> > 	if [ -d /usr/local/X11R6/lib ]; then
> > 	    _LDC="${_LDC} /usr/local/X11R6/lib"
> > 	fi
> > 	echo 'adding to ldconfig path:' ${_LDC}
> > 	ldconfig -m ${_LDC}
> > fi

	Yeah, I thought it was going to be a port or something
for a while...



-matt

-- 
Matthew C. Mead

mmead@Glock.COM
http://www.Glock.COM/~mmead/

From owner-freebsd-current  Wed Mar 20 21:49:08 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id VAA24367
          for current-outgoing; Wed, 20 Mar 1996 21:49:08 -0800 (PST)
Received: from time.cdrom.com (time.cdrom.com [204.216.27.226])
          by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id VAA24355
          for <current@FreeBSD.org>; Wed, 20 Mar 1996 21:49:04 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by time.cdrom.com (8.7.5/8.6.9) with SMTP id VAA22271; Wed, 20 Mar 1996 21:48:31 -0800 (PST)
To: Warner Losh <imp@village.org>
cc: "Rodney W. Grimes" <rgrimes@gndrsh.aac.dev.com>, current@FreeBSD.org
Subject: Re: AMD doesn't like SNAP! (panic: unwire: page not in pmap) 
In-reply-to: Your message of "Wed, 20 Mar 1996 21:12:52 MST."
             <199603210412.VAA06465@rover.village.org> 
Date: Wed, 20 Mar 1996 21:48:30 -0800
Message-ID: <22268.827387310@time.cdrom.com>
From: "Jordan K. Hubbard" <jkh@time.cdrom.com>
Sender: owner-current@FreeBSD.org
X-Loop: FreeBSD.org
Precedence: bulk

> Seriously, if someone were to go back through the FreeBSD archives and
> concentrate all of the advice Rod has given out over the years on
> mother boards and the like, I think we'd have a nice addition to the
> hardware part of the handbook.
> 
> Jordan, are the archives back on line?

Until we get loop-back mounts working, I think the only way it could
happen would be to create a sup collection that points to it.

Unfortunately, the mail archives are very poor targets for sup since
each and every message would cause the entire multi-megabyte file to
transfer all over again.

Hmmmmm.  Perhaps it's time to subscribe special archival lists *off*
of freefall on another machine which provides archival search and
access?

					Jordan

From owner-freebsd-current  Wed Mar 20 21:57:04 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id VAA24971
          for current-outgoing; Wed, 20 Mar 1996 21:57:04 -0800 (PST)
Received: from neon.Glock.COM (root@neon.glock.com [198.82.228.159])
          by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id VAA24963
          for <current@freebsd.org>; Wed, 20 Mar 1996 21:57:01 -0800 (PST)
Received: (from mmead@localhost) by neon.Glock.COM (8.7.4/8.7.3) id AAA00978 for current@freebsd.org; Thu, 21 Mar 1996 00:57:00 -0500 (EST)
From: "matthew c. mead" <mmead@Glock.COM>
Message-Id: <199603210557.AAA00978@neon.Glock.COM>
Subject: lost+found ???
To: current@freebsd.org
Date: Thu, 21 Mar 1996 00:56:59 -0500 (EST)
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 created most of my filesystems in 2.1.0R with the standard
sysinstall newfs, but none of them have lost+found directories.
After newfs'ing new drive partitions and such under -current,
I've noticed none of them have lost+found directories either.
What do I need to do?



-matt

-- 
Matthew C. Mead

mmead@Glock.COM
http://www.Glock.COM/~mmead/

From owner-freebsd-current  Wed Mar 20 22:02:01 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id WAA25359
          for current-outgoing; Wed, 20 Mar 1996 22:02:01 -0800 (PST)
Received: from GndRsh.aac.dev.com (GndRsh.aac.dev.com [198.145.92.241])
          by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id WAA25349
          for <current@FreeBSD.org>; Wed, 20 Mar 1996 22:01:55 -0800 (PST)
Received: (from rgrimes@localhost) by GndRsh.aac.dev.com (8.6.12/8.6.12) id WAA23336; Wed, 20 Mar 1996 22:01:15 -0800
From: "Rodney W. Grimes" <rgrimes@GndRsh.aac.dev.com>
Message-Id: <199603210601.WAA23336@GndRsh.aac.dev.com>
Subject: Re: AMD doesn't like SNAP! (panic: unwire: page not in pmap)
To: imp@village.org (Warner Losh)
Date: Wed, 20 Mar 1996 22:01:14 -0800 (PST)
Cc: jkh@time.cdrom.com, current@FreeBSD.org
In-Reply-To: <199603210412.VAA06465@rover.village.org> from "Warner Losh" at Mar 20, 96 09:12:52 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

> 
> : Sigh..  A Rod's Tips page at http://www.freebsd.org/handbook/hw.html
> : SURE WOULD BE NICE, yup!  Save lots of people lots of trouble..  :-)
> 
> An idea occurred to me while eating sushi and driking coffee with a
> friend (you know who you are) the other night.  Why not take the
> archives, grep out all of Rod's mail, organize it into a tips page,
> put his name on it and then let him correct all the mistake we've made
> :-)
> 
> Seriously, if someone were to go back through the FreeBSD archives and
> concentrate all of the advice Rod has given out over the years on
> mother boards and the like, I think we'd have a nice addition to the
> hardware part of the handbook.
> 
> Jordan, are the archives back on line?

If some one does this I will gladly addit it and make corrections/updates
to it, I just don't have the time to do it myself.


-- 
Rod Grimes                                      rgrimes@gndrsh.aac.dev.com
Accurate Automation Company                 Reliable computers for FreeBSD

From owner-freebsd-current  Wed Mar 20 22:04:01 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id WAA25501
          for current-outgoing; Wed, 20 Mar 1996 22:04:01 -0800 (PST)
Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19])
          by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id WAA25464
          for <current@FreeBSD.ORG>; Wed, 20 Mar 1996 22:03:50 -0800 (PST)
Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.12/8.6.9) id QAA24097; Thu, 21 Mar 1996 16:53:22 +1100
Date: Thu, 21 Mar 1996 16:53:22 +1100
From: Bruce Evans <bde@zeta.org.au>
Message-Id: <199603210553.QAA24097@godzilla.zeta.org.au>
To: julian@ref.tfs.com, scrappy@ki.net
Subject: Re: PATCH: small, syntax changes for devfs
Cc: current@FreeBSD.ORG
Sender: owner-current@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

>	For some reason, I'm getting all my /dev/sd0[abcef] devices, but
>none of the /dev/sd0s1[abcef] devices.  Looking at the code, I can't find

There seems to be a bug or two, and some details aren't right yet:
- perhaps you don't have those devices.  There are about 512 slice/partition
  names per physical device, and only the existent ones are generated.
- names for partitions aren't generated unless the slice containing the
  partitions or at least one partition on that slice is open.  I'm not
  sure if they should be generated; anyway, this isn't implemented.
- names for aliases for partitions in the compatibility slice apparently
  arent't generated.  I'm not sure if the should be; but this is supposed
  to be implemented.
- names for my removable rsd1 weren't generated correctly.  After messing
  around with this for a while, the disk became inaccessible even using
  ordinary /dev.  This bug has something to do with the disk usually not
  having any devices open on it.

Bruce

From owner-freebsd-current  Wed Mar 20 22:09:14 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id WAA25899
          for current-outgoing; Wed, 20 Mar 1996 22:09:14 -0800 (PST)
Received: from VX23.CC.MONASH.EDU.AU (vx23.cc.monash.edu.au [130.194.1.23])
          by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id WAA25891
          for <current@freebsd.org>; Wed, 20 Mar 1996 22:09:05 -0800 (PST)
Received: from moa.cc.monash.edu.au (george@moa.cc.monash.edu.au)
 by vaxc.cc.monash.edu.au (PMDF V5.0-6 #16291)
 id <01I2LWBN5CZE9I5ANJ@vaxc.cc.monash.edu.au> for current@freebsd.org; Thu,
 21 Mar 1996 17:07:13 +1100
Received: (george@localhost) by moa.cc.monash.edu.au (8.6.10/8.6.4)
 id QAA12180 for current@freebsd.org; Thu, 21 Mar 1996 16:07:07 +1000
Date: Thu, 21 Mar 1996 16:07:07 +1000
From: George Scott <George.Scott@cc.monash.edu.au>
Subject: Re: DEVFS vs "regular /dev"
To: current@freebsd.org
Message-id: <199603210607.QAA12180@moa.cc.monash.edu.au>
MIME-version: 1.0
Content-type: TEXT/PLAIN
Content-transfer-encoding: 7BIT
Sender: owner-current@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

>>> This assumes that the file system abstractions currently in place
>>> change as well, since the /dev FS can't be mounted *after* the / FS
>>> has been mounted as an inferior FS --
>> why not?
>> you don't need a mounted /dev to mount root.
>> that's done specially.
> 
> So you don't need a mounted root to have a mounted /dev, of course!
> 
> This makes it possible to remount root r/w without unmounting the
> devfs (and so still needing /dev).
> 
>>> the /dev has to be there as
>>> an overlay mount (translucent FS), and that means FS changes to allow
>>> translucence and to divorce volume mappings from the need for a mount
>>> point (basically, a shadow / and /dev on which the devfs /dev is mounted
>>> and the real / is mounted over top of the shadow /).
>> 
>> I think that's not needed
> 
> Root remount, again.  If you divorce the mappings, you can mount root
> over and over despite devfs being mounted by default.

I'm not sure I understand all this, but never mind.

What would be wrong with doing something like this..

At boot time the kernel creates a memory-filesystem (mfs or other) with a /dev
directory.  During the device probes this /dev gets populated with appropriate
device entries.  At the end of the kernel initialisations the kernel union
mounts the root disk over the memory /.

For those detractors in a previous thread this would also allow those who
are so inclined to have their own custom modifications to /dev or even to
remount their root without the union to keep using the old method.

George.

From owner-freebsd-current  Wed Mar 20 22:33:18 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id WAA27825
          for current-outgoing; Wed, 20 Mar 1996 22:33:18 -0800 (PST)
Received: from VX23.CC.MONASH.EDU.AU (vx23.cc.monash.edu.au [130.194.1.23])
          by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id WAA27816
          for <freebsd-current@freebsd.org>; Wed, 20 Mar 1996 22:33:16 -0800 (PST)
Received: from moa.cc.monash.edu.au (george@moa.cc.monash.edu.au)
 by vaxc.cc.monash.edu.au (PMDF V5.0-6 #16291)
 id <01I2LX2482Y29I5ANJ@vaxc.cc.monash.edu.au> for freebsd-current@freebsd.org;
 Thu, 21 Mar 1996 17:28:33 +1100
Received: (george@localhost) by moa.cc.monash.edu.au (8.6.10/8.6.4)
 id QAA12234 for freebsd-current@freebsd.org; Thu, 21 Mar 1996 16:28:32 +1000
Date: Thu, 21 Mar 1996 16:28:32 +1000
From: George Scott <George.Scott@cc.monash.edu.au>
Subject: Re: 2.2-960226-SNAP now on ftp.freebsd.org
To: freebsd-current@freebsd.org
Message-id: <199603210628.QAA12234@moa.cc.monash.edu.au>
MIME-version: 1.0
Content-type: TEXT/PLAIN
Content-transfer-encoding: 7BIT
Sender: owner-current@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

>>>> Don't forget /.profile, for the single-user shell.
> 
> It is very handy when booted single user as the root shell in that
> case has a home directory of / instead of /root.  I am pretty sure
> that was the reason that CSRG added this link when they moved root's
> home directory from / to /root.
> 
> This also applies to /.cshrc -> /root/.cshrc (hard link) same reason,
> only when you ask for the single user shell to be /bin/csh.

/.profile and co are also used if you log in when your home directory doesn't
exist (eg, NFS server is down, careless administrator).

George.

From owner-freebsd-current  Wed Mar 20 23:42:33 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id XAA03926
          for current-outgoing; Wed, 20 Mar 1996 23:42:33 -0800 (PST)
Received: from nixpbe.pdb.sni.de (mail.sni.de [192.109.2.33])
          by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id XAA03850
          for <current@FreeBSD.org>; Wed, 20 Mar 1996 23:41:38 -0800 (PST)
Received: (from nerv@localhost) by nixpbe.pdb.sni.de (8.6.12/8.6.12) id IAA26228 for current@FreeBSD.org; Thu, 21 Mar 1996 08:40:51 +0100
Message-Id: <199603210740.IAA26228@nixpbe.pdb.sni.de>
Subject: Re: lost+found ???
To: mmead@Glock.COM (matthew c. mead)
Date: Thu, 21 Mar 96 8:38:11 MET
From: Greg Lehey <lehey.pad@sni.de>
Cc: current@FreeBSD.org
In-Reply-To: <199603210557.AAA00978@neon.Glock.COM>; from "matthew c. mead" at Mar 21, 96 12:56 am
X-Mailer: xmail 2.4 (based on ELM 2.2 PL16)
Sender: owner-current@FreeBSD.org
X-Loop: FreeBSD.org
Precedence: bulk

>
>     I created most of my filesystems in 2.1.0R with the standard
> sysinstall newfs, but none of them have lost+found directories.
> After newfs'ing new drive partitions and such under -current,
> I've noticed none of them have lost+found directories either.

Looks like a buglet in sysinstall.

> What do I need to do?

# mkdir /lost+found
# mkdir /usr/lost+found

etc.

Greg

From owner-freebsd-current  Wed Mar 20 23:44:34 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id XAA04280
          for current-outgoing; Wed, 20 Mar 1996 23:44:34 -0800 (PST)
Received: from grumble.grondar.za (root@grumble.grondar.za [196.7.18.130])
          by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id XAA04259
          for <current@FreeBSD.org>; Wed, 20 Mar 1996 23:44:26 -0800 (PST)
Received: from grumble.grondar.za (mark@localhost [127.0.0.1]) by grumble.grondar.za (8.7.5/8.7.3) with ESMTP id JAA17704; Thu, 21 Mar 1996 09:43:54 +0200 (SAT)
Message-Id: <199603210743.JAA17704@grumble.grondar.za>
To: "matthew c. mead" <mmead@Glock.COM>
cc: current@FreeBSD.org
Subject: Re: lost+found ??? 
Date: Thu, 21 Mar 1996 09:43:54 +0200
From: Mark Murray <mark@grondar.za>
Sender: owner-current@FreeBSD.org
X-Loop: FreeBSD.org
Precedence: bulk

"matthew c. mead" wrote:
>     I created most of my filesystems in 2.1.0R with the standard
> sysinstall newfs, but none of them have lost+found directories.
> After newfs'ing new drive partitions and such under -current,
> I've noticed none of them have lost+found directories either.
> What do I need to do?

# mkdir lost+found

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  Wed Mar 20 23:49:37 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id XAA04949
          for current-outgoing; Wed, 20 Mar 1996 23:49:37 -0800 (PST)
Received: from genesis.atrad.adelaide.edu.au (genesis.atrad.adelaide.edu.au [129.127.96.120])
          by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id XAA04920
          for <current@freebsd.org>; Wed, 20 Mar 1996 23:49:16 -0800 (PST)
Received: from msmith@localhost by genesis.atrad.adelaide.edu.au (8.6.12/8.6.9) id SAA11899; Thu, 21 Mar 1996 18:34:32 +1030
From: Michael Smith <msmith@atrad.adelaide.edu.au>
Message-Id: <199603210804.SAA11899@genesis.atrad.adelaide.edu.au>
Subject: Re: lost+found ???
To: mmead@Glock.COM (matthew c. mead)
Date: Thu, 21 Mar 1996 18:34:31 +1030 (CST)
Cc: current@freebsd.org
In-Reply-To: <199603210557.AAA00978@neon.Glock.COM> from "matthew c. mead" at Mar 21, 96 00:56:59 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

matthew c. mead stands accused of saying:
> 
>     I created most of my filesystems in 2.1.0R with the standard
> sysinstall newfs, but none of them have lost+found directories.
> After newfs'ing new drive partitions and such under -current,
> I've noticed none of them have lost+found directories either.
> What do I need to do?

Nothing, fsck creates them as it needs them.

> -matt

-- 
]] 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 Mar 21 00:11:03 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id AAA06274
          for current-outgoing; Thu, 21 Mar 1996 00:11:03 -0800 (PST)
Received: from nixpbe.pdb.sni.de (mail.sni.de [192.109.2.33])
          by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id AAA06260
          for <freebsd-current@freebsd.org>; Thu, 21 Mar 1996 00:10:50 -0800 (PST)
Received: (from nerv@localhost) by nixpbe.pdb.sni.de (8.6.12/8.6.12) id JAA28609 for freebsd-current@freebsd.org; Thu, 21 Mar 1996 09:10:13 +0100
Message-Id: <199603210810.JAA28609@nixpbe.pdb.sni.de>
Subject: Re: GNU tar 1.11.2
To: nate@sri.MT.net (Nate Williams)
Date: Thu, 21 Mar 96 9:07:33 MET
From: Greg Lehey <lehey.pad@sni.de>
Cc: freebsd-current@freebsd.org
In-Reply-To: <199603201623.JAA07794@rocky.sri.MT.net>; from "Nate Williams" at Mar 20, 96 9:23 am
X-Mailer: xmail 2.4 (based on ELM 2.2 PL16)
Sender: owner-current@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

>
>> I just found, that a command:
>>
>> tar -C /tmp -xsf foo.tar
>>
>> drops core. This is because tar seems to assume, that when s flag is
>> used, there are more arguments to come, and ends up calling strlen(0)
>> (see patch below).
>>
>> I looked up GNU tar 1.11.8 (dated May 1995), and the code indeed seems
>> to have changed a bit. It doesn't work correctly either, but gives a
>> "Missing file name after -C".
>>
>> However, is anyone considered bumping the tar version from 1.11.2
>> (March 1993) to 1.11.8 for any reason whatever ?
>
> I looked at it a while back, and the new GNU tar contains a lot of stuff
> that I don't think we need, but one of the international folks (ie;
> 8-bit clean) like Andrey comment.

I've been using it for nearly a year now, and it works fine for me.
To the best of my knowledge, there's no support of Slavonic languages
there.  I could be nasty and say that there's no support for French or
German either--certainly the translations into these languages leave
something to be desired.

I have a performance fix for 1.11.8 which could probably be
retrofitted to 1.11.2, though I don't know why you'd want to.  I have
a 4 GB file system with a very large number of multiply linked files.
The standard version creates a list of files with link count > 1 and
searches it linearly for every file.  The result was that a full
backup of the file system took something like 3 hours CPU time.  I
replaced the list with a table indexed by inode number (yep, up to
2**20 entries, but it's all virtual), and reduced the time by a factor
of 99.5%.  I can drag out the fixes if anybody's interested.

Greg


From owner-freebsd-current  Thu Mar 21 00:14:28 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id AAA06565
          for current-outgoing; Thu, 21 Mar 1996 00:14:28 -0800 (PST)
Received: from time.cdrom.com (time.cdrom.com [204.216.27.226])
          by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id AAA06560
          for <current@FreeBSD.org>; Thu, 21 Mar 1996 00:14:25 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by time.cdrom.com (8.7.5/8.6.9) with SMTP id AAA23698; Thu, 21 Mar 1996 00:13:55 -0800 (PST)
To: Greg Lehey <lehey.pad@sni.de>
cc: mmead@Glock.COM (matthew c. mead), current@FreeBSD.org
Subject: Re: lost+found ??? 
In-reply-to: Your message of "Thu, 21 Mar 1996 08:38:11 +0700."
             <199603210740.IAA26228@nixpbe.pdb.sni.de> 
Date: Thu, 21 Mar 1996 00:13:55 -0800
Message-ID: <23696.827396035@time.cdrom.com>
From: "Jordan K. Hubbard" <jkh@time.cdrom.com>
Sender: owner-current@FreeBSD.org
X-Loop: FreeBSD.org
Precedence: bulk

> >
> >     I created most of my filesystems in 2.1.0R with the standard
> > sysinstall newfs, but none of them have lost+found directories.
> > After newfs'ing new drive partitions and such under -current,
> > I've noticed none of them have lost+found directories either.
> 
> Looks like a buglet in sysinstall.

Actualy, no - fsck is supposed to create lost+found entries on demand,
at least it always has on every BSD derived Sun and DEC system I've
ever used.

					Jordan

From owner-freebsd-current  Thu Mar 21 00:22:06 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id AAA07118
          for current-outgoing; Thu, 21 Mar 1996 00:22:06 -0800 (PST)
Received: from ra.dkuug.dk (ra.dkuug.dk [193.88.44.193])
          by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id AAA07113
          Thu, 21 Mar 1996 00:21:59 -0800 (PST)
Received: (from sos@localhost) by ra.dkuug.dk (8.6.12/8.6.12) id JAA07135; Thu, 21 Mar 1996 09:02:11 +0100
Message-Id: <199603210802.JAA07135@ra.dkuug.dk>
Subject: Re: Native & Linux ELF support finally there...
To: imp@village.org (Warner Losh)
Date: Thu, 21 Mar 1996 09:02:11 +0100 (MET)
Cc: sos@FreeBSD.org, current@FreeBSD.org
In-Reply-To: <199603210420.VAA06487@rover.village.org> from "Warner Losh" at Mar 20, 96 09:20:43 pm
From: sos@FreeBSD.org
Reply-to: sos@FreeBSD.org
X-Mailer: ELM [version 2.4 PL24]
Content-Type: text
Sender: owner-current@FreeBSD.org
X-Loop: FreeBSD.org
Precedence: bulk

In reply to Warner Losh who wrote:
> 
> A while back someone asked me if they could do the following sick
> thing:
> 
> Compile FreeBSD kernel, put it on a linux box, run lilo pointed at
> this kernel, and reboot and have their "Linux" box suddenly be a
> "FreeBSD" box running all their Linux stuff.
> 
> Is that now possible?  Or are there too many kernel things that would
> preclude this (eg no ps, netstat, etc)?

Auch, havn't thought of that one :)
This looks like a "hostile takeover" of some kind, could be fun if
it worked:

"Tired of that linux system ?? well, just copy our kernel ontop
of the old one..."

I think however that there are toomany hidden obstacles before
this will work, but it could be fun if it worked...

-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Soren Schmidt             (sos@FreeBSD.org)             FreeBSD Core Team
               So much code to hack -- so little time.

From owner-freebsd-current  Thu Mar 21 00:39:20 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id AAA07999
          for current-outgoing; Thu, 21 Mar 1996 00:39:20 -0800 (PST)
Received: from tfs.com (tfs.com [140.145.250.1])
          by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id AAA07994
          for <current@freebsd.org>; Thu, 21 Mar 1996 00:39:17 -0800 (PST)
Received: from critter.tfs.com by tfs.com (smail3.1.28.1) with SMTP
	id m0tzfti-0003xZC; Thu, 21 Mar 96 00:39 PST
Received: from localhost.tfs.com (localhost.tfs.com [127.0.0.1]) by critter.tfs.com (8.6.12/8.6.12) with SMTP id GAA14055; Thu, 21 Mar 1996 06:48:15 GMT
X-Authentication-Warning: critter.tfs.com: Host localhost.tfs.com didn't use HELO protocol
To: davidg@Root.COM
cc: Terry Lambert <terry@lambert.org>, julian@ref.tfs.com (JULIAN Elischer),
        scrappy@ki.net, current@freebsd.org
Subject: Re: DEVFS vs "regular /dev" 
In-reply-to: Your message of "Wed, 20 Mar 1996 16:10:05 PST."
             <199603210010.QAA03902@Root.COM> 
Date: Thu, 21 Mar 1996 06:48:14 +0000
Message-ID: <14053.827390894@critter.tfs.com>
From: Poul-Henning Kamp <phk@critter.tfs.com>
Sender: owner-current@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

> >> > This assumes that the file system abstractions currently in place
> >> > change as well, since the /dev FS can't be mounted *after* the / FS
> >> > has been mounted as an inferior FS --
> >> why not?
> >> you don't need a mounted /dev to mount root.
> >> that's done specially.
> >
> >So you don't need a mounted root to have a mounted /dev, of course!
> 
>    That's silly. The root filesystem is mounted long before /dev would be, 

Not that long before.  /sbin/init will have to mount it to get in touch
with /dev/console, /dev/null and ...

--
Poul-Henning Kamp           | phk@FreeBSD.ORG       FreeBSD Core-team.
http://www.freebsd.org/~phk | phk@login.dknet.dk    Private mailbox.
whois: [PHK]                | phk@ref.tfs.com       TRW Financial Systems, Inc.
Future will arrive by its own means, progress not so.

From owner-freebsd-current  Thu Mar 21 00:53:58 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id AAA08566
          for current-outgoing; Thu, 21 Mar 1996 00:53:58 -0800 (PST)
Received: from tfs.com (tfs.com [140.145.250.1])
          by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id AAA08561
          for <current@freebsd.org>; Thu, 21 Mar 1996 00:53:56 -0800 (PST)
Received: from critter.tfs.com by tfs.com (smail3.1.28.1) with SMTP
	id m0tzftg-0003xSC; Thu, 21 Mar 96 00:39 PST
Received: from localhost.tfs.com (localhost.tfs.com [127.0.0.1]) by critter.tfs.com (8.6.12/8.6.12) with SMTP id HAA14196; Thu, 21 Mar 1996 07:03:02 GMT
X-Authentication-Warning: critter.tfs.com: Host localhost.tfs.com didn't use HELO protocol
To: Bruce Evans <bde@zeta.org.au>
cc: julian@ref.tfs.com, scrappy@ki.net, current@freebsd.org
Subject: Re: PATCH: small, syntax changes for devfs 
In-reply-to: Your message of "Thu, 21 Mar 1996 16:53:22 +1100."
             <199603210553.QAA24097@godzilla.zeta.org.au> 
Date: Thu, 21 Mar 1996 07:03:02 +0000
Message-ID: <14194.827391782@critter.tfs.com>
From: Poul-Henning Kamp <phk@critter.tfs.com>
Sender: owner-current@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

> >	For some reason, I'm getting all my /dev/sd0[abcef] devices, but
> >none of the /dev/sd0s1[abcef] devices.  Looking at the code, I can't find
> 
> - names for partitions aren't generated unless the slice containing the
>   partitions or at least one partition on that slice is open.  I'm not
>   sure if they should be generated; anyway, this isn't implemented.
and since wd0s1 isn't there either, how can you trigger that ?
I belive all sensible slices/partitions should appear in /devfs by default,
so that you can just fsck them from fstab...

--
Poul-Henning Kamp           | phk@FreeBSD.ORG       FreeBSD Core-team.
http://www.freebsd.org/~phk | phk@login.dknet.dk    Private mailbox.
whois: [PHK]                | phk@ref.tfs.com       TRW Financial Systems, Inc.
Future will arrive by its own means, progress not so.

From owner-freebsd-current  Thu Mar 21 02:09:02 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id CAA15099
          for current-outgoing; Thu, 21 Mar 1996 02:09:02 -0800 (PST)
Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211])
          by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id CAA15092
          for <current@FreeBSD.org>; Thu, 21 Mar 1996 02:08:58 -0800 (PST)
Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id DAA29477; Thu, 21 Mar 1996 03:02:53 -0700
From: Terry Lambert <terry@lambert.org>
Message-Id: <199603211002.DAA29477@phaeton.artisoft.com>
Subject: Re: DEVFS vs "regular /dev"
To: George.Scott@cc.monash.edu.au (George Scott)
Date: Thu, 21 Mar 1996 03:02:53 -0700 (MST)
Cc: current@FreeBSD.org
In-Reply-To: <199603210607.QAA12180@moa.cc.monash.edu.au> from "George Scott" at Mar 21, 96 04:07:07 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'm not sure I understand all this, but never mind.
> 
> What would be wrong with doing something like this..
> 
> At boot time the kernel creates a memory-filesystem (mfs or other) with a /dev
> directory.  During the device probes this /dev gets populated with appropriate
> device entries.  At the end of the kernel initialisations the kernel union
> mounts the root disk over the memory /.

This is exactly what I was suggesting.  My suggestion differs only in
that I think it is only necessary to skeletonize / and /dev; an FS that
only supports directories and doesn't suppor file creation or anything
else could be built into the devfs itself as static data.  This would
be a lot less work, and you would not have to drag in a memfs image
into kernel static data.

> For those detractors in a previous thread this would also allow those who
> are so inclined to have their own custom modifications to /dev or even to
> remount their root without the union to keep using the old method.

Yes.  Though I would rip out specfs so the old method would fail.  8-).

The vnops code for specfs sucks uot something fierce.  This is what
I was describing when I said the Heidemann framework had been pounded
into 4.4BSD without much care...


					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 Mar 21 02:11:05 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id CAA15305
          for current-outgoing; Thu, 21 Mar 1996 02:11:05 -0800 (PST)
Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211])
          by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id CAA15294
          Thu, 21 Mar 1996 02:11:01 -0800 (PST)
Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id DAA29489; Thu, 21 Mar 1996 03:05:23 -0700
From: Terry Lambert <terry@lambert.org>
Message-Id: <199603211005.DAA29489@phaeton.artisoft.com>
Subject: Re: Native & Linux ELF support finally there...
To: sos@freebsd.org
Date: Thu, 21 Mar 1996 03:05:22 -0700 (MST)
Cc: imp@village.org, current@freebsd.org
In-Reply-To: <199603210802.JAA07135@ra.dkuug.dk> from "sos@freebsd.org" at Mar 21, 96 09:02:11 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

> > A while back someone asked me if they could do the following sick
> > thing:
> > 
> > Compile FreeBSD kernel, put it on a linux box, run lilo pointed at
> > this kernel, and reboot and have their "Linux" box suddenly be a
> > "FreeBSD" box running all their Linux stuff.
> > 
> > Is that now possible?  Or are there too many kernel things that would
> > preclude this (eg no ps, netstat, etc)?
> 
> Auch, havn't thought of that one :)
> This looks like a "hostile takeover" of some kind, could be fun if
> it worked:
> 
> "Tired of that linux system ?? well, just copy our kernel ontop
> of the old one..."
> 
> I think however that there are toomany hidden obstacles before
> this will work, but it could be fun if it worked...

Put in the devfs and put in the "logical device driver" framework
to recognize linux partitioning techniques for swap, root, etc.,
and it will work with some minor /etc file changes (mostly fstab
and inittab).

And I prefer to call it a "competitive upgrade".


					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 Mar 21 02:20:48 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id CAA16303
          for current-outgoing; Thu, 21 Mar 1996 02:20:48 -0800 (PST)
Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11])
          by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id CAA16296
          for <freebsd-current@FreeBSD.org>; Thu, 21 Mar 1996 02:20:44 -0800 (PST)
Received: from sax.sax.de by irz301.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id LAA15331 for <freebsd-current@FreeBSD.org>; Thu, 21 Mar 1996 11:20:38 +0100
Received: by sax.sax.de (8.6.11/8.6.12-s1) with UUCP
	id LAA20937 for freebsd-current@FreeBSD.org; Thu, 21 Mar 1996 11:20:38 +0100
Received: (from j@localhost) by uriah.heep.sax.de (8.7.4/8.6.9) id KAA12004 for freebsd-current@FreeBSD.org; Thu, 21 Mar 1996 10:26:19 +0100 (MET)
From: J Wunsch <j@uriah.heep.sax.de>
Message-Id: <199603210926.KAA12004@uriah.heep.sax.de>
Subject: Re: PATCH/DEVFS: /dev/dump & /dev/klog
To: freebsd-current@FreeBSD.org (FreeBSD-current users)
Date: Thu, 21 Mar 1996 10:26:18 +0100 (MET)
In-Reply-To: <199603200811.AAA15977@ref.tfs.com> from "JULIAN Elischer" at Mar 20, 96 00:11:39 am
X-Phone: +49-351-2012 669
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

As JULIAN Elischer wrote:

>  I have only one comment, which is that
>  there is a new devfs registration routine that uses a singl argument 
>  for a name rather than the dir/make pair..
>  check devfsext.h

Please, update the man page.

-- 
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 Mar 21 02:20:56 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id CAA16329
          for current-outgoing; Thu, 21 Mar 1996 02:20:56 -0800 (PST)
Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11])
          by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id CAA16312
          for <freebsd-current@FreeBSD.org>; Thu, 21 Mar 1996 02:20:50 -0800 (PST)
Received: from sax.sax.de by irz301.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id LAA15339 for <freebsd-current@FreeBSD.org>; Thu, 21 Mar 1996 11:20:42 +0100
Received: by sax.sax.de (8.6.11/8.6.12-s1) with UUCP
	id LAA20941 for freebsd-current@FreeBSD.org; Thu, 21 Mar 1996 11:20:41 +0100
Received: (from j@localhost) by uriah.heep.sax.de (8.7.4/8.6.9) id KAA12073 for freebsd-current@FreeBSD.org; Thu, 21 Mar 1996 10:31:38 +0100 (MET)
From: J Wunsch <j@uriah.heep.sax.de>
Message-Id: <199603210931.KAA12073@uriah.heep.sax.de>
Subject: Re: perl4
To: freebsd-current@FreeBSD.org (FreeBSD-current users)
Date: Thu, 21 Mar 1996 10:31:38 +0100 (MET)
In-Reply-To: <988.827339761@time.cdrom.com> from "Jordan K. Hubbard" at Mar 20, 96 08:36:01 am
X-Phone: +49-351-2012 669
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

As Jordan K. Hubbard wrote:

> You're saying you're willing to re-write all of the offending
> utilities in C, including the test scripts for xntpd and sendmail?

...including all future scripts?

-- 
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 Mar 21 02:22:10 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id CAA16554
          for current-outgoing; Thu, 21 Mar 1996 02:22:10 -0800 (PST)
Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11])
          by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id CAA16538
          for <freebsd-current@FreeBSD.org>; Thu, 21 Mar 1996 02:22:06 -0800 (PST)
Received: from sax.sax.de by irz301.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id LAA15343 for <freebsd-current@FreeBSD.org>; Thu, 21 Mar 1996 11:20:44 +0100
Received: by sax.sax.de (8.6.11/8.6.12-s1) with UUCP
	id LAA20944 for freebsd-current@FreeBSD.org; Thu, 21 Mar 1996 11:20:43 +0100
Received: (from j@localhost) by uriah.heep.sax.de (8.7.4/8.6.9) id KAA12094 for freebsd-current@FreeBSD.org; Thu, 21 Mar 1996 10:34:15 +0100 (MET)
From: J Wunsch <j@uriah.heep.sax.de>
Message-Id: <199603210934.KAA12094@uriah.heep.sax.de>
Subject: Re: perl4
To: freebsd-current@FreeBSD.org (FreeBSD-current users)
Date: Thu, 21 Mar 1996 10:34:14 +0100 (MET)
In-Reply-To: <199603201659.KAA20250@compound> from "Tony Kimball" at Mar 20, 96 10:59:52 am
X-Phone: +49-351-2012 669
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

As Tony Kimball wrote:

>    You're saying you're willing to re-write all of the offending
>    utilities in C, including the test scripts for xntpd and sendmail?
> 
> Do the test scripts really need to be part of the base OS?

Btw., you've only checked for installed scripts.  Do also check out
the Makefiles.  I know that i've been using ``perl -e'' in some of the
Makefiles myself.

I don't believe removing Perl is an option.  And, we aren't the only
system that ships Perl as part of the base system.  I remember Data
General having it as well, most likely others too.

-- 
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 Mar 21 02:57:13 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id CAA18567
          for current-outgoing; Thu, 21 Mar 1996 02:57:13 -0800 (PST)
Received: from GndRsh.aac.dev.com (GndRsh.aac.dev.com [198.145.92.241])
          by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id CAA18558
          for <freebsd-current@FreeBSD.org>; Thu, 21 Mar 1996 02:57:09 -0800 (PST)
Received: (from rgrimes@localhost) by GndRsh.aac.dev.com (8.6.12/8.6.12) id CAA23624; Thu, 21 Mar 1996 02:56:52 -0800
From: "Rodney W. Grimes" <rgrimes@GndRsh.aac.dev.com>
Message-Id: <199603211056.CAA23624@GndRsh.aac.dev.com>
Subject: Re: perl4
To: j@uriah.heep.sax.de (J Wunsch)
Date: Thu, 21 Mar 1996 02:56:51 -0800 (PST)
Cc: freebsd-current@FreeBSD.org
In-Reply-To: <199603210934.KAA12094@uriah.heep.sax.de> from "J Wunsch" at Mar 21, 96 10:34:14 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

> 
> As Tony Kimball wrote:
> 
> >    You're saying you're willing to re-write all of the offending
> >    utilities in C, including the test scripts for xntpd and sendmail?
> > 
> > Do the test scripts really need to be part of the base OS?
> 
> Btw., you've only checked for installed scripts.  Do also check out
> the Makefiles.  I know that i've been using ``perl -e'' in some of the
> Makefiles myself.

That particular things kinda makes my stomach turn, as it creates yet
more cyclic dependincy trees that are very hard to break.  Think about
what would happen if we did upgrade to perl5 in the base system and
now our Makefiles with perl -e in them fall over because they need to
be changed.  Instant cyclic build problem.

Makefiles should be written using a minimal set of tools, not any old
thing that happens to be avaliable on the system.  If you look at the
current toolist required in /usr/src/Makefile it is already way to
large and needs some control put on just what we do allow to be used
in a Makefile.

> I don't believe removing Perl is an option.  And, we aren't the only
> system that ships Perl as part of the base system.  I remember Data
> General having it as well, most likely others too.
> 
> -- 
> 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. ;-)
> 


-- 
Rod Grimes                                      rgrimes@gndrsh.aac.dev.com
Accurate Automation Company                 Reliable computers for FreeBSD

From owner-freebsd-current  Thu Mar 21 05:14:43 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id FAA25091
          for current-outgoing; Thu, 21 Mar 1996 05:14:43 -0800 (PST)
Received: from Root.COM (implode.Root.COM [198.145.90.17])
          by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id FAA25086
          for <current@freebsd.org>; Thu, 21 Mar 1996 05:14:41 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by Root.COM (8.6.12/8.6.5) with SMTP id FAA05246; Thu, 21 Mar 1996 05:13:54 -0800
Message-Id: <199603211313.FAA05246@Root.COM>
X-Authentication-Warning: implode.Root.COM: Host localhost didn't use HELO protocol
To: Poul-Henning Kamp <phk@critter.tfs.com>
cc: Terry Lambert <terry@lambert.org>, julian@ref.tfs.com (JULIAN Elischer),
        scrappy@ki.net, current@freebsd.org
Subject: Re: DEVFS vs "regular /dev" 
In-reply-to: Your message of "Thu, 21 Mar 1996 06:48:14 GMT."
             <14053.827390894@critter.tfs.com> 
From: David Greenman <davidg@Root.COM>
Reply-To: davidg@Root.COM
Date: Thu, 21 Mar 1996 05:13:54 -0800
Sender: owner-current@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

>> >> > This assumes that the file system abstractions currently in place
>> >> > change as well, since the /dev FS can't be mounted *after* the / FS
>> >> > has been mounted as an inferior FS --
>> >> why not?
>> >> you don't need a mounted /dev to mount root.
>> >> that's done specially.
>> >
>> >So you don't need a mounted root to have a mounted /dev, of course!
>> 
>>    That's silly. The root filesystem is mounted long before /dev would be, 
>
>Not that long before.  /sbin/init will have to mount it to get in touch
>with /dev/console, /dev/null and ...

   No, it will be mounted in the kernel.

-DG

David Greenman
Core-team/Principal Architect, The FreeBSD Project

From owner-freebsd-current  Thu Mar 21 05:21:44 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id FAA25486
          for current-outgoing; Thu, 21 Mar 1996 05:21:44 -0800 (PST)
Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11])
          by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id FAA25475
          for <freebsd-current@FreeBSD.org>; Thu, 21 Mar 1996 05:21:21 -0800 (PST)
Received: from sax.sax.de by irz301.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id OAA22767 for <freebsd-current@FreeBSD.org>; Thu, 21 Mar 1996 14:21:00 +0100
Received: by sax.sax.de (8.6.11/8.6.12-s1) with UUCP
	id OAA22721 for freebsd-current@FreeBSD.org; Thu, 21 Mar 1996 14:21:00 +0100
Received: (from j@localhost) by uriah.heep.sax.de (8.7.4/8.6.9) id NAA13192 for freebsd-current@FreeBSD.org; Thu, 21 Mar 1996 13:59:43 +0100 (MET)
From: J Wunsch <j@uriah.heep.sax.de>
Message-Id: <199603211259.NAA13192@uriah.heep.sax.de>
Subject: Re: lost+found ???
To: freebsd-current@FreeBSD.org (FreeBSD-current users)
Date: Thu, 21 Mar 1996 13:59:43 +0100 (MET)
In-Reply-To: <199603210804.SAA11899@genesis.atrad.adelaide.edu.au> from "Michael Smith" at Mar 21, 96 06:34:31 pm
X-Phone: +49-351-2012 669
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

As Michael Smith wrote:

> > What do I need to do?
> 
> Nothing, fsck creates them as it needs them.

...thereby happily destroying arbitrary disk data if it has to extend
the root directory and fails to find free space to do so.

newfs should create it.

-- 
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 Mar 21 05:22:01 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id FAA25509
          for current-outgoing; Thu, 21 Mar 1996 05:22:01 -0800 (PST)
Received: from tfs.com (tfs.com [140.145.250.1])
          by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id FAA25504
          for <current@freebsd.org>; Thu, 21 Mar 1996 05:21:59 -0800 (PST)
Received: from critter.tfs.com by tfs.com (smail3.1.28.1) with SMTP
	id m0tzkJL-0003wAC; Thu, 21 Mar 96 05:21 PST
Received: from localhost.tfs.com (localhost.tfs.com [127.0.0.1]) by critter.tfs.com (8.6.12/8.6.12) with SMTP id NAA00627; Thu, 21 Mar 1996 13:21:43 GMT
X-Authentication-Warning: critter.tfs.com: Host localhost.tfs.com didn't use HELO protocol
To: davidg@Root.COM
cc: Terry Lambert <terry@lambert.org>, julian@ref.tfs.com (JULIAN Elischer),
        scrappy@ki.net, current@freebsd.org
Subject: Re: DEVFS vs "regular /dev" 
In-reply-to: Your message of "Thu, 21 Mar 1996 05:13:54 PST."
             <199603211313.FAA05246@Root.COM> 
Date: Thu, 21 Mar 1996 13:21:42 +0000
Message-ID: <625.827414502@critter.tfs.com>
From: Poul-Henning Kamp <phk@critter.tfs.com>
Sender: owner-current@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

> >> >> > This assumes that the file system abstractions currently in place
> >> >> > change as well, since the /dev FS can't be mounted *after* the / FS
> >> >> > has been mounted as an inferior FS --
> >> >> why not?
> >> >> you don't need a mounted /dev to mount root.
> >> >> that's done specially.
> >> >
> >> >So you don't need a mounted root to have a mounted /dev, of course!
> >> 
> >>    That's silly. The root filesystem is mounted long before /dev would be,
 
> >
> >Not that long before.  /sbin/init will have to mount it to get in touch
> >with /dev/console, /dev/null and ...
> 
>    No, it will be mounted in the kernel.

ok, that is not really needed...

--
Poul-Henning Kamp           | phk@FreeBSD.ORG       FreeBSD Core-team.
http://www.freebsd.org/~phk | phk@login.dknet.dk    Private mailbox.
whois: [PHK]                | phk@ref.tfs.com       TRW Financial Systems, Inc.
Future will arrive by its own means, progress not so.

From owner-freebsd-current  Thu Mar 21 05:32:50 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id FAA26157
          for current-outgoing; Thu, 21 Mar 1996 05:32:50 -0800 (PST)
Received: from Root.COM (implode.Root.COM [198.145.90.17])
          by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id FAA26152
          for <current@freebsd.org>; Thu, 21 Mar 1996 05:32:48 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by Root.COM (8.6.12/8.6.5) with SMTP id FAA05288; Thu, 21 Mar 1996 05:31:11 -0800
Message-Id: <199603211331.FAA05288@Root.COM>
X-Authentication-Warning: implode.Root.COM: Host localhost didn't use HELO protocol
To: Poul-Henning Kamp <phk@critter.tfs.com>
cc: Terry Lambert <terry@lambert.org>, julian@ref.tfs.com (JULIAN Elischer),
        scrappy@ki.net, current@freebsd.org
Subject: Re: DEVFS vs "regular /dev" 
In-reply-to: Your message of "Thu, 21 Mar 1996 13:21:42 GMT."
             <625.827414502@critter.tfs.com> 
From: David Greenman <davidg@Root.COM>
Reply-To: davidg@Root.COM
Date: Thu, 21 Mar 1996 05:31:11 -0800
Sender: owner-current@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

>> >> >So you don't need a mounted root to have a mounted /dev, of course!
>> >> 
>> >>    That's silly. The root filesystem is mounted long before /dev would be,
> 
>> >
>> >Not that long before.  /sbin/init will have to mount it to get in touch
>> >with /dev/console, /dev/null and ...

   I just re-read what you said...I think you might have read what I wrote
backwards - the root filesystem is mounted automagically in the kernel very
early in system startup. /dev, whether it's done in the kernel or in
/sbin/init, would be done quite a bit later in relative terms.

>>    No, it will be mounted in the kernel.
>
>ok, that is not really needed...

   If we do the mount in /sbin/init and it fails for some reason (like the
mount point doesn't exist), then we'll have no way to inform the operator
(there isn't a /dev/console to write to). If we do it in the kernel, we can
emit a message saying "/dev: not found" or something.

-DG

David Greenman
Core-team/Principal Architect, The FreeBSD Project

From owner-freebsd-current  Thu Mar 21 05:34:20 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id FAA26210
          for current-outgoing; Thu, 21 Mar 1996 05:34:20 -0800 (PST)
Received: from tfs.com (tfs.com [140.145.250.1])
          by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id FAA26205
          for <current@freebsd.org>; Thu, 21 Mar 1996 05:34:19 -0800 (PST)
Received: from critter.tfs.com by tfs.com (smail3.1.28.1) with SMTP
	id m0tzkVN-0003wIC; Thu, 21 Mar 96 05:34 PST
Received: from localhost.tfs.com (localhost.tfs.com [127.0.0.1]) by critter.tfs.com (8.6.12/8.6.12) with SMTP id NAA00680; Thu, 21 Mar 1996 13:34:15 GMT
X-Authentication-Warning: critter.tfs.com: Host localhost.tfs.com didn't use HELO protocol
To: davidg@Root.COM
cc: Terry Lambert <terry@lambert.org>, julian@ref.tfs.com (JULIAN Elischer),
        scrappy@ki.net, current@freebsd.org
Subject: Re: DEVFS vs "regular /dev" 
In-reply-to: Your message of "Thu, 21 Mar 1996 05:31:11 PST."
             <199603211331.FAA05288@Root.COM> 
Date: Thu, 21 Mar 1996 05:34:14 -0800
Message-ID: <678.827415254@critter.tfs.com>
From: Poul-Henning Kamp <phk@critter.tfs.com>
Sender: owner-current@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

> >> >> >So you don't need a mounted root to have a mounted /dev, of course!
> >> >> 
> >> >>    That's silly. The root filesystem is mounted long before /dev would 
be,
> > 
> >> >
> >> >Not that long before.  /sbin/init will have to mount it to get in touch
> >> >with /dev/console, /dev/null and ...
> 
>    I just re-read what you said...I think you might have read what I wrote
> backwards - the root filesystem is mounted automagically in the kernel very
> early in system startup. /dev, whether it's done in the kernel or in
> /sbin/init, would be done quite a bit later in relative terms.
well, yes, "later" in relative terms, but not many actual seconds though :-)

>    If we do the mount in /sbin/init and it fails for some reason (like the
> mount point doesn't exist), then we'll have no way to inform the operator
> (there isn't a /dev/console to write to). If we do it in the kernel, we can
> emit a message saying "/dev: not found" or something.

I think sbin/init should be started with stdin+stdout pointing to console
for this and other reasons as well.

--
Poul-Henning Kamp           | phk@FreeBSD.ORG       FreeBSD Core-team.
http://www.freebsd.org/~phk | phk@login.dknet.dk    Private mailbox.
whois: [PHK]                | phk@ref.tfs.com       TRW Financial Systems, Inc.
Future will arrive by its own means, progress not so.

From owner-freebsd-current  Thu Mar 21 05:49:53 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id FAA27182
          for current-outgoing; Thu, 21 Mar 1996 05:49:53 -0800 (PST)
Received: from cocoa.ops.neosoft.com (root@cocoa.ops.neosoft.com [206.109.5.227])
          by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id FAA27174
          for <current@freebsd.org>; Thu, 21 Mar 1996 05:49:50 -0800 (PST)
Received: (from dbaker@localhost) by cocoa.ops.neosoft.com (8.7.5/8.6.12) id HAA03290; Thu, 21 Mar 1996 07:49:29 -0600 (CST)
Date: Thu, 21 Mar 1996 07:49:28 -0600 (CST)
From: Daniel Baker <dbaker@cocoa.ops.neosoft.com>
X-Sender: dbaker@cocoa.ops.neosoft.com
To: "matthew c. mead" <mmead@Glock.COM>
cc: current@freebsd.org
Subject: Re: lost+found ???
In-Reply-To: <199603210557.AAA00978@neon.Glock.COM>
Message-ID: <Pine.BSF.3.91.960321074854.330A-100000@cocoa.ops.neosoft.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-current@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

On Thu, 21 Mar 1996, matthew c. mead wrote:

>     I created most of my filesystems in 2.1.0R with the standard
> sysinstall newfs, but none of them have lost+found directories.
> After newfs'ing new drive partitions and such under -current,
> I've noticed none of them have lost+found directories either.
> What do I need to do?
I beleieve that the lost+found directories are only created when
needed..

Daniel

> 
> 
> 
> -matt
> 
> -- 
> Matthew C. Mead
> 
> mmead@Glock.COM
> http://www.Glock.COM/~mmead/
> 

     Daniel Baker - Daniel@Cuckoo.COM
"Uhhhhhhh, thank you, drive through please"


From owner-freebsd-current  Thu Mar 21 05:52:59 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id FAA27466
          for current-outgoing; Thu, 21 Mar 1996 05:52:59 -0800 (PST)
Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11])
          by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id FAA27454
          for <freebsd-current@FreeBSD.org>; Thu, 21 Mar 1996 05:52:42 -0800 (PST)
Received: from sax.sax.de by irz301.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id OAA23970 for <freebsd-current@FreeBSD.org>; Thu, 21 Mar 1996 14:50:47 +0100
Received: by sax.sax.de (8.6.11/8.6.12-s1) with UUCP
	id OAA22869 for freebsd-current@FreeBSD.org; Thu, 21 Mar 1996 14:50:46 +0100
Received: (from j@localhost) by uriah.heep.sax.de (8.7.4/8.6.9) id OAA13562 for freebsd-current@FreeBSD.org; Thu, 21 Mar 1996 14:32:19 +0100 (MET)
From: J Wunsch <j@uriah.heep.sax.de>
Message-Id: <199603211332.OAA13562@uriah.heep.sax.de>
Subject: Re: perl4
To: freebsd-current@FreeBSD.org (FreeBSD-current users)
Date: Thu, 21 Mar 1996 14:32:19 +0100 (MET)
In-Reply-To: <199603211056.CAA23624@GndRsh.aac.dev.com> from "Rodney W. Grimes" at Mar 21, 96 02:56:51 am
X-Phone: +49-351-2012 669
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

As Rodney W. Grimes wrote:

> > Btw., you've only checked for installed scripts.  Do also check out
> > the Makefiles.  I know that i've been using ``perl -e'' in some of the
> > Makefiles myself.
> 
> That particular things kinda makes my stomach turn, as it creates yet
> more cyclic dependincy trees that are very hard to break.  Think about
> what would happen if we did upgrade to perl5 in the base system and
> now our Makefiles with perl -e in them fall over because they need to
> be changed.  Instant cyclic build problem.

While i think that i've been using ``generic Perl'', i get your point.

However, i'm not sure at all whether it was in the base system, or
in a port only.  (I do own about 10 or so ports as well.)
-- 
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 Mar 21 07:33:58 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id HAA04370
          for current-outgoing; Thu, 21 Mar 1996 07:33:58 -0800 (PST)
Received: from localhost.cdrom.com (localhost.cdrom.com [127.0.0.1])
          by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id HAA04344
          Thu, 21 Mar 1996 07:33:48 -0800 (PST)
Message-Id: <199603211533.HAA04344@freefall.freebsd.org>
X-Authentication-Warning: freefall.freebsd.org: Host localhost.cdrom.com [127.0.0.1] didn't use HELO protocol
To: J Wunsch <j@uriah.heep.sax.de>
cc: freebsd-current@FreeBSD.org (FreeBSD-current users)
Subject: Re: lost+found ??? 
In-reply-to: Your message of "Thu, 21 Mar 1996 13:59:43 +0100."
             <199603211259.NAA13192@uriah.heep.sax.de> 
Date: Thu, 21 Mar 1996 07:33:47 -0800
From: "Justin T. Gibbs" <gibbs@freefall.freebsd.org>
Sender: owner-current@FreeBSD.org
X-Loop: FreeBSD.org
Precedence: bulk

>As Michael Smith wrote:
>
>> > What do I need to do?
>> 
>> Nothing, fsck creates them as it needs them.
>
>...thereby happily destroying arbitrary disk data if it has to extend
>the root directory and fails to find free space to do so.
>
>newfs should create it.

I agree.  Terry brought this up some time ago and I agreed with it then.

>-- 
>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 Mar 21 08:18:24 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id IAA16130
          for current-outgoing; Thu, 21 Mar 1996 08:18:24 -0800 (PST)
Received: from brasil.moneng.mei.com (brasil.moneng.mei.com [151.186.109.160])
          by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id IAA16098
          for <freebsd-current@FreeBSD.org>; Thu, 21 Mar 1996 08:18:15 -0800 (PST)
Received: (from jgreco@localhost) by brasil.moneng.mei.com (8.7.Beta.1/8.7.Beta.1) id KAA02561; Thu, 21 Mar 1996 10:13:51 -0600
From: Joe Greco <jgreco@brasil.moneng.mei.com>
Message-Id: <199603211613.KAA02561@brasil.moneng.mei.com>
Subject: Re: lost+found ???
To: j@uriah.heep.sax.de (J Wunsch)
Date: Thu, 21 Mar 1996 10:13:51 -0600 (CST)
Cc: freebsd-current@FreeBSD.org
In-Reply-To: <199603211259.NAA13192@uriah.heep.sax.de> from "J Wunsch" at Mar 21, 96 01:59:43 pm
X-Mailer: ELM [version 2.4 PL24]
Content-Type: text
Sender: owner-current@FreeBSD.org
X-Loop: FreeBSD.org
Precedence: bulk

> As Michael Smith wrote:
> 
> > > What do I need to do?
> > 
> > Nothing, fsck creates them as it needs them.
> 
> ...thereby happily destroying arbitrary disk data if it has to extend
> the root directory and fails to find free space to do so.
> 
> newfs should create it.

I gotta agree with this stand even though I hate lost+found directories
cluttering up my directory hierarchies....  :-)  oh, and Jordan, Suns create
lost+found at mkfs time - I'm looking at the source that does the deed. 

They _will_ also create it at fsck time if it does not exist, but it looks
like that's handled as an "unusual" condition.

... Joe

-------------------------------------------------------------------------------
Joe Greco - Systems Software Engineer, UNIX/Network Hacker, Etc.   414/362-3308
Marquette Electronics, Inc. - R&D - Milwaukee, WI                jgreco@mei.com

From owner-freebsd-current  Thu Mar 21 08:20:22 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id IAA16662
          for current-outgoing; Thu, 21 Mar 1996 08:20:22 -0800 (PST)
Received: from GndRsh.aac.dev.com (GndRsh.aac.dev.com [198.145.92.241])
          by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id IAA16630
          Thu, 21 Mar 1996 08:20:17 -0800 (PST)
Received: (from rgrimes@localhost) by GndRsh.aac.dev.com (8.6.12/8.6.12) id IAA23838; Thu, 21 Mar 1996 08:20:12 -0800
From: "Rodney W. Grimes" <rgrimes@GndRsh.aac.dev.com>
Message-Id: <199603211620.IAA23838@GndRsh.aac.dev.com>
Subject: Re: lost+found ???
To: gibbs@freefall.freebsd.org (Justin T. Gibbs)
Date: Thu, 21 Mar 1996 08:20:12 -0800 (PST)
Cc: j@uriah.heep.sax.de, freebsd-current@FreeBSD.org
In-Reply-To: <199603211533.HAA04344@freefall.freebsd.org> from "Justin T. Gibbs" at Mar 21, 96 07:33:47 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

> 
> >As Michael Smith wrote:
> >
> >> > What do I need to do?
> >> 
> >> Nothing, fsck creates them as it needs them.
> >
> >...thereby happily destroying arbitrary disk data if it has to extend
> >the root directory and fails to find free space to do so.
> >
> >newfs should create it.
> 
> I agree.  Terry brought this up some time ago and I agreed with it then.

I concur, the automagic stuff is fine as long as you never fill a disk,
which then just happens to causes some strange panic, which fsck then
goes to clean up and polity clobbers a root dir block while trying to
find space to create lost+found.  Not a pretty picture at all.... :-(


-- 
Rod Grimes                                      rgrimes@gndrsh.aac.dev.com
Accurate Automation Company                 Reliable computers for FreeBSD

From owner-freebsd-current  Thu Mar 21 08:20:31 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id IAA16709
          for current-outgoing; Thu, 21 Mar 1996 08:20:31 -0800 (PST)
Received: from GndRsh.aac.dev.com (GndRsh.aac.dev.com [198.145.92.241])
          by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id IAA16685
          for <current@FreeBSD.org>; Thu, 21 Mar 1996 08:20:26 -0800 (PST)
Received: (from rgrimes@localhost) by GndRsh.aac.dev.com (8.6.12/8.6.12) id IAA23813; Thu, 21 Mar 1996 08:16:42 -0800
From: "Rodney W. Grimes" <rgrimes@GndRsh.aac.dev.com>
Message-Id: <199603211616.IAA23813@GndRsh.aac.dev.com>
Subject: Re: DEVFS vs "regular /dev"
To: phk@critter.tfs.com (Poul-Henning Kamp)
Date: Thu, 21 Mar 1996 08:16:42 -0800 (PST)
Cc: davidg@Root.COM, terry@lambert.org, julian@ref.tfs.com, scrappy@ki.net,
        current@FreeBSD.org
In-Reply-To: <678.827415254@critter.tfs.com> from "Poul-Henning Kamp" at Mar 21, 96 05:34:14 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

> 
> > >> >> >So you don't need a mounted root to have a mounted /dev, of course!
> > >> >> 
> > >> >>    That's silly. The root filesystem is mounted long before /dev would 
> be,
> > > 
> > >> >
> > >> >Not that long before.  /sbin/init will have to mount it to get in touch
> > >> >with /dev/console, /dev/null and ...
> > 
> >    I just re-read what you said...I think you might have read what I wrote
> > backwards - the root filesystem is mounted automagically in the kernel very
> > early in system startup. /dev, whether it's done in the kernel or in
> > /sbin/init, would be done quite a bit later in relative terms.
> well, yes, "later" in relative terms, but not many actual seconds though :-)
> 
> >    If we do the mount in /sbin/init and it fails for some reason (like the
> > mount point doesn't exist), then we'll have no way to inform the operator
> > (there isn't a /dev/console to write to). If we do it in the kernel, we can
> > emit a message saying "/dev: not found" or something.
> 
> I think sbin/init should be started with stdin+stdout pointing to console
> for this and other reasons as well.

Try this (ONLY MAKE SURE YOU HAVE A WAY TO RECOVER) if you wish to see
the criticality of certain /dev/files:

rm /dev/log
rm /dev/klog
rm /dev/console
reboot

Now spend a hour or two trying to find out why the damn system hangs
right after mounting root.


-- 
Rod Grimes                                      rgrimes@gndrsh.aac.dev.com
Accurate Automation Company                 Reliable computers for FreeBSD

From owner-freebsd-current  Thu Mar 21 08:22:55 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id IAA17382
          for current-outgoing; Thu, 21 Mar 1996 08:22:55 -0800 (PST)
Received: from brasil.moneng.mei.com (brasil.moneng.mei.com [151.186.109.160])
          by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id IAA17362
          for <current@FreeBSD.org>; Thu, 21 Mar 1996 08:22:51 -0800 (PST)
Received: (from jgreco@localhost) by brasil.moneng.mei.com (8.7.Beta.1/8.7.Beta.1) id KAA02588; Thu, 21 Mar 1996 10:18:04 -0600
From: Joe Greco <jgreco@brasil.moneng.mei.com>
Message-Id: <199603211618.KAA02588@brasil.moneng.mei.com>
Subject: Re: DEVFS vs "regular /dev"
To: davidg@root.com
Date: Thu, 21 Mar 1996 10:17:54 -0600 (CST)
Cc: phk@critter.tfs.com, terry@lambert.org, julian@ref.tfs.com, scrappy@ki.net,
        current@FreeBSD.org
In-Reply-To: <199603211331.FAA05288@Root.COM> from "David Greenman" at Mar 21, 96 05:31:11 am
X-Mailer: ELM [version 2.4 PL24]
Content-Type: text
Sender: owner-current@FreeBSD.org
X-Loop: FreeBSD.org
Precedence: bulk

>    If we do the mount in /sbin/init and it fails for some reason (like the
> mount point doesn't exist), then we'll have no way to inform the operator
> (there isn't a /dev/console to write to). If we do it in the kernel, we can
> emit a message saying "/dev: not found" or something.

They just got through arguing this in NetBSD's port-sun3 list (folks tend to
forget to do the MAKEDEV every once in a while).  It would seem to me that a
little "special handling" for init would not be so bad, i.e. pass init file
descriptors 0, 1, and 2 already pointing at the console, so that the console
does not have to be accessible via the filesystem immediately.

I know that there is some "ugh" associated with this, but it would seem the
most robust method to provide USEFUL error trapping and reporting.

... Joe

-------------------------------------------------------------------------------
Joe Greco - Systems Administrator			      jgreco@ns.sol.net
Solaria Public Access UNIX - Milwaukee, WI			   414/546-7968

From owner-freebsd-current  Thu Mar 21 08:27:20 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id IAA18599
          for current-outgoing; Thu, 21 Mar 1996 08:27:20 -0800 (PST)
Received: from rocky.sri.MT.net (rocky.sri.MT.net [204.182.243.10])
          by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id IAA18560
          Thu, 21 Mar 1996 08:27:12 -0800 (PST)
Received: (from nate@localhost) by rocky.sri.MT.net (8.6.12/8.6.12) id JAA13464; Thu, 21 Mar 1996 09:29:16 -0700
Date: Thu, 21 Mar 1996 09:29:16 -0700
From: Nate Williams <nate@sri.MT.net>
Message-Id: <199603211629.JAA13464@rocky.sri.MT.net>
To: "Justin T. Gibbs" <gibbs@freefall.freebsd.org>
Cc: J Wunsch <j@uriah.heep.sax.de>,
        freebsd-current@FreeBSD.org (FreeBSD-current users)
Subject: Re: lost+found ??? 
In-Reply-To: <199603211533.HAA04344@freefall.freebsd.org>
References: <199603211259.NAA13192@uriah.heep.sax.de>
	<199603211533.HAA04344@freefall.freebsd.org>
Sender: owner-current@FreeBSD.org
X-Loop: FreeBSD.org
Precedence: bulk

> >> > What do I need to do?
> >> 
> >> Nothing, fsck creates them as it needs them.
> >
> >...thereby happily destroying arbitrary disk data if it has to extend
> >the root directory and fails to find free space to do so.
> >
> >newfs should create it.
> 
> I agree.  Terry brought this up some time ago and I agreed with it then.

If we want it, the code is all there for it.  Simply defined -DLOSTDIR
in the newfs Makefile.  Unfortunately, I'm not able to test it as my
'test' box is doing just that right now.



Nate

From owner-freebsd-current  Thu Mar 21 09:14:47 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id JAA01178
          for current-outgoing; Thu, 21 Mar 1996 09:14:47 -0800 (PST)
Received: from time.cdrom.com (time.cdrom.com [204.216.27.226])
          by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id JAA01163
          for <freebsd-current@FreeBSD.org>; Thu, 21 Mar 1996 09:14:44 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by time.cdrom.com (8.7.5/8.6.9) with SMTP id JAA14571; Thu, 21 Mar 1996 09:13:02 -0800 (PST)
To: Joe Greco <jgreco@brasil.moneng.mei.com>
cc: j@uriah.heep.sax.de (J Wunsch), freebsd-current@FreeBSD.org
Subject: Re: lost+found ??? 
In-reply-to: Your message of "Thu, 21 Mar 1996 10:13:51 CST."
             <199603211613.KAA02561@brasil.moneng.mei.com> 
Date: Thu, 21 Mar 1996 09:13:02 -0800
Message-ID: <14569.827428382@time.cdrom.com>
From: "Jordan K. Hubbard" <jkh@time.cdrom.com>
Sender: owner-current@FreeBSD.org
X-Loop: FreeBSD.org
Precedence: bulk

> They _will_ also create it at fsck time if it does not exist, but it looks
> like that's handled as an "unusual" condition.

Interesting, looks like I've frequently had this as an unusal
condition.. :-)

					Jordan

From owner-freebsd-current  Thu Mar 21 09:25:06 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id JAA04163
          for current-outgoing; Thu, 21 Mar 1996 09:25:06 -0800 (PST)
Received: from ref.tfs.com (ref.tfs.com [140.145.254.251])
          by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id JAA04150
          for <current@freebsd.org>; Thu, 21 Mar 1996 09:25:02 -0800 (PST)
Received: (from julian@localhost) by ref.tfs.com (8.7.3/8.6.9) id NAA17420; Wed, 20 Mar 1996 13:59:19 -0800 (PST)
Message-Id: <199603202159.NAA17420@ref.tfs.com>
Subject: Re: PATCH: small, syntax changes for devfs
To: scrappy@ki.net (Marc G. Fournier)
Date: Wed, 20 Mar 1996 13:59:19 -0800 (PST)
From: "JULIAN Elischer" <julian@ref.tfs.com>
Cc: current@freebsd.org
In-Reply-To: <Pine.BSF.3.91.960320162140.3864F-100000@ki.net> from "Marc G. Fournier" at Mar 20, 96 04:29:10 pm
X-Mailer: ELM [version 2.4 PL25 ME8b]
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 again...
> 
[...]
> 	Question...is it safe to put "printf" statements inside of the
> kernel in arbitrary places?  I'm trying to figure out why set_ds_labeldevs()
> isn't creating slice devices in /devfs, and figure that putting in a few
> extra printf's might help figure it out, but just wondering if this would
> break anything. :)
you can put printf's almost anywhere.
set_ds_labeldevs doesn't make nodes?
I seem to have all the nodes on my systems...


> 
> 
> 
>   	if (slice >= BASE_SLICE && sp->ds_bdev == NULL && sp->ds_size != 0) {
>   		mynor = minor(dkmodpart(dev, RAW_PART));
> ! 		sp->ds_bdev = 
> ! 			devfs_add_devswf(bdevsw, mynor, DV_BLK, 0, 0, 0640,
> ! 					 dsname(dname, unit, slice, RAW_PART,
> ! 					        partname));

better to use %s than just the string..
(what if we want a device with a % in it ? :)


> ! 		sp->ds_cdev = 
> ! 			devfs_add_devswf(cdevsw, mynor, DV_CHR, 0, 0, 0640, 
> ! 					 "r%s", dsname(dname, unit, slice, 
> ! 						       RAW_PART, partname));
>   	}
>   #endif
>   	if (sp->ds_label == NULL) {
looks great..

From owner-freebsd-current  Thu Mar 21 09:25:13 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id JAA04216
          for current-outgoing; Thu, 21 Mar 1996 09:25:13 -0800 (PST)
Received: from ref.tfs.com (ref.tfs.com [140.145.254.251])
          by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id JAA04171
          for <current@freebsd.org>; Thu, 21 Mar 1996 09:25:05 -0800 (PST)
Received: (from julian@localhost) by ref.tfs.com (8.7.3/8.6.9) id NAA17319; Wed, 20 Mar 1996 13:00:45 -0800 (PST)
Message-Id: <199603202100.NAA17319@ref.tfs.com>
Subject: Re: DEVFS vs "regular /dev"
To: terry@lambert.org (Terry Lambert)
Date: Wed, 20 Mar 1996 13:00:45 -0800 (PST)
From: "JULIAN Elischer" <julian@ref.tfs.com>
Cc: scrappy@ki.net, current@freebsd.org
In-Reply-To: <199603201933.MAA27577@phaeton.artisoft.com> from "Terry Lambert" at Mar 20, 96 12:33:42 pm
X-Mailer: ELM [version 2.4 PL25 ME8b]
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 good but one question.....

> 
> > 	Just curious, but what is the advantage (and disadvantage, if any?)
> > of using devfs vs "regular /dev"?  My first thought would be that its
> > memory based instead of file system based, giving better performance, but
> > that's just a guess.
> 
[.... tons of reasons ]

> 
> This assumes that the file system abstractions currently in place
> change as well, since the /dev FS can't be mounted *after* the / FS
> has been mounted as an inferior FS --
why not?
you don't need a mounted /dev to mount root.
that's done specially.

> the /dev has to be there as
> an overlay mount (translucent FS), and that means FS changes to allow
> translucence and to divorce volume mappings from the need for a mount
> point (basically, a shadow / and /dev on which the devfs /dev is mounted
> and the real / is mounted over top of the shadow /).

I think that's not needed

julian

From owner-freebsd-current  Thu Mar 21 09:53:52 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id JAA11560
          for current-outgoing; Thu, 21 Mar 1996 09:53:52 -0800 (PST)
Received: from brasil.moneng.mei.com (brasil.moneng.mei.com [151.186.109.160])
          by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id JAA11551
          for <freebsd-current@freebsd.org>; Thu, 21 Mar 1996 09:53:49 -0800 (PST)
Received: (from jgreco@localhost) by brasil.moneng.mei.com (8.7.Beta.1/8.7.Beta.1) id LAA02791; Thu, 21 Mar 1996 11:52:03 -0600
From: Joe Greco <jgreco@brasil.moneng.mei.com>
Message-Id: <199603211752.LAA02791@brasil.moneng.mei.com>
Subject: Re: lost+found ???
To: jkh@time.cdrom.com (Jordan K. Hubbard)
Date: Thu, 21 Mar 1996 11:52:03 -0600 (CST)
Cc: freebsd-current@freebsd.org
In-Reply-To: <14569.827428382@time.cdrom.com> from "Jordan K. Hubbard" at Mar 21, 96 09:13:02 am
X-Mailer: ELM [version 2.4 PL24]
Content-Type: text
Sender: owner-current@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

> > They _will_ also create it at fsck time if it does not exist, but it looks
> > like that's handled as an "unusual" condition.
> 
> Interesting, looks like I've frequently had this as an unusal
> condition.. :-)

Well, it IS this way under Solaris 2.4, and I am fairly sure that the same
behaviour is there under SunOS 4.1, and just about everything in between.

... Joe

-------------------------------------------------------------------------------
Joe Greco - Systems Administrator			      jgreco@ns.sol.net
Solaria Public Access UNIX - Milwaukee, WI			   414/546-7968

From owner-freebsd-current  Thu Mar 21 10:11:17 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id KAA14264
          for current-outgoing; Thu, 21 Mar 1996 10:11:17 -0800 (PST)
Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211])
          by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id KAA14230
          for <freebsd-current@freebsd.org>; Thu, 21 Mar 1996 10:10:58 -0800 (PST)
Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id KAA00406; Thu, 21 Mar 1996 10:58:04 -0700
From: Terry Lambert <terry@lambert.org>
Message-Id: <199603211758.KAA00406@phaeton.artisoft.com>
Subject: Re: lost+found ???
To: j@uriah.heep.sax.de (J Wunsch)
Date: Thu, 21 Mar 1996 10:58:03 -0700 (MST)
Cc: freebsd-current@freebsd.org
In-Reply-To: <199603211259.NAA13192@uriah.heep.sax.de> from "J Wunsch" at Mar 21, 96 01:59:43 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

> As Michael Smith wrote:
> 
> > > What do I need to do?
> > 
> > Nothing, fsck creates them as it needs them.
> 
> ...thereby happily destroying arbitrary disk data if it has to extend
> the root directory and fails to find free space to do so.
> 
> newfs should create it.

I argued this one and lost.  I think you are right, though, in the
basis that the files may be coming from directories with sufficient
free space, requiring additional directory blocks to be allocated
to recover name information.  Such blocks are not necessarily
freed by the process causing files to end up in lost+found.

Even in the case where blocks are freed, the names in lost+found
are based on the inode number and may cause less entries per block
than were in the block before the names were "lost" if the files all
had short names (ie: 3 characters or less is 8 bytes per name in
the directory entry block).

While we are on the subject, did anyone commit my fix so that fsck
doesn't have to be run twice in the case that it's creating lost+found?


					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 Mar 21 10:21:18 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id KAA15383
          for current-outgoing; Thu, 21 Mar 1996 10:21:18 -0800 (PST)
Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211])
          by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id KAA15376
          for <current@FreeBSD.org>; Thu, 21 Mar 1996 10:21:13 -0800 (PST)
Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id LAA00435; Thu, 21 Mar 1996 11:09:47 -0700
From: Terry Lambert <terry@lambert.org>
Message-Id: <199603211809.LAA00435@phaeton.artisoft.com>
Subject: Re: DEVFS vs "regular /dev"
To: jgreco@brasil.moneng.mei.com (Joe Greco)
Date: Thu, 21 Mar 1996 11:09:47 -0700 (MST)
Cc: davidg@root.com, phk@critter.tfs.com, terry@lambert.org,
        julian@ref.tfs.com, scrappy@ki.net, current@FreeBSD.org
In-Reply-To: <199603211618.KAA02588@brasil.moneng.mei.com> from "Joe Greco" at Mar 21, 96 10:17:54 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

> >    If we do the mount in /sbin/init and it fails for some reason (like the
> > mount point doesn't exist), then we'll have no way to inform the operator
> > (there isn't a /dev/console to write to). If we do it in the kernel, we can
> > emit a message saying "/dev: not found" or something.
> 
> They just got through arguing this in NetBSD's port-sun3 list (folks tend to
> forget to do the MAKEDEV every once in a while).  It would seem to me that a
> little "special handling" for init would not be so bad, i.e. pass init file
> descriptors 0, 1, and 2 already pointing at the console, so that the console
> does not have to be accessible via the filesystem immediately.
> 
> I know that there is some "ugh" associated with this, but it would seem the
> most robust method to provide USEFUL error trapping and reporting.

OR

Provide a file system to mount as "/" that has a "/dev" directory
in it as part of devfs, and mount it before mounting root (and mount
root over top of the "/" portion of it using a translucent mount).

Then you don't need a mount point and you don't need to special case
all this crap for init...

This would be an easy change for devfs itself, and the root mount
changes I've already submitted allow the overlay.


					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 Mar 21 10:22:52 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id KAA15545
          for current-outgoing; Thu, 21 Mar 1996 10:22:52 -0800 (PST)
Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211])
          by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id KAA15503
          for <freebsd-current@FreeBSD.org>; Thu, 21 Mar 1996 10:22:24 -0800 (PST)
Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id LAA00425; Thu, 21 Mar 1996 11:05:48 -0700
From: Terry Lambert <terry@lambert.org>
Message-Id: <199603211805.LAA00425@phaeton.artisoft.com>
Subject: Re: lost+found ???
To: jkh@time.cdrom.com (Jordan K. Hubbard)
Date: Thu, 21 Mar 1996 11:05:48 -0700 (MST)
Cc: jgreco@brasil.moneng.mei.com, j@uriah.heep.sax.de,
        freebsd-current@FreeBSD.org
In-Reply-To: <14569.827428382@time.cdrom.com> from "Jordan K. Hubbard" at Mar 21, 96 09:13:02 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

> > They _will_ also create it at fsck time if it does not exist, but it looks
> > like that's handled as an "unusual" condition.
> 
> Interesting, looks like I've frequently had this as an unusal
> condition.. :-)

The problem, of course, is that deleting files in lost+found will
truncate back the size of the directory, to a minimum of 512 bytes,
if you remove the things from the lost+found.

The lost+found creation makes an 8k directory, but the first time you
use it and do something about the recovered files, it's back down to
512 bytes (the directory block size).

Traditionally, the directory has been pegged at 8k of allocated blocks
to ensure that there is some place to put at least 8k of directory
entries.  This is probably too small for modern file system sizes
any more.  8-(.

That's it's considered "unusual" is proven by the need to run fsck
again (my fsck patch simply maintains the correct link count for
the create case -- something that wasn't, apparently, tested ever
before, since it was an '"unusual" condition').


					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 Mar 21 10:30:31 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id KAA16315
          for current-outgoing; Thu, 21 Mar 1996 10:30:31 -0800 (PST)
Received: from austin.polstra.com (austin.polstra.com [206.213.73.10])
          by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id KAA16308
          for <freebsd-current@freebsd.org>; Thu, 21 Mar 1996 10:30:28 -0800 (PST)
Received: from austin.polstra.com (jdp@localhost) by austin.polstra.com (8.6.12/8.6.12) with ESMTP id KAA16203 for <freebsd-current@freebsd.org>; Thu, 21 Mar 1996 10:30:28 -0800
Message-Id: <199603211830.KAA16203@austin.polstra.com>
To: freebsd-current@freebsd.org
Subject: GNU accepts FreeBSD/ELF binutils changes
Date: Thu, 21 Mar 1996 10:30:28 -0800
From: John Polstra <jdp@polstra.com>
Sender: owner-current@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

Good news!  GNU has accepted my binutils changes for FreeBSD/ELF.

> I have applied versions of the binutils patches to the development
> sources.  Thanks.  The top level config.sub file is really part of the
> gcc distribution.
> 
> Ian Taylor
> ian@cygnus.com

I haven't heard from them yet about the gcc changes.
--
   John Polstra                                       jdp@polstra.com
   John D. Polstra & Co., Inc.                Seattle, Washington USA
   "Self-knowledge is always bad news."                 -- John Barth

From owner-freebsd-current  Thu Mar 21 10:32:10 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id KAA16527
          for current-outgoing; Thu, 21 Mar 1996 10:32:10 -0800 (PST)
Received: from precipice.shockwave.com (precipice.shockwave.com [171.69.108.33])
          by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id KAA16520
          Thu, 21 Mar 1996 10:32:08 -0800 (PST)
Received: from localhost.shockwave.com (localhost.shockwave.com [127.0.0.1]) by precipice.shockwave.com (8.7.4/8.7.3) with SMTP id KAA02241; Thu, 21 Mar 1996 10:32:01 -0800 (PST)
Message-Id: <199603211832.KAA02241@precipice.shockwave.com>
To: sos@FreeBSD.org
cc: imp@village.org (Warner Losh), current@FreeBSD.org
From: Paul Traina <pst@FreeBSD.org>
Subject: Re: Native & Linux ELF support finally there... 
In-reply-to: Your message of "Thu, 21 Mar 1996 09:02:11 +0100."
             <199603210802.JAA07135@ra.dkuug.dk> 
Date: Thu, 21 Mar 1996 10:32:01 -0800
Sender: owner-current@FreeBSD.org
X-Loop: FreeBSD.org
Precedence: bulk


  From: sos@FreeBSD.org
  Subject: Re: Native & Linux ELF support finally there...
  
  "Tired of that linux system ?? well, just copy our kernel ontop
  of the old one..."

The strength of BSD over Linux for most users is /not/ the kernel.
Most Linux users are quite happy with their ugly mess of a kernel,
and would find our kernel far inferior (what?  config(1)?  what's that?).

Our strength is the consistency of our kernel and binaries working
together in harmony,  forming a unified front that will crush the
geneticly impure Linux systems.  All we need is living room!

FreeBSD has ushered in a third generation of UNIX which will last a
thousand years!

One UNIX.  One Operating System.  Forever.

Paul Traina
Minister of Propoganda^H^H^H^H^H^H^H^H^HInformation

p.s. :-)  No offense to the people who found themselves inconvienced by
	  the last person spouting that line.

From owner-freebsd-current  Thu Mar 21 10:43:50 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id KAA17911
          for current-outgoing; Thu, 21 Mar 1996 10:43:50 -0800 (PST)
Received: from rover.village.org (rover.village.org [204.144.255.49])
          by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id KAA17905
          Thu, 21 Mar 1996 10:43:45 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by rover.village.org (8.6.11/8.6.6) with SMTP id LAA12425; Thu, 21 Mar 1996 11:43:43 -0700
Message-Id: <199603211843.LAA12425@rover.village.org>
To: Paul Traina <pst@FreeBSD.org>
Subject: Re: Native & Linux ELF support finally there... 
Cc: sos@FreeBSD.org, current@FreeBSD.org
In-reply-to: Your message of Thu, 21 Mar 1996 10:32:01 PST
Date: Thu, 21 Mar 1996 11:43:43 -0700
From: Warner Losh <imp@village.org>
Sender: owner-current@FreeBSD.org
X-Loop: FreeBSD.org
Precedence: bulk

: The strength of BSD over Linux for most users is /not/ the kernel.
: Most Linux users are quite happy with their ugly mess of a kernel,
: and would find our kernel far inferior (what?  config(1)?  what's that?).

I hate the Linux config system, but their X gui thing is kinda cool.
I wish that I could have released OI on FreeBSD, since I had a crude
config tool there that made config(1)able files.  The tool is, alas,
long since gone due to job changes.

: Our strength is the consistency of our kernel and binaries working
: together in harmony,  forming a unified front that will crush the
: geneticly impure Linux systems.  All we need is living room!

That goes without saying.  The person that I talked to about this was
interested in testing out FreeBSD in a low impact way as a transient
step to the greater goal of replacing the Linux machine with a FreeBDS
one.

I'm going to have to try this when I get my new SuSE Linux CDroms in a
few days.  Evidentally, they have a complete ELF system on them. :-)

Warner

From owner-freebsd-current  Thu Mar 21 10:47:23 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id KAA18120
          for current-outgoing; Thu, 21 Mar 1996 10:47:23 -0800 (PST)
Received: from ki.net (root@ki.net [142.77.249.8])
          by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id KAA18113
          for <current@FreeBSD.org>; Thu, 21 Mar 1996 10:46:57 -0800 (PST)
Received: (from scrappy@localhost) by ki.net (8.7.4/8.7.4) id NAA29541; Thu, 21 Mar 1996 13:45:31 -0500 (EST)
Date: Thu, 21 Mar 1996 13:45:30 -0500 (EST)
From: "Marc G. Fournier" <scrappy@ki.net>
To: "Rodney W. Grimes" <rgrimes@GndRsh.aac.dev.com>
cc: current@FreeBSD.org
Subject: Re: DEVFS vs "regular /dev"
In-Reply-To: <199603211616.IAA23813@GndRsh.aac.dev.com>
Message-ID: <Pine.BSF.3.91.960321134250.29201C-100000@ki.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-current@FreeBSD.org
X-Loop: FreeBSD.org
Precedence: bulk

On Thu, 21 Mar 1996, Rodney W. Grimes wrote:

> rm /dev/log
> rm /dev/klog

	Since I don't really want to find out I'm wrong by actually
testing this...but so far as I can tell, /dev/log and /dev/klog are used
by syslogd only.

	When I started doing the modifications to the devfs code, /dev/klog
wasn't being created, yet the system was booting up to a login prompt without
any problems.  As well, /dev/log itself was being created as a device instead
of as a socket, again causing syslogd to not run, but not seeming to affect
anything else.

Marc G. Fournier | POP Mail  Telnet Acct  DNS Hosting
System           |  WWW Services   Database Services  | Knowledge, 
  Administrator  |                                    | Information and
 scrappy@ki.net  |      WWW: http://www.ki.net        | Communications, Inc


From owner-freebsd-current  Thu Mar 21 10:55:22 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id KAA18547
          for current-outgoing; Thu, 21 Mar 1996 10:55:22 -0800 (PST)
Received: from precipice.shockwave.com (precipice.shockwave.com [171.69.108.33])
          by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id KAA18542
          for <freebsd-current@freebsd.org>; Thu, 21 Mar 1996 10:55:17 -0800 (PST)
Received: from localhost.shockwave.com (localhost.shockwave.com [127.0.0.1]) by precipice.shockwave.com (8.7.4/8.7.3) with SMTP id KAA02362; Thu, 21 Mar 1996 10:53:50 -0800 (PST)
Message-Id: <199603211853.KAA02362@precipice.shockwave.com>
To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch)
cc: freebsd-current@freebsd.org (FreeBSD-current users)
Subject: Re: perl4 
In-reply-to: Your message of "Wed, 20 Mar 1996 10:13:13 +0100."
             <199603200913.KAA07672@uriah.heep.sax.de> 
Date: Thu, 21 Mar 1996 10:53:50 -0800
From: Paul Traina <pst@shockwave.com>
Sender: owner-current@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk


  From: J Wunsch <j@uriah.heep.sax.de>
  Subject: Re: perl4
  As Paul Traina wrote:
  
  >  By the way, which is inherantly
  > broken when executed as any sort of script.  It needs to be a shell builtin
  > or it needs to die.
  
  Huh?  #!/bin/sh, #!/bin/csh aren't shell builtins either.  In fact,
  all these scripts are acceptable to execve(2), and the shell won't
  even notice the difference to a binary executable.

I know that, that's not what I said.  Let me repeat myself:

	"By the way, which is inherantly broken when executed as _any_ sort of
	 a script.  It needs to be a shell builtin or it needs to die."

which(1) needs to be a shell builtin, not a sh script, not a csh script, not
a perl script, (and not a binary) to work properly.

From owner-freebsd-current  Thu Mar 21 10:55:33 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id KAA18585
          for current-outgoing; Thu, 21 Mar 1996 10:55:33 -0800 (PST)
Received: from rocky.sri.MT.net (rocky.sri.MT.net [204.182.243.10])
          by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id KAA18566
          Thu, 21 Mar 1996 10:55:28 -0800 (PST)
Received: (from nate@localhost) by rocky.sri.MT.net (8.6.12/8.6.12) id LAA14008; Thu, 21 Mar 1996 11:58:19 -0700
Date: Thu, 21 Mar 1996 11:58:19 -0700
From: Nate Williams <nate@sri.MT.net>
Message-Id: <199603211858.LAA14008@rocky.sri.MT.net>
To: stable@FreeBSD.org, current@FreeBSD.org
CC: hosokawa@mt.cs.keio.ac.jp
Subject: Laptop users take notice
Sender: owner-current@FreeBSD.org
X-Loop: FreeBSD.org
Precedence: bulk

I'd like to start a 'freebsd-mobile' mailing lists for users of laptops,
notebooks, and other mobile users of FreeBSD.  I'm starting on the home
stretch for getting APM support working, and the next stage will be
finishing up the PC-CARD support, but I'm going to need some more
testers soon.

What we have now is a pretty good framework based on the work
Poul-Henning and the BSD Nomads group have done, but it needs to be
filled in.  Most of the code to fill it in exists, but needs to be
thought out, integrated, and tested.

My status on the project is that yesterday I got APM suspend/resume
working on my box, so I need to do a bit more cleanup and testing of the
APM driver, and then I need some folks to test and review these fixes
before I commit them.

My proposed schedule for committing code to the tree: (Notice no dates. :)
1) Finish and clean up the APM support
2) Bring in some of the recent PC-CARD patches from the Nomads
3) Bring in and cleanup the user-land patches from the Nomads
4) Tweak the /etc config files as necessary
5) Bring in the driver modifications for PCCARD support

I'm more than willing to change my schedule, or let anyone else do the
work, but I have an advantage/disadvantage in that I *have* to get this
working for a project for my employer.  The advantage is that I have
time, the disadvantage is that I have a deadline coming up which means I
won't be able to use as much on-the-clock time in a few weeks.

Also, if necessary I can make patches against -current and -stable
(preferrable -stable since that's what I'm running) of all of the above
in order to get people jump-started.

What I'm looking for:
1) Laptop or notebook owners who can test patches
2) Folks interested in this area to give feedback

What I'm not looking for:
1) People who want to throw out the existing interface for something new
2) People who are willing to make suggestions without doing a bit of
   work to help out.

Most of us are stretched pretty thin as it is, but I think getting
PC-CARD support in FreeBSD would be a great feather in our cap, and I
believe we have the existing framework is adequate for now.

I'm willing to co-ordinate the work, and I'm hoping that the patches I
generate will be tested fairly well (I have access to 2 different
laptops most of the time), but no guarantees.

Send me email, and if there is enough interest we can get the postmaster
to setup a mailing list on freefall.

Thanks!


Nate

From owner-freebsd-current  Thu Mar 21 10:56:29 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id KAA18763
          for current-outgoing; Thu, 21 Mar 1996 10:56:29 -0800 (PST)
Received: from perki.connect.com.au (perki.connect.com.au [192.189.54.5])
          by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id KAA18758
          for <current@freefall.freebsd.org>; Thu, 21 Mar 1996 10:56:26 -0800 (PST)
Received: (from Unemeton@localhost) by perki.connect.com.au id FAA10441
  (8.6.12/IDA-1.6); Fri, 22 Mar 1996 05:55:31 +1100
>Received: from localhost (giles@localhost [127.0.0.1]) by nemeton.com.au (8.6.12/8.6.9) with SMTP id TAA05488; Thu, 21 Mar 1996 19:32:02 +1100
Message-Id: <199603210832.TAA05488@nemeton.com.au>
To: bmk@transport.com
Subject: Re: perl4 
In-reply-to: <199603202241.OAA02668@dtr.com> 
Date: Thu, 21 Mar 1996 19:32:01 +1100
From: Giles Lean <giles@nemeton.com.au>
Content-Type: text
Sender: owner-current@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk


On Wed, 20 Mar 1996 14:41:45 -0800 (PST)  "Brant M. Katkansky" wrote:

> * Leave things the way they are, and keep perl4 as the standard perl.
> Perl5 can be installed in /usr/local as a package.
> 

Do this, but rename /usr/bin/perl to /usr/bin/perl4 (and symlink it to
/usr/bin/perl5.036 -- what happened to that?).

Then the FreeBSD scripts in /usr/bin etc can invoke #! /usr/bin/perl4
and a user installing perl5 into /usr/local/bin won't be surprised.

This solution "works" for our existing scripts, doesn't bloat the
distribution and looks less out of date since we're clearly shipping
perl4 on purpose.

User scripts with #! /usr/bin/perl won't work until something is done;
we might need a "use perl4 or install perl5" sort of script as
/usr/bin/perl for one release.

Giles


From owner-freebsd-current  Thu Mar 21 10:57:13 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id KAA18796
          for current-outgoing; Thu, 21 Mar 1996 10:57:13 -0800 (PST)
Received: from GndRsh.aac.dev.com (GndRsh.aac.dev.com [198.145.92.241])
          by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id KAA18791
          for <current@FreeBSD.org>; Thu, 21 Mar 1996 10:57:10 -0800 (PST)
Received: (from rgrimes@localhost) by GndRsh.aac.dev.com (8.6.12/8.6.12) id KAA24142; Thu, 21 Mar 1996 10:56:31 -0800
From: "Rodney W. Grimes" <rgrimes@GndRsh.aac.dev.com>
Message-Id: <199603211856.KAA24142@GndRsh.aac.dev.com>
Subject: Re: DEVFS vs "regular /dev"
To: scrappy@ki.net (Marc G. Fournier)
Date: Thu, 21 Mar 1996 10:56:31 -0800 (PST)
Cc: current@FreeBSD.org
In-Reply-To: <Pine.BSF.3.91.960321134250.29201C-100000@ki.net> from "Marc G. Fournier" at Mar 21, 96 01:45:30 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

> 
> On Thu, 21 Mar 1996, Rodney W. Grimes wrote:
> 
> > rm /dev/log
> > rm /dev/klog
> 
> 	Since I don't really want to find out I'm wrong by actually
> testing this...but so far as I can tell, /dev/log and /dev/klog are used
> by syslogd only.
> 
> 	When I started doing the modifications to the devfs code, /dev/klog
> wasn't being created, yet the system was booting up to a login prompt without
> any problems.  As well, /dev/log itself was being created as a device instead
> of as a socket, again causing syslogd to not run, but not seeming to affect
> anything else.

These problems may have been corrected.  I do know for certain that certain
/dev/ entries missing causes the system to hang very early in init, and you
can not even get up single user to fix it.  This _needs_ fixed badly, you
should be able to
rm -r /dev
reboot
and get the system up single user, if not you have a chicken and egg
problem as to how to repair a damaged or loss /dev tree.


-- 
Rod Grimes                                      rgrimes@gndrsh.aac.dev.com
Accurate Automation Company                 Reliable computers for FreeBSD

From owner-freebsd-current  Thu Mar 21 11:13:23 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id LAA19439
          for current-outgoing; Thu, 21 Mar 1996 11:13:23 -0800 (PST)
Received: from ki.net (root@ki.net [142.77.249.8])
          by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id LAA19431
          for <current@FreeBSD.org>; Thu, 21 Mar 1996 11:13:10 -0800 (PST)
Received: (from scrappy@localhost) by ki.net (8.7.4/8.7.4) id OAA00208; Thu, 21 Mar 1996 14:12:45 -0500 (EST)
Date: Thu, 21 Mar 1996 14:12:44 -0500 (EST)
From: "Marc G. Fournier" <scrappy@ki.net>
To: "Rodney W. Grimes" <rgrimes@GndRsh.aac.dev.com>
cc: current@FreeBSD.org
Subject: Re: DEVFS vs "regular /dev"
In-Reply-To: <199603211856.KAA24142@GndRsh.aac.dev.com>
Message-ID: <Pine.BSF.3.91.960321141107.29201D-100000@ki.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-current@FreeBSD.org
X-Loop: FreeBSD.org
Precedence: bulk

On Thu, 21 Mar 1996, Rodney W. Grimes wrote:

> These problems may have been corrected.  I do know for certain that certain
> /dev/ entries missing causes the system to hang very early in init, and you
> can not even get up single user to fix it.  This _needs_ fixed badly, you
> should be able to
> rm -r /dev
> reboot
> and get the system up single user, if not you have a chicken and egg
> problem as to how to repair a damaged or loss /dev tree.
>
	That's what got me started playing with the DEVFS code.  I figured
I'd try to boot the system using devfs instead of the "normal /dev", and
found that /dev/ttyv* wasn't being created, so I couldn't login.  I've got
my system now to the point that I could do 'rm -r /dev' and be able to book
without any problems.

Marc G. Fournier | POP Mail  Telnet Acct  DNS Hosting
System           |  WWW Services   Database Services  | Knowledge, 
  Administrator  |                                    | Information and
 scrappy@ki.net  |      WWW: http://www.ki.net        | Communications, Inc


From owner-freebsd-current  Thu Mar 21 11:21:15 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id LAA19732
          for current-outgoing; Thu, 21 Mar 1996 11:21:15 -0800 (PST)
Received: from ibp.ibp.fr (ibp.ibp.fr [132.227.60.30])
          by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id LAA19727
          for <current@FreeBSD.org>; Thu, 21 Mar 1996 11:21:12 -0800 (PST)
Received: from blaise.ibp.fr (blaise.ibp.fr [132.227.60.1])
	by ibp.ibp.fr (8.6.12/jtpda-5.0) with ESMTP id UAA18764
	; Thu, 21 Mar 1996 20:21:07 +0100
Received: from (uucp@localhost)
	by blaise.ibp.fr (8.6.12/jtpda-5.0) with UUCP id UAA03947
	; Thu, 21 Mar 1996 20:21:06 +0100
Received: (from roberto@localhost) by keltia.freenix.fr (8.7.5/keltia-uucp-2.7) id TAA13224; Thu, 21 Mar 1996 19:48:54 +0100 (MET)
From: Ollivier Robert <roberto@keltia.freenix.fr>
Message-Id: <199603211848.TAA13224@keltia.freenix.fr>
Subject: Re: lost+found ???
To: mark@grondar.za (Mark Murray)
Date: Thu, 21 Mar 1996 19:48:53 +0100 (MET)
Cc: mmead@Glock.COM, current@FreeBSD.org
In-Reply-To: <199603210743.JAA17704@grumble.grondar.za> from Mark Murray at "Mar 21, 96 09:43:54 am"
X-Operating-System: FreeBSD 2.2-CURRENT ctm#1788
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

It seems that Mark Murray said:
> # mkdir lost+found

inode #3  used to be  --  and still is  in several  Unixes -- reserved  for
lost+found  directories, populated   at _newfs_  fime,   not by fsck.  That
enable fsck  to save recovered  inodes  even if  the  fs is full (directory
entries are pre-created too). 

Why don't we use the same  method as anyone ? Is  there a _good_ reason not
to do it at newfs time ?
-- 
Ollivier ROBERT    -=- The daemon is FREE! -=-    roberto@keltia.frmug.fr.net
   FreeBSD keltia.freenix.fr 2.2-CURRENT #7: Mon Mar 18 21:28:18 MET 1996

From owner-freebsd-current  Thu Mar 21 11:54:12 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id LAA20890
          for current-outgoing; Thu, 21 Mar 1996 11:54:12 -0800 (PST)
Received: from precipice.shockwave.com (precipice.shockwave.com [171.69.108.33])
          by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id LAA20885
          Thu, 21 Mar 1996 11:54:07 -0800 (PST)
Received: from localhost.shockwave.com (localhost.shockwave.com [127.0.0.1]) by precipice.shockwave.com (8.7.4/8.7.3) with SMTP id LAA02727; Thu, 21 Mar 1996 11:54:05 -0800 (PST)
Message-Id: <199603211954.LAA02727@precipice.shockwave.com>
To: freebsd-hubs@freebsd.org, jkh@freebsd.org
Cc: hackers@freebsd.org, current@freebsd.org
Subject: Re: new sup server 
In-reply-to: Your message of "Wed, 20 Mar 1996 07:34:25 PST."
             <Pine.SUN.3.91.960320073226.1731A-100000@picea.FSL.ORST.EDU> 
Date: Thu, 21 Mar 1996 11:54:05 -0800
From: Paul Traina <pst@shockwave.com>
Sender: owner-current@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

If you run a mirror and are NOT on freebsd-hubs, get your butt on there
please.

Freefall updates its trees at 1:00, 7:00, 13:00, and 19:00 pacific time.
It makes sense for other mirrors to attempt to start SUP operations
at least an HOUR after Freefall /starts/ its update, to insure it has
completed.

sup2's schedule is currently 2:10, 8:10, 14:10, and 20:10,  4 times a day.

I would suggest that we coordinate as follows, to avoid overloading the T1
to freefall:

Here's my proposal, it's just a proposal, feel free to improve upon it.

----------------------------------------------------------------------------

SUP windows start 1 hour + ((your mirror number - 1) * 10 minutes).

e.g.  [ALL TIMES PACIFIC TIME]

	sup2	2:10	8;10	13:10	20:10
	sup3	2:20	8:20	13:20	20:20
	sup4	2:30	8:30	13:30	20:30
	sup5	2:40	8:40	13:40	20:40
	sup6	2:50	8:50	13:50	20:50

4 times a day may be excessive, in which case, pick 1 two or 3 times.
/Preferably/ we should work with our adjacent neighbors to do the right
thing.  If you want to sup outside the 100 minute window (assuming 10
mirrors) then do it whenever you want.  This is just to avoid contention
for that precious time right after freefall does its updates.

Here's an example of neighbor coordination, in the following example,
sup3 and sup4 choose sup windows that would cause them to never overlap.

	sup2	2:10	8;10	13:10	20:10		4x
	sup3	2:20		13:20			2x
	sup4		8:30	13:30			2x
	sup5	2:40	8:40		20:40		3x
	sup6			13:50			1x

----------------------------------------------------------------------------

I would /strongly/ reccomend people in general avoid the "on the hour"
timeslot (except for sup7).

I suspect that Jordan will be trimming off sup's from non-official-mirror
sites real soon now to reduce the load on freefall and the T1.

Ministry of Information

From owner-freebsd-current  Thu Mar 21 13:42:38 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id NAA14075
          for current-outgoing; Thu, 21 Mar 1996 13:42:38 -0800 (PST)
Received: from skynet.ctr.columbia.edu (skynet.ctr.columbia.edu [128.59.64.70])
          by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id NAA14000
          for <current@freebsd.org>; Thu, 21 Mar 1996 13:42:31 -0800 (PST)
Received: (from wpaul@localhost) by skynet.ctr.columbia.edu (8.6.12/8.6.9) id QAA13188; Thu, 21 Mar 1996 16:42:20 -0500
From: Bill Paul <wpaul@skynet.ctr.columbia.edu>
Message-Id: <199603212142.QAA13188@skynet.ctr.columbia.edu>
Subject: flock() and chroot()
To: current@freebsd.org
Date: Thu, 21 Mar 1996 16:42:19 -0500 (EST)
Cc: wpaul@skynet.ctr.columbia.edu (Bill Paul)
X-Mailer: ELM [version 2.4 PL24]
Content-Type: text
Sender: owner-current@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

I've got a question concerning file locking:

I got a bug report recently from a guy trying to use NIS inside a
chroot()ed environment. Apparently he's created a filesystem tree
which has the real /var and /dev mounted in it (I'm not sure how he
did this since he neglected to provide details -- I've asked him
to elaborate) and has set up a guest user that is placed in this
confined environment at login.

In this environment, _yp_dobind() fails, which breaks NIS client
facilities. The point where is breaks is:

        if ((lfd = open(YPBINDLOCK, O_RDONLY)) == -1)
                return(YPERR_YPBIND);
        errno = 0;
        switch (flock(lfd, LOCK_EX|LOCK_NB) == -1 && errno == EWOULDBLOCK) {
        case 0:
                close(lfd);
                return (YPERR_YPBIND);
                break;
        case 1:
        default:
                close(lfd);
                break;
        }

What's happening here is that _yp_dobind() is trying to establish
an exclusive lock on /var/run/ypbind.lock. This file should already
be exclusively locked by ypbind, so the attempt should fail with
EWOULDBLOCK. If this happens, _yp_dobind() then knows that ypbind
is actually running and falls through to the rest of the routine,
otherwise it bails.

In this case, the flock() is actually succeeding even though ypbind is
running. I think this is because ypbind has flock()ed /var/run/ypbind.lock
whereas _yp_dobind() is trying to flock() $CHROOT/var/run/ypbind.lock.
The question is: is this the correct behavior? On the one hand, since
$CHROOT/var/run/ypbind.lock is located under a different mount point,
it seems reasonable to assume that the kernel is refering to it using
a different filesystem object than /var/run/ypbind.lock. On the other
hand, they are both the same file. On the third hand, chroot() confuses
the whole matter even further.

I can fix this particular problem by looking for ypbind in a different
way (you can verify that an RPC server is running by poking at its
NULLPROC procedure and seeing if it responds), but I'd still like to
know if the observed flock() behavior is bogus or not.

Note that all this is happening with FreeBSD-current:

FreeBSD 2.2-960212-CURRENT #0: Fri Mar 15 14:52:11 CST 1996

-Bill

-- 
=============================================================================
-Bill Paul            (212) 854-6020 | System Manager
Work:         wpaul@ctr.columbia.edu | Center for Telecommunications Research
Home:  wpaul@skynet.ctr.columbia.edu | Columbia University, New York City
=============================================================================
License error: The license for this .sig file has expired. You must obtain
a new license key before any more witty phrases will appear in this space.
=============================================================================

From owner-freebsd-current  Thu Mar 21 14:09:26 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id OAA18407
          for current-outgoing; Thu, 21 Mar 1996 14:09:26 -0800 (PST)
Received: from mail.think.com (Mail1.Think.COM [131.239.33.245])
          by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id OAA18400
          for <current@freefall.freebsd.org>; Thu, 21 Mar 1996 14:09:23 -0800 (PST)
Received: from Early-Bird-1.Think.COM by mail.think.com; Thu, 21 Mar 96 17:09:14 -0500
Received: from compound (fergus-26.dialup.cfa.org) by Early-Bird.Think.COM; Thu, 21 Mar 96 17:09:11 EST
Received: (from alk@localhost) by compound (8.6.12/8.6.112) id QAA00889; Thu, 21 Mar 1996 16:10:14 -0600
Date: Thu, 21 Mar 1996 16:10:14 -0600
Message-Id: <199603212210.QAA00889@compound>
From: Tony Kimball <alk@Think.COM>
To: current@freefall.freebsd.org
Subject: Re: new sup server
Sender: owner-current@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk


   From: Paul Traina <pst@shockwave.com>
   Date: Thu, 21 Mar 1996 11:54:05 -0800
   Subject: Re: new sup server 

   I would suggest that we coordinate as follows, to avoid overloading the T1
   to freefall:

This won't do as much good as it should, unless the mirrors work for
those as point at them.  I mentioned this on -questions, but perhaps
it bears repeating, that *only* freefall is working for me
using the 2.1R client.  I suspect the mirrors are running newer
versions of the server (although I have not investigated at length).

sup -v sup5.current
SUP 8.26 (4.3 BSD) for file sup5.current at Mar 21 15:32:28
SUP: Read error on network: Connection reset by peer
SUP: Network write timed out
SUP Upgrade of src-base-current at Thu Mar 21 15:44:31 1996
SUP: Error reading signon reply from fileserver

Similarly sup2, sup3, while sup4 refuses connections with perfect
consistency to date.

From owner-freebsd-current  Thu Mar 21 14:53:23 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id OAA22100
          for current-outgoing; Thu, 21 Mar 1996 14:53:23 -0800 (PST)
Received: (from dima@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id OAA22066
          Thu, 21 Mar 1996 14:53:14 -0800 (PST)
Message-Id: <199603212253.OAA22066@freefall.freebsd.org>
Subject: Re: new sup server
To: pst@shockwave.com (Paul Traina)
Date: Thu, 21 Mar 1996 14:53:13 -0800 (PST)
Cc: freebsd-hubs@FreeBSD.org, jkh@FreeBSD.org, hackers@FreeBSD.org,
        current@FreeBSD.org
In-Reply-To: <199603211954.LAA02727@precipice.shockwave.com> from "Paul Traina" at Mar 21, 96 11:54:05 am
From: dima@FreeBSD.org (Dima Ruban)
X-Class: Fast
Organization: HackerDome
X-Mailer: ELM [version 2.4 PL24]
Content-Type: text
Sender: owner-current@FreeBSD.org
X-Loop: FreeBSD.org
Precedence: bulk

Paul Traina writes:
> 
> If you run a mirror and are NOT on freebsd-hubs, get your butt on there
> please.
> 
> Freefall updates its trees at 1:00, 7:00, 13:00, and 19:00 pacific time.
> It makes sense for other mirrors to attempt to start SUP operations

It does make sence. I have only one question. How long does it 
usualy take to upgrade freefall? one hour, two, three?

> at least an HOUR after Freefall /starts/ its update, to insure it has
> completed.

Do you think, one hour would be enough?

> sup2's schedule is currently 2:10, 8:10, 14:10, and 20:10,  4 times a day.
> 
> I would suggest that we coordinate as follows, to avoid overloading the T1
> to freefall:
> 
> Here's my proposal, it's just a proposal, feel free to improve upon it.
> 
> ----------------------------------------------------------------------------
> 
> SUP windows start 1 hour + ((your mirror number - 1) * 10 minutes).
> 
> e.g.  [ALL TIMES PACIFIC TIME]
> 
> 	sup2	2:10	8;10	13:10	20:10
> 	sup3	2:20	8:20	13:20	20:20
> 	sup4	2:30	8:30	13:30	20:30
> 	sup5	2:40	8:40	13:40	20:40

I'll set up my server to update information at 2:40 and 13:40.

> 	sup6	2:50	8:50	13:50	20:50
> 
> 4 times a day may be excessive, in which case, pick 1 two or 3 times.
> /Preferably/ we should work with our adjacent neighbors to do the right
> thing.  If you want to sup outside the 100 minute window (assuming 10
> mirrors) then do it whenever you want.  This is just to avoid contention
> for that precious time right after freefall does its updates.
> 
> Here's an example of neighbor coordination, in the following example,
> sup3 and sup4 choose sup windows that would cause them to never overlap.
> 
> 	sup2	2:10	8;10	13:10	20:10		4x
> 	sup3	2:20		13:20			2x
> 	sup4		8:30	13:30			2x
> 	sup5	2:40	8:40		20:40		3x

deal. I've increased 2x -> 3x.
Now I have 40 2,8,20 * * *

> 	sup6			13:50			1x
> 
> ----------------------------------------------------------------------------
> 
> I would /strongly/ reccomend people in general avoid the "on the hour"
> timeslot (except for sup7).
> 
> I suspect that Jordan will be trimming off sup's from non-official-mirror
> sites real soon now to reduce the load on freefall and the T1.

Absolutely agreed.

> 
> Ministry of Information
> 

-- dima

From owner-freebsd-current  Thu Mar 21 14:55:51 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id OAA22235
          for current-outgoing; Thu, 21 Mar 1996 14:55:51 -0800 (PST)
Received: (from dima@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id OAA22228
          Thu, 21 Mar 1996 14:55:49 -0800 (PST)
Message-Id: <199603212255.OAA22228@freefall.freebsd.org>
Subject: Re: new sup server
To: alk@Think.COM (Tony Kimball)
Date: Thu, 21 Mar 1996 14:55:49 -0800 (PST)
Cc: current@freefall.freebsd.org
In-Reply-To: <199603212210.QAA00889@compound> from "Tony Kimball" at Mar 21, 96 04:10:14 pm
From: dima@FreeBSD.ORG (Dima Ruban)
X-Class: Fast
Organization: HackerDome
X-Mailer: ELM [version 2.4 PL24]
Content-Type: text
Sender: owner-current@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

Tony Kimball writes:
> 
> 
>    From: Paul Traina <pst@shockwave.com>
>    Date: Thu, 21 Mar 1996 11:54:05 -0800
>    Subject: Re: new sup server 
> 
>    I would suggest that we coordinate as follows, to avoid overloading the T1
>    to freefall:
> 
> This won't do as much good as it should, unless the mirrors work for
> those as point at them.  I mentioned this on -questions, but perhaps
> it bears repeating, that *only* freefall is working for me
> using the 2.1R client.  I suspect the mirrors are running newer
> versions of the server (although I have not investigated at length).
> 
> sup -v sup5.current
> SUP 8.26 (4.3 BSD) for file sup5.current at Mar 21 15:32:28

Probably you have to upgrade sup client? (to 9.x)

> SUP: Read error on network: Connection reset by peer
> SUP: Network write timed out
> SUP Upgrade of src-base-current at Thu Mar 21 15:44:31 1996
> SUP: Error reading signon reply from fileserver
> 
> Similarly sup2, sup3, while sup4 refuses connections with perfect
> consistency to date.
> 

-- dima

From owner-freebsd-current  Thu Mar 21 15:13:58 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id PAA23421
          for current-outgoing; Thu, 21 Mar 1996 15:13:58 -0800 (PST)
Received: from mail.think.com (Mail1.Think.COM [131.239.33.245])
          by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id PAA23406
          for <current@freefall.freebsd.org>; Thu, 21 Mar 1996 15:13:51 -0800 (PST)
Received: from Early-Bird-1.Think.COM by mail.think.com; Thu, 21 Mar 96 18:13:41 -0500
Received: from compound (fergus-26.dialup.cfa.org) by Early-Bird.Think.COM; Thu, 21 Mar 96 18:13:38 EST
Received: (from alk@localhost) by compound (8.6.12/8.6.112) id RAA01294; Thu, 21 Mar 1996 17:14:41 -0600
Date: Thu, 21 Mar 1996 17:14:41 -0600
Message-Id: <199603212314.RAA01294@compound>
From: Tony Kimball <alk@Think.COM>
To: dima@FreeBSD.ORG
Cc: current@freefall.freebsd.org
In-Reply-To: <199603212255.OAA22228@freefall.freebsd.org> (dima@FreeBSD.ORG)
Subject: Re: new sup server
Sender: owner-current@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk


   Probably you have to upgrade sup client? (to 9.x)

Indeed, so I have inferred, pending verification.  Perhaps I should
also make explicit a further inference and an observation: Under
this hypothesis, there will be a lot of folks doing this since the sup
servers break against the release client.  Therefore, the mirrors are
not doing the trick of offloading for any but present -current users.
Moreover, it is considered standard practice (for good reason) to
change the port when changing protocols.



From owner-freebsd-current  Thu Mar 21 15:21:31 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id PAA23980
          for current-outgoing; Thu, 21 Mar 1996 15:21:31 -0800 (PST)
Received: from gauss.math.purdue.edu (gauss.math.purdue.edu [128.210.21.2])
          by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id PAA23961
          for <current@freefall.freebsd.org>; Thu, 21 Mar 1996 15:21:27 -0800 (PST)
Received: from hopf.math.purdue.edu (freebsd@hopf.math.purdue.edu [128.210.3.18]) by gauss.math.purdue.edu (8.7.4/Purdue_Math) with ESMTP id SAA27942 for <current@freefall.freebsd.org>; Thu, 21 Mar 1996 18:21:25 -0500 (EST)
Received: (from freebsd@localhost) by hopf.math.purdue.edu (8.7.1/8.6.11) id SAA07486 for current@freefall.freebsd.org; Thu, 21 Mar 1996 18:21:22 -0500 (EST)
Date: Thu, 21 Mar 1996 18:21:22 -0500 (EST)
From: Clarence Wilkerson <freebsd@hopf.math.purdue.edu>
Message-Id: <199603212321.SAA07486@hopf.math.purdue.edu>
To: current@freefall.freebsd.org
Subject: Adaptec 1542B and 1522 on current kernels
Sender: owner-current@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk


My kernels are going into a stall and debug mode when trying to
boot on a 486DX4 with either a 1542B or 1522 installed for the taoe
and cdrom drive ( filesystems on ide drives).

At the point where it says waiting for scsi devices to settle, it hangs for a
awhile, then says device is frozen and then drops into some debug
mode.

The adapters work under DOS, Linux, and NextStep.....

Help
Clarence

From owner-freebsd-current  Thu Mar 21 15:23:23 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id PAA24164
          for current-outgoing; Thu, 21 Mar 1996 15:23:23 -0800 (PST)
Received: from mail.cs.tu-berlin.de (root@mail.cs.tu-berlin.de [130.149.17.13])
          by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id PAA24147
          for <freebsd-current@freebsd.org>; Thu, 21 Mar 1996 15:23:12 -0800 (PST)
Received: from caramba.cs.tu-berlin.de (wosch@caramba.cs.tu-berlin.de [130.149.17.12]) by mail.cs.tu-berlin.de (8.6.12/8.6.12) with ESMTP id AAA06988; Fri, 22 Mar 1996 00:02:53 +0100
Received: (from wosch@localhost) by campa.panke.de (8.6.9/8.6.9) id WAA00319; Thu, 21 Mar 1996 22:50:38 +0100
Date: Thu, 21 Mar 1996 22:50:38 +0100
From: Wolfram Schneider <wosch@cs.tu-berlin.de>
Message-Id: <199603212150.WAA00319@campa.panke.de>
To: scott@statsci.com, freebsd-current@freebsd.org
In-reply-to: Scott Blachowicz's message of Wed, 20 Mar 1996 11:24:52 -0800
Subject: Re: perl4
Reply-to: Wolfram Schneider <wosch@cs.tu-berlin.de>
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

3In article <m0tzTV8-000r3sC@main.statsci.com> Scott Blachowicz <scott@statsci.com> writes:

>> > By the way, which is inherantly broken when executed as any sort of
>> > script.  It needs to be a shell builtin or it needs to die.

>I think the point was more that if you define the purpose of 'which' to be
>"tell me what would be run if I use this command", then it has to be a
>shell builtin in order to find shell-local functions and aliases.

Sometimes you need a non-interactive which(1). FreeBSD use which in
bsd.port.mk. Not all shells have a builtin 'which' or the shells use
an other name for which (bash -> type). Our programs should not depend
on non-standardized shell builtins.

Wolfram 

From owner-freebsd-current  Thu Mar 21 15:23:27 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id PAA24181
          for current-outgoing; Thu, 21 Mar 1996 15:23:27 -0800 (PST)
Received: from mail.cs.tu-berlin.de (root@mail.cs.tu-berlin.de [130.149.17.13])
          by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id PAA24165
          for <current@freebsd.org>; Thu, 21 Mar 1996 15:23:23 -0800 (PST)
Received: from caramba.cs.tu-berlin.de (wosch@caramba.cs.tu-berlin.de [130.149.17.12]) by mail.cs.tu-berlin.de (8.6.12/8.6.12) with ESMTP id AAA06991; Fri, 22 Mar 1996 00:02:56 +0100
Received: (from wosch@localhost) by campa.panke.de (8.6.9/8.6.9) id WAA00335; Thu, 21 Mar 1996 22:53:53 +0100
Date: Thu, 21 Mar 1996 22:53:53 +0100
From: Wolfram Schneider <wosch@cs.tu-berlin.de>
Message-Id: <199603212153.WAA00335@campa.panke.de>
To: Tony Kimball <alk@Think.COM>
CC: current@freebsd.org
In-reply-to: Tony Kimball's message of Tue, 19 Mar 1996 16:39:06 -0600
Subject: Re: perl4
Reply-to: Wolfram Schneider <wosch@cs.tu-berlin.de>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
References: <199603192239.QAA18506@compound>
Sender: owner-current@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

In article <199603192239.QAA18506@compound> Tony Kimball <alk@Think.COM> writes:

>So remove them both from the base distribution.  p4 can be made a
>package at zero-maintenance cost.  How much breaks, and how hard is
>it to fix?
>
>./bin/makewhatis: a /usr/bin/perl script text
>./bin/catman: a /usr/bin/perl script text
>./bin/killall: a /usr/bin/perl script text
>./bin/sgmlfmt: a /usr/bin/perl script text
>./bin/which: a /usr/bin/perl script text
>./sbin/adduser: a /usr/bin/perl script text
>./sbin/kbdmap: a /usr/bin/perl script text
>./sbin/vidfont: a /usr/bin/perl script text
>./sbin/spkrtest: a /usr/bin/perl script text
>
>Not much.  Eliminate it, and that reduces the installed base OS size
>by 4MB, meaning more installations, more market share, better
>differentiation from bloated commercial systems.

4MB? Guess 100K.

Wolfram

From owner-freebsd-current  Thu Mar 21 15:51:11 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id PAA26564
          for current-outgoing; Thu, 21 Mar 1996 15:51:11 -0800 (PST)
Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11])
          by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id PAA26516
          for <freebsd-current@FreeBSD.org>; Thu, 21 Mar 1996 15:50:50 -0800 (PST)
Received: from sax.sax.de by irz301.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id AAA12351 for <freebsd-current@FreeBSD.org>; Fri, 22 Mar 1996 00:50:42 +0100
Received: by sax.sax.de (8.6.11/8.6.12-s1) with UUCP
	id AAA28379 for freebsd-current@FreeBSD.org; Fri, 22 Mar 1996 00:50:41 +0100
Received: (from j@localhost) by uriah.heep.sax.de (8.7.4/8.6.9) id AAA14621 for freebsd-current@FreeBSD.org; Fri, 22 Mar 1996 00:42:28 +0100 (MET)
From: J Wunsch <j@uriah.heep.sax.de>
Message-Id: <199603212342.AAA14621@uriah.heep.sax.de>
Subject: Re: lost+found ???
To: freebsd-current@FreeBSD.org (FreeBSD-current users)
Date: Fri, 22 Mar 1996 00:42:27 +0100 (MET)
Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch)
In-Reply-To: <199603211629.JAA13464@rocky.sri.MT.net> from "Nate Williams" at Mar 21, 96 09:29:16 am
X-Phone: +49-351-2012 669
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

As Nate Williams wrote:

> If we want it, the code is all there for it.  Simply defined -DLOSTDIR
> in the newfs Makefile.  Unfortunately, I'm not able to test it as my
> 'test' box is doing just that right now.

Horribly broken. :-(

A few required tweaks aside to get it compiled at all:


j@uriah 1097% ./newfs -t0 -u0 -i65536 -l1 /dev/rfd0
/dev/rfd0:      2880 sectors in 80 cylinders of 2 tracks, 18 sectors
        1.4MB in 5 cyl groups (16 c/g, 0.28MB/g, 32 i/g)
super-block backups (for fsck -b #) at:
 32, 632, 1184, 1784, 2336,
write error: 72
wtfs: Bad address

but:

j@uriah 1098% /sbin/newfs -t0 -u0 -i65536 -l1 /dev/rfd0
/dev/rfd0:      2880 sectors in 80 cylinders of 2 tracks, 18 sectors
        1.4MB in 5 cyl groups (16 c/g, 0.28MB/g, 32 i/g)
super-block backups (for fsck -b #) at:
 32, 632, 1184, 1784, 2336,

-- 
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 Mar 21 16:04:48 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id QAA27400
          for current-outgoing; Thu, 21 Mar 1996 16:04:48 -0800 (PST)
Received: from time.cdrom.com (time.cdrom.com [204.216.27.226])
          by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id QAA27395
          Thu, 21 Mar 1996 16:04:46 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by time.cdrom.com (8.7.5/8.6.9) with SMTP id QAA01346; Thu, 21 Mar 1996 16:04:26 -0800 (PST)
To: Paul Traina <pst@shockwave.com>
cc: freebsd-hubs@freebsd.org, jkh@freebsd.org, hackers@freebsd.org,
        current@freebsd.org
Subject: Re: new sup server 
In-reply-to: Your message of "Thu, 21 Mar 1996 11:54:05 PST."
             <199603211954.LAA02727@precipice.shockwave.com> 
Date: Thu, 21 Mar 1996 16:04:26 -0800
Message-ID: <1344.827453066@time.cdrom.com>
From: "Jordan K. Hubbard" <jkh@time.cdrom.com>
Sender: owner-current@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

> I suspect that Jordan will be trimming off sup's from non-official-mirror
> sites real soon now to reduce the load on freefall and the T1.

You suspect correctly.  This is a fine proposal and I urge everyone
here to heed the Call of Paul.

> Ministry of Information

If you really want to adopt that title, it's all yours.  Just don't
forget that you get to take poison with the rest of us, come the
bitter end. :-)

From owner-freebsd-current  Thu Mar 21 17:48:18 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id RAA04116
          for current-outgoing; Thu, 21 Mar 1996 17:48:18 -0800 (PST)
Received: from who.cdrom.com (who.cdrom.com [204.216.27.3])
          by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id RAA04079
          Thu, 21 Mar 1996 17:48:10 -0800 (PST)
Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211])
          by who.cdrom.com (8.6.12/8.6.11) with ESMTP id RAA21435
          ; Thu, 21 Mar 1996 17:45:44 -0800
Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id SAA01606; Thu, 21 Mar 1996 18:35:00 -0700
From: Terry Lambert <terry@lambert.org>
Message-Id: <199603220135.SAA01606@phaeton.artisoft.com>
Subject: Re: new sup server
To: jkh@time.cdrom.com (Jordan K. Hubbard)
Date: Thu, 21 Mar 1996 18:35:00 -0700 (MST)
Cc: pst@shockwave.com, freebsd-hubs@FreeBSD.org, jkh@FreeBSD.org,
        hackers@FreeBSD.org, current@FreeBSD.org
In-Reply-To: <1344.827453066@time.cdrom.com> from "Jordan K. Hubbard" at Mar 21, 96 04:04:26 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 you really want to adopt that title, it's all yours.  Just don't
> forget that you get to take poison with the rest of us, come the
> bitter end. :-)

Boo.  Hiss.  Bad self-referential sentence there, Jordan... stick
to the puns.  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  Thu Mar 21 19:47:11 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id TAA10378
          for current-outgoing; Thu, 21 Mar 1996 19:47:11 -0800 (PST)
Received: from fw.ast.com (fw.ast.com [165.164.6.25])
          by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id TAA10373
          for <current@freebsd.org>; Thu, 21 Mar 1996 19:47:08 -0800 (PST)
Received: from nemesis by fw.ast.com with uucp
	(Smail3.1.29.1 #3) id m0tzxjh-00084cC; Thu, 21 Mar 96 21:41 CST
Received: by nemesis.lonestar.org (Smail3.1.27.1 #20)
	id m0tzxgp-000CzFC; Thu, 21 Mar 96 21:38 WET
Message-Id: <m0tzxgp-000CzFC@nemesis.lonestar.org>
Date: Thu, 21 Mar 96 21:38 WET
To: current@freebsd.org
From: uhclem@nemesis.lonestar.org (Frank Durda IV)
Sent: Thu Mar 21 1996, 21:38:58 CST
Subject: Re: lost+found 
Sender: owner-current@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

[0]    I created most of my filesystems in 2.1.0R with the standard
[0]sysinstall newfs, but none of them have lost+found directories.
[0]After newfs'ing new drive partitions and such under -current,
[0]I've noticed none of them have lost+found directories either.
[0]What do I need to do?

[1]Nothing, fsck creates them as it needs them.

That's what I thought until a recent crash and fsck was unable
to create lost+found or did not try.  The end result was that
I had to get a DOS disk block zapper and rename "tmp" to "lost+found"
so that fsck would be happy and quit deleting entire directories at
great speed.  The failure seemed to spring up when you had an unreferenced
directory rather than an unreferenced file.   It seems like it remembers
to make lost+found when recovering an unreferenced file.

Perhaps there were more serious problems with the file system in my case.

Now I routinely create lost+found and lost-found so that I can
easily make one out of the other in case lost+found gets nuked by the
crash.  And yes, this all happened on 2.1.0.

Frank Durda IV <uhclem@nemesis.lonestar.org>|"The Knights who say "LETNi"
or uhclem%nemesis@rwsystr.nkn.net           | demand...  A SEGMENT REGISTER!!!"
					    |"A what?"
or ...letni!rwsys!nemesis!uhclem	    |"LETNi! LETNi! LETNi!"  - 1983


From owner-freebsd-current  Thu Mar 21 21:05:19 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id VAA14689
          for current-outgoing; Thu, 21 Mar 1996 21:05:19 -0800 (PST)
Received: from fw.ast.com (fw.ast.com [165.164.6.25])
          by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id VAA14668
          Thu, 21 Mar 1996 21:05:14 -0800 (PST)
Received: from nemesis by fw.ast.com with uucp
	(Smail3.1.29.1 #3) id m0tzyN2-0007zaC; Thu, 21 Mar 96 22:22 CST
Received: by nemesis.lonestar.org (Smail3.1.27.1 #20)
	id m0tzyJE-000D1jC; Thu, 21 Mar 96 22:18 WET
Message-Id: <m0tzyJE-000D1jC@nemesis.lonestar.org>
Date: Thu, 21 Mar 96 22:18 WET
To: hackers@freebsd.org, current@freebsd.org
From: uhclem@nemesis.lonestar.org (Frank Durda IV)
Sent: Thu Mar 21 1996, 22:18:39 CST
Subject: Crash advice needed (long) APPENDIX A
Cc: uhclem@nemesis.lonestar.org
Sender: owner-current@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

A few minutes after my first long-winded explanation of the crashes
I have been having, another crash occurred.  I was typing away on screen
4 when the console went dead (no response in vi) and the disks quit
chattering.  I switched over to screen 1 and found a panic display.

I began to copy it down, but the message quickly scrolled off the
screen due to repeated messages from the SCSI driver.  
(Gripe! there needs to be a way to prevent this.)

Here are the highlights I was able to record:

Fatal tray 12 page fault while in kernel mode
Virtual address 0x10
IP at 0xf0195d3c  (exact address as the crash earlier today, somewhere
		   in Xintr15 and IRQ 15 is used by SCSI on this system)

syncing disks
sd0(aha0:0:0:) timed out:
adapter not taking commands.. frozen?!
Debugger("aha1542") called		(this system has a 1540B)
AGAIN
aha0: MBO 02 and not 00 (free)
These last few lines repeat every ten seconds or so until I got
tired of looking at them and pressed RESET.

(I have seen this MBO 02 and not 00 (free) message on a 1542C
 controller at work when it is talking to a WangDat tape drive.
 Sometimes this system also gets a "NO SENSE" message and
 will claim the tape drive is not ready (it is ready) or busy (it isn't).
 Solution on that system: turn everything off and back on and everyone
 is happy.  Unfortunately, cycling power does not improve things here.)

I hope this helps provide a clue.  Note also on this system that
the bulk of disk I/O occurs on the SCSI drive since news, uucp and
mail all have their spools there and it was quite busy when this
crash occurred.   The IDE was hardly ticking over.

Frank Durda IV <uhclem@nemesis.lonestar.org>|Chief Dalek: "The supreme council
or uhclem%nemesis@rwsystr.nkn.net           | has ordered that London 
					    | destroyed with fire bombs."
or ...letni!rwsys!nemesis!uhclem	    |Peon Dalek: "I obey.  Do you
					      want fries with that?"


From owner-freebsd-current  Thu Mar 21 22:28:38 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id WAA18488
          for current-outgoing; Thu, 21 Mar 1996 22:28:38 -0800 (PST)
Received: from VX23.CC.MONASH.EDU.AU (vx23.cc.monash.edu.au [130.194.1.23])
          by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id WAA18471
          Thu, 21 Mar 1996 22:28:28 -0800 (PST)
Received: from moa.cc.monash.edu.au (george@moa.cc.monash.edu.au)
 by vaxc.cc.monash.edu.au (PMDF V5.0-6 #16291)
 id <01I2NBBLYBLO9I5GGI@vaxc.cc.monash.edu.au>; Fri, 22 Mar 1996 17:27:52 +1100
Received: (george@localhost) by moa.cc.monash.edu.au (8.6.10/8.6.4)
 id QAA17304; Fri, 22 Mar 1996 16:27:50 +1000
Date: Fri, 22 Mar 1996 16:27:50 +1000
From: George Scott <George.Scott@cc.monash.edu.au>
Subject: Re:  Crash advice needed (long) APPENDIX A
To: current@freebsd.org, hackers@freebsd.org
Cc: uhclem@nemesis.lonestar.org
Message-id: <199603220627.QAA17304@moa.cc.monash.edu.au>
MIME-version: 1.0
Content-type: TEXT/PLAIN
Content-transfer-encoding: 7BIT
Sender: owner-current@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

> sd0(aha0:0:0:) timed out:
> adapter not taking commands.. frozen?!
> Debugger("aha1542") called		(this system has a 1540B)
> AGAIN
> aha0: MBO 02 and not 00 (free)
> These last few lines repeat every ten seconds or so until I got
> tired of looking at them and pressed RESET.
> 
> (I have seen this MBO 02 and not 00 (free) message on a 1542C
>  controller at work when it is talking to a WangDat tape drive.
>  Sometimes this system also gets a "NO SENSE" message and
>  will claim the tape drive is not ready (it is ready) or busy (it isn't).
>  Solution on that system: turn everything off and back on and everyone
>  is happy.  Unfortunately, cycling power does not improve things here.)

I had this frequently under 2.1.0-RELEASE on a '486 with an AHA-1542CP (with
the P stuff disabled).

I had 5 drives on the external connector and 2 on the internal and noticed
that the time outs stopped happening when I disconnected either the external
or internal drives, so I figured bus length as the cause.  It was over 20'
so I shortened it as much as I could (to 16' if I remember) but the problems
still occured.

I ended up putting the internal drives on a spare AVA-1515 I had waiting for
another project and haven't had one problem since.

George.

From owner-freebsd-current  Thu Mar 21 23:21:46 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id XAA21038
          for current-outgoing; Thu, 21 Mar 1996 23:21:46 -0800 (PST)
Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19])
          by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id XAA21033
          for <current@FreeBSD.org>; Thu, 21 Mar 1996 23:21:42 -0800 (PST)
Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.12/8.6.9) id SAA24449; Fri, 22 Mar 1996 18:16:51 +1100
Date: Fri, 22 Mar 1996 18:16:51 +1100
From: Bruce Evans <bde@zeta.org.au>
Message-Id: <199603220716.SAA24449@godzilla.zeta.org.au>
To: bde@zeta.org.au, phk@critter.tfs.com
Subject: Re: PATCH: small, syntax changes for devfs
Cc: current@FreeBSD.org, julian@ref.tfs.com, scrappy@ki.net
Sender: owner-current@FreeBSD.org
X-Loop: FreeBSD.org
Precedence: bulk

>> - names for partitions aren't generated unless the slice containing the
>>   partitions or at least one partition on that slice is open.  I'm not
>>   sure if they should be generated; anyway, this isn't implemented.
>and since wd0s1 isn't there either, how can you trigger that ?
>I belive all sensible slices/partitions should appear in /devfs by default,
>so that you can just fsck them from fstab...

wd0s1 is there, and opening it would reveal wd0s1[a-h], but this isn't
much use.  Perhaps wd0s1 should be a directory containing [a-h].  I
prefer a flat namespace.

Bruce

From owner-freebsd-current  Fri Mar 22 00:16:04 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id AAA22914
          for current-outgoing; Fri, 22 Mar 1996 00:16:04 -0800 (PST)
Received: from GndRsh.aac.dev.com (GndRsh.aac.dev.com [198.145.92.241])
          by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id AAA22869
          Fri, 22 Mar 1996 00:15:54 -0800 (PST)
Received: (from rgrimes@localhost) by GndRsh.aac.dev.com (8.6.12/8.6.12) id AAA25003; Fri, 22 Mar 1996 00:14:38 -0800
From: "Rodney W. Grimes" <rgrimes@GndRsh.aac.dev.com>
Message-Id: <199603220814.AAA25003@GndRsh.aac.dev.com>
Subject: Re: Crash advice needed (long) APPENDIX A
To: George.Scott@cc.monash.edu.au (George Scott)
Date: Fri, 22 Mar 1996 00:14:38 -0800 (PST)
Cc: current@freebsd.org, hackers@freebsd.org, uhclem@nemesis.lonestar.org
In-Reply-To: <199603220627.QAA17304@moa.cc.monash.edu.au> from "George Scott" at Mar 22, 96 04:27:50 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

> 
> > sd0(aha0:0:0:) timed out:
> > adapter not taking commands.. frozen?!
> > Debugger("aha1542") called		(this system has a 1540B)
> > AGAIN
> > aha0: MBO 02 and not 00 (free)
> > These last few lines repeat every ten seconds or so until I got
> > tired of looking at them and pressed RESET.
> > 
> > (I have seen this MBO 02 and not 00 (free) message on a 1542C
> >  controller at work when it is talking to a WangDat tape drive.
> >  Sometimes this system also gets a "NO SENSE" message and
> >  will claim the tape drive is not ready (it is ready) or busy (it isn't).
> >  Solution on that system: turn everything off and back on and everyone
> >  is happy.  Unfortunately, cycling power does not improve things here.)
> 
> I had this frequently under 2.1.0-RELEASE on a '486 with an AHA-1542CP (with
> the P stuff disabled).
> 
> I had 5 drives on the external connector and 2 on the internal and noticed
> that the time outs stopped happening when I disconnected either the external
> or internal drives, so I figured bus length as the cause.  It was over 20'
> so I shortened it as much as I could (to 16' if I remember) but the problems
> still occured.
> 
> I ended up putting the internal drives on a spare AVA-1515 I had waiting for
> another project and haven't had one problem since.

Thought the first person here is running a 1540B which is not a fast scsi-ii
controller, I can fully see why George was having a problem, and why it
went away.  The 1542CP _is_ a fast scsi-ii device and I suspect you had
some fast devices (>5MHz) on there.  When running fast scsi-ii it is very
hard to get away with a cable chain longer than 3 meters (~10 feet) and
you had better be using active termination and _high_ quality cables.

I can just see the problems comming when Ultra SCSI 20Mhz starts becoming
popular as that will often require a total cable length on the order of
1.5 meter tops unless you pay extra special attention to the fact that
this becomes a high frequency transmission line and must be treated us such.

-- 
Rod Grimes                                      rgrimes@gndrsh.aac.dev.com
Accurate Automation Company                 Reliable computers for FreeBSD

From owner-freebsd-current  Fri Mar 22 00:51:30 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id AAA24063
          for current-outgoing; Fri, 22 Mar 1996 00:51:30 -0800 (PST)
Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11])
          by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id AAA24053
          for <freebsd-current@FreeBSD.org>; Fri, 22 Mar 1996 00:51:25 -0800 (PST)
Received: from sax.sax.de by irz301.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id JAA04123 for <freebsd-current@FreeBSD.org>; Fri, 22 Mar 1996 09:50:51 +0100
Received: by sax.sax.de (8.6.11/8.6.12-s1) with UUCP
	id JAA03145 for freebsd-current@FreeBSD.org; Fri, 22 Mar 1996 09:50:51 +0100
Received: (from j@localhost) by uriah.heep.sax.de (8.7.4/8.6.9) id JAA17469 for freebsd-current@FreeBSD.org; Fri, 22 Mar 1996 09:08:27 +0100 (MET)
From: J Wunsch <j@uriah.heep.sax.de>
Message-Id: <199603220808.JAA17469@uriah.heep.sax.de>
Subject: Re: Adaptec 1542B and 1522 on current kernels
To: freebsd-current@FreeBSD.org (FreeBSD-current users)
Date: Fri, 22 Mar 1996 09:08:26 +0100 (MET)
Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch)
In-Reply-To: <199603212321.SAA07486@hopf.math.purdue.edu> from "Clarence Wilkerson" at Mar 21, 96 06:21:22 pm
X-Phone: +49-351-2012 669
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

As Clarence Wilkerson wrote:
> 
> 
> My kernels are going into a stall and debug mode when trying to
> boot on a 486DX4 with either a 1542B or 1522 installed for the taoe
> and cdrom drive ( filesystems on ide drives).

How -current?  For a system from end of February, my 1540 works.

-- 
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  Fri Mar 22 00:51:34 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id AAA24081
          for current-outgoing; Fri, 22 Mar 1996 00:51:34 -0800 (PST)
Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11])
          by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id AAA24049
          for <freebsd-current@FreeBSD.org>; Fri, 22 Mar 1996 00:51:21 -0800 (PST)
Received: from sax.sax.de by irz301.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id JAA04101 for <freebsd-current@FreeBSD.org>; Fri, 22 Mar 1996 09:50:41 +0100
Received: by sax.sax.de (8.6.11/8.6.12-s1) with UUCP
	id JAA03132 for freebsd-current@FreeBSD.org; Fri, 22 Mar 1996 09:50:40 +0100
Received: (from j@localhost) by uriah.heep.sax.de (8.7.4/8.6.9) id JAA17803 for freebsd-current@FreeBSD.org; Fri, 22 Mar 1996 09:26:31 +0100 (MET)
From: J Wunsch <j@uriah.heep.sax.de>
Message-Id: <199603220826.JAA17803@uriah.heep.sax.de>
Subject: Re: lost+found ???
To: freebsd-current@FreeBSD.org (FreeBSD-current users)
Date: Fri, 22 Mar 1996 09:26:31 +0100 (MET)
Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch)
In-Reply-To: <199603211758.KAA00406@phaeton.artisoft.com> from "Terry Lambert" at Mar 21, 96 10:58:03 am
X-Phone: +49-351-2012 669
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

As Terry Lambert wrote:

> While we are on the subject, did anyone commit my fix so that fsck
> doesn't have to be run twice in the case that it's creating lost+found?

I've still got it sitting in my inbox.  I wanted to examine your
supplied `test case' first before committing.

-- 
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  Fri Mar 22 00:56:59 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id AAA24340
          for current-outgoing; Fri, 22 Mar 1996 00:56:59 -0800 (PST)
Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11])
          by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id AAA24152
          for <freebsd-current@FreeBSD.org>; Fri, 22 Mar 1996 00:52:08 -0800 (PST)
Received: from sax.sax.de by irz301.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id JAA04105 for <freebsd-current@FreeBSD.org>; Fri, 22 Mar 1996 09:50:42 +0100
Received: by sax.sax.de (8.6.11/8.6.12-s1) with UUCP
	id JAA03135 for freebsd-current@FreeBSD.org; Fri, 22 Mar 1996 09:50:42 +0100
Received: (from j@localhost) by uriah.heep.sax.de (8.7.4/8.6.9) id JAA17816 for freebsd-current@FreeBSD.org; Fri, 22 Mar 1996 09:27:55 +0100 (MET)
From: J Wunsch <j@uriah.heep.sax.de>
Message-Id: <199603220827.JAA17816@uriah.heep.sax.de>
Subject: Re: lost+found ???
To: freebsd-current@FreeBSD.org (FreeBSD-current users)
Date: Fri, 22 Mar 1996 09:27:55 +0100 (MET)
Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch)
In-Reply-To: <199603211848.TAA13224@keltia.freenix.fr> from "Ollivier Robert" at Mar 21, 96 07:48:53 pm
X-Phone: +49-351-2012 669
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

As Ollivier Robert wrote:

> inode #3  used to be  --  and still is  in several  Unixes -- reserved  for
> lost+found  directories, populated   at _newfs_  fime,   not by fsck.  That
> enable fsck  to save recovered  inodes  even if  the  fs is full (directory
> entries are pre-created too). 
> 
> Why don't we use the same  method as anyone ? Is  there a _good_ reason not
> to do it at newfs time ?

Since nobody was objecting this time (and yes, i knew that i've
basically been picking Terry's argumentation here :), i'm going to see
to get the -DLOSTDIR in newfs/mkfs.c functional again.

-- 
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  Fri Mar 22 05:15:47 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id FAA05115
          for current-outgoing; Fri, 22 Mar 1996 05:15:47 -0800 (PST)
Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19])
          by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id FAA05110
          for <freebsd-current@FreeBSD.org>; Fri, 22 Mar 1996 05:15:44 -0800 (PST)
Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.12/8.6.9) id AAA06842; Sat, 23 Mar 1996 00:14:16 +1100
Date: Sat, 23 Mar 1996 00:14:16 +1100
From: Bruce Evans <bde@zeta.org.au>
Message-Id: <199603221314.AAA06842@godzilla.zeta.org.au>
To: jkh@time.cdrom.com, terry@lambert.org
Subject: Re: lost+found ???
Cc: freebsd-current@FreeBSD.org, j@uriah.heep.sax.de,
        jgreco@brasil.moneng.mei.com
Sender: owner-current@FreeBSD.org
X-Loop: FreeBSD.org
Precedence: bulk

>Traditionally, the directory has been pegged at 8k of allocated blocks
>to ensure that there is some place to put at least 8k of directory
>entries.  This is probably too small for modern file system sizes
>any more.  8-(.

It needs to be large enough to hold files named #1 ... #n where n is
the number of inodes.  This is too large for me.

Bruce

From owner-freebsd-current  Fri Mar 22 06:35:56 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id GAA08993
          for current-outgoing; Fri, 22 Mar 1996 06:35:56 -0800 (PST)
Received: from skiddaw.elsevier.co.uk (skiddaw.elsevier.co.uk [193.131.222.60])
          by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id GAA08978
          for <current@FreeBSD.org>; Fri, 22 Mar 1996 06:35:45 -0800 (PST)
Received: from snowdon.elsevier.co.uk (snowdon.elsevier.co.uk [193.131.197.164]) by skiddaw.elsevier.co.uk (8.6.13/8.6.12) with ESMTP id OAA19367 for <current@FreeBSD.org>; Fri, 22 Mar 1996 14:31:16 GMT
Received: from tees by snowdon with SMTP (PP); Fri, 22 Mar 1996 14:26:14 +0000
Received: (from dpr@localhost) by tees (SMI-8.6/8.6.12) id OAA06826;
          Fri, 22 Mar 1996 14:31:31 GMT
From: Paul Richards <p.richards@elsevier.co.uk>
Message-Id: <199603221431.OAA06826@tees>
Subject: Re: DEVFS vs "regular /dev"
To: rgrimes@GndRsh.aac.dev.com (Rodney W. Grimes)
Date: Fri, 22 Mar 1996 14:31:30 +0000 (GMT)
Cc: scrappy@ki.net, current@FreeBSD.org
In-Reply-To: <199603211856.KAA24142@GndRsh.aac.dev.com> from "Rodney W. Grimes" at Mar 21, 96 10:56:31 am
X-Mailer: ELM [version 2.4 PL24]
Content-Type: text
Sender: owner-current@FreeBSD.org
X-Loop: FreeBSD.org
Precedence: bulk

In reply to Rodney W. Grimes who said
> 
> These problems may have been corrected.  I do know for certain that certain
> /dev/ entries missing causes the system to hang very early in init, and you
> can not even get up single user to fix it.  This _needs_ fixed badly, you
> should be able to
> rm -r /dev
> reboot
> and get the system up single user, if not you have a chicken and egg
> problem as to how to repair a damaged or loss /dev tree.
> 

This is *exactly* the problem I reported a few weeks ago where I tried to run
with a devfs only system and it hung before getting to single user.

This was what promted my complaints about a lack of fixit floppy since I
was seriously spammed without one.

-- 
  Paul Richards. Originative Solutions Ltd.  (Netcraft Ltd. contractor)
  Elsevier Science TIS online journal project.
  Email: p.richards@elsevier.co.uk
  Phone: 0370 462071 (Mobile), +44 (0)1865 843155

From owner-freebsd-current  Fri Mar 22 08:06:30 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id IAA13030
          for current-outgoing; Fri, 22 Mar 1996 08:06:30 -0800 (PST)
Received: from localhost.cdrom.com (localhost.cdrom.com [127.0.0.1])
          by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id IAA13025
          Fri, 22 Mar 1996 08:06:25 -0800 (PST)
Message-Id: <199603221606.IAA13025@freefall.freebsd.org>
X-Authentication-Warning: freefall.freebsd.org: Host localhost.cdrom.com [127.0.0.1] didn't use HELO protocol
To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch)
cc: freebsd-current@FreeBSD.org (FreeBSD-current users)
Subject: Re: Adaptec 1542B and 1522 on current kernels 
In-reply-to: Your message of "Fri, 22 Mar 1996 09:08:26 +0100."
             <199603220808.JAA17469@uriah.heep.sax.de> 
Date: Fri, 22 Mar 1996 08:06:25 -0800
From: "Justin T. Gibbs" <gibbs@freefall.freebsd.org>
Sender: owner-current@FreeBSD.org
X-Loop: FreeBSD.org
Precedence: bulk

>As Clarence Wilkerson wrote:
>> 
>> 
>> My kernels are going into a stall and debug mode when trying to
>> boot on a 486DX4 with either a 1542B or 1522 installed for the taoe
>> and cdrom drive ( filesystems on ide drives).
>
>How -current?  For a system from end of February, my 1540 works.

Wasn't there a reported fix to some of these 154X card problems that
required using a FIFO scheme for recycling mailboxes?  We currently
do LIFO.

>-- 
>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  Fri Mar 22 09:24:13 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id JAA16495
          for current-outgoing; Fri, 22 Mar 1996 09:24:13 -0800 (PST)
Received: from precipice.shockwave.com (precipice.shockwave.com [171.69.108.33])
          by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id JAA16487
          Fri, 22 Mar 1996 09:24:11 -0800 (PST)
Received: from localhost.shockwave.com (localhost.shockwave.com [127.0.0.1]) by precipice.shockwave.com (8.7.4/8.7.3) with SMTP id JAA06071; Fri, 22 Mar 1996 09:24:03 -0800 (PST)
Message-Id: <199603221724.JAA06071@precipice.shockwave.com>
To: "Jordan K. Hubbard" <jkh@time.cdrom.com>
cc: freebsd-hubs@freebsd.org, jkh@freebsd.org, hackers@freebsd.org,
        current@freebsd.org
Subject: Re: new sup server 
In-reply-to: Your message of "Thu, 21 Mar 1996 16:04:26 PST."
             <1344.827453066@time.cdrom.com> 
Date: Fri, 22 Mar 1996 09:24:03 -0800
From: Paul Traina <pst@shockwave.com>
Sender: owner-current@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk


  From: "Jordan K. Hubbard" <jkh@time.cdrom.com>
  Subject: Re: new sup server 
  > I suspect that Jordan will be trimming off sup's from non-official-mirror
  > sites real soon now to reduce the load on freefall and the T1.
  
  You suspect correctly.  This is a fine proposal and I urge everyone
  here to heed the Call of Paul.
  
  > Ministry of Information
  
  If you really want to adopt that title, it's all yours.  Just don't
  forget that you get to take poison with the rest of us, come the
  bitter end. :-)

I was thinking I could escape across the border to someplace running VMS... :-)

From owner-freebsd-current  Fri Mar 22 09:25:04 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id JAA16628
          for current-outgoing; Fri, 22 Mar 1996 09:25:04 -0800 (PST)
Received: from ref.tfs.com (ref.tfs.com [140.145.254.251])
          by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id JAA16600
          for <current@freebsd.org>; Fri, 22 Mar 1996 09:24:59 -0800 (PST)
Received: (from julian@localhost) by ref.tfs.com (8.7.3/8.6.9) id MAA19785; Thu, 21 Mar 1996 12:16:32 -0800 (PST)
Message-Id: <199603212016.MAA19785@ref.tfs.com>
Subject: Re: DEVFS vs "regular /dev"
To: davidg@Root.COM
Date: Thu, 21 Mar 1996 12:16:31 -0800 (PST)
From: "JULIAN Elischer" <julian@ref.tfs.com>
Cc: phk@critter.tfs.com, terry@lambert.org, scrappy@ki.net,
        current@freebsd.org
In-Reply-To: <199603211313.FAA05246@Root.COM> from "David Greenman" at Mar 21, 96 05:13:54 am
X-Mailer: ELM [version 2.4 PL25 ME8b]
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

> 
> 
> 
> >> >> > This assumes that the file system abstractions currently in place
> >> >> > change as well, since the /dev FS can't be mounted *after* the / FS
> >> >> > has been mounted as an inferior FS --
> >> >> why not?
> >> >> you don't need a mounted /dev to mount root.
> >> >> that's done specially.
> >> >
> >> >So you don't need a mounted root to have a mounted /dev, of course!
> >> 
> >>    That's silly. The root filesystem is mounted long before /dev would be, 
> >
> >Not that long before.  /sbin/init will have to mount it to get in touch
> >with /dev/console, /dev/null and ...
> 
>    No, it will be mounted in the kernel.
>From within the kernel's point of view, the devfs is always available
I could easily add a function that would 'open' a device by name
even if the devfs is not mounted..
e.g.
 error = deviceopen("console",O_RDONLY,0,&vnpointer);
 if (error) 
 {
	printf(" failed to open /dev/console, errno = %d",error);
 }

 maybe even a version that given a proc struct, will open it on behalf
 of that process..
> 
> -DG
> 
> David Greenman
> Core-team/Principal Architect, The FreeBSD Project
> 


From owner-freebsd-current  Fri Mar 22 09:34:07 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id JAA17335
          for current-outgoing; Fri, 22 Mar 1996 09:34:07 -0800 (PST)
Received: from tcsi.tcs.com (tcsi.tcs.com [137.134.41.11])
          by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id JAA17330
          for <current@FreeBSD.org>; Fri, 22 Mar 1996 09:34:03 -0800 (PST)
Received: from phact.tcs.com (phact.tcs.com [137.134.41.99]) by tcsi.tcs.com (8.7.4/8.6.10) with ESMTP id JAA22169; Fri, 22 Mar 1996 09:32:36 -0800 (PST)
Received: from cozumel.tcs.com (cozumel.tcs.com [137.134.104.12]) by phact.tcs.com (8.6.10/8.6.10) with ESMTP id JAA06316; Fri, 22 Mar 1996 09:32:35 -0800
From: Douglas Ambrisko <ambrisko@tcs.com>
Received: (ambrisko@localhost) by cozumel.tcs.com (8.6.10/8.6.10) id JAA18126; Fri, 22 Mar 1996 09:31:02 -0800
Message-Id: <199603221731.JAA18126@cozumel.tcs.com>
Subject: Re: DEVFS vs "regular /dev"
To: rgrimes@gndrsh.aac.dev.com (Rodney W. Grimes)
Date: Fri, 22 Mar 1996 09:31:01 -0800 (PST)
Cc: current@FreeBSD.org
In-Reply-To: <199603211856.KAA24142@GndRsh.aac.dev.com> from "Rodney W. Grimes" at Mar 21, 96 10:56:31 am
X-Mailer: ELM [version 2.4 PL23]
Content-Type: text
Sender: owner-current@FreeBSD.org
X-Loop: FreeBSD.org
Precedence: bulk

Rodney W. Grimes writes:
| 
| These problems may have been corrected.  I do know for certain that certain
| /dev/ entries missing causes the system to hang very early in init, and you
| can not even get up single user to fix it.  This _needs_ fixed badly, you
| should be able to
| rm -r /dev
| reboot
| and get the system up single user, if not you have a chicken and egg
| problem as to how to repair a damaged or loss /dev tree.

One company I worked for, stashed a small kernel, miniroot and dev tree
on the /usr partition.  If you made a "mistake" on the root partition
you could reboot from the the usr slice and fix the root partittion.

It was an interesting idea.

Doug A.

From owner-freebsd-current  Fri Mar 22 09:35:44 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id JAA17415
          for current-outgoing; Fri, 22 Mar 1996 09:35:44 -0800 (PST)
Received: from main.statsci.com (main.statsci.com [198.145.127.110])
          by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id JAA17407
          for <current@FreeBSD.org>; Fri, 22 Mar 1996 09:35:41 -0800 (PST)
Received: from statsci.com by main.statsci.com with smtp
	(Smail3.1.29.1 #3) id m0u0Ak4-000r3uC; Fri, 22 Mar 96 09:35 PST
Message-Id: <m0u0Ak4-000r3uC@main.statsci.com>
To: Bruce Evans <bde@zeta.org.au>
cc: phk@critter.tfs.com, current@FreeBSD.org, julian@ref.tfs.com,
        scrappy@ki.net
Subject: Re: PATCH: small, syntax changes for devfs 
In-reply-to: Your message of "Fri, 22 Mar 1996 18:16:51 +1100."
             <199603220716.SAA24449@godzilla.zeta.org.au> 
Reply-to: scott@statsci.com
Date: Fri, 22 Mar 1996 09:35:10 -0800
From: Scott Blachowicz <scott@statsci.com>
Sender: owner-current@FreeBSD.org
X-Loop: FreeBSD.org
Precedence: bulk

Bruce Evans <bde@zeta.org.au> wrote:

> wd0s1 is there, and opening it would reveal wd0s1[a-h], but this isn't
> much use.  Perhaps wd0s1 should be a directory containing [a-h].  I
> prefer a flat namespace.

Doesn't wd0s1 need to be a device file so you have something to run
disklabel against?

Scott Blachowicz  Ph: 206/283-8802x240   Mathsoft (Data Analysis Products Div)
                                         1700 Westlake Ave N #500
scott@statsci.com                        Seattle, WA USA   98109
Scott.Blachowicz@seaslug.org

From owner-freebsd-current  Fri Mar 22 09:38:53 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id JAA17509
          for current-outgoing; Fri, 22 Mar 1996 09:38:53 -0800 (PST)
Received: from GndRsh.aac.dev.com (GndRsh.aac.dev.com [198.145.92.241])
          by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id JAA17502
          for <current@FreeBSD.org>; Fri, 22 Mar 1996 09:38:50 -0800 (PST)
Received: (from rgrimes@localhost) by GndRsh.aac.dev.com (8.6.12/8.6.12) id JAA25344; Fri, 22 Mar 1996 09:37:45 -0800
From: "Rodney W. Grimes" <rgrimes@GndRsh.aac.dev.com>
Message-Id: <199603221737.JAA25344@GndRsh.aac.dev.com>
Subject: Re: DEVFS vs "regular /dev"
To: ambrisko@tcs.com (Douglas Ambrisko)
Date: Fri, 22 Mar 1996 09:37:44 -0800 (PST)
Cc: current@FreeBSD.org
In-Reply-To: <199603221731.JAA18126@cozumel.tcs.com> from "Douglas Ambrisko" at Mar 22, 96 09:31:01 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

> 
> Rodney W. Grimes writes:
> | 
> | These problems may have been corrected.  I do know for certain that certain
> | /dev/ entries missing causes the system to hang very early in init, and you
> | can not even get up single user to fix it.  This _needs_ fixed badly, you
> | should be able to
> | rm -r /dev
> | reboot
> | and get the system up single user, if not you have a chicken and egg
> | problem as to how to repair a damaged or loss /dev tree.
> 
> One company I worked for, stashed a small kernel, miniroot and dev tree
> on the /usr partition.  If you made a "mistake" on the root partition
> you could reboot from the the usr slice and fix the root partittion.
> 
> It was an interesting idea.

And a darn goodone if I might add.  I often do this on my freespace
floater partition if I am going to go play with things like this...

cd /A;
dump 0Bf 2000000 - /dev/rsd0a | restore rf -

whooommmpp... instant emergeny boot via sd(0,h)/kernel....


-- 
Rod Grimes                                      rgrimes@gndrsh.aac.dev.com
Accurate Automation Company                 Reliable computers for FreeBSD

From owner-freebsd-current  Fri Mar 22 09:55:41 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id JAA17987
          for current-outgoing; Fri, 22 Mar 1996 09:55:41 -0800 (PST)
Received: from mail.rwth-aachen.de (mail.RWTH-Aachen.DE [137.226.144.9])
          by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id JAA17980
          for <freebsd-current@freefall.FreeBSD.org>; Fri, 22 Mar 1996 09:55:38 -0800 (PST)
Received: from gilberto.physik.rwth-aachen.de (gilberto.physik.rwth-aachen.de)
 by mail.rwth-aachen.de (PMDF V5.0-4 #13110)
 id <01I2NE9K809S001Y05@mail.rwth-aachen.de> for
 freebsd-current@freefall.FreeBSD.org; Fri, 22 Mar 1996 18:51:43 +0100
Received: (from kuku@localhost) by gilberto.physik.rwth-aachen.de
 (8.6.11/8.6.9) id SAA29897 for freebsd-current@freefall.cdrom.com; Fri,
 22 Mar 1996 18:54:28 +0100
Date: Fri, 22 Mar 1996 18:54:28 +0100
From: "Christoph P. Kukulies" <kuku@gilberto.physik.rwth-aachen.de>
Subject: entropy source: Interrupts in use.
To: freebsd-current@freefall.FreeBSD.org
Message-id: <199603221754.SAA29897@gilberto.physik.rwth-aachen.de>
Content-transfer-encoding: 7BIT
Sender: owner-current@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk


What does the bootup message

Entropy source: Interrupts in use.

mean?

Something I should worry about? I added an isdn card to irq 15
recently.

--Chris Christoph P. U. Kukulies kuku@gil.physik.rwth-aachen.de

From owner-freebsd-current  Fri Mar 22 10:12:11 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id KAA18862
          for current-outgoing; Fri, 22 Mar 1996 10:12:11 -0800 (PST)
Received: from ki.net (root@ki.net [142.77.249.8])
          by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id KAA18752
          for <current@freebsd.org>; Fri, 22 Mar 1996 10:11:20 -0800 (PST)
Received: (from scrappy@localhost) by ki.net (8.7.4/8.7.4) id NAA25762; Fri, 22 Mar 1996 13:11:43 -0500 (EST)
Date: Fri, 22 Mar 1996 13:11:41 -0500 (EST)
From: "Marc G. Fournier" <scrappy@ki.net>
To: current@freebsd.org
Subject: Problem with SMC8013EPC?
Message-ID: <Pine.BSF.3.91.960322130742.23921E-100000@ki.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-current@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk


Hi...

	I put in a problem report on this already, but I'm curious as
to whether there are any known problem with the drivers for the SMC 8013EPC
Ethernet card?

	In the course of the past 10 minutes, I've had two panics, first one
happening just as I was doing a 'diff' between two source trees, one of
which was NFS mounted from a -stable machine, and the other seemingly 
resulting from typing characters across a telnet link to the machine
(current process == telnetd)

	According to DDB, the panic was at 

		ed start(f01dc0f0) at ed start+0x315

	Come to think about it, if I remember right, the problem report I
submitted on this had, as part of its trace, calls to:

		udp output()
		udp usrreq()

	This time it was calls to:

		tcp output()
		tcp usrreq()

Thanks...

Marc G. Fournier | POP Mail  Telnet Acct  DNS Hosting
System           |  WWW Services   Database Services  | Knowledge, 
  Administrator  |                                    | Information and
 scrappy@ki.net  |      WWW: http://www.ki.net        | Communications, Inc


From owner-freebsd-current  Fri Mar 22 10:27:04 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id KAA19617
          for current-outgoing; Fri, 22 Mar 1996 10:27:04 -0800 (PST)
Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211])
          by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id KAA19610
          for <current@FreeBSD.ORG>; Fri, 22 Mar 1996 10:27:02 -0800 (PST)
Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id LAA02981; Fri, 22 Mar 1996 11:20:31 -0700
From: Terry Lambert <terry@lambert.org>
Message-Id: <199603221820.LAA02981@phaeton.artisoft.com>
Subject: Re: PATCH: small, syntax changes for devfs
To: bde@zeta.org.au (Bruce Evans)
Date: Fri, 22 Mar 1996 11:20:31 -0700 (MST)
Cc: bde@zeta.org.au, phk@critter.tfs.com, current@FreeBSD.ORG,
        julian@ref.tfs.com, scrappy@ki.net
In-Reply-To: <199603220716.SAA24449@godzilla.zeta.org.au> from "Bruce Evans" at Mar 22, 96 06:16: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

> wd0s1 is there, and opening it would reveal wd0s1[a-h], but this isn't
> much use.  Perhaps wd0s1 should be a directory containing [a-h].  I
> prefer a flat namespace.

Why?

It's possible, of course, to "chunk up" names, 2 characters at a time,
to build a flat name space, but is this necessary or even desirable?

At the very least, each device should be treated as a directory for
the purposes of getdirents and the ISDIR attributes, anyway.  It
lets you have "status" and other information in the "directory".

For the purposes of read/write, you treat it as a file.

Consider: a device reference is a vnode reference in devfs: all
lookup instances are predicated on the path to the devfs.  That
means I can access devices remotely without modifications (assuming
no layer 5 differentiation between systems -- if B9600 isn't the
same on both boxes, well, you're pretty much screwed).


					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 Mar 22 10:35:21 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id KAA20129
          for current-outgoing; Fri, 22 Mar 1996 10:35:21 -0800 (PST)
Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211])
          by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id KAA20118
          for <current@FreeBSD.org>; Fri, 22 Mar 1996 10:35:15 -0800 (PST)
Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id LAA03010; Fri, 22 Mar 1996 11:29:04 -0700
From: Terry Lambert <terry@lambert.org>
Message-Id: <199603221829.LAA03010@phaeton.artisoft.com>
Subject: Re: PATCH: small, syntax changes for devfs
To: scott@statsci.com
Date: Fri, 22 Mar 1996 11:29:04 -0700 (MST)
Cc: bde@zeta.org.au, phk@critter.tfs.com, current@FreeBSD.org,
        julian@ref.tfs.com, scrappy@ki.net
In-Reply-To: <m0u0Ak4-000r3uC@main.statsci.com> from "Scott Blachowicz" at Mar 22, 96 09:35:10 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

> > wd0s1 is there, and opening it would reveal wd0s1[a-h], but this isn't
> > much use.  Perhaps wd0s1 should be a directory containing [a-h].  I
> > prefer a flat namespace.
> 
> Doesn't wd0s1 need to be a device file so you have something to run
> disklabel against?

Yes, but "reveal" doesn't mean you blow the others away.  I dislike
"potential" entries for non-clone devices, so "reveal" would be
annoying otherwise, I think.

This is really irrelevant to flat vs. non-flat name spaces.  There is
no reason why a device file can't be a directory and a file at the
same time.  Device reads and writes don't care about seek offsets
and getdirentries() is a seperate call that can act on the fd using
the fd's seek offset field entirely seperately from use as a device.

Truly, getdirentries wants to take a seek offset as an argument instead
of using the seek portion of the fd to avoid any possible conflict
on seekable physical devices that have logical devices hierarchically
associated with them.


					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 Mar 22 10:54:14 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id KAA21134
          for current-outgoing; Fri, 22 Mar 1996 10:54:14 -0800 (PST)
Received: from FSL.ORST.EDU (FSL.ORST.EDU [128.193.112.105])
          by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id KAA21128
          Fri, 22 Mar 1996 10:53:51 -0800 (PST)
Received: from picea.FSL.ORST.EDU (hernanw@picea.FSL.ORST.EDU [128.193.112.3]) by FSL.ORST.EDU (8.6.9/8.6.9) with ESMTP id KAA12972; Fri, 22 Mar 1996 10:52:40 -0800
Received: (from hernanw@localhost) by picea.FSL.ORST.EDU (8.7/8.6.9) id KAA26143; Fri, 22 Mar 1996 10:52:38 -0800 (PST)
Date: Fri, 22 Mar 1996 10:52:36 -0800 (PST)
From: Wayne Hernandez <hernanw@FSL.ORST.EDU>
To: Paul Traina <pst@shockwave.com>
cc: freebsd-hubs@freebsd.org, jkh@freebsd.org, hackers@freebsd.org,
        current@freebsd.org
Subject: Re: new sup server 
In-Reply-To: <199603211954.LAA02727@precipice.shockwave.com>
Message-ID: <Pine.SUN.3.91.960322103912.24587C-100000@picea.FSL.ORST.EDU>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-current@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk



On Thu, 21 Mar 1996, Paul Traina wrote:

> Here's an example of neighbor coordination, in the following example,
> sup3 and sup4 choose sup windows that would cause them to never overlap.
> 
> 	sup2	2:10	8;10	13:10	20:10		4x
> 	sup3	2:20		13:20			2x
> 	sup4		8:30	13:30			2x
> 	sup5	2:40	8:40		20:40		3x
> 	sup6			13:50			1x
> 

I'm reset to 2:20 and 13:20.  I'm seeing a "invalid release" in my logs, 
that I'm trying to track down to which one of my releases have something 
wrong.  

While I am at it, I have most of /.016/FreeBSD mirrored, but the links 
don't seem to work within netscape.  If you need another mirror site to 
cut down on the snapshot grabbers.  I will have to do some house cleaning 
to make room for todays snapshot though, before I have it available.  I'm 
going to attempt to burn a cd which my current machine.  My sup server is 
running 2.1.0 at the moment.


Wayne

From owner-freebsd-current  Fri Mar 22 10:56:48 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id KAA21395
          for current-outgoing; Fri, 22 Mar 1996 10:56:48 -0800 (PST)
Received: from Root.COM (implode.Root.COM [198.145.90.17])
          by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id KAA21390
          for <current@FreeBSD.ORG>; Fri, 22 Mar 1996 10:56:46 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by Root.COM (8.6.12/8.6.5) with SMTP id KAA08631; Fri, 22 Mar 1996 10:57:03 -0800
Message-Id: <199603221857.KAA08631@Root.COM>
X-Authentication-Warning: implode.Root.COM: Host localhost didn't use HELO protocol
To: "Marc G. Fournier" <scrappy@ki.net>
cc: current@FreeBSD.ORG
Subject: Re: Problem with SMC8013EPC? 
In-reply-to: Your message of "Fri, 22 Mar 1996 13:11:41 EST."
             <Pine.BSF.3.91.960322130742.23921E-100000@ki.net> 
From: David Greenman <davidg@Root.COM>
Reply-To: davidg@Root.COM
Date: Fri, 22 Mar 1996 10:57:03 -0800
Sender: owner-current@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

>	I put in a problem report on this already, but I'm curious as
>to whether there are any known problem with the drivers for the SMC 8013EPC
>Ethernet card?

   There are no known bugs, we're using a similar card in freefall (same
driver) and have uptimes >30 days...and we do heavy TCP/IP and NFS.

>	In the course of the past 10 minutes, I've had two panics, first one
>happening just as I was doing a 'diff' between two source trees, one of
>which was NFS mounted from a -stable machine, and the other seemingly 
>resulting from typing characters across a telnet link to the machine
>(current process == telnetd)
>
>	According to DDB, the panic was at 
>
>		ed start(f01dc0f0) at ed start+0x315
>
>	Come to think about it, if I remember right, the problem report I
>submitted on this had, as part of its trace, calls to:
>
>		udp output()
>		udp usrreq()
>
>	This time it was calls to:
>
>		tcp output()
>		tcp usrreq()

   Sounds like your interrupt mask isn't right somehow, resulting in spl
blocking not working.

-DG

David Greenman
Core-team/Principal Architect, The FreeBSD Project

From owner-freebsd-current  Fri Mar 22 11:04:50 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id LAA21954
          for current-outgoing; Fri, 22 Mar 1996 11:04:50 -0800 (PST)
Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211])
          by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id LAA21949
          for <freebsd-current@freefall.freebsd.org>; Fri, 22 Mar 1996 11:04:42 -0800 (PST)
Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id LAA03059; Fri, 22 Mar 1996 11:58:22 -0700
From: Terry Lambert <terry@lambert.org>
Message-Id: <199603221858.LAA03059@phaeton.artisoft.com>
Subject: Re: lost+found ???
To: mrm@Sceard.COM (M.R.Murphy)
Date: Fri, 22 Mar 1996 11:58:22 -0700 (MST)
Cc: freebsd-current@freefall.freebsd.org, joerg_wunsch@uriah.heep.sax.de,
        terry@lambert.org
In-Reply-To: <9603220654.AA23195@Sceard.COM> from "M.R.Murphy" at Mar 22, 96 06:54:08 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 disagree :-). I'd prefer the SVR2 approach of a separate simple script
> to create, populate, and then depopulate lost+found, remembering the
> concept that a tool should do one thing, of course. The reason for
> populate/depopulate is to insure that an expanddir isn't necessary in
> the fsck processing. Terry?

If you populate lost+found to preexpand it, then depopulate it, the 4.4
UFS directory compaction code will once again remove the space.  In 4.4
unused directory blocks are reclaimed through truncation.

This only worked in previous releases because directories were only
grown, never shrunk.  To recover unused space, you'd need to backup
and restore, or make a new directory and "mv" everything there, and
delete the old one.

I'm pretty sure that what happened is the directory truncation code
caused them to worry about this, and they copped out on special
casing inode 3.  Once they were in for a penny, they might as well
be in for a pound, and they copped out on the creation ("no, that's
a feature").  I simply don't buy the "deterministically recoverable"
argument when block allocation is involved.

To do something about this would require modifying the FS code so that
inode 3 is always used (again), and so that the dir code specifically
*didn't* truncate inode 3 below 8k (or whatever the magic number is).

On the subject of the 8k, Bruce is wrong about the requirements: the
most you have to deal with is the number of files allowed to be a
problem with properly ordered updates: basically, one directory
worth of names... and in that case, you'll get blocks back from
the directory that died.  It's still possible to overflow the 16
additional (reserved) blocks, but it's unlikely.

Of course if you mount async, all bets are off. 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  Fri Mar 22 12:20:34 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id MAA27209
          for current-outgoing; Fri, 22 Mar 1996 12:20:34 -0800 (PST)
Received: from linux4nn.gn.iaf.nl (root@linux4nn.gn.iaf.nl [193.67.144.34])
          by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id MAA27199
          Fri, 22 Mar 1996 12:20:26 -0800 (PST)
Received: from uni4nn.iaf.nl (root@uni4nn.iaf.nl [193.67.144.33]) by linux4nn.gn.iaf.nl (8.6.9/8.6.9) with SMTP id VAA02047; Fri, 22 Mar 1996 21:20:18 +0100
Received: by uni4nn.iaf.nl with UUCP id AA07781
  (5.67b/IDA-1.5); Fri, 22 Mar 1996 21:19:49 +0100
Received: by iafnl.es.iaf.nl with UUCP id AA30903
  (5.67b/IDA-1.5); Fri, 22 Mar 1996 21:00:52 +0100
Received: (from wilko@localhost) by yedi.iaf.nl (8.6.12/8.6.6) id TAA00680; Fri, 22 Mar 1996 19:42:35 +0100
From: Wilko Bulte <wilko@yedi.iaf.nl>
Message-Id: <199603221842.TAA00680@yedi.iaf.nl>
X-Organisation: Private FreeBSD site - Arnhem - The Netherlands
Subject: Re: Crash advice needed (long) APPENDIX A
To: George.Scott@cc.monash.edu.au (George Scott)
Date: Fri, 22 Mar 1996 19:42:35 +0100 (MET)
Cc: current@FreeBSD.ORG, hackers@FreeBSD.ORG, uhclem@nemesis.lonestar.org
In-Reply-To: <199603220627.QAA17304@moa.cc.monash.edu.au> from "George Scott" at Mar 22, 96 04:27:50 pm
X-Mailer: ELM [version 2.4 PL23]
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Sender: owner-current@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

> > Debugger("aha1542") called		(this system has a 1540B)
> > AGAIN
> > aha0: MBO 02 and not 00 (free)
> > These last few lines repeat every ten seconds or so until I got
> > tired of looking at them and pressed RESET.
> > 
> > (I have seen this MBO 02 and not 00 (free) message on a 1542C
> >  controller at work when it is talking to a WangDat tape drive.
> >  Sometimes this system also gets a "NO SENSE" message and
> >  will claim the tape drive is not ready (it is ready) or busy (it isn't).
> >  Solution on that system: turn everything off and back on and everyone
> >  is happy.  Unfortunately, cycling power does not improve things here.)
> 
> I had this frequently under 2.1.0-RELEASE on a '486 with an AHA-1542CP (with
> the P stuff disabled).
> 
> I had 5 drives on the external connector and 2 on the internal and noticed
> that the time outs stopped happening when I disconnected either the external
> or internal drives, so I figured bus length as the cause.  It was over 20'
> so I shortened it as much as I could (to 16' if I remember) but the problems
> still occured.

Apart from the fact that 20' is too long (3m max for fast-SCSI, 1542C is
a Fast capable controller that will try to use 10Mbytes/sec with a Fast
device) Adaptecs tend to work better if the controller is at the end of
the SCSI bus. So, either use the internal or external connector but not
both at the same time

_     __________________________________________________________________________
 |   / o / /  _   Wilko Bulte             email: wilko@yedi.iaf.nl
 |/|/ / / /( (_)  Private FreeBSD site  - Arnhem - The Netherlands
--------------------------------------------------------------------------------

From owner-freebsd-current  Fri Mar 22 13:10:50 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id NAA29616
          for current-outgoing; Fri, 22 Mar 1996 13:10:50 -0800 (PST)
Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211])
          by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id NAA29594
          Fri, 22 Mar 1996 13:10:40 -0800 (PST)
Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id OAA03306; Fri, 22 Mar 1996 14:04:08 -0700
From: Terry Lambert <terry@lambert.org>
Message-Id: <199603222104.OAA03306@phaeton.artisoft.com>
Subject: Re: Crash advice needed (long) APPENDIX A
To: wilko@yedi.iaf.nl (Wilko Bulte)
Date: Fri, 22 Mar 1996 14:04:08 -0700 (MST)
Cc: George.Scott@cc.monash.edu.au, current@freebsd.org, hackers@freebsd.org,
        uhclem@nemesis.lonestar.org
In-Reply-To: <199603221842.TAA00680@yedi.iaf.nl> from "Wilko Bulte" at Mar 22, 96 07:42: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

> Apart from the fact that 20' is too long (3m max for fast-SCSI, 1542C is
> a Fast capable controller that will try to use 10Mbytes/sec with a Fast
> device) Adaptecs tend to work better if the controller is at the end of
> the SCSI bus. So, either use the internal or external connector but not
> both at the same time

Using both busses is not a problem for the CF; the C and prior can
only successfully use the internal or the external unless there is
a modification (invloving a capacitor and a resistor soldered on near
the external connector).

At one time, Rod Grimes posted the ECN (Engineering Change Notice)
number for this mod to the older Adaptec controllers.


					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 Mar 22 13:37:54 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id NAA01438
          for current-outgoing; Fri, 22 Mar 1996 13:37:54 -0800 (PST)
Received: from austin.polstra.com (austin.polstra.com [206.213.73.10])
          by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id NAA01413
          Fri, 22 Mar 1996 13:37:27 -0800 (PST)
Received: from austin.polstra.com (jdp@localhost) by austin.polstra.com (8.6.12/8.6.12) with ESMTP id NAA26670; Fri, 22 Mar 1996 13:37:17 -0800
Message-Id: <199603222137.NAA26670@austin.polstra.com>
To: jkh@time.cdrom.com
Cc: freebsd-hubs@FreeBSD.org, jkh@FreeBSD.org, hackers@FreeBSD.org,
        current@FreeBSD.org
Subject: Re: new sup server
In-reply-to: <1344.827453066@time.cdrom.com>
Date: Fri, 22 Mar 1996 13:37:17 -0800
From: John Polstra <jdp@polstra.com>
Sender: owner-current@FreeBSD.org
X-Loop: FreeBSD.org
Precedence: bulk

Jordan wrote:

> > I suspect that Jordan will be trimming off sup's from non-official-mirror
> > sites real soon now to reduce the load on freefall and the T1.
> 
> You suspect correctly.

PLEASE don't do that yet!  I am telling you again: the sup mirrors still
do NOT work right.

In several attempts spread over the past few months, I have never
yet succeeded in getting any of the sup mirrors to give me an intact
cvs tree.  Invariably, they delete some of my perfectly good files,
without replacing them later on.  As an example, sup5 is currently
(and repeatably) doing this to me:

    SUP 9.26 (4.3 BSD) for file supfile.sup5 at Mar 20 04:15:01
    SUP Upgrade of src-base-cvs at Wed Mar 20 04:15:01 1996
    SUP Fileserver 9.13 (4.3 BSD) 21149 on burka.rdy.com at 04:15:01
    SUP Fileserver supports compression.
    SUP Requesting changes since Mar 16 17:06:47 1996
    SUP: Unable to delete directory src/usr.sbin
    SUP: Unable to delete directory src/usr.bin
    SUP Deleted directory src/tools
    SUP: Unable to delete directory src/sys
    SUP: Unable to delete directory src/share
    SUP: Unable to delete directory src/secure
    SUP: Unable to delete directory src/sbin
    SUP: Unable to delete directory src/release
    SUP: Unable to delete directory src/lkm
    SUP: Unable to delete directory src/libexec
    SUP: Unable to delete directory src/lib
    SUP Deleted directory src/kerberosIV
    SUP: Unable to delete directory src/include
    SUP: Unable to delete directory src/gnu
    SUP: Unable to delete directory src/games
    SUP: Unable to delete directory src/etc
    SUP: Unable to delete directory src/eBones
    SUP: Unable to delete directory src/bin
    SUP Deleted directory src/TODO-2.1
    SUP Deleted file src/Makefile,v
    SUP Deleted file src/COPYRIGHT,v
    SUP Deleted directory src/Attic

It can't be blamed on an out-of-date sup client, either.  I'm using the
client from -stable, which is identical to the one in -current.

I'm currently working with Dima to try and figure out what is going on.
I've instrumented my sup client with a bunch of printfs, and I'm trying
to analyze the copious output they've given me.  (Help from somebody who
already knows the sup internals would be most welcome!)

Until this is finally fixed, I'm in trouble if you cut me off from
sup.freebsd.org.
--
   John Polstra                                       jdp@polstra.com
   John D. Polstra & Co., Inc.                Seattle, Washington USA
   "Self-knowledge is always bad news."                 -- John Barth

From owner-freebsd-current  Fri Mar 22 14:04:47 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id OAA03611
          for current-outgoing; Fri, 22 Mar 1996 14:04:47 -0800 (PST)
Received: from ki.net (root@ki.net [142.77.249.8])
          by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id OAA03602
          for <current@FreeBSD.ORG>; Fri, 22 Mar 1996 14:04:38 -0800 (PST)
Received: (from scrappy@localhost) by ki.net (8.7.4/8.7.4) id RAA00184; Fri, 22 Mar 1996 17:05:02 -0500 (EST)
Date: Fri, 22 Mar 1996 17:05:00 -0500 (EST)
From: "Marc G. Fournier" <scrappy@ki.net>
To: David Greenman <davidg@Root.COM>
cc: current@FreeBSD.ORG
Subject: Re: Problem with SMC8013EPC? 
In-Reply-To: <199603221857.KAA08631@Root.COM>
Message-ID: <Pine.BSF.3.91.960322170007.23921N-100000@ki.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-current@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

On Fri, 22 Mar 1996, David Greenman wrote:

> >	According to DDB, the panic was at 
> >
> >		ed start(f01dc0f0) at ed start+0x315
> >
> >	Come to think about it, if I remember right, the problem report I
> >submitted on this had, as part of its trace, calls to:
> >
> >		udp output()
> >		udp usrreq()
> >
> >	This time it was calls to:
> >
> >		tcp output()
> >		tcp usrreq()
> 
>    Sounds like your interrupt mask isn't right somehow, resulting in spl
> blocking not working.
>
	Since it has done this to me several times today (4 or 5 so far),
what exactly should I be looking for?  This bug is what is currently keeping
me from using this machine for anything except to modify the devfs code.

	How can the interrupt mask not be right?  No, don't answer that
one...not quite what I meant :(  *If* I'm understanding what you mean
about interrupt mask (which there is a good chance I'm not), mine is currently
set at IRQ 5, and the system doesn't seem to be reporting anything else
trying to occupy that space.

	All that is in that machine is an Adaptec 1542CF controller, a
mono card (full length, relatively old), and the ethernet controller
(0x280, 5, 0xD8000)

Thanks...
	
Marc G. Fournier | POP Mail  Telnet Acct  DNS Hosting
System           |  WWW Services   Database Services  | Knowledge, 
  Administrator  |                                    | Information and
 scrappy@ki.net  |      WWW: http://www.ki.net        | Communications, Inc


From owner-freebsd-current  Fri Mar 22 15:33:52 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id PAA12089
          for current-outgoing; Fri, 22 Mar 1996 15:33:52 -0800 (PST)
Received: from skynet.ctr.columbia.edu (skynet.ctr.columbia.edu [128.59.64.70])
          by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id PAA12071
          for <current@freebsd.org>; Fri, 22 Mar 1996 15:33:48 -0800 (PST)
Received: (from wpaul@localhost) by skynet.ctr.columbia.edu (8.6.12/8.6.9) id SAA16544; Fri, 22 Mar 1996 18:33:42 -0500
From: Bill Paul <wpaul@skynet.ctr.columbia.edu>
Message-Id: <199603222333.SAA16544@skynet.ctr.columbia.edu>
Subject: Re: flock() and chroot()
To: wpaul@skynet.ctr.columbia.edu (Bill Paul)
Date: Fri, 22 Mar 1996 18:33:41 -0500 (EST)
Cc: current@freebsd.org
In-Reply-To: <199603212142.QAA13188@skynet.ctr.columbia.edu> from "Bill Paul" at Mar 21, 96 04:42:19 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 world, I had to walk into mine 
and say:

> I've got a question concerning file locking:
> 
> I got a bug report recently from a guy trying to use NIS inside a
> chroot()ed environment. Apparently he's created a filesystem tree
> which has the real /var and /dev mounted in it (I'm not sure how he
> did this since he neglected to provide details -- I've asked him
> to elaborate) and has set up a guest user that is placed in this
> confined environment at login.

Nevermind. He's mounting the filesystem using NFS. There's no point
in thinking too hard about NFS file locking the way things are now. :)

I'm going to try fixing the problem with _yp_dobind() this weekend.

-Bill

-- 
=============================================================================
-Bill Paul            (212) 854-6020 | System Manager
Work:         wpaul@ctr.columbia.edu | Center for Telecommunications Research
Home:  wpaul@skynet.ctr.columbia.edu | Columbia University, New York City
=============================================================================
License error: The license for this .sig file has expired. You must obtain
a new license key before any more witty phrases will appear in this space.
=============================================================================

From owner-freebsd-current  Fri Mar 22 15:45:09 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id PAA12721
          for current-outgoing; Fri, 22 Mar 1996 15:45:09 -0800 (PST)
Received: from jhome.DIALix.COM (root@jhome.DIALix.COM [192.203.228.69])
          by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id PAA12698
          Fri, 22 Mar 1996 15:44:57 -0800 (PST)
Received: from localhost.DIALix.oz.au (peter@localhost.DIALix.oz.au [127.0.0.1]) by jhome.DIALix.COM (8.7.4/8.7.3) with SMTP id HAA07395; Sat, 23 Mar 1996 07:43:56 +0800 (WST)
Message-Id: <199603222343.HAA07395@jhome.DIALix.COM>
X-Authentication-Warning: jhome.DIALix.COM: Host peter@localhost.DIALix.oz.au [127.0.0.1] didn't use HELO protocol
To: John Polstra <jdp@polstra.com>
cc: jkh@time.cdrom.com, freebsd-hubs@freebsd.org, jkh@freebsd.org,
        hackers@freebsd.org, current@freebsd.org
Subject: Re: new sup server 
In-reply-to: Your message of "Fri, 22 Mar 1996 13:37:17 PST."
             <199603222137.NAA26670@austin.polstra.com> 
Date: Sat, 23 Mar 1996 07:43:55 +0800
From: Peter Wemm <peter@jhome.DIALix.COM>
Sender: owner-current@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

>Jordan wrote:
>
>> > I suspect that Jordan will be trimming off sup's from non-official-mirror
>> > sites real soon now to reduce the load on freefall and the T1.
>> 
>> You suspect correctly.
>
>PLEASE don't do that yet!  I am telling you again: the sup mirrors still
>do NOT work right.

Am I the only one that thinks that using sup to feed the sup mirrors is
*extemely* prone to error?  The script that is run on freefall takes anywhere
between 1.5 and 3 hours to run (depending on what other cron jobs are running
in parallel). That's only a 5 hour window of relative safety for the sup
mirrors to try and get a clean copy.  And, if something goes wrong and a file
is damaged on the mirror but the timestamp is not touched, then it stays
damaged.

And if something happens like the supscan being run from a different
directory, it's a disaster. (eg: freefall's sup having src/ prefixes and a
mirror doing the supscan inside the src directory with no prefix.)

CTM would be *far* better to feed the mirrors with, if only it preserved the
timestamps of the files. (phk: hint hint! :-)

(note: I'm only suggesting the possibility of geting the data to the mirrors
via ctm, not suggesting that the mirrors stop providing sup access once
they've got the data..  big difference..)

I initially got my source via sup, but after several sup botches (way back at
about the 2.0.5 era), I tried CTM. and have *never* had the slightest hiccup
in about a thousand deltas. 

CTM can be a bit of a pain if you're using it on a live source tree, but for
mirrors, having the md5 checksums and the sanity checks that go along with it
is essential for mirroring.  Unfortunately, the lack of timestamp preservation
pretty much rules out ctm if it's for a mirrored sup-server which depends on
the timestamps.

Cheers,
-Peter

From owner-freebsd-current  Fri Mar 22 16:40:01 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id QAA15870
          for current-outgoing; Fri, 22 Mar 1996 16:40:01 -0800 (PST)
Received: from gdi.uoregon.edu (cisco-ts13-line10.uoregon.edu [128.223.150.159])
          by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id QAA15843
          for <freebsd-current@freefall.freebsd.org>; Fri, 22 Mar 1996 16:39:54 -0800 (PST)
Received: (from dwhite@localhost) by gdi.uoregon.edu (8.6.12/8.6.12) id QAA00291; Fri, 22 Mar 1996 16:33:15 -0800
Date: Fri, 22 Mar 1996 16:33:10 -0800 (PST)
From: Doug White <dwhite@riley-net170-164.uoregon.edu>
Reply-To: dwhite@resnet.uoregon.edu
To: "Christoph P. Kukulies" <kuku@gilberto.physik.rwth-aachen.de>
cc: freebsd-current@freefall.freebsd.org
Subject: Re: entropy source: Interrupts in use.
In-Reply-To: <199603221754.SAA29897@gilberto.physik.rwth-aachen.de>
Message-ID: <Pine.BSF.3.91.960322163247.281A-100000@gdi.uoregon.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-current@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

On Fri, 22 Mar 1996, Christoph P. Kukulies wrote:

> 
> What does the bootup message
> 
> Entropy source: Interrupts in use.
> 
> mean?
> 
> Something I should worry about? I added an isdn card to irq 15
> recently.

My guess is that this IRQ is used, probably by a secondary IDE 
controller.  Try using a different IRQ.

Doug White                              | University of Oregon  
Internet:  dwhite@resnet.uoregon.edu    | Residence Networking Assistant
http://gladstone.uoregon.edu/~dwhite    | Computer Science Major


From owner-freebsd-current  Fri Mar 22 17:21:32 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id RAA18563
          for current-outgoing; Fri, 22 Mar 1996 17:21:32 -0800 (PST)
Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19])
          by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id RAA18558
          for <current@freebsd.org>; Fri, 22 Mar 1996 17:21:29 -0800 (PST)
Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.12/8.6.9) id MAA00596; Sat, 23 Mar 1996 12:17:03 +1100
Date: Sat, 23 Mar 1996 12:17:03 +1100
From: Bruce Evans <bde@zeta.org.au>
Message-Id: <199603230117.MAA00596@godzilla.zeta.org.au>
To: scott@statsci.com, terry@lambert.org
Subject: Re: PATCH: small, syntax changes for devfs
Cc: bde@zeta.org.au, current@freebsd.org, julian@ref.tfs.com,
        phk@critter.tfs.com, scrappy@ki.net
Sender: owner-current@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

>> > wd0s1 is there, and opening it would reveal wd0s1[a-h], but this isn't
>> > much use.  Perhaps wd0s1 should be a directory containing [a-h].  I
>> > prefer a flat namespace.
>> 
>> Doesn't wd0s1 need to be a device file so you have something to run
>> disklabel against?

Sort of.  You would normally run disklabel on wd0s1c.  wd0s1c and wd0s1
are currently just aliases for each other if a label exists (if there is
no label, than at most wd0s1 exists).  This is mainly for historical
reasons.  The directory layout would be:

                        wd0
                         |
          /-----------------------------\
        wd0s1    wd0s2    wd0s3  ...  wd0s30
          |       ...      ...         ...
  /---------------------------------\
wd0s1a wd0s1b wd0s1c=wd0s1(?) ... wd0s1h

>This is really irrelevant to flat vs. non-flat name spaces.  There is
>no reason why a device file can't be a directory and a file at the
>same time.  Device reads and writes don't care about seek offsets

The semantics aren't clear.  wd0s1 would be a container for both
wd0s1[a-h] and the raw bytes on the device.  I like ordinary read()
to work on directories.

Bruce

From owner-freebsd-current  Fri Mar 22 17:28:51 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id RAA18862
          for current-outgoing; Fri, 22 Mar 1996 17:28:51 -0800 (PST)
Received: from vpm.com (vpm.com [205.162.123.143])
          by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id RAA18851
          for <current@freebsd.org>; Fri, 22 Mar 1996 17:28:37 -0800 (PST)
Received: from netcomsv.netcom.com (pm55.cwo.com [205.162.123.65]) by vpm.com (8.6.12/8.6.12) with SMTP id RAA12388 for <current@freebsd.org>; Fri, 22 Mar 1996 17:30:04 -0800
Message-Id: <199603230130.RAA12388@vpm.com>
X-Sender: mcs@vpm.com
X-Mailer: Windows Eudora Pro Version 2.1.2
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Date: Fri, 22 Mar 1996 17:25:43 -0800
To: current@freebsd.org
From: Mark Stout <mcs@vpm.com>
Sender: owner-current@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

subscribe


From owner-freebsd-current  Fri Mar 22 17:37:31 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id RAA19180
          for current-outgoing; Fri, 22 Mar 1996 17:37:31 -0800 (PST)
Received: from time.cdrom.com (time.cdrom.com [204.216.27.226])
          by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id RAA19175
          Fri, 22 Mar 1996 17:37:28 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by time.cdrom.com (8.7.5/8.6.9) with SMTP id RAA22625; Fri, 22 Mar 1996 17:35:27 -0800 (PST)
To: John Polstra <jdp@polstra.com>
cc: freebsd-hubs@FreeBSD.org, jkh@FreeBSD.org, hackers@FreeBSD.org,
        current@FreeBSD.org
Subject: Re: new sup server 
In-reply-to: Your message of "Fri, 22 Mar 1996 13:37:17 PST."
             <199603222137.NAA26670@austin.polstra.com> 
Date: Fri, 22 Mar 1996 17:35:27 -0800
Message-ID: <22623.827544927@time.cdrom.com>
From: "Jordan K. Hubbard" <jkh@time.cdrom.com>
Sender: owner-current@FreeBSD.org
X-Loop: FreeBSD.org
Precedence: bulk

> PLEASE don't do that yet!  I am telling you again: the sup mirrors still
> do NOT work right.

Don't worry, I'm in no hurry to do this and, as I told Garrett, will not
be cutting off key contributors, simply redundant mirrors when the time
comes.

					Jordan

From owner-freebsd-current  Fri Mar 22 17:37:47 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id RAA19239
          for current-outgoing; Fri, 22 Mar 1996 17:37:47 -0800 (PST)
Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19])
          by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id RAA19225
          for <current@FreeBSD.org>; Fri, 22 Mar 1996 17:37:36 -0800 (PST)
Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.12/8.6.9) id MAA01156; Sat, 23 Mar 1996 12:29:49 +1100
Date: Sat, 23 Mar 1996 12:29:49 +1100
From: Bruce Evans <bde@zeta.org.au>
Message-Id: <199603230129.MAA01156@godzilla.zeta.org.au>
To: bde@zeta.org.au, terry@lambert.org
Subject: Re: PATCH: small, syntax changes for devfs
Cc: current@FreeBSD.org, julian@ref.tfs.com, phk@critter.tfs.com,
        scrappy@ki.net
Sender: owner-current@FreeBSD.org
X-Loop: FreeBSD.org
Precedence: bulk

>> I prefer a flat namespace.

>Why?

- it's easier to search.
- existing programs depend on it.
- it forces you to choose short unambiguous names in a consistent way.
  This is most important for tty names.

I think a layered namespace would need to have zillions of links to
a flat namespace to avoid these problems.

Bruce

From owner-freebsd-current  Fri Mar 22 17:56:16 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id RAA19864
          for current-outgoing; Fri, 22 Mar 1996 17:56:16 -0800 (PST)
Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19])
          by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id RAA19857
          for <freebsd-current@freefall.freebsd.org>; Fri, 22 Mar 1996 17:56:13 -0800 (PST)
Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.12/8.6.9) id MAA02055; Sat, 23 Mar 1996 12:50:33 +1100
Date: Sat, 23 Mar 1996 12:50:33 +1100
From: Bruce Evans <bde@zeta.org.au>
Message-Id: <199603230150.MAA02055@godzilla.zeta.org.au>
To: mrm@sceard.com, terry@lambert.org
Subject: Re: lost+found ???
Cc: freebsd-current@freefall.freebsd.org, joerg_wunsch@uriah.heep.sax.de
Sender: owner-current@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

>On the subject of the 8k, Bruce is wrong about the requirements: the
>most you have to deal with is the number of files allowed to be a
>problem with properly ordered updates: basically, one directory
>worth of names... and in that case, you'll get blocks back from
>the directory that died.  It's still possible to overflow the 16
>additional (reserved) blocks, but it's unlikely.

>Of course if you mount async, all bets are off. 8-(.

I.e., lost+found only works when it is least needed :-).

I think you can lose more than one directory if an inode block for a
directory becomes unreadable.

I wonder if fsck handles huge directories better than ufs.

Bruce

From owner-freebsd-current  Fri Mar 22 19:12:32 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id TAA24098
          for current-outgoing; Fri, 22 Mar 1996 19:12:32 -0800 (PST)
Received: from sequent.kiae.su (sequent.kiae.su [144.206.136.6])
          by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id TAA24092
          Fri, 22 Mar 1996 19:12:25 -0800 (PST)
Received: by sequent.kiae.su id AA18236
  (5.65.kiae-2 ); Sat, 23 Mar 1996 06:08:26 +0300
Received: by sequent.KIAE.su (UUMAIL/2.0); Sat, 23 Mar 96 06:08:26 +0300
Received: (from ache@localhost) by astral.msk.su (8.7.5/8.7.3) id GAA00996; Sat, 23 Mar 1996 06:07:36 +0300 (MSK)
Message-Id: <199603230307.GAA00996@astral.msk.su>
Subject: aic7870 recognized only after second reboot
To: scsi@freebsd.org, current@freebsd.org (FreeBSD-current)
Date: Sat, 23 Mar 1996 06:07:36 +0300 (MSK)
From: =?KOI8-R?Q?=E1=CE=C4=D2=C5=CA_=FE=C5=D2=CE=CF=D7?= (aka Andrey A. Chernov, Black Mage) <ache@astral.msk.su>
X-Class: Fast
X-Mailer: ELM [version 2.4ME+ PL13 (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

First boot didn't find it aic7870.
Second one (Ctrl-Alt-Del) find it, but very strange:
(all this messages not appearse at the first boot)

Mar 22 15:04:50 test /kernel: Probing for devices on the PCI bus:
Mar 22 15:04:50 test /kernel: pci0:0: vendor=0x10b9, device=0x1451, class=bridge (host) [no driver assigned]
Mar 22 15:04:50 test /kernel: chip0 <Intel 82375EB PCI-EISA bridge> rev 4 on pci0:6
Mar 22 15:04:50 test /kernel: ahc0 <Adaptec aic7870 SCSI host adapter> rev 0 int a irq 10 on pci0:10
Mar 22 15:04:50 test /kernel: checksum error
Mar 22 15:04:50 test /kernel: ahc0: SEEPROM read failed, using leftover BIOS values
Mar 22 15:04:50 test /kernel: ahc0: aic7870 Single Channel, SCSI Id=7, aic7870, 16 SCBs
Mar 22 15:04:50 test /kernel: ahc0 waiting for scsi devices to settle
Mar 22 15:04:51 test /kernel: (ahc0:0:0): "IBM DPES-31080 S31Q" type 0 fixed SCSI 2
Mar 22 15:04:51 test /kernel: sd0(ahc0:0:0): Direct-Access 1034MB (2118144 512 byte sectors)

Controller BIOS comes first correctly in both cases and assign C: to disk.
Next hard reboot did not find it again.
It happens on both 2.1 and -current with equal messages.

Any ideas?

-- 
Andrey A. Chernov        : And I rest so composedly,  /Now, in my bed,
ache@astral.msk.su       : That any beholder  /Might fancy me dead -
http://dt.demos.su/~ache : Might start at beholding me,  /Thinking me dead.
RELCOM Team,FreeBSD Team :         E.A.Poe         From "For Annie" 1849

From owner-freebsd-current  Fri Mar 22 19:50:35 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id TAA26133
          for current-outgoing; Fri, 22 Mar 1996 19:50:35 -0800 (PST)
Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211])
          by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id TAA26122
          for <current@freebsd.org>; Fri, 22 Mar 1996 19:50:29 -0800 (PST)
Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id UAA04412; Fri, 22 Mar 1996 20:43:33 -0700
From: Terry Lambert <terry@lambert.org>
Message-Id: <199603230343.UAA04412@phaeton.artisoft.com>
Subject: Re: PATCH: small, syntax changes for devfs
To: bde@zeta.org.au (Bruce Evans)
Date: Fri, 22 Mar 1996 20:43:33 -0700 (MST)
Cc: scott@statsci.com, terry@lambert.org, bde@zeta.org.au, current@freebsd.org,
        julian@ref.tfs.com, phk@critter.tfs.com, scrappy@ki.net
In-Reply-To: <199603230117.MAA00596@godzilla.zeta.org.au> from "Bruce Evans" at Mar 23, 96 12:17: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

> >This is really irrelevant to flat vs. non-flat name spaces.  There is
> >no reason why a device file can't be a directory and a file at the
> >same time.  Device reads and writes don't care about seek offsets
> 
> The semantics aren't clear.  wd0s1 would be a container for both
> wd0s1[a-h] and the raw bytes on the device.  I like ordinary read()
> to work on directories.

Bletch.  How would I mark a file "Bruce can't see this when he
iterates the directory" if I let you read the directory data?

Or "This file is still here, but it has been marked deleted so
that the user can use 'undelete' on it later because he's the kind
of silly git who deletes first and thinks second".

There's a lot of useful things you can do with directory data if
it's considered opaque.

Plus your application would need to have all sorts of hooks for
each possible directory layout on disk -- that's exactly what
getdirentries() is trying to avoid.

Even if we bought into your idea, we could still have an ioctl()
that means "convert this fd which is a directory reference in
the devfs to point to a venode for a devices instead".  Since
the current utilities all operate on terminal devices instead
of intermediate devices anyway, this wouldn't damage backward
compatability.


					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 Mar 22 19:54:06 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id TAA26286
          for current-outgoing; Fri, 22 Mar 1996 19:54:06 -0800 (PST)
Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211])
          by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id TAA26279
          for <current@FreeBSD.org>; Fri, 22 Mar 1996 19:53:57 -0800 (PST)
Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id UAA04429; Fri, 22 Mar 1996 20:47:08 -0700
From: Terry Lambert <terry@lambert.org>
Message-Id: <199603230347.UAA04429@phaeton.artisoft.com>
Subject: Re: PATCH: small, syntax changes for devfs
To: bde@zeta.org.au (Bruce Evans)
Date: Fri, 22 Mar 1996 20:47:08 -0700 (MST)
Cc: bde@zeta.org.au, terry@lambert.org, current@FreeBSD.org,
        julian@ref.tfs.com, phk@critter.tfs.com, scrappy@ki.net
In-Reply-To: <199603230129.MAA01156@godzilla.zeta.org.au> from "Bruce Evans" at Mar 23, 96 12:29:49 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 prefer a flat namespace.
> 
> >Why?
> 
> - it's easier to search.
> - existing programs depend on it.
> - it forces you to choose short unambiguous names in a consistent way.
>   This is most important for tty names.
> 
> I think a layered namespace would need to have zillions of links to
> a flat namespace to avoid these problems.

Counterexamples:

1)	/dev/pty/000 (a cloning pty device driver instead of fixed
	allocation and a kernel rebuild).

2)	A physical device with a changer with a DOS partition table
	on one of the spindles, with an extended partition on one
	of the partitions with a BSD disklabel on one of the
	extended partitions...


					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 Mar 22 20:06:34 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id UAA26787
          for current-outgoing; Fri, 22 Mar 1996 20:06:34 -0800 (PST)
Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211])
          by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id UAA26778
          for <freebsd-current@freefall.freebsd.org>; Fri, 22 Mar 1996 20:06:26 -0800 (PST)
Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id UAA04471; Fri, 22 Mar 1996 20:59:16 -0700
From: Terry Lambert <terry@lambert.org>
Message-Id: <199603230359.UAA04471@phaeton.artisoft.com>
Subject: Re: lost+found ???
To: bde@zeta.org.au (Bruce Evans)
Date: Fri, 22 Mar 1996 20:59:15 -0700 (MST)
Cc: mrm@sceard.com, terry@lambert.org, freebsd-current@freefall.freebsd.org,
        joerg_wunsch@uriah.heep.sax.de
In-Reply-To: <199603230150.MAA02055@godzilla.zeta.org.au> from "Bruce Evans" at Mar 23, 96 12:50:33 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

> >On the subject of the 8k, Bruce is wrong about the requirements: the
> >most you have to deal with is the number of files allowed to be a
> >problem with properly ordered updates: basically, one directory
> >worth of names... and in that case, you'll get blocks back from
> >the directory that died.  It's still possible to overflow the 16
> >additional (reserved) blocks, but it's unlikely.
> 
> >Of course if you mount async, all bets are off. 8-(.
> 
> I.e., lost+found only works when it is least needed :-).

Not true.  If you are running async, you are obviously willing
to newfs the partition when you reboot after a crash.  I've only
barely refrained from suggesting we change the option name from
"async" to "i_am_willing_to_newfs_the_partition_after_a_crash".

It's a good idea, but those of us who are too gung-ho to wait for
the writes to be done correctly are probably also too gung-ho to
be done typing the mount command to get onto typing the next
command after that, so it would never fly.

Using "async" instead of, for instance, hacking in soft updates
to get the same speed effect without the attendant risks, is the
moral equivalent of picking up the soap in a Shawshank shower.
You're just *asking* for it... eventually, you will be obliged
...your power supply will fail, or your UPS will fail during a
power outage, or a cable will vibrate loose, etc., etc..


> I think you can lose more than one directory if an inode block for a
> directory becomes unreadable.

More than one directory entry; not more than the contents of one
directory, at least in the case of soft failures with properly
ordered metadata writes.

> I wonder if fsck handles huge directories better than ufs.

Huh? What?  This is a non-sequitur, as far as I can tell... fsck
is a ufs utility -- it must handle them the same.


					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 Mar 22 20:50:50 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id UAA28680
          for current-outgoing; Fri, 22 Mar 1996 20:50:50 -0800 (PST)
Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19])
          by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id UAA28674
          for <freebsd-current@freefall.freebsd.org>; Fri, 22 Mar 1996 20:50:46 -0800 (PST)
Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.12/8.6.9) id PAA08953; Sat, 23 Mar 1996 15:44:44 +1100
Date: Sat, 23 Mar 1996 15:44:44 +1100
From: Bruce Evans <bde@zeta.org.au>
Message-Id: <199603230444.PAA08953@godzilla.zeta.org.au>
To: bde@zeta.org.au, terry@lambert.org
Subject: Re: lost+found ???
Cc: freebsd-current@freefall.freebsd.org, joerg_wunsch@uriah.heep.sax.de,
        mrm@sceard.com
Sender: owner-current@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

>> >Of course if you mount async, all bets are off. 8-(.
>> 
>> I.e., lost+found only works when it is least needed :-).

>Not true.  If you are running async, you are obviously willing
>to newfs the partition when you reboot after a crash.  I've only
>barely refrained from suggesting we change the option name from
>"async" to "i_am_willing_to_newfs_the_partition_after_a_crash".

Yes, I expect to lose it all after every 1000-100000 crashes.

>Using "async" instead of, for instance, hacking in soft updates
>to get the same speed effect without the attendant risks, is the
>moral equivalent of picking up the soap in a Shawshank shower.
>You're just *asking* for it... eventually, you will be obliged
>...your power supply will fail, or your UPS will fail during a
>power outage, or a cable will vibrate loose, etc., etc..

Or the disk drive will fail.  In my experience, total disk drive
failures are more common than total losses of async file systems,
except when the file system or disk driver is buggy.

Please send followups to alt.flame.fs.metadata.

>> I think you can lose more than one directory if an inode block for a
>> directory becomes unreadable.

>More than one directory entry; not more than the contents of one
>directory, at least in the case of soft failures with properly
>ordered metadata writes.

Oops, I meant a block that happens to contain the inodes for lots of
directories.  This seems to be the worst case for the loss of a single
ufs block.

>> I wonder if fsck handles huge directories better than ufs.

>Huh? What?  This is a non-sequitur, as far as I can tell... fsck
>is a ufs utility -- it must handle them the same.

ufs is slow for huge directories.  fsck would probably be slower if
it used similar algorithms.  However, it knows that it only needs to
append to lost+found (at least after it has started expanding lost+found)
so it need not be slower than O(n) (n = number of files in lost+found).

Bruce

From owner-freebsd-current  Fri Mar 22 21:25:01 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id VAA29985
          for current-outgoing; Fri, 22 Mar 1996 21:25:01 -0800 (PST)
Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211])
          by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id VAA29976
          for <freebsd-current@freefall.freebsd.org>; Fri, 22 Mar 1996 21:24:59 -0800 (PST)
Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id WAA04946; Fri, 22 Mar 1996 22:18:00 -0700
From: Terry Lambert <terry@lambert.org>
Message-Id: <199603230518.WAA04946@phaeton.artisoft.com>
Subject: Re: lost+found ???
To: bde@zeta.org.au (Bruce Evans)
Date: Fri, 22 Mar 1996 22:18:00 -0700 (MST)
Cc: bde@zeta.org.au, terry@lambert.org, freebsd-current@freefall.freebsd.org,
        joerg_wunsch@uriah.heep.sax.de, mrm@sceard.com
In-Reply-To: <199603230444.PAA08953@godzilla.zeta.org.au> from "Bruce Evans" at Mar 23, 96 03:44: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

> Or the disk drive will fail.  In my experience, total disk drive
> failures are more common than total losses of async file systems,
> except when the file system or disk driver is buggy.
> 
> Please send followups to alt.flame.fs.metadata.

8-).

> >> I think you can lose more than one directory if an inode block for a
> >> directory becomes unreadable.
> 
> >More than one directory entry; not more than the contents of one
> >directory, at least in the case of soft failures with properly
> >ordered metadata writes.
> 
> Oops, I meant a block that happens to contain the inodes for lots of
> directories.  This seems to be the worst case for the loss of a single
> ufs block.

I think what would happen is the directories would be placed in
lost+found as inode-number-named-files, and their contents would
remain untouched -- were you thinking there would be a cascade
of files going into lost+found from each of the munged directories?

> >> I wonder if fsck handles huge directories better than ufs.
> 
> >Huh? What?  This is a non-sequitur, as far as I can tell... fsck
> >is a ufs utility -- it must handle them the same.
> 
> ufs is slow for huge directories.  fsck would probably be slower if
> it used similar algorithms.  However, it knows that it only needs to
> append to lost+found (at least after it has started expanding lost+found)
> so it need not be slower than O(n) (n = number of files in lost+found).

Ah.  I think it only appends, so the answer should be "yes".


					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 Mar 22 21:54:43 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id VAA01718
          for current-outgoing; Fri, 22 Mar 1996 21:54:43 -0800 (PST)
Received: from fw.ast.com (fw.ast.com [165.164.6.25])
          by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id VAA01693
          Fri, 22 Mar 1996 21:54:38 -0800 (PST)
Received: from nemesis by fw.ast.com with uucp
	(Smail3.1.29.1 #3) id m0u0Lpt-0007zaC; Fri, 22 Mar 96 23:25 CST
Received: by nemesis.lonestar.org (Smail3.1.27.1 #20)
	id m0u0LlJ-000DYmC; Fri, 22 Mar 96 23:21 WET
Message-Id: <m0u0LlJ-000DYmC@nemesis.lonestar.org>
Date: Fri, 22 Mar 96 23:21 WET
To: hackers@freebsd.org, current@freebsd.org
From: uhclem@nemesis.lonestar.org (Frank Durda IV)
Sent: Fri Mar 22 1996, 23:21:13 CST
Subject: Crash advice needed APPENDIX B
Cc: uhclem@nemesis.lonestar.org
Sender: owner-current@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk


Thanks for all the responses to my query.  However, it seems
that some other peoples ancedotal experiences got merged with my symptoms
and now people think I have hardware I don't have.   I'll try to
clarify the config and respond to as many of the questions as I can.

1.	The system has a 1540B as stated in the original posting,
	not a 1542C or CF.  It is a 1540B.  (No floppy controller on board.)
	I have been using Rev H boards until tonight when I
	switched to a Rev J to see if that makes any difference.


2.	I was using MCODE F3F7 BIOS BC00 throughout most
	of the tests since changing the SCSI card was one of
	the last things I tried.  
	I then switched to a 1540B rev H with MCODE 3054 BIOS BD00.
	Based on 30 hours, this change increased the failure rate
	dramatically, and ALL of the failures with this second
	board were panics IDENTICAL to this one:
	Fatal trap 12: page fault while in kernel mode
	fault virtual address = 0x10
	fault code = supervisor read, page not present
	instruction pointer = 0x8:0xf01953dc	(_Xintr15+some)
	code segment: base=0x0, limit 0xfffff, type=0x1b
	DPL=0, pres 1, def32 1 gran 1
	processor eflags = resume IOPL=0
	current process = Idle
	Interrupt mask = 	(nothing)
	panic: page fault

	syncing disks...  (which fails to occur)

	While this microcode was in place, uptime fell to about three
	hours per crash and there have been four crashes.  (I am not here
	constantly, so the system just sat at one panic for several
	hours.)

	This sharp increase in panics may indicate some sort of
	incompatibility with FreeBSD and this particular revision of
	Adaptec Microcode.  According to Adaptec it is the latest firmware,
	although it is dated two or three years ago.   This SCSI issue
	may need serious investigation.


3.	This evening, I switched to a 1540B Rev J card with a
	MCODE 3054 BIOS BD00 to see if the failure rate goes down
	at least to previous levels.  This is the third SCSI card tried.
	This config has only been up three hours (it has seven hours of
	catch-up so it is busy) but this isn't long enough for any
	conclusions.


4.	The SCSI cabling consists of an internal ribbon-style cable
	(which has now been replaced three times) no longer than 18".
	The sole internal device is connected to the last connector.
	There are only three connectors TOTAL on the cable.

	The external cable is a round shielded cable with molded CHAMP 50
	connectors on each end which came with the Archive 2150eS.
	This cable is approx 6' long.  I do not have another cable
	to try in this position, but as a next step, I will
	completely remove the tape drive from the system and terminate the
	1540B.   

	The 2150eS uses a CHAMP-50 plug terminator, which is
	installed on the back of the drive cabinet and clamped in
	position.

	So total SCSI length is under 8 Feet.


5.	Termination resistors are NOT installed on the 1540B.

	For those curious about 1540B settings:
		J5 1 8 9 11
		J6 1
		J7 2
		J9 2 6 14
	which translates into:
	J5 1  Synchronous Transfer
	   8  DMA 1 (factory setting)
	   9  IRQ select 0 
	   11 IRQ select 2
	(9+11 and 14 in J9 == IRQ15)
	(DMA transfer speed is set to 5.0MB/s since no jumpers are in place)
	J6 1  BIOS Enable
	J7 2  I/O port 0x330
	J9 2  DRQ 5
	   6  DACK 5
	   14 IRQ 15
	   

6.	Someone asked about the settings on the Barracuda, which is a
	ST12550N (not a NW or ND).   The jumpers are:
	J4-9-10  Delay motor start (10 sec * ID)
	J01- 2-4 Terminator power from pin 26 on the SCSI bus.
	The resistor packs are installed (never removed).
	The drive selected as controller 0.

	If someone thinks drive power for termination would be better,
	I'll try it.  

	In answer to another question, the above settings prevent the
	Barracuda from supplying terminating power to the bus.

	Oh, and the drive has no fear of overheating.  It is mounted
	in a 5.25" bay with 1/2" slot free below and a full slot free
	above.   Brackets and chassis were drilled to increase air flow.
	The system cover has been off since this exercise began.


7.	It has been suggested that I remove the cache.  I'll just
	mention that the cache and the board it is plugged-into were
	both replaced earlier and there was no change in failure rate.
	Further, this board/cache has no trouble with SCO UNIX,
	Windows '95 and Windows NT which have all run on it previously
	(for weeks at a time under heavy stress-loads using a program
	called "evildisk" which is used to qualify hard disk drives).
	The CPU also ran 1.1.5.1 and 2.0.5 which some crashes, but not
	nearly the volume.  Why would the cache "detect" 2.1.0 and fail
	on cue?

	Granted, FreeBSD 2.0.5 did not like the cache when booting
	a compressed kernel.  It would always fail during uncompression.
	This was fixed in 2.1.0 and I have seen no other solid
	errors of that type.

	However, if other substitutions and removals do not correct
	the problem, I will pull the cache module for a period of time.

	Note that I also have three types of cache module I can try:
	Intel 64K and 128K parts, and IDTs pin-compatible 128K version. The
	IDT version happens to be the kind I have been using to date, not
	the Intel one.  (Yes, I do have lots of parts around.)


8.	Yes, the 486DX CPU has been replaced.  It was exchanged when
	the cache was exchanged.   The problem remained.


9.	Someone suggested the EISA config might be strange.  Just
	a reminder that the motherboard was replaced and with it the
	non-volatile EISA/CMOS settings.  Also, there are no timing
	adjustments available via System Configuration/CMOS tools
	on this system.  The ISA bus runs at 8.33MHz.


10.	Someone suggested reseating all socketed parts.   In effect,
	all boards with parts in them have been replaced, so ALL parts
	have been replaced, except peripherals.


11.	Someone suggested building a new kernel with "options DIAGNOSTIC",
	but didn't mention what this will do to/for me.  I will
	go ahead and do this and switch to it on the next crash,
	which should be about 1AM or 5AM if we stick to our time table.


So there we are, perhaps this will eliminate some of the stranger stuff
people were thinking and help focus things down to a short list of
things to try.   Near term, the list appears to be:
	1.	Switch to DIAGNOSTIC kernel.  Won't fix anything, but
		will hopefully scream louder.
	2.	Switch to old BIOS/MCODE on 1540B SCSI adapter.
	3.	Switch SCSI adapter to a different IRQ as this might
		be a problem with spurious interrupt on the master
		controller and the SCSI driver not dealing with it well.
		(Two people suggested getting it off IRQ 15.)
		IRQ 12 is used by the PS/2 mouse, but IRQ 9 is free
		since the network card was removed.  No other IRQs are
		available on the master interrupt controller.
	4.	Abandon Synchronous transfer capability on SCSI adapter.
	5.	Remove cache.  About a 30% system performance hit,
		but I will try it.
	6.	Disconnect floppies.  Might have to leave one to keep
		BIOS from freaking, and this seems like a long shot since
		the floppy drives aren't being used.
	7.	Switch to ALL SCSI.  Expensive at this point in the
		game, and nobody should have to abandon IDE since it
		works fine on many other operating systems.
	8.	By Pentium-class system from Rod.  Ah, yes.  Well that
		might happen once the Triton IIs are stable, but it can't
		happen today.

Again, thanks to all who offered suggestions, even the insane ones!  :-)
No, I can't afford a dual-processor Alpha.  Besides, it doesn't run
FreeBSD today!


Frank Durda IV <uhclem@nemesis.lonestar.org>|"Microsoft Support, can I help
or uhclem%nemesis@rwsystr.nkn.net           | you?"  "Yeah, yuck, yuck, I'd
					    | like to talk to Bill."  "Just
or ...letni!rwsys!nemesis!uhclem	    | a minute..."  



From owner-freebsd-current  Fri Mar 22 22:21:57 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id WAA02603
          for current-outgoing; Fri, 22 Mar 1996 22:21:57 -0800 (PST)
Received: from localhost.cdrom.com (localhost.cdrom.com [127.0.0.1])
          by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id WAA02581
          Fri, 22 Mar 1996 22:21:52 -0800 (PST)
Message-Id: <199603230621.WAA02581@freefall.freebsd.org>
X-Authentication-Warning: freefall.freebsd.org: Host localhost.cdrom.com [127.0.0.1] didn't use HELO protocol
To: uhclem@nemesis.lonestar.org (Frank Durda IV)
cc: hackers@freebsd.org, current@freebsd.org
Subject: Re: Crash advice needed APPENDIX B 
In-reply-to: Your message of "Fri, 22 Mar 1996 23:21:00 +0700."
             <m0u0LlJ-000DYmC@nemesis.lonestar.org> 
Date: Fri, 22 Mar 1996 22:21:52 -0800
From: "Justin T. Gibbs" <gibbs@freefall.freebsd.org>
Sender: owner-current@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

>	In answer to another question, the above settings prevent the
>	Barracuda from supplying terminating power to the bus.
>
>	Oh, and the drive has no fear of overheating.  It is mounted
>	in a 5.25" bay with 1/2" slot free below and a full slot free
>	above.   Brackets and chassis were drilled to increase air flow.
>	The system cover has been off since this exercise began.

Having the cover off usually decreases the air flow around your
drives since there is no negative pressure created by the fans in
your case to pull air in through the face plate and over the drive.
I don't think this is your problem though, but you may want to
keep this in mind in the future.

>	1.	Switch to DIAGNOSTIC kernel.  Won't fix anything, but
>		will hopefully scream louder.

This won't help you track down the problem.

I would suggest modifying the driver so that it reuses the mailboxes
in FIFO order off the free list (use a TAILQ).  This supposedly fixed
a problem on some bt cards that had similar symptoms.

>Frank Durda IV <uhclem@nemesis.lonestar.org>|"Microsoft Support, can I help
>or uhclem%nemesis@rwsystr.nkn.net           | you?"  "Yeah, yuck, yuck, I'd
>					    | like to talk to Bill."  "Just
>or ...letni!rwsys!nemesis!uhclem	    | a minute..."  
>
>

--
Justin T. Gibbs
===========================================
  FreeBSD: Turning PCs into workstations
===========================================

From owner-freebsd-current  Fri Mar 22 22:27:46 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id WAA02843
          for current-outgoing; Fri, 22 Mar 1996 22:27:46 -0800 (PST)
Received: from GndRsh.aac.dev.com (GndRsh.aac.dev.com [198.145.92.241])
          by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id WAA02837
          Fri, 22 Mar 1996 22:27:43 -0800 (PST)
Received: (from rgrimes@localhost) by GndRsh.aac.dev.com (8.6.12/8.6.12) id WAA26014; Fri, 22 Mar 1996 22:23:23 -0800
From: "Rodney W. Grimes" <rgrimes@GndRsh.aac.dev.com>
Message-Id: <199603230623.WAA26014@GndRsh.aac.dev.com>
Subject: Re: Crash advice needed APPENDIX B
To: uhclem@nemesis.lonestar.org (Frank Durda IV)
Date: Fri, 22 Mar 1996 22:23:23 -0800 (PST)
Cc: hackers@freebsd.org, current@freebsd.org, uhclem@nemesis.lonestar.org
In-Reply-To: <m0u0LlJ-000DYmC@nemesis.lonestar.org> from "Frank Durda IV" at Mar 22, 96 11:21:00 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

...
> 6.	Someone asked about the settings on the Barracuda, which is a
> 	ST12550N (not a NW or ND).   The jumpers are:
> 	J4-9-10  Delay motor start (10 sec * ID)
> 	J01- 2-4 Terminator power from pin 26 on the SCSI bus.
> 	The resistor packs are installed (never removed).
> 	The drive selected as controller 0.
> 
> 	If someone thinks drive power for termination would be better,
> 	I'll try it.  

Termination power from the drive is far far far far better...

> 	In answer to another question, the above settings prevent the
> 	Barracuda from supplying terminating power to the bus.

That is fine and also desireable, it also happens to keep scsi bus
induced noise from getting into the termination on the drive.

...
> 
> 7.	It has been suggested that I remove the cache.  I'll just
> 	mention that the cache and the board it is plugged-into were
> 	both replaced earlier and there was no change in failure rate.
> 	Further, this board/cache has no trouble with SCO UNIX,
> 	Windows '95 and Windows NT which have all run on it previously
> 	(for weeks at a time under heavy stress-loads using a program
> 	called "evildisk" which is used to qualify hard disk drives).
> 	The CPU also ran 1.1.5.1 and 2.0.5 which some crashes, but not
> 	nearly the volume.  Why would the cache "detect" 2.1.0 and fail
> 	on cue?

Because SCO Unix, Windows 95 and Windows NT are all gross in the way
they handled bus master DMA disk controllers, they use a dedicated
buffer area that is marked uncacheable just so they can run on the
broken cache coherency motherboards.    Can you say totally defeat
the purpose of bus master DMA buy having the processor bcopy data
around...

> 	Granted, FreeBSD 2.0.5 did not like the cache when booting
> 	a compressed kernel.  It would always fail during uncompression.
> 	This was fixed in 2.1.0 and I have seen no other solid
> 	errors of that type.

Big indication your board does infact have a cache coherency problem.

> 	8.	By Pentium-class system from Rod.  Ah, yes.  Well that
> 		might happen once the Triton IIs are stable, but it can't
> 		happen today.

I like this option for some strange reason :-) :-) :-)  I tried again today
to get PCI/I-P55T2P4 status from ASUS, but they had no new news for me :-(.


-- 
Rod Grimes                                      rgrimes@gndrsh.aac.dev.com
Accurate Automation Company                 Reliable computers for FreeBSD

From owner-freebsd-current  Fri Mar 22 23:12:45 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id XAA06131
          for current-outgoing; Fri, 22 Mar 1996 23:12:45 -0800 (PST)
Received: from localhost.indirect.com (s3.phxslip4.indirect.com [165.247.24.3])
          by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id XAA05991
          for <freebsd-current@FreeBSD.ORG>; Fri, 22 Mar 1996 23:12:05 -0800 (PST)
Received: (from straka@localhost) by localhost.indirect.com (8.6.12/8.6.12) id AAA00353; Sat, 23 Mar 1996 00:07:27 -0700
Date: Sat, 23 Mar 1996 00:06:56 -0700 (MST)
From: "Richard S. Straka" <straka@indirect.com>
X-Sender: straka@localhost
To: freebsd-current@FreeBSD.ORG
Subject: 960321-SNAP - panic: unwire: page not in pmap
Message-ID: <Pine.BSF.3.91.960322234848.282B-100000@localhost>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-current@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk


While booting from the boot floppy in 960321-SNAP, the kernel panics
with the message 

panic: unwire: page not in pmap

My machine is an AMD486DX4/100 with an IDE hard drive and 16MB mem.
This occurs after all the devices are successfully probed and
sysinstall is loading. The screen blanks as if the sysinstall menus
are going to appear and then the panic occurs and the machine locks up.
This problem also occurs with the boot floppies from 960226-SNAP and
960303-SNAP.  Any help solving this problem would be greatly 
appreciated. Thanks in advance.
                                      Richard Straka
                                      straka@indirect.com



From owner-freebsd-current  Sat Mar 23 00:07:26 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id AAA08755
          for current-outgoing; Sat, 23 Mar 1996 00:07:26 -0800 (PST)
Received: from wiley.csusb.edu (wiley.csusb.edu [139.182.2.2])
          by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id AAA08749
          for <freebsd-current@freefall.freebsd.org>; Sat, 23 Mar 1996 00:07:23 -0800 (PST)
Received: (from rmallory@localhost) by wiley.csusb.edu (8.6.11/8.6.11) id AAA27044; Sat, 23 Mar 1996 00:11:09 -0800
From: Rob Mallory <rmallory@wiley.csusb.edu>
Message-Id: <199603230811.AAA27044@wiley.csusb.edu>
Subject: Re: lost+found ???
To: bde@zeta.org.au (Bruce Evans)
Date: Sat, 23 Mar 1996 00:11:08 -0800 (PST)
Cc: bde@zeta.org.au, terry@lambert.org, freebsd-current@freefall.freebsd.org
In-Reply-To: <199603230444.PAA08953@godzilla.zeta.org.au> from "Bruce Evans" at Mar 23, 96 03:44:44 pm
X-Mailer: ELM [version 2.4 PL22]
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

> 
> >> >Of course if you mount async, all bets are off. 8-(.
> >> 
> >> I.e., lost+found only works when it is least needed :-).
> 
> >Not true.  If you are running async, you are obviously willing
> >to newfs the partition when you reboot after a crash.  I've only
> >barely refrained from suggesting we change the option name from
> >"async" to "i_am_willing_to_newfs_the_partition_after_a_crash".
> 
> Yes, I expect to lose it all after every 1000-100000 crashes.
> 
Ummm.. I think I might lean towards Terry's mount -o flag mentioned 
above... knowing which filesystems to "risk" (/usr/obj is good)
and having current backups is good.  Then again, I see newfs/restore
as the perfect "speed-disk" defragger, and -async as a perfect excuse
to defrag my disks every now and then!!

recently, I defragg'd after it lost the "." directory of my /usr/obj 
async mounted filesystem. fuzz-check put a new lost+found in the newly 
created (empty) directory of the async filesystem,,  but I laughed 
when 'df' reported 78% usage! hehe!

((hey--I noticed recently you cant newfs a mounted filesystem like
you could about 4 months ago.:(  I defrag'd my / one time when newfs'ing
what I thought to be a new drive... it was rather cool doing a 
'cat etc/*' after realizing what i really newfs'd,  and watching
the buffer-cache work really well! it actually still "had" a bunch of
files for a few seconds before a major panic! hehe.. freebsd is fun.

-Rob Mallory

From owner-freebsd-current  Sat Mar 23 02:20:42 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id CAA13657
          for current-outgoing; Sat, 23 Mar 1996 02:20:42 -0800 (PST)
Received: from tfs.com (tfs.com [140.145.250.1])
          by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id CAA13637
          Sat, 23 Mar 1996 02:20:34 -0800 (PST)
Received: from critter.tfs.com by tfs.com (smail3.1.28.1) with SMTP
	id m0u0QQx-0003wNC; Sat, 23 Mar 96 02:20 PST
Received: from localhost.tfs.com (localhost.tfs.com [127.0.0.1]) by critter.tfs.com (8.6.12/8.6.12) with SMTP id IAA07430; Sat, 23 Mar 1996 08:00:37 GMT
X-Authentication-Warning: critter.tfs.com: Host localhost.tfs.com didn't use HELO protocol
To: Peter Wemm <peter@jhome.DIALix.COM>
cc: John Polstra <jdp@polstra.com>, jkh@time.cdrom.com,
        freebsd-hubs@FreeBSD.ORG, jkh@FreeBSD.ORG, hackers@FreeBSD.ORG,
        current@FreeBSD.ORG
Subject: Re: new sup server 
In-reply-to: Your message of "Sat, 23 Mar 1996 07:43:55 +0800."
             <199603222343.HAA07395@jhome.DIALix.COM> 
Date: Sat, 23 Mar 1996 08:00:37 +0000
Message-ID: <7428.827568037@critter.tfs.com>
From: Poul-Henning Kamp <phk@critter.tfs.com>
Sender: owner-current@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

> Am I the only one that thinks that using sup to feed the sup mirrors is
> *extemely* prone to error?
no.

> CTM would be *far* better to feed the mirrors with, if only it preserved the
> timestamps of the files. (phk: hint hint! :-)

Well, >anybody< could implement that, hint hint! :-)

> I initially got my source via sup, but after several sup botches (way back at
> about the 2.0.5 era), I tried CTM. and have *never* had the slightest hiccup
> in about a thousand deltas. 
:-)

--
Poul-Henning Kamp           | phk@FreeBSD.ORG       FreeBSD Core-team.
http://www.freebsd.org/~phk | phk@login.dknet.dk    Private mailbox.
whois: [PHK]                | phk@ref.tfs.com       TRW Financial Systems, Inc.
Future will arrive by its own means, progress not so.

From owner-freebsd-current  Sat Mar 23 03:13:42 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id DAA15666
          for current-outgoing; Sat, 23 Mar 1996 03:13:42 -0800 (PST)
Received: from zit1.zit.th-darmstadt.de (zit1.zit.th-darmstadt.de [130.83.63.20])
          by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id DAA15659
          Sat, 23 Mar 1996 03:13:38 -0800 (PST)
Received: from [130.83.63.13] (apfel.zit.th-darmstadt.de [130.83.63.13]) by zit1.zit.th-darmstadt.de (8.7.5/8.6.9) with SMTP id MAA04112; Sat, 23 Mar 1996 12:13:23 +0100 (MET)
X-Sender: petzi@zit1.zit.th-darmstadt.de
Message-Id: <v02140b00ad7982a00ce0@[130.83.63.13]>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Date: Sat, 23 Mar 1996 12:13:29 +0100
To: John Polstra <jdp@polstra.com>
From: petzi@zit.th-darmstadt.de (Michael Beckmann)
Subject: Re: new sup server
Cc: freebsd-hubs@freebsd.org, jkh@freebsd.org, hackers@freebsd.org,
        current@freebsd.org
Sender: owner-current@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

> I am telling you again: the sup mirrors still
>do NOT work right.

I must agree with that. I tried to run a sup mirror in Germany, but have
never been able to make world or build a kernel with the sources from that
mirror. There has always been corruption of the source tree.

Due to the highly loaded intercontinental lines, the sup updates from
Freefall can take several hours, and in rare cases, (in particular if
freefall doesn't let me in due to its ten user limit) they aren't finished
until next night. It appears that the situation has improved somewhat with
the new Internet connection of Freefall, though, which doesn't route
through MCI/BBNPlanet any more.

I would really like to provide some service for up-to-date FreeBSD sources
in Europe, but sup simply doesn't work right under these conditions. I
wouldn't mind the updates taking several hours, but I do mind getting
garbled sources. They cost me a lot of time already.

Michael



From owner-freebsd-current  Sat Mar 23 04:43:49 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id EAA20396
          for current-outgoing; Sat, 23 Mar 1996 04:43:49 -0800 (PST)
Received: from grumble.grondar.za (root@grumble.grondar.za [196.7.18.130])
          by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id EAA20391
          for <freebsd-current@freefall.freebsd.org>; Sat, 23 Mar 1996 04:43:37 -0800 (PST)
Received: from grumble.grondar.za (mark@localhost [127.0.0.1]) by grumble.grondar.za (8.7.5/8.7.3) with ESMTP id OAA00694; Sat, 23 Mar 1996 14:42:54 +0200 (SAT)
Message-Id: <199603231242.OAA00694@grumble.grondar.za>
To: "Christoph P. Kukulies" <kuku@gilberto.physik.rwth-aachen.de>
cc: freebsd-current@freefall.freebsd.org
Subject: Re: entropy source: Interrupts in use. 
Date: Sat, 23 Mar 1996 14:42:54 +0200
From: Mark Murray <mark@grondar.za>
Sender: owner-current@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

"Christoph P. Kukulies" wrote:
> 
> What does the bootup message
> 
> Entropy source: Interrupts in use.
> 
> mean?
> 
> Something I should worry about? I added an isdn card to irq 15
> recently.

Look at random(4) for more info. /dev/random hooks into some interrupts
as sources of entropy.

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 Mar 23 09:06:44 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id JAA28852
          for current-outgoing; Sat, 23 Mar 1996 09:06:44 -0800 (PST)
Received: from time.cdrom.com (time.cdrom.com [204.216.27.226])
          by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id JAA28847
          for <current@freebsd.org>; Sat, 23 Mar 1996 09:06:42 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by time.cdrom.com (8.7.5/8.6.9) with SMTP id JAA05785 for <current@freebsd.org>; Sat, 23 Mar 1996 09:06:26 -0800 (PST)
To: current@freebsd.org
Subject: Bleah!  Who broke this recently?!
Date: Sat, 23 Mar 1996 09:06:26 -0800
Message-ID: <5783.827600786@time.cdrom.com>
From: "Jordan K. Hubbard" <jkh@time.cdrom.com>
Sender: owner-current@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

-DFAILSAFE -DCOMPAT_43 -DCD9660 -DMSDOSFS -DNFS -DFFS -DINET -DKERNEL  ../../pci/if_de.c
../../pci/if_de.c: In function `tulip_ioctl':
../../pci/if_de.c:1886: structure has no member named `ac_ipaddr'
*** Error code 1

It worked just 2 days ago..  So much for the SNAP I was rolling.. :-(

						Jordan

From owner-freebsd-current  Sat Mar 23 09:33:37 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id JAA29653
          for current-outgoing; Sat, 23 Mar 1996 09:33:37 -0800 (PST)
Received: from rocky.sri.MT.net (rocky.sri.MT.net [204.182.243.10])
          by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id JAA29648
          for <current@freebsd.org>; Sat, 23 Mar 1996 09:33:35 -0800 (PST)
Received: (from nate@localhost) by rocky.sri.MT.net (8.6.12/8.6.12) id KAA21397; Sat, 23 Mar 1996 10:33:28 -0700
Date: Sat, 23 Mar 1996 10:33:28 -0700
From: Nate Williams <nate@sri.MT.net>
Message-Id: <199603231733.KAA21397@rocky.sri.MT.net>
To: "Jordan K. Hubbard" <jkh@time.cdrom.com>
Cc: current@freebsd.org
Subject: Re: Bleah!  Who broke this recently?!
In-Reply-To: <5783.827600786@time.cdrom.com>
References: <5783.827600786@time.cdrom.com>
Sender: owner-current@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

> -DFAILSAFE -DCOMPAT_43 -DCD9660 -DMSDOSFS -DNFS -DFFS -DINET -DKERNEL  ../../pci/if_de.c
> ../../pci/if_de.c: In function `tulip_ioctl':
> ../../pci/if_de.c:1886: structure has no member named `ac_ipaddr'
> *** Error code 1
> 
> It worked just 2 days ago..  So much for the SNAP I was rolling.. :-(
> 

netinet/if_ether.[ch]
===================================================
revision 1.14
date: 1996/03/23 01:32:30;  author: fenner;  state: Exp;  lines: +1 -2
Send ARP's for aliased subnets with the proper source address.
Get rid of ac->ac_ipaddr and arpwhohas() since they assume that
an interface has only one address.

Obtained from:  BSD/OS 2.1, via Rich Stevens <rstevens@noao.edu>
===================================================


Nate

From owner-freebsd-current  Sat Mar 23 09:42:00 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id JAA29858
          for current-outgoing; Sat, 23 Mar 1996 09:42:00 -0800 (PST)
Received: from time.cdrom.com (time.cdrom.com [204.216.27.226])
          by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id JAA29853
          for <current@freebsd.org>; Sat, 23 Mar 1996 09:41:58 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by time.cdrom.com (8.7.5/8.6.9) with SMTP id JAA06785; Sat, 23 Mar 1996 09:41:37 -0800 (PST)
To: Nate Williams <nate@sri.MT.net>
cc: current@freebsd.org
Subject: Re: Bleah! Who broke this recently?! 
In-reply-to: Your message of "Sat, 23 Mar 1996 10:33:28 MST."
             <199603231733.KAA21397@rocky.sri.MT.net> 
Date: Sat, 23 Mar 1996 09:41:37 -0800
Message-ID: <6783.827602897@time.cdrom.com>
From: "Jordan K. Hubbard" <jkh@time.cdrom.com>
Sender: owner-current@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

> netinet/if_ether.[ch]
> ===================================================
> revision 1.14
> date: 1996/03/23 01:32:30;  author: fenner;  state: Exp;  lines: +1 -2
> Send ARP's for aliased subnets with the proper source address.
> Get rid of ac->ac_ipaddr and arpwhohas() since they assume that
> an interface has only one address.
> 
> Obtained from:  BSD/OS 2.1, via Rich Stevens <rstevens@noao.edu>

Yup, I just derived the same information.  I'm grubbing through the
header files right now trying to figure out just what the heck Garrett
intended, and I've also sent him a letter chewing him out for very
clearly failing to test this before committing it (a quick compile of
GENERIC would have pointed it up in minutes).

Oh well.  It's just especially annoying to come in expecting to see a
snapshot rolled and finding an error instead.  At least it was fairly
far along before croaking, but until I find a fix for this my snapshot
CD is dead in the water..  Sigh...

						Jordan

From owner-freebsd-current  Sat Mar 23 09:42:43 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id JAA29893
          for current-outgoing; Sat, 23 Mar 1996 09:42:43 -0800 (PST)
Received: from rocky.sri.MT.net (rocky.sri.MT.net [204.182.243.10])
          by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id JAA29888
          Sat, 23 Mar 1996 09:42:40 -0800 (PST)
Received: (from nate@localhost) by rocky.sri.MT.net (8.6.12/8.6.12) id KAA21415; Sat, 23 Mar 1996 10:42:33 -0700
Date: Sat, 23 Mar 1996 10:42:33 -0700
From: Nate Williams <nate@sri.MT.net>
Message-Id: <199603231742.KAA21415@rocky.sri.MT.net>
To: "Jordan K. Hubbard" <jkh@time.cdrom.com>
Cc: fenner@FreeBSd.org, current@FreeBSd.org
Subject: Re: Bleah!  Who broke this recently?!
In-Reply-To: <5783.827600786@time.cdrom.com>
References: <5783.827600786@time.cdrom.com>
Sender: owner-current@FreeBSd.org
X-Loop: FreeBSD.org
Precedence: bulk

Jordan K. Hubbard writes:
> -DFAILSAFE -DCOMPAT_43 -DCD9660 -DMSDOSFS -DNFS -DFFS -DINET -DKERNEL  ../../pci/if_de.c
> ../../pci/if_de.c: In function `tulip_ioctl':
> ../../pci/if_de.c:1886: structure has no member named `ac_ipaddr'

/sys/pci/if_pdq.c
/sys/pci/if_de.c
/sys/i386/isa/if_le.c
/sys/i386/isa/if_zp.c

All rely on ac_ipaddr, which no longer exists.

The code from if_zp.c & if_le.c is:
    if (sc->le_ac.ac_ipaddr.s_addr != 0) {
        le_multi_op(sc, etherbroadcastaddr, TRUE);
        sc->le_flags |= LE_BRDCSTONLY|IFF_MULTICAST;
    }

I'm not sure, but you may be able to remove the check and always set
the flags on the other two devices, and in if_pdq.c and if_de.c the line
referencing ac_ipaddr can be deleted.


Nate

From owner-freebsd-current  Sat Mar 23 09:42:47 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id JAA29914
          for current-outgoing; Sat, 23 Mar 1996 09:42:47 -0800 (PST)
Received: from time.cdrom.com (time.cdrom.com [204.216.27.226])
          by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id JAA29906
          for <current@freebsd.org>; Sat, 23 Mar 1996 09:42:45 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by time.cdrom.com (8.7.5/8.6.9) with SMTP id JAA06838 for <current@freebsd.org>; Sat, 23 Mar 1996 09:42:29 -0800 (PST)
To: current@freebsd.org
Subject: This also worries me..
Date: Sat, 23 Mar 1996 09:42:29 -0800
Message-ID: <6836.827602949@time.cdrom.com>
From: "Jordan K. Hubbard" <jkh@time.cdrom.com>
Sender: owner-current@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

cc -c -O -W -Wreturn-type -Wcomment -Wredundant-decls -Wimplicit  -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes  -Winline  -nostdinc -I. -I../.. -I../../sys -I../../../include -DI386_CPU -DI486_CPU -DI586_CPU -DI686_CPU -DATAPI -DFAILSAFE -DCOMPAT_43 -DCD9660 -DMSDOSFS -DNFS -DFFS -DINET -DKERNEL  ../../netinet/in_proto.c
../../netinet/in_proto.c:99: warning: initialization from incompatible pointer type
../../netinet/in_proto.c:115: warning: initialization from incompatible pointer type
../../netinet/in_proto.c:115: warning: initialization from incompatible pointer type
../../netinet/in_proto.c:120: warning: initialization from incompatible pointer type
../../netinet/in_proto.c:124: warning: initialization from incompatible pointer type
../../netinet/in_proto.c:129: warning: initialization from incompatible pointer type
../../netinet/in_proto.c:134: warning: initialization from incompatible pointer type
../../netinet/in_proto.c:169: warning: initialization from incompatible pointer type
../../netinet/in_proto.c:169: warning: initialization from incompatible pointer type

Groan.

					Jordan

From owner-freebsd-current  Sat Mar 23 09:51:49 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id JAA00410
          for current-outgoing; Sat, 23 Mar 1996 09:51:49 -0800 (PST)
Received: from time.cdrom.com (time.cdrom.com [204.216.27.226])
          by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id JAA00405
          Sat, 23 Mar 1996 09:51:47 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by time.cdrom.com (8.7.5/8.6.9) with SMTP id JAA06898; Sat, 23 Mar 1996 09:51:31 -0800 (PST)
To: wollman@freebsd.org
cc: current@freebsd.org
Subject: Whoops!  My apologies!!
Date: Sat, 23 Mar 1996 09:51:31 -0800
Message-ID: <6896.827603491@time.cdrom.com>
From: "Jordan K. Hubbard" <jkh@time.cdrom.com>
Sender: owner-current@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

I incorrectly targeted Garrett as the perpetrator of the latest
brokenness (and left a message on his phone) - it was NOT Garrett!
Garrett, my fervent apologies.

It appears that Mr. Fenner is the more appropriate target of my
wrath..  Grrrr!

					Jordan

From owner-freebsd-current  Sat Mar 23 11:05:17 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id LAA03090
          for current-outgoing; Sat, 23 Mar 1996 11:05:17 -0800 (PST)
Received: from lear35.cytex.com (root@lear35.cytex.com [38.252.97.5])
          by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id LAA03083
          for <freebsd-current@freebsd.org>; Sat, 23 Mar 1996 11:05:15 -0800 (PST)
Received: (from mbartley@localhost) by lear35.cytex.com (8.7.5/8.6.12) id LAA02099 for freebsd-current@freebsd.org; Sat, 23 Mar 1996 11:05:13 -0800 (PST)
From: Matt Bartley <mbartley@lear35.cytex.com>
Message-Id: <199603231905.LAA02099@lear35.cytex.com>
Subject: kern/subr_prf.c
To: freebsd-current@freebsd.org
Date: Sat, 23 Mar 1996 11:05:13 -0800 (PST)
X-Mailer: ELM [version 2.4ME+ PL13 (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 just ran sup this morning.  This is what happened when I tried to
recompile the kernel:

cc -c -O -W -Wreturn-type -Wcomment -Wredundant-decls -Wimplicit
  -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes  -Winline
  -nostdinc -I. -I../.. -I../../sys -I../../../include -DI386_CPU -DI486_CPU
  -DI586_CPU -DI686_CPU -DATAPI -DFAILSAFE -DCOMPAT_43 -DCD9660 -DMSDOSFS
  -DNFS -DFFS -DINET -DKERNEL  ../../kern/subr_prf.c
../../kern/subr_prf.c: In function `panic':
../../kern/subr_prf.c:123: `debugger_on_panic' undeclared (first use this
  function)
../../kern/subr_prf.c:123: (Each undeclared identifier is reported only once
../../kern/subr_prf.c:123: for each function it appears in.)
*** Error code 1

Stop.

That was with the GENERIC kernel - I tried that after my custom kernel
failed the same way.

from kern/subr_prf.c:
debugger_on_panic is declared
----------------------------------------------------------------------
#if defined(DDB) || defined (KGDB)
#ifdef DDB_UNATTENDED
	static int debugger_on_panic = 0;
#else
	static int debugger_on_panic = 1;
#endif

SYSCTL_INT(_debug, OID_AUTO, debugger_on_panic, CTLFLAG_RW,
	&debugger_on_panic, 0, "");
#endif
----------------------------------------------------------------------
here is where it failed in compile, at the end of the fuction panic():
----------------------------------------------------------------------
	printf("\n");

	if (debugger_on_panic) {              <---- source of error
#ifdef KGDB
		kgdb_panic();
#endif
#ifdef DDB
		Debugger ("panic");
#endif
	}
	boot(bootopt);
}
----------------------------------------------------------------------

From owner-freebsd-current  Sat Mar 23 11:06:01 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id LAA03160
          for current-outgoing; Sat, 23 Mar 1996 11:06:01 -0800 (PST)
Received: from alpha.xerox.com (alpha.Xerox.COM [13.1.64.93])
          by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id LAA03153
          for <current@freebsd.org>; Sat, 23 Mar 1996 11:05:59 -0800 (PST)
Received: from crevenia.parc.xerox.com ([13.2.116.11]) by alpha.xerox.com with SMTP id <15198(12)>; Sat, 23 Mar 1996 11:05:26 PST
Received: from localhost by crevenia.parc.xerox.com with SMTP id <177478>; Sat, 23 Mar 1996 11:05:21 -0800
To: Nate Williams <nate@sri.mt.net>
cc: "Jordan K. Hubbard" <jkh@time.cdrom.com>, current@freebsd.org,
        fenner@parc.xerox.com
Subject: Re: Bleah! Who broke this recently?! 
In-reply-to: Your message of "Sat, 23 Mar 96 09:42:33 PST."
             <199603231742.KAA21415@rocky.sri.MT.net> 
Date: Sat, 23 Mar 1996 11:05:09 PST
From: Bill Fenner <fenner@parc.xerox.com>
Message-Id: <96Mar23.110521pst.177478@crevenia.parc.xerox.com>
Sender: owner-current@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

In message <199603231742.KAA21415@rocky.sri.MT.net> you write:
>Jordan K. Hubbard writes:
>> -DFAILSAFE -DCOMPAT_43 -DCD9660 -DMSDOSFS -DNFS -DFFS -DINET -DKERNEL  ../..
>  /pci/if_de.c
>> ../../pci/if_de.c: In function `tulip_ioctl':
>> ../../pci/if_de.c:1886: structure has no member named `ac_ipaddr'

Argh, that's what I get for depending on "make depend".  Sorry, folks, my
bad.  These were all abstraction violations anyway, why does the driver
care about the address that ARP's get sent on?  But I'll go try to fix things
or back my change out.

  Bill

From owner-freebsd-current  Sat Mar 23 12:15:00 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id MAA08123
          for current-outgoing; Sat, 23 Mar 1996 12:15:00 -0800 (PST)
Received: from alpha.xerox.com (alpha.Xerox.COM [13.1.64.93])
          by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id MAA08118
          Sat, 23 Mar 1996 12:14:58 -0800 (PST)
Received: from crevenia.parc.xerox.com ([13.2.116.11]) by alpha.xerox.com with SMTP id <14485(1)>; Sat, 23 Mar 1996 12:14:22 PST
Received: from localhost by crevenia.parc.xerox.com with SMTP id <177478>; Sat, 23 Mar 1996 12:14:11 -0800
To: "Jordan K. Hubbard" <jkh@time.cdrom.com>
cc: wollman@freebsd.org, current@freebsd.org
Subject: Re: Whoops! My apologies!! 
In-reply-to: Your message of "Sat, 23 Mar 96 09:51:31 PST."
             <6896.827603491@time.cdrom.com> 
Date: Sat, 23 Mar 1996 12:13:59 PST
From: Bill Fenner <fenner@parc.xerox.com>
Message-Id: <96Mar23.121411pst.177478@crevenia.parc.xerox.com>
Sender: owner-current@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

In message <6896.827603491@time.cdrom.com> you write:
>It appears that Mr. Fenner is the more appropriate target of my
>wrath..  Grrrr!

My humblest apologies.  I hereby swear that I will never make a commit
again without building an entire GENERIC kernel from scratch with my
commit in place, no matter how well I think I know the ramifications.

  Bill

From owner-freebsd-current  Sat Mar 23 12:57:42 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id MAA10249
          for current-outgoing; Sat, 23 Mar 1996 12:57:42 -0800 (PST)
Received: from time.cdrom.com (time.cdrom.com [204.216.27.226])
          by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id MAA10244
          Sat, 23 Mar 1996 12:57:39 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by time.cdrom.com (8.7.5/8.6.9) with SMTP id MAA07397; Sat, 23 Mar 1996 12:57:18 -0800 (PST)
To: Bill Fenner <fenner@parc.xerox.com>
cc: wollman@freebsd.org, current@freebsd.org
Subject: Re: Whoops! My apologies!! 
In-reply-to: Your message of "Sat, 23 Mar 1996 12:13:59 PST."
             <96Mar23.121411pst.177478@crevenia.parc.xerox.com> 
Date: Sat, 23 Mar 1996 12:57:16 -0800
Message-ID: <7395.827614636@time.cdrom.com>
From: "Jordan K. Hubbard" <jkh@time.cdrom.com>
Sender: owner-current@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

Well, I in turn must apologies for flying off the handle.  I was just
really really hoping to get this SNAP albatros from around my neck
this weekend and this sudden failure had me in visions of Monday
coming with nothing to show.  Your prompt attention to the problem
has been most appreciated!

					Jordan

> In message <6896.827603491@time.cdrom.com> you write:
> >It appears that Mr. Fenner is the more appropriate target of my
> >wrath..  Grrrr!
> 
> My humblest apologies.  I hereby swear that I will never make a commit
> again without building an entire GENERIC kernel from scratch with my
> commit in place, no matter how well I think I know the ramifications.
> 
>   Bill


From owner-freebsd-current  Sat Mar 23 13:02:30 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id NAA10661
          for current-outgoing; Sat, 23 Mar 1996 13:02:30 -0800 (PST)
Received: from localhost.cdrom.com (localhost.cdrom.com [127.0.0.1])
          by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id NAA10649
          Sat, 23 Mar 1996 13:02:26 -0800 (PST)
Message-Id: <199603232102.NAA10649@freefall.freebsd.org>
X-Authentication-Warning: freefall.freebsd.org: Host localhost.cdrom.com [127.0.0.1] didn't use HELO protocol
To: Bill Fenner <fenner@parc.xerox.com>
cc: "Jordan K. Hubbard" <jkh@time.cdrom.com>, wollman@FreeBSD.org,
        current@FreeBSD.org
Subject: Re: Whoops! My apologies!! 
In-reply-to: Your message of "Sat, 23 Mar 1996 12:13:59 PST."
             <96Mar23.121411pst.177478@crevenia.parc.xerox.com> 
Date: Sat, 23 Mar 1996 13:02:25 -0800
From: "Justin T. Gibbs" <gibbs@freefall.freebsd.org>
Sender: owner-current@FreeBSD.org
X-Loop: FreeBSD.org
Precedence: bulk

>In message <6896.827603491@time.cdrom.com> you write:
>>It appears that Mr. Fenner is the more appropriate target of my
>>wrath..  Grrrr!
>
>My humblest apologies.  I hereby swear that I will never make a commit
>again without building an entire GENERIC kernel from scratch with my
>commit in place, no matter how well I think I know the ramifications.
>
>  Bill

Use LINT instead.  I made the mistake of relying on GENERIC when I
was tidying up the SCSI code's use of its own sized types and wound
up missing a few files.
--
Justin T. Gibbs
===========================================
  FreeBSD: Turning PCs into workstations
===========================================

From owner-freebsd-current  Sat Mar 23 13:17:49 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id NAA11700
          for current-outgoing; Sat, 23 Mar 1996 13:17:49 -0800 (PST)
Received: from time.cdrom.com (time.cdrom.com [204.216.27.226])
          by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id NAA11689
          for <current@freebsd.org>; Sat, 23 Mar 1996 13:17:44 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by time.cdrom.com (8.7.5/8.6.9) with SMTP id NAA08215 for <current@freebsd.org>; Sat, 23 Mar 1996 13:17:26 -0800 (PST)
To: current@freebsd.org
Subject: Sigh..  It's just not my day! :-)
Date: Sat, 23 Mar 1996 13:17:26 -0800
Message-ID: <8213.827615846@time.cdrom.com>
From: "Jordan K. Hubbard" <jkh@time.cdrom.com>
Sender: owner-current@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

cc -c -O -W -Wreturn-type -Wcomment -Wredundant-decls -Wimplicit  -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes  -Winline  -nostdinc -I. -I../.. -I../../sys -I../../../include -DI386_CPU -DI486_CPU -DI586_CPU -DI686_CPU -DATAPI -DFAILSAFE -DCOMPAT_43 -DCD9660 -DMSDOSFS -DNFS -DFFS -DINET -DKERNEL  ../../kern/subr_prf.c
../../kern/subr_prf.c: In function `panic':
../../kern/subr_prf.c:123: `debugger_on_panic' undeclared (first use this function)
../../kern/subr_prf.c:123: (Each undeclared identifier is reported only once
../../kern/subr_prf.c:123: for each function it appears in.)
*** Error code 1

I'll try to fix this one myself, but it really looks like testing in
-current has gone to hell here folks! :-(

					Jordan

From owner-freebsd-current  Sat Mar 23 16:00:24 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id QAA20463
          for current-outgoing; Sat, 23 Mar 1996 16:00:24 -0800 (PST)
Received: from cyb (cyb.alaska.net [204.17.139.166])
          by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id QAA20457
          for <current@freebsd.org>; Sat, 23 Mar 1996 16:00:17 -0800 (PST)
Received: by cyb (Smail3.1.29.1 #9)
	id m0u0dAu-0006etC; Sat, 23 Mar 96 14:56 AKST
Message-Id: <m0u0dAu-0006etC@cyb>
From: loodvrij@gridpoint.com (Bruce J. Keeler)
Subject: Patch to talkd
To: current@freebsd.org
Date: Sat, 23 Mar 1996 14:56:48 -0900 (AKST)
X-Mailer: ELM [version 2.4 PL24]
Content-Type: text
Sender: owner-current@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

I've a tendancy to leave myself logged in a time or two on the console,
then go and do real work on an Xterm somewhere else.  The problem with this
is that incoming talk requests go to the first matching utmp entry, usually
the console vtys, and I usually miss them.

Here is a patch to talkd which makes it send the request to the tty with
the lowest idle time.
-- 
Bruce J. Keeler                               Internet: loodvrij@gridpoint.com
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
"The thing with beating your head against a wall is that it feels so *good* 
when you stop."


*** process.c.old	Sat Oct 22 09:37:06 1994
--- process.c	Sat Mar 23 14:46:39 1996
***************
*** 190,195 ****
--- 190,196 ----
  	int status;
  	FILE *fd;
  	struct stat statb;
+ 	time_t best = 0;
  	char line[sizeof(ubuf.ut_line) + 1];
  	char ftty[sizeof(_PATH_DEV) - 1 + sizeof(line)];
  
***************
*** 204,220 ****
  		if (SCMPN(ubuf.ut_name, name) == 0) {
  			strncpy(line, ubuf.ut_line, sizeof(ubuf.ut_line));
  			line[sizeof(ubuf.ut_line)] = '\0';
! 			if (*tty == '\0') {
! 				status = PERMISSION_DENIED;
  				/* no particular tty was requested */
  				(void) strcpy(ftty + sizeof(_PATH_DEV) - 1,
  				    line);
  				if (stat(ftty, &statb) == 0) {
  					if (!(statb.st_mode & 020))
  						continue;
! 					(void) strcpy(tty, line);
! 					status = SUCCESS;
! 					break;
  				}
  			}
  			if (strcmp(line, tty) == 0) {
--- 205,225 ----
  		if (SCMPN(ubuf.ut_name, name) == 0) {
  			strncpy(line, ubuf.ut_line, sizeof(ubuf.ut_line));
  			line[sizeof(ubuf.ut_line)] = '\0';
! 			if (*tty == '\0' || best != 0) {
! 				if (best == 0)
! 					status = PERMISSION_DENIED;
  				/* no particular tty was requested */
  				(void) strcpy(ftty + sizeof(_PATH_DEV) - 1,
  				    line);
  				if (stat(ftty, &statb) == 0) {
  					if (!(statb.st_mode & 020))
  						continue;
! 					if (statb.st_atime > best) {
! 						best = statb.st_atime;
! 						(void) strcpy(tty, line);
! 						status = SUCCESS;
! 						continue;
! 					}
  				}
  			}
  			if (strcmp(line, tty) == 0) {

From owner-freebsd-current  Sat Mar 23 16:48:34 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id QAA24460
          for current-outgoing; Sat, 23 Mar 1996 16:48:34 -0800 (PST)
Received: from veda.is (root@ubiq.veda.is [193.4.230.60])
          by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id QAA24433
          for <freebsd-current@freefall.FreeBSD.org>; Sat, 23 Mar 1996 16:48:22 -0800 (PST)
Received: (from adam@localhost) by veda.is (8.7.4/8.7.3) id AAA00428; Sun, 24 Mar 1996 00:48:08 GMT
Date: Sun, 24 Mar 1996 00:48:08 GMT
From: Adam David <adam@veda.is>
Message-Id: <199603240048.AAA00428@veda.is>
To: freebsd-current@freefall.FreeBSD.org
Subject: Re: lost+found ???
References: <199603210557.AAA00978@neon.Glock.COM> <199603210804.SAA11899@genesis.atrad.adelaide.edu.au>
X-Newsreader: NN version 6.5.0 #2 (NOV)
Sender: owner-current@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

>> What do I need to do?

>Nothing, fsck creates them as it needs them.

Does it still happily create lost+found as inode #2 if ".." is missing?
Would it use inode #1 in the absence of the "." entry?

--
Adam David <adam@veda.is>

From owner-freebsd-current  Sat Mar 23 18:08:36 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id SAA13159
          for current-outgoing; Sat, 23 Mar 1996 18:08:36 -0800 (PST)
Received: from sxt2.space.lockheed.com (sxt2.space.lockheed.com [192.68.162.109])
          by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id SAA13145
          for <freebsd-current@freebsd.org>; Sat, 23 Mar 1996 18:08:33 -0800 (PST)
Received: by sxt2.space.lockheed.com (5.65/DEC-Ultrix/4.3)
	id AA21315; Sat, 23 Mar 1996 18:02:52 -0800
Date: Sat, 23 Mar 1996 18:02:51 -0800 (PST)
From: "Brian N. Handy" <handy@sxt2.space.lockheed.com>
To: freebsd-current@freebsd.org
Subject: -current SNAP woes?
Message-Id: <Pine.ULT.3.91.960323175929.20530A-100000@sxt2.space.lockheed.com>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-current@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk


So...I was one of the few to snag what appears to be a complete copy of 
2.2-960321-SNAP before it vanished into the bit bucket.

I was just wondering...does that mean what I have is actually

		"2.2-960321-UNAUTHORIZED_BOOTLEG"

or just

		"2.2-960321-DOOMED_SNAP_ATTEMPT"?

Cheers,

Brian

From owner-freebsd-current  Sat Mar 23 18:15:51 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id SAA15028
          for current-outgoing; Sat, 23 Mar 1996 18:15:51 -0800 (PST)
Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211])
          by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id SAA15017
          for <freebsd-current@freefall.freebsd.org>; Sat, 23 Mar 1996 18:15:49 -0800 (PST)
Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id TAA08681; Sat, 23 Mar 1996 19:08:37 -0700
From: Terry Lambert <terry@lambert.org>
Message-Id: <199603240208.TAA08681@phaeton.artisoft.com>
Subject: Re: lost+found ???
To: adam@veda.is (Adam David)
Date: Sat, 23 Mar 1996 19:08:36 -0700 (MST)
Cc: freebsd-current@freefall.freebsd.org
In-Reply-To: <199603240048.AAA00428@veda.is> from "Adam David" at Mar 24, 96 00:48:08 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

> >> What do I need to do?
> 
> >Nothing, fsck creates them as it needs them.
> 
> Does it still happily create lost+found as inode #2 if ".." is missing?
> Would it use inode #1 in the absence of the "." entry?

Tee hee hee.

Inode 1 is not use because historically it was used to chain the bad
blocks and some archive programs know this and refuse to back it up.

Inode #2 is the root inode.

Inode #3 is the traditional lost+found inode.

And no, fsck creates the lost+found as a normal directory, so it gets
whatever inode it gets (if you precreate it with newfs, it will get
inode 3).

Consider: you might rename lost+found.  The old fsck would still
put entries in it; the new one would make another lost+found.


					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  Sat Mar 23 18:48:30 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id SAA20148
          for current-outgoing; Sat, 23 Mar 1996 18:48:30 -0800 (PST)
Received: from veda.is (root@ubiq.veda.is [193.4.230.60])
          by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id SAA20143
          for <freebsd-current@freebsd.org>; Sat, 23 Mar 1996 18:48:23 -0800 (PST)
Received: (from adam@localhost) by veda.is (8.7.4/8.7.3) id CAA00668 for freebsd-current@freebsd.org; Sun, 24 Mar 1996 02:48:08 GMT
From: Adam David <adam@veda.is>
Message-Id: <199603240248.CAA00668@veda.is>
Subject: async mounts, etc.
To: freebsd-current@freebsd.org
Date: Sun, 24 Mar 1996 02:48:07 +0000 (GMT)
X-Mailer: ELM [version 2.4ME+ PL13 (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 using an async mount for a newsspool for a few months, but today
it seems that some limit was exceeded and it panicked on average twice an hour
with "bad dir". It did not help to let fsck exercise the disk - I mean that
repair to the filesystem claimed to be successful but there were further panics.
After mounting without the async option, the filesystem is stable again. I have
a crashdump, but I suspect it only shows that the filesystem was damaged.

This reminds me of another similar problem with an NFS mounted from localhost
with the union option, it happened a few months back. After many weeks of
regular operation, it crashed when some limit was exceeded. After this, every
attempt to mount the upper layer would cause an instant panic. There was not
enough diskspace at the time to take a crashdump, and I have not dared test
it since. I used a bunch of symbolic links in the end, instead of the lower
layer.

Oh, and that reminds me to ask: Just how broken is nullfs? Is it lying broken
because it depends on other stuff not yet settled, or is it just waiting to be
fixed?

In the preceding description, I said "exceeded some limit" because all of a
sudden with no obvious explanation (for instance due to kernel changes, etc),
a system which was working reliably and was to all intents and purposes normal,
suddenly became unstable. The NFS.union directory contained several thousand
entries at the time.

--
Adam David <adam@veda.is>

From owner-freebsd-current  Sat Mar 23 19:08:56 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id TAA20852
          for current-outgoing; Sat, 23 Mar 1996 19:08:56 -0800 (PST)
Received: from austin.polstra.com (austin.polstra.com [206.213.73.10])
          by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id TAA20818
          Sat, 23 Mar 1996 19:08:43 -0800 (PST)
Received: from austin.polstra.com (jdp@localhost) by austin.polstra.com (8.6.12/8.6.12) with ESMTP id TAA24632; Sat, 23 Mar 1996 19:08:42 -0800
Message-Id: <199603240308.TAA24632@austin.polstra.com>
To: freebsd-current@freebsd.org
Cc: freebsd-hubs@freebsd.org, jkh@freebsd.org, hackers@freebsd.org,
        dima@freebsd.org
Subject: Re: new sup server
In-reply-to: <199603222137.NAA26670@austin.polstra.com>
Date: Sat, 23 Mar 1996 19:08:42 -0800
From: John Polstra <jdp@polstra.com>
Sender: owner-current@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

I wrote:

> In several attempts spread over the past few months, I have never
> yet succeeded in getting any of the sup mirrors to give me an intact
> cvs tree.  Invariably, they delete some of my perfectly good files,
> without replacing them later on.  As an example, sup5 is currently
> (and repeatably) doing this to me:
>
> [bad stuff elided]

I'm following up my own posting to report that, thanks to a lot of
help from Nate and Dima, the problems I reported about sup5 are
now completely solved.  It works perfectly now, and I encourage
people to use it.

Let's hear it for the good guys!
--
   John Polstra                                       jdp@polstra.com
   John D. Polstra & Co., Inc.                Seattle, Washington USA
   "Self-knowledge is always bad news."                 -- John Barth

From owner-freebsd-current  Sat Mar 23 19:20:35 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id TAA21654
          for current-outgoing; Sat, 23 Mar 1996 19:20:35 -0800 (PST)
Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19])
          by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id TAA21647
          Sat, 23 Mar 1996 19:20:29 -0800 (PST)
Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.12/8.6.9) id OAA25513; Sun, 24 Mar 1996 14:13:53 +1100
Date: Sun, 24 Mar 1996 14:13:53 +1100
From: Bruce Evans <bde@zeta.org.au>
Message-Id: <199603240313.OAA25513@godzilla.zeta.org.au>
To: fenner@parc.xerox.com, jkh@time.cdrom.com
Subject: Re: Whoops! My apologies!!
Cc: current@freebsd.org, wollman@freebsd.org
Sender: owner-current@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

>My humblest apologies.  I hereby swear that I will never make a commit
>again without building an entire GENERIC kernel from scratch with my
				  LINT (or both)
>commit in place, no matter how well I think I know the ramifications.

Bruce

From owner-freebsd-current  Sat Mar 23 19:49:43 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id TAA23965
          for current-outgoing; Sat, 23 Mar 1996 19:49:43 -0800 (PST)
Received: from sierra.zyzzyva.com (root@ppp0.zyzzyva.com [198.183.2.50])
          by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id TAA23925
          Sat, 23 Mar 1996 19:49:29 -0800 (PST)
Received: from zyzzyva.com (randy@localhost [127.0.0.1]) by sierra.zyzzyva.com (8.7.4/8.6.11) with ESMTP id VAA03210; Sat, 23 Mar 1996 21:49:17 -0600 (CST)
Message-Id: <199603240349.VAA03210@sierra.zyzzyva.com>
To: freebsd-current@freebsd.org
Subject: problem with NFS mounts
Cc: freebsd-hackers@freebsd.org
X-uri: http://www.zyzzyva.com/
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Sat, 23 Mar 1996 21:49:17 -0600
From: Randy Terbush <randy@zyzzyva.com>
Sender: owner-current@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk


I have a fresh install of -stable on a machine that is mounting
a couple of directories on a NetBSD-current machine. Mounts are
as follows.

netbsd:/disks/sd2/src /usr/src
netbsd:/disks/sd2/obj /usr/obj

With one mount, there is no problem. With both mounts, I cannot do
a listing of /usr. Listing any other partition is not a problem.
Only the partition where the mounts are. 'cd' into the mounted
resource hangs. 'ls' of /usr hangs.

Ideas?






From owner-freebsd-current  Sat Mar 23 20:10:27 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id UAA25621
          for current-outgoing; Sat, 23 Mar 1996 20:10:27 -0800 (PST)
Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19])
          by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id UAA25615
          for <current@freebsd.org>; Sat, 23 Mar 1996 20:10:23 -0800 (PST)
Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.12/8.6.9) id PAA27722; Sun, 24 Mar 1996 15:07:17 +1100
Date: Sun, 24 Mar 1996 15:07:17 +1100
From: Bruce Evans <bde@zeta.org.au>
Message-Id: <199603240407.PAA27722@godzilla.zeta.org.au>
To: current@freebsd.org, jkh@time.cdrom.com
Subject: Re: This also worries me..
Sender: owner-current@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

>cc -c -O -W -Wreturn-type -Wcomment -Wredundant-decls -Wimplicit  -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes  -Winline  -nostdinc -I. -I../.. -I../../sys -I../../../include -DI386_CPU -DI486_CPU -DI586_CPU -DI686_CPU -DATAPI -DFAILSAFE -DCOMPAT_43 -DCD9660 -DMSDOSFS -DNFS -DFFS -DINET -DKERNEL  ../../netinet/in_proto.c
>../../netinet/in_proto.c:99: warning: initialization from incompatible pointer type
>...

These warnings have been printed for 3 months and their causes have been
present since prehistoric times.  -current users have apparently gotten
used to the warnings.

Bruce


From owner-freebsd-current  Sat Mar 23 21:50:16 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id VAA02950
          for current-outgoing; Sat, 23 Mar 1996 21:50:16 -0800 (PST)
Received: from time.cdrom.com (time.cdrom.com [204.216.27.226])
          by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id VAA02944
          for <freebsd-current@freebsd.org>; Sat, 23 Mar 1996 21:50:14 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by time.cdrom.com (8.7.5/8.6.9) with SMTP id VAA21271; Sat, 23 Mar 1996 21:49:50 -0800 (PST)
To: "Brian N. Handy" <handy@sxt2.space.lockheed.com>
cc: freebsd-current@freebsd.org
Subject: Re: -current SNAP woes? 
In-reply-to: Your message of "Sat, 23 Mar 1996 18:02:51 PST."
             <Pine.ULT.3.91.960323175929.20530A-100000@sxt2.space.lockheed.com> 
Date: Sat, 23 Mar 1996 21:49:50 -0800
Message-ID: <21269.827646590@time.cdrom.com>
From: "Jordan K. Hubbard" <jkh@time.cdrom.com>
Sender: owner-current@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

> 		"2.2-960321-DOOMED_SNAP_ATTEMPT"?

That's the one.

						Jordan

From owner-freebsd-current  Sat Mar 23 23:33:26 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id XAA08930
          for current-outgoing; Sat, 23 Mar 1996 23:33:26 -0800 (PST)
Received: from precipice.shockwave.com (precipice.shockwave.com [171.69.108.33])
          by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id XAA08923
          Sat, 23 Mar 1996 23:33:23 -0800 (PST)
Received: from localhost.shockwave.com (localhost.shockwave.com [127.0.0.1]) by precipice.shockwave.com (8.7.4/8.7.3) with SMTP id XAA07511; Sat, 23 Mar 1996 23:33:12 -0800 (PST)
Message-Id: <199603240733.XAA07511@precipice.shockwave.com>
To: petzi@zit.th-darmstadt.de (Michael Beckmann)
cc: John Polstra <jdp@polstra.com>, freebsd-hubs@freebsd.org, jkh@freebsd.org,
        hackers@freebsd.org, current@freebsd.org
Subject: Re: new sup server 
In-reply-to: Your message of "Sat, 23 Mar 1996 12:13:29 +0100."
             <v02140b00ad7982a00ce0@[130.83.63.13]> 
Date: Sat, 23 Mar 1996 23:33:09 -0800
From: Paul Traina <pst@shockwave.com>
Sender: owner-current@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk


  From: petzi@zit.th-darmstadt.de (Michael Beckmann)
  Subject: Re: new sup server
  
  I must agree with that. I tried to run a sup mirror in Germany, but have
  never been able to make world or build a kernel with the sources from that
  mirror. There has always been corruption of the source tree.

I'm surprised.  Are you talking -current, -stable, or -cvs?

I build -current trees by suping off of sup2 (i.e. I'm my own customer)
every few days and have never had a sup-related corruption.
  
  Due to the highly loaded intercontinental lines, the sup updates from
  Freefall can take several hours, and in rare cases, (in particular if
  freefall doesn't let me in due to its ten user limit) they aren't finished
  until next night. It appears that the situation has improved somewhat with
  the new Internet connection of Freefall, though, which doesn't route
  through MCI/BBNPlanet any more.
  
  I would really like to provide some service for up-to-date FreeBSD sources
  in Europe, but sup simply doesn't work right under these conditions. I
  wouldn't mind the updates taking several hours, but I do mind getting
  garbled sources. They cost me a lot of time already.

Sounds like a big call to fix CTM.