From owner-freebsd-current Sun Jan 24 00:08:32 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id AAA29095
for freebsd-current-outgoing; Sun, 24 Jan 1999 00:08:32 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from labinfo.iet.unipi.it (labinfo.iet.unipi.it [131.114.9.5])
by hub.freebsd.org (8.8.8/8.8.8) with SMTP id AAA29090
for <current@FreeBSD.ORG>; Sun, 24 Jan 1999 00:08:26 -0800 (PST)
(envelope-from luigi@labinfo.iet.unipi.it)
Received: from localhost (luigi@localhost) by labinfo.iet.unipi.it (8.6.5/8.6.5) id GAA23221; Sun, 24 Jan 1999 06:56:30 +0100
From: Luigi Rizzo <luigi@labinfo.iet.unipi.it>
Message-Id: <199901240556.GAA23221@labinfo.iet.unipi.it>
Subject: Re: dummynet causes crash?
To: bright@hotjobs.com (Alfred Perlstein)
Date: Sun, 24 Jan 1999 06:56:30 +0100 (MET)
Cc: current@FreeBSD.ORG
In-Reply-To: <Pine.BSF.4.05.9901240248020.55154-100000@bright.fx.genx.net> from "Alfred Perlstein" at Jan 24, 99 02:57:46 am
X-Mailer: ELM [version 2.4 PL23]
Content-Type: text
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
which version of ip_dummynet are you using. There were lately a few
changes to fix a problem related to route entries being freed in the
wrong way.
> .(02:36:11)(root@bright.reserved)
> ipfw add pipe 1 ip from server to cvsup.freebsd.org
> (long pause i assume DNS)
> 00000 pipe 1 ip from 192.168.2.20 to 198.104.92.71
...
>
> Fatal trap 12: page fault while in kernel mode
> fault virtual address = 0xdeadc116
interestingly enough, the above address is "0xdeadbeef + 551 (decimal)".
It looks like somehow a wrong route entry was passed to ether_output().
> the only thing i can think of is that dummynet doesn't like not being told
> if a pipe is 'in' or 'out' :/
nope -- it can detect this by itself. the problem must be elsewhere.
if you have more input on the dummynet version (as per the CVS log)
and os version please let me know.
> my ether card is a: ed card, a 'realteck 8029'
... and the network card does not make a difference, dummynet works at
a layer above.
cheers
luigi
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Sun Jan 24 00:18:12 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id AAA29950
for freebsd-current-outgoing; Sun, 24 Jan 1999 00:18:12 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from gratis.grondar.za (gratis.grondar.za [196.7.18.65])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA29934
for <current@FreeBSD.ORG>; Sun, 24 Jan 1999 00:18:04 -0800 (PST)
(envelope-from mark@grondar.za)
Received: from greenpeace.grondar.za (greenpeace.grondar.za [196.7.18.132])
by gratis.grondar.za (8.9.2/8.9.1) with ESMTP id KAA59455;
Sun, 24 Jan 1999 10:17:48 +0200 (SAST)
(envelope-from mark@grondar.za)
Received: from grondar.za (localhost [127.0.0.1])
by greenpeace.grondar.za (8.9.2/8.9.2) with ESMTP id KAA02681;
Sun, 24 Jan 1999 10:17:47 +0200 (SAST)
(envelope-from mark@grondar.za)
Message-Id: <199901240817.KAA02681@greenpeace.grondar.za>
To: Randy Bush <randy@psg.com>
cc: John Polstra <jdp@polstra.com>, current@FreeBSD.ORG
Subject: Re: make aout-to-elf-build failure
In-Reply-To: Your message of " Sat, 23 Jan 1999 12:53:39 PST." <m104A3n-0008G4C@rip.psg.com>
References: <m1047WH-0008G4C@rip.psg.com> <199901231907.LAA16027@vashon.polstra.com> <m104A3n-0008G4C@rip.psg.com>
Date: Sun, 24 Jan 1999 10:17:46 +0200
From: Mark Murray <mark@grondar.za>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
Randy Bush wrote:
> an hour further on
>
> /usr/obj/aout/usr/src/tmp/usr/libexec/elf/ld: warning: libcrypt.so.2, needed
by /usr/obj/elf/usr/src/kerberosIV/libexec/kauthd/../../lib/libkrb/libkrb.so, n
ot found (try using --rpath)
> /usr/obj/elf/usr/src/kerberosIV/libexec/kauthd/../../lib/libkrb/libkrb.so: un
defined reference to `crypt'
> *** Error code 1
Fixed. Please resup.
M
--
Mark Murray
Join the anti-SPAM movement: http://www.cauce.org
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Sun Jan 24 00:23:26 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id AAA00561
for freebsd-current-outgoing; Sun, 24 Jan 1999 00:23:26 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from gratis.grondar.za (gratis.grondar.za [196.7.18.65])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA00556;
Sun, 24 Jan 1999 00:23:16 -0800 (PST)
(envelope-from mark@grondar.za)
Received: from greenpeace.grondar.za (greenpeace.grondar.za [196.7.18.132])
by gratis.grondar.za (8.9.2/8.9.1) with ESMTP id KAA62097;
Sun, 24 Jan 1999 10:22:57 +0200 (SAST)
(envelope-from mark@grondar.za)
Received: from grondar.za (localhost [127.0.0.1])
by greenpeace.grondar.za (8.9.2/8.9.2) with ESMTP id KAA02825;
Sun, 24 Jan 1999 10:22:53 +0200 (SAST)
(envelope-from mark@grondar.za)
Message-Id: <199901240822.KAA02825@greenpeace.grondar.za>
To: Dag-Erling Smorgrav <des@flood.ping.uio.no>
cc: Kazutaka YOKOTA <yokota@zodiac.mech.utsunomiya-u.ac.jp>,
peter@netplex.com.au, sos@FreeBSD.ORG, current@FreeBSD.ORG
Subject: Re: Death to LKM screen savers? (was: Re: HEADS UP: i386 a.out LKM support now an option..)
In-Reply-To: Your message of " 24 Jan 1999 05:06:35 +0100." <xzpyamtnwl0.fsf@flood.ping.uio.no>
References: <199901171925.DAA06456@spinner.netplex.com.au> <199901240255.LAA24094@zodiac.mech.utsunomiya-u.ac.jp> <xzpzp79ny37.fsf@flood.ping.uio.no> <xzpyamtnwl0.fsf@flood.ping.uio.no>
Date: Sun, 24 Jan 1999 10:22:52 +0200
From: Mark Murray <mark@grondar.za>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
Dag-Erling Smorgrav wrote:
> Doh, they were already axed by sos in late December. 'cvs co src/lkm'
> still creates directories for them though. I'm sure someone with more
> CVS experience than me will be able to explain why :)
Because you left off the "-P" "Prune empty directories" flag.
M
--
Mark Murray
Join the anti-SPAM movement: http://www.cauce.org
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Sun Jan 24 00:47:06 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id AAA02364
for freebsd-current-outgoing; Sun, 24 Jan 1999 00:47:06 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from cheddar.netmonger.net (cheddar.netmonger.net [209.54.21.140])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA02359
for <current@freebsd.org>; Sun, 24 Jan 1999 00:47:05 -0800 (PST)
(envelope-from chris@cheddar.netmonger.net)
Received: (from chris@localhost)
by cheddar.netmonger.net (8.8.8/8.8.8) id DAA16032;
Sun, 24 Jan 1999 03:46:53 -0500 (EST)
Message-ID: <19990124034653.A15039@netmonger.net>
Date: Sun, 24 Jan 1999 03:46:53 -0500
From: Christopher Masto <chris@netmonger.net>
To: current@FreeBSD.ORG
Subject: Running 4.0, a few weirdies
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.91.1i
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
I just finished a make world and kernel build from sourced cvsuped at
around Jan 23, 21:00 EST. There were no build problems, and I saw the
crypt backout was in, so I installed it. System seems to be working
so far, but with the following suprises:
The old "unable to mount /, specified device does not match root
device" on booting. My /etc/fstab had (working with -current from
just a few weeks ago):
/dev/wd0s1a / ufs rw 1 1
I thought this was the new world order.. apparently not. I had to change
it back to:
/dev/wd0a / ufs rw 1 1
Mucking with the kernel config file's "root on xxx" didn't seem to
make any difference.
I didn't see anything about this change in /usr/src/UPDATING, and I
must have missed its mention on this list.
After fixing that, I ran into problems with libcrypt. Specifically,
everything seems to be linked against libcrypt.so.3
<insert pause as I get distracted, go to look at something with
Netscape, and experience lockup, assuming kernel panic.. back to
the old kernel for now>
Ahem. As I was saying, everything (well, login, su, cvs, perl, etc.)
seems to be linked against libcrypt.so.3, but there was no such
version installed.
I have in /usr/obj/..blah../tmp/usr/lib:
lrwxr-xr-x 1 root wheel 13 Jan 22 19:58 libcrypt.a@ -> libexpcrypt.a
lrwxr-xr-x 1 root wheel 14 Jan 22 19:58 libcrypt.so@ -> libexpcrypt.so
lrwxr-xr-x 1 root wheel 16 Jan 22 19:58 libcrypt.so.2@ -> libexpcrypt.so.3
lrwxr-xr-x 1 root wheel 16 Jan 22 19:58 libcrypt.so.3@ -> libexpcrypt.so.3
But in /usr/lib:
lrwxrwxrwx 1 root wheel 12 Oct 5 08:39 /usr/lib/libcrypt.so@ -> libscrypt.so
lrwxrwxrwx 1 root wheel 14 Oct 5 08:39 /usr/lib/libcrypt.so.2@ -> libscrypt.so.2
Which would seem to explain how it happened, but obviously
installworld doesn't put these into /usr/lib.. all the other libraries
have current timestamps.
Speaking of timestamps.. when I booted the new kernel, my clock came
up wrong. Really confused me when I reconfigured the kernel and make
said it was up to date. Somehow it had gone back about 20 hours. I
ntpdated it back to normal, but next time I rebooted, it had gone
ahead a couple of hours. I've now booted my week-old kernel, and
the time was not altered.
That's all that I noticed. I will try another update to get Matt's vm
fix.. if it still panics, I'll get a proper backtrace. And yes, I'm
using INVARIANTS.
--
Christopher Masto Director of Operations NetMonger Communications
chris@netmonger.net info@netmonger.net http://www.netmonger.net
"Good tools allow users to do stupid things." -- Clay Shirky
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Sun Jan 24 01:20:23 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id BAA04899
for freebsd-current-outgoing; Sun, 24 Jan 1999 01:20:23 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from gratis.grondar.za (gratis.grondar.za [196.7.18.65])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA04893
for <current@FreeBSD.ORG>; Sun, 24 Jan 1999 01:20:19 -0800 (PST)
(envelope-from mark@grondar.za)
Received: from greenpeace.grondar.za (greenpeace.grondar.za [196.7.18.132])
by gratis.grondar.za (8.9.2/8.9.1) with ESMTP id LAA95895;
Sun, 24 Jan 1999 11:20:03 +0200 (SAST)
(envelope-from mark@grondar.za)
Received: from grondar.za (localhost [127.0.0.1])
by greenpeace.grondar.za (8.9.2/8.9.2) with ESMTP id LAA03089;
Sun, 24 Jan 1999 11:20:01 +0200 (SAST)
(envelope-from mark@grondar.za)
Message-Id: <199901240920.LAA03089@greenpeace.grondar.za>
To: Christopher Masto <chris@netmonger.net>
cc: current@FreeBSD.ORG
Subject: Re: Running 4.0, a few weirdies
In-Reply-To: Your message of " Sun, 24 Jan 1999 03:46:53 EST." <19990124034653.A15039@netmonger.net>
References: <19990124034653.A15039@netmonger.net>
Date: Sun, 24 Jan 1999 11:20:00 +0200
From: Mark Murray <mark@grondar.za>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
Christopher Masto wrote:
> After fixing that, I ran into problems with libcrypt. Specifically,
> everything seems to be linked against libcrypt.so.3
This has been fixed. Please resup.
M
--
Mark Murray
Join the anti-SPAM movement: http://www.cauce.org
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Sun Jan 24 01:26:17 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id BAA05342
for freebsd-current-outgoing; Sun, 24 Jan 1999 01:26:17 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from Wit401305.student.utwente.nl (wit401305.student.utwente.nl [130.89.236.145])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA05332
for <freebsd-current@FreeBSD.ORG>; Sun, 24 Jan 1999 01:26:15 -0800 (PST)
(envelope-from daeron@Wit401305.student.utwente.nl)
Received: from localhost (daeron@localhost)
by Wit401305.student.utwente.nl (8.9.2/8.9.2) with ESMTP id KAA00410;
Sun, 24 Jan 1999 10:25:59 +0100 (CET)
(envelope-from daeron@Wit401305.student.utwente.nl)
Date: Sun, 24 Jan 1999 10:25:59 +0100 (CET)
From: Pascal Hofstee <daeron@Wit401305.student.utwente.nl>
To: "Daniel C. Sobral" <dcs@newsguy.com>
cc: freebsd-current@FreeBSD.ORG
Subject: Re: Bootstrap loader problems on CURRENT
In-Reply-To: <36AAA3F8.14D589D8@newsguy.com>
Message-ID: <Pine.BSF.4.05.9901241021160.400-100000@Wit401305.student.utwente.nl>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
On Sun, 24 Jan 1999, Daniel C. Sobral wrote:
> Pascal Hofstee wrote:
> This is most likely my fault. The only place where ficlExecFD gets
> executed is during initialization, when loading /boot/boot.4th. What
> do you have there? I suppose you have no trouble booting if you
> rename that file, correct?
Removing *.4th from /boot indeed solves the problem.
To test it .. I simply used the .4th-files in
/usr/share/examples/bootforth/
--------------------
Pascal Hofstee - daeron@shadowmere.student.utwente.nl
-----BEGIN GEEK CODE BLOCK-----
Version: 3.1
GCS d- s+: a-- C++ UB++++ P+ L- E--- W- N+ o? K- w--- O? M V? PS+ PE Y-- PGP--
t+ 5 X-- R tv+ b+ DI D- G e* h+ r- y+
------END GEEK CODE BLOCK------
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Sun Jan 24 01:33:29 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id BAA06050
for freebsd-current-outgoing; Sun, 24 Jan 1999 01:33:29 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from relay.nuxi.com (nuxi.cs.ucdavis.edu [128.120.56.38])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA06045
for <current@FreeBSD.ORG>; Sun, 24 Jan 1999 01:33:26 -0800 (PST)
(envelope-from obrien@NUXI.com)
Received: (from obrien@localhost)
by relay.nuxi.com (8.9.1/8.9.1) id BAA43922;
Sun, 24 Jan 1999 01:33:06 -0800 (PST)
(envelope-from obrien)
Date: Sun, 24 Jan 1999 01:33:06 -0800
From: "David O'Brien" <obrien@NUXI.com>
To: des@flood.ping.uio.no
Cc: current@FreeBSD.ORG
Subject: Re: Death to LKM screen savers? (was: Re: HEADS UP: i386 a.out LKM support now an option..)
Message-ID: <19990124013306.A43896@relay.nuxi.com>
Reply-To: obrien@NUXI.com
References: <199901171925.DAA06456@spinner.netplex.com.au> <199901240255.LAA24094@zodiac.mech.utsunomiya-u.ac.jp> <xzpzp79ny37.fsf@flood.ping.uio.no> <xzpyamtnwl0.fsf@flood.ping.uio.no> <199901240500.VAA16698@vashon.polstra.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.95i
In-Reply-To: <199901240500.VAA16698@vashon.polstra.com>; from John Polstra on Sat, Jan 23, 1999 at 09:00:58PM -0800
X-Operating-System: FreeBSD 3.0-CURRENT
Organization: The NUXI BSD group
X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A
X-Pgp-Keyid: 34F9F9D5
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
On Sat, Jan 23, 1999 at 09:00:58PM -0800, John Polstra wrote:
>
> Always use "-P" when you check out sources: "cvs co -P src/lkm".
> And when you update sources already checked out, use "cvs upd -Pd".
Or use a ~/.cvsrc file. Mine is:
diff -u
update -Pd
checkout -P
--
-- David (obrien@NUXI.com -or- obrien@FreeBSD.org)
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Sun Jan 24 01:47:44 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id BAA07359
for freebsd-current-outgoing; Sun, 24 Jan 1999 01:47:44 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from cheddar.netmonger.net (cheddar.netmonger.net [209.54.21.140])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA07354
for <current@FreeBSD.ORG>; Sun, 24 Jan 1999 01:47:43 -0800 (PST)
(envelope-from chris@cheddar.netmonger.net)
Received: (from chris@localhost)
by cheddar.netmonger.net (8.8.8/8.8.8) id EAA19920;
Sun, 24 Jan 1999 04:47:31 -0500 (EST)
Message-ID: <19990124044731.A19710@netmonger.net>
Date: Sun, 24 Jan 1999 04:47:31 -0500
From: Christopher Masto <chris@netmonger.net>
To: current@FreeBSD.ORG
Subject: Re: Running 4.0, a few weirdies
References: <19990124034653.A15039@netmonger.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.91.1i
In-Reply-To: <19990124034653.A15039@netmonger.net>; from Christopher Masto on Sun, Jan 24, 1999 at 03:46:53AM -0500
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
On Sun, Jan 24, 1999 at 03:46:53AM -0500, Christopher Masto wrote:
> That's all that I noticed. I will try another update to get Matt's vm
> fix.. if it still panics, I'll get a proper backtrace. And yes, I'm
> using INVARIANTS.
Well, I resupped and rebuilt, and did the thing that crashed it
before, and it didn't crash this time. Not a very interesting
machine, but everything seems to work. (I just need to remember to
put the AWE32 pnp stuff in /kernel.config or wherever it belongs.)
Copyright (c) 1992-1999 FreeBSD Inc.
Copyright (c) 1982, 1986, 1989, 1991, 1993
The Regents of the University of California. All rights reserved.
FreeBSD 4.0-CURRENT #1: Sun Jan 24 02:49:52 EST 1999
root@lion-around.at.yiff.net:/usr/local/usr-src/sys/compile/LION-AROUND
Timecounter "i8254" frequency 1193182 Hz
CPU: Pentium/P54C (166.19-MHz 586-class CPU)
Origin = "GenuineIntel" Id = 0x52c Stepping=12
Features=0x1bf<FPU,VME,DE,PSE,TSC,MSR,MCE,CX8>
real memory = 100663296 (98304K bytes)
config> quit
avail memory = 94875648 (92652K bytes)
Preloaded elf kernel "kernel" at 0xf02d9000.
Probing for devices on PCI bus 0:
chip0: <Intel 82439> rev 0x03 on pci0.0.0
chip1: <Intel 82371SB PCI to ISA bridge> rev 0x01 on pci0.7.0
ide_pci0: <Intel PIIX3 Bus-master IDE controller> rev 0x00 on pci0.7.1
vga0: <S3 ViRGE VX graphics accelerator> rev 0x02 int a irq 11 on pci0.12.0
Probing for PnP devices:
CSN 1 Vendor ID: CTL00c1 [0xc1008c0e] Serial 0x0dc2a4bc Comp ID: PNPb02f [0x2fb0d041]
Probing for devices on the ISA bus:
sc0 on isa
sc0: VGA color <16 virtual consoles, flags=0x0>
atkbdc0 at 0x60-0x6f on motherboard
atkbd0 irq 1 on isa
psm0 irq 12 on isa
psm0: model NetScroll Mouse, device ID 0
sio0 at 0x3f8-0x3ff irq 4 flags 0x10 on isa
sio0: type 16550A
sio1 at 0x2f8-0x2ff irq 3 on isa
sio1: type 16550A
ppc0 at 0x378 irq 7 on isa
ppc0: W83877F chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode
ppc0: FIFO with 16/16/16 bytes threshold
nlpt0: <generic printer> on ppbus 0
nlpt0: Interrupt-driven port
ppi0: <generic parallel i/o> on ppbus 0
plip0: <PLIP network interface> on ppbus 0
fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa
fdc0: FIFO enabled, 8 bytes threshold
fd0: 1.44MB 3.5in
wdc0 at 0x1f0-0x1f7 irq 14 flags 0xa0ffa0ff on isa
wdc0: unit 0 (wd0): <WDC AC32500H>, DMA, 32-bit, multi-block-16
wd0: 2441MB (4999680 sectors), 4960 cyls, 16 heads, 63 S/T, 512 B/S
wdc0: unit 1 (atapi): <CD-ROM CDU311/3.0i>, removable, accel, dma, iordis
acd0: drive speed 1378KB/sec, 128KB cache
acd0: supported read types: CD-DA
acd0: Audio: play, 256 volume levels
acd0: Mechanism: ejectable tray
acd0: Medium: no/blank disc inside, unlocked
wdc1 at 0x170-0x177 irq 15 flags 0xa0ffa0ff on isa
wdc1: unit 0 (wd2): <Maxtor 91008D7>, DMA, 32-bit, multi-block-16
wd2: 9617MB (19696320 sectors), 19540 cyls, 16 heads, 63 S/T, 512 B/S
1 3C5x9 board(s) on ISA found at 0x300
ep0 at 0x300-0x30f irq 10 on isa
ep0: utp[*UTP*] address 00:60:97:a3:63:e6
vga0 at 0x3b0-0x3df maddr 0xa0000 msize 131072 on isa
npx0 on motherboard
npx0: INT 16 interface
apm0 not found
sb0 at 0x220 irq 5 drq 1 on isa
snd0: <SoundBlaster 16 4.16>
sbxvi0 at drq 5 on isa
snd0: <SoundBlaster 16 4.16>
sbmidi0 at 0x330 on isa
snd0: <SoundBlaster MPU-401>
awe0 at 0x620 on isa
AWE32: not detected
Intel Pentium detected, installing workaround for F00F bug
IP packet filtering initialized, divert enabled, rule-based forwarding enabled, logging limited to 100 packets/entry
IP Filter: initialized. Default = pass all, Logging = enabled
ffs_mountfs: superblock updated for soft updates
ffs_mountfs: superblock updated for soft updates
ffs_mountfs: superblock updated for soft updates
ffs_mountfs: superblock updated for soft updates
ffs_mountfs: superblock updated for soft updates
--
Christopher Masto Director of Operations NetMonger Communications
chris@netmonger.net info@netmonger.net http://www.netmonger.net
"Good tools allow users to do stupid things." -- Clay Shirky
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Sun Jan 24 02:37:38 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id CAA11925
for freebsd-current-outgoing; Sun, 24 Jan 1999 02:37:38 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from adelphi.physics.adelaide.edu.au (adelphi.physics.adelaide.edu.au [129.127.36.247])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA11919
for <current@freebsd.org>; Sun, 24 Jan 1999 02:37:33 -0800 (PST)
(envelope-from kkennawa@physics.adelaide.edu.au)
Received: from bragg (bragg [129.127.36.34])
by adelphi.physics.adelaide.edu.au (8.8.8/8.8.8/UofA-1.5) with SMTP id VAA22312;
Sun, 24 Jan 1999 21:07:18 +1030 (CST)
Received: from localhost by bragg; (5.65/1.1.8.2/05Aug95-0227PM)
id AA04610; Sun, 24 Jan 1999 21:07:18 +1030
Date: Sun, 24 Jan 1999 21:07:18 +1030 (CST)
From: Kris Kennaway <kkennawa@physics.adelaide.edu.au>
X-Sender: kkennawa@bragg
To: Christopher Masto <chris@netmonger.net>
Cc: current@FreeBSD.ORG
Subject: Re: Running 4.0, a few weirdies
In-Reply-To: <19990124034653.A15039@netmonger.net>
Message-Id: <Pine.OSF.4.05.9901242103460.31801-100000@bragg>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
On Sun, 24 Jan 1999, Christopher Masto wrote:
> The old "unable to mount /, specified device does not match root
> device" on booting. My /etc/fstab had (working with -current from
> just a few weeks ago):
>
> /dev/wd0s1a / ufs rw 1 1
>
> I thought this was the new world order.. apparently not. I had to change
> it back to:
>
> /dev/wd0a / ufs rw 1 1
Just another datapoint: I just bumped into this too upon tipping over to 4.0.
Kris
-----
(ASP) Microsoft Corporation (MSFT) announced today that the release of its
productivity suite, Office 2000, will be delayed until the first quarter
of 1901.
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Sun Jan 24 03:04:44 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id DAA14815
for freebsd-current-outgoing; Sun, 24 Jan 1999 03:04:44 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from rip.psg.com (rip.psg.com [147.28.0.39])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA14773
for <freebsd-current@FreeBSD.ORG>; Sun, 24 Jan 1999 03:04:37 -0800 (PST)
(envelope-from randy@psg.com)
Received: from localhost (1024 bytes) by rip.psg.com
via sendmail with P:stdio/R:inet_resolve/T:smtp
(sender: <randy>) (ident <randy> using unix)
id <m104NL6-0008G4C@rip.psg.com>
for <freebsd-current@FreeBSD.ORG>; Sun, 24 Jan 1999 03:04:24 -0800 (PST)
(Smail-3.2.0.101 1997-Dec-17 #1 built 1998-Oct-13)
Message-Id: <m104NL6-0008G4C@rip.psg.com>
Date: Sun, 24 Jan 1999 03:04:24 -0800 (PST)
From: Randy Bush <randy@psg.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
To: Mark Murray <mark@grondar.za>
Cc: freebsd-current@FreeBSD.ORG
Subject: Re: make aout-to-elf-build failure
References: <m1047WH-0008G4C@rip.psg.com>
<199901231907.LAA16027@vashon.polstra.com>
<m104A3n-0008G4C@rip.psg.com>
<199901240817.KAA02681@greenpeace.grondar.za>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
>> /usr/obj/aout/usr/src/tmp/usr/libexec/elf/ld: warning: libcrypt.so.2, needed by /usr/obj/elf/usr/src/kerberosIV/libexec/kauthd/../../lib/libkrb/libkrb.so, not found (try using --rpath)
>> /usr/obj/elf/usr/src/kerberosIV/libexec/kauthd/../../lib/libkrb/libkrb.so: undefined reference to `crypt'
>> *** Error code 1
> Fixed. Please resup.
Edit src/kerberosIV/libexec/kauthd/Makefile
Add delta 1.1 97.09.24.20.37.13 markm
Add delta 1.2 99.01.24.08.12.56 markm
Edit src/lib/libcrypt/Makefile
Add delta 1.17 99.01.24.07.48.30 markm
grazie!
randy
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Sun Jan 24 03:19:45 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id DAA17234
for freebsd-current-outgoing; Sun, 24 Jan 1999 03:19:45 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from gratis.grondar.za (gratis.grondar.za [196.7.18.65])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA17223
for <freebsd-current@FreeBSD.ORG>; Sun, 24 Jan 1999 03:19:36 -0800 (PST)
(envelope-from mark@grondar.za)
Received: from greenpeace.grondar.za (greenpeace.grondar.za [196.7.18.132])
by gratis.grondar.za (8.9.2/8.9.1) with ESMTP id NAA97143;
Sun, 24 Jan 1999 13:19:19 +0200 (SAST)
(envelope-from mark@grondar.za)
Received: from grondar.za (localhost [127.0.0.1])
by greenpeace.grondar.za (8.9.2/8.9.2) with ESMTP id NAA03526;
Sun, 24 Jan 1999 13:19:18 +0200 (SAST)
(envelope-from mark@grondar.za)
Message-Id: <199901241119.NAA03526@greenpeace.grondar.za>
To: Randy Bush <randy@psg.com>
cc: freebsd-current@FreeBSD.ORG
Subject: Re: make aout-to-elf-build failure
In-Reply-To: Your message of " Sun, 24 Jan 1999 03:04:24 PST." <m104NL6-0008G4C@rip.psg.com>
References: <m1047WH-0008G4C@rip.psg.com> <199901231907.LAA16027@vashon.polstra.com> <m104A3n-0008G4C@rip.psg.com> <199901240817.KAA02681@greenpeace.grondar.za> <m104NL6-0008G4C@rip.psg.com>
Date: Sun, 24 Jan 1999 13:19:17 +0200
From: Mark Murray <mark@grondar.za>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
Randy Bush wrote:
> grazie!
Prego!
M
--
Mark Murray
Join the anti-SPAM movement: http://www.cauce.org
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Sun Jan 24 03:29:09 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id DAA19164
for freebsd-current-outgoing; Sun, 24 Jan 1999 03:29:09 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from adelphi.physics.adelaide.edu.au (adelphi.physics.adelaide.edu.au [129.127.36.247])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA19118
for <current@freebsd.org>; Sun, 24 Jan 1999 03:29:04 -0800 (PST)
(envelope-from kkennawa@physics.adelaide.edu.au)
Received: from bragg (bragg [129.127.36.34])
by adelphi.physics.adelaide.edu.au (8.8.8/8.8.8/UofA-1.5) with SMTP id VAA23515
for <current@freebsd.org>; Sun, 24 Jan 1999 21:58:45 +1030 (CST)
Received: from localhost by bragg; (5.65/1.1.8.2/05Aug95-0227PM)
id AA12922; Sun, 24 Jan 1999 21:58:45 +1030
Date: Sun, 24 Jan 1999 21:58:45 +1030 (CST)
From: Kris Kennaway <kkennawa@physics.adelaide.edu.au>
X-Sender: kkennawa@bragg
To: current@FreeBSD.ORG
Subject: spec_getpages error
Message-Id: <Pine.OSF.4.05.9901242157100.8830-100000@bragg>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
4.0-CURRENT as of earlier this evening (before the most recent set of commits
by Matt):
spec_getpages: I/O read failure: (error code=0)
size: 4096, resid: 4096, a_count: 3156, valid: 0x0
nread: 0, reqpage: 0, pindex: 0, pcount: 1
vm_fault: pager read error, pid 1237 (cvsup)
Jan 24 21:49:23 morden /kernel.test: pid 1237 (cvsup), uid 0: exited on signal
6 (core dumped)
Kris
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Sun Jan 24 03:42:49 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id DAA21167
for freebsd-current-outgoing; Sun, 24 Jan 1999 03:42:49 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from adelphi.physics.adelaide.edu.au (adelphi.physics.adelaide.edu.au [129.127.36.247])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA21146
for <current@freebsd.org>; Sun, 24 Jan 1999 03:42:30 -0800 (PST)
(envelope-from kkennawa@physics.adelaide.edu.au)
Received: from bragg (bragg [129.127.36.34])
by adelphi.physics.adelaide.edu.au (8.8.8/8.8.8/UofA-1.5) with SMTP id WAA23179
for <current@freebsd.org>; Sun, 24 Jan 1999 22:12:13 +1030 (CST)
Received: from localhost by bragg; (5.65/1.1.8.2/05Aug95-0227PM)
id AA12122; Sun, 24 Jan 1999 22:12:13 +1030
Date: Sun, 24 Jan 1999 22:12:12 +1030 (CST)
From: Kris Kennaway <kkennawa@physics.adelaide.edu.au>
X-Sender: kkennawa@bragg
To: current@FreeBSD.ORG
Subject: Re: spec_getpages error
In-Reply-To: <Pine.OSF.4.05.9901242157100.8830-100000@bragg>
Message-Id: <Pine.OSF.4.05.9901242211110.8830-100000@bragg>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
On Sun, 24 Jan 1999, Kris Kennaway wrote:
> 4.0-CURRENT as of earlier this evening (before the most recent set of commits
> by Matt):
>
> spec_getpages: I/O read failure: (error code=0)
> size: 4096, resid: 4096, a_count: 3156, valid: 0x0
> nread: 0, reqpage: 0, pindex: 0, pcount: 1
> vm_fault: pager read error, pid 1237 (cvsup)
> Jan 24 21:49:23 morden /kernel.test: pid 1237 (cvsup), uid 0: exited on signal
> 6 (core dumped)
I forgot to mention that this is running on a vn - it seems to be a repeatable
failure.
Kris
-----
(ASP) Microsoft Corporation (MSFT) announced today that the release of its
productivity suite, Office 2000, will be delayed until the first quarter
of 1901.
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Sun Jan 24 04:48:42 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id EAA29953
for freebsd-current-outgoing; Sun, 24 Jan 1999 04:48:42 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from mail.vr.IN-Berlin.DE (gnu.in-berlin.de [192.109.42.4])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA29945
for <freebsd-current@FreeBSD.ORG>; Sun, 24 Jan 1999 04:48:40 -0800 (PST)
(envelope-from dva.in-berlin.de!balu@hirsch.in-berlin.de)
Received: from hirsch.in-berlin.de (root@hirsch.in-berlin.de [192.109.42.6])
by mail.vr.IN-Berlin.DE (8.9.1a/8.9.1) with ESMTP id NAA12839;
Sun, 24 Jan 1999 13:48:21 +0100 (CET)
(envelope-from dva.in-berlin.de!balu@hirsch.in-berlin.de)
Received: by hirsch.in-berlin.de (Smail3.2)
id <m104Oxd-000ck0C>; Sun, 24 Jan 1999 13:48:17 +0100 (CET)
Received: (from balu@localhost)
by dva.in-berlin.de (8.9.1/8.9.1) id NAA27809;
Sun, 24 Jan 1999 13:09:12 +0100 (CET)
(envelope-from balu)
Date: Sun, 24 Jan 1999 13:09:12 +0100
From: Boris Staeblow <balu@dva.in-berlin.de>
To: dillon@apollo.backplane.com
Cc: freebsd-current@FreeBSD.ORG
Subject: Re: Heads up! New swapper and VM changes have been committed to -4.x
Message-ID: <19990124130912.A27246@dva.in-berlin.de>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.95i
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
> Make sure your /usr/src/lib/libkvm is updated. Also update
> /usr/src/include/kvm.h. Then update and recompile top, systat,
> and pstat.
What about an "kvmrebuild"-target in the main Makefile?
Beside your suggestions there are much more programs which use
libkvm:
/bin/ps/
/libexec/rpc.rstatd/
/sbin/ccdconfig/
/sbin/dmesg/
/sbin/dset/
/usr.bin/fstat/
/usr.bin/gcore/
/usr.bin/ipcs/
/usr.bin/netstat/
/usr.bin/nfsstat/
/usr.bin/systat/
/usr.bin/top/
/usr.bin/vmstat/
/usr.bin/w/
/usr.sbin/iostat/
/usr.sbin/kernbb/
/usr.sbin/kgmon/
/usr.sbin/pstat/
/usr.sbin/xntpd/xntpd/
If someone complain about problems with ps, top... you can just tell him
to try "make kvmrebuild" (or something comparable).
Boris
--
balu@dva.in-berlin.de
Boris Staeblow
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Sun Jan 24 04:52:03 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id EAA00708
for freebsd-current-outgoing; Sun, 24 Jan 1999 04:52:03 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from caladan.tdx.co.uk (caladan.tdx.co.uk [195.188.177.4])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA00701
for <freebsd-current@FreeBSD.ORG>; Sun, 24 Jan 1999 04:52:00 -0800 (PST)
(envelope-from kpielorz@tdx.co.uk)
Received: from tdx.co.uk (lorca-tx.tdx.co.uk [195.188.177.242])
by caladan.tdx.co.uk (8.9.2/8.9.2) with ESMTP id MAA51585;
Sun, 24 Jan 1999 12:51:30 GMT
Message-ID: <36AB1752.4276266F@tdx.co.uk>
Date: Sun, 24 Jan 1999 12:51:30 +0000
From: Karl Pielorz <kpielorz@tdx.co.uk>
Organization: TDX - The Digital eXchange
X-Mailer: Mozilla 4.5 [en] (WinNT; I)
X-Accept-Language: en
MIME-Version: 1.0
To: Boris Staeblow <balu@dva.in-berlin.de>
CC: dillon@apollo.backplane.com, freebsd-current@FreeBSD.ORG
Subject: Re: Heads up! New swapper and VM changes have been committed to -4.x
References: <19990124130912.A27246@dva.in-berlin.de>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
Boris Staeblow wrote:
>
> > Make sure your /usr/src/lib/libkvm is updated. Also update
> > /usr/src/include/kvm.h. Then update and recompile top, systat,
> > and pstat.
>
> What about an "kvmrebuild"-target in the main Makefile?
Would have the effect of a make build/install world actually do this? (working
on the principal if it's needed by the world it should be built with the 'make
buildworld' / installworld etc.
-Kp
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Sun Jan 24 05:25:55 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id FAA02708
for freebsd-current-outgoing; Sun, 24 Jan 1999 05:25:55 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from peach.ocn.ne.jp (peach.ocn.ne.jp [210.145.254.87])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA02703
for <freebsd-current@FreeBSD.ORG>; Sun, 24 Jan 1999 05:25:52 -0800 (PST)
(envelope-from dcs@newsguy.com)
Received: from newsguy.com by peach.ocn.ne.jp (8.9.1a/OCN) id WAA04542; Sun, 24 Jan 1999 22:25:26 +0900 (JST)
Message-ID: <36AB1EED.DC54C8A1@newsguy.com>
Date: Sun, 24 Jan 1999 22:23:57 +0900
From: "Daniel C. Sobral" <dcs@newsguy.com>
X-Mailer: Mozilla 4.5 [en] (Win98; I)
X-Accept-Language: pt-BR,ja
MIME-Version: 1.0
To: Boris Staeblow <balu@dva.in-berlin.de>
CC: dillon@apollo.backplane.com, freebsd-current@FreeBSD.ORG
Subject: Re: Heads up! New swapper and VM changes have been committed to -4.x
References: <19990124130912.A27246@dva.in-berlin.de>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
Boris Staeblow wrote:
>
> Beside your suggestions there are much more programs which use
> libkvm:
>
> /sbin/dset/
If I am not mistaken, dset got canned.
--
Daniel C. Sobral (8-DCS)
dcs@newsguy.com
If you sell your soul to the Devil and all you get is an MCSE from
it, you haven't gotten market rate.
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Sun Jan 24 05:26:46 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id FAA02758
for freebsd-current-outgoing; Sun, 24 Jan 1999 05:26:46 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from bright.fx.genx.net (bright.fx.genx.net [206.64.4.154])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA02753
for <current@FreeBSD.ORG>; Sun, 24 Jan 1999 05:26:43 -0800 (PST)
(envelope-from bright@hotjobs.com)
Received: from localhost (bright@localhost)
by bright.fx.genx.net (8.9.1/8.9.1) with ESMTP id IAA00106;
Sun, 24 Jan 1999 08:32:38 -0500 (EST)
(envelope-from bright@hotjobs.com)
X-Authentication-Warning: bright.fx.genx.net: bright owned process doing -bs
Date: Sun, 24 Jan 1999 08:32:38 -0500 (EST)
From: Alfred Perlstein <bright@hotjobs.com>
X-Sender: bright@bright.fx.genx.net
To: Luigi Rizzo <luigi@labinfo.iet.unipi.it>
cc: current@FreeBSD.ORG
Subject: Re: dummynet causes crash?
In-Reply-To: <199901240556.GAA23221@labinfo.iet.unipi.it>
Message-ID: <Pine.BSF.4.05.9901240827220.55154-100000@bright.fx.genx.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
On Sun, 24 Jan 1999, Luigi Rizzo wrote:
> which version of ip_dummynet are you using. There were lately a few
> changes to fix a problem related to route entries being freed in the
> wrong way.
* $Id: ip_dummynet.c,v 1.7 1999/01/12 16:43:52 eivind Exp $
this is what you want right?
>
> > .(02:36:11)(root@bright.reserved)
> > ipfw add pipe 1 ip from server to cvsup.freebsd.org
> > (long pause i assume DNS)
> > 00000 pipe 1 ip from 192.168.2.20 to 198.104.92.71
> ...
> >
> > Fatal trap 12: page fault while in kernel mode
> > fault virtual address = 0xdeadc116
>
> interestingly enough, the above address is "0xdeadbeef + 551 (decimal)".
> It looks like somehow a wrong route entry was passed to ether_output().
usr/src/sys/netinet % netstat -rn
Routing tables
Internet:
Destination Gateway Flags Refs Use Netif
Expire
default 192.168.2.5 UGSc 3 1 ed1
127.0.0.1 127.0.0.1 UH 1 26 lo0
192.168.2 link#1 UC 0 0 ed1
192.168.2.5 0:0:1b:3:65:f8 UHLW 4 25 ed1
632
>
> > the only thing i can think of is that dummynet doesn't like not being told
> > if a pipe is 'in' or 'out' :/
>
> nope -- it can detect this by itself. the problem must be elsewhere.
> if you have more input on the dummynet version (as per the CVS log)
> and os version please let me know.
usr/src/sys/netinet % uname -a
FreeBSD bright.reserved 4.0-CURRENT FreeBSD 4.0-CURRENT #0: Sun Jan 24
01:35:24 EST 1999 perlsta@bright.reserved:/usr/src/sys/compile/bright
i386
>
> > my ether card is a: ed card, a 'realteck 8029'
>
> ... and the network card does not make a difference, dummynet works at
> a layer above.
oh. :/
Alfred Perlstein - Programmer, HotJobs Inc. - www.hotjobs.com
-- There are operating systems, and then there's FreeBSD.
-- http://www.freebsd.org/ 4.0-current
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Sun Jan 24 05:29:55 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id FAA02925
for freebsd-current-outgoing; Sun, 24 Jan 1999 05:29:55 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from bsd1.gccs.com.au (router.gccs.com.au [203.17.152.1])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA02919
for <freebsd-current@freebsd.org>; Sun, 24 Jan 1999 05:29:50 -0800 (PST)
(envelope-from starr3@gccs.com.au)
Received: from lb50x (lb50x.gccs.com.au [203.17.152.10])
by bsd1.gccs.com.au (8.9.1/8.9.1) with SMTP id XAA34411
for <freebsd-current@freebsd.org>; Sun, 24 Jan 1999 23:29:34 +1000 (EST)
Message-ID: <03a701be479d$99a3f7d0$0a9811cb@gccs.com.au>
From: "Harry Starr" <starr3@gccs.com.au>
To: "current" <freebsd-current@FreeBSD.ORG>
Subject: Problem booting using /boot/loader
Date: Sun, 24 Jan 1999 23:29:41 +1000
MIME-Version: 1.0
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.00.0810.800
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.0810.800
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
I just cvsup'd and made world, and rebuilt a kernel. (The last rebuild was
Jan 11).
NOW, /boot/loader cannot mount my root partition.
Luckily, boot2 can still load the new kernel properly.
Here is the pertinent info:
* No IDE drives, BUT 1 ATAPI CD-ROM on second IDE channel.
Booting kernel reports no wdc0; cd-rom found on wdc1.
* SCSI controller (ncr0) with two SCSI disks at ID 2, and ID 3
* FreeBSD on ID 2; one slice only (s1), a is root, b is swap, e is usr
* ID 3 is /usr/junk
The boot/boot2 goes OK (reports 0:da(0,a)/boot/loader) and brings up the
loader OK.
The currdev is disk1s1a.
/boot/loader seems to boot the kernel OK.
/boot/boot.conf is empty.
kernel initializes and gets to the SCSI delay message, then panics:
Panic message is: "error 6: panic : cannount mount root (2)"
Can anyone shed some light on this for me ??
The previous boot/loader (Jan 11) booted this configuration fine!!
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Sun Jan 24 05:39:37 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id FAA03759
for freebsd-current-outgoing; Sun, 24 Jan 1999 05:39:37 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from adelphi.physics.adelaide.edu.au (adelphi.physics.adelaide.edu.au [129.127.36.247])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA03749
for <current@freebsd.org>; Sun, 24 Jan 1999 05:39:34 -0800 (PST)
(envelope-from kkennawa@physics.adelaide.edu.au)
Received: from bragg (bragg [129.127.36.34])
by adelphi.physics.adelaide.edu.au (8.8.8/8.8.8/UofA-1.5) with SMTP id AAA24054
for <current@freebsd.org>; Mon, 25 Jan 1999 00:09:20 +1030 (CST)
Received: from localhost by bragg; (5.65/1.1.8.2/05Aug95-0227PM)
id AA00151; Mon, 25 Jan 1999 00:09:20 +1030
Date: Mon, 25 Jan 1999 00:09:20 +1030 (CST)
From: Kris Kennaway <kkennawa@physics.adelaide.edu.au>
X-Sender: kkennawa@bragg
To: current@FreeBSD.ORG
Subject: fetch(1) headers not installed
Message-Id: <Pine.OSF.4.05.9901250006140.21168-100000@bragg>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
'make includes' does not install fetch.h and fetch_err.h, the only two header
files in /usr/include which aren't installed by that target. They are
installed by 'make install' however.
Is this intentional behaviour?
Kris
-----
(ASP) Microsoft Corporation (MSFT) announced today that the release of its
productivity suite, Office 2000, will be delayed until the first quarter
of 1901.
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Sun Jan 24 06:11:47 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id GAA07466
for freebsd-current-outgoing; Sun, 24 Jan 1999 06:11:47 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from peach.ocn.ne.jp (peach.ocn.ne.jp [210.145.254.87])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA07458
for <freebsd-current@FreeBSD.ORG>; Sun, 24 Jan 1999 06:11:44 -0800 (PST)
(envelope-from dcs@newsguy.com)
Received: from newsguy.com by peach.ocn.ne.jp (8.9.1a/OCN) id XAA10835; Sun, 24 Jan 1999 23:11:20 +0900 (JST)
Message-ID: <36AB294E.E9B094B8@newsguy.com>
Date: Sun, 24 Jan 1999 23:08:14 +0900
From: "Daniel C. Sobral" <dcs@newsguy.com>
X-Mailer: Mozilla 4.5 [en] (Win98; I)
X-Accept-Language: pt-BR,ja
MIME-Version: 1.0
To: Harry Starr <starr3@gccs.com.au>
CC: current <freebsd-current@FreeBSD.ORG>
Subject: Re: Problem booting using /boot/loader
References: <03a701be479d$99a3f7d0$0a9811cb@gccs.com.au>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
Harry Starr wrote:
>
> Can anyone shed some light on this for me ??
Can you provide the bios disk assignment shown by loader?
> The previous boot/loader (Jan 11) booted this configuration fine!!
Upon installation, the old loader is preserver as /boot/loader.old.
Can you confirm it is still working? The problem just might be with
the kernel, instead of the loader...
(Did you recompile the kernel too, btw?)
--
Daniel C. Sobral (8-DCS)
dcs@newsguy.com
If you sell your soul to the Devil and all you get is an MCSE from
it, you haven't gotten market rate.
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Sun Jan 24 06:28:27 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id GAA08797
for freebsd-current-outgoing; Sun, 24 Jan 1999 06:28:27 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from bsd1.gccs.com.au (router.gccs.com.au [203.17.152.1])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA08792
for <freebsd-current@FreeBSD.ORG>; Sun, 24 Jan 1999 06:28:24 -0800 (PST)
(envelope-from starr3@gccs.com.au)
Received: from lb50x (lb50x.gccs.com.au [203.17.152.10])
by bsd1.gccs.com.au (8.9.1/8.9.1) with SMTP id AAA34501;
Mon, 25 Jan 1999 00:28:01 +1000 (EST)
Message-ID: <049701be47a5$c455b600$0a9811cb@gccs.com.au>
From: "Harry Starr" <starr3@gccs.com.au>
To: "Daniel C. Sobral" <dcs@newsguy.com>
Cc: "current" <freebsd-current@FreeBSD.ORG>
Subject: Re: Problem booting using /boot/loader
Date: Mon, 25 Jan 1999 00:28:09 +1000
MIME-Version: 1.0
Content-Type: text/plain;
charset="Windows-1252"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.00.0810.800
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.0810.800
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
Yep!
/boot/loader.old works OK! (dated Jan 11)
/boot/loader (Jan 24) fails.
And yes, the kernel was recompiled from the same cvsup sources.
Definitely looks like something broke in the current loader.
Harry.
----- Original Message -----
From: Daniel C. Sobral <dcs@newsguy.com>
To: Harry Starr <starr3@gccs.com.au>
Cc: current <freebsd-current@FreeBSD.ORG>
Sent: Monday, January 25, 1999 12:08 AM
Subject: Re: Problem booting using /boot/loader
>Harry Starr wrote:
>>
>> Can anyone shed some light on this for me ??
>
>Can you provide the bios disk assignment shown by loader?
>
>> The previous boot/loader (Jan 11) booted this configuration fine!!
>
>Upon installation, the old loader is preserver as /boot/loader.old.
>Can you confirm it is still working? The problem just might be with
>the kernel, instead of the loader...
>
>(Did you recompile the kernel too, btw?)
>
>--
>Daniel C. Sobral (8-DCS)
>dcs@newsguy.com
>
> If you sell your soul to the Devil and all you get is an MCSE from
>it, you haven't gotten market rate.
>
>
>To Unsubscribe: send mail to majordomo@FreeBSD.org
>with "unsubscribe freebsd-current" in the body of the message
>
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Sun Jan 24 06:34:25 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id GAA09695
for freebsd-current-outgoing; Sun, 24 Jan 1999 06:34:25 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from bsd1.gccs.com.au (router.gccs.com.au [203.17.152.1])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA09684
for <freebsd-current@FreeBSD.ORG>; Sun, 24 Jan 1999 06:34:20 -0800 (PST)
(envelope-from starr3@gccs.com.au)
Received: from lb50x (lb50x.gccs.com.au [203.17.152.10])
by bsd1.gccs.com.au (8.9.1/8.9.1) with SMTP id AAA34515;
Mon, 25 Jan 1999 00:33:59 +1000 (EST)
Message-ID: <049d01be47a6$99b14f30$0a9811cb@gccs.com.au>
From: "Harry Starr" <starr3@gccs.com.au>
To: "Daniel C. Sobral" <dcs@newsguy.com>
Cc: "current" <freebsd-current@FreeBSD.ORG>
Subject: Re: Problem booting using /boot/loader
Date: Mon, 25 Jan 1999 00:34:07 +1000
MIME-Version: 1.0
Content-Type: text/plain;
charset="Windows-1252"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.00.0810.800
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.0810.800
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
Oops! Forgot the BIOS stuff.
BIOS drive A: is disk0
BIOS drive C: is disk1
BIOS drive D: is disk2
an lsdev to loader gives the expected response:
<snip>
disk1: BIOS drive C:
disk1s1a: FFS 64MB (0 - 131072)
disk1s1b: swap 128MB (131072-393216)
disk1s1e: FFS 3904MB (393216 - 8388608)
Harry.
----- Original Message -----
From: Daniel C. Sobral <dcs@newsguy.com>
To: Harry Starr <starr3@gccs.com.au>
Cc: current <freebsd-current@FreeBSD.ORG>
Sent: Monday, January 25, 1999 12:08 AM
Subject: Re: Problem booting using /boot/loader
>Harry Starr wrote:
>>
>> Can anyone shed some light on this for me ??
>
>Can you provide the bios disk assignment shown by loader?
>
>> The previous boot/loader (Jan 11) booted this configuration fine!!
>
>Upon installation, the old loader is preserver as /boot/loader.old.
>Can you confirm it is still working? The problem just might be with
>the kernel, instead of the loader...
>
>(Did you recompile the kernel too, btw?)
>
>--
>Daniel C. Sobral (8-DCS)
>dcs@newsguy.com
>
> If you sell your soul to the Devil and all you get is an MCSE from
>it, you haven't gotten market rate.
>
>
>To Unsubscribe: send mail to majordomo@FreeBSD.org
>with "unsubscribe freebsd-current" in the body of the message
>
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Sun Jan 24 06:59:26 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id GAA11191
for freebsd-current-outgoing; Sun, 24 Jan 1999 06:59:26 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from uni4nn.gn.iaf.nl (osmium.gn.iaf.nl [193.67.144.12])
by hub.freebsd.org (8.8.8/8.8.8) with SMTP id GAA11184
for <current@FreeBSD.ORG>; Sun, 24 Jan 1999 06:59:23 -0800 (PST)
(envelope-from wilko@yedi.iaf.nl)
Received: by uni4nn.gn.iaf.nl with UUCP id AA23121
(5.67b/IDA-1.5); Sun, 24 Jan 1999 15:56:47 +0100
Received: (from wilko@localhost) by yedi.iaf.nl (8.8.8/8.6.12) id PAA12682; Sun, 24 Jan 1999 15:57:05 +0100 (CET)
From: Wilko Bulte <wilko@yedi.iaf.nl>
Message-Id: <199901241457.PAA12682@yedi.iaf.nl>
Subject: Re: panic: found dirty cache page 0xf046f1c0
In-Reply-To: <199901240614.WAA60278@apollo.backplane.com> from Matthew Dillon at "Jan 23, 99 10:14:57 pm"
To: dillon@apollo.backplane.com (Matthew Dillon)
Date: Sun, 24 Jan 1999 15:57:05 +0100 (CET)
Cc: current@FreeBSD.ORG
X-Organisation: Private FreeBSD site - Arnhem, The Netherlands
X-Pgp-Info: PGP public key at 'finger wilko@freefall.freebsd.org'
X-Mailer: ELM [version 2.4ME+ PL38 (25)]
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
As Matthew Dillon wrote...
> I've committed one bug fix to the 'found dirty cache page' bug --
> turns out vm_map_split() was the culprit, renaming pages
> without removing them from PQ_CACHE. The bug was introduced
> in -3.0, and hit the KASSERT() I put in -4.x.
>
> I've committed a general inlining of 'changing the page dirty
> status to VM_PAGE_BITS_ALL' and put a sanity check in the inline.
> If this problem occurs again, you will get a different panic.
> One of:
>
> vm_page_dirty: page in cache!
> vm_page_busy: page already busy!!!
> vm_page_wakeup: page not busy!!!
>
> If your box drops into DDB, please get a backtrace and report
> it to the list or to me and we should be able to track down
> any remaining dirty-pages-in-PQ_CACHE bugs.
FYI: a buildworld of -current including the above on FreeBSD/axp completed
without any incidents.
Wilko
_ ______________________________________________________________________
| / o / / _ Bulte email: wilko@yedi.iaf.nl
|/|/ / / /( (_) Arnhem, The Netherlands WWW : http://www.tcja.nl
______________________________________________ Powered by FreeBSD __________
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Sun Jan 24 06:59:57 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id GAA11223
for freebsd-current-outgoing; Sun, 24 Jan 1999 06:59:57 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from uni4nn.gn.iaf.nl (osmium.gn.iaf.nl [193.67.144.12])
by hub.freebsd.org (8.8.8/8.8.8) with SMTP id GAA11218
for <current@FreeBSD.ORG>; Sun, 24 Jan 1999 06:59:56 -0800 (PST)
(envelope-from wilko@yedi.iaf.nl)
Received: by uni4nn.gn.iaf.nl with UUCP id AA23103
(5.67b/IDA-1.5); Sun, 24 Jan 1999 15:56:43 +0100
Received: (from wilko@localhost) by yedi.iaf.nl (8.8.8/8.6.12) id LAA10644; Sun, 24 Jan 1999 11:02:16 +0100 (CET)
From: Wilko Bulte <wilko@yedi.iaf.nl>
Message-Id: <199901241002.LAA10644@yedi.iaf.nl>
Subject: Re: 2Re: panic: found dirty cache page 0xf046f1c0
In-Reply-To: <Pine.BSF.4.05.9901232132130.55154-100000@bright.fx.genx.net> from Alfred Perlstein at "Jan 23, 99 09:45:56 pm"
To: bright@hotjobs.com (Alfred Perlstein)
Date: Sun, 24 Jan 1999 11:02:16 +0100 (CET)
Cc: dillon@apollo.backplane.com, niels@bakker.net, peter@netplex.com.au,
current@FreeBSD.ORG
X-Organisation: Private FreeBSD site - Arnhem, The Netherlands
X-Pgp-Info: PGP public key at 'finger wilko@freefall.freebsd.org'
X-Mailer: ELM [version 2.4ME+ PL38 (25)]
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
As Alfred Perlstein wrote...
> On Sat, 23 Jan 1999, Matthew Dillon wrote:
>
> i have 'ed' driver and mine blows up as well.
>
> > :Here too... pretty quickly after boot on a SMP machine (current as of Jan
> > :12) that pushes quite a bit of traffic, the following messages appear:
> > :
> > :de0: abnormal interrupt: transmit underflow (raising TX threshold to 96|256)
> > :de0: abnormal interrupt: transmit underflow (raising TX threshold to 128|512)
> > :de0: abnormal interrupt: transmit underflow (raising TX threshold to 160|1024)
I have seen these messages on both Freebsd/x86 and /axp with single CPU
machines. Almost all of them disappeared when I started using decent
UTP cabling. Believe it or not. So, I'd say the messages are not linked
to SMP at all.
> > :
> > :de0: <Digital 21140A Fast Ethernet> rev 0x22 int a irq 16 on pci0.12.0
> > :de0: 21140A [10-100Mb/s] pass 2.2
> > :de0: address 00:c0:f0:1f:5d:0d
> > :de0: enabling Full Duplex 100baseTX port>
> > Three people getting these panics, three people with DEC ethernet
> > cards. Random complaints about card during ifconfig: speaker goes click,
> > console gets junked, etc etc etc.
> >
>
> > s there anyone having this panic who does NOT have a DEC ethernet
> > card ?
Wilko
_ ______________________________________________________________________
| / o / / _ Bulte email: wilko@yedi.iaf.nl
|/|/ / / /( (_) Arnhem, The Netherlands WWW : http://www.tcja.nl
______________________________________________ Powered by FreeBSD __________
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Sun Jan 24 07:12:17 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id HAA12090
for freebsd-current-outgoing; Sun, 24 Jan 1999 07:12:17 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from ozz.etrust.ru (ozz.etrust.ru [195.2.84.116])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA12084
for <current@FreeBSD.org>; Sun, 24 Jan 1999 07:12:13 -0800 (PST)
(envelope-from osa@etrust.ru)
Received: from localhost (localhost [127.0.0.1])
by ozz.etrust.ru (8.9.2/8.9.1) with ESMTP id SAA00690
for <current@FreeBSD.org>; Sun, 24 Jan 1999 18:08:25 +0300 (MSK)
(envelope-from osa@etrust.ru)
Date: Sun, 24 Jan 1999 18:08:25 +0300 (MSK)
From: oZZ!!! <osa@etrust.ru>
To: current@FreeBSD.ORG
Subject: Re: Problem booting using /boot/loader (fwd)
Message-ID: <Pine.BSF.4.05.9901241803450.600-100000@ozz.etrust.ru>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
>Yep!
>/boot/loader.old works OK! (dated Jan 11)
>/boot/loader (Jan 24) fails.
>And yes, the kernel was recompiled from the same cvsup sources.
>Definitely looks like something broke in the current loader.
>
>Harry.
>Harry Starr wrote:
>>
>> Can anyone shed some light on this for me ??
>
>Can you provide the bios disk assignment shown by loader?
>
>> The previous boot/loader (Jan 11) booted this configuration fine!!
>
>Upon installation, the old loader is preserver as /boot/loader.old.
>Can you confirm it is still working? The problem just might be with
>the kernel, instead of the loader...
>
>(Did you recompile the kernel too, btw?)
>
>--
>Daniel C. Sobral (8-DCS)
>dcs@newsguy.com
>
> If you sell your soul to the Devil and all you get is an MCSE from
>it, you haven't gotten market rate.
>
I think i have this problem too...
Today i cvsuped my source tree (tag=.), then successfully recompiled &
installed new 4.0-CURRENT system.
/boot/loader can't work...
/boot/loader.old works 19990120 OK!
Rgdz,
Sergey A. Osokin aka oZZ,
osa@etrust.ru
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Sun Jan 24 07:19:09 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id HAA12657
for freebsd-current-outgoing; Sun, 24 Jan 1999 07:19:09 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from rip.psg.com (rip.psg.com [147.28.0.39])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA12651
for <freebsd-current@FreeBSD.ORG>; Sun, 24 Jan 1999 07:19:08 -0800 (PST)
(envelope-from randy@psg.com)
Received: from localhost (875 bytes) by rip.psg.com
via sendmail with P:stdio/R:inet_resolve/T:smtp
(sender: <randy>) (ident <randy> using unix)
id <m104RJR-0008G4C@rip.psg.com>
for <freebsd-current@FreeBSD.ORG>; Sun, 24 Jan 1999 07:18:57 -0800 (PST)
(Smail-3.2.0.101 1997-Dec-17 #1 built 1998-Oct-13)
Message-Id: <m104RJR-0008G4C@rip.psg.com>
Date: Sun, 24 Jan 1999 07:18:57 -0800 (PST)
From: Randy Bush <randy@psg.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
To: Mark Murray <mark@grondar.za>
Cc: freebsd-current@FreeBSD.ORG
Subject: Re: make aout-to-elf-build failure
References: <m1047WH-0008G4C@rip.psg.com>
<199901231907.LAA16027@vashon.polstra.com>
<m104A3n-0008G4C@rip.psg.com>
<199901240817.KAA02681@greenpeace.grondar.za>
<m104NL6-0008G4C@rip.psg.com>
<199901241119.NAA03526@greenpeace.grondar.za>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
oops! still have
/usr/obj/aout/usr/src/tmp/usr/libexec/elf/ld: warning: libcrypt.so.2, needed by /usr/obj/elf/usr/src/kerberosIV/libexec/kipd/../../lib/libkrb/libkrb.so, not found (try using --rpath)
/usr/obj/elf/usr/src/kerberosIV/libexec/kipd/../../lib/libkrb/libkrb.so: undefined reference to `crypt'
*** Error code 1
Stop.
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Sun Jan 24 07:20:06 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id HAA12991
for freebsd-current-outgoing; Sun, 24 Jan 1999 07:20:06 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from oldnews.quick.net ([207.212.170.1])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA12985
for <current@freebsd.org>; Sun, 24 Jan 1999 07:20:03 -0800 (PST)
(envelope-from donegan@oldnews.quick.net)
Received: (from donegan@localhost) by oldnews.quick.net (8.8.5/8.6.9) id HAA13534; Sun, 24 Jan 1999 07:19:49 -0800 (PST)
Date: Sun, 24 Jan 1999 07:19:49 -0800 (PST)
From: "Steven P. Donegan" <donegan@quick.net>
To: current@FreeBSD.ORG
Subject: Current's availability
Message-ID: <Pine.BSI.3.91.990124071736.11812C-100000@oldnews.quick.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
Yesterday I tried to ftp a current set of floppies from
current.freebsd.org - nothing there but 2.2.X stuff - 3.0 tree gone and
no 4.X tree apparent. Today I get connection refused at that site. ANy
pointers to a current tree would be appreciated. TIA.
Steven P. Donegan email: donegan@quick.net
Sr. Network Infrastructure Engineer ICBM: N 33' 47.538/W 117' 59.687
WANG Global (within 1 meter - 133 ASL)
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Sun Jan 24 07:25:41 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id HAA13286
for freebsd-current-outgoing; Sun, 24 Jan 1999 07:25:41 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from gratis.grondar.za (gratis.grondar.za [196.7.18.65])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA13281
for <freebsd-current@FreeBSD.ORG>; Sun, 24 Jan 1999 07:25:36 -0800 (PST)
(envelope-from mark@grondar.za)
Received: from greenpeace.grondar.za (greenpeace.grondar.za [196.7.18.132])
by gratis.grondar.za (8.9.2/8.9.2) with ESMTP id RAA00981;
Sun, 24 Jan 1999 17:25:19 +0200 (SAST)
(envelope-from mark@grondar.za)
Received: from grondar.za (localhost [127.0.0.1])
by greenpeace.grondar.za (8.9.2/8.9.2) with ESMTP id RAA16018;
Sun, 24 Jan 1999 17:25:18 +0200 (SAST)
(envelope-from mark@grondar.za)
Message-Id: <199901241525.RAA16018@greenpeace.grondar.za>
To: Randy Bush <randy@psg.com>
cc: freebsd-current@FreeBSD.ORG
Subject: Re: make aout-to-elf-build failure
In-Reply-To: Your message of " Sun, 24 Jan 1999 07:18:57 PST." <m104RJR-0008G4C@rip.psg.com>
References: <m1047WH-0008G4C@rip.psg.com> <199901231907.LAA16027@vashon.polstra.com> <m104A3n-0008G4C@rip.psg.com> <199901240817.KAA02681@greenpeace.grondar.za> <m104NL6-0008G4C@rip.psg.com> <199901241119.NAA03526@greenpeace.grondar.za> <m104RJR-0008G4C@rip.psg.com>
Date: Sun, 24 Jan 1999 17:25:17 +0200
From: Mark Murray <mark@grondar.za>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
Randy Bush wrote:
> oops! still have
>
> /usr/obj/aout/usr/src/tmp/usr/libexec/elf/ld: warning: libcrypt.so.2, needed
by /usr/obj/elf/usr/src/kerberosIV/libexec/kipd/../../lib/libkrb/libkrb.so, not
found (try using --rpath)
> /usr/obj/elf/usr/src/kerberosIV/libexec/kipd/../../lib/libkrb/libkrb.so: unde
fined reference to `crypt'
> *** Error code 1
If you are in a hurry, follow the procedure I gave in the other mail.
Otherwise, wait for the fix, coming right now :-).
I an Mr. Kerberos (Freebsd division) if you haven't deduced this already :)
M
--
Mark Murray
Join the anti-SPAM movement: http://www.cauce.org
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Sun Jan 24 07:26:32 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id HAA13500
for freebsd-current-outgoing; Sun, 24 Jan 1999 07:26:32 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from flood.ping.uio.no (flood.ping.uio.no [129.240.78.31])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA13482;
Sun, 24 Jan 1999 07:26:20 -0800 (PST)
(envelope-from des@flood.ping.uio.no)
Received: (from des@localhost)
by flood.ping.uio.no (8.9.1/8.9.1) id QAA54715;
Sun, 24 Jan 1999 16:25:41 +0100 (CET)
(envelope-from des)
To: Mark Murray <mark@grondar.za>
Cc: Dag-Erling Smorgrav <des@flood.ping.uio.no>,
Kazutaka YOKOTA <yokota@zodiac.mech.utsunomiya-u.ac.jp>,
peter@netplex.com.au, sos@FreeBSD.ORG, current@FreeBSD.ORG
Subject: Re: Death to LKM screen savers? (was: Re: HEADS UP: i386 a.out LKM support now an option..)
References: <199901171925.DAA06456@spinner.netplex.com.au> <199901240255.LAA24094@zodiac.mech.utsunomiya-u.ac.jp> <xzpzp79ny37.fsf@flood.ping.uio.no> <xzpyamtnwl0.fsf@flood.ping.uio.no> <199901240822.KAA02825@greenpeace.grondar.za>
From: Dag-Erling Smorgrav <des@flood.ping.uio.no>
Date: 24 Jan 1999 16:25:38 +0100
In-Reply-To: Mark Murray's message of "Sun, 24 Jan 1999 10:22:52 +0200"
Message-ID: <xzpognog0b1.fsf@flood.ping.uio.no>
Lines: 12
X-Mailer: Gnus v5.5/Emacs 19.34
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
Mark Murray <mark@grondar.za> writes:
> Dag-Erling Smorgrav wrote:
> > Doh, they were already axed by sos in late December. 'cvs co src/lkm'
> > still creates directories for them though. I'm sure someone with more
> > CVS experience than me will be able to explain why :)
> Because you left off the "-P" "Prune empty directories" flag.
Yeah, I thought I had that in my .cvsrc but apparently not. Thanks!
DES
--
Dag-Erling Smorgrav - des@flood.ping.uio.no
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Sun Jan 24 07:37:44 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id HAA14313
for freebsd-current-outgoing; Sun, 24 Jan 1999 07:37:44 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from gratis.grondar.za (gratis.grondar.za [196.7.18.65])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA14308
for <freebsd-current@FreeBSD.ORG>; Sun, 24 Jan 1999 07:37:37 -0800 (PST)
(envelope-from mark@grondar.za)
Received: from greenpeace.grondar.za (greenpeace.grondar.za [196.7.18.132])
by gratis.grondar.za (8.9.2/8.9.2) with ESMTP id RAA01421;
Sun, 24 Jan 1999 17:37:22 +0200 (SAST)
(envelope-from mark@grondar.za)
Received: from grondar.za (localhost [127.0.0.1])
by greenpeace.grondar.za (8.9.2/8.9.2) with ESMTP id RAA16096;
Sun, 24 Jan 1999 17:37:19 +0200 (SAST)
(envelope-from mark@grondar.za)
Message-Id: <199901241537.RAA16096@greenpeace.grondar.za>
To: Randy Bush <randy@psg.com>
cc: freebsd-current@FreeBSD.ORG
Subject: Re: make aout-to-elf-build failure
In-Reply-To: Your message of " Sun, 24 Jan 1999 07:18:57 PST." <m104RJR-0008G4C@rip.psg.com>
References: <m1047WH-0008G4C@rip.psg.com> <199901231907.LAA16027@vashon.polstra.com> <m104A3n-0008G4C@rip.psg.com> <199901240817.KAA02681@greenpeace.grondar.za> <m104NL6-0008G4C@rip.psg.com> <199901241119.NAA03526@greenpeace.grondar.za> <m104RJR-0008G4C@rip.psg.com>
Date: Sun, 24 Jan 1999 17:37:18 +0200
From: Mark Murray <mark@grondar.za>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
Randy Bush wrote:
> oops! still have
>
> /usr/obj/aout/usr/src/tmp/usr/libexec/elf/ld: warning: libcrypt.so.2, needed
by /usr/obj/elf/usr/src/kerberosIV/libexec/kipd/../../lib/libkrb/libkrb.so, not
found (try using --rpath)
> /usr/obj/elf/usr/src/kerberosIV/libexec/kipd/../../lib/libkrb/libkrb.so: unde
fined reference to `crypt'
> *** Error code 1
Hi
Just in case you get any more of these (mentioning `crypt'), here is a
workaround:
Go to the right subdirectory (in this case
/usr/src/kerberosIV/libexec/kipd/) and edit the Makefile; add
-lcrypt to the end of the LDADD line. You may need to remove it
later, but it will keep your build going. I'd be grateful for
reports of places where this is necesary.
M
--
Mark Murray
Join the anti-SPAM movement: http://www.cauce.org
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Sun Jan 24 09:01:12 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id JAA22244
for freebsd-current-outgoing; Sun, 24 Jan 1999 09:01:12 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from po4.wam.umd.edu (po4.wam.umd.edu [128.8.10.166])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA22238
for <freebsd-current@freebsd.org>; Sun, 24 Jan 1999 09:01:10 -0800 (PST)
(envelope-from culverk@wam.umd.edu)
Received: from rac6.wam.umd.edu ((IDENT root)@rac6.wam.umd.edu [128.8.10.146])
by po4.wam.umd.edu (8.9.0.Beta6/8.9.0.Beta6) with ESMTP id MAA09903
for <freebsd-current@freebsd.org>; Sun, 24 Jan 1999 12:00:58 -0500 (EST)
Received: from rac6.wam.umd.edu ((IDENT sendmail)@localhost [127.0.0.1])
by rac6.wam.umd.edu (8.9.0.Beta6/8.9.0.Beta6) with SMTP id MAA07398
for <freebsd-current@freebsd.org>; Sun, 24 Jan 1999 12:00:56 -0500 (EST)
Received: from localhost by rac6.wam.umd.edu (8.9.0.Beta6/8.9.0.Beta6) with SMTP id MAA07393
for <freebsd-current@freebsd.org>; Sun, 24 Jan 1999 12:00:55 -0500 (EST)
X-Authentication-Warning: rac6.wam.umd.edu: culverk owned process doing -bs
Date: Sun, 24 Jan 1999 12:00:55 -0500 (EST)
From: Kenneth Wayne Culver <culverk@wam.umd.edu>
To: freebsd-current@FreeBSD.ORG
Subject: pcm0
Message-ID: <Pine.GSO.3.95q.990124115851.7281A-100000@rac6.wam.umd.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
I tried out pcm0 for sound on a ViBRA16x soundcard (don't laugh) and sound
works. The only problem is that there is no mixer. I was wondering if this
was a known problem with my card, or if nobody has done the mixer code
yet... Thanks.
Kenneth Culver
Computer Science Major at the University of Maryland, College Park.
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Sun Jan 24 09:03:35 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id JAA22600
for freebsd-current-outgoing; Sun, 24 Jan 1999 09:03:35 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from stade.demon.co.uk (stade.demon.co.uk [158.152.29.164])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA22592
for <freebsd-current@FreeBSD.ORG>; Sun, 24 Jan 1999 09:03:29 -0800 (PST)
(envelope-from aw1@stade.co.uk)
Received: (from aw1@localhost)
by stade.demon.co.uk (8.9.2/8.9.1) id RAA01143
for freebsd-current@FreeBSD.ORG; Sun, 24 Jan 1999 17:01:40 GMT
(envelope-from aw1)
Date: Sun, 24 Jan 1999 17:01:40 +0000
From: Adrian Wontroba <aw1@stade.co.uk>
To: freebsd-current@FreeBSD.ORG
Subject: Re: Booting -current with new loader
Message-ID: <19990124170140.A688@titus.stade.co.uk>
Reply-To: aw1@stade.co.uk
References: <Pine.LNX.3.95.990121114034.29987E-100000@nhj.nlc.net.au> <199901210700.XAA06653@dingo.cdrom.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.95.1i
In-Reply-To: <199901210700.XAA06653@dingo.cdrom.com>; from Mike Smith on Wed, Jan 20, 1999 at 11:00:27PM -0800
X-Operating-System: FreeBSD 4.0-CURRENT
Organization: Yes, I need some of that.
X-Phone: +(44) 121 681 6677
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
On Wed, Jan 20, 1999 at 11:00:27PM -0800, Mike Smith wrote:
> Right now I'm looking at stamping the disklabel which contains the
> designated root filesystem and passing the stamp into the kernel, which
> will then go look for it. There are still gremlins with this approach,
> but I can't think of anything better. 8(
Well, it would probably help avoid the confusion and terror I went
through today (8-)
I updated my boot blocks (last done a month ago) and the machine refused
to mount my root filesystem (on /dev/da0s2a) with "specified device does
not match mounted device".
The machine would load OK with /kernel at the boot prompt. After fiddling with
num_ide_disks and some RTSLing, I discovered root_disc_unit (8-)
set num_ide_disks=-1
set root_disk_unit=0 <<<<<<<<<<<<<<<<<<<<<
load /kernel
load -t userconfig_script /kernel.config
autoboot
Bliss!
--
Adrian Wontroba
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Sun Jan 24 09:04:08 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id JAA22778
for freebsd-current-outgoing; Sun, 24 Jan 1999 09:04:08 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from stade.demon.co.uk (stade.demon.co.uk [158.152.29.164])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA22737
for <current@FreeBSD.ORG>; Sun, 24 Jan 1999 09:03:59 -0800 (PST)
(envelope-from aw1@stade.co.uk)
Received: (from aw1@localhost)
by stade.demon.co.uk (8.9.2/8.9.1) id QAA03266;
Sun, 24 Jan 1999 16:09:30 GMT
(envelope-from aw1)
Date: Sun, 24 Jan 1999 16:09:30 +0000
From: Adrian Wontroba <aw1@stade.co.uk>
To: Matthew Dillon <dillon@apollo.backplane.com>
Cc: current@FreeBSD.ORG
Subject: Re: Heads up! New swapper and VM changes have been committed to -4.x
Message-ID: <19990124160930.A2534@titus.stade.co.uk>
Reply-To: aw1@stade.co.uk
References: <199901210456.UAA10191@apollo.backplane.com> <199901210855.AAA05930@apollo.backplane.com> <19990123104630.A74306@titus.stade.co.uk> <199901240045.QAA52250@apollo.backplane.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.95.1i
In-Reply-To: <199901240045.QAA52250@apollo.backplane.com>; from Matthew Dillon on Sat, Jan 23, 1999 at 04:45:34PM -0800
X-Operating-System: FreeBSD 4.0-CURRENT
Organization: Yes, I need some of that.
X-Phone: +(44) 121 681 6677
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
On Sat, Jan 23, 1999 at 04:45:34PM -0800, Matthew Dillon wrote:
<swapinfo totals not adding up>
> Make sure your /usr/src/lib/libkvm is updated. Also update
> /usr/src/include/kvm.h. Then update and recompile top, systat,
> and pstat.
Ahh. My cvsup / cvs / buildworld must have been at just the wrong
time. This morning's has fixed swapinfo, top and systat/swap.
--
Adrian Wontroba
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Sun Jan 24 09:09:41 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id JAA23148
for freebsd-current-outgoing; Sun, 24 Jan 1999 09:09:41 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from labinfo.iet.unipi.it (labinfo.iet.unipi.it [131.114.9.5])
by hub.freebsd.org (8.8.8/8.8.8) with SMTP id JAA23139
for <freebsd-current@FreeBSD.ORG>; Sun, 24 Jan 1999 09:09:37 -0800 (PST)
(envelope-from luigi@labinfo.iet.unipi.it)
Received: from localhost (luigi@localhost) by labinfo.iet.unipi.it (8.6.5/8.6.5) id PAA23998; Sun, 24 Jan 1999 15:57:58 +0100
From: Luigi Rizzo <luigi@labinfo.iet.unipi.it>
Message-Id: <199901241457.PAA23998@labinfo.iet.unipi.it>
Subject: Re: pcm0
To: culverk@wam.umd.edu (Kenneth Wayne Culver)
Date: Sun, 24 Jan 1999 15:57:58 +0100 (MET)
Cc: freebsd-current@FreeBSD.ORG
In-Reply-To: <Pine.GSO.3.95q.990124115851.7281A-100000@rac6.wam.umd.edu> from "Kenneth Wayne Culver" at Jan 24, 99 12:00:36 pm
X-Mailer: ELM [version 2.4 PL23]
Content-Type: text
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
> I tried out pcm0 for sound on a ViBRA16x soundcard (don't laugh) and sound
> works. The only problem is that there is no mixer. I was wondering if this
> was a known problem with my card, or if nobody has done the mixer code
i think it kind of worked a few months ago when i put in support for
the Vibra16X -- are you sure your /dev/mixer is linked to the correct
device (/dev/mixer1) ?
luigi
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Sun Jan 24 09:09:41 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id JAA23149
for freebsd-current-outgoing; Sun, 24 Jan 1999 09:09:41 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from dingo.cdrom.com (castles340.castles.com [208.214.167.40])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA23138
for <current@FreeBSD.ORG>; Sun, 24 Jan 1999 09:09:37 -0800 (PST)
(envelope-from mike@dingo.cdrom.com)
Received: from dingo.cdrom.com (LOCALHOST [127.0.0.1])
by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id JAA03841;
Sun, 24 Jan 1999 09:05:40 -0800 (PST)
(envelope-from mike@dingo.cdrom.com)
Message-Id: <199901241705.JAA03841@dingo.cdrom.com>
X-Mailer: exmh version 2.0.2 2/24/98
To: Kris Kennaway <kkennawa@physics.adelaide.edu.au>
cc: Christopher Masto <chris@netmonger.net>, current@FreeBSD.ORG
Subject: Re: Running 4.0, a few weirdies
In-reply-to: Your message of "Sun, 24 Jan 1999 21:07:18 +1030."
<Pine.OSF.4.05.9901242103460.31801-100000@bragg>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Sun, 24 Jan 1999 09:05:40 -0800
From: Mike Smith <mike@smith.net.au>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
> On Sun, 24 Jan 1999, Christopher Masto wrote:
>
> > The old "unable to mount /, specified device does not match root
> > device" on booting. My /etc/fstab had (working with -current from
> > just a few weeks ago):
> >
> > /dev/wd0s1a / ufs rw 1 1
> >
> > I thought this was the new world order.. apparently not. I had to change
> > it back to:
> >
> > /dev/wd0a / ufs rw 1 1
>
> Just another datapoint: I just bumped into this too upon tipping over to 4.0.
Can you boot single-user and send me the output of 'mount'?
If you are showing "root_device" on /, you need to re-sup, rebuild and
reinstall your bootblocks, then go back to your old /etc/fstab.
Note that mount and fsck are supposed to ignore the /etc/fstab settings
for / if they can work out what's already there.
--
\\ Sometimes you're ahead, \\ Mike Smith
\\ sometimes you're behind. \\ mike@smith.net.au
\\ The race is long, and in the \\ msmith@freebsd.org
\\ end it's only with yourself. \\ msmith@cdrom.com
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Sun Jan 24 09:18:09 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id JAA23912
for freebsd-current-outgoing; Sun, 24 Jan 1999 09:18:09 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from smtp01.wxs.nl (smtp01.wxs.nl [195.121.6.61])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA23906
for <current@FreeBSD.ORG>; Sun, 24 Jan 1999 09:18:07 -0800 (PST)
(envelope-from asmodai@wxs.nl)
Received: from daemon.ninth-circle.org ([195.121.57.171]) by smtp01.wxs.nl
(Netscape Messaging Server 3.6) with ESMTP id AAA6DB3
for <current@FreeBSD.ORG>; Sun, 24 Jan 1999 18:17:54 +0100
Message-ID: <XFMail.990124182612.asmodai@wxs.nl>
X-Mailer: XFMail 1.3 [p0] on FreeBSD
X-Priority: 3 (Normal)
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 8bit
MIME-Version: 1.0
Date: Sun, 24 Jan 1999 18:26:12 +0100 (CET)
Organization: Ninth Circle Enterprises
From: Jeroen Ruigrok/Asmodai <asmodai@wxs.nl>
To: FreeBSD Current <current@FreeBSD.ORG>
Subject: Transition to 4.0
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
Just a general note to Matt, Mark and a couple of other commiters:
my transition from 3.0 CURRENT to 4.0 CURRENT (make world and a new kernel)
as of today Sun Jan 24 18:25:32 CET 1999 work flawlessly up till now.
Hope this is some good info after all the breakages =)
---
Jeroen Ruigrok van der Werven It's a Dance of Energy,
asmodai(at)wxs.nl when the Mind goes Binary...
Network/Security Specialist <http://home.wxs.nl/~asmodai>
BSD & picoBSD: The Power to Serve <http://www.freebsd.org>
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Sun Jan 24 09:23:38 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id JAA24337
for freebsd-current-outgoing; Sun, 24 Jan 1999 09:23:38 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from cx757770-a.fed1.sdca.home.com (cx757770-a.fed1.sdca.home.com [24.0.167.56])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA24332
for <FreeBSD-current@FreeBSD.ORG>; Sun, 24 Jan 1999 09:23:36 -0800 (PST)
(envelope-from daren@sefcik.cc)
Received: from sefcik.cc (rover.sefcik.cc [10.0.0.9])
by cx757770-a.fed1.sdca.home.com (8.9.1/8.9.1) with ESMTP id JAA08647
for <FreeBSD-current@FreeBSD.ORG>; Sun, 24 Jan 1999 09:31:11 -0800 (PST)
Message-ID: <36AB5AE5.D0235F6B@sefcik.cc>
Date: Sun, 24 Jan 1999 09:39:49 -0800
From: Daren Sefcik <daren@sefcik.cc>
X-Mailer: Mozilla 4.07 [en] (X11; I; FreeBSD 3.0-CURRENT i386)
MIME-Version: 1.0
To: FreeBSD-current@FreeBSD.ORG
Subject: subscribe daren@sefcik.cc
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
subscribe daren@sefcik.cc
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Sun Jan 24 09:27:56 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id JAA24784
for freebsd-current-outgoing; Sun, 24 Jan 1999 09:27:56 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from dingo.cdrom.com (castles340.castles.com [208.214.167.40])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA24779
for <freebsd-current@FreeBSD.ORG>; Sun, 24 Jan 1999 09:27:54 -0800 (PST)
(envelope-from mike@dingo.cdrom.com)
Received: from dingo.cdrom.com (LOCALHOST [127.0.0.1])
by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id JAA03964;
Sun, 24 Jan 1999 09:23:57 -0800 (PST)
(envelope-from mike@dingo.cdrom.com)
Message-Id: <199901241723.JAA03964@dingo.cdrom.com>
X-Mailer: exmh version 2.0.2 2/24/98
To: "Harry Starr" <starr3@gccs.com.au>
cc: "Daniel C. Sobral" <dcs@newsguy.com>,
"current" <freebsd-current@FreeBSD.ORG>
Subject: Re: Problem booting using /boot/loader
In-reply-to: Your message of "Mon, 25 Jan 1999 00:28:09 +1000."
<049701be47a5$c455b600$0a9811cb@gccs.com.au>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Sun, 24 Jan 1999 09:23:57 -0800
From: Mike Smith <mike@smith.net.au>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
> Yep!
>
> /boot/loader.old works OK! (dated Jan 11)
>
> /boot/loader (Jan 24) fails.
>
> And yes, the kernel was recompiled from the same cvsup sources.
>
> Definitely looks like something broke in the current loader.
There was a window of a few hours where the 4-current loader was broken
due to a typo on my part. I forgot to merge the fix back into 3-stable
(which I've just now done).
Please resup/rebuild/reinstall the loader. Also note that for those of
you that had to change your /etc/fstab - you'll have to change it right
back. 8)
If you have to push through a loader that has this bug,
'set root_disk_unit=0' for eg. a system with root on wd0 or da0 will
avoid the broken code.
--
\\ Sometimes you're ahead, \\ Mike Smith
\\ sometimes you're behind. \\ mike@smith.net.au
\\ The race is long, and in the \\ msmith@freebsd.org
\\ end it's only with yourself. \\ msmith@cdrom.com
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Sun Jan 24 09:33:47 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id JAA25620
for freebsd-current-outgoing; Sun, 24 Jan 1999 09:33:47 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from dingo.cdrom.com (castles340.castles.com [208.214.167.40])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA25614
for <freebsd-current@FreeBSD.ORG>; Sun, 24 Jan 1999 09:33:45 -0800 (PST)
(envelope-from mike@dingo.cdrom.com)
Received: from dingo.cdrom.com (LOCALHOST [127.0.0.1])
by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id JAA04022;
Sun, 24 Jan 1999 09:30:00 -0800 (PST)
(envelope-from mike@dingo.cdrom.com)
Message-Id: <199901241730.JAA04022@dingo.cdrom.com>
X-Mailer: exmh version 2.0.2 2/24/98
To: aw1@stade.co.uk
cc: freebsd-current@FreeBSD.ORG
Subject: Re: Booting -current with new loader
In-reply-to: Your message of "Sun, 24 Jan 1999 17:01:40 GMT."
<19990124170140.A688@titus.stade.co.uk>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Sun, 24 Jan 1999 09:29:59 -0800
From: Mike Smith <mike@smith.net.au>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
> On Wed, Jan 20, 1999 at 11:00:27PM -0800, Mike Smith wrote:
> > Right now I'm looking at stamping the disklabel which contains the
> > designated root filesystem and passing the stamp into the kernel, which
> > will then go look for it. There are still gremlins with this approach,
> > but I can't think of anything better. 8(
>
> Well, it would probably help avoid the confusion and terror I went
> through today (8-)
>
> I updated my boot blocks (last done a month ago) and the machine refused
> to mount my root filesystem (on /dev/da0s2a) with "specified device does
> not match mounted device".
>
> The machine would load OK with /kernel at the boot prompt. After fiddling with
> num_ide_disks and some RTSLing, I discovered root_disc_unit (8-)
>
> set num_ide_disks=-1
> set root_disk_unit=0 <<<<<<<<<<<<<<<<<<<<<
> load /kernel
> load -t userconfig_script /kernel.config
> autoboot
Yeah, my fault. num_ide_disks is now deprecated, you can throw it
away. If you resup, you won't need root_disk_unit either - that just
avoids the code I broke.
--
\\ Sometimes you're ahead, \\ Mike Smith
\\ sometimes you're behind. \\ mike@smith.net.au
\\ The race is long, and in the \\ msmith@freebsd.org
\\ end it's only with yourself. \\ msmith@cdrom.com
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Sun Jan 24 09:34:48 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id JAA25731
for freebsd-current-outgoing; Sun, 24 Jan 1999 09:34:48 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from hawaii.conterra.com (hawaii.conterra.com [209.12.164.32])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA25711;
Sun, 24 Jan 1999 09:34:44 -0800 (PST)
(envelope-from myself@conterra.com)
Received: from dmaddox.conterra.com (dmaddox.conterra.com [209.12.169.48])
by hawaii.conterra.com (8.8.8/8.8.7) with ESMTP id MAA22971;
Sun, 24 Jan 1999 12:34:31 -0500 (EST)
Received: (from myself@localhost)
by dmaddox.conterra.com (8.9.2/8.9.1) id MAA00779;
Sun, 24 Jan 1999 12:34:31 -0500 (EST)
(envelope-from myself)
Date: Sun, 24 Jan 1999 12:34:30 -0500
From: "Donald J . Maddox" <dmaddox@conterra.com>
To: Tom Torrance at home <tom@tomqnx.com>
Cc: hackers@FreeBSD.ORG, current@FreeBSD.ORG
Subject: Re: RELENG_3 boot failed
Message-ID: <19990124123430.B709@dmaddox.conterra.com>
Reply-To: dmaddox@conterra.com
References: <m104RZL-000I5qC@TomQNX.tomqnx.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.95.1i
In-Reply-To: <m104RZL-000I5qC@TomQNX.tomqnx.com>; from Tom Torrance at home on Sun, Jan 24, 1999 at 10:35:23AM -0500
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
On Sun, Jan 24, 1999 at 10:35:23AM -0500, Tom Torrance at home wrote:
> After a cvsup this AM, the boot process failed when attempting
> to mount the root partition, with the message:
> specified device does no match mounted device.
>
> I had to change the device specification in /etc/fstab from
> /dev/da0s2a to /dev/da0a to boot properly.
Whoops... I just noted that you're using RELENG_3, but I'm
getting the same problem on:
FreeBSD 4.0-CURRENT #0: Sun Jan 24 00:23:52 EST 1999
so I'm cc'ing -current on this reply...
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Sun Jan 24 09:39:11 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id JAA26087
for freebsd-current-outgoing; Sun, 24 Jan 1999 09:39:11 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from po4.wam.umd.edu (po4.wam.umd.edu [128.8.10.166])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA26081
for <freebsd-current@freebsd.org>; Sun, 24 Jan 1999 09:39:08 -0800 (PST)
(envelope-from culverk@wam.umd.edu)
Received: from rac2.wam.umd.edu ((IDENT root)@rac2.wam.umd.edu [128.8.10.142])
by po4.wam.umd.edu (8.9.0.Beta6/8.9.0.Beta6) with ESMTP id MAA10778
for <freebsd-current@freebsd.org>; Sun, 24 Jan 1999 12:38:56 -0500 (EST)
Received: from rac2.wam.umd.edu ((IDENT sendmail)@localhost [127.0.0.1])
by rac2.wam.umd.edu (8.9.0.Beta6/8.9.0.Beta6) with SMTP id MAA09317
for <freebsd-current@freebsd.org>; Sun, 24 Jan 1999 12:38:55 -0500 (EST)
Received: from localhost by rac2.wam.umd.edu (8.9.0.Beta6/8.9.0.Beta6) with SMTP id MAA09312
for <freebsd-current@freebsd.org>; Sun, 24 Jan 1999 12:38:54 -0500 (EST)
X-Authentication-Warning: rac2.wam.umd.edu: culverk owned process doing -bs
Date: Sun, 24 Jan 1999 12:38:54 -0500 (EST)
From: Kenneth Wayne Culver <culverk@wam.umd.edu>
To: freebsd-current@FreeBSD.ORG
Subject: one other small prob with pcm0
Message-ID: <Pine.GSO.3.95q.990124123535.9252A-100000@rac2.wam.umd.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
This is a trivial problem, but I just thought I'd let someone know about
it. (cosmetic) Take a look at my dmesg output:
Copyright (c) 1992-1999 FreeBSD Inc.
Copyright (c) 1982, 1986, 1989, 1991, 1993
The Regents of the University of California. All rights reserved.
FreeBSD 4.0-CURRENT #1: Sun Jan 24 12:29:32 EST 1999
culverk@localhost.x-press.net:/usr/src/sys/compile/MYKERNEL
Timecounter "i8254" frequency 1193182 Hz
Timecounter "TSC" frequency 199739418 Hz
CPU: AMD-K6tm w/ multimedia extensions (199.74-MHz 586-class CPU)
Origin = "AuthenticAMD" Id = 0x562 Stepping=2
Features=0x8001bf<FPU,VME,DE,PSE,TSC,MSR,MCE,CX8,MMX>
real memory = 67108864 (65536K bytes)
avail memory = 62918656 (61444K bytes)
Preloaded elf kernel "kernel" at 0xf024e000.
Preloaded splash_image_data "/boot/banner2.bmp" at 0xf024e09c.
Preloaded elf module "splash_bmp.ko" at 0xf024e0ec.
Probing for devices on PCI bus 0:
chip0: <Host to PCI bridge (vendor=10b9 device=1531)> rev 0xb2 on pci0.0.0
chip1: <AcerLabs M1533 portable PCI-ISA bridge> rev 0xb4 on pci0.2.0
de0: <Digital 21140A Fast Ethernet> rev 0x22 int a irq 11 on pci0.3.0
de0: 21140A [10-100Mb/s] pass 2.2
de0: address 00:c0:f0:1f:21:02
vga0: <Cirrus Logic GD5446 SVGA controller> rev 0x00 on pci0.4.0
ide_pci0: <Acer Aladdin IV/V (M5229) Bus-master IDE controller> rev 0x20 int a i
rq 0 on pci0.11.0
Probing for PnP devices:
CSN 1 Vendor ID: SUP2074 [0x7420b04e] Serial 0x00007916 Comp ID: @@@0000
[0x00000000]
CSN 2 Vendor ID: CTL00f0 [0xf0008c0e] Serial 0xffffffff Comp ID: PNPb02f
[0x2fb0d041]
pcm1 (SB16pnp <Vibra16X> sn 0xffffffff) at 0x220-0x22f irq 5 drq 1 flags
0x13 on isa
Probing for devices on the ISA bus:
sc0 on isa
sc0: VGA color <16 virtual consoles, flags=0x0>
atkbdc0 at 0x60-0x6f on motherboard
atkbd0 irq 1 on isa
psm0 irq 12 on isa
psm0: model IntelliMouse, device ID 3
pcm0 not found
The rest has been cut out because it doesn't matter.
My problem is that although pcm1 works, why does the message above about
pcm0 not found come up?? Thanks.
Kenneth Culver
Computer Science Major at the University of Maryland, College Park.
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Sun Jan 24 09:52:19 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id JAA27662
for freebsd-current-outgoing; Sun, 24 Jan 1999 09:52:19 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from cerebus.nectar.com (nectar-gw.nectar.com [204.0.249.101])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA27652
for <current@FreeBSD.ORG>; Sun, 24 Jan 1999 09:52:17 -0800 (PST)
(envelope-from nectar@nectar.com)
Received: (from smap@localhost)
by cerebus.nectar.com (8.9.1/8.9.1) id LAA00679;
Sun, 24 Jan 1999 11:52:01 -0600 (CST)
(envelope-from nectar@nectar.com)
Received: from spawn.nectar.com(10.0.0.101) by cerebus.nectar.com via smap (V2.1)
id xma000677; Sun, 24 Jan 99 11:51:57 -0600
Received: from spawn.nectar.com (localhost [127.0.0.1])
by spawn.nectar.com (8.9.2/8.9.1) with ESMTP id LAA83676;
Sun, 24 Jan 1999 11:51:58 -0600 (CST)
(envelope-from nectar@spawn.nectar.com)
Message-Id: <199901241751.LAA83676@spawn.nectar.com>
X-Mailer: exmh version 2.0.2 2/24/98
X-PGP-RSAfprint: 00 F9 E6 A2 C5 4D 0A 76 26 8B 8B 57 73 D0 DE EE
X-PGP-RSAkey: http://www.nectar.com/nectar-pgp262.txt
From: Jacques Vidrine <n@nectar.com>
In-reply-to: <Pine.BSF.4.02A.9901231943050.22339-100000@peloton.physics.montana.edu>
References: <Pine.BSF.4.02A.9901231943050.22339-100000@peloton.physics.montana.edu>
Subject: Re: ack! LaTeX?
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
To: Brett Taylor <brett@peloton.physics.montana.edu>
cc: Jacques Vidrine <n@nectar.com>, current@FreeBSD.ORG
Date: Sun, 24 Jan 1999 11:51:58 -0600
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
On 23 January 1999 at 19:44, Brett Taylor <brett@peloton.physics.montana.edu> wrote:
> How is teTeX not working? I'm using a month or so old version of -current
> (back in the 3.0 days) on my home machine and teTeX works fine there.
The latex installed by the teTex port complained about not being able to
find default settings, or some such.
I'm now using teTeX-beta after rebuilding libwww. Previously it complained
about undefined symbols. I thought my libwww was fresh, but now I must
suppose not.
Jacques Vidrine / n@nectar.com / nectar@FreeBSD.org
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Sun Jan 24 09:59:03 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id JAA28401
for freebsd-current-outgoing; Sun, 24 Jan 1999 09:59:03 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA28395
for <current@FreeBSD.ORG>; Sun, 24 Jan 1999 09:59:02 -0800 (PST)
(envelope-from dillon@apollo.backplane.com)
Received: (from dillon@localhost)
by apollo.backplane.com (8.9.2/8.9.1) id JAA03816;
Sun, 24 Jan 1999 09:58:13 -0800 (PST)
(envelope-from dillon)
Date: Sun, 24 Jan 1999 09:58:13 -0800 (PST)
From: Matthew Dillon <dillon@apollo.backplane.com>
Message-Id: <199901241758.JAA03816@apollo.backplane.com>
To: Wilko Bulte <wilko@yedi.iaf.nl>
Cc: Doug Rabson <dfr@nlsystems.com>, current@FreeBSD.ORG
Subject: Re: panic: found dirty cache page 0xf046f1c0
References: <199901241457.PAA12682@yedi.iaf.nl>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
:FYI: a buildworld of -current including the above on FreeBSD/axp completed
:without any incidents.
:
:Wilko
:...
:... ( other reports )
We are looking good, I've got half a dozen positive reports!
On general principles, I think it is possible to make the FreeBSD
VM system bulletproof. The problem is that there are lots of odd
exceptions and special rules that haven't been black-boxed or even
documented ( other then being in John's head, which isn't all that
useful to me ). The rules tend to be layed out in code on each
occurance, which inevitably leads to mistakes. The mistakes
are further compounded by a severe lack of enforcement ( KASSERT()s )
and thus propogate from release to release, building up as time passes.
With appropriate black boxing, documentation, and enforcement, it
should be fairly easy to shorten the development cycle on finding
the bugs. __inline procedures are a godsend because there are literally
a hundred places in the code where someone 'optimized' it by doing
a manual expansion of something from some other module in order to avoid
a subroutine call. This cross module pollinization tends to make
things even less readable. Bleh.
So, for example, a few commits ago I added enforcement of the no-dirty-
pages-on-cache-queue rule and systems started to panic. That enforcement
had to be extended to every dirtying of a page before we actually found
the bug ( which turned out to be a -3.x bug ). More recently I have
added enforcement for PG_BUSY state changes to disallow the busying of
an already-busy page, and unbusying of a non-busy page.
In discussions with John, there are a number of other rules that have
been broken and need to be fixed. Pages on PQ_CACHE are supposed to be
unqueued prior to being busied, held, or wired, for example, but the
rule is pretty much ignored and a lot of code was hacked in to check for
and requeue ( to another queue) the busy-page-on-cache case.
Entry conditions, exit conditions, and side effects for procedures are
mostly undocumented. biodone() sequencing is not well documented, and
struct buf's have a 'kitchen sink' mentality from being hacked up so much.
There are currently too many NFS-specific exceptions strewn all over
the code.
It all works, but it is also a mess.
-Matt
Matthew Dillon
<dillon@backplane.com>
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Sun Jan 24 10:28:43 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id KAA01544
for freebsd-current-outgoing; Sun, 24 Jan 1999 10:28:43 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from gratis.grondar.za (gratis.grondar.za [196.7.18.65])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA01537
for <current@FreeBSD.ORG>; Sun, 24 Jan 1999 10:28:35 -0800 (PST)
(envelope-from mark@grondar.za)
Received: from greenpeace.grondar.za (greenpeace.grondar.za [196.7.18.132])
by gratis.grondar.za (8.9.2/8.9.2) with ESMTP id TAA44055;
Sun, 24 Jan 1999 19:59:31 +0200 (SAST)
(envelope-from mark@grondar.za)
Received: from grondar.za (localhost [127.0.0.1])
by greenpeace.grondar.za (8.9.2/8.9.2) with ESMTP id TAA19551;
Sun, 24 Jan 1999 19:59:30 +0200 (SAST)
(envelope-from mark@grondar.za)
Message-Id: <199901241759.TAA19551@greenpeace.grondar.za>
To: Jeroen Ruigrok/Asmodai <asmodai@wxs.nl>
cc: FreeBSD Current <current@FreeBSD.ORG>
Subject: Re: Transition to 4.0
In-Reply-To: Your message of " Sun, 24 Jan 1999 18:26:12 +0100." <XFMail.990124182612.asmodai@wxs.nl>
References: <XFMail.990124182612.asmodai@wxs.nl>
Date: Sun, 24 Jan 1999 19:59:29 +0200
From: Mark Murray <mark@grondar.za>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
Jeroen Ruigrok/Asmodai wrote:
> Just a general note to Matt, Mark and a couple of other commiters:
>
> my transition from 3.0 CURRENT to 4.0 CURRENT (make world and a new kernel)
> as of today Sun Jan 24 18:25:32 CET 1999 work flawlessly up till now.
>
> Hope this is some good info after all the breakages =)
Good news is always welcome :-)
M
--
Mark Murray
Join the anti-SPAM movement: http://www.cauce.org
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Sun Jan 24 10:31:56 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id KAA02253
for freebsd-current-outgoing; Sun, 24 Jan 1999 10:31:56 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from frmug.org (frmug-gw.frmug.org [193.56.58.252])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA02240
for <current@FreeBSD.ORG>; Sun, 24 Jan 1999 10:31:52 -0800 (PST)
(envelope-from roberto@keltia.freenix.fr)
Received: (from uucp@localhost)
by frmug.org (8.9.1/frmug-2.3/nospam) with UUCP id TAA20473
for current@FreeBSD.ORG; Sun, 24 Jan 1999 19:31:38 +0100 (CET)
(envelope-from roberto@keltia.freenix.fr)
Received: by keltia.freenix.fr (Postfix, from userid 101)
id B921E1513; Sun, 24 Jan 1999 19:17:05 +0100 (CET)
Date: Sun, 24 Jan 1999 19:17:05 +0100
From: Ollivier Robert <roberto@keltia.freenix.fr>
To: FreeBSD Current <current@FreeBSD.ORG>
Subject: Re: Transition to 4.0
Message-ID: <19990124191705.A61587@keltia.freenix.fr>
Mail-Followup-To: FreeBSD Current <current@FreeBSD.ORG>
References: <XFMail.990124182612.asmodai@wxs.nl>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.95i
In-Reply-To: <XFMail.990124182612.asmodai@wxs.nl>; from Jeroen Ruigrok/Asmodai on Sun, Jan 24, 1999 at 06:26:12PM +0100
X-Operating-System: FreeBSD 3.0-CURRENT/ELF ctm#4994 AMD-K6 MMX @ 200 MHz
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
According to Jeroen Ruigrok/Asmodai:
> my transition from 3.0 CURRENT to 4.0 CURRENT (make world and a new kernel)
> as of today Sun Jan 24 18:25:32 CET 1999 work flawlessly up till now.
Same here with an SMP kernel.
FreeBSD tara 4.0-CURRENT FreeBSD 4.0-CURRENT #9: Sun Jan 24 18:54:47 CET 1999
roberto@tara:/src/src/sys/compile/TARA_SMP i386
CTM cvs-cur #5014 from sources @ 1999/01/24 00:11
--
Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- roberto@keltia.freenix.fr
FreeBSD keltia.freenix.fr 3.0-CURRENT #69: Mon Jan 18 02:02:12 CET 1999
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Sun Jan 24 11:01:20 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id LAA05352
for freebsd-current-outgoing; Sun, 24 Jan 1999 11:01:20 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from rip.psg.com (rip.psg.com [147.28.0.39])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA05343
for <freebsd-current@freebsd.org>; Sun, 24 Jan 1999 11:01:17 -0800 (PST)
(envelope-from randy@psg.com)
Received: from localhost (9974 bytes) by rip.psg.com
via sendmail with P:stdio/R:inet_resolve/T:smtp
(sender: <randy>) (ident <randy> using unix)
id <m104UmP-0008G4C@rip.psg.com>
for <freebsd-current@freebsd.org>; Sun, 24 Jan 1999 11:01:05 -0800 (PST)
(Smail-3.2.0.101 1997-Dec-17 #1 built 1998-Oct-13)
Message-Id: <m104UmP-0008G4C@rip.psg.com>
Date: Sun, 24 Jan 1999 11:01:05 -0800 (PST)
From: Randy Bush <randy@psg.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
To: freebsd-current@FreeBSD.ORG
Subject: gnurr in build-aout-to-elf
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
this looks non-fatal, but unsightly
(cd /usr/src/share/doc/smm/title; groff -mtty-char -Tascii -ms -o1- /usr/src/share/doc/smm/title/Title) | gzip -cn > Title.ascii.gz
/usr/src/share/doc/smm/title/Title:48: warning: `pt' not defined
/usr/src/share/doc/smm/title/Title:173: warning: `Ed' not defined
/usr/src/share/doc/smm/title/Title:173: warning: `Dt' not defined
/usr/src/share/doc/smm/title/Title:173: warning: `OT' not defined
(cd /usr/src/share/doc/smm/01.setup; groff -mtty-char -Tascii -t -ms -o1- /usr/src/share/doc/smm/01.setup/0.t /usr/src/share/doc/smm/01.setup/1.t /usr/src/share/doc/smm/01.setup/2.t /usr/src/share/doc/smm/01.setup/3.t /usr/src/share/doc/smm/01.setup/4.t /usr/src/share/doc/smm/01.setup/5.t /usr/src/share/doc/smm/01.setup/6.t) | gzip -cn > paper.ascii.gz
/usr/src/share/doc/smm/01.setup/1.t:62: warning: can't find font `CW'
/usr/src/share/doc/smm/01.setup/2.t:1341: warning: can't find font `C'
/usr/src/share/doc/smm/01.setup/2.t:1379: warning: indent cannot be negative
/usr/src/share/doc/smm/01.setup/2.t:1423: warning: indent cannot be negative
/usr/src/share/doc/smm/01.setup/6.t:672: warning: indent cannot be negative
===> share/doc/smm/12.timed
touch _stamp.extraobjs
(cd /usr/src/share/doc/smm/12.timed/../../../../usr.sbin/timed/SMM.doc/timed; groff -mtty-char -Tascii -t -s -ms -o1- /usr/src/share/doc/smm/12.timed/../../../../usr.sbin/timed/SMM.doc/timed/timed.ms) | gzip -cn > paper.ascii.gz
<standard input>:239: macro error: automatically terminating display
<standard input>:251: macro error: DE without DS, ID, CD, LD or BD
<standard input>:308: macro error: automatically terminating display
<standard input>:317: macro error: DE without DS, ID, CD, LD or BD
<standard input>:374: macro error: automatically terminating display
<standard input>:382: macro error: DE without DS, ID, CD, LD or BD
<standard input>:439: macro error: automatically terminating display
<standard input>:446: macro error: DE without DS, ID, CD, LD or BD
<standard input>:503: macro error: automatically terminating display
<standard input>:516: macro error: DE without DS, ID, CD, LD or BD
<standard input>:573: macro error: automatically terminating display
<standard input>:581: macro error: DE without DS, ID, CD, LD or BD
<standard input>:638: macro error: automatically terminating display
<standard input>:646: macro error: DE without DS, ID, CD, LD or BD
<standard input>:703: macro error: automatically terminating display
<standard input>:711: macro error: DE without DS, ID, CD, LD or BD
<standard input>:768: macro error: automatically terminating display
<standard input>:777: macro error: DE without DS, ID, CD, LD or BD
<standard input>:834: macro error: automatically terminating display
<standard input>:843: macro error: DE without DS, ID, CD, LD or BD
<standard input>:900: macro error: automatically terminating display
<standard input>:907: macro error: DE without DS, ID, CD, LD or BD
<standard input>:964: macro error: automatically terminating display
<standard input>:971: macro error: DE without DS, ID, CD, LD or BD
<standard input>:1028: macro error: automatically terminating display
<standard input>:1039: macro error: DE without DS, ID, CD, LD or BD
<standard input>:1096: macro error: automatically terminating display
<standard input>:1105: macro error: DE without DS, ID, CD, LD or BD
<standard input>:1162: macro error: automatically terminating display
<standard input>:1169: macro error: DE without DS, ID, CD, LD or BD
<standard input>:1226: macro error: automatically terminating display
<standard input>:1236: macro error: DE without DS, ID, CD, LD or BD
<standard input>:1293: macro error: automatically terminating display
<standard input>:1301: macro error: DE without DS, ID, CD, LD or BD
<standard input>:1358: macro error: automatically terminating display
<standard input>:1366: macro error: DE without DS, ID, CD, LD or BD
<standard input>:1423: macro error: automatically terminating display
<standard input>:1430: macro error: DE without DS, ID, CD, LD or BD
<standard input>:1487: macro error: automatically terminating display
<standard input>:1496: macro error: DE without DS, ID, CD, LD or BD
<standard input>:1553: macro error: automatically terminating display
<standard input>:1561: macro error: DE without DS, ID, CD, LD or BD
<standard input>:1620: macro error: automatically terminating display
<standard input>:1628: macro error: DE without DS, ID, CD, LD or BD
===> share/doc/usd/04.csh
touch _stamp.extraobjs
(cd /usr/src/share/doc/usd/04.csh/../../../../bin/csh/USD.doc; groff -mtty-char -Tascii -s -ms -o1- /usr/src/share/doc/usd/04.csh/../../../../bin/csh/USD.doc/tabs /usr/src/share/doc/usd/04.csh/../../../../bin/csh/USD.doc/csh.1 /usr/src/share/doc/usd/04.csh/../../../../bin/csh/USD.doc/csh.2 /usr/src/share/doc/usd/04.csh/../../../../bin/csh/USD.doc/csh.3 /usr/src/share/doc/usd/04.csh/../../../../bin/csh/USD.doc/csh.4 /usr/src/share/doc/usd/04.csh/../../../../bin/csh/USD.doc/csh.a /usr/src/share/doc/usd/04.csh/../../../../bin/csh/USD.doc/csh.g) | gzip -cn > paper.ascii.gz
<standard input>:3550: warning: `1.6' not defined
===> share/doc/usd/12.vi/viapwh
touch _stamp.extraobjs
(cd /usr/src/share/doc/usd/12.vi/viapwh/../../../../../contrib/nvi/docs/USD.doc/vitut; groff -mtty-char -Tascii -t -ms -o1- /usr/src/share/doc/usd/12.vi/viapwh/../../../../../contrib/nvi/docs/USD.doc/vitut/vi.apwh.ms) | gzip -cn > viapwh.ascii.gz
/usr/src/share/doc/usd/12.vi/viapwh/../../../../../contrib/nvi/docs/USD.doc/vitut/vi.apwh.ms:42: warning: `CB' not defined
/usr/src/share/doc/usd/12.vi/viapwh/../../../../../contrib/nvi/docs/USD.doc/vitut/vi.apwh.ms:88: warning: `VL' not defined
/usr/src/share/doc/usd/12.vi/viapwh/../../../../../contrib/nvi/docs/USD.doc/vitut/vi.apwh.ms:109: warning: `LE' not defined
===> share/doc/papers/kernmalloc
(cd /usr/src/share/doc/papers/kernmalloc; soelim kernmalloc.t) > kernmalloc.ms
vgrind -f < /usr/src/share/doc/papers/kernmalloc/appendix.t > appendix.ms
touch _stamp.extraobjs
(cd /usr/obj/aout/usr/src/share/doc/papers/kernmalloc; groff -mtty-char -Tascii -e -t -p -ms -o1- kernmalloc.ms appendix.ms) | gzip -cn > kernmalloc.ascii.gz
kernmalloc.ms:66: warning: number register `d' not defined
kernmalloc.ms:407: warning: number register `OI' not defined
appendix.ms:3: warning: only `z' and `u' scale indicators valid in this context
appendix.ms:14: warning: number register `v' not defined
appendix.ms:107: warning: `vS' not defined
appendix.ms:131: warning: number register `x' not defined
appendix.ms:271: warning: `vE' not defined
===> share/doc/papers/memfs
indxbib -c /usr/src/share/doc/papers/memfs/../../../../contrib/groff/indxbib/eign -o ref.bib /usr/src/share/doc/papers/memfs/ref.bib
vgrind -f < /usr/src/share/doc/papers/memfs/A.t > A.gt
refer -n -e -l -s -p /usr/src/share/doc/papers/memfs/ref.bib /usr/src/share/doc/papers/memfs/0.t /usr/src/share/doc/papers/memfs/1.t A.gt > paper.t
touch _stamp.extraobjs
(cd /usr/obj/aout/usr/src/share/doc/papers/memfs; groff -mtty-char -Tascii -ms -o1- /usr/src/share/doc/papers/memfs/tmac.srefs paper.t) | gzip -cn > memfs.ascii.gz
/usr/src/share/doc/papers/memfs/1.t:390: warning: number register `rS' not defined
/usr/src/share/doc/papers/memfs/1.t:390: warning: `Li' not defined
/usr/src/share/doc/papers/memfs/1.t:390: warning: number register `Ns' not defined
/usr/src/share/doc/papers/memfs/1.t:401: warning: `FS' not defined
/usr/src/share/doc/papers/memfs/1.t:401: warning: `[G' not defined
/usr/src/share/doc/papers/memfs/1.t:401: warning: `[O' not defined
/usr/src/share/doc/papers/memfs/1.t:401: warning: `FE' not defined
/usr/src/share/doc/papers/memfs/1.t:413: warning: `[V' not defined
/usr/src/share/doc/papers/memfs/1.t:413: warning: `[N' not defined
/usr/src/share/doc/papers/memfs/1.t:413: warning: `[I' not defined
/usr/src/share/doc/papers/memfs/1.t:413: warning: `[O' not defined
/usr/src/share/doc/papers/memfs/1.t:427: warning: `[I' not defined
/usr/src/share/doc/papers/memfs/1.t:427: warning: `[O' not defined
/usr/src/share/doc/papers/memfs/1.t:441: warning: `[I' not defined
/usr/src/share/doc/papers/memfs/1.t:441: warning: `[O' not defined
A.gt:3: warning: only `z' and `u' scale indicators valid in this context
A.gt:14: warning: number register `v' not defined
A.gt:110: warning: `vS' not defined
A.gt:154: warning: number register `x' not defined
A.gt:351: warning: `vE' not defined
===> sys/i386/boot/cdboot
...
cc -O2 -malign-functions=0 -malign-jumps=0 -malign-loops=0 -mno-486 -DDO_BAD144 -DBOOTWAIT=5000 -DTIMEOUT= -DBOOTSEG=0x1000 -DBOOTSTACK=0xFFF0 -I/usr/src/sys/i386/boot/cdboot/../biosboot -DCDBOOT -Wreturn-type -Wcomment -Wredundant-decls -Wimplicit -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wuninitialized -Wformat -Wunused -fformat-extensions -ansi -DCOMCONSOLE=0x3F8 -DCONSPEED=9600 -aout -nostdinc -I/usr/src/sys/i386/boot/cdboot/../../../../include -I/usr/src/sys/i386/boot/cdboot/../../.. -I/usr/obj/aout
/usr/src/sys/i386/boot/cdboot -I/usr/obj/aout/usr/src/tmp/usr/include -c /usr/src/sys/i386/boot/cdboot/boot.c
/usr/src/sys/i386/boot/cdboot/boot.c: In function `boot':
/usr/src/sys/i386/boot/cdboot/boot.c:118: warning: unused variable `i'
/usr/src/sys/i386/boot/cdboot/boot.c: In function `loadprog':
/usr/src/sys/i386/boot/cdboot/boot.c:256: warning: unsigned int format, long unsigned int arg (arg 2)
/usr/src/sys/i386/boot/cdboot/boot.c:273: warning: unsigned int format, long unsigned int arg (arg 2)
/usr/src/sys/i386/boot/cdboot/boot.c:279: warning: unsigned int format, long unsigned int arg (arg 2)
/usr/src/sys/i386/boot/cdboot/boot.c:303: warning: unsigned int format, long unsigned int arg (arg 4)
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Sun Jan 24 11:11:27 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id LAA06105
for freebsd-current-outgoing; Sun, 24 Jan 1999 11:11:27 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from flood.ping.uio.no (flood.ping.uio.no [129.240.78.31])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA05897
for <freebsd-current@FreeBSD.ORG>; Sun, 24 Jan 1999 11:08:36 -0800 (PST)
(envelope-from des@flood.ping.uio.no)
Received: (from des@localhost)
by flood.ping.uio.no (8.9.1/8.9.1) id UAA55645;
Sun, 24 Jan 1999 20:08:09 +0100 (CET)
(envelope-from des)
To: Boris Staeblow <balu@dva.in-berlin.de>
Cc: dillon@apollo.backplane.com, freebsd-current@FreeBSD.ORG
Subject: Re: Heads up! New swapper and VM changes have been committed to -4.x
References: <19990124130912.A27246@dva.in-berlin.de>
From: Dag-Erling Smorgrav <des@flood.ping.uio.no>
Date: 24 Jan 1999 20:08:08 +0100
In-Reply-To: Boris Staeblow's message of "Sun, 24 Jan 1999 13:09:12 +0100"
Message-ID: <xzpiudwfq07.fsf@flood.ping.uio.no>
Lines: 37
X-Mailer: Gnus v5.5/Emacs 19.34
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
Boris Staeblow <balu@dva.in-berlin.de> writes:
> Beside your suggestions there are much more programs which use
> libkvm:
>
> /bin/ps/
> /libexec/rpc.rstatd/
> /sbin/ccdconfig/
> /sbin/dmesg/
These are statically linked, and must be relinked after libkvm has
been rebuilt.
> /sbin/dset/
This does not exist anymore.
> /usr.bin/fstat/
> /usr.bin/gcore/
> /usr.bin/ipcs/
> /usr.bin/netstat/
> /usr.bin/nfsstat/
> /usr.bin/systat/
> /usr.bin/top/
> /usr.bin/vmstat/
> /usr.bin/w/
> /usr.sbin/iostat/
> /usr.sbin/kernbb/
> /usr.sbin/kgmon/
> /usr.sbin/pstat/
> /usr.sbin/xntpd/xntpd/
These are dynamically linked, and will automatically pick up the new
libkvm.
DES
--
Dag-Erling Smorgrav - des@flood.ping.uio.no
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Sun Jan 24 11:52:36 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id LAA10486
for freebsd-current-outgoing; Sun, 24 Jan 1999 11:52:36 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from roma.coe.ufrj.br (roma.coe.ufrj.br [146.164.53.65])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA10479
for <current@FreeBSD.ORG>; Sun, 24 Jan 1999 11:52:34 -0800 (PST)
(envelope-from jonny@jonny.eng.br)
Received: (from jonny@localhost)
by roma.coe.ufrj.br (8.8.8/8.8.8) id RAA24088;
Sun, 24 Jan 1999 17:52:03 -0200 (EDT)
(envelope-from jonny)
From: Joao Carlos Mendes Luis <jonny@jonny.eng.br>
Message-Id: <199901241952.RAA24088@roma.coe.ufrj.br>
Subject: Re: Death to LKM screen savers? (was: Re: HEADS UP: i386 a.out LKM support now an option..)
In-Reply-To: <Pine.BSF.4.05.9901240016530.55154-100000@bright.fx.genx.net> from Alfred Perlstein at "Jan 24, 1999 0:19:18 am"
To: bright@hotjobs.com (Alfred Perlstein)
Date: Sun, 24 Jan 1999 17:52:03 -0200 (EDT)
Cc: jdp@polstra.com, des@flood.ping.uio.no, current@FreeBSD.ORG
X-Mailer: ELM [version 2.4ME+ PL43 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
#define quoting(Alfred Perlstein)
// cvs up (not cvsup) takes me a LONG time to execute, i've been using '-z3'
// for comppression because i'm on dialup, is this ok with you guys? (it
// doesn't help much though...)
//
// cvs -z3 up -Pd src
//
// i'm also using ssh for transport as rlogin doesn't work well for me.
If you are using ssh, why use -z3 ? ssh does already compress the
channel, doesn't it ?
Jonny
--
Joao Carlos Mendes Luis M.Sc. Student
jonny@jonny.eng.br Universidade Federal do Rio de Janeiro
"This .sig is not meant to be politically correct."
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Sun Jan 24 12:02:02 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id MAA11387
for freebsd-current-outgoing; Sun, 24 Jan 1999 12:02:02 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from ayukawa.aus.org (ayukawa.aus.org [199.166.246.1])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA11354
for <current@freebsd.org>; Sun, 24 Jan 1999 12:01:58 -0800 (PST)
(envelope-from lh@aus.org)
Received: from zer0.net (lh@zer0.net [199.166.246.189]) by ayukawa.aus.org (8.8.7/8.7.3) with ESMTP id OAA26652 for <current@freebsd.org>; Sun, 24 Jan 1999 14:42:35 -0500 (EST)
Message-Id: <199901241942.OAA26652@ayukawa.aus.org>
X-Mailer: XFMail 1.3-beta-042198 [p0] on FreeBSD
X-Priority: 3 (Normal)
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 8bit
MIME-Version: 1.0
Date: Sun, 24 Jan 1999 15:01:38 -0500 (EST)
Reply-To: lh@aus.org
From: Luke <lh@aus.org>
To: current@FreeBSD.ORG
Subject: 4.0-Current, netscape halts system
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
I built 4.0 and after getting over the libcrypt thing it worked ok.
But now every copy of netscape I have [5, all freebsd]
freezes the system, waiting, switching to ttyv* dont help. and it doesnt dump
core or syslog anything. Im not exactly sure what info would be helpful.
Anyways other than netscape it works great
---
E-Mail: Luke <lh@aus.org>
Sent by XFMail
----------------------------------
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Sun Jan 24 12:11:23 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id MAA12519
for freebsd-current-outgoing; Sun, 24 Jan 1999 12:11:23 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from hawaii.conterra.com (hawaii.conterra.com [209.12.164.32])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA12504;
Sun, 24 Jan 1999 12:11:19 -0800 (PST)
(envelope-from myself@conterra.com)
Received: from dmaddox.conterra.com (dmaddox.conterra.com [209.12.169.48])
by hawaii.conterra.com (8.8.8/8.8.7) with ESMTP id PAA27327;
Sun, 24 Jan 1999 15:11:06 -0500 (EST)
Received: (from root@localhost)
by dmaddox.conterra.com (8.9.2/8.9.1) id PAA00736;
Sun, 24 Jan 1999 15:11:05 -0500 (EST)
(envelope-from myself)
Date: Sun, 24 Jan 1999 15:11:04 -0500
From: "Donald J . Maddox" <dmaddox@conterra.com>
To: Stingray <chrisd@bsdbox.dynip.com>
Cc: questions@FreeBSD.ORG, current@FreeBSD.ORG
Subject: Re: Problems with 4.0-current
Message-ID: <19990124151104.A721@dmaddox.conterra.com>
Reply-To: dmaddox@conterra.com
References: <Pine.BSF.3.96.990124134230.23619A-100000@bsdbox.dynip.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.95.1i
In-Reply-To: <Pine.BSF.3.96.990124134230.23619A-100000@bsdbox.dynip.com>; from Stingray on Sun, Jan 24, 1999 at 01:47:25PM -0600
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
On Sun, Jan 24, 1999 at 01:47:25PM -0600, Stingray wrote:
> I just CVSup'd 4.0-current and installed it, then made an elf kernel.
> The elf kernel seemed to boot up just fine, but when the file systems
> where being mounted, it couldn't mount /:
>
> Specified device does not match mounted device.
>
> I believe this was the error message. Does anyone know what it means?
I am seeing the same problem... It works if you use the old-style names,
e.g. wd0a instead of wd0s1a. Not sure yet what's causing this...
(CC'ed to -current)
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Sun Jan 24 12:46:36 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id MAA16763
for freebsd-current-outgoing; Sun, 24 Jan 1999 12:46:36 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from khavrinen.lcs.mit.edu (khavrinen.lcs.mit.edu [18.24.4.193])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA16758
for <current@FreeBSD.ORG>; Sun, 24 Jan 1999 12:46:35 -0800 (PST)
(envelope-from wollman@khavrinen.lcs.mit.edu)
Received: (from wollman@localhost)
by khavrinen.lcs.mit.edu (8.9.1/8.9.1) id PAA16931;
Sun, 24 Jan 1999 15:46:18 -0500 (EST)
(envelope-from wollman)
Date: Sun, 24 Jan 1999 15:46:18 -0500 (EST)
From: Garrett Wollman <wollman@khavrinen.lcs.mit.edu>
Message-Id: <199901242046.PAA16931@khavrinen.lcs.mit.edu>
To: Archie Cobbs <archie@whistle.com>
Cc: current@FreeBSD.ORG
Subject: kvm question
In-Reply-To: <199901230748.XAA14754@bubba.whistle.com>
References: <199901230748.XAA14754@bubba.whistle.com>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
<<On Fri, 22 Jan 1999 23:48:50 -0800 (PST), Archie Cobbs <archie@whistle.com> said:
> I ran into an interesting problem in the process of modifying
> "netstat" to understand the PF_NETGRAPH protocol family. "netstat"
> uses kvm_read(), etc. to read kernel symbols. However, this doesn't
Don't do that. Use sysctl, that's what it's there for.
-GAWollman
--
Garrett A. Wollman | O Siem / We are all family / O Siem / We're all the same
wollman@lcs.mit.edu | O Siem / The fires of freedom
Opinions not those of| Dance in the burning flame
MIT, LCS, CRS, or NSA| - Susan Aglukark and Chad Irschick
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Sun Jan 24 12:50:49 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id MAA17084
for freebsd-current-outgoing; Sun, 24 Jan 1999 12:50:49 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from labinfo.iet.unipi.it (labinfo.iet.unipi.it [131.114.9.5])
by hub.freebsd.org (8.8.8/8.8.8) with SMTP id MAA17079
for <freebsd-current@FreeBSD.ORG>; Sun, 24 Jan 1999 12:50:47 -0800 (PST)
(envelope-from luigi@labinfo.iet.unipi.it)
Received: from localhost (luigi@localhost) by labinfo.iet.unipi.it (8.6.5/8.6.5) id TAA24382; Sun, 24 Jan 1999 19:39:04 +0100
From: Luigi Rizzo <luigi@labinfo.iet.unipi.it>
Message-Id: <199901241839.TAA24382@labinfo.iet.unipi.it>
Subject: Re: one other small prob with pcm0
To: culverk@wam.umd.edu (Kenneth Wayne Culver)
Date: Sun, 24 Jan 1999 19:39:04 +0100 (MET)
Cc: freebsd-current@FreeBSD.ORG
In-Reply-To: <Pine.GSO.3.95q.990124123535.9252A-100000@rac2.wam.umd.edu> from "Kenneth Wayne Culver" at Jan 24, 99 12:38:35 pm
X-Mailer: ELM [version 2.4 PL23]
Content-Type: text
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
> This is a trivial problem, but I just thought I'd let someone know about
> it. (cosmetic) Take a look at my dmesg output:
...
> Probing for PnP devices:
...
> pcm1 (SB16pnp <Vibra16X> sn 0xffffffff) at 0x220-0x22f irq 5 drq 1 flags
> 0x13 on isa
> Probing for devices on the ISA bus:
...
> pcm0 not found
if you mean we should not report devices not found unless booting in
verbose mode, i think other drivers do that as well. If you mean that
you'd like to have the card detected as unit #0, i am afraid that is
not possible because we do attach immediately after probes.
cheers
luigi
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Sun Jan 24 12:54:04 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id MAA17446
for freebsd-current-outgoing; Sun, 24 Jan 1999 12:53:42 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA17441
for <current@FreeBSD.ORG>; Sun, 24 Jan 1999 12:53:41 -0800 (PST)
(envelope-from julian@whistle.com)
Received: (from daemon@localhost)
by alpo.whistle.com (8.8.5/8.8.5) id MAA19347;
Sun, 24 Jan 1999 12:52:37 -0800 (PST)
Received: from s204m82.isp.whistle.com(207.76.204.82)
via SMTP by alpo.whistle.com, id smtpds19345; Sun Jan 24 20:52:34 1999
Date: Sun, 24 Jan 1999 12:52:30 -0800 (PST)
From: Julian Elischer <julian@whistle.com>
X-Sender: julian@s204m82.isp.whistle.com
To: Garrett Wollman <wollman@khavrinen.lcs.mit.edu>
cc: Archie Cobbs <archie@whistle.com>, current@FreeBSD.ORG
Subject: Re: kvm question
In-Reply-To: <199901242046.PAA16931@khavrinen.lcs.mit.edu>
Message-ID: <Pine.BSF.4.05.9901241251480.21631-100000@s204m82.isp.whistle.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
As soon as someone modifies sysctl to work with KLD modules....
that would be a reasonable suggestion
On Sun, 24 Jan 1999, Garrett Wollman wrote:
> <<On Fri, 22 Jan 1999 23:48:50 -0800 (PST), Archie Cobbs <archie@whistle.com> said:
>
> > I ran into an interesting problem in the process of modifying
> > "netstat" to understand the PF_NETGRAPH protocol family. "netstat"
> > uses kvm_read(), etc. to read kernel symbols. However, this doesn't
>
> Don't do that. Use sysctl, that's what it's there for.
>
> -GAWollman
>
> --
> Garrett A. Wollman | O Siem / We are all family / O Siem / We're all the same
> wollman@lcs.mit.edu | O Siem / The fires of freedom
> Opinions not those of| Dance in the burning flame
> MIT, LCS, CRS, or NSA| - Susan Aglukark and Chad Irschick
>
> To Unsubscribe: send mail to majordomo@FreeBSD.org
> with "unsubscribe freebsd-current" in the body of the message
>
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Sun Jan 24 12:55:58 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id MAA17821
for freebsd-current-outgoing; Sun, 24 Jan 1999 12:55:58 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from drama.navinet.net (drama.navinet.net [206.25.93.8])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA17805
for <current@freebsd.org>; Sun, 24 Jan 1999 12:55:56 -0800 (PST)
(envelope-from forrie@drama.navinet.net)
Received: (from root@localhost)
by drama.navinet.net (8.9.2/8.9.2) id PAA05256;
Sun, 24 Jan 1999 15:55:32 -0500 (EST)
Date: Sun, 24 Jan 1999 15:55:32 -0500
From: Baby Jane Hudson <root@drama.navinet.net>
To: Luke <lh@aus.org>
Cc: current@FreeBSD.ORG
Subject: Re: 4.0-Current, netscape halts system
Message-ID: <19990124155532.A3764@drama.navinet.net>
References: <199901241942.OAA26652@ayukawa.aus.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.95.1i
In-Reply-To: <199901241942.OAA26652@ayukawa.aus.org>; from Luke on Sun, Jan 24, 1999 at 03:01:38PM -0500
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
I've given up on Netscape. On some FreeBSD-based machines
I have, it just core dumps... on others it works. Nobody
seems to know (or care) why, so I would suggest following
the development of Gzilla and Amaya.
Of course, it would be immensely helpful if we knew what
mysterious person within netscape provided the port to
begin with (Hey, now there's a great idea) so we might ask
some questions. But, that's what you get for free...
On Sun, Jan 24, 1999 at 03:01:38PM -0500, Luke wrote:
> I built 4.0 and after getting over the libcrypt thing it worked ok.
> But now every copy of netscape I have [5, all freebsd]
> freezes the system, waiting, switching to ttyv* dont help. and it doesnt dump
> core or syslog anything. Im not exactly sure what info would be helpful.
> Anyways other than netscape it works great
>
> ---
>
> E-Mail: Luke <lh@aus.org>
> Sent by XFMail
> ----------------------------------
>
> To Unsubscribe: send mail to majordomo@FreeBSD.org
> with "unsubscribe freebsd-current" in the body of the message
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Sun Jan 24 13:10:46 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id NAA19406
for freebsd-current-outgoing; Sun, 24 Jan 1999 13:10:46 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from khavrinen.lcs.mit.edu (khavrinen.lcs.mit.edu [18.24.4.193])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA19392
for <current@FreeBSD.ORG>; Sun, 24 Jan 1999 13:10:44 -0800 (PST)
(envelope-from wollman@khavrinen.lcs.mit.edu)
Received: (from wollman@localhost)
by khavrinen.lcs.mit.edu (8.9.1/8.9.1) id QAA17006;
Sun, 24 Jan 1999 16:10:30 -0500 (EST)
(envelope-from wollman)
Date: Sun, 24 Jan 1999 16:10:30 -0500 (EST)
From: Garrett Wollman <wollman@khavrinen.lcs.mit.edu>
Message-Id: <199901242110.QAA17006@khavrinen.lcs.mit.edu>
To: Archie Cobbs <archie@whistle.com>
Cc: mike@smith.net.au (Mike Smith), current@FreeBSD.ORG
Subject: Re: kvm question
In-Reply-To: <199901231904.LAA18363@bubba.whistle.com>
References: <199901231658.IAA00639@dingo.cdrom.com>
<199901231904.LAA18363@bubba.whistle.com>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
<<On Sat, 23 Jan 1999 11:04:15 -0800 (PST), Archie Cobbs <archie@whistle.com> said:
> Peter pointed out that having the sysctl's as symbols was a nice
> advantage of the current system. How important is this?
I don't think it's important at all. (Then again, I liked the old
system.)
> If we were willing to give this up, then the SYSCTL() macro could
> just expand to a SYSINIT() that called sysctl_add_subtree() (or
> whatever you want to call it) upon loading.
Seems reasonable to me. The only problem with this is likely to be
OID_AUTO, which I happen to think is bogus anyway. It is vital that
we maintain the ability to reference sysctl entities by compile-time
constant integers, so as not to break backwards compatibility with
other 4.4 systems and the Stevens books.
-GAWollman
--
Garrett A. Wollman | O Siem / We are all family / O Siem / We're all the same
wollman@lcs.mit.edu | O Siem / The fires of freedom
Opinions not those of| Dance in the burning flame
MIT, LCS, CRS, or NSA| - Susan Aglukark and Chad Irschick
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Sun Jan 24 13:14:47 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id NAA19921
for freebsd-current-outgoing; Sun, 24 Jan 1999 13:14:47 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from po3.wam.umd.edu (po3.wam.umd.edu [128.8.10.165])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA19912
for <current@FreeBSD.ORG>; Sun, 24 Jan 1999 13:14:45 -0800 (PST)
(envelope-from culverk@wam.umd.edu)
Received: from rac9.wam.umd.edu ((IDENT root)@rac9.wam.umd.edu [128.8.10.149])
by po3.wam.umd.edu (8.9.0.Beta6/8.9.0.Beta6) with ESMTP id QAA24911;
Sun, 24 Jan 1999 16:14:22 -0500 (EST)
Received: from rac9.wam.umd.edu ((IDENT sendmail)@localhost [127.0.0.1])
by rac9.wam.umd.edu (8.9.0.Beta6/8.9.0.Beta6) with SMTP id QAA20736;
Sun, 24 Jan 1999 16:14:20 -0500 (EST)
Received: from localhost by rac9.wam.umd.edu (8.9.0.Beta6/8.9.0.Beta6) with SMTP id QAA20724;
Sun, 24 Jan 1999 16:14:18 -0500 (EST)
X-Authentication-Warning: rac9.wam.umd.edu: culverk owned process doing -bs
Date: Sun, 24 Jan 1999 16:14:18 -0500 (EST)
From: Kenneth Wayne Culver <culverk@wam.umd.edu>
To: Baby Jane Hudson <root@drama.navinet.net>
cc: Luke <lh@aus.org>, current@FreeBSD.ORG
Subject: Re: 4.0-Current, netscape halts system
In-Reply-To: <19990124155532.A3764@drama.navinet.net>
Message-ID: <Pine.GSO.3.95q.990124161349.20566A-100000@rac9.wam.umd.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
> I've given up on Netscape. On some FreeBSD-based machines
> I have, it just core dumps... on others it works. Nobody
> seems to know (or care) why, so I would suggest following
> the development of Gzilla and Amaya.
>
> Of course, it would be immensely helpful if we knew what
> mysterious person within netscape provided the port to
> begin with (Hey, now there's a great idea) so we might ask
> some questions. But, that's what you get for free...
>
>
If you are having a problem with Netscape for FreeBSD, then just try the
Linux version.
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Sun Jan 24 13:15:11 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id NAA20159
for freebsd-current-outgoing; Sun, 24 Jan 1999 13:15:11 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from dingo.cdrom.com (castles340.castles.com [208.214.167.40])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA20154
for <current@FreeBSD.ORG>; Sun, 24 Jan 1999 13:15:09 -0800 (PST)
(envelope-from mike@dingo.cdrom.com)
Received: from dingo.cdrom.com (LOCALHOST [127.0.0.1])
by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id NAA05078;
Sun, 24 Jan 1999 13:11:13 -0800 (PST)
(envelope-from mike@dingo.cdrom.com)
Message-Id: <199901242111.NAA05078@dingo.cdrom.com>
X-Mailer: exmh version 2.0.2 2/24/98
To: Garrett Wollman <wollman@khavrinen.lcs.mit.edu>
cc: Archie Cobbs <archie@whistle.com>, mike@smith.net.au (Mike Smith),
current@FreeBSD.ORG
Subject: Re: kvm question
In-reply-to: Your message of "Sun, 24 Jan 1999 16:10:30 EST."
<199901242110.QAA17006@khavrinen.lcs.mit.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Sun, 24 Jan 1999 13:11:12 -0800
From: Mike Smith <mike@smith.net.au>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
> <<On Sat, 23 Jan 1999 11:04:15 -0800 (PST), Archie Cobbs <archie@whistle.com> said:
>
> > Peter pointed out that having the sysctl's as symbols was a nice
> > advantage of the current system. How important is this?
>
> I don't think it's important at all. (Then again, I liked the old
> system.)
>
> > If we were willing to give this up, then the SYSCTL() macro could
> > just expand to a SYSINIT() that called sysctl_add_subtree() (or
> > whatever you want to call it) upon loading.
>
> Seems reasonable to me. The only problem with this is likely to be
> OID_AUTO, which I happen to think is bogus anyway. It is vital that
> we maintain the ability to reference sysctl entities by compile-time
> constant integers, so as not to break backwards compatibility with
> other 4.4 systems and the Stevens books.
Backwards compatibility is one thing, but new nodes should be named,
not numbered. OID_AUTO is bogus because it perpetuates the numbering
of nodes.
--
\\ Sometimes you're ahead, \\ Mike Smith
\\ sometimes you're behind. \\ mike@smith.net.au
\\ The race is long, and in the \\ msmith@freebsd.org
\\ end it's only with yourself. \\ msmith@cdrom.com
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Sun Jan 24 13:31:31 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id NAA21942
for freebsd-current-outgoing; Sun, 24 Jan 1999 13:31:31 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from whistle.com (s205m131.whistle.com [207.76.205.131])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA21937
for <current@FreeBSD.ORG>; Sun, 24 Jan 1999 13:31:30 -0800 (PST)
(envelope-from archie@whistle.com)
Received: (from smap@localhost) by whistle.com (8.7.5/8.6.12) id NAA01138; Sun, 24 Jan 1999 13:30:40 -0800 (PST)
Received: from bubba.whistle.com( 207.76.205.7) by whistle.com via smap (V2.0)
id xma001132; Sun, 24 Jan 99 13:30:38 -0800
Received: (from archie@localhost) by bubba.whistle.com (8.8.7/8.6.12) id NAA21377; Sun, 24 Jan 1999 13:30:37 -0800 (PST)
From: Archie Cobbs <archie@whistle.com>
Message-Id: <199901242130.NAA21377@bubba.whistle.com>
Subject: Re: kvm question
In-Reply-To: <Pine.BSF.4.05.9901241251480.21631-100000@s204m82.isp.whistle.com> from Julian Elischer at "Jan 24, 99 12:52:30 pm"
To: julian@whistle.com (Julian Elischer)
Date: Sun, 24 Jan 1999 13:30:37 -0800 (PST)
Cc: wollman@khavrinen.lcs.mit.edu, current@FreeBSD.ORG
X-Mailer: ELM [version 2.4ME+ PL38 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
Julian Elischer writes:
> As soon as someone modifies sysctl to work with KLD modules....
> that would be a reasonable suggestion
>
> On Sun, 24 Jan 1999, Garrett Wollman wrote:
> > > I ran into an interesting problem in the process of modifying
> > > "netstat" to understand the PF_NETGRAPH protocol family. "netstat"
> > > uses kvm_read(), etc. to read kernel symbols. However, this doesn't
> >
> > Don't do that. Use sysctl, that's what it's there for.
> >
> > -GAWollman
Julian is of course correct... but Garrett you missed my point...
Forget netstat for a second. The question is simply, "I'm offering
to fix libkvm to understand KLD modules; is anybody interested?"
Whether libkvm should even exist in a perfect world (it shouldn't)
is an entirely different question. For now, we're stuck with it
until somebody changes *everything* to use sysctl instead.
-Archie
___________________________________________________________________________
Archie Cobbs * Whistle Communications, Inc. * http://www.whistle.com
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Sun Jan 24 13:51:09 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id NAA23018
for freebsd-current-outgoing; Sun, 24 Jan 1999 13:51:09 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from spinner.netplex.com.au (spinner.netplex.com.au [202.12.86.3])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA23012
for <current@FreeBSD.ORG>; Sun, 24 Jan 1999 13:51:04 -0800 (PST)
(envelope-from peter@netplex.com.au)
Received: from spinner.netplex.com.au (localhost [127.0.0.1])
by spinner.netplex.com.au (8.9.2/8.9.2/Netplex) with ESMTP id FAA03656;
Mon, 25 Jan 1999 05:50:32 +0800 (WST)
(envelope-from peter@spinner.netplex.com.au)
Message-Id: <199901242150.FAA03656@spinner.netplex.com.au>
X-Mailer: exmh version 2.0.2 2/24/98
To: Archie Cobbs <archie@whistle.com>
cc: julian@whistle.com (Julian Elischer), wollman@khavrinen.lcs.mit.edu,
current@FreeBSD.ORG
Subject: Re: kvm question
In-reply-to: Your message of "Sun, 24 Jan 1999 13:30:37 PST."
<199901242130.NAA21377@bubba.whistle.com>
Date: Mon, 25 Jan 1999 05:50:32 +0800
From: Peter Wemm <peter@netplex.com.au>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
Archie Cobbs wrote:
> Julian Elischer writes:
> > As soon as someone modifies sysctl to work with KLD modules....
> > that would be a reasonable suggestion
> >
> > On Sun, 24 Jan 1999, Garrett Wollman wrote:
> > > > I ran into an interesting problem in the process of modifying
> > > > "netstat" to understand the PF_NETGRAPH protocol family. "netstat"
> > > > uses kvm_read(), etc. to read kernel symbols. However, this doesn't
> > >
> > > Don't do that. Use sysctl, that's what it's there for.
> > >
> > > -GAWollman
>
> Julian is of course correct... but Garrett you missed my point...
>
> Forget netstat for a second. The question is simply, "I'm offering
> to fix libkvm to understand KLD modules; is anybody interested?"
>
> Whether libkvm should even exist in a perfect world (it shouldn't)
> is an entirely different question. For now, we're stuck with it
> until somebody changes *everything* to use sysctl instead.
The correct fix, BTW, is to dump kvm_mkdb and have kvm_nlist() get it's
data from the kernel, either via kldsym() or via a sysctl mechanism (which
a lot of people have suggested, but nobody has shown the slightest
interest in suggesting how this could/should be done).
> -Archie
Cheers,
-Peter
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Sun Jan 24 14:01:33 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id OAA23785
for freebsd-current-outgoing; Sun, 24 Jan 1999 14:01:33 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from khavrinen.lcs.mit.edu (khavrinen.lcs.mit.edu [18.24.4.193])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA23780
for <current@FreeBSD.ORG>; Sun, 24 Jan 1999 14:01:30 -0800 (PST)
(envelope-from wollman@khavrinen.lcs.mit.edu)
Received: (from wollman@localhost)
by khavrinen.lcs.mit.edu (8.9.1/8.9.1) id RAA17112;
Sun, 24 Jan 1999 17:01:11 -0500 (EST)
(envelope-from wollman)
Date: Sun, 24 Jan 1999 17:01:11 -0500 (EST)
From: Garrett Wollman <wollman@khavrinen.lcs.mit.edu>
Message-Id: <199901242201.RAA17112@khavrinen.lcs.mit.edu>
To: Mike Smith <mike@smith.net.au>
Cc: current@FreeBSD.ORG
Subject: sysctl oids (was: Re: kvm question)
In-Reply-To: <199901242111.NAA05078@dingo.cdrom.com>
References: <199901242110.QAA17006@khavrinen.lcs.mit.edu>
<199901242111.NAA05078@dingo.cdrom.com>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
<<On Sun, 24 Jan 1999 13:11:12 -0800, Mike Smith <mike@smith.net.au> said:
> Backwards compatibility is one thing, but new nodes should be named,
> not numbered. OID_AUTO is bogus because it perpetuates the numbering
> of nodes.
Nonsense. There are plenty of contexts in which a number makes far
more sense than a name -- pretty much anything in any network stack
other than Chaosnet, for example. If any of us ever make good on the
threat of SNMP integration, having fixed numerical identifiers will be
a requirement.
-GAWollman
--
Garrett A. Wollman | O Siem / We are all family / O Siem / We're all the same
wollman@lcs.mit.edu | O Siem / The fires of freedom
Opinions not those of| Dance in the burning flame
MIT, LCS, CRS, or NSA| - Susan Aglukark and Chad Irschick
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Sun Jan 24 14:10:45 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id OAA24532
for freebsd-current-outgoing; Sun, 24 Jan 1999 14:10:45 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from rip.psg.com (rip.psg.com [147.28.0.39])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA24527
for <freebsd-current@FreeBSD.ORG>; Sun, 24 Jan 1999 14:10:44 -0800 (PST)
(envelope-from randy@psg.com)
Received: from localhost (3160 bytes) by rip.psg.com
via sendmail with P:stdio/R:inet_resolve/T:smtp
(sender: <randy>) (ident <randy> using unix)
id <m104Xjk-0008G5C@rip.psg.com>
for <freebsd-current@FreeBSD.ORG>; Sun, 24 Jan 1999 14:10:32 -0800 (PST)
(Smail-3.2.0.101 1997-Dec-17 #1 built 1998-Oct-13)
Message-Id: <m104Xjk-0008G5C@rip.psg.com>
Date: Sun, 24 Jan 1999 14:10:32 -0800 (PST)
From: Randy Bush <randy@psg.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
To: Mark Murray <mark@grondar.za>
Cc: freebsd-current@FreeBSD.ORG
Subject: Re: make aout-to-elf-build failure
References: <m1047WH-0008G4C@rip.psg.com>
<199901231907.LAA16027@vashon.polstra.com>
<m104A3n-0008G4C@rip.psg.com>
<199901240817.KAA02681@greenpeace.grondar.za>
<m104NL6-0008G4C@rip.psg.com>
<199901241119.NAA03526@greenpeace.grondar.za>
<m104RJR-0008G4C@rip.psg.com>
<199901241537.RAA16096@greenpeace.grondar.za>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
>> /usr/obj/aout/usr/src/tmp/usr/libexec/elf/ld: warning: libcrypt.so.2, needed by /usr/obj/elf/usr/src/kerberosIV/libexec/kipd/../../lib/libkrb/libkrb.so, not found (try using --rpath)
>> /usr/obj/elf/usr/src/kerberosIV/libexec/kipd/../../lib/libkrb/libkrb.so: undefined reference to `crypt'
>> *** Error code 1
> Go to the right subdirectory (in this case
> /usr/src/kerberosIV/libexec/kipd/) and edit the Makefile; add
> -lcrypt to the end of the LDADD line. You may need to remove it
> later, but it will keep your build going. I'd be grateful for
> reports of places where this is necesary.
-DNOCLEAN is cool, but helps less with aout-to-elf-build elf stage compiles
than one might wish. well, i am whining. it cuts 110 minutes to 5. but
clearly i am missing an obvious shortcut here.
/usr/obj/elf/usr/src/kerberosIV/libexec/kipd/../../lib/libkrb/libkrb.so: undefined reference to `crypt'
/usr/obj/elf/usr/src/kerberosIV/libexec/kpropd/../../lib/libkrb/libkrb.so: undefined reference to `crypt'
/usr/obj/elf/usr/src/kerberosIV/libexec/telnetd/../../lib/libkrb/libkrb.so: undefined reference to `crypt'
/usr/obj/elf/usr/src/kerberosIV/usr.bin/kdestroy/../../lib/libkrb/libkrb.so: undefined reference to `crypt'
/usr/obj/elf/usr/src/kerberosIV/usr.bin/klist/../../lib/libkrb/libkrb.so: undefined reference to `crypt'
/usr/obj/elf/usr/src/kerberosIV/usr.bin/telnet/../../lib/libkrb/libkrb.so: undefined reference to `crypt'
/usr/obj/elf/usr/src/kerberosIV/usr.sbin/ext_srvtab/../../lib/libkrb/libkrb.so: undefined reference to `crypt'
/usr/obj/elf/usr/src/kerberosIV/usr.sbin/kadmind/../../lib/libkrb/libkrb.so: undefined reference to `crypt'
/usr/obj/elf/usr/src/kerberosIV/usr.sbin/kdb_destroy/../../lib/libkrb/libkrb.so: undefined reference to `crypt'
/usr/obj/elf/usr/src/kerberosIV/usr.sbin/kdb_edit/../../lib/libkrb/libkrb.so: undefined reference to `crypt'
/usr/obj/elf/usr/src/kerberosIV/usr.sbin/kdb_init/../../lib/libkrb/libkrb.so: undefined reference to `crypt'
/usr/obj/elf/usr/src/kerberosIV/usr.sbin/kdb_util/../../lib/libkrb/libkrb.so: undefined reference to `crypt'
/usr/obj/elf/usr/src/kerberosIV/usr.sbin/kerberos/../../lib/libkrb/libkrb.so: undefined reference to `crypt'
/usr/obj/elf/usr/src/kerberosIV/usr.sbin/kip/../../lib/libkrb/libkrb.so: undefined reference to `crypt'
/usr/obj/elf/usr/src/kerberosIV/usr.sbin/kprop/../../lib/libkrb/libkrb.so: undefined reference to `crypt'
/usr/obj/elf/usr/src/kerberosIV/usr.sbin/kstash/../../lib/libkrb/libkrb.so: undefined reference to `crypt'
randy
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Sun Jan 24 14:23:44 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id OAA25752
for freebsd-current-outgoing; Sun, 24 Jan 1999 14:23:44 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA25747
for <current@FreeBSD.ORG>; Sun, 24 Jan 1999 14:23:43 -0800 (PST)
(envelope-from julian@whistle.com)
Received: (from daemon@localhost)
by alpo.whistle.com (8.8.5/8.8.5) id OAA20827;
Sun, 24 Jan 1999 14:15:18 -0800 (PST)
Received: from current1.whistle.com(207.76.205.22)
via SMTP by alpo.whistle.com, id smtpdu20820; Sun Jan 24 22:15:13 1999
Date: Sun, 24 Jan 1999 14:15:08 -0800 (PST)
From: Julian Elischer <julian@whistle.com>
To: Garrett Wollman <wollman@khavrinen.lcs.mit.edu>
cc: Mike Smith <mike@smith.net.au>, current@FreeBSD.ORG
Subject: Re: sysctl oids (was: Re: kvm question)
In-Reply-To: <199901242201.RAA17112@khavrinen.lcs.mit.edu>
Message-ID: <Pine.BSF.3.95.990124140935.6880C-100000@current1.whistle.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
yeah and we should get those nice valves that used to make radios so
useful as space-heaters.
On Sun, 24 Jan 1999, Garrett Wollman wrote:
> <<On Sun, 24 Jan 1999 13:11:12 -0800, Mike Smith <mike@smith.net.au> said:
>
> > Backwards compatibility is one thing, but new nodes should be named,
> > not numbered. OID_AUTO is bogus because it perpetuates the numbering
> > of nodes.
>
> Nonsense. There are plenty of contexts in which a number makes far
> more sense than a name -- pretty much anything in any network stack
> other than Chaosnet, for example. If any of us ever make good on the
> threat of SNMP integration, having fixed numerical identifiers will be
> a requirement.
SNMP will require a translation layer anyhow..
numbers cannot and should not be used. They are not easily
maintained in the face of multiple external modules being dynamically
loadable.
That is at least my opinion.. you may and do disagree. I guess you will
say that numbers are just as dynamic, etc.etc. well I just think that in
the REAL WORLD, as opposed to the theoretical world, names (which require
no co-ordination between authors), are a better choice than numbers,
which require some central naming authority.
>
> -GAWollman
>
> --
> Garrett A. Wollman | O Siem / We are all family / O Siem / We're all the same
> wollman@lcs.mit.edu | O Siem / The fires of freedom
> Opinions not those of| Dance in the burning flame
> MIT, LCS, CRS, or NSA| - Susan Aglukark and Chad Irschick
>
> To Unsubscribe: send mail to majordomo@FreeBSD.org
> with "unsubscribe freebsd-current" in the body of the message
>
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Sun Jan 24 14:29:42 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id OAA26527
for freebsd-current-outgoing; Sun, 24 Jan 1999 14:29:42 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from polaris.we.lc.ehu.es (polaris.we.lc.ehu.es [158.227.6.43])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA26514
for <freebsd-current@FreeBSD.ORG>; Sun, 24 Jan 1999 14:29:39 -0800 (PST)
(envelope-from jose@we.lc.ehu.es)
Received: from we.lc.ehu.es (lxpx79.lx.ehu.es [158.227.99.79])
by polaris.we.lc.ehu.es (8.9.1/8.9.1) with ESMTP id XAA06629;
Sun, 24 Jan 1999 23:29:13 +0100 (MET)
Message-ID: <36AB9EB8.6B0E8755@we.lc.ehu.es>
Date: Sun, 24 Jan 1999 23:29:12 +0100
From: "José Mª Alcaide" <jose@we.lc.ehu.es>
Organization: Universidad del País Vasco - Dept. Electricidad y Electrónica
X-Mailer: Mozilla 4.07 [en] (X11; U; FreeBSD 3.0-STABLE i386)
MIME-Version: 1.0
To: Luigi Rizzo <luigi@labinfo.iet.unipi.it>
CC: Kenneth Wayne Culver <culverk@wam.umd.edu>, freebsd-current@FreeBSD.ORG
Subject: Re: one other small prob with pcm0
References: <199901241839.TAA24382@labinfo.iet.unipi.it>
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
Luigi Rizzo wrote:
>
> > This is a trivial problem, but I just thought I'd let someone know about
> > it. (cosmetic) Take a look at my dmesg output:
> ...
> > Probing for PnP devices:
> ...
> > pcm1 (SB16pnp <Vibra16X> sn 0xffffffff) at 0x220-0x22f irq 5 drq 1 flags
> > 0x13 on isa
> > Probing for devices on the ISA bus:
> ...
> > pcm0 not found
>
> if you mean we should not report devices not found unless booting in
> verbose mode, i think other drivers do that as well. If you mean that
> you'd like to have the card detected as unit #0, i am afraid that is
> not possible because we do attach immediately after probes.
>
I have found out how to avoid the "pcm0 not probed due to drq conflict..."
message. Simply, disable the pcm driver (in your kernel config file,
or booting with the -c option). If the pcm driver is present in the
kernel, even if it is disabled, the PnP code attachs the sound cards
to it.
-- JMA
-----------------------------------------------------------------------
José Mª Alcaide | mailto:jose@we.lc.ehu.es
Universidad del País Vasco | http://www.we.lc.ehu.es/~jose
Dpto. de Electricidad y Electrónica |
Facultad de Ciencias - Campus de Lejona | Tel.: +34-946012479
48940 Lejona (Vizcaya) - SPAIN | Fax: +34-944858139
-----------------------------------------------------------------------
"Go ahead... make my day." - H. Callahan
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Sun Jan 24 14:33:58 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id OAA27485
for freebsd-current-outgoing; Sun, 24 Jan 1999 14:33:58 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from ayukawa.aus.org (ayukawa.aus.org [199.166.246.1])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA27476
for <current@FreeBSD.ORG>; Sun, 24 Jan 1999 14:33:51 -0800 (PST)
(envelope-from lh@aus.org)
Received: from zer0.net (lh@zer0.net [199.166.246.189]) by ayukawa.aus.org (8.8.7/8.7.3) with ESMTP id RAA27376; Sun, 24 Jan 1999 17:13:02 -0500 (EST)
Message-Id: <199901242213.RAA27376@ayukawa.aus.org>
X-Mailer: XFMail 1.3-beta-042198 [p0] on FreeBSD
X-Priority: 3 (Normal)
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 8bit
MIME-Version: 1.0
In-Reply-To: <Pine.GSO.3.95q.990124161349.20566A-100000@rac9.wam.umd.edu>
Date: Sun, 24 Jan 1999 17:31:38 -0500 (EST)
Reply-To: lh@aus.org
From: Luke <lh@aus.org>
To: Kenneth Wayne Culver <culverk@wam.umd.edu>
Subject: Re: 4.0-Current, netscape halts system
Cc: current@FreeBSD.ORG, Baby Jane Hudson <root@drama.navinet.net>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
On 24-Jan-99 Kenneth Wayne Culver wrote:
>> I've given up on Netscape. On some FreeBSD-based machines
>> I have, it just core dumps... on others it works. Nobody
>> seems to know (or care) why, so I would suggest following
>> the development of Gzilla and Amaya.
>>
>> Of course, it would be immensely helpful if we knew what
>> mysterious person within netscape provided the port to
>> begin with (Hey, now there's a great idea) so we might ask
>> some questions. But, that's what you get for free...
>>
>>
> If you are having a problem with Netscape for FreeBSD, then just try the
> Linux version.
I was thinking of doing that, since FreeBSD can run BSDi,SCO, Linux etc
binaries, [I dont have Linux emulation installed (or even looked into)] which
one would be the best to try. It's become tiring since netscape forces hitting
the reset switch. I shouldnt be complaining :) I had 3.0-RELEASE and just had
to have that new number ..
---
E-Mail: Luke <lh@aus.org>
Sent by XFMail
----------------------------------
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Sun Jan 24 14:41:08 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id OAA28049
for freebsd-current-outgoing; Sun, 24 Jan 1999 14:41:08 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA28044
for <current@FreeBSD.ORG>; Sun, 24 Jan 1999 14:41:07 -0800 (PST)
(envelope-from jkh@zippy.cdrom.com)
Received: from zippy.cdrom.com (localhost.cdrom.com [127.0.0.1])
by zippy.cdrom.com (8.9.2/8.9.1) with ESMTP id OAA01232;
Sun, 24 Jan 1999 14:41:27 -0800 (PST)
To: "Steven P. Donegan" <donegan@quick.net>
cc: current@FreeBSD.ORG
Subject: Re: Current's availability
In-reply-to: Your message of "Sun, 24 Jan 1999 07:19:49 PST."
<Pine.BSI.3.91.990124071736.11812C-100000@oldnews.quick.net>
Date: Sun, 24 Jan 1999 14:41:27 -0800
Message-ID: <1229.917217687@zippy.cdrom.com>
From: "Jordan K. Hubbard" <jkh@zippy.cdrom.com>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
It's all a bit ill right now during the transition to 3.0S/4.0C from
2.2S/3.0C - I hope to have the build boxen back on the feet this week
sometime.
- Jordan
> Yesterday I tried to ftp a current set of floppies from
> current.freebsd.org - nothing there but 2.2.X stuff - 3.0 tree gone and
> no 4.X tree apparent. Today I get connection refused at that site. ANy
> pointers to a current tree would be appreciated. TIA.
>
> Steven P. Donegan email: donegan@quick.net
> Sr. Network Infrastructure Engineer ICBM: N 33' 47.538/W 117' 59.687
> WANG Global (within 1 meter - 133 ASL)
>
>
> To Unsubscribe: send mail to majordomo@FreeBSD.org
> with "unsubscribe freebsd-current" in the body of the message
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Sun Jan 24 14:45:22 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id OAA28746
for freebsd-current-outgoing; Sun, 24 Jan 1999 14:45:22 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from kot.ne.mediaone.net (kot.ne.mediaone.net [24.128.29.136])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA28737
for <current@freebsd.org>; Sun, 24 Jan 1999 14:45:20 -0800 (PST)
(envelope-from mi@kot.ne.mediaone.net)
Received: (from mi@localhost)
by kot.ne.mediaone.net (8.9.1a/8.9.1) id RAA04500
for current@freebsd.org; Sun, 24 Jan 1999 17:44:55 -0500 (EST)
From: Mikhail Teterin <mi@kot.ne.mediaone.net>
Message-Id: <199901242244.RAA04500@kot.ne.mediaone.net>
Subject: Re: sysctl oids (was: Re: kvm question)
In-Reply-To: <Pine.BSF.3.95.990124140935.6880C-100000@current1.whistle.com> from Julian Elischer at "Jan 24, 1999 02:15:08 pm"
To: current@FreeBSD.ORG
Date: Sun, 24 Jan 1999 17:44:55 -0500 (EST)
X-Face: %UW#n0|w>ydeGt/b@1-.UFP=K^~-:0f#O:D7w<gv/&E-lL7twZCT8B~/PA4|\t$ti+22K">
hJ5G_<5143Bb3kOIs9XpX+"V+~$adGP:J|SLieM31VIhqXeLBli"<kcG^EOVih
y+z3/UR{6SCQ
X-Mailer: ELM [version 2.4ME+ PL49 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
Julian Elischer once stated:
=> Nonsense. There are plenty of contexts in which a number makes far
=> more sense than a name -- pretty much anything in any network stack
=> other than Chaosnet, for example. If any of us ever make good on the
=> threat of SNMP integration, having fixed numerical identifiers will
=> be a requirement.
=SNMP will require a translation layer anyhow.. numbers cannot and
=should not be used. They are not easily maintained in the face of
=multiple external modules being dynamically loadable.
=That is at least my opinion.. you may and do disagree. I guess you will
=say that numbers are just as dynamic, etc.etc. well I just think that
=in the REAL WORLD, as opposed to the theoretical world, names (which
=require no co-ordination between authors), are a better choice than
=numbers, which require some central naming authority.
Pardon my intrusion, but I strongly dislike the very thought about
my computer looking-up the same string more then once or twice. If it
counts -- I'd take a number over a string anytime anywhere other
then in a documentation.
-mi
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Sun Jan 24 15:05:19 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id PAA00946
for freebsd-current-outgoing; Sun, 24 Jan 1999 15:05:19 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA00936
for <current@FreeBSD.ORG>; Sun, 24 Jan 1999 15:05:17 -0800 (PST)
(envelope-from dillon@apollo.backplane.com)
Received: (from dillon@localhost)
by apollo.backplane.com (8.9.2/8.9.1) id PAA05248;
Sun, 24 Jan 1999 15:04:42 -0800 (PST)
(envelope-from dillon)
Date: Sun, 24 Jan 1999 15:04:42 -0800 (PST)
From: Matthew Dillon <dillon@apollo.backplane.com>
Message-Id: <199901242304.PAA05248@apollo.backplane.com>
To: Mikhail Teterin <mi@kot.ne.mediaone.net>
Cc: current@FreeBSD.ORG
Subject: Re: sysctl oids (was: Re: kvm question)
References: <199901242244.RAA04500@kot.ne.mediaone.net>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
This is a silly argument. Unless the operation in question
needs to be run a thousand times a second, a string is just
fine as a lookup mechanism. Duh. Besides, you can always
cache the translation.
-Matt
Matthew Dillon
<dillon@backplane.com>
:Julian Elischer once stated:
:
:=> Nonsense. There are plenty of contexts in which a number makes far
:=> more sense than a name -- pretty much anything in any network stack
:=> other than Chaosnet, for example. If any of us ever make good on the
:=> threat of SNMP integration, having fixed numerical identifiers will
:=> be a requirement.
:
:=SNMP will require a translation layer anyhow.. numbers cannot and
:=should not be used. They are not easily maintained in the face of
:=multiple external modules being dynamically loadable.
:
:=That is at least my opinion.. you may and do disagree. I guess you will
:=say that numbers are just as dynamic, etc.etc. well I just think that
:=in the REAL WORLD, as opposed to the theoretical world, names (which
:=require no co-ordination between authors), are a better choice than
:=numbers, which require some central naming authority.
:
:Pardon my intrusion, but I strongly dislike the very thought about
:my computer looking-up the same string more then once or twice. If it
:counts -- I'd take a number over a string anytime anywhere other
:then in a documentation.
:
: -mi
:
:To Unsubscribe: send mail to majordomo@FreeBSD.org
:with "unsubscribe freebsd-current" in the body of the message
:
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Sun Jan 24 15:20:24 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id PAA03618
for freebsd-current-outgoing; Sun, 24 Jan 1999 15:20:24 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from rebma.ghostwheel.com (rebma.ghostwheel.com [207.201.56.159])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA03599
for <freebsd-current@freebsd.org>; Sun, 24 Jan 1999 15:20:18 -0800 (PST)
(envelope-from fbsd-cur@ghostwheel.com)
Received: from avalon (avalon.ghostwheel.com [207.201.56.88])
by rebma.ghostwheel.com (8.8.8/8.8.8) with SMTP id PAA17570
for <freebsd-current@freebsd.org>; Sun, 24 Jan 1999 15:20:10 -0800 (PST)
(envelope-from fbsd-cur@ghostwheel.com)
Message-Id: <4.1.19990124151511.009793a0@pop2.ghostwheel.com>
X-Sender: fbsd-cur@pop2.ghostwheel.com (Unverified)
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.1
Date: Sun, 24 Jan 1999 15:16:47 -0800
To: freebsd-current@FreeBSD.ORG
From: Chris Knight <fbsd-cur@ghostwheel.com>
Subject: Can't mount root. Really need help...
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
Greetings,
I have learned a very valuable lesson. No matter how many time I have
made world, I shouldn't do it while I'm tired. Last night I synced my tree
and made world. I rebooted, and was going to remake my kernel after the
boot. That became an impossibility.
After the the message "Waiting 15 seconds fopr SCSI devices to settle", and
before the listing of my SCSI devices is this ominous message:
ffs_mountroot: can't find rootvperror 6: panic: cannot mount root (2)
At the end of the SCSI device listing, the system starts a reboot.
Any help in either understanding what happened or getting the box back
online appreciated!
Also, if someone could tell me where I could obtain a copy of the boot.flp
and fixit.flp for a recent elf build of -current I would really appreciate it.
-ck
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Sun Jan 24 15:20:47 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id PAA03720
for freebsd-current-outgoing; Sun, 24 Jan 1999 15:20:47 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from baerenklau.de.freebsd.org (baerenklau.de.freebsd.org [195.185.195.14])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA03707
for <current@FreeBSD.ORG>; Sun, 24 Jan 1999 15:20:45 -0800 (PST)
(envelope-from w@panke.de.freebsd.org)
Received: (from uucp@localhost)
by baerenklau.de.freebsd.org (8.8.8/8.8.8) with UUCP id AAA18707;
Mon, 25 Jan 1999 00:20:20 +0100 (CET)
(envelope-from w@panke.de.freebsd.org)
Received: (from w@localhost)
by campa.panke.de.freebsd.org (8.8.8/8.8.8) id AAA01178;
Mon, 25 Jan 1999 00:17:59 +0100 (MET)
(envelope-from w)
Message-ID: <19990125001758.A346@panke.de.freebsd.org>
Date: Mon, 25 Jan 1999 00:17:58 +0100
From: Wolfram Schneider <wosch@panke.de.freebsd.org>
To: Warner Losh <imp@village.org>, current@FreeBSD.ORG
Subject: Re: Mail archive question
References: <199901211910.MAA79228@harmony.village.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.93.1i
In-Reply-To: <199901211910.MAA79228@harmony.village.org>; from Warner Losh on Thu, Jan 21, 1999 at 12:10:38PM -0700
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
On 1999-01-21 12:10:38 -0700, Warner Losh wrote:
> Given a message id and a mailing list, is there some way construct a
> URL that will fetch that mail message. This will make doing the
> UPDATING file a little easier when long messages are sent to
> -current. I can say blah blah blah changed, see <gross url> for
> details.
http://www.freebsd.org/cgi/mid.cgi?id=199901211910.MAA79228@harmony.village.org
or shorter
http://www.freebsd.org/cgi/mid.cgi?199901211910.MAA79228
--
Wolfram Schneider <wosch@freebsd.org> http://freebsd.org/~w/
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Sun Jan 24 15:23:53 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id PAA04261
for freebsd-current-outgoing; Sun, 24 Jan 1999 15:23:53 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from bsd1.gccs.com.au (router.gccs.com.au [203.17.152.1])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA04247
for <freebsd-current@FreeBSD.ORG>; Sun, 24 Jan 1999 15:23:48 -0800 (PST)
(envelope-from starr3@gccs.com.au)
Received: from lb50x (lb50x.gccs.com.au [203.17.152.10])
by bsd1.gccs.com.au (8.9.1/8.9.1) with SMTP id JAA35326;
Mon, 25 Jan 1999 09:23:21 +1000 (EST)
Message-ID: <002b01be47f0$8dea2c90$0a9811cb@gccs.com.au>
From: "Harry Starr" <starr3@gccs.com.au>
To: "Mike Smith" <mike@smith.net.au>
Cc: "Daniel C. Sobral" <dcs@newsguy.com>,
"current" <freebsd-current@FreeBSD.ORG>
Subject: Re: Problem booting using /boot/loader
Date: Mon, 25 Jan 1999 09:23:30 +1000
MIME-Version: 1.0
Content-Type: text/plain;
charset="Windows-1252"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.00.0810.800
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.0810.800
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
Just to let you know that re-cvsup'ing and building /boot has FIXED the
problem.
Thanks, Mike.
Harry.
----- Original Message -----
From: Mike Smith <mike@smith.net.au>
To: Harry Starr <starr3@gccs.com.au>
Cc: Daniel C. Sobral <dcs@newsguy.com>; current
<freebsd-current@FreeBSD.ORG>
Sent: Monday, January 25, 1999 3:23 AM
Subject: Re: Problem booting using /boot/loader
>> Yep!
>>
>> /boot/loader.old works OK! (dated Jan 11)
>>
>> /boot/loader (Jan 24) fails.
>>
>> And yes, the kernel was recompiled from the same cvsup sources.
>>
>> Definitely looks like something broke in the current loader.
>
>There was a window of a few hours where the 4-current loader was broken
>due to a typo on my part. I forgot to merge the fix back into 3-stable
>(which I've just now done).
>
>Please resup/rebuild/reinstall the loader. Also note that for those of
>you that had to change your /etc/fstab - you'll have to change it right
>back. 8)
>
>If you have to push through a loader that has this bug,
>'set root_disk_unit=0' for eg. a system with root on wd0 or da0 will
>avoid the broken code.
>
>--
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Sun Jan 24 15:24:01 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id PAA04348
for freebsd-current-outgoing; Sun, 24 Jan 1999 15:24:01 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA04317
for <current@FreeBSD.ORG>; Sun, 24 Jan 1999 15:23:58 -0800 (PST)
(envelope-from jkh@zippy.cdrom.com)
Received: from zippy.cdrom.com (localhost.cdrom.com [127.0.0.1])
by zippy.cdrom.com (8.9.2/8.9.1) with ESMTP id PAA01480;
Sun, 24 Jan 1999 15:23:50 -0800 (PST)
To: lh@aus.org
cc: Kenneth Wayne Culver <culverk@wam.umd.edu>, current@FreeBSD.ORG,
Baby Jane Hudson <root@drama.navinet.net>
Subject: Re: 4.0-Current, netscape halts system
In-reply-to: Your message of "Sun, 24 Jan 1999 17:31:38 EST."
<199901242213.RAA27376@ayukawa.aus.org>
Date: Sun, 24 Jan 1999 15:23:50 -0800
Message-ID: <1476.917220230@zippy.cdrom.com>
From: "Jordan K. Hubbard" <jkh@zippy.cdrom.com>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
I really don't understand the problems that everyone is having,
myself. I've been running netscape (communicator 4.5) in -current for
ages now and just switched to 4.0 without any problems. My netscape
still continues to function just fine and has never crashed any of
my system so much as once.
Why the wide disparity in experience, I wonder?
> On 24-Jan-99 Kenneth Wayne Culver wrote:
> >> I've given up on Netscape. On some FreeBSD-based machines
> >> I have, it just core dumps... on others it works. Nobody
> >> seems to know (or care) why, so I would suggest following
> >> the development of Gzilla and Amaya.
> >>
> >> Of course, it would be immensely helpful if we knew what
> >> mysterious person within netscape provided the port to
> >> begin with (Hey, now there's a great idea) so we might ask
> >> some questions. But, that's what you get for free...
> >>
> >>
> > If you are having a problem with Netscape for FreeBSD, then just try the
> > Linux version.
>
> I was thinking of doing that, since FreeBSD can run BSDi,SCO, Linux e
tc
> binaries, [I dont have Linux emulation installed (or even looked into)] which
> one would be the best to try. It's become tiring since netscape forces hittin
g
> the reset switch. I shouldnt be complaining :) I had 3.0-RELEASE and just had
> to have that new number ..
>
> ---
>
> E-Mail: Luke <lh@aus.org>
> Sent by XFMail
> ----------------------------------
>
> To Unsubscribe: send mail to majordomo@FreeBSD.org
> with "unsubscribe freebsd-current" in the body of the message
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Sun Jan 24 15:28:53 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id PAA05279
for freebsd-current-outgoing; Sun, 24 Jan 1999 15:28:53 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from kot.ne.mediaone.net (kot.ne.mediaone.net [24.128.29.136])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA05266
for <current@freebsd.org>; Sun, 24 Jan 1999 15:28:51 -0800 (PST)
(envelope-from mi@kot.ne.mediaone.net)
Received: (from mi@localhost)
by kot.ne.mediaone.net (8.9.1a/8.9.1) id SAA04614
for current@freebsd.org; Sun, 24 Jan 1999 18:28:28 -0500 (EST)
From: Mikhail Teterin <mi@kot.ne.mediaone.net>
Message-Id: <199901242328.SAA04614@kot.ne.mediaone.net>
Subject: Re: sysctl oids (was: Re: kvm question)
In-Reply-To: <199901242304.PAA05248@apollo.backplane.com> from Matthew Dillon at "Jan 24, 1999 03:04:42 pm"
To: current@FreeBSD.ORG
Date: Sun, 24 Jan 1999 18:28:28 -0500 (EST)
X-Face: %UW#n0|w>ydeGt/b@1-.UFP=K^~-:0f#O:D7w<gv/&E-lL7twZCT8B~/PA4|\t$ti+22K">
hJ5G_<5143Bb3kOIs9XpX+"V+~$adGP:J|SLieM31VIhqXeLBli"<kcG^EOVih
y+z3/UR{6SCQ
X-Mailer: ELM [version 2.4ME+ PL49 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
Matthew Dillon once stated:
= This is a silly argument. Unless the operation in question
= needs to be run a thousand times a second, a string is just
= fine as a lookup mechanism. Duh. Besides, you can always
= cache the translation.
I'll agree, that todays hardware turns this into a matter of taste.
Your argument will not remain smart for too long, however, either.
Pretty soon you may need to change "thousand" into "million" and so
on. Likewise, my argument was not at all silly back when my kernel was
smaller then 700Kb. My taste did not change since...
-mi
=:Julian Elischer once stated:
=:
=:=> Nonsense. There are plenty of contexts in which a number makes far
=:=> more sense than a name -- pretty much anything in any network stack
=:=> other than Chaosnet, for example. If any of us ever make good on the
=:=> threat of SNMP integration, having fixed numerical identifiers will
=:=> be a requirement.
=:
=:=SNMP will require a translation layer anyhow.. numbers cannot and
=:=should not be used. They are not easily maintained in the face of
=:=multiple external modules being dynamically loadable.
=:
=:=That is at least my opinion.. you may and do disagree. I guess you will
=:=say that numbers are just as dynamic, etc.etc. well I just think that
=:=in the REAL WORLD, as opposed to the theoretical world, names (which
=:=require no co-ordination between authors), are a better choice than
=:=numbers, which require some central naming authority.
=:
=:Pardon my intrusion, but I strongly dislike the very thought about
=:my computer looking-up the same string more then once or twice. If it
=:counts -- I'd take a number over a string anytime anywhere other
=:then in a documentation.
=:
=: -mi
=:
=:To Unsubscribe: send mail to majordomo@FreeBSD.org
=:with "unsubscribe freebsd-current" in the body of the message
=:
=
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Sun Jan 24 15:31:46 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id PAA05930
for freebsd-current-outgoing; Sun, 24 Jan 1999 15:31:46 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from fw.bby.com.au (ns.bby.com.au [192.83.119.129])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA05909
for <current@FreeBSD.ORG>; Sun, 24 Jan 1999 15:31:36 -0800 (PST)
(envelope-from gnb@itga.com.au)
Received: (from daemon@localhost) by fw.bby.com.au (8.8.8/8.6.9) id KAA01230; Mon, 25 Jan 1999 10:31:14 +1100 (EST)
Received: from lightning.itga.com.au(192.168.71.20)
via SMTP by fw.bby.com.au, id smtpd001228; Sun Jan 24 23:31:14 1999
Received: from lightning (lightning [192.168.71.20])
by lightning.itga.com.au (8.9.1a/8.9.1) with ESMTP id KAA20875;
Mon, 25 Jan 1999 10:31:13 +1100 (EST)
Message-Id: <199901242331.KAA20875@lightning.itga.com.au>
X-Mailer: exmh version 2.0.1 12/23/97
From: Gregory Bond <gnb@itga.com.au>
To: Warner Losh <imp@village.org>
Cc: Kazutaka YOKOTA <yokota@zodiac.mech.utsunomiya-u.ac.jp>,
current@FreeBSD.ORG
Subject: Re: keymaps
In-reply-to: Your message of Thu, 21 Jan 1999 21:40:02 -0700.
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Mon, 25 Jan 1999 10:31:13 +1100
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
> What's wrong with us.unix.kbd?
This also swaps a bunch of other things - Grave<->Esc, BS<->Del, etc. It was
more confusing, so I made a new keymap.
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Sun Jan 24 15:32:40 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id PAA06194
for freebsd-current-outgoing; Sun, 24 Jan 1999 15:32:40 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from verdi.nethelp.no (verdi.nethelp.no [158.36.41.162])
by hub.freebsd.org (8.8.8/8.8.8) with SMTP id PAA06185
for <current@FreeBSD.ORG>; Sun, 24 Jan 1999 15:32:37 -0800 (PST)
(envelope-from sthaug@nethelp.no)
From: sthaug@nethelp.no
Received: (qmail 16688 invoked by uid 1001); 24 Jan 1999 23:32:24 +0000 (GMT)
To: jkh@zippy.cdrom.com
Cc: lh@aus.org, culverk@wam.umd.edu, current@FreeBSD.ORG,
root@drama.navinet.net
Subject: Re: 4.0-Current, netscape halts system
In-Reply-To: Your message of "Sun, 24 Jan 1999 15:23:50 -0800"
References: <1476.917220230@zippy.cdrom.com>
X-Mailer: Mew version 1.05+ on Emacs 19.34.2
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Date: Mon, 25 Jan 1999 00:32:24 +0100
Message-ID: <16686.917220744@verdi.nethelp.no>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
> I really don't understand the problems that everyone is having,
> myself. I've been running netscape (communicator 4.5) in -current for
> ages now and just switched to 4.0 without any problems. My netscape
> still continues to function just fine and has never crashed any of
> my system so much as once.
>
> Why the wide disparity in experience, I wonder?
On my system, running the FreeBSD 4.0[678] or 4.5 version, the setting
of MOZILLA_NO_ASYNC_DNS makes a noticeable difference.
With MOZILLA_NO_ASYNC_DNS turned off, Netscape uses normal name lookup
inside the netscape process itself. In 2.2.[78] this worked fine, in
3.0 I get frequent hangs if the name lookups take "too long". I can
avoid the hangs if I make sure that the name to IP address is in my
local name server cache (for instance by doing a manual nslookup or
similar on the name). This is of course rather cumbersome.
With MOZILLA_NO_ASYNC_DNS turned on, Netscape starts a separate (huge,
resource consuming) asynchronous DNS lookup daemon. But I don't get
the hangs.
Steinar Haug, Nethelp consulting, sthaug@nethelp.no
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Sun Jan 24 15:33:37 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id PAA06332
for freebsd-current-outgoing; Sun, 24 Jan 1999 15:33:37 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA06325
for <current@FreeBSD.ORG>; Sun, 24 Jan 1999 15:33:36 -0800 (PST)
(envelope-from julian@whistle.com)
Received: (from daemon@localhost)
by alpo.whistle.com (8.8.5/8.8.5) id PAA21876;
Sun, 24 Jan 1999 15:25:35 -0800 (PST)
Received: from current1.whistle.com(207.76.205.22)
via SMTP by alpo.whistle.com, id smtpdr21872; Sun Jan 24 23:25:30 1999
Date: Sun, 24 Jan 1999 15:25:26 -0800 (PST)
From: Julian Elischer <julian@whistle.com>
To: Mikhail Teterin <mi@kot.ne.mediaone.net>
cc: current@FreeBSD.ORG
Subject: Re: sysctl oids (was: Re: kvm question)
In-Reply-To: <199901242244.RAA04500@kot.ne.mediaone.net>
Message-ID: <Pine.BSF.3.95.990124152448.6880E-100000@current1.whistle.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
On Sun, 24 Jan 1999, Mikhail Teterin wrote:
>
> Pardon my intrusion, but I strongly dislike the very thought about
> my computer looking-up the same string more then once or twice. If it
> counts -- I'd take a number over a string anytime anywhere other
> then in a documentation.
how often do you use this?
>
> -mi
>
> To Unsubscribe: send mail to majordomo@FreeBSD.org
> with "unsubscribe freebsd-current" in the body of the message
>
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Sun Jan 24 15:40:30 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id PAA07073
for freebsd-current-outgoing; Sun, 24 Jan 1999 15:40:30 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from kot.ne.mediaone.net (kot.ne.mediaone.net [24.128.29.136])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA07068
for <current@freebsd.org>; Sun, 24 Jan 1999 15:40:27 -0800 (PST)
(envelope-from mi@kot.ne.mediaone.net)
Received: (from mi@localhost)
by kot.ne.mediaone.net (8.9.1a/8.9.1) id SAA04694
for current@freebsd.org; Sun, 24 Jan 1999 18:40:05 -0500 (EST)
From: Mikhail Teterin <mi@kot.ne.mediaone.net>
Message-Id: <199901242340.SAA04694@kot.ne.mediaone.net>
Subject: Re: sysctl oids (was: Re: kvm question)
In-Reply-To: <Pine.BSF.3.95.990124152448.6880E-100000@current1.whistle.com> from Julian Elischer at "Jan 24, 1999 03:25:26 pm"
To: current@FreeBSD.ORG
Date: Sun, 24 Jan 1999 18:40:05 -0500 (EST)
X-Face: %UW#n0|w>ydeGt/b@1-.UFP=K^~-:0f#O:D7w<gv/&E-lL7twZCT8B~/PA4|\t$ti+22K">
hJ5G_<5143Bb3kOIs9XpX+"V+~$adGP:J|SLieM31VIhqXeLBli"<kcG^EOVih
y+z3/UR{6SCQ
X-Mailer: ELM [version 2.4ME+ PL49 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
Julian Elischer once stated:
=> Pardon my intrusion, but I strongly dislike the very thought about
=> my computer looking-up the same string more then once or twice. If it
=> counts -- I'd take a number over a string anytime anywhere other
=> then in a documentation.
=how often do you use this?
Seldom. But the strings are still in the kernel, which becomes
bigger with every build. My argument was more general, however,
and directed against the growing tendency to use string literal
(and copy them beck and forth). IMHO, the point of faster hardware
is purely to have thing running faster, rather then letting
programmers be "sloppier".
However, as I already stated, this is just my preference.
-mi
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Sun Jan 24 15:49:39 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id PAA07810
for freebsd-current-outgoing; Sun, 24 Jan 1999 15:49:39 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from amber.ghostwheel.com (amber.ghostwheel.com [207.201.56.89])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA07799
for <current@FreeBSD.ORG>; Sun, 24 Jan 1999 15:49:37 -0800 (PST)
(envelope-from merlin@ghostwheel.com)
Received: from avalon (avalon [207.201.56.88])
by amber.ghostwheel.com (8.8.8/8.8.5) with SMTP id OAA08267
for <current@FreeBSD.ORG>; Sun, 24 Jan 1999 14:15:22 -0800 (PST)
Message-Id: <4.1.19990124140032.0098e840@pop2.ghostwheel.com>
X-Sender: merlin@pop2.ghostwheel.com
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.1
Date: Sun, 24 Jan 1999 14:09:41 -0800
To: current@FreeBSD.ORG
From: Chris Knight <merlin@ghostwheel.com>
Subject: Can't mount root. Really need help...
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
Greetings,
I have learned a very valuable lesson. No matter how many time I have
made world, I shouldn't do it while I'm tired. Last night I synced my tree
and made world. I rebooted, and was going to remake my kernel after the
boot. That became an impossibility.
After the the message "Waiting 15 seconds fopr SCSI devices to settle", and
before the listing of my SCSI devices is this ominous message:
ffs_mountroot: can't find rootvperror 6: panic: cannot mount root (2)
At the end of the SCSI device listing, the system starts a reboot.
Any help in either understanding what happened or getting the box back
online appreciated!
-ck
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Sun Jan 24 15:56:11 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id PAA08846
for freebsd-current-outgoing; Sun, 24 Jan 1999 15:56:11 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA08839
for <current@FreeBSD.ORG>; Sun, 24 Jan 1999 15:56:10 -0800 (PST)
(envelope-from dillon@apollo.backplane.com)
Received: (from dillon@localhost)
by apollo.backplane.com (8.9.2/8.9.1) id PAA05605;
Sun, 24 Jan 1999 15:55:50 -0800 (PST)
(envelope-from dillon)
Date: Sun, 24 Jan 1999 15:55:50 -0800 (PST)
From: Matthew Dillon <dillon@apollo.backplane.com>
Message-Id: <199901242355.PAA05605@apollo.backplane.com>
To: Mikhail Teterin <mi@kot.ne.mediaone.net>
Cc: current@FreeBSD.ORG
Subject: Re: sysctl oids (was: Re: kvm question)
References: <199901242340.SAA04694@kot.ne.mediaone.net>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
:Seldom. But the strings are still in the kernel, which becomes
:bigger with every build. My argument was more general, however,
:and directed against the growing tendency to use string literal
:(and copy them beck and forth). IMHO, the point of faster hardware
:is purely to have thing running faster, rather then letting
:programmers be "sloppier".
:
:However, as I already stated, this is just my preference.
:
: -mi
You are operating under the assumption that the strings somehow
take a huge amount of space compared to an int and the rest of the
sysctl structure. This couldn't be farther from the truth.
apollo:/usr/src/sys# sysctl -A | awk '{ print $1; }' | sed -e 's/://' | wc
384 382 7555
8K. Not a big deal. And this doesn't even include filtering out the
prefixes which I'm duplicate-counting all over the place.
The equivalent 'integer' form, judging by the average length of the
postfix string, would still eat 3K, so we'd only be saving 5K.
Strings are a whole lot more portable then integer assignments.
-Matt
Matthew Dillon
<dillon@backplane.com>
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Sun Jan 24 15:58:25 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id PAA09322
for freebsd-current-outgoing; Sun, 24 Jan 1999 15:58:25 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA09314
for <current@FreeBSD.ORG>; Sun, 24 Jan 1999 15:58:20 -0800 (PST)
(envelope-from dillon@apollo.backplane.com)
Received: (from dillon@localhost)
by apollo.backplane.com (8.9.2/8.9.1) id PAA05648;
Sun, 24 Jan 1999 15:58:04 -0800 (PST)
(envelope-from dillon)
Date: Sun, 24 Jan 1999 15:58:04 -0800 (PST)
From: Matthew Dillon <dillon@apollo.backplane.com>
Message-Id: <199901242358.PAA05648@apollo.backplane.com>
To: Chris Knight <merlin@ghostwheel.com>
Cc: current@FreeBSD.ORG
Subject: Re: Can't mount root. Really need help...
References: <4.1.19990124140032.0098e840@pop2.ghostwheel.com>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
From the boot prompt you should be able to specify the correct
root device. Try:
boot: /kernel -a
The problem is probably the breakage other people have described,
with sd0sNa turning into sd0a or da0a or something like that.
-Matt
Matthew Dillon
<dillon@backplane.com>
:Greetings,
:
: I have learned a very valuable lesson. No matter how many time I have
:made world, I shouldn't do it while I'm tired. Last night I synced my tree
:and made world. I rebooted, and was going to remake my kernel after the
:boot. That became an impossibility.
:
:After the the message "Waiting 15 seconds fopr SCSI devices to settle", and
:before the listing of my SCSI devices is this ominous message:
:
:ffs_mountroot: can't find rootvperror 6: panic: cannot mount root (2)
:
:At the end of the SCSI device listing, the system starts a reboot.
:
:Any help in either understanding what happened or getting the box back
:online appreciated!
:
:-ck
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Sun Jan 24 16:05:56 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id QAA11543
for freebsd-current-outgoing; Sun, 24 Jan 1999 16:05:56 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from freebase.sitaranetworks.com (freebase.sitaranetworks.com [199.103.141.181])
by hub.freebsd.org (8.8.8/8.8.8) with SMTP id QAA11521
for <current@FreeBSD.ORG>; Sun, 24 Jan 1999 16:05:53 -0800 (PST)
(envelope-from john@loverso.southborough.ma.us)
Received: from loverso.southborough.ma.us (loverso.sitaranetworks.com [199.103.141.107])
by freebase.sitaranetworks.com (8.8.8/8.8.8) with ESMTP id TAA10147;
Sun, 24 Jan 1999 19:05:39 -0500 (EST)
Received: from loverso.southborough.ma.us (localhost [127.0.0.1]) by loverso.southborough.ma.us (8.8.8/8.6.9) with ESMTP id TAA27514; Sun, 24 Jan 1999 19:05:38 -0500 (EST)
Message-Id: <199901250005.TAA27514@loverso.southborough.ma.us>
To: "Jordan K. Hubbard" <jkh@zippy.cdrom.com>
Cc: current@FreeBSD.ORG
Subject: Re: Current's availability
In-reply-to: Message from "Jordan K. Hubbard" <jkh@zippy.cdrom.com>
<1229.917217687@zippy.cdrom.com> .
X-Face: "UZ!}1W2N?eJdN(`1%|/OOPqJ).Idk?UyvWw'W-%`Gto8^IkEm>.g1O$[.;~}8E=Ire0|lO
.o>:NlJS1@vO9bVmswRoq3j<A2*d2*S+2%tyPf2|dwcrNgSx%#^d@7'85{"$i2,xw/T,I<]R$FG"{>
DdX9YGSeJ5a(mfX[1u>Z63G5_^+'8LVqjqvn
X-Url: http://surf.to/loverso
Date: Sun, 24 Jan 1999 19:05:37 -0500
From: John Robert LoVerso <john@loverso.southborough.ma.us>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
Will you be keeping the last snapshot of 2.2.X around when it returns?
On another note, does current@freebsd.org now correspond to 4.X ("-current")
discussions, while stable@freebsd.org now correspond to 3.X ("-stable")?
If so, is there / will there be a separate forum for 2.X ("-stable in a
past life")?
John
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Sun Jan 24 16:06:50 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id QAA12123
for freebsd-current-outgoing; Sun, 24 Jan 1999 16:06:50 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA12116
for <current@FreeBSD.ORG>; Sun, 24 Jan 1999 16:06:49 -0800 (PST)
(envelope-from jkh@zippy.cdrom.com)
Received: from zippy.cdrom.com (localhost.cdrom.com [127.0.0.1])
by zippy.cdrom.com (8.9.2/8.9.1) with ESMTP id QAA01713;
Sun, 24 Jan 1999 16:07:04 -0800 (PST)
To: John Robert LoVerso <john@loverso.southborough.ma.us>
cc: current@FreeBSD.ORG
Subject: Re: Current's availability
In-reply-to: Your message of "Sun, 24 Jan 1999 19:05:37 EST."
<199901250005.TAA27514@loverso.southborough.ma.us>
Date: Sun, 24 Jan 1999 16:07:04 -0800
Message-ID: <1710.917222824@zippy.cdrom.com>
From: "Jordan K. Hubbard" <jkh@zippy.cdrom.com>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
Yes.
> Will you be keeping the last snapshot of 2.2.X around when it returns?
>
>
> On another note, does current@freebsd.org now correspond to 4.X ("-current")
> discussions, while stable@freebsd.org now correspond to 3.X ("-stable")?
> If so, is there / will there be a separate forum for 2.X ("-stable in a
> past life")?
>
> John
>
> To Unsubscribe: send mail to majordomo@FreeBSD.org
> with "unsubscribe freebsd-current" in the body of the message
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Sun Jan 24 16:07:30 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id QAA12207
for freebsd-current-outgoing; Sun, 24 Jan 1999 16:07:30 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA12202
for <current@FreeBSD.ORG>; Sun, 24 Jan 1999 16:07:29 -0800 (PST)
(envelope-from jkh@zippy.cdrom.com)
Received: from zippy.cdrom.com (localhost.cdrom.com [127.0.0.1])
by zippy.cdrom.com (8.9.2/8.9.1) with ESMTP id QAA01731;
Sun, 24 Jan 1999 16:07:48 -0800 (PST)
To: John Robert LoVerso <john@loverso.southborough.ma.us>
cc: current@FreeBSD.ORG
Subject: Re: Current's availability
In-reply-to: Your message of "Sun, 24 Jan 1999 19:05:37 EST."
<199901250005.TAA27514@loverso.southborough.ma.us>
Date: Sun, 24 Jan 1999 16:07:48 -0800
Message-ID: <1728.917222868@zippy.cdrom.com>
From: "Jordan K. Hubbard" <jkh@zippy.cdrom.com>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
> On another note, does current@freebsd.org now correspond to 4.X ("-current")
> discussions, while stable@freebsd.org now correspond to 3.X ("-stable")?
Basically, yes.
> If so, is there / will there be a separate forum for 2.X ("-stable in a
> past life")?
I think we could probably discuss those questions in -stable as well
since that list doesn't get anywhere near as much traffic as -current
in any case, and many of the interested users overlap.
- Jordan
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Sun Jan 24 16:14:43 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id QAA13046
for freebsd-current-outgoing; Sun, 24 Jan 1999 16:14:43 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from stade.demon.co.uk (stade.demon.co.uk [158.152.29.164])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA13034
for <freebsd-current@FreeBSD.ORG>; Sun, 24 Jan 1999 16:14:40 -0800 (PST)
(envelope-from aw1@stade.co.uk)
Received: (from aw1@localhost)
by stade.demon.co.uk (8.9.2/8.9.1) id XAA00831;
Sun, 24 Jan 1999 23:11:46 GMT
(envelope-from aw1)
Date: Sun, 24 Jan 1999 23:11:46 +0000
From: Adrian Wontroba <aw1@stade.co.uk>
To: Mike Smith <mike@smith.net.au>
Cc: freebsd-current@FreeBSD.ORG
Subject: Re: Booting -current with new loader
Message-ID: <19990124231145.A382@titus.stade.co.uk>
Reply-To: aw1@stade.co.uk
References: <19990124170140.A688@titus.stade.co.uk> <199901241730.JAA04022@dingo.cdrom.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.95.1i
In-Reply-To: <199901241730.JAA04022@dingo.cdrom.com>; from Mike Smith on Sun, Jan 24, 1999 at 09:29:59AM -0800
X-Operating-System: FreeBSD 4.0-CURRENT
Organization: Yes, I need some of that.
X-Phone: +(44) 121 681 6677
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
On Sun, Jan 24, 1999 at 09:29:59AM -0800, Mike Smith wrote:
> num_ide_disks is now deprecated, you can throw it
> away. If you resup, you won't need root_disk_unit either - that just
> avoids the code I broke.
Confirmed. My system now boots quite happily without num_ide_disks or
root_disk_unit.
--
Adrian Wontroba
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Sun Jan 24 16:21:00 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id QAA13706
for freebsd-current-outgoing; Sun, 24 Jan 1999 16:21:00 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from whistle.com (s205m131.whistle.com [207.76.205.131])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA13692
for <current@FreeBSD.ORG>; Sun, 24 Jan 1999 16:20:57 -0800 (PST)
(envelope-from archie@whistle.com)
Received: (from smap@localhost) by whistle.com (8.7.5/8.6.12) id QAA02168; Sun, 24 Jan 1999 16:20:13 -0800 (PST)
Received: from bubba.whistle.com( 207.76.205.7) by whistle.com via smap (V2.0)
id xma002166; Sun, 24 Jan 99 16:20:12 -0800
Received: (from archie@localhost) by bubba.whistle.com (8.8.7/8.6.12) id QAA22590; Sun, 24 Jan 1999 16:20:12 -0800 (PST)
From: Archie Cobbs <archie@whistle.com>
Message-Id: <199901250020.QAA22590@bubba.whistle.com>
Subject: Re: 4.0-Current, netscape halts system
In-Reply-To: <1476.917220230@zippy.cdrom.com> from "Jordan K. Hubbard" at "Jan 24, 99 03:23:50 pm"
To: jkh@zippy.cdrom.com (Jordan K. Hubbard)
Date: Sun, 24 Jan 1999 16:20:12 -0800 (PST)
Cc: current@FreeBSD.ORG
X-Mailer: ELM [version 2.4ME+ PL38 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
Jordan K. Hubbard writes:
> I really don't understand the problems that everyone is having,
> myself. I've been running netscape (communicator 4.5) in -current for
> ages now and just switched to 4.0 without any problems. My netscape
> still continues to function just fine and has never crashed any of
> my system so much as once.
>
> Why the wide disparity in experience, I wonder?
Do you ever run Java applets? Netscape 4.5 seems to work fine
until running Java, which kicks off some sort of time bomb.
Death is not immediate, but it is guaranteed.
-Archie
___________________________________________________________________________
Archie Cobbs * Whistle Communications, Inc. * http://www.whistle.com
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Sun Jan 24 16:22:55 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id QAA13910
for freebsd-current-outgoing; Sun, 24 Jan 1999 16:22:55 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from rah.star-gate.com (sj-dsl-9-129-138.dspeed.net [209.249.129.138])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA13905
for <current@FreeBSD.ORG>; Sun, 24 Jan 1999 16:22:53 -0800 (PST)
(envelope-from hasty@rah.star-gate.com)
Received: from rah.star-gate.com (localhost.star-gate.com [127.0.0.1])
by rah.star-gate.com (8.9.1/8.8.8) with ESMTP id QAA05365;
Sun, 24 Jan 1999 16:21:16 -0800 (PST)
(envelope-from hasty@rah.star-gate.com)
Message-Id: <199901250021.QAA05365@rah.star-gate.com>
X-Mailer: exmh version 2.0.2 2/24/98
To: "Jordan K. Hubbard" <jkh@zippy.cdrom.com>
cc: lh@aus.org, Kenneth Wayne Culver <culverk@wam.umd.edu>,
current@FreeBSD.ORG, Baby Jane Hudson <root@drama.navinet.net>
Subject: Re: 4.0-Current, netscape halts system
In-reply-to: Your message of "Sun, 24 Jan 1999 15:23:50 PST."
<1476.917220230@zippy.cdrom.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Sun, 24 Jan 1999 16:21:16 -0800
From: Amancio Hasty <hasty@rah.star-gate.com>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
http://www.developer.com/experts/expertspanel.html
click on Bar's Guide to the the Interactive Fiction and after
the page finishes loading click "Back" on Netscape's tool bar.
Instant core -dump.
Amancio
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Sun Jan 24 16:45:31 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id QAA16821
for freebsd-current-outgoing; Sun, 24 Jan 1999 16:45:31 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from dingo.cdrom.com (castles154.castles.com [208.214.165.154])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA16813
for <current@FreeBSD.ORG>; Sun, 24 Jan 1999 16:45:29 -0800 (PST)
(envelope-from mike@dingo.cdrom.com)
Received: from dingo.cdrom.com (LOCALHOST [127.0.0.1])
by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id QAA06023;
Sun, 24 Jan 1999 16:41:17 -0800 (PST)
(envelope-from mike@dingo.cdrom.com)
Message-Id: <199901250041.QAA06023@dingo.cdrom.com>
X-Mailer: exmh version 2.0.2 2/24/98
To: Garrett Wollman <wollman@khavrinen.lcs.mit.edu>
cc: Mike Smith <mike@smith.net.au>, current@FreeBSD.ORG
Subject: Re: sysctl oids (was: Re: kvm question)
In-reply-to: Your message of "Sun, 24 Jan 1999 17:01:11 EST."
<199901242201.RAA17112@khavrinen.lcs.mit.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Sun, 24 Jan 1999 16:41:17 -0800
From: Mike Smith <mike@smith.net.au>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
> <<On Sun, 24 Jan 1999 13:11:12 -0800, Mike Smith <mike@smith.net.au> said:
>
> > Backwards compatibility is one thing, but new nodes should be named,
> > not numbered. OID_AUTO is bogus because it perpetuates the numbering
> > of nodes.
>
> Nonsense. There are plenty of contexts in which a number makes far
> more sense than a name -- pretty much anything in any network stack
> other than Chaosnet, for example. If any of us ever make good on the
> threat of SNMP integration, having fixed numerical identifiers will be
> a requirement.
A number can be a name, but a name not a number. It's obvious that
enumerated objects need numeric identifiers, but not desirable to
mandate the existence of numbers to match all names.
Unless you want the IANA to step in of course.
--
\\ Sometimes you're ahead, \\ Mike Smith
\\ sometimes you're behind. \\ mike@smith.net.au
\\ The race is long, and in the \\ msmith@freebsd.org
\\ end it's only with yourself. \\ msmith@cdrom.com
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Sun Jan 24 16:48:01 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id QAA16981
for freebsd-current-outgoing; Sun, 24 Jan 1999 16:47:09 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from dingo.cdrom.com (castles154.castles.com [208.214.165.154])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA16976
for <current@FreeBSD.ORG>; Sun, 24 Jan 1999 16:47:07 -0800 (PST)
(envelope-from mike@dingo.cdrom.com)
Received: from dingo.cdrom.com (LOCALHOST [127.0.0.1])
by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id QAA06042;
Sun, 24 Jan 1999 16:43:12 -0800 (PST)
(envelope-from mike@dingo.cdrom.com)
Message-Id: <199901250043.QAA06042@dingo.cdrom.com>
X-Mailer: exmh version 2.0.2 2/24/98
To: Mikhail Teterin <mi@kot.ne.mediaone.net>
cc: current@FreeBSD.ORG
Subject: Re: sysctl oids (was: Re: kvm question)
In-reply-to: Your message of "Sun, 24 Jan 1999 17:44:55 EST."
<199901242244.RAA04500@kot.ne.mediaone.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Sun, 24 Jan 1999 16:43:12 -0800
From: Mike Smith <mike@smith.net.au>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
>
> Pardon my intrusion, but I strongly dislike the very thought about
> my computer looking-up the same string more then once or twice. If it
> counts -- I'd take a number over a string anytime anywhere other
> then in a documentation.
Since sysctl isn't a performance interface, this isn't really an issue.
OTOH, you should consider going back to single-character directory
names, since that's much more significant.
--
\\ Sometimes you're ahead, \\ Mike Smith
\\ sometimes you're behind. \\ mike@smith.net.au
\\ The race is long, and in the \\ msmith@freebsd.org
\\ end it's only with yourself. \\ msmith@cdrom.com
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Sun Jan 24 16:57:30 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id QAA17611
for freebsd-current-outgoing; Sun, 24 Jan 1999 16:57:30 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from hydrogen.fircrest.net (metriclient-1.uoregon.edu [128.223.172.1])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA17577
for <current@freebsd.org>; Sun, 24 Jan 1999 16:56:59 -0800 (PST)
(envelope-from gurney_j@efn.org)
Received: (from jmg@localhost)
by hydrogen.fircrest.net (8.9.1/8.8.7) id QAA02722;
Sun, 24 Jan 1999 16:56:05 -0800 (PST)
Message-ID: <19990124165605.05029@hydrogen.nike.efn.org>
Date: Sun, 24 Jan 1999 16:56:05 -0800
From: John-Mark Gurney <gurney_j@efn.org>
To: current@FreeBSD.ORG
Subject: bug with TCP over lossy lines?
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.69
Reply-To: John-Mark Gurney <gurney_j@resnet.uoregon.edu>
Organization: Cu Networking
X-Operating-System: FreeBSD 3.0-CURRENT i386
X-PGP-Fingerprint: B7 EC EF F8 AE ED A7 31 96 7A 22 B3 D8 56 36 F4
X-Files: The truth is out there
X-URL: http://resnet.uoregon.edu/~gurney_j/
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
well, I've seen a bug where the machine will actually recieve a packet
from the remote machine that ack's data, but for some reason it will
not get to the stack, and the local machine will continue to send old
data...
the local machine is metriclient-1.uoregon.edu, the remote machine is
jupiter.uoregon.edu... I'm connected via a Ricochet wireless modem...
it opperates in the 900Mhz range and causes (and I believe is susceptible
to) interference to/from 900Mhz phones...
here is a tcpdump run on metriclient-1:
16:37:16.547109 metriclient-1.uoregon.edu.3016 > jupiter.uoregon.edu.ssh: . 10880:12340(1460) ack 41 win 17520 (DF) [tos 0x8]
16:37:21.707361 jupiter.uoregon.edu.ssh > metriclient-1.uoregon.edu.3016: . ack 13800 win 8760 (DF) [tos 0x8]
16:37:21.709420 metriclient-1.uoregon.edu.3016 > jupiter.uoregon.edu.ssh: . 13800:15260(1460) ack 41 win 17520 (DF) [tos 0x8]
16:37:21.711135 metriclient-1.uoregon.edu.3016 > jupiter.uoregon.edu.ssh: . 15260:16720(1460) ack 41 win 17520 (DF) [tos 0x8]
16:37:29.666465 jupiter.uoregon.edu.ssh > metriclient-1.uoregon.edu.3016: . ack 15260 win 8760 (DF) [tos 0x8]
16:37:29.666911 metriclient-1.uoregon.edu.3016 > jupiter.uoregon.edu.ssh: . 16720:18180(1460) ack 41 win 17520 (DF) [tos 0x8]
16:37:29.668611 metriclient-1.uoregon.edu.3016 > jupiter.uoregon.edu.ssh: . 18180:19640(1460) ack 41 win 17520 (DF) [tos 0x8]
16:37:40.866012 jupiter.uoregon.edu.ssh > metriclient-1.uoregon.edu.3016: . ack 16720 win 8760 (DF) [tos 0x8]
16:37:46.545981 metriclient-1.uoregon.edu.3016 > jupiter.uoregon.edu.ssh: . 15260:16720(1460) ack 41 win 17520 (DF) [tos 0x8]
16:38:20.544650 metriclient-1.uoregon.edu.3016 > jupiter.uoregon.edu.ssh: . 15260:16720(1460) ack 41 win 17520 (DF) [tos 0x8]
why are we sending data that the remote has already ack'd?? it does
finally recover as jupiter will send another ack packet for even more
data, but it doesn't explain why we send data that the remote host
ack'd...
the line that I'm going over has a VERY high latency right now.. ping is
returning rtt's in the 4-8second range...
I am running natd on the local host, but I have seen something VERY
similar happen on my notebook running an older 3.0-current...
FreeBSD hydrogen.fircrest.net 3.0-CURRENT FreeBSD 3.0-CURRENT #9: Sun Dec 6 11:52:59 PST 1998 jmg@hydrogen.fircrest.net:/a/home/johng/FreeBSD-checkout/30r/sys/compile/hydrogen i386
and the kernel has been built with these files:
tcp.h: $Id: tcp.h,v 1.10 1998/07/13 11:09:51 bde Exp $
tcp_debug.c: $Id: tcp_debug.c,v 1.13 1998/08/17 01:05:25 bde Exp $
tcp_debug.h: $Id: tcp_debug.h,v 1.7 1997/02/22 09:41:37 peter Exp $
tcp_fsm.h: $Id: tcp_fsm.h,v 1.10 1997/08/16 19:15:38 wollman Exp $
tcp_input.c: $Id: tcp_input.c,v 1.81 1998/09/11 16:04:03 wollman Exp $
tcp_output.c: $Id: tcp_output.c,v 1.31 1998/07/13 11:53:59 bde Exp $
tcp_seq.h: $Id: tcp_seq.h,v 1.8 1997/02/22 09:41:41 peter Exp $
tcp_subr.c: $Id: tcp_subr.c,v 1.47 1998/09/06 08:17:35 phk Exp $
tcp_timer.c: $Id: tcp_timer.c,v 1.28 1998/04/24 09:25:35 dg Exp $
tcp_timer.h: $Id: tcp_timer.h,v 1.13 1997/09/07 05:26:48 bde Exp $
tcp_usrreq.c: $Id: tcp_usrreq.c,v 1.38 1998/08/23 03:07:15 wollman Exp $
tcp_var.h: $Id: tcp_var.h,v 1.48 1998/08/24 07:47:39 dfr Exp $
tcpip.h: $Id: tcpip.h,v 1.7 1998/09/26 14:26:59 dfr Exp $
--
John-Mark Gurney Voice: +1 541 684 8449
Cu Networking P.O. Box 5693, 97405
Live in Peace, destroy Micro$oft, support free software, run FreeBSD
Don't trust anyone you don't have the source for
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Sun Jan 24 17:04:06 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id RAA18424
for freebsd-current-outgoing; Sun, 24 Jan 1999 17:04:06 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from nlsystems.com (nlsys.demon.co.uk [158.152.125.33])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA18377
for <current@freebsd.org>; Sun, 24 Jan 1999 17:04:01 -0800 (PST)
(envelope-from dfr@nlsystems.com)
Received: from localhost (dfr@localhost)
by nlsystems.com (8.9.1/8.8.5) with SMTP id BAA82249;
Mon, 25 Jan 1999 01:05:29 GMT
Date: Mon, 25 Jan 1999 01:05:29 +0000 (GMT)
From: Doug Rabson <dfr@nlsystems.com>
To: Archie Cobbs <archie@whistle.com>
cc: Julian Elischer <julian@whistle.com>, wollman@khavrinen.lcs.mit.edu,
current@FreeBSD.ORG
Subject: Re: kvm question
In-Reply-To: <199901242130.NAA21377@bubba.whistle.com>
Message-ID: <Pine.BSF.4.01.9901250102560.59627-100000@herring.nlsystems.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
On Sun, 24 Jan 1999, Archie Cobbs wrote:
> Julian Elischer writes:
> > As soon as someone modifies sysctl to work with KLD modules....
> > that would be a reasonable suggestion
> >
> > On Sun, 24 Jan 1999, Garrett Wollman wrote:
> > > > I ran into an interesting problem in the process of modifying
> > > > "netstat" to understand the PF_NETGRAPH protocol family. "netstat"
> > > > uses kvm_read(), etc. to read kernel symbols. However, this doesn't
> > >
> > > Don't do that. Use sysctl, that's what it's there for.
> > >
> > > -GAWollman
>
> Julian is of course correct... but Garrett you missed my point...
>
> Forget netstat for a second. The question is simply, "I'm offering
> to fix libkvm to understand KLD modules; is anybody interested?"
>
> Whether libkvm should even exist in a perfect world (it shouldn't)
> is an entirely different question. For now, we're stuck with it
> until somebody changes *everything* to use sysctl instead.
I've been hacking all evening on sysctl. I have a scheme using SLISTs to
store the contents of a SYSCTL_NODE and SYSINIT to register the oids. It
should work well when I finish debugging it but there is a cost of
2*sizeof(void*) per sysctl entry.
--
Doug Rabson Mail: dfr@nlsystems.com
Nonlinear Systems Ltd. Phone: +44 181 442 9037
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Sun Jan 24 17:04:32 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id RAA18474
for freebsd-current-outgoing; Sun, 24 Jan 1999 17:04:32 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from wat-border.sentex.ca (sentex-uu.sentex.ca [209.167.167.178])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA18463
for <current@freebsd.org>; Sun, 24 Jan 1999 17:04:30 -0800 (PST)
(envelope-from mike@sentex.net)
Received: from gravel (ospf-wat.sentex.net [209.167.248.81])
by wat-border.sentex.ca (8.8.8/8.8.8) with SMTP id UAA08884
for <current@freebsd.org>; Sun, 24 Jan 1999 20:04:16 -0500 (EST)
(envelope-from mike@sentex.net)
Message-Id: <3.0.5.32.19990124201113.02d384f0@granite.sentex.ca>
X-Sender: mdtancsa@granite.sentex.ca
X-Mailer: QUALCOMM Windows Eudora Pro Version 3.0.5 (32)
Date: Sun, 24 Jan 1999 20:11:13 -0500
To: current@FreeBSD.ORG
From: Mike Tancsa <mike@sentex.net>
Subject: reading BIOS environmental vars
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
Is there any way to read some of the newer BIOS features such as CPU temp.,
fan status etc ? Is this even a standardize BIOS feature set ?
---Mike
**********************************************************************
Mike Tancsa, Network Admin * mike@sentex.net
Sentex Communications Corp, * http://www.sentex.net/mike
Cambridge, Ontario * 01.519.651.3400
Canada *
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Sun Jan 24 17:11:50 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id RAA19219
for freebsd-current-outgoing; Sun, 24 Jan 1999 17:11:50 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA19214
for <current@FreeBSD.ORG>; Sun, 24 Jan 1999 17:11:49 -0800 (PST)
(envelope-from dillon@apollo.backplane.com)
Received: (from dillon@localhost)
by apollo.backplane.com (8.9.2/8.9.1) id RAA09508;
Sun, 24 Jan 1999 17:11:19 -0800 (PST)
(envelope-from dillon)
Date: Sun, 24 Jan 1999 17:11:19 -0800 (PST)
From: Matthew Dillon <dillon@apollo.backplane.com>
Message-Id: <199901250111.RAA09508@apollo.backplane.com>
To: Mike Smith <mike@smith.net.au>
Cc: Garrett Wollman <wollman@khavrinen.lcs.mit.edu>,
Mike Smith <mike@smith.net.au>, current@FreeBSD.ORG
Subject: Re: sysctl oids (was: Re: kvm question)
References: <199901250041.QAA06023@dingo.cdrom.com>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
:> > not numbered. OID_AUTO is bogus because it perpetuates the numbering
:> > of nodes.
:>
:> Nonsense. There are plenty of contexts in which a number makes far
:> more sense than a name -- pretty much anything in any network stack
:> other than Chaosnet, for example. If any of us ever make good on the
:> threat of SNMP integration, having fixed numerical identifiers will be
:> a requirement.
:
:A number can be a name, but a name not a number. It's obvious that
:enumerated objects need numeric identifiers, but not desirable to
:mandate the existence of numbers to match all names.
:
:Unless you want the IANA to step in of course.
... actually, a name *CAN* be a number. You simply compute a 64 bit
CRC on the name. The chance of collision is vanishingly small --
for reference:
http://www.backplane.com/diablo/crc64.html
-Matt
Matthew Dillon
<dillon@backplane.com>
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Sun Jan 24 17:30:14 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id RAA22049
for freebsd-current-outgoing; Sun, 24 Jan 1999 17:30:14 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from pc2-c804.uibk.ac.at (pc2-c804.uibk.ac.at [138.232.82.17])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA22024
for <freebsd-current@freebsd.org>; Sun, 24 Jan 1999 17:30:11 -0800 (PST)
(envelope-from fatal@pc2-c804.uibk.ac.at)
Received: (from fatal@localhost)
by pc2-c804.uibk.ac.at (8.8.6/8.8.6) id DAA27263
for freebsd-current@freebsd.org; Mon, 25 Jan 1999 03:39:57 +0100
From: Marco van Hylckama Vlieg <fatal@pc2-c804.uibk.ac.at>
Message-Id: <199901250239.DAA27263@pc2-c804.uibk.ac.at>
Subject: 3.0-CURRENT -> RELENG_3: trouble ?
To: freebsd-current@FreeBSD.ORG
Date: Mon, 25 Jan 1999 03:39:57 +0100 (MET)
Reply-To: "Marco van Hylckama Vlieg" <marco@windowmaker.org>
X-Mailer: ELM [version 2.4 PL25]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
Hello all,
I'm running 3.0-CURRENT at the moment, last timme I built world is
about 2 or 3 weeks ago I guess. What I want to do is go to 3.0-RELEASE
and from then start keeping track of the 3.x-STABLE branch.
Since I've read a lot about various problems people had with this
I now wonder: is it safe to CVSUP to RELENG_3 right now or will bad
things happen? I don't want to mess up my system.
If someone could give me some guidelines on how to get going on the
above described track or point me to a webpage/document or anything else
that describes what to do I'd be eternally grateful. At the moment it's
very unclear to me what to do and whether I'll be able to boot and/or
login to my system after I went to RELENG_3.
I'm running 3.0-CURRENT with everything ELF including the kernel.
Any assistance is highly appreciated,
Regards,
Marco
--
QQWT!"^""9QQQ ------------------------------------------------
QP' _%7? WindowMaker, the choice of a GNUstep Generation.
P WQQ, http://www.windowmaker.org/
' mWQh Marco's WindowMaker icons:
.__s_QWQQ http://marco.shada.com/wmaker/
. ]QQQQQQQ@
L )WQQQQQQ( Marco van Hylckama Vlieg
!`_ajQQQQQ@( marco@windowmaker.org
"?TUVY"` ------------------------------------------------
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Sun Jan 24 17:31:12 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id RAA22255
for freebsd-current-outgoing; Sun, 24 Jan 1999 17:31:12 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA22246
for <current@FreeBSD.ORG>; Sun, 24 Jan 1999 17:31:11 -0800 (PST)
(envelope-from jdp@polstra.com)
Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13])
by wall.polstra.com (8.9.1/8.9.1) with ESMTP id RAA10998;
Sun, 24 Jan 1999 17:30:58 -0800 (PST)
(envelope-from jdp@polstra.com)
Received: (from jdp@localhost)
by vashon.polstra.com (8.9.1/8.9.1) id RAA18030;
Sun, 24 Jan 1999 17:30:53 -0800 (PST)
(envelope-from jdp@polstra.com)
Message-ID: <XFMail.990124173053.jdp@polstra.com>
X-Mailer: XFMail 1.3 [p0] on FreeBSD
X-Priority: 3 (Normal)
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 8bit
MIME-Version: 1.0
In-Reply-To: <Pine.BSF.4.05.9901240124310.55154-100000@bright.fx.genx.net>
Date: Sun, 24 Jan 1999 17:30:53 -0800 (PST)
Organization: Polstra & Co., Inc.
From: John Polstra <jdp@polstra.com>
To: Alfred Perlstein <bright@hotjobs.com>
Subject: Re: Death to LKM screen savers? (was: Re: HEADS UP: i386 a.out L
Cc: current@FreeBSD.ORG
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
On 24-Jan-99 Alfred Perlstein wrote:
> On Sat, 23 Jan 1999, Mike Smith wrote:
>
>> Finally, why not just use a local repository you weenie? 8)
>
> Because, certain other weenies :) have web pages up on
> http://www.freebsd.org/handbook that don't explain how to do this, and
> aren't very clear on the topics that ARE discussed. :)
You've got a lot to learn if you think this kind of unconstructive
slap in the face is going to inspire or motivate anybody.
---
John Polstra jdp@polstra.com
John D. Polstra & Co., Inc. Seattle, Washington USA
"Nobody ever went broke underestimating the taste of the American public."
-- H. L. Mencken
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Sun Jan 24 17:36:11 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id RAA22812
for freebsd-current-outgoing; Sun, 24 Jan 1999 17:36:11 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from dingo.cdrom.com (castles154.castles.com [208.214.165.154])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA22807
for <current@FreeBSD.ORG>; Sun, 24 Jan 1999 17:36:09 -0800 (PST)
(envelope-from mike@dingo.cdrom.com)
Received: from dingo.cdrom.com (LOCALHOST [127.0.0.1])
by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id RAA06299;
Sun, 24 Jan 1999 17:32:14 -0800 (PST)
(envelope-from mike@dingo.cdrom.com)
Message-Id: <199901250132.RAA06299@dingo.cdrom.com>
X-Mailer: exmh version 2.0.2 2/24/98
To: John Polstra <jdp@polstra.com>
cc: Alfred Perlstein <bright@hotjobs.com>, current@FreeBSD.ORG
Subject: Re: Death to LKM screen savers? (was: Re: HEADS UP: i386 a.out L
In-reply-to: Your message of "Sun, 24 Jan 1999 17:30:53 PST."
<XFMail.990124173053.jdp@polstra.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Sun, 24 Jan 1999 17:32:13 -0800
From: Mike Smith <mike@smith.net.au>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
>
> On 24-Jan-99 Alfred Perlstein wrote:
> > On Sat, 23 Jan 1999, Mike Smith wrote:
> >
> >> Finally, why not just use a local repository you weenie? 8)
> >
> > Because, certain other weenies :) have web pages up on
> > http://www.freebsd.org/handbook that don't explain how to do this, and
> > aren't very clear on the topics that ARE discussed. :)
>
> You've got a lot to learn if you think this kind of unconstructive
> slap in the face is going to inspire or motivate anybody.
This probably should have been a private mail; it requires IRC context
before it's clear.
Alfred was having some conceptual difficulties with the CVS repository
concept; I think he's got it sorted out now. I'm not sure whether it
was a documentation issue or just a stubborn idea-firewall.
--
\\ Sometimes you're ahead, \\ Mike Smith
\\ sometimes you're behind. \\ mike@smith.net.au
\\ The race is long, and in the \\ msmith@freebsd.org
\\ end it's only with yourself. \\ msmith@cdrom.com
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Sun Jan 24 17:43:41 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id RAA23709
for freebsd-current-outgoing; Sun, 24 Jan 1999 17:43:41 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from whistle.com (s205m131.whistle.com [207.76.205.131])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA23704
for <current@FreeBSD.ORG>; Sun, 24 Jan 1999 17:43:39 -0800 (PST)
(envelope-from archie@whistle.com)
Received: (from smap@localhost) by whistle.com (8.7.5/8.6.12) id RAA02748; Sun, 24 Jan 1999 17:42:15 -0800 (PST)
Received: from bubba.whistle.com( 207.76.205.7) by whistle.com via smap (V2.0)
id xma002746; Sun, 24 Jan 99 17:41:59 -0800
Received: (from archie@localhost) by bubba.whistle.com (8.8.7/8.6.12) id RAA23396; Sun, 24 Jan 1999 17:41:59 -0800 (PST)
From: Archie Cobbs <archie@whistle.com>
Message-Id: <199901250141.RAA23396@bubba.whistle.com>
Subject: Re: sysctl oids (was: Re: kvm question)
In-Reply-To: <Pine.BSF.3.95.990124140935.6880C-100000@current1.whistle.com> from Julian Elischer at "Jan 24, 99 02:15:08 pm"
To: julian@whistle.com (Julian Elischer)
Date: Sun, 24 Jan 1999 17:41:59 -0800 (PST)
Cc: wollman@khavrinen.lcs.mit.edu, mike@smith.net.au, current@FreeBSD.ORG
X-Mailer: ELM [version 2.4ME+ PL38 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
Julian Elischer writes:
> That is at least my opinion.. you may and do disagree. I guess you will
> say that numbers are just as dynamic, etc.etc. well I just think that in
> the REAL WORLD, as opposed to the theoretical world, names (which require
> no co-ordination between authors), are a better choice than numbers,
> which require some central naming authority.
A "real world" example of this is the idea of dynamically registered
tty line disciplines. Line disciplines are identified by hard-wired
constant integers (sys/ttycom.h):
#define TTYDISC 0 /* termios tty line discipline */
#define TABLDISC 3 /* tablet discipline */
#define SLIPDISC 4 /* serial IP discipline */
#define PPPDISC 5 /* PPP discipline */
A KLD can dynamically register a new line discipline. But guess
what? There's no way for your user program to easily figure out
what number it got. It will vary depending on what other line
disciplines are registered.
If instead line disciplines were identified by strings, like "tty",
"ppp", "slip", etc. then this problem would be a lot easier.
-Archie
___________________________________________________________________________
Archie Cobbs * Whistle Communications, Inc. * http://www.whistle.com
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Sun Jan 24 17:47:40 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id RAA24164
for freebsd-current-outgoing; Sun, 24 Jan 1999 17:47:40 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from ns.mt.sri.com (sri-gw.MT.net [206.127.105.141])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA24158
for <current@FreeBSD.ORG>; Sun, 24 Jan 1999 17:47:38 -0800 (PST)
(envelope-from nate@mt.sri.com)
Received: from mt.sri.com (rocky.mt.sri.com [206.127.76.100])
by ns.mt.sri.com (8.8.8/8.8.8) with SMTP id SAA06164;
Sun, 24 Jan 1999 18:47:24 -0700 (MST)
(envelope-from nate@rocky.mt.sri.com)
Received: by mt.sri.com (SMI-8.6/SMI-SVR4)
id SAA03468; Sun, 24 Jan 1999 18:47:23 -0700
Date: Sun, 24 Jan 1999 18:47:23 -0700
Message-Id: <199901250147.SAA03468@mt.sri.com>
From: Nate Williams <nate@mt.sri.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
To: Archie Cobbs <archie@whistle.com>
Cc: jkh@zippy.cdrom.com (Jordan K. Hubbard), current@FreeBSD.ORG
Subject: Re: 4.0-Current, netscape halts system
In-Reply-To: <199901250020.QAA22590@bubba.whistle.com>
References: <1476.917220230@zippy.cdrom.com>
<199901250020.QAA22590@bubba.whistle.com>
X-Mailer: VM 6.34 under 19.16 "Lille" XEmacs Lucid
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
> > I really don't understand the problems that everyone is having,
> > myself. I've been running netscape (communicator 4.5) in -current for
> > ages now and just switched to 4.0 without any problems. My netscape
> > still continues to function just fine and has never crashed any of
> > my system so much as once.
> >
> > Why the wide disparity in experience, I wonder?
>
> Do you ever run Java applets? Netscape 4.5 seems to work fine
> until running Java, which kicks off some sort of time bomb.
> Death is not immediate, but it is guaranteed.
Agreed. However, I disabled Java, and I can also get death anytime I
try to download a file using netscape. Not fun.
In the interim I'm back to using 3.07, which is rock-solid but doesn't
support all of the java that I'd like it to. ;(
Nate
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Sun Jan 24 18:00:10 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id SAA26261
for freebsd-current-outgoing; Sun, 24 Jan 1999 18:00:10 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from mail.atl.bellsouth.net (mail.atl.bellsouth.net [205.152.0.21])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA26243
for <freebsd-current@FreeBSD.ORG>; Sun, 24 Jan 1999 18:00:06 -0800 (PST)
(envelope-from wghicks@bellsouth.net)
Received: from wghicks.bellsouth.net (root@host-209-214-77-43.atl.bellsouth.net [209.214.77.43])
by mail.atl.bellsouth.net (8.8.8-spamdog/8.8.5) with ESMTP id UAA25648;
Sun, 24 Jan 1999 20:59:45 -0500 (EST)
Received: from localhost (wghicks@localhost [127.0.0.1])
by wghicks.bellsouth.net (8.9.2/8.9.2) with ESMTP id VAA77856;
Sun, 24 Jan 1999 21:16:20 -0500 (EST)
(envelope-from wghicks@wghicks.bellsouth.net)
To: marco@windowmaker.org, fatal@pc2-c804.uibk.ac.at
Cc: freebsd-current@FreeBSD.ORG
Subject: Re: 3.0-CURRENT -> RELENG_3: trouble ?
In-Reply-To: Your message of "Mon, 25 Jan 1999 03:39:57 +0100 (MET)"
<199901250239.DAA27263@pc2-c804.uibk.ac.at>
References: <199901250239.DAA27263@pc2-c804.uibk.ac.at>
X-Mailer: Mew version 1.93 on XEmacs 20.4 (Emerald)
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-Id: <19990124211620H.wghicks@wghicks.bellsouth.net>
Date: Sun, 24 Jan 1999 21:16:20 -0500
From: W Gerald Hicks <wghicks@bellsouth.net>
X-Dispatcher: imput version 980905(IM100)
Lines: 66
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
From: Marco van Hylckama Vlieg <fatal@pc2-c804.uibk.ac.at>
Subject: 3.0-CURRENT -> RELENG_3: trouble ?
Date: Mon, 25 Jan 1999 03:39:57 +0100 (MET)
> Hello all,
>
> I'm running 3.0-CURRENT at the moment, last timme I built world is
> about 2 or 3 weeks ago I guess. What I want to do is go to 3.0-RELEASE
> and from then start keeping track of the 3.x-STABLE branch.
Careful... making world can be addictive :-)
Your system would have been built before the split, so this will be
a simple update for you. It can be more difficult trying to move
backwards.
>
> Since I've read a lot about various problems people had with this
> I now wonder: is it safe to CVSUP to RELENG_3 right now or will bad
> things happen? I don't want to mess up my system.
The -stable branch seems to be what's advertised; so far I haven't
endured any problems at all.
>
> If someone could give me some guidelines on how to get going on the
> above described track or point me to a webpage/document or anything else
> that describes what to do I'd be eternally grateful. At the moment it's
> very unclear to me what to do and whether I'll be able to boot and/or
> login to my system after I went to RELENG_3.
>
Not much, I'd recommend getting friendly with mergemaster:
/usr/ports/sysutils/mergemaster
This script helps with manually updating any possible changes to
/etc Most often, on -stable, there aren't any.
You'll need to change a line in your cvsupfile from 'tag=.' to
'tag=RELENG_3'
I usually do a 'make buildworld' in multi-user mode then shutdown
to single user mode to do a 'make installworld' and rebuild and
install a new kernel before rebooting.
Over here, we prefer to use the cvsup-mirror port to maintain a
local repository. The major advantages include having the repository
metadata available locally along the ability to mirror the mail
archives.
>From there, you can either run cvsup against your local cvsupd or
use standard CVS commands. I prefer the latter, but the former
is faster.
> I'm running 3.0-CURRENT with everything ELF including the kernel.
>
> Any assistance is highly appreciated,
It shouldn't offer you any surprises...
Good Luck,
Jerry Hicks
wghicks@bellsouth.net
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Sun Jan 24 18:05:45 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id SAA26827
for freebsd-current-outgoing; Sun, 24 Jan 1999 18:05:45 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from vanessa.eliuk.org (pme210.sunshine.net [209.17.178.210])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA26818
for <current@FreeBSD.ORG>; Sun, 24 Jan 1999 18:05:42 -0800 (PST)
(envelope-from kevin_eliuk@sunshine.net)
Received: from localhost (cagey@localhost)
by vanessa.eliuk.org (8.9.2/8.9.2) with ESMTP id SAA00247
for <current@FreeBSD.ORG>; Sun, 24 Jan 1999 18:04:44 -0800 (PST)
(envelope-from cagey@vanessa.eliuk.org)
Date: Sun, 24 Jan 1999 18:04:44 -0800 (PST)
From: "Kevin G. Eliuk" <kevin_eliuk@sunshine.net>
Reply-To: "Kevin G. Eliuk" <kevin_eliuk@sunshine.net>
To: current@FreeBSD.ORG
Subject: Date going ahead by one year.
Message-ID: <Pine.BSF.4.05.9901241740170.462-100000@vanessa.eliuk.org>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
Hello,
This may be just a chance occurance although I recall some posting in
the last day regarding the date being changed when rebooting, so I
thought I would post.
Rebooted my machine after letting others near the box and upon starting
pine it was asking whether I wanted to save my sent mail. Upon
checking, my date was out by one year:
vanessa# date
Mon Jan 24 17:36:23 PST 2000
vanessa# ntpdate timelord.uregina.ca
24 Jan 17:37:33 ntpdate: step time server 142.3.100.15 offset \
-31536003.762284
vanessa# date
Sun Jan 24 17:37:41 PST 1999
Hopefully this is not worth mentioning, but it occurs that it may be
something, and that if it is a bug, may have been overlooked with all
the alerts that were posted today.
If not <blush> ...
--
Regards,
Kevin G. Eliuk
Discover Rock Solid, Discover FreeBSD | http://www.FreeBSD.Org
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Sun Jan 24 18:54:45 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id SAA02116
for freebsd-current-outgoing; Sun, 24 Jan 1999 18:54:45 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.26.10.9])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA02111
for <current@FreeBSD.ORG>; Sun, 24 Jan 1999 18:54:42 -0800 (PST)
(envelope-from bde@godzilla.zeta.org.au)
Received: (from bde@localhost)
by godzilla.zeta.org.au (8.8.7/8.8.7) id NAA05292;
Mon, 25 Jan 1999 13:54:17 +1100
Date: Mon, 25 Jan 1999 13:54:17 +1100
From: Bruce Evans <bde@zeta.org.au>
Message-Id: <199901250254.NAA05292@godzilla.zeta.org.au>
To: mike@smith.net.au, wollman@khavrinen.lcs.mit.edu
Subject: Re: kvm question
Cc: archie@whistle.com, current@FreeBSD.ORG
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
>Backwards compatibility is one thing, but new nodes should be named,
>not numbered. OID_AUTO is bogus because it perpetuates the numbering
>of nodes.
OID_AUTO is not bogus. It is just an implementation detail.
The sysctl data structures have to have a place to put a number for
old-style numbered sysctls, and you put OID_AUTO in that place when
you don't want a number.
Bruce
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Sun Jan 24 19:31:55 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id TAA05797
for freebsd-current-outgoing; Sun, 24 Jan 1999 19:31:55 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from bright.fx.genx.net (bright.fx.genx.net [206.64.4.154])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA05792
for <current@FreeBSD.ORG>; Sun, 24 Jan 1999 19:31:53 -0800 (PST)
(envelope-from bright@hotjobs.com)
Received: from localhost (bright@localhost)
by bright.fx.genx.net (8.9.1/8.9.1) with ESMTP id WAA00877;
Sun, 24 Jan 1999 22:37:49 -0500 (EST)
(envelope-from bright@hotjobs.com)
X-Authentication-Warning: bright.fx.genx.net: bright owned process doing -bs
Date: Sun, 24 Jan 1999 22:37:49 -0500 (EST)
From: Alfred Perlstein <bright@hotjobs.com>
X-Sender: bright@bright.fx.genx.net
To: Mike Smith <mike@smith.net.au>
cc: John Polstra <jdp@polstra.com>, current@FreeBSD.ORG
Subject: Re: Death to LKM screen savers? (was: Re: HEADS UP: i386 a.out L
In-Reply-To: <199901250132.RAA06299@dingo.cdrom.com>
Message-ID: <Pine.BSF.4.05.9901242222270.55154-100000@bright.fx.genx.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
On Sun, 24 Jan 1999, Mike Smith wrote:
> > >> Finally, why not just use a local repository you weenie? 8)
> > >
> > > Because, certain other weenies :) have web pages up on
> > > http://www.freebsd.org/handbook that don't explain how to do this, and
> > > aren't very clear on the topics that ARE discussed. :)
> >
> > You've got a lot to learn if you think this kind of unconstructive
> > slap in the face is going to inspire or motivate anybody.
>
> This probably should have been a private mail; it requires IRC context
> before it's clear.
>
> Alfred was having some conceptual difficulties with the CVS repository
> concept; I think he's got it sorted out now. I'm not sure whether it
> was a documentation issue or just a stubborn idea-firewall.
Combination of cluelessness, newbieness to cvs/rccs, and a headcold, all
*my* fault. I apologize, and thank you for the help via IRC.
I couldn't figure out that you can use cvsup to grab the repo, then
use plain 'ol cvs from that. Now i'm well on my way into 'make
release'.
thanks a lot,
-Alfred
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Sun Jan 24 19:43:17 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id TAA06587
for freebsd-current-outgoing; Sun, 24 Jan 1999 19:43:17 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from mail.atl.bellsouth.net (mail.atl.bellsouth.net [205.152.0.21])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA06467
for <current@FreeBSD.ORG>; Sun, 24 Jan 1999 19:43:15 -0800 (PST)
(envelope-from wghicks@bellsouth.net)
Received: from wghicks.bellsouth.net (root@host-209-214-77-43.atl.bellsouth.net [209.214.77.43])
by mail.atl.bellsouth.net (8.8.8-spamdog/8.8.5) with ESMTP id WAA16896;
Sun, 24 Jan 1999 22:43:01 -0500 (EST)
Received: from localhost (wghicks@localhost [127.0.0.1])
by wghicks.bellsouth.net (8.9.2/8.9.2) with ESMTP id WAA52496;
Sun, 24 Jan 1999 22:59:37 -0500 (EST)
(envelope-from wghicks@wghicks.bellsouth.net)
To: bright@hotjobs.com
Cc: current@FreeBSD.ORG
Subject: Re: Death to LKM screen savers? (was: Re: HEADS UP: i386 a.out L
In-Reply-To: Your message of "Sun, 24 Jan 1999 22:37:49 -0500 (EST)"
<Pine.BSF.4.05.9901242222270.55154-100000@bright.fx.genx.net>
References: <Pine.BSF.4.05.9901242222270.55154-100000@bright.fx.genx.net>
X-Mailer: Mew version 1.93 on XEmacs 20.4 (Emerald)
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-Id: <19990124225936P.wghicks@wghicks.bellsouth.net>
Date: Sun, 24 Jan 1999 22:59:36 -0500
From: W Gerald Hicks <wghicks@bellsouth.net>
X-Dispatcher: imput version 980905(IM100)
Lines: 20
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
From: Alfred Perlstein <bright@hotjobs.com>
> I couldn't figure out that you can use cvsup to grab the repo, then
> use plain 'ol cvs from that. Now i'm well on my way into 'make
> release'.
And if you have cvsup-mirror loaded (running cvsupd), you can even use
cvsup against your local repository.
Seems a good bit faster than regular CVS for checkouts and updates.
Cheers,
Jerry Hicks
wghicks@bellsouth.net
>
> thanks a lot,
> -Alfred
>
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Sun Jan 24 20:03:58 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id UAA08434
for freebsd-current-outgoing; Sun, 24 Jan 1999 20:03:58 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from dns.MexComUSA.NET (cm4094.cableco-op.com [208.138.40.94])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA08427
for <current@FreeBSD.ORG>; Sun, 24 Jan 1999 20:03:53 -0800 (PST)
(envelope-from eculp@MexComUSA.net)
Received: from MexComUSA.net (cm4094.cableco-op.com [208.138.40.94])
by dns.MexComUSA.NET (8.9.2/8.9.1) with ESMTP id UAA97853;
Sun, 24 Jan 1999 20:03:34 -0800 (PST)
(envelope-from eculp@MexComUSA.net)
Message-ID: <36ABED16.111D4ACB@MexComUSA.net>
Date: Sun, 24 Jan 1999 20:03:34 -0800
From: Edwin Culp <eculp@MexComUSA.net>
Organization: Mexico Communicates, S.C.
X-Mailer: Mozilla 4.5 [en] (X11; I; FreeBSD 4.0-CURRENT i386)
X-Accept-Language: en
MIME-Version: 1.0
To: Nate Williams <nate@mt.sri.com>
CC: current@FreeBSD.ORG
Subject: Re: 4.0-Current, netscape halts system
References: <1476.917220230@zippy.cdrom.com>
<199901250020.QAA22590@bubba.whistle.com> <199901250147.SAA03468@mt.sri.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
Nate Williams wrote:
> > > I really don't understand the problems that everyone is having,
> > > myself. I've been running netscape (communicator 4.5) in -current for
> > > ages now and just switched to 4.0 without any problems. My netscape
> > > still continues to function just fine and has never crashed any of
> > > my system so much as once.
> > >
> > > Why the wide disparity in experience, I wonder?
> >
> > Do you ever run Java applets? Netscape 4.5 seems to work fine
> > until running Java, which kicks off some sort of time bomb.
> > Death is not immediate, but it is guaranteed.
>
> Agreed. However, I disabled Java, and I can also get death anytime I
> try to download a file using netscape. Not fun.
>
> In the interim I'm back to using 3.07, which is rock-solid but doesn't
> support all of the java that I'd like it to. ;(
>
> Nate
>
I am current as of today 4.0, I have communicator 4.5 downloaded some time
ago (November more or less) directly from netscape and installed in
/usr/local/netscape with a link to /usr/local/bin/netscape and I have been
using it all day with no problems. My intranet if full of java and haven't
had a problem, knock on wood:-) I just downloaded a 9M file after reading
your mail to see if that would cause a problem and it didn't. Netscape is
"as stable as ever" on FreeBSD Current 4.0 for me. That bothers me:-) I
wonder why?
ed
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Sun Jan 24 20:05:03 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id UAA08770
for freebsd-current-outgoing; Sun, 24 Jan 1999 20:05:03 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from kot.ne.mediaone.net (kot.ne.mediaone.net [24.128.29.136])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA08757
for <current@freebsd.org>; Sun, 24 Jan 1999 20:05:01 -0800 (PST)
(envelope-from mi@kot.ne.mediaone.net)
Received: (from mi@localhost)
by kot.ne.mediaone.net (8.9.1a/8.9.1) id XAA05780
for current@freebsd.org; Sun, 24 Jan 1999 23:04:34 -0500 (EST)
From: Mikhail Teterin <mi@kot.ne.mediaone.net>
Message-Id: <199901250404.XAA05780@kot.ne.mediaone.net>
Subject: Re: sysctl oids (was: Re: kvm question)
In-Reply-To: <199901250043.QAA06042@dingo.cdrom.com> from Mike Smith at "Jan 24, 1999 04:43:12 pm"
To: current@FreeBSD.ORG
Date: Sun, 24 Jan 1999 23:04:34 -0500 (EST)
X-Face: %UW#n0|w>ydeGt/b@1-.UFP=K^~-:0f#O:D7w<gv/&E-lL7twZCT8B~/PA4|\t$ti+22K">
hJ5G_<5143Bb3kOIs9XpX+"V+~$adGP:J|SLieM31VIhqXeLBli"<kcG^EOVih
y+z3/UR{6SCQ
X-Mailer: ELM [version 2.4ME+ PL49 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
Mike Smith once stated:
=OTOH, you should consider going back to single-character directory
=names, since that's much more significant.
a) this will limit the number of directories to you-know-what
b) this will inconvinience a _user_ rather then a _programmer_,
for whom writing efficient code is an exciting challenge in
itself :)
-mi
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Sun Jan 24 20:19:56 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id UAA10769
for freebsd-current-outgoing; Sun, 24 Jan 1999 20:19:56 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA10752
for <current@FreeBSD.ORG>; Sun, 24 Jan 1999 20:19:49 -0800 (PST)
(envelope-from dillon@apollo.backplane.com)
Received: (from dillon@localhost)
by apollo.backplane.com (8.9.2/8.9.1) id UAA00493;
Sun, 24 Jan 1999 20:19:33 -0800 (PST)
(envelope-from dillon)
Date: Sun, 24 Jan 1999 20:19:33 -0800 (PST)
From: Matthew Dillon <dillon@apollo.backplane.com>
Message-Id: <199901250419.UAA00493@apollo.backplane.com>
To: current@FreeBSD.ORG
Subject: IDE DMA works, I'll be a...
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
Well I'll be a cat in a hat! IDE DMA actually works on my old
PPro-200 box with a new IDE drive! A solid 8 MBytes/sec out of the
thing. My poor old 4 GB SCSI barracuda could only do 4.3 MB/sec.
Time to replace the barracuda, I think.
It doesn't work on my CTX box, though - heh. Quantity verses Quality,
I guess. The CTX box was ~$1K 3 months ago while my PPro box was ~$3K
a year and a half ago.
-Matt
Matthew Dillon
<dillon@backplane.com>
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Sun Jan 24 20:23:42 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id UAA11243
for freebsd-current-outgoing; Sun, 24 Jan 1999 20:23:42 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from rip.psg.com (rip.psg.com [147.28.0.39])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA11236
for <freebsd-current@FreeBSD.ORG>; Sun, 24 Jan 1999 20:23:41 -0800 (PST)
(envelope-from randy@psg.com)
Received: from localhost (1408 bytes) by rip.psg.com
via sendmail with P:stdio/R:inet_resolve/T:smtp
(sender: <randy>) (ident <randy> using unix)
id <m104dYf-0008G4C@rip.psg.com>
for <freebsd-current@FreeBSD.ORG>; Sun, 24 Jan 1999 20:23:29 -0800 (PST)
(Smail-3.2.0.101 1997-Dec-17 #1 built 1998-Oct-13)
Message-Id: <m104dYf-0008G4C@rip.psg.com>
Date: Sun, 24 Jan 1999 20:23:29 -0800 (PST)
From: Randy Bush <randy@psg.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
To: Mark Murray <mark@grondar.za>
Cc: freebsd-current@FreeBSD.ORG
Subject: Re: make aout-to-elf-build failure
References: <m1047WH-0008G4C@rip.psg.com>
<199901231907.LAA16027@vashon.polstra.com>
<m104A3n-0008G4C@rip.psg.com>
<199901240817.KAA02681@greenpeace.grondar.za>
<m104NL6-0008G4C@rip.psg.com>
<199901241119.NAA03526@greenpeace.grondar.za>
<m104RJR-0008G4C@rip.psg.com>
<199901241537.RAA16096@greenpeace.grondar.za>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
>> /usr/obj/aout/usr/src/tmp/usr/libexec/elf/ld: warning: libcrypt.so.2, needed by /usr/obj/elf/usr/src/kerberosIV/libexec/kipd/../../lib/libkrb/libkrb.so, not found (try using --rpath)
>> /usr/obj/elf/usr/src/kerberosIV/libexec/kipd/../../lib/libkrb/libkrb.so: undefined reference to `crypt'
>> *** Error code 1
> Go to the right subdirectory (in this case
> /usr/src/kerberosIV/libexec/kipd/) and edit the Makefile; add
> -lcrypt to the end of the LDADD line. You may need to remove it
> later, but it will keep your build going. I'd be grateful for
> reports of places where this is necesary.
when i did all these, see previous msg, it all worked. i successfully went
from a pure aout 3.0-current of 981231 to 4.0-current of today.
your assistance was really appreciated.
randy
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Sun Jan 24 20:26:09 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id UAA11658
for freebsd-current-outgoing; Sun, 24 Jan 1999 20:26:09 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from st-lcremean.tidalwave.net (st-lcremean.tidalwave.net [208.213.203.186])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA11647
for <current@FreeBSD.ORG>; Sun, 24 Jan 1999 20:26:04 -0800 (PST)
(envelope-from lee@st-lcremean.tidalwave.net)
Received: (from lee@localhost)
by st-lcremean.tidalwave.net (8.9.2/8.9.2) id XAA01761;
Sun, 24 Jan 1999 23:25:43 -0500 (EST)
(envelope-from lee)
Message-ID: <19990124232542.A1754@tidalwave.net>
Date: Sun, 24 Jan 1999 23:25:42 -0500
From: Lee Cremeans <lee@st-lcremean.tidalwave.net>
To: Matthew Dillon <dillon@apollo.backplane.com>, current@FreeBSD.ORG
Subject: Re: IDE DMA works, I'll be a...
Reply-To: lcremean@tidalwave.net
References: <199901250419.UAA00493@apollo.backplane.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.93.2i
In-Reply-To: <199901250419.UAA00493@apollo.backplane.com>; from Matthew Dillon on Sun, Jan 24, 1999 at 08:19:33PM -0800
X-OS: FreeBSD 3.0-CURRENT
X-Evil: microsoft.com
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
On Sun, Jan 24, 1999 at 08:19:33PM -0800, Matthew Dillon wrote:
> It doesn't work on my CTX box, though - heh. Quantity verses Quality,
> I guess. The CTX box was ~$1K 3 months ago while my PPro box was ~$3K
> a year and a half ago.
Can you find out what chipset is in this guy? There's support for anything
Intel or VIA, Promise UDMA cards, Cyrix MediaGX, and Acer Aladdin IV/V right
now.
--
+--------------------------------------------------------------------+
| Lee Cremeans -- Manassas, VA, USA (WakkyMouse on DALnet and WTnet)|
| lcremean@tidalwave.net| http://st-lcremean.tidalwave.net/~lee |
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Sun Jan 24 20:32:21 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id UAA12164
for freebsd-current-outgoing; Sun, 24 Jan 1999 20:32:21 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA12159
for <current@FreeBSD.ORG>; Sun, 24 Jan 1999 20:32:19 -0800 (PST)
(envelope-from dillon@apollo.backplane.com)
Received: (from dillon@localhost)
by apollo.backplane.com (8.9.2/8.9.1) id UAA00610;
Sun, 24 Jan 1999 20:32:07 -0800 (PST)
(envelope-from dillon)
Date: Sun, 24 Jan 1999 20:32:07 -0800 (PST)
From: Matthew Dillon <dillon@apollo.backplane.com>
Message-Id: <199901250432.UAA00610@apollo.backplane.com>
To: current@FreeBSD.ORG
Subject: beginnings of a diskless boot sequence being committed
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
I'm going to commit a cleaned up version of my rc startup mods
to handle diskless BOOTP kernels, especially diskless BOOTP kernels
with read-only NFS mounts of / and /usr.
Basically this consists of a bit of code in /etc/rc and, later tonight,
an /etc/rc.diskless script ( a new script ).
-Matt
Matthew Dillon
<dillon@backplane.com>
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Sun Jan 24 20:35:02 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id UAA12559
for freebsd-current-outgoing; Sun, 24 Jan 1999 20:35:02 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA12525
for <current@FreeBSD.ORG>; Sun, 24 Jan 1999 20:35:00 -0800 (PST)
(envelope-from dillon@apollo.backplane.com)
Received: (from dillon@localhost)
by apollo.backplane.com (8.9.2/8.9.1) id UAA00625;
Sun, 24 Jan 1999 20:34:33 -0800 (PST)
(envelope-from dillon)
Date: Sun, 24 Jan 1999 20:34:33 -0800 (PST)
From: Matthew Dillon <dillon@apollo.backplane.com>
Message-Id: <199901250434.UAA00625@apollo.backplane.com>
To: Lee Cremeans <lee@st-lcremean.tidalwave.net>
Cc: current@FreeBSD.ORG
Subject: Re: IDE DMA works, I'll be a...
References: <199901250419.UAA00493@apollo.backplane.com> <19990124232542.A1754@tidalwave.net>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
:On Sun, Jan 24, 1999 at 08:19:33PM -0800, Matthew Dillon wrote:
:
:> It doesn't work on my CTX box, though - heh. Quantity verses Quality,
:> I guess. The CTX box was ~$1K 3 months ago while my PPro box was ~$3K
:> a year and a half ago.
:
:Can you find out what chipset is in this guy? There's support for anything
:Intel or VIA, Promise UDMA cards, Cyrix MediaGX, and Acer Aladdin IV/V right
:now.
I haven't cvs updated in 24 hours, if the Acer is newly committed then I'll
have to update again and retry. The CTX is using the Acer.
ide_pci0: <Acer Aladdin IV/V (M5229) Bus-master IDE controller> rev 0x20 int a irq 0 on pci0.11.0
wdc0 at 0x1f0-0x1f7 irq 14 flags 0xa0ffa0ff on isa
wdc0: unit 0 (wd0): <QUANTUM Bigfoot TX4.0AT>, 32-bit, multi-block-16
wd0: 3832MB (7849170 sectors), 8306 cyls, 15 heads, 63 S/T, 512 B/S
wdc1 at 0x170-0x177 irq 15 flags 0xa0ffa0ff on isa
wdc1: unit 0 (atapi): <ATAPI CDROM/V1.70>, removable, dma, iordy
-Matt
Matthew Dillon
<dillon@backplane.com>
:--
:+--------------------------------------------------------------------+
:| Lee Cremeans -- Manassas, VA, USA (WakkyMouse on DALnet and WTnet)|
:| lcremean@tidalwave.net| http://st-lcremean.tidalwave.net/~lee |
:
:
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Sun Jan 24 20:38:16 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id UAA13167
for freebsd-current-outgoing; Sun, 24 Jan 1999 20:38:16 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from st-lcremean.tidalwave.net (st-lcremean.tidalwave.net [208.213.203.186])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA13125
for <current@FreeBSD.ORG>; Sun, 24 Jan 1999 20:38:10 -0800 (PST)
(envelope-from lee@st-lcremean.tidalwave.net)
Received: (from lee@localhost)
by st-lcremean.tidalwave.net (8.9.2/8.9.2) id XAA01833;
Sun, 24 Jan 1999 23:37:49 -0500 (EST)
(envelope-from lee)
Message-ID: <19990124233749.A1816@tidalwave.net>
Date: Sun, 24 Jan 1999 23:37:49 -0500
From: Lee Cremeans <lee@st-lcremean.tidalwave.net>
To: Matthew Dillon <dillon@apollo.backplane.com>
Cc: current@FreeBSD.ORG
Subject: Re: IDE DMA works, I'll be a...
Reply-To: lcremean@tidalwave.net
References: <199901250419.UAA00493@apollo.backplane.com> <19990124232542.A1754@tidalwave.net> <199901250434.UAA00625@apollo.backplane.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.93.2i
In-Reply-To: <199901250434.UAA00625@apollo.backplane.com>; from Matthew Dillon on Sun, Jan 24, 1999 at 08:34:33PM -0800
X-OS: FreeBSD 3.0-CURRENT
X-Evil: microsoft.com
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
On Sun, Jan 24, 1999 at 08:34:33PM -0800, Matthew Dillon wrote:
>
> :On Sun, Jan 24, 1999 at 08:19:33PM -0800, Matthew Dillon wrote:
> :
> :> It doesn't work on my CTX box, though - heh. Quantity verses Quality,
> :> I guess. The CTX box was ~$1K 3 months ago while my PPro box was ~$3K
> :> a year and a half ago.
> :
> :Can you find out what chipset is in this guy? There's support for anything
> :Intel or VIA, Promise UDMA cards, Cyrix MediaGX, and Acer Aladdin IV/V right
> :now.
>
> I haven't cvs updated in 24 hours, if the Acer is newly committed then I'll
> have to update again and retry. The CTX is using the Acer.
>
> ide_pci0: <Acer Aladdin IV/V (M5229) Bus-master IDE controller> rev 0x20 int a irq 0 on pci0.11.0
^^^^^^^^^^^^^^^^^^^^^^^^
It's there...what symptoms are you seeing? Are you overclocking?
--
+--------------------------------------------------------------------+
| Lee Cremeans -- Manassas, VA, USA (WakkyMouse on DALnet and WTnet)|
| lcremean@tidalwave.net| http://st-lcremean.tidalwave.net/~lee |
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Sun Jan 24 20:53:54 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id UAA15407
for freebsd-current-outgoing; Sun, 24 Jan 1999 20:53:54 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA15398
for <current@FreeBSD.ORG>; Sun, 24 Jan 1999 20:53:52 -0800 (PST)
(envelope-from dillon@apollo.backplane.com)
Received: (from dillon@localhost)
by apollo.backplane.com (8.9.2/8.9.1) id UAA00799;
Sun, 24 Jan 1999 20:53:19 -0800 (PST)
(envelope-from dillon)
Date: Sun, 24 Jan 1999 20:53:19 -0800 (PST)
From: Matthew Dillon <dillon@apollo.backplane.com>
Message-Id: <199901250453.UAA00799@apollo.backplane.com>
To: Lee Cremeans <lee@st-lcremean.tidalwave.net>
Cc: current@FreeBSD.ORG
Subject: Re: IDE DMA works, I'll be a...
References: <199901250419.UAA00493@apollo.backplane.com> <19990124232542.A1754@tidalwave.net> <199901250434.UAA00625@apollo.backplane.com> <19990124233749.A1816@tidalwave.net>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
:> I haven't cvs updated in 24 hours, if the Acer is newly committed then I'll
:> have to update again and retry. The CTX is using the Acer.
:>
:> ide_pci0: <Acer Aladdin IV/V (M5229) Bus-master IDE controller> rev 0x20 int a irq 0 on pci0.11.0
: ^^^^^^^^^^^^^^^^^^^^^^^^
:
:It's there...what symptoms are you seeing? Are you overclocking?
:--
:+--------------------------------------------------------------------+
:| Lee Cremeans -- Manassas, VA, USA (WakkyMouse on DALnet and WTnet)|
No overclocking. Stock CTX box. Could it be the drive, maybe?
I only get 2.4 MBytes/sec, same as before. On my PPro box ( Intel
PIIX3 Bus-master IDE controller ) it went from around 2.4 MB/sec
to 8 MBytes/sec.
archive:/cvs# time dd if=/dev/zero of=test2 bs=32k count=1024
1024+0 records in
1024+0 records out
33554432 bytes transferred in 13.700387 secs (2449159 bytes/sec)
0.000u 2.728s 0:13.75 19.7% 357+1405k 5+525io 1pf+0w
-Matt
Matthew Dillon
<dillon@backplane.com>
ide_pci0: <Acer Aladdin IV/V (M5229) Bus-master IDE controller> rev 0x20 int a irq 0 on pci0.11.0
wdc0 at 0x1f0-0x1f7 irq 14 flags 0xa0ffa0ff on isa
wdc0: unit 0 (wd0): <QUANTUM Bigfoot TX4.0AT>, 32-bit, multi-block-16
wd0: 3832MB (7849170 sectors), 8306 cyls, 15 heads, 63 S/T, 512 B/S
wdc1 at 0x170-0x177 irq 15 flags 0xa0ffa0ff on isa
wdc1: unit 0 (atapi): <ATAPI CDROM/V1.70>, removable, dma, iordy
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Sun Jan 24 21:02:36 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id VAA16300
for freebsd-current-outgoing; Sun, 24 Jan 1999 21:02:36 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from allegro.lemis.com (allegro.lemis.com [192.109.197.134])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA16295
for <current@FreeBSD.ORG>; Sun, 24 Jan 1999 21:02:32 -0800 (PST)
(envelope-from grog@freebie.lemis.com)
Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137])
by allegro.lemis.com (8.9.1/8.9.0) with ESMTP id PAA27809;
Mon, 25 Jan 1999 15:32:17 +1030 (CST)
Received: (from grog@localhost)
by freebie.lemis.com (8.9.2/8.9.0) id PAA51192;
Mon, 25 Jan 1999 15:32:16 +1030 (CST)
Date: Mon, 25 Jan 1999 15:32:16 +1030
From: Greg Lehey <grog@lemis.com>
To: lcremean@tidalwave.net
Cc: Matthew Dillon <dillon@apollo.backplane.com>, current@FreeBSD.ORG
Subject: Re: IDE DMA works, I'll be a...
Message-ID: <19990125153216.Q36690@freebie.lemis.com>
References: <199901250419.UAA00493@apollo.backplane.com> <19990124232542.A1754@tidalwave.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.95.1i
In-Reply-To: <19990124232542.A1754@tidalwave.net>; from Lee Cremeans on Sun, Jan 24, 1999 at 11:25:42PM -0500
WWW-Home-Page: http://www.lemis.com/~grog
Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia
Phone: +61-8-8388-8286
Fax: +61-8-8388-8725
Mobile: +61-41-739-7062
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
On Sunday, 24 January 1999 at 23:25:42 -0500, Lee Cremeans wrote:
> On Sun, Jan 24, 1999 at 08:19:33PM -0800, Matthew Dillon wrote:
>
>> It doesn't work on my CTX box, though - heh. Quantity verses Quality,
>> I guess. The CTX box was ~$1K 3 months ago while my PPro box was ~$3K
>> a year and a half ago.
>
> Can you find out what chipset is in this guy? There's support for anything
> Intel or VIA, Promise UDMA cards, Cyrix MediaGX, and Acer Aladdin IV/V right
> now.
See kern/9550. The driver *used* to support my SiS chipset, but it no
longer does when both master and slave drive are present since I
updated about a week ago. Possibly the same bug is biting Matt.
Greg
--
See complete headers for address, home page and phone numbers
finger grog@lemis.com for PGP public key
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Sun Jan 24 21:12:26 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id VAA17898
for freebsd-current-outgoing; Sun, 24 Jan 1999 21:12:26 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from st-lcremean.tidalwave.net (st-lcremean.tidalwave.net [208.213.203.186])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA17889
for <current@FreeBSD.ORG>; Sun, 24 Jan 1999 21:12:23 -0800 (PST)
(envelope-from lee@st-lcremean.tidalwave.net)
Received: (from lee@localhost)
by st-lcremean.tidalwave.net (8.9.2/8.9.2) id AAA01986;
Mon, 25 Jan 1999 00:12:04 -0500 (EST)
(envelope-from lee)
Message-ID: <19990125001204.A1916@tidalwave.net>
Date: Mon, 25 Jan 1999 00:12:04 -0500
From: Lee Cremeans <lee@st-lcremean.tidalwave.net>
To: Matthew Dillon <dillon@apollo.backplane.com>
Cc: current@FreeBSD.ORG
Subject: Re: IDE DMA works, I'll be a...
Reply-To: lcremean@tidalwave.net
References: <199901250419.UAA00493@apollo.backplane.com> <19990124232542.A1754@tidalwave.net> <199901250434.UAA00625@apollo.backplane.com> <19990124233749.A1816@tidalwave.net> <199901250453.UAA00799@apollo.backplane.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.93.2i
In-Reply-To: <199901250453.UAA00799@apollo.backplane.com>; from Matthew Dillon on Sun, Jan 24, 1999 at 08:53:19PM -0800
X-OS: FreeBSD 3.0-CURRENT
X-Evil: microsoft.com
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
>
> :> I haven't cvs updated in 24 hours, if the Acer is newly committed then I'll
> :> have to update again and retry. The CTX is using the Acer.
> :>
> :> ide_pci0: <Acer Aladdin IV/V (M5229) Bus-master IDE controller> rev 0x20 int a irq 0 on pci0.11.0
> : ^^^^^^^^^^^^^^^^^^^^^^^^
> :
> :It's there...what symptoms are you seeing? Are you overclocking?
> :--
> :+--------------------------------------------------------------------+
> :| Lee Cremeans -- Manassas, VA, USA (WakkyMouse on DALnet and WTnet)|
>
>
> No overclocking. Stock CTX box. Could it be the drive, maybe?
>
> I only get 2.4 MBytes/sec, same as before. On my PPro box ( Intel
> PIIX3 Bus-master IDE controller ) it went from around 2.4 MB/sec
> to 8 MBytes/sec.
>
> archive:/cvs# time dd if=/dev/zero of=test2 bs=32k count=1024
I do read testing with
dd if=/dev/rwd0 of=/dev/null bs=1024k count=(at least 20).
I get 13 MB/s on my Seagate Medalist Pro 9140 this way.
wdc0: unit 0 (wd0): <ST39140A>, DMA, 32-bit, multi-block-16
wd0: 8693MB (17803440 sectors), 17662 cyls, 16 heads, 63 S/T, 512 B/S
st-lcremean:~ $ dd if=/dev/rwd0 of=/dev/null bs=1024k count=30
30+0 records in
30+0 records out
31457280 bytes transferred in 2.295490 secs (13703950 bytes/sec)
However, if it only does 2.4MB/s writing on the Acer, it may be that UDMA
isn't getting enabled correctly. Which rev of ide_pci.c do you have?
PS: I can put up the M1543 programmer's manual on my machine if you want to
fix it; I don't have my Acer board here anymore, so can't do this myself.
--
+--------------------------------------------------------------------+
| Lee Cremeans -- Manassas, VA, USA (WakkyMouse on DALnet and WTnet)|
| lcremean@tidalwave.net| http://st-lcremean.tidalwave.net/~lee |
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Sun Jan 24 21:15:51 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id VAA18174
for freebsd-current-outgoing; Sun, 24 Jan 1999 21:15:51 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from mail.HiWAAY.net (fly.HiWAAY.net [208.147.154.56])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA18167
for <current@FreeBSD.ORG>; Sun, 24 Jan 1999 21:15:50 -0800 (PST)
(envelope-from dkelly@nospam.hiwaay.net)
Received: from nospam.hiwaay.net (tnt1-113.HiWAAY.net [208.147.147.113])
by mail.HiWAAY.net (8.9.1a/8.9.0) with ESMTP id XAA31136
for <current@FreeBSD.ORG>; Sun, 24 Jan 1999 23:15:36 -0600 (CST)
Received: from nospam.hiwaay.net (localhost [127.0.0.1])
by nospam.hiwaay.net (8.9.2/8.9.1) with ESMTP id WAA73442
for <current@FreeBSD.ORG>; Sun, 24 Jan 1999 22:48:36 -0600 (CST)
(envelope-from dkelly@nospam.hiwaay.net)
Message-Id: <199901250448.WAA73442@nospam.hiwaay.net>
X-Mailer: exmh version 2.0.2 2/24/98
To: current@FreeBSD.ORG
From: David Kelly <dkelly@hiwaay.net>
Subject: Re: IDE DMA works, I'll be a...
In-reply-to: Message from Matthew Dillon <dillon@apollo.backplane.com>
of "Sun, 24 Jan 1999 20:19:33 PST." <199901250419.UAA00493@apollo.backplane.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Sun, 24 Jan 1999 22:48:35 -0600
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
Matthew Dillon writes:
> Well I'll be a cat in a hat! IDE DMA actually works on my old
> PPro-200 box with a new IDE drive! A solid 8 MBytes/sec out of the
> thing. My poor old 4 GB SCSI barracuda could only do 4.3 MB/sec.
> Time to replace the barracuda, I think.
What did you use to measure? Bonnie?
For kicks time something interesting such as a CVS checkout with both
source and destination on the same drive. While the burst thruput is
higher am curious what the effect on real world seeks is.
4G Barracuda that only does 4.3 MB/sec? An ST15150[NW]? My narrow 5400
RPM IBM DCAS has been faster than 7200 RPM ST15150-either-N-or-W on SGI,
Mac, and FreeBSD hosts. Haven't done the same tests but ST34173's are
faster than the ST15150's.
HD on my "good" system is an IBM DCHS09. Haven't checked recently but
bonnie used to peak at around 8.5 MB/sec. In practical applications such
as a CVS checkout or sorting mail thru slocal I notice the practical
limit seems to be 80 to 100 tps as reported by "systat -v". And at that
rate its often doing only 600k/sec (small transaction blocksize of 4k).
Have seen it reach 120 to 140 on occasion. And once it it 150.
Caught this just now in a "make release", it just doesn't go much
faster than 143 tps:
Discs fd0 da0 sa0 sa1 pass0 pass1 pass2 intrn
KB/t 0.00 9.49 0.00 0.00 0.00 0.00 0.00 8337 buf
tps 0 143 0 0 0 0 0 8461 desiredvnodes
MB/s 0.00 1.32 0.00 0.00 0.00 0.00 0.00 18768 numvnodes
Recently I enabled optional flags on a 2.2.7 system's wd driver. For
lack of any better guess, used 0x80ff. Got a noticable improvement on a
Gateway P-133 and the OEM 1G HD but haven't bothered to attempt accurate
measure.
--
David Kelly N4HHE, dkelly@nospam.hiwaay.net
=====================================================================
The human mind ordinarily operates at only ten percent of its
capacity -- the rest is overhead for the operating system.
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Sun Jan 24 21:38:48 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id VAA20184
for freebsd-current-outgoing; Sun, 24 Jan 1999 21:38:48 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from st-lcremean.tidalwave.net (host-e186.tidalwave.net [208.213.203.186] (may be forged))
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA20178
for <current@freebsd.org>; Sun, 24 Jan 1999 21:38:43 -0800 (PST)
(envelope-from lee@st-lcremean.tidalwave.net)
Received: (from lee@localhost)
by st-lcremean.tidalwave.net (8.9.2/8.9.2) id AAA02069;
Mon, 25 Jan 1999 00:38:05 -0500 (EST)
(envelope-from lee)
Message-ID: <19990125003805.B1916@tidalwave.net>
Date: Mon, 25 Jan 1999 00:38:05 -0500
From: Lee Cremeans <lee@st-lcremean.tidalwave.net>
To: Greg Lehey <grog@lemis.com>
Cc: Matthew Dillon <dillon@apollo.backplane.com>, current@FreeBSD.ORG
Subject: Re: IDE DMA works, I'll be a...
Reply-To: lcremean@tidalwave.net
References: <199901250419.UAA00493@apollo.backplane.com> <19990124232542.A1754@tidalwave.net> <19990125153216.Q36690@freebie.lemis.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.93.2i
In-Reply-To: <19990125153216.Q36690@freebie.lemis.com>; from Greg Lehey on Mon, Jan 25, 1999 at 03:32:16PM +1030
X-OS: FreeBSD 3.0-CURRENT
X-Evil: microsoft.com
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
On Mon, Jan 25, 1999 at 03:32:16PM +1030, Greg Lehey wrote:
> On Sunday, 24 January 1999 at 23:25:42 -0500, Lee Cremeans wrote:
> > On Sun, Jan 24, 1999 at 08:19:33PM -0800, Matthew Dillon wrote:
> >
> >> It doesn't work on my CTX box, though - heh. Quantity verses Quality,
> >> I guess. The CTX box was ~$1K 3 months ago while my PPro box was ~$3K
> >> a year and a half ago.
> >
> > Can you find out what chipset is in this guy? There's support for anything
> > Intel or VIA, Promise UDMA cards, Cyrix MediaGX, and Acer Aladdin IV/V right
> > now.
>
> See kern/9550. The driver *used* to support my SiS chipset, but it no
> longer does when both master and slave drive are present since I
> updated about a week ago. Possibly the same bug is biting Matt.
Ok, I'm reading the PR now, and it seems this is not what Matt is
complaining about. What I gather is that Matt's drive works without hiccups,
it's just slower than it should be. What you have is the timeout bug,
something that 1) only seems to hit unsupported chipsets -- this is why I
wrote the Acer support 2) seems to happen on these Seagate 5xxxxA drives a
lot (someone else was complaining of this after the Acer support was
committed).
Try this patch:
--- ide_pci.c Mon Jan 25 00:26:35 1999
+++ ide_pci.c.new Mon Jan 25 00:31:58 1999
@@ -279,9 +279,10 @@
/* If we're here, then this controller is most likely not set
for UDMA, even if the drive may be. Make the drive wise
up. */
-
- if(!wdcmd(WDDMA_MDMA2, wdinfo))
- printf("generic_dmainit: could not set multiword DMA mode!\n");
+ if(udma_mode(wp) >= 2) {
+ if(!wdcmd(WDDMA_MDMA2, wdinfo))
+ printf("generic_dmainit: could not set multiword DMA mode!\n");
+ }
return 1;
}
#ifdef IDE_PCI_DEBUG
Feel free to clean it up if you like, since I'm not clear on what style(9)
thinks of this. It makes it so that we only try forcing MWDMA2 on UDMA
drives, since that seems to be the most common clash with the generic code
-- the drive is expecting UDMA, but the controller isn't. This code was
originally put there because it made my Seagate 9GB work in DMA mode on my
then-unsupported Acer chipset. Before this, it was forcing MWDMA2 on all
comers, and that may be giving the 5xxxx drives fits.
--
+--------------------------------------------------------------------+
| Lee Cremeans -- Manassas, VA, USA (WakkyMouse on DALnet and WTnet)|
| lcremean@tidalwave.net| http://st-lcremean.tidalwave.net/~lee |
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Sun Jan 24 22:01:59 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id WAA22240
for freebsd-current-outgoing; Sun, 24 Jan 1999 22:01:59 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from gratis.grondar.za (gratis.grondar.za [196.7.18.65])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA22230
for <freebsd-current@FreeBSD.ORG>; Sun, 24 Jan 1999 22:01:54 -0800 (PST)
(envelope-from mark@grondar.za)
Received: from greenpeace.grondar.za (greenpeace.grondar.za [196.7.18.132])
by gratis.grondar.za (8.9.2/8.9.2) with ESMTP id IAA68668;
Mon, 25 Jan 1999 08:01:37 +0200 (SAST)
(envelope-from mark@grondar.za)
Received: from grondar.za (localhost [127.0.0.1])
by greenpeace.grondar.za (8.9.2/8.9.2) with ESMTP id IAA21990;
Mon, 25 Jan 1999 08:01:37 +0200 (SAST)
(envelope-from mark@grondar.za)
Message-Id: <199901250601.IAA21990@greenpeace.grondar.za>
To: Randy Bush <randy@psg.com>
cc: freebsd-current@FreeBSD.ORG
Subject: Re: make aout-to-elf-build failure
In-Reply-To: Your message of " Sun, 24 Jan 1999 20:23:29 PST." <m104dYf-0008G4C@rip.psg.com>
References: <m1047WH-0008G4C@rip.psg.com> <199901231907.LAA16027@vashon.polstra.com> <m104A3n-0008G4C@rip.psg.com> <199901240817.KAA02681@greenpeace.grondar.za> <m104NL6-0008G4C@rip.psg.com> <199901241119.NAA03526@greenpeace.grondar.za> <m104RJR-0008G4C@rip.psg.com> <199901241537.RAA16096@greenpeace.grondar.za> <m104dYf-0008G4C@rip.psg.com>
Date: Mon, 25 Jan 1999 08:01:37 +0200
From: Mark Murray <mark@grondar.za>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
Randy Bush wrote:
> when i did all these, see previous msg, it all worked. i successfully went
> from a pure aout 3.0-current of 981231 to 4.0-current of today.
Cool!
> your assistance was really appreciated.
Yours too. I have the list of places from your other mail, and I'll be
doing them this evening.
M
--
Mark Murray
Join the anti-SPAM movement: http://www.cauce.org
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Sun Jan 24 22:08:38 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id WAA22928
for freebsd-current-outgoing; Sun, 24 Jan 1999 22:08:38 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.26.10.9])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA22923
for <current@FreeBSD.ORG>; Sun, 24 Jan 1999 22:08:35 -0800 (PST)
(envelope-from bde@godzilla.zeta.org.au)
Received: (from bde@localhost)
by godzilla.zeta.org.au (8.8.7/8.8.7) id RAA24912;
Mon, 25 Jan 1999 17:08:19 +1100
Date: Mon, 25 Jan 1999 17:08:19 +1100
From: Bruce Evans <bde@zeta.org.au>
Message-Id: <199901250608.RAA24912@godzilla.zeta.org.au>
To: grog@lemis.com, lcremean@tidalwave.net
Subject: Re: IDE DMA works, I'll be a...
Cc: current@FreeBSD.ORG, dillon@apollo.backplane.com
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
>> Can you find out what chipset is in this guy? There's support for anything
>> Intel or VIA, Promise UDMA cards, Cyrix MediaGX, and Acer Aladdin IV/V right
>> now.
>
>See kern/9550. The driver *used* to support my SiS chipset, but it no
>longer does when both master and slave drive are present since I
>updated about a week ago. Possibly the same bug is biting Matt.
The driver doesn't have any special support for SiS. It uses generic
support in some cases, apparently including your case. Recent fixes
made it actually initialize DMA on the correct drive, but the
initialization in generic_dmainit() is buggy (it assumes multi-word
DMA mode 2 but your IDE timing is apparently incompatible with this).
Bruce
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Sun Jan 24 22:20:18 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id WAA24536
for freebsd-current-outgoing; Sun, 24 Jan 1999 22:20:18 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from st-lcremean.tidalwave.net (host-e186.tidalwave.net [208.213.203.186] (may be forged))
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA24531
for <current@FreeBSD.ORG>; Sun, 24 Jan 1999 22:20:14 -0800 (PST)
(envelope-from lee@st-lcremean.tidalwave.net)
Received: (from lee@localhost)
by st-lcremean.tidalwave.net (8.9.2/8.9.2) id BAA02235;
Mon, 25 Jan 1999 01:19:38 -0500 (EST)
(envelope-from lee)
Message-ID: <19990125011938.F1916@tidalwave.net>
Date: Mon, 25 Jan 1999 01:19:38 -0500
From: Lee Cremeans <lee@st-lcremean.tidalwave.net>
To: Bruce Evans <bde@zeta.org.au>, grog@lemis.com
Cc: current@FreeBSD.ORG, dillon@apollo.backplane.com
Subject: Re: IDE DMA works, I'll be a...
Reply-To: lcremean@tidalwave.net
References: <199901250608.RAA24912@godzilla.zeta.org.au>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.93.2i
In-Reply-To: <199901250608.RAA24912@godzilla.zeta.org.au>; from Bruce Evans on Mon, Jan 25, 1999 at 05:08:19PM +1100
X-OS: FreeBSD 3.0-CURRENT
X-Evil: microsoft.com
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
On Mon, Jan 25, 1999 at 05:08:19PM +1100, Bruce Evans wrote:
> >> Can you find out what chipset is in this guy? There's support for anything
> >> Intel or VIA, Promise UDMA cards, Cyrix MediaGX, and Acer Aladdin IV/V right
> >> now.
> >
> >See kern/9550. The driver *used* to support my SiS chipset, but it no
> >longer does when both master and slave drive are present since I
> >updated about a week ago. Possibly the same bug is biting Matt.
>
> The driver doesn't have any special support for SiS. It uses generic
> support in some cases, apparently including your case. Recent fixes
> made it actually initialize DMA on the correct drive, but the
> initialization in generic_dmainit() is buggy (it assumes multi-word
> DMA mode 2 but your IDE timing is apparently incompatible with this).
Originally, this was meant so that people with UDMA drives could use them in
_some_ DMA mode on a chipset without explicit support (on the assumption
that the controller will be all set up for MWDMA2 or a compatible mode; a
hack, yes, but when you don't know anything about the controller, you can't
very well fix it), but the code was written to assume that for _any_
DMA-capable drive on a generic controller. The patch I just posted limits
the force-set to UDMA drives only, like it should have been in the first
place.
--
+--------------------------------------------------------------------+
| Lee Cremeans -- Manassas, VA, USA (WakkyMouse on DALnet and WTnet)|
| lcremean@tidalwave.net| http://st-lcremean.tidalwave.net/~lee |
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Sun Jan 24 22:44:48 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id WAA27016
for freebsd-current-outgoing; Sun, 24 Jan 1999 22:44:48 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from ns.mt.sri.com (sri-gw.MT.net [206.127.105.141])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA27008
for <current@FreeBSD.ORG>; Sun, 24 Jan 1999 22:44:46 -0800 (PST)
(envelope-from nate@mt.sri.com)
Received: from mt.sri.com (rocky.mt.sri.com [206.127.76.100])
by ns.mt.sri.com (8.8.8/8.8.8) with SMTP id XAA08356;
Sun, 24 Jan 1999 23:44:43 -0700 (MST)
(envelope-from nate@rocky.mt.sri.com)
Received: by mt.sri.com (SMI-8.6/SMI-SVR4)
id XAA04563; Sun, 24 Jan 1999 23:44:42 -0700
Date: Sun, 24 Jan 1999 23:44:42 -0700
Message-Id: <199901250644.XAA04563@mt.sri.com>
From: Nate Williams <nate@mt.sri.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
To: Edwin Culp <eculp@MexComUSA.net>
Cc: Nate Williams <nate@mt.sri.com>, current@FreeBSD.ORG
Subject: Re: 4.0-Current, netscape halts system
In-Reply-To: <36ABED16.111D4ACB@MexComUSA.net>
References: <1476.917220230@zippy.cdrom.com>
<199901250020.QAA22590@bubba.whistle.com>
<199901250147.SAA03468@mt.sri.com>
<36ABED16.111D4ACB@MexComUSA.net>
X-Mailer: VM 6.34 under 19.16 "Lille" XEmacs Lucid
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
> > > > I really don't understand the problems that everyone is having,
> > > > myself. I've been running netscape (communicator 4.5) in -current for
> > > > ages now and just switched to 4.0 without any problems. My netscape
> > > > still continues to function just fine and has never crashed any of
> > > > my system so much as once.
> > > >
> > > > Why the wide disparity in experience, I wonder?
> > >
> > > Do you ever run Java applets? Netscape 4.5 seems to work fine
> > > until running Java, which kicks off some sort of time bomb.
> > > Death is not immediate, but it is guaranteed.
> >
> > Agreed. However, I disabled Java, and I can also get death anytime I
> > try to download a file using netscape. Not fun.
>
> I am current as of today 4.0, I have communicator 4.5 downloaded some time
> ago (November more or less) directly from netscape and installed in
> /usr/local/netscape with a link to /usr/local/bin/netscape and I have been
> using it all day with no problems. My intranet if full of java and haven't
> had a problem, knock on wood:-) I just downloaded a 9M file after reading
> your mail to see if that would cause a problem and it didn't. Netscape is
> "as stable as ever" on FreeBSD Current 4.0 for me. That bothers me:-) I
> wonder why?
I'm running 2.2-stable, so maybe that's a difference.
Nate
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Sun Jan 24 23:03:22 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id XAA29155
for freebsd-current-outgoing; Sun, 24 Jan 1999 23:03:22 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.26.10.9])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA29141
for <current@FreeBSD.ORG>; Sun, 24 Jan 1999 23:03:18 -0800 (PST)
(envelope-from bde@godzilla.zeta.org.au)
Received: (from bde@localhost)
by godzilla.zeta.org.au (8.8.7/8.8.7) id SAA29745;
Mon, 25 Jan 1999 18:03:15 +1100
Date: Mon, 25 Jan 1999 18:03:15 +1100
From: Bruce Evans <bde@zeta.org.au>
Message-Id: <199901250703.SAA29745@godzilla.zeta.org.au>
To: bde@zeta.org.au, grog@lemis.com, lcremean@tidalwave.net
Subject: Re: IDE DMA works, I'll be a...
Cc: current@FreeBSD.ORG, dillon@apollo.backplane.com
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
>> The driver doesn't have any special support for SiS. It uses generic
>> support in some cases, apparently including your case. Recent fixes
>> made it actually initialize DMA on the correct drive, but the
>> initialization in generic_dmainit() is buggy (it assumes multi-word
>> DMA mode 2 but your IDE timing is apparently incompatible with this).
>
>Originally, this was meant so that people with UDMA drives could use them in
>_some_ DMA mode on a chipset without explicit support (on the assumption
>that the controller will be all set up for MWDMA2 or a compatible mode; a
>hack, yes, but when you don't know anything about the controller, you can't
>very well fix it), but the code was written to assume that for _any_
>DMA-capable drive on a generic controller. The patch I just posted limits
>the force-set to UDMA drives only, like it should have been in the first
>place.
Not just any DMA-capable drive - only MWDMA2-capable ones. It seems
reasonable to set such drives to MWDMA2 mode. Whether this works depends
more on the controller's initialization than the drive.
The forced-set (in via_571_dmainit()) doesn't work as well as skipping
the set for a VIA controller here. For the following drives:
wd0 = SAMSUNG SHD-3212A 406MB, pio_mode() = mwdma_mode() = udmamode() = -1
wd2 = QUANTUM FIREBALL ST6.4A, pio_mode() = 4, mwdma_mode() = udma_mode() = 2
I see the following behaviour:
- after pretending that wd0 supports mwdma2 or udma2, DMA mode actually
works (interrupt overhead is significantly reduced). Forcing MWDMA2 or
UDMA2 has no effect on the drive, but breaks the slave cdrom.
- forcing UDMA2 for wd2 has no effect on the drive IIRC, but breaks the
slave cdrom. Normally I don't notice the breakage because I don't
have a slave cdrom on the second controller.
- forcing MWDMA2 for wd2 seems to slightly increase interrupt overhead,
and breaks the slave cdrom.
Apparently my drives default to their best mode after reset, and UltraDMA
IDE timing works for old drives, and the setting DMA features on master
drives somehow affects slave cdroms. On another system with PIIX1 and
a MWDMA2 drive, I have no problems with the slave cdrom.
Bruce
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Sun Jan 24 23:21:32 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id XAA01386
for freebsd-current-outgoing; Sun, 24 Jan 1999 23:21:32 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from st-lcremean.tidalwave.net (host-e186.tidalwave.net [208.213.203.186] (may be forged))
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA01377
for <current@FreeBSD.ORG>; Sun, 24 Jan 1999 23:21:29 -0800 (PST)
(envelope-from lee@st-lcremean.tidalwave.net)
Received: (from lee@localhost)
by st-lcremean.tidalwave.net (8.9.2/8.9.2) id CAA02605;
Mon, 25 Jan 1999 02:21:02 -0500 (EST)
(envelope-from lee)
Message-ID: <19990125022102.A2244@tidalwave.net>
Date: Mon, 25 Jan 1999 02:21:02 -0500
From: Lee Cremeans <lee@st-lcremean.tidalwave.net>
To: Bruce Evans <bde@zeta.org.au>, grog@lemis.com
Cc: current@FreeBSD.ORG, dillon@apollo.backplane.com
Subject: Re: IDE DMA works, I'll be a...
Reply-To: lcremean@tidalwave.net
References: <199901250703.SAA29745@godzilla.zeta.org.au>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.93.2i
In-Reply-To: <199901250703.SAA29745@godzilla.zeta.org.au>; from Bruce Evans on Mon, Jan 25, 1999 at 06:03:15PM +1100
X-OS: FreeBSD 3.0-CURRENT
X-Evil: microsoft.com
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
On Mon, Jan 25, 1999 at 06:03:15PM +1100, Bruce Evans wrote:
> >> The driver doesn't have any special support for SiS. It uses generic
> >> support in some cases, apparently including your case. Recent fixes
> >> made it actually initialize DMA on the correct drive, but the
> >> initialization in generic_dmainit() is buggy (it assumes multi-word
> >> DMA mode 2 but your IDE timing is apparently incompatible with this).
> >
> >Originally, this was meant so that people with UDMA drives could use them in
> >_some_ DMA mode on a chipset without explicit support (on the assumption
> >that the controller will be all set up for MWDMA2 or a compatible mode; a
> >hack, yes, but when you don't know anything about the controller, you can't
> >very well fix it), but the code was written to assume that for _any_
> >DMA-capable drive on a generic controller. The patch I just posted limits
> >the force-set to UDMA drives only, like it should have been in the first
> >place.
>
> Not just any DMA-capable drive - only MWDMA2-capable ones. It seems
> reasonable to set such drives to MWDMA2 mode. Whether this works depends
> more on the controller's initialization than the drive.
>
> The forced-set (in via_571_dmainit()) doesn't work as well as skipping
> the set for a VIA controller here. For the following drives:
>
> wd0 = SAMSUNG SHD-3212A 406MB, pio_mode() = mwdma_mode() = udmamode() = -1
> wd2 = QUANTUM FIREBALL ST6.4A, pio_mode() = 4, mwdma_mode() = udma_mode() = 2
>
> I see the following behaviour:
> - after pretending that wd0 supports mwdma2 or udma2, DMA mode actually
> works (interrupt overhead is significantly reduced). Forcing MWDMA2 or
> UDMA2 has no effect on the drive, but breaks the slave cdrom.
> - forcing UDMA2 for wd2 has no effect on the drive IIRC, but breaks the
> slave cdrom. Normally I don't notice the breakage because I don't
> have a slave cdrom on the second controller.
> - forcing MWDMA2 for wd2 seems to slightly increase interrupt overhead,
> and breaks the slave cdrom.
Hm. I did not see this at all here, but I also run with my Seagate being the
only thing on the primary controller, and an LS-120 drive as master and a
Toshiba 32X CD-ROM as slave on the second controller. What I did see when I
got my drive was loads upon loads of interrupt timeout errors, which didn't
happen on my previous drive (a JTS C4300-3AF, non UDMA); turning off DMA
stopped it, and so did adding the forced MWDMA2 in generic_dmainit. This
was months ago, like late last summer/early fall, long before your
unit-number fixes were added, and that bogosity is what inspired me to write
the Acer support.
> Apparently my drives default to their best mode after reset, and UltraDMA
> IDE timing works for old drives, and the setting DMA features on master
> drives somehow affects slave cdroms. On another system with PIIX1 and
> a MWDMA2 drive, I have no problems with the slave cdrom.
Probably because PIIX1 can't set the timings for each device individually,
and (I would assume) therefore goes with the lowest common denominator for
both devices.
--
+--------------------------------------------------------------------+
| Lee Cremeans -- Manassas, VA, USA (WakkyMouse on DALnet and WTnet)|
| lcremean@tidalwave.net| http://st-lcremean.tidalwave.net/~lee |
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Sun Jan 24 23:44:50 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id XAA04666
for freebsd-current-outgoing; Sun, 24 Jan 1999 23:44:50 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from zibbi.mikom.csir.co.za (zibbi.mikom.csir.co.za [146.64.24.58])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA04659
for <current@FreeBSD.ORG>; Sun, 24 Jan 1999 23:44:45 -0800 (PST)
(envelope-from jhay@zibbi.mikom.csir.co.za)
Received: (from jhay@localhost)
by zibbi.mikom.csir.co.za (8.9.1/8.9.1) id JAA06882;
Mon, 25 Jan 1999 09:44:10 +0200 (SAT)
From: John Hay <jhay@mikom.csir.co.za>
Message-Id: <199901250744.JAA06882@zibbi.mikom.csir.co.za>
Subject: Re: Current's availability
In-Reply-To: <1229.917217687@zippy.cdrom.com> from "Jordan K. Hubbard" at "Jan 24, 99 02:41:27 pm"
To: jkh@zippy.cdrom.com (Jordan K. Hubbard)
Date: Mon, 25 Jan 1999 09:44:09 +0200 (SAT)
Cc: donegan@quick.net, current@FreeBSD.ORG
X-Mailer: ELM [version 2.4ME+ PL32 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
> It's all a bit ill right now during the transition to 3.0S/4.0C from
> 2.2S/3.0C - I hope to have the build boxen back on the feet this week
> sometime.
>
> - Jordan
>
>
> > Yesterday I tried to ftp a current set of floppies from
> > current.freebsd.org - nothing there but 2.2.X stuff - 3.0 tree gone and
> > no 4.X tree apparent. Today I get connection refused at that site. ANy
> > pointers to a current tree would be appreciated. TIA.
If you are really desperate and you find our link speed ok, you can get
3.0 and 4.0 snaps on ftp.internat.freebsd.org.
John
--
John Hay -- John.Hay@mikom.csir.co.za
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Sun Jan 24 23:45:06 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id XAA04851
for freebsd-current-outgoing; Sun, 24 Jan 1999 23:45:06 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from labinfo.iet.unipi.it (labinfo.iet.unipi.it [131.114.9.5])
by hub.freebsd.org (8.8.8/8.8.8) with SMTP id XAA04846
for <current@FreeBSD.ORG>; Sun, 24 Jan 1999 23:45:04 -0800 (PST)
(envelope-from luigi@labinfo.iet.unipi.it)
Received: from localhost (luigi@localhost) by labinfo.iet.unipi.it (8.6.5/8.6.5) id GAA25782; Mon, 25 Jan 1999 06:33:26 +0100
From: Luigi Rizzo <luigi@labinfo.iet.unipi.it>
Message-Id: <199901250533.GAA25782@labinfo.iet.unipi.it>
Subject: Re: beginnings of a diskless boot sequence being committed
To: dillon@apollo.backplane.com (Matthew Dillon)
Date: Mon, 25 Jan 1999 06:33:26 +0100 (MET)
Cc: current@FreeBSD.ORG
In-Reply-To: <199901250432.UAA00610@apollo.backplane.com> from "Matthew Dillon" at Jan 24, 99 08:31:48 pm
X-Mailer: ELM [version 2.4 PL23]
Content-Type: text
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
> I'm going to commit a cleaned up version of my rc startup mods
> to handle diskless BOOTP kernels, especially diskless BOOTP kernels
> with read-only NFS mounts of / and /usr.
>
> Basically this consists of a bit of code in /etc/rc and, later tonight,
> an /etc/rc.diskless script ( a new script ).
before you reinvent the wheel, have you looked at my code in
http://www.iet.unipi.it/~luigi/diskless981113/
this is sliglthly pout of date wrt what i have now (an rc.diskless
file, which essentially contains all rc modifications that you see in
the above web page)
cheers
luigi
-----------------------------------+-------------------------------------
Luigi RIZZO .
EMAIL: luigi@iet.unipi.it . Dip. di Ing. dell'Informazione
HTTP://www.iet.unipi.it/~luigi/ . Universita` di Pisa
TEL/FAX: +39-050-568.533/522 . via Diotisalvi 2, 56126 PISA (Italy)
-----------------------------------+-------------------------------------
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Mon Jan 25 00:04:21 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id AAA07374
for freebsd-current-outgoing; Mon, 25 Jan 1999 00:04:21 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA07363
for <current@FreeBSD.ORG>; Mon, 25 Jan 1999 00:04:19 -0800 (PST)
(envelope-from phk@critter.freebsd.dk)
Received: from critter.freebsd.dk (localhost [127.0.0.1])
by critter.freebsd.dk (8.9.1/8.8.5) with ESMTP id JAA16669;
Mon, 25 Jan 1999 09:02:03 +0100 (CET)
To: Garrett Wollman <wollman@khavrinen.lcs.mit.edu>
cc: Mike Smith <mike@smith.net.au>, current@FreeBSD.ORG
Subject: Re: sysctl oids (was: Re: kvm question)
In-reply-to: Your message of "Sun, 24 Jan 1999 17:01:11 EST."
<199901242201.RAA17112@khavrinen.lcs.mit.edu>
Date: Mon, 25 Jan 1999 09:02:02 +0100
Message-ID: <16667.917251322@critter.freebsd.dk>
From: Poul-Henning Kamp <phk@critter.freebsd.dk>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
In message <199901242201.RAA17112@khavrinen.lcs.mit.edu>, Garrett Wollman write
s:
><<On Sun, 24 Jan 1999 13:11:12 -0800, Mike Smith <mike@smith.net.au> said:
>
>> Backwards compatibility is one thing, but new nodes should be named,
>> not numbered. OID_AUTO is bogus because it perpetuates the numbering
>> of nodes.
>
>Nonsense. There are plenty of contexts in which a number makes far
>more sense than a name -- pretty much anything in any network stack
>other than Chaosnet, for example. If any of us ever make good on the
>threat of SNMP integration, having fixed numerical identifiers will be
>a requirement.
BS!
Yes, for systematic, programatically generated subtrees i could be
an advantage implementation wise, but for the root of the subtree
any anything else there is no reason to. You just look up the name
once and cache the numeric OID.
If anything we should get rid of as many users of the numeric OIDs
as possible...
--
Poul-Henning Kamp FreeBSD coreteam member
phk@FreeBSD.ORG "Real hackers run -current on their laptop."
FreeBSD -- It will take a long time before progress goes too far!
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Mon Jan 25 00:33:08 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id AAA11068
for freebsd-current-outgoing; Mon, 25 Jan 1999 00:33:08 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from solaris.matti.ee (solaris.matti.ee [194.126.98.135])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA11048
for <current@FreeBSD.ORG>; Mon, 25 Jan 1999 00:33:04 -0800 (PST)
(envelope-from vallo@myhakas.matti.ee)
Received: from myhakas.matti.ee (myhakas.matti.ee [194.126.114.87]) by solaris.matti.ee (8.8.8/8.8.8.s) with ESMTP id KAA25323; Mon, 25 Jan 1999 10:32:58 +0200 (EET)
Received: (from vallo@localhost)
by myhakas.matti.ee (8.9.1/8.9.1) id KAA35495;
Mon, 25 Jan 1999 10:32:58 +0200 (EET)
(envelope-from vallo)
Message-ID: <19990125103258.B34889@matti.ee>
Date: Mon, 25 Jan 1999 10:32:58 +0200
From: Vallo Kallaste <vallo@matti.ee>
To: Amancio Hasty <hasty@rah.star-gate.com>
Cc: current@FreeBSD.ORG
Subject: Re: 4.0-Current, netscape halts system
Reply-To: vallo@matti.ee
References: <1476.917220230@zippy.cdrom.com> <199901250021.QAA05365@rah.star-gate.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.93.2i
In-Reply-To: <199901250021.QAA05365@rah.star-gate.com>; from Amancio Hasty on Sun, Jan 24, 1999 at 04:21:16PM -0800
Organization: =?iso-8859-15?Q?AS_Matti_B=FCrootehnika?=
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
On Sun, Jan 24, 1999 at 04:21:16PM -0800, Amancio Hasty <hasty@rah.star-gate.com> wrote:
> http://www.developer.com/experts/expertspanel.html
>
> click on Bar's Guide to the the Interactive Fiction and after
> the page finishes loading click "Back" on Netscape's tool bar.
>
> Instant core -dump.
You are right. I'm running previously called 3.0-CURRENT and Netscape
Navigator 4.5. Sources are from Dec.29 1998. Also I'm getting
coredumps when loading a huge page containing tables(table) and then
using "back". It always crashes when going back, not on initial
loading. Why ?
--
Vallo Kallaste
vallo@matti.ee
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Mon Jan 25 00:36:28 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id AAA11375
for freebsd-current-outgoing; Mon, 25 Jan 1999 00:36:28 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from rah.star-gate.com (sj-dsl-9-129-138.dspeed.net [209.249.129.138])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA11370
for <current@FreeBSD.ORG>; Mon, 25 Jan 1999 00:36:27 -0800 (PST)
(envelope-from hasty@rah.star-gate.com)
Received: from rah.star-gate.com (localhost.star-gate.com [127.0.0.1])
by rah.star-gate.com (8.9.1/8.8.8) with ESMTP id AAA10521;
Mon, 25 Jan 1999 00:35:07 -0800 (PST)
(envelope-from hasty@rah.star-gate.com)
Message-Id: <199901250835.AAA10521@rah.star-gate.com>
X-Mailer: exmh version 2.0.2 2/24/98
To: vallo@matti.ee
cc: current@FreeBSD.ORG
Subject: Re: 4.0-Current, netscape halts system
In-reply-to: Your message of "Mon, 25 Jan 1999 10:32:58 +0200."
<19990125103258.B34889@matti.ee>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Mon, 25 Jan 1999 00:35:06 -0800
From: Amancio Hasty <hasty@rah.star-gate.com>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
I think this is the first step to show the bug . The next step is to
pray that the netscape developer is listening so he can fix it .
I think is odd that the bug doesn't happen with the linux version
of netscape.
Cheers,
Amancio
> On Sun, Jan 24, 1999 at 04:21:16PM -0800, Amancio Hasty <hasty@rah.star-gate.com> wrote:
>
> > http://www.developer.com/experts/expertspanel.html
> >
> > click on Bar's Guide to the the Interactive Fiction and after
> > the page finishes loading click "Back" on Netscape's tool bar.
> >
> > Instant core -dump.
>
> You are right. I'm running previously called 3.0-CURRENT and Netscape
> Navigator 4.5. Sources are from Dec.29 1998. Also I'm getting
> coredumps when loading a huge page containing tables(table) and then
> using "back". It always crashes when going back, not on initial
> loading. Why ?
>
> --
> Vallo Kallaste
> vallo@matti.ee
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Mon Jan 25 00:48:10 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id AAA12916
for freebsd-current-outgoing; Mon, 25 Jan 1999 00:48:10 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from korin.warman.org.pl (korin.nask.waw.pl [195.187.243.10])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA12910
for <current@FreeBSD.ORG>; Mon, 25 Jan 1999 00:48:05 -0800 (PST)
(envelope-from abial@nask.pl)
Received: from localhost (abial@localhost)
by korin.warman.org.pl (8.9.1/8.8.5) with SMTP id JAA15138;
Mon, 25 Jan 1999 09:53:10 +0100 (CET)
X-Authentication-Warning: korin.warman.org.pl: abial owned process doing -bs
Date: Mon, 25 Jan 1999 09:53:10 +0100 (CET)
From: Andrzej Bialecki <abial@nask.pl>
X-Sender: abial@korin.warman.org.pl
To: Mike Smith <mike@smith.net.au>
cc: Garrett Wollman <wollman@khavrinen.lcs.mit.edu>,
Archie Cobbs <archie@whistle.com>, current@FreeBSD.ORG
Subject: Re: kvm question
In-Reply-To: <199901242111.NAA05078@dingo.cdrom.com>
Message-ID: <Pine.BSF.4.02A.9901250951330.21763-100000@korin.warman.org.pl>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
On Sun, 24 Jan 1999, Mike Smith wrote:
> > <<On Sat, 23 Jan 1999 11:04:15 -0800 (PST), Archie Cobbs <archie@whistle.com> said:
> >
> > > Peter pointed out that having the sysctl's as symbols was a nice
> > > advantage of the current system. How important is this?
> >
> > I don't think it's important at all. (Then again, I liked the old
> > system.)
> >
> > > If we were willing to give this up, then the SYSCTL() macro could
> > > just expand to a SYSINIT() that called sysctl_add_subtree() (or
> > > whatever you want to call it) upon loading.
> >
> > Seems reasonable to me. The only problem with this is likely to be
> > OID_AUTO, which I happen to think is bogus anyway. It is vital that
> > we maintain the ability to reference sysctl entities by compile-time
> > constant integers, so as not to break backwards compatibility with
> > other 4.4 systems and the Stevens books.
>
> Backwards compatibility is one thing, but new nodes should be named,
> not numbered. OID_AUTO is bogus because it perpetuates the numbering
> of nodes.
...that is, IFF we're going to keep the number/name pairs as OIDs, and not
only the numbers, which seems more appropriate...
Andrzej Bialecki
-------------------- ++-------++ -------------------------------------
<abial@nask.pl> ||PicoBSD|| FreeBSD in your pocket? Go and see:
Research & Academic |+-------+| "Small & Embedded FreeBSD"
Network in Poland | |TT~~~| | http://www.freebsd.org/~picobsd/
-------------------- ~-+==---+-+ -------------------------------------
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Mon Jan 25 01:06:45 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id BAA14562
for freebsd-current-outgoing; Mon, 25 Jan 1999 01:06:45 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from send104.yahoomail.com (send104.yahoomail.com [205.180.60.122])
by hub.freebsd.org (8.8.8/8.8.8) with SMTP id BAA14555
for <freebsd-current@freebsd.org>; Mon, 25 Jan 1999 01:06:44 -0800 (PST)
(envelope-from thallgren@yahoo.com)
Message-ID: <19990125090940.490.rocketmail@send104.yahoomail.com>
Received: from [131.116.188.2] by send104.yahoomail.com; Mon, 25 Jan 1999 01:09:40 PST
Date: Mon, 25 Jan 1999 01:09:40 -0800 (PST)
From: Tommy Hallgren <thallgren@yahoo.com>
Subject: New Syscons and GGI
To: freebsd-current@FreeBSD.ORG
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
Hi!
Now that the console system is restructured, shouldn't we consider
using GGI instead of inventing the wheel?
I happened to find this link and they seem to be positive to
supporting FreeBSD.
http://synergy.caltech.edu/~ggi/mailinglist/ev-mar98/139.html
==
Regards: Tommy - The source of all good beers...
thallgren@yahoo.com
_________________________________________________________
DO YOU YAHOO!?
Get your free @yahoo.com address at http://mail.yahoo.com
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Mon Jan 25 01:07:31 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id BAA14648
for freebsd-current-outgoing; Mon, 25 Jan 1999 01:07:31 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA14642
for <current@FreeBSD.ORG>; Mon, 25 Jan 1999 01:07:30 -0800 (PST)
(envelope-from dillon@apollo.backplane.com)
Received: (from dillon@localhost)
by apollo.backplane.com (8.9.2/8.9.1) id BAA02600;
Mon, 25 Jan 1999 01:02:36 -0800 (PST)
(envelope-from dillon)
Date: Mon, 25 Jan 1999 01:02:36 -0800 (PST)
From: Matthew Dillon <dillon@apollo.backplane.com>
Message-Id: <199901250902.BAA02600@apollo.backplane.com>
To: Luigi Rizzo <luigi@labinfo.iet.unipi.it>
Cc: current@FreeBSD.ORG
Subject: Re: beginnings of a diskless boot sequence being committed
References: <199901250533.GAA25782@labinfo.iet.unipi.it>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
:>
:> Basically this consists of a bit of code in /etc/rc and, later tonight,
:> an /etc/rc.diskless script ( a new script ).
:
:before you reinvent the wheel, have you looked at my code in
:http://www.iet.unipi.it/~luigi/diskless981113/
:
:this is sliglthly pout of date wrt what i have now (an rc.diskless
:file, which essentially contains all rc modifications that you see in
:the above web page)
:
: cheers
: luigi
:-----------------------------------+-------------------------------------
: Luigi RIZZO .
I was basically just cleaning up stuff I've been using for several
months.
Your stuff looks quite similar.
What I propose is that a new kernel sysctl variable be added called
'kern.conf_dir' which the kernel initially sets to nothing.
We modify /etc/rc to detect a diskless boot ( trivial ) ... the
rc.diskless code must run before just about anything else since
the filesystems are all NFS read-only mounts ( and we want to be able
to leave them that way ).
rc.diskless figures out the IP address BOOTP assigned us and changes
kern.conf_dir to point to /conf/$IP.
/etc/rc.conf is then made 'smart' about where to look for rc.conf.local
and /etc/rc is also made smart about where to look for rc.local.
Specifically, if someone has set kern.conf_dir, *that* is where they
look.
Here is the proposed change to /etc/rc.conf ( the tail end of it ). Rather
then look for and source /etc/rc.conf.local, it uses kern.conf_dir.
##############################################################
### Allow local configuration override at the very end here ##
##############################################################
#
# If the kernel configuration script MIB exists, use it.
sysctl -n kern.conf_dir > /dev/null 2>&1
if [ $? = 0 ]; then
conf_dir=`sysctl -n kern.conf_dir`
fi
if [ "X$conf_dir" = "X" ]; then
conf_dir=/etc
fi
if [ -f $conf_dir/rc.conf.local ]; then
. $conf_dir/rc.conf.local
fi
--------
/etc/rc must be modified to do something similar when it is ready to
run /etc/rc.local -- it would use ${kern.conf_dir}/rc.local instead.
The only non-standard item is that /etc/rc needs to bypass the standard
disk configuraton code on a diskless boot, because the fstab is the
server's, not the diskless workstation's.
My proposal pretty much keeps intact the rc / rc.conf mechanism and simply
'moves' where rc and rc.conf look for rc.local and rc.conf.local, plus
a little additional magic to allow it to hook all the MFS filesystems
into the system.
Of course, then there are all the files in /conf/IPADDRESS/... actually
not too many, but these require a little more customization depending
on how you like to setup your server.
I haven't committed the whole thing yet, I would like to get feedback on
the general idea before I do so. But it is ready to go now.
#!/bin/sh
# $Id: rc,v 1.170 1999/01/25 04:40:53 dillon Exp $
# From: @(#)rc 5.27 (Berkeley) 6/5/91
#...
stty status '^T'
# Set shell to ignore SIGINT (2), but not children;
# shell catches SIGQUIT (3) and returns to single user after fsck.
trap : 2
trap : 3 # shouldn't be needed
HOME=/; export HOME
PATH=/sbin:/bin:/usr/sbin:/usr/bin:/usr/local/sbin
export PATH
# BOOTP diskless boot. We have to run the rc file early in order to
# handle read-only NFS mounts, where the various config files
# in /etc often don't apply. rc.diskless may terminate the rc script
# early or it may fall through, depending on the case.
#
if [ -f /etc/rc.diskless ]; then
if [ `/sbin/sysctl -n vfs.nfs.diskless_valid` != 0 ]; then
. /etc/rc.diskless
fi
fi
# Configure ccd devices.
if [ "X$skip_diskconf" != "XYES" -a -f /etc/ccd.conf ]; then
ccdconfig -C
fi
...
if [ "X$skip_diskconf" != "XYES" ]; then
swapon -a
fi
if [ "X$skip_diskconf" != "XYES" -a $1x = autobootx ]; then
...
else
echo Skipping disk checks ...
fi
( a couple of more minor skip_diskconf checks )
....
# Run custom disk mounting function ( typically setup by rc.diskless )
#
if [ "X$diskless_mount_func" != "X" ]; then
$diskless_mount_func
fi
... normal rc continues ...
# Do traditional rc.local file if it exists.
#
if [ -f $conf_dir/rc.local ]; then
echo -n 'starting local daemons:'
sh $conf_dir/rc.local
echo '.'
fi
--------
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Mon Jan 25 01:10:20 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id BAA15009
for freebsd-current-outgoing; Mon, 25 Jan 1999 01:10:20 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from asteroid.svib.ru (asteroid.svib.ru [195.151.166.145])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA14993
for <current@FreeBSD.ORG>; Mon, 25 Jan 1999 01:10:17 -0800 (PST)
(envelope-from tarkhil@asteroid.svib.ru)
Received: from shuttle.svib.ru (root@shuttle.svib.ru [195.151.166.144])
by asteroid.svib.ru (8.9.1a/8.9.1) with ESMTP id MAA17532
for <current@FreeBSD.ORG>; Mon, 25 Jan 1999 12:10:13 +0300 (MSK)
Received: from shuttle.svib.ru (tarkhil@minas-tirith.pol.ru [127.0.0.1])
by shuttle.svib.ru (8.8.8/8.8.8) with ESMTP id MAA08975
for <current@FreeBSD.ORG>; Mon, 25 Jan 1999 12:11:02 +0300 (MSK)
(envelope-from tarkhil@shuttle.svib.ru)
Message-Id: <199901250911.MAA08975@shuttle.svib.ru>
X-Mailer: exmh version 2.0.2 2/24/98
To: current@FreeBSD.ORG
Subject: Re: IDE DMA works, I'll be a...
In-reply-to: Your message "Sun, 24 Jan 1999 20:53:19 PST."
<199901250453.UAA00799@apollo.backplane.com>
Reply-To: tarkhil@asteroid.svib.ru
X-URL: http://freebsd.svib.ru
Mime-Version: 1.0
Content-Type: text/plain; charset=koi8-r
Content-Transfer-Encoding: 8bit
Date: Mon, 25 Jan 1999 12:11:01 +0300
From: Alex Povolotsky <tarkhil@asteroid.svib.ru>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
<199901250453.UAA00799@apollo.backplane.com>Matthew Dillon writes:
> archive:/cvs# time dd if=/dev/zero of=test2 bs=32k count=1024
> 1024+0 records in
> 1024+0 records out
> 33554432 bytes transferred in 13.700387 secs (2449159 bytes/sec)
> 0.000u 2.728s 0:13.75 19.7% 357+1405k 5+525io 1pf+0w
I'm getting the very same speed (on 3.0-RELEASE).
CPU: AMD-K6(tm) 3D processor (300.68-MHz 586-class CPU)
Origin = "AuthenticAMD" Id = 0x584 Stepping=4
Features=0x8001bf<FPU,VME,DE,PSE,TSC,MSR,MCE,CX8,MMX>
[no overclocking]
ide_pci0: <VIA 82C586x (Apollo) Bus-master IDE controller> rev 0x06 on pci0.7.1
wdc0 at 0x1f0-0x1f7 irq 14 flags 0xa0ffa0ff on isa
wdc0: unit 0 (wd0): <ST31722A>, DMA, 32-bit, multi-block-16
wd0: 1625MB (3329424 sectors), 3303 cyls, 16 heads, 63 S/T, 512 B/S
What should I check?
Alex.
--
Alexander B. Povolotsky [ICQ 18277558]
[2:5020/145] [http://freebsd.svib.ru] [tarkhil@asteroid.svib.ru]
[Urgent messages: 234-9696 ÁÂ.#35442 or tarkhil@pager.express.ru]
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Mon Jan 25 01:34:41 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id BAA17892
for freebsd-current-outgoing; Mon, 25 Jan 1999 01:34:41 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from send104.yahoomail.com (send104.yahoomail.com [205.180.60.122])
by hub.freebsd.org (8.8.8/8.8.8) with SMTP id BAA17887
for <freebsd-current@freebsd.org>; Mon, 25 Jan 1999 01:34:40 -0800 (PST)
(envelope-from thallgren@yahoo.com)
Message-ID: <19990125093736.6252.rocketmail@send104.yahoomail.com>
Received: from [131.116.188.2] by send104.yahoomail.com; Mon, 25 Jan 1999 01:37:36 PST
Date: Mon, 25 Jan 1999 01:37:36 -0800 (PST)
From: Tommy Hallgren <thallgren@yahoo.com>
Subject: (cont.) New Syscons and GGI
To: freebsd-current@FreeBSD.ORG
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
I found this log of an GGI irc meeting.
http://www.uk.ggi-project.org/irc/irc-980920-log
==
Regards: Tommy - The source of all good beers...
thallgren@yahoo.com
_________________________________________________________
DO YOU YAHOO!?
Get your free @yahoo.com address at http://mail.yahoo.com
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Mon Jan 25 01:40:20 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id BAA18651
for freebsd-current-outgoing; Mon, 25 Jan 1999 01:40:20 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from polaris.we.lc.ehu.es (polaris.we.lc.ehu.es [158.227.6.43])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA18637
for <freebsd-current@FreeBSD.ORG>; Mon, 25 Jan 1999 01:40:13 -0800 (PST)
(envelope-from jose@we.lc.ehu.es)
Received: from we.lc.ehu.es (tiburon [158.227.6.111])
by polaris.we.lc.ehu.es (8.9.1/8.9.1) with ESMTP id KAA07743;
Mon, 25 Jan 1999 10:39:23 +0100 (MET)
Message-ID: <36AC3BC5.A78565A2@we.lc.ehu.es>
Date: Mon, 25 Jan 1999 10:39:17 +0100
From: "Jose M. Alcaide" <jose@we.lc.ehu.es>
Organization: Universidad del Pais Vasco - Dept. de Electricidad y Electronica
X-Mailer: Mozilla 4.07 [en] (X11; U; FreeBSD 2.2.8-RELEASE i386)
MIME-Version: 1.0
To: Marco van Hylckama Vlieg <marco@windowmaker.org>
CC: freebsd-current@FreeBSD.ORG
Subject: Re: 3.0-CURRENT -> RELENG_3: trouble ?
References: <199901250239.DAA27263@pc2-c804.uibk.ac.at>
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
Marco van Hylckama Vlieg wrote:
>
> I'm running 3.0-CURRENT at the moment, last timme I built world is
> about 2 or 3 weeks ago I guess. What I want to do is go to 3.0-RELEASE
> and from then start keeping track of the 3.x-STABLE branch.
>
> Since I've read a lot about various problems people had with this
> I now wonder: is it safe to CVSUP to RELENG_3 right now or will bad
> things happen? I don't want to mess up my system.
I did the 3.0-CURRENT --> 3.0-STABLE transition the last weekend
without _any_ problem. Usually I cvsup every night, but I disabled
this process just before the branch. One day after the branch
I restarted the cvsup procedure, this time tracking RELENG_3.
I "made the world" on last Saturday and everything worked fine
[as usual :-)].
> If someone could give me some guidelines on how to get going on the
> above described track or point me to a webpage/document or anything else
> that describes what to do I'd be eternally grateful. At the moment it's
> very unclear to me what to do and whether I'll be able to boot and/or
> login to my system after I went to RELENG_3.
>
> I'm running 3.0-CURRENT with everything ELF including the kernel.
If you "made the world" before, simply repeat the procedure. Remember
that there is an excellent tutorial written by Nik Clayton.
-- JMA
-----------------------------------------------------------------------
José Mª Alcaide | mailto:jose@we.lc.ehu.es
Universidad del País Vasco | http://www.we.lc.ehu.es/~jose
Dpto. de Electricidad y Electrónica |
Facultad de Ciencias - Campus de Lejona | Tel.: +34-946012479
48940 Lejona (Vizcaya) - SPAIN | Fax: +34-944858139
-----------------------------------------------------------------------
"Go ahead... make my day." - H. Callahan
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Mon Jan 25 01:54:28 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id BAA20001
for freebsd-current-outgoing; Mon, 25 Jan 1999 01:54:28 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from freebsd.dk (freebsd.dk [212.242.42.178])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA19996
for <freebsd-current@FreeBSD.ORG>; Mon, 25 Jan 1999 01:54:24 -0800 (PST)
(envelope-from sos@freebsd.dk)
Received: (from sos@localhost)
by freebsd.dk (8.9.1/8.9.1) id KAA28306;
Mon, 25 Jan 1999 10:54:20 +0100 (CET)
(envelope-from sos)
From: Søren Schmidt <sos@freebsd.dk>
Message-Id: <199901250954.KAA28306@freebsd.dk>
Subject: Re: New Syscons and GGI
In-Reply-To: <19990125090940.490.rocketmail@send104.yahoomail.com> from Tommy Hallgren at "Jan 25, 1999 1: 9:40 am"
To: thallgren@yahoo.com (Tommy Hallgren)
Date: Mon, 25 Jan 1999 10:54:19 +0100 (CET)
Cc: freebsd-current@FreeBSD.ORG
X-Mailer: ELM [version 2.4ME+ PL43 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
It seems Tommy Hallgren wrote:
> Hi!
>
> Now that the console system is restructured, shouldn't we consider
> using GGI instead of inventing the wheel?
>
> I happened to find this link and they seem to be positive to
> supporting FreeBSD.
>
> http://synergy.caltech.edu/~ggi/mailinglist/ev-mar98/139.html
Hmm, I've been following what they are doing for quite awhile,
and frankly I dont see why we should move at this point in time.
However it is possible to write a KLD module that would provide
the hooks for a GGI compliant interface, so you could write such
a beast if you want GGI functionality.
There also is a licencing problem with GGI, the kernel gunk is
IIRC free under a BSD like licence, but the userland stuff are
GPL, which we try to stay clear of for obvious reasons.
- Søren
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Mon Jan 25 02:46:13 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id CAA26360
for freebsd-current-outgoing; Mon, 25 Jan 1999 02:46:13 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from labinfo.iet.unipi.it (labinfo.iet.unipi.it [131.114.9.5])
by hub.freebsd.org (8.8.8/8.8.8) with SMTP id CAA26021
for <current@FreeBSD.ORG>; Mon, 25 Jan 1999 02:43:38 -0800 (PST)
(envelope-from luigi@labinfo.iet.unipi.it)
Received: from localhost (luigi@localhost) by labinfo.iet.unipi.it (8.6.5/8.6.5) id JAA26243; Mon, 25 Jan 1999 09:25:22 +0100
From: Luigi Rizzo <luigi@labinfo.iet.unipi.it>
Message-Id: <199901250825.JAA26243@labinfo.iet.unipi.it>
Subject: Re: beginnings of a diskless boot sequence being committed
To: dillon@apollo.backplane.com (Matthew Dillon)
Date: Mon, 25 Jan 1999 09:25:22 +0100 (MET)
Cc: current@FreeBSD.ORG
In-Reply-To: <199901250902.BAA02600@apollo.backplane.com> from "Matthew Dillon" at Jan 25, 99 01:02:17 am
X-Mailer: ELM [version 2.4 PL23]
Content-Type: text
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
> :> Basically this consists of a bit of code in /etc/rc and, later tonight,
> :> an /etc/rc.diskless script ( a new script ).
> :
> :before you reinvent the wheel, have you looked at my code in
> :http://www.iet.unipi.it/~luigi/diskless981113/
...
> I was basically just cleaning up stuff I've been using for several
> months.
me too :)
> Your stuff looks quite similar.
>
> What I propose is that a new kernel sysctl variable be added called
> 'kern.conf_dir' which the kernel initially sets to nothing.
ok, i can only suggest that if you replace the sysctl kern.conf_dir
variable with a shell variable as i did, you can achieve a more
portable result (this also in light of Jordan's idea of having a
2.2S CD being made... putting patches for diskless into some
'xperimnt' directory would be helpful). Other than that, i have no
objections, and i am very glad you raised the issue since i am
using diskless machines a lot!
I haven't seen how you suggest to build&populate the MFS filesystems --
right now i use a rather crude method of putting all the stuff in a tgz
archive on the server and expanding it at runtime on the client. I
haven't solved the problem with passwords (i.e. i just copy the files
from the server. -- this is clearly a security hole, perhaps YP-based
solutions would be much better).
cheers
luigi
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Mon Jan 25 03:03:10 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id DAA27945
for freebsd-current-outgoing; Mon, 25 Jan 1999 03:03:10 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from gatekeeper.tsc.tdk.com (gatekeeper.tsc.tdk.com [207.113.159.21])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA27930
for <current@FreeBSD.ORG>; Mon, 25 Jan 1999 03:03:07 -0800 (PST)
(envelope-from gdonl@tsc.tdk.com)
Received: from sunrise.gv.tsc.tdk.com (root@sunrise.gv.tsc.tdk.com [192.168.241.191])
by gatekeeper.tsc.tdk.com (8.8.8/8.8.8) with ESMTP id DAA07130;
Mon, 25 Jan 1999 03:03:00 -0800 (PST)
(envelope-from gdonl@tsc.tdk.com)
Received: from salsa.gv.tsc.tdk.com (salsa.gv.tsc.tdk.com [192.168.241.194])
by sunrise.gv.tsc.tdk.com (8.8.5/8.8.5) with ESMTP id DAA18354;
Mon, 25 Jan 1999 03:02:59 -0800 (PST)
Received: (from gdonl@localhost)
by salsa.gv.tsc.tdk.com (8.8.5/8.8.5) id DAA25921;
Mon, 25 Jan 1999 03:02:58 -0800 (PST)
From: Don Lewis <Don.Lewis@tsc.tdk.com>
Message-Id: <199901251102.DAA25921@salsa.gv.tsc.tdk.com>
Date: Mon, 25 Jan 1999 03:02:57 -0800
In-Reply-To: Warner Losh <imp@village.org>
"Re: keymaps" (Jan 21, 9:40pm)
X-Mailer: Mail User's Shell (7.2.6 alpha(3) 7/19/95)
To: Warner Losh <imp@village.org>
Subject: Re: keymaps
Cc: current@FreeBSD.ORG
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
On Jan 21, 9:40pm, Warner Losh wrote:
} Subject: Re: keymaps
} In message <199901220043.LAA22437@lightning.itga.com.au> Gregory Bond writes:
} : my vote: A version of the standard keymap with CapsLock and LeftCtl
} : functions swapped so the control key is under my left finger like
} : God intended!
}
} What's wrong with us.unix.kbd?
Two things for me:
It's not in the sysinstall menu.
I'm not sure I like the Esc <-> ~` swap.
Does anyone know of any decent PC keyboards with a Unix-friendly layout?
I'm pretty happy with the layout on a Sun Type-5 keyboard, which puts
Esc right above Tab and to the left of 1 (where PC's generally have ~`).
The Return key is wide, but is confined to the home row, and Backspace
is also wide and is in the row immediately above it. This leaves room
in the top row (below the function keys, where PC's put Backspace),
for |\, which PC keyboards put in various random places, and ~`.
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Mon Jan 25 03:27:19 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id DAA00825
for freebsd-current-outgoing; Mon, 25 Jan 1999 03:27:19 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from spinner.netplex.com.au (spinner.netplex.com.au [202.12.86.3])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA00820
for <current@FreeBSD.ORG>; Mon, 25 Jan 1999 03:27:15 -0800 (PST)
(envelope-from peter@netplex.com.au)
Received: from spinner.netplex.com.au (localhost [127.0.0.1])
by spinner.netplex.com.au (8.9.2/8.9.2/Netplex) with ESMTP id TAA03489;
Mon, 25 Jan 1999 19:24:59 +0800 (WST)
(envelope-from peter@spinner.netplex.com.au)
Message-Id: <199901251124.TAA03489@spinner.netplex.com.au>
X-Mailer: exmh version 2.0.2 2/24/98
To: Luigi Rizzo <luigi@labinfo.iet.unipi.it>
cc: dillon@apollo.backplane.com (Matthew Dillon), current@FreeBSD.ORG
Subject: Re: beginnings of a diskless boot sequence being committed
In-reply-to: Your message of "Mon, 25 Jan 1999 09:25:22 +0100."
<199901250825.JAA26243@labinfo.iet.unipi.it>
Date: Mon, 25 Jan 1999 19:24:59 +0800
From: Peter Wemm <peter@netplex.com.au>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
Luigi Rizzo wrote:
[..]
> I haven't seen how you suggest to build&populate the MFS filesystems --
> right now i use a rather crude method of putting all the stuff in a tgz
> archive on the server and expanding it at runtime on the client. I
> haven't solved the problem with passwords (i.e. i just copy the files
> from the server. -- this is clearly a security hole, perhaps YP-based
> solutions would be much better).
Didn't Matt have patches for initializing a MFS from a mmap'ed file rather
than from swap at some point?
Cheers,
-Peter
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Mon Jan 25 03:28:24 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id DAA01071
for freebsd-current-outgoing; Mon, 25 Jan 1999 03:28:24 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from caladan.tdx.co.uk (caladan.tdx.co.uk [195.188.177.4])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA01066
for <current@freebsd.org>; Mon, 25 Jan 1999 03:28:22 -0800 (PST)
(envelope-from kpielorz@tdx.co.uk)
Received: from tdx.co.uk (lorca-tx.tdx.co.uk [195.188.177.242])
by caladan.tdx.co.uk (8.9.2/8.9.2) with ESMTP id LAA00847
for <current@freebsd.org>; Mon, 25 Jan 1999 11:28:18 GMT
Message-ID: <36AC5551.F9E99D45@tdx.co.uk>
Date: Mon, 25 Jan 1999 11:28:17 +0000
From: Karl Pielorz <kpielorz@tdx.co.uk>
Organization: TDX - The Digital eXchange
X-Mailer: Mozilla 4.5 [en] (WinNT; I)
X-Accept-Language: en
MIME-Version: 1.0
To: current@FreeBSD.ORG
Subject: IDE DMA problems? (4.0-current as of 01/24/99 ~01:10)
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
Hi,
Just finsihed upgrading to 4.0-Current, and both my machines now come up with:
wd0: DMA failure, DMA status 0
wd0: DMA failure, DMA status 0
wd2: DMA failure, DMA status 0
wd2: DMA failure, DMA status 0
wd1: DMA failure, DMA status 0
wd3: DMA failure, DMA status 0
wd3: DMA failure, DMA status 0
wd1: DMA failure, DMA status 0
wd1: DMA failure, DMA status 0
(basically that error for all IDE drives installed).
Both motherboards are P-Pro's (ones a dual, ones a single) - using Intel 440FX
chipset's...
DMesg shows:
wdc0 at 0x1f0-0x1f7 irq 14 flags 0x20002000 on isa
wdc0: unit 0 (wd0): <QUANTUM FIREBALL SE4.3A>, DMA
wd0: 4110MB (8418816 sectors), 14848 cyls, 9 heads, 63 S/T, 512 B/S
wdc0: unit 1 (wd1): <QUANTUM FIREBALL ST2.1A>, DMA
wd1: 2014MB (4124736 sectors), 4092 cyls, 16 heads, 63 S/T, 512 B/S
wdc1 at 0x170-0x177 irq 15 flags 0x20002000 on isa
wdc1: unit 0 (wd2): <QUANTUM FIREBALL SE4.3A>, DMA
wd2: 4110MB (8418816 sectors), 14848 cyls, 9 heads, 63 S/T, 512 B/S
wdc1: unit 1 (wd3): <QUANTUM SIROCCO2550A>, DMA
wd3: 2445MB (5008752 sectors), 4969 cyls, 16 heads, 63 S/T, 512 B/S
I never got these 'failures' before... (They keep popping up on the console as
well :-(
Can they be ignored? Can they be fixed? :) - The drives appear to work OK...
The more the drives get access, the more messages I get (I guess
understandably)...
-Kp
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Mon Jan 25 03:40:46 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id DAA01877
for freebsd-current-outgoing; Mon, 25 Jan 1999 03:40:46 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from freebsd.dk (freebsd.dk [212.242.42.178])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA01872
for <current@FreeBSD.ORG>; Mon, 25 Jan 1999 03:40:43 -0800 (PST)
(envelope-from sos@freebsd.dk)
Received: (from sos@localhost)
by freebsd.dk (8.9.1/8.9.1) id MAA28486;
Mon, 25 Jan 1999 12:40:32 +0100 (CET)
(envelope-from sos)
From: Søren Schmidt <sos@freebsd.dk>
Message-Id: <199901251140.MAA28486@freebsd.dk>
Subject: Re: IDE DMA problems? (4.0-current as of 01/24/99 ~01:10)
In-Reply-To: <36AC5551.F9E99D45@tdx.co.uk> from Karl Pielorz at "Jan 25, 1999 11:28:17 am"
To: kpielorz@tdx.co.uk (Karl Pielorz)
Date: Mon, 25 Jan 1999 12:40:32 +0100 (CET)
Cc: current@FreeBSD.ORG
X-Mailer: ELM [version 2.4ME+ PL43 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
It seems Karl Pielorz wrote:
This is due to Julians commit in 1.183 (IIRC) of wd.c, its bogus :(
The following patchh cures the mess, and fixes a couble of other
nits as well:
-Søren
Index: wd.c
===================================================================
RCS file: /home/ncvs/src/sys/i386/isa/wd.c,v
retrieving revision 1.186
diff -u -r1.186 wd.c
--- wd.c 1999/01/17 05:46:24 1.186
+++ wd.c 1999/01/19 18:29:23
@@ -1084,10 +1086,11 @@
du = wddrives[dkunit(bp->b_dev)];
/* finish off DMA */
- if (du->dk_flags & (DKFL_DMA|DKFL_USEDMA)) {
+ if ((du->dk_flags & (DKFL_DMA|DKFL_SINGLE)) == DKFL_DMA) {
/* XXX SMP boxes sometimes generate an early intr. Why? */
- if ((wddma[du->dk_interface].wdd_dmastatus(du->dk_dmacookie) & WDDS_INTERRUPT)
- != 0)
+ if ((wddma[du->dk_interface].wdd_dmastatus(du->dk_dmacookie) &
+ WDDS_INTERRUPT) == 0)
+ return;
dmastat = wddma[du->dk_interface].wdd_dmadone(du->dk_dmacookie);
}
@@ -1568,6 +1571,7 @@
if (wdwait(du, 0, TIMEOUT) < 0)
return (1);
if( command == WDCC_FEATURES) {
+ outb(wdc + wd_sdh, WDSD_IBM | (du->dk_unit << 4) | head);
outb(wdc + wd_features, count);
if ( count == WDFEA_SETXFER )
outb(wdc + wd_seccnt, sector);
@@ -2289,9 +2293,8 @@
{
int err = 0;
- if ((du->dk_flags & (DKFL_DMA|DKFL_USEDMA)) && du->dk_dmacookie)
+ if ((du->dk_flags & (DKFL_DMA|DKFL_SINGLE)) == DKFL_DMA)
wddma[du->dk_interface].wdd_dmadone(du->dk_dmacookie);
-
(void)wdwait(du, 0, TIMEOUT);
outb(du->dk_altport, WDCTL_IDS | WDCTL_RST);
DELAY(10 * 1000);
> Hi,
>
> Just finsihed upgrading to 4.0-Current, and both my machines now come up with:
>
> wd0: DMA failure, DMA status 0
> wd0: DMA failure, DMA status 0
> wd2: DMA failure, DMA status 0
> wd2: DMA failure, DMA status 0
> wd1: DMA failure, DMA status 0
> wd3: DMA failure, DMA status 0
> wd3: DMA failure, DMA status 0
> wd1: DMA failure, DMA status 0
> wd1: DMA failure, DMA status 0
>
> (basically that error for all IDE drives installed).
>
> Both motherboards are P-Pro's (ones a dual, ones a single) - using Intel 440FX
> chipset's...
>
> DMesg shows:
>
> wdc0 at 0x1f0-0x1f7 irq 14 flags 0x20002000 on isa
> wdc0: unit 0 (wd0): <QUANTUM FIREBALL SE4.3A>, DMA
> wd0: 4110MB (8418816 sectors), 14848 cyls, 9 heads, 63 S/T, 512 B/S
> wdc0: unit 1 (wd1): <QUANTUM FIREBALL ST2.1A>, DMA
> wd1: 2014MB (4124736 sectors), 4092 cyls, 16 heads, 63 S/T, 512 B/S
> wdc1 at 0x170-0x177 irq 15 flags 0x20002000 on isa
> wdc1: unit 0 (wd2): <QUANTUM FIREBALL SE4.3A>, DMA
> wd2: 4110MB (8418816 sectors), 14848 cyls, 9 heads, 63 S/T, 512 B/S
> wdc1: unit 1 (wd3): <QUANTUM SIROCCO2550A>, DMA
> wd3: 2445MB (5008752 sectors), 4969 cyls, 16 heads, 63 S/T, 512 B/S
>
>
> I never got these 'failures' before... (They keep popping up on the console as
> well :-(
>
> Can they be ignored? Can they be fixed? :) - The drives appear to work OK...
> The more the drives get access, the more messages I get (I guess
> understandably)...
>
> -Kp
>
> To Unsubscribe: send mail to majordomo@FreeBSD.org
> with "unsubscribe freebsd-current" in the body of the message
>
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Mon Jan 25 04:30:50 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id EAA08529
for freebsd-current-outgoing; Mon, 25 Jan 1999 04:30:50 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from drama.navinet.net (drama.navinet.net [206.25.93.8])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA08521
for <current@freebsd.org>; Mon, 25 Jan 1999 04:30:48 -0800 (PST)
(envelope-from forrie@drama.navinet.net)
Received: (from forrie@localhost)
by drama.navinet.net (8.9.2/8.9.2) id HAA11080;
Mon, 25 Jan 1999 07:30:30 -0500 (EST)
Date: Mon, 25 Jan 1999 07:30:30 -0500
From: Forrest Aldrich <forrie@drama.navinet.net>
To: Edwin Culp <eculp@MexComUSA.net>
Cc: current@FreeBSD.ORG
Subject: Re: 4.0-Current, netscape halts system
Message-ID: <19990125073030.A11018@drama.navinet.net>
References: <1476.917220230@zippy.cdrom.com> <199901250020.QAA22590@bubba.whistle.com> <199901250147.SAA03468@mt.sri.com> <36ABED16.111D4ACB@MexComUSA.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.95.1i
In-Reply-To: <36ABED16.111D4ACB@MexComUSA.net>; from Edwin Culp on Sun, Jan 24, 1999 at 08:03:34PM -0800
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
I've a feeling that somewhere there is a memory
problem. Netscape-specific perhaps, but I suspect
otherwise due to what I've seen.
For example: the one machine that I have which
will constantly dump core when Netscape is run
is an HP Vectra. I've tried 3.0, 2.2.8, all current
patches, etc. Core dump. Yet when I loaded Linux,
it worked without incident.
I have not yet tried Linux emulation, but will give
it a shot.
I suspected that perhaps the netscape binary needed
to be recompiled against a current system. Why?
System calls are updated, etc. There might be
something really funky going on. The fact that it's
stripped of debugging symbols doesn't help much --
but perhaps someone more adept at debugging might
take a moment to look into it.
Forrest
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Mon Jan 25 05:02:42 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id FAA12046
for freebsd-current-outgoing; Mon, 25 Jan 1999 05:02:42 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from ns.tar.com (ns.tar.com [204.95.187.2])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA12038
for <current@FreeBSD.ORG>; Mon, 25 Jan 1999 05:02:39 -0800 (PST)
(envelope-from dick@ns.tar.com)
Received: (from dick@localhost)
by ns.tar.com (8.9.2/8.9.1) id HAA13963;
Mon, 25 Jan 1999 07:02:09 -0600 (CST)
(envelope-from dick)
Date: Mon, 25 Jan 1999 07:02:08 -0600
From: "Richard Seaman, Jr." <dick@tar.com>
To: grog@lemis.com
Cc: Bruce Evans <bde@zeta.org.au>, lcremean@tidalwave.net, current@FreeBSD.ORG
Subject: Re: IDE DMA works, I'll be a...
Message-ID: <19990125070208.C445@tar.com>
References: <199901250608.RAA24912@godzilla.zeta.org.au>
Mime-Version: 1.0
Content-Type: multipart/mixed; boundary="rS8CxjVDS/+yyDmU"
X-Mailer: Mutt 0.95i
In-Reply-To: <199901250608.RAA24912@godzilla.zeta.org.au>; from Bruce Evans on Mon, Jan 25, 1999 at 05:08:19PM +1100
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
--rS8CxjVDS/+yyDmU
Content-Type: text/plain; charset=us-ascii
On Mon, Jan 25, 1999 at 05:08:19PM +1100, Bruce Evans wrote:
> >> Can you find out what chipset is in this guy? There's support for anything
> >> Intel or VIA, Promise UDMA cards, Cyrix MediaGX, and Acer Aladdin IV/V right
> >> now.
> >
> >See kern/9550. The driver *used* to support my SiS chipset, but it no
> >longer does when both master and slave drive are present since I
> >updated about a week ago. Possibly the same bug is biting Matt.
>
> The driver doesn't have any special support for SiS. It uses generic
> support in some cases, apparently including your case. Recent fixes
> made it actually initialize DMA on the correct drive, but the
> initialization in generic_dmainit() is buggy (it assumes multi-word
> DMA mode 2 but your IDE timing is apparently incompatible with this).
I also experienced breakage with a SiS chip set. The following lines of
code in generic_dmainit in ide_pci.c are the problem:
/* If we're here, then this controller is most likely not set
for UDMA, even if the drive may be. Make the drive wise
up. */
if(!wdcmd(WDDMA_MDMA2, wdinfo))
printf("generic_dmainit: could not set multiword DMA mode!\n");
You can try the attached patch if you want. It seems to work here.
--
Richard Seamman, Jr. email: dick@tar.com
5182 N. Maple Lane phone: 414-367-5450
Chenequa WI 53058 fax: 414-367-5852
--rS8CxjVDS/+yyDmU
Content-Type: text/plain; charset=us-ascii
Content-Disposition: attachment; filename=sisdiff
Index: ide_pci.c
===================================================================
RCS file: /home/ncvs/src/sys/pci/ide_pci.c,v
retrieving revision 1.28
diff -c -r1.28 ide_pci.c
*** ide_pci.c 1999/01/17 05:46:25 1.28
--- ide_pci.c 1999/01/20 18:06:54
***************
*** 110,115 ****
--- 110,124 ----
static void
generic_status(struct ide_pci_cookie *cookie);
+ static int
+ sis_dmainit(struct ide_pci_cookie *cookie,
+ struct wdparams *wp,
+ int (*wdcmd)(int, void *),
+ void *wdinfo);
+
+ static void
+ sis_status(struct ide_pci_cookie *cookie);
+
static void
via_571_status(struct ide_pci_cookie *cookie);
***************
*** 279,285 ****
/* If we're here, then this controller is most likely not set
for UDMA, even if the drive may be. Make the drive wise
up. */
!
if(!wdcmd(WDDMA_MDMA2, wdinfo))
printf("generic_dmainit: could not set multiword DMA mode!\n");
return 1;
--- 288,294 ----
/* If we're here, then this controller is most likely not set
for UDMA, even if the drive may be. Make the drive wise
up. */
!
if(!wdcmd(WDDMA_MDMA2, wdinfo))
printf("generic_dmainit: could not set multiword DMA mode!\n");
return 1;
***************
*** 303,308 ****
--- 312,527 ----
generic_status
};
+ /* SiS 5591 */
+
+ static int
+ sis_dmainit(struct ide_pci_cookie *cookie,
+ struct wdparams *wp,
+ int(*wdcmd)(int, void *),
+ void *wdinfo)
+ {
+ int r;
+ unsigned int workword, new, mask;
+ int ctlr, unit;
+ int iobase_bm;
+ pcici_t tag;
+ int unitno;
+
+ unit = cookie->unit;
+ ctlr = cookie->ctlr;
+ iobase_bm = cookie->iobase_bm;
+ tag = cookie->tag;
+
+ unitno = ctlr * 2 + unit;
+
+ if (udma_mode(wp) >= 2) {
+ workword = pci_conf_read(tag, ctlr * 4 + 0x40);
+
+ /* These settings are a little arbitrary. They're taken from my
+ * system, where the BIOS has already set the values, but where
+ * we don't detect that we're initialized because the
+ * BMISTA_DMA?CAP values aren't set by the BIOS.
+ * 0x8000 turns on UDMA
+ * 0x2000 sets UDMA cycle time to 2 PCI clocks for data out
+ * 0x0300 sets DATC to 3 PCI clocks
+ * 0x0001 sets DRTC to 1 PCI clock
+ */
+ if (unit) {
+ mask = 0x0000ffff;
+ new = 0xa3010000;
+ } else {
+ mask = 0xffff0000;
+ new = 0x0000a301;
+ }
+
+ workword &= mask;
+ workword |= new;
+
+ pci_conf_write(tag, ctlr * 4 + 0x40, workword);
+
+ outb(iobase_bm + BMISTA_PORT,
+ (inb(iobase_bm + BMISTA_PORT) | ((unit == 0) ? BMISTA_DMA0CAP : BMISTA_DMA1CAP)));
+
+ if (bootverbose)
+ printf("SiS 5591 dmainit: %s drive %d setting ultra DMA mode 2\n",
+ unitno < 2 ? "primary" : "secondary",
+ unitno & 1);
+ r = wdcmd(WDDMA_UDMA2, wdinfo);
+ if (!r) {
+ printf("SiS 5591 dmainit: %s drive %d setting DMA mode failed\n",
+ unitno < 2 ? "primary" : "secondary",
+ unitno & 1);
+ return 0;
+ }
+
+ if (bootverbose)
+ sis_status(cookie);
+
+ return 1;
+
+ }
+
+ /* otherwise, try and program it for MW DMA mode 2 */
+ else if (mwdma_mode(wp) >= 2 && pio_mode(wp) >= 4) {
+ workword = pci_conf_read(tag, ctlr * 4 + 0x40);
+
+ /* These settings are a little arbitrary. They're taken from my
+ * system, where the BIOS has already set the values, but where
+ * we don't detect that we're initialized because the
+ * BMISTA_DMA?CAP values aren't set by the BIOS.
+ * 0x0300 sets DATC to 3 PCI clocks
+ * 0x0001 sets DRTC to 1 PCI clock
+ */
+ if (unit) {
+ mask = 0x0000ffff;
+ new = 0x03010000;
+ } else {
+ mask = 0xffff0000;
+ new = 0x00000301;
+ }
+
+ workword &= mask;
+ workword |= new;
+
+ pci_conf_write(tag, ctlr * 4 + 0x40, workword);
+
+ outb(iobase_bm + BMISTA_PORT,
+ (inb(iobase_bm + BMISTA_PORT) | ((unit == 0) ? BMISTA_DMA0CAP : BMISTA_DMA1CAP)));
+
+ /* Set multiword DMA mode 2 on drive */
+ if (bootverbose)
+ printf("SiS 5591 dmainit: %s drive %d setting multiword DMA mode 2\n",
+ unitno < 2 ? "primary" : "secondary",
+ unitno & 1);
+ r = wdcmd(WDDMA_MDMA2, wdinfo);
+ if (!r) {
+ printf("SiS 5591 dmainit: %s drive %d setting DMA mode failed\n",
+ unitno < 2 ? "primary" : "secondary",
+ unitno & 1);
+ return 0;
+ }
+
+ if (bootverbose)
+ sis_status(cookie);
+
+ return 1;
+
+ }
+ return 0;
+ }
+
+ static void
+ sis_status(struct ide_pci_cookie *cookie)
+ {
+ int iobase_wd;
+ int ctlr, unit;
+ int iobase_bm;
+ pcici_t tag;
+ pcidi_t type;
+ u_int word40[5];
+ int i, unitno;
+ int DRTC, DATC;
+ int val;
+
+ iobase_wd = cookie->iobase_wd;
+ unit = cookie->unit;
+ ctlr = cookie->ctlr;
+ iobase_bm = cookie->iobase_bm;
+ tag = cookie->tag;
+ type = cookie->type;
+
+ unitno = ctlr * 2 + unit;
+
+ for (i=0; i<5; i++) {
+ word40[i] = pci_conf_read(tag, i * 4 + 0x40);
+ }
+
+ DRTC = word40[ctlr] >> (16 * unit);
+ DATC = word40[ctlr] >> (8 + 16*unit);
+
+ if (unitno == 0) {
+ if ((word40[4] & 0x80000) == 0) {
+ val = word40[2] & 0xf;
+ if (val == 0)
+ val = 12;
+ else if (val > 11)
+ val++;
+ printf ("SiS 5591 status: CRTC %d PCICLK, ", val);
+ val = (word40[2] >> 8) & 0x7;
+ if (val == 0)
+ val = 8 ;
+ else if (val > 6)
+ val = 12;
+ printf ("CATC %d PCICLK, applies to all IDE devices\n", val);
+ } else {
+ printf ("SiS 5591 status: CRTC and CATC timings are per device, taken from DRTC and DATC\n");
+ }
+ printf ("SiS 5591 status: burst cycles %s, fast post write control %s\n",
+ ((word40[2] >> 16) & 0x80) ? "enabled" : "disabled",
+ ((word40[2] >> 16) & 0x20) ? "enabled" : "disabled");
+
+ }
+ val = DRTC & 0xf;
+ if (val == 0)
+ val = 12;
+ else if (val > 11)
+ val++;
+ printf ("SiS 5591 status: %s drive %d DRTC %d PCICLK,",
+ unitno < 2 ? "primary" : "secondary",
+ unitno & 1,
+ val);
+ val = DATC & 0x7;
+ if (val == 0)
+ val = 8 ;
+ else if (val > 6)
+ val = 12;
+ printf (" DATC %d PCICLK\n", val);
+ printf ("SiS 5591 status: %s drive %d Ultra DMA %s",
+ unitno < 2 ? "primary" : "secondary",
+ unitno & 1,
+ (DATC & 0x80) ? "enabled" : "disabled\n");
+ if (DATC & 0x80)
+ printf (", %d PCICLK data out\n", ((DATC >> 5) & 0x3) + 1);
+ printf ("SiS 5591 status: %s drive %d postwrite %s, prefetch %s prefetch count is %d\n",
+ unitno < 2 ? "primary" : "secondary",
+ unitno & 1,
+ ((word40[2] >> (28 + unitno)) & 1) ? "enabled" : "disabled",
+ ((word40[2] >> (24 + unitno)) & 1) ? "enabled" : "disabled",
+ (word40[3] >> (16 * ctlr)) & 0xffff);
+ printf ("SiS 5591 status: %s drive %d has%s been configured for DMA\n",
+ unitno < 2 ? "primary" : "secondary",
+ unitno & 1,
+ (inb(iobase_bm + BMISTA_PORT) & ((unit == 0) ? BMISTA_DMA0CAP : BMISTA_DMA1CAP)) ?
+ " " : " not");
+ }
+
+ static struct vendor_fns vs_sis =
+ {
+ sis_dmainit,
+ sis_status
+ };
+
+
/* VIA Technologies "82C571" PCI-IDE controller core */
static void
***************
*** 1169,1174 ****
--- 1388,1395 ----
return ("Cyrix 5530 Bus-master IDE controller");
if (type == 0x522910b9)
return ("Acer Aladdin IV/V (M5229) Bus-master IDE controller");
+ if (type == 0x55131039)
+ return ("SiS 5591 Bus-master IDE Controller");
if (data & 0x8000)
return ("PCI IDE controller (busmaster capable)");
#ifndef CMD640
***************
*** 1238,1243 ****
--- 1459,1467 ----
break;
case 0x522910B9: /* Acer Aladdin IV/V (M5229) */
vp = &vs_acer;
+ break;
+ case 0x55131039: /* SiS 5591 */
+ vp = &vs_sis;
break;
default:
/* everybody else */
--rS8CxjVDS/+yyDmU--
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Mon Jan 25 05:06:47 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id FAA12383
for freebsd-current-outgoing; Mon, 25 Jan 1999 05:06:47 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from st-lcremean.tidalwave.net (st-lcremean.tidalwave.net [208.213.203.186])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA12378
for <current@FreeBSD.ORG>; Mon, 25 Jan 1999 05:06:44 -0800 (PST)
(envelope-from lee@st-lcremean.tidalwave.net)
Received: (from lee@localhost)
by st-lcremean.tidalwave.net (8.9.2/8.9.2) id IAA03464;
Mon, 25 Jan 1999 08:06:17 -0500 (EST)
(envelope-from lee)
Message-ID: <19990125080617.A3456@tidalwave.net>
Date: Mon, 25 Jan 1999 08:06:17 -0500
From: Lee Cremeans <lee@st-lcremean.tidalwave.net>
To: tarkhil@asteroid.svib.ru, current@FreeBSD.ORG
Subject: Re: IDE DMA works, I'll be a...
Reply-To: lcremean@tidalwave.net
References: <199901250453.UAA00799@apollo.backplane.com> <199901250911.MAA08975@shuttle.svib.ru>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.93.2i
In-Reply-To: <199901250911.MAA08975@shuttle.svib.ru>; from Alex Povolotsky on Mon, Jan 25, 1999 at 12:11:01PM +0300
X-OS: FreeBSD 3.0-CURRENT
X-Evil: microsoft.com
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
On Mon, Jan 25, 1999 at 12:11:01PM +0300, Alex Povolotsky wrote:
> <199901250453.UAA00799@apollo.backplane.com>Matthew Dillon writes:
> > archive:/cvs# time dd if=/dev/zero of=test2 bs=32k count=1024
> > 1024+0 records in
> > 1024+0 records out
> > 33554432 bytes transferred in 13.700387 secs (2449159 bytes/sec)
> > 0.000u 2.728s 0:13.75 19.7% 357+1405k 5+525io 1pf+0w
>
> I'm getting the very same speed (on 3.0-RELEASE).
>
> CPU: AMD-K6(tm) 3D processor (300.68-MHz 586-class CPU)
> Origin = "AuthenticAMD" Id = 0x584 Stepping=4
> Features=0x8001bf<FPU,VME,DE,PSE,TSC,MSR,MCE,CX8,MMX>
> [no overclocking]
> ide_pci0: <VIA 82C586x (Apollo) Bus-master IDE controller> rev 0x06 on pci0.7.1
> wdc0 at 0x1f0-0x1f7 irq 14 flags 0xa0ffa0ff on isa
> wdc0: unit 0 (wd0): <ST31722A>, DMA, 32-bit, multi-block-16
> wd0: 1625MB (3329424 sectors), 3303 cyls, 16 heads, 63 S/T, 512 B/S
>
> What should I check?
You need to update to 3.0-STABLE; bde committed some fixes to the VIA UDMA
code there.
--
+--------------------------------------------------------------------+
| Lee Cremeans -- Manassas, VA, USA (WakkyMouse on DALnet and WTnet)|
| lcremean@tidalwave.net| http://st-lcremean.tidalwave.net/~lee |
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Mon Jan 25 05:23:03 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id FAA14006
for freebsd-current-outgoing; Mon, 25 Jan 1999 05:23:03 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from awfulhak.org (awfulhak.force9.co.uk [195.166.136.63])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA13988;
Mon, 25 Jan 1999 05:22:58 -0800 (PST)
(envelope-from brian@Awfulhak.org)
Received: from keep.lan.Awfulhak.org (brian@keep.lan.Awfulhak.org [172.16.0.8])
by awfulhak.org (8.8.8/8.8.8) with ESMTP id NAA04154;
Mon, 25 Jan 1999 13:22:49 GMT
(envelope-from brian@Awfulhak.org)
Received: from keep.lan.Awfulhak.org (brian@localhost [127.0.0.1])
by keep.lan.Awfulhak.org (8.9.2/8.9.2) with ESMTP id JAA09098;
Mon, 25 Jan 1999 09:54:29 GMT
(envelope-from brian@keep.lan.Awfulhak.org)
Message-Id: <199901250954.JAA09098@keep.lan.Awfulhak.org>
X-Mailer: exmh version 2.0.2 2/24/98
To: Archie Cobbs <archie@whistle.com>
cc: arch@FreeBSD.ORG, current@FreeBSD.ORG
Subject: Re: DEVFS, the time has come...
In-reply-to: Your message of "Sat, 23 Jan 1999 01:10:32 PST."
<199901230910.BAA14995@bubba.whistle.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Mon, 25 Jan 1999 09:54:29 +0000
From: Brian Somers <brian@Awfulhak.org>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
[.....]
> So I'd like to make another attempt to get agreement on the next
> step here, so that *something* can happen. We need to get more
> people using DEVFS, so we can gain some experience & feedback.
> I don't think DEVFS has any issues that are not surmountable.
> However, at some point you must take the next step.
[.....]
> Comments?? The issue here is not whether this proposal is a sufficient
> *final* incarnation of DEVFS, but whether it's a sufficient next step..
How functional is DEVFS at the moment ? I was using it before the
SLICE stuff was torn out, and gave up at that point. Without SLICE,
does DEVFS create the devices with the same major/minor numbers as
normal ? Without SLICE, is it necessary to have a /dev to boot off ?
FWIW, I'm 100% behind DEVFS as none of the pitfalls affect me :-I
> -Archie
>
> ___________________________________________________________________________
> Archie Cobbs * Whistle Communications, Inc. * http://www.whistle.com
--
Brian <brian@Awfulhak.org> <brian@FreeBSD.org> <brian@OpenBSD.org>
<http://www.Awfulhak.org>
Don't _EVER_ lose your sense of humour !
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Mon Jan 25 05:33:59 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id FAA15314
for freebsd-current-outgoing; Mon, 25 Jan 1999 05:33:59 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from st-lcremean.tidalwave.net (st-lcremean.tidalwave.net [208.213.203.186])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA15309
for <current@freebsd.org>; Mon, 25 Jan 1999 05:33:55 -0800 (PST)
(envelope-from lee@st-lcremean.tidalwave.net)
Received: (from lee@localhost)
by st-lcremean.tidalwave.net (8.9.2/8.9.2) id IAA03560;
Mon, 25 Jan 1999 08:33:08 -0500 (EST)
(envelope-from lee)
Message-ID: <19990125083308.B3456@tidalwave.net>
Date: Mon, 25 Jan 1999 08:33:08 -0500
From: Lee Cremeans <lee@st-lcremean.tidalwave.net>
To: tarkhil@asteroid.svib.ru
Cc: current@FreeBSD.ORG
Subject: Re: IDE DMA works, I'll be a...
Reply-To: lcremean@tidalwave.net
References: <19990125080617.A3456@tidalwave.net> <199901251309.QAA08380@shuttle.svib.ru>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.93.2i
In-Reply-To: <199901251309.QAA08380@shuttle.svib.ru>; from Alex Povolotsky on Mon, Jan 25, 1999 at 04:09:27PM +0300
X-OS: FreeBSD 3.0-CURRENT
X-Evil: microsoft.com
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
On Mon, Jan 25, 1999 at 04:09:27PM +0300, Alex Povolotsky wrote:
> <19990125080617.A3456@tidalwave.net>Lee Cremeans writes:
> >> ide_pci0: <VIA 82C586x (Apollo) Bus-master IDE controller> rev 0x06 on pci0.
> >7.1
>
> Don't you know if I can upgrade only one file, ide_pci.c? STABLE seems to not
> much stable right now :-(
Just updating wd.c and ide_pci.c should work.
--
+--------------------------------------------------------------------+
| Lee Cremeans -- Manassas, VA, USA (WakkyMouse on DALnet and WTnet)|
| lcremean@tidalwave.net| http://st-lcremean.tidalwave.net/~lee |
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Mon Jan 25 05:40:18 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id FAA15802
for freebsd-current-outgoing; Mon, 25 Jan 1999 05:40:18 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from server.noc.demon.net (server.noc.demon.net [193.195.224.4])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA15794
for <freebsd-current@FreeBSD.ORG>; Mon, 25 Jan 1999 05:40:15 -0800 (PST)
(envelope-from geoffb@gti.noc.demon.net)
Received: by server.noc.demon.net; id NAA11652; Mon, 25 Jan 1999 13:40:14 GMT
Received: from gti.noc.demon.net(195.11.55.101) by inside.noc.demon.net via smap (3.2)
id xma011638; Mon, 25 Jan 99 13:40:04 GMT
Received: (from geoffb@localhost)
by gti.noc.demon.net (8.8.8/8.8.8) id NAA24077
for freebsd-current@FreeBSD.ORG; Mon, 25 Jan 1999 13:40:01 GMT
Message-ID: <19990125134001.E20146@gti.noc.demon.net>
Date: Mon, 25 Jan 1999 13:40:01 +0000
From: Geoff Buckingham <geoffb@demon.net>
To: freebsd-current@FreeBSD.ORG
Subject: Re: KVA/KVM shortages
Reply-To: Geoff Buckingham <geoffb@demon.net>
References: <19990121180941.G19395@gti.noc.demon.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.93.2i
In-Reply-To: <19990121180941.G19395@gti.noc.demon.net>; from Geoff Buckingham on Thu, Jan 21, 1999 at 06:09:41PM +0000
Organisation: Demon Internet Ltd
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
Previously on Thu, Jan 21, 1999 at 06:09:41PM +0000, Geoff Buckingham wrote:
: On tuesday I crashed a machine after it ran out of kvm. (dual PII 400 with
: 768MB RAM) poking about in the code adding:
:
: options "VM_KMEM_SIZE=(24*1024*1024)"
: options "VM_KMEM_SIZE_MAX=(128*1024*1024)"
:
: seems like a good way foward. Is it?
:
As no one seemed to comment directly on this I thouht I would relay our
experiances:
panic: pmap_new_proc: u_map allocation failed
Imediatly after the login promt appeared on the console:-(
This was running UNI-proccessor with softupdates and ccd the application
is disk and network heavy, circa 300 processes, however most memory is
used as cache.
This is 3.0-RELEASE with security fixes.
--
GeoffB
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Mon Jan 25 06:00:38 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id GAA17736
for freebsd-current-outgoing; Mon, 25 Jan 1999 06:00:38 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from caladan.tdx.co.uk (caladan.tdx.co.uk [195.188.177.4])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA17731
for <current@FreeBSD.ORG>; Mon, 25 Jan 1999 06:00:36 -0800 (PST)
(envelope-from kpielorz@tdx.co.uk)
Received: from tdx.co.uk (lorca-tx.tdx.co.uk [195.188.177.242])
by caladan.tdx.co.uk (8.9.2/8.9.2) with ESMTP id NAA00376;
Mon, 25 Jan 1999 13:58:58 GMT
Message-ID: <36AC78A2.AD5D42C6@tdx.co.uk>
Date: Mon, 25 Jan 1999 13:58:58 +0000
From: Karl Pielorz <kpielorz@tdx.co.uk>
Organization: TDX - The Digital eXchange
X-Mailer: Mozilla 4.5 [en] (WinNT; I)
X-Accept-Language: en
MIME-Version: 1.0
To: =?iso-8859-1?Q?S=F8ren?= Schmidt <sos@freebsd.dk>
CC: current@FreeBSD.ORG
Subject: Re: IDE DMA problems? (4.0-current as of 01/24/99 ~01:10)
References: <199901251140.MAA28486@freebsd.dk>
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
"Søren Schmidt" wrote:
> This is due to Julians commit in 1.183 (IIRC) of wd.c, its bogus :(
>
> The following patchh cures the mess, and fixes a couble of other
> nits as well:
> [snip]
Thanks, the patch fixed the problem...
-Kp
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Mon Jan 25 06:08:26 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id GAA19129
for freebsd-current-outgoing; Mon, 25 Jan 1999 06:08:26 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from axl.noc.iafrica.com (axl.noc.iafrica.com [196.31.1.175])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA18912
for <current@freebsd.org>; Mon, 25 Jan 1999 06:07:00 -0800 (PST)
(envelope-from sheldonh@axl.noc.iafrica.com)
Received: from sheldonh (helo=axl.noc.iafrica.com)
by axl.noc.iafrica.com with local-esmtp (Exim 2.10 #1)
id 104mf6-00006S-00
for current@freebsd.org; Mon, 25 Jan 1999 16:06:44 +0200
From: Sheldon Hearn <axl@iafrica.com>
To: current@FreeBSD.ORG
Subject: Stale files in /usr/lib
Date: Mon, 25 Jan 1999 16:06:44 +0200
Message-ID: <399.917273204@axl.noc.iafrica.com>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
Hi folks,
The following files are not being created by installworld:
/usr/lib/crt0.o
/usr/lib/c++rt0.o
/usr/lib/gcrt0.o
/usr/lib/scrt0.o
/usr/lib/sgcrt0.o
/usr/lib/kztail.o
/usr/lib/kzhead.o
Am I correct in assuming they're stale and can be removed?
Ciao,
Sheldon.
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Mon Jan 25 06:25:21 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id GAA21331
for freebsd-current-outgoing; Mon, 25 Jan 1999 06:25:21 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from mortar.carlson.com (mortar.carlson.com [208.240.12.98])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA21326;
Mon, 25 Jan 1999 06:25:17 -0800 (PST)
(envelope-from veldy@visi.com)
Received: from mortar.carlson.com (root@localhost)
by mortar.carlson.com with ESMTP id IAA00991;
Mon, 25 Jan 1999 08:24:47 -0600 (CST)
Received: from w142844 ([172.25.99.35])
by mortar.carlson.com with SMTP id IAA00987;
Mon, 25 Jan 1999 08:24:47 -0600 (CST)
Message-ID: <006201be486e$86a31630$236319ac@w142844.carlson.com>
From: "Thomas T. Veldhouse" <veldy@visi.com>
To: "FreeBSD-Current" <freebsd-current@FreeBSD.ORG>,
"FreeBSD-Stable" <freebsd-stable@FreeBSD.ORG>
X-Mailer: Microsoft Outlook Express 4.72.3110.5
X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3
Subject: Re: Failure to make buildworld on RELENG_3
Date: Mon, 25 Jan 1999 08:25:14 -0600
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
I completely re-cvsuped the sources and I still get errors in libpam.
Here is my make.conf:
# $Id: make.conf,v 1.70 1998/10/16 03:26:54 peter Exp $
#
# This file, if present, will be read by make (see /usr/share/mk/sys.mk).
# It allows you to override macro definitions to make without changing
# your source tree, or anything the source tree installs.
#
# This file must be in valid Makefile syntax.
#
# You have to find the things you can put here in the Makefiles and
# documentation of the source tree.
#
# One, and probably the most common, use could be:
#
CFLAGS= -O -pipe
#
# Another useful entry is
#
#NOPROFILE= true
# Avoid compiling profiled libraries
#
#INSTALL=install -C
# Compare before install
#
# To avoid building the default system perl
#NOPERL= true
# To avoid building the suid perl
#NOSUIDPERL= true
#
# To avoid building sendmail
#NO_SENDMAIL= true
#
# To have 'obj' symlinks created in your source directory
# (they aren't needed/necessary)
#OBJLINK= yes
#
# To compile just the kernel with special optimisations, you should use
# this instead of CFLAGS (which is not applicable to kernel builds anyway):
#
COPTFLAGS= -O -pipe
#
# To use an ELF kernel, you can set this flag. MAKE SURE that you have a
# working /boot/loader installed. /boot.config should specify
"/boot/loader"
# as the kernel. The bootblocks load the third stage loader, then it loads
# the kernel proper and any other modules you want. Its startup script
# file is /boot/loader.conf:
#
#KERNFORMAT= elf
#
# To compile and install the 4.4 lite libm instead of the default use:
#
#WANT_CSRG_LIBM= yes
#
# If you do not want unformatted manual pages to be compressed
# when they are installed:
#
#NOMANCOMPRESS= true
#
#
# If you want the "compat" shared libraries installed as part of your normal
# builds, uncomment these:
#
#COMPAT1X= yes
#COMPAT20= yes
#COMPAT21= yes
#
#
# If you do not want additional documentation (some of which are
# a few hundred KB's) for ports to be installed:
#
#NOPORTDOCS= true
#
#
# Default format for system documentation, depends on your printer.
# Set this to "ascii" for simple printers or screen
#
#PRINTERDEVICE= ps
#
#
# How long to wait for a console keypress before booting the default kernel.
# This value is approximately in milliseconds. Keypresses are accepted by
the
# BIOS before booting from disk, making it possible to give custom boot
# parameters even when this is set to 0.
#
#BOOTWAIT=0
#BOOTWAIT=30000
#
# By default, the system will always use the keyboard/video card as system
# console. However, the boot blocks may be dynamically configured to use a
# serial port in addition to or instead of the keyboard/video console.
#
# By default we use COM1 as our serial console port *if* we're going to use
# a serial port as our console at all. (0x3E8 = COM2)
#
#BOOT_COMCONSOLE_PORT= 0x3F8
#
# The default serial console speed is 9600. Set the speed to a larger value
# for better interactive response.
#
#BOOT_COMCONSOLE_SPEED= 115200
#
#
# By default, this points to /usr/X11R6 for XFree86 releases 3.0 or earlier.
# If you have a XFree86 from before 3.0 that has the X distribution in
# /usr/X386, you want to uncomment this.
#
#X11BASE= /usr/X386
#
#
# If you have Motif on your system, uncomment this.
#
#HAVE_MOTIF= yes
#MOTIF_STATIC= yes
#
# If the default location of the Motif library (specified below) is NOT
# appropriate for you, uncomment this and change it to the correct value.
# If your motif is in ${X11BASE}/lib, you don't need to touch this line.
#
#MOTIFLIB= -L${X11BASE}/lib -lXm
#
#
# If you are running behind a firewall, uncomment the following to leave a
# hint for various make-spawned utilities that they should use passive FTP.
#
#FTP_PASSIVE_MODE= YES
#
# If you're resident in the USA, this will help various ports to determine
# whether or not they should attempt to comply with the various U.S.
# export regulations on certain types of software which do not apply to
# anyone else in the world.
#
USA_RESIDENT= YES
#
# Next one will help ports developers to debug
#
#FORCE_PKG_REGISTER= YES
#
#
# Port master sites.
#
# If you want your port fetches to go somewhere else than the default
# (specified below) in case the distfile/patchfile was not found,
# uncomment this and change it to a location nearest you. (Don't
# remove the "/${DIST_SUBDIR}/" part.)
#
#MASTER_SITE_BACKUP?= \
# ftp://ftp.freebsd.org/pub/FreeBSD/distfiles/${DIST_SUBDIR}/
#
# If you want your port fetches to check the above site first (before
# the MASTER_SITES specified in the port Makefiles), uncomment the
# line below. You can also change the right side to point to wherever
# you want.
#
#MASTER_SITE_OVERRIDE?= ${MASTER_SITE_BACKUP}
#
# Some ports use a special variable to point to a collection of
# mirrors of well-known software archives. If you have a mirror close
# to you, uncomment any of the following lines and change it to that
# address. (Don't remove the "/%SUBDIR%/" part.)
#
# Note: the right hand sides of the following lines are only for your
# information. For a full list of default sites, take a look at
# bsd.port.mk.
#
#MASTER_SITE_XCONTRIB= ftp://ftp.x.org/contrib/%SUBDIR%/
#MASTER_SITE_GNU= ftp://prep.ai.mit.edu/pub/gnu/%SUBDIR%/
#MASTER_SITE_PERL_CPAN=
ftp://ftp.digital.com/pub/plan/perl/CPAN/modules/by-module/%SUBDIR%/
#MASTER_SITE_TEX_CTAN= ftp://ftp.tex.ac.uk/tex-archive/%SUBDIR%/
#MASTER_SITE_SUNSITE= ftp://sunsite.unc.edu/pub/Linux/%SUBDIR%/
#
#
# Kerberos IV
# If you want KerberosIV (KTH eBones), define this:
#
MAKE_KERBEROS4= yes
#
#
# Kerberos5
# If you want to install Kerberos5 somewhere other than /usr/local,
# define this:
#
#KRB5_HOME= /usr/local/krb5
#
#
# CVSup update flags. Edit SUPFILE settings to reflect whichever
distribution
# file(s) you use on your site (see /usr/share/examples/cvsup/README for
more
# information on CVSup and these files). To use, do "make update" in
/usr/src.
#
#SUP_UPDATE= yes
#
#SUP= /usr/local/bin/cvsup
#SUPFLAGS= -g -L 2 -z
#SUPFILE= /usr/share/examples/cvsup/standard-supfile
#SUPFILE1= /usr/share/examples/cvsup/secure-supfile
#SUPFILE2= /usr/share/examples/cvsup/ports-supfile
#
# top(1) uses a hash table for the user names. The size of this hash
# can be tuned to match the number of local users. The table size should
# be a prime number approximately twice as large as the number of lines in
# /etc/passwd. The default number is 20011.
#
#TOP_TABLE_SIZE= 101
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Mon Jan 25 06:50:06 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id GAA24531
for freebsd-current-outgoing; Mon, 25 Jan 1999 06:50:06 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from ipt2.iptelecom.net.ua (ipt2.iptelecom.net.ua [195.123.29.2])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA24454
for <current@FreeBSD.ORG>; Mon, 25 Jan 1999 06:49:56 -0800 (PST)
(envelope-from sobomax@altavista.net)
Received: from vega.pfts.com (async2-16.iptelecom.net.ua [195.123.29.81])
by ipt2.iptelecom.net.ua (8.8.8/8.8.8) with ESMTP id QAA01063;
Mon, 25 Jan 1999 16:49:21 +0200 (EET)
(envelope-from sobomax@altavista.net)
Received: from altavista.net (big_brother [192.168.1.1])
by vega.pfts.com (8.9.1/8.9.1) with ESMTP id QAA28336;
Mon, 25 Jan 1999 16:49:17 +0200 (EET)
(envelope-from sobomax@altavista.net)
Message-ID: <36AC8477.EDE68A@altavista.net>
Date: Mon, 25 Jan 1999 16:49:27 +0200
From: Maxim Sobolev <sobomax@altavista.net>
X-Mailer: Mozilla 4.5 [en] (WinNT; I)
X-Accept-Language: ru,en
MIME-Version: 1.0
To: Archie Cobbs <archie@whistle.com>
CC: current@FreeBSD.ORG
Subject: Re: DEVFS, the time has come...
References: <199901230910.BAA14995@bubba.whistle.com>
Content-Type: text/plain; charset=x-user-defined
Content-Transfer-Encoding: 8bit
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
Dear Archie,
Can you point all people (and me of course) who want to test DEVFS to some
common information about DEVFS (usage, possible advantages/disadvantages etc.)?
I think some FAQ or so will be nice. It's really will help us to go further
with this issue.
Sincerely,
Maxim
Archie Cobbs wrote:
> This email was a few weeks ago, and there was a lively debate, then
> Julian sent an email listing some issues/requirements, and then
> the thread kindof died and now we're back to where we were before,
> which is not any further on..
[Skipped]
> Comments?? The issue here is not whether this proposal is a sufficient
> *final* incarnation of DEVFS, but whether it's a sufficient next step..
>
> -Archie
>
> ___________________________________________________________________________
> Archie Cobbs * Whistle Communications, Inc. * http://www.whistle.com
>
> To Unsubscribe: send mail to majordomo@FreeBSD.org
> with "unsubscribe freebsd-current" in the body of the message
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Mon Jan 25 08:16:04 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id IAA03859
for freebsd-current-outgoing; Mon, 25 Jan 1999 08:16:04 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from khavrinen.lcs.mit.edu (khavrinen.lcs.mit.edu [18.24.4.193])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA03788
for <current@FreeBSD.ORG>; Mon, 25 Jan 1999 08:15:58 -0800 (PST)
(envelope-from wollman@khavrinen.lcs.mit.edu)
Received: (from wollman@localhost)
by khavrinen.lcs.mit.edu (8.9.1/8.9.1) id LAA19410;
Mon, 25 Jan 1999 11:15:36 -0500 (EST)
(envelope-from wollman)
Date: Mon, 25 Jan 1999 11:15:36 -0500 (EST)
From: Garrett Wollman <wollman@khavrinen.lcs.mit.edu>
Message-Id: <199901251615.LAA19410@khavrinen.lcs.mit.edu>
To: Matthew Dillon <dillon@apollo.backplane.com>
Cc: Mikhail Teterin <mi@kot.ne.mediaone.net>, current@FreeBSD.ORG
Subject: Re: sysctl oids (was: Re: kvm question)
In-Reply-To: <199901242355.PAA05605@apollo.backplane.com>
References: <199901242340.SAA04694@kot.ne.mediaone.net>
<199901242355.PAA05605@apollo.backplane.com>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
<<On Sun, 24 Jan 1999 15:55:50 -0800 (PST), Matthew Dillon <dillon@apollo.backplane.com> said:
> Strings are a whole lot more portable then integer assignments.
Nonsense. Strings are not portable at all -- they only exist in
FreeBSD. The reference implementation (4.4BSD) and its other
descendants use numbers.
-GAWollman
--
Garrett A. Wollman | O Siem / We are all family / O Siem / We're all the same
wollman@lcs.mit.edu | O Siem / The fires of freedom
Opinions not those of| Dance in the burning flame
MIT, LCS, CRS, or NSA| - Susan Aglukark and Chad Irschick
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Mon Jan 25 08:32:21 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id IAA06228
for freebsd-current-outgoing; Mon, 25 Jan 1999 08:32:21 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA06219
for <current@freebsd.org>; Mon, 25 Jan 1999 08:32:19 -0800 (PST)
(envelope-from jdp@polstra.com)
Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13])
by wall.polstra.com (8.9.1/8.9.1) with ESMTP id IAA14794;
Mon, 25 Jan 1999 08:32:18 -0800 (PST)
(envelope-from jdp@polstra.com)
From: John Polstra <jdp@polstra.com>
Received: (from jdp@localhost)
by vashon.polstra.com (8.9.1/8.9.1) id IAA19173;
Mon, 25 Jan 1999 08:32:17 -0800 (PST)
(envelope-from jdp@polstra.com)
Date: Mon, 25 Jan 1999 08:32:17 -0800 (PST)
Message-Id: <199901251632.IAA19173@vashon.polstra.com>
To: axl@iafrica.com
Subject: Re: Stale files in /usr/lib
Newsgroups: polstra.freebsd.current
In-Reply-To: <399.917273204@axl.noc.iafrica.com>
Organization: Polstra & Co., Seattle, WA
Cc: current@FreeBSD.ORG
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
In article <399.917273204@axl.noc.iafrica.com>,
Sheldon Hearn <axl@iafrica.com> wrote:
>
> The following files are not being created by installworld:
>
> /usr/lib/crt0.o
> /usr/lib/c++rt0.o
> /usr/lib/gcrt0.o
> /usr/lib/scrt0.o
> /usr/lib/sgcrt0.o
> /usr/lib/kztail.o
> /usr/lib/kzhead.o
>
> Am I correct in assuming they're stale and can be removed?
Yes, they all reside in /usr/lib/aout now.
John
--
John Polstra jdp@polstra.com
John D. Polstra & Co., Inc. Seattle, Washington USA
"Nobody ever went broke underestimating the taste of the American public."
-- H. L. Mencken
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Mon Jan 25 08:40:06 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id IAA07608
for freebsd-current-outgoing; Mon, 25 Jan 1999 08:40:06 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA07465
for <current@FreeBSD.ORG>; Mon, 25 Jan 1999 08:39:59 -0800 (PST)
(envelope-from phk@critter.freebsd.dk)
Received: from critter.freebsd.dk (localhost [127.0.0.1])
by critter.freebsd.dk (8.9.1/8.8.5) with ESMTP id RAA21829;
Mon, 25 Jan 1999 17:37:45 +0100 (CET)
To: Garrett Wollman <wollman@khavrinen.lcs.mit.edu>
cc: Matthew Dillon <dillon@apollo.backplane.com>,
Mikhail Teterin <mi@kot.ne.mediaone.net>, current@FreeBSD.ORG
Subject: Re: sysctl oids (was: Re: kvm question)
In-reply-to: Your message of "Mon, 25 Jan 1999 11:15:36 EST."
<199901251615.LAA19410@khavrinen.lcs.mit.edu>
Date: Mon, 25 Jan 1999 17:37:45 +0100
Message-ID: <21827.917282265@critter.freebsd.dk>
From: Poul-Henning Kamp <phk@critter.freebsd.dk>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
In message <199901251615.LAA19410@khavrinen.lcs.mit.edu>, Garrett Wollman write
s:
><<On Sun, 24 Jan 1999 15:55:50 -0800 (PST), Matthew Dillon <dillon@apollo.backplane.com> said:
>
>> Strings are a whole lot more portable then integer assignments.
>
>Nonsense. Strings are not portable at all -- they only exist in
>FreeBSD. The reference implementation (4.4BSD) and its other
>descendants use numbers.
Which is irrelevant, since they don't use sysctl for the same things
as us anyway (apart from a very small subset which is >ALREADY< special
cased in the kernel).
--
Poul-Henning Kamp FreeBSD coreteam member
phk@FreeBSD.ORG "Real hackers run -current on their laptop."
FreeBSD -- It will take a long time before progress goes too far!
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Mon Jan 25 08:57:08 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id IAA10390
for freebsd-current-outgoing; Mon, 25 Jan 1999 08:57:08 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA10382
for <current@freebsd.org>; Mon, 25 Jan 1999 08:57:06 -0800 (PST)
(envelope-from jdp@polstra.com)
Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13])
by wall.polstra.com (8.9.1/8.9.1) with ESMTP id IAA14903;
Mon, 25 Jan 1999 08:57:05 -0800 (PST)
(envelope-from jdp@polstra.com)
From: John Polstra <jdp@polstra.com>
Received: (from jdp@localhost)
by vashon.polstra.com (8.9.1/8.9.1) id IAA19232;
Mon, 25 Jan 1999 08:57:04 -0800 (PST)
(envelope-from jdp@polstra.com)
Date: Mon, 25 Jan 1999 08:57:04 -0800 (PST)
Message-Id: <199901251657.IAA19232@vashon.polstra.com>
To: wghicks@bellsouth.net
Subject: Re: Death to LKM screen savers? (was: Re: HEADS UP: i386 a.out L
Newsgroups: polstra.freebsd.current
In-Reply-To: <19990124225936P.wghicks@wghicks.bellsouth.net>
References: <Pine.BSF.4.05.9901242222270.55154-100000@bright.fx.genx.net>
Organization: Polstra & Co., Seattle, WA
Cc: current@FreeBSD.ORG
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
In article <19990124225936P.wghicks@wghicks.bellsouth.net>,
W Gerald Hicks <wghicks@bellsouth.net> wrote:
>
> And if you have cvsup-mirror loaded (running cvsupd), you can even use
> cvsup against your local repository.
>
> Seems a good bit faster than regular CVS for checkouts and updates.
It is _much_ faster. (I took some measurements a couple of years
ago.) But you do lose the ability to do handy things like "cvs diff",
"cvs log", and "cvs ann".
John
--
John Polstra jdp@polstra.com
John D. Polstra & Co., Inc. Seattle, Washington USA
"Nobody ever went broke underestimating the taste of the American public."
-- H. L. Mencken
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Mon Jan 25 09:05:40 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id JAA11362
for freebsd-current-outgoing; Mon, 25 Jan 1999 09:05:40 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from pegasus.freibergnet.de (pegasus.freibergnet.de [194.123.255.9])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA11355
for <freebsd-current@freebsd.org>; Mon, 25 Jan 1999 09:05:34 -0800 (PST)
(envelope-from holm@pegasus.freibergnet.de)
Received: (from holm@localhost)
by pegasus.freibergnet.de (8.9.2/8.9.1) id SAA00592
for freebsd-current@freebsd.org; Mon, 25 Jan 1999 18:05:30 +0100 (CET)
(envelope-from holm)
Date: Mon, 25 Jan 1999 18:05:30 +0100
From: Holm Tiffe <holm@freibergnet.de>
To: freebsd-current@FreeBSD.ORG
Subject: broken installworld when OBJLINK= yes
Message-ID: <19990125180530.A553@pegasus.freibergnet.de>
Reply-To: holm@freibergnet.de
Mime-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit
X-Mailer: Mutt 0.95i
Organization: FreibergNet Internet Services
X-Phone: +49-3731-781279
X-Fax: +49-3731-781377
X-PGP-fingerprint: 86 EC A5 63 B5 28 78 13 8B FC E9 09 04 6E 86 FC
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
Hi,
after several days fiddeling with the cvs and source trees
I've finnaly found out, that setting OBJLINK= yes in /etc/make.conf
breaks installworld's.
Buildworld is successfully building the entire tree, but after that
the obj link in the source-tree is pointing to an /usr/obj/aout/something
and the install is failing to find the librarys.
2nd:
Why is it neccessary to install shared libraries whit the schg flag set
in the obj tree ?
This successfully prevents from builds over nfs.
sorry for my broken english
Holm
--
FreibergNet Systemhaus GbR Holm Tiffe * Administration, Development
Systemhaus für Daten- und Netzwerktechnik phone +49 3731 781279
Unternehmensgruppe Liebscher & Partner fax +49 3731 781377
D-09599 Freiberg * Am St. Niclas Schacht 13 http://www.freibergnet.de/
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Mon Jan 25 09:13:47 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id JAA12207
for freebsd-current-outgoing; Mon, 25 Jan 1999 09:13:47 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from axl.noc.iafrica.com (axl.noc.iafrica.com [196.31.1.175])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA11824
for <current@freebsd.org>; Mon, 25 Jan 1999 09:10:46 -0800 (PST)
(envelope-from sheldonh@axl.noc.iafrica.com)
Received: from sheldonh (helo=axl.noc.iafrica.com)
by axl.noc.iafrica.com with local-esmtp (Exim 2.10 #1)
id 104pWm-000PBF-00; Mon, 25 Jan 1999 19:10:20 +0200
From: Sheldon Hearn <axl@iafrica.com>
To: John Polstra <jdp@polstra.com>
cc: current@FreeBSD.ORG
Subject: Re: Stale files in /usr/lib
In-reply-to: Your message of "Mon, 25 Jan 1999 08:32:17 PST."
<199901251632.IAA19173@vashon.polstra.com>
Date: Mon, 25 Jan 1999 19:10:20 +0200
Message-ID: <96796.917284220@axl.noc.iafrica.com>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
On Mon, 25 Jan 1999 08:32:17 PST, John Polstra wrote:
> Yes, they all reside in /usr/lib/aout now.
So then for a machine that makes world with -DNOAUT they don't exist,
assuming all ports have been rebuilt for an ELF world, yes?
Ciao,
Sheldon.
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Mon Jan 25 09:20:13 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id JAA12880
for freebsd-current-outgoing; Mon, 25 Jan 1999 09:20:13 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA12852
for <current@freebsd.org>; Mon, 25 Jan 1999 09:20:10 -0800 (PST)
(envelope-from jdp@polstra.com)
Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13])
by wall.polstra.com (8.9.1/8.9.1) with ESMTP id JAA15011;
Mon, 25 Jan 1999 09:20:08 -0800 (PST)
(envelope-from jdp@polstra.com)
Received: (from jdp@localhost)
by vashon.polstra.com (8.9.1/8.9.1) id JAA19273;
Mon, 25 Jan 1999 09:20:06 -0800 (PST)
(envelope-from jdp@polstra.com)
Message-ID: <XFMail.990125092006.jdp@polstra.com>
X-Mailer: XFMail 1.3 [p0] on FreeBSD
X-Priority: 3 (Normal)
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 8bit
MIME-Version: 1.0
In-Reply-To: <96796.917284220@axl.noc.iafrica.com>
Date: Mon, 25 Jan 1999 09:20:06 -0800 (PST)
Organization: Polstra & Co., Inc.
From: John Polstra <jdp@polstra.com>
To: Sheldon Hearn <axl@iafrica.com>
Subject: Re: Stale files in /usr/lib
Cc: current@FreeBSD.ORG
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
On 25-Jan-99 Sheldon Hearn wrote:
>
> On Mon, 25 Jan 1999 08:32:17 PST, John Polstra wrote:
>
>> Yes, they all reside in /usr/lib/aout now.
>
> So then for a machine that makes world with -DNOAUT they don't exist,
-DNOAOUT
> assuming all ports have been rebuilt for an ELF world, yes?
I don't know -- I've never used -DNOAOUT. :-) Somebody else will
have to answer that one.
Note, without those files you'll never again be able to link an a.out
program on the machine. Are you sure you really want that limitation?
John
---
John Polstra jdp@polstra.com
John D. Polstra & Co., Inc. Seattle, Washington USA
"Nobody ever went broke underestimating the taste of the American public."
-- H. L. Mencken
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Mon Jan 25 09:29:44 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id JAA13689
for freebsd-current-outgoing; Mon, 25 Jan 1999 09:29:44 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from arnold.neland.dk (mail.swimsuit.internet.dk [194.255.12.232])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA13684
for <freebsd-current@FreeBSD.ORG>; Mon, 25 Jan 1999 09:29:37 -0800 (PST)
(envelope-from leif@neland.dk)
Received: from localhost (leif@localhost)
by arnold.neland.dk (8.9.2/8.9.1) with ESMTP id SAA02920;
Mon, 25 Jan 1999 18:29:10 +0100 (CET)
(envelope-from leif@arnold.neland.dk)
Date: Mon, 25 Jan 1999 18:29:10 +0100 (CET)
From: Leif Neland <leif@neland.dk>
To: Chris Knight <fbsd-cur@ghostwheel.com>
cc: freebsd-current@FreeBSD.ORG
Subject: Re: Can't mount root. Really need help...
In-Reply-To: <4.1.19990124151511.009793a0@pop2.ghostwheel.com>
Message-ID: <Pine.BSF.4.05.9901251828410.2887-100000@arnold.neland.dk>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
On Sun, 24 Jan 1999, Chris Knight wrote:
> Greetings,
>
> I have learned a very valuable lesson. No matter how many time I have
> made world, I shouldn't do it while I'm tired. Last night I synced my tree
> and made world. I rebooted, and was going to remake my kernel after the
> boot. That became an impossibility.
>
Can't you boot kernel.old?
Leif
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Mon Jan 25 09:32:44 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id JAA14068
for freebsd-current-outgoing; Mon, 25 Jan 1999 09:32:44 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from axl.noc.iafrica.com (axl.noc.iafrica.com [196.31.1.175])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA14053
for <current@freebsd.org>; Mon, 25 Jan 1999 09:32:30 -0800 (PST)
(envelope-from sheldonh@axl.noc.iafrica.com)
Received: from sheldonh (helo=axl.noc.iafrica.com)
by axl.noc.iafrica.com with local-esmtp (Exim 2.10 #1)
id 104prh-0007ct-00; Mon, 25 Jan 1999 19:31:57 +0200
From: Sheldon Hearn <axl@iafrica.com>
To: John Polstra <jdp@polstra.com>
cc: current@FreeBSD.ORG
Subject: Re: Stale files in /usr/lib
In-reply-to: Your message of "Mon, 25 Jan 1999 09:20:06 PST."
<XFMail.990125092006.jdp@polstra.com>
Date: Mon, 25 Jan 1999 19:31:56 +0200
Message-ID: <29318.917285516@axl.noc.iafrica.com>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
On Mon, 25 Jan 1999 09:20:06 PST, John Polstra wrote:
> Note, without those files you'll never again be able to link an a.out
> program on the machine. Are you sure you really want that limitation?
As I understand it, the only times this hurts me are:
1) When I want to build binaries for another (a.out-only) box.
2) When I want to use dynamically-linked a.out binaries that were
compiled elsewhere on this box.
Unless I'm missing something, I'm happy with that. Thanks for the
feedback, I'll wait for someone else to answer on the other issue.
Ciao,
Sheldon.
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Mon Jan 25 09:34:08 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id JAA14193
for freebsd-current-outgoing; Mon, 25 Jan 1999 09:34:08 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from nlsystems.com (nlsys.demon.co.uk [158.152.125.33])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA14185
for <current@freebsd.org>; Mon, 25 Jan 1999 09:34:02 -0800 (PST)
(envelope-from dfr@nlsystems.com)
Received: from localhost (dfr@localhost)
by nlsystems.com (8.9.1/8.8.5) with SMTP id RAA87871
for <current@freebsd.org>; Mon, 25 Jan 1999 17:36:06 GMT
Date: Mon, 25 Jan 1999 17:36:00 +0000 (GMT)
From: Doug Rabson <dfr@nlsystems.com>
To: current@FreeBSD.ORG
Subject: Dynamic sysctl registration
Message-ID: <Pine.BSF.4.01.9901251726100.59627-100000@herring.nlsystems.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
I've made some changes to sysctl to allow nodes to be declared dynamically
either by loading kld modules which contain SYSCTL declarations or, in
theory, by generating oids from some other kernel data such as the device
tree.
To recap for those that are interested, the existing scheme uses linker
sets to represent interior nodes of the tree. Each child node has a
pointer in its parent's linker set (contained in the parent's oid_arg1
field). This is hard to make dynamic because linker sets can't easily be
extended without wastefully allocating and reallocating memory.
I have changed the code to use an SLIST to store the list of children for
an interior node. This has the advantage that nodes can be easily added
and removed. There is an associated cost (about 8 bytes per node on i386)
which I think is reasonable. All the oids in the kernel (or kld module)
are collected together in a single linker set from which the tree is
constructed by threading the oids onto their parent's list.
The kernel-user interface is completely unchanged.
If anyone is interested in seeing diffs (approx 23k), please contact me.
--
Doug Rabson Mail: dfr@nlsystems.com
Nonlinear Systems Ltd. Phone: +44 181 442 9037
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Mon Jan 25 09:56:22 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id JAA16532
for freebsd-current-outgoing; Mon, 25 Jan 1999 09:56:22 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA16522
for <current@FreeBSD.ORG>; Mon, 25 Jan 1999 09:56:18 -0800 (PST)
(envelope-from dillon@apollo.backplane.com)
Received: (from dillon@localhost)
by apollo.backplane.com (8.9.2/8.9.1) id JAA06826;
Mon, 25 Jan 1999 09:54:31 -0800 (PST)
(envelope-from dillon)
Date: Mon, 25 Jan 1999 09:54:31 -0800 (PST)
From: Matthew Dillon <dillon@apollo.backplane.com>
Message-Id: <199901251754.JAA06826@apollo.backplane.com>
To: Luigi Rizzo <luigi@labinfo.iet.unipi.it>
Cc: current@FreeBSD.ORG
Subject: Re: beginnings of a diskless boot sequence being committed
References: <199901250825.JAA26243@labinfo.iet.unipi.it>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
:> 'kern.conf_dir' which the kernel initially sets to nothing.
:
:ok, i can only suggest that if you replace the sysctl kern.conf_dir
:variable with a shell variable as i did, you can achieve a more
:portable result (this also in light of Jordan's idea of having a
:2.2S CD being made... putting patches for diskless into some
:'xperimnt' directory would be helpful). Other than that, i have no
:objections, and i am very glad you raised the issue since i am
:using diskless machines a lot!
That's what I had originally, but extracting the machine's IP
address is not trivial, and I didn't want to stick:
bootp_ifc=`route -n get default | fgrep interface | awk '{ print $2; }'`
bootp_ipa=`ifconfig $bootp_ifc | fgrep inet | head -1 | awk '{ print $2; }'`
In /etc/rc.conf in roder to synthesize the directory containing
rc.conf.local.
So I have rc.diskless figure it out and sto it in kern.conf_dir, and
rc.conf extracts it from that.
:I haven't seen how you suggest to build&populate the MFS filesystems --
:right now i use a rather crude method of putting all the stuff in a tgz
:archive on the server and expanding it at runtime on the client. I
:haven't solved the problem with passwords (i.e. i just copy the files
:from the server. -- this is clearly a security hole, perhaps YP-based
:solutions would be much better).
:
: cheers
: luigi
There isn't much to build. Most of the MFS filesystems start out
empty.
test2:/home/dillon> df
Filesystem 1K-blocks Used Avail Capacity Mounted on
209.157.86.2:/ 63503 46447 11976 80% /
209.157.86.2:/usr 508143 320642 146850 69% /usr
209.157.86.2:/var 63503 12333 46090 21% /var
mfs:42 959 70 813 8% /var/run
mfs:44 7903 596 6675 8% /var/db
mfs:46 31743 4 29200 0% /var/tmp
mfs:48 31743 8 29196 0% /var/spool
procfs 4 4 0 100% /proc
mfs:66 1511 58 1333 4% /dev
mfs:79 31743 1989 27215 7% /home
/var/run - starts out empty
/var/db - starts out empty
/var/tmp - starts out empty
/var/spool - simple skeleton directory structure
/dev - mount server:/ to a temporary place and use cpio to populate
/home - populate from template ( up to the user, I include a sample )
If I wanted to make a full system, I suppose I would make /var an MFS
filesystem too and use the system mtree to create it's directory structure.
But most diskless workstations do not need to run cron :-)
-Matt
Matthew Dillon
<dillon@backplane.com>
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Mon Jan 25 10:01:47 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id KAA17048
for freebsd-current-outgoing; Mon, 25 Jan 1999 10:01:47 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA17042
for <current@FreeBSD.ORG>; Mon, 25 Jan 1999 10:01:45 -0800 (PST)
(envelope-from dillon@apollo.backplane.com)
Received: (from dillon@localhost)
by apollo.backplane.com (8.9.2/8.9.1) id KAA06878;
Mon, 25 Jan 1999 10:01:20 -0800 (PST)
(envelope-from dillon)
Date: Mon, 25 Jan 1999 10:01:20 -0800 (PST)
From: Matthew Dillon <dillon@apollo.backplane.com>
Message-Id: <199901251801.KAA06878@apollo.backplane.com>
To: Peter Wemm <peter@netplex.com.au>
Cc: Luigi Rizzo <luigi@labinfo.iet.unipi.it>, current@FreeBSD.ORG
Subject: Re: beginnings of a diskless boot sequence being committed
References: <199901251124.TAA03489@spinner.netplex.com.au>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
I sure did, but I never committed them. I would have to redo them
at this point. The patch was to have MFS maintain a persistant file,
so you could fsck the file as if it were a disk and then the mfs mount it.
Security is an issue, but it depends on how your password file is setup.
You don't have to export the server's own root - the key thing is that
you want to export a shared root to all the workstations, so it would not
be too hard to implement kerberos as an authentication mechanism for the
workstations. At home, I just export my server's root. Point #2 is,
of course, that you export a read-only root.
-Matt
Matthew Dillon
<dillon@backplane.com>
:
:Luigi Rizzo wrote:
:[..]
:> I haven't seen how you suggest to build&populate the MFS filesystems --
:> right now i use a rather crude method of putting all the stuff in a tgz
:> archive on the server and expanding it at runtime on the client. I
:> haven't solved the problem with passwords (i.e. i just copy the files
:> from the server. -- this is clearly a security hole, perhaps YP-based
:> solutions would be much better).
:
:Didn't Matt have patches for initializing a MFS from a mmap'ed file rather
:than from swap at some point?
:
:Cheers,
:-Peter
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Mon Jan 25 10:03:19 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id KAA17168
for freebsd-current-outgoing; Mon, 25 Jan 1999 10:03:19 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA17162
for <freebsd-current@FreeBSD.ORG>; Mon, 25 Jan 1999 10:03:17 -0800 (PST)
(envelope-from dillon@apollo.backplane.com)
Received: (from dillon@localhost)
by apollo.backplane.com (8.9.2/8.9.1) id KAA06905;
Mon, 25 Jan 1999 10:03:12 -0800 (PST)
(envelope-from dillon)
Date: Mon, 25 Jan 1999 10:03:12 -0800 (PST)
From: Matthew Dillon <dillon@apollo.backplane.com>
Message-Id: <199901251803.KAA06905@apollo.backplane.com>
To: Geoff Buckingham <geoffb@demon.net>
Cc: freebsd-current@FreeBSD.ORG
Subject: Re: KVA/KVM shortages
References: <19990121180941.G19395@gti.noc.demon.net> <19990125134001.E20146@gti.noc.demon.net>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
If you can get a kernel core, run vmstat -m on it to see what the state
of the allocation hoppers was.
-Matt
Matthew Dillon
<dillon@backplane.com>
:As no one seemed to comment directly on this I thouht I would relay our
:experiances:
:
:panic: pmap_new_proc: u_map allocation failed
:
:Imediatly after the login promt appeared on the console:-(
:
:This was running UNI-proccessor with softupdates and ccd the application
:is disk and network heavy, circa 300 processes, however most memory is
:used as cache.
:
:This is 3.0-RELEASE with security fixes.
:
:--
:GeoffB
:
:To Unsubscribe: send mail to majordomo@FreeBSD.org
:with "unsubscribe freebsd-current" in the body of the message
:
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Mon Jan 25 10:06:55 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id KAA17584
for freebsd-current-outgoing; Mon, 25 Jan 1999 10:06:55 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from jason04.u.washington.edu (jason04.u.washington.edu [140.142.78.5])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA17579
for <current@FreeBSD.ORG>; Mon, 25 Jan 1999 10:06:54 -0800 (PST)
(envelope-from jcwells@u.washington.edu)
Received: from saul7.u.washington.edu (root@saul7.u.washington.edu [140.142.82.2])
by jason04.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id KAA43698;
Mon, 25 Jan 1999 10:06:53 -0800
Received: from S8-37-26.student.washington.edu (S8-37-26.student.washington.edu [128.208.37.26])
by saul7.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id KAA14358;
Mon, 25 Jan 1999 10:06:52 -0800 (PST)
Date: Mon, 25 Jan 1999 18:06:15 +0000 (GMT)
From: "Jason C. Wells" <jcwells@u.washington.edu>
X-Sender: jason@s8-37-26.student.washington.edu
Reply-To: "Jason C. Wells" <jcwells@u.washington.edu>
To: John Polstra <jdp@polstra.com>
cc: Sheldon Hearn <axl@iafrica.com>, current@FreeBSD.ORG
Subject: Re: Stale files in /usr/lib
In-Reply-To: <XFMail.990125092006.jdp@polstra.com>
Message-ID: <Pine.BSF.4.05.9901251802440.852-100000@s8-37-26.student.washington.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
On Mon, 25 Jan 1999, John Polstra wrote:
>On 25-Jan-99 Sheldon Hearn wrote:
>> On Mon, 25 Jan 1999 08:32:17 PST, John Polstra wrote:
>>> Yes, they all reside in /usr/lib/aout now.
>>
>> So then for a machine that makes world with -DNOAUT they don't exist,
> -DNOAOUT
>> assuming all ports have been rebuilt for an ELF world, yes?
>
>I don't know -- I've never used -DNOAOUT. :-) Somebody else will
>have to answer that one.
I did make buildworld with -DNOAOUT on -stable and it went fine. I did
make installworld and it croaked because it couldn't find the
afforementioned files.
Now I know what is up!
The answer to your question is: those files don't exist on a -DNOAOUT
build as evidence by the error message I recieved. :)
Catchya Later, | Give me UNIX or give me a typewriter.
Jason Wells | http://www.freebsd.org/
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Mon Jan 25 10:09:32 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id KAA17739
for freebsd-current-outgoing; Mon, 25 Jan 1999 10:09:32 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from asteroid.svib.ru (asteroid.svib.ru [195.151.166.145])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA17734
for <current@FreeBSD.ORG>; Mon, 25 Jan 1999 10:09:29 -0800 (PST)
(envelope-from tarkhil@asteroid.svib.ru)
Received: from shuttle.svib.ru (root@shuttle.svib.ru [195.151.166.144])
by asteroid.svib.ru (8.9.1a/8.9.1) with ESMTP id VAA20979;
Mon, 25 Jan 1999 21:09:24 +0300 (MSK)
Received: from shuttle.svib.ru (tarkhil@minas-tirith.pol.ru [127.0.0.1])
by shuttle.svib.ru (8.8.8/8.8.8) with ESMTP id VAA01072;
Mon, 25 Jan 1999 21:10:11 +0300 (MSK)
(envelope-from tarkhil@shuttle.svib.ru)
Message-Id: <199901251810.VAA01072@shuttle.svib.ru>
X-Mailer: exmh version 2.0.2 2/24/98
To: lcremean@tidalwave.net
cc: tarkhil@asteroid.svib.ru, current@FreeBSD.ORG
Subject: Re: IDE DMA works, I'll be a...
In-reply-to: Your message "Mon, 25 Jan 1999 08:33:08 EST."
<19990125083308.B3456@tidalwave.net>
Reply-To: tarkhil@asteroid.svib.ru
X-URL: http://freebsd.svib.ru
Mime-Version: 1.0
Content-Type: text/plain; charset=koi8-r
Content-Transfer-Encoding: 8bit
Date: Mon, 25 Jan 1999 21:10:10 +0300
From: Alex Povolotsky <tarkhil@asteroid.svib.ru>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
<19990125083308.B3456@tidalwave.net>Lee Cremeans writes:
>On Mon, Jan 25, 1999 at 04:09:27PM +0300, Alex Povolotsky wrote:
>> <19990125080617.A3456@tidalwave.net>Lee Cremeans writes:
>> >> ide_pci0: <VIA 82C586x (Apollo) Bus-master IDE controller> rev 0x06 on pc
>i0.
>> >7.1
>>
>> Don't you know if I can upgrade only one file, ide_pci.c? STABLE seems to no
>t
>> much stable right now :-(
>
>Just updating wd.c and ide_pci.c should work.
No. wd.c requires some more files. I'd better wait a bit, unless some kind sou
l will tell me what and how should I do.
opt_ide_delay.h is the missing one for wd.c, and just updating ide_pci.c
results in totally broken wd.
Alex.
--
Alexander B. Povolotsky [ICQ 18277558]
[2:5020/145] [http://freebsd.svib.ru] [tarkhil@asteroid.svib.ru]
[Urgent messages: 234-9696 ÁÂ.#35442 or tarkhil@pager.express.ru]
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Mon Jan 25 10:12:10 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id KAA18160
for freebsd-current-outgoing; Mon, 25 Jan 1999 10:12:10 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from axl.noc.iafrica.com (axl.noc.iafrica.com [196.31.1.175])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA18155
for <current@freebsd.org>; Mon, 25 Jan 1999 10:12:07 -0800 (PST)
(envelope-from sheldonh@axl.noc.iafrica.com)
Received: from sheldonh (helo=axl.noc.iafrica.com)
by axl.noc.iafrica.com with local-esmtp (Exim 2.10 #1)
id 104qTQ-000Lfy-00; Mon, 25 Jan 1999 20:10:56 +0200
From: Sheldon Hearn <axl@iafrica.com>
To: "Jason C. Wells" <jcwells@u.washington.edu>
cc: John Polstra <jdp@polstra.com>, current@FreeBSD.ORG
Subject: Re: Stale files in /usr/lib
In-reply-to: Your message of "Mon, 25 Jan 1999 18:06:15 GMT."
<Pine.BSF.4.05.9901251802440.852-100000@s8-37-26.student.washington.edu>
Date: Mon, 25 Jan 1999 20:10:56 +0200
Message-ID: <83325.917287856@axl.noc.iafrica.com>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
On Mon, 25 Jan 1999 18:06:15 GMT, "Jason C. Wells" wrote:
> I did make buildworld with -DNOAOUT on -stable and it went fine. I did
> make installworld and it croaked because it couldn't find the
> afforementioned files.
Well, their absence certainly doesn't blow up installworld on a -current
machine.
Ciao,
Sheldon.
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Mon Jan 25 10:16:02 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id KAA18510
for freebsd-current-outgoing; Mon, 25 Jan 1999 10:16:02 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from labinfo.iet.unipi.it (labinfo.iet.unipi.it [131.114.9.5])
by hub.freebsd.org (8.8.8/8.8.8) with SMTP id KAA18431
for <current@FreeBSD.ORG>; Mon, 25 Jan 1999 10:15:55 -0800 (PST)
(envelope-from luigi@labinfo.iet.unipi.it)
Received: from localhost (luigi@localhost) by labinfo.iet.unipi.it (8.6.5/8.6.5) id RAA27194; Mon, 25 Jan 1999 17:04:14 +0100
From: Luigi Rizzo <luigi@labinfo.iet.unipi.it>
Message-Id: <199901251604.RAA27194@labinfo.iet.unipi.it>
Subject: Re: beginnings of a diskless boot sequence being committed
To: dillon@apollo.backplane.com (Matthew Dillon)
Date: Mon, 25 Jan 1999 17:04:14 +0100 (MET)
Cc: current@FreeBSD.ORG
In-Reply-To: <199901251754.JAA06826@apollo.backplane.com> from "Matthew Dillon" at Jan 25, 99 09:54:12 am
X-Mailer: ELM [version 2.4 PL23]
Content-Type: text
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
> :> 'kern.conf_dir' which the kernel initially sets to nothing.
> :
> :ok, i can only suggest that if you replace the sysctl kern.conf_dir
> :variable with a shell variable as i did, you can achieve a more
...
> That's what I had originally, but extracting the machine's IP
> address is not trivial, and I didn't want to stick:
>
> bootp_ifc=`route -n get default | fgrep interface | awk '{ print $2; }'`
> bootp_ipa=`ifconfig $bootp_ifc | fgrep inet | head -1 | awk '{ print $2; }'`
I think it is much easier than that. The kernel BOOTP support sets
the machine's hostname, so you can do something like
if [ "`hostname`" = "" ]
then
# regular non-bootp sequence
mount -u -o rw /
...
mount -a -t nonfs
else
. /etc/rc.diskless
fi
if you want, save the `hostname` before executing rc.network to
remember if you started as diskless or not.
> :I haven't seen how you suggest to build&populate the MFS filesystems --
...
> There isn't much to build. Most of the MFS filesystems start out
> empty.
ok here we use a different approach. For simplicity I am using a
single MFS system with all the things you put in /var, and including
/var/dev and /var/etc (with /dev -> /var/dev and /etc -> /var/etc
on the diskless machine).
cheers
luigi
-----------------------------------+-------------------------------------
Luigi RIZZO .
EMAIL: luigi@iet.unipi.it . Dip. di Ing. dell'Informazione
HTTP://www.iet.unipi.it/~luigi/ . Universita` di Pisa
TEL/FAX: +39-050-568.533/522 . via Diotisalvi 2, 56126 PISA (Italy)
-----------------------------------+-------------------------------------
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Mon Jan 25 10:21:32 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id KAA19276
for freebsd-current-outgoing; Mon, 25 Jan 1999 10:21:32 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from po8.andrew.cmu.edu (PO8.ANDREW.CMU.EDU [128.2.10.108])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA19265
for <current@FreeBSD.ORG>; Mon, 25 Jan 1999 10:21:26 -0800 (PST)
(envelope-from tcrimi+@andrew.cmu.edu)
Received: (from postman@localhost) by po8.andrew.cmu.edu (8.8.5/8.8.2) id NAA06170; Mon, 25 Jan 1999 13:21:17 -0500 (EST)
Received: via switchmail; Mon, 25 Jan 1999 13:21:16 -0500 (EST)
Received: from po6.andrew.cmu.edu via qmail
ID </afs/andrew.cmu.edu/service/mailqs/q007/QF.kqf=Lr:00Ude01I=00>;
Mon, 25 Jan 1999 13:20:39 -0500 (EST)
Received: from unix15.andrew.cmu.edu via qmail
ID </afs/andrew.cmu.edu/usr18/tcrimi/.Outgoing/QF.sqetTuS00UwH0PBLQ0>;
Sun, 24 Jan 1999 17:00:26 -0500 (EST)
Received: from mms.4.60.Jun.27.1996.03.02.53.sun4.51.EzMail.2.0.CUILIB.3.45.SNAP.NOT.LINKED.unix15.andrew.cmu.edu.sun4m.54
via MS.5.6.unix15.andrew.cmu.edu.sun4_51;
Sun, 24 Jan 1999 17:00:26 -0500 (EST)
Message-ID: <MqetTuS00UwH0PBLI0@andrew.cmu.edu>
Date: Sun, 24 Jan 1999 17:00:26 -0500 (EST)
From: Thomas Valentino Crimi <tcrimi+@andrew.cmu.edu>
To: julian@whistle.com (Julian Elischer), Archie Cobbs <archie@whistle.com>
Subject: Re: kvm question
Cc: wollman@khavrinen.lcs.mit.edu, current@FreeBSD.ORG
In-Reply-To: <199901242130.NAA21377@bubba.whistle.com>
References: <199901242130.NAA21377@bubba.whistle.com>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
Excerpts from FreeBSD-Current: 24-Jan-99 Re: kvm question by Archie
Cobbs@whistle.com
> Whether libkvm should even exist in a perfect world (it shouldn't)
> is an entirely different question. For now, we're stuck with it
> until somebody changes *everything* to use sysctl instead.
Just as a question, how much of a performance difference is there
between using libkvm and sysctl? If I were looking for a way to keep
constant tabs on system performance with the minimal impact (think top,
xsysinfo, sysstat, etc), which would I want to use if any difference
exists at all?
My suspicion would be that sysctl might actually be faster unless
libkvm mmap's /dev/kmem so then that would elimiate the need for
syscalls.
libkvm may never fully die to support 3rd party software, but that is
no reason to not upgrade the userland we do have control over so that ps
and top will work under any kernel upgrade.
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Mon Jan 25 10:40:30 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id KAA21583
for freebsd-current-outgoing; Mon, 25 Jan 1999 10:40:30 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA21567;
Mon, 25 Jan 1999 10:40:25 -0800 (PST)
(envelope-from julian@whistle.com)
Received: (from daemon@localhost)
by alpo.whistle.com (8.8.5/8.8.5) id KAA13238;
Mon, 25 Jan 1999 10:37:57 -0800 (PST)
Received: from s204m82.isp.whistle.com(207.76.204.82)
via SMTP by alpo.whistle.com, id smtpdF13231; Mon Jan 25 18:37:45 1999
Date: Mon, 25 Jan 1999 10:37:42 -0800 (PST)
From: Julian Elischer <julian@whistle.com>
X-Sender: julian@s204m82.isp.whistle.com
To: Brian Somers <brian@Awfulhak.org>
cc: Archie Cobbs <archie@whistle.com>, arch@FreeBSD.ORG, current@FreeBSD.ORG
Subject: Re: DEVFS, the time has come...
In-Reply-To: <199901250954.JAA09098@keep.lan.Awfulhak.org>
Message-ID: <Pine.BSF.4.05.9901251035500.569-100000@s204m82.isp.whistle.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
yo, brian,
are you on 'net'?
have you had a look at the netgraph stuff?
particularly the kernel nodes that we use in conjuntion with mpd, and the
usserland modules of mpd that we use with it?
On Mon, 25 Jan 1999, Brian Somers wrote:
> [.....]
> > So I'd like to make another attempt to get agreement on the next
> > step here, so that *something* can happen. We need to get more
> > people using DEVFS, so we can gain some experience & feedback.
> > I don't think DEVFS has any issues that are not surmountable.
> > However, at some point you must take the next step.
> [.....]
> > Comments?? The issue here is not whether this proposal is a sufficient
> > *final* incarnation of DEVFS, but whether it's a sufficient next step..
>
> How functional is DEVFS at the moment ? I was using it before the
> SLICE stuff was torn out, and gave up at that point. Without SLICE,
> does DEVFS create the devices with the same major/minor numbers as
> normal ? Without SLICE, is it necessary to have a /dev to boot off ?
>
> FWIW, I'm 100% behind DEVFS as none of the pitfalls affect me :-I
>
> > -Archie
> >
> > ___________________________________________________________________________
> > Archie Cobbs * Whistle Communications, Inc. * http://www.whistle.com
>
> --
> Brian <brian@Awfulhak.org> <brian@FreeBSD.org> <brian@OpenBSD.org>
> <http://www.Awfulhak.org>
> Don't _EVER_ lose your sense of humour !
>
>
>
> To Unsubscribe: send mail to majordomo@FreeBSD.org
> with "unsubscribe freebsd-current" in the body of the message
>
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Mon Jan 25 10:44:32 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id KAA22090
for freebsd-current-outgoing; Mon, 25 Jan 1999 10:44:32 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from whistle.com (s205m131.whistle.com [207.76.205.131])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA22083;
Mon, 25 Jan 1999 10:44:29 -0800 (PST)
(envelope-from archie@whistle.com)
Received: (from smap@localhost) by whistle.com (8.7.5/8.6.12) id KAA11475; Mon, 25 Jan 1999 10:44:13 -0800 (PST)
Received: from bubba.whistle.com( 207.76.205.7) by whistle.com via smap (V2.0)
id xma011473; Mon, 25 Jan 99 10:43:47 -0800
Received: (from archie@localhost) by bubba.whistle.com (8.8.7/8.6.12) id KAA01627; Mon, 25 Jan 1999 10:43:47 -0800 (PST)
From: Archie Cobbs <archie@whistle.com>
Message-Id: <199901251843.KAA01627@bubba.whistle.com>
Subject: Re: DEVFS, the time has come...
In-Reply-To: <199901250954.JAA09098@keep.lan.Awfulhak.org> from Brian Somers at "Jan 25, 99 09:54:29 am"
To: brian@Awfulhak.org (Brian Somers)
Date: Mon, 25 Jan 1999 10:43:46 -0800 (PST)
Cc: arch@FreeBSD.ORG, current@FreeBSD.ORG,
julian@whistle.com (Julian Elischer)
X-Mailer: ELM [version 2.4ME+ PL38 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
Brian Somers writes:
> > So I'd like to make another attempt to get agreement on the next
> > step here, so that *something* can happen. We need to get more
> > people using DEVFS, so we can gain some experience & feedback.
> > I don't think DEVFS has any issues that are not surmountable.
> > However, at some point you must take the next step.
> [.....]
> > Comments?? The issue here is not whether this proposal is a sufficient
> > *final* incarnation of DEVFS, but whether it's a sufficient next step..
>
> How functional is DEVFS at the moment ? I was using it before the
> SLICE stuff was torn out, and gave up at that point. Without SLICE,
> does DEVFS create the devices with the same major/minor numbers as
> normal ? Without SLICE, is it necessary to have a /dev to boot off ?
You would have to ask Julian this question. However, my impression
is that there are a couple of things that are broken, but nothing
too serious that it can't be fixed/updated relatively quickly.
Julian, is that accurrate? What about the MFS problem -- how hard
is that to fix? I.E. What's required to get DEVFS to the point
where 'the masses' (including me :-) can use it with minimal
pain/disruption?
-Archie
___________________________________________________________________________
Archie Cobbs * Whistle Communications, Inc. * http://www.whistle.com
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Mon Jan 25 11:16:52 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id LAA25782
for freebsd-current-outgoing; Mon, 25 Jan 1999 11:16:52 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from arg1.demon.co.uk (arg1.demon.co.uk [194.222.34.166])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA25776
for <current@freebsd.org>; Mon, 25 Jan 1999 11:16:48 -0800 (PST)
(envelope-from arg@arg1.demon.co.uk)
Received: from localhost (arg@localhost)
by arg1.demon.co.uk (8.8.8/8.8.8) with SMTP id SAA22387;
Mon, 25 Jan 1999 18:28:11 GMT
(envelope-from arg@arg1.demon.co.uk)
Date: Mon, 25 Jan 1999 18:28:10 +0000 (GMT)
From: Andrew Gordon <arg@arg1.demon.co.uk>
X-Sender: arg@server.arg.sj.co.uk
To: "Jordan K. Hubbard" <jkh@zippy.cdrom.com>
cc: current@FreeBSD.ORG
Subject: Re: 4.0-Current, netscape halts system
In-Reply-To: <1476.917220230@zippy.cdrom.com>
Message-ID: <Pine.BSF.3.96.990125182019.22310B-100000@server.arg.sj.co.uk>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
On Sun, 24 Jan 1999, Jordan K. Hubbard wrote:
> I really don't understand the problems that everyone is having,
> myself. I've been running netscape (communicator 4.5) in -current for
> ages now and just switched to 4.0 without any problems. My netscape
> still continues to function just fine and has never crashed any of
> my system so much as once.
>
> Why the wide disparity in experience, I wonder?
One variable may be available memory. On my system, with default datasize
limit of 16M from login.conf, Netscape coredumps very frequently. With
datasize unlimited, Netscape eats all the available swap (this system is
64M real 128M swap) and kills the system that way. I currently run
Netscape with datasize set to 64M, pending a new disc for more swap! In
this configuration, Netscape either coredumps or starts behavhing oddly
about once every 3 days, but at least I can just restart it rather than
needing to reboot after a swap outage.
Colour depth also has an effect - changing from 8-bit to 32-bit on the X
server seems to have made this worse (as you might expect).
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Mon Jan 25 11:24:18 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id LAA26954
for freebsd-current-outgoing; Mon, 25 Jan 1999 11:24:18 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from whistle.com (s205m131.whistle.com [207.76.205.131])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA26949
for <current@freebsd.org>; Mon, 25 Jan 1999 11:24:16 -0800 (PST)
(envelope-from archie@whistle.com)
Received: (from smap@localhost) by whistle.com (8.7.5/8.6.12) id LAA12034; Mon, 25 Jan 1999 11:23:44 -0800 (PST)
Received: from bubba.whistle.com( 207.76.205.7) by whistle.com via smap (V2.0)
id xma012032; Mon, 25 Jan 99 11:23:26 -0800
Received: (from archie@localhost) by bubba.whistle.com (8.8.7/8.6.12) id LAA01882; Mon, 25 Jan 1999 11:23:26 -0800 (PST)
From: Archie Cobbs <archie@whistle.com>
Message-Id: <199901251923.LAA01882@bubba.whistle.com>
Subject: Re: 4.0-Current, netscape halts system
In-Reply-To: <199901250644.XAA04563@mt.sri.com> from Nate Williams at "Jan 24, 99 11:44:42 pm"
To: nate@mt.sri.com (Nate Williams)
Date: Mon, 25 Jan 1999 11:23:26 -0800 (PST)
Cc: current@FreeBSD.ORG
X-Mailer: ELM [version 2.4ME+ PL38 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
Nate Williams writes:
> > I am current as of today 4.0, I have communicator 4.5 downloaded some time
> > ago (November more or less) directly from netscape and installed in
> > /usr/local/netscape with a link to /usr/local/bin/netscape and I have been
> > using it all day with no problems. My intranet if full of java and haven't
> > had a problem, knock on wood:-) I just downloaded a 9M file after reading
> > your mail to see if that would cause a problem and it didn't. Netscape is
> > "as stable as ever" on FreeBSD Current 4.0 for me. That bothers me:-) I
> > wonder why?
>
> I'm running 2.2-stable, so maybe that's a difference.
Me too... (I get crashes running Java)
-Archie
___________________________________________________________________________
Archie Cobbs * Whistle Communications, Inc. * http://www.whistle.com
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Mon Jan 25 11:41:33 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id LAA29395
for freebsd-current-outgoing; Mon, 25 Jan 1999 11:41:33 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from mail9.svr.pol.co.uk (mail9.svr.pol.co.uk [195.92.193.22])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA29388
for <current@freebsd.org>; Mon, 25 Jan 1999 11:41:29 -0800 (PST)
(envelope-from A.M.Zanker@open.ac.uk)
Received: from modem-123.zidovudine.dialup.pol.co.uk ([62.136.94.251] helo=jemima)
by mail9.svr.pol.co.uk with smtp (Exim 2.10 #1)
id 104rt1-0005n6-00
for current@freebsd.org; Mon, 25 Jan 1999 19:41:27 +0000
Message-Id: <4.1.19990125192623.009dcea0@swale.open.ac.uk>
X-Sender: mikez@swale.open.ac.uk
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.1
Date: Mon, 25 Jan 1999 19:40:25 +0000
To: current@FreeBSD.ORG
From: Mike Zanker <A.M.Zanker@open.ac.uk>
Subject: Reboot after intense disk activity
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
I've been having a problem ever since I moved from 2.2.8-STABLE to
3.0-CURRENT (all elf). After long periods of intense disk activity (e.g. rm
-rf * in /usr/obj or a make world) my keyboard seems to become less
responsive and I can hear a quick burst of disk activity with each key
press. On a couple of occasions the machine has then frozen for a few
seconds (with the disk LED lit) and then rebooted. This happened last night
following a cvsup of RELENG_3, removal of /usr/obj then a make buildworld.
My system is current as of 16/1/99. When the machine reboots there are no
core files, nothing unexpected in /var/log/messages and only around 128K of
swap used (out of 160MB).
Machine spec:
P133, Intel 82371FB IDE controller, 2GB Seagate IDE disk, 3.2GB Quantum
hard disk, 80MB RAM, 4MB Matrox Mystique 220 graphics card.
Please let me know if further information is needed.
Thanks,
Mike
--
Mike Zanker, Academic Computing Service, The Open University, UK
Tel: +44 1908 652726, Fax: +44 1908 652193
Views expressed are personal and do not necessarily reflect University opinion.
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Mon Jan 25 12:01:11 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id MAA02588
for freebsd-current-outgoing; Mon, 25 Jan 1999 12:01:11 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from axl.noc.iafrica.com (axl.noc.iafrica.com [196.31.1.175])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA02551
for <current@freebsd.org>; Mon, 25 Jan 1999 12:01:00 -0800 (PST)
(envelope-from sheldonh@axl.noc.iafrica.com)
Received: from sheldonh (helo=axl.noc.iafrica.com)
by axl.noc.iafrica.com with local-esmtp (Exim 2.10 #1)
id 104sB7-000HI5-00; Mon, 25 Jan 1999 22:00:09 +0200
From: Sheldon Hearn <axl@iafrica.com>
To: Andrew Gordon <arg@arg1.demon.co.uk>
cc: "Jordan K. Hubbard" <jkh@zippy.cdrom.com>, current@FreeBSD.ORG
Subject: Re: 4.0-Current, netscape halts system
In-reply-to: Your message of "Mon, 25 Jan 1999 18:28:10 GMT."
<Pine.BSF.3.96.990125182019.22310B-100000@server.arg.sj.co.uk>
Date: Mon, 25 Jan 1999 22:00:09 +0200
Message-ID: <66468.917294409@axl.noc.iafrica.com>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
On Mon, 25 Jan 1999 18:28:10 GMT, Andrew Gordon wrote:
> One variable may be available memory. On my system, with default
> datasize limit of 16M from login.conf, Netscape coredumps very
> frequently.
Aha! That figures.
Since I upgraded to CURRENT, with its login.conf which defaults to
unlimited resources, my frequent netscape core dumps have gone away.
I hadn't realized why until now.
Suggestion: wwhen people complain about Netscape, ask them to mail us
back the output of ``ulimit -a''.
Thanks,
Sheldon.
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Mon Jan 25 13:10:26 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id NAA11221
for freebsd-current-outgoing; Mon, 25 Jan 1999 13:10:26 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from zippy.dyn.ml.org (spain-13.ppp.hooked.net [206.169.228.13])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA11215
for <current@FreeBSD.ORG>; Mon, 25 Jan 1999 13:10:24 -0800 (PST)
(envelope-from garbanzo@hooked.net)
Received: from localhost (garbanzo@zippy.dyn.ml.org [127.0.0.1])
by zippy.dyn.ml.org (8.9.1/8.8.8) with ESMTP id NAA07653;
Mon, 25 Jan 1999 13:12:59 -0800 (PST)
(envelope-from garbanzo@hooked.net)
Date: Mon, 25 Jan 1999 13:12:59 -0800 (PST)
From: Alex Zepeda <garbanzo@hooked.net>
X-Sender: garbanzo@zippy.dyn.ml.org
To: "Jason C. Wells" <jcwells@u.washington.edu>
cc: John Polstra <jdp@polstra.com>, Sheldon Hearn <axl@iafrica.com>,
current@FreeBSD.ORG
Subject: Re: Stale files in /usr/lib
In-Reply-To: <Pine.BSF.4.05.9901251802440.852-100000@s8-37-26.student.washington.edu>
Message-ID: <Pine.BSF.4.05.9901251312290.890-100000@zippy.dyn.ml.org>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
On Mon, 25 Jan 1999, Jason C. Wells wrote:
[..\
> I did make buildworld with -DNOAOUT on -stable and it went fine. I did
> make installworld and it croaked because it couldn't find the
> afforementioned files.
You need to make installworld with -DNOAOUT too. Otherwise it _will_ look
for a.out stuff to install.
> Now I know what is up!
- alex
| "Contrary to popular belief, penguins are not the salvation of modern |
| technology. Neither do they throw parties for the urban proletariat." |
| Powered by FreeBSD http://www.freebsd.org/ |
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Mon Jan 25 13:30:31 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id NAA13927
for freebsd-current-outgoing; Mon, 25 Jan 1999 13:30:31 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA13916
for <current@FreeBSD.ORG>; Mon, 25 Jan 1999 13:30:24 -0800 (PST)
(envelope-from dillon@apollo.backplane.com)
Received: (from dillon@localhost)
by apollo.backplane.com (8.9.2/8.9.1) id NAA07766;
Mon, 25 Jan 1999 13:30:17 -0800 (PST)
(envelope-from dillon)
Date: Mon, 25 Jan 1999 13:30:17 -0800 (PST)
From: Matthew Dillon <dillon@apollo.backplane.com>
Message-Id: <199901252130.NAA07766@apollo.backplane.com>
To: Andrew Gordon <arg@arg1.demon.co.uk>
Cc: "Jordan K. Hubbard" <jkh@zippy.cdrom.com>, current@FreeBSD.ORG
Subject: Re: 4.0-Current, netscape halts system
References: <Pine.BSF.3.96.990125182019.22310B-100000@server.arg.sj.co.uk>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
:One variable may be available memory. On my system, with default datasize
:limit of 16M from login.conf, Netscape coredumps very frequently. With
:datasize unlimited, Netscape eats all the available swap (this system is
:64M real 128M swap) and kills the system that way. I currently run
:Netscape with datasize set to 64M, pending a new disc for more swap! In
:this configuration, Netscape either coredumps or starts behavhing oddly
:about once every 3 days, but at least I can just restart it rather than
:needing to reboot after a swap outage.
:
:Colour depth also has an effect - changing from 8-bit to 32-bit on the X
:server seems to have made this worse (as you might expect).
I've been using netscape on a 24bit color system for well over a year
and have never had a serious memory leak problem or X session ( or
machine ) crashing due to it. I don't leave the netscape window open
all the time, though... I tend to exit out of it when I'm not using it.
-Matt
Matthew Dillon
<dillon@backplane.com>
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Mon Jan 25 14:12:34 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id OAA20565
for freebsd-current-outgoing; Mon, 25 Jan 1999 14:12:34 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from whistle.com (s205m131.whistle.com [207.76.205.131])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA20556
for <current@FreeBSD.ORG>; Mon, 25 Jan 1999 14:12:33 -0800 (PST)
(envelope-from archie@whistle.com)
Received: (from smap@localhost) by whistle.com (8.7.5/8.6.12) id OAA14766; Mon, 25 Jan 1999 14:12:30 -0800 (PST)
Received: from bubba.whistle.com( 207.76.205.7) by whistle.com via smap (V2.0)
id xma014764; Mon, 25 Jan 99 14:12:02 -0800
Received: (from archie@localhost) by bubba.whistle.com (8.8.7/8.6.12) id OAA18030; Mon, 25 Jan 1999 14:12:02 -0800 (PST)
From: Archie Cobbs <archie@whistle.com>
Message-Id: <199901252212.OAA18030@bubba.whistle.com>
Subject: Re: Dynamic sysctl registration
In-Reply-To: <Pine.BSF.4.01.9901251726100.59627-100000@herring.nlsystems.com> from Doug Rabson at "Jan 25, 99 05:36:00 pm"
To: dfr@nlsystems.com (Doug Rabson)
Date: Mon, 25 Jan 1999 14:12:02 -0800 (PST)
Cc: current@FreeBSD.ORG
X-Mailer: ELM [version 2.4ME+ PL38 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
Doug Rabson writes:
> I've made some changes to sysctl to allow nodes to be declared dynamically
> either by loading kld modules which contain SYSCTL declarations or, in
> theory, by generating oids from some other kernel data such as the device
> tree.
>
> To recap for those that are interested, the existing scheme uses linker
> sets to represent interior nodes of the tree. Each child node has a
> pointer in its parent's linker set (contained in the parent's oid_arg1
> field). This is hard to make dynamic because linker sets can't easily be
> extended without wastefully allocating and reallocating memory.
>
> I have changed the code to use an SLIST to store the list of children for
> an interior node. This has the advantage that nodes can be easily added
> and removed. There is an associated cost (about 8 bytes per node on i386)
> which I think is reasonable. All the oids in the kernel (or kld module)
> are collected together in a single linker set from which the tree is
> constructed by threading the oids onto their parent's list.
>
> The kernel-user interface is completely unchanged.
>
> If anyone is interested in seeing diffs (approx 23k), please contact me.
I'm interested.. could you email me the diffs?
I'm more interested in whether these patches can be committed... ?
Have Poul, DG, et. al. seen them?
-Archie
___________________________________________________________________________
Archie Cobbs * Whistle Communications, Inc. * http://www.whistle.com
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Mon Jan 25 14:13:40 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id OAA20675
for freebsd-current-outgoing; Mon, 25 Jan 1999 14:13:40 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from whistle.com (s205m131.whistle.com [207.76.205.131])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA20670
for <current@freebsd.org>; Mon, 25 Jan 1999 14:13:39 -0800 (PST)
(envelope-from archie@whistle.com)
Received: (from smap@localhost) by whistle.com (8.7.5/8.6.12) id OAA14785; Mon, 25 Jan 1999 14:13:30 -0800 (PST)
Received: from bubba.whistle.com( 207.76.205.7) by whistle.com via smap (V2.0)
id xma014781; Mon, 25 Jan 99 14:13:27 -0800
Received: (from archie@localhost) by bubba.whistle.com (8.8.7/8.6.12) id OAA18042; Mon, 25 Jan 1999 14:13:27 -0800 (PST)
From: Archie Cobbs <archie@whistle.com>
Message-Id: <199901252213.OAA18042@bubba.whistle.com>
Subject: Re: kvm question
In-Reply-To: <MqetTuS00UwH0PBLI0@andrew.cmu.edu> from Thomas Valentino Crimi at "Jan 24, 99 05:00:26 pm"
To: tcrimi+@andrew.cmu.edu (Thomas Valentino Crimi)
Date: Mon, 25 Jan 1999 14:13:27 -0800 (PST)
Cc: current@FreeBSD.ORG
X-Mailer: ELM [version 2.4ME+ PL38 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
Thomas Valentino Crimi writes:
> > Whether libkvm should even exist in a perfect world (it shouldn't)
> > is an entirely different question. For now, we're stuck with it
> > until somebody changes *everything* to use sysctl instead.
>
> Just as a question, how much of a performance difference is there
> between using libkvm and sysctl? If I were looking for a way to keep
> constant tabs on system performance with the minimal impact (think top,
> xsysinfo, sysstat, etc), which would I want to use if any difference
> exists at all?
>
> My suspicion would be that sysctl might actually be faster unless
> libkvm mmap's /dev/kmem so then that would elimiate the need for
> syscalls.
libkvm is probably faster, but it really doesn't matter because
they're both probably about the same and the application for this
stuff is not performance critical.
-Archie
___________________________________________________________________________
Archie Cobbs * Whistle Communications, Inc. * http://www.whistle.com
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Mon Jan 25 14:32:52 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id OAA23384
for freebsd-current-outgoing; Mon, 25 Jan 1999 14:32:52 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA23361
for <current@FreeBSD.ORG>; Mon, 25 Jan 1999 14:32:44 -0800 (PST)
(envelope-from phk@critter.freebsd.dk)
Received: from critter.freebsd.dk (localhost [127.0.0.1])
by critter.freebsd.dk (8.9.1/8.8.5) with ESMTP id XAA22794;
Mon, 25 Jan 1999 23:31:37 +0100 (CET)
To: Archie Cobbs <archie@whistle.com>
cc: dfr@nlsystems.com (Doug Rabson), current@FreeBSD.ORG
Subject: Re: Dynamic sysctl registration
In-reply-to: Your message of "Mon, 25 Jan 1999 14:12:02 PST."
<199901252212.OAA18030@bubba.whistle.com>
Date: Mon, 25 Jan 1999 23:31:36 +0100
Message-ID: <22792.917303496@critter.freebsd.dk>
From: Poul-Henning Kamp <phk@critter.freebsd.dk>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
In message <199901252212.OAA18030@bubba.whistle.com>, Archie Cobbs writes:
>Doug Rabson writes:
>>
>> If anyone is interested in seeing diffs (approx 23k), please contact me.
>
>I'm interested.. could you email me the diffs?
>
>I'm more interested in whether these patches can be committed... ?
>Have Poul, DG, et. al. seen them?
I'm somewhat weary of doing too much for sysctl, until we have
intelligently examined the stuff and decided which way we want to
go with it.
(This patch is probably perfectly all right, without this comment
being construed as a "Reviewed by:" :-), but before it goes in, I
would like to hear if sysctl "is basically what we want" or if
sysctl needs to be extended (for instance in the "repository"
direction) ?
One of the weak points about the current sysctl scheme is the
rather simpleminded permission scheme, will we need something
more capable ? The current system >is< capable if you write it
yourself in a function, but we don't want 100 functions doing
the same thing.)
We probably also need to consider name-space management...
And, documentation. I do like the "semi-literate" programming
style, where you can stick a meaningfull documentation (ie,
potentially several pages of it) right there in the source, (but
I don't want it compiled in and loaded!) but for it to become real
documentation, SGML or -man will be needed, and that would probably
be too ugly for most eyes, or no ?
--
Poul-Henning Kamp FreeBSD coreteam member
phk@FreeBSD.ORG "Real hackers run -current on their laptop."
FreeBSD -- It will take a long time before progress goes too far!
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Mon Jan 25 14:33:32 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id OAA23576
for freebsd-current-outgoing; Mon, 25 Jan 1999 14:33:32 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.95.76.54])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA23562
for <freebsd-current@freebsd.org>; Mon, 25 Jan 1999 14:33:28 -0800 (PST)
(envelope-from sgk@troutmask.apl.washington.edu)
Received: (from sgk@localhost)
by troutmask.apl.washington.edu (8.9.1/8.9.1) id OAA02595
for freebsd-current@freebsd.org; Mon, 25 Jan 1999 14:34:55 -0800 (PST)
(envelope-from sgk)
From: Steve Kargl <sgk@troutmask.apl.washington.edu>
Message-Id: <199901252234.OAA02595@troutmask.apl.washington.edu>
Subject: removing f2c from base distribution
To: freebsd-current@FreeBSD.ORG
Date: Mon, 25 Jan 1999 14:34:55 -0800 (PST)
X-Mailer: ELM [version 2.4ME+ PL43 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
Ladies and Gents,
I have completed the portification of f2c and its support library.
In principle, src/usr.bin/f2c, src/lib/{libI77,libF77,libf2c}, and
src/gnu/usr.bin/cc/f77 can be moved into the attic in -current (4.x).
Appropriate adjustments to the Makefile files in src/usr.bin,
src/lib, and src/gnu/usr.bin/cc need to be made.
ftp://troutmask.apl.washington.edu/pub/f2c-freebsd.2.0.1.tar.gz
ftp://troutmask.apl.washington.edu/pub/f2c-freebsd.tgz
ftp://troutmask.apl.washington.edu/pub/f77-freebsd.0.3.tar.gz
ftp://troutmask.apl.washington.edu/pub/f77-freebsd.tgz
f2c-freebsd.2.0.1.tar.gz is a version of f2c and its library
where I have merged the version in the FreeBSD source tree from
Dec 1998 with the latest version of f2c and its library from
www.netlib.org. The Makefile in f2c-freebsd.2.0.1/libf2c is setup
to build only ELF libraries which is reasonable because this is
as a replacement for functionality in a post-elf-transition source
tree.
f2c-freebsd.tgz is a gzipped tar file of the port. It should
be placed in ports/lang. When unpacked it will produce a
directory named f2c-freebsd, and it should be able to be built
on both i386 and alpha axp architectures.
f77-freebsd.0.3.tar.gz contains the source code for a new driver
utility that is meant to replace the current f77(1) in
src/gnu/usr.bin/cc/f77. By default, the new f77 will use Sun
Microsystem's Fortran preprocessor (ports/devel/fpp), but it
can be built to use GNU cpp. The new f77 recognizes all f2c and
fpp (or cpp) options that make sense in the context of compilation.
Any option not recognized as a valid f2c or fpp (or cpp) option is
automatically passed to gcc except for gcc options that take
space delimited arguments (these aren't supported, yet).
f77-freebsd.tgz is a gzipped tar file of the port. It should
be placed in ports/lang. When unpacked it will produce a
directory named f77-freebsd. The new f77(1) should be
architecture independent, but I don't have an alpha axp machine
for testing.
NOTE: Do *NOT* try to use the f2c port with the old f77(1) from
src/gnu/usr.bin/cc/f77. The loader can't find the f2c.h header
file or the new library locations.
--
Steve
finger kargl@troutmask.apl.washington.edu
http://troutmask.apl.washington.edu/~clesceri/kargl.html
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Mon Jan 25 14:44:13 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id OAA24961
for freebsd-current-outgoing; Mon, 25 Jan 1999 14:44:13 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from whistle.com (s205m131.whistle.com [207.76.205.131])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA24938;
Mon, 25 Jan 1999 14:44:01 -0800 (PST)
(envelope-from archie@whistle.com)
Received: (from smap@localhost) by whistle.com (8.7.5/8.6.12) id OAA15329; Mon, 25 Jan 1999 14:44:00 -0800 (PST)
Received: from bubba.whistle.com( 207.76.205.7) by whistle.com via smap (V2.0)
id xma015327; Mon, 25 Jan 99 14:43:34 -0800
Received: (from archie@localhost) by bubba.whistle.com (8.8.7/8.6.12) id OAA18272; Mon, 25 Jan 1999 14:43:34 -0800 (PST)
From: Archie Cobbs <archie@whistle.com>
Message-Id: <199901252243.OAA18272@bubba.whistle.com>
Subject: libbind, etc.
To: peter@FreeBSD.ORG, current@FreeBSD.ORG
Date: Mon, 25 Jan 1999 14:43:34 -0800 (PST)
X-Mailer: ELM [version 2.4ME+ PL38 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
Right now we build libbind (so named, etc. can link) but don't
install it in /usr/lib.
However, there are parts of it that would be very nice to have
available to user programs.. in particular the event library
(see: "nroff -man /usr/src/contrib/bind/lib/isc/eventlib.mdoc" )
I would like to make this stuff available somehow as a library
in /usr/lib. Would anyone violently object? And what would be
the best approach?
Since some of libbind is already part of libc, we proabably don't
want to install all of libbind .. perhaps we could just install
the event library and call it libevent ?
Nordic-proof flame suit ready,
-Archie
___________________________________________________________________________
Archie Cobbs * Whistle Communications, Inc. * http://www.whistle.com
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Mon Jan 25 14:48:05 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id OAA25312
for freebsd-current-outgoing; Mon, 25 Jan 1999 14:47:06 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from whistle.com (s205m131.whistle.com [207.76.205.131])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA25297;
Mon, 25 Jan 1999 14:47:01 -0800 (PST)
(envelope-from archie@whistle.com)
Received: (from smap@localhost) by whistle.com (8.7.5/8.6.12) id OAA15365; Mon, 25 Jan 1999 14:47:01 -0800 (PST)
Received: from bubba.whistle.com( 207.76.205.7) by whistle.com via smap (V2.0)
id xma015363; Mon, 25 Jan 99 14:46:33 -0800
Received: (from archie@localhost) by bubba.whistle.com (8.8.7/8.6.12) id OAA18293; Mon, 25 Jan 1999 14:46:33 -0800 (PST)
From: Archie Cobbs <archie@whistle.com>
Message-Id: <199901252246.OAA18293@bubba.whistle.com>
Subject: Same module loaded twice?
To: current@freebsd.org, hackers@freebsd.org
Date: Mon, 25 Jan 1999 14:46:33 -0800 (PST)
X-Mailer: ELM [version 2.4ME+ PL38 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-current@freebsd.org
Precedence: bulk
X-Loop: FreeBSD.ORG
In the output below, notice there are two modules named "ng_sync_sr"
loaded in the "kernel" object (due to a typo), and moreover there's
a "netgraph" module loaded in both the "kernel" object and the "netgraph.ko"
object..
$ kldstat -v
Id Refs Address Size Name
1 4 0xf0100000 1be82c kernel
Contains modules:
Id Name
1 rootbus
2 netgraph
3 ng_sync_sr
4 ng_sync_sr
5 ufs
6 nfs
7 msdos
8 procfs
9 cd9660
10 ipfw
11 if_tun
12 if_sl
13 if_ppp
14 if_loop
15 shell
16 execgzip
17 elf
18 aout
2 1 0xf07f1000 3000 ng_socket.ko
Contains modules:
Id Name
20 ng_socket
3 2 0xf07f5000 4000 netgraph.ko
Contains modules:
Id Name
19 netgraph
Why and how does the linker allow this? It seems like:
- When the kernel was compiled, the ng_sync_sr conflict should
have caused a failure
- When the netgraph.ko was kldloaded, there should have been
an error from the conflicting module names
Curiously,
-Archie
___________________________________________________________________________
Archie Cobbs * Whistle Communications, Inc. * http://www.whistle.com
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Mon Jan 25 15:15:44 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id PAA29679
for freebsd-current-outgoing; Mon, 25 Jan 1999 15:15:44 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from alushta.NL.net (alushta.NL.net [193.78.240.22])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA29672
for <current@freebsd.org>; Mon, 25 Jan 1999 15:15:42 -0800 (PST)
(envelope-from benst@terminus.stuyts.nl)
Received: from stuyts by alushta.NL.net with UUCP id <8735-6863>; Tue, 26 Jan 1999 00:15:30 +0100
Received: from daneel.stuyts.nl (daneel.stuyts.nl [193.78.231.7])
by terminus.stuyts.nl (8.9.1/8.9.1) with ESMTP id XAA16537
for <current@freebsd.org>; Mon, 25 Jan 1999 23:28:11 +0100 (MET)
(envelope-from benst)
Received: (from benst@localhost)
by daneel.stuyts.nl (8.8.5/8.8.5) id XAA11789
for current@freebsd.org; Mon, 25 Jan 1999 23:28:16 +0100 (MET)
Message-Id: <199901252228.XAA11789@daneel.stuyts.nl>
Content-Type: text/plain
MIME-Version: 1.0 (NeXT Mail 3.3 v118.2)
X-Nextstep-Mailer: Mail 3.3 (Enhance 1.2)
Received: by NeXT.Mailer (1.118.2)
From: Ben Stuyts <ben@stuyts.nl>
Date: Mon, 25 Jan 99 23:28:13 +0100
To: current@FreeBSD.ORG
Subject: Req: "make update" target in ports/doc
Reply-To: ben@stuyts.nl
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
Hello,
Would it be possible to add a "make update" target to the top Makefile in
ports and doc? Similar to the Makefile in /usr/src, so that it does something
like "cvs -q update -P -d".
It would keep the Makefiles more orthogonal, and in any case, make update
types easier than cvs -q update -P -d. B-)
Kind regards,
Ben
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Mon Jan 25 15:17:20 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id PAA00146
for freebsd-current-outgoing; Mon, 25 Jan 1999 15:17:20 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from hawaii.conterra.com (hawaii.conterra.com [209.12.164.32])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA00113
for <current@FreeBSD.ORG>; Mon, 25 Jan 1999 15:17:16 -0800 (PST)
(envelope-from myself@conterra.com)
Received: from dmaddox.conterra.com (dmaddox.conterra.com [209.12.169.48])
by hawaii.conterra.com (8.8.8/8.8.7) with ESMTP id SAA09821
for <current@FreeBSD.ORG>; Mon, 25 Jan 1999 18:17:14 -0500 (EST)
Received: (from myself@localhost)
by dmaddox.conterra.com (8.9.2/8.9.1) id SAA01286
for current@FreeBSD.ORG; Mon, 25 Jan 1999 18:17:13 -0500 (EST)
(envelope-from myself)
Date: Mon, 25 Jan 1999 18:17:12 -0500
From: "Donald J . Maddox" <dmaddox@conterra.com>
To: current@FreeBSD.ORG
Subject: link_elf: symbol lkmexists undefined
Message-ID: <19990125181712.B1172@dmaddox.conterra.com>
Reply-To: dmaddox@conterra.com
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.95.1i
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
Since building a new kernel and a full 'make world' on Jan 24,
I am seeing this at boot:
avail memory = 62210048 (60752K bytes)
Preloaded elf kernel "kernel" at 0xf02cc000.
Preloaded elf module "msdos.ko" at 0xf02cc09c.
Preloaded elf module "procfs.ko" at 0xf02cc13c.
Preloaded elf module "if_tun.ko" at 0xf02cc1dc.
Preloaded elf module "if_disc.ko" at 0xf02cc27c.
Preloaded elf module "linux.ko" at 0xf02cc31c.
Preloaded elf module "vesa.ko" at 0xf02cc3bc.
Preloaded elf module "joy.ko" at 0xf02cc458.
link_elf: symbol lkmexists undefined
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Anybody have any idea where this is coming from?
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Mon Jan 25 15:31:25 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id PAA01872
for freebsd-current-outgoing; Mon, 25 Jan 1999 15:31:25 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from janus.syracuse.net (janus.syracuse.net [205.232.47.15])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA01860
for <current@freebsd.org>; Mon, 25 Jan 1999 15:31:17 -0800 (PST)
(envelope-from green@unixhelp.org)
Received: from localhost (green@localhost)
by janus.syracuse.net (8.8.8/8.8.7) with ESMTP id SAA03178
for <current@freebsd.org>; Mon, 25 Jan 1999 18:31:21 -0500 (EST)
Date: Mon, 25 Jan 1999 18:31:20 -0500 (EST)
From: Brian Feldman <green@unixhelp.org>
X-Sender: green@janus.syracuse.net
To: current@FreeBSD.ORG
Subject: Addition to /etc/rc, maybe
Message-ID: <Pine.BSF.4.05.9901251830570.2040-100000@janus.syracuse.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
How does this look?
--- src/etc/rc.orig Mon Jan 25 17:39:07 1999
+++ src/etc/rc Mon Jan 25 17:43:52 1999
@@ -152,6 +152,16 @@
clean_var
fi
+# Load the vn module, if enabled.
+if [ "X$vn_enable" = "XYES" ]; then
+ echo "Loading vn module."
+ if [ -f /modules/vn.ko ]; then
+ kldload vn
+ else
+ echo "Cannot find /modules/vn.ko."
+ fi
+fi
+
# Add additional swapfile, if configured.
if [ "x$swapfile" != "xNO" -a -w "$swapfile" -a -b /dev/vn0b ]; then
echo "Adding $swapfile as additional swap."
--- src/etc/rc.conf.orig Mon Jan 25 17:36:03 1999
+++ src/etc/rc.conf Mon Jan 25 17:44:14 1999
@@ -12,7 +12,9 @@
### Important initial Boot-time options #####################
##############################################################
+vn_enable="NO" # Set to YES if you want the vn kld loaded.
swapfile="NO" # Set to name of swapfile if aux swapfile desired.
+ # This needs pseudo-device vn or vn_enable="YES".
apm_enable="NO" # Set to YES if you want APM enabled.
pccard_enable="NO" # Set to YES if you want to configure PCCARD devices.
pccard_mem="DEFAULT" # If pccard_enable=YES, this is card memory address.
Brian Feldman _ __ ___ ___ ___
green@unixhelp.org _ __ ___ | _ ) __| \
http://www.freebsd.org/ _ __ ___ ____ | _ \__ \ |) |
FreeBSD: The Power to Serve! _ __ ___ ____ _____ |___/___/___/
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Mon Jan 25 15:38:22 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id PAA02760
for freebsd-current-outgoing; Mon, 25 Jan 1999 15:38:22 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from janus.syracuse.net (janus.syracuse.net [205.232.47.15])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA02749
for <current@FreeBSD.ORG>; Mon, 25 Jan 1999 15:38:18 -0800 (PST)
(envelope-from green@unixhelp.org)
Received: from localhost (green@localhost)
by janus.syracuse.net (8.8.8/8.8.7) with ESMTP id SAA03628;
Mon, 25 Jan 1999 18:37:55 -0500 (EST)
Date: Mon, 25 Jan 1999 18:37:55 -0500 (EST)
From: Brian Feldman <green@unixhelp.org>
X-Sender: green@janus.syracuse.net
To: Luigi Rizzo <luigi@labinfo.iet.unipi.it>
cc: Alfred Perlstein <bright@hotjobs.com>, current@FreeBSD.ORG
Subject: Re: dummynet causes crash?
In-Reply-To: <199901240556.GAA23221@labinfo.iet.unipi.it>
Message-ID: <Pine.BSF.4.05.9901251836320.2040-100000@janus.syracuse.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
On Sun, 24 Jan 1999, Luigi Rizzo wrote:
> which version of ip_dummynet are you using. There were lately a few
> changes to fix a problem related to route entries being freed in the
> wrong way.
>
> > .(02:36:11)(root@bright.reserved)
> > ipfw add pipe 1 ip from server to cvsup.freebsd.org
> > (long pause i assume DNS)
> > 00000 pipe 1 ip from 192.168.2.20 to 198.104.92.71
> ...
> >
> > Fatal trap 12: page fault while in kernel mode
> > fault virtual address = 0xdeadc116
>
> interestingly enough, the above address is "0xdeadbeef + 551 (decimal)".
> It looks like somehow a wrong route entry was passed to ether_output().
>
> > the only thing i can think of is that dummynet doesn't like not being told
> > if a pipe is 'in' or 'out' :/
>
> nope -- it can detect this by itself. the problem must be elsewhere.
> if you have more input on the dummynet version (as per the CVS log)
> and os version please let me know.
>
> > my ether card is a: ed card, a 'realteck 8029'
>
> ... and the network card does not make a difference, dummynet works at
> a layer above.
>
> cheers
> luigi
{"/home/green"}$ calc 0xdeadc116 - 0xdeadc0de
56
possibly? IIRC 0xdeadc0de is used to fill freed memory areas in certain cases,
to help detect programming errors related to such.
>
> To Unsubscribe: send mail to majordomo@FreeBSD.org
> with "unsubscribe freebsd-current" in the body of the message
>
Brian Feldman _ __ ___ ___ ___
green@unixhelp.org _ __ ___ | _ ) __| \
http://www.freebsd.org/ _ __ ___ ____ | _ \__ \ |) |
FreeBSD: The Power to Serve! _ __ ___ ____ _____ |___/___/___/
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Mon Jan 25 15:55:53 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id PAA04922
for freebsd-current-outgoing; Mon, 25 Jan 1999 15:55:53 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from janus.syracuse.net (janus.syracuse.net [205.232.47.15])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA04914
for <freebsd-current@FreeBSD.ORG>; Mon, 25 Jan 1999 15:55:50 -0800 (PST)
(envelope-from green@unixhelp.org)
Received: from localhost (green@localhost)
by janus.syracuse.net (8.8.8/8.8.7) with ESMTP id SAA04895;
Mon, 25 Jan 1999 18:55:41 -0500 (EST)
Date: Mon, 25 Jan 1999 18:55:40 -0500 (EST)
From: Brian Feldman <green@unixhelp.org>
X-Sender: green@janus.syracuse.net
To: Dag-Erling Smorgrav <des@flood.ping.uio.no>
cc: Boris Staeblow <balu@dva.in-berlin.de>, dillon@apollo.backplane.com,
freebsd-current@FreeBSD.ORG
Subject: Re: Heads up! New swapper and VM changes have been committed to -4.x
In-Reply-To: <xzpiudwfq07.fsf@flood.ping.uio.no>
Message-ID: <Pine.BSF.4.05.9901251855010.2040-100000@janus.syracuse.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
On 24 Jan 1999, Dag-Erling Smorgrav wrote:
> Boris Staeblow <balu@dva.in-berlin.de> writes:
> > Beside your suggestions there are much more programs which use
> > libkvm:
> >
> > /bin/ps/
> > /libexec/rpc.rstatd/
> > /sbin/ccdconfig/
> > /sbin/dmesg/
>
> These are statically linked, and must be relinked after libkvm has
> been rebuilt.
>
> > /sbin/dset/
>
> This does not exist anymore.
>
> > /usr.bin/fstat/
> > /usr.bin/gcore/
> > /usr.bin/ipcs/
> > /usr.bin/netstat/
> > /usr.bin/nfsstat/
> > /usr.bin/systat/
> > /usr.bin/top/
> > /usr.bin/vmstat/
> > /usr.bin/w/
> > /usr.sbin/iostat/
> > /usr.sbin/kernbb/
> > /usr.sbin/kgmon/
> > /usr.sbin/pstat/
> > /usr.sbin/xntpd/xntpd/
>
> These are dynamically linked, and will automatically pick up the new
> libkvm.
>
But (most) still require the structures to be the exact same way, which is the
reason for the recompile anyway... don't forget that!
> DES
> --
> Dag-Erling Smorgrav - des@flood.ping.uio.no
>
> To Unsubscribe: send mail to majordomo@FreeBSD.org
> with "unsubscribe freebsd-current" in the body of the message
>
Brian Feldman _ __ ___ ___ ___
green@unixhelp.org _ __ ___ | _ ) __| \
http://www.freebsd.org/ _ __ ___ ____ | _ \__ \ |) |
FreeBSD: The Power to Serve! _ __ ___ ____ _____ |___/___/___/
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Mon Jan 25 16:03:17 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id QAA07008
for freebsd-current-outgoing; Mon, 25 Jan 1999 16:03:17 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from crap.31337.net (node1484.a2000.nl [62.108.20.132])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA07001
for <freebsd-current@freebsd.org>; Mon, 25 Jan 1999 16:03:14 -0800 (PST)
(envelope-from alexlh@funk.org)
Received: from p.funk.org (nose.funk.org [194.109.86.229])
by crap.31337.net (8.9.1/8.9.1) with ESMTP id AAA07912
for <freebsd-current@freebsd.org>; Tue, 26 Jan 1999 00:20:36 GMT
(envelope-from alexlh@funk.org)
Received: from funk.org (localhost.a2000.nl [127.0.0.1])
by p.funk.org (8.9.2/8.9.1) with ESMTP id BAA71694
for <freebsd-current@freebsd.org>; Tue, 26 Jan 1999 01:02:54 +0100 (CET)
(envelope-from alexlh@funk.org)
Message-ID: <36AD062E.EDF6A994@funk.org>
Date: Tue, 26 Jan 1999 01:02:54 +0100
From: Alex Le Heux <alexlh@funk.org>
X-Mailer: Mozilla 4.5 [en] (X11; I; FreeBSD 4.0-CURRENT i386)
X-Accept-Language: en
MIME-Version: 1.0
To: freebsd-current@FreeBSD.ORG
Subject: usb driver broken?
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
Hi,
Am I the only one who gets this when he tries to compile a kernel with
the usb drivers in it?
cc -c -O -Wreturn-type -Wcomment -Wredundant-decls -Wimplicit
-Wnested-externs -Wstrict-prototypes -Wmissing-prototypes
-Wpointer-arith -Winline -Wuninitialized -Wformat -Wunused
-fformat-extensions -ansi -nostdinc -I- -I. -I../.. -I../../../include
-DKERNEL -include opt_global.h -elf ../../dev/usb/uhci.c
../../dev/usb/uhci.c: In function `uhci_dumpregs':
../../dev/usb/uhci.c:406: `UHCI_LEGSUP' undeclared (first use this
function)
../../dev/usb/uhci.c:406: (Each undeclared identifier is reported only
once
../../dev/usb/uhci.c:406: for each function it appears in.)
machine/cpufunc.h:284: warning: inlining failed in call to `inw'
../../dev/usb/uhci.c:406: warning: called from here
*** Error code 1
Stop.
Alex
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Mon Jan 25 16:34:15 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id QAA12199
for freebsd-current-outgoing; Mon, 25 Jan 1999 16:34:15 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from rebma.ghostwheel.com (rebma.ghostwheel.com [207.201.56.159])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA12185
for <freebsd-current@FreeBSD.ORG>; Mon, 25 Jan 1999 16:34:12 -0800 (PST)
(envelope-from fbsd-cur@ghostwheel.com)
Received: from avalon (avalon.ghostwheel.com [207.201.56.88])
by rebma.ghostwheel.com (8.8.8/8.8.8) with SMTP id QAA20319;
Mon, 25 Jan 1999 16:32:51 -0800 (PST)
(envelope-from fbsd-cur@ghostwheel.com)
Message-Id: <4.1.19990125162916.0098d930@pop2.ghostwheel.com>
X-Sender: fbsd-cur@pop2.ghostwheel.com (Unverified)
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.1
Date: Mon, 25 Jan 1999 16:29:28 -0800
To: Leif Neland <leif@neland.dk>
From: Chris Knight <fbsd-cur@ghostwheel.com>
Subject: Re: Can't mount root. Really need help...
Cc: freebsd-current@FreeBSD.ORG
In-Reply-To: <Pine.BSF.4.05.9901251828410.2887-100000@arnold.neland.dk>
References: <4.1.19990124151511.009793a0@pop2.ghostwheel.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
At 06:29 PM 1/25/99 +0100, Leif Neland wrote:
>
>
>On Sun, 24 Jan 1999, Chris Knight wrote:
>
>> Greetings,
>>
>> I have learned a very valuable lesson. No matter how many time I have
>> made world, I shouldn't do it while I'm tired. Last night I synced my tree
>> and made world. I rebooted, and was going to remake my kernel after the
>> boot. That became an impossibility.
>>
>
>Can't you boot kernel.old?
Although I have gotten past this, it was not kernel realated. I had made
world, but not yet remade my kernel. The problem was in /boot/loader, and
I was able to get past it by using /boot/loader.old
Thanks for the response though!
-ck
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Mon Jan 25 16:40:48 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id QAA13358
for freebsd-current-outgoing; Mon, 25 Jan 1999 16:40:48 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from janus.syracuse.net (janus.syracuse.net [205.232.47.15])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA13349
for <current@FreeBSD.ORG>; Mon, 25 Jan 1999 16:40:42 -0800 (PST)
(envelope-from green@unixhelp.org)
Received: from localhost (green@localhost)
by janus.syracuse.net (8.8.8/8.8.7) with ESMTP id TAA07361;
Mon, 25 Jan 1999 19:40:38 -0500 (EST)
Date: Mon, 25 Jan 1999 19:40:38 -0500 (EST)
From: Brian Feldman <green@unixhelp.org>
X-Sender: green@janus.syracuse.net
To: Matthew Dillon <dillon@apollo.backplane.com>
cc: Lee Cremeans <lee@st-lcremean.tidalwave.net>, current@FreeBSD.ORG
Subject: Re: IDE DMA works, I'll be a...
In-Reply-To: <199901250453.UAA00799@apollo.backplane.com>
Message-ID: <Pine.BSF.4.05.9901251937010.6492-100000@janus.syracuse.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
On Sun, 24 Jan 1999, Matthew Dillon wrote:
>
> :> I haven't cvs updated in 24 hours, if the Acer is newly committed then I'll
> :> have to update again and retry. The CTX is using the Acer.
> :>
> :> ide_pci0: <Acer Aladdin IV/V (M5229) Bus-master IDE controller> rev 0x20 int a irq 0 on pci0.11.0
> : ^^^^^^^^^^^^^^^^^^^^^^^^
> :
> :It's there...what symptoms are you seeing? Are you overclocking?
> :--
> :+--------------------------------------------------------------------+
> :| Lee Cremeans -- Manassas, VA, USA (WakkyMouse on DALnet and WTnet)|
>
>
> No overclocking. Stock CTX box. Could it be the drive, maybe?
>
> I only get 2.4 MBytes/sec, same as before. On my PPro box ( Intel
> PIIX3 Bus-master IDE controller ) it went from around 2.4 MB/sec
> to 8 MBytes/sec.
>
> archive:/cvs# time dd if=/dev/zero of=test2 bs=32k count=1024
> 1024+0 records in
> 1024+0 records out
> 33554432 bytes transferred in 13.700387 secs (2449159 bytes/sec)
> 0.000u 2.728s 0:13.75 19.7% 357+1405k 5+525io 1pf+0w
>
Hmm, this is strange. I used to be able to get >3MB/s with an old chipset and
plain K6, now with
ide_pci0: <Acer Aladdin IV/V (M5229) Bus-master IDE controller> rev 0x20 int a $
wdc0 at 0x1f0-0x1f7 irq 14 flags 0xa0ffa0ff on isa
wdc0: unit 0 (wd0): <Maxtor 71626 AP>, DMA, 32-bit, multi-block-32
wd0: 1554MB (3183264 sectors), 3158 cyls, 16 heads, 63 S/T, 512 B/S
wdc0: unit 1 (wd1): <Maxtor 71626 AP>, DMA, 32-bit, multi-block-32
wd1: 1554MB (3183264 sectors), 3158 cyls, 16 heads, 63 S/T, 512 B/S
wdc1 at 0x170-0x177 irq 15 flags 0xa0ffa0ff on isa
wdc1: unit 0 (atapi): <LS-120 COSM 02 UHD Floppy/0271C09T>, removable, iordy
wfd0: medium type unknown (no disk)
wdc1: unit 1 (atapi): <NEC CD-ROM DRIVE:285/3.04>, removable, dma, iordy
This is strange, because DMA enabled on wd[01] and acd0 doesn't seem to... err
"work". I say this because I am down to ~2.5MB/s on each hard drive, a MB or
so decrease; I also seem to be reading (bs=512k) from the CD uncooked device
at the right speed (~2MB/s), but it takes up 40% of the CPU, which seems
to be just PIO. Anyone else?
>
> -Matt
> Matthew Dillon
> <dillon@backplane.com>
>
> ide_pci0: <Acer Aladdin IV/V (M5229) Bus-master IDE controller> rev 0x20 int a irq 0 on pci0.11.0
> wdc0 at 0x1f0-0x1f7 irq 14 flags 0xa0ffa0ff on isa
> wdc0: unit 0 (wd0): <QUANTUM Bigfoot TX4.0AT>, 32-bit, multi-block-16
> wd0: 3832MB (7849170 sectors), 8306 cyls, 15 heads, 63 S/T, 512 B/S
> wdc1 at 0x170-0x177 irq 15 flags 0xa0ffa0ff on isa
> wdc1: unit 0 (atapi): <ATAPI CDROM/V1.70>, removable, dma, iordy
>
>
> To Unsubscribe: send mail to majordomo@FreeBSD.org
> with "unsubscribe freebsd-current" in the body of the message
>
Brian Feldman _ __ ___ ___ ___
green@unixhelp.org _ __ ___ | _ ) __| \
http://www.freebsd.org/ _ __ ___ ____ | _ \__ \ |) |
FreeBSD: The Power to Serve! _ __ ___ ____ _____ |___/___/___/
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Mon Jan 25 16:46:02 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id QAA14094
for freebsd-current-outgoing; Mon, 25 Jan 1999 16:46:02 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from axl.noc.iafrica.com (axl.noc.iafrica.com [196.31.1.175])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA14059
for <current@freebsd.org>; Mon, 25 Jan 1999 16:45:59 -0800 (PST)
(envelope-from sheldonh@axl.noc.iafrica.com)
Received: from sheldonh (helo=axl.noc.iafrica.com)
by axl.noc.iafrica.com with local-esmtp (Exim 2.10 #1)
id 104wdI-0000QD-00; Tue, 26 Jan 1999 02:45:32 +0200
From: Sheldon Hearn <axl@iafrica.com>
To: Brian Feldman <green@unixhelp.org>
cc: Matthew Dillon <dillon@apollo.backplane.com>,
Lee Cremeans <lee@st-lcremean.tidalwave.net>, current@FreeBSD.ORG
Subject: Re: IDE DMA works, I'll be a...
In-reply-to: Your message of "Mon, 25 Jan 1999 19:40:38 EST."
<Pine.BSF.4.05.9901251937010.6492-100000@janus.syracuse.net>
Date: Tue, 26 Jan 1999 02:45:32 +0200
Message-ID: <1624.917311532@axl.noc.iafrica.com>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
On Mon, 25 Jan 1999 19:40:38 EST, Brian Feldman wrote:
> I say this because I am down to ~2.5MB/s on each hard drive, a MB or
> so decrease; I also seem to be reading (bs=512k) from the CD uncooked
> device at the right speed (~2MB/s), but it takes up 40% of the CPU,
> which seems to be just PIO. Anyone else?
Since I rebuilt world shortly after Matt's VM surgery started, I've also
noticed this -- lower apparent transfer rates from /dev/zero to disk,
higher CPU usage during such transfers.
I'm _not_ saying it's Matt's stuff that's done this, it's just that that
was the stuff I _noticed_ happening in commit mail. I think I saw
something happening to wd.c recently as well, so I _definitely_ am not
going on record as laying blame.
Just some confirmation. :-)
Ciao,
Sheldon.
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Mon Jan 25 17:00:03 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id RAA16157
for freebsd-current-outgoing; Mon, 25 Jan 1999 17:00:03 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA16111
for <current@FreeBSD.ORG>; Mon, 25 Jan 1999 16:59:59 -0800 (PST)
(envelope-from dillon@apollo.backplane.com)
Received: (from dillon@localhost)
by apollo.backplane.com (8.9.2/8.9.1) id QAA08899;
Mon, 25 Jan 1999 16:59:40 -0800 (PST)
(envelope-from dillon)
Date: Mon, 25 Jan 1999 16:59:40 -0800 (PST)
From: Matthew Dillon <dillon@apollo.backplane.com>
Message-Id: <199901260059.QAA08899@apollo.backplane.com>
To: Sheldon Hearn <axl@iafrica.com>
Cc: Brian Feldman <green@unixhelp.org>,
Lee Cremeans <lee@st-lcremean.tidalwave.net>, current@FreeBSD.ORG
Subject: Re: IDE DMA works, I'll be a...
References: <1624.917311532@axl.noc.iafrica.com>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
:On Mon, 25 Jan 1999 19:40:38 EST, Brian Feldman wrote:
:
:> I say this because I am down to ~2.5MB/s on each hard drive, a MB or
:> so decrease; I also seem to be reading (bs=512k) from the CD uncooked
:...
:
:Since I rebuilt world shortly after Matt's VM surgery started, I've also
:noticed this -- lower apparent transfer rates from /dev/zero to disk,
:higher CPU usage during such transfers.
:
:I'm _not_ saying it's Matt's stuff that's done this, it's just that that
:was the stuff I _noticed_ happening in commit mail. I think I saw
:something happening to wd.c recently as well, so I _definitely_ am not
:going on record as laying blame.
:
:Just some confirmation. :-)
:
:Ciao,
:Sheldon.
Hmm, interesting. A dd copy doesn't touch on the main of what I did,
but I do have a (bad) hack in there to handle a case that John brought
up in regards to the inactive page queue getting overloaded with
clean meta-data. It might be interesting to turn that off and see if
your transfer rates improve.
You can turn off the hack by commenting out the case that activates
it: Add the #if/#endif and split the open brace out from the else,
as shown.
I would like to know if your transfer rate improves or not, and by
how much.
/*
* Figure out what to do with dirty pages when they are encountered.
* Assume that 1/3 of the pages on the inactive list are clean. If
* we think we can reach our target, disable laundering (do not
* clean any dirty pages). If we miss the target we will loop back
* up and do a laundering run.
*/
#if 0
if (cnt.v_inactive_count / 3 > page_shortage) {
maxlaunder = 0;
launder_loop = 0;
} else
#endif
{
maxlaunder =
(cnt.v_inactive_target > max_page_launder) ?
max_page_launder : cnt.v_inactive_target;
launder_loop = 1;
}
-Matt
Matthew Dillon
<dillon@backplane.com>
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Mon Jan 25 17:18:35 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id RAA19070
for freebsd-current-outgoing; Mon, 25 Jan 1999 17:18:35 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from janus.syracuse.net (janus.syracuse.net [205.232.47.15])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA19061
for <current@FreeBSD.ORG>; Mon, 25 Jan 1999 17:18:33 -0800 (PST)
(envelope-from green@unixhelp.org)
Received: from localhost (green@localhost)
by janus.syracuse.net (8.8.8/8.8.7) with ESMTP id UAA09555;
Mon, 25 Jan 1999 20:18:12 -0500 (EST)
Date: Mon, 25 Jan 1999 20:18:12 -0500 (EST)
From: Brian Feldman <green@unixhelp.org>
X-Sender: green@janus.syracuse.net
To: Matthew Dillon <dillon@apollo.backplane.com>
cc: Sheldon Hearn <axl@iafrica.com>,
Lee Cremeans <lee@st-lcremean.tidalwave.net>, current@FreeBSD.ORG
Subject: Re: IDE DMA works, I'll be a...
In-Reply-To: <199901260059.QAA08899@apollo.backplane.com>
Message-ID: <Pine.BSF.4.05.9901252016180.7918-100000@janus.syracuse.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
On Mon, 25 Jan 1999, Matthew Dillon wrote:
> :On Mon, 25 Jan 1999 19:40:38 EST, Brian Feldman wrote:
> :
> :> I say this because I am down to ~2.5MB/s on each hard drive, a MB or
> :> so decrease; I also seem to be reading (bs=512k) from the CD uncooked
> :...
> :
> :Since I rebuilt world shortly after Matt's VM surgery started, I've also
> :noticed this -- lower apparent transfer rates from /dev/zero to disk,
> :higher CPU usage during such transfers.
> :
> :I'm _not_ saying it's Matt's stuff that's done this, it's just that that
> :was the stuff I _noticed_ happening in commit mail. I think I saw
> :something happening to wd.c recently as well, so I _definitely_ am not
> :going on record as laying blame.
> :
> :Just some confirmation. :-)
> :
> :Ciao,
> :Sheldon.
>
> Hmm, interesting. A dd copy doesn't touch on the main of what I did,
> but I do have a (bad) hack in there to handle a case that John brought
> up in regards to the inactive page queue getting overloaded with
> clean meta-data. It might be interesting to turn that off and see if
> your transfer rates improve.
>
> You can turn off the hack by commenting out the case that activates
> it: Add the #if/#endif and split the open brace out from the else,
> as shown.
>
> I would like to know if your transfer rate improves or not, and by
> how much.
>
>
> /*
> * Figure out what to do with dirty pages when they are encountered.
> * Assume that 1/3 of the pages on the inactive list are clean. If
> * we think we can reach our target, disable laundering (do not
> * clean any dirty pages). If we miss the target we will loop back
> * up and do a laundering run.
> */
>
> #if 0
> if (cnt.v_inactive_count / 3 > page_shortage) {
> maxlaunder = 0;
> launder_loop = 0;
> } else
> #endif
> {
> maxlaunder =
> (cnt.v_inactive_target > max_page_launder) ?
> max_page_launder : cnt.v_inactive_target;
> launder_loop = 1;
> }
>
>
> -Matt
> Matthew Dillon
> <dillon@backplane.com>
>
I'd rather use if (0 && cnt.v_inactive_count / 3 > page_shortage) {. I'm
trying it out now, here's the "before":
IOZONE performance measurements:
2972048 bytes/second for writing the file
2962863 bytes/second for reading the file
>
> To Unsubscribe: send mail to majordomo@FreeBSD.org
> with "unsubscribe freebsd-current" in the body of the message
>
Brian Feldman _ __ ___ ___ ___
green@unixhelp.org _ __ ___ | _ ) __| \
http://www.freebsd.org/ _ __ ___ ____ | _ \__ \ |) |
FreeBSD: The Power to Serve! _ __ ___ ____ _____ |___/___/___/
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Mon Jan 25 17:32:47 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id RAA21134
for freebsd-current-outgoing; Mon, 25 Jan 1999 17:32:47 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from arg1.demon.co.uk (arg1.demon.co.uk [194.222.34.166])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA21124
for <current@FreeBSD.ORG>; Mon, 25 Jan 1999 17:32:40 -0800 (PST)
(envelope-from arg@arg1.demon.co.uk)
Received: from localhost (arg@localhost)
by arg1.demon.co.uk (8.8.8/8.8.8) with SMTP id BAA23727;
Tue, 26 Jan 1999 01:31:40 GMT
(envelope-from arg@arg1.demon.co.uk)
Date: Tue, 26 Jan 1999 01:31:39 +0000 (GMT)
From: Andrew Gordon <arg@arg1.demon.co.uk>
X-Sender: arg@server.arg.sj.co.uk
To: Matthew Dillon <dillon@apollo.backplane.com>
cc: current@FreeBSD.ORG
Subject: Re: 4.0-Current, netscape halts system
In-Reply-To: <199901252130.NAA07766@apollo.backplane.com>
Message-ID: <Pine.BSF.3.96.990126012634.23694A-100000@server.arg.sj.co.uk>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
On Mon, 25 Jan 1999, Matthew Dillon wrote:
> :One variable may be available memory. On my system, with default datasize
> :limit of 16M from login.conf, Netscape coredumps very frequently. With
>
> I've been using netscape on a 24bit color system for well over a year
> and have never had a serious memory leak problem or X session ( or
> machine ) crashing due to it. I don't leave the netscape window open
> all the time, though... I tend to exit out of it when I'm not using it.
>
> -Matt
> Matthew Dillon
> <dillon@backplane.com>
Just to clarify:
1) I'm not sure I would necesarily accuse Netscape of having a leak:
what with caching pages in RAM and the allocation policy of whatever
malloc they use, maybe it really needs this much and would stabilise
at some size of 100M+ - I just don't have the swap space to find out.
2) I have never seen a system crash as such. However, having the X server
killed due to out-of-swap leaves the console fouled up and so could
easily be mis-described as a crash.
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Mon Jan 25 17:35:39 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id RAA21505
for freebsd-current-outgoing; Mon, 25 Jan 1999 17:35:39 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA21488
for <current@FreeBSD.ORG>; Mon, 25 Jan 1999 17:35:32 -0800 (PST)
(envelope-from dillon@apollo.backplane.com)
Received: (from dillon@localhost)
by apollo.backplane.com (8.9.2/8.9.1) id RAA11762;
Mon, 25 Jan 1999 17:35:25 -0800 (PST)
(envelope-from dillon)
Date: Mon, 25 Jan 1999 17:35:25 -0800 (PST)
From: Matthew Dillon <dillon@apollo.backplane.com>
Message-Id: <199901260135.RAA11762@apollo.backplane.com>
To: Brian Feldman <green@unixhelp.org>
Cc: Sheldon Hearn <axl@iafrica.com>,
Lee Cremeans <lee@st-lcremean.tidalwave.net>, current@FreeBSD.ORG
Subject: Re: IDE DMA works, I'll be a...
References: <Pine.BSF.4.05.9901252016180.7918-100000@janus.syracuse.net>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
:> I would like to know if your transfer rate improves or not, and by
:> how much.
:>
:> #if 0
:> if (cnt.v_inactive_count / 3 > page_shortage) {
:> maxlaunder = 0;
:> launder_loop = 0;
:> } else
:> #endif
:> {
:> -Matt
:
:I'd rather use if (0 && cnt.v_inactive_count / 3 > page_shortage) {. I'm
:trying it out now, here's the "before":
:
:IOZONE performance measurements:
: 2972048 bytes/second for writing the file
: 2962863 bytes/second for reading the file
: Brian Feldman _ __ ___ ___ ___
Welll... I went ahead and tested it on my diskless workstation,
which actually has a DMA IDE drive connected to it at the moment
for another test I'm running.
I didn't see any change in performance. That doesn't meant that
hasn't been a chance, just that it doesn't look like the one thing
I thought might be causing it is causing it.
Are you sure the problem isn't simply that your disk is getting
a bit more full and causing the test to skip around more ( or move
to more inner tracks, which have lower transfer rates), and
thus appear to slow down a little ?
-Matt
Before ( iozone 64 on a 48MB machine )
IOZONE performance measurements:
7809031 bytes/second for writing the file
10324440 bytes/second for reading the file
IOZONE performance measurements:
8388608 bytes/second for writing the file
10324440 bytes/second for reading the file
After ( iozone 64 on a 48MB machine )
IOZONE performance measurements:
8103711 bytes/second for writing the file
10336864 bytes/second for reading the file
IOZONE performance measurements:
8429768 bytes/second for writing the file
10324440 bytes/second for reading the file
Matthew Dillon
<dillon@backplane.com>
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Mon Jan 25 17:47:56 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id RAA24019
for freebsd-current-outgoing; Mon, 25 Jan 1999 17:47:56 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from ayukawa.aus.org (ayukawa.aus.org [199.166.246.1])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA24010
for <current@FreeBSD.ORG>; Mon, 25 Jan 1999 17:47:53 -0800 (PST)
(envelope-from lh@aus.org)
Received: from zer0.net (lh@zer0.net [199.166.246.189]) by ayukawa.aus.org (8.8.7/8.7.3) with ESMTP id UAA07471; Mon, 25 Jan 1999 20:28:25 -0500 (EST)
Message-Id: <199901260128.UAA07471@ayukawa.aus.org>
X-Mailer: XFMail 1.3-beta-042198 [p0] on FreeBSD
X-Priority: 3 (Normal)
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 8bit
MIME-Version: 1.0
In-Reply-To: <66468.917294409@axl.noc.iafrica.com>
Date: Mon, 25 Jan 1999 20:47:29 -0500 (EST)
Reply-To: lh@aus.org
From: Luke <lh@aus.org>
To: Sheldon Hearn <axl@iafrica.com>
Subject: Re: 4.0-Current, netscape halts system
Cc: current@FreeBSD.ORG, "Jordan K. Hubbard" <jkh@zippy.cdrom.com>,
Andrew Gordon <arg@arg1.demon.co.uk>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
> Aha! That figures.
>
> Since I upgraded to CURRENT, with its login.conf which defaults to
> unlimited resources, my frequent netscape core dumps have gone away.
>
> I hadn't realized why until now.
>
> Suggestion: wwhen people complain about Netscape, ask them to mail us
> back the output of ``ulimit -a''.
>
My login.conf has unlimited for everything for myself and netscape still
crashes/locks up. And I have 64M/175swap so I dont think its running out of
memory.
---
E-Mail: Luke <lh@aus.org>
Sent by XFMail
----------------------------------
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Mon Jan 25 17:59:12 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id RAA26634
for freebsd-current-outgoing; Mon, 25 Jan 1999 17:59:12 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from darkstar.psa.at (darkstar.psa.at [194.152.163.137])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA26629
for <current@freebsd.org>; Mon, 25 Jan 1999 17:59:10 -0800 (PST)
(envelope-from entropy@compufit.at)
Received: from unet4-45.univie.ac.at ([131.130.233.45] helo=entropy.quake.at)
by darkstar.psa.at with esmtp (Exim 2.05 #1)
id 104xyM-0002fb-00
for current@freebsd.org; Tue, 26 Jan 1999 03:11:23 +0100
Received: from localhost ([127.0.0.1])
by entropy.quake.at with esmtp (Exim 2.05 #1)
id 104xkL-000O1v-00
for current@freebsd.org; Tue, 26 Jan 1999 02:56:53 +0100
Date: Tue, 26 Jan 1999 02:56:53 +0100 (CET)
From: Alexander Sanda <entropy@compufit.at>
X-Sender: root@darkstar.vmx
To: current@FreeBSD.ORG
Subject: PPP (userland) troubles ?
Message-ID: <Pine.BSF.4.05.9901260204010.24456-100000@darkstar.vmx>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
Hi!
I'am not sure where this comes from, but at the moment I have some
troubles with the userland ppp.
The symptoms: After establishing the connection and setting the
defaultroute *nothing* works, that means, the line seems
to be completely dead. Not even the peer can be pinged.
However, after a short while the symptoms vanish and
everything is as it should be. I don't believe in faults
at my provider, since I tested it with different accounts
and basically got the same results.
Sometimes when I try to ping the peer, I get some "sendto:
no buffer space available" messages before the reply
packets start to drop in.
Config: (very)-current, everything ELF, ppp via plain and simple modem
dialup.
--
# /AS/ http://privat.schlund.de/entropy/ #
# #
# XX has detected, that your mouse cursor has changed position. Please #
# restart XX, so it can be updated. -- From The Gimp manual #
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Mon Jan 25 18:02:32 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id SAA27329
for freebsd-current-outgoing; Mon, 25 Jan 1999 18:02:32 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from drama.navinet.net (drama.navinet.net [206.25.93.8])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA27314
for <current@freebsd.org>; Mon, 25 Jan 1999 18:02:30 -0800 (PST)
(envelope-from forrie@drama.navinet.net)
Received: (from forrie@localhost)
by drama.navinet.net (8.9.2/8.9.2) id VAA18980;
Mon, 25 Jan 1999 21:02:05 -0500 (EST)
Date: Mon, 25 Jan 1999 21:02:05 -0500
From: Forrest Aldrich <forrie@drama.navinet.net>
To: Luke <lh@aus.org>
Cc: current@FreeBSD.ORG
Subject: Re: 4.0-Current, netscape halts system
Message-ID: <19990125210205.A18967@drama.navinet.net>
References: <66468.917294409@axl.noc.iafrica.com> <199901260128.UAA07471@ayukawa.aus.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.95.1i
In-Reply-To: <199901260128.UAA07471@ayukawa.aus.org>; from Luke on Mon, Jan 25, 1999 at 08:47:29PM -0500
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
My setup is about the same. I just modified all my login.conf
defaults to be unlimited/infinity. Still the same crappy core dumps.
Forrest
On Mon, Jan 25, 1999 at 08:47:29PM -0500, Luke wrote:
> > Aha! That figures.
> >
> > Since I upgraded to CURRENT, with its login.conf which defaults to
> > unlimited resources, my frequent netscape core dumps have gone away.
> >
> > I hadn't realized why until now.
> >
> > Suggestion: wwhen people complain about Netscape, ask them to mail us
> > back the output of ``ulimit -a''.
> >
> My login.conf has unlimited for everything for myself and netscape still
> crashes/locks up. And I have 64M/175swap so I dont think its running out of
> memory.
> ---
>
> E-Mail: Luke <lh@aus.org>
> Sent by XFMail
> ----------------------------------
>
> To Unsubscribe: send mail to majordomo@FreeBSD.org
> with "unsubscribe freebsd-current" in the body of the message
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Mon Jan 25 18:07:48 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id SAA28287
for freebsd-current-outgoing; Mon, 25 Jan 1999 18:07:48 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from janus.syracuse.net (janus.syracuse.net [205.232.47.15])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA28233
for <current@FreeBSD.ORG>; Mon, 25 Jan 1999 18:07:39 -0800 (PST)
(envelope-from green@unixhelp.org)
Received: from localhost (green@localhost)
by janus.syracuse.net (8.8.8/8.8.7) with ESMTP id VAA12512;
Mon, 25 Jan 1999 21:07:16 -0500 (EST)
Date: Mon, 25 Jan 1999 21:07:15 -0500 (EST)
From: Brian Feldman <green@unixhelp.org>
X-Sender: green@janus.syracuse.net
To: Matthew Dillon <dillon@apollo.backplane.com>
cc: Sheldon Hearn <axl@iafrica.com>,
Lee Cremeans <lee@st-lcremean.tidalwave.net>, current@FreeBSD.ORG
Subject: Re: IDE DMA works, I'll be a...
In-Reply-To: <199901260135.RAA11762@apollo.backplane.com>
Message-ID: <Pine.BSF.4.05.9901252106160.12387-100000@janus.syracuse.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
On Mon, 25 Jan 1999, Matthew Dillon wrote:
> :> I would like to know if your transfer rate improves or not, and by
> :> how much.
> :>
> :> #if 0
> :> if (cnt.v_inactive_count / 3 > page_shortage) {
> :> maxlaunder = 0;
> :> launder_loop = 0;
> :> } else
> :> #endif
> :> {
> :> -Matt
> :
> :I'd rather use if (0 && cnt.v_inactive_count / 3 > page_shortage) {. I'm
> :trying it out now, here's the "before":
> :
> :IOZONE performance measurements:
> : 2972048 bytes/second for writing the file
> : 2962863 bytes/second for reading the file
> : Brian Feldman _ __ ___ ___ ___
>
> Welll... I went ahead and tested it on my diskless workstation,
> which actually has a DMA IDE drive connected to it at the moment
> for another test I'm running.
>
> I didn't see any change in performance. That doesn't meant that
> hasn't been a chance, just that it doesn't look like the one thing
> I thought might be causing it is causing it.
>
> Are you sure the problem isn't simply that your disk is getting
> a bit more full and causing the test to skip around more ( or move
> to more inner tracks, which have lower transfer rates), and
> thus appear to slow down a little ?
No, this REALLY isn't it. I have tons free on the test drive. iozone 100 on
a 64 mb system:
{"/home/green"}$ diff iozone.old iozone
15,16c15,16
< Writing the 100 Megabyte file, 'iozone.tmp'...37.320312 seconds
< Reading the file...37.710938 seconds
---
> Writing the 100 Megabyte file, 'iozone.tmp'...37.750000 seconds
> Reading the file...37.687500 seconds
19,20c19,20
< 2809665 bytes/second for writing the file
< 2780562 bytes/second for reading the file
---
> 2777684 bytes/second for writing the file
> 2782291 bytes/second for reading the file
>
> -Matt
>
> Before ( iozone 64 on a 48MB machine )
>
> IOZONE performance measurements:
> 7809031 bytes/second for writing the file
> 10324440 bytes/second for reading the file
>
> IOZONE performance measurements:
> 8388608 bytes/second for writing the file
> 10324440 bytes/second for reading the file
>
> After ( iozone 64 on a 48MB machine )
>
> IOZONE performance measurements:
> 8103711 bytes/second for writing the file
> 10336864 bytes/second for reading the file
>
> IOZONE performance measurements:
> 8429768 bytes/second for writing the file
> 10324440 bytes/second for reading the file
>
> Matthew Dillon
> <dillon@backplane.com>
>
Brian Feldman _ __ ___ ___ ___
green@unixhelp.org _ __ ___ | _ ) __| \
http://www.freebsd.org/ _ __ ___ ____ | _ \__ \ |) |
FreeBSD: The Power to Serve! _ __ ___ ____ _____ |___/___/___/
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Mon Jan 25 18:25:47 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id SAA01887
for freebsd-current-outgoing; Mon, 25 Jan 1999 18:25:47 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from janus.syracuse.net (janus.syracuse.net [205.232.47.15])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA01877
for <current@FreeBSD.ORG>; Mon, 25 Jan 1999 18:25:44 -0800 (PST)
(envelope-from green@unixhelp.org)
Received: from localhost (green@localhost)
by janus.syracuse.net (8.8.8/8.8.7) with ESMTP id VAA13533;
Mon, 25 Jan 1999 21:25:37 -0500 (EST)
Date: Mon, 25 Jan 1999 21:25:37 -0500 (EST)
From: Brian Feldman <green@unixhelp.org>
X-Sender: green@janus.syracuse.net
To: Matthew Dillon <dillon@apollo.backplane.com>
cc: Sheldon Hearn <axl@iafrica.com>,
Lee Cremeans <lee@st-lcremean.tidalwave.net>, current@FreeBSD.ORG
Subject: Re: IDE DMA works, I'll be a...
In-Reply-To: <Pine.BSF.4.05.9901252106160.12387-100000@janus.syracuse.net>
Message-ID: <Pine.BSF.4.05.9901252123110.13366-100000@janus.syracuse.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
And here's with Soren's (sorry, I don't have any kind of European keyboard
mapping) patch.
{"/home/green"}$ diff3 iozone.old iozone iozone.newer
====
1:15,16c
Writing the 100 Megabyte file, 'iozone.tmp'...37.320312 seconds
Reading the file...37.710938 seconds
2:15,16c
Writing the 100 Megabyte file, 'iozone.tmp'...37.750000 seconds
Reading the file...37.687500 seconds
3:15,16c
Writing the 100 Megabyte file, 'iozone.tmp'...39.187500 seconds
Reading the file...38.820312 seconds
====
1:19,20c
2809665 bytes/second for writing the file
2780562 bytes/second for reading the file
2:19,20c
2777684 bytes/second for writing the file
2782291 bytes/second for reading the file
3:19,20c
2675792 bytes/second for writing the file
2701101 bytes/second for reading the file
Brian Feldman _ __ ___ ___ ___
green@unixhelp.org _ __ ___ | _ ) __| \
http://www.freebsd.org/ _ __ ___ ____ | _ \__ \ |) |
FreeBSD: The Power to Serve! _ __ ___ ____ _____ |___/___/___/
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Mon Jan 25 18:29:15 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id SAA02557
for freebsd-current-outgoing; Mon, 25 Jan 1999 18:29:15 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from hillbilly.hayseed.net (dnai-207-181-249-194.dsl.dnai.com [207.181.249.194])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA02549
for <freebsd-current@FreeBSD.ORG>; Mon, 25 Jan 1999 18:29:12 -0800 (PST)
(envelope-from enkhyl@scient.com)
Received: from localhost (IDENT:root@localhost [127.0.0.1])
by hillbilly.hayseed.net (8.9.1/8.8.5) with ESMTP id SAA00502;
Mon, 25 Jan 1999 18:28:46 -0800
Date: Mon, 25 Jan 1999 18:28:42 -0800 (PST)
From: Christopher Nielsen <enkhyl@scient.com>
X-Sender: enkhyl@ender.sf.scient.com
Reply-To: Christopher Nielsen <cnielsen@pobox.com>
To: Alex Le Heux <alexlh@funk.org>
cc: freebsd-current@FreeBSD.ORG
Subject: Re: usb driver broken?
In-Reply-To: <36AD062E.EDF6A994@funk.org>
Message-ID: <Pine.BSF.4.05.9901251825200.303-100000@ender.sf.scient.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
On Tue, 26 Jan 1999, Alex Le Heux wrote:
> Am I the only one who gets this when he tries to compile a kernel with
> the usb drivers in it?
Nope. I ran into this same problem, but I haven't had a chance to query
the list about it. This is produced by having USB_DEBUG turned on in your
kernel config. UHCI_LEGSUP isn't defined anywhere in the usb code.
> cc -c -O -Wreturn-type -Wcomment -Wredundant-decls -Wimplicit
> -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes
> -Wpointer-arith -Winline -Wuninitialized -Wformat -Wunused
> -fformat-extensions -ansi -nostdinc -I- -I. -I../.. -I../../../include
> -DKERNEL -include opt_global.h -elf ../../dev/usb/uhci.c
> ../../dev/usb/uhci.c: In function `uhci_dumpregs':
> ../../dev/usb/uhci.c:406: `UHCI_LEGSUP' undeclared (first use this
> function)
> ../../dev/usb/uhci.c:406: (Each undeclared identifier is reported only
> once
> ../../dev/usb/uhci.c:406: for each function it appears in.)
> machine/cpufunc.h:284: warning: inlining failed in call to `inw'
> ../../dev/usb/uhci.c:406: warning: called from here
> *** Error code 1
>
> Stop.
--
Christopher Nielsen
Scient: The eBusiness Systems Innovator
<http://www.scient.com>
cnielsen@scient.com
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Mon Jan 25 18:43:28 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id SAA06024
for freebsd-current-outgoing; Mon, 25 Jan 1999 18:43:28 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA06001
for <current@freebsd.org>; Mon, 25 Jan 1999 18:43:23 -0800 (PST)
(envelope-from julian@whistle.com)
Received: (from daemon@localhost)
by alpo.whistle.com (8.8.5/8.8.5) id SAA00502
for <current@freebsd.org>; Mon, 25 Jan 1999 18:41:40 -0800 (PST)
Received: from current1.whistle.com(207.76.205.22)
via SMTP by alpo.whistle.com, id smtpdNIx497; Tue Jan 26 02:41:32 1999
Date: Mon, 25 Jan 1999 18:41:25 -0800 (PST)
From: Julian Elischer <julian@whistle.com>
To: current@FreeBSD.ORG
Subject: HEADS UP! (kernel thread support)
Message-ID: <Pine.BSF.3.95.990125183840.8019J-100000@current1.whistle.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
The Linuxthreads changes in the system that have been optioned out for a
while have been enabled after testing by many people.
this will require a recompile of at least PS and probably the usual
culprits, (libkvm etc) (unless of course you've already been running with
the support turned on.)
julian
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Mon Jan 25 19:01:42 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id TAA09065
for freebsd-current-outgoing; Mon, 25 Jan 1999 19:01:42 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from awfulhak.org (awfulhak.force9.co.uk [195.166.136.63])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA09042;
Mon, 25 Jan 1999 19:01:36 -0800 (PST)
(envelope-from brian@Awfulhak.org)
Received: from keep.lan.Awfulhak.org (brian@keep.lan.Awfulhak.org [172.16.0.8])
by awfulhak.org (8.8.8/8.8.8) with ESMTP id BAA28275;
Tue, 26 Jan 1999 01:52:23 GMT
(envelope-from brian@Awfulhak.org)
Received: from keep.lan.Awfulhak.org (brian@localhost [127.0.0.1])
by keep.lan.Awfulhak.org (8.9.2/8.9.2) with ESMTP id AAA08234;
Tue, 26 Jan 1999 00:24:06 GMT
(envelope-from brian@keep.lan.Awfulhak.org)
Message-Id: <199901260024.AAA08234@keep.lan.Awfulhak.org>
X-Mailer: exmh version 2.0.2 2/24/98
To: Julian Elischer <julian@whistle.com>
cc: Brian Somers <brian@Awfulhak.org>, Archie Cobbs <archie@whistle.com>,
arch@FreeBSD.ORG, current@FreeBSD.ORG
Subject: Re: DEVFS, the time has come...
In-reply-to: Your message of "Mon, 25 Jan 1999 10:37:42 PST."
<Pine.BSF.4.05.9901251035500.569-100000@s204m82.isp.whistle.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Tue, 26 Jan 1999 00:24:06 +0000
From: Brian Somers <brian@Awfulhak.org>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
> yo, brian,
> are you on 'net'?
>
> have you had a look at the netgraph stuff?
> particularly the kernel nodes that we use in conjuntion with mpd, and the
> usserland modules of mpd that we use with it?
Eh, dunno :-/ What's netgraph (it rings bells - have you mentioned
it before ?) ?
--
Brian <brian@Awfulhak.org> <brian@FreeBSD.org> <brian@OpenBSD.org>
<http://www.Awfulhak.org>
Don't _EVER_ lose your sense of humour !
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Mon Jan 25 19:03:30 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id TAA09317
for freebsd-current-outgoing; Mon, 25 Jan 1999 19:03:30 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA09306
for <current@freebsd.org>; Mon, 25 Jan 1999 19:03:29 -0800 (PST)
(envelope-from julian@whistle.com)
Received: (from daemon@localhost)
by alpo.whistle.com (8.8.5/8.8.5) id SAA00921
for <current@freebsd.org>; Mon, 25 Jan 1999 18:55:29 -0800 (PST)
Received: from current1.whistle.com(207.76.205.22)
via SMTP by alpo.whistle.com, id smtpdBYQ902; Tue Jan 26 02:55:21 1999
Date: Mon, 25 Jan 1999 18:55:15 -0800 (PST)
From: Julian Elischer <julian@whistle.com>
To: current@FreeBSD.ORG
Subject: Another heads-up (threads stack support)
Message-ID: <Pine.BSF.3.95.990125185054.8019K-100000@current1.whistle.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
This commit also requires a recompile of the usual cuplits.
Part of the reason for this commit is to make the thread-stack and non
thread stack cases be the same from the point of view of
non kernel programs. his allows the 'VM_STACK' option to be turned on and
off entirely vi kernel configurations and the userland to be left alone
(after this that is)
Testers on the ALPHA platform should contact "Richard Seaman, Jr."
<dick@tar.com>
to help test the alpha version of these changes. If they are ok then this
option can be made standard, allowing Pthreads stacks to be dynamic
in the same way that linuxthreads are..
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Mon Jan 25 19:08:45 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id TAA10227
for freebsd-current-outgoing; Mon, 25 Jan 1999 19:08:45 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from whizzo.transsys.com (whizzo.TransSys.COM [144.202.42.10])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA10195
for <freebsd-current@FreeBSD.ORG>; Mon, 25 Jan 1999 19:08:42 -0800 (PST)
(envelope-from louie@whizzo.transsys.com)
Received: from whizzo.transsys.com (localhost.transsys.com [127.0.0.1])
by whizzo.transsys.com (8.9.2/8.9.1) with ESMTP id WAA12765;
Mon, 25 Jan 1999 22:08:25 -0500 (EST)
(envelope-from louie@whizzo.transsys.com)
Message-Id: <199901260308.WAA12765@whizzo.transsys.com>
X-Mailer: exmh version 2.0.2 2/24/98
To: Alex Le Heux <alexlh@funk.org>
cc: freebsd-current@FreeBSD.ORG
From: "Louis A. Mamakos" <louie@TransSys.COM>
Subject: Re: usb driver broken?
References: <36AD062E.EDF6A994@funk.org>
In-reply-to: Your message of "Tue, 26 Jan 1999 01:02:54 +0100."
<36AD062E.EDF6A994@funk.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Mon, 25 Jan 1999 22:08:25 -0500
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
I had this problem too. It seems that the code included when you
define USB_DEBUG has suffered some bitrot. Drop this out of your
kernel config, and these compile time errors will go away.
louie
> Hi,
>
> Am I the only one who gets this when he tries to compile a kernel with
> the usb drivers in it?
>
>
> cc -c -O -Wreturn-type -Wcomment -Wredundant-decls -Wimplicit
> -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes
> -Wpointer-arith -Winline -Wuninitialized -Wformat -Wunused
> -fformat-extensions -ansi -nostdinc -I- -I. -I../.. -I../../../include
> -DKERNEL -include opt_global.h -elf ../../dev/usb/uhci.c
> ../../dev/usb/uhci.c: In function `uhci_dumpregs':
> ../../dev/usb/uhci.c:406: `UHCI_LEGSUP' undeclared (first use this
> function)
> ../../dev/usb/uhci.c:406: (Each undeclared identifier is reported only
> once
> ../../dev/usb/uhci.c:406: for each function it appears in.)
> machine/cpufunc.h:284: warning: inlining failed in call to `inw'
> ../../dev/usb/uhci.c:406: warning: called from here
> *** Error code 1
>
> Stop.
>
>
> Alex
>
> To Unsubscribe: send mail to majordomo@FreeBSD.org
> with "unsubscribe freebsd-current" in the body of the message
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Mon Jan 25 19:10:00 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id TAA10508
for freebsd-current-outgoing; Mon, 25 Jan 1999 19:10:00 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from pozo.pozo.com (pozo.pozo.com [207.201.8.18])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA10500
for <current@FreeBSD.ORG>; Mon, 25 Jan 1999 19:09:57 -0800 (PST)
(envelope-from mantar@netcom.com)
Received: from dual (DUAL [192.168.0.2])
by pozo.pozo.com (8.9.2/8.9.2) with SMTP id TAA14855;
Mon, 25 Jan 1999 19:09:38 -0800 (PST)
(envelope-from mantar@netcom.com)
Message-Id: <4.1.19990125190740.00a135f0@192.168.0.1>
X-Sender: null@192.168.0.1
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.1
Date: Mon, 25 Jan 1999 19:09:37 -0800
To: Julian Elischer <julian@whistle.com>, current@FreeBSD.ORG
From: Manfred Antar <mantar@netcom.com>
Subject: Re: HEADS UP! (kernel thread support)
In-Reply-To: <Pine.BSF.3.95.990125183840.8019J-100000@current1.whistle.c
om>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
At 06:41 PM 1/25/99 -0800, Julian Elischer wrote:
>The Linuxthreads changes in the system that have been optioned out for a
>while have been enabled after testing by many people.
>
>this will require a recompile of at least PS and probably the usual
>culprits, (libkvm etc) (unless of course you've already been running with
>the support turned on.)
>
>julian
>
Does this mean I can take -DCOMPAT_LINUX_THREADS out of /etc/make.conf ?
Thanks
Manfred
=====================
|| mantar@netcom.com ||
|| pozo@infinex.com ||
|| Ph. (415) 681-6235 ||
=====================
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Mon Jan 25 19:22:49 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id TAA13364
for freebsd-current-outgoing; Mon, 25 Jan 1999 19:22:49 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from outmail.utsunomiya-u.ac.jp (outmail.utsunomiya-u.ac.jp [160.12.196.3])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA13356
for <current@freebsd.org>; Mon, 25 Jan 1999 19:22:47 -0800 (PST)
(envelope-from yokota@zodiac.mech.utsunomiya-u.ac.jp)
Received: from zodiac.mech.utsunomiya-u.ac.jp (IDENT:LpXrY6z7jUwvuW125PTe7bZw6IGTFmeP@zodiac.mech.utsunomiya-u.ac.jp [160.12.42.1])
by outmail.utsunomiya-u.ac.jp (8.9.1/8.9.1) with ESMTP id MAA25448
for <current@freebsd.org>; Tue, 26 Jan 1999 12:22:43 +0900 (JST)
Received: from zodiac.mech.utsunomiya-u.ac.jp (zodiac.mech.utsunomiya-u.ac.jp [160.12.42.1]) by zodiac.mech.utsunomiya-u.ac.jp (8.7.6+2.6Wbeta7/3.4W/zodiac-May96) with ESMTP
id MAA16405; Tue, 26 Jan 1999 12:25:22 +0900 (JST)
Message-Id: <199901260325.MAA16405@zodiac.mech.utsunomiya-u.ac.jp>
To: current@FreeBSD.ORG
cc: yokota@zodiac.mech.utsunomiya-u.ac.jp
Subject: Re: keymaps
In-reply-to: Your message of "Fri, 22 Jan 1999 01:05:22 JST."
<199901211605.BAA24511@zodiac.mech.utsunomiya-u.ac.jp>
References: <199901211605.BAA24511@zodiac.mech.utsunomiya-u.ac.jp>
Date: Tue, 26 Jan 1999 12:25:21 +0900
From: Kazutaka YOKOTA <yokota@zodiac.mech.utsunomiya-u.ac.jp>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
>I recently looked at keymaps in /usr/share/syscons/keymaps and found
>many minor errors. In addition to that, there is so much
>inconsistency among existing keymaps. True that national keyboards have
>different layout of regular keys (alphanumeric keys and symbol keys).
>But, it is absurd that functions keys and special keys are handled in
>so many different ways.
[...]
>But, unless there is a good reason to make other exceptions, I will
>modify the other national keymaps to adapt these key assignments.
>
>Any comments? I am open to suggestions.
>
>Kazu
Ok, this is my second keymap proposal.
Kazu
* 101/102/104 Enhanced Keyboard support
Key Code Key Stroke Function
-----------------------------------------------------------------------------
1 Ctrl-Alt-Esc Enter DDB (debug).
57 Ctrl-Alt-Space Suspend (susp).
70 ScrollLock Backscroll (slock).
84 Alt-SysRq(PrintScreen) - (nop)
92 PrintScreen Switch to the next vty (nscr).
92 Ctrl-PrintScreen Enter DDB (debug).
104 Pause Backscroll (slock).
104 Shift-Pause Start screen saver (saver).
104 Alt-Pause Suspend (susp).
105 Left Windows fkey62
106 Right Windows fkey63
107 Menu fkey64
108 Ctrl-Break(Pause) - (nop)
The separate SysRq key doesn't exist on the enhanced keyboard. It is
combined with the PrintScreen key. The SysRq code is generated when
the Alt and the PrintScreen keys are pressed together.
The separate Break key doesn't exist on the enhanced keyboard. It is
combined with the Pause key. The Break code is generated when the
Ctrl and the Pause keys are pressed together.
The above assignments for the keycodes 1, 57, 70, 84 and 92 are
compatible with many, if not all, existing keymaps.
The base case for the keycode 104 is compatible with existing keymaps.
The keycode 108 is new.
Many keymaps lacks entries for 105 through 107.
* 84 Keyboard support
Key Code Key Stroke Function
-----------------------------------------------------------------------------
1 Ctrl-Alt-Esc Enter DDB (debug).
57 Ctrl-Alt-Space Suspend (susp).
70 ScrollLock Backscroll (slock).
84 SysRq - (nop)
92 Shift-PrintScreen(*) Switch to the next vty (nscr).
92 Shift-Ctrl-PrintScreen Enter DDB (debug).
104 Ctrl-Pause(NumLock) Backscroll (slock).
104 Shift-Ctrl-Alt-Pause(NumLock) Start screen saver (saver).
104 Ctrl-Alt-Pause(NumLock) Suspend (susp).
108 Ctrl-Break(ScrollLock) - (nop)
The separate PrintScreen key doesn't exist on the 84 keyboard. It is
combined with the numpad * key. The PrintScreen code is generated
when the Shift and the numpad * keys are pressed together.
The separate Pause key doesn't exist on the 84 keyboard. It is
combined with the NumLock key. The Pause code is generated when the
Ctrl and the NumlLock keys are pressed together.
The separate Break key doesn't exist on the 84 keyboard. It is
combined with the ScrollLock key. The Break code is generated when
the Ctrl and the ScrollLock keys are pressed together.
* Proposed keymap
Combining the support for the 84 keyboard and the enhanced keyboard
described above, we will get the following keymap entries.
alt
ctrl alt alt ctrl
code base shift ctrl shift alt shift ctrl shift
-----------------------------------------------------
1 esc esc esc esc esc esc debug esc
57 ' ' ' ' null ' ' ' ' ' ' susp ' '
70 slock slock slock slock slock slock slock slock
84 nop nop nop nop nop nop nop nop
92 nscr nscr debug debug nop nop nop nop
104 slock saver slock saver susp nop susp nop
105 fkey62fkey62fkey62fkey62fkey62fkey62fkey62fkey62
106 fkey63fkey63fkey63fkey63fkey63fkey63fkey63fkey63
107 fkey64fkey64fkey64fkey64fkey64fkey64fkey64fkey64
108 nop nop nop nop nop nop nop nop
* Summary of magic key sequences
101 keyboard 84 keyboard function
------------------------------------------------------------------------
Ctrl-Alt-Delete Ctrl-Alt-Delete reboot
Ctrl-Alt-Esc Ctrl-Alt-Esc debug
Ctrl-Alt-Space Ctrl-Alt-Space susp
ScrollLock ScrollLock slock
PrintScreen Shift-(Numpad *)/PrintScreen nscr
Ctrl-PrintScreen Shift-Ctrl-(Numpad *)/PrintScreen debug
Alt-PrintScreen/SysRq SysRq nop
Pause Ctrl-NumLock slock
Shift-Pause Shift-Ctrl-NumLock saver
Alt-Pause Alt-Ctrl-NumLock susp
Ctrl-Pause/Break Ctrl-ScrollLock/Break nop
<<EOF>>
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Mon Jan 25 19:23:39 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id TAA13476
for freebsd-current-outgoing; Mon, 25 Jan 1999 19:23:39 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA13469
for <current@FreeBSD.ORG>; Mon, 25 Jan 1999 19:23:38 -0800 (PST)
(envelope-from julian@whistle.com)
Received: (from daemon@localhost)
by alpo.whistle.com (8.8.5/8.8.5) id TAA01538;
Mon, 25 Jan 1999 19:19:54 -0800 (PST)
Received: from current1.whistle.com(207.76.205.22)
via SMTP by alpo.whistle.com, id smtpdOf1533; Tue Jan 26 03:19:49 1999
Date: Mon, 25 Jan 1999 19:19:46 -0800 (PST)
From: Julian Elischer <julian@whistle.com>
To: Manfred Antar <mantar@netcom.com>
cc: current@FreeBSD.ORG
Subject: Re: HEADS UP! (kernel thread support)
In-Reply-To: <4.1.19990125190740.00a135f0@192.168.0.1>
Message-ID: <Pine.BSF.3.95.990125191928.8019Q-100000@current1.whistle.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
yes
On Mon, 25 Jan 1999, Manfred Antar wrote:
> At 06:41 PM 1/25/99 -0800, Julian Elischer wrote:
> >The Linuxthreads changes in the system that have been optioned out for a
> >while have been enabled after testing by many people.
> >
> >this will require a recompile of at least PS and probably the usual
> >culprits, (libkvm etc) (unless of course you've already been running with
> >the support turned on.)
> >
> >julian
> >
> Does this mean I can take -DCOMPAT_LINUX_THREADS out of /etc/make.conf ?
>
> Thanks
> Manfred
> =====================
> || mantar@netcom.com ||
> || pozo@infinex.com ||
> || Ph. (415) 681-6235 ||
> =====================
>
>
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Mon Jan 25 19:53:42 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id TAA19513
for freebsd-current-outgoing; Mon, 25 Jan 1999 19:53:42 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from whistle.com (s205m131.whistle.com [207.76.205.131])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA19503;
Mon, 25 Jan 1999 19:53:40 -0800 (PST)
(envelope-from archie@whistle.com)
Received: (from smap@localhost) by whistle.com (8.7.5/8.6.12) id TAA20599; Mon, 25 Jan 1999 19:53:34 -0800 (PST)
Received: from bubba.whistle.com( 207.76.205.7) by whistle.com via smap (V2.0)
id xma020594; Mon, 25 Jan 99 19:53:16 -0800
Received: (from archie@localhost) by bubba.whistle.com (8.8.7/8.6.12) id TAA22716; Mon, 25 Jan 1999 19:53:16 -0800 (PST)
From: Archie Cobbs <archie@whistle.com>
Message-Id: <199901260353.TAA22716@bubba.whistle.com>
Subject: Re: DEVFS, the time has come...
In-Reply-To: <199901260024.AAA08234@keep.lan.Awfulhak.org> from Brian Somers at "Jan 26, 99 00:24:06 am"
To: brian@Awfulhak.org (Brian Somers)
Date: Mon, 25 Jan 1999 19:53:16 -0800 (PST)
Cc: julian@whistle.com, arch@FreeBSD.ORG, current@FreeBSD.ORG
X-Mailer: ELM [version 2.4ME+ PL38 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
Brian Somers writes:
> > yo, brian,
> > are you on 'net'?
> >
> > have you had a look at the netgraph stuff?
> > particularly the kernel nodes that we use in conjuntion with mpd, and the
> > usserland modules of mpd that we use with it?
>
> Eh, dunno :-/ What's netgraph (it rings bells - have you mentioned
> it before ?) ?
It was announced on freebsd-net .. beta version. Check out the
blurb on our new & improved web site! :-)
ftp://ftp.whistle.com/pub/archie/netgraph/index.html
-Archie
___________________________________________________________________________
Archie Cobbs * Whistle Communications, Inc. * http://www.whistle.com
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Mon Jan 25 20:52:10 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id UAA29029
for freebsd-current-outgoing; Mon, 25 Jan 1999 20:52:10 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from whistle.com (s205m131.whistle.com [207.76.205.131])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA29024
for <current@freebsd.org>; Mon, 25 Jan 1999 20:52:07 -0800 (PST)
(envelope-from archie@whistle.com)
Received: (from smap@localhost) by whistle.com (8.7.5/8.6.12) id UAA21369; Mon, 25 Jan 1999 20:51:35 -0800 (PST)
Received: from bubba.whistle.com( 207.76.205.7) by whistle.com via smap (V2.0)
id xma021367; Mon, 25 Jan 99 20:51:15 -0800
Received: (from archie@localhost) by bubba.whistle.com (8.8.7/8.6.12) id UAA23212; Mon, 25 Jan 1999 20:51:14 -0800 (PST)
From: Archie Cobbs <archie@whistle.com>
Message-Id: <199901260451.UAA23212@bubba.whistle.com>
Subject: Re: DEVFS, the time has come...
In-Reply-To: <36AC8477.EDE68A@altavista.net> from Maxim Sobolev at "Jan 25, 99 04:49:27 pm"
To: sobomax@altavista.net (Maxim Sobolev)
Date: Mon, 25 Jan 1999 20:51:14 -0800 (PST)
Cc: current@FreeBSD.ORG, julian@whistle.com (Julian Elischer)
X-Mailer: ELM [version 2.4ME+ PL38 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
Maxim Sobolev writes:
> Can you point all people (and me of course) who want to test DEVFS to some
> common information about DEVFS (usage, possible advantages/disadvantages etc.
> I think some FAQ or so will be nice. It's really will help us to go further
> with this issue.
I agree.. and I've bugged Julian to put something together...
Basically, there are a few things that need to be done to get DEVFS
into the 'mainstream'... and this includes SLICE.
The only thing that DEVFS doesn't completely work for right now is
disks, because the way disks are handled right now is all a bunch
of hardwired stuff. SLICE is intended to fix this problem, and in
the process make easy things like a compressed encrypted filesystem
striped across a 10 disk array.. :-)
So the things to do are:
1. Finish DEVFS-enabling the SCSI "da" disk driver.
2. Implement asynchronous device management in DEVFS (kernel thread)
This solves the problem of doing lengthy I/O during interrupts.
3. Fix the MFS problem -- hopefully Matt Dillon can help here
in the course of his ongoing cleanups & bug fixes.
4. Completely rewrite libdisk to use and understand SLICE.
(This might actually be a kharmically refreshing experience).
5. Update the installer code to work with the new libdisk
OR write a "compatibility layer" that implements the old
libdisk API on top of the new libdisk.
6. No change to fdisk(8); minor change to disklabel(8).
I'm willing to take a look at the libdisk issue.. in which case
a few helpful pointers from anyone who knows would be nice:
- What other code beside the installer (if any) uses libdisk?
- What are the relevant installer files in the source tree?
-Archie
___________________________________________________________________________
Archie Cobbs * Whistle Communications, Inc. * http://www.whistle.com
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Mon Jan 25 21:01:44 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id VAA00573
for freebsd-current-outgoing; Mon, 25 Jan 1999 21:01:44 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA00561
for <current@FreeBSD.ORG>; Mon, 25 Jan 1999 21:01:42 -0800 (PST)
(envelope-from jkh@zippy.cdrom.com)
Received: from zippy.cdrom.com (localhost.cdrom.com [127.0.0.1])
by zippy.cdrom.com (8.9.2/8.9.1) with ESMTP id VAA89211;
Mon, 25 Jan 1999 21:01:35 -0800 (PST)
To: Archie Cobbs <archie@whistle.com>
cc: sobomax@altavista.net (Maxim Sobolev), current@FreeBSD.ORG,
julian@whistle.com (Julian Elischer)
Subject: Re: DEVFS, the time has come...
In-reply-to: Your message of "Mon, 25 Jan 1999 20:51:14 PST."
<199901260451.UAA23212@bubba.whistle.com>
Date: Mon, 25 Jan 1999 21:01:35 -0800
Message-ID: <89208.917326895@zippy.cdrom.com>
From: "Jordan K. Hubbard" <jkh@zippy.cdrom.com>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
> - What other code beside the installer (if any) uses libdisk?
Nothing does. That probably says something in and of itself. :)
> - What are the relevant installer files in the source tree?
/usr/src/release/sysinstall.
- Jordan
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Mon Jan 25 21:13:01 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id VAA02229
for freebsd-current-outgoing; Mon, 25 Jan 1999 21:13:01 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from jli.com (jli.com [199.2.111.1])
by hub.freebsd.org (8.8.8/8.8.8) with SMTP id VAA02223
for <current@freebsd.org>; Mon, 25 Jan 1999 21:12:59 -0800 (PST)
(envelope-from trost@cloud.rain.com)
Received: (qmail 23264 invoked by uid 4); 26 Jan 1999 05:12:58 -0000
Received: (qmail 15513 invoked from network); 26 Jan 1999 05:09:35 -0000
Received: from localhost.cloud.rain.com (HELO grey.cloud.rain.com) (127.0.0.1)
by localhost.cloud.rain.com with SMTP; 26 Jan 1999 05:09:35 -0000
To: current@FreeBSD.ORG
Subject: Re: beginnings of a diskless boot sequence being committed
References: <199901251604.RAA27194@labinfo.iet.unipi.it>
In-reply-to: Your message of Mon, 25 Jan 1999 17:04:14 +0100.
<199901251604.RAA27194@labinfo.iet.unipi.it>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <15509.917327374.1@grey.cloud.rain.com>
Date: Mon, 25 Jan 1999 21:09:34 -0800
Message-ID: <15510.917327374@grey.cloud.rain.com>
From: Bill Trost <trost@cloud.rain.com>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
Luigi Rizzo writes:
> :I haven't seen how you suggest to build&populate the MFS filesystems --
...
> There isn't much to build. Most of the MFS filesystems start
> out empty.
ok here we use a different approach. For simplicity I am using a
single MFS system with all the things you put in /var, and including
/var/dev and /var/etc (with /dev -> /var/dev and /etc -> /var/etc on
the diskless machine).
I have a wacky idea in this vein that I want to pursue sometime --
instead of pushing off lots of symlinks for the various writable
portions of the read-only root directory (which strikes as a bit odd in
itself), I was considering union-mounting an MFS filesystem directly
over the read-only root partition. The advantage of this approach
is that you do not have to know ahead of time what portions of the
read-only partition need to be writable -- files get copied into the MFS
partition only if and when they are written to.
Thoughts? It seems like it would be feasible, and it might even be
possible to do it directly in /etc/fstab without having to put any sort
of cleverness in /etc/rc.
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Mon Jan 25 21:18:34 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id VAA02740
for freebsd-current-outgoing; Mon, 25 Jan 1999 21:18:34 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from lab321.ru (anonymous1.omsk.net.ru [62.76.128.34])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA02636
for <current@freebsd.org>; Mon, 25 Jan 1999 21:17:06 -0800 (PST)
(envelope-from kev@lab321.ru)
Received: (from kev@localhost)
by lab321.ru (8.8.8/8.9.1a) id LAA20058;
Tue, 26 Jan 1999 11:16:47 +0600 (OS)
Date: Tue, 26 Jan 1999 11:16:47 +0600 (OS)
From: Eugeny Kuzakov <kev@lab321.ru>
Message-Id: <199901260516.LAA20058@lab321.ru>
To: Archie Cobbs <archie@whistle.com>, current@FreeBSD.ORG
Subject: Re: 4.0-Current, netscape halts system
X-Newsgroups: local.maillist.FreeBSD.freebsd-current
In-Reply-To: <199901251923.LAA01882@bubba.whistle.com>
Organization: Powered by FreeBSD 4.0-CURRENT.
MIME-Version: 1.0
Content-Type: text/plain; charset=koi8-r
Content-Transfer-Encoding: 8bit
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
÷Ù ÐÉÓÁÌÉ:
> Nate Williams writes:
>> > I am current as of today 4.0, I have communicator 4.5 downloaded some time
>> > ago (November more or less) directly from netscape and installed in
>> > /usr/local/netscape with a link to /usr/local/bin/netscape and I have been
>> > using it all day with no problems. My intranet if full of java and haven't
>> > had a problem, knock on wood:-) I just downloaded a 9M file after reading
>> > your mail to see if that would cause a problem and it didn't. Netscape is
>> > "as stable as ever" on FreeBSD Current 4.0 for me. That bothers me:-) I
>> > wonder why?
>> I'm running 2.2-stable, so maybe that's a difference.
> Me too... (I get crashes running Java)
And me too..
Now netscape(with java too...) works for me, but after disabling splash...
I can not understand it...
I cvsuped&rebuilded system at 25-jan-1999..
--
Best wishes, Eugeny
http://coredumped.null.ru
CoreDumped@CoreDumped.null.ru
ICQ#: 5885106
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Mon Jan 25 22:37:58 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id WAA13149
for freebsd-current-outgoing; Mon, 25 Jan 1999 22:37:58 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from smtp02.wxs.nl (smtp02.wxs.nl [195.121.6.60])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA13138
for <current@FreeBSD.ORG>; Mon, 25 Jan 1999 22:37:54 -0800 (PST)
(envelope-from asmodai@wxs.nl)
Received: from daemon.ninth-circle.org ([195.121.57.77]) by smtp02.wxs.nl
(Netscape Messaging Server 3.6) with ESMTP id AAAAA8;
Tue, 26 Jan 1999 07:37:53 +0100
Message-ID: <XFMail.990126074618.asmodai@wxs.nl>
X-Mailer: XFMail 1.3 [p0] on FreeBSD
X-Priority: 3 (Normal)
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 8bit
MIME-Version: 1.0
In-Reply-To: <Pine.BSF.3.96.990126012634.23694A-100000@server.arg.sj.co.uk>
Date: Tue, 26 Jan 1999 07:46:18 +0100 (CET)
Organization: Ninth Circle Enterprises
From: Jeroen Ruigrok/Asmodai <asmodai@wxs.nl>
To: Andrew Gordon <arg@arg1.demon.co.uk>
Subject: Re: 4.0-Current, netscape halts system
Cc: current@FreeBSD.ORG, Matthew Dillon <dillon@apollo.backplane.com>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
On 26-Jan-99 Andrew Gordon wrote:
> On Mon, 25 Jan 1999, Matthew Dillon wrote:
>> :One variable may be available memory. On my system, with default
>> :datasize
>> :limit of 16M from login.conf, Netscape coredumps very frequently. With
>>
>> I've been using netscape on a 24bit color system for well over a
>> year and have never had a serious memory leak problem or X
>> session ( or machine ) crashing due to it. I don't leave the
>> netscape window open all the time, though... I tend to exit
>> out of it when I'm not using it.
This would indicate that it might have to do then with prolonged exposure
to memory and the memory-system(s) (swap, paging). Is there anyway to
monitor the syscalls and the amount of memory used and released by each
call Matt? Hope ye see where I'm getting at...
> 1) I'm not sure I would necesarily accuse Netscape of having a leak:
> what with caching pages in RAM and the allocation policy of whatever
> malloc they use, maybe it really needs this much and would stabilise
> at some size of 100M+ - I just don't have the swap space to find out.
Yer kidding right? A program that _needs_ 100 MB or more? Surely yer
kidding... I haven't seen a program in normal corporate/home use that
justifies the memory usage of 100 MB or more including NetScape's
Navigator/Communicator.
> 2) I have never seen a system crash as such. However, having the X
> server killed due to out-of-swap leaves the console fouled up and so
> could easily be mis-described as a crash.
I wonder if X could be the originator of the problems, my guess is it can't
since Linux uses the same X and I haven't heard any complaints from that
corner.
Also it's nice that the program dumps core, but afaik without debug symbols
it's not much use.
---
Jeroen Ruigrok van der Werven It's a Dance of Energy,
asmodai(at)wxs.nl when the Mind goes Binary...
Network/Security Specialist <http://home.wxs.nl/~asmodai>
BSD & picoBSD: The Power to Serve <http://www.freebsd.org>
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Mon Jan 25 22:43:14 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id WAA13741
for freebsd-current-outgoing; Mon, 25 Jan 1999 22:43:14 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from rip.psg.com (rip.psg.com [147.28.0.39])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA13733
for <freebsd-current@freebsd.org>; Mon, 25 Jan 1999 22:43:10 -0800 (PST)
(envelope-from randy@psg.com)
Received: from localhost (658 bytes) by rip.psg.com
via sendmail with P:stdio/R:inet_resolve/T:smtp
(sender: <randy>) (ident <randy> using unix)
id <m1052DN-0008G4C@rip.psg.com>
for <freebsd-current@freebsd.org>; Mon, 25 Jan 1999 22:43:09 -0800 (PST)
(Smail-3.2.0.101 1997-Dec-17 #1 built 1998-Oct-13)
Message-Id: <m1052DN-0008G4C@rip.psg.com>
Date: Mon, 25 Jan 1999 22:43:09 -0800 (PST)
From: Randy Bush <randy@psg.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
To: freebsd-current@FreeBSD.ORG
Subject: cvsup build failure
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
4.0-current as of today.
i am trying to make cvsup and blooie!
new source -> compiling ../src/TreeComp.m3
new source -> compiling ../src/FSServer.m3
new source -> compiling ../src/FSServerU.m3
new source -> compiling ../src/Main.m3
-> linking cvsupd
/usr/lib/aout/crt0.o: file not recognized: File format not recognized
is it to do with having NOAOUT in /etc/make.conf?
randy
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Mon Jan 25 23:35:01 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id XAA20502
for freebsd-current-outgoing; Mon, 25 Jan 1999 23:35:01 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from mail11.digital.com (mail11.digital.com [192.208.46.10])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA20481
for <current@freebsd.org>; Mon, 25 Jan 1999 23:34:59 -0800 (PST)
(envelope-from perry@zso.dec.com)
Received: from yakko.zso.dec.com (yakko.zso.dec.com [16.64.16.191])
by mail11.digital.com (8.9.1a/8.9.1/WV2.0c) with ESMTP id CAA07811;
Tue, 26 Jan 1999 02:36:05 -0500 (EST)
Received: from localhost (perry@localhost)
by yakko.zso.dec.com (8.9.1/8.9.1) with SMTP id XAA28740;
Mon, 25 Jan 1999 23:34:33 -0800 (PST)
Message-Id: <199901260734.XAA28740@yakko.zso.dec.com>
X-Authentication-Warning: yakko.zso.dec.com: perry@localhost didn't use HELO protocol
To: Jeroen Ruigrok/Asmodai <asmodai@wxs.nl>
cc: Andrew Gordon <arg@arg1.demon.co.uk>, current@FreeBSD.ORG,
Matthew Dillon <dillon@apollo.backplane.com>
Reply-To: perry@zso.dec.com
Subject: Re: 4.0-Current, netscape halts system
In-reply-to: Message from Jeroen Ruigrok/Asmodai <asmodai@wxs.nl>
of "Tue, 26 Jan 1999 07:46:18 +0100." <XFMail.990126074618.asmodai@wxs.nl>
Mime-Version: 1.0 (generated by tm-edit 7.108)
Content-Type: text/plain; charset=US-ASCII
Date: Mon, 25 Jan 1999 23:34:32 -0800
From: "Reginald S. Perry" <perry@zso.dec.com>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
I have been having these X lockups with the linux netscape 4.5
running. I may have exacerbated it when I installed the linux
realplayer and macromedia flash plugins.
I would like to have a methodology to help debug this, but I have just
this one system to use as the debug system. I do also have a vt220
which I could set up if that would help.
The key here is that for me it locks the system up completely. I
cannot telnet in remotely and the ctrl-alt-esc key sequence does not
work so its unclear to me how to debug this. Tell me what I would need
to help debug it, and I will try to be of some help. Ill attach my
dmesg output.
-Reggie
Copyright (c) 1992-1999 FreeBSD Inc.
Copyright (c) 1982, 1986, 1989, 1991, 1993
The Regents of the University of California. All rights reserved.
FreeBSD 3.0-CURRENT #0: Sun Jan 17 09:52:17 PST 1999
root@trane.lambdawerks.org:/usr/src/sys/compile/TRANE
Timecounter "i8254" frequency 1193182 Hz
CPU: Pentium/P55C (586-class CPU)
Origin = "GenuineIntel" Id = 0x543 Stepping=3
Features=0x8003bf<FPU,VME,DE,PSE,TSC,MSR,MCE,CX8,APIC,MMX>
real memory = 134217728 (131072K bytes)
config> pnp 1 0 os enable irq0 5 drq0 1 drq1 5 port0 0x220 port1 0x330 port2 0x388
config> pnp 1 1 os disable
config> pnp 1 2 os enable port0 0x620 port1 0xa20 port2 0xe20
config> pnp 1 3 os disable
config> quit
avail memory = 127401984 (124416K bytes)
Programming 24 pins in IOAPIC #0
FreeBSD/SMP: Multiprocessor motherboard
cpu0 (BSP): apic id: 0, version: 0x00030010, at 0xfee00000
cpu1 (AP): apic id: 1, version: 0x00030010, at 0xfee00000
io0 (APIC): apic id: 2, version: 0x00170011, at 0xfec00000
Preloaded elf kernel "kernel" at 0xf02f3000.
Preloaded userconfig_script "/kernel.config" at 0xf02f309c.
Probing for devices on PCI bus 0:
chip0: <Intel 82439> rev 0x03 on pci0.0.0
chip1: <Intel 82371SB PCI to ISA bridge> rev 0x01 on pci0.7.0
ide_pci0: <Intel PIIX3 Bus-master IDE controller> rev 0x00 on pci0.7.1
vga0: <Matrox MGA 2164W graphics accelerator> rev 0x00 int a irq 18 on pci0.18.0
bt0: <Buslogic Multi-Master SCSI Host Adapter> rev 0x08 int a irq 17 on pci0.19.0
bt0: BT-958 FW Rev. 5.06I Ultra Wide SCSI Host Adapter, SCSI ID 7, 192 CCBs
fxp0: <Intel EtherExpress Pro 10/100B Ethernet> rev 0x02 int a irq 16 on pci0.20.0
fxp0: Ethernet address 00:a0:c9:90:bb:52
Probing for PnP devices:
CSN 1 Vendor ID: CTL009e [0x9e008c0e] Serial 0x0d9191f1 Comp ID: PNPb02f [0x2fb0d041]
Probing for devices on the ISA bus:
sc0 on isa
sc0: VGA color <16 virtual consoles, flags=0x0>
atkbdc0 at 0x60-0x6f on motherboard
atkbd0 irq 1 on isa
psm0 irq 12 on isa
psm0: model GlidePoint, device ID 0
sio0 at 0x3f8-0x3ff irq 4 flags 0x10 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: FIFO enabled, 8 bytes threshold
fd0: 1.44MB 3.5in
wdc0 not found at 0x1f0
wdc1 not found at 0x170
bt: unit number (1) too high
bt1 not found at 0x330
vga0 at 0x3b0-0x3df maddr 0xa0000 msize 131072 on isa
npx0 on motherboard
npx0: INT 16 interface
sb0 at 0x220 irq 5 drq 1 on isa
snd0: <SoundBlaster 16 4.16>
sbxvi0 at drq 5 on isa
snd0: <SoundBlaster 16 4.16>
sbmidi0 at 0x330 on isa
snd0: <SoundBlaster MPU-401>
opl0 at 0x388 on isa
snd0: <Yamaha OPL3 FM>
awe0 at 0x620 on isa
awe0: <SoundBlaster EMU8000 MIDI (RAM4096k)>
Intel Pentium detected, installing workaround for F00F bug
APIC_IO: Testing 8254 interrupt delivery
APIC_IO: routing 8254 via pin 2
Waiting 2 seconds for SCSI devices to settle
SMP: AP CPU #1 Launched!
sa0 at bt0 bus 0 target 5 lun 0
sa0: <HP C1533A 9608> Removable Sequential Access SCSI-2 device
sa0: 10.0MB/s transfers (10.0MHz, offset 8)
da0 at bt0 bus 0 target 0 lun 0
da0: <IBM DCAS-34330W !# S65A> Fixed Direct Access SCSI-2 device
da0: 40.0MB/s transfers (20.0MHz, offset 15, 16bit), Tagged Queueing Enabled
da0: 4134MB (8467200 512 byte sectors: 255H 63S/T 527C)
da1 at bt0 bus 0 target 4 lun 0
da1: <IBM DCAS-34330W !# S65A> Fixed Direct Access SCSI-2 device
da1: 40.0MB/s transfers (20.0MHz, offset 15, 16bit), Tagged Queueing Enabled
da1: 4134MB (8467200 512 byte sectors: 255H 63S/T 527C)
changing root device to da0s1a
WARNING: / was not properly dismounted
vinum: loaded
cd0 at bt0 bus 0 target 1 lun 0
cd0: <TOSHIBA CD-ROM XM-5701TA 0167> Removable CD-ROM SCSI-2 device
cd0: 10.0MB/s transfers (10.0MHz, offset 8)
cd0: cd present [296322 x 2048 byte records]
ffs_mountfs: superblock updated for soft updates
ffs_mountfs: superblock updated for soft updates
ffs_mountfs: superblock updated for soft updates
ffs_mountfs: superblock updated for soft updates
ffs_mountfs: superblock updated for soft updates
ffs_mountfs: superblock updated for soft updates
ffs_mountfs: superblock updated for soft updates
ffs_mountfs: superblock updated for soft updates
>"Asmodai" == Asmodai <Jeroen> writes:
> On 26-Jan-99 Andrew Gordon wrote: On Mon, 25 Jan 1999, Matthew
> Dillon wrote:
>> :One variable may be available memory. On my system, with default
>> :datasize
>> :limit of 16M from login.conf, Netscape coredumps very frequently.
> With
>>
>> I've been using netscape on a 24bit color system for well over a
>> year and have never had a serious memory leak problem or X
>> session ( or machine ) crashing due to it. I don't leave the
>> netscape window open all the time, though... I tend to exit
>> out of it when I'm not using it.
> This would indicate that it might have to do then with prolonged
> exposure to memory and the memory-system(s) (swap, paging). Is there
> anyway to monitor the syscalls and the amount of memory used and
> released by each call Matt? Hope ye see where I'm getting at...
> 1) I'm not sure I would necesarily accuse Netscape of having a leak:
> what with caching pages in RAM and the allocation policy of whatever
> malloc they use, maybe it really needs this much and would stabilise
> at some size of 100M+ - I just don't have the swap space to find out.
> Yer kidding right? A program that _needs_ 100 MB or more? Surely yer
> kidding... I haven't seen a program in normal corporate/home use
> that justifies the memory usage of 100 MB or more including
> NetScape's Navigator/Communicator.
> 2) I have never seen a system crash as such. However, having the X
> server killed due to out-of-swap leaves the console fouled up and so
> could easily be mis-described as a crash.
> I wonder if X could be the originator of the problems, my guess is
> it can't since Linux uses the same X and I haven't heard any
> complaints from that corner.
> Also it's nice that the program dumps core, but afaik without debug
> symbols it's not much use.
> --- Jeroen Ruigrok van der Werven It's a Dance of Energy,
> asmodai(at)wxs.nl when the Mind goes Binary... Network/Security
> Specialist <http://home.wxs.nl/~asmodai> BSD & picoBSD: The Power to
> Serve <http://www.freebsd.org>
> To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe
> freebsd-current" in the body of the message
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Tue Jan 26 00:03:31 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id AAA23833
for freebsd-current-outgoing; Tue, 26 Jan 1999 00:03:31 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from bright.fx.genx.net (bright.fx.genx.net [206.64.4.154])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA23826
for <current@FreeBSD.ORG>; Tue, 26 Jan 1999 00:03:28 -0800 (PST)
(envelope-from bright@hotjobs.com)
Received: from localhost (bright@localhost)
by bright.fx.genx.net (8.9.1/8.9.1) with ESMTP id DAA76712;
Tue, 26 Jan 1999 03:07:33 -0500 (EST)
(envelope-from bright@hotjobs.com)
X-Authentication-Warning: bright.fx.genx.net: bright owned process doing -bs
Date: Tue, 26 Jan 1999 03:07:33 -0500 (EST)
From: Alfred Perlstein <bright@hotjobs.com>
X-Sender: bright@bright.fx.genx.net
To: "Reginald S. Perry" <perry@zso.dec.com>
cc: Jeroen Ruigrok/Asmodai <asmodai@wxs.nl>,
Andrew Gordon <arg@arg1.demon.co.uk>, current@FreeBSD.ORG,
Matthew Dillon <dillon@apollo.backplane.com>
Subject: Re: 4.0-Current, netscape halts system
In-Reply-To: <199901260734.XAA28740@yakko.zso.dec.com>
Message-ID: <Pine.BSF.4.05.9901260259530.55154-100000@bright.fx.genx.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
On Mon, 25 Jan 1999, Reginald S. Perry wrote:
> I have been having these X lockups with the linux netscape 4.5
> running. I may have exacerbated it when I installed the linux
> realplayer and macromedia flash plugins.
>
> I would like to have a methodology to help debug this, but I have just
> this one system to use as the debug system. I do also have a vt220
> which I could set up if that would help.
>
> The key here is that for me it locks the system up completely. I
> cannot telnet in remotely and the ctrl-alt-esc key sequence does not
> work so its unclear to me how to debug this. Tell me what I would need
> to help debug it, and I will try to be of some help. Ill attach my
> dmesg output.
>
> -Reggie
>
options DDB
options BREAK_TO_DEBUGGER #a BREAK on a comconsole goes to
options INVARIANTS
options INVARIANT_SUPPORT
device sio0 at isa? port "IO_COM1" tty irq 4 vector siointr
device sio1 at isa? port "IO_COM2" flags 0x30 tty irq 3 vector siointr
my 'sio2' is setup with special flags to make it always be the consol.
look in lint for more hints.
when the machine locks:
send a break:
if on vt220: F5
using tip/cu: ~%
take a look at 'ps' and copy it down to see what's up.
you may also want to enable crash dumps, look in rc.conf and set
your 'dumpdevice' to your swap partition. then you can type 'panic'
and get a core image of the system to look at.
on the next reboot you can 'kdb' the kernel and then type 'bt' to
get a backtrace.
i have a vt320 for vanity purposes :), but i suggest you use a
serial line into an xterm on another box if you can, ddb isn't the
nicest interface and being able to cut and paste in and out of ddb
in an xterm is nice.
-Alfred
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Tue Jan 26 00:15:43 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id AAA25278
for freebsd-current-outgoing; Tue, 26 Jan 1999 00:15:43 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA25273
for <current@FreeBSD.ORG>; Tue, 26 Jan 1999 00:15:40 -0800 (PST)
(envelope-from phk@critter.freebsd.dk)
Received: from critter.freebsd.dk (localhost [127.0.0.1])
by critter.freebsd.dk (8.9.1/8.8.5) with ESMTP id JAA24711;
Tue, 26 Jan 1999 09:14:36 +0100 (CET)
To: Archie Cobbs <archie@whistle.com>
cc: sobomax@altavista.net (Maxim Sobolev), current@FreeBSD.ORG,
julian@whistle.com (Julian Elischer)
Subject: Re: DEVFS, the time has come...
In-reply-to: Your message of "Mon, 25 Jan 1999 20:51:14 PST."
<199901260451.UAA23212@bubba.whistle.com>
Date: Tue, 26 Jan 1999 09:14:36 +0100
Message-ID: <24709.917338476@critter.freebsd.dk>
From: Poul-Henning Kamp <phk@critter.freebsd.dk>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
In message <199901260451.UAA23212@bubba.whistle.com>, Archie Cobbs writes:
>Maxim Sobolev writes:
>> Can you point all people (and me of course) who want to test DEVFS to some
>> common information about DEVFS (usage, possible advantages/disadvantages etc.
>> I think some FAQ or so will be nice. It's really will help us to go further
>> with this issue.
>
>I agree.. and I've bugged Julian to put something together...
>
>Basically, there are a few things that need to be done to get DEVFS
>into the 'mainstream'... and this includes SLICE.
No, it doesn't have to be SLICE. In particular, if we're going the
SLICE way, it should be done >right<, and Julians SLICE code didn't
do that. (I know, I spent close to 6 months prototyping the concept
and julian had my code to work from).
--
Poul-Henning Kamp FreeBSD coreteam member
phk@FreeBSD.ORG "Real hackers run -current on their laptop."
FreeBSD -- It will take a long time before progress goes too far!
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Tue Jan 26 00:22:26 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id AAA26228
for freebsd-current-outgoing; Tue, 26 Jan 1999 00:22:26 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA26216
for <current@FreeBSD.ORG>; Tue, 26 Jan 1999 00:22:24 -0800 (PST)
(envelope-from dillon@apollo.backplane.com)
Received: (from dillon@localhost)
by apollo.backplane.com (8.9.2/8.9.1) id AAA14526;
Tue, 26 Jan 1999 00:22:17 -0800 (PST)
(envelope-from dillon)
Date: Tue, 26 Jan 1999 00:22:17 -0800 (PST)
From: Matthew Dillon <dillon@apollo.backplane.com>
Message-Id: <199901260822.AAA14526@apollo.backplane.com>
To: Bill Trost <trost@cloud.rain.com>
Cc: current@FreeBSD.ORG
Subject: Re: beginnings of a diskless boot sequence being committed
References: <199901251604.RAA27194@labinfo.iet.unipi.it> <15510.917327374@grey.cloud.rain.com>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
:...
:portions of the read-only root directory (which strikes as a bit odd in
:itself), I was considering union-mounting an MFS filesystem directly
:over the read-only root partition. The advantage of this approach
It isn't a bad idea, but I dunno how stable the union filesystem is.
I prefer to be told when I'm not supposed to write somewhere, though :-)
I like keeping things formally read-only if that is what they essentially
are.
If all else fails, perhaps use of union will allow overriding /etc.
Hmmm.
:is that you do not have to know ahead of time what portions of the
:read-only partition need to be writable -- files get copied into the MFS
:partition only if and when they are written to.
:
:Thoughts? It seems like it would be feasible, and it might even be
:possible to do it directly in /etc/fstab without having to put any sort
:of cleverness in /etc/rc.
-Matt
Matthew Dillon
<dillon@backplane.com>
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Tue Jan 26 01:13:53 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id BAA02199
for freebsd-current-outgoing; Tue, 26 Jan 1999 01:13:53 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA02192
for <current@freebsd.org>; Tue, 26 Jan 1999 01:13:52 -0800 (PST)
(envelope-from julian@whistle.com)
Received: (from daemon@localhost)
by alpo.whistle.com (8.8.5/8.8.5) id BAA08128
for <current@freebsd.org>; Tue, 26 Jan 1999 01:06:02 -0800 (PST)
Received: from current1.whistle.com(207.76.205.22)
via SMTP by alpo.whistle.com, id smtpdKg8125; Tue Jan 26 09:06:01 1999
Date: Tue, 26 Jan 1999 01:05:57 -0800 (PST)
From: Julian Elischer <julian@whistle.com>
To: current@FreeBSD.ORG
Subject: KLD broken-ness?
Message-ID: <Pine.BSF.3.95.990126010200.8657G-100000@current1.whistle.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
Can the KLD guru's look at this problem?
the ng_socket module depends on the netgraph module.
is there a reason that it can't find the one already in the kernel?
If you want to look at them these modules can be found at:
ftp://ftp.whistle.com/pub/archie/netgraph/netgraph.tgz
---------- Forwarded message ----------
Date: Tue, 26 Jan 1999 10:12:41 +0200 (SAT)
From: John Hay <jhay@mikom.csir.co.za>
To: Julian Elischer <julian@whistle.com>
Subject: Re: netgraph stuff
> you need the NETGRAPH option for if_sr.c
> and you need to load the ng_socket option to run the program
> of course you might keep the SOCKET precompiled by using
> options NETGRAPH_SOCKET as well
>
Ok, I have success. I have to compile everything into the the kernel.
I can ping and telnet over the link.
> > Well yes I have options NETGRAPH in the kernel and I do a kldload netgraph.
> > If I don't load it, ngctl don't want to run. It just dies with:
> > "ngctl: can't create node: Protocol not supported"
> > It looks like some things don't get set up / initialized if netgraph is
> > compiled into the kernel and not loaded as a kld.
> >
> > Hmmm Maybe this is my problem.
>
> options NETGRAPH is the equivalent of doing "kldload netgraph"
> during boot.
> It's needed if any other files statically link against it.
> (the sync drivers are the ony files that do that must be statically linked
> themselves.)
> the netgraph mosule however doesn't load the ng_socket module.
> (though the reverse may be true)
>
> >
> what does
> kldstat -v
> say?
It looks like the klds don't "see" the modules that are compiled into the
kernel. With a kernel compiled only with "options NETGRAPH" kldstat -v
looks like this:
------------
# kldstat -v
Id Refs Address Size Name
1 2 0xf0100000 121450 kernel
Contains modules:
Id Name
1 rootbus
2 netgraph
3 ng_sync_sr
4 ufs
5 procfs
6 if_loop
7 shell
8 elf
9 aout
2 1 0xf06f5000 3000 daemon_saver.ko
Contains modules:
Id Name
10 daemon_saver
#
------------
Then if I load ng_socket, it loads netgraph again:
-----------
# kldload ng_socket
# kldstat -v
Id Refs Address Size Name
1 4 0xf0100000 121450 kernel
Contains modules:
Id Name
1 rootbus
2 netgraph
3 ng_sync_sr
4 ufs
5 procfs
6 if_loop
7 shell
8 elf
9 aout
2 1 0xf06f5000 3000 daemon_saver.ko
Contains modules:
Id Name
10 daemon_saver
3 1 0xf0712000 3000 ng_socket.ko
Contains modules:
Id Name
12 ng_socket
4 1 0xf0716000 4000 netgraph.ko
Contains modules:
Id Name
11 netgraph
#
------------
On the other hand with everything needed compiled into the kernel, it looks
like this:
------------
# kldstat -v
Id Refs Address Size Name
1 2 0xf0100000 124178 kernel
Contains modules:
Id Name
1 rootbus
2 netgraph
3 ng_sync_sr
4 ufs
5 procfs
6 ng_socket
7 ng_iface
8 ng_echo
9 ng_cisco
10 if_loop
11 shell
12 elf
13 aout
2 1 0xf06f7000 3000 daemon_saver.ko
Contains modules:
Id Name
14 daemon_saver
#
------------
John
--
John Hay -- John.Hay@mikom.csir.co.za
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Tue Jan 26 01:18:42 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id BAA02719
for freebsd-current-outgoing; Tue, 26 Jan 1999 01:18:42 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from nlsystems.com (nlsys.demon.co.uk [158.152.125.33])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA02714
for <current@FreeBSD.ORG>; Tue, 26 Jan 1999 01:18:39 -0800 (PST)
(envelope-from dfr@nlsystems.com)
Received: from localhost (dfr@localhost)
by nlsystems.com (8.9.1/8.8.5) with SMTP id JAA91096;
Tue, 26 Jan 1999 09:17:40 GMT
Date: Tue, 26 Jan 1999 09:17:40 +0000 (GMT)
From: Doug Rabson <dfr@nlsystems.com>
To: Poul-Henning Kamp <phk@critter.freebsd.dk>
cc: Archie Cobbs <archie@whistle.com>, current@FreeBSD.ORG
Subject: Re: Dynamic sysctl registration
In-Reply-To: <22792.917303496@critter.freebsd.dk>
Message-ID: <Pine.BSF.4.01.9901260851310.88955-100000@herring.nlsystems.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
On Mon, 25 Jan 1999, Poul-Henning Kamp wrote:
> In message <199901252212.OAA18030@bubba.whistle.com>, Archie Cobbs writes:
> >Doug Rabson writes:
> >>
> >> If anyone is interested in seeing diffs (approx 23k), please contact me.
> >
> >I'm interested.. could you email me the diffs?
> >
> >I'm more interested in whether these patches can be committed... ?
> >Have Poul, DG, et. al. seen them?
>
> I'm somewhat weary of doing too much for sysctl, until we have
> intelligently examined the stuff and decided which way we want to
> go with it.
I'm fairly weary of it myself which is why I've put off doing this work
for literally years.
>
> (This patch is probably perfectly all right, without this comment
> being construed as a "Reviewed by:" :-), but before it goes in, I
> would like to hear if sysctl "is basically what we want" or if
> sysctl needs to be extended (for instance in the "repository"
> direction) ?
>
> One of the weak points about the current sysctl scheme is the
> rather simpleminded permission scheme, will we need something
> more capable ? The current system >is< capable if you write it
> yourself in a function, but we don't want 100 functions doing
> the same thing.)
>
> We probably also need to consider name-space management...
>
> And, documentation. I do like the "semi-literate" programming
> style, where you can stick a meaningfull documentation (ie,
> potentially several pages of it) right there in the source, (but
> I don't want it compiled in and loaded!) but for it to become real
> documentation, SGML or -man will be needed, and that would probably
> be too ugly for most eyes, or no ?
I'm finding it hard to focus on whether a registry is needed. Possibly by
the proposed devd, possibly not. I think that a decision can't be made
without actually working on the design of anything which uses it is not
going to be possible.
I'm not trying to replace sysctl at this point, just spruce it up a bit so
it at least works with the new kernel subsystems. The limited time I have
to spend on FreeBSD at the moment pretty much prevents anything more
ambitious.
--
Doug Rabson Mail: dfr@nlsystems.com
Nonlinear Systems Ltd. Phone: +44 181 442 9037
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Tue Jan 26 01:26:29 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id BAA03191
for freebsd-current-outgoing; Tue, 26 Jan 1999 01:26:29 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from nlsystems.com (nlsys.demon.co.uk [158.152.125.33])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA03186
for <current@freebsd.org>; Tue, 26 Jan 1999 01:26:24 -0800 (PST)
(envelope-from dfr@nlsystems.com)
Received: from localhost (dfr@localhost)
by nlsystems.com (8.9.1/8.8.5) with SMTP id JAA91135;
Tue, 26 Jan 1999 09:25:21 GMT
Date: Tue, 26 Jan 1999 09:25:21 +0000 (GMT)
From: Doug Rabson <dfr@nlsystems.com>
To: Poul-Henning Kamp <phk@critter.freebsd.dk>
cc: Archie Cobbs <archie@whistle.com>, Maxim Sobolev <sobomax@altavista.net>,
current@FreeBSD.ORG, Julian Elischer <julian@whistle.com>
Subject: Re: DEVFS, the time has come...
In-Reply-To: <24709.917338476@critter.freebsd.dk>
Message-ID: <Pine.BSF.4.01.9901260922311.88955-100000@herring.nlsystems.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
On Tue, 26 Jan 1999, Poul-Henning Kamp wrote:
> In message <199901260451.UAA23212@bubba.whistle.com>, Archie Cobbs writes:
> >Maxim Sobolev writes:
> >> Can you point all people (and me of course) who want to test DEVFS to some
> >> common information about DEVFS (usage, possible advantages/disadvantages etc.
> >> I think some FAQ or so will be nice. It's really will help us to go further
> >> with this issue.
> >
> >I agree.. and I've bugged Julian to put something together...
> >
> >Basically, there are a few things that need to be done to get DEVFS
> >into the 'mainstream'... and this includes SLICE.
>
> No, it doesn't have to be SLICE. In particular, if we're going the
> SLICE way, it should be done >right<, and Julians SLICE code didn't
> do that. (I know, I spent close to 6 months prototyping the concept
> and julian had my code to work from).
Wouldn't it be possible to fit this into the device system? If we treat
disks as devices and partition types as drivers, most of the boring work
of matching drivers to devices and keeping lists and trees of objects will
happen automatically.
--
Doug Rabson Mail: dfr@nlsystems.com
Nonlinear Systems Ltd. Phone: +44 181 442 9037
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Tue Jan 26 01:27:10 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id BAA03293
for freebsd-current-outgoing; Tue, 26 Jan 1999 01:27:10 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from nlsystems.com (nlsys.demon.co.uk [158.152.125.33])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA03270;
Tue, 26 Jan 1999 01:27:05 -0800 (PST)
(envelope-from dfr@nlsystems.com)
Received: from localhost (dfr@localhost)
by nlsystems.com (8.9.1/8.8.5) with SMTP id JAA91150;
Tue, 26 Jan 1999 09:29:16 GMT
Date: Tue, 26 Jan 1999 09:29:16 +0000 (GMT)
From: Doug Rabson <dfr@nlsystems.com>
To: Archie Cobbs <archie@whistle.com>
cc: current@FreeBSD.ORG, hackers@FreeBSD.ORG
Subject: Re: Same module loaded twice?
In-Reply-To: <199901252246.OAA18293@bubba.whistle.com>
Message-ID: <Pine.BSF.4.01.9901260927200.88955-100000@herring.nlsystems.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
On Mon, 25 Jan 1999, Archie Cobbs wrote:
> In the output below, notice there are two modules named "ng_sync_sr"
> loaded in the "kernel" object (due to a typo), and moreover there's
> a "netgraph" module loaded in both the "kernel" object and the "netgraph.ko"
> object..
>
> $ kldstat -v
> Id Refs Address Size Name
> 1 4 0xf0100000 1be82c kernel
> Contains modules:
> Id Name
> 1 rootbus
> 2 netgraph
> 3 ng_sync_sr
> 4 ng_sync_sr
> 5 ufs
> 6 nfs
> 7 msdos
> 8 procfs
> 9 cd9660
> 10 ipfw
> 11 if_tun
> 12 if_sl
> 13 if_ppp
> 14 if_loop
> 15 shell
> 16 execgzip
> 17 elf
> 18 aout
> 2 1 0xf07f1000 3000 ng_socket.ko
> Contains modules:
> Id Name
> 20 ng_socket
> 3 2 0xf07f5000 4000 netgraph.ko
> Contains modules:
> Id Name
> 19 netgraph
>
> Why and how does the linker allow this? It seems like:
>
> - When the kernel was compiled, the ng_sync_sr conflict should
> have caused a failure
> - When the netgraph.ko was kldloaded, there should have been
> an error from the conflicting module names
The linker doesn't care (mostly) about modules at the moment, just the
files which contain them. Mike has been thinking recently about a more
flexible scheme with dependancies and versioning at the module level which
is probably the right direction to take.
--
Doug Rabson Mail: dfr@nlsystems.com
Nonlinear Systems Ltd. Phone: +44 181 442 9037
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Tue Jan 26 01:31:14 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id BAA03725
for freebsd-current-outgoing; Tue, 26 Jan 1999 01:31:14 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from nlsystems.com (nlsys.demon.co.uk [158.152.125.33])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA03720
for <current@freebsd.org>; Tue, 26 Jan 1999 01:31:11 -0800 (PST)
(envelope-from dfr@nlsystems.com)
Received: from localhost (dfr@localhost)
by nlsystems.com (8.9.1/8.8.5) with SMTP id JAA91167;
Tue, 26 Jan 1999 09:33:16 GMT
Date: Tue, 26 Jan 1999 09:33:16 +0000 (GMT)
From: Doug Rabson <dfr@nlsystems.com>
To: Julian Elischer <julian@whistle.com>
cc: current@FreeBSD.ORG
Subject: Re: KLD broken-ness?
In-Reply-To: <Pine.BSF.3.95.990126010200.8657G-100000@current1.whistle.com>
Message-ID: <Pine.BSF.4.01.9901260930490.88955-100000@herring.nlsystems.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
On Tue, 26 Jan 1999, Julian Elischer wrote:
>
> Can the KLD guru's look at this problem?
> the ng_socket module depends on the netgraph module.
> is there a reason that it can't find the one already in the kernel?
>
> If you want to look at them these modules can be found at:
>
> ftp://ftp.whistle.com/pub/archie/netgraph/netgraph.tgz
As I just mentioned in my reply to Archie, the current dependancy system
in KLD is at the file level, not the module level. For the moment, you
will have to work with the current system (which might mean not allowing
static linking for this module).
Something better will probably happen. As always, the main problem is
time :-(
--
Doug Rabson Mail: dfr@nlsystems.com
Nonlinear Systems Ltd. Phone: +44 181 442 9037
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Tue Jan 26 02:24:18 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id CAA11979
for freebsd-current-outgoing; Tue, 26 Jan 1999 02:24:18 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from iclub.nsu.ru (iclub.nsu.ru [193.124.222.66])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA11961
for <freebsd-current@freebsd.org>; Tue, 26 Jan 1999 02:24:03 -0800 (PST)
(envelope-from semen@iclub.nsu.ru)
Received: from localhost (semen@localhost)
by iclub.nsu.ru (8.9.2/8.8.5) with SMTP id QAA03410
for <freebsd-current@freebsd.org>; Tue, 26 Jan 1999 16:23:48 +0600 (NS)
Date: Tue, 26 Jan 1999 16:23:47 +0600 (NS)
From: Ustimenko Semen <semen@iclub.nsu.ru>
To: freebsd-current@FreeBSD.ORG
Subject: What about inclusion of NTFS RO driver into current
Message-ID: <Pine.BSF.3.96.990126162215.2806C-100000@iclub.nsu.ru>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
Hello!
Possibly we can include it also in RELENG_2_2?
Bye.
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Tue Jan 26 02:42:56 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id CAA13915
for freebsd-current-outgoing; Tue, 26 Jan 1999 02:42:56 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA13904
for <current@freebsd.org>; Tue, 26 Jan 1999 02:42:52 -0800 (PST)
(envelope-from phk@critter.freebsd.dk)
Received: from critter.freebsd.dk (localhost [127.0.0.1])
by critter.freebsd.dk (8.9.1/8.8.5) with ESMTP id LAA25359;
Tue, 26 Jan 1999 11:41:08 +0100 (CET)
To: Doug Rabson <dfr@nlsystems.com>
cc: Archie Cobbs <archie@whistle.com>, Maxim Sobolev <sobomax@altavista.net>,
current@FreeBSD.ORG, Julian Elischer <julian@whistle.com>
Subject: Re: DEVFS, the time has come...
In-reply-to: Your message of "Tue, 26 Jan 1999 09:25:21 GMT."
<Pine.BSF.4.01.9901260922311.88955-100000@herring.nlsystems.com>
Date: Tue, 26 Jan 1999 11:41:06 +0100
Message-ID: <25357.917347266@critter.freebsd.dk>
From: Poul-Henning Kamp <phk@critter.freebsd.dk>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
>> No, it doesn't have to be SLICE. In particular, if we're going the
>> SLICE way, it should be done >right<, and Julians SLICE code didn't
>> do that. (I know, I spent close to 6 months prototyping the concept
>> and julian had my code to work from).
>
>Wouldn't it be possible to fit this into the device system? If we treat
>disks as devices and partition types as drivers, most of the boring work
>of matching drivers to devices and keeping lists and trees of objects will
>happen automatically.
Well, as long as you remember that it is not a strict hierarchy:
I could slice two disks, mirror the slices and concatenate the
mirrors if I wanted to.
It's not tricky to get it right, once you know where the pitfalls are,
the trick is to get it right AND make it elegant.
--
Poul-Henning Kamp FreeBSD coreteam member
phk@FreeBSD.ORG "Real hackers run -current on their laptop."
FreeBSD -- It will take a long time before progress goes too far!
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Tue Jan 26 02:47:25 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id CAA14384
for freebsd-current-outgoing; Tue, 26 Jan 1999 02:47:25 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from SIMULTAN.CH (eunet-gw.simultan.ch [194.191.191.82] (may be forged))
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA14372
for <freebsd-current@FreeBSD.ORG>; Tue, 26 Jan 1999 02:47:19 -0800 (PST)
(envelope-from tseidmann@simultan.ch)
Received: from simultan.ch (wsaltis-053.SIMULTAN.CH [192.92.128.53])
by SIMULTAN.CH (8.9.1a/8.9.1) with ESMTP id LAA10984;
Tue, 26 Jan 1999 11:46:00 +0100 (CET)
Message-ID: <36AD9CB2.21618CA6@simultan.ch>
Date: Tue, 26 Jan 1999 11:45:06 +0100
From: Thomas Seidmann <tseidmann@simultan.ch>
X-Mailer: Mozilla 4.5 [en] (WinNT; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Ustimenko Semen <semen@iclub.nsu.ru>
CC: freebsd-current@FreeBSD.ORG
Subject: Re: What about inclusion of NTFS RO driver into current
References: <Pine.BSF.3.96.990126162215.2806C-100000@iclub.nsu.ru>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
Hi,
I've modified the NTFS driver in following ways:
1. Transformed into a KLD
2. Fixed a bug in the driver for NTFS volumes with clusters above 1K
My plan is to put it on my WWW page today. The modified version works
for both 4.0-CURRENT and RELENG_3 as of today. Currently I'm working on
dealing correclty with the 'attribute list' attribute (nice recursion
:-)) in order to eliminate the limit of a single MFT entry per file.
Cheers,
Thomas
--
==========================================================
Thomas Seidmann
Simultan AG, CH-6246 Altishofen, Switzerland
mailto:tseidmann@simultan.ch tel +41.62.7489000
http://www.simultan.ch/~thomas fax +41.62.7489010
==========================================================
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Tue Jan 26 03:03:33 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id DAA15944
for freebsd-current-outgoing; Tue, 26 Jan 1999 03:03:33 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from labinfo.iet.unipi.it (labinfo.iet.unipi.it [131.114.9.5])
by hub.freebsd.org (8.8.8/8.8.8) with SMTP id DAA15923
for <current@FreeBSD.ORG>; Tue, 26 Jan 1999 03:02:53 -0800 (PST)
(envelope-from luigi@labinfo.iet.unipi.it)
Received: from localhost (luigi@localhost) by labinfo.iet.unipi.it (8.6.5/8.6.5) id HAA29514; Tue, 26 Jan 1999 07:43:42 +0100
From: Luigi Rizzo <luigi@labinfo.iet.unipi.it>
Message-Id: <199901260643.HAA29514@labinfo.iet.unipi.it>
Subject: Re: beginnings of a diskless boot sequence being committed
To: trost@cloud.rain.com (Bill Trost)
Date: Tue, 26 Jan 1999 07:43:42 +0100 (MET)
Cc: current@FreeBSD.ORG
In-Reply-To: <15510.917327374@grey.cloud.rain.com> from "Bill Trost" at Jan 25, 99 09:09:15 pm
X-Mailer: ELM [version 2.4 PL23]
Content-Type: text
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
> I have a wacky idea in this vein that I want to pursue sometime --
> instead of pushing off lots of symlinks for the various writable
> portions of the read-only root directory (which strikes as a bit odd in
> itself), I was considering union-mounting an MFS filesystem directly
> over the read-only root partition. The advantage of this approach
> is that you do not have to know ahead of time what portions of the
the problem is that i don't know how well unionfs works, and i don't
have the ability to fix it.
cheers
luigi
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Tue Jan 26 03:21:03 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id DAA17333
for freebsd-current-outgoing; Tue, 26 Jan 1999 03:21:03 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from flood.ping.uio.no (flood.ping.uio.no [129.240.78.31])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA17326
for <freebsd-current@FreeBSD.ORG>; Tue, 26 Jan 1999 03:21:01 -0800 (PST)
(envelope-from des@flood.ping.uio.no)
Received: (from des@localhost)
by flood.ping.uio.no (8.9.2/8.9.1) id MAA04556;
Tue, 26 Jan 1999 12:20:51 +0100 (CET)
(envelope-from des)
To: Brian Feldman <green@unixhelp.org>
Cc: Dag-Erling Smorgrav <des@flood.ping.uio.no>,
Boris Staeblow <balu@dva.in-berlin.de>, dillon@apollo.backplane.com,
freebsd-current@FreeBSD.ORG
Subject: Re: Heads up! New swapper and VM changes have been committed to -4.x
References: <Pine.BSF.4.05.9901251855010.2040-100000@janus.syracuse.net>
From: Dag-Erling Smorgrav <des@flood.ping.uio.no>
Date: 26 Jan 1999 12:20:49 +0100
In-Reply-To: Brian Feldman's message of "Mon, 25 Jan 1999 18:55:40 -0500 (EST)"
Message-ID: <xzpognmjn5a.fsf@flood.ping.uio.no>
Lines: 20
X-Mailer: Gnus v5.5/Emacs 19.34
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
Brian Feldman <green@unixhelp.org> writes:
> On 24 Jan 1999, Dag-Erling Smorgrav wrote:
> > [...]
> > These are statically linked, and must be relinked after libkvm has
> > been rebuilt.
> > [...]
> > These are dynamically linked, and will automatically pick up the new
> > libkvm.
> But (most) still require the structures to be the exact same way,
> which is the reason for the recompile anyway... don't forget that!
No, because the libkvm interface has not changed, only its internals.
libkvm must be updated to be able to talk to the kernel, and
applications which use it must be relinked with it. In the case of
dynamically linked applications, this is done automatically at load
time. Or am I reading this wrong?
DES
--
Dag-Erling Smorgrav - des@flood.ping.uio.no
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Tue Jan 26 03:26:33 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id DAA17934
for freebsd-current-outgoing; Tue, 26 Jan 1999 03:26:33 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from labinfo.iet.unipi.it (labinfo.iet.unipi.it [131.114.9.5])
by hub.freebsd.org (8.8.8/8.8.8) with SMTP id DAA17751
for <current@FreeBSD.ORG>; Tue, 26 Jan 1999 03:25:08 -0800 (PST)
(envelope-from luigi@labinfo.iet.unipi.it)
Received: from localhost (luigi@localhost) by labinfo.iet.unipi.it (8.6.5/8.6.5) id KAA29975; Tue, 26 Jan 1999 10:10:55 +0100
From: Luigi Rizzo <luigi@labinfo.iet.unipi.it>
Message-Id: <199901260910.KAA29975@labinfo.iet.unipi.it>
Subject: Re: dummynet causes crash?
To: green@unixhelp.org (Brian Feldman)
Date: Tue, 26 Jan 1999 10:10:54 +0100 (MET)
Cc: bright@hotjobs.com, current@FreeBSD.ORG
In-Reply-To: <Pine.BSF.4.05.9901251836320.2040-100000@janus.syracuse.net> from "Brian Feldman" at Jan 25, 99 06:37:36 pm
X-Mailer: ELM [version 2.4 PL23]
Content-Type: text
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
> > > fault virtual address = 0xdeadc116
> >
> > interestingly enough, the above address is "0xdeadbeef + 551 (decimal)".
> > It looks like somehow a wrong route entry was passed to ether_output().
...
> {"/home/green"}$ calc 0xdeadc116 - 0xdeadc0de
> 56
> possibly? IIRC 0xdeadc0de is used to fill freed memory areas in certain cases,
> to help detect programming errors related to such.
you are right, a much better guess, and more helpful hint.
cheers
luigi
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Tue Jan 26 03:36:39 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id DAA19041
for freebsd-current-outgoing; Tue, 26 Jan 1999 03:36:39 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from peach.ocn.ne.jp (peach.ocn.ne.jp [210.145.254.87])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA19007
for <current@FreeBSD.ORG>; Tue, 26 Jan 1999 03:36:35 -0800 (PST)
(envelope-from dcs@newsguy.com)
Received: from newsguy.com by peach.ocn.ne.jp (8.9.1a/OCN) id UAA29328; Tue, 26 Jan 1999 20:36:19 +0900 (JST)
Message-ID: <36AD9D66.8AE9ED04@newsguy.com>
Date: Tue, 26 Jan 1999 19:48:06 +0900
From: "Daniel C. Sobral" <dcs@newsguy.com>
X-Mailer: Mozilla 4.5 [en] (Win98; I)
X-Accept-Language: pt-BR,ja
MIME-Version: 1.0
To: Matthew Dillon <dillon@apollo.backplane.com>
CC: Bill Trost <trost@cloud.rain.com>, current@FreeBSD.ORG
Subject: Re: beginnings of a diskless boot sequence being committed
References: <199901251604.RAA27194@labinfo.iet.unipi.it> <15510.917327374@grey.cloud.rain.com> <199901260822.AAA14526@apollo.backplane.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
Matthew Dillon wrote:
>
> It isn't a bad idea, but I dunno how stable the union filesystem is.
Last I heard, it was hopelessly unstable. Well, not hopelessly. We
just have to fix the coherency problems in our vfs design. :-)
--
Daniel C. Sobral (8-DCS)
dcs@newsguy.com
If you sell your soul to the Devil and all you get is an MCSE from
it, you haven't gotten market rate.
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Tue Jan 26 04:16:49 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id EAA25250
for freebsd-current-outgoing; Tue, 26 Jan 1999 04:16:49 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from polaris.we.lc.ehu.es (polaris.we.lc.ehu.es [158.227.6.43])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA24848
for <current@FreeBSD.ORG>; Tue, 26 Jan 1999 04:11:23 -0800 (PST)
(envelope-from jose@we.lc.ehu.es)
Received: from we.lc.ehu.es (saturno [158.227.6.120])
by polaris.we.lc.ehu.es (8.9.1/8.9.1) with ESMTP id NAA12321;
Tue, 26 Jan 1999 13:08:18 +0100 (MET)
Message-ID: <36ADB032.695437F3@we.lc.ehu.es>
Date: Tue, 26 Jan 1999 13:08:18 +0100
From: "Jose M. Alcaide" <jose@we.lc.ehu.es>
Organization: Universidad del Pais Vasco - Dept. de Electricidad y Electronica
X-Mailer: Mozilla 4.07 [en] (X11; I; FreeBSD 3.0-STABLE i386)
MIME-Version: 1.0
To: Kazutaka YOKOTA <yokota@zodiac.mech.utsunomiya-u.ac.jp>
CC: current@FreeBSD.ORG
Subject: Re: keymaps
References: <199901211605.BAA24511@zodiac.mech.utsunomiya-u.ac.jp> <199901260325.MAA16405@zodiac.mech.utsunomiya-u.ac.jp>
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
Kazutaka YOKOTA wrote:
>
> * Summary of magic key sequences
>
> 101 keyboard 84 keyboard function
> ------------------------------------------------------------------------
> Ctrl-Alt-Delete Ctrl-Alt-Delete reboot
> Ctrl-Alt-Esc Ctrl-Alt-Esc debug
> Ctrl-Alt-Space Ctrl-Alt-Space susp
> ScrollLock ScrollLock slock
> PrintScreen Shift-(Numpad *)/PrintScreen nscr
> Ctrl-PrintScreen Shift-Ctrl-(Numpad *)/PrintScreen debug
> Alt-PrintScreen/SysRq SysRq nop
> Pause Ctrl-NumLock slock
> Shift-Pause Shift-Ctrl-NumLock saver
> Alt-Pause Alt-Ctrl-NumLock susp
> Ctrl-Pause/Break Ctrl-ScrollLock/Break nop
"Nihil obstat" :-)
-- JMA
-----------------------------------------------------------------------
José Mª Alcaide | mailto:jose@we.lc.ehu.es
Universidad del País Vasco | http://www.we.lc.ehu.es/~jose
Dpto. de Electricidad y Electrónica |
Facultad de Ciencias - Campus de Lejona | Tel.: +34-946012479
48940 Lejona (Vizcaya) - SPAIN | Fax: +34-944858139
-----------------------------------------------------------------------
"Go ahead... make my day." - H. Callahan
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Tue Jan 26 04:38:54 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id EAA26646
for freebsd-current-outgoing; Tue, 26 Jan 1999 04:38:54 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from iclub.nsu.ru (iclub.nsu.ru [193.124.222.66])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA26630
for <freebsd-current@FreeBSD.ORG>; Tue, 26 Jan 1999 04:38:44 -0800 (PST)
(envelope-from semen@iclub.nsu.ru)
Received: from localhost (semen@localhost)
by iclub.nsu.ru (8.9.2/8.8.5) with SMTP id SAA05710
for <freebsd-current@FreeBSD.ORG>; Tue, 26 Jan 1999 18:38:10 +0600 (NS)
Date: Tue, 26 Jan 1999 18:38:10 +0600 (NS)
From: Ustimenko Semen <semen@iclub.nsu.ru>
To: freebsd-current@FreeBSD.ORG
Subject: Re: What about inclusion of NTFS RO driver into current
In-Reply-To: <Pine.BSF.3.96.990126162215.2806C-100000@iclub.nsu.ru>
Message-ID: <Pine.BSF.3.96.990126183327.5641A-100000@iclub.nsu.ru>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
Sorry, for self follow up,
I haven't explain thougth clean enought.
I've spoken of almost ready NTFS driver, that is reported
to work for near 4-5 people. It was for stable and current
(don't know how to call them now) with little difference.
Thank you
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Tue Jan 26 04:49:45 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id EAA27806
for freebsd-current-outgoing; Tue, 26 Jan 1999 04:49:45 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from octopus.originative.co.uk (originat.demon.co.uk [158.152.220.9])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA27790
for <current@FreeBSD.ORG>; Tue, 26 Jan 1999 04:49:21 -0800 (PST)
(envelope-from paul@originative.co.uk)
From: paul@originative.co.uk
Received: by OCTOPUS with Internet Mail Service (5.5.1960.3)
id <DN2A7ZCJ>; Tue, 26 Jan 1999 12:47:46 -0000
Message-ID: <A6D02246E1ABD2119F5200C0F0303D10FDDB@OCTOPUS>
To: phk@critter.freebsd.dk, dfr@nlsystems.com
Cc: archie@whistle.com, sobomax@altavista.net, current@FreeBSD.ORG,
julian@whistle.com
Subject: RE: DEVFS, the time has come...
Date: Tue, 26 Jan 1999 12:47:45 -0000
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.1960.3)
Content-Type: text/plain
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
> -----Original Message-----
> From: Poul-Henning Kamp [mailto:phk@critter.freebsd.dk]
> Sent: Tuesday, January 26, 1999 10:41 AM
> To: Doug Rabson
> Cc: Archie Cobbs; Maxim Sobolev; current@FreeBSD.ORG; Julian Elischer
> Subject: Re: DEVFS, the time has come...
>
>
>
> >> No, it doesn't have to be SLICE. In particular, if we're going the
> >> SLICE way, it should be done >right<, and Julians SLICE
> code didn't
> >> do that. (I know, I spent close to 6 months prototyping the concept
> >> and julian had my code to work from).
> >
> >Wouldn't it be possible to fit this into the device system?
> If we treat
> >disks as devices and partition types as drivers, most of the
> boring work
> >of matching drivers to devices and keeping lists and trees
> of objects will
> >happen automatically.
>
> Well, as long as you remember that it is not a strict hierarchy:
> I could slice two disks, mirror the slices and concatenate the
> mirrors if I wanted to.
Where does this happen though?
If we go with Doug's idea (which seems quite neat), then the device
subsystem will present devices for each of the slices/partitions that
the low level disk handling code finds during the probe phase.
The mirroring of slices and subsequent concatenation of the mirrors, or
any other combination of slice munging that might take place happens
later doesn't it, using something like vinum. If so then can't vinum
become responsible for modifying the device view, i.e. if it creates a
concatenated partition then it could remove the two "low level" slice
devices and create a new disk device that represents the concatenated
area. You might not want to remove the low level devices or it could be
a vinum configuration option.
If something like vinum doesn't exist then you're not going to be doing
any mirroring or concatenation and Doug's solution would be fine for
creating the device nodes needed to represent the "actual" layout of the
disks, as opposed to a "view" of the disks that might be created by
vinum et al.
Paul.
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Tue Jan 26 04:50:14 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id EAA28094
for freebsd-current-outgoing; Tue, 26 Jan 1999 04:50:14 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from send205.yahoomail.com (send205.mail.yahoo.com [128.11.68.129])
by hub.freebsd.org (8.8.8/8.8.8) with SMTP id EAA28086
for <freebsd-current@freebsd.org>; Tue, 26 Jan 1999 04:50:11 -0800 (PST)
(envelope-from edwardsweeney@yahoo.com)
Message-ID: <19990126124944.19046.rocketmail@send205.yahoomail.com>
Received: from [38.30.235.49] by send205.mail.yahoo.com; Tue, 26 Jan 1999 04:49:44 PST
Date: Tue, 26 Jan 1999 04:49:44 -0800 (PST)
From: Ed Sweeney <edwardsweeney@yahoo.com>
Subject: crypt.3.gz prob with make aout-to-elf-install
To: freebsd-current@FreeBSD.ORG
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
I seem to be the only one with this problem. After
make-aout-to-elf-build, make-aout-to-elf-install gives:
===> lib/../secure/lib/libcrypt
install -c -o root -g wheel -m 444 libdescrypt.a /usr/lib/aout
install -c -o root -g wheel -m 444 libdescrypt_p.a /usr/lib/aout
install -c -o root -g wheel -m 444 -fschg libdescrypt.so.2.0
/usr/lib/aout
install -c -o root -g wheel -m 444 crypt.3.gz /usr/share/man/man3
install: crypt.3.gz: No such file or directory
*** Error code 71
Not sure what I've mucked up. Any help would be appreciated, thanks.
-Ed
==
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Ed Sweeney, Fairfax, VA
mailto:edwardsweeney@yahoo.com
_________________________________________________________
DO YOU YAHOO!?
Get your free @yahoo.com address at http://mail.yahoo.com
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Tue Jan 26 05:03:53 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id FAA29198
for freebsd-current-outgoing; Tue, 26 Jan 1999 05:03:53 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from ns.tar.com (ns.tar.com [204.95.187.2])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA29187
for <current@FreeBSD.ORG>; Tue, 26 Jan 1999 05:03:51 -0800 (PST)
(envelope-from dick@ns.tar.com)
Received: (from dick@localhost)
by ns.tar.com (8.9.2/8.9.1) id HAA06511;
Tue, 26 Jan 1999 07:02:25 -0600 (CST)
(envelope-from dick)
Date: Tue, 26 Jan 1999 07:02:25 -0600
From: "Richard Seaman, Jr." <dick@tar.com>
To: Manfred Antar <mantar@netcom.com>
Cc: Julian Elischer <julian@whistle.com>, current@FreeBSD.ORG
Subject: Re: HEADS UP! (kernel thread support)
Message-ID: <19990126070224.B478@tar.com>
References: <Pine.BSF.3.95.990125183840.8019J-100000@current1.whistle.c om> <4.1.19990125190740.00a135f0@192.168.0.1>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.95i
In-Reply-To: <4.1.19990125190740.00a135f0@192.168.0.1>; from Manfred Antar on Mon, Jan 25, 1999 at 07:09:37PM -0800
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
On Mon, Jan 25, 1999 at 07:09:37PM -0800, Manfred Antar wrote:
> At 06:41 PM 1/25/99 -0800, Julian Elischer wrote:
> >The Linuxthreads changes in the system that have been optioned out for a
> >while have been enabled after testing by many people.
> >
> >this will require a recompile of at least PS and probably the usual
> >culprits, (libkvm etc) (unless of course you've already been running with
> >the support turned on.)
> >
> >julian
> >
> Does this mean I can take -DCOMPAT_LINUX_THREADS out of /etc/make.conf ?
Julian also committed changes so that you can take -DVM_STACK out of
/etc/make.conf too, if you had it in (i386 only).
--
Richard Seamman, Jr. email: dick@tar.com
5182 N. Maple Lane phone: 414-367-5450
Chenequa WI 53058 fax: 414-367-5852
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Tue Jan 26 05:04:25 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id FAA29503
for freebsd-current-outgoing; Tue, 26 Jan 1999 05:04:25 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA29487
for <current@FreeBSD.ORG>; Tue, 26 Jan 1999 05:04:21 -0800 (PST)
(envelope-from phk@critter.freebsd.dk)
Received: from critter.freebsd.dk (localhost [127.0.0.1])
by critter.freebsd.dk (8.9.1/8.8.5) with ESMTP id OAA25989;
Tue, 26 Jan 1999 14:03:03 +0100 (CET)
To: paul@originative.co.uk
cc: dfr@nlsystems.com, archie@whistle.com, sobomax@altavista.net,
current@FreeBSD.ORG, julian@whistle.com
Subject: Re: DEVFS, the time has come...
In-reply-to: Your message of "Tue, 26 Jan 1999 12:47:45 GMT."
<A6D02246E1ABD2119F5200C0F0303D10FDDB@OCTOPUS>
Date: Tue, 26 Jan 1999 14:03:02 +0100
Message-ID: <25987.917355782@critter.freebsd.dk>
From: Poul-Henning Kamp <phk@critter.freebsd.dk>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
>> >
>> >Wouldn't it be possible to fit this into the device system?
>> If we treat
>> >disks as devices and partition types as drivers, most of the
>> boring work
>> >of matching drivers to devices and keeping lists and trees
>> of objects will
>> >happen automatically.
>>
>> Well, as long as you remember that it is not a strict hierarchy:
>> I could slice two disks, mirror the slices and concatenate the
>> mirrors if I wanted to.
>
>Where does this happen though?
>
>If we go with Doug's idea (which seems quite neat), then the device
>subsystem will present devices for each of the slices/partitions that
>the low level disk handling code finds during the probe phase.
Step back one step, and realize that handling fdisk or disklabel
"partitioning" is just another geometry translation, just like
mirroring/striping/concatenating/raid-%d/copy-on-write and so on.
(The only magic about them is that we're more used to them.)
Vinum would fit right into this.
The major problem is the "struct buf" which is too bloated to work
with for iorequests. There are some boot time issues too but they
are more a DEVFS kind of thing than a SLICE/GEOMETRY thing.
As I said, doing it generally is easy, all in all. If there is
interest I can try to find my design-notes for it.
--
Poul-Henning Kamp FreeBSD coreteam member
phk@FreeBSD.ORG "Real hackers run -current on their laptop."
FreeBSD -- It will take a long time before progress goes too far!
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Tue Jan 26 05:05:04 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id FAA29642
for freebsd-current-outgoing; Tue, 26 Jan 1999 05:05:04 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from adelphi.physics.adelaide.edu.au (adelphi.physics.adelaide.edu.au [129.127.36.247])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA29608
for <current@freebsd.org>; Tue, 26 Jan 1999 05:05:00 -0800 (PST)
(envelope-from kkennawa@physics.adelaide.edu.au)
Received: from bragg (bragg [129.127.36.34])
by adelphi.physics.adelaide.edu.au (8.8.8/8.8.8/UofA-1.5) with SMTP id XAA08181
for <current@freebsd.org>; Tue, 26 Jan 1999 23:34:56 +1030 (CST)
Received: from localhost by bragg; (5.65/1.1.8.2/05Aug95-0227PM)
id AA29798; Tue, 26 Jan 1999 23:34:56 +1030
Date: Tue, 26 Jan 1999 23:34:56 +1030 (CST)
From: Kris Kennaway <kkennawa@physics.adelaide.edu.au>
X-Sender: kkennawa@bragg
To: current@FreeBSD.ORG
Subject: vn still broken
Message-Id: <Pine.OSF.4.05.9901262327560.11196-100000@bragg>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
As I reported the other day, VNs are broken in -current.
It seems that if I try and cp some file which hasn't been recently read (i.e.
isn't being cached), it fails with:
[morden|root] 23:29 /mnt/myports> cp curl~/Makefile .
cp: ./Makefile: Bad address
and gives the following console warnings:
spec_getpages: I/O read failure: (error code=0)
size: 2048, resid: 2048, a_count: 724, valid: 0x0
nread: 0, reqpage: 0, pindex: 0, pcount: 1
vm_fault: pager read error, pid 77566 (cp)
however, if I first 'more' curl~/Makefile and then try and copy it, it
succeeds.
Kris
-----
(ASP) Microsoft Corporation (MSFT) announced today that the release of its
productivity suite, Office 2000, will be delayed until the first quarter
of 1901.
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Tue Jan 26 05:12:16 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id FAA00571
for freebsd-current-outgoing; Tue, 26 Jan 1999 05:12:16 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA00558
for <current@freebsd.org>; Tue, 26 Jan 1999 05:12:12 -0800 (PST)
(envelope-from phk@critter.freebsd.dk)
Received: from critter.freebsd.dk (localhost [127.0.0.1])
by critter.freebsd.dk (8.9.1/8.8.5) with ESMTP id OAA26059
for <current@freebsd.org>; Tue, 26 Jan 1999 14:11:41 +0100 (CET)
To: current@FreeBSD.ORG
Subject: wd0: DMA failure, DMA status 0
From: Poul-Henning Kamp <phk@FreeBSD.ORG>
Date: Tue, 26 Jan 1999 14:11:41 +0100
Message-ID: <26057.917356301@critter.freebsd.dk>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
Is "wd0: DMA failure, DMA status 0" something which needs looked at ?
Poul-Henning
FreeBSD 4.0-CURRENT #1: Tue Jan 26 12:13:25 CET 1999
root@schizo.freebsd.dk:/usr/src/sys/compile/SCHIZO
Timecounter "i8254" frequency 1193182 Hz
CPU: Pentium Pro (686-class CPU)
Origin = "GenuineIntel" Id = 0x619 Stepping=9
Features=0xfbff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV>
real memory = 134217728 (131072K bytes)
config> quit
avail memory = 128073728 (125072K bytes)
Programming 24 pins in IOAPIC #0
FreeBSD/SMP: Multiprocessor motherboard
cpu0 (BSP): apic id: 0, version: 0x00040011, at 0xfec08000
cpu1 (AP): apic id: 12, version: 0x00040011, at 0xfec08000
io0 (APIC): apic id: 13, version: 0x00170011, at 0xfec00000
Preloaded elf kernel "kernel" at 0xf027d000.
Probing for devices on PCI bus 0:
chip0: <Intel 82440FX (Natoma) PCI and memory controller> rev 0x02 on pci0.0.0
fxp0: <Intel EtherExpress Pro 10/100B Ethernet> rev 0x01 int a irq 18 on pci0.6.
0
fxp0: Ethernet address 00:a0:c9:49:5e:fa
chip1: <Intel 82371SB PCI to ISA bridge> rev 0x01 on pci0.7.0
ide_pci0: <Intel PIIX3 Bus-master IDE controller> rev 0x00 on pci0.7.1
vga0: <S3 Trio 64 graphics accelerator> rev 0x04 int a irq 17 on pci0.15.0
Probing for devices on the ISA bus:
sc0 on isa
sc0: VGA color <16 virtual consoles, flags=0x0>
atkbdc0 at 0x60-0x6f on motherboard
atkbd0 irq 1 on isa
psm0 not found
sio0 at 0x3f8-0x3ff irq 4 flags 0x10 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: FIFO enabled, 8 bytes threshold
fd0: 1.44MB 3.5in
wdc0 at 0x1f0-0x1f7 irq 14 flags 0xa0ff on isa
wdc0: unit 0 (wd0): <ST34520A>, DMA, 32-bit, multi-block-16
wd0: 4341MB (8890560 sectors), 9408 cyls, 15 heads, 63 S/T, 512 B/S
vga0 at 0x3b0-0x3df maddr 0xa0000 msize 131072 on isa
npx0 on motherboard
npx0: INT 16 interface
APIC_IO: routing 8254 via 8259 on pin 0
changing root device to wd0s1a
SMP: AP CPU #1 Launched!
wd0: DMA failure, DMA status 0
wd0: DMA failure, DMA status 0
wd0: DMA failure, DMA status 0
wd0: DMA failure, DMA status 0
wd0: DMA failure, DMA status 0
wd0: DMA failure, DMA status 0
--
Poul-Henning Kamp FreeBSD coreteam member
phk@FreeBSD.ORG "Real hackers run -current on their laptop."
FreeBSD -- It will take a long time before progress goes too far!
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Tue Jan 26 05:16:14 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id FAA01102
for freebsd-current-outgoing; Tue, 26 Jan 1999 05:16:14 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from caladan.tdx.co.uk (caladan.tdx.co.uk [195.188.177.4])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA01088;
Tue, 26 Jan 1999 05:16:06 -0800 (PST)
(envelope-from kpielorz@tdx.co.uk)
Received: from tdx.co.uk (lorca-tx.tdx.co.uk [195.188.177.242])
by caladan.tdx.co.uk (8.9.2/8.9.2) with ESMTP id NAA75212;
Tue, 26 Jan 1999 13:15:59 GMT
Message-ID: <36ADC00F.84D55970@tdx.co.uk>
Date: Tue, 26 Jan 1999 13:15:59 +0000
From: Karl Pielorz <kpielorz@tdx.co.uk>
Organization: TDX - The Digital eXchange
X-Mailer: Mozilla 4.5 [en] (WinNT; I)
X-Accept-Language: en
MIME-Version: 1.0
To: Poul-Henning Kamp <phk@FreeBSD.ORG>
CC: current@FreeBSD.ORG
Subject: Re: wd0: DMA failure, DMA status 0
References: <26057.917356301@critter.freebsd.dk>
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
Poul-Henning Kamp wrote:
>
> Is "wd0: DMA failure, DMA status 0" something which needs looked at ?
>
> Poul-Henning
Søren Schmidt posted a patch for this (was in the list a few days ago), if you
look through the mail archives you should see it... I don't know if it's been
comitted - I'm running it here fine though...
-Kp
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Tue Jan 26 05:17:39 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id FAA01195
for freebsd-current-outgoing; Tue, 26 Jan 1999 05:17:39 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from freebsd.dk (freebsd.dk [212.242.42.178])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA01187;
Tue, 26 Jan 1999 05:17:33 -0800 (PST)
(envelope-from sos@freebsd.dk)
Received: (from sos@localhost)
by freebsd.dk (8.9.1/8.9.1) id OAA31728;
Tue, 26 Jan 1999 14:17:30 +0100 (CET)
(envelope-from sos)
From: Søren Schmidt <sos@freebsd.dk>
Message-Id: <199901261317.OAA31728@freebsd.dk>
Subject: Re: wd0: DMA failure, DMA status 0
In-Reply-To: <26057.917356301@critter.freebsd.dk> from Poul-Henning Kamp at "Jan 26, 1999 2:11:41 pm"
To: phk@FreeBSD.ORG (Poul-Henning Kamp)
Date: Tue, 26 Jan 1999 14:17:30 +0100 (CET)
Cc: current@FreeBSD.ORG
X-Mailer: ELM [version 2.4ME+ PL43 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
It seems Poul-Henning Kamp wrote:
>
>
> Is "wd0: DMA failure, DMA status 0" something which needs looked at ?
Blame Julian, he broke it in v 1.183 of wd.c, the following patch
works on all my HW, but I dont have the "cyrix" chipset Julian
made the patch for, to test it on (it also contains other small
corrections mostly from Bruce)...
Index: wd.c
===================================================================
RCS file: /home/ncvs/src/sys/i386/isa/wd.c,v
retrieving revision 1.186
diff -u -r1.186 wd.c
--- wd.c 1999/01/17 05:46:24 1.186
+++ wd.c 1999/01/19 18:29:23
@@ -1084,10 +1086,11 @@
du = wddrives[dkunit(bp->b_dev)];
/* finish off DMA */
- if (du->dk_flags & (DKFL_DMA|DKFL_USEDMA)) {
+ if ((du->dk_flags & (DKFL_DMA|DKFL_SINGLE)) == DKFL_DMA) {
/* XXX SMP boxes sometimes generate an early intr. Why? */
- if ((wddma[du->dk_interface].wdd_dmastatus(du->dk_dmacookie) & WDDS_INTERRUPT)
- != 0)
+ if ((wddma[du->dk_interface].wdd_dmastatus(du->dk_dmacookie) &
+ WDDS_INTERRUPT) == 0)
+ return;
dmastat = wddma[du->dk_interface].wdd_dmadone(du->dk_dmacookie);
}
@@ -1568,6 +1571,7 @@
if (wdwait(du, 0, TIMEOUT) < 0)
return (1);
if( command == WDCC_FEATURES) {
+ outb(wdc + wd_sdh, WDSD_IBM | (du->dk_unit << 4) | head);
outb(wdc + wd_features, count);
if ( count == WDFEA_SETXFER )
outb(wdc + wd_seccnt, sector);
@@ -2289,9 +2293,8 @@
{
int err = 0;
- if ((du->dk_flags & (DKFL_DMA|DKFL_USEDMA)) && du->dk_dmacookie)
+ if ((du->dk_flags & (DKFL_DMA|DKFL_SINGLE)) == DKFL_DMA)
wddma[du->dk_interface].wdd_dmadone(du->dk_dmacookie);
-
(void)wdwait(du, 0, TIMEOUT);
outb(du->dk_altport, WDCTL_IDS | WDCTL_RST);
DELAY(10 * 1000);
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Tue Jan 26 06:13:53 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id GAA08239
for freebsd-current-outgoing; Tue, 26 Jan 1999 06:13:53 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from gatekeeper.tsc.tdk.com (gatekeeper.tsc.tdk.com [207.113.159.21])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA08234
for <freebsd-current@FreeBSD.ORG>; Tue, 26 Jan 1999 06:13:51 -0800 (PST)
(envelope-from gdonl@tsc.tdk.com)
Received: from sunrise.gv.tsc.tdk.com (root@sunrise.gv.tsc.tdk.com [192.168.241.191])
by gatekeeper.tsc.tdk.com (8.8.8/8.8.8) with ESMTP id GAA27271;
Tue, 26 Jan 1999 06:13:06 -0800 (PST)
(envelope-from gdonl@tsc.tdk.com)
Received: from salsa.gv.tsc.tdk.com (salsa.gv.tsc.tdk.com [192.168.241.194])
by sunrise.gv.tsc.tdk.com (8.8.5/8.8.5) with ESMTP id GAA16615;
Tue, 26 Jan 1999 06:13:05 -0800 (PST)
Received: (from gdonl@localhost)
by salsa.gv.tsc.tdk.com (8.8.5/8.8.5) id GAA18902;
Tue, 26 Jan 1999 06:13:04 -0800 (PST)
From: Don Lewis <Don.Lewis@tsc.tdk.com>
Message-Id: <199901261413.GAA18902@salsa.gv.tsc.tdk.com>
Date: Tue, 26 Jan 1999 06:13:04 -0800
In-Reply-To: Dag-Erling Smorgrav <des@flood.ping.uio.no>
"Re: Heads up! New swapper and VM changes have been committed to -4.x" (Jan 26, 12:20pm)
X-Mailer: Mail User's Shell (7.2.6 alpha(3) 7/19/95)
To: Dag-Erling Smorgrav <des@flood.ping.uio.no>,
Brian Feldman <green@unixhelp.org>
Subject: Re: Heads up! New swapper and VM changes have been committed to -4.x
Cc: Boris Staeblow <balu@dva.in-berlin.de>, dillon@apollo.backplane.com,
freebsd-current@FreeBSD.ORG
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
On Jan 26, 12:20pm, Dag-Erling Smorgrav wrote:
} Subject: Re: Heads up! New swapper and VM changes have been committed to -
} Brian Feldman <green@unixhelp.org> writes:
} > On 24 Jan 1999, Dag-Erling Smorgrav wrote:
} > > These are dynamically linked, and will automatically pick up the new
} > > libkvm.
} > But (most) still require the structures to be the exact same way,
} > which is the reason for the recompile anyway... don't forget that!
}
} No, because the libkvm interface has not changed, only its internals.
} libkvm must be updated to be able to talk to the kernel, and
} applications which use it must be relinked with it. In the case of
} dynamically linked applications, this is done automatically at load
} time. Or am I reading this wrong?
It depends on what has changed. If the application asks libkvm to
fetch some structure from the kernel, and the application's idea of
what the structure looks like is different that what is compiled into
the kernel and libkvm, the application will not work correctly. For
instance, if the layout of the proc structure changes, an application
that was compiled with the old structure definition that calls
kvm_getprocs() will get a pointer to a structure with the new layout.
When the application dereferences the pointer that kvm_getprocs() returns
at some offset into the structure, it will be looking at some other part
of the proc structure than what it wants.
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Tue Jan 26 06:14:40 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id GAA08547
for freebsd-current-outgoing; Tue, 26 Jan 1999 06:14:40 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from octopus.originative.co.uk (originat.demon.co.uk [158.152.220.9])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA08223
for <current@FreeBSD.ORG>; Tue, 26 Jan 1999 06:13:26 -0800 (PST)
(envelope-from paul@originative.co.uk)
From: paul@originative.co.uk
Received: by OCTOPUS with Internet Mail Service (5.5.1960.3)
id <DN2A7ZCW>; Tue, 26 Jan 1999 14:11:47 -0000
Message-ID: <A6D02246E1ABD2119F5200C0F0303D10FDDC@OCTOPUS>
To: perry@zso.dec.com, asmodai@wxs.nl
Cc: arg@arg1.demon.co.uk, current@FreeBSD.ORG, dillon@apollo.backplane.com
Subject: RE: 4.0-Current, netscape halts system
Date: Tue, 26 Jan 1999 14:11:46 -0000
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.1960.3)
Content-Type: text/plain
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
> -----Original Message-----
> From: Reginald S. Perry [mailto:perry@zso.dec.com]
> Sent: Tuesday, January 26, 1999 7:35 AM
> To: Jeroen Ruigrok/Asmodai
> Cc: Andrew Gordon; current@FreeBSD.ORG; Matthew Dillon
> Subject: Re: 4.0-Current, netscape halts system
>
>
> I have been having these X lockups with the linux netscape 4.5
> running. I may have exacerbated it when I installed the linux
> realplayer and macromedia flash plugins.
>
> I would like to have a methodology to help debug this, but I
> have just
> this one system to use as the debug system. I do also have a vt220
> which I could set up if that would help.
>
> The key here is that for me it locks the system up completely. I
> cannot telnet in remotely and the ctrl-alt-esc key sequence does not
> work so its unclear to me how to debug this. Tell me what I
> would need
> to help debug it, and I will try to be of some help. Ill attach my
> dmesg output.
>
I've had the problem recently and in the past where the system locks up
completely and a lot of the time the speaker starts a continuous beep.
Locks up solid, requires a power-cycle.
It's not a new problem, it used to happen a lot on my dual processor box
and I've had it happen a few time this week on my single processor dev
box. The hardware is very different on both boxes and compared to yours
so the cause must be somewhere fairly generic.
I *think* Netscape was in use every time but I can't see how netscape
itself can be directly responsible for a system lockup, it must be
tickling some interrupt problem.
Paul.
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Tue Jan 26 06:23:02 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id GAA09501
for freebsd-current-outgoing; Tue, 26 Jan 1999 06:23:02 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from bright.fx.genx.net (bright.fx.genx.net [206.64.4.154])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA09496
for <current@freebsd.org>; Tue, 26 Jan 1999 06:23:01 -0800 (PST)
(envelope-from bright@hotjobs.com)
Received: from localhost (bright@localhost)
by bright.fx.genx.net (8.9.1/8.9.1) with ESMTP id JAA77059
for <current@freebsd.org>; Tue, 26 Jan 1999 09:29:30 -0500 (EST)
(envelope-from bright@hotjobs.com)
X-Authentication-Warning: bright.fx.genx.net: bright owned process doing -bs
Date: Tue, 26 Jan 1999 09:29:30 -0500 (EST)
From: Alfred Perlstein <bright@hotjobs.com>
X-Sender: bright@bright.fx.genx.net
To: current@FreeBSD.ORG
Subject: link_elf: symbol grow undefined
Message-ID: <Pine.BSF.4.05.9901260923310.55154-100000@bright.fx.genx.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
I sup'd and recompiled last night (2am EST) and get that message when
running 'linux' after boot on my console,
on my tty i get: kldload: can't load linux: Exec format error
while looking at this i noticed that loading joy.ko:
tty: kldload: can't load joy.ko: Exec format error
console: link_elf: symbol lkmexists undefined
thanks,
-Alfred
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Tue Jan 26 06:45:08 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id GAA12511
for freebsd-current-outgoing; Tue, 26 Jan 1999 06:45:08 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from mortar.carlson.com (mortar.carlson.com [208.240.12.98])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA12493;
Tue, 26 Jan 1999 06:45:05 -0800 (PST)
(envelope-from veldy@visi.com)
Received: from mortar.carlson.com (root@localhost)
by mortar.carlson.com with ESMTP id IAA01684;
Tue, 26 Jan 1999 08:44:37 -0600 (CST)
Received: from w142844 ([172.25.99.35])
by mortar.carlson.com with SMTP id IAA01680;
Tue, 26 Jan 1999 08:44:28 -0600 (CST)
Message-ID: <004801be493a$751fed30$236319ac@w142844.carlson.com>
From: "Thomas T. Veldhouse" <veldy@visi.com>
To: "FreeBSD-Stable" <freebsd-stable@FreeBSD.ORG>,
"FreeBSD-Current" <freebsd-current@FreeBSD.ORG>
Subject: /boot/loader and Secondary IDE Master?
Date: Tue, 26 Jan 1999 08:44:54 -0600
MIME-Version: 1.0
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 4.72.3110.5
X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
Has the boot loader / kernel been changed to allow booting off of the
secondary IDE master yet, or more correctly, has a solution been found (for
3.0-STABLE)? I have been using a patch created by somebody on the list from
a few days back that has worked quite well. However, I have noted a lot of
activity surrounding the boot process. I don't know if I missed anything,
but perhaps this works now. I have been using the following in my
loader.rc:
set currdev=disk2s1a
set rootdev=disk2s1a
boot /kernel
Is this still necessary? I have tried building the kernel without the patch
and leaving my loader.rc as is and it still tries to boot off of wd1 instead
of wd2. Is there a new parameter perhaps?
Tom Veldhouse
veldy@visi.com
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Tue Jan 26 07:51:44 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id HAA22135
for freebsd-current-outgoing; Tue, 26 Jan 1999 07:51:44 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from khavrinen.lcs.mit.edu (khavrinen.lcs.mit.edu [18.24.4.193])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA22129
for <current@FreeBSD.ORG>; Tue, 26 Jan 1999 07:51:39 -0800 (PST)
(envelope-from wollman@khavrinen.lcs.mit.edu)
Received: (from wollman@localhost)
by khavrinen.lcs.mit.edu (8.9.1/8.9.1) id KAA25207;
Tue, 26 Jan 1999 10:50:38 -0500 (EST)
(envelope-from wollman)
Date: Tue, 26 Jan 1999 10:50:38 -0500 (EST)
From: Garrett Wollman <wollman@khavrinen.lcs.mit.edu>
Message-Id: <199901261550.KAA25207@khavrinen.lcs.mit.edu>
To: Luigi Rizzo <luigi@labinfo.iet.unipi.it>
Cc: trost@cloud.rain.com (Bill Trost), current@FreeBSD.ORG
Subject: Re: beginnings of a diskless boot sequence being committed
In-Reply-To: <199901260643.HAA29514@labinfo.iet.unipi.it>
References: <15510.917327374@grey.cloud.rain.com>
<199901260643.HAA29514@labinfo.iet.unipi.it>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
<<On Tue, 26 Jan 1999 07:43:42 +0100 (MET), Luigi Rizzo <luigi@labinfo.iet.unipi.it> said:
> the problem is that i don't know how well unionfs works, and i don't
> have the ability to fix it.
Please keep in mind that there are two *different* entiries being
discussed here:
1) mount -o union
2) mount -t union (which should really be called `translucentfs').
The former is a generic property of the VFS layer; the latter is a
specific filesystem with rather different properties.
-GAWollman
--
Garrett A. Wollman | O Siem / We are all family / O Siem / We're all the same
wollman@lcs.mit.edu | O Siem / The fires of freedom
Opinions not those of| Dance in the burning flame
MIT, LCS, CRS, or NSA| - Susan Aglukark and Chad Irschick
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Tue Jan 26 07:53:07 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id HAA22544
for freebsd-current-outgoing; Tue, 26 Jan 1999 07:53:07 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from bart.esiee.fr (bart.esiee.fr [147.215.1.20])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA22514
for <freebsd-current@FreeBSD.ORG>; Tue, 26 Jan 1999 07:52:36 -0800 (PST)
(envelope-from bonnetf@bart.esiee.fr)
Received: (from bonnetf@localhost)
by bart.esiee.fr (8.9.1a/8.9.1) id QAA24899
for freebsd-current@FreeBSD.ORG; Tue, 26 Jan 1999 16:52:11 +0100 (MET)
From: Frank Bonnet <bonnetf@bart.esiee.fr>
Message-Id: <199901261552.QAA24899@bart.esiee.fr>
Subject: NIS with HPUX 10.20
To: freebsd-current@FreeBSD.ORG
Date: Tue, 26 Jan 1999 16:52:11 MET
X-Mailer: Elm [revision: 112.7]
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
Hi
I'm in trouble with NIS on a 3.0 client.
NIS is setup correctly ;-)
"ypcat" works well but NOT "ypmatch" ( for any map )
The NIS master server is a HPUX 10.20 box which is
accessed by many UNIX clients ( HP and Sun ) without
problem.
Any idea ?
TIA
--
Frank Bonnet
Groupe ESIEE Paris
http://www.esiee.fr/~bonnetf/
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Tue Jan 26 07:56:17 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id HAA23163
for freebsd-current-outgoing; Tue, 26 Jan 1999 07:56:17 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from peloton.physics.montana.edu (peloton.physics.montana.edu [153.90.192.177])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA23158
for <current@FreeBSD.ORG>; Tue, 26 Jan 1999 07:56:15 -0800 (PST)
(envelope-from brett@peloton.physics.montana.edu)
Received: from localhost (brett@localhost)
by peloton.physics.montana.edu (8.8.8/8.8.7) with ESMTP id IAA26694;
Tue, 26 Jan 1999 08:55:47 -0700 (MST)
(envelope-from brett@peloton.physics.montana.edu)
Date: Tue, 26 Jan 1999 08:55:47 -0700 (MST)
From: Brett Taylor <brett@peloton.physics.montana.edu>
To: Jacques Vidrine <n@nectar.com>
cc: current@FreeBSD.ORG
Subject: Re: ack! LaTeX?
In-Reply-To: <199901241751.LAA83676@spawn.nectar.com>
Message-ID: <Pine.BSF.4.05.9901260854510.23157-100000@peloton.physics.montana.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
Hi,
> The latex installed by the teTex port complained about not being able to
> find default settings, or some such.
Did you run texconfig? I'm having no trouble at all on my -current
machine; well I guess it's a -STABLE machine now but... :-)
Brett
******************************************************************
Brett Taylor brett@peloton.physics.montana.edu
http://peloton.physics.montana.edu/brett/
"love isn't someplace that we fall, it's something that we do"
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Tue Jan 26 08:11:40 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id IAA25174
for freebsd-current-outgoing; Tue, 26 Jan 1999 08:11:40 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from pau-amma.whistle.com (s205m64.whistle.com [207.76.205.64])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA25169
for <freebsd-current@FreeBSD.ORG>; Tue, 26 Jan 1999 08:11:37 -0800 (PST)
(envelope-from dhw@whistle.com)
Received: (from dhw@localhost)
by pau-amma.whistle.com (8.9.1/8.9.1) id IAA04396;
Tue, 26 Jan 1999 08:10:16 -0800 (PST)
(envelope-from dhw)
Date: Tue, 26 Jan 1999 08:10:16 -0800 (PST)
From: David Wolfskill <dhw@whistle.com>
Message-Id: <199901261610.IAA04396@pau-amma.whistle.com>
To: bonnetf@bart.esiee.fr, freebsd-current@FreeBSD.ORG
Subject: Re: NIS with HPUX 10.20
In-Reply-To: <199901261552.QAA24899@bart.esiee.fr>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
>From: Frank Bonnet <bonnetf@bart.esiee.fr>
>Date: Tue, 26 Jan 1999 16:52:11 MET
>I'm in trouble with NIS on a 3.0 client.
>NIS is setup correctly ;-)
>"ypcat" works well but NOT "ypmatch" ( for any map )
>The NIS master server is a HPUX 10.20 box which is
>accessed by many UNIX clients ( HP and Sun ) without
>problem.
Hmmm.... Well, on a 3.0-STABLE system set up recently, I'm *not* seeing
such problems:
dhw-test1[1]% uname -a
FreeBSD dhw-test1.whistle.com 3.0-STABLE FreeBSD 3.0-STABLE #0: Fri Jan 22 22:54:35 PST 1999 root@dhw-test1.whistle.com:/usr/src/sys/compile/DHW-TEST1 i386
(Rather than demonstrating that ypcat works, which isn't an issue, I'll show
the result from ypmatch....)
dhw-test1[2]% ypmatch -k /defaults amd.ftp
/defaults sublink:=${key}
In our case, the master NIS server is (also) a FreeBSD box, but it's
running 2.2.6-R.
The 3.0-CURRENT was built from the RELENG_3 sources, and I had applied
my patch to contrib/amd/libamu/mount_fs.c (which chould *not* have had
anything at all to do with NIS), and did a "make world" (followed by
rebuilding & installing the kernel).
david
--
David Wolfskill UNIX System Administrator
dhw@whistle.com voice: (650) 577-7158 pager: (650) 371-4621
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Tue Jan 26 08:23:32 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id IAA26656
for freebsd-current-outgoing; Tue, 26 Jan 1999 08:23:32 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from ns.mt.sri.com (sri-gw.MT.net [206.127.105.141])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA26636
for <freebsd-current@FreeBSD.ORG>; Tue, 26 Jan 1999 08:23:28 -0800 (PST)
(envelope-from nate@mt.sri.com)
Received: from mt.sri.com (rocky.mt.sri.com [206.127.76.100])
by ns.mt.sri.com (8.8.8/8.8.8) with SMTP id JAA23165;
Tue, 26 Jan 1999 09:23:27 -0700 (MST)
(envelope-from nate@rocky.mt.sri.com)
Received: by mt.sri.com (SMI-8.6/SMI-SVR4)
id JAA12330; Tue, 26 Jan 1999 09:23:26 -0700
Date: Tue, 26 Jan 1999 09:23:26 -0700
Message-Id: <199901261623.JAA12330@mt.sri.com>
From: Nate Williams <nate@mt.sri.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
To: Steve Kargl <sgk@troutmask.apl.washington.edu>
Cc: freebsd-current@FreeBSD.ORG, jkh@time.cdrom.com
Subject: Re: removing f2c from base distribution
In-Reply-To: <199901252234.OAA02595@troutmask.apl.washington.edu>
References: <199901252234.OAA02595@troutmask.apl.washington.edu>
X-Mailer: VM 6.34 under 19.16 "Lille" XEmacs Lucid
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
> Ladies and Gents,
>
> I have completed the portification of f2c and its support library.
Who is going to pick this up? Last time I volunteered, Jordan balked at
the idea.
Nate
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Tue Jan 26 09:25:16 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id JAA03452
for freebsd-current-outgoing; Tue, 26 Jan 1999 09:25:16 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from fang.cs.sunyit.edu (fang.cs.sunyit.edu [192.52.220.66])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA03440
for <freebsd-current@FreeBSD.ORG>; Tue, 26 Jan 1999 09:25:09 -0800 (PST)
(envelope-from meyerd1@fang.cs.sunyit.edu)
Received: from fang.cs.sunyit.edu (fang.cs.sunyit.edu [192.52.220.66])
by fang.cs.sunyit.edu (8.8.8/8.8.8) with SMTP id MAA17304;
Tue, 26 Jan 1999 12:25:37 -0500 (EST)
(envelope-from meyerd1@fang.cs.sunyit.edu)
Date: Tue, 26 Jan 1999 12:25:37 -0500 (EST)
From: Daniel Aaron Meyer <meyerd1@fang.cs.sunyit.edu>
To: David Wolfskill <dhw@whistle.com>
cc: bonnetf@bart.esiee.fr, freebsd-current@FreeBSD.ORG
Subject: Re: NIS with HPUX 10.20
In-Reply-To: <199901261610.IAA04396@pau-amma.whistle.com>
Message-ID: <Pine.BSF.4.02A.9901261220240.17228-100000@fang.cs.sunyit.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
Are the links in /usr/lib correct? They didnt get moved to /usr/lib/aout
when a make aout-to-elf was run? I believe this causes ypcat to display
the maps, but ypmatch will not work.
libcrypt.a -> libdescrypt.a
libcrypt.so.2 -> libdescrypt.so.2
libcrypt_p.a -> libdescrypt_p.a
--Dan
On Tue, 26 Jan 1999, David Wolfskill wrote:
> >From: Frank Bonnet <bonnetf@bart.esiee.fr>
> >Date: Tue, 26 Jan 1999 16:52:11 MET
>
> >I'm in trouble with NIS on a 3.0 client.
>
> >NIS is setup correctly ;-)
>
> >"ypcat" works well but NOT "ypmatch" ( for any map )
>
> >The NIS master server is a HPUX 10.20 box which is
> >accessed by many UNIX clients ( HP and Sun ) without
> >problem.
>
> Hmmm.... Well, on a 3.0-STABLE system set up recently, I'm *not* seeing
> such problems:
>
> dhw-test1[1]% uname -a
> FreeBSD dhw-test1.whistle.com 3.0-STABLE FreeBSD 3.0-STABLE #0: Fri Jan 22 22:54:35 PST 1999 root@dhw-test1.whistle.com:/usr/src/sys/compile/DHW-TEST1 i386
>
> (Rather than demonstrating that ypcat works, which isn't an issue, I'll show
> the result from ypmatch....)
>
> dhw-test1[2]% ypmatch -k /defaults amd.ftp
> /defaults sublink:=${key}
>
>
> In our case, the master NIS server is (also) a FreeBSD box, but it's
> running 2.2.6-R.
>
> The 3.0-CURRENT was built from the RELENG_3 sources, and I had applied
> my patch to contrib/amd/libamu/mount_fs.c (which chould *not* have had
> anything at all to do with NIS), and did a "make world" (followed by
> rebuilding & installing the kernel).
>
> david
> --
> David Wolfskill UNIX System Administrator
> dhw@whistle.com voice: (650) 577-7158 pager: (650) 371-4621
>
> To Unsubscribe: send mail to majordomo@FreeBSD.org
> with "unsubscribe freebsd-current" in the body of the message
>
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Tue Jan 26 09:52:09 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id JAA06305
for freebsd-current-outgoing; Tue, 26 Jan 1999 09:52:09 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from pau-amma.whistle.com (s205m64.whistle.com [207.76.205.64])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA06300
for <freebsd-current@FreeBSD.ORG>; Tue, 26 Jan 1999 09:52:08 -0800 (PST)
(envelope-from dhw@whistle.com)
Received: (from dhw@localhost)
by pau-amma.whistle.com (8.9.1/8.9.1) id JAA05102;
Tue, 26 Jan 1999 09:51:05 -0800 (PST)
(envelope-from dhw)
Date: Tue, 26 Jan 1999 09:51:05 -0800 (PST)
From: David Wolfskill <dhw@whistle.com>
Message-Id: <199901261751.JAA05102@pau-amma.whistle.com>
To: freebsd-current@FreeBSD.ORG, meyerd1@fang.cs.sunyit.edu
Subject: Re: NIS with HPUX 10.20
Cc: bonnetf@bart.esiee.fr
In-Reply-To: <Pine.BSF.4.02A.9901261220240.17228-100000@fang.cs.sunyit.edu>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
>Date: Tue, 26 Jan 1999 12:25:37 -0500 (EST)
>From: Daniel Aaron Meyer <meyerd1@fang.cs.sunyit.edu>
>Are the links in /usr/lib correct? They didnt get moved to /usr/lib/aout
>when a make aout-to-elf was run?...
In our case, I didn't do a "make aout-to-elf": I started with a system
on which I installed the 3.0-SNAP of 19990112; I then picked up the
RELENG_3 sources and did a "make world".
I did note that, unlike the SNAP, the result had a /usr/libexec/ld.so;
since several programs (that were being loaded from an NFS-resident
/usr/local/bin, all of which are a.out) whined about its lack (as they
died), I thought this was probably A Good Thing.
On the other hand, it seems that the /usr/libexec/ld-elf.so.1 was *not*
modified by the "make world" process; I thought that odd.
david
--
David Wolfskill UNIX System Administrator
dhw@whistle.com voice: (650) 577-7158 pager: (650) 371-4621
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Tue Jan 26 09:58:53 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id JAA07463
for freebsd-current-outgoing; Tue, 26 Jan 1999 09:58:53 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from pau-amma.whistle.com (s205m64.whistle.com [207.76.205.64])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA07458
for <current@FreeBSD.ORG>; Tue, 26 Jan 1999 09:58:51 -0800 (PST)
(envelope-from dhw@whistle.com)
Received: (from dhw@localhost)
by pau-amma.whistle.com (8.9.1/8.9.1) id JAA05166;
Tue, 26 Jan 1999 09:58:02 -0800 (PST)
(envelope-from dhw)
Date: Tue, 26 Jan 1999 09:58:02 -0800 (PST)
From: David Wolfskill <dhw@whistle.com>
Message-Id: <199901261758.JAA05166@pau-amma.whistle.com>
To: current@FreeBSD.ORG, des@flood.ping.uio.no
Subject: Re: CALL FOR FEEDBACK: inetd
In-Reply-To: <xzp7lvcfg8r.fsf@flood.ping.uio.no>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
>From: Dag-Erling Smorgrav <des@flood.ping.uio.no>
>Date: 28 Dec 1998 16:17:24 +0100
>I just committed a patch to inetd (rev. 1.44 of inetd.c) which I hope
>fixes the "junk pointer: too low to make sense" bug mentioned in PR
>bin/8183. I'd appreciate if those of you who have experienced problems
>with inetd would tell me as quickly as possible if the patch
>alleviates those problems.
I realize that this note may be so late that it is anticlimactic... but
the 3.0 machine here that had been exhibiting the above-referenced
problems (typically, in conjunction with amanda backups) has resolutely
failed to exhibit them since the inetd patch was installed.
We believe that the machine has been exercised enough that the symptoms
would have recurred had the problem(s) still existed.
Thanks,
david
--
David Wolfskill UNIX System Administrator
dhw@whistle.com voice: (650) 577-7158 pager: (650) 371-4621
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Tue Jan 26 10:48:16 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id KAA14080
for freebsd-current-outgoing; Tue, 26 Jan 1999 10:48:16 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from thelab.hub.org (nat0690.mpoweredpc.net [142.177.190.182])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA14071
for <freebsd-current@freebsd.org>; Tue, 26 Jan 1999 10:48:14 -0800 (PST)
(envelope-from scrappy@hub.org)
Received: from localhost (scrappy@localhost)
by thelab.hub.org (8.9.1/8.9.1) with ESMTP id OAA96094
for <freebsd-current@freebsd.org>; Tue, 26 Jan 1999 14:48:12 -0400 (AST)
(envelope-from scrappy@hub.org)
X-Authentication-Warning: thelab.hub.org: scrappy owned process doing -bs
Date: Tue, 26 Jan 1999 14:48:11 -0400 (AST)
From: The Hermit Hacker <scrappy@hub.org>
To: freebsd-current@FreeBSD.ORG
Subject: Hate to ask, but...aout -> elf ...
Message-ID: <Pine.BSF.4.05.9901261440120.94383-100000@thelab.hub.org>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
After seeing the trouble that Jordan had, I'm curiuos as to what is going
to be involved in going from an aout system, last built around the 21st of
October, 1998 (3.0-CURRENT of the time) to 3.0-STABLE ...
Just did a gander through the archives, and saw one mention, by Jordan,
about new boot blocks and whatnot...
I'm 2.5k kilometers from the server, and have some really good ppl 'on
site' if anything blows up terribly, but it still makes me nervous...I do
have it on a serial console, but...
Is it a simple matter of 'make aout-to-elf', or...?
I recall awhile bac there being a URL that someone had put up, so pointers
are most welcome...I don't mind reading through a document, just need to
know where to find it...
I've been putting this off, hoping to get *to* the computer and doing it
'face-to-face', but its not looking like that will happen for another
couple of months, and I've having problems with the server that appear to
be software, but the software is now 3+ months old, and don't want to put
in problem reports :(
Any help/suggestions and caveats are much appreciated...
Marc G. Fournier
Systems Administrator @ hub.org
primary: scrappy@hub.org secondary: scrappy@{freebsd|postgresql}.org
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Tue Jan 26 10:57:21 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id KAA15138
for freebsd-current-outgoing; Tue, 26 Jan 1999 10:57:21 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from dingo.cdrom.com (castles236.castles.com [208.214.165.236])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA15113
for <freebsd-current@FreeBSD.ORG>; Tue, 26 Jan 1999 10:57:16 -0800 (PST)
(envelope-from mike@dingo.cdrom.com)
Received: from dingo.cdrom.com (localhost [127.0.0.1])
by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id KAA18216;
Tue, 26 Jan 1999 10:53:05 -0800 (PST)
(envelope-from mike@dingo.cdrom.com)
Message-Id: <199901261853.KAA18216@dingo.cdrom.com>
X-Mailer: exmh version 2.0.2 2/24/98
To: Nate Williams <nate@mt.sri.com>
cc: Steve Kargl <sgk@troutmask.apl.washington.edu>,
freebsd-current@FreeBSD.ORG, jkh@time.cdrom.com
Subject: Re: removing f2c from base distribution
In-reply-to: Your message of "Tue, 26 Jan 1999 09:23:26 MST."
<199901261623.JAA12330@mt.sri.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Tue, 26 Jan 1999 10:53:04 -0800
From: Mike Smith <mike@smith.net.au>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
> > Ladies and Gents,
> >
> > I have completed the portification of f2c and its support library.
>
> Who is going to pick this up? Last time I volunteered, Jordan balked at
> the idea.
I was among the people that asked Steve to do the work; I'd have no
trouble with you doing the integration/extraction. You might just
want to check that the recent alpha-related changes that were submitted
for f2c are covered in the portified version.
--
\\ Sometimes you're ahead, \\ Mike Smith
\\ sometimes you're behind. \\ mike@smith.net.au
\\ The race is long, and in the \\ msmith@freebsd.org
\\ end it's only with yourself. \\ msmith@cdrom.com
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Tue Jan 26 11:05:25 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id LAA16133
for freebsd-current-outgoing; Tue, 26 Jan 1999 11:05:25 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from dingo.cdrom.com (castles236.castles.com [208.214.165.236])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA16126
for <freebsd-current@FreeBSD.ORG>; Tue, 26 Jan 1999 11:05:22 -0800 (PST)
(envelope-from mike@dingo.cdrom.com)
Received: from dingo.cdrom.com (localhost [127.0.0.1])
by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id LAA18345;
Tue, 26 Jan 1999 11:01:25 -0800 (PST)
(envelope-from mike@dingo.cdrom.com)
Message-Id: <199901261901.LAA18345@dingo.cdrom.com>
X-Mailer: exmh version 2.0.2 2/24/98
To: David Wolfskill <dhw@whistle.com>
cc: freebsd-current@FreeBSD.ORG, meyerd1@fang.cs.sunyit.edu,
bonnetf@bart.esiee.fr
Subject: Re: NIS with HPUX 10.20
In-reply-to: Your message of "Tue, 26 Jan 1999 09:51:05 PST."
<199901261751.JAA05102@pau-amma.whistle.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Tue, 26 Jan 1999 11:01:25 -0800
From: Mike Smith <mike@smith.net.au>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
>
> On the other hand, it seems that the /usr/libexec/ld-elf.so.1 was *not*
> modified by the "make world" process; I thought that odd.
Read the install(1) manpage, particularly the -C option.
--
\\ Sometimes you're ahead, \\ Mike Smith
\\ sometimes you're behind. \\ mike@smith.net.au
\\ The race is long, and in the \\ msmith@freebsd.org
\\ end it's only with yourself. \\ msmith@cdrom.com
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Tue Jan 26 11:06:35 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id LAA16243
for freebsd-current-outgoing; Tue, 26 Jan 1999 11:06:35 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.95.76.54])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA16238
for <freebsd-current@FreeBSD.ORG>; Tue, 26 Jan 1999 11:06:34 -0800 (PST)
(envelope-from sgk@troutmask.apl.washington.edu)
Received: (from sgk@localhost)
by troutmask.apl.washington.edu (8.9.1/8.9.1) id LAA06277;
Tue, 26 Jan 1999 11:07:42 -0800 (PST)
(envelope-from sgk)
From: Steve Kargl <sgk@troutmask.apl.washington.edu>
Message-Id: <199901261907.LAA06277@troutmask.apl.washington.edu>
Subject: Re: removing f2c from base distribution
In-Reply-To: <199901261853.KAA18216@dingo.cdrom.com> from Mike Smith at "Jan 26, 1999 10:53: 4 am"
To: mike@smith.net.au (Mike Smith)
Date: Tue, 26 Jan 1999 11:07:42 -0800 (PST)
Cc: nate@mt.sri.com, freebsd-current@FreeBSD.ORG, jkh@time.cdrom.com
X-Mailer: ELM [version 2.4ME+ PL43 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
Mike Smith wrote:
> > > Ladies and Gents,
> > >
> > > I have completed the portification of f2c and its support library.
> >
> > Who is going to pick this up? Last time I volunteered, Jordan balked at
> > the idea.
>
> I was among the people that asked Steve to do the work; I'd have no
> trouble with you doing the integration/extraction. You might just
> want to check that the recent alpha-related changes that were submitted
> for f2c are covered in the portified version.
>
Yes, I have included the recent patch to f2c.h in the port.
In the Makefile file in lang/f2c-freebsd, you'll find:
.if (${ARCH} == "alpha")
pre-configure:
@cp files/f2c.h.alpha ${WRKSRC}/f2c/f2c.h
.endif
Someday, I'll install FreeBSD on my alphastation, and then
I'll be able to test i386 and alpha architectures.
--
Steve
finger kargl@troutmask.apl.washington.edu
http://troutmask.apl.washington.edu/~clesceri/kargl.html
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Tue Jan 26 11:09:54 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id LAA16478
for freebsd-current-outgoing; Tue, 26 Jan 1999 11:09:54 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA16469
for <current@FreeBSD.ORG>; Tue, 26 Jan 1999 11:09:51 -0800 (PST)
(envelope-from dillon@apollo.backplane.com)
Received: (from dillon@localhost)
by apollo.backplane.com (8.9.2/8.9.1) id LAA20725;
Tue, 26 Jan 1999 11:09:50 -0800 (PST)
(envelope-from dillon)
Date: Tue, 26 Jan 1999 11:09:50 -0800 (PST)
From: Matthew Dillon <dillon@apollo.backplane.com>
Message-Id: <199901261909.LAA20725@apollo.backplane.com>
To: current@FreeBSD.ORG
Subject: /usr/src/share/examples/diskless committed
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
This shows, in general, how a diskless configuration can be setup
using rc.diskless.
This directory also contains information on templating ( though I haven't
comitted cpdup yet so it isn't as useful as it could be ).
It obviously needs a lot of work, committers should feel free to commit
updates to the documentation & examples.
-Matt
Matthew Dillon
<dillon@backplane.com>
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Tue Jan 26 11:31:25 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id LAA18709
for freebsd-current-outgoing; Tue, 26 Jan 1999 11:31:25 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from awfulhak.org (awfulhak.force9.co.uk [195.166.136.63])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA18697
for <current@FreeBSD.ORG>; Tue, 26 Jan 1999 11:31:19 -0800 (PST)
(envelope-from brian@Awfulhak.org)
Received: from keep.lan.Awfulhak.org (brian@keep.lan.Awfulhak.org [172.16.0.8])
by awfulhak.org (8.8.8/8.8.8) with ESMTP id TAA29798;
Tue, 26 Jan 1999 19:30:44 GMT
(envelope-from brian@Awfulhak.org)
Received: from keep.lan.Awfulhak.org (brian@localhost [127.0.0.1])
by keep.lan.Awfulhak.org (8.9.2/8.9.2) with ESMTP id IAA34557;
Tue, 26 Jan 1999 08:21:14 GMT
(envelope-from brian@keep.lan.Awfulhak.org)
Message-Id: <199901260821.IAA34557@keep.lan.Awfulhak.org>
X-Mailer: exmh version 2.0.2 2/24/98
To: Alexander Sanda <entropy@compufit.at>
cc: current@FreeBSD.ORG
Subject: Re: PPP (userland) troubles ?
In-reply-to: Your message of "Tue, 26 Jan 1999 02:56:53 +0100."
<Pine.BSF.4.05.9901260204010.24456-100000@darkstar.vmx>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Tue, 26 Jan 1999 08:21:14 +0000
From: Brian Somers <brian@Awfulhak.org>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
> Hi!
>
> I'am not sure where this comes from, but at the moment I have some
> troubles with the userland ppp.
>
> The symptoms: After establishing the connection and setting the
> defaultroute *nothing* works, that means, the line seems
> to be completely dead. Not even the peer can be pinged.
> However, after a short while the symptoms vanish and
> everything is as it should be. I don't believe in faults
> at my provider, since I tested it with different accounts
> and basically got the same results.
>
> Sometimes when I try to ping the peer, I get some "sendto:
> no buffer space available" messages before the reply
> packets start to drop in.
>
> Config: (very)-current, everything ELF, ppp via plain and simple modem
> dialup.
Are you using a routing daemon ? Also, have you tried just having
``add default HISADDR'' in ppp.conf and leaving everything out of
ppp.linkup ? What do your routing tables look like before/during/after
the hang ?
> --
> # /AS/ http://privat.schlund.de/entropy/ #
> # #
> # XX has detected, that your mouse cursor has changed position. Please #
> # restart XX, so it can be updated. -- From The Gimp manual #
--
Brian <brian@Awfulhak.org> <brian@FreeBSD.org> <brian@OpenBSD.org>
<http://www.Awfulhak.org>
Don't _EVER_ lose your sense of humour !
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Tue Jan 26 11:35:17 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id LAA19387
for freebsd-current-outgoing; Tue, 26 Jan 1999 11:35:17 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from ns.mt.sri.com (sri-gw.MT.net [206.127.105.141])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA19380
for <freebsd-current@FreeBSD.ORG>; Tue, 26 Jan 1999 11:35:14 -0800 (PST)
(envelope-from nate@mt.sri.com)
Received: from mt.sri.com (rocky.mt.sri.com [206.127.76.100])
by ns.mt.sri.com (8.8.8/8.8.8) with SMTP id MAA24691;
Tue, 26 Jan 1999 12:35:08 -0700 (MST)
(envelope-from nate@rocky.mt.sri.com)
Received: by mt.sri.com (SMI-8.6/SMI-SVR4)
id MAA13403; Tue, 26 Jan 1999 12:35:07 -0700
Date: Tue, 26 Jan 1999 12:35:07 -0700
Message-Id: <199901261935.MAA13403@mt.sri.com>
From: Nate Williams <nate@mt.sri.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
To: Mike Smith <mike@smith.net.au>
Cc: Nate Williams <nate@mt.sri.com>,
Steve Kargl <sgk@troutmask.apl.washington.edu>,
freebsd-current@FreeBSD.ORG, jkh@time.cdrom.com
Subject: Re: removing f2c from base distribution
In-Reply-To: <199901261853.KAA18216@dingo.cdrom.com>
References: <199901261623.JAA12330@mt.sri.com>
<199901261853.KAA18216@dingo.cdrom.com>
X-Mailer: VM 6.34 under 19.16 "Lille" XEmacs Lucid
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
> > > Ladies and Gents,
> > >
> > > I have completed the portification of f2c and its support library.
> >
> > Who is going to pick this up? Last time I volunteered, Jordan balked at
> > the idea.
>
> I was among the people that asked Steve to do the work; I'd have no
> trouble with you doing the integration/extraction.
Agreed, I also thought this was a good idea.
> You might just want to check that the recent alpha-related changes
> that were submitted for f2c are covered in the portified version.
Apparently so. I can't do it *right now* as I don't have a 3.0 box
handy, but I should by this weekend.
Nate
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Tue Jan 26 11:39:23 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id LAA19746
for freebsd-current-outgoing; Tue, 26 Jan 1999 11:39:23 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA19718;
Tue, 26 Jan 1999 11:39:12 -0800 (PST)
(envelope-from julian@whistle.com)
Received: (from daemon@localhost)
by alpo.whistle.com (8.8.5/8.8.5) id LAA22469;
Tue, 26 Jan 1999 11:28:21 -0800 (PST)
Received: from s204m82.isp.whistle.com(207.76.204.82)
via SMTP by alpo.whistle.com, id smtpdF22465; Tue Jan 26 19:28:20 1999
Date: Tue, 26 Jan 1999 11:28:17 -0800 (PST)
From: Julian Elischer <julian@whistle.com>
X-Sender: julian@s204m82.isp.whistle.com
To: S?ren Schmidt <sos@freebsd.dk>
cc: Poul-Henning Kamp <phk@FreeBSD.ORG>, current@FreeBSD.ORG
Subject: Re: wd0: DMA failure, DMA status 0
In-Reply-To: <199901261317.OAA31728@freebsd.dk>
Message-ID: <Pine.BSF.4.05.9901261123160.69443-100000@s204m82.isp.whistle.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
hmm I have a suspicion that this breaks the cyrix chip
I hope we don't have a situation where no answer can run on both hardware!
I'll get back to you as soon as I've tested it..
The cyrix chip causes the code to go into that clause regularly when it's
interrupting
and if I don't let it continue, it just hangs forever.
the register hasn't yet had time to show the interrupt or something.....
I'll work on it a bit more and try narrow it down. (I meant to spend more
time on it but forgot)
On Tue, 26 Jan 1999, S?ren Schmidt wrote:
> It seems Poul-Henning Kamp wrote:
> >
> >
> > Is "wd0: DMA failure, DMA status 0" something which needs looked at ?
>
> Blame Julian, he broke it in v 1.183 of wd.c, the following patch
> works on all my HW, but I dont have the "cyrix" chipset Julian
> made the patch for, to test it on (it also contains other small
> corrections mostly from Bruce)...
>
>
> Index: wd.c
> ===================================================================
> RCS file: /home/ncvs/src/sys/i386/isa/wd.c,v
> retrieving revision 1.186
> diff -u -r1.186 wd.c
> --- wd.c 1999/01/17 05:46:24 1.186
> +++ wd.c 1999/01/19 18:29:23
> @@ -1084,10 +1086,11 @@
> du = wddrives[dkunit(bp->b_dev)];
>
> /* finish off DMA */
> - if (du->dk_flags & (DKFL_DMA|DKFL_USEDMA)) {
> + if ((du->dk_flags & (DKFL_DMA|DKFL_SINGLE)) == DKFL_DMA) {
> /* XXX SMP boxes sometimes generate an early intr. Why? */
> - if ((wddma[du->dk_interface].wdd_dmastatus(du->dk_dmacookie) & WDDS_INTERRUPT)
> - != 0)
> + if ((wddma[du->dk_interface].wdd_dmastatus(du->dk_dmacookie) &
> + WDDS_INTERRUPT) == 0)
> + return;
> dmastat = wddma[du->dk_interface].wdd_dmadone(du->dk_dmacookie);
> }
>
> @@ -1568,6 +1571,7 @@
> if (wdwait(du, 0, TIMEOUT) < 0)
> return (1);
> if( command == WDCC_FEATURES) {
> + outb(wdc + wd_sdh, WDSD_IBM | (du->dk_unit << 4) | head);
> outb(wdc + wd_features, count);
> if ( count == WDFEA_SETXFER )
> outb(wdc + wd_seccnt, sector);
> @@ -2289,9 +2293,8 @@
> {
> int err = 0;
>
> - if ((du->dk_flags & (DKFL_DMA|DKFL_USEDMA)) && du->dk_dmacookie)
> + if ((du->dk_flags & (DKFL_DMA|DKFL_SINGLE)) == DKFL_DMA)
> wddma[du->dk_interface].wdd_dmadone(du->dk_dmacookie);
> -
> (void)wdwait(du, 0, TIMEOUT);
> outb(du->dk_altport, WDCTL_IDS | WDCTL_RST);
> DELAY(10 * 1000);
>
>
> To Unsubscribe: send mail to majordomo@FreeBSD.org
> with "unsubscribe freebsd-current" in the body of the message
>
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Tue Jan 26 11:41:06 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id LAA20081
for freebsd-current-outgoing; Tue, 26 Jan 1999 11:41:06 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from po3.wam.umd.edu (po3.wam.umd.edu [128.8.10.165])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA19670
for <freebsd-current@freebsd.org>; Tue, 26 Jan 1999 11:38:26 -0800 (PST)
(envelope-from culverk@wam.umd.edu)
Received: from rac5.wam.umd.edu ((IDENT root)@rac5.wam.umd.edu [128.8.10.145])
by po3.wam.umd.edu (8.9.0.Beta6/8.9.0.Beta6) with ESMTP id OAA08745
for <freebsd-current@freebsd.org>; Tue, 26 Jan 1999 14:38:15 -0500 (EST)
Received: from rac5.wam.umd.edu ((IDENT sendmail)@localhost [127.0.0.1])
by rac5.wam.umd.edu (8.9.0.Beta6/8.9.0.Beta6) with SMTP id OAA10930
for <freebsd-current@freebsd.org>; Tue, 26 Jan 1999 14:38:14 -0500 (EST)
Received: from localhost by rac5.wam.umd.edu (8.9.0.Beta6/8.9.0.Beta6) with SMTP id OAA10925
for <freebsd-current@freebsd.org>; Tue, 26 Jan 1999 14:38:12 -0500 (EST)
X-Authentication-Warning: rac5.wam.umd.edu: culverk owned process doing -bs
Date: Tue, 26 Jan 1999 14:38:12 -0500 (EST)
From: Kenneth Wayne Culver <culverk@wam.umd.edu>
To: freebsd-current@FreeBSD.ORG
Subject: linux kld
Message-ID: <Pine.GSO.3.95q.990126143611.10812A-100000@rac5.wam.umd.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
when my computer starts up (just finished make world 5 minutes ago) I get
the following error:
link_elf: symbol grow undefined.
does this mean that the linux emu is broken right now?
Kenneth Culver
Computer Science Major at the University of Maryland, College Park.
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Tue Jan 26 12:00:16 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id MAA22283
for freebsd-current-outgoing; Tue, 26 Jan 1999 12:00:16 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from relay.nuxi.com (nuxi.cs.ucdavis.edu [128.120.56.38])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA22278
for <freebsd-current@FreeBSD.ORG>; Tue, 26 Jan 1999 12:00:14 -0800 (PST)
(envelope-from obrien@NUXI.com)
Received: (from obrien@localhost)
by relay.nuxi.com (8.9.1/8.9.1) id MAA60040;
Tue, 26 Jan 1999 12:00:06 -0800 (PST)
(envelope-from obrien)
Date: Tue, 26 Jan 1999 12:00:06 -0800
From: "David O'Brien" <obrien@NUXI.com>
To: Mike Smith <mike@smith.net.au>
Cc: freebsd-current@FreeBSD.ORG
Subject: Re: removing f2c from base distribution
Message-ID: <19990126120006.A60006@relay.nuxi.com>
Reply-To: obrien@NUXI.com
References: <199901261623.JAA12330@mt.sri.com> <199901261853.KAA18216@dingo.cdrom.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.95i
In-Reply-To: <199901261853.KAA18216@dingo.cdrom.com>; from Mike Smith on Tue, Jan 26, 1999 at 10:53:04AM -0800
X-Operating-System: FreeBSD 3.0-CURRENT
Organization: The NUXI BSD group
X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A
X-Pgp-Keyid: 34F9F9D5
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
> I was among the people that asked Steve to do the work; I'd have no
> trouble with you doing the integration/extraction. You might just
> want to check that the recent alpha-related changes that were submitted
> for f2c are covered in the portified version.
This might be a good time to bring this up.
Might we create src/opt/ where things we are used to maintaining can be
put? Nightly the latest src/opt/foo can be checked out and tarred up.
This way everyone can still work on and commit fixes to this software.
Just as happened for the Alpha. With a tarball sitting outside of the
FreeBSD world, it is hard to be as responsible for the code.
Alternately, I guess we could just have the code live in
/usr/ports/lang/f2c/src/, but I don't know if Satoshi wants /usr/ports
to expand like that.
--
-- David (obrien@NUXI.com -or- obrien@FreeBSD.org)
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Tue Jan 26 12:21:41 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id MAA24569
for freebsd-current-outgoing; Tue, 26 Jan 1999 12:21:41 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from ns.tar.com (ns.tar.com [204.95.187.2])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA24563
for <freebsd-current@FreeBSD.ORG>; Tue, 26 Jan 1999 12:21:39 -0800 (PST)
(envelope-from dick@ns.tar.com)
Received: (from dick@localhost)
by ns.tar.com (8.9.2/8.9.1) id OAA72401;
Tue, 26 Jan 1999 14:09:20 -0600 (CST)
(envelope-from dick)
Date: Tue, 26 Jan 1999 14:09:20 -0600
From: "Richard Seaman, Jr." <dick@tar.com>
To: Kenneth Wayne Culver <culverk@wam.umd.edu>
Cc: freebsd-current@FreeBSD.ORG
Subject: Re: linux kld
Message-ID: <19990126140919.D478@tar.com>
References: <Pine.GSO.3.95q.990126143611.10812A-100000@rac5.wam.umd.edu>
Mime-Version: 1.0
Content-Type: multipart/mixed; boundary="PEIAKu/WMn1b1Hv9"
X-Mailer: Mutt 0.95i
In-Reply-To: <Pine.GSO.3.95q.990126143611.10812A-100000@rac5.wam.umd.edu>; from Kenneth Wayne Culver on Tue, Jan 26, 1999 at 02:38:12PM -0500
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
--PEIAKu/WMn1b1Hv9
Content-Type: text/plain; charset=us-ascii
On Tue, Jan 26, 1999 at 02:38:12PM -0500, Kenneth Wayne Culver wrote:
> when my computer starts up (just finished make world 5 minutes ago) I get
> the following error:
>
> link_elf: symbol grow undefined.
>
> does this mean that the linux emu is broken right now?
I think it means there is a goof in some changes I sent to Julian
that he committed. If you want a quick fix, try applying the
attached patch, drop into the /usr/src/sys/modules/linux directory
and do a make clean, make and then make install. Then execute
"linux".
--
Richard Seamman, Jr. email: dick@tar.com
5182 N. Maple Lane phone: 414-367-5450
Chenequa WI 53058 fax: 414-367-5852
--PEIAKu/WMn1b1Hv9
Content-Type: text/plain; charset=us-ascii
Content-Disposition: attachment; filename="linux.kld.fix"
Index: sys/modules/linux/Makefile
===================================================================
RCS file: /home/ncvs/src/sys/modules/linux/Makefile,v
retrieving revision 1.24
diff -c -r1.24 Makefile
*** Makefile 1998/11/12 00:37:39 1.24
--- Makefile 1999/01/26 20:01:52
***************
*** 9,15 ****
OBJS= linux_locore.o
MAN8= linux.8
! CFLAGS+= -DCOMPAT_LINUX #-DDEBUG
EXPORT_SYMS=_linux_mod
CLEANFILES+= vnode_if.h vnode_if.c linux_genassym.o linux_genassym \
linux_assym.h opt_compat.h opt_linux.h opt_vmpage.h
--- 9,15 ----
OBJS= linux_locore.o
MAN8= linux.8
! CFLAGS+= -DCOMPAT_LINUX -DVM_STACK #-DDEBUG
EXPORT_SYMS=_linux_mod
CLEANFILES+= vnode_if.h vnode_if.c linux_genassym.o linux_genassym \
linux_assym.h opt_compat.h opt_linux.h opt_vmpage.h
--PEIAKu/WMn1b1Hv9--
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Tue Jan 26 12:28:09 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id MAA25430
for freebsd-current-outgoing; Tue, 26 Jan 1999 12:28:09 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA25422
for <current@freebsd.org>; Tue, 26 Jan 1999 12:28:05 -0800 (PST)
(envelope-from jdp@polstra.com)
Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13])
by wall.polstra.com (8.9.1/8.9.1) with ESMTP id MAA23338;
Tue, 26 Jan 1999 12:28:00 -0800 (PST)
(envelope-from jdp@polstra.com)
From: John Polstra <jdp@polstra.com>
Received: (from jdp@localhost)
by vashon.polstra.com (8.9.1/8.9.1) id MAA23311;
Tue, 26 Jan 1999 12:27:59 -0800 (PST)
(envelope-from jdp@polstra.com)
Date: Tue, 26 Jan 1999 12:27:59 -0800 (PST)
Message-Id: <199901262027.MAA23311@vashon.polstra.com>
To: archie@whistle.com
Subject: Re: libbind, etc.
Newsgroups: polstra.freebsd.current
In-Reply-To: <199901252243.OAA18272@bubba.whistle.com>
Organization: Polstra & Co., Seattle, WA
Cc: current@FreeBSD.ORG
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
In article <199901252243.OAA18272@bubba.whistle.com>,
Archie Cobbs <archie@whistle.com> wrote:
> Right now we build libbind (so named, etc. can link) but don't
> install it in /usr/lib.
>
> However, there are parts of it that would be very nice to have
> available to user programs.. in particular the event library
> (see: "nroff -man /usr/src/contrib/bind/lib/isc/eventlib.mdoc" )
I think the event library is quite nice. I'd like to see it get
installed so that it's available for more general use.
John
--
John Polstra jdp@polstra.com
John D. Polstra & Co., Inc. Seattle, Washington USA
"Nobody ever went broke underestimating the taste of the American public."
-- H. L. Mencken
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Tue Jan 26 12:31:59 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id MAA25785
for freebsd-current-outgoing; Tue, 26 Jan 1999 12:31:59 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from po4.wam.umd.edu (po4.wam.umd.edu [128.8.10.166])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA25780
for <freebsd-current@freebsd.org>; Tue, 26 Jan 1999 12:31:58 -0800 (PST)
(envelope-from culverk@wam.umd.edu)
Received: from rac4.wam.umd.edu ((IDENT root)@rac4.wam.umd.edu [128.8.10.144])
by po4.wam.umd.edu (8.9.0.Beta6/8.9.0.Beta6) with ESMTP id PAA28667
for <freebsd-current@freebsd.org>; Tue, 26 Jan 1999 15:31:53 -0500 (EST)
Received: from rac4.wam.umd.edu ((IDENT sendmail)@localhost [127.0.0.1])
by rac4.wam.umd.edu (8.9.0.Beta6/8.9.0.Beta6) with SMTP id PAA19527
for <freebsd-current@freebsd.org>; Tue, 26 Jan 1999 15:31:51 -0500 (EST)
Received: from localhost by rac4.wam.umd.edu (8.9.0.Beta6/8.9.0.Beta6) with SMTP id PAA19493
for <freebsd-current@freebsd.org>; Tue, 26 Jan 1999 15:31:50 -0500 (EST)
X-Authentication-Warning: rac4.wam.umd.edu: culverk owned process doing -bs
Date: Tue, 26 Jan 1999 15:31:49 -0500 (EST)
From: Kenneth Wayne Culver <culverk@wam.umd.edu>
To: freebsd-current@FreeBSD.ORG
Subject: pam_kerberosIV.so
Message-ID: <Pine.GSO.3.95q.990126153100.19296A-100000@rac4.wam.umd.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
I was wondering if this module was known to be broken, because I can't get
it to work...
Kenneth Culver
Computer Science Major at the University of Maryland, College Park.
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Tue Jan 26 12:48:03 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id MAA27670
for freebsd-current-outgoing; Tue, 26 Jan 1999 12:48:03 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from pcpsj.pfcs.com (harlan.clark.net [168.143.10.179])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA27596
for <current@FreeBSD.ORG>; Tue, 26 Jan 1999 12:47:59 -0800 (PST)
(envelope-from Harlan.Stenn@pfcs.com)
Received: from mumps.pfcs.com [192.52.69.11] (HELO mumps.pfcs.com)
by pcpsj.pfcs.com (8.8.8/8.8.8) via ESMTP
id <PAA05495-Harlan.Stenn@pfcs.com>;
Tue, 26 Jan 1999 15:47:39 -0500 (EST)
Received: from brown.pfcs.com [192.52.69.44] (HELO brown.pfcs.com)
by mumps.pfcs.com (8.8.8/8.8.8) via ESMTP
id <MAA26647-harlan@pfcs.com>;
Tue, 26 Jan 1999 12:47:38 -0800 (PST)
Received: from localhost [127.0.0.1] (HELO brown.pfcs.com)
by brown.pfcs.com (8.8.8/8.8.8) via ESMTP
id <PAA16578-harlan@pfcs.com>;
Tue, 26 Jan 1999 15:47:02 -0500 (EST)
X-Mailer: exmh version 2.0.2 2/24/98
To: John Polstra <jdp@polstra.com>
cc: archie@whistle.com, current@FreeBSD.ORG
Subject: Re: libbind, etc.
In-Reply-To: John Polstra's (jdp@polstra.com) message
dated Tue, 26 Jan 1999 12:27:59. <199901262027.MAA23311@vashon.polstra.com>
X-Face: "csXK}xnnsH\h_ce`T#|pM]tG,6Xu.{3Rb\]&XJgVyTS'w{E+|-(}n<m88'RZQA.<2]zo&R
I8nHuPumSNjsAN&WGhll?v}1#%)~2%QI~4Vs%IuWb#OmZmKck_1Ee&C\k&vJ}BWx:Bb#Mx8>:c(Cc*
$cbtusxDP6T)Hr'k&zrwq0.3&~bAI~YJco[r.mE+K|(q]F=ZNXug:s6tyOk{VTqARy0#axm6BWti9C
d
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Tue, 26 Jan 1999 15:47:02 -0500
Message-ID: <16576.917383622@brown.pfcs.com>
From: Harlan Stenn <Harlan.Stenn@pfcs.com>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
I believe an upgrade to the eventlib is coming Real Soon Now.
I'm not sure about this - it might have been the logging module.
H
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Tue Jan 26 13:35:16 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id NAA03629
for freebsd-current-outgoing; Tue, 26 Jan 1999 13:35:16 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.95.76.54])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA03614
for <freebsd-current@FreeBSD.ORG>; Tue, 26 Jan 1999 13:35:11 -0800 (PST)
(envelope-from sgk@troutmask.apl.washington.edu)
Received: (from sgk@localhost)
by troutmask.apl.washington.edu (8.9.1/8.9.1) id NAA07056;
Tue, 26 Jan 1999 13:36:21 -0800 (PST)
(envelope-from sgk)
From: Steve Kargl <sgk@troutmask.apl.washington.edu>
Message-Id: <199901262136.NAA07056@troutmask.apl.washington.edu>
Subject: Re: removing f2c from base distribution
In-Reply-To: <19990126120006.A60006@relay.nuxi.com> from "David O'Brien" at "Jan 26, 1999 12: 0: 6 pm"
To: obrien@NUXI.com
Date: Tue, 26 Jan 1999 13:36:21 -0800 (PST)
Cc: mike@smith.net.au, freebsd-current@FreeBSD.ORG
X-Mailer: ELM [version 2.4ME+ PL43 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
David O'Brien wrote:
> > I was among the people that asked Steve to do the work; I'd have no
> > trouble with you doing the integration/extraction. You might just
> > want to check that the recent alpha-related changes that were submitted
> > for f2c are covered in the portified version.
>
> This might be a good time to bring this up.
> Might we create src/opt/ where things we are used to maintaining can be
> put? Nightly the latest src/opt/foo can be checked out and tarred up.
I agree that there is a gray area between base distribution and
ports. Sendmail, postfix, tcl, and others fall into this gray area.
I think f2c falls into the ports catagory because it is not under
active development (although it is actively maintained) and updating
a port every few months seems reasonable.
> Alternately, I guess we could just have the code live in
> /usr/ports/lang/f2c/src/, but I don't know if Satoshi wants /usr/ports
> to expand like that.
I think that this is a Bad Idea(tm) even if Satoshi does not. This would
still require someone looking over the GNATS database for changes to the
software, and then having someone with commit privelege willing to deal
with the PR.
Each Makefile under the ports systems contains a maintainer line. I
do not think it unreasonable for someone to send patchs directly to the
maintainer.
--
Steve
finger kargl@troutmask.apl.washington.edu
http://troutmask.apl.washington.edu/~clesceri/kargl.html
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Tue Jan 26 13:37:19 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id NAA03846
for freebsd-current-outgoing; Tue, 26 Jan 1999 13:37:19 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from verdi.nethelp.no (verdi.nethelp.no [158.36.41.162])
by hub.freebsd.org (8.8.8/8.8.8) with SMTP id NAA03839
for <current@FreeBSD.ORG>; Tue, 26 Jan 1999 13:37:14 -0800 (PST)
(envelope-from sthaug@nethelp.no)
From: sthaug@nethelp.no
Received: (qmail 6225 invoked by uid 1001); 26 Jan 1999 21:37:11 +0000 (GMT)
To: Harlan.Stenn@pfcs.com
Cc: jdp@polstra.com, archie@whistle.com, current@FreeBSD.ORG
Subject: Re: libbind, etc.
In-Reply-To: Your message of "Tue, 26 Jan 1999 15:47:02 -0500"
References: <16576.917383622@brown.pfcs.com>
X-Mailer: Mew version 1.05+ on Emacs 19.34.2
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Date: Tue, 26 Jan 1999 22:37:11 +0100
Message-ID: <6223.917386631@verdi.nethelp.no>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
> I believe an upgrade to the eventlib is coming Real Soon Now.
>
> I'm not sure about this - it might have been the logging module.
BIND 8.2 is currently in alpha testing, and has some changes in
eventlib compared to BIND 8.1.2. As far as I can see, there are minor
differences in
eventlib.c
logging.c
memcluster.c
and there are new routines to handle a "control channel" in
ctl_clnt.c
ctl_p.c
ctl_p.h
ctl_srvr.c
I would suggest simply using eventlib from BIND 8.1.2 for now, and
wait until the BIND 8.2 changes have seen some more use.
Steinar Haug, Nethelp consulting, sthaug@nethelp.no
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Tue Jan 26 13:37:33 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id NAA03888
for freebsd-current-outgoing; Tue, 26 Jan 1999 13:37:33 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from relay.nuxi.com (nuxi.cs.ucdavis.edu [128.120.56.38])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA03870
for <freebsd-current@FreeBSD.ORG>; Tue, 26 Jan 1999 13:37:28 -0800 (PST)
(envelope-from obrien@NUXI.com)
Received: (from obrien@localhost)
by relay.nuxi.com (8.9.1/8.9.1) id NAA60796;
Tue, 26 Jan 1999 13:37:26 -0800 (PST)
(envelope-from obrien)
Date: Tue, 26 Jan 1999 13:37:26 -0800
From: "David O'Brien" <obrien@NUXI.com>
To: Steve Kargl <sgk@troutmask.apl.washington.edu>
Cc: freebsd-current@FreeBSD.ORG
Subject: Re: removing f2c from base distribution
Message-ID: <19990126133726.D48745@relay.nuxi.com>
Reply-To: obrien@NUXI.com
References: <19990126120006.A60006@relay.nuxi.com> <199901262136.NAA07056@troutmask.apl.washington.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.95i
In-Reply-To: <199901262136.NAA07056@troutmask.apl.washington.edu>; from Steve Kargl on Tue, Jan 26, 1999 at 01:36:21PM -0800
X-Operating-System: FreeBSD 3.0-CURRENT
Organization: The NUXI BSD group
X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A
X-Pgp-Keyid: 34F9F9D5
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
> Each Makefile under the ports systems contains a maintainer line. I
> do not think it unreasonable for someone to send patchs directly to the
> maintainer.
Except that some maintainers dissapear, and maintainers w/o commit
abilities still have to get someone to update the port for them.
--
-- David (obrien@NUXI.com -or- obrien@FreeBSD.org)
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Tue Jan 26 13:38:37 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id NAA04053
for freebsd-current-outgoing; Tue, 26 Jan 1999 13:38:37 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from assurance.rstcorp.com (assurance.rstcorp.com [206.29.49.3])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA04046
for <freebsd-current@freebsd.org>; Tue, 26 Jan 1999 13:38:34 -0800 (PST)
(envelope-from vshah@rstcorp.com)
Received: (from uucp@localhost)
by assurance.rstcorp.com (8.8.8/8.8.8) id QAA04701
for <freebsd-current@freebsd.org>; Tue, 26 Jan 1999 16:38:33 -0500
Received: from sandbox.rstcorp.com(206.29.49.63) by assurance.rstcorp.com via smap (V2.0)
id xma004693; Tue, 26 Jan 99 16:38:23 -0500
Received: from jabberwock.rstcorp.com (jabberwock [206.29.49.98])
by sandbox.rstcorp.com (8.8.8/8.8.8) with ESMTP id QAA26936
for <freebsd-current@freebsd.org>; Tue, 26 Jan 1999 16:38:17 -0500 (EST)
Received: (from vshah@localhost)
by jabberwock.rstcorp.com (8.9.2/8.8.8) id QAA00748;
Tue, 26 Jan 1999 16:38:21 -0500 (EST)
Date: Tue, 26 Jan 1999 16:38:21 -0500 (EST)
Message-Id: <199901262138.QAA00748@jabberwock.rstcorp.com>
From: "Viren R. Shah" <viren@rstcorp.com>
To: freebsd-current@FreeBSD.ORG
Subject: Problem with loader?
X-Mailer: VM 6.34 under 19.16 "Lille" XEmacs Lucid
Reply-To: "Viren R. Shah" <viren@rstcorp.com>
X-Face: )~y+U*K:yzjz{q<5lzpI_SVef'U.])9g[C9`1N@]u3,MHY7f*l7C)[_NjM4y4K8$uIUh|\u
(K&&HS6,M!61&GMTk'mqmB/Qg]]X}"?TzsFl]"2v!bl8']dma.:^IY^a[lbOI>U:b<~FyK3q-p{HmZ
mn~g.`~BE!5{2D:}Yi+\_KkWe?XaHj9$ko1k8iKLYv5*_2c8"G=?Up[}hn+7RNM(bzBZ_wWk6!Pf&B
?3Tcm7M7B~W%K/I0aX3]*=jP?aM]H6HBPT`oLk+0n^_;N\2\%|Rhy;p}34Q.jEsM\qtnxcm;ag%Nq
Mime-Version: 1.0 (generated by tm-edit 7.106)
Content-Type: text/plain; charset=US-ASCII
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
I just cvsupped (01/26 2pm EST) and made world. After building a new
kernel, and installing new bootblocks, upon boot I get the following
error:
FreeBSD/i386 bootstrap loader Revision 0.2
ficlExecFD: Error at line 1
int=0000000e err=00000004 efl=00010246 eip=0000fda0
[at which point my patience ran out, and I didn't jot down the rest]
I booted with a loader from Jan 19, and it works. Did I goof up
somewhere? or is this a loader bug?
If needed I can boot from the recent loader again, and get the rest of
the register dump.
Viren
--
Viren R. Shah | Everyone was born right-handed.
viren@rstcorp.com | Only the greatest overcome it.
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Tue Jan 26 13:38:54 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id NAA04118
for freebsd-current-outgoing; Tue, 26 Jan 1999 13:38:54 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from darkstar.psa.at (darkstar.psa.at [194.152.163.137])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA04049
for <current@freebsd.org>; Tue, 26 Jan 1999 13:38:36 -0800 (PST)
(envelope-from root@psa.at)
Received: from uvo1-66.univie.ac.at ([131.130.231.66] helo=entropy.quake.at)
by darkstar.psa.at with esmtp (Exim 2.05 #1)
id 105GO3-000387-00; Tue, 26 Jan 1999 22:51:08 +0100
Received: from localhost ([127.0.0.1])
by entropy.quake.at with esmtp (Exim 2.10 #2)
id 105G9P-0000sN-00; Tue, 26 Jan 1999 22:35:59 +0100
Date: Tue, 26 Jan 1999 22:35:59 +0100 (CET)
From: Alexander Sanda <entropy@compufit.at>
X-Sender: root@darkstar.vmx
To: Brian Somers <brian@Awfulhak.org>
cc: current@FreeBSD.ORG
Subject: Re: PPP (userland) troubles ?
In-Reply-To: <199901260821.IAA34557@keep.lan.Awfulhak.org>
Message-ID: <Pine.BSF.4.05.9901262221550.3357-100000@darkstar.vmx>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
On Tue, 26 Jan 1999, Brian Somers wrote:
> Are you using a routing daemon ? Also, have you tried just having
> ``add default HISADDR'' in ppp.conf and leaving everything out of
> ppp.linkup ? What do your routing tables look like before/during/after
> the hang ?
I usually run routed, yes, and it didn't ever affect the
dialup functionality. Disabling routed does not change the behaviour in
any way.
My ppp.linkup doesn't really contain much stuff. The only thing it does
is running the mailqueue.
Also, I have "add default HISADDR" in my ppp.conf. A sample output of
netstat -nr after establishing the connection looks like follows:
[73]root@darkstar:/root #>netstat -nr
Routing tables
Internet:
Destination Gateway Flags Refs Use Netif
Expire
default 131.130.230.14 UGSc 10 1 tun0
127.0.0.1 127.0.0.1 UH 21 1910 lo0
131.130.230.14 131.130.231.66 UH 11 0 tun0
131.130.231.66 127.0.0.1 UH 0 0 lo0
[74]root@darkstar:/root #>
In this case, 131.130.231.66 is the adress assigned to my tun0
interface, 131.130.230.14 is the peer. So this, really looks ok.
To remove any possible influences, I have temporarily removed the lan
configuration (normally, this box has a 3c905 NIC for my littly lan).
In fact, I never had problems like that, they started to show up a few
days ago (a lot of stuff has been commited the last couple of days, and
I also noted small changes to /usr/src/usr.sbin/ppp.
The delay until everything works ok looks like something waits for some
buffer to be filled up, because there is absolutely no modem activity
for the first couple of seconds.
--
# /AS/ http://privat.schlund.de/entropy/ #
# #
# XX has detected, that your mouse cursor has changed position. Please #
# restart XX, so it can be updated. -- From The Gimp manual #
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Tue Jan 26 13:44:14 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id NAA05149
for freebsd-current-outgoing; Tue, 26 Jan 1999 13:44:14 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA05140
for <freebsd-current@FreeBSD.ORG>; Tue, 26 Jan 1999 13:44:11 -0800 (PST)
(envelope-from julian@whistle.com)
Received: (from daemon@localhost)
by alpo.whistle.com (8.8.5/8.8.5) id NAA27980;
Tue, 26 Jan 1999 13:38:15 -0800 (PST)
Received: from current1.whistle.com(207.76.205.22)
via SMTP by alpo.whistle.com, id smtpda27973; Tue Jan 26 21:38:11 1999
Date: Tue, 26 Jan 1999 13:38:06 -0800 (PST)
From: Julian Elischer <julian@whistle.com>
To: Kenneth Wayne Culver <culverk@wam.umd.edu>
cc: freebsd-current@FreeBSD.ORG
Subject: Re: linux kld
In-Reply-To: <Pine.GSO.3.95q.990126143611.10812A-100000@rac5.wam.umd.edu>
Message-ID: <Pine.BSF.3.95.990126133542.9362B-100000@current1.whistle.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
Fixed I think....
add the flag -DVM_STACK to the CFLAGS line in sys/modules/linux/Makefile
(this is checked in now but til you get it this should fix it.
On Tue, 26 Jan 1999, Kenneth Wayne Culver wrote:
> when my computer starts up (just finished make world 5 minutes ago) I get
> the following error:
>
> link_elf: symbol grow undefined.
>
> does this mean that the linux emu is broken right now?
>
> Kenneth Culver
> Computer Science Major at the University of Maryland, College Park.
>
>
>
> To Unsubscribe: send mail to majordomo@FreeBSD.org
> with "unsubscribe freebsd-current" in the body of the message
>
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Tue Jan 26 13:47:26 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id NAA05485
for freebsd-current-outgoing; Tue, 26 Jan 1999 13:47:26 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.95.76.54])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA05477
for <freebsd-current@FreeBSD.ORG>; Tue, 26 Jan 1999 13:47:23 -0800 (PST)
(envelope-from sgk@troutmask.apl.washington.edu)
Received: (from sgk@localhost)
by troutmask.apl.washington.edu (8.9.1/8.9.1) id NAA07097;
Tue, 26 Jan 1999 13:48:42 -0800 (PST)
(envelope-from sgk)
From: Steve Kargl <sgk@troutmask.apl.washington.edu>
Message-Id: <199901262148.NAA07097@troutmask.apl.washington.edu>
Subject: Re: removing f2c from base distribution
In-Reply-To: <19990126133726.D48745@relay.nuxi.com> from "David O'Brien" at "Jan 26, 1999 1:37:26 pm"
To: obrien@NUXI.com
Date: Tue, 26 Jan 1999 13:48:41 -0800 (PST)
Cc: freebsd-current@FreeBSD.ORG
X-Mailer: ELM [version 2.4ME+ PL43 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
David O'Brien wrote:
> > Each Makefile under the ports systems contains a maintainer line. I
> > do not think it unreasonable for someone to send patchs directly to the
> > maintainer.
>
> Except that some maintainers dissapear, and maintainers w/o commit
> abilities still have to get someone to update the port for them.
>
Yes, I recognize that this is problem. A partial solution might
be anoncvs to a shadow tree of the master ports repository. Only
those ports in the shadow tree which satisfy portlint and "make;
make install; make package" would get committed to the master
repository.
Now, if Satoshi has read the above, could someone please revive him
and make sure he takes his heart medication ;-)
--
Steve
finger kargl@troutmask.apl.washington.edu
http://troutmask.apl.washington.edu/~clesceri/kargl.html
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Tue Jan 26 14:48:33 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id OAA13136
for freebsd-current-outgoing; Tue, 26 Jan 1999 14:48:33 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA13122
for <current@freebsd.org>; Tue, 26 Jan 1999 14:48:29 -0800 (PST)
(envelope-from jdp@polstra.com)
Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13])
by wall.polstra.com (8.9.1/8.9.1) with ESMTP id OAA24036;
Tue, 26 Jan 1999 14:48:27 -0800 (PST)
(envelope-from jdp@polstra.com)
From: John Polstra <jdp@polstra.com>
Received: (from jdp@localhost)
by vashon.polstra.com (8.9.1/8.9.1) id OAA23732;
Tue, 26 Jan 1999 14:48:27 -0800 (PST)
(envelope-from jdp@polstra.com)
Date: Tue, 26 Jan 1999 14:48:27 -0800 (PST)
Message-Id: <199901262248.OAA23732@vashon.polstra.com>
To: randy@psg.com
Subject: Re: cvsup build failure
Newsgroups: polstra.freebsd.current
In-Reply-To: <m1052DN-0008G4C@rip.psg.com>
Organization: Polstra & Co., Seattle, WA
Cc: current@FreeBSD.ORG
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
In article <m1052DN-0008G4C@rip.psg.com>, Randy Bush <randy@psg.com> wrote:
> 4.0-current as of today.
>
> i am trying to make cvsup and blooie!
>
> new source -> compiling ../src/TreeComp.m3
> new source -> compiling ../src/FSServer.m3
> new source -> compiling ../src/FSServerU.m3
> new source -> compiling ../src/Main.m3
> -> linking cvsupd
> /usr/lib/aout/crt0.o: file not recognized: File format not recognized
>
> is it to do with having NOAOUT in /etc/make.conf?
No, I think it's probably that you have an old a.out version of the
modula-3 port installed, but now your system is ELF. This should
fix it:
pkg_delete modula-3-3.6 modula-3-lib-3.6 cvsup-15.4.2
Make sure you have up-to-date versions of the cvsup, modula-3,
and modula-3-lib ports.
Make sure neither OBJFORMAT, PORTOBJFORMAT, nor NOCLEANDEPENDS
is set in your environment or in "/etc/make.conf".
cd /usr/ports/net/cvsup
make clean
make install
John
--
John Polstra jdp@polstra.com
John D. Polstra & Co., Inc. Seattle, Washington USA
"Nobody ever went broke underestimating the taste of the American public."
-- H. L. Mencken
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Tue Jan 26 14:50:18 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id OAA13391
for freebsd-current-outgoing; Tue, 26 Jan 1999 14:50:18 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA13381
for <current@freebsd.org>; Tue, 26 Jan 1999 14:50:13 -0800 (PST)
(envelope-from jdp@polstra.com)
Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13])
by wall.polstra.com (8.9.1/8.9.1) with ESMTP id OAA24051;
Tue, 26 Jan 1999 14:50:12 -0800 (PST)
(envelope-from jdp@polstra.com)
From: John Polstra <jdp@polstra.com>
Received: (from jdp@localhost)
by vashon.polstra.com (8.9.1/8.9.1) id OAA23750;
Tue, 26 Jan 1999 14:50:12 -0800 (PST)
(envelope-from jdp@polstra.com)
Date: Tue, 26 Jan 1999 14:50:12 -0800 (PST)
Message-Id: <199901262250.OAA23750@vashon.polstra.com>
To: culverk@wam.umd.edu
Subject: Re: pam_kerberosIV.so
Newsgroups: polstra.freebsd.current
In-Reply-To: <Pine.GSO.3.95q.990126153100.19296A-100000@rac4.wam.umd.edu>
Organization: Polstra & Co., Seattle, WA
Cc: current@FreeBSD.ORG
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
In article <Pine.GSO.3.95q.990126153100.19296A-100000@rac4.wam.umd.edu>,
Kenneth Wayne Culver <culverk@wam.umd.edu> wrote:
> I was wondering if this module was known to be broken, because I can't get
> it to work...
No, it worked when I tested it.
John
--
John Polstra jdp@polstra.com
John D. Polstra & Co., Inc. Seattle, Washington USA
"Nobody ever went broke underestimating the taste of the American public."
-- H. L. Mencken
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Tue Jan 26 15:19:31 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id PAA16182
for freebsd-current-outgoing; Tue, 26 Jan 1999 15:19:31 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from rip.psg.com (rip.psg.com [147.28.0.39])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA16177
for <current@freebsd.org>; Tue, 26 Jan 1999 15:19:30 -0800 (PST)
(envelope-from randy@psg.com)
Received: from localhost (1425 bytes) by rip.psg.com
via sendmail with P:stdio/R:inet_resolve/T:smtp
(sender: <randy>) (ident <randy> using unix)
id <m105HlZ-0008G4C@rip.psg.com>
for <current@freebsd.org>; Tue, 26 Jan 1999 15:19:29 -0800 (PST)
(Smail-3.2.0.101 1997-Dec-17 #1 built 1998-Oct-13)
Message-Id: <m105HlZ-0008G4C@rip.psg.com>
Date: Tue, 26 Jan 1999 15:19:29 -0800 (PST)
From: Randy Bush <randy@psg.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
To: John Polstra <jdp@polstra.com>
Cc: current@FreeBSD.ORG
Subject: Re: cvsup build failure
References: <m1052DN-0008G4C@rip.psg.com>
<199901262248.OAA23732@vashon.polstra.com>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
> In article <m1052DN-0008G4C@rip.psg.com>, Randy Bush <randy@psg.com> wrote:
>> 4.0-current as of today.
>>
>> i am trying to make cvsup and blooie!
>>
>> new source -> compiling ../src/TreeComp.m3
>> new source -> compiling ../src/FSServer.m3
>> new source -> compiling ../src/FSServerU.m3
>> new source -> compiling ../src/Main.m3
>> -> linking cvsupd
>> /usr/lib/aout/crt0.o: file not recognized: File format not recognized
>>
>> is it to do with having NOAOUT in /etc/make.conf?
>
> No, I think it's probably that you have an old a.out version of the
> modula-3 port installed, but now your system is ELF. This should
> fix it:
>
> pkg_delete modula-3-3.6 modula-3-lib-3.6 cvsup-15.4.2
>
> Make sure you have up-to-date versions of the cvsup, modula-3,
> and modula-3-lib ports.
>
> Make sure neither OBJFORMAT, PORTOBJFORMAT, nor NOCLEANDEPENDS
> is set in your environment or in "/etc/make.conf".
>
> cd /usr/ports/net/cvsup
> make clean
> make install
worked. thank you.
randy
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Tue Jan 26 15:34:34 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id PAA17927
for freebsd-current-outgoing; Tue, 26 Jan 1999 15:34:34 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from phantasm.thekeep.org (PHANTASM.ANDREW.CMU.EDU [128.2.36.218])
by hub.freebsd.org (8.8.8/8.8.8) with SMTP id PAA17917
for <freebsd-current@FreeBSD.ORG>; Tue, 26 Jan 1999 15:34:31 -0800 (PST)
(envelope-from dar@thekeep.org)
Received: (qmail 63153 invoked by uid 100); 26 Jan 1999 23:34:30 -0000
Date: Tue, 26 Jan 1999 18:34:30 -0500
From: Dan Root <dar@thekeep.org>
To: freebsd-current@FreeBSD.ORG
Subject: Memory usage weirdness
Message-ID: <19990126183430.A61727@thekeep.org>
Mime-Version: 1.0
Content-Type: multipart/mixed; boundary="pWyiEgJYm5f9v55/"
X-Mailer: Mutt 0.95i
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
--pWyiEgJYm5f9v55/
Content-Type: text/plain; charset=us-ascii
Content-Description: Mail message
What would cause more memory to be considered in the active state than
could be accounted for by running processes?
My main machine (running -current as of the afternoon of Jan 25) has
somewhere between 80 and 100 megs of memory listed as used via ps and top
(which, I presume doesn't take in to account shared executable pages, but
does include the 16 megs the X server is mapping on the video card), yet
both top and vmstat show over 170 megs worth of memory being active.
Furthermore, if I kill off my X session and associated processes, active
memory usage doesn't decrease, even after 5 or more minutes. According to
the vmstat manpage, 20 seconds later, the pages released would be
considered inactive.
Since I was curious, I wrote a small program which scanned the contents of
/proc/*/map and added up the amount of memory supposedly being used by
current processes, to make sure top and ps weren't confused. Sure enough,
the figure was far less than the amount that was being listed active at any
given time, by on the order of anywhere between 50% and 75%.
Is this normal, or should I look for some process that's thrashing through
vast amounts of pages in short periods of time?
(For those who wish to look at it, I've attached output from various
commands such as vmstat, top, ps, the contents of /proc/*/map, plus my
kernel config file)
--
/* Dan Root - XTEA cipher */ static unsigned D=0x9E3779B9,l=0xC6EF3720,s;
/* t=64bit text, k=128bit key */ #define m(x,y) ((x<<4^x>>5)+(x^s)+k[s>>y&3])
void enc(int*t,int*k){for(s=0;s!=+l;){t[0]+=m(t[1],0);s+=D;t[1]+=m(t[0],11);}}
void dec(int*t,int*k){for(s=-l;s==0;){t[1]-=m(t[0],11);s-=D;t[0]-=m(t[1],0);}}
--pWyiEgJYm5f9v55/
Content-Type: text/plain; charset=us-ascii
Content-Description: Output from vmstat -m
Content-Disposition: attachment; filename="vmstat.m"
Memory statistics by bucket size
Size In Use Free Requests HighWater Couldfree
16 180 76 84919 1280 0
32 411 4581 325012 640 6290
64 9208 3016 1154010 320 1103
128 824 6888 184390 160 28831
256 8504 152 317570 80 939
512 36 4 139 40 0
1K 139 281 12795 20 1159
2K 41 5 451 10 165
4K 11 1 1530 5 0
8K 5 26 4182 5 3885
16K 2 0 2 5 0
32K 3 0 3 5 0
64K 7 0 7 5 0
128K 1 0 1 5 0
Memory usage type by bucket size
Size Type(s)
16 kld, devbuf, temp, proc, sysctl, shm, soname, pcb, vnodes,
ether_multi, routetbl
32 kld, sigio, devbuf, temp, pgrp, subproc, sysctl, SWAP, soname, pcb,
cluster_save buffer, vnodes, ifaddr, ether_multi, routetbl, in_multi,
newblk, bmsafemap, indirdep, freefrag, freefile, diradd, mkdir,
dirrem
64 file, lockf, namecache, devbuf, temp, session, iov, shm, soname, pcb,
cluster_save buffer, vnodes, ifaddr, routetbl, pagedep, allocdirect,
allocindir
128 kld, timecounter, file desc, zombie, namecache, devbuf, temp, proc,
cred, ttys, soname, cluster_save buffer, vnodes, ifaddr, routetbl,
inodedep, freeblks, ZONE
256 file desc, devbuf, temp, subproc, vnodes, routetbl, NFS srvsock,
NFS daemon, newblk, FFS node
512 kld, devbuf, temp, proc, ioctlops, BIO buffer, mount, UFS mount
1K kld, devbuf, temp, BIO buffer, NQNFS Lease
2K devbuf, ttys, pcb, BIO buffer, UFS mount, mbuf
4K kld, devbuf, temp, ioctlops, UFS mount
8K kld, temp, pagedep, indirdep, UFS mount
16K devbuf
32K devbuf, temp, SWAP
64K ISOFS mount, kld, NFS hash, inodedep, UFS ihash, UFS quota,
VM pgdata
128K namecache
Memory statistics by type Type Kern
Type InUse MemUse HighUse Limit Requests Limit Limit Size(s)
ISOFS mount 1 64K 64K 40960K 1 0 0 64K
kld 16 79K 84K 40960K 39 0 0 16,32,128,512,1K,4K,8K,64K
timecounter 5 1K 1K 40960K 5 0 0 128
file desc 72 10K 12K 40960K 61972 0 0 128,256
file 183 12K 15K 40960K 603245 0 0 64
sigio 2 1K 1K 40960K 17 0 0 32
zombie 0 0K 1K 40960K 61818 0 0 128
lockf 10 1K 2K 40960K 58364 0 0 64
namecache 8938 688K 784K 40960K 268805 0 0 64,128,128K
devbuf 252 133K 133K 40960K 703 0 0 16,32,64,128,256,512,1K,2K,4K,16K,32K
temp 157 31K 42K 40960K 57270 0 0 16,32,64,128,256,512,1K,4K,8K,32K
pgrp 38 2K 2K 40960K 933 0 0 32
session 33 3K 3K 40960K 567 0 0 64
proc 14 2K 2K 40960K 590 0 0 16,128,512
subproc 77 6K 7K 40960K 123599 0 0 32,256
cred 42 6K 6K 40960K 2908 0 0 128
sysctl 0 0K 1K 40960K 940 0 0 16,32
SWAP 2 21K 21K 40960K 2 0 0 32,32K
ioctlops 0 0K 4K 40960K 4 0 0 512,4K
iov 0 0K 1K 40960K 10 0 0 64
shm 2 1K 1K 40960K 827 0 0 16,64
ttys 641 84K 84K 40960K 2045 0 0 128,2K
soname 10 1K 1K 40960K 74789 0 0 16,32,64,128
pcb 37 5K 5K 40960K 7183 0 0 16,32,64,2K
BIO buffer 160 188K 419K 40960K 12494 0 0 512,1K,2K
cluster_save buffer 0 0K 1K 40960K 9756 0 0 32,64,128
mount 5 3K 3K 40960K 5 0 0 512
vnodes 68 8K 26K 40960K 2973 0 0 16,32,64,128,256
ifaddr 10 1K 1K 40960K 10 0 0 32,64,128
ether_multi 7 1K 1K 40960K 7 0 0 16,32
routetbl 145 19K 29K 40960K 1412 0 0 16,32,64,128,256
in_multi 2 1K 1K 40960K 2 0 0 32
NFS srvsock 2 1K 1K 40960K 2 0 0 256
NFS daemon 1 1K 1K 40960K 1 0 0 256
NQNFS Lease 1 1K 1K 40960K 1 0 0 1K
NFS hash 1 64K 64K 40960K 1 0 0 64K
pagedep 3 9K 24K 40960K 6595 0 0 64,8K
inodedep 5 65K 639K 40960K 41384 0 0 128,64K
newblk 1 1K 1K 40960K 163836 0 0 32,256
bmsafemap 1 1K 2K 40960K 7033 0 0 32
allocdirect 1 1K 166K 40960K 105078 0 0 64
indirdep 0 0K 209K 40960K 7413 0 0 32,8K
allocindir 0 0K 131K 40960K 58757 0 0 64
freefrag 0 0K 9K 40960K 35964 0 0 32
freeblks 0 0K 332K 40960K 13325 0 0 128
freefile 0 0K 82K 40960K 11186 0 0 32
diradd 2 1K 53K 40960K 19268 0 0 32
mkdir 0 0K 6K 40960K 844 0 0 32
dirrem 1 1K 144K 40960K 13384 0 0 32
FFS node 8389 2098K 2130K 40960K 247609 0 0 256
UFS ihash 1 64K 64K 40960K 1 0 0 64K
UFS quota 1 64K 64K 40960K 1 0 0 64K
UFS mount 12 26K 26K 40960K 12 0 0 512,2K,4K,8K
VM pgdata 1 64K 64K 40960K 1 0 0 64K
ZONE 19 3K 3K 40960K 19 0 0 128
mbuf 1 2K 2K 40960K 1 0 0 2K
Memory Totals: In Use Free Requests
3816K 1737K 2085011
--pWyiEgJYm5f9v55/
Content-Type: text/plain; charset=us-ascii
Content-Description: Output from vmstat -s
Content-Disposition: attachment; filename="vmstat.s"
4123448 cpu context switches
23506677 device interrupts
2882703 software interrupts
3789127 traps
46970380 system calls
10 swap pager pageins
10 swap pager pages paged in
17 swap pager pageouts
19 swap pager pages paged out
8357 vnode pager pageins
51568 vnode pager pages paged in
0 vnode pager pageouts
0 vnode pager pages paged out
183 page daemon wakeups
327791 pages examined by the page daemon
164615 pages reactivated
1094388 copy-on-write faults
213960 copy-on-write optimized faults
1604322 zero fill pages zeroed
46244 zero fill pages prezeroed
33 intransit blocking page faults
3550488 total VM faults taken
3719017 pages freed
187 pages freed by daemon
93319 pages freed by exiting processes
43771 pages active
10572 pages inactive
2974 pages in VM cache
5827 pages wired down
876 pages free
4096 bytes per page
4289817 total name lookups
cache hits (84% pos + 8% neg) system 2% per-directory
deletions 0%, falsehits 0%, toolong 0%
--pWyiEgJYm5f9v55/
Content-Type: text/plain; charset=us-ascii
Content-Description: Output from top
Content-Disposition: attachment; filename=top
last pid: 61803; load averages: 0.00, 0.13, 0.13 up 0+20:05:27 17:27:46
56 processes: 1 running, 55 sleeping
Mem: 171M Active, 41M Inact, 23M Wired, 12M Cache, 8319K Buf, 3960K Free
Swap: 64M Total, 192K Used, 64M Free
PID USERNAME PRI NICE SIZE RES STATE C TIME WCPU CPU COMMAND
227 root 2 0 31124K 26664K select 1 12:31 0.15% 0.15% XF86_SVGA
269 dar 10 0 1756K 960K nanslp 0 1:48 0.00% 0.00% wmmixer
268 dar 10 0 1904K 1096K nanslp 1 1:32 0.00% 0.00% wmtime
270 dar 2 0 2692K 1572K select 1 1:21 0.00% 0.00% xterm
278 dar 2 0 1920K 1356K select 1 0:45 0.00% 0.00% screen-3.7.4
260 dar 2 0 2964K 1524K select 0 0:41 0.00% 0.00% wmaker
178 root 2 0 784K 320K select 1 0:21 0.00% 0.00% moused
218 root 2 0 1492K 920K select 1 0:19 0.00% 0.00% zephyrd
279 dar 2 0 1332K 892K select 0 0:16 0.00% 0.00% vt
99 root 2 -12 1040K 544K select 1 0:11 0.00% 0.00% xntpd
52765 root 2 0 3344K 1216K select 0 0:09 0.00% 0.00% httpd
190 qmails 2 0 836K 384K select 0 0:07 0.00% 0.00% qmail-send
94 bind 2 0 1768K 1112K select 1 0:05 0.00% 0.00% named
59890 root 2 0 1108K 528K select 0 0:04 0.00% 0.00% telnetd
59895 jason 2 0 2040K 884K select 0 0:03 0.00% 0.00% zwgc
201 root 2 0 1344K 684K select 1 0:03 0.00% 0.00% sshd1
197 root 2 0 780K 284K select 1 0:02 0.00% 0.00% qmail-lspawn
61222 dar 2 0 1676K 1200K select 0 0:02 0.00% 0.00% ssh1
59891 jason 3 0 1304K 884K ttyin 0 0:02 0.00% 0.00% tcsh
224 root 2 0 2244K 1004K select 0 0:02 0.00% 0.00% xdm
191 qmaill -6 0 768K 324K piperd 0 0:02 0.00% 0.00% cyclog
145 root 10 0 988K 488K nanslp 0 0:02 0.00% 0.00% cron
196 qmaill -6 0 752K 228K piperd 1 0:01 0.00% 0.00% accustamp
280 dar 10 0 1144K 616K wait 1 0:01 0.00% 0.00% rc
52790 root 10 0 1140K 616K wait 0 0:01 0.00% 0.00% rc
220 root 2 0 1020K 564K select 1 0:01 0.00% 0.00% zhm
60354 dar 2 0 1688K 1204K select 0 0:01 0.00% 0.00% ssh1
89 root 2 0 816K 472K select 0 0:01 0.00% 0.00% syslogd
213 root 10 0 848K 420K nanslp 1 0:01 0.00% 0.00% idled
61678 dar 3 0 1132K 772K ttyin 0 0:01 0.00% 0.00% rc
189 qmaild 2 0 792K 344K accept 1 0:01 0.00% 0.00% tcpserver
199 qmailq -6 0 768K 328K piperd 1 0:00 0.00% 0.00% qmail-clean
61727 dar 10 0 1712K 1344K wait 0 0:00 0.00% 0.00% mutt
198 qmailr 2 0 776K 260K select 0 0:00 0.00% 0.00% qmail-rspawn
117 root 2 0 1052K 624K select 1 0:00 0.00% 0.00% kerberos
1 root 10 0 496K 112K wait 1 0:00 0.00% 0.00% init
61489 nobody 2 0 3344K 1440K select 1 0:00 0.00% 0.00% httpd
142 root 2 0 860K 428K select 0 0:00 0.00% 0.00% inetd
53333 dar 10 0 1128K 540K wait 0 0:00 0.00% 0.00% rc
244 dar 10 0 1040K 396K wait 1 0:00 0.00% 0.00% rc
61397 nobody 18 0 3344K 1424K lockf 0 0:00 0.00% 0.00% httpd
61527 nobody 18 0 3344K 1416K lockf 0 0:00 0.00% 0.00% httpd
54589 dar 10 0 1128K 552K wait 1 0:00 0.00% 0.00% rc
61803 root 31 0 1564K 688K CPU1 0 0:00 0.00% 0.00% top
271 dar 10 0 1116K 544K wait 0 0:00 0.00% 0.00% rc
52784 dar 10 0 1128K 548K wait 1 0:00 0.00% 0.00% rc
215 root 2 0 1460K 712K select 1 0:00 0.00% 0.00% xfs
228 root 10 0 2268K 1216K wait 1 0:00 0.00% 0.00% xdm
61729 dar 2 0 1268K 860K select 1 0:00 0.00% 0.00% vim
261 root 2 0 1124K 508K select 0 0:00 0.00% 0.00% kadmind
61582 nobody 18 0 3344K 1404K lockf 0 0:00 0.00% 0.00% httpd
61583 nobody 18 0 3344K 1420K lockf 0 0:00 0.00% 0.00% httpd
60825 dar 18 0 1148K 648K pause 0 0:00 0.00% 0.00% screen-3.7.4
223 root 3 0 824K 468K ttyin 1 0:00 0.00% 0.00% getty
254 dar 2 0 1200K 540K select 1 0:00 0.00% 0.00% ssh-agent1
61728 dar 10 0 496K 184K wait 0 0:00 0.00% 0.00% sh
--pWyiEgJYm5f9v55/
Content-Type: text/plain; charset=us-ascii
Content-Description: Output from dmesg
Content-Disposition: attachment; filename=dmesg
Copyright (c) 1992-1999 FreeBSD Inc.
Copyright (c) 1982, 1986, 1989, 1991, 1993
The Regents of the University of California. All rights reserved.
FreeBSD 4.0-CURRENT #2: Mon Jan 25 20:40:14 EST 1999
dar@phantasm.thekeep.org:/usr/src/sys/compile/PHANTASM
Timecounter "i8254" frequency 1193120 Hz
CPU: Pentium Pro (686-class CPU)
Origin = "GenuineIntel" Id = 0x619 Stepping=9
Features=0xfbff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV>
real memory = 268435456 (262144K bytes)
config> quit
avail memory = 258490368 (252432K bytes)
Programming 24 pins in IOAPIC #0
FreeBSD/SMP: Multiprocessor motherboard
cpu0 (BSP): apic id: 0, version: 0x00040011, at 0xfec08000
cpu1 (AP): apic id: 4, version: 0x00040011, at 0xfec08000
io0 (APIC): apic id: 13, version: 0x00170011, at 0xfec00000
Preloaded elf kernel "kernel" at 0xf02df000.
ccd0-3: Concatenated disk drivers
Probing for devices on PCI bus 0:
chip0: <Intel 82440FX (Natoma) PCI and memory controller> rev 0x02 on pci0.0.0
fxp0: <Intel EtherExpress Pro 10/100B Ethernet> rev 0x01 int a irq 18 on pci0.6.0
fxp0: Ethernet address 00:a0:c9:06:b6:a5
chip1: <Intel 82371SB PCI to ISA bridge> rev 0x01 on pci0.7.0
ide_pci0: <Intel PIIX3 Bus-master IDE controller> rev 0x00 on pci0.7.1
ahc0: <Adaptec aic7880 Ultra SCSI adapter> rev 0x00 int a irq 17 on pci0.9.0
ahc0: aic7880 Wide Channel A, SCSI Id=15, 16/255 SCBs
bt0: <Buslogic Multi-Master SCSI Host Adapter> rev 0x08 int a irq 16 on pci0.11.0
bt0: BT-948 FW Rev. 5.06I Ultra Narrow SCSI Host Adapter, SCSI ID 7, 192 CCBs
vga0: <VGA-compatible display device> rev 0x03 int a irq 19 on pci0.19.0
Probing for PnP devices:
CSN 1 Vendor ID: CSC0b36 [0x360b630e] Serial 0xffffffff Comp ID: @@@0000 [0x00000000]
mss_attach <CS4236>1 at 0x530 irq 5 dma 1:0 flags 0x10
pcm1 (CS423x/Yamaha/AD1816 <CS4236> sn 0xffffffff) at 0x530-0x537 irq 5 drq 1 flags 0x10 on isa
Probing for devices on the ISA bus:
sc0 on isa
sc0: VGA color <16 virtual consoles, flags=0x0>
atkbdc0 at 0x60-0x6f on motherboard
atkbd0 irq 1 on isa
psm0 irq 12 on isa
psm0: model Generic PS/2 mouse, device ID 0
sio0 at 0x3f8-0x3ff irq 4 flags 0x10 on isa
sio0: type 16550A
sio1 at 0x2f8-0x2ff irq 3 on isa
sio1: type 16550A
fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa
wdc0 at 0x1f0-0x1f7 irq 14 flags 0x80ff80ff on isa
wdc0: unit 0 (wd0): <IBM-DTTA-351680>, 32-bit, multi-block-16
wd0: 16124MB (33022080 sectors), 32760 cyls, 16 heads, 63 S/T, 512 B/S
wdc1 at 0x170-0x177 irq 15 flags 0x80ff80ff on isa
wdc1: unit 0 (wd2): <Seagate Technology 1275MB - ST31276A>, 32-bit, multi-block-16
wd2: 1221MB (2501856 sectors), 2482 cyls, 16 heads, 63 S/T, 512 B/S
vga0 at 0x3b0-0x3df maddr 0xa0000 msize 131072 on isa
npx0 on motherboard
npx0: INT 16 interface
joy0 at 0x201 on isa
joy0: joystick
APIC_IO: routing 8254 via 8259 on pin 0
SMP: AP CPU #1 Launched!
sa0 at bt0 bus 0 target 1 lun 0
sa0: <ARCHIVE Python 28388-XXX 5.45> Removable Sequential Access SCSI-2 device
sa0: 6.756MB/s transfers (6.756MHz, offset 15)
changing root device to wd0s1a
ffs_mountfs: superblock updated for soft updates
ffs_mountfs: superblock updated for soft updates
cd0 at bt0 bus 0 target 4 lun 0
cd0: <SONY CD-ROM CDU-76S 1.1c> Removable CD-ROM SCSI-2 device
cd0: 5.0MB/s transfers (5.0MHz, offset 15)
cd0: Attempt to query device size failed: NOT READY, Medium not present
--pWyiEgJYm5f9v55/
Content-Type: text/plain; charset=us-ascii
Content-Description: Output from ps -axlw
Content-Disposition: attachment; filename="ps.axlw"
UID PID PPID CPU PRI NI VSZ RSS WCHAN STAT TT TIME COMMAND
0 0 0 0 -18 0 0 0 sched DLs ?? 0:00.24 (swapper)
0 1 0 0 10 0 496 112 wait Is ?? 0:00.21 /sbin/init --
0 2 0 0 -18 0 0 0 psleep DL ?? 0:04.40 (pagedaemon)
0 3 0 1 18 0 0 0 psleep DL ?? 0:00.00 (vmdaemon)
0 4 0 0 18 0 0 0 syncer DL ?? 1:11.68 (syncer)
0 89 1 0 2 0 816 472 select Ss ?? 0:00.99 syslogd -u
10 94 1 0 2 0 1768 1112 select Ss ?? 0:05.28 named -u bind -g bind
0 99 1 42 2 -12 1040 544 select S<s ?? 0:11.32 xntpd -p /var/run/xntpd.pid
0 142 1 0 2 0 860 460 select Is ?? 0:00.15 inetd
0 145 1 0 10 0 988 488 nanslp Ss ?? 0:01.55 cron
0 178 1 0 2 0 784 320 select Is ?? 0:20.64 moused -p /dev/psm0 -t auto
0 201 1 0 2 0 1344 684 select Is ?? 0:02.54 /usr/local/sbin/sshd (sshd1)
0 213 1 0 10 0 848 488 nanslp Is ?? 0:00.81 /usr/local/libexec/idled
0 218 1 0 2 0 1496 924 select Ss ?? 0:19.32 /usr/local/sbin/zephyrd
0 220 1 1 2 0 1020 556 select Is ?? 0:01.24 /usr/local/sbin/zhm zephyr.thekeep.org
0 224 1 0 2 0 2244 1004 select S ?? 0:01.78 /usr/X11R6/bin/xdm -nodaemon ttyv1
0 227 224 2 28 0 31124 26664 - Rs ?? 12:34.63 /usr/X11R6/bin/X -auth /usr/X11R6/lib/X11/xdm/authdir/authfiles/
0 228 224 109 10 0 2268 1216 wait Is ?? 0:00.06 -:0 (xdm)
100 244 228 109 10 0 1040 396 wait Is ?? 0:00.12 /usr/local/bin/rc /home/dar/.xsession
100 254 1 0 2 0 1200 540 select Is ?? 0:00.01 ssh-agent (ssh-agent1)
100 260 244 0 2 0 2964 1524 select S ?? 0:41.54 wmaker
0 261 1 0 2 0 1124 508 select Is ?? 0:00.05 kadmind
100 268 260 0 10 0 1904 1096 nanslp S ?? 1:32.74 wmtime -digital
100 269 260 0 10 0 1756 960 nanslp S ?? 1:48.73 wmmixer -w -s
0 270 260 0 2 0 2692 1572 select S ?? 1:22.09 xterm
0 278 1 0 2 0 1920 1360 select Ss ?? 0:45.99 SCREEN vt (screen-3.7.4)
0 52765 1 0 2 0 3344 1224 select Ss ?? 0:08.64 /usr/local/sbin/httpd -DSSL
0 59890 142 0 2 0 1108 528 select Ss ?? 0:04.21 telnetd
65534 61397 52765 0 18 0 3344 1444 lockf I ?? 0:00.11 /usr/local/sbin/httpd -DSSL
65534 61489 52765 0 2 0 3344 1460 select I ?? 0:00.17 /usr/local/sbin/httpd -DSSL
65534 61527 52765 0 18 0 3344 1436 lockf I ?? 0:00.11 /usr/local/sbin/httpd -DSSL
65534 61582 52765 0 18 0 3344 1424 lockf I ?? 0:00.04 /usr/local/sbin/httpd -DSSL
65534 61583 52765 0 18 0 3344 1440 lockf I ?? 0:00.04 /usr/local/sbin/httpd -DSSL
0 61829 142 0 2 0 1108 700 select Ss ?? 0:00.10 telnetd
0 61854 142 0 2 0 1108 704 select Ss ?? 0:00.05 telnetd
100 61678 278 0 3 0 1132 772 ttyin Is+ p0 0:00.71 /usr/local/bin/rc
100 271 270 0 10 0 1116 544 wait Is+ p1 0:00.07 rc
100 60825 271 0 18 0 1148 648 pause I+ p1 0:00.02 screen -r (screen-3.7.4)
100 279 278 0 2 0 1332 888 select Is+ p2 0:15.87 vt
100 280 278 0 10 0 1144 620 wait Is+ p3 0:01.30 /usr/local/bin/rc
100 61727 280 0 10 0 1712 1348 wait I+ p3 0:00.41 mutt
100 61728 61727 0 10 0 496 188 wait I+ p3 0:00.01 sh -c vim +/^$ '/tmp/mutt-phantasm-61727-6'
100 61729 61728 0 2 0 1268 860 select I+ p3 0:00.38 vim +/^$ /tmp/mutt-phantasm-61727-6
100 52784 278 0 10 0 1128 548 wait Is+ p4 0:00.07 /usr/local/bin/rc
0 52790 52784 1 10 0 1140 620 wait S+ p4 0:01.41 /usr/local/bin/rc
0 61862 52790 0 28 0 420 236 - R+ p4 0:00.00 ps -axlw
100 54589 278 0 10 0 1128 552 wait Is+ p5 0:00.10 /usr/local/bin/rc
0 61222 54589 0 2 0 1676 1200 select I+ p5 0:02.26 ssh pedantic (ssh1)
100 53333 278 0 10 0 1128 540 wait Is+ p6 0:00.13 /usr/local/bin/rc
0 60354 53333 0 2 0 1688 1204 select I+ p6 0:01.13 ssh pedantic (ssh1)
126 59891 59890 0 3 0 1304 880 ttyin Ss+ p7 0:01.87 -tcsh (tcsh)
126 59895 1 0 2 0 2040 884 select S+ p7 0:02.93 zwgc
116 61830 61829 0 18 0 448 296 pause Is p8 0:00.10 -csh (csh)
116 61833 61830 0 2 0 3404 2092 select S+ p8 0:01.69 (pine)
126 61855 61854 0 3 0 1280 936 ttyin Ss+ p9 0:00.17 -tcsh (tcsh)
0 223 1 0 3 0 824 468 ttyin Is+ v0 0:00.02 /usr/libexec/getty Pc ttyv0
0 117 1 0 2 0 1052 628 select I+ con- 0:00.24 kerberos
82 189 1 0 2 0 792 344 accept I+ con- 0:00.66 /usr/local/bin/tcpserver -u 82 -g 81 0 smtp /var/qmail/bin/qmail
87 190 1 0 2 0 836 384 select I+ con- 0:06.77 qmail-send
83 191 1 0 -6 0 768 324 piperd I+ con- 0:01.58 /usr/local/bin/cyclog -s 512000 -n 10 /var/log/qmail
83 196 190 0 -6 0 752 228 piperd I+ con- 0:01.43 /usr/local/bin/accustamp
0 197 190 0 2 0 780 284 select I+ con- 0:02.49 qmail-lspawn ./.inbox
86 198 190 0 2 0 776 260 select I+ con- 0:00.22 qmail-rspawn
85 199 190 0 -6 0 768 328 piperd I+ con- 0:00.42 qmail-clean
0 215 1 0 2 0 1460 712 select I+ con- 0:00.07 /usr/X11R6/bin/xfs
--pWyiEgJYm5f9v55/
Content-Type: text/plain; charset=us-ascii
Content-Disposition: attachment; filename=PHANTASM
machine "i386"
cpu "I686_CPU"
ident PHANTASM
maxusers 50
options INCLUDE_CONFIG_FILE
options SMP
options APIC_IO
options NCPU=2
options NBUS=2
options NAPIC=1
options NINTR=24
options "MD5"
options "VM86"
options DDB
options PERFMON
options SOFTUPDATES
options QUOTA
options "AUTO_EOI_1"
#options "AUTO_EOI_2"
options "CLK_USE_I8254_CALIBRATION"
options CLK_USE_TSC_CALIBRATION
options AHC_ALLOW_MEMIO
options INET #InterNETworking
options FFS #Berkeley Fast Filesystem
options FFS_ROOT #FFS usable as root device [keep this!]
options MFS #Memory Filesystem
options MFS_ROOT #MFS usable as root device, "MFS" req'ed
options NFS #Network Filesystem
options NFS_ROOT #NFS usable as root device, "NFS" req'ed
options "CD9660"
options PROCFS #Process filesystem
options "COMPAT_43" #Compatible with BSD 4.3 [KEEP THIS!]
options SCSI_DELAY=1500 #Be pessimistic about Joe SCSI device
options UCONSOLE #Allow users to grab the console
options USERCONFIG #boot -c editor
options VISUAL_USERCONFIG #visual boot -c editor
config kernel root on wd0
controller isa0
controller pci0
controller fdc0 at isa? port "IO_FD1" bio irq 6 drq 2
disk fd0 at fdc0 drive 0
options "CMD640" # work around CMD640 chip deficiency
controller wdc0 at isa? port "IO_WD1" bio irq 14 flags 0x80ff80ff
disk wd0 at wdc0 drive 0
disk wd1 at wdc0 drive 1
controller wdc1 at isa? port "IO_WD2" bio irq 15 flags 0x80ff80ff
disk wd2 at wdc1 drive 0
disk wd3 at wdc1 drive 1
controller ahc0
controller bt0
controller scbus0
device da0
device ch0
device cd0
device sa0
device pass0
options "SA_SPACE_TIMEOUT=(15)"
options "SA_REWIND_TIMEOUT=(2*15)"
options "SA_ERASE_TIMEOUT=(4*15)"
#old
#device sc0 at isa? port IO_KBD conflicts tty irq 1
#device psm0 at isa? port IO_KBD conflicts tty irq 12
#new
controller atkbdc0 at isa? port IO_KBD tty
device atkbd0 at isa? tty irq 1
device psm0 at isa? tty irq 12
device vga0 at isa? port ? conflicts
device sc0 at isa? tty
pseudo-device splash
device npx0 at isa? port IO_NPX irq 13
device sio0 at isa? port "IO_COM1" flags 0x10 tty irq 4
device sio1 at isa? port "IO_COM2" tty irq 3
device pnp0
device pcm0
device joy0 at isa? port IO_GAME
device fxp0
pseudo-device loop
pseudo-device ether
pseudo-device vn
pseudo-device snp 2
pseudo-device bpfilter 4
pseudo-device pty 128
pseudo-device gzip # Exec gzipped a.out's
pseudo-device ccd 4
options KTRACE #kernel tracing
options SYSVSHM
options SYSVSEM
options SYSVMSG
options "EXT2FS"
--pWyiEgJYm5f9v55/--
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Tue Jan 26 17:11:56 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id RAA01208
for freebsd-current-outgoing; Tue, 26 Jan 1999 17:11:56 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from vader.cs.berkeley.edu (vader.CS.Berkeley.EDU [128.32.38.234])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA01202
for <freebsd-current@FreeBSD.ORG>; Tue, 26 Jan 1999 17:11:54 -0800 (PST)
(envelope-from asami@vader.cs.berkeley.edu)
Received: from silvia.hip.berkeley.edu (sji-ca13-237.ix.netcom.com [209.109.238.237]) by vader.cs.berkeley.edu (8.8.7/8.7.3) with ESMTP id RAA01030; Tue, 26 Jan 1999 17:11:45 -0800 (PST)
Received: (from asami@localhost) by silvia.hip.berkeley.edu (8.9.1/8.6.9) id RAA63993; Tue, 26 Jan 1999 17:11:36 -0800 (PST)
Date: Tue, 26 Jan 1999 17:11:36 -0800 (PST)
Message-Id: <199901270111.RAA63993@silvia.hip.berkeley.edu>
To: obrien@NUXI.com
CC: mike@smith.net.au, freebsd-current@FreeBSD.ORG
In-reply-to: <19990126120006.A60006@relay.nuxi.com> (obrien@NUXI.com)
Subject: Re: removing f2c from base distribution
From: asami@FreeBSD.ORG (Satoshi Asami)
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
* From: "David O'Brien" <obrien@NUXI.com>
* Alternately, I guess we could just have the code live in
* /usr/ports/lang/f2c/src/, but I don't know if Satoshi wants /usr/ports
* to expand like that.
Eek. I don't think people will appreciate the ports collection
suddenly exploding in size with things like that. (Portlint and
tcpblast are exceptions since they are so small.)
Satoshi
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Tue Jan 26 17:19:27 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id RAA01690
for freebsd-current-outgoing; Tue, 26 Jan 1999 17:19:27 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from vader.cs.berkeley.edu (vader.CS.Berkeley.EDU [128.32.38.234])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA01685
for <freebsd-current@FreeBSD.ORG>; Tue, 26 Jan 1999 17:19:26 -0800 (PST)
(envelope-from asami@vader.cs.berkeley.edu)
Received: from silvia.hip.berkeley.edu (sji-ca13-237.ix.netcom.com [209.109.238.237]) by vader.cs.berkeley.edu (8.8.7/8.7.3) with ESMTP id RAA01037; Tue, 26 Jan 1999 17:16:54 -0800 (PST)
Received: (from asami@localhost) by silvia.hip.berkeley.edu (8.9.1/8.6.9) id RAA64007; Tue, 26 Jan 1999 17:16:45 -0800 (PST)
Date: Tue, 26 Jan 1999 17:16:45 -0800 (PST)
Message-Id: <199901270116.RAA64007@silvia.hip.berkeley.edu>
To: sgk@troutmask.apl.washington.edu
CC: obrien@NUXI.com, freebsd-current@FreeBSD.ORG
In-reply-to: <199901262148.NAA07097@troutmask.apl.washington.edu> (message
from Steve Kargl on Tue, 26 Jan 1999 13:48:41 -0800 (PST))
Subject: Re: removing f2c from base distribution
From: asami@FreeBSD.ORG (Satoshi Asami)
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
* From: Steve Kargl <sgk@troutmask.apl.washington.edu>
* Yes, I recognize that this is problem. A partial solution might
* be anoncvs to a shadow tree of the master ports repository. Only
* those ports in the shadow tree which satisfy portlint and "make;
* make install; make package" would get committed to the master
* repository.
*
* Now, if Satoshi has read the above, could someone please revive him
* and make sure he takes his heart medication ;-)
Um, I'm still alive but can someone explain me why this can't be a
"regular" port? Being useful to some but not the majority, no other
parts of the system depending on it, this looks like a model citizen
in the ideal ports world. :)
Satoshi
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Tue Jan 26 17:21:58 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id RAA02154
for freebsd-current-outgoing; Tue, 26 Jan 1999 17:21:58 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from rip.psg.com (rip.psg.com [147.28.0.39])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA02148
for <freebsd-current@freebsd.org>; Tue, 26 Jan 1999 17:21:56 -0800 (PST)
(envelope-from randy@psg.com)
Received: from localhost (1423 bytes) by rip.psg.com
via sendmail with P:stdio/R:inet_resolve/T:smtp
(sender: <randy>) (ident <randy> using unix)
id <m105Jg3-0008G5C@rip.psg.com>
for <freebsd-current@freebsd.org>; Tue, 26 Jan 1999 17:21:55 -0800 (PST)
(Smail-3.2.0.101 1997-Dec-17 #1 built 1998-Oct-13)
Message-Id: <m105Jg3-0008G5C@rip.psg.com>
Date: Tue, 26 Jan 1999 17:21:55 -0800 (PST)
From: Randy Bush <randy@psg.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
To: freebsd-current@FreeBSD.ORG
Subject: rc.conf breaks rc.conf.local
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
you really want to do something like
rip.psg.com:/usr/src# diff -c /usr/src/etc/rc.conf /etc/rc.conf
*** /usr/src/etc/rc.conf Tue Jan 26 11:55:53 1999
--- /etc/rc.conf Tue Jan 26 17:16:06 1999
***************
*** 19,25 ****
pccard_ifconfig="NO" # Specialized pccard ethernet configuration (or NO).
local_startup="/usr/local/etc/rc.d /usr/X11R6/etc/rc.d" # startup script dirs.
local_periodic="/usr/local/etc/periodic /usr/X11R6/etc/periodic" # periodic script dirs
! rc_conf_files="/etc/rc.conf.site /etc/rc.conf.local"
##############################################################
### Network configuration sub-section ######################
--- 19,25 ----
pccard_ifconfig="NO" # Specialized pccard ethernet configuration (or NO).
local_startup="/usr/local/etc/rc.d /usr/X11R6/etc/rc.d" # startup script dirs.
local_periodic="/usr/local/etc/periodic /usr/X11R6/etc/periodic" # periodic script dirs
! rc_conf_files="rc.conf.site rc.conf.local"
##############################################################
### Network configuration sub-section ######################
***************
*** 205,211 ****
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Tue Jan 26 17:29:19 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id RAA02897
for freebsd-current-outgoing; Tue, 26 Jan 1999 17:29:19 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.95.76.54])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA02887;
Tue, 26 Jan 1999 17:29:17 -0800 (PST)
(envelope-from sgk@troutmask.apl.washington.edu)
Received: (from sgk@localhost)
by troutmask.apl.washington.edu (8.9.1/8.9.1) id RAA08180;
Tue, 26 Jan 1999 17:30:35 -0800 (PST)
(envelope-from sgk)
From: Steve Kargl <sgk@troutmask.apl.washington.edu>
Message-Id: <199901270130.RAA08180@troutmask.apl.washington.edu>
Subject: Re: removing f2c from base distribution
In-Reply-To: <199901270116.RAA64007@silvia.hip.berkeley.edu> from Satoshi Asami at "Jan 26, 1999 5:16:45 pm"
To: asami@FreeBSD.ORG (Satoshi Asami)
Date: Tue, 26 Jan 1999 17:30:35 -0800 (PST)
Cc: obrien@NUXI.com, freebsd-current@FreeBSD.ORG
X-Mailer: ELM [version 2.4ME+ PL43 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
Satoshi Asami wrote:
> * From: Steve Kargl <sgk@troutmask.apl.washington.edu>
>
> * Yes, I recognize that this is problem. A partial solution might
> * be anoncvs to a shadow tree of the master ports repository. Only
> * those ports in the shadow tree which satisfy portlint and "make;
> * make install; make package" would get committed to the master
> * repository.
> *
> * Now, if Satoshi has read the above, could someone please revive him
> * and make sure he takes his heart medication ;-)
>
> Um, I'm still alive but can someone explain me why this can't be a
> "regular" port? Being useful to some but not the majority, no other
> parts of the system depending on it, this looks like a model citizen
> in the ideal ports world. :)
>
Well, actually I did f2c as a port, and it does indeed fit
inside the ports paradigm. Please, see my original email in
the thread.
--
Steve
finger kargl@troutmask.apl.washington.edu
http://troutmask.apl.washington.edu/~clesceri/kargl.html
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Tue Jan 26 17:40:21 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id RAA04093
for freebsd-current-outgoing; Tue, 26 Jan 1999 17:40:21 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA04082
for <freebsd-current@FreeBSD.ORG>; Tue, 26 Jan 1999 17:40:19 -0800 (PST)
(envelope-from dillon@apollo.backplane.com)
Received: (from dillon@localhost)
by apollo.backplane.com (8.9.2/8.9.1) id RAA27083;
Tue, 26 Jan 1999 17:40:13 -0800 (PST)
(envelope-from dillon)
Date: Tue, 26 Jan 1999 17:40:13 -0800 (PST)
From: Matthew Dillon <dillon@apollo.backplane.com>
Message-Id: <199901270140.RAA27083@apollo.backplane.com>
To: Dan Root <dar@thekeep.org>
Cc: freebsd-current@FreeBSD.ORG
Subject: Re: Memory usage weirdness
References: <19990126183430.A61727@thekeep.org>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
:
:What would cause more memory to be considered in the active state than
:could be accounted for by running processes?
:
:My main machine (running -current as of the afternoon of Jan 25) has
:somewhere between 80 and 100 megs of memory listed as used via ps and top
:(which, I presume doesn't take in to account shared executable pages, but
:does include the 16 megs the X server is mapping on the video card), yet
:both top and vmstat show over 170 megs worth of memory being active.
:
:Furthermore, if I kill off my X session and associated processes, active
:memory usage doesn't decrease, even after 5 or more minutes. According to
:...
There are two different things here:
(1) AVM ( Active Virtual Memory ) and ARM ( Active Real Memory ).
These might include device mmaps that are not considered real memory
by the paging subsystem ( though I believe I've fixed the AVM thingy
where X would mmap /dev/mem and AVM would become insane ).
(2) VM Paging queue statistics
wired, active, inactive, cache, free.
The VM system does not bother moving things from active to inactive
unless there is some stress on the memory subsystem. If you are
just sitting idle, I wouldn't expect to see active pages moved to
inactive.
X consists of quite a few direct maps of code, and less in the way of
BSS data. So when you exit the X session, only the BSS data, which has
no backing store on exit, will have been returned ( active->free queue ).
The mmap'd code, which is vnode-backed, just stays active until something
stresses the memory subsystem.
-Matt
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Tue Jan 26 17:41:08 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id RAA04345
for freebsd-current-outgoing; Tue, 26 Jan 1999 17:41:08 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA04339
for <freebsd-current@FreeBSD.ORG>; Tue, 26 Jan 1999 17:41:06 -0800 (PST)
(envelope-from jkh@zippy.cdrom.com)
Received: from zippy.cdrom.com (localhost.cdrom.com [127.0.0.1])
by zippy.cdrom.com (8.9.2/8.9.1) with ESMTP id RAA76603;
Tue, 26 Jan 1999 17:41:33 -0800 (PST)
To: Nate Williams <nate@mt.sri.com>
cc: Steve Kargl <sgk@troutmask.apl.washington.edu>,
freebsd-current@FreeBSD.ORG, jkh@time.cdrom.com
Subject: Re: removing f2c from base distribution
In-reply-to: Your message of "Tue, 26 Jan 1999 09:23:26 MST."
<199901261623.JAA12330@mt.sri.com>
Date: Tue, 26 Jan 1999 17:41:32 -0800
Message-ID: <76600.917401292@zippy.cdrom.com>
From: "Jordan K. Hubbard" <jkh@zippy.cdrom.com>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
I'm not currently balking at the idea of you picking it up - by all
means, feel free! :)
Just also remember that Peter will at some point be doing an egcs
upgrade, so if that has issues for fortran they should be worked
out at this time.
- Jordan
> > Ladies and Gents,
> >
> > I have completed the portification of f2c and its support library.
>
> Who is going to pick this up? Last time I volunteered, Jordan balked at
> the idea.
>
>
> Nate
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Tue Jan 26 17:48:52 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id RAA05079
for freebsd-current-outgoing; Tue, 26 Jan 1999 17:48:52 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from adelphi.physics.adelaide.edu.au (adelphi.physics.adelaide.edu.au [129.127.36.247])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA05072
for <freebsd-current@freebsd.org>; Tue, 26 Jan 1999 17:48:45 -0800 (PST)
(envelope-from kkennawa@physics.adelaide.edu.au)
Received: from bragg (bragg [129.127.36.34])
by adelphi.physics.adelaide.edu.au (8.8.8/8.8.8/UofA-1.5) with SMTP id MAA13489;
Wed, 27 Jan 1999 12:18:40 +1030 (CST)
Received: from localhost by bragg; (5.65/1.1.8.2/05Aug95-0227PM)
id AA25606; Wed, 27 Jan 1999 12:18:40 +1030
Date: Wed, 27 Jan 1999 12:18:40 +1030 (CST)
From: Kris Kennaway <kkennawa@physics.adelaide.edu.au>
X-Sender: kkennawa@bragg
To: "Jordan K. Hubbard" <jkh@zippy.cdrom.com>
Cc: freebsd-current@FreeBSD.ORG
Subject: egcs (was Re: removing f2c from base distribution)
In-Reply-To: <76600.917401292@zippy.cdrom.com>
Message-Id: <Pine.OSF.4.05.9901271215480.17624-100000@bragg>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
On Tue, 26 Jan 1999, Jordan K. Hubbard wrote:
> Just also remember that Peter will at some point be doing an egcs
> upgrade, so if that has issues for fortran they should be worked
> out at this time.
On this matter, I found out the other day that eg++-compiled binaries are not
binary-compatible with those produced by gcc (e.g. libraries cannot apparently
be linked to by gcc, etc). Has anyone considered the implications of this?
Kris
-----
(ASP) Microsoft Corporation (MSFT) announced today that the release of its
productivity suite, Office 2000, will be delayed until the first quarter
of 1901.
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Tue Jan 26 17:54:06 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id RAA05590
for freebsd-current-outgoing; Tue, 26 Jan 1999 17:54:06 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from vader.cs.berkeley.edu (vader.CS.Berkeley.EDU [128.32.38.234])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA05548
for <freebsd-current@FreeBSD.ORG>; Tue, 26 Jan 1999 17:54:01 -0800 (PST)
(envelope-from asami@vader.cs.berkeley.edu)
Received: from silvia.hip.berkeley.edu (sji-ca13-237.ix.netcom.com [209.109.238.237]) by vader.cs.berkeley.edu (8.8.7/8.7.3) with ESMTP id RAA01094; Tue, 26 Jan 1999 17:51:29 -0800 (PST)
Received: (from asami@localhost) by silvia.hip.berkeley.edu (8.9.1/8.6.9) id RAA64117; Tue, 26 Jan 1999 17:51:25 -0800 (PST)
Date: Tue, 26 Jan 1999 17:51:25 -0800 (PST)
Message-Id: <199901270151.RAA64117@silvia.hip.berkeley.edu>
To: sgk@troutmask.apl.washington.edu
CC: obrien@NUXI.com, freebsd-current@FreeBSD.ORG
In-reply-to: <199901270130.RAA08180@troutmask.apl.washington.edu> (message
from Steve Kargl on Tue, 26 Jan 1999 17:30:35 -0800 (PST))
Subject: Re: removing f2c from base distribution
From: asami@FreeBSD.ORG (Satoshi Asami)
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
* Well, actually I did f2c as a port, and it does indeed fit
* inside the ports paradigm. Please, see my original email in
* the thread.
Yes, I know that. I was just wondering why people would want it
otherwise.
Satoshi
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Tue Jan 26 18:09:12 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id SAA07233
for freebsd-current-outgoing; Tue, 26 Jan 1999 18:09:12 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA07219
for <freebsd-current@FreeBSD.ORG>; Tue, 26 Jan 1999 18:09:08 -0800 (PST)
(envelope-from jkh@zippy.cdrom.com)
Received: from zippy.cdrom.com (localhost.cdrom.com [127.0.0.1])
by zippy.cdrom.com (8.9.2/8.9.1) with ESMTP id SAA76760;
Tue, 26 Jan 1999 18:09:40 -0800 (PST)
To: The Hermit Hacker <scrappy@hub.org>
cc: freebsd-current@FreeBSD.ORG
Subject: Re: Hate to ask, but...aout -> elf ...
In-reply-to: Your message of "Tue, 26 Jan 1999 14:48:11 -0400."
<Pine.BSF.4.05.9901261440120.94383-100000@thelab.hub.org>
Date: Tue, 26 Jan 1999 18:09:40 -0800
Message-ID: <76756.917402980@zippy.cdrom.com>
From: "Jordan K. Hubbard" <jkh@zippy.cdrom.com>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
> Is it a simple matter of 'make aout-to-elf', or...?
As of today, just type "make upgrade NOCONFIRM=YES" and wait for the
server to reboot some n hours later (where n is governed by the speed
of your machine :).
- Jordan
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Tue Jan 26 18:20:58 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id SAA08824
for freebsd-current-outgoing; Tue, 26 Jan 1999 18:20:58 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from time.cdrom.com (time.cdrom.com [204.216.27.226])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA08811;
Tue, 26 Jan 1999 18:20:53 -0800 (PST)
(envelope-from jkh@time.cdrom.com)
Received: (from root@localhost)
by time.cdrom.com (8.9.2/8.9.2) id SAA50280;
Tue, 26 Jan 1999 18:20:56 -0800 (PST)
(envelope-from jkh)
Date: Tue, 26 Jan 1999 18:20:56 -0800 (PST)
From: "Jordan K. Hubbard" <jkh@time.cdrom.com>
Message-Id: <199901270220.SAA50280@time.cdrom.com>
To: sef@FreeBSD.ORG
Subject: kdump/ktrace broken in -current
Cc: current@FreeBSD.ORG
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
===> kdump
cc -O -pipe -I/a/time/src/usr.bin/kdump/../ktrace -I/a/time/src/usr.bin/kdump/../.. -c /a/time/src/usr.bin/kdump/kdump.c
/bin/sh /a/time/src/usr.bin/kdump/mkioctls > ioctl.c
cc -O -pipe -I/a/time/src/usr.bin/kdump/../ktrace -I/a/time/src/usr.bin/kdump/../.. -c ioctl.c
In file included from ioctl.c:66:
/usr/include/pccard/cardinfo.h:57: redeclaration of `enum cardstate'
/usr/include/pccard/cardinfo.h:57: conflicting types for `noslot'
/usr/include/pccard/card.h:57: previous declaration of `noslot'
/usr/include/pccard/cardinfo.h:57: conflicting types for `empty'
/usr/include/pccard/card.h:57: previous declaration of `empty'
JFYI..
- Jordan
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Tue Jan 26 18:27:40 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id SAA09775
for freebsd-current-outgoing; Tue, 26 Jan 1999 18:27:40 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from fw.bby.com.au (ns.bby.com.au [192.83.119.129])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA09762
for <current@FreeBSD.ORG>; Tue, 26 Jan 1999 18:27:37 -0800 (PST)
(envelope-from gnb@itga.com.au)
Received: (from daemon@localhost) by fw.bby.com.au (8.8.8/8.6.9) id NAA20481; Wed, 27 Jan 1999 13:27:06 +1100 (EST)
Received: from lightning.itga.com.au(192.168.71.20)
via SMTP by fw.bby.com.au, id smtpd020479; Wed Jan 27 02:26:55 1999
Received: from lightning (lightning [192.168.71.20])
by lightning.itga.com.au (8.9.1a/8.9.1) with ESMTP id NAA21568;
Wed, 27 Jan 1999 13:26:54 +1100 (EST)
Message-Id: <199901270226.NAA21568@lightning.itga.com.au>
From: Gregory Bond <gnb@itga.com.au>
To: Matthew Dillon <dillon@apollo.backplane.com>
Cc: Mike Smith <mike@smith.net.au>, current@FreeBSD.ORG,
Matt Behrens <matt@zigg.com>
Subject: Re: SOFTUPDATES hangs keyboard
In-reply-to: Your message of Sun, 03 Jan 1999 23:40:46 -0800.
Date: Wed, 27 Jan 1999 13:26:54 +1100
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
I've just done my first CVSup since the 3-Stable split, using RELENG_3.
This was after Matt D. committed a couple of VM fixes back to the 3-S branch.
I have also enabled 32-bit DMA on my drive at the same time (amazing
what you can learn from reading LINT - and read speed went from 3Mb/s to
12Mb/s).
Whatever it was, it has seemingly fixed the problem I was having with
softupdates-related system hangs. Previously, if I enabled softupdates on
/usr/src, it would hang within a few seconds doing "cd /usr/src/games; make".
Now I have done two entire "make buildworld"s with /usr/src and /usr/obj
on the same softupdates partition with no hangs.
It's still not perfect, because every so often when I reboot I get
something like
syncing disks: 13 9 4 4 4 4 4 4 4 4 4 4 4 4 4 giving up
and I have had a panic when shutting down (something about freeing vnodes).
I'm now running with DDB and INVARIANTS so I'll try and catch something
more useful. And I'll try removing the flags from wd0 in the kernel
and see if that is the problem....
Greg,
still not quite brave enough to run softupdates on /usr or /var....
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Tue Jan 26 18:28:50 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id SAA09919
for freebsd-current-outgoing; Tue, 26 Jan 1999 18:28:50 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from thelab.hub.org (nat0690.mpoweredpc.net [142.177.190.182])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA09913
for <freebsd-current@FreeBSD.ORG>; Tue, 26 Jan 1999 18:28:48 -0800 (PST)
(envelope-from scrappy@hub.org)
Received: from localhost (scrappy@localhost)
by thelab.hub.org (8.9.1/8.9.1) with ESMTP id WAA00698;
Tue, 26 Jan 1999 22:28:33 -0400 (AST)
(envelope-from scrappy@hub.org)
X-Authentication-Warning: thelab.hub.org: scrappy owned process doing -bs
Date: Tue, 26 Jan 1999 22:28:32 -0400 (AST)
From: The Hermit Hacker <scrappy@hub.org>
To: "Jordan K. Hubbard" <jkh@zippy.cdrom.com>
cc: freebsd-current@FreeBSD.ORG
Subject: Re: Hate to ask, but...aout -> elf ...
In-Reply-To: <76756.917402980@zippy.cdrom.com>
Message-ID: <Pine.BSF.4.05.9901262224380.76634-100000@thelab.hub.org>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
On Tue, 26 Jan 1999, Jordan K. Hubbard wrote:
> > Is it a simple matter of 'make aout-to-elf', or...?
>
> As of today, just type "make upgrade NOCONFIRM=YES" and wait for the
> server to reboot some n hours later (where n is governed by the speed
> of your machine :).
Oh, now, *that* makes me nervous :) 2500 kilometers away from my baby,
and "waiting for the server to reboot" is what I'm trying to avoid :)
What exactly does this do? I'm going to read through the Makefile as soon
as I get it upgraded but...I think my more immediate concern is the kernel
and boot blocks...any summary somewhere of what to expect? :) Binaries
breaking? config files in /etc going poof?
thanks...
Marc G. Fournier
Systems Administrator @ hub.org
primary: scrappy@hub.org secondary: scrappy@{freebsd|postgresql}.org
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Tue Jan 26 18:30:40 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id SAA10154
for freebsd-current-outgoing; Tue, 26 Jan 1999 18:30:40 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from thelab.hub.org (nat0690.mpoweredpc.net [142.177.190.182])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA10149
for <freebsd-current@FreeBSD.ORG>; Tue, 26 Jan 1999 18:30:39 -0800 (PST)
(envelope-from scrappy@hub.org)
Received: from localhost (scrappy@localhost)
by thelab.hub.org (8.9.1/8.9.1) with ESMTP id WAA00757;
Tue, 26 Jan 1999 22:30:35 -0400 (AST)
(envelope-from scrappy@hub.org)
X-Authentication-Warning: thelab.hub.org: scrappy owned process doing -bs
Date: Tue, 26 Jan 1999 22:30:35 -0400 (AST)
From: The Hermit Hacker <scrappy@hub.org>
To: "Jordan K. Hubbard" <jkh@zippy.cdrom.com>
cc: freebsd-current@FreeBSD.ORG
Subject: Re: Hate to ask, but...aout -> elf ...
In-Reply-To: <Pine.BSF.4.05.9901262224380.76634-100000@thelab.hub.org>
Message-ID: <Pine.BSF.4.05.9901262229470.76634-100000@thelab.hub.org>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
Oh, one other thing...this moves me from an aout system to an elf one...is
this a one time only thing, and then back to 'make world', or is this
something I just continue to use for future upgrades?
On Tue, 26 Jan 1999, The Hermit Hacker wrote:
> On Tue, 26 Jan 1999, Jordan K. Hubbard wrote:
>
> > > Is it a simple matter of 'make aout-to-elf', or...?
> >
> > As of today, just type "make upgrade NOCONFIRM=YES" and wait for the
> > server to reboot some n hours later (where n is governed by the speed
> > of your machine :).
>
> Oh, now, *that* makes me nervous :) 2500 kilometers away from my baby,
> and "waiting for the server to reboot" is what I'm trying to avoid :)
>
> What exactly does this do? I'm going to read through the Makefile as soon
> as I get it upgraded but...I think my more immediate concern is the kernel
> and boot blocks...any summary somewhere of what to expect? :) Binaries
> breaking? config files in /etc going poof?
>
> thanks...
>
> Marc G. Fournier
> Systems Administrator @ hub.org
> primary: scrappy@hub.org secondary: scrappy@{freebsd|postgresql}.org
>
>
> To Unsubscribe: send mail to majordomo@FreeBSD.org
> with "unsubscribe freebsd-current" in the body of the message
>
Marc G. Fournier
Systems Administrator @ hub.org
primary: scrappy@hub.org secondary: scrappy@{freebsd|postgresql}.org
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Tue Jan 26 19:01:14 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id TAA13403
for freebsd-current-outgoing; Tue, 26 Jan 1999 19:01:14 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from awfulhak.org (awfulhak.force9.co.uk [195.166.136.63])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA13398
for <current@FreeBSD.ORG>; Tue, 26 Jan 1999 19:01:09 -0800 (PST)
(envelope-from brian@Awfulhak.org)
Received: from keep.lan.Awfulhak.org (root@keep.lan.Awfulhak.org [172.16.0.8])
by awfulhak.org (8.8.8/8.8.8) with ESMTP id AAA27657;
Wed, 27 Jan 1999 00:58:23 GMT
(envelope-from brian@Awfulhak.org)
Received: from keep.lan.Awfulhak.org (brian@localhost [127.0.0.1])
by keep.lan.Awfulhak.org (8.9.2/8.9.2) with ESMTP id AAA15871;
Wed, 27 Jan 1999 00:59:49 GMT
(envelope-from brian@keep.lan.Awfulhak.org)
Message-Id: <199901270059.AAA15871@keep.lan.Awfulhak.org>
X-Mailer: exmh version 2.0.2 2/24/98
To: Alexander Sanda <entropy@compufit.at>
cc: Brian Somers <brian@Awfulhak.org>, current@FreeBSD.ORG
Subject: Re: PPP (userland) troubles ?
In-reply-to: Your message of "Tue, 26 Jan 1999 22:35:59 +0100."
<Pine.BSF.4.05.9901262221550.3357-100000@darkstar.vmx>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Wed, 27 Jan 1999 00:59:48 +0000
From: Brian Somers <brian@Awfulhak.org>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
Hi,
It's quite possible that this is another latency problem introduced
by my recent timer changes... the changes make the .1 second
latencies into longer - possibly indefinite - latencies.
To find out if this is the problem, can you try connecting
interactively. You should see the same delay. You can then try
again, but during the delay, pressing return a few times at the
prompt should wake ppp up. Is this happening ?
BTW, I recently fixed one of these bugs when ``openmode'' is set to
``passive''....
> On Tue, 26 Jan 1999, Brian Somers wrote:
>
> > Are you using a routing daemon ? Also, have you tried just having
> > ``add default HISADDR'' in ppp.conf and leaving everything out of
> > ppp.linkup ? What do your routing tables look like before/during/after
> > the hang ?
>
> I usually run routed, yes, and it didn't ever affect the
> dialup functionality. Disabling routed does not change the behaviour in
> any way.
>
> My ppp.linkup doesn't really contain much stuff. The only thing it does
> is running the mailqueue.
>
> Also, I have "add default HISADDR" in my ppp.conf. A sample output of
> netstat -nr after establishing the connection looks like follows:
>
> [73]root@darkstar:/root #>netstat -nr
> Routing tables
>
> Internet:
> Destination Gateway Flags Refs Use Netif
> Expire
> default 131.130.230.14 UGSc 10 1 tun0
> 127.0.0.1 127.0.0.1 UH 21 1910 lo0
> 131.130.230.14 131.130.231.66 UH 11 0 tun0
> 131.130.231.66 127.0.0.1 UH 0 0 lo0
> [74]root@darkstar:/root #>
>
> In this case, 131.130.231.66 is the adress assigned to my tun0
> interface, 131.130.230.14 is the peer. So this, really looks ok.
>
> To remove any possible influences, I have temporarily removed the lan
> configuration (normally, this box has a 3c905 NIC for my littly lan).
>
> In fact, I never had problems like that, they started to show up a few
> days ago (a lot of stuff has been commited the last couple of days, and
> I also noted small changes to /usr/src/usr.sbin/ppp.
>
> The delay until everything works ok looks like something waits for some
> buffer to be filled up, because there is absolutely no modem activity
> for the first couple of seconds.
>
> --
> # /AS/ http://privat.schlund.de/entropy/ #
> # #
> # XX has detected, that your mouse cursor has changed position. Please #
> # restart XX, so it can be updated. -- From The Gimp manual #
Cheers.
--
Brian <brian@Awfulhak.org> <brian@FreeBSD.org> <brian@OpenBSD.org>
<http://www.Awfulhak.org>
Don't _EVER_ lose your sense of humour !
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Tue Jan 26 19:17:24 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id TAA14987
for freebsd-current-outgoing; Tue, 26 Jan 1999 19:17:24 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from rip.psg.com (rip.psg.com [147.28.0.39])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA14982
for <freebsd-current@freebsd.org>; Tue, 26 Jan 1999 19:17:20 -0800 (PST)
(envelope-from randy@psg.com)
Received: from localhost (2349 bytes) by rip.psg.com
via sendmail with P:stdio/R:inet_resolve/T:smtp
(sender: <randy>) (ident <randy> using unix)
id <m105LTg-0008G4C@rip.psg.com>
for <freebsd-current@freebsd.org>; Tue, 26 Jan 1999 19:17:16 -0800 (PST)
(Smail-3.2.0.101 1997-Dec-17 #1 built 1998-Oct-13)
Message-Id: <m105LTg-0008G4C@rip.psg.com>
Date: Tue, 26 Jan 1999 19:17:16 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
From: Randy Bush <randy@psg.com>
To: freebsd-current@FreeBSD.ORG
Subject: sdr25 wants to reinstall xfree
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
is this for real or is it an aout-to-elf thing?
randy
===> Generating temporary packing list
/bin/ln -sf libtcl80.so.1 /usr/local/lib/libtcl80.so
/usr/bin/env OBJFORMAT=elf /sbin/ldconfig -m /usr/local/lib
/usr/bin/env PKG_PREFIX=/usr/local /bin/sh /usr/ports/lang/tcl80/pkg/INSTALL.tclsh
===> Registering installation for tcl-8.0.4
===> Returning to build of tk-8.0.4
===> tk-8.0.4 depends on shared library: X11.6 - not found
===> Verifying install for X11.6 in /usr/ports/x11/XFree86
Assuming that you have fetched a USA-Legal Wraphelp.c.
>> X333src-1.tgz doesn't seem to exist on this system.
>> Attempting to fetch from ftp://ftp.xfree86.org/pub/XFree86/3.3.3/source/.
Receiving X333src-1.tgz (16596763 bytes): 100%
16596763 bytes transfered in 132.8 seconds (122.00 Kbytes/s)
>> X333src-2.tgz doesn't seem to exist on this system.
>> Attempting to fetch from ftp://ftp.xfree86.org/pub/XFree86/3.3.3/source/.
Receiving X333src-2.tgz (14501435 bytes): 100%
14501435 bytes transfered in 111.4 seconds (127.07 Kbytes/s)
>> 3.3.3-3.3.3.1.diff.gz doesn't seem to exist on this system.
>> Attempting to fetch from ftp://ftp.xfree86.org/pub/XFree86/3.3.3.1/fixes/.
Receiving 3.3.3-3.3.3.1.diff.gz (178472 bytes): 100%
178472 bytes transfered in 1.7 seconds (99.77 Kbytes/s)
===> Extracting for XFree86-3.3.3.1
>> Checksum OK for xc/X333src-1.tgz.
>> Checksum OK for xc/X333src-2.tgz.
>> Checksum OK for xc/3.3.3-3.3.3.1.diff.gz.
===> Patching for XFree86-3.3.3.1
===> Applying distribution patches for XFree86-3.3.3.1
===> Configuring for XFree86-3.3.3.1
*** I don't see the static library for tk version in /usr/local/lib.
*** XF86Setup will not be installed. If you want to build this program
*** install tk 4.2 or 8.0 first.
Which servers do you wish to build, you can save a lot of disk space
by only compiling the server you will be using. It will also save you
considerable compile time.
Do you want to build the VGA16 server? [YES] ^C
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-multimedia" in the body of the message
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Tue Jan 26 19:40:38 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id TAA17306
for freebsd-current-outgoing; Tue, 26 Jan 1999 19:40:38 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from spinner.netplex.com.au (spinner.netplex.com.au [202.12.86.3])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA17279;
Tue, 26 Jan 1999 19:40:31 -0800 (PST)
(envelope-from peter@netplex.com.au)
Received: from spinner.netplex.com.au (localhost [127.0.0.1])
by spinner.netplex.com.au (8.9.2/8.9.2/Netplex) with ESMTP id LAA09860;
Wed, 27 Jan 1999 11:40:17 +0800 (WST)
(envelope-from peter@spinner.netplex.com.au)
Message-Id: <199901270340.LAA09860@spinner.netplex.com.au>
X-Mailer: exmh version 2.0.2 2/24/98
To: "Jordan K. Hubbard" <jkh@time.cdrom.com>
cc: sef@FreeBSD.ORG, current@FreeBSD.ORG
Subject: Re: kdump/ktrace broken in -current
In-reply-to: Your message of "Tue, 26 Jan 1999 18:20:56 PST."
<199901270220.SAA50280@time.cdrom.com>
Date: Wed, 27 Jan 1999 11:40:17 +0800
From: Peter Wemm <peter@netplex.com.au>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
"Jordan K. Hubbard" wrote:
> ===> kdump
> cc -O -pipe -I/a/time/src/usr.bin/kdump/../ktrace -I/a/time/src/usr.bin/kdump
/../.. -c /a/time/src/usr.bin/kdump/kdump.c
> /bin/sh /a/time/src/usr.bin/kdump/mkioctls > ioctl.c
> cc -O -pipe -I/a/time/src/usr.bin/kdump/../ktrace -I/a/time/src/usr.bin/kdump
/../.. -c ioctl.c
> In file included from ioctl.c:66:
> /usr/include/pccard/cardinfo.h:57: redeclaration of `enum cardstate'
> /usr/include/pccard/cardinfo.h:57: conflicting types for `noslot'
> /usr/include/pccard/card.h:57: previous declaration of `noslot'
> /usr/include/pccard/cardinfo.h:57: conflicting types for `empty'
> /usr/include/pccard/card.h:57: previous declaration of `empty'
I had this problem.. There is a stray file in /usr/include/pccard - card.h
should not be there, and the generator script for ktrace/kdump/truss finds
it.
===
revision 1.9
date: 1997/11/18 21:03:57; author: nate; state: dead; lines: +0 -0
- Renamed 'card.h' to 'cardinfo.h', to avoid namespace collisions with
the card.h that config builds.
[ Repository renaming done in the background to save the card.h history ]
===
> JFYI..
>
> - Jordan
>
> To Unsubscribe: send mail to majordomo@FreeBSD.org
> with "unsubscribe freebsd-current" in the body of the message
>
Cheers,
-Peter
--
Peter Wemm <peter@netplex.com.au> Netplex Consulting
"No coffee, No workee!" :-)
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Tue Jan 26 19:54:38 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id TAA18866
for freebsd-current-outgoing; Tue, 26 Jan 1999 19:54:38 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from thelab.hub.org (nat0690.mpoweredpc.net [142.177.190.182])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA18856
for <freebsd-current@FreeBSD.ORG>; Tue, 26 Jan 1999 19:54:33 -0800 (PST)
(envelope-from scrappy@hub.org)
Received: from localhost (scrappy@localhost)
by thelab.hub.org (8.9.1/8.9.1) with ESMTP id XAA02137;
Tue, 26 Jan 1999 23:54:26 -0400 (AST)
(envelope-from scrappy@hub.org)
X-Authentication-Warning: thelab.hub.org: scrappy owned process doing -bs
Date: Tue, 26 Jan 1999 23:54:25 -0400 (AST)
From: The Hermit Hacker <scrappy@hub.org>
To: "Jordan K. Hubbard" <jkh@zippy.cdrom.com>
cc: freebsd-current@FreeBSD.ORG
Subject: "make upgrade NOCONFIRM=YES" (Was: Re: Hate to ask, but...aout ->
elf ... )
In-Reply-To: <Pine.BSF.4.05.9901262224380.76634-100000@thelab.hub.org>
Message-ID: <Pine.BSF.4.05.9901262351070.812-100000@thelab.hub.org>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
make upgrade NOCONFIRM=YES
Your source tree must not be fully populated; unable to find upgrade
script
in /usr/src/release/scripts/doupgrade.sh.
*** Error code 1
Stop.
*** Error code 1
Stop.
Just connected to freefall and did a 'cvs checkout' of release, and the
file doesn't appear to exist there either, so it isn't an out of sync
cvsup or anything...*raised eyebrow*
On Tue, 26 Jan 1999, The Hermit Hacker wrote:
> On Tue, 26 Jan 1999, Jordan K. Hubbard wrote:
>
> > > Is it a simple matter of 'make aout-to-elf', or...?
> >
> > As of today, just type "make upgrade NOCONFIRM=YES" and wait for the
> > server to reboot some n hours later (where n is governed by the speed
> > of your machine :).
>
> Oh, now, *that* makes me nervous :) 2500 kilometers away from my baby,
> and "waiting for the server to reboot" is what I'm trying to avoid :)
>
> What exactly does this do? I'm going to read through the Makefile as soon
> as I get it upgraded but...I think my more immediate concern is the kernel
> and boot blocks...any summary somewhere of what to expect? :) Binaries
> breaking? config files in /etc going poof?
>
> thanks...
>
> Marc G. Fournier
> Systems Administrator @ hub.org
> primary: scrappy@hub.org secondary: scrappy@{freebsd|postgresql}.org
>
>
> To Unsubscribe: send mail to majordomo@FreeBSD.org
> with "unsubscribe freebsd-current" in the body of the message
>
Marc G. Fournier
Systems Administrator @ hub.org
primary: scrappy@hub.org secondary: scrappy@{freebsd|postgresql}.org
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Tue Jan 26 19:59:09 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id TAA19286
for freebsd-current-outgoing; Tue, 26 Jan 1999 19:59:09 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from mail.westbend.net (ns1.westbend.net [156.46.203.3])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA19281
for <freebsd-current@FreeBSD.ORG>; Tue, 26 Jan 1999 19:59:04 -0800 (PST)
(envelope-from hetzels@westbend.net)
Received: from admin (admin.westbend.net [156.46.203.13])
by mail.westbend.net (8.8.8/8.8.8) with SMTP id VAA25638;
Tue, 26 Jan 1999 21:58:43 -0600 (CST)
(envelope-from hetzels@westbend.net)
Message-ID: <009f01be49a9$575bfea0$0dcb2e9c@westbend.net>
From: "Scot W. Hetzel" <hetzels@westbend.net>
To: "The Hermit Hacker" <scrappy@hub.org>
Cc: <freebsd-current@FreeBSD.ORG>
References: <Pine.BSF.4.05.9901262351070.812-100000@thelab.hub.org>
Subject: Re: "make upgrade NOCONFIRM=YES" (Was: Re: Hate to ask, but...aout ->elf ... )
Date: Tue, 26 Jan 1999 21:58:46 -0600
Organization: West Bend Internet
MIME-Version: 1.0
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.00.2013.1300
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2013.1300
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
From: The Hermit Hacker <scrappy@hub.org>
>
> make upgrade NOCONFIRM=YES
> Your source tree must not be fully populated; unable to find upgrade
> script
> in /usr/src/release/scripts/doupgrade.sh.
> *** Error code 1
>
> Stop.
> *** Error code 1
>
> Stop.
>
> Just connected to freefall and did a 'cvs checkout' of release, and the
> file doesn't appear to exist there either, so it isn't an out of sync
> cvsup or anything...*raised eyebrow*
>
I just read on the STABLE list that the doupgrade.sh file was moved to the
tools directory.
Scot
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Tue Jan 26 20:08:52 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id UAA20477
for freebsd-current-outgoing; Tue, 26 Jan 1999 20:08:52 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from fw.bby.com.au (ns.bby.com.au [192.83.119.129])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA20439
for <current@FreeBSD.ORG>; Tue, 26 Jan 1999 20:08:49 -0800 (PST)
(envelope-from gnb@itga.com.au)
Received: (from daemon@localhost) by fw.bby.com.au (8.8.8/8.6.9) id PAA21510; Wed, 27 Jan 1999 15:08:26 +1100 (EST)
Received: from lightning.itga.com.au(192.168.71.20)
via SMTP by fw.bby.com.au, id smtpd021508; Wed Jan 27 04:08:22 1999
Received: from lightning (lightning [192.168.71.20])
by lightning.itga.com.au (8.9.1a/8.9.1) with ESMTP id PAA26575;
Wed, 27 Jan 1999 15:08:21 +1100 (EST)
Message-Id: <199901270408.PAA26575@lightning.itga.com.au>
From: Gregory Bond <gnb@itga.com.au>
Cc: Matthew Dillon <dillon@apollo.backplane.com>,
Mike Smith <mike@smith.net.au>, current@FreeBSD.ORG,
Matt Behrens <matt@zigg.com>
Subject: WD/ide_pci bug! [was Re: SOFTUPDATES hangs keyboard ]
In-reply-to: Your message of Wed, 27 Jan 1999 13:26:54 +1100.
Date: Wed, 27 Jan 1999 15:08:21 +1100
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
Well stone the bloody crows.
System: HP Kayak XA 440BX M/b, P-II, Quantum Fireball ex4.3a
For months I've been running with no flags on either wdc0 or wd0.
Having followed the recent discussions about DMA mode etc I looked at
LINT and added "flags 0xa0ff" to wd0. Rebuilt the system using the
latest 3-Stable code, including Matt D.s VM fixes, and tried yet again
the test that has quite reliably frozen my system (softupdates enabled
on /usr/src, cd /usr/src/games, make) and, lo and behold, it worked. I
thought it was probably Matt's VM patches but (just to make sure) I
built a kernel without the wd flags and tried again. It failed.
This seems to be saying the problem is the WD driver: When I have flags
on my disk, it all works; when I use the default, it fails (but only
on filesystems with softupdates activity...)
Any ide_pci experts like me to try some more tests?
Matt: I'm sorry I ever doubted the VM code or the softupdates!
Probing for devices on PCI bus 0:
chip0: <Intel 82443BX host to PCI bridge> rev 0x02 on pci0.0.0
chip1: <Intel 82443BX host to AGP bridge> rev 0x02 on pci0.1.0
chip2: <Intel 82371AB PCI to ISA bridge> rev 0x02 on pci0.7.0
ide_pci0: <Intel PIIX4 Bus-master IDE controller> rev 0x01 on pci0.7.1
chip3: <Intel 82371AB Power management controller> rev 0x02 on pci0.7.3
[...]
wdc0 at 0x1f0-0x1f7 irq 14 on isa
wdc0: unit 0 (wd0): <QUANTUM FIREBALL EX4.3A>, DMA, 32-bit, multi-block-16
wd0: 4104MB (8405775 sectors), 8895 cyls, 15 heads, 63 S/T, 512 B/S
wdc1 at 0x170-0x177 irq 15 on isa
wdc1: unit 0 (atapi): <CD-532E-A/2.0C>, removable, accel, ovlap, dma, iordis
acd0: drive speed 5512KB/sec, 128KB cache
acd0: supported read types: CD-R, CD-RW, CD-DA, packet track
acd0: Audio: play, 16 volume levels
acd0: Mechanism: ejectable tray
acd0: Medium: CD-ROM 120mm data disc loaded, unlocked
vga0 at 0x3b0-0x3df maddr 0xa0000 msize 131072 on isa
Greg.
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Tue Jan 26 20:10:27 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id UAA20938
for freebsd-current-outgoing; Tue, 26 Jan 1999 20:10:27 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from peach.ocn.ne.jp (peach.ocn.ne.jp [210.145.254.87])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA20927
for <freebsd-current@FreeBSD.ORG>; Tue, 26 Jan 1999 20:10:25 -0800 (PST)
(envelope-from dcs@newsguy.com)
Received: from newsguy.com by peach.ocn.ne.jp (8.9.1a/OCN) id NAA23893; Wed, 27 Jan 1999 13:10:18 +0900 (JST)
Message-ID: <36AE8EA4.2768A5C3@newsguy.com>
Date: Wed, 27 Jan 1999 12:57:24 +0900
From: "Daniel C. Sobral" <dcs@newsguy.com>
X-Mailer: Mozilla 4.5 [en] (Win98; I)
X-Accept-Language: pt-BR,ja
MIME-Version: 1.0
To: "Viren R. Shah" <viren@rstcorp.com>
CC: freebsd-current@FreeBSD.ORG
Subject: Re: Problem with loader?
References: <199901262138.QAA00748@jabberwock.rstcorp.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
"Viren R. Shah" wrote:
>
> FreeBSD/i386 bootstrap loader Revision 0.2
> ficlExecFD: Error at line 1
^^^^^^^^^^
> int=0000000e err=00000004 efl=00010246 eip=0000fda0
> [at which point my patience ran out, and I didn't jot down the rest]
>
> I booted with a loader from Jan 19, and it works. Did I goof up
> somewhere? or is this a loader bug?
You didn't goof. This is a known bug, and I even quite sure I know
where it is and how to fix it, but I have been waiting for an answer
from ficl's author.
Remove/rename /boot/boot.4th. This (loading a Forth script) isn't
working at the present time. If you need to work with it, I can send
you a temporary patch.
--
Daniel C. Sobral (8-DCS)
dcs@newsguy.com
If you sell your soul to the Devil and all you get is an MCSE from
it, you haven't gotten market rate.
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Tue Jan 26 21:05:00 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id VAA26508
for freebsd-current-outgoing; Tue, 26 Jan 1999 21:05:00 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from ns.mt.sri.com (sri-gw.MT.net [206.127.105.141])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA26497
for <freebsd-current@FreeBSD.ORG>; Tue, 26 Jan 1999 21:04:57 -0800 (PST)
(envelope-from nate@mt.sri.com)
Received: from mt.sri.com (rocky.mt.sri.com [206.127.76.100])
by ns.mt.sri.com (8.8.8/8.8.8) with SMTP id WAA29270;
Tue, 26 Jan 1999 22:04:55 -0700 (MST)
(envelope-from nate@rocky.mt.sri.com)
Received: by mt.sri.com (SMI-8.6/SMI-SVR4)
id WAA18271; Tue, 26 Jan 1999 22:04:53 -0700
Date: Tue, 26 Jan 1999 22:04:53 -0700
Message-Id: <199901270504.WAA18271@mt.sri.com>
From: Nate Williams <nate@mt.sri.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
To: "Jordan K. Hubbard" <jkh@zippy.cdrom.com>
Cc: Nate Williams <nate@mt.sri.com>,
Steve Kargl <sgk@troutmask.apl.washington.edu>,
freebsd-current@FreeBSD.ORG, jkh@time.cdrom.com
Subject: Re: removing f2c from base distribution
In-Reply-To: <76600.917401292@zippy.cdrom.com>
References: <199901261623.JAA12330@mt.sri.com>
<76600.917401292@zippy.cdrom.com>
X-Mailer: VM 6.34 under 19.16 "Lille" XEmacs Lucid
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
> I'm not currently balking at the idea of you picking it up - by all
> means, feel free! :)
Roger Wilco, Ok-dokey, good deal. :)
> Just also remember that Peter will at some point be doing an egcs
> upgrade, so if that has issues for fortran they should be worked
> out at this time.
Steven?
Nate
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Tue Jan 26 21:05:00 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id VAA26509
for freebsd-current-outgoing; Tue, 26 Jan 1999 21:05:00 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from cheddar.netmonger.net (cheddar.netmonger.net [209.54.21.140])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA26496
for <current@freebsd.org>; Tue, 26 Jan 1999 21:04:57 -0800 (PST)
(envelope-from chris@cheddar.netmonger.net)
Received: (from chris@localhost)
by cheddar.netmonger.net (8.8.8/8.8.8) id AAA12438;
Wed, 27 Jan 1999 00:04:56 -0500 (EST)
Message-ID: <19990127000455.A6699@netmonger.net>
Date: Wed, 27 Jan 1999 00:04:55 -0500
From: Christopher Masto <chris@netmonger.net>
To: current@FreeBSD.ORG
Subject: Re: IDE DMA works, I'll be a...
References: <Pine.BSF.4.05.9901252106160.12387-100000@janus.syracuse.net> <Pine.BSF.4.05.9901252123110.13366-100000@janus.syracuse.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.91.1i
In-Reply-To: <Pine.BSF.4.05.9901252123110.13366-100000@janus.syracuse.net>; from Brian Feldman on Mon, Jan 25, 1999 at 09:25:37PM -0500
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
Well, now I'm plenty confused. I wasn't aware that IDE DMA didn't
work, so this subject line caught me a bit by suprise. Maybe I just
have "supported" hardware everywhere, or maybe I'm missing something
and I don't even know it. Or maybe I'm just posting this for
comparison purposes.
I know that this 2.5-year-old machine has an Asus motherboard of
some sort:
FreeBSD 4.0-CURRENT #1: Sun Jan 24 02:49:52 EST 1999
root@lion-around.at.yiff.net:/usr/local/usr-src/sys/compile/LION-AROUND
Timecounter "i8254" frequency 1193182 Hz
CPU: Pentium/P54C (166.19-MHz 586-class CPU)
Origin = "GenuineIntel" Id = 0x52c Stepping=12
Features=0x1bf<FPU,VME,DE,PSE,TSC,MSR,MCE,CX8>
real memory = 100663296 (98304K bytes)
config> quit
avail memory = 94875648 (92652K bytes)
Preloaded elf kernel "kernel" at 0xf02d9000.
Probing for devices on PCI bus 0:
chip0: <Intel 82439> rev 0x03 on pci0.0.0
chip1: <Intel 82371SB PCI to ISA bridge> rev 0x01 on pci0.7.0
ide_pci0: <Intel PIIX3 Bus-master IDE controller> rev 0x00 on pci0.7.1
[...]
wdc0 at 0x1f0-0x1f7 irq 14 flags 0xa0ffa0ff on isa
wdc0: unit 0 (wd0): <WDC AC32500H>, DMA, 32-bit, multi-block-16
wd0: 2441MB (4999680 sectors), 4960 cyls, 16 heads, 63 S/T, 512 B/S
wdc0: unit 1 (atapi): <CD-ROM CDU311/3.0i>, removable, accel, dma, iordis
acd0: drive speed 1378KB/sec, 128KB cache
[...]
wdc1 at 0x170-0x177 irq 15 flags 0xa0ffa0ff on isa
wdc1: unit 0 (wd2): <Maxtor 91008D7>, DMA, 32-bit, multi-block-16
wd2: 9617MB (19696320 sectors), 19540 cyls, 16 heads, 63 S/T, 512 B/S
On the old wd0 that I got with the machine:
$ time dd if=/dev/zero of=test2 bs=32k count=1024
1024+0 records in
1024+0 records out
33554432 bytes transferred in 5.177823 secs (6480413 bytes/sec)
dd if=/dev/zero of=test2 bs=32k count=1024 0.03s user 2.08s system 28% cpu 7.458 total
$ time dd if=/dev/rwd0 of=/dev/null bs=32k count=1024
1024+0 records in
1024+0 records out
33554432 bytes transferred in 4.064697 secs (8255088 bytes/sec)
dd if=/dev/rwd0 of=/dev/null bs=32k count=1024 0.00s user 0.14s system 3% cpu 4.070 total
And on the brand spanking new Maxtor UltraDMA happy happy:
$ time dd if=/dev/zero of=test2 bs=32k count=1024
1024+0 records in
1024+0 records out
33554432 bytes transferred in 3.073696 secs (10916640 bytes/sec)
dd if=/dev/zero of=test2 bs=32k count=1024 0.01s user 2.26s system 72% cpu 3.124 total
$ time dd if=/dev/rwd2 of=/dev/null bs=32k count=1024
1024+0 records in
1024+0 records out
33554432 bytes transferred in 2.521986 secs (13304765 bytes/sec)
dd if=/dev/rwd2 of=/dev/null bs=32k count=1024 0.00s user 0.13s system 5% cpu 2.528 total
Just out of curiosity, I compared with a machine with what was at the time
an expensive SCSI controller. Same CPU as mine.
FreeBSD 2.2.7-STABLE #0: Sat Aug 8 22:38:59 EDT 1998
[...]
ahc0 <Adaptec 3940 Ultra SCSI host adapter> rev 0 int a irq 9 on pci1:4:0
ahc0: aic7880 Wide Channel A, SCSI Id=7, 16 SCBs
(ahc0:0:0): "SEAGATE ST34371W 0484" type 0 fixed SCSI 2
sd0(ahc0:0:0): Direct-Access 4148MB (8496884 512 byte sectors)
$ time dd if=/dev/zero of=test2 bs=32k count=1024
1024+0 records in
1024+0 records out
33554432 bytes transferred in 3.393906 secs (9886671 bytes/sec)
dd if=/dev/zero of=test2 bs=32k count=1024 0.04s user 1.33s system 40% cpu 3.411 total
$ time dd if=/dev/rsd0 of=/dev/null bs=32k count=1024
1024+0 records in
1024+0 records out
33554432 bytes transferred in 3.525452 secs (9517767 bytes/sec)
dd if=/dev/rsd0 of=/dev/null bs=32k count=1024 0.03s user 0.12s system 2% cpu 5.330 total
The bleeding edge and I have a pretty good relationship. I haven't
been bitten by softupdates, IDE DMA, or the new VM (well, I did have
that panic, but the fix had already become available).
Of course, I'm now running afoul of 4.0-related libtool breakage in
the ports collection, but it's not exactly a mystery to fix.
--
Christopher Masto Director of Operations NetMonger Communications
chris@netmonger.net info@netmonger.net http://www.netmonger.net
"Good tools allow users to do stupid things." -- Clay Shirky
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Tue Jan 26 21:10:51 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id VAA27032
for freebsd-current-outgoing; Tue, 26 Jan 1999 21:10:51 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA27027;
Tue, 26 Jan 1999 21:10:47 -0800 (PST)
(envelope-from jkh@zippy.cdrom.com)
Received: from zippy.cdrom.com (localhost.cdrom.com [127.0.0.1])
by zippy.cdrom.com (8.9.2/8.9.1) with ESMTP id VAA77559;
Tue, 26 Jan 1999 21:11:11 -0800 (PST)
To: Peter Wemm <peter@netplex.com.au>
cc: "Jordan K. Hubbard" <jkh@time.cdrom.com>, sef@FreeBSD.ORG,
current@FreeBSD.ORG
Subject: Re: kdump/ktrace broken in -current
In-reply-to: Your message of "Wed, 27 Jan 1999 11:40:17 +0800."
<199901270340.LAA09860@spinner.netplex.com.au>
Date: Tue, 26 Jan 1999 21:11:11 -0800
Message-ID: <77556.917413871@zippy.cdrom.com>
From: "Jordan K. Hubbard" <jkh@zippy.cdrom.com>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
> I had this problem.. There is a stray file in /usr/include/pccard - card.h
> should not be there, and the generator script for ktrace/kdump/truss finds
> it.
Ah crap... This is an upgrade problem we're going to need to deal
with specially then. :(
Maybe we should blow /usr/include away at some stage in the
aout-to-elf process?
- Jordan
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Tue Jan 26 21:15:58 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id VAA27890
for freebsd-current-outgoing; Tue, 26 Jan 1999 21:15:58 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA27882
for <freebsd-current@FreeBSD.ORG>; Tue, 26 Jan 1999 21:15:56 -0800 (PST)
(envelope-from jkh@zippy.cdrom.com)
Received: from zippy.cdrom.com (localhost.cdrom.com [127.0.0.1])
by zippy.cdrom.com (8.9.2/8.9.1) with ESMTP id VAA77599;
Tue, 26 Jan 1999 21:16:24 -0800 (PST)
To: The Hermit Hacker <scrappy@hub.org>
cc: freebsd-current@FreeBSD.ORG
Subject: Re: "make upgrade NOCONFIRM=YES" (Was: Re: Hate to ask, but...aout -> elf ... )
In-reply-to: Your message of "Tue, 26 Jan 1999 23:54:25 -0400."
<Pine.BSF.4.05.9901262351070.812-100000@thelab.hub.org>
Date: Tue, 26 Jan 1999 21:16:23 -0800
Message-ID: <77595.917414183@zippy.cdrom.com>
From: "Jordan K. Hubbard" <jkh@zippy.cdrom.com>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
Already fixed. :)
>
> make upgrade NOCONFIRM=YES
> Your source tree must not be fully populated; unable to find upgrade
> script
> in /usr/src/release/scripts/doupgrade.sh.
> *** Error code 1
>
> Stop.
> *** Error code 1
>
> Stop.
>
> Just connected to freefall and did a 'cvs checkout' of release, and the
> file doesn't appear to exist there either, so it isn't an out of sync
> cvsup or anything...*raised eyebrow*
>
>
> On Tue, 26 Jan 1999, The Hermit Hacker wrote:
>
> > On Tue, 26 Jan 1999, Jordan K. Hubbard wrote:
> >
> > > > Is it a simple matter of 'make aout-to-elf', or...?
> > >
> > > As of today, just type "make upgrade NOCONFIRM=YES" and wait for the
> > > server to reboot some n hours later (where n is governed by the speed
> > > of your machine :).
> >
> > Oh, now, *that* makes me nervous :) 2500 kilometers away from my baby,
> > and "waiting for the server to reboot" is what I'm trying to avoid :)
> >
> > What exactly does this do? I'm going to read through the Makefile as soon
> > as I get it upgraded but...I think my more immediate concern is the kernel
> > and boot blocks...any summary somewhere of what to expect? :) Binaries
> > breaking? config files in /etc going poof?
> >
> > thanks...
> >
> > Marc G. Fournier
> > Systems Administrator @ hub.org
> > primary: scrappy@hub.org secondary: scrappy@{freebsd|postgresql}.
org
> >
> >
> > To Unsubscribe: send mail to majordomo@FreeBSD.org
> > with "unsubscribe freebsd-current" in the body of the message
> >
>
> Marc G. Fournier
> Systems Administrator @ hub.org
> primary: scrappy@hub.org secondary: scrappy@{freebsd|postgresql}.or
g
>
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Tue Jan 26 21:18:50 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id VAA28175
for freebsd-current-outgoing; Tue, 26 Jan 1999 21:18:50 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from thelab.hub.org (nat0690.mpoweredpc.net [142.177.190.182])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA28170
for <freebsd-current@FreeBSD.ORG>; Tue, 26 Jan 1999 21:18:46 -0800 (PST)
(envelope-from scrappy@hub.org)
Received: from localhost (scrappy@localhost)
by thelab.hub.org (8.9.1/8.9.1) with ESMTP id BAA03402;
Wed, 27 Jan 1999 01:18:42 -0400 (AST)
(envelope-from scrappy@hub.org)
X-Authentication-Warning: thelab.hub.org: scrappy owned process doing -bs
Date: Wed, 27 Jan 1999 01:18:42 -0400 (AST)
From: The Hermit Hacker <scrappy@hub.org>
To: "Jordan K. Hubbard" <jkh@zippy.cdrom.com>
cc: freebsd-current@FreeBSD.ORG
Subject: Re: "make upgrade NOCONFIRM=YES" (Was: Re: Hate to ask, but...aout
-> elf ... )
In-Reply-To: <77595.917414183@zippy.cdrom.com>
Message-ID: <Pine.BSF.4.05.9901270118230.812-100000@thelab.hub.org>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
On Tue, 26 Jan 1999, Jordan K. Hubbard wrote:
> Already fixed. :)
Thank you, will try to run it first thing in the morning then :)
Here's hoping...
>
> >
> > make upgrade NOCONFIRM=YES
> > Your source tree must not be fully populated; unable to find upgrade
> > script
> > in /usr/src/release/scripts/doupgrade.sh.
> > *** Error code 1
> >
> > Stop.
> > *** Error code 1
> >
> > Stop.
> >
> > Just connected to freefall and did a 'cvs checkout' of release, and the
> > file doesn't appear to exist there either, so it isn't an out of sync
> > cvsup or anything...*raised eyebrow*
> >
> >
> > On Tue, 26 Jan 1999, The Hermit Hacker wrote:
> >
> > > On Tue, 26 Jan 1999, Jordan K. Hubbard wrote:
> > >
> > > > > Is it a simple matter of 'make aout-to-elf', or...?
> > > >
> > > > As of today, just type "make upgrade NOCONFIRM=YES" and wait for the
> > > > server to reboot some n hours later (where n is governed by the speed
> > > > of your machine :).
> > >
> > > Oh, now, *that* makes me nervous :) 2500 kilometers away from my baby,
> > > and "waiting for the server to reboot" is what I'm trying to avoid :)
> > >
> > > What exactly does this do? I'm going to read through the Makefile as soon
> > > as I get it upgraded but...I think my more immediate concern is the kernel
> > > and boot blocks...any summary somewhere of what to expect? :) Binaries
> > > breaking? config files in /etc going poof?
> > >
> > > thanks...
> > >
> > > Marc G. Fournier
> > > Systems Administrator @ hub.org
> > > primary: scrappy@hub.org secondary: scrappy@{freebsd|postgresql}.
> org
> > >
> > >
> > > To Unsubscribe: send mail to majordomo@FreeBSD.org
> > > with "unsubscribe freebsd-current" in the body of the message
> > >
> >
> > Marc G. Fournier
> > Systems Administrator @ hub.org
> > primary: scrappy@hub.org secondary: scrappy@{freebsd|postgresql}.or
> g
> >
>
Marc G. Fournier
Systems Administrator @ hub.org
primary: scrappy@hub.org secondary: scrappy@{freebsd|postgresql}.org
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Tue Jan 26 21:20:28 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id VAA28404
for freebsd-current-outgoing; Tue, 26 Jan 1999 21:20:28 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from ns.mt.sri.com (sri-gw.MT.net [206.127.105.141])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA28393;
Tue, 26 Jan 1999 21:20:23 -0800 (PST)
(envelope-from nate@mt.sri.com)
Received: from mt.sri.com (rocky.mt.sri.com [206.127.76.100])
by ns.mt.sri.com (8.8.8/8.8.8) with SMTP id WAA29449;
Tue, 26 Jan 1999 22:20:21 -0700 (MST)
(envelope-from nate@rocky.mt.sri.com)
Received: by mt.sri.com (SMI-8.6/SMI-SVR4)
id WAA18549; Tue, 26 Jan 1999 22:20:20 -0700
Date: Tue, 26 Jan 1999 22:20:20 -0700
Message-Id: <199901270520.WAA18549@mt.sri.com>
From: Nate Williams <nate@mt.sri.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
To: Peter Wemm <peter@netplex.com.au>
Cc: "Jordan K. Hubbard" <jkh@time.cdrom.com>, sef@FreeBSD.ORG,
current@FreeBSD.ORG
Subject: Re: kdump/ktrace broken in -current
In-Reply-To: <199901270340.LAA09860@spinner.netplex.com.au>
References: <199901270220.SAA50280@time.cdrom.com>
<199901270340.LAA09860@spinner.netplex.com.au>
X-Mailer: VM 6.34 under 19.16 "Lille" XEmacs Lucid
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
> "Jordan K. Hubbard" wrote:
> > ===> kdump
> > cc -O -pipe -I/a/time/src/usr.bin/kdump/../ktrace -I/a/time/src/usr.bin/kdump
> /../.. -c /a/time/src/usr.bin/kdump/kdump.c
> > /bin/sh /a/time/src/usr.bin/kdump/mkioctls > ioctl.c
> > cc -O -pipe -I/a/time/src/usr.bin/kdump/../ktrace -I/a/time/src/usr.bin/kdump
> /../.. -c ioctl.c
> > In file included from ioctl.c:66:
> > /usr/include/pccard/cardinfo.h:57: redeclaration of `enum cardstate'
> > /usr/include/pccard/cardinfo.h:57: conflicting types for `noslot'
> > /usr/include/pccard/card.h:57: previous declaration of `noslot'
> > /usr/include/pccard/cardinfo.h:57: conflicting types for `empty'
> > /usr/include/pccard/card.h:57: previous declaration of `empty'
>
> I had this problem.. There is a stray file in /usr/include/pccard - card.h
> should not be there, and the generator script for ktrace/kdump/truss finds
> it.
>
> ===
> revision 1.9
> date: 1997/11/18 21:03:57; author: nate; state: dead; lines: +0 -0
> - Renamed 'card.h' to 'cardinfo.h', to avoid namespace collisions with
> the card.h that config builds.
>
> [ Repository renaming done in the background to save the card.h history ]
> ===
How did this get back 'alive'? It was removed over a year ago...
Nate
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Tue Jan 26 21:53:53 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id VAA01190
for freebsd-current-outgoing; Tue, 26 Jan 1999 21:53:53 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.95.76.54])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA01179
for <freebsd-current@FreeBSD.ORG>; Tue, 26 Jan 1999 21:53:49 -0800 (PST)
(envelope-from sgk@troutmask.apl.washington.edu)
Received: (from sgk@localhost)
by troutmask.apl.washington.edu (8.9.1/8.9.1) id VAA09197;
Tue, 26 Jan 1999 21:55:03 -0800 (PST)
(envelope-from sgk)
From: Steve Kargl <sgk@troutmask.apl.washington.edu>
Message-Id: <199901270555.VAA09197@troutmask.apl.washington.edu>
Subject: Re: removing f2c from base distribution
In-Reply-To: <199901270504.WAA18271@mt.sri.com> from Nate Williams at "Jan 26, 1999 10: 4:53 pm"
To: nate@mt.sri.com (Nate Williams)
Date: Tue, 26 Jan 1999 21:55:03 -0800 (PST)
Cc: jkh@zippy.cdrom.com, nate@mt.sri.com, freebsd-current@FreeBSD.ORG,
jkh@time.cdrom.com
X-Mailer: ELM [version 2.4ME+ PL43 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
Nate Williams wrote:
>
> > Just also remember that Peter will at some point be doing an egcs
> > upgrade, so if that has issues for fortran they should be worked
> > out at this time.
>
> Steven?
>
egcs contains g77 and egcs can be configured to be built with or
without g77. My port of f2c, libf2c, and my new f77(1) should
not conflict with inclusion of g77. In fact, I think g77 which
had used libf2c for its run time library has renamed the library
to libg77, so no conflict should arise.
The question is whether Peter wants to include g77, and whether
people would see this as bloat. I know g77 outperforms f2c+gcc
on my real-world benchmarks by a significant margin.
If my port of f2c and libf2c and the new f77(1) are found to
be adequate, then a committer should remove src/lib/lib{I77,F77,f2c},
src/usr.bin/f2c, and src/gnu/usr.bin/cc/f77. The removal of the
last directory will delete our gcc's knowledge of Fortran.
--
Steve
finger kargl@troutmask.apl.washington.edu
http://troutmask.apl.washington.edu/~clesceri/kargl.html
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Tue Jan 26 22:00:06 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id WAA01730
for freebsd-current-outgoing; Tue, 26 Jan 1999 22:00:06 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from relay.nuxi.com ([169.237.7.38])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA01710;
Tue, 26 Jan 1999 22:00:02 -0800 (PST)
(envelope-from obrien@NUXI.com)
Received: (from obrien@localhost)
by relay.nuxi.com (8.9.1/8.9.1) id WAA07023;
Tue, 26 Jan 1999 22:00:01 -0800 (PST)
(envelope-from obrien)
Date: Tue, 26 Jan 1999 22:00:01 -0800
From: "David O'Brien" <obrien@NUXI.com>
To: Satoshi Asami <asami@FreeBSD.ORG>
Cc: freebsd-current@FreeBSD.ORG
Subject: Re: removing f2c from base distribution
Message-ID: <19990126220000.G4119@relay.nuxi.com>
Reply-To: obrien@NUXI.com
References: <199901262148.NAA07097@troutmask.apl.washington.edu> <199901270116.RAA64007@silvia.hip.berkeley.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.95i
In-Reply-To: <199901270116.RAA64007@silvia.hip.berkeley.edu>; from Satoshi Asami on Tue, Jan 26, 1999 at 05:16:45PM -0800
X-Operating-System: FreeBSD 3.0-CURRENT
Organization: The NUXI BSD group
X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A
X-Pgp-Keyid: 34F9F9D5
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
> Um, I'm still alive but can someone explain me why this can't be a
> "regular" port? Being useful to some but not the majority, no other
> parts of the system depending on it, this looks like a model citizen
> in the ideal ports world. :)
Because we loose control over it. There is a move to push some things
out of the base system and into ports. Fine, but then how does bug fixes
happen? I believe the committed that fixed the f2c problems on the Alpha
really liked having the abilility to do so.
For many parts of the system, I really think we need to make the optional
and installable as ports, but the *maintance* of them should stay along
our traditional means.
--
-- David (obrien@NUXI.com -or- obrien@FreeBSD.org)
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Tue Jan 26 22:01:50 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id WAA01849
for freebsd-current-outgoing; Tue, 26 Jan 1999 22:01:50 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.95.76.54])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA01843;
Tue, 26 Jan 1999 22:01:48 -0800 (PST)
(envelope-from sgk@troutmask.apl.washington.edu)
Received: (from sgk@localhost)
by troutmask.apl.washington.edu (8.9.1/8.9.1) id WAA09222;
Tue, 26 Jan 1999 22:03:04 -0800 (PST)
(envelope-from sgk)
From: Steve Kargl <sgk@troutmask.apl.washington.edu>
Message-Id: <199901270603.WAA09222@troutmask.apl.washington.edu>
Subject: Re: removing f2c from base distribution
In-Reply-To: <199901270151.RAA64117@silvia.hip.berkeley.edu> from Satoshi Asami at "Jan 26, 1999 5:51:25 pm"
To: asami@FreeBSD.ORG (Satoshi Asami)
Date: Tue, 26 Jan 1999 22:03:04 -0800 (PST)
Cc: obrien@NUXI.com, freebsd-current@FreeBSD.ORG
X-Mailer: ELM [version 2.4ME+ PL43 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
Satoshi Asami wrote:
> * Well, actually I did f2c as a port, and it does indeed fit
> * inside the ports paradigm. Please, see my original email in
> * the thread.
>
> Yes, I know that. I was just wondering why people would want it
> otherwise.
>
My original email provided an opportunity to revisit
the sendmail versus postfix controversy. That is, some
software seems to fall short of support for inclusion in the
base distribution but it may be too important for ports.
Maybe the package system that I seen discussed will obviate
the controversy.
--
Steve
finger kargl@troutmask.apl.washington.edu
http://troutmask.apl.washington.edu/~clesceri/kargl.html
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Tue Jan 26 22:06:48 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id WAA02325
for freebsd-current-outgoing; Tue, 26 Jan 1999 22:06:48 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from relay.nuxi.com ([169.237.7.38])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA02320
for <freebsd-current@FreeBSD.ORG>; Tue, 26 Jan 1999 22:06:45 -0800 (PST)
(envelope-from obrien@NUXI.com)
Received: (from obrien@localhost)
by relay.nuxi.com (8.9.1/8.9.1) id WAA07157;
Tue, 26 Jan 1999 22:06:44 -0800 (PST)
(envelope-from obrien)
Date: Tue, 26 Jan 1999 22:06:44 -0800
From: "David O'Brien" <obrien@NUXI.com>
To: Steve Kargl <sgk@troutmask.apl.washington.edu>
Cc: freebsd-current@FreeBSD.ORG
Subject: Re: removing f2c from base distribution
Message-ID: <19990126220644.A7037@relay.nuxi.com>
Reply-To: obrien@NUXI.com
References: <199901270504.WAA18271@mt.sri.com> <199901270555.VAA09197@troutmask.apl.washington.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.95i
In-Reply-To: <199901270555.VAA09197@troutmask.apl.washington.edu>; from Steve Kargl on Tue, Jan 26, 1999 at 09:55:03PM -0800
X-Operating-System: FreeBSD 3.0-CURRENT
Organization: The NUXI BSD group
X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A
X-Pgp-Keyid: 34F9F9D5
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
> The question is whether Peter wants to include g77, and whether
> people would see this as bloat. I know g77 outperforms f2c+gcc
> on my real-world benchmarks by a significant margin.
A good question, is how easy it is to download egcs-g77-1.1.1.tar.gz and
build it into something workable assuming the EGCS C and C++ compilers
are part of the system.
I've got a Bmaked contribified version of EGCS, but didn't do g77. So
maybe a consensus should be made what to do about FORTRAN in the base
system.
--
-- David (obrien@NUXI.com -or- obrien@FreeBSD.org)
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Tue Jan 26 22:13:57 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id WAA03049
for freebsd-current-outgoing; Tue, 26 Jan 1999 22:13:57 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.95.76.54])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA03043;
Tue, 26 Jan 1999 22:13:55 -0800 (PST)
(envelope-from sgk@troutmask.apl.washington.edu)
Received: (from sgk@localhost)
by troutmask.apl.washington.edu (8.9.1/8.9.1) id WAA09286;
Tue, 26 Jan 1999 22:15:11 -0800 (PST)
(envelope-from sgk)
From: Steve Kargl <sgk@troutmask.apl.washington.edu>
Message-Id: <199901270615.WAA09286@troutmask.apl.washington.edu>
Subject: Re: removing f2c from base distribution
In-Reply-To: <19990126220000.G4119@relay.nuxi.com> from "David O'Brien" at "Jan 26, 1999 10: 0: 1 pm"
To: obrien@NUXI.com
Date: Tue, 26 Jan 1999 22:15:11 -0800 (PST)
Cc: asami@FreeBSD.ORG, freebsd-current@FreeBSD.ORG
X-Mailer: ELM [version 2.4ME+ PL43 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
David O'Brien wrote:
> > Um, I'm still alive but can someone explain me why this can't be a
> > "regular" port? Being useful to some but not the majority, no other
> > parts of the system depending on it, this looks like a model citizen
> > in the ideal ports world. :)
>
> Because we loose control over it. There is a move to push some things
> out of the base system and into ports. Fine, but then how does bug fixes
> happen? I believe the committed that fixed the f2c problems on the Alpha
> really liked having the abilility to do so.
David, I'm the person who pointed out the problems with f2c on
alpha, and my alphastation does not run FreeBSd, yet.
Indeed, there were some changes on netlib that deal
with 64bit issues and alignment on page boundaries that now exist
in the port (and these change may not be in the base distribution).
I sent Joerg a patch for current that was 35KB in size.
--
Steve
finger kargl@troutmask.apl.washington.edu
http://troutmask.apl.washington.edu/~clesceri/kargl.html
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Tue Jan 26 22:21:41 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id WAA03845
for freebsd-current-outgoing; Tue, 26 Jan 1999 22:21:41 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.95.76.54])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA03840
for <freebsd-current@FreeBSD.ORG>; Tue, 26 Jan 1999 22:21:40 -0800 (PST)
(envelope-from sgk@troutmask.apl.washington.edu)
Received: (from sgk@localhost)
by troutmask.apl.washington.edu (8.9.1/8.9.1) id WAA09332;
Tue, 26 Jan 1999 22:22:56 -0800 (PST)
(envelope-from sgk)
From: Steve Kargl <sgk@troutmask.apl.washington.edu>
Message-Id: <199901270622.WAA09332@troutmask.apl.washington.edu>
Subject: Re: removing f2c from base distribution
In-Reply-To: <19990126220644.A7037@relay.nuxi.com> from "David O'Brien" at "Jan 26, 1999 10: 6:44 pm"
To: obrien@NUXI.com
Date: Tue, 26 Jan 1999 22:22:56 -0800 (PST)
Cc: freebsd-current@FreeBSD.ORG
X-Mailer: ELM [version 2.4ME+ PL43 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
David O'Brien wrote:
> > The question is whether Peter wants to include g77, and whether
> > people would see this as bloat. I know g77 outperforms f2c+gcc
> > on my real-world benchmarks by a significant margin.
>
> A good question, is how easy it is to download egcs-g77-1.1.1.tar.gz and
> build it into something workable assuming the EGCS C and C++ compilers
> are part of the system.
>
I haven't read the egcs mailinglist in a few weeks, but my impression
is that if you download egcs-g77-1.1.1.tar.gz after building the
egcs C and C++ compilers, you then have to recompile at a minimum
the C compiler. Things may have changed, but g77 is simply a frontend
to the gcc backend. It is not a standalone compiler.
--
Steve
finger kargl@troutmask.apl.washington.edu
http://troutmask.apl.washington.edu/~clesceri/kargl.html
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Tue Jan 26 22:24:12 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id WAA04097
for freebsd-current-outgoing; Tue, 26 Jan 1999 22:24:12 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from gratis.grondar.za (gratis.grondar.za [196.7.18.65])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA04087
for <freebsd-current@FreeBSD.ORG>; Tue, 26 Jan 1999 22:24:07 -0800 (PST)
(envelope-from mark@grondar.za)
Received: from greenpeace.grondar.za (greenpeace.grondar.za [196.7.18.132])
by gratis.grondar.za (8.9.2/8.9.2) with ESMTP id IAA74675;
Wed, 27 Jan 1999 08:23:54 +0200 (SAST)
(envelope-from mark@grondar.za)
Received: from grondar.za (localhost [127.0.0.1])
by greenpeace.grondar.za (8.9.2/8.9.2) with ESMTP id IAA01480;
Wed, 27 Jan 1999 08:23:52 +0200 (SAST)
(envelope-from mark@grondar.za)
Message-Id: <199901270623.IAA01480@greenpeace.grondar.za>
To: obrien@NUXI.com
cc: Steve Kargl <sgk@troutmask.apl.washington.edu>,
freebsd-current@FreeBSD.ORG
Subject: Re: removing f2c from base distribution
In-Reply-To: Your message of " Tue, 26 Jan 1999 22:06:44 PST." <19990126220644.A7037@relay.nuxi.com>
References: <199901270504.WAA18271@mt.sri.com> <199901270555.VAA09197@troutmask.apl.washington.edu> <19990126220644.A7037@relay.nuxi.com>
Date: Wed, 27 Jan 1999 08:23:50 +0200
From: Mark Murray <mark@grondar.za>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
"David O'Brien" wrote:
> I've got a Bmaked contribified version of EGCS, but didn't do g77. So
> maybe a consensus should be made what to do about FORTRAN in the base
> system.
If you are collecting votes, please add mine; I feel quite strongly
(knowing the scientists that I do that use Fortran) that it _should_
be in the base system. Please include it.
M
--
Mark Murray
Join the anti-SPAM movement: http://www.cauce.org
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Tue Jan 26 22:30:56 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id WAA04584
for freebsd-current-outgoing; Tue, 26 Jan 1999 22:30:56 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from dingo.cdrom.com (castles131.castles.com [208.214.165.131])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA04579
for <freebsd-current@FreeBSD.ORG>; Tue, 26 Jan 1999 22:30:54 -0800 (PST)
(envelope-from mike@dingo.cdrom.com)
Received: from dingo.cdrom.com (LOCALHOST [127.0.0.1])
by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id WAA21695;
Tue, 26 Jan 1999 22:26:47 -0800 (PST)
(envelope-from mike@dingo.cdrom.com)
Message-Id: <199901270626.WAA21695@dingo.cdrom.com>
X-Mailer: exmh version 2.0.2 2/24/98
To: Mark Murray <mark@grondar.za>
cc: obrien@NUXI.com, Steve Kargl <sgk@troutmask.apl.washington.edu>,
freebsd-current@FreeBSD.ORG
Subject: Re: removing f2c from base distribution
In-reply-to: Your message of "Wed, 27 Jan 1999 08:23:50 +0200."
<199901270623.IAA01480@greenpeace.grondar.za>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Tue, 26 Jan 1999 22:26:46 -0800
From: Mike Smith <mike@smith.net.au>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
> "David O'Brien" wrote:
> > I've got a Bmaked contribified version of EGCS, but didn't do g77. So
> > maybe a consensus should be made what to do about FORTRAN in the base
> > system.
>
> If you are collecting votes, please add mine; I feel quite strongly
> (knowing the scientists that I do that use Fortran) that it _should_
> be in the base system. Please include it.
We've already established that it doesn't need to be in the base system.
Your scientist friends are probably already going to be installing
their favorite text editors; it's no harder to install the Fortran
support.
--
\\ Sometimes you're ahead, \\ Mike Smith
\\ sometimes you're behind. \\ mike@smith.net.au
\\ The race is long, and in the \\ msmith@freebsd.org
\\ end it's only with yourself. \\ msmith@cdrom.com
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Tue Jan 26 22:32:45 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id WAA04706
for freebsd-current-outgoing; Tue, 26 Jan 1999 22:32:45 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from gratis.grondar.za (gratis.grondar.za [196.7.18.65])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA04701
for <freebsd-current@freebsd.org>; Tue, 26 Jan 1999 22:32:40 -0800 (PST)
(envelope-from mark@grondar.za)
Received: from greenpeace.grondar.za (greenpeace.grondar.za [196.7.18.132])
by gratis.grondar.za (8.9.2/8.9.2) with ESMTP id IAA74703;
Wed, 27 Jan 1999 08:32:34 +0200 (SAST)
(envelope-from mark@grondar.za)
Received: from grondar.za (localhost [127.0.0.1])
by greenpeace.grondar.za (8.9.2/8.9.2) with ESMTP id IAA01637;
Wed, 27 Jan 1999 08:32:30 +0200 (SAST)
(envelope-from mark@grondar.za)
Message-Id: <199901270632.IAA01637@greenpeace.grondar.za>
To: Randy Bush <randy@psg.com>
cc: freebsd-current@FreeBSD.ORG
Subject: Re: sdr25 wants to reinstall xfree
In-Reply-To: Your message of " Tue, 26 Jan 1999 19:17:16 PST." <m105LTg-0008G4C@rip.psg.com>
References: <m105LTg-0008G4C@rip.psg.com>
Date: Wed, 27 Jan 1999 08:32:29 +0200
From: Mark Murray <mark@grondar.za>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
Randy Bush wrote:
> is this for real or is it an aout-to-elf thing?
This is for real. Tk80 is looking for ELFed X11 (You did recompile
your X, Right? If not then it is an ELF thing). The XFree86 port
is rather good, IMHO.
M
> randy
>
>
> ===> Generating temporary packing list
> /bin/ln -sf libtcl80.so.1 /usr/local/lib/libtcl80.so
> /usr/bin/env OBJFORMAT=elf /sbin/ldconfig -m /usr/local/lib
> /usr/bin/env PKG_PREFIX=/usr/local /bin/sh /usr/ports/lang/tcl80/pkg/INSTALL.
tclsh
> ===> Registering installation for tcl-8.0.4
> ===> Returning to build of tk-8.0.4
> ===> tk-8.0.4 depends on shared library: X11.6 - not found
> ===> Verifying install for X11.6 in /usr/ports/x11/XFree86
>
> Assuming that you have fetched a USA-Legal Wraphelp.c.
> >> X333src-1.tgz doesn't seem to exist on this system.
> >> Attempting to fetch from ftp://ftp.xfree86.org/pub/XFree86/3.3.3/source/.
> Receiving X333src-1.tgz (16596763 bytes): 100%
> 16596763 bytes transfered in 132.8 seconds (122.00 Kbytes/s)
> >> X333src-2.tgz doesn't seem to exist on this system.
> >> Attempting to fetch from ftp://ftp.xfree86.org/pub/XFree86/3.3.3/source/.
> Receiving X333src-2.tgz (14501435 bytes): 100%
> 14501435 bytes transfered in 111.4 seconds (127.07 Kbytes/s)
> >> 3.3.3-3.3.3.1.diff.gz doesn't seem to exist on this system.
> >> Attempting to fetch from ftp://ftp.xfree86.org/pub/XFree86/3.3.3.1/fixes/.
> Receiving 3.3.3-3.3.3.1.diff.gz (178472 bytes): 100%
> 178472 bytes transfered in 1.7 seconds (99.77 Kbytes/s)
> ===> Extracting for XFree86-3.3.3.1
> >> Checksum OK for xc/X333src-1.tgz.
> >> Checksum OK for xc/X333src-2.tgz.
> >> Checksum OK for xc/3.3.3-3.3.3.1.diff.gz.
> ===> Patching for XFree86-3.3.3.1
> ===> Applying distribution patches for XFree86-3.3.3.1
> ===> Configuring for XFree86-3.3.3.1
> *** I don't see the static library for tk version in /usr/local/lib.
> *** XF86Setup will not be installed. If you want to build this program
> *** install tk 4.2 or 8.0 first.
>
> Which servers do you wish to build, you can save a lot of disk space
> by only compiling the server you will be using. It will also save you
> considerable compile time.
> Do you want to build the VGA16 server? [YES] ^C
>
> To Unsubscribe: send mail to majordomo@FreeBSD.org
> with "unsubscribe freebsd-multimedia" in the body of the message
>
> To Unsubscribe: send mail to majordomo@FreeBSD.org
> with "unsubscribe freebsd-current" in the body of the message
--
Mark Murray
Join the anti-SPAM movement: http://www.cauce.org
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Tue Jan 26 22:36:58 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id WAA04924
for freebsd-current-outgoing; Tue, 26 Jan 1999 22:36:58 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from piglet.dstc.edu.au (piglet.dstc.edu.au [130.102.176.1])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA04914
for <freebsd-current@freebsd.org>; Tue, 26 Jan 1999 22:36:53 -0800 (PST)
(envelope-from ggm@asuncion.dstc.edu.au)
Received: from asuncion.dstc.edu.au (asuncion.dstc.edu.au [130.102.176.155])
by piglet.dstc.edu.au (8.8.7/8.8.7) with ESMTP id QAA26204
for <freebsd-current@freebsd.org>; Wed, 27 Jan 1999 16:36:51 +1000 (EST)
Received: (from ggm@localhost)
by asuncion.dstc.edu.au (8.8.8+Sun/8.8.8) id QAA00931
for freebsd-current@freebsd.org; Wed, 27 Jan 1999 16:36:50 +1000 (EST)
Date: Wed, 27 Jan 1999 16:36:50 +1000 (EST)
From: George Michaelson <ggm@dstc.edu.au>
Message-Id: <199901270636.QAA00931@asuncion.dstc.edu.au>
To: freebsd-current@FreeBSD.ORG
Subject: IPSEC in current: any success stories?
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
If anybody else in current-land is able to discuss
making ipsec work correctly, using the codebase
cross-ported from OpenBSD, I'd love some hints.
This isn't something I'd expect anybody wants discussed
in current itself, I'm just hunting the right people!
cheers
-George
(I have it compiled/installed ok. Making bits fly is my problem)
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Tue Jan 26 22:43:13 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id WAA05533
for freebsd-current-outgoing; Tue, 26 Jan 1999 22:43:13 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.95.76.54])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA05528
for <freebsd-current@FreeBSD.ORG>; Tue, 26 Jan 1999 22:43:12 -0800 (PST)
(envelope-from sgk@troutmask.apl.washington.edu)
Received: (from sgk@localhost)
by troutmask.apl.washington.edu (8.9.1/8.9.1) id WAA09457;
Tue, 26 Jan 1999 22:44:11 -0800 (PST)
(envelope-from sgk)
From: Steve Kargl <sgk@troutmask.apl.washington.edu>
Message-Id: <199901270644.WAA09457@troutmask.apl.washington.edu>
Subject: Re: removing f2c from base distribution
In-Reply-To: <199901270626.WAA21695@dingo.cdrom.com> from Mike Smith at "Jan 26, 1999 10:26:46 pm"
To: mike@smith.net.au (Mike Smith)
Date: Tue, 26 Jan 1999 22:44:11 -0800 (PST)
Cc: mark@grondar.za, obrien@NUXI.com, freebsd-current@FreeBSD.ORG
X-Mailer: ELM [version 2.4ME+ PL43 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
Mike Smith wrote:
> > "David O'Brien" wrote:
> > > I've got a Bmaked contribified version of EGCS, but didn't do g77. So
> > > maybe a consensus should be made what to do about FORTRAN in the base
> > > system.
> >
> > If you are collecting votes, please add mine; I feel quite strongly
> > (knowing the scientists that I do that use Fortran) that it _should_
> > be in the base system. Please include it.
>
> We've already established that it doesn't need to be in the base system.
This may be true of f2c because it is not tightly bound to the
FSF compiler technology.
> Your scientist friends are probably already going to be installing
> their favorite text editors; it's no harder to install the Fortran
> support.
g77 is a frontend to the FSF compiler backend, and thus it is bound
to specific versions. So, it could become a support nightmare to ensure
a g77 port is in sync with the egcs backend in the base distribution.
It might even be impractical to try to build a standalone g77 port.
--
Steve
finger kargl@troutmask.apl.washington.edu
http://troutmask.apl.washington.edu/~clesceri/kargl.html
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Tue Jan 26 22:58:15 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id WAA07221
for freebsd-current-outgoing; Tue, 26 Jan 1999 22:58:15 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from rf900.physics.usyd.edu.au (rf900.physics.usyd.edu.au [129.78.129.109])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA07215
for <current@FreeBSD.ORG>; Tue, 26 Jan 1999 22:58:09 -0800 (PST)
(envelope-from dawes@rf900.physics.usyd.edu.au)
Received: (from dawes@localhost)
by rf900.physics.usyd.edu.au (8.9.1a/8.9.1) id RAA12691;
Wed, 27 Jan 1999 17:57:58 +1100 (EST)
Message-ID: <19990127175758.G11595@rf900.physics.usyd.edu.au>
Date: Wed, 27 Jan 1999 17:57:58 +1100
From: David Dawes <dawes@rf900.physics.usyd.edu.au>
To: Bruce Evans <bde@zeta.org.au>, current@FreeBSD.ORG
Subject: Re: Promise FastTrack PCI IDE controller
References: <199901221254.XAA23422@godzilla.zeta.org.au>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.93.2i
In-Reply-To: <199901221254.XAA23422@godzilla.zeta.org.au>; from Bruce Evans on Fri, Jan 22, 1999 at 11:54:59PM +1100
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
On Fri, Jan 22, 1999 at 11:54:59PM +1100, Bruce Evans wrote:
>>I've been playing with a Promise FastTrack RAID (IDE) controller with
>>3.0-current as of yesterday. Although it is recognised in the PCI bus
>>probe as a "Promise Ultra/33" (it has the same vendor/chip ID as the
>>non-RAID card), the probes in i386/isa/wd.c fail. I added some debugging
>>printfs to the code, and have found that wdreset() is failing. By
>>changing the code to ignore that failure, it gets further, and correctly
>>identifies the attached disks. I can even access the disks sufficiently
>>to read the partition table with fdisk (but with timeouts).
>
>Errors in wdreset() for the Promise (at least for the Ultra/33)
>probably mean that du->dk_altport is not initialized properly. (Setting
>du->dk_altport is the only thing that is very special for the Promise,
>and wdreset() is the only function that uses du->dk_altport for anything
>except debugging.) The wrong setting of du->dk_altport may be caused by
>the section of code in pci/ide_pci.c described by "/* This code below
>is mighty bogus. ...". Bugs there may also break DMA capability.
There is a problem with the way du->dk_altport is set in wdattach. It
is set correctly in wdprobe, but incorrectly in wdattach. The following
patch fixes that. However, this isn't sufficient to get the card working
with the RAID BIOS is installed. The wdreset() problem is, however,
more noticable in that case because it then it gets called after the
attach.
David
--
*** wd.c.ORIG Sun Jan 17 16:46:24 1999
--- wd.c Wed Jan 27 17:55:33 1999
***************
*** 422,428 ****
--- 425,432 ----
struct isa_device *wdup;
struct disk *du;
struct wdparams *wp;
+ int interface;
dvp->id_intr = wdintr;
if (dvp->id_unit >= NWDC)
***************
*** 470,476 ****
du->dk_lunit = lunit;
du->dk_port = dvp->id_iobase;
! du->dk_altport = du->dk_port + wd_ctlr;
/*
* Use the individual device flags or the controller
* flags.
--- 475,490 ----
du->dk_lunit = lunit;
du->dk_port = dvp->id_iobase;
! interface = dvp->id_unit / 2;
! if (wddma[interface].wdd_candma != NULL) {
! du->dk_dmacookie =
! wddma[interface].wdd_candma(dvp->id_iobase,
! du->dk_ctrlr, du->dk_unit);
! du->dk_altport =
! wddma[interface].wdd_altiobase(du->dk_dmacookie);
! }
! if (du->dk_altport == 0)
! du->dk_altport = du->dk_port + wd_ctlr;
/*
* Use the individual device flags or the controller
* flags.
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Tue Jan 26 22:59:41 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id WAA07478
for freebsd-current-outgoing; Tue, 26 Jan 1999 22:59:41 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from mail2.lig.bellsouth.net (mail2.lig.bellsouth.net [205.152.0.56])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA07469
for <current@freebsd.org>; Tue, 26 Jan 1999 22:59:37 -0800 (PST)
(envelope-from gljohns@bellsouth.net)
Received: from gforce.johnson.home (host-209-214-151-74.msy.bellsouth.net [209.214.151.74])
by mail2.lig.bellsouth.net (8.8.8-spamdog/8.8.5) with ESMTP id BAA17897;
Wed, 27 Jan 1999 01:58:53 -0500 (EST)
Received: (from glenn@localhost)
by gforce.johnson.home (8.9.2/8.9.2) id AAA10537;
Wed, 27 Jan 1999 00:58:50 -0600 (CST)
(envelope-from glenn)
From: Glenn Johnson <gljohns@bellsouth.net>
Date: Wed, 27 Jan 1999 00:58:50 -0600
To: current@FreeBSD.ORG
Cc: Steve Kargl <sgk@troutmask.apl.washington.edu>,
"David O'Brien" <obrien@NUXI.com>
Subject: Re: removing f2c from base distribution
Message-ID: <19990127005850.A10486@gforce.johnson.home>
References: <199901270504.WAA18271@mt.sri.com> <199901270555.VAA09197@troutmask.apl.washington.edu> <19990126220644.A7037@relay.nuxi.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.95.1i
In-Reply-To: <19990126220644.A7037@relay.nuxi.com>; from David O'Brien on Tue, Jan 26, 1999 at 10:06:44PM -0800
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
On Tue, Jan 26, 1999 at 10:06:44PM -0800, David O'Brien wrote:
> > The question is whether Peter wants to include g77, and whether
> > people would see this as bloat. I know g77 outperforms f2c+gcc
> > on my real-world benchmarks by a significant margin.
>
> A good question, is how easy it is to download egcs-g77-1.1.1.tar.gz and
> build it into something workable assuming the EGCS C and C++ compilers
> are part of the system.
>
> I've got a Bmaked contribified version of EGCS, but didn't do g77. So
> maybe a consensus should be made what to do about FORTRAN in the base
> system.
>
I for one feel that Fortran should remain as part of the base system,
either as f2c or g77. I would prefer g77 because of the performance
advantage and compatability with Fortran code being ported from other
systems. This is something I do quite a bit of.
I have contributed a couple of ports that are written in Fortran and I
plan on contributing more. I have been waiting to see what decisions
were made in this area however before proceeding.
The biggest problem has been that the port of g77 has not worked
properly for quite some time and in fact is currently marked as
broken. I would anticipate that this situation would not change much in
the future if the base gcc (egcs?) is modified far enough away from a
"standard" gcc distribution, as is currently the case with our gcc. As
far as getting g77 from the egcs port, well, the release versions have
been fine for g77 but the snapshots have been hit and miss. The ports
system has not provided a reliable means of Fortran support, IMHO.
However, if g77 were part of the base FreeBSD system, assuming f2c is
ripped out, then Fortran support would be "gaurenteed" to be there when
needed. I understand that most people using FreeBSD are using it for
server tasks and C development. However, FreeBSD is also an excellent
OS for a scientific workstation, and that means Fortran is essential. I
run a "farm" of 6 dual CPU PPro/PII systems running quantum chemical
calculations 24/7. I do my part to get my colleagues to try FreeBSD
instead of NT and Linux. Removing Fortran support from the base system
will make that a tougher job.
Thanks.
--
Glenn Johnson
gljohns@bellsouth.net
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Wed Jan 27 01:33:36 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id BAA20379
for freebsd-current-outgoing; Wed, 27 Jan 1999 01:33:36 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from iquest3.iquest.net (iquest3.iquest.net [209.43.20.203])
by hub.freebsd.org (8.8.8/8.8.8) with SMTP id BAA20374
for <freebsd-current@FreeBSD.ORG>; Wed, 27 Jan 1999 01:33:35 -0800 (PST)
(envelope-from toor@y.dyson.net)
Received: (qmail 10673 invoked from network); 27 Jan 1999 09:33:32 -0000
Received: from dyson.iquest.net (HELO y.dyson.net) (198.70.144.127)
by iquest3.iquest.net with SMTP; 27 Jan 1999 09:33:32 -0000
Received: (from root@localhost)
by y.dyson.net (8.9.1/8.9.1) id EAA00703;
Wed, 27 Jan 1999 04:33:28 -0500 (EST)
Message-Id: <199901270933.EAA00703@y.dyson.net>
Subject: Re: Memory usage weirdness
In-Reply-To: <19990126183430.A61727@thekeep.org> from Dan Root at "Jan 26, 99 06:34:30 pm"
To: dar@thekeep.org (Dan Root)
Date: Wed, 27 Jan 1999 04:33:28 -0500 (EST)
Cc: freebsd-current@FreeBSD.ORG
From: "John S. Dyson" <dyson@iquest.net>
Reply-To: dyson@iquest.net
X-Mailer: ELM [version 2.4ME+ PL38 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
Dan Root said:
Content-Description: Mail message
>
> Is this normal, or should I look for some process that's thrashing through
> vast amounts of pages in short periods of time?
>
It is normal and expected. A little secret about FreeBSD's VM is that
it works on a page demand type timeclock and not an arbitrary real time
timeclock. This helps the system (partially) to be self-tuning.
--
John | Never try to teach a pig to sing,
dyson@iquest.net | it makes one look stupid
jdyson@nc.com | and it irritates the pig.
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Wed Jan 27 01:40:59 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id BAA20732
for freebsd-current-outgoing; Wed, 27 Jan 1999 01:40:59 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from abc.123.org (123.org [194.172.236.49])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA20727
for <freebsd-current@FreeBSD.ORG>; Wed, 27 Jan 1999 01:40:57 -0800 (PST)
(envelope-from k@abc.123.org)
Received: (from k@localhost)
by abc.123.org (8.9.1/8.9.1) id KAA06876;
Wed, 27 Jan 1999 10:40:37 +0100 (CET)
(envelope-from k)
Message-ID: <19990127104037.B772@123.org>
Date: Wed, 27 Jan 1999 10:40:37 +0100
From: Kai Voigt <k@123.org>
To: "Jordan K. Hubbard" <jkh@zippy.cdrom.com>,
The Hermit Hacker <scrappy@hub.org>
Cc: freebsd-current@FreeBSD.ORG
Subject: Re: Hate to ask, but...aout -> elf ...
References: <Pine.BSF.4.05.9901261440120.94383-100000@thelab.hub.org> <76756.917402980@zippy.cdrom.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.93.2i
In-Reply-To: <76756.917402980@zippy.cdrom.com>; from Jordan K. Hubbard on Tue, Jan 26, 1999 at 06:09:40PM -0800
Organization: 123.org
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
Jordan K. Hubbard wrote:
> > Is it a simple matter of 'make aout-to-elf', or...?
>
> As of today, just type "make upgrade NOCONFIRM=YES" and wait for the
> server to reboot some n hours later (where n is governed by the speed
> of your machine :).
you deserve an error message when you wake up over there...
/usr/src (admin@abc) # make upgrade
"/usr/src/Makefile.upgrade", line 258: Need an operator
"/usr/src/Makefile.upgrade", line 259: Need an operator
"/usr/src/Makefile.upgrade", line 260: Need an operator
"/usr/src/Makefile.upgrade", line 266: Need an operator
make: fatal errors encountered -- cannot continue
*** Error code 1
Stop.
This happens on a 3.0R with freshly cvup'ed -current /usr/src/
Kai
--
kai voigt hamburger chaussee 36
24113 kiel
0431-642677
http://k.123.org/
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Wed Jan 27 02:48:49 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id CAA26833
for freebsd-current-outgoing; Wed, 27 Jan 1999 02:48:49 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA26828
for <current@freebsd.org>; Wed, 27 Jan 1999 02:48:47 -0800 (PST)
(envelope-from phk@critter.freebsd.dk)
Received: from critter.freebsd.dk (localhost [127.0.0.1])
by critter.freebsd.dk (8.9.1/8.8.5) with ESMTP id LAA29765
for <current@freebsd.org>; Wed, 27 Jan 1999 11:48:18 +0100 (CET)
To: current@FreeBSD.ORG
Subject: "JAIL" code headed for -current.
From: Poul-Henning Kamp <phk@FreeBSD.ORG>
Date: Wed, 27 Jan 1999 11:48:16 +0100
Message-ID: <29763.917434096@critter.freebsd.dk>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
I'm polishing up the "JAIL" code I wrote and readying it for -current.
This code provides an optional strenthening of the chroot() jail
as we know it, and will provide safe sandboxes for most practical
uses.
The biggest impact of this is a new argument to the suser() call
all over the kernel:
suser(NOJAIL, bla, bla);
or
suser(0, bla, bla);
The NOJAIL option means that a jailed root fails the test.
I will add this extra arg to suser() in the first commit.
Each Jail can optionally be assigned one IP number, which they
have access to. All connections to and from that jail will
use that IP#.
If there is interest, this code will be merged to 3.1 as well.
This work was sponsored by: www.servetheweb.com
--
Poul-Henning Kamp FreeBSD coreteam member
phk@FreeBSD.ORG "Real hackers run -current on their laptop."
FreeBSD -- It will take a long time before progress goes too far!
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Wed Jan 27 02:53:53 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id CAA27336
for freebsd-current-outgoing; Wed, 27 Jan 1999 02:53:53 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from top.worldcontrol.com (snblitz.sc.scruznet.com [165.227.132.84])
by hub.freebsd.org (8.8.8/8.8.8) with SMTP id CAA27330
for <freebsd-current@freebsd.org>; Wed, 27 Jan 1999 02:53:50 -0800 (PST)
(envelope-from brian@worldcontrol.com)
From: brian@worldcontrol.com
Received: (qmail 404 invoked by uid 100); 27 Jan 1999 10:54:45 -0000
Date: Wed, 27 Jan 1999 02:54:45 -0800
To: freebsd-current@FreeBSD.ORG
Subject: pcm0: timeout flushing dbuf_out, chan 0 cnt 0xfffa41ec flags 0x00000241
Message-ID: <19990127025445.A336@top.worldcontrol.com>
Mail-Followup-To: freebsd-current@freebsd.org
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.95.1i
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
pcm no longer works correctly the Yamaha YMF715 based sound system
of my laptop.
It was working fine up till shortly before secure/libcrypt broke on -current.
The kernel with broken pcm0 is from:
FreeBSD top.worldcontrol.com 4.0-CURRENT FreeBSD 4.0-CURRENT #3: Mon Jan 25 02:53:31 PST 1999 brian@bls2.worldcontrol.com:/ust/src/sys/compile/LAPTOP i386
# cat /usr/X11R6/lib/X11/afterstep/sounds/drip.au > /dev/audio
[produces 'drip scratchy hiss scratchy hiss scratchy his...']
^C
timeout flushing dbuf_out, chan 0 cnt 0xffff669b flags 0x00000041
mpg123 given the song 'I am pretty, oh so pretty' will produce
I I I I I am am am am am prre prre prre ty ty ty ty , , , , oh oh oh ...
like noise.
xanim plays entirely correct audio.
rvplayer (linux version) plays correctly except last few seconds repeat.
mtv (linux, multithreaded version) has the 'I am pretty' stutter
effect in hi and med quality audio modes. It works correctly in
low quality mode.
I did change to a AMD K6-2 333MHz processor during that time.
Used to be a Intel P5-233MMX.
--
Brian Litzinger <brian@litzinger.com>
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Wed Jan 27 03:00:03 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id DAA28069
for freebsd-current-outgoing; Wed, 27 Jan 1999 03:00:03 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from zeus.theinternet.com.au (zeus.theinternet.com.au [203.34.176.2])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA28005
for <freebsd-current@FreeBSD.ORG>; Wed, 27 Jan 1999 02:59:58 -0800 (PST)
(envelope-from akm@zeus.theinternet.com.au)
Received: (from akm@localhost)
by zeus.theinternet.com.au (8.8.7/8.8.7) id UAA00972;
Wed, 27 Jan 1999 20:59:45 +1000 (EST)
(envelope-from akm)
From: Andrew Kenneth Milton <akm@zeus.theinternet.com.au>
Message-Id: <199901271059.UAA00972@zeus.theinternet.com.au>
Subject: Re: pcm0: timeout flushing dbuf_out, chan 0 cnt 0xfffa41ec flags 0x00000241
In-Reply-To: <19990127025445.A336@top.worldcontrol.com> from "brian@worldcontrol.com" at "Jan 27, 99 02:54:45 am"
To: brian@worldcontrol.com
Date: Wed, 27 Jan 1999 20:59:45 +1000 (EST)
Cc: freebsd-current@FreeBSD.ORG
X-Mailer: ELM [version 2.4ME+ PL32 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
+----[ brian@worldcontrol.com ]---------------------------------------------
| pcm no longer works correctly the Yamaha YMF715 based sound system
| of my laptop.
|
| mpg123 given the song 'I am pretty, oh so pretty' will produce
|
| I I I I I am am am am am prre prre prre ty ty ty ty , , , , oh oh oh ...
|
| like noise.
I had this when I had incorrectly set the 'flags' to pcm for my
2nd dma channel.
Did you rebuild a kernel and not respecify the flags (or not specify
them in the kernel config).?
--
Totally Holistic Enterprises Internet| P:+61 7 3870 0066 | Andrew
The Internet (Aust) Pty Ltd | F:+61 7 3870 4477 | Milton
ACN: 082 081 472 | M:+61 416 022 411 |72 Col .Sig
PO Box 837 Indooroopilly QLD 4068 |akm@theinternet.com.au|Specialist
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Wed Jan 27 03:03:25 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id DAA28333
for freebsd-current-outgoing; Wed, 27 Jan 1999 03:03:25 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from server.noc.demon.net (server.noc.demon.net [193.195.224.4])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA28286;
Wed, 27 Jan 1999 03:03:11 -0800 (PST)
(envelope-from geoffb@gti.noc.demon.net)
Received: by server.noc.demon.net; id LAA11724; Wed, 27 Jan 1999 11:03:10 GMT
Received: from gti.noc.demon.net(195.11.55.101) by inside.noc.demon.net via smap (3.2)
id xmab11717; Wed, 27 Jan 99 11:02:56 GMT
Received: (from geoffb@localhost)
by gti.noc.demon.net (8.8.8/8.8.8) id LAA27235;
Wed, 27 Jan 1999 11:02:54 GMT
Message-ID: <19990127110254.D20146@gti.noc.demon.net>
Date: Wed, 27 Jan 1999 11:02:54 +0000
From: Geoff Buckingham <geoffb@demon.net>
To: Poul-Henning Kamp <phk@FreeBSD.ORG>, current@FreeBSD.ORG
Subject: Re: "JAIL" code headed for -current.
Reply-To: Geoff Buckingham <geoffb@demon.net>
References: <29763.917434096@critter.freebsd.dk>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.93.2i
In-Reply-To: <29763.917434096@critter.freebsd.dk>; from Poul-Henning Kamp on Wed, Jan 27, 1999 at 11:48:16AM +0100
Organisation: Demon Internet Ltd
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
Previously on Wed, Jan 27, 1999 at 11:48:16AM +0100, Poul-Henning Kamp wrote:
:
:
: If there is interest, this code will be merged to 3.1 as well.
:
I would like to express interest at this point.
--
Geoff Buckingham
Demon Internet
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Wed Jan 27 03:11:34 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id DAA29099
for freebsd-current-outgoing; Wed, 27 Jan 1999 03:11:34 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from axl.noc.iafrica.com (axl.noc.iafrica.com [196.31.1.175])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA29090
for <current@freebsd.org>; Wed, 27 Jan 1999 03:11:20 -0800 (PST)
(envelope-from sheldonh@axl.noc.iafrica.com)
Received: from sheldonh (helo=axl.noc.iafrica.com)
by axl.noc.iafrica.com with local-esmtp (Exim 2.10 #1)
id 105Srj-000JOb-00; Wed, 27 Jan 1999 13:10:35 +0200
From: Sheldon Hearn <axl@iafrica.com>
To: Jeroen Ruigrok/Asmodai <asmodai@wxs.nl>
cc: Andrew Gordon <arg@arg1.demon.co.uk>, current@FreeBSD.ORG,
Matthew Dillon <dillon@apollo.backplane.com>
Subject: Re: 4.0-Current, netscape halts system
In-reply-to: Your message of "Tue, 26 Jan 1999 07:46:18 +0100."
<XFMail.990126074618.asmodai@wxs.nl>
Date: Wed, 27 Jan 1999 13:10:35 +0200
Message-ID: <74560.917435435@axl.noc.iafrica.com>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
On Tue, 26 Jan 1999 07:46:18 +0100, Jeroen Ruigrok/Asmodai wrote:
> Yer kidding right? A program that _needs_ 100 MB or more? Surely yer
> kidding... I haven't seen a program in normal corporate/home use that
> justifies the memory usage of 100 MB or more including NetScape's
> Navigator/Communicator.
You haven't had to provide an ISP-grade news or proxy service yet, have
you? :-)
Ignoring that comment, since I assume you meant "I haven't seen an
end-user application in...", it _is_ conceivable that the way Netscape
keeps track of its cache _does_ mean an inevitable requirement for
enormous amounts of memory.
I still don't think we're getting any closer to the question "Why is
Netscape unstable on CURRENT when it worked fine for me on STABLE?" The
problem seems to be that those who know enough to offer a useful answer
don't seem to be seeing the instability reported.
So if this thread isn't going to be dropped, the focus should probably
be shifted to "What information should we request from people who have
this problem?"
Ciao,
Sheldon.
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Wed Jan 27 03:14:36 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id DAA29411
for freebsd-current-outgoing; Wed, 27 Jan 1999 03:14:36 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from axl.noc.iafrica.com (axl.noc.iafrica.com [196.31.1.175])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA29403
for <freebsd-current@freebsd.org>; Wed, 27 Jan 1999 03:14:29 -0800 (PST)
(envelope-from sheldonh@axl.noc.iafrica.com)
Received: from sheldonh (helo=axl.noc.iafrica.com)
by axl.noc.iafrica.com with local-esmtp (Exim 2.10 #1)
id 105Sur-000JRM-00; Wed, 27 Jan 1999 13:13:49 +0200
From: Sheldon Hearn <axl@iafrica.com>
To: David Wolfskill <dhw@whistle.com>
cc: freebsd-current@FreeBSD.ORG, meyerd1@fang.cs.sunyit.edu,
bonnetf@bart.esiee.fr
Subject: Re: NIS with HPUX 10.20
In-reply-to: Your message of "Tue, 26 Jan 1999 09:51:05 PST."
<199901261751.JAA05102@pau-amma.whistle.com>
Date: Wed, 27 Jan 1999 13:13:49 +0200
Message-ID: <74731.917435629@axl.noc.iafrica.com>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
On Tue, 26 Jan 1999 09:51:05 PST, David Wolfskill wrote:
> I did note that, unlike the SNAP, the result had a /usr/libexec/ld.so;
Did you make your RELENG_3 world with or without -DNOAOUT? I don't think
/usr/libexec is created for a -DNOAOUT world. I've noticed this
particularly with jdk.
Ciao,
Sheldon.
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Wed Jan 27 03:22:20 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id DAA00185
for freebsd-current-outgoing; Wed, 27 Jan 1999 03:22:20 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from axl.noc.iafrica.com (axl.noc.iafrica.com [196.31.1.175])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA00178
for <freebsd-current@freebsd.org>; Wed, 27 Jan 1999 03:22:15 -0800 (PST)
(envelope-from sheldonh@axl.noc.iafrica.com)
Received: from sheldonh (helo=axl.noc.iafrica.com)
by axl.noc.iafrica.com with local-esmtp (Exim 2.10 #1)
id 105T10-000JVZ-00; Wed, 27 Jan 1999 13:20:10 +0200
From: Sheldon Hearn <axl@iafrica.com>
To: Mike Smith <mike@smith.net.au>
cc: David Wolfskill <dhw@whistle.com>, freebsd-current@FreeBSD.ORG,
meyerd1@fang.cs.sunyit.edu, bonnetf@bart.esiee.fr
Subject: Re: NIS with HPUX 10.20
In-reply-to: Your message of "Tue, 26 Jan 1999 11:01:25 PST."
<199901261901.LAA18345@dingo.cdrom.com>
Date: Wed, 27 Jan 1999 13:20:10 +0200
Message-ID: <74992.917436010@axl.noc.iafrica.com>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
On Tue, 26 Jan 1999 11:01:25 PST, Mike Smith wrote:
> Read the install(1) manpage, particularly the -C option.
The question, though, is _why_ the need to use -C when installing
ld-elf.so.1? It's not flagged schg, from the looks of my box.
Ciao,
Sheldon.
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Wed Jan 27 03:30:05 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id DAA01030
for freebsd-current-outgoing; Wed, 27 Jan 1999 03:29:42 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from speed.rcc.on.ca (radio163.mipps.net [205.189.197.163] (may be forged))
by hub.freebsd.org (8.8.8/8.8.8) with SMTP id DAA01024
for <current@FreeBSD.ORG>; Wed, 27 Jan 1999 03:29:40 -0800 (PST)
(envelope-from tr49986@rcc.on.ca)
Received: from chopper ([207.164.233.98]) by speed.rcc.on.ca (8.6.12/8.6.9) with SMTP id HAA27353 for <current@FreeBSD.ORG>; Wed, 27 Jan 1999 07:38:54 -0500
Message-ID: <007901be491e$f3c3e220$0a00000a@chopper.my.intranet>
From: "RT" <tr49986@rcc.on.ca>
To: <current@FreeBSD.ORG>
Subject: Re: removing f2c from base distribution
Date: Tue, 26 Jan 1999 06:16:51 -0500
MIME-Version: 1.0
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 4.72.3155.0
X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3155.0
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
I highly doubt that I'll ever use FORTRAN directly or indirectly. If it's
not used by a vast majority, it should be optional...
-----Original Message-----
From: Mike Smith <mike@smith.net.au>
To: Mark Murray <mark@grondar.za>
Cc: obrien@NUXI.com <obrien@NUXI.com>; Steve Kargl
<sgk@troutmask.apl.washington.edu>; freebsd-current@FreeBSD.ORG
<freebsd-current@FreeBSD.ORG>
Date: Wednesday, January 27, 1999 2:40 AM
Subject: Re: removing f2c from base distribution
>> "David O'Brien" wrote:
>> > I've got a Bmaked contribified version of EGCS, but didn't do g77. So
>> > maybe a consensus should be made what to do about FORTRAN in the base
>> > system.
>>
>> If you are collecting votes, please add mine; I feel quite strongly
>> (knowing the scientists that I do that use Fortran) that it _should_
>> be in the base system. Please include it.
>
>We've already established that it doesn't need to be in the base system.
>Your scientist friends are probably already going to be installing
>their favorite text editors; it's no harder to install the Fortran
>support.
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Wed Jan 27 03:44:03 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id DAA02484
for freebsd-current-outgoing; Wed, 27 Jan 1999 03:43:21 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.26.10.9])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA02479
for <freebsd-current@FreeBSD.ORG>; Wed, 27 Jan 1999 03:43:18 -0800 (PST)
(envelope-from bde@godzilla.zeta.org.au)
Received: (from bde@localhost)
by godzilla.zeta.org.au (8.8.7/8.8.7) id WAA14759;
Wed, 27 Jan 1999 22:41:46 +1100
Date: Wed, 27 Jan 1999 22:41:46 +1100
From: Bruce Evans <bde@zeta.org.au>
Message-Id: <199901271141.WAA14759@godzilla.zeta.org.au>
To: axl@iafrica.com, mike@smith.net.au
Subject: Re: NIS with HPUX 10.20
Cc: bonnetf@bart.esiee.fr, dhw@whistle.com, freebsd-current@FreeBSD.ORG,
meyerd1@fang.cs.sunyit.edu
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
>> Read the install(1) manpage, particularly the -C option.
>
>The question, though, is _why_ the need to use -C when installing
>ld-elf.so.1? It's not flagged schg, from the looks of my box.
So that ld-elf.so.1 can be installed safely on an active system.
Plain install is braindamaged (doesn't give an atomic install) and we
(ab)use `install -C' to get an atomic install. This has nothing to do
with schg flagging except schg flagging prevents completely atomic
installs.
The missing schg is a bug if the schg for ld.so is not a bug.
Bruce
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Wed Jan 27 03:51:45 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id DAA03148
for freebsd-current-outgoing; Wed, 27 Jan 1999 03:51:45 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from labinfo.iet.unipi.it (labinfo.iet.unipi.it [131.114.9.5])
by hub.freebsd.org (8.8.8/8.8.8) with SMTP id DAA03142
for <freebsd-current@FreeBSD.ORG>; Wed, 27 Jan 1999 03:51:32 -0800 (PST)
(envelope-from luigi@labinfo.iet.unipi.it)
Received: from localhost (luigi@localhost) by labinfo.iet.unipi.it (8.6.5/8.6.5) id JAA04163; Wed, 27 Jan 1999 09:57:17 +0100
From: Luigi Rizzo <luigi@labinfo.iet.unipi.it>
Message-Id: <199901270857.JAA04163@labinfo.iet.unipi.it>
Subject: Re: pcm0: timeout flushing dbuf_out, chan 0 cnt 0xfffa41ec flags 0x00000241
To: brian@worldcontrol.com
Date: Wed, 27 Jan 1999 09:57:17 +0100 (MET)
Cc: freebsd-current@FreeBSD.ORG
In-Reply-To: <19990127025445.A336@top.worldcontrol.com> from "brian@worldcontrol.com" at Jan 27, 99 02:54:26 am
X-Mailer: ELM [version 2.4 PL23]
Content-Type: text
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
> pcm no longer works correctly the Yamaha YMF715 based sound system
> of my laptop.
> It was working fine up till shortly before secure/libcrypt broke on -current.
i haven't done anything recently on the pcm driver.
Also, it seems that you have changed hardware. can you check if the old
kernel still works fine with the new hardeare ?
> I did change to a AMD K6-2 333MHz processor during that time.
> Used to be a Intel P5-233MMX.
cheers
luigi
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Wed Jan 27 04:03:25 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id EAA05606
for freebsd-current-outgoing; Wed, 27 Jan 1999 04:03:25 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from janus.syracuse.net (janus.syracuse.net [205.232.47.15])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA05576
for <current@freebsd.org>; Wed, 27 Jan 1999 04:03:23 -0800 (PST)
(envelope-from green@unixhelp.org)
Received: from localhost (green@localhost)
by janus.syracuse.net (8.8.8/8.8.7) with ESMTP id HAA23457
for <current@freebsd.org>; Wed, 27 Jan 1999 07:03:22 -0500 (EST)
Date: Wed, 27 Jan 1999 07:03:22 -0500 (EST)
From: Brian Feldman <green@unixhelp.org>
X-Sender: green@janus.syracuse.net
To: current@FreeBSD.ORG
Subject: One answer, one question.
Message-ID: <Pine.BSF.4.05.9901270701510.23381-100000@janus.syracuse.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
And the culprit for the Netscape problems is (drumroll please)
-DVM_STACK!
Now can someone help me out here, and figure out why:
{"/home/green"}$ ps
ps: bad namelist
{"/home/green"}$ sysctl kern.bootfile
kern.bootfile: /kernel
{"/home/green"}$ l /var/db/kvm_kernel.db
-rw-r--r-- 1 root wheel 1310720 Jan 27 00:53 /var/db/kvm_kernel.db
Brian Feldman _ __ ___ ___ ___
green@unixhelp.org _ __ ___ | _ ) __| \
http://www.freebsd.org/ _ __ ___ ____ | _ \__ \ |) |
FreeBSD: The Power to Serve! _ __ ___ ____ _____ |___/___/___/
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Wed Jan 27 04:13:56 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id EAA07394
for freebsd-current-outgoing; Wed, 27 Jan 1999 04:13:56 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from axl.noc.iafrica.com (axl.noc.iafrica.com [196.31.1.175])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA07385
for <freebsd-current@freebsd.org>; Wed, 27 Jan 1999 04:13:52 -0800 (PST)
(envelope-from sheldonh@axl.noc.iafrica.com)
Received: from sheldonh (helo=axl.noc.iafrica.com)
by axl.noc.iafrica.com with local-esmtp (Exim 2.10 #1)
id 105TpK-000KLW-00; Wed, 27 Jan 1999 14:12:10 +0200
From: Sheldon Hearn <axl@iafrica.com>
To: Bruce Evans <bde@zeta.org.au>
cc: mike@smith.net.au, bonnetf@bart.esiee.fr, dhw@whistle.com,
freebsd-current@FreeBSD.ORG, meyerd1@fang.cs.sunyit.edu
Subject: Re: NIS with HPUX 10.20
In-reply-to: Your message of "Wed, 27 Jan 1999 22:41:46 +1100."
<199901271141.WAA14759@godzilla.zeta.org.au>
Date: Wed, 27 Jan 1999 14:12:10 +0200
Message-ID: <78213.917439130@axl.noc.iafrica.com>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
On Wed, 27 Jan 1999 22:41:46 +1100, Bruce Evans wrote:
> So that ld-elf.so.1 can be installed safely on an active system.
I assume I should take your "installed safely" to mean "not installed"?
Are there a lot of files that aren't installed for similar reasons
during an installworld? If there are, I'd be interested in hearing about
them so that I can update them manually.
Ciao,
Sheldon.
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Wed Jan 27 04:26:31 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id EAA08839
for freebsd-current-outgoing; Wed, 27 Jan 1999 04:26:31 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from peach.ocn.ne.jp (peach.ocn.ne.jp [210.145.254.87])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA08830
for <freebsd-current@FreeBSD.ORG>; Wed, 27 Jan 1999 04:26:28 -0800 (PST)
(envelope-from dcs@newsguy.com)
Received: from newsguy.com by peach.ocn.ne.jp (8.9.1a/OCN) id VAA12551; Wed, 27 Jan 1999 21:26:16 +0900 (JST)
Message-ID: <36AF012C.65B439E8@newsguy.com>
Date: Wed, 27 Jan 1999 21:06:04 +0900
From: "Daniel C. Sobral" <dcs@newsguy.com>
X-Mailer: Mozilla 4.5 [en] (Win98; I)
X-Accept-Language: pt-BR,ja
MIME-Version: 1.0
To: "Jordan K. Hubbard" <jkh@zippy.cdrom.com>
CC: The Hermit Hacker <scrappy@hub.org>, freebsd-current@FreeBSD.ORG
Subject: Re: Hate to ask, but...aout -> elf ...
References: <76756.917402980@zippy.cdrom.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
"Jordan K. Hubbard" wrote:
>
> > Is it a simple matter of 'make aout-to-elf', or...?
>
> As of today, just type "make upgrade NOCONFIRM=YES" and wait for the
> server to reboot some n hours later (where n is governed by the speed
> of your machine :).
THERE is a brave man, if I ever saw one!
(well, there is that *other* definition of bravery, which I'll left
unstated... :)
--
Daniel C. Sobral (8-DCS)
dcs@newsguy.com
If you sell your soul to the Devil and all you get is an MCSE from
it, you haven't gotten market rate.
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Wed Jan 27 04:26:43 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id EAA08899
for freebsd-current-outgoing; Wed, 27 Jan 1999 04:26:43 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from peach.ocn.ne.jp (peach.ocn.ne.jp [210.145.254.87])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA08894
for <freebsd-current@FreeBSD.ORG>; Wed, 27 Jan 1999 04:26:41 -0800 (PST)
(envelope-from dcs@newsguy.com)
Received: from newsguy.com by peach.ocn.ne.jp (8.9.1a/OCN) id VAA12486; Wed, 27 Jan 1999 21:25:56 +0900 (JST)
Message-ID: <36AEFC21.A9B32C67@newsguy.com>
Date: Wed, 27 Jan 1999 20:44:33 +0900
From: "Daniel C. Sobral" <dcs@newsguy.com>
X-Mailer: Mozilla 4.5 [en] (Win98; I)
X-Accept-Language: pt-BR,ja
MIME-Version: 1.0
To: Mark Murray <mark@grondar.za>
CC: obrien@NUXI.com, Steve Kargl <sgk@troutmask.apl.washington.edu>,
freebsd-current@FreeBSD.ORG
Subject: Re: removing f2c from base distribution
References: <199901270504.WAA18271@mt.sri.com> <199901270555.VAA09197@troutmask.apl.washington.edu> <19990126220644.A7037@relay.nuxi.com> <199901270623.IAA01480@greenpeace.grondar.za>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
Mark Murray wrote:
>
> "David O'Brien" wrote:
> > I've got a Bmaked contribified version of EGCS, but didn't do g77. So
> > maybe a consensus should be made what to do about FORTRAN in the base
> > system.
>
> If you are collecting votes, please add mine; I feel quite strongly
> (knowing the scientists that I do that use Fortran) that it _should_
> be in the base system. Please include it.
A lot of people use a lot of things out of ports. Why should Fortran
be different?
--
Daniel C. Sobral (8-DCS)
dcs@newsguy.com
If you sell your soul to the Devil and all you get is an MCSE from
it, you haven't gotten market rate.
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Wed Jan 27 04:58:03 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id EAA11783
for freebsd-current-outgoing; Wed, 27 Jan 1999 04:58:03 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.26.10.9])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA11735
for <freebsd-current@FreeBSD.ORG>; Wed, 27 Jan 1999 04:57:58 -0800 (PST)
(envelope-from bde@godzilla.zeta.org.au)
Received: (from bde@localhost)
by godzilla.zeta.org.au (8.8.7/8.8.7) id XAA21036;
Wed, 27 Jan 1999 23:56:51 +1100
Date: Wed, 27 Jan 1999 23:56:51 +1100
From: Bruce Evans <bde@zeta.org.au>
Message-Id: <199901271256.XAA21036@godzilla.zeta.org.au>
To: axl@iafrica.com, bde@zeta.org.au
Subject: Re: NIS with HPUX 10.20
Cc: bonnetf@bart.esiee.fr, dhw@whistle.com, freebsd-current@FreeBSD.ORG,
meyerd1@fang.cs.sunyit.edu, mike@smith.net.au
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
>> So that ld-elf.so.1 can be installed safely on an active system.
>
>I assume I should take your "installed safely" to mean "not installed"?
I meant what I said.
>Are there a lot of files that aren't installed for similar reasons
>during an installworld? If there are, I'd be interested in hearing about
>them so that I can update them manually.
No. installworld more or less assumes single user. install(1) without
-C is always unsafe on active systems, even for files that don't change,
because the targets go away temporaily. `install -C' is completely
safe for files that don't change and fairly safe otherwise. The latter
depends on the magic of unlinked open (or mmapped) files and enough disk
and RAM for the active unlinked copies. Perhaps it's not completely
safe for ld-elf.so.1. It is safe if all accesses are by file descriptor
except for an initial open.
Bruce
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Wed Jan 27 05:06:07 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id FAA12990
for freebsd-current-outgoing; Wed, 27 Jan 1999 05:06:07 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from vader.cs.berkeley.edu (vader.CS.Berkeley.EDU [128.32.38.234])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA12983
for <freebsd-current@FreeBSD.ORG>; Wed, 27 Jan 1999 05:06:06 -0800 (PST)
(envelope-from asami@vader.cs.berkeley.edu)
Received: from silvia.hip.berkeley.edu (sji-ca13-237.ix.netcom.com [209.109.238.237]) by vader.cs.berkeley.edu (8.8.7/8.7.3) with ESMTP id FAA01750; Wed, 27 Jan 1999 05:04:08 -0800 (PST)
Received: (from asami@localhost) by silvia.hip.berkeley.edu (8.9.1/8.6.9) id FAA65753; Wed, 27 Jan 1999 05:03:58 -0800 (PST)
Date: Wed, 27 Jan 1999 05:03:58 -0800 (PST)
Message-Id: <199901271303.FAA65753@silvia.hip.berkeley.edu>
To: sgk@troutmask.apl.washington.edu
CC: mike@smith.net.au, mark@grondar.za, obrien@NUXI.com,
freebsd-current@FreeBSD.ORG
In-reply-to: <199901270644.WAA09457@troutmask.apl.washington.edu> (message
from Steve Kargl on Tue, 26 Jan 1999 22:44:11 -0800 (PST))
Subject: Re: removing f2c from base distribution
From: asami@FreeBSD.ORG (Satoshi Asami)
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
* From: Steve Kargl <sgk@troutmask.apl.washington.edu>
* g77 is a frontend to the FSF compiler backend, and thus it is bound
* to specific versions. So, it could become a support nightmare to ensure
* a g77 port is in sync with the egcs backend in the base distribution.
I don't think it would be that much of a support nightmare. Compilers
in the base system don't change that often. If the port maintainer
takes care to synchronize it with the system compiler, we should be
fine.
* It might even be impractical to try to build a standalone g77 port.
That I don't know. I believe the compiler driver (gcc) can be
instructed to call frontends in places other than /usr/libexec though.
Maybe it would be feasible if we leave in hooks for that. (That is,
if people want to compile fortran programs with /usr/bin/gcc.)
Satoshi
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Wed Jan 27 05:12:35 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id FAA13378
for freebsd-current-outgoing; Wed, 27 Jan 1999 05:12:35 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.26.10.9])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA13373
for <current@FreeBSD.ORG>; Wed, 27 Jan 1999 05:12:33 -0800 (PST)
(envelope-from bde@godzilla.zeta.org.au)
Received: (from bde@localhost)
by godzilla.zeta.org.au (8.8.7/8.8.7) id AAA22283;
Thu, 28 Jan 1999 00:12:30 +1100
Date: Thu, 28 Jan 1999 00:12:30 +1100
From: Bruce Evans <bde@zeta.org.au>
Message-Id: <199901271312.AAA22283@godzilla.zeta.org.au>
To: bde@zeta.org.au, current@FreeBSD.ORG, dawes@rf900.physics.usyd.edu.au
Subject: Re: Promise FastTrack PCI IDE controller
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
>>Errors in wdreset() for the Promise (at least for the Ultra/33)
>>probably mean that du->dk_altport is not initialized properly. (Setting
>>...
>
>There is a problem with the way du->dk_altport is set in wdattach. It
>is set correctly in wdprobe, but incorrectly in wdattach. The following
>patch fixes that. However, this isn't sufficient to get the card working
>with the RAID BIOS is installed. The wdreset() problem is, however,
>more noticable in that case because it then it gets called after the
>attach.
I knew about the wdattach() bug, but thought that it was unimportant
because wdreset() doesn't get called except for error handling. Of
course, errors are likely when the interface is screwed up.
The driver has some support for falling back to PIO mode after certain
errors. I've never seen that work. Timeouts are very generious so I
would expect it to take several minutes at best. It only does it for
aborted commands, and there is no provision for getting back to DMA mode
if the error wasn't for DMA.
Bruce
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Wed Jan 27 05:14:40 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id FAA13680
for freebsd-current-outgoing; Wed, 27 Jan 1999 05:14:40 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from vader.cs.berkeley.edu (vader.CS.Berkeley.EDU [128.32.38.234])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA13675
for <current@FreeBSD.ORG>; Wed, 27 Jan 1999 05:14:39 -0800 (PST)
(envelope-from asami@vader.cs.berkeley.edu)
Received: from silvia.hip.berkeley.edu (sji-ca13-237.ix.netcom.com [209.109.238.237]) by vader.cs.berkeley.edu (8.8.7/8.7.3) with ESMTP id FAA01760; Wed, 27 Jan 1999 05:14:37 -0800 (PST)
Received: (from asami@localhost) by silvia.hip.berkeley.edu (8.9.1/8.6.9) id FAA65788; Wed, 27 Jan 1999 05:14:33 -0800 (PST)
Date: Wed, 27 Jan 1999 05:14:33 -0800 (PST)
Message-Id: <199901271314.FAA65788@silvia.hip.berkeley.edu>
To: gljohns@bellsouth.net
CC: current@FreeBSD.ORG, sgk@troutmask.apl.washington.edu, obrien@NUXI.com
In-reply-to: <19990127005850.A10486@gforce.johnson.home> (message from Glenn
Johnson on Wed, 27 Jan 1999 00:58:50 -0600)
Subject: Re: removing f2c from base distribution
From: asami@FreeBSD.ORG (Satoshi Asami)
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
* The biggest problem has been that the port of g77 has not worked
* properly for quite some time and in fact is currently marked as
* broken. I would anticipate that this situation would not change much in
That (and bug fix issues, as DavidO contends) all depends on the
commitment of the maintainer (which there is none for the g77 port).
Unless someone who uses g77 regularly steps up to maintain it, it will
remain broken. This is the same for all ports, and I don't see why a
fortran compiler should be an exception.
Granted, if won't be blatantly broken if it's in the base
distribution, but that's only because people will yell and scream if
their "make world" doesn't work. If the amount of noise that
generates is significantly different from what happens if it's a
broken port, that's actually a pretty good argument *against* putting
it in the base distribution, as it means we can keep g77 running only
by annoying people who don't use it when it's broken. (1/2 :)
This port has been marked broken since July last year. Sorry, but I
just don't have a whole lot of sympathy for something that can stay
broken that long without anyone fixing it. ;)
Satoshi
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Wed Jan 27 05:18:42 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id FAA13982
for freebsd-current-outgoing; Wed, 27 Jan 1999 05:18:42 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from axl.noc.iafrica.com (axl.noc.iafrica.com [196.31.1.175])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA13972
for <freebsd-current@freebsd.org>; Wed, 27 Jan 1999 05:18:37 -0800 (PST)
(envelope-from sheldonh@axl.noc.iafrica.com)
Received: from sheldonh (helo=axl.noc.iafrica.com)
by axl.noc.iafrica.com with local-esmtp (Exim 2.11 #1)
id 105Uq3-000NT1-00; Wed, 27 Jan 1999 15:16:59 +0200
From: Sheldon Hearn <axl@iafrica.com>
To: Bruce Evans <bde@zeta.org.au>
cc: bonnetf@bart.esiee.fr, dhw@whistle.com, freebsd-current@FreeBSD.ORG,
meyerd1@fang.cs.sunyit.edu, mike@smith.net.au
Subject: Re: NIS with HPUX 10.20
In-reply-to: Your message of "Wed, 27 Jan 1999 23:56:51 +1100."
<199901271256.XAA21036@godzilla.zeta.org.au>
Date: Wed, 27 Jan 1999 15:16:59 +0200
Message-ID: <90210.917443019@axl.noc.iafrica.com>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
On Wed, 27 Jan 1999 23:56:51 +1100, Bruce Evans wrote:
> No. installworld more or less assumes single user.
This is really what I'm getting at. :-)
If installworld assumes single-user mode, why do we install -C
ld-elf.so.1 ? The first time I asked this question, I didn't mention
single-user mode and your answer was that it's to protect "live
systems". What's so live about a single-user system that we can't assume
nothing else needs ld-elf.so.1 while we're smacking it?
Ciao,
Sheldon.
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Wed Jan 27 05:58:45 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id FAA17722
for freebsd-current-outgoing; Wed, 27 Jan 1999 05:58:45 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from nlsystems.com (nlsys.demon.co.uk [158.152.125.33])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA17709
for <current@FreeBSD.ORG>; Wed, 27 Jan 1999 05:58:42 -0800 (PST)
(envelope-from dfr@nlsystems.com)
Received: from localhost (dfr@localhost)
by nlsystems.com (8.9.1/8.8.5) with SMTP id NAA96373;
Wed, 27 Jan 1999 13:56:01 GMT
Date: Wed, 27 Jan 1999 13:56:01 +0000 (GMT)
From: Doug Rabson <dfr@nlsystems.com>
To: paul@originative.co.uk
cc: phk@critter.freebsd.dk, archie@whistle.com, sobomax@altavista.net,
current@FreeBSD.ORG, julian@whistle.com
Subject: RE: DEVFS, the time has come...
In-Reply-To: <A6D02246E1ABD2119F5200C0F0303D10FDDB@OCTOPUS>
Message-ID: <Pine.BSF.4.01.9901271341260.95594-100000@herring.nlsystems.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
On Tue, 26 Jan 1999 paul@originative.co.uk wrote:
> > -----Original Message-----
> > From: Poul-Henning Kamp [mailto:phk@critter.freebsd.dk]
> > Sent: Tuesday, January 26, 1999 10:41 AM
> > To: Doug Rabson
> > Cc: Archie Cobbs; Maxim Sobolev; current@FreeBSD.ORG; Julian Elischer
> > Subject: Re: DEVFS, the time has come...
> >
> >
> >
> > >> No, it doesn't have to be SLICE. In particular, if we're going the
> > >> SLICE way, it should be done >right<, and Julians SLICE
> > code didn't
> > >> do that. (I know, I spent close to 6 months prototyping the concept
> > >> and julian had my code to work from).
> > >
> > >Wouldn't it be possible to fit this into the device system?
> > If we treat
> > >disks as devices and partition types as drivers, most of the
> > boring work
> > >of matching drivers to devices and keeping lists and trees
> > of objects will
> > >happen automatically.
> >
> > Well, as long as you remember that it is not a strict hierarchy:
> > I could slice two disks, mirror the slices and concatenate the
> > mirrors if I wanted to.
>
> Where does this happen though?
>
> If we go with Doug's idea (which seems quite neat), then the device
> subsystem will present devices for each of the slices/partitions that
> the low level disk handling code finds during the probe phase.
>
> The mirroring of slices and subsequent concatenation of the mirrors, or
> any other combination of slice munging that might take place happens
> later doesn't it, using something like vinum. If so then can't vinum
> become responsible for modifying the device view, i.e. if it creates a
> concatenated partition then it could remove the two "low level" slice
> devices and create a new disk device that represents the concatenated
> area. You might not want to remove the low level devices or it could be
> a vinum configuration option.
>
> If something like vinum doesn't exist then you're not going to be doing
> any mirroring or concatenation and Doug's solution would be fine for
> creating the device nodes needed to represent the "actual" layout of the
> disks, as opposed to a "view" of the disks that might be created by
> vinum et al.
Poul is correct that this stuff is fairly easy. I did a sketch
implementation of a simple disk interface with drivers for mbr and bsd
labels and it seems to be the right direction to take. There are issues I
didn't bother to tackle (device naming, geometry) but since Julian's slice
code had this functionality and it is well understood, I don't think there
would be problems.
As far as ccd and vinum go, I thought that ccd would pick up disk
partitions from the leaves of the slice tree and do its thing to create a
virtual disk. This virtual disk would then be fed back into the disk
probing system to spawn another partition tree. Vinum could do something
similar but I think it has its own advanced ideas on partitioning.
The system could be easily extended to probing the filesystem type. It
would be really nice to automount partitions from removable media as it is
inserted. I think the requirement that a user must use (root privileged)
commands just to get to the files on a floppy/zip is ridiculous for
someone used to Win32 systems. Perhaps the nebulous devd could be coerced
into managing removable media as well (with configuration options for
mounting, e.g. nosuid).
And another thing. Why can't we use a non-driver-specific name for the
disk? Most users simply don't care whether the driver was fd, wfd, wd or
anything. They just want to get to their files without any fuss.
--
Doug Rabson Mail: dfr@nlsystems.com
Nonlinear Systems Ltd. Phone: +44 181 442 9037
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Wed Jan 27 06:01:46 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id GAA18085
for freebsd-current-outgoing; Wed, 27 Jan 1999 06:01:46 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from fledge.watson.org (FLEDGE.RES.CMU.EDU [128.2.93.229])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA18080
for <current@FreeBSD.ORG>; Wed, 27 Jan 1999 06:01:44 -0800 (PST)
(envelope-from robert@cyrus.watson.org)
Received: from fledge.watson.org (robert@fledge.pr.watson.org [192.0.2.3])
by fledge.watson.org (8.8.8/8.8.8) with SMTP id JAA04693;
Wed, 27 Jan 1999 09:01:41 -0500 (EST)
Date: Wed, 27 Jan 1999 09:01:41 -0500 (EST)
From: Robert Watson <robert@cyrus.watson.org>
X-Sender: robert@fledge.watson.org
Reply-To: Robert Watson <robert+freebsd@cyrus.watson.org>
To: RT <tr49986@rcc.on.ca>
cc: current@FreeBSD.ORG
Subject: Re: removing f2c from base distribution
In-Reply-To: <007901be491e$f3c3e220$0a00000a@chopper.my.intranet>
Message-ID: <Pine.BSF.3.96.990127085709.4361A-100000@fledge.watson.org>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
On Tue, 26 Jan 1999, RT wrote:
> I highly doubt that I'll ever use FORTRAN directly or indirectly. If it's
> not used by a vast majority, it should be optional...
So the problem seems to be that 'included in the system' is a problem
because the system gets unwieldy in terms of junk a lot of people don't
use, but 'included as a port' or 'included as a package' means it might be
too detached from the system. There's quite a list of things on this
list, including UUCP which the majority do not use. There's also that
list of things which almost everyone use except some people who find it
inconvenient that it's included, such as sendmail. What might be really
nice is to see all user-land files broken out into whatever the new
package format will be, in the style of RedHat packages for the base
system. At install, needless to say, you have a default install that
looks just like today's (it installs the packages that map directly to the
current system), but you also have other installs, and the option to flag
things in and out of the install, in the style of existing packages, with
dependencies, etc.
One sad side-effect of this would, of course, be managing the dependencies
(both in source and in binary form)and the screwing up of the existing
build tree if the build tree was to be restructured to match the packages.
But the RedHat arrangement does have appeal: I understand that even / is
part of a package :). And I certainly don't have time (and probably not
the understanding) to figure out how to make all this work. :)
Robert N Watson
robert@fledge.watson.org http://www.watson.org/~robert/
PGP key fingerprint: 03 01 DD 8E 15 67 48 73 25 6D 10 FC EC 68 C1 1C
Carnegie Mellon University http://www.cmu.edu/
TIS Labs at Network Associates, Inc. http://www.tis.com/
SafePort Network Services http://www.safeport.com/
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Wed Jan 27 06:07:30 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id GAA18701
for freebsd-current-outgoing; Wed, 27 Jan 1999 06:07:30 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from uni-sb.de (uni-sb.de [134.96.252.33])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA18683
for <current@freebsd.org>; Wed, 27 Jan 1999 06:07:26 -0800 (PST)
(envelope-from rock@cs.uni-sb.de)
Received: from cs.uni-sb.de (cs.uni-sb.de [134.96.252.31])
by uni-sb.de (8.9.2/1999010400) with ESMTP id PAA13077
for <current@freebsd.org>; Wed, 27 Jan 1999 15:07:03 +0100 (CET)
Received: from cs.uni-sb.de (maxtnt-047.rz.uni-sb.de [134.96.70.174])
by cs.uni-sb.de (8.9.2/1999010400) with ESMTP id PAA11041
for <current@freebsd.org>; Wed, 27 Jan 1999 15:07:03 +0100 (CET)
Message-ID: <36AF1D9A.A5A6BEC1@cs.uni-sb.de>
Date: Wed, 27 Jan 1999 15:07:22 +0100
From: "D. Rock" <rock@cs.uni-sb.de>
X-Mailer: Mozilla 4.5 [de] (WinNT; U)
X-Accept-Language: de
MIME-Version: 1.0
To: current@FreeBSD.ORG
Subject: No CD-ROM support in boot.flp?
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
>jkh 1999/01/26 07:14:11 PST
>
> Modified files:
> release/scripts doFS.sh dokern.sh
> Log:
> 1. Adjust fs sizes to get floppies back under control.
>
> 2. Viciously slash all CD support out of boot.flp. It's basically just
> a net boot floppy now.
>
> Revision Changes Path
> 1.22 +1 -1 src/release/scripts/doFS.sh
> 1.10 +13 -4 src/release/scripts/dokern.sh
Does this mean, it is now pointless to use boot.flp as a boot image
for CD-ROMs: I can boot from the CD, but not install...
Are there any plans to create another boot disk (cdrom.flp?), 2.88MB
in size especially for CD-ROM boots?
Daniel
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Wed Jan 27 06:25:55 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id GAA20231
for freebsd-current-outgoing; Wed, 27 Jan 1999 06:25:55 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA20225
for <current@FreeBSD.ORG>; Wed, 27 Jan 1999 06:25:53 -0800 (PST)
(envelope-from jkh@zippy.cdrom.com)
Received: from zippy.cdrom.com (localhost.cdrom.com [127.0.0.1])
by zippy.cdrom.com (8.9.2/8.9.1) with ESMTP id GAA79653;
Wed, 27 Jan 1999 06:26:16 -0800 (PST)
To: "D. Rock" <rock@cs.uni-sb.de>
cc: current@FreeBSD.ORG
Subject: Re: No CD-ROM support in boot.flp?
In-reply-to: Your message of "Wed, 27 Jan 1999 15:07:22 +0100."
<36AF1D9A.A5A6BEC1@cs.uni-sb.de>
Date: Wed, 27 Jan 1999 06:26:16 -0800
Message-ID: <79650.917447176@zippy.cdrom.com>
From: "Jordan K. Hubbard" <jkh@zippy.cdrom.com>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
> Are there any plans to create another boot disk (cdrom.flp?), 2.88MB
> in size especially for CD-ROM boots?
Yes.
- Jordan
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Wed Jan 27 06:33:19 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id GAA21242
for freebsd-current-outgoing; Wed, 27 Jan 1999 06:33:19 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from lamb.sas.com (lamb.sas.com [192.35.83.8])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA21235
for <freebsd-current@freebsd.org>; Wed, 27 Jan 1999 06:33:17 -0800 (PST)
(envelope-from jwd@unx.sas.com)
Received: from mozart (mozart.unx.sas.com [192.58.184.8])
by lamb.sas.com (8.9.1/8.9.1) with SMTP id JAA09944
for <freebsd-current@freebsd.org>; Wed, 27 Jan 1999 09:33:15 -0500 (EST)
Received: from bb01f39.unx.sas.com by mozart (5.65c/SAS/Domains/5-6-90)
id AA19115; Wed, 27 Jan 1999 09:33:14 -0500
Received: (from jwd@localhost)
by bb01f39.unx.sas.com (8.9.1/8.9.1) id JAA75703
for freebsd-current@freebsd.org; Wed, 27 Jan 1999 09:33:14 -0500 (EST)
(envelope-from jwd)
From: "John W. DeBoskey" <jwd@unx.sas.com>
Message-Id: <199901271433.JAA75703@bb01f39.unx.sas.com>
Subject: make release - Party Time!
To: freebsd-current@FreeBSD.ORG
Date: Wed, 27 Jan 1999 09:33:14 -0500 (EST)
X-Mailer: ELM [version 2.4ME+ PL43 (25)]
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
Hi,
A note of thanks to Jordan and everyone else who's been working
on the new 4.0 code... We have our first complete processing of
cd /usr/src && make world && cd release && make release.
---> Wed Jan 27 02:20:13 EST 1999 - Nightly build for 4.0-19990127-SNAP
---> Wed Jan 27 07:40:27 EST 1999 - Creating /pub/FreeBSD/4.0-19990127-SNAP
---> Wed Jan 27 07:52:36 EST 1999 - build of 4.0-19990127-SNAP was a success.
Good work folks!
-John
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Wed Jan 27 06:57:29 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id GAA23730
for freebsd-current-outgoing; Wed, 27 Jan 1999 06:57:29 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from smtp02.wxs.nl (smtp02.wxs.nl [195.121.6.60])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA23722
for <current@FreeBSD.ORG>; Wed, 27 Jan 1999 06:57:27 -0800 (PST)
(envelope-from asmodai@wxs.nl)
Received: from daemon.ninth-circle.org ([195.121.56.55]) by smtp02.wxs.nl
(Netscape Messaging Server 3.6) with ESMTP id AAA671C;
Wed, 27 Jan 1999 15:57:25 +0100
Message-ID: <XFMail.990127160554.asmodai@wxs.nl>
X-Mailer: XFMail 1.3 [p0] on FreeBSD
X-Priority: 3 (Normal)
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 8bit
MIME-Version: 1.0
In-Reply-To: <Pine.BSF.4.05.9901270701510.23381-100000@janus.syracuse.net>
Date: Wed, 27 Jan 1999 16:05:54 +0100 (CET)
Organization: Ninth Circle Enterprises
From: Jeroen Ruigrok/Asmodai <asmodai@wxs.nl>
To: Brian Feldman <green@unixhelp.org>
Subject: RE: One answer, one question.
Cc: current@FreeBSD.ORG
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
On 27-Jan-99 Brian Feldman wrote:
> And the culprit for the Netscape problems is (drumroll please)
> -DVM_STACK!
> Now can someone help me out here, and figure out why:
> {"/home/green"}$ ps
> ps: bad namelist
> {"/home/green"}$ sysctl kern.bootfile
> kern.bootfile: /kernel
> {"/home/green"}$ l /var/db/kvm_kernel.db
> -rw-r--r-- 1 root wheel 1310720 Jan 27 00:53 /var/db/kvm_kernel.db
Ye sure about it?
I cannot remember that -DVM_STACK was used on 3.0 CURRENT when the problems
were starting already.
Also, I am also not seeing the relevance of ps. Sure, Matthew commited a
bunch of VM hacks 'n fixes which appear to work nicely here (mayhaps even
better than the prior stuff) and ps works properly. Ye sure yet not just
forgetting to rebuild ps and the likes after the recent changes?
---
Jeroen Ruigrok van der Werven It's a Dance of Energy,
asmodai(at)wxs.nl when the Mind goes Binary...
Network/Security Specialist <http://home.wxs.nl/~asmodai>
BSD & picoBSD: The Power to Serve <http://www.freebsd.org>
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Wed Jan 27 07:08:48 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id HAA25163
for freebsd-current-outgoing; Wed, 27 Jan 1999 07:08:48 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from janus.syracuse.net (janus.syracuse.net [205.232.47.15])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA25156
for <current@FreeBSD.ORG>; Wed, 27 Jan 1999 07:08:47 -0800 (PST)
(envelope-from green@unixhelp.org)
Received: from localhost (green@localhost)
by janus.syracuse.net (8.8.8/8.8.7) with ESMTP id KAA01391;
Wed, 27 Jan 1999 10:08:34 -0500 (EST)
Date: Wed, 27 Jan 1999 10:08:34 -0500 (EST)
From: Brian Feldman <green@unixhelp.org>
X-Sender: green@janus.syracuse.net
To: Jeroen Ruigrok/Asmodai <asmodai@wxs.nl>
cc: current@FreeBSD.ORG
Subject: RE: One answer, one question.
In-Reply-To: <XFMail.990127160554.asmodai@wxs.nl>
Message-ID: <Pine.BSF.4.05.9901271007430.1310-100000@janus.syracuse.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
On Wed, 27 Jan 1999, Jeroen Ruigrok/Asmodai wrote:
> On 27-Jan-99 Brian Feldman wrote:
> > And the culprit for the Netscape problems is (drumroll please)
> > -DVM_STACK!
> > Now can someone help me out here, and figure out why:
> > {"/home/green"}$ ps
> > ps: bad namelist
> > {"/home/green"}$ sysctl kern.bootfile
> > kern.bootfile: /kernel
> > {"/home/green"}$ l /var/db/kvm_kernel.db
> > -rw-r--r-- 1 root wheel 1310720 Jan 27 00:53 /var/db/kvm_kernel.db
>
> Ye sure about it?
>
> I cannot remember that -DVM_STACK was used on 3.0 CURRENT when the problems
> were starting already.
>
> Also, I am also not seeing the relevance of ps. Sure, Matthew commited a
> bunch of VM hacks 'n fixes which appear to work nicely here (mayhaps even
> better than the prior stuff) and ps works properly. Ye sure yet not just
> forgetting to rebuild ps and the likes after the recent changes?
I am certain VM_STACK is breaking Netscape. Ps isn't related, but I am having
problems with it, even after rebuilding everything, kvm_mkdb'ing... :(
>
> ---
> Jeroen Ruigrok van der Werven It's a Dance of Energy,
> asmodai(at)wxs.nl when the Mind goes Binary...
> Network/Security Specialist <http://home.wxs.nl/~asmodai>
> BSD & picoBSD: The Power to Serve <http://www.freebsd.org>
>
> To Unsubscribe: send mail to majordomo@FreeBSD.org
> with "unsubscribe freebsd-current" in the body of the message
>
Brian Feldman _ __ ___ ___ ___
green@unixhelp.org _ __ ___ | _ ) __| \
http://www.freebsd.org/ _ __ ___ ____ | _ \__ \ |) |
FreeBSD: The Power to Serve! _ __ ___ ____ _____ |___/___/___/
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Wed Jan 27 07:11:29 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id HAA25458
for freebsd-current-outgoing; Wed, 27 Jan 1999 07:11:29 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from smtp04.wxs.nl (smtp04.wxs.nl [195.121.6.59])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA25433
for <current@FreeBSD.ORG>; Wed, 27 Jan 1999 07:11:26 -0800 (PST)
(envelope-from asmodai@wxs.nl)
Received: from daemon.ninth-circle.org ([195.121.56.137]) by smtp04.wxs.nl
(Netscape Messaging Server 3.6) with ESMTP id AAA494F
for <current@FreeBSD.ORG>; Wed, 27 Jan 1999 16:11:24 +0100
Message-ID: <XFMail.990127161953.asmodai@wxs.nl>
X-Mailer: XFMail 1.3 [p0] on FreeBSD
X-Priority: 3 (Normal)
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 8bit
MIME-Version: 1.0
Date: Wed, 27 Jan 1999 16:19:53 +0100 (CET)
Organization: Ninth Circle Enterprises
From: Jeroen Ruigrok/Asmodai <asmodai@wxs.nl>
To: FreeBSD Current <current@FreeBSD.ORG>
Subject: $Id$
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
Ok
dumb question mayhaps...
Why isn't the FreeBSD project using tags like $FreeBSD$ instead of the
now-used $Id$?
I looked in the log files and saw that at one point there was an attempted
switch, but it got reversed again.
---
Jeroen Ruigrok van der Werven It's a Dance of Energy,
asmodai(at)wxs.nl when the Mind goes Binary...
Network/Security Specialist <http://home.wxs.nl/~asmodai>
BSD & picoBSD: The Power to Serve <http://www.freebsd.org>
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Wed Jan 27 07:20:03 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id HAA26399
for freebsd-current-outgoing; Wed, 27 Jan 1999 07:20:03 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from smtp01.wxs.nl (smtp01.wxs.nl [195.121.6.61])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA26325
for <current@FreeBSD.ORG>; Wed, 27 Jan 1999 07:20:00 -0800 (PST)
(envelope-from asmodai@wxs.nl)
Received: from daemon.ninth-circle.org ([195.121.56.137]) by smtp01.wxs.nl
(Netscape Messaging Server 3.61) with ESMTP id AAA4EE7;
Wed, 27 Jan 1999 16:19:57 +0100
Message-ID: <XFMail.990127162827.asmodai@wxs.nl>
X-Mailer: XFMail 1.3 [p0] on FreeBSD
X-Priority: 3 (Normal)
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 8bit
MIME-Version: 1.0
In-Reply-To: <Pine.BSF.4.05.9901271007430.1310-100000@janus.syracuse.net>
Date: Wed, 27 Jan 1999 16:28:27 +0100 (CET)
Organization: Ninth Circle Enterprises
From: Jeroen Ruigrok/Asmodai <asmodai@wxs.nl>
To: Brian Feldman <green@unixhelp.org>
Subject: RE: One answer, one question.
Cc: current@FreeBSD.ORG
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
On 27-Jan-99 Brian Feldman wrote:
> I am certain VM_STACK is breaking Netscape. Ps isn't related, but I am
> having problems with it, even after rebuilding everything, kvm_mkdb'ing...
> :(
OK, I'm going to rebuild NetScape against the latest sources et al, I last
compiled it against a 3.0 CURRENT in December...
Heh, did that while I was typing this mail... It doesn't appear to work any
differently then before (which means it will crash after a while).
In what sense do ye think VM_STACK is related to the Netscape issue? I'd
love to hear what ye think causes it to bomb...
regards,
---
Jeroen Ruigrok van der Werven It's a Dance of Energy,
asmodai(at)wxs.nl when the Mind goes Binary...
Network/Security Specialist <http://home.wxs.nl/~asmodai>
BSD & picoBSD: The Power to Serve <http://www.freebsd.org>
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Wed Jan 27 07:21:06 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id HAA26539
for freebsd-current-outgoing; Wed, 27 Jan 1999 07:21:06 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from janus.syracuse.net (janus.syracuse.net [205.232.47.15])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA26522
for <current@FreeBSD.ORG>; Wed, 27 Jan 1999 07:21:02 -0800 (PST)
(envelope-from green@unixhelp.org)
Received: from localhost (green@localhost)
by janus.syracuse.net (8.8.8/8.8.7) with ESMTP id KAA01991;
Wed, 27 Jan 1999 10:20:14 -0500 (EST)
Date: Wed, 27 Jan 1999 10:20:14 -0500 (EST)
From: Brian Feldman <green@unixhelp.org>
X-Sender: green@janus.syracuse.net
To: Sheldon Hearn <axl@iafrica.com>
cc: Jeroen Ruigrok/Asmodai <asmodai@wxs.nl>,
Andrew Gordon <arg@arg1.demon.co.uk>, current@FreeBSD.ORG,
Matthew Dillon <dillon@apollo.backplane.com>
Subject: Re: 4.0-Current, netscape halts system
In-Reply-To: <74560.917435435@axl.noc.iafrica.com>
Message-ID: <Pine.BSF.4.05.9901271018500.1310-100000@janus.syracuse.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
On Wed, 27 Jan 1999, Sheldon Hearn wrote:
>
>
> On Tue, 26 Jan 1999 07:46:18 +0100, Jeroen Ruigrok/Asmodai wrote:
>
> > Yer kidding right? A program that _needs_ 100 MB or more? Surely yer
> > kidding... I haven't seen a program in normal corporate/home use that
> > justifies the memory usage of 100 MB or more including NetScape's
> > Navigator/Communicator.
>
> You haven't had to provide an ISP-grade news or proxy service yet, have
> you? :-)
>
> Ignoring that comment, since I assume you meant "I haven't seen an
> end-user application in...", it _is_ conceivable that the way Netscape
> keeps track of its cache _does_ mean an inevitable requirement for
> enormous amounts of memory.
>
> I still don't think we're getting any closer to the question "Why is
> Netscape unstable on CURRENT when it worked fine for me on STABLE?" The
> problem seems to be that those who know enough to offer a useful answer
> don't seem to be seeing the instability reported.
>
> So if this thread isn't going to be dropped, the focus should probably
> be shifted to "What information should we request from people who have
> this problem?"
>
> Ciao,
> Sheldon.
If you have Netscape problems, it would be worthwhile to try removing
-DVM_STACK from src/sys/compile/BLAH/Makefile and doing a make clean all
install. I am pretty certain this is the cause of Netscape crashing, at least
on startup...
>
> To Unsubscribe: send mail to majordomo@FreeBSD.org
> with "unsubscribe freebsd-current" in the body of the message
>
Brian Feldman _ __ ___ ___ ___
green@unixhelp.org _ __ ___ | _ ) __| \
http://www.freebsd.org/ _ __ ___ ____ | _ \__ \ |) |
FreeBSD: The Power to Serve! _ __ ___ ____ _____ |___/___/___/
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Wed Jan 27 07:28:08 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id HAA27255
for freebsd-current-outgoing; Wed, 27 Jan 1999 07:28:08 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from janus.syracuse.net (janus.syracuse.net [205.232.47.15])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA27250
for <current@FreeBSD.ORG>; Wed, 27 Jan 1999 07:28:07 -0800 (PST)
(envelope-from green@unixhelp.org)
Received: from localhost (green@localhost)
by janus.syracuse.net (8.8.8/8.8.7) with ESMTP id KAA02389;
Wed, 27 Jan 1999 10:28:03 -0500 (EST)
Date: Wed, 27 Jan 1999 10:28:03 -0500 (EST)
From: Brian Feldman <green@unixhelp.org>
X-Sender: green@janus.syracuse.net
To: Jeroen Ruigrok/Asmodai <asmodai@wxs.nl>
cc: current@FreeBSD.ORG
Subject: RE: One answer, one question.
In-Reply-To: <XFMail.990127162827.asmodai@wxs.nl>
Message-ID: <Pine.BSF.4.05.9901271026040.1310-100000@janus.syracuse.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
On Wed, 27 Jan 1999, Jeroen Ruigrok/Asmodai wrote:
> On 27-Jan-99 Brian Feldman wrote:
> > I am certain VM_STACK is breaking Netscape. Ps isn't related, but I am
> > having problems with it, even after rebuilding everything, kvm_mkdb'ing...
> > :(
>
> OK, I'm going to rebuild NetScape against the latest sources et al, I last
> compiled it against a 3.0 CURRENT in December...
>
> Heh, did that while I was typing this mail... It doesn't appear to work any
> differently then before (which means it will crash after a while).
>
> In what sense do ye think VM_STACK is related to the Netscape issue? I'd
> love to hear what ye think causes it to bomb...
I haven't really messed with it too much, so right now I think it's related
because testing makes it appear to be. i.e. if I have a kernel with VM_STACK
Netscape will sig11 right after loading; without VM_STACK it's as stable as
ever. I'd love to figure out why ps isn't working, though...
>
> regards,
>
> ---
> Jeroen Ruigrok van der Werven It's a Dance of Energy,
> asmodai(at)wxs.nl when the Mind goes Binary...
> Network/Security Specialist <http://home.wxs.nl/~asmodai>
> BSD & picoBSD: The Power to Serve <http://www.freebsd.org>
>
Brian Feldman _ __ ___ ___ ___
green@unixhelp.org _ __ ___ | _ ) __| \
http://www.freebsd.org/ _ __ ___ ____ | _ \__ \ |) |
FreeBSD: The Power to Serve! _ __ ___ ____ _____ |___/___/___/
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Wed Jan 27 07:33:27 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id HAA28144
for freebsd-current-outgoing; Wed, 27 Jan 1999 07:33:27 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from verdi.nethelp.no (verdi.nethelp.no [158.36.41.162])
by hub.freebsd.org (8.8.8/8.8.8) with SMTP id HAA28136
for <current@FreeBSD.ORG>; Wed, 27 Jan 1999 07:33:25 -0800 (PST)
(envelope-from sthaug@nethelp.no)
From: sthaug@nethelp.no
Received: (qmail 20706 invoked by uid 1001); 27 Jan 1999 15:33:23 +0000 (GMT)
To: green@unixhelp.org
Cc: asmodai@wxs.nl, current@FreeBSD.ORG
Subject: RE: One answer, one question.
In-Reply-To: Your message of "Wed, 27 Jan 1999 10:28:03 -0500 (EST)"
References: <Pine.BSF.4.05.9901271026040.1310-100000@janus.syracuse.net>
X-Mailer: Mew version 1.05+ on Emacs 19.34.2
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Date: Wed, 27 Jan 1999 16:33:23 +0100
Message-ID: <20704.917451203@verdi.nethelp.no>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
> > In what sense do ye think VM_STACK is related to the Netscape issue? I'd
> > love to hear what ye think causes it to bomb...
>
> I haven't really messed with it too much, so right now I think it's related
> because testing makes it appear to be. i.e. if I have a kernel with VM_STACK
> Netscape will sig11 right after loading; without VM_STACK it's as stable as
> ever. I'd love to figure out why ps isn't working, though...
Unfortunately, for some of us Netscape dying is not the problem. Netscape
*hanging* is the problem. For me, it appears to be related to DNS lookups
*and FreeBSD 3.0.
If I run with MOZILLA_NO_ASYNC_DNS (ie. no DNS helper process), I often
get hangs. This did not happen with FreeBSD 2.2.8. It appears to happen if
name lookups take "too long". If I prime the cache on the DNS server (eg.
by looking up the name manually beforehand), *or* if I let Netscape start
a DNS helper process, I don't get these hangs.
Steinar Haug, Nethelp consulting, sthaug@nethelp.no
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Wed Jan 27 07:59:46 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id HAA01741
for freebsd-current-outgoing; Wed, 27 Jan 1999 07:59:46 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from smtp03.wxs.nl (smtp03.wxs.nl [195.121.6.37])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA01732
for <current@FreeBSD.ORG>; Wed, 27 Jan 1999 07:59:44 -0800 (PST)
(envelope-from asmodai@wxs.nl)
Received: from daemon.ninth-circle.org ([195.121.56.154]) by smtp03.wxs.nl
(Netscape Messaging Server 3.6) with ESMTP id AAAA08;
Wed, 27 Jan 1999 16:59:42 +0100
Message-ID: <XFMail.990127170809.asmodai@wxs.nl>
X-Mailer: XFMail 1.3 [p0] on FreeBSD
X-Priority: 3 (Normal)
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 8bit
MIME-Version: 1.0
In-Reply-To: <20704.917451203@verdi.nethelp.no>
Date: Wed, 27 Jan 1999 17:08:09 +0100 (CET)
Organization: Ninth Circle Enterprises
From: Jeroen Ruigrok/Asmodai <asmodai@wxs.nl>
To: sthaug@nethelp.no
Subject: RE: One answer, one question.
Cc: current@FreeBSD.ORG, green@unixhelp.org
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
On 27-Jan-99 sthaug@nethelp.no wrote:
>> > In what sense do ye think VM_STACK is related to the Netscape issue?
>> > I'd love to hear what ye think causes it to bomb...
>>
>> I haven't really messed with it too much, so right now I think it's
>> related because testing makes it appear to be. i.e. if I have a kernel
>> with VM_STACK Netscape will sig11 right after loading; without VM_STACK
>> it's as stable as ever. I'd love to figure out why ps isn't working,
>> though...
>
> Unfortunately, for some of us Netscape dying is not the problem. Netscape
> *hanging* is the problem. For me, it appears to be related to DNS lookups
> *and FreeBSD 3.0.
Steinaur, ye're referring to the dns helper process which gets spawned by
Netscape?
> If I run with MOZILLA_NO_ASYNC_DNS (ie. no DNS helper process), I often
> get hangs. This did not happen with FreeBSD 2.2.8. It appears to happen
> if name lookups take "too long". If I prime the cache on the DNS server
> (eg. by looking up the name manually beforehand), *or* if I let Netscape
> start a DNS helper process, I don't get these hangs.
OK, that answered it ;)
Do ye use the testbox as a nameserver? Because my box is configured as a
primary nameserver with forwarding. It hangs as soon as name lookups go
afoul. That's one reason towards a hang.
Some other people have experienced and replicated java/javascript pages
that also accounts to the hangs.
Brian appears to have problems with the (new) stack and Netscape.
IMHO those are three completely different things that do not appear to have
anything in common.
Any thoughts?
---
Jeroen Ruigrok van der Werven It's a Dance of Energy,
asmodai(at)wxs.nl when the Mind goes Binary...
Network/Security Specialist <http://home.wxs.nl/~asmodai>
BSD & picoBSD: The Power to Serve <http://www.freebsd.org>
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Wed Jan 27 08:02:02 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id IAA02040
for freebsd-current-outgoing; Wed, 27 Jan 1999 08:02:02 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from janus.syracuse.net (janus.syracuse.net [205.232.47.15])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA01997
for <current@FreeBSD.ORG>; Wed, 27 Jan 1999 08:01:58 -0800 (PST)
(envelope-from green@unixhelp.org)
Received: from localhost (green@localhost)
by janus.syracuse.net (8.8.8/8.8.7) with ESMTP id LAA04075;
Wed, 27 Jan 1999 11:01:33 -0500 (EST)
Date: Wed, 27 Jan 1999 11:01:33 -0500 (EST)
From: Brian Feldman <green@unixhelp.org>
X-Sender: green@janus.syracuse.net
To: sthaug@nethelp.no
cc: asmodai@wxs.nl, current@FreeBSD.ORG
Subject: RE: One answer, one question.
In-Reply-To: <20704.917451203@verdi.nethelp.no>
Message-ID: <Pine.BSF.4.05.9901271101020.2913-100000@janus.syracuse.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
350 Restarting at 4087132. Send STORE or RETRIEVE to initiate transfer.
150 Opening BINARY mode data connection for mozilla-source.tar.gz (7854772 bytes).
37% |****************** | 4414 KB 39:56 ETA
When it's done, I'll work on figuring out the DNS problems.
Brian Feldman _ __ ___ ___ ___
green@unixhelp.org _ __ ___ | _ ) __| \
http://www.freebsd.org/ _ __ ___ ____ | _ \__ \ |) |
FreeBSD: The Power to Serve! _ __ ___ ____ _____ |___/___/___/
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Wed Jan 27 08:02:47 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id IAA02119
for freebsd-current-outgoing; Wed, 27 Jan 1999 08:02:47 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from megaweapon.zigg.com (megaweapon.zigg.com [206.114.60.8])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA02111
for <current@FreeBSD.ORG>; Wed, 27 Jan 1999 08:02:39 -0800 (PST)
(envelope-from matt@zigg.com)
Received: from localhost (matt@localhost)
by megaweapon.zigg.com (8.9.2/8.9.2) with ESMTP id KAA01370;
Wed, 27 Jan 1999 10:56:24 -0500 (EST)
(envelope-from matt@zigg.com)
Date: Wed, 27 Jan 1999 10:56:22 -0500 (EST)
From: Matt Behrens <matt@zigg.com>
To: Gregory Bond <gnb@itga.com.au>
cc: Matthew Dillon <dillon@apollo.backplane.com>,
Mike Smith <mike@smith.net.au>, current@FreeBSD.ORG
Subject: Re: WD/ide_pci bug! [was Re: SOFTUPDATES hangs keyboard ]
In-Reply-To: <199901270408.PAA26575@lightning.itga.com.au>
Message-ID: <Pine.BSF.4.05.9901271050470.406-100000@megaweapon.zigg.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
Greg et al,
I added "flags 0x80ff" to my wd0 and wd1 lines (I don't have PCI
IDE, but rather VLB, so the 0x4000 bit doesn't apply) :), was able
to successfully get 32-bit mode and multiblock-16 out of both of
my drives, and have been able to enable softupdates all around
again without seeing any of my problems either. (I did re-cvsup
-STABLE just before the kernel rebuild and did config -r to make
sure everything was cleared out -- my old kernel was from the 20th,
I believe.)
My previous test was simple -- tar zxvf samba-2.0.0.tar.gz. :)
Just to see if maybe it was just because it was being faster, I
also concurrently ran a chflags -R noschg /usr/obj;rm -rf /usr/obj
on the same partition. I did see somewhat "pausy" activity, but
it didn't actually hang.
Now, we just have to figure out why 32-bit-mode is so special. :)
I have access to a few other boxes; I'll get those set up and see
what we can see.
On Wed, 27 Jan 1999, Gregory Bond wrote:
: Well stone the bloody crows.
:
: System: HP Kayak XA 440BX M/b, P-II, Quantum Fireball ex4.3a
:
: For months I've been running with no flags on either wdc0 or wd0.
: Having followed the recent discussions about DMA mode etc I looked at
: LINT and added "flags 0xa0ff" to wd0. Rebuilt the system using the
: latest 3-Stable code, including Matt D.s VM fixes, and tried yet again
: the test that has quite reliably frozen my system (softupdates enabled
: on /usr/src, cd /usr/src/games, make) and, lo and behold, it worked. I
: thought it was probably Matt's VM patches but (just to make sure) I
: built a kernel without the wd flags and tried again. It failed.
:
: This seems to be saying the problem is the WD driver: When I have flags
: on my disk, it all works; when I use the default, it fails (but only
: on filesystems with softupdates activity...)
:
: Any ide_pci experts like me to try some more tests?
:
: Matt: I'm sorry I ever doubted the VM code or the softupdates!
:
: Probing for devices on PCI bus 0:
: chip0: <Intel 82443BX host to PCI bridge> rev 0x02 on pci0.0.0
: chip1: <Intel 82443BX host to AGP bridge> rev 0x02 on pci0.1.0
: chip2: <Intel 82371AB PCI to ISA bridge> rev 0x02 on pci0.7.0
: ide_pci0: <Intel PIIX4 Bus-master IDE controller> rev 0x01 on pci0.7.1
: chip3: <Intel 82371AB Power management controller> rev 0x02 on pci0.7.3
: [...]
: wdc0 at 0x1f0-0x1f7 irq 14 on isa
: wdc0: unit 0 (wd0): <QUANTUM FIREBALL EX4.3A>, DMA, 32-bit, multi-block-16
: wd0: 4104MB (8405775 sectors), 8895 cyls, 15 heads, 63 S/T, 512 B/S
: wdc1 at 0x170-0x177 irq 15 on isa
: wdc1: unit 0 (atapi): <CD-532E-A/2.0C>, removable, accel, ovlap, dma, iordis
: acd0: drive speed 5512KB/sec, 128KB cache
: acd0: supported read types: CD-R, CD-RW, CD-DA, packet track
: acd0: Audio: play, 16 volume levels
: acd0: Mechanism: ejectable tray
: acd0: Medium: CD-ROM 120mm data disc loaded, unlocked
: vga0 at 0x3b0-0x3df maddr 0xa0000 msize 131072 on isa
:
: Greg.
:
- Matt Behrens <matt@zigg.com>
Network Administrator, zigg.com <http://www.zigg.com/>
Engineer, Nameless IRC Network <http://www.nameless.net/>
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Wed Jan 27 08:03:00 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id IAA02154
for freebsd-current-outgoing; Wed, 27 Jan 1999 08:03:00 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from ns.tar.com (ns.tar.com [204.95.187.2])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA02149
for <current@FreeBSD.ORG>; Wed, 27 Jan 1999 08:02:58 -0800 (PST)
(envelope-from dick@ns.tar.com)
Received: (from dick@localhost)
by ns.tar.com (8.9.2/8.9.1) id KAA01327;
Wed, 27 Jan 1999 10:02:32 -0600 (CST)
(envelope-from dick)
Date: Wed, 27 Jan 1999 10:02:31 -0600
From: "Richard Seaman, Jr." <dick@tar.com>
To: Brian Feldman <green@unixhelp.org>
Cc: Sheldon Hearn <axl@iafrica.com>, Jeroen Ruigrok/Asmodai <asmodai@wxs.nl>,
Andrew Gordon <arg@arg1.demon.co.uk>, current@FreeBSD.ORG,
Matthew Dillon <dillon@apollo.backplane.com>
Subject: Re: 4.0-Current, netscape halts system
Message-ID: <19990127100231.A421@tar.com>
References: <74560.917435435@axl.noc.iafrica.com> <Pine.BSF.4.05.9901271018500.1310-100000@janus.syracuse.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.95i
In-Reply-To: <Pine.BSF.4.05.9901271018500.1310-100000@janus.syracuse.net>; from Brian Feldman on Wed, Jan 27, 1999 at 10:20:14AM -0500
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
On Wed, Jan 27, 1999 at 10:20:14AM -0500, Brian Feldman wrote:
> On Wed, 27 Jan 1999, Sheldon Hearn wrote:
> >
> > I still don't think we're getting any closer to the question "Why is
> > Netscape unstable on CURRENT when it worked fine for me on STABLE?" The
> > problem seems to be that those who know enough to offer a useful answer
> > don't seem to be seeing the instability reported.
> >
> > So if this thread isn't going to be dropped, the focus should probably
> > be shifted to "What information should we request from people who have
> > this problem?"
> >
> > Ciao,
> > Sheldon.
>
> If you have Netscape problems, it would be worthwhile to try removing
> -DVM_STACK from src/sys/compile/BLAH/Makefile and doing a make clean all
> install. I am pretty certain this is the cause of Netscape crashing, at least
> on startup...
Anything is possible. FWIW, though, I've been running with -DVM_STACK
enabled for over a month, and I use Netscape 4.5 everyday, and never had
a problem.
--
Richard Seamman, Jr. email: dick@tar.com
5182 N. Maple Lane phone: 414-367-5450
Chenequa WI 53058 fax: 414-367-5852
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Wed Jan 27 08:06:08 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id IAA02547
for freebsd-current-outgoing; Wed, 27 Jan 1999 08:06:08 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from ns.tar.com (ns.tar.com [204.95.187.2])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA02540
for <current@FreeBSD.ORG>; Wed, 27 Jan 1999 08:06:06 -0800 (PST)
(envelope-from dick@ns.tar.com)
Received: (from dick@localhost)
by ns.tar.com (8.9.2/8.9.1) id KAA01359;
Wed, 27 Jan 1999 10:05:21 -0600 (CST)
(envelope-from dick)
Date: Wed, 27 Jan 1999 10:05:21 -0600
From: "Richard Seaman, Jr." <dick@tar.com>
To: Brian Feldman <green@unixhelp.org>
Cc: Sheldon Hearn <axl@iafrica.com>, Jeroen Ruigrok/Asmodai <asmodai@wxs.nl>,
Andrew Gordon <arg@arg1.demon.co.uk>, current@FreeBSD.ORG,
Matthew Dillon <dillon@apollo.backplane.com>
Subject: Re: 4.0-Current, netscape halts system
Message-ID: <19990127100521.B421@tar.com>
References: <74560.917435435@axl.noc.iafrica.com> <Pine.BSF.4.05.9901271018500.1310-100000@janus.syracuse.net> <19990127100231.A421@tar.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.95i
In-Reply-To: <19990127100231.A421@tar.com>; from Richard Seaman, Jr. on Wed, Jan 27, 1999 at 10:02:31AM -0600
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
On Wed, Jan 27, 1999 at 10:02:31AM -0600, Richard Seaman, Jr. wrote:
> > If you have Netscape problems, it would be worthwhile to try removing
> > -DVM_STACK from src/sys/compile/BLAH/Makefile and doing a make clean all
> > install. I am pretty certain this is the cause of Netscape crashing, at least
> > on startup...
>
> Anything is possible. FWIW, though, I've been running with -DVM_STACK
> enabled for over a month, and I use Netscape 4.5 everyday, and never had
> a problem.
One other thing... -DVM_STACK has been the "default" for only about 36
hours now.
--
Richard Seamman, Jr. email: dick@tar.com
5182 N. Maple Lane phone: 414-367-5450
Chenequa WI 53058 fax: 414-367-5852
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Wed Jan 27 08:09:35 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id IAA02845
for freebsd-current-outgoing; Wed, 27 Jan 1999 08:09:35 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from janus.syracuse.net (janus.syracuse.net [205.232.47.15])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA02840
for <current@FreeBSD.ORG>; Wed, 27 Jan 1999 08:09:33 -0800 (PST)
(envelope-from green@unixhelp.org)
Received: from localhost (green@localhost)
by janus.syracuse.net (8.8.8/8.8.7) with ESMTP id LAA04406;
Wed, 27 Jan 1999 11:07:44 -0500 (EST)
Date: Wed, 27 Jan 1999 11:07:43 -0500 (EST)
From: Brian Feldman <green@unixhelp.org>
X-Sender: green@janus.syracuse.net
To: "Richard Seaman, Jr." <dick@tar.com>
cc: Sheldon Hearn <axl@iafrica.com>, Jeroen Ruigrok/Asmodai <asmodai@wxs.nl>,
Andrew Gordon <arg@arg1.demon.co.uk>, current@FreeBSD.ORG,
Matthew Dillon <dillon@apollo.backplane.com>
Subject: Re: 4.0-Current, netscape halts system
In-Reply-To: <19990127100231.A421@tar.com>
Message-ID: <Pine.BSF.4.05.9901271104160.4181-100000@janus.syracuse.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
On Wed, 27 Jan 1999, Richard Seaman, Jr. wrote:
> On Wed, Jan 27, 1999 at 10:20:14AM -0500, Brian Feldman wrote:
> > On Wed, 27 Jan 1999, Sheldon Hearn wrote:
> > >
> > > I still don't think we're getting any closer to the question "Why is
> > > Netscape unstable on CURRENT when it worked fine for me on STABLE?" The
> > > problem seems to be that those who know enough to offer a useful answer
> > > don't seem to be seeing the instability reported.
> > >
> > > So if this thread isn't going to be dropped, the focus should probably
> > > be shifted to "What information should we request from people who have
> > > this problem?"
> > >
> > > Ciao,
> > > Sheldon.
> >
> > If you have Netscape problems, it would be worthwhile to try removing
> > -DVM_STACK from src/sys/compile/BLAH/Makefile and doing a make clean all
> > install. I am pretty certain this is the cause of Netscape crashing, at least
> > on startup...
>
> Anything is possible. FWIW, though, I've been running with -DVM_STACK
> enabled for over a month, and I use Netscape 4.5 everyday, and never had
> a problem.
Netscape 4.08 here, never had VM_STACK being used before.... most recent kernel.
I booted with a new kernel to find out netscape sig11d on start-up. Then I
booted /kernel.old and Netscape worked fine. So I booted a brand-new kernel
without VM_STACK and Netscape runs. Go figure? :) The old kernel had not
VM_STACK. Anyhoo, I'm making world in hopes of getting rid of that damned ps
error.
>
> --
> Richard Seamman, Jr. email: dick@tar.com
> 5182 N. Maple Lane phone: 414-367-5450
> Chenequa WI 53058 fax: 414-367-5852
>
Brian Feldman _ __ ___ ___ ___
green@unixhelp.org _ __ ___ | _ ) __| \
http://www.freebsd.org/ _ __ ___ ____ | _ \__ \ |) |
FreeBSD: The Power to Serve! _ __ ___ ____ _____ |___/___/___/
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Wed Jan 27 08:23:19 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id IAA04731
for freebsd-current-outgoing; Wed, 27 Jan 1999 08:23:19 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from symbion.srrc.usda.gov (symbion.srrc.usda.gov [199.133.86.40])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA04714;
Wed, 27 Jan 1999 08:23:11 -0800 (PST)
(envelope-from gjohnson@nola.srrc.usda.gov)
Received: (from glenn@localhost)
by symbion.srrc.usda.gov (8.9.2/8.9.2) id KAA80500;
Wed, 27 Jan 1999 10:23:01 -0600 (CST)
(envelope-from glenn)
From: Glenn Johnson <gjohnson@nola.srrc.usda.gov>
Date: Wed, 27 Jan 1999 10:23:01 -0600
To: Satoshi Asami <asami@FreeBSD.ORG>
Cc: gljohns@bellsouth.net, current@FreeBSD.ORG,
sgk@troutmask.apl.washington.edu, obrien@NUXI.com
Subject: Re: removing f2c from base distribution
Message-ID: <19990127102301.A80336@symbion.srrc.usda.gov>
References: <19990127005850.A10486@gforce.johnson.home> <199901271314.FAA65788@silvia.hip.berkeley.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.95.1i
In-Reply-To: <199901271314.FAA65788@silvia.hip.berkeley.edu>; from Satoshi Asami on Wed, Jan 27, 1999 at 05:14:33AM -0800
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
On Wed, Jan 27, 1999 at 05:14:33AM -0800, Satoshi Asami wrote:
> * The biggest problem has been that the port of g77 has not worked
> * properly for quite some time and in fact is currently marked as
> * broken. I would anticipate that this situation would not change much in
>
> That (and bug fix issues, as DavidO contends) all depends on the
> commitment of the maintainer (which there is none for the g77 port).
> Unless someone who uses g77 regularly steps up to maintain it, it will
> remain broken. This is the same for all ports, and I don't see why a
> Fortran compiler should be an exception.
>
> Granted, if won't be blatantly broken if it's in the base
> distribution, but that's only because people will yell and scream if
> their "make world" doesn't work. If the amount of noise that
> generates is significantly different from what happens if it's a
> broken port, that's actually a pretty good argument *against* putting
> it in the base distribution, as it means we can keep g77 running only
> by annoying people who don't use it when it's broken. (1/2 :)
>
> This port has been marked broken since July last year. Sorry, but I
> just don't have a whole lot of sympathy for something that can stay
> broken that long without anyone fixing it. ;)
>
Your points are well taken. I had a local port of g77 that built
against our current gcc. I never submitted it however for a couple
of reasons:
1. The port I had was for 0.5.19. This will build against our current
gcc, but g77 has advanced significantly since then. Unfortunately, the
newer versions need gcc 2.8. It was simply easier for me to use the
newer versions of g77 with gcc 2.8 or egcs release versions. Note that I
said easier for me; some colleagues of mine could/would not want to have
to maintain a compiler on their own. Yes, I was told this on a couple
of occasions. I can not see a point in me becoming the g77 0.5.19 port
maintainer when I am using newer versions of g77.
2. In light of the above, it seemed that f77 (f2c/gcc) was good enough
for most cases. The g77 port was not essential because there was
fairly good Fortran support in the base system. Apparently this will
no longer be the case and therefore the g77 (or f2c) port will become
essential. That is to say, essential for those needing Fortran.
If it is decided that Fortran support will disappear from the base
system and nobody else wants to maintain g77, I will gladly do
it. However, I will only maintain a version that I am using so that
means I will maintain a port once gcc 2.8 is officially brought in as
the stock compiler.
--
Glenn Johnson
Technician
USDA, ARS, SRRC
New Orleans, LA
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Wed Jan 27 08:24:02 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id IAA04857
for freebsd-current-outgoing; Wed, 27 Jan 1999 08:24:02 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from khavrinen.lcs.mit.edu (khavrinen.lcs.mit.edu [18.24.4.193])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA04803
for <freebsd-current@FreeBSD.ORG>; Wed, 27 Jan 1999 08:24:00 -0800 (PST)
(envelope-from wollman@khavrinen.lcs.mit.edu)
Received: (from wollman@localhost)
by khavrinen.lcs.mit.edu (8.9.1/8.9.1) id LAA07822;
Wed, 27 Jan 1999 11:23:56 -0500 (EST)
(envelope-from wollman)
Date: Wed, 27 Jan 1999 11:23:56 -0500 (EST)
From: Garrett Wollman <wollman@khavrinen.lcs.mit.edu>
Message-Id: <199901271623.LAA07822@khavrinen.lcs.mit.edu>
To: "Daniel C. Sobral" <dcs@newsguy.com>
Cc: freebsd-current@FreeBSD.ORG
Subject: Re: removing f2c from base distribution
In-Reply-To: <36AEFC21.A9B32C67@newsguy.com>
References: <199901270504.WAA18271@mt.sri.com>
<199901270555.VAA09197@troutmask.apl.washington.edu>
<19990126220644.A7037@relay.nuxi.com>
<199901270623.IAA01480@greenpeace.grondar.za>
<36AEFC21.A9B32C67@newsguy.com>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
<<On Wed, 27 Jan 1999 20:44:33 +0900, "Daniel C. Sobral" <dcs@newsguy.com> said:
> A lot of people use a lot of things out of ports. Why should Fortran
> be different?
Because Berkeley Unix has /always/ included a FORTRAN compiler.
-GAWollman
--
Garrett A. Wollman | O Siem / We are all family / O Siem / We're all the same
wollman@lcs.mit.edu | O Siem / The fires of freedom
Opinions not those of| Dance in the burning flame
MIT, LCS, CRS, or NSA| - Susan Aglukark and Chad Irschick
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Wed Jan 27 08:24:53 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id IAA04917
for freebsd-current-outgoing; Wed, 27 Jan 1999 08:24:53 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from gargoyle.bazzle.com (gargoyle.bazzle.com [206.103.246.189])
by hub.freebsd.org (8.8.8/8.8.8) with SMTP id IAA04904
for <current@FreeBSD.ORG>; Wed, 27 Jan 1999 08:24:50 -0800 (PST)
(envelope-from ejc@bazzle.com)
Received: (qmail 59885 invoked from network); 27 Jan 1999 16:24:49 -0000
Received: from gargoyle.bazzle.com (206.103.246.189)
by gargoyle.bazzle.com with SMTP; 27 Jan 1999 16:24:49 -0000
Date: Wed, 27 Jan 1999 11:24:48 -0500 (EST)
From: "Eric J. Chet" <ejc@bazzle.com>
To: Brian Feldman <green@unixhelp.org>
cc: Jeroen Ruigrok/Asmodai <asmodai@wxs.nl>, current@FreeBSD.ORG
Subject: RE: One answer, one question.
In-Reply-To: <Pine.BSF.4.05.9901271007430.1310-100000@janus.syracuse.net>
Message-ID: <Pine.BSF.4.05.9901271120370.59103-100000@gargoyle.bazzle.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
On Wed, 27 Jan 1999, Brian Feldman wrote:
> On Wed, 27 Jan 1999, Jeroen Ruigrok/Asmodai wrote:
>
> > Also, I am also not seeing the relevance of ps. Sure, Matthew commited a
> > bunch of VM hacks 'n fixes which appear to work nicely here (mayhaps even
> > better than the prior stuff) and ps works properly. Ye sure yet not just
> > forgetting to rebuild ps and the likes after the recent changes?
>
> I am certain VM_STACK is breaking Netscape. Ps isn't related, but I am having
> problems with it, even after rebuilding everything, kvm_mkdb'ing... :(
>
Hello
I don't see the problems here, running -current 1/26. I have been
using netscape and native kernel threads(-lpthread from lt.tar.com) heavly
without any problems.
ejc
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Wed Jan 27 08:43:42 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id IAA07672
for freebsd-current-outgoing; Wed, 27 Jan 1999 08:43:42 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from pau-amma.whistle.com (s205m64.whistle.com [207.76.205.64])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA07663
for <freebsd-current@FreeBSD.ORG>; Wed, 27 Jan 1999 08:43:40 -0800 (PST)
(envelope-from dhw@whistle.com)
Received: (from dhw@localhost)
by pau-amma.whistle.com (8.9.1/8.9.1) id IAA12570;
Wed, 27 Jan 1999 08:42:08 -0800 (PST)
(envelope-from dhw)
Date: Wed, 27 Jan 1999 08:42:08 -0800 (PST)
From: David Wolfskill <dhw@whistle.com>
Message-Id: <199901271642.IAA12570@pau-amma.whistle.com>
To: axl@iafrica.com
Subject: Re: NIS with HPUX 10.20
Cc: freebsd-current@FreeBSD.ORG
In-Reply-To: <74731.917435629@axl.noc.iafrica.com>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
>From: Sheldon Hearn <axl@iafrica.com>
>Date: Wed, 27 Jan 1999 13:13:49 +0200
>> I did note that, unlike the SNAP, the result had a /usr/libexec/ld.so;
>Did you make your RELENG_3 world with or without -DNOAOUT? I don't think
>/usr/libexec is created for a -DNOAOUT world. I've noticed this
>particularly with jdk.
I made it via "make world" -- no other arguments.
Unless I have a reason for doing otherwise (of which, of course, I must
be aware), I use defaults. My goal is to figure out how to migrate our
engineering net to 3.x as painlessly as possible... quickly.
I am finding, for example, that the NFS-mounted /usr/local that I
inherited when I got here, though it has its expected advantages as in
non-FreeBSD UNIX environments, is becoming a liability in this regard.
david
--
David Wolfskill UNIX System Administrator
dhw@whistle.com voice: (650) 577-7158 pager: (650) 371-4621
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Wed Jan 27 08:52:39 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id IAA08782
for freebsd-current-outgoing; Wed, 27 Jan 1999 08:52:39 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from smtp04.wxs.nl (smtp04.wxs.nl [195.121.6.59])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA08770
for <current@FreeBSD.ORG>; Wed, 27 Jan 1999 08:52:35 -0800 (PST)
(envelope-from asmodai@wxs.nl)
Received: from daemon.ninth-circle.org ([195.121.56.175]) by smtp04.wxs.nl
(Netscape Messaging Server 3.6) with ESMTP id AAA433B
for <current@FreeBSD.ORG>; Wed, 27 Jan 1999 17:52:29 +0100
Message-ID: <XFMail.990127180059.asmodai@wxs.nl>
X-Mailer: XFMail 1.3 [p0] on FreeBSD
X-Priority: 3 (Normal)
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 8bit
MIME-Version: 1.0
Date: Wed, 27 Jan 1999 18:00:59 +0100 (CET)
Organization: Ninth Circle Enterprises
From: Jeroen Ruigrok/Asmodai <asmodai@wxs.nl>
To: FreeBSD Current <current@FreeBSD.ORG>
Subject: Netscape | Mozilla
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
OK,
just to re-organise something here:
Some people are referring to Netscape (Navigator | Communicator)
whereas others are referring to Mozilla (from www.mozilla.org)
I think this makes a ton of differences.
Also, anyone even bothered to file the communicator 4.5 binary?
[root@daemon] (27) # file /usr/local/netscape-4.5/communicator-4.5.bin
/usr/local/netscape-4.5/communicator-4.5.bin: FreeBSD/i386 compact demand
paged dynamically linked executable
Matt or others might want to slap me for being way off but afaik the VM
stuff was tied with the swapping and not paging. So this would mean that
the VM_STACK cannot be the problem.
Might the old communicator still being tied to a.out?
Questions and no real answers =\
---
Jeroen Ruigrok van der Werven It's a Dance of Energy,
asmodai(at)wxs.nl when the Mind goes Binary...
Network/Security Specialist <http://home.wxs.nl/~asmodai>
BSD & picoBSD: The Power to Serve <http://www.freebsd.org>
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Wed Jan 27 08:55:02 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id IAA09104
for freebsd-current-outgoing; Wed, 27 Jan 1999 08:55:02 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from ns.mt.sri.com (sri-gw.MT.net [206.127.105.141])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA09070;
Wed, 27 Jan 1999 08:55:00 -0800 (PST)
(envelope-from nate@mt.sri.com)
Received: from mt.sri.com (rocky.mt.sri.com [206.127.76.100])
by ns.mt.sri.com (8.8.8/8.8.8) with SMTP id JAA04576;
Wed, 27 Jan 1999 09:54:46 -0700 (MST)
(envelope-from nate@rocky.mt.sri.com)
Received: by mt.sri.com (SMI-8.6/SMI-SVR4)
id JAA21318; Wed, 27 Jan 1999 09:54:45 -0700
Date: Wed, 27 Jan 1999 09:54:45 -0700
Message-Id: <199901271654.JAA21318@mt.sri.com>
From: Nate Williams <nate@mt.sri.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
To: obrien@NUXI.com
Cc: Satoshi Asami <asami@FreeBSD.ORG>, freebsd-current@FreeBSD.ORG
Subject: Re: removing f2c from base distribution
In-Reply-To: <19990126220000.G4119@relay.nuxi.com>
References: <199901262148.NAA07097@troutmask.apl.washington.edu>
<199901270116.RAA64007@silvia.hip.berkeley.edu>
<19990126220000.G4119@relay.nuxi.com>
X-Mailer: VM 6.34 under 19.16 "Lille" XEmacs Lucid
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
> > Um, I'm still alive but can someone explain me why this can't be a
> > "regular" port? Being useful to some but not the majority, no other
> > parts of the system depending on it, this looks like a model citizen
> > in the ideal ports world. :)
>
> Because we loose control over it. There is a move to push some things
> out of the base system and into ports. Fine, but then how does bug fixes
> happen?
I think this is a moot point. As Steven pointed out months ago, the
version of f2c in the base system had rotted due to lack of maintainer.
Keeping it in the base system isn't going to keep it updated unless
*someone* wants to update it.
> I believe the committed that fixed the f2c problems on the Alpha
> really liked having the abilility to do so.
And that person would have been able to do it in the ports if they were
so motivated just as easily.
Nate
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Wed Jan 27 09:05:52 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id JAA10219
for freebsd-current-outgoing; Wed, 27 Jan 1999 09:05:52 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from vader.cs.berkeley.edu (vader.CS.Berkeley.EDU [128.32.38.234])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA10210
for <freebsd-current@FreeBSD.ORG>; Wed, 27 Jan 1999 09:05:49 -0800 (PST)
(envelope-from asami@vader.cs.berkeley.edu)
Received: from silvia.hip.berkeley.edu (sji-ca13-237.ix.netcom.com [209.109.238.237]) by vader.cs.berkeley.edu (8.8.7/8.7.3) with ESMTP id JAA02108; Wed, 27 Jan 1999 09:05:46 -0800 (PST)
Received: (from asami@localhost) by silvia.hip.berkeley.edu (8.9.1/8.6.9) id JAA67070; Wed, 27 Jan 1999 09:05:41 -0800 (PST)
Date: Wed, 27 Jan 1999 09:05:41 -0800 (PST)
Message-Id: <199901271705.JAA67070@silvia.hip.berkeley.edu>
To: wollman@khavrinen.lcs.mit.edu
CC: dcs@newsguy.com, freebsd-current@FreeBSD.ORG
In-reply-to: <199901271623.LAA07822@khavrinen.lcs.mit.edu> (message from
Garrett Wollman on Wed, 27 Jan 1999 11:23:56 -0500 (EST))
Subject: Re: removing f2c from base distribution
From: asami@FreeBSD.ORG (Satoshi Asami)
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
* From: Garrett Wollman <wollman@khavrinen.lcs.mit.edu>
* > A lot of people use a lot of things out of ports. Why should Fortran
* > be different?
*
* Because Berkeley Unix has /always/ included a FORTRAN compiler.
Maybe that's because Berkeley Unix never had (until recently, anyway)
a ports system? :)
Satoshi
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Wed Jan 27 09:06:39 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id JAA10309
for freebsd-current-outgoing; Wed, 27 Jan 1999 09:06:39 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from ns.mt.sri.com (sri-gw.MT.net [206.127.105.141])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA10300
for <freebsd-current@FreeBSD.ORG>; Wed, 27 Jan 1999 09:06:36 -0800 (PST)
(envelope-from nate@mt.sri.com)
Received: from mt.sri.com (rocky.mt.sri.com [206.127.76.100])
by ns.mt.sri.com (8.8.8/8.8.8) with SMTP id KAA04675;
Wed, 27 Jan 1999 10:06:17 -0700 (MST)
(envelope-from nate@rocky.mt.sri.com)
Received: by mt.sri.com (SMI-8.6/SMI-SVR4)
id KAA21389; Wed, 27 Jan 1999 10:06:16 -0700
Date: Wed, 27 Jan 1999 10:06:16 -0700
Message-Id: <199901271706.KAA21389@mt.sri.com>
From: Nate Williams <nate@mt.sri.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
To: Garrett Wollman <wollman@khavrinen.lcs.mit.edu>
Cc: "Daniel C. Sobral" <dcs@newsguy.com>, freebsd-current@FreeBSD.ORG
Subject: Re: removing f2c from base distribution
In-Reply-To: <199901271623.LAA07822@khavrinen.lcs.mit.edu>
References: <199901270504.WAA18271@mt.sri.com>
<199901270555.VAA09197@troutmask.apl.washington.edu>
<19990126220644.A7037@relay.nuxi.com>
<199901270623.IAA01480@greenpeace.grondar.za>
<36AEFC21.A9B32C67@newsguy.com>
<199901271623.LAA07822@khavrinen.lcs.mit.edu>
X-Mailer: VM 6.34 under 19.16 "Lille" XEmacs Lucid
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
> > A lot of people use a lot of things out of ports. Why should Fortran
> > be different?
>
> Because Berkeley Unix has /always/ included a FORTRAN compiler.
And they have /always/ included games. Next issue.
Nate
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Wed Jan 27 09:06:43 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id JAA10324
for freebsd-current-outgoing; Wed, 27 Jan 1999 09:06:43 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from pooh.elsevier.nl (pooh.elsevier.nl [145.36.9.32])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA10308
for <current@FreeBSD.ORG>; Wed, 27 Jan 1999 09:06:39 -0800 (PST)
(envelope-from steveo@iol.ie)
Received: from pooh.elsevier.nl (localhost [127.0.0.1])
by pooh.elsevier.nl (8.9.2/8.9.2) with ESMTP id RAA71356;
Wed, 27 Jan 1999 17:05:37 GMT
(envelope-from steveo@iol.ie)
Message-ID: <XFMail.990127170536.steveo@iol.ie>
X-Mailer: XFMail 1.3 [p0] on FreeBSD
X-Priority: 3 (Normal)
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 8bit
MIME-Version: 1.0
In-Reply-To: <XFMail.990127180059.asmodai@wxs.nl>
Date: Wed, 27 Jan 1999 17:05:36 -0000 (GMT)
From: "Steve O'Hara-Smith" <steveo@iol.ie>
To: Jeroen Ruigrok/Asmodai <asmodai@wxs.nl>
Subject: RE: Netscape | Mozilla
Cc: FreeBSD Current <current@FreeBSD.ORG>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
On 27-Jan-99 Jeroen Ruigrok/Asmodai wrote:
> OK,
>
> just to re-organise something here:
>
> Might the old communicator still being tied to a.out?
This I can answer - all versions of netscape are aout, (I've
just been looking for an elf netscape so that I can throw away my aout
libraries which are being carried around only for netscape nowadays).
----------------------------------
E-Mail: Steve O'Hara-Smith <steveo@iol.ie>
Date: 27-Jan-99
Time: 17:03:48
This message was sent by XFMail
----------------------------------
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Wed Jan 27 09:09:22 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id JAA10637
for freebsd-current-outgoing; Wed, 27 Jan 1999 09:09:22 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from vader.cs.berkeley.edu (vader.CS.Berkeley.EDU [128.32.38.234])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA10615
for <current@FreeBSD.ORG>; Wed, 27 Jan 1999 09:09:16 -0800 (PST)
(envelope-from asami@vader.cs.berkeley.edu)
Received: from silvia.hip.berkeley.edu (sji-ca13-237.ix.netcom.com [209.109.238.237]) by vader.cs.berkeley.edu (8.8.7/8.7.3) with ESMTP id JAA02112; Wed, 27 Jan 1999 09:09:10 -0800 (PST)
Received: (from asami@localhost) by silvia.hip.berkeley.edu (8.9.1/8.6.9) id JAA67094; Wed, 27 Jan 1999 09:09:05 -0800 (PST)
Date: Wed, 27 Jan 1999 09:09:05 -0800 (PST)
Message-Id: <199901271709.JAA67094@silvia.hip.berkeley.edu>
To: gjohnson@nola.srrc.usda.gov
CC: gljohns@bellsouth.net, current@FreeBSD.ORG,
sgk@troutmask.apl.washington.edu, obrien@NUXI.com
In-reply-to: <19990127102301.A80336@symbion.srrc.usda.gov> (message from Glenn
Johnson on Wed, 27 Jan 1999 10:23:01 -0600)
Subject: Re: removing f2c from base distribution
From: asami@FreeBSD.ORG (Satoshi Asami)
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
* From: Glenn Johnson <gjohnson@nola.srrc.usda.gov>
* Your points are well taken. I had a local port of g77 that built
* against our current gcc. I never submitted it however for a couple
* of reasons:
*
* 1. The port I had was for 0.5.19. This will build against our current
* gcc, but g77 has advanced significantly since then. Unfortunately, the
* newer versions need gcc 2.8. It was simply easier for me to use the
* newer versions of g77 with gcc 2.8 or egcs release versions. Note that I
* said easier for me; some colleagues of mine could/would not want to have
* to maintain a compiler on their own. Yes, I was told this on a couple
* of occasions. I can not see a point in me becoming the g77 0.5.19 port
* maintainer when I am using newer versions of g77.
I wasn't blaming you (or anyone in particular, for that matter). You
don't even have to become a maintainer. But if you have a fix to the
build problems, and you think it is an important enough piece of
software for you and other people, please send in a patch so it can be
built.
Satoshi
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Wed Jan 27 09:14:39 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id JAA11402
for freebsd-current-outgoing; Wed, 27 Jan 1999 09:14:39 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from megaweapon.zigg.com (megaweapon.zigg.com [206.114.60.8])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA11397
for <current@FreeBSD.ORG>; Wed, 27 Jan 1999 09:14:33 -0800 (PST)
(envelope-from matt@zigg.com)
Received: from localhost (matt@localhost)
by megaweapon.zigg.com (8.9.2/8.9.2) with ESMTP id MAA00345;
Wed, 27 Jan 1999 12:08:08 -0500 (EST)
(envelope-from matt@zigg.com)
Date: Wed, 27 Jan 1999 12:07:52 -0500 (EST)
From: Matt Behrens <matt@zigg.com>
To: Gregory Bond <gnb@itga.com.au>
cc: Matthew Dillon <dillon@apollo.backplane.com>,
Mike Smith <mike@smith.net.au>, current@FreeBSD.ORG
Subject: Re: WD/ide_pci bug! [was Re: SOFTUPDATES hangs keyboard ]
In-Reply-To: <Pine.BSF.4.05.9901271050470.406-100000@megaweapon.zigg.com>
Message-ID: <Pine.BSF.4.05.9901271206280.325-100000@megaweapon.zigg.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
Never mind. Apparently it went south on me while I was having
lunch.
I got this curious error when I paniced the debugger (paraphrased):
HELP! busy_count is less then 0 (-1)
Is this something of a clue? I've never been able to sync the
drives at all by panicing, it can't communicate with the IDE
controller for some reason. Lots of status 0x58's.
On Wed, 27 Jan 1999, Matt Behrens wrote:
: Greg et al,
:
: I added "flags 0x80ff" to my wd0 and wd1 lines (I don't have PCI
: IDE, but rather VLB, so the 0x4000 bit doesn't apply) :), was able
: to successfully get 32-bit mode and multiblock-16 out of both of
: my drives, and have been able to enable softupdates all around
: again without seeing any of my problems either. (I did re-cvsup
: -STABLE just before the kernel rebuild and did config -r to make
: sure everything was cleared out -- my old kernel was from the 20th,
: I believe.)
:
: My previous test was simple -- tar zxvf samba-2.0.0.tar.gz. :)
: Just to see if maybe it was just because it was being faster, I
: also concurrently ran a chflags -R noschg /usr/obj;rm -rf /usr/obj
: on the same partition. I did see somewhat "pausy" activity, but
: it didn't actually hang.
:
: Now, we just have to figure out why 32-bit-mode is so special. :)
: I have access to a few other boxes; I'll get those set up and see
: what we can see.
:
: On Wed, 27 Jan 1999, Gregory Bond wrote:
:
: : Well stone the bloody crows.
: :
: : System: HP Kayak XA 440BX M/b, P-II, Quantum Fireball ex4.3a
: :
: : For months I've been running with no flags on either wdc0 or wd0.
: : Having followed the recent discussions about DMA mode etc I looked at
: : LINT and added "flags 0xa0ff" to wd0. Rebuilt the system using the
: : latest 3-Stable code, including Matt D.s VM fixes, and tried yet again
: : the test that has quite reliably frozen my system (softupdates enabled
: : on /usr/src, cd /usr/src/games, make) and, lo and behold, it worked. I
: : thought it was probably Matt's VM patches but (just to make sure) I
: : built a kernel without the wd flags and tried again. It failed.
: :
: : This seems to be saying the problem is the WD driver: When I have flags
: : on my disk, it all works; when I use the default, it fails (but only
: : on filesystems with softupdates activity...)
: :
: : Any ide_pci experts like me to try some more tests?
: :
: : Matt: I'm sorry I ever doubted the VM code or the softupdates!
: :
: : Probing for devices on PCI bus 0:
: : chip0: <Intel 82443BX host to PCI bridge> rev 0x02 on pci0.0.0
: : chip1: <Intel 82443BX host to AGP bridge> rev 0x02 on pci0.1.0
: : chip2: <Intel 82371AB PCI to ISA bridge> rev 0x02 on pci0.7.0
: : ide_pci0: <Intel PIIX4 Bus-master IDE controller> rev 0x01 on pci0.7.1
: : chip3: <Intel 82371AB Power management controller> rev 0x02 on pci0.7.3
: : [...]
: : wdc0 at 0x1f0-0x1f7 irq 14 on isa
: : wdc0: unit 0 (wd0): <QUANTUM FIREBALL EX4.3A>, DMA, 32-bit, multi-block-16
: : wd0: 4104MB (8405775 sectors), 8895 cyls, 15 heads, 63 S/T, 512 B/S
: : wdc1 at 0x170-0x177 irq 15 on isa
: : wdc1: unit 0 (atapi): <CD-532E-A/2.0C>, removable, accel, ovlap, dma, iordis
: : acd0: drive speed 5512KB/sec, 128KB cache
: : acd0: supported read types: CD-R, CD-RW, CD-DA, packet track
: : acd0: Audio: play, 16 volume levels
: : acd0: Mechanism: ejectable tray
: : acd0: Medium: CD-ROM 120mm data disc loaded, unlocked
: : vga0 at 0x3b0-0x3df maddr 0xa0000 msize 131072 on isa
: :
: : Greg.
: :
:
: - Matt Behrens <matt@zigg.com>
: Network Administrator, zigg.com <http://www.zigg.com/>
: Engineer, Nameless IRC Network <http://www.nameless.net/>
:
:
- Matt Behrens <matt@zigg.com>
Network Administrator, zigg.com <http://www.zigg.com/>
Engineer, Nameless IRC Network <http://www.nameless.net/>
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Wed Jan 27 09:15:54 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id JAA11557
for freebsd-current-outgoing; Wed, 27 Jan 1999 09:15:54 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from peach.ocn.ne.jp (peach.ocn.ne.jp [210.145.254.87])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA11543
for <freebsd-current@FreeBSD.ORG>; Wed, 27 Jan 1999 09:15:50 -0800 (PST)
(envelope-from dcs@newsguy.com)
Received: from newsguy.com by peach.ocn.ne.jp (8.9.1a/OCN) id CAA19465; Thu, 28 Jan 1999 02:15:39 +0900 (JST)
Message-ID: <36AF4948.D0F88A52@newsguy.com>
Date: Thu, 28 Jan 1999 02:13:44 +0900
From: "Daniel C. Sobral" <dcs@newsguy.com>
X-Mailer: Mozilla 4.5 [en] (Win98; I)
X-Accept-Language: pt-BR,ja
MIME-Version: 1.0
To: Garrett Wollman <wollman@khavrinen.lcs.mit.edu>
CC: freebsd-current@FreeBSD.ORG
Subject: Re: removing f2c from base distribution
References: <199901270504.WAA18271@mt.sri.com>
<199901270555.VAA09197@troutmask.apl.washington.edu>
<19990126220644.A7037@relay.nuxi.com>
<199901270623.IAA01480@greenpeace.grondar.za>
<36AEFC21.A9B32C67@newsguy.com> <199901271623.LAA07822@khavrinen.lcs.mit.edu>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
Garrett Wollman wrote:
>
> <<On Wed, 27 Jan 1999 20:44:33 +0900, "Daniel C. Sobral" <dcs@newsguy.com> said:
>
> > A lot of people use a lot of things out of ports. Why should Fortran
> > be different?
>
> Because Berkeley Unix has /always/ included a FORTRAN compiler.
Somehow I feared you might have said that... :-)
All things considered, though, it just doesn't mean anything to me.
So, this is were we agree to disagree, I guess. :-)
--
Daniel C. Sobral (8-DCS)
dcs@newsguy.com
If you sell your soul to the Devil and all you get is an MCSE from
it, you haven't gotten market rate.
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Wed Jan 27 09:17:37 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id JAA11751
for freebsd-current-outgoing; Wed, 27 Jan 1999 09:17:37 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from smtp04.wxs.nl (smtp04.wxs.nl [195.121.6.59])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA11731
for <current@FreeBSD.ORG>; Wed, 27 Jan 1999 09:17:33 -0800 (PST)
(envelope-from asmodai@wxs.nl)
Received: from daemon.ninth-circle.org ([195.121.56.175]) by smtp04.wxs.nl
(Netscape Messaging Server 3.6) with ESMTP id AAA5DFB;
Wed, 27 Jan 1999 18:17:27 +0100
Message-ID: <XFMail.990127182557.asmodai@wxs.nl>
X-Mailer: XFMail 1.3 [p0] on FreeBSD
X-Priority: 3 (Normal)
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 8bit
MIME-Version: 1.0
In-Reply-To: <XFMail.990127170536.steveo@iol.ie>
Date: Wed, 27 Jan 1999 18:25:57 +0100 (CET)
Organization: Ninth Circle Enterprises
From: Jeroen Ruigrok/Asmodai <asmodai@wxs.nl>
To: "Steve O'Hara-Smith" <steveo@iol.ie>
Subject: RE: Netscape | Mozilla
Cc: FreeBSD Current <current@FreeBSD.ORG>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
On 27-Jan-99 Steve O'Hara-Smith wrote:
> On 27-Jan-99 Jeroen Ruigrok/Asmodai wrote:
>> Might the old communicator still being tied to a.out?
>
> This I can answer - all versions of netscape are aout, (I've
> just been looking for an elf netscape so that I can throw away my aout
> libraries which are being carried around only for netscape nowadays).
OK, thanks. Now to see where that places netscape into the whole...
We aren't building a.out ld's ever since e-day (ELF-day), so the problem
had to be present before that time. Comments?
*ponders deeply*
---
Jeroen Ruigrok van der Werven It's a Dance of Energy,
asmodai(at)wxs.nl when the Mind goes Binary...
Network/Security Specialist <http://home.wxs.nl/~asmodai>
BSD & picoBSD: The Power to Serve <http://www.freebsd.org>
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Wed Jan 27 09:17:44 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id JAA11785
for freebsd-current-outgoing; Wed, 27 Jan 1999 09:17:44 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.95.76.54])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA11764;
Wed, 27 Jan 1999 09:17:38 -0800 (PST)
(envelope-from sgk@troutmask.apl.washington.edu)
Received: (from sgk@localhost)
by troutmask.apl.washington.edu (8.9.1/8.9.1) id JAA11594;
Wed, 27 Jan 1999 09:18:49 -0800 (PST)
(envelope-from sgk)
From: Steve Kargl <sgk@troutmask.apl.washington.edu>
Message-Id: <199901271718.JAA11594@troutmask.apl.washington.edu>
Subject: Re: removing f2c from base distribution
In-Reply-To: <199901271709.JAA67094@silvia.hip.berkeley.edu> from Satoshi Asami at "Jan 27, 1999 9: 9: 5 am"
To: asami@FreeBSD.ORG (Satoshi Asami)
Date: Wed, 27 Jan 1999 09:18:49 -0800 (PST)
Cc: gjohnson@nola.srrc.usda.gov, gljohns@bellsouth.net, current@FreeBSD.ORG,
obrien@NUXI.com
X-Mailer: ELM [version 2.4ME+ PL43 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
Satoshi Asami wrote:
> * From: Glenn Johnson <gjohnson@nola.srrc.usda.gov>
>
> * Your points are well taken. I had a local port of g77 that built
> * against our current gcc. I never submitted it however for a couple
> * of reasons:
> *
> * 1. The port I had was for 0.5.19. This will build against our current
> * gcc, but g77 has advanced significantly since then. Unfortunately, the
> * newer versions need gcc 2.8. It was simply easier for me to use the
> * newer versions of g77 with gcc 2.8 or egcs release versions. Note that I
> * said easier for me; some colleagues of mine could/would not want to have
> * to maintain a compiler on their own. Yes, I was told this on a couple
> * of occasions. I can not see a point in me becoming the g77 0.5.19 port
> * maintainer when I am using newer versions of g77.
>
> I wasn't blaming you (or anyone in particular, for that matter). You
> don't even have to become a maintainer. But if you have a fix to the
> build problems, and you think it is an important enough piece of
> software for you and other people, please send in a patch so it can be
> built.
>
The g77-0.5.19(.1) is *extremely* out-of-date. It should be dropped from
the ports collection, and if someone wants to use g77, then they should
install egcs.
The newer versions of g77 do not work with gcc-2.7.2.x. The author of
g77 states that you shouldn't even try to back port g77 to any version
of gcc earlier than gcc-2.8
--
Steve
finger kargl@troutmask.apl.washington.edu
http://troutmask.apl.washington.edu/~clesceri/kargl.html
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Wed Jan 27 09:23:20 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id JAA12532
for freebsd-current-outgoing; Wed, 27 Jan 1999 09:23:20 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.95.76.54])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA12525
for <freebsd-current@FreeBSD.ORG>; Wed, 27 Jan 1999 09:23:18 -0800 (PST)
(envelope-from sgk@troutmask.apl.washington.edu)
Received: (from sgk@localhost)
by troutmask.apl.washington.edu (8.9.1/8.9.1) id JAA11643;
Wed, 27 Jan 1999 09:24:28 -0800 (PST)
(envelope-from sgk)
From: Steve Kargl <sgk@troutmask.apl.washington.edu>
Message-Id: <199901271724.JAA11643@troutmask.apl.washington.edu>
Subject: Re: removing f2c from base distribution
In-Reply-To: <199901271623.LAA07822@khavrinen.lcs.mit.edu> from Garrett Wollman at "Jan 27, 1999 11:23:56 am"
To: wollman@khavrinen.lcs.mit.edu (Garrett Wollman)
Date: Wed, 27 Jan 1999 09:24:28 -0800 (PST)
Cc: dcs@newsguy.com, freebsd-current@FreeBSD.ORG
X-Mailer: ELM [version 2.4ME+ PL43 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
Garrett Wollman wrote:
> <<On Wed, 27 Jan 1999 20:44:33 +0900, "Daniel C. Sobral" <dcs@newsguy.com> said:
>
>
> > A lot of people use a lot of things out of ports. Why should Fortran
> > be different?
>
> Because Berkeley Unix has /always/ included a FORTRAN compiler.
>
Didn't Berkeley Unix also include a Pascal compiler?
--
Steve
finger kargl@troutmask.apl.washington.edu
http://troutmask.apl.washington.edu/~clesceri/kargl.html
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Wed Jan 27 09:30:01 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id JAA13581
for freebsd-current-outgoing; Wed, 27 Jan 1999 09:30:01 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from vader.cs.berkeley.edu (vader.CS.Berkeley.EDU [128.32.38.234])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA13536
for <current@FreeBSD.ORG>; Wed, 27 Jan 1999 09:29:59 -0800 (PST)
(envelope-from asami@vader.cs.berkeley.edu)
Received: from silvia.hip.berkeley.edu (sji-ca13-237.ix.netcom.com [209.109.238.237]) by vader.cs.berkeley.edu (8.8.7/8.7.3) with ESMTP id JAA02143; Wed, 27 Jan 1999 09:29:49 -0800 (PST)
Received: (from asami@localhost) by silvia.hip.berkeley.edu (8.9.1/8.6.9) id JAA67196; Wed, 27 Jan 1999 09:29:38 -0800 (PST)
Date: Wed, 27 Jan 1999 09:29:38 -0800 (PST)
Message-Id: <199901271729.JAA67196@silvia.hip.berkeley.edu>
To: sgk@troutmask.apl.washington.edu
CC: gjohnson@nola.srrc.usda.gov, gljohns@bellsouth.net, current@FreeBSD.ORG,
obrien@NUXI.com
In-reply-to: <199901271718.JAA11594@troutmask.apl.washington.edu> (message
from Steve Kargl on Wed, 27 Jan 1999 09:18:49 -0800 (PST))
Subject: Re: removing f2c from base distribution
From: asami@FreeBSD.ORG (Satoshi Asami)
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
* The g77-0.5.19(.1) is *extremely* out-of-date. It should be dropped from
* the ports collection, and if someone wants to use g77, then they should
* install egcs.
*
* The newer versions of g77 do not work with gcc-2.7.2.x. The author of
* g77 states that you shouldn't even try to back port g77 to any version
* of gcc earlier than gcc-2.8
Well, Glenn said he got it to work with our compiler. :)
But anyway, I don't have any problem to delete the g77 port for now.
Is that ok with everyone else?
Satoshi
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Wed Jan 27 09:39:54 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id JAA14649
for freebsd-current-outgoing; Wed, 27 Jan 1999 09:39:54 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from schizo.cdsnet.net (schizo.cdsnet.net [204.118.244.32])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA14633;
Wed, 27 Jan 1999 09:39:43 -0800 (PST)
(envelope-from mrcpu@internetcds.com)
Received: from localhost (mrcpu@localhost) by schizo.cdsnet.net (8.8.8/8.7.3) with SMTP id JAA28004; Wed, 27 Jan 1999 09:34:51 -0800 (PST)
Date: Wed, 27 Jan 1999 09:34:51 -0800 (PST)
From: Jaye Mathisen <mrcpu@internetcds.com>
X-Sender: mrcpu@schizo.cdsnet.net
To: Poul-Henning Kamp <phk@FreeBSD.ORG>
cc: current@FreeBSD.ORG
Subject: Re: "JAIL" code headed for -current.
In-Reply-To: <29763.917434096@critter.freebsd.dk>
Message-ID: <Pine.NEB.3.95.990127093443.27570o-100000@schizo.cdsnet.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
Consider this interest.
On Wed, 27 Jan 1999, Poul-Henning Kamp wrote:
>
> I'm polishing up the "JAIL" code I wrote and readying it for -current.
>
> This code provides an optional strenthening of the chroot() jail
> as we know it, and will provide safe sandboxes for most practical
> uses.
>
> The biggest impact of this is a new argument to the suser() call
> all over the kernel:
>
> suser(NOJAIL, bla, bla);
> or
> suser(0, bla, bla);
>
> The NOJAIL option means that a jailed root fails the test.
>
> I will add this extra arg to suser() in the first commit.
>
> Each Jail can optionally be assigned one IP number, which they
> have access to. All connections to and from that jail will
> use that IP#.
>
> If there is interest, this code will be merged to 3.1 as well.
>
> This work was sponsored by: www.servetheweb.com
>
> --
> Poul-Henning Kamp FreeBSD coreteam member
> phk@FreeBSD.ORG "Real hackers run -current on their laptop."
> FreeBSD -- It will take a long time before progress goes too far!
>
> To Unsubscribe: send mail to majordomo@FreeBSD.org
> with "unsubscribe freebsd-current" in the body of the message
>
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Wed Jan 27 09:43:07 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id JAA14985
for freebsd-current-outgoing; Wed, 27 Jan 1999 09:43:07 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from ayukawa.aus.org (ayukawa.aus.org [199.166.246.1])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA14971
for <current@freebsd.org>; Wed, 27 Jan 1999 09:43:02 -0800 (PST)
(envelope-from lh@aus.org)
Received: from zer0.net (lh@zer0.net [199.166.246.189]) by ayukawa.aus.org (8.8.7/8.7.3) with ESMTP id MAA20727; Wed, 27 Jan 1999 12:16:04 -0500 (EST)
Message-Id: <199901271716.MAA20727@ayukawa.aus.org>
X-Mailer: XFMail 1.3-beta-042198 [p0] on FreeBSD
X-Priority: 3 (Normal)
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 8bit
MIME-Version: 1.0
In-Reply-To: <XFMail.990127180059.asmodai@wxs.nl>
Date: Wed, 27 Jan 1999 12:35:09 -0500 (EST)
Reply-To: lh@aus.org
From: Luke <lh@aus.org>
To: current@FreeBSD.ORG
Subject: RE: Netscape | Mozilla
Cc: FreeBSD Current <current@FreeBSD.ORG>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
> Also, anyone even bothered to file the communicator 4.5 binary?
Hopefully this helps [4.0-current -DNOSECURE -O2 -pipe]
Netscape: FreeBSD/i386 compact demand paged dynamically linked executable
This is 4.5b1 communicator, and locks up X often enough I dont use it.
netscape.bin: unknown pure executable
This is a 3.x version and doesnt lock up X but can't view alot of pages properly
It does crash occasionally , but just coredumps.
I have a 1990429 mozilla built but it was built on 3.0 and doesnt work very
well, I am trying to build a new one.
> Matt or others might want to slap me for being way off but afaik the VM
> stuff was tied with the swapping and not paging. So this would mean that
> the VM_STACK cannot be the problem.
what is this VM_STACK option?
---
E-Mail: Luke <lh@aus.org>
Sent by XFMail
----------------------------------
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Wed Jan 27 09:46:35 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id JAA15570
for freebsd-current-outgoing; Wed, 27 Jan 1999 09:46:35 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.95.76.54])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA15562;
Wed, 27 Jan 1999 09:46:34 -0800 (PST)
(envelope-from sgk@troutmask.apl.washington.edu)
Received: (from sgk@localhost)
by troutmask.apl.washington.edu (8.9.1/8.9.1) id JAA11749;
Wed, 27 Jan 1999 09:47:41 -0800 (PST)
(envelope-from sgk)
From: Steve Kargl <sgk@troutmask.apl.washington.edu>
Message-Id: <199901271747.JAA11749@troutmask.apl.washington.edu>
Subject: Re: removing f2c from base distribution
In-Reply-To: <199901271729.JAA67196@silvia.hip.berkeley.edu> from Satoshi Asami at "Jan 27, 1999 9:29:38 am"
To: asami@FreeBSD.ORG (Satoshi Asami)
Date: Wed, 27 Jan 1999 09:47:41 -0800 (PST)
Cc: gjohnson@nola.srrc.usda.gov, gljohns@bellsouth.net, current@FreeBSD.ORG,
obrien@NUXI.com
X-Mailer: ELM [version 2.4ME+ PL43 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
Satoshi Asami wrote:
> * The g77-0.5.19(.1) is *extremely* out-of-date. It should be dropped from
> * the ports collection, and if someone wants to use g77, then they should
> * install egcs.
> *
> * The newer versions of g77 do not work with gcc-2.7.2.x. The author of
> * g77 states that you shouldn't even try to back port g77 to any version
> * of gcc earlier than gcc-2.8
>
> Well, Glenn said he got it to work with our compiler. :)
Maybe I misunderstood, but I thought Glenn got g77-0.5.19 to
work with our gcc-2.7.x. g77 is now at version 0.5.24. Those
micro numbers are significant changes, and these represent over
a years work on g77.
finger -l fortran@delysid.gnu.org |more
>
> But anyway, I don't have any problem to delete the g77 port for now.
> Is that ok with everyone else?
>
> Satoshi
>
--
Steve
finger kargl@troutmask.apl.washington.edu
http://troutmask.apl.washington.edu/~clesceri/kargl.html
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Wed Jan 27 10:03:55 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id KAA17778
for freebsd-current-outgoing; Wed, 27 Jan 1999 10:03:55 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from vader.cs.berkeley.edu (vader.CS.Berkeley.EDU [128.32.38.234])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA17764
for <current@FreeBSD.ORG>; Wed, 27 Jan 1999 10:03:52 -0800 (PST)
(envelope-from asami@vader.cs.berkeley.edu)
Received: from silvia.hip.berkeley.edu (sji-ca13-237.ix.netcom.com [209.109.238.237]) by vader.cs.berkeley.edu (8.8.7/8.7.3) with ESMTP id KAA02193; Wed, 27 Jan 1999 10:02:07 -0800 (PST)
Received: (from asami@localhost) by silvia.hip.berkeley.edu (8.9.1/8.6.9) id KAA67378; Wed, 27 Jan 1999 10:02:01 -0800 (PST)
Date: Wed, 27 Jan 1999 10:02:01 -0800 (PST)
Message-Id: <199901271802.KAA67378@silvia.hip.berkeley.edu>
To: sgk@troutmask.apl.washington.edu
CC: gjohnson@nola.srrc.usda.gov, gljohns@bellsouth.net, current@FreeBSD.ORG,
obrien@NUXI.com
In-reply-to: <199901271747.JAA11749@troutmask.apl.washington.edu> (message
from Steve Kargl on Wed, 27 Jan 1999 09:47:41 -0800 (PST))
Subject: Re: removing f2c from base distribution
From: asami@FreeBSD.ORG (Satoshi Asami)
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
* Maybe I misunderstood, but I thought Glenn got g77-0.5.19 to
* work with our gcc-2.7.x. g77 is now at version 0.5.24. Those
* micro numbers are significant changes, and these represent over
* a years work on g77.
No, I misunderstood. So Glenn got 0.5.19 to work, but it's very old.
Anything newer than that (like the current 0.5.24) doesn't work with
gcc 2.7.x and the author says don't bother trying. I got it now.
Satoshi
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Wed Jan 27 10:09:24 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id KAA18473
for freebsd-current-outgoing; Wed, 27 Jan 1999 10:09:24 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA18467
for <freebsd-current@FreeBSD.ORG>; Wed, 27 Jan 1999 10:09:21 -0800 (PST)
(envelope-from phk@critter.freebsd.dk)
Received: from critter.freebsd.dk (localhost [127.0.0.1])
by critter.freebsd.dk (8.9.1/8.8.5) with ESMTP id TAA31049;
Wed, 27 Jan 1999 19:08:04 +0100 (CET)
To: "Daniel C. Sobral" <dcs@newsguy.com>
cc: Garrett Wollman <wollman@khavrinen.lcs.mit.edu>,
freebsd-current@FreeBSD.ORG
Subject: Re: removing f2c from base distribution
In-reply-to: Your message of "Thu, 28 Jan 1999 02:13:44 +0900."
<36AF4948.D0F88A52@newsguy.com>
Date: Wed, 27 Jan 1999 19:08:03 +0100
Message-ID: <31047.917460483@critter.freebsd.dk>
From: Poul-Henning Kamp <phk@critter.freebsd.dk>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
In message <36AF4948.D0F88A52@newsguy.com>, "Daniel C. Sobral" writes:
>Garrett Wollman wrote:
>>
>> <<On Wed, 27 Jan 1999 20:44:33 +0900, "Daniel C. Sobral" <dcs@newsguy.com> said:
>>
>> > A lot of people use a lot of things out of ports. Why should Fortran
>> > be different?
>>
>> Because Berkeley Unix has /always/ included a FORTRAN compiler.
>
>Somehow I feared you might have said that... :-)
>
Yes, it was impolite to point out a mistake like that in public...
Poul-Henning "Just because Berkeley always did it that way doesn't mean
it is the right way" Kamp
--
Poul-Henning Kamp FreeBSD coreteam member
phk@FreeBSD.ORG "Real hackers run -current on their laptop."
FreeBSD -- It will take a long time before progress goes too far!
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Wed Jan 27 10:17:15 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id KAA19321
for freebsd-current-outgoing; Wed, 27 Jan 1999 10:17:15 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from jason05.u.washington.edu (jason05.u.washington.edu [140.142.78.6])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA19316
for <current@FreeBSD.ORG>; Wed, 27 Jan 1999 10:17:14 -0800 (PST)
(envelope-from jcwells@u.washington.edu)
Received: from saul5.u.washington.edu (root@saul5.u.washington.edu [140.142.83.3])
by jason05.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id KAA46866;
Wed, 27 Jan 1999 10:17:10 -0800
Received: from S8-37-26.student.washington.edu (S8-37-26.student.washington.edu [128.208.37.26])
by saul5.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id KAA13862;
Wed, 27 Jan 1999 10:17:09 -0800 (PST)
Date: Wed, 27 Jan 1999 18:16:32 +0000 (GMT)
From: "Jason C. Wells" <jcwells@u.washington.edu>
X-Sender: jason@s8-37-26.student.washington.edu
Reply-To: "Jason C. Wells" <jcwells@u.washington.edu>
To: "Steve O'Hara-Smith" <steveo@iol.ie>
cc: Jeroen Ruigrok/Asmodai <asmodai@wxs.nl>,
FreeBSD Current <current@FreeBSD.ORG>
Subject: RE: Netscape | Mozilla
In-Reply-To: <XFMail.990127170536.steveo@iol.ie>
Message-ID: <Pine.BSF.4.05.9901271815420.4709-100000@s8-37-26.student.washington.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
On Wed, 27 Jan 1999, Steve O'Hara-Smith wrote:
> This I can answer - all versions of netscape are aout, (I've
>just been looking for an elf netscape so that I can throw away my aout
>libraries which are being carried around only for netscape nowadays).
I wrote a port for Linux Netscape if anyone wants it. I sent it in but it
came back to me with some comments about netscape port proliferation.
Catchya Later, | Give me UNIX or give me a typewriter.
Jason Wells | http://www.freebsd.org/
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Wed Jan 27 10:18:20 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id KAA19442
for freebsd-current-outgoing; Wed, 27 Jan 1999 10:18:20 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from jason05.u.washington.edu (jason05.u.washington.edu [140.142.78.6])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA19437
for <current@FreeBSD.ORG>; Wed, 27 Jan 1999 10:18:19 -0800 (PST)
(envelope-from jcwells@u.washington.edu)
Received: from saul9.u.washington.edu (root@saul9.u.washington.edu [140.142.82.7])
by jason05.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id KAA25242;
Wed, 27 Jan 1999 10:18:18 -0800
Received: from S8-37-26.student.washington.edu (S8-37-26.student.washington.edu [128.208.37.26])
by saul9.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id KAA28871;
Wed, 27 Jan 1999 10:18:17 -0800 (PST)
Date: Wed, 27 Jan 1999 18:17:40 +0000 (GMT)
From: "Jason C. Wells" <jcwells@u.washington.edu>
X-Sender: jason@s8-37-26.student.washington.edu
Reply-To: "Jason C. Wells" <jcwells@u.washington.edu>
To: "Steve O'Hara-Smith" <steveo@iol.ie>
cc: Jeroen Ruigrok/Asmodai <asmodai@wxs.nl>,
FreeBSD Current <current@FreeBSD.ORG>
Subject: RE: Netscape | Mozilla
In-Reply-To: <Pine.BSF.4.05.9901271815420.4709-100000@s8-37-26.student.washington.edu>
Message-ID: <Pine.BSF.4.05.9901271817180.5076-100000@s8-37-26.student.washington.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
On Wed, 27 Jan 1999, Jason C. Wells wrote:
>On Wed, 27 Jan 1999, Steve O'Hara-Smith wrote:
>
>> This I can answer - all versions of netscape are aout, (I've
>>just been looking for an elf netscape so that I can throw away my aout
>>libraries which are being carried around only for netscape nowadays).
>
>I wrote a port for Linux Netscape if anyone wants it. I sent it in but it
>came back to me with some comments about netscape port proliferation.
Errrrr Linux-Netscape 4.5 that is.
Catchya Later, | Give me UNIX or give me a typewriter.
Jason Wells | http://www.freebsd.org/
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Wed Jan 27 10:20:23 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id KAA19691
for freebsd-current-outgoing; Wed, 27 Jan 1999 10:20:23 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from symbion.srrc.usda.gov (symbion.srrc.usda.gov [199.133.86.40])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA19680;
Wed, 27 Jan 1999 10:20:18 -0800 (PST)
(envelope-from gjohnson@nola.srrc.usda.gov)
Received: (from glenn@localhost)
by symbion.srrc.usda.gov (8.9.2/8.9.2) id MAA17826;
Wed, 27 Jan 1999 12:20:08 -0600 (CST)
(envelope-from glenn)
From: Glenn Johnson <gjohnson@nola.srrc.usda.gov>
Date: Wed, 27 Jan 1999 12:20:08 -0600
To: Satoshi Asami <asami@FreeBSD.ORG>
Cc: sgk@troutmask.apl.washington.edu, current@FreeBSD.ORG, obrien@NUXI.com
Subject: Re: removing f2c from base distribution
Message-ID: <19990127122008.A17603@symbion.srrc.usda.gov>
References: <199901271718.JAA11594@troutmask.apl.washington.edu> <199901271729.JAA67196@silvia.hip.berkeley.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.95.1i
In-Reply-To: <199901271729.JAA67196@silvia.hip.berkeley.edu>; from Satoshi Asami on Wed, Jan 27, 1999 at 09:29:38AM -0800
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
On Wed, Jan 27, 1999 at 09:29:38AM -0800, Satoshi Asami wrote:
> * The g77-0.5.19(.1) is *extremely* out-of-date. It should be dropped from
> * the ports collection, and if someone wants to use g77, then they should
> * install egcs.
> *
> * The newer versions of g77 do not work with gcc-2.7.2.x. The author of
> * g77 states that you shouldn't even try to back port g77 to any version
> * of gcc earlier than gcc-2.8
>
> Well, Glenn said he got it to work with our compiler. :)
No, I said I had a port of g77 0.5.19 that built against gcc
2.7.2.1. This was a while back. I am currently using g77 0.5.24, which
needs gcc 2.8.
Getting g77 from egcs is the best option right now. However, it seems to
me that this adds a lot of bloat (duplication of C, C++, etc.) to the
system for someone wanting to use FreeBSD as a scientific workstation
platform. In contrast, how much bloat is added to the base system by
having a g77 binary and a couple of libraries?
>
> But anyway, I don't have any problem to delete the g77 port for now.
> Is that ok with everyone else?
>
This is OK by me.
--
Glenn Johnson
Technician
USDA, ARS, SRRC
New Orleans, LA
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Wed Jan 27 10:40:29 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id KAA22002
for freebsd-current-outgoing; Wed, 27 Jan 1999 10:40:29 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA21994
for <current@freebsd.org>; Wed, 27 Jan 1999 10:40:28 -0800 (PST)
(envelope-from dillon@apollo.backplane.com)
Received: (from dillon@localhost)
by apollo.backplane.com (8.9.2/8.9.1) id KAA46853;
Wed, 27 Jan 1999 10:40:27 -0800 (PST)
(envelope-from dillon)
Date: Wed, 27 Jan 1999 10:40:27 -0800 (PST)
From: Matthew Dillon <dillon@apollo.backplane.com>
Message-Id: <199901271840.KAA46853@apollo.backplane.com>
To: current@FreeBSD.ORG
Subject: -Wall going into kernel today
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
I am doing commits for all cleanup required to turn on -Wall and
-Wcast-qual, and will then turn on -Wall and -Wcast-qual ( and also get
rid of the extra -W options that -Wall inherently includes ). I'm
also cleaning up the LINT compile, there are a couple of failures
in the usb code, pci/intpm.c, pci/pcisupport.c, and so forth.
-Matt
Matthew Dillon
<dillon@backplane.com>
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Wed Jan 27 10:44:45 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id KAA22538
for freebsd-current-outgoing; Wed, 27 Jan 1999 10:44:45 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from cogsci.ed.ac.uk (stevenson144.cogsci.ed.ac.uk [129.215.144.1])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA22529
for <freebsd-current@FreeBSD.ORG>; Wed, 27 Jan 1999 10:44:35 -0800 (PST)
(envelope-from richard@cogsci.ed.ac.uk)
Received: (from richard@localhost)
by cogsci.ed.ac.uk (8.8.7/8.8.7) id SAA17130;
Wed, 27 Jan 1999 18:44:13 GMT
Date: Wed, 27 Jan 1999 18:44:13 GMT
Message-Id: <199901271844.SAA17130@cogsci.ed.ac.uk>
From: Richard Tobin <richard@cogsci.ed.ac.uk>
Subject: Re: removing f2c from base distribution
To: Garrett Wollman <wollman@khavrinen.lcs.mit.edu>
In-Reply-To: Garrett Wollman's message of Wed, 27 Jan 1999 11:23:56 -0500 (EST)
Organization: just say no
Cc: freebsd-current@FreeBSD.ORG
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
> Because Berkeley Unix has /always/ included a FORTRAN compiler.
Maybe we should put Franz Lisp back in.
bash-2.02$ uname -sr
FreeBSD 3.0-RELEASE
bash-2.02$ lisp
Franz Lisp, Opus 38.92
->
-- Richard
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Wed Jan 27 11:05:13 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id LAA25397
for freebsd-current-outgoing; Wed, 27 Jan 1999 11:05:13 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from pinhead.parag.codegen.com (ppp-sfx201--058.sirius.net [205.134.235.58])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA25369
for <current@FreeBSD.ORG>; Wed, 27 Jan 1999 11:05:09 -0800 (PST)
(envelope-from parag@cgt.com)
Received: from pinhead.parag.codegen.com (localhost.parag.codegen.com [127.0.0.1])
by pinhead.parag.codegen.com (8.9.2/8.8.8) with ESMTP id LAA17774;
Wed, 27 Jan 1999 11:04:22 -0800 (PST)
(envelope-from parag@pinhead.parag.codegen.com)
Message-Id: <199901271904.LAA17774@pinhead.parag.codegen.com>
X-Mailer: exmh version 2.0.2 2/24/98
To: Brian Feldman <green@unixhelp.org>
cc: "Richard Seaman, Jr." <dick@tar.com>, Sheldon Hearn <axl@iafrica.com>,
Jeroen Ruigrok/Asmodai <asmodai@wxs.nl>,
Andrew Gordon <arg@arg1.demon.co.uk>, current@FreeBSD.ORG,
Matthew Dillon <dillon@apollo.backplane.com>
Subject: Re: 4.0-Current, netscape halts system
In-Reply-To: Message from Brian Feldman <green@unixhelp.org>
of "Wed, 27 Jan 1999 11:07:43 EST." <Pine.BSF.4.05.9901271104160.4181-100000@janus.syracuse.net>
X-Face: =O'Kj74icvU|oS*<7gS/8'\Pbpm}okVj*@UC!IgkmZQAO!W[|iBiMs*|)n*`X
]pW%m>Oz_mK^Gdazsr.Z0/JsFS1uF8gBVIoChGwOy{EK=<6g?aHE`[\S]C]T0Wm
X-URL: http://www.codegen.com
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Wed, 27 Jan 1999 11:04:22 -0800
From: Parag Patel <parag@cgt.com>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
Just another data point. I just updated my 2xPII/300 system to
4.0-CURRENT last night (Tues Jan 26), and I'm running Netscape 4.5 just
fine - no crashes od any odd behavior at all. VM_STACK is defined, I
have 256Mb RAM, and 256Mb swap (which is currently untouched since the
reboot) striped across 2 disks. A make -j8 buildworld also succeeded
early this morning at about 5am. Softupdates is turned on for all
disks and all partitions except /tmp which is async mfs.
-- Parag Patel
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Wed Jan 27 11:20:45 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id LAA27146
for freebsd-current-outgoing; Wed, 27 Jan 1999 11:20:45 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from ayukawa.aus.org (ayukawa.aus.org [199.166.246.1])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA27134
for <current@FreeBSD.ORG>; Wed, 27 Jan 1999 11:20:41 -0800 (PST)
(envelope-from lh@aus.org)
Received: from zer0.net (lh@zer0.net [199.166.246.189]) by ayukawa.aus.org (8.8.7/8.7.3) with ESMTP id OAA22237; Wed, 27 Jan 1999 14:01:26 -0500 (EST)
Message-Id: <199901271901.OAA22237@ayukawa.aus.org>
X-Mailer: XFMail 1.3-beta-042198 [p0] on FreeBSD
X-Priority: 3 (Normal)
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 8bit
MIME-Version: 1.0
In-Reply-To: <Pine.BSF.4.05.9901271815420.4709-100000@s8-37-26.student.washington.edu>
Date: Wed, 27 Jan 1999 14:20:32 -0500 (EST)
Reply-To: lh@aus.org
From: Luke <lh@aus.org>
To: "Jason C. Wells" <jcwells@u.washington.edu>
Subject: RE: Netscape | Mozilla
Cc: FreeBSD Current <current@FreeBSD.ORG>,
"Steve O'Hara-Smith" <steveo@iol.ie>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
> I wrote a port for Linux Netscape if anyone wants it. I sent it in but it
> came back to me with some comments about netscape port proliferation.
I tried that one but it wants linux_lib installed on /compat and theres
no room. Do you know if its ok to make /compat a link to somewhere else for the
linux_lib port. [why does it install into / anyways]
---
E-Mail: Luke <lh@aus.org>
Sent by XFMail
----------------------------------
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Wed Jan 27 11:23:42 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id LAA27434
for freebsd-current-outgoing; Wed, 27 Jan 1999 11:23:42 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from ns.tar.com (ns.tar.com [204.95.187.2])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA27429
for <current@FreeBSD.ORG>; Wed, 27 Jan 1999 11:23:40 -0800 (PST)
(envelope-from dick@ns.tar.com)
Received: (from dick@localhost)
by ns.tar.com (8.9.2/8.9.1) id NAA27234;
Wed, 27 Jan 1999 13:23:34 -0600 (CST)
(envelope-from dick)
Date: Wed, 27 Jan 1999 13:23:34 -0600
From: "Richard Seaman, Jr." <dick@tar.com>
To: Parag Patel <parag@cgt.com>
Cc: current@FreeBSD.ORG
Subject: Re: 4.0-Current, netscape halts system
Message-ID: <19990127132334.F421@tar.com>
References: <green@unixhelp.org> <199901271904.LAA17774@pinhead.parag.codegen.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.95i
In-Reply-To: <199901271904.LAA17774@pinhead.parag.codegen.com>; from Parag Patel on Wed, Jan 27, 1999 at 11:04:22AM -0800
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
On Wed, Jan 27, 1999 at 11:04:22AM -0800, Parag Patel wrote:
>
> Just another data point. I just updated my 2xPII/300 system to
> 4.0-CURRENT last night (Tues Jan 26), and I'm running Netscape 4.5 just
> fine - no crashes od any odd behavior at all. VM_STACK is defined, I
> have 256Mb RAM, and 256Mb swap (which is currently untouched since the
> reboot) striped across 2 disks. A make -j8 buildworld also succeeded
> early this morning at about 5am. Softupdates is turned on for all
> disks and all partitions except /tmp which is async mfs.
In private mail, Brian Feldman has indicated his problem was NOT
the VM_STACK option, but was another configuration problem that
he since fixed.
--
Richard Seamman, Jr. email: dick@tar.com
5182 N. Maple Lane phone: 414-367-5450
Chenequa WI 53058 fax: 414-367-5852
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Wed Jan 27 11:26:41 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id LAA27828
for freebsd-current-outgoing; Wed, 27 Jan 1999 11:26:41 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from janus.syracuse.net (janus.syracuse.net [205.232.47.15])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA27794
for <current@FreeBSD.ORG>; Wed, 27 Jan 1999 11:26:35 -0800 (PST)
(envelope-from green@unixhelp.org)
Received: from localhost (green@localhost)
by janus.syracuse.net (8.8.8/8.8.7) with ESMTP id OAA15673;
Wed, 27 Jan 1999 14:26:19 -0500 (EST)
Date: Wed, 27 Jan 1999 14:26:19 -0500 (EST)
From: Brian Feldman <green@unixhelp.org>
X-Sender: green@janus.syracuse.net
To: Luke <lh@aus.org>
cc: "Jason C. Wells" <jcwells@u.washington.edu>,
FreeBSD Current <current@FreeBSD.ORG>,
"Steve O'Hara-Smith" <steveo@iol.ie>
Subject: RE: Netscape | Mozilla
In-Reply-To: <199901271901.OAA22237@ayukawa.aus.org>
Message-ID: <Pine.BSF.4.05.9901271425490.15027-100000@janus.syracuse.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
On Wed, 27 Jan 1999, Luke wrote:
> > I wrote a port for Linux Netscape if anyone wants it. I sent it in but it
> > came back to me with some comments about netscape port proliferation.
>
> I tried that one but it wants linux_lib installed on /compat and theres
> no room. Do you know if its ok to make /compat a link to somewhere else for the
> linux_lib port. [why does it install into / anyways]
Yep, it's alright! I've been doing that for many months. It's installed into /
because it's a "core"ish thing.
> ---
>
> E-Mail: Luke <lh@aus.org>
> Sent by XFMail
> ----------------------------------
>
> To Unsubscribe: send mail to majordomo@FreeBSD.org
> with "unsubscribe freebsd-current" in the body of the message
>
Brian Feldman _ __ ___ ___ ___
green@unixhelp.org _ __ ___ | _ ) __| \
http://www.freebsd.org/ _ __ ___ ____ | _ \__ \ |) |
FreeBSD: The Power to Serve! _ __ ___ ____ _____ |___/___/___/
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Wed Jan 27 11:26:58 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id LAA27884
for freebsd-current-outgoing; Wed, 27 Jan 1999 11:26:58 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from ns.tar.com (ns.tar.com [204.95.187.2])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA27879
for <current@FreeBSD.ORG>; Wed, 27 Jan 1999 11:26:56 -0800 (PST)
(envelope-from dick@ns.tar.com)
Received: (from dick@localhost)
by ns.tar.com (8.9.2/8.9.1) id NAA27262;
Wed, 27 Jan 1999 13:26:50 -0600 (CST)
(envelope-from dick)
Date: Wed, 27 Jan 1999 13:26:50 -0600
From: "Richard Seaman, Jr." <dick@tar.com>
To: Luke <lh@aus.org>
Cc: FreeBSD Current <current@FreeBSD.ORG>
Subject: Re: Netscape | Mozilla
Message-ID: <19990127132650.G421@tar.com>
References: <Pine.BSF.4.05.9901271815420.4709-100000@s8-37-26.student.washington.edu> <199901271901.OAA22237@ayukawa.aus.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.95i
In-Reply-To: <199901271901.OAA22237@ayukawa.aus.org>; from Luke on Wed, Jan 27, 1999 at 02:20:32PM -0500
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
On Wed, Jan 27, 1999 at 02:20:32PM -0500, Luke wrote:
> I tried that one but it wants linux_lib installed on /compat and theres
> no room. Do you know if its ok to make /compat a link to somewhere else for the
> linux_lib port. [why does it install into / anyways]
I have /compat symlinked to another partition. As long as its mounted
before you need anything in /compat you should be fine. At least here,
thats no problem, and I turn on linux in /etc/rc.conf.
--
Richard Seamman, Jr. email: dick@tar.com
5182 N. Maple Lane phone: 414-367-5450
Chenequa WI 53058 fax: 414-367-5852
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Wed Jan 27 11:36:53 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id LAA29347
for freebsd-current-outgoing; Wed, 27 Jan 1999 11:36:53 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from mail2.leirianet.pt (vortex.leirianet.pt [195.23.92.20])
by hub.freebsd.org (8.8.8/8.8.8) with SMTP id LAA29339
for <freebsd-current@freebsd.org>; Wed, 27 Jan 1999 11:36:44 -0800 (PST)
(envelope-from mfer@leirianet.pt)
Received: (qmail 3486 invoked from network); 27 Jan 1999 19:36:40 -0000
Received: from unknown (HELO OSIRIS) (195.61.93.61)
by mail2.leirianet.pt with SMTP; 27 Jan 1999 19:36:40 -0000
From: M Ferreira <mfer@leirianet.pt>
To: freebsd-current@FreeBSD.ORG
Subject: Summary: Spontaneous system freeze
Date: Wed, 27 Jan 1999 19:35:56 GMT
Reply-To: M Ferreira <mfer@leirianet.pt>
Message-ID: <36b269dc.31591536@mail2.leirianet.pt>
X-Mailer: Forte Agent 1.5/32.451
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by hub.freebsd.org id LAA29343
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
After full hardware examination i discovered what was behind these
unexplainable crashes.
We're using a gigabyte ga-6bxds motherboard wich supports 2 pii
processors. We acquired the machine already assembled and (strangely)
running.
We're using only a single processor and our suplier naturally
installed it in CPU1 slot. This was the problem.
These boards require single-processor setups to use CPU2 slot, thus
the sudden freezes.
In the board booklet, this indication comes almost unnoticed. Gigabyte
should put more care in their docs.
M Ferreira
No dia Thu, 21 Jan 1999 19:40:17 GMT, escreveu o seguinte:
>I'm trying to get 3.0-RELEASE to run as stable as possible on a PII
>with aic7895 onboard scsi controller.
>
>my dmesg output is:
>
>Timecounter "i8254" frequency 1193182 Hz cost 3126 ns
>Timecounter "TSC" frequency 349069134 Hz cost 140 ns
>CPU: Pentium II (quarter-micron) (349.07-MHz 686-class CPU)
> Origin = "GenuineIntel" Id = 0x652 Stepping=2
>
>Features=0x183fbff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CM
>OV,PAT,PSE36,MMX,<b24>>
>real memory = 134217728 (131072K bytes)
>avail memory = 127844352 (124848K bytes)
>Probing for devices on PCI bus 0:
>chip0: <Intel 82443BX host to PCI bridge> rev 0x02 on pci0.0.0
>chip1: <Intel 82443BX host to AGP bridge> rev 0x02 on pci0.1.0
>chip2: <Intel 82371AB PCI to ISA bridge> rev 0x02 on pci0.7.0
>chip3: <Intel 82371AB USB host controller> rev 0x01 int d irq 11 on
>pci0.7.2
>chip4: <Intel 82371AB Power management controller> rev 0x02 on
>pci0.7.3
>vga0: <ATI model 4756 graphics accelerator> rev 0x3a int a irq 255 on
>pci0.8.0
>de0: <Digital 21140A Fast Ethernet> rev 0x20 int a irq 10 on pci0.10.0
>de0: 21140A [10-100Mb/s] pass 2.0
>de0: address 00:48:54:00:07:b1
>ahc0: <Adaptec aic7895 Ultra SCSI adapter> rev 0x04 int a irq 5 on
>pci0.12.0
>ahc0: aic7895 Wide Channel A, SCSI Id=7, 16/255 SCBs
>ahc1: <Adaptec aic7895 Ultra SCSI adapter> rev 0x04 int b irq 5 on
>pci0.12.1
>ahc1: Using left over BIOS settings
>ahc1: aic7895 Wide Channel B, SCSI Id=7, 16/255 SCBs
>Probing for devices on PCI bus 1:
>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 flags 0x10 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
>psm0 at 0x60-0x64 irq 12 on motherboard
>psm0: model Generic PS/2 mouse, device ID 0
>fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa
>fdc0: FIFO enabled, 8 bytes threshold
>fd0: 1.44MB 3.5in
>npx0 on motherboard
>npx0: INT 16 interface
>Waiting 15 seconds for SCSI devices to settle
>sa0 at ahc0 bus 0 target 5 lun 0
>sa0: <HP T20 3.00> Removable Sequential Access SCSI2 device
>sa0: 3.300MB/s transfers
>da4 at ahc1 bus 0 target 2 lun 0
>da4: <SEAGATE ST34520W 1444> Fixed Direct Access SCSI2 device
>da4: 40.0MB/s transfers (20.0MHz, offset 8, 16bit), Tagged Queueing
>Enabled
>da4: 4340MB (8888924 512 byte sectors: 64H 32S/T 4340C)
>da5 at ahc1 bus 0 target 3 lun 0
>da5: <SEAGATE ST34520W 1444> Fixed Direct Access SCSI2 device
>da5: 40.0MB/s transfers (20.0MHz, offset 8, 16bit), Tagged Queueing
>Enabled
>da5: 4340MB (8888924 512 byte sectors: 64H 32S/T 4340C)
>da0 at ahc0 bus 0 target 0 lun 0
>da0: <IBM DCAS-32160W S65A> Fixed Direct Access SCSI2 device
>da0: 40.0MB/s transfers (20.0MHz, offset 8, 16bit), Tagged Queueing
>Enabled
>da0: 2063MB (4226725 512 byte sectors: 255H 63S/T 263C)
>da1 at ahc0 bus 0 target 1 lun 0
>da1: <IBM DCAS-32160W S65A> Fixed Direct Access SCSI2 device
>da1: 40.0MB/s transfers (20.0MHz, offset 8, 16bit), Tagged Queueing
>Enabled
>da1: 2063MB (4226725 512 byte sectors: 255H 63S/T 263C)
>changing root device to da0s1a
>
>I'm having spontaneous freezes whenever I compile anything, be it a
>kernel build or a port install.
>
>Beeing more specific, it's a total system freeze. Nothing on the
>console (have DDB in the kernel), no response to pings, and total
>keyboard freeze.
>
>Can anyone shed any light on this?
>
>tia
>
>M Ferreira
>
>
>To Unsubscribe: send mail to majordomo@FreeBSD.org
>with "unsubscribe freebsd-questions" in the body of the message
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Wed Jan 27 11:38:32 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id LAA29470
for freebsd-current-outgoing; Wed, 27 Jan 1999 11:38:32 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from servo.ccr.org (servo.ccr.org [198.3.0.2])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA29462
for <freebsd-current@freebsd.org>; Wed, 27 Jan 1999 11:38:30 -0800 (PST)
(envelope-from mo@servo.ccr.org)
Received: from servo.ccr.org (localhost [127.0.0.1])
by servo.ccr.org (8.9.2/8.9.2) with ESMTP id OAA50778
for <freebsd-current@freebsd.org>; Wed, 27 Jan 1999 14:38:23 -0500 (EST)
(envelope-from mo@servo.ccr.org)
Message-Id: <199901271938.OAA50778@servo.ccr.org>
To: freebsd-current@FreeBSD.ORG
Subject: "Argument by Authority"
Date: Wed, 27 Jan 1999 14:38:23 -0500
From: "Mike O'Dell" <mo@servo.ccr.org>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
just for a calibration,
i asked Dennis Ritchie his opinion of "the right behavior"
his comment about posix might be the trump card, although
i'd like to see chapter and verse if that's the case.
for what it's worth.
-mo
------- Forwarded Message
MessageName: (Message 47)
From: dmr@plan9.bell-labs.com
Date: Wed, 27 Jan 1999 14:30:59 -0500
To: mo@servo.ccr.org
Well the research systems from v7 (just looked) through Brazil
produce no diagnostic. So much for "should."
Irix complains, suppressible with -f. I wonder if it's in posix?
Dennis
------- End of Forwarded Message
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Wed Jan 27 11:45:15 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id LAA00508
for freebsd-current-outgoing; Wed, 27 Jan 1999 11:45:15 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from kithrup.com (kithrup.com [205.179.156.40])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA00437
for <current@freebsd.org>; Wed, 27 Jan 1999 11:44:38 -0800 (PST)
(envelope-from sef@kithrup.com)
Received: (from sef@localhost)
by kithrup.com (8.8.8/8.8.8) id LAA15317;
Wed, 27 Jan 1999 11:44:35 -0800 (PST)
(envelope-from sef)
Date: Wed, 27 Jan 1999 11:44:35 -0800 (PST)
From: Sean Eric Fagan <sef@kithrup.com>
Message-Id: <199901271944.LAA15317@kithrup.com>
To: current@FreeBSD.ORG
Subject: Re: "JAIL" code headed for -current.
In-Reply-To: <29763.917434096.kithrup.freebsd.current@critter.freebsd.dk>
Organization: Kithrup Enterprises, Ltd.
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
In article <29763.917434096.kithrup.freebsd.current@critter.freebsd.dk> you write:
>The biggest impact of this is a new argument to the suser() call
>all over the kernel:
>
> suser(NOJAIL, bla, bla);
>or
> suser(0, bla, bla);
Oh, goody, more gratuitious incomaptibilities with everyone else.
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Wed Jan 27 11:47:14 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id LAA00717
for freebsd-current-outgoing; Wed, 27 Jan 1999 11:47:14 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from roma.coe.ufrj.br (roma.coe.ufrj.br [146.164.53.65])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA00689;
Wed, 27 Jan 1999 11:47:02 -0800 (PST)
(envelope-from jonny@jonny.eng.br)
Received: (from jonny@localhost)
by roma.coe.ufrj.br (8.8.8/8.8.8) id RAA28507;
Wed, 27 Jan 1999 17:46:45 -0200 (EDT)
(envelope-from jonny)
From: Joao Carlos Mendes Luis <jonny@jonny.eng.br>
Message-Id: <199901271946.RAA28507@roma.coe.ufrj.br>
Subject: Re: "JAIL" code headed for -current.
In-Reply-To: <29763.917434096@critter.freebsd.dk> from Poul-Henning Kamp at "Jan 27, 1999 11:48:16 am"
To: phk@FreeBSD.ORG (Poul-Henning Kamp)
Date: Wed, 27 Jan 1999 17:46:45 -0200 (EDT)
Cc: current@FreeBSD.ORG
X-Mailer: ELM [version 2.4ME+ PL43 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
#define quoting(Poul-Henning Kamp)
// I'm polishing up the "JAIL" code I wrote and readying it for -current.
//
// This code provides an optional strenthening of the chroot() jail
// as we know it, and will provide safe sandboxes for most practical
// uses.
//
// The biggest impact of this is a new argument to the suser() call
// all over the kernel:
//
// suser(NOJAIL, bla, bla);
// or
// suser(0, bla, bla);
//
// The NOJAIL option means that a jailed root fails the test.
Do you have a list of which tests will receive this option ?
// I will add this extra arg to suser() in the first commit.
//
// Each Jail can optionally be assigned one IP number, which they
// have access to. All connections to and from that jail will
// use that IP#.
This looks interesting. How would you specify the IP to use ?
Jonny
--
Joao Carlos Mendes Luis M.Sc. Student
jonny@jonny.eng.br Universidade Federal do Rio de Janeiro
"This .sig is not meant to be politically correct."
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Wed Jan 27 12:06:04 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id MAA03036
for freebsd-current-outgoing; Wed, 27 Jan 1999 12:06:04 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from khavrinen.lcs.mit.edu (khavrinen.lcs.mit.edu [18.24.4.193])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA03029
for <freebsd-current@FreeBSD.ORG>; Wed, 27 Jan 1999 12:06:02 -0800 (PST)
(envelope-from wollman@khavrinen.lcs.mit.edu)
Received: (from wollman@localhost)
by khavrinen.lcs.mit.edu (8.9.1/8.9.1) id PAA08973;
Wed, 27 Jan 1999 15:04:38 -0500 (EST)
(envelope-from wollman)
Date: Wed, 27 Jan 1999 15:04:38 -0500 (EST)
From: Garrett Wollman <wollman@khavrinen.lcs.mit.edu>
Message-Id: <199901272004.PAA08973@khavrinen.lcs.mit.edu>
To: "Mike O'Dell" <mo@servo.ccr.org>
Cc: freebsd-current@FreeBSD.ORG
Subject: "Argument by Authority"
In-Reply-To: <199901271938.OAA50778@servo.ccr.org>
References: <199901271938.OAA50778@servo.ccr.org>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
<<On Wed, 27 Jan 1999 14:38:23 -0500, "Mike O'Dell" <mo@servo.ccr.org> said:
> i asked Dennis Ritchie his opinion of "the right behavior"
The right behavior of what?
-GAWollman
--
Garrett A. Wollman | O Siem / We are all family / O Siem / We're all the same
wollman@lcs.mit.edu | O Siem / The fires of freedom
Opinions not those of| Dance in the burning flame
MIT, LCS, CRS, or NSA| - Susan Aglukark and Chad Irschick
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Wed Jan 27 12:19:56 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id MAA04807
for freebsd-current-outgoing; Wed, 27 Jan 1999 12:19:56 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from darkstar.psa.at (darkstar.psa.at [194.152.163.137])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA04790
for <current@freebsd.org>; Wed, 27 Jan 1999 12:19:48 -0800 (PST)
(envelope-from root@psa.at)
Received: from unet2-111.univie.ac.at ([131.130.232.111] helo=entropy.quake.at)
by darkstar.psa.at with esmtp (Exim 2.05 #1)
id 105bdc-0003mB-00; Wed, 27 Jan 1999 21:32:37 +0100
Received: from localhost ([127.0.0.1])
by entropy.quake.at with esmtp (Exim 2.10 #2)
id 105bOJ-000FQA-00; Wed, 27 Jan 1999 21:16:48 +0100
Date: Wed, 27 Jan 1999 21:16:47 +0100 (CET)
From: System administration <root@psa.at>
X-Sender: root@darkstar.vmx
To: Luke <lh@aus.org>
cc: "Jason C. Wells" <jcwells@u.washington.edu>,
FreeBSD Current <current@FreeBSD.ORG>,
"Steve O'Hara-Smith" <steveo@iol.ie>
Subject: RE: Netscape | Mozilla
In-Reply-To: <199901271901.OAA22237@ayukawa.aus.org>
Message-ID: <Pine.BSF.4.05.9901272114140.59256-100000@darkstar.vmx>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
On Wed, 27 Jan 1999, Luke wrote:
> I tried that one but it wants linux_lib installed on /compat and theres
> no room. Do you know if its ok to make /compat a link to somewhere else for the
> linux_lib port. [why does it install into / anyways]
Should not harm anything. I have linked /compat/linux to /home/linux
(home is on its own filesystem), since my / is quite limited
in space.
No problems (and I don't really know why it should cause any).
--
# /AS/ http://privat.schlund.de/entropy/ #
# XX has detected, that your mouse cursor has changed position. Please #
# restart XX, so it can be updated. -- From The Gimp manual #
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Wed Jan 27 12:25:35 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id MAA05635
for freebsd-current-outgoing; Wed, 27 Jan 1999 12:25:35 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from darkstar.psa.at (darkstar.psa.at [194.152.163.137])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA05624
for <current@freebsd.org>; Wed, 27 Jan 1999 12:25:31 -0800 (PST)
(envelope-from root@psa.at)
Received: from unet2-111.univie.ac.at ([131.130.232.111] helo=entropy.quake.at)
by darkstar.psa.at with esmtp (Exim 2.05 #1)
id 105bjh-0003mI-00; Wed, 27 Jan 1999 21:38:53 +0100
Received: from localhost ([127.0.0.1])
by entropy.quake.at with esmtp (Exim 2.10 #2)
id 105bUP-000FQL-00; Wed, 27 Jan 1999 21:23:05 +0100
Date: Wed, 27 Jan 1999 21:23:05 +0100 (CET)
From: System administration <root@psa.at>
X-Sender: root@darkstar.vmx
To: Brian Feldman <green@unixhelp.org>
cc: current@FreeBSD.ORG
Subject: Re: One answer, one question.
In-Reply-To: <Pine.BSF.4.05.9901270701510.23381-100000@janus.syracuse.net>
Message-ID: <Pine.BSF.4.05.9901272118340.59256-100000@darkstar.vmx>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
On Wed, 27 Jan 1999, Brian Feldman wrote:
> Now can someone help me out here, and figure out why:
> {"/home/green"}$ ps
> ps: bad namelist
> {"/home/green"}$ sysctl kern.bootfile
> kern.bootfile: /kernel
> {"/home/green"}$ l /var/db/kvm_kernel.db
> -rw-r--r-- 1 root wheel 1310720 Jan 27 00:53 /var/db/kvm_kernel.db
can't confirm this here. I have been using -DCOMPAT_LINUX_THREADS and
-DVM_STACK for a while and do not experience any X lockups or other
problems with communicator (4.5 final).
Also, ps works fine, but I did have similar problems with it a while
ago. I could fix them by recompiling libkvm first, followed by related
tools (ps, top, vmstat, [...]). At least, ps links statically with
libkvm so it really depends on an up-to-date kvm library.
--
# /AS/ http://privat.schlund.de/entropy/ #
# #
# XX has detected, that your mouse cursor has changed position. Please #
# restart XX, so it can be updated. -- From The Gimp manual #
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Wed Jan 27 12:29:21 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id MAA06163
for freebsd-current-outgoing; Wed, 27 Jan 1999 12:29:21 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from panzer.plutotech.com (panzer.plutotech.com [206.168.67.125])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA06150
for <current@FreeBSD.ORG>; Wed, 27 Jan 1999 12:29:18 -0800 (PST)
(envelope-from ken@panzer.plutotech.com)
Received: (from ken@localhost)
by panzer.plutotech.com (8.9.2/8.8.5) id NAA53089;
Wed, 27 Jan 1999 13:28:26 -0700 (MST)
From: "Kenneth D. Merry" <ken@plutotech.com>
Message-Id: <199901272028.NAA53089@panzer.plutotech.com>
Subject: Re: WD/ide_pci bug! [was Re: SOFTUPDATES hangs keyboard ]
In-Reply-To: <Pine.BSF.4.05.9901271206280.325-100000@megaweapon.zigg.com> from Matt Behrens at "Jan 27, 99 12:07:52 pm"
To: matt@zigg.com (Matt Behrens)
Date: Wed, 27 Jan 1999 13:28:26 -0700 (MST)
Cc: gnb@itga.com.au, dillon@apollo.backplane.com, mike@smith.net.au,
current@FreeBSD.ORG
X-Mailer: ELM [version 2.4ME+ PL28s (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
Matt Behrens wrote...
> Never mind. Apparently it went south on me while I was having
> lunch.
>
> I got this curious error when I paniced the debugger (paraphrased):
>
> HELP! busy_count is less then 0 (-1)
>
> Is this something of a clue? I've never been able to sync the
> drives at all by panicing, it can't communicate with the IDE
> controller for some reason. Lots of status 0x58's.
- That's not a fatal error.
- You didn't write down the whole message. (the whole message would have
told you what function generated the error message, and which
drive caused the problem)
- I think there still may be a bug in the devstat implementation in the wd
driver that causes the busy count to go negative sometimes.
Anyway, I wouldn't worry too much about it.
Ken
--
Kenneth Merry
ken@plutotech.com
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Wed Jan 27 12:45:40 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id MAA08015
for freebsd-current-outgoing; Wed, 27 Jan 1999 12:45:40 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from peedub.muc.de (newpc.muc.ditec.de [194.120.126.33])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA07995
for <freebsd-current@freebsd.org>; Wed, 27 Jan 1999 12:45:34 -0800 (PST)
(envelope-from garyj@peedub.muc.de)
Received: from peedub.muc.de (localhost [127.0.0.1]) by peedub.muc.de (8.9.2/8.6.9) with ESMTP id VAA36888 for <freebsd-current@freebsd.org>; Wed, 27 Jan 1999 21:24:32 +0100 (CET)
Message-Id: <199901272024.VAA36888@peedub.muc.de>
X-Mailer: exmh version 2.0.2 2/24/98
To: freebsd-current@FreeBSD.ORG
Subject: devstat and atapi-cd.c
From: Gary Jennejohn <garyj@muc.de>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Wed, 27 Jan 1999 21:24:32 +0100
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
Are there any plans to add devstat support to atapi-cd.c, a la scsi_cd.c ?
Is it even considered to be desirable ?
--------
Gary Jennejohn
Home - garyj@muc.de
Work - garyj@fkr.dec.com
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Wed Jan 27 12:47:59 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id MAA08328
for freebsd-current-outgoing; Wed, 27 Jan 1999 12:47:59 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from iclub.nsu.ru (iclub.nsu.ru [193.124.222.66])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA08253
for <freebsd-current@FreeBSD.org>; Wed, 27 Jan 1999 12:47:35 -0800 (PST)
(envelope-from semen@iclub.nsu.ru)
Received: from localhost (semen@localhost)
by iclub.nsu.ru (8.9.2/8.8.5) with SMTP id CAA49959
for <freebsd-current@FreeBSD.org>; Thu, 28 Jan 1999 02:46:28 +0600 (NS)
Date: Thu, 28 Jan 1999 02:46:28 +0600 (NS)
From: Ustimenko Semen <semen@iclub.nsu.ru>
To: freebsd-current@FreeBSD.ORG
Subject: About to commit NTFS driver
Message-ID: <Pine.BSF.3.96.990128024451.49866B-100000@iclub.nsu.ru>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
Hello!
Are there any disagrees with an idea to commit a NTFS
driver into current:
I can commit/maintain driver mentioned at
http://www.freebsd.org/projects/
Driver is readonly, specialy developed for freebsd,
supports most of NTFS's features.
Source is at http://iclub.nsu.ru/~semen/ntfs/
Thank you!
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Wed Jan 27 12:59:36 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id MAA09470
for freebsd-current-outgoing; Wed, 27 Jan 1999 12:59:36 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from servo.ccr.org (servo.ccr.org [198.3.0.2])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA09463
for <freebsd-current@FreeBSD.ORG>; Wed, 27 Jan 1999 12:59:34 -0800 (PST)
(envelope-from mo@servo.ccr.org)
Received: from servo.ccr.org (localhost [127.0.0.1])
by servo.ccr.org (8.9.2/8.9.2) with ESMTP id PAA50894;
Wed, 27 Jan 1999 15:59:13 -0500 (EST)
(envelope-from mo@servo.ccr.org)
Message-Id: <199901272059.PAA50894@servo.ccr.org>
To: Garrett Wollman <wollman@khavrinen.lcs.mit.edu>
cc: "Mike O'Dell" <mo@servo.ccr.org>, freebsd-current@FreeBSD.ORG
Subject: Re: "Argument by Authority"
In-reply-to: Your message of "Wed, 27 Jan 1999 15:04:38 EST."
<199901272004.PAA08973@khavrinen.lcs.mit.edu>
Date: Wed, 27 Jan 1999 15:59:13 -0500
From: "Mike O'Dell" <mo@servo.ccr.org>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
i asked his notion of the right behavior of "rm"
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Wed Jan 27 13:10:36 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id NAA10856
for freebsd-current-outgoing; Wed, 27 Jan 1999 13:10:36 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from panzer.plutotech.com (panzer.plutotech.com [206.168.67.125])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA10831
for <freebsd-current@FreeBSD.ORG>; Wed, 27 Jan 1999 13:10:32 -0800 (PST)
(envelope-from ken@panzer.plutotech.com)
Received: (from ken@localhost)
by panzer.plutotech.com (8.9.2/8.8.5) id OAA53490;
Wed, 27 Jan 1999 14:10:17 -0700 (MST)
From: "Kenneth D. Merry" <ken@plutotech.com>
Message-Id: <199901272110.OAA53490@panzer.plutotech.com>
Subject: Re: devstat and atapi-cd.c
In-Reply-To: <199901272024.VAA36888@peedub.muc.de> from Gary Jennejohn at "Jan 27, 99 09:24:32 pm"
To: garyj@muc.de (Gary Jennejohn)
Date: Wed, 27 Jan 1999 14:10:17 -0700 (MST)
Cc: freebsd-current@FreeBSD.ORG
X-Mailer: ELM [version 2.4ME+ PL28s (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
Gary Jennejohn wrote...
> Are there any plans to add devstat support to atapi-cd.c, a la scsi_cd.c ?
>
> Is it even considered to be desirable ?
I think it is desireable. I think the best person to do it is probably
Soren or someone else who is familar with the driver.
The thing you have to make sure of is that you have exactly one
devstat_start_transaction() call for each transaction that you send to the
device, and exactly one devstat_end_transaction() call for each transaction
you get back. That includes any error cases, as well as the "normal"
cases.
Ken
--
Kenneth Merry
ken@plutotech.com
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Wed Jan 27 13:18:36 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id NAA11654
for freebsd-current-outgoing; Wed, 27 Jan 1999 13:18:36 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from rover.village.org (rover.village.org [204.144.255.49])
by hub.freebsd.org (8.8.8/8.8.8) with SMTP id NAA11649
for <current@freebsd.org>; Wed, 27 Jan 1999 13:18:34 -0800 (PST)
(envelope-from imp@village.org)
Received: from harmony [10.0.0.6]
by rover.village.org with esmtp (Exim 1.71 #1)
id 105cM4-0004dO-00; Wed, 27 Jan 1999 14:18:32 -0700
Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.1/8.8.3) with ESMTP id OAA44214; Wed, 27 Jan 1999 14:17:32 -0700 (MST)
Message-Id: <199901272117.OAA44214@harmony.village.org>
To: Jeroen Ruigrok/Asmodai <asmodai@wxs.nl>
Subject: Re: $Id$
Cc: FreeBSD Current <current@FreeBSD.ORG>
In-reply-to: Your message of "Wed, 27 Jan 1999 16:19:53 +0100."
<XFMail.990127161953.asmodai@wxs.nl>
References: <XFMail.990127161953.asmodai@wxs.nl>
Date: Wed, 27 Jan 1999 14:17:32 -0700
From: Warner Losh <imp@village.org>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
In message <XFMail.990127161953.asmodai@wxs.nl> Jeroen Ruigrok/Asmodai writes:
: Why isn't the FreeBSD project using tags like $FreeBSD$ instead of the
: now-used $Id$?
The stuff was added to the tree, but was backed out because our CVS
support, at the time, wasn't up to snuff. I'd love to see this
change, but there are many other things that I'd like to see before
that.
Warner
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Wed Jan 27 13:23:53 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id NAA12342
for freebsd-current-outgoing; Wed, 27 Jan 1999 13:23:53 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA12335
for <current@FreeBSD.ORG>; Wed, 27 Jan 1999 13:23:52 -0800 (PST)
(envelope-from dillon@apollo.backplane.com)
Received: (from dillon@localhost)
by apollo.backplane.com (8.9.2/8.9.1) id NAA55283;
Wed, 27 Jan 1999 13:23:51 -0800 (PST)
(envelope-from dillon)
Date: Wed, 27 Jan 1999 13:23:51 -0800 (PST)
From: Matthew Dillon <dillon@apollo.backplane.com>
Message-Id: <199901272123.NAA55283@apollo.backplane.com>
To: current@FreeBSD.ORG
Subject: Doh: kern/kern_environment, getenv()
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
Boy, aren't we lucky that every kern_envp entry has an '='
sign! This turns into a NOP most of the time.
Fixed.
-Matt
char *
getenv(char *name)
{
char *cp, *ep;
int len;
for (cp = kern_envp; cp != NULL; cp = kernenv_next(cp)) {
for (ep = cp; (*ep != '=') && (*ep != 0); ep++)
;
len = ep - cp;
if (*ep = '=') <<<<<<<<<<<<<<<<<<<<<<< single '='
ep++;
if (!strncmp(name, cp, len))
return(ep);
}
return(NULL);
}
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Wed Jan 27 13:24:43 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id NAA12626
for freebsd-current-outgoing; Wed, 27 Jan 1999 13:24:43 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from whistle.com (s205m131.whistle.com [207.76.205.131])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA12619
for <current@FreeBSD.ORG>; Wed, 27 Jan 1999 13:24:42 -0800 (PST)
(envelope-from archie@whistle.com)
Received: (from smap@localhost) by whistle.com (8.7.5/8.6.12) id NAA21448; Wed, 27 Jan 1999 13:24:30 -0800 (PST)
Received: from bubba.whistle.com( 207.76.205.7) by whistle.com via smap (V2.0)
id xma021442; Wed, 27 Jan 99 13:24:01 -0800
Received: (from archie@localhost) by bubba.whistle.com (8.8.7/8.6.12) id NAA15248; Wed, 27 Jan 1999 13:24:01 -0800 (PST)
From: Archie Cobbs <archie@whistle.com>
Message-Id: <199901272124.NAA15248@bubba.whistle.com>
Subject: Re: DEVFS, the time has come...
In-Reply-To: <Pine.BSF.4.01.9901271341260.95594-100000@herring.nlsystems.com> from Doug Rabson at "Jan 27, 99 01:56:01 pm"
To: dfr@nlsystems.com (Doug Rabson)
Date: Wed, 27 Jan 1999 13:24:01 -0800 (PST)
Cc: current@FreeBSD.ORG
X-Mailer: ELM [version 2.4ME+ PL38 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
Doug Rabson writes:
> And another thing. Why can't we use a non-driver-specific name for the
> disk? Most users simply don't care whether the driver was fd, wfd, wd or
> anything. They just want to get to their files without any fuss.
I agree.. and same thing goes for Ethernet drivers. I actually
like the way Linux always has "eth0", "eth1", ... (which we could
do using netgraph, with some work).
-Archie
___________________________________________________________________________
Archie Cobbs * Whistle Communications, Inc. * http://www.whistle.com
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Wed Jan 27 13:28:53 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id NAA12990
for freebsd-current-outgoing; Wed, 27 Jan 1999 13:28:53 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA12983
for <current@FreeBSD.ORG>; Wed, 27 Jan 1999 13:28:50 -0800 (PST)
(envelope-from dillon@apollo.backplane.com)
Received: (from dillon@localhost)
by apollo.backplane.com (8.9.2/8.9.1) id NAA56542;
Wed, 27 Jan 1999 13:28:49 -0800 (PST)
(envelope-from dillon)
Date: Wed, 27 Jan 1999 13:28:49 -0800 (PST)
From: Matthew Dillon <dillon@apollo.backplane.com>
Message-Id: <199901272128.NAA56542@apollo.backplane.com>
To: current@FreeBSD.ORG
Subject: btokup() macro in sys/malloc.h
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
Is this parenthesization correct ?
OLD
#define btokup(addr) (&kmemusage[(caddr_t)(addr) - kmembase >> PAGE_SHIFT])
NEW
#define btokup(addr) (&kmemusage[((caddr_t)(addr) - kmembase) >> PAGE_SHIFT])
-Matt
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Wed Jan 27 13:35:11 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id NAA13852
for freebsd-current-outgoing; Wed, 27 Jan 1999 13:35:11 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA13838
for <current@FreeBSD.ORG>; Wed, 27 Jan 1999 13:35:08 -0800 (PST)
(envelope-from dillon@apollo.backplane.com)
Received: (from dillon@localhost)
by apollo.backplane.com (8.9.2/8.9.1) id NAA57832;
Wed, 27 Jan 1999 13:35:08 -0800 (PST)
(envelope-from dillon)
Date: Wed, 27 Jan 1999 13:35:08 -0800 (PST)
From: Matthew Dillon <dillon@apollo.backplane.com>
Message-Id: <199901272135.NAA57832@apollo.backplane.com>
To: current@FreeBSD.ORG
Subject: kern/subr_scanf array index of signed char
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
BZZZZZZZZZZZzzzzzzzzzzztttttt! Houston, we have a problem!
Fixed.
-Matt
Matthew Dillon
<dillon@backplane.com>
@@ -323,7 +323,7 @@
/* take only those things in the class */
if (flags & SUPPRESS) {
n = 0;
- while (ccltab[*inp]) {
+ while (ccltab[(int)(unsigned char)*inp]) {
n++, inr--, inp++;
if (--width == 0)
break;
@@ -337,7 +337,7 @@
goto match_failure;
} else {
p0 = p = va_arg(ap, char *);
- while (ccltab[*inp]) {
+ while (ccltab[(int)(unsigned char)*inp]) {
inr--;
*p++ = *inp++;
if (--width == 0)
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Wed Jan 27 13:57:53 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id NAA16934
for freebsd-current-outgoing; Wed, 27 Jan 1999 13:57:53 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from h24-64-221-247.gv.wave.shaw.ca (h24-64-221-247.gv.wave.shaw.ca [24.64.221.247])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA16928
for <current@freebsd.org>; Wed, 27 Jan 1999 13:57:51 -0800 (PST)
(envelope-from jake@h24-64-221-247.gv.wave.shaw.ca)
Received: from h24-64-221-247.gv.wave.shaw.ca (localhost [127.0.0.1])
by h24-64-221-247.gv.wave.shaw.ca (8.9.2/8.9.2) with ESMTP id NAA73197
for <current@freebsd.org>; Wed, 27 Jan 1999 13:57:44 -0800 (PST)
(envelope-from jake@h24-64-221-247.gv.wave.shaw.ca)
Message-Id: <199901272157.NAA73197@h24-64-221-247.gv.wave.shaw.ca>
X-Mailer: exmh version 2.0.2 2/24/98
To: current@FreeBSD.ORG
Subject: Re: Netscape | Mozilla
In-reply-to: Your message of "Wed, 27 Jan 1999 14:26:19 EST."
<Pine.BSF.4.05.9901271425490.15027-100000@janus.syracuse.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Wed, 27 Jan 1999 13:57:44 -0800
From: Jake <jake@checker.org>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
> Should not harm anything. I have linked /compat/linux to /home/linux
> (home is on its own filesystem), since my / is quite limited
> in space.
>
> No problems (and I don't really know why it should cause any).
h24-64-221-247# ls -al /compat
lrwxr-xr-x 1 root wheel 11 Oct 22 05:47 /compat -> /usr/compat
h24-64-221-247#
I thought this was automatic, like /home ?
I'm pretty sure I've had to do it by hand in the past, but maybe six months
ago
I started over with some 3.0-SNAP, expected to have to go make that link,
and found it was already there. go figure.
I may, of course, be completely out to lunch.
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Wed Jan 27 14:01:24 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id OAA17426
for freebsd-current-outgoing; Wed, 27 Jan 1999 14:01:24 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA17411
for <current@FreeBSD.ORG>; Wed, 27 Jan 1999 14:01:19 -0800 (PST)
(envelope-from dillon@apollo.backplane.com)
Received: (from dillon@localhost)
by apollo.backplane.com (8.9.2/8.9.1) id OAA61764;
Wed, 27 Jan 1999 14:01:18 -0800 (PST)
(envelope-from dillon)
Date: Wed, 27 Jan 1999 14:01:18 -0800 (PST)
From: Matthew Dillon <dillon@apollo.backplane.com>
Message-Id: <199901272201.OAA61764@apollo.backplane.com>
to: current@FreeBSD.ORG
Subject: bug in devfs_strategy() ???
References: <199901272135.NAA57832@apollo.backplane.com>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
Aren't there are few BREAK statements missing from this ?
-Matt
Matthew Dillon
<dillon@backplane.com>
static int
devfs_strategy(struct vop_strategy_args *ap)
{
...
switch (ap->a_vp->v_type) {
case VCHR:
(*dnp->by.Cdev.cdevsw->d_strategy)(bp);
case VBLK:
(*dnp->by.Bdev.bdevsw->d_strategy)(bp);
}
return (0);
}
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Wed Jan 27 14:15:13 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id OAA18962
for freebsd-current-outgoing; Wed, 27 Jan 1999 14:15:13 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA18957
for <current@FreeBSD.ORG>; Wed, 27 Jan 1999 14:15:12 -0800 (PST)
(envelope-from dillon@apollo.backplane.com)
Received: (from dillon@localhost)
by apollo.backplane.com (8.9.2/8.9.1) id OAA63874;
Wed, 27 Jan 1999 14:15:11 -0800 (PST)
(envelope-from dillon)
Date: Wed, 27 Jan 1999 14:15:11 -0800 (PST)
From: Matthew Dillon <dillon@apollo.backplane.com>
Message-Id: <199901272215.OAA63874@apollo.backplane.com>
To: current@FreeBSD.ORG
Subject: bug in netatm/atm_cm.c ?
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
around line 2192. Shouldn't this be ap->aal.type == ATM_AAL5 ???
/*
* AAL
*/
if (ap->aal.type = ATM_AAL5) {
struct t_atm_aal5 *ap5, *cv5;
ap5 = &ap->aal.v.aal5;
cv5 = &cvp->cvc_attr.aal.v.aal5;
-Matt
Matthew Dillon
<dillon@backplane.com>
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Wed Jan 27 14:28:22 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id OAA20732
for freebsd-current-outgoing; Wed, 27 Jan 1999 14:28:22 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from ns.tar.com (ns.tar.com [204.95.187.2])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA20721
for <current@FreeBSD.ORG>; Wed, 27 Jan 1999 14:28:19 -0800 (PST)
(envelope-from dick@ns.tar.com)
Received: (from dick@localhost)
by ns.tar.com (8.9.2/8.9.1) id QAA31454;
Wed, 27 Jan 1999 16:28:14 -0600 (CST)
(envelope-from dick)
Date: Wed, 27 Jan 1999 16:28:14 -0600
From: "Richard Seaman, Jr." <dick@tar.com>
To: Luke <lh@aus.org>
Cc: current@FreeBSD.ORG
Subject: Whats VM_STACK (was Re: Netscape | Mozilla)
Message-ID: <19990127162814.O421@tar.com>
References: <XFMail.990127180059.asmodai@wxs.nl> <199901271716.MAA20727@ayukawa.aus.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.95i
In-Reply-To: <199901271716.MAA20727@ayukawa.aus.org>; from Luke on Wed, Jan 27, 1999 at 12:35:09PM -0500
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
On Wed, Jan 27, 1999 at 12:35:09PM -0500, Luke wrote:
> what is this VM_STACK option?
Its some new code to manage "autogrow" stacks. The existing (old) code
made a process stack autogrow. But, its useful to be able to create
additional autogrow memory regions to use as thread stacks in threaded
programs. The additional code does this, and uses the same code to
manage the process stack.
Its been around for a month or so, hidden behind the VM_STACK option
(ie. you had to add -DVM_STACK when compiling kernel/world). The idea
was that if it works, the option would be removed and the code made
permanent. For i386 machines, the "option" was made the default about
2 days ago for -current, and was made the default for 3.X today.
You can still pull it out if you have problems, as its still mostly
hidden behind the VM_STACK defines. -DVM_STACK is now just turned
on by default. As soon as it gets more testing on alpha machines,
and if it seems to continue to work elsewhere, and if there's no
great objection, its likely to become permanent.
mmap(2) has some more information (if your sources are very current).
--
Richard Seamman, Jr. email: dick@tar.com
5182 N. Maple Lane phone: 414-367-5450
Chenequa WI 53058 fax: 414-367-5852
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Wed Jan 27 14:44:19 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id OAA23735
for freebsd-current-outgoing; Wed, 27 Jan 1999 14:44:19 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA23730
for <current@FreeBSD.ORG>; Wed, 27 Jan 1999 14:44:18 -0800 (PST)
(envelope-from dillon@apollo.backplane.com)
Received: (from dillon@localhost)
by apollo.backplane.com (8.9.2/8.9.1) id OAA64912;
Wed, 27 Jan 1999 14:44:17 -0800 (PST)
(envelope-from dillon)
Date: Wed, 27 Jan 1999 14:44:17 -0800 (PST)
From: Matthew Dillon <dillon@apollo.backplane.com>
Message-Id: <199901272244.OAA64912@apollo.backplane.com>
To: current@FreeBSD.ORG
Subject: bug in nfs_access()
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
bug in nfs_access(). nfs/nfs_vnops.c, line 414 or so.
Fixed!
This is a nasty one. I'm surprised it hasn't caused grief before
-Matt
Matthew Dillon
<dillon@backplane.com>
...
auio.uio_procp = ap->a_p;
if (vp->v_type == VREG)
error = nfs_readrpc(vp, &auio, ap->a_cred);
else if (vp->v_type == VDIR) {
char* bp;
bp = malloc(NFS_DIRBLKSIZ, M_TEMP, M_WAITOK);
aiov.iov_base = bp;
aiov.iov_len = auio.uio_resid = NFS_DIRBLKSIZ;
error = nfs_readdirrpc(vp, &auio, ap->a_cred);
free(bp, M_TEMP);
} else if (vp->v_type = VLNK)
error = nfs_readlinkrpc(vp, &auio, ap->a_cred);
else
error = EACCES;
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Wed Jan 27 14:45:54 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id OAA23963
for freebsd-current-outgoing; Wed, 27 Jan 1999 14:45:54 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from adelphi.physics.adelaide.edu.au (adelphi.physics.adelaide.edu.au [129.127.36.247])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA23931
for <current@freebsd.org>; Wed, 27 Jan 1999 14:45:50 -0800 (PST)
(envelope-from kkennawa@physics.adelaide.edu.au)
Received: from bragg (bragg [129.127.36.34])
by adelphi.physics.adelaide.edu.au (8.8.8/8.8.8/UofA-1.5) with SMTP id JAA24088;
Thu, 28 Jan 1999 09:15:40 +1030 (CST)
Received: from localhost by bragg; (5.65/1.1.8.2/05Aug95-0227PM)
id AA05758; Thu, 28 Jan 1999 09:15:40 +1030
Date: Thu, 28 Jan 1999 09:15:36 +1030 (CST)
From: Kris Kennaway <kkennawa@physics.adelaide.edu.au>
X-Sender: kkennawa@bragg
To: Luke <lh@aus.org>
Cc: "Jason C. Wells" <jcwells@u.washington.edu>,
FreeBSD Current <current@FreeBSD.ORG>,
"Steve O'Hara-Smith" <steveo@iol.ie>
Subject: RE: Netscape | Mozilla
In-Reply-To: <199901271901.OAA22237@ayukawa.aus.org>
Message-Id: <Pine.OSF.4.05.9901280914310.22605-100000@bragg>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
On Wed, 27 Jan 1999, Luke wrote:
> > I wrote a port for Linux Netscape if anyone wants it. I sent it in but it
> > came back to me with some comments about netscape port proliferation.
>
> I tried that one but it wants linux_lib installed on /compat and theres
> no room. Do you know if its ok to make /compat a link to somewhere else for the
> linux_lib port. [why does it install into / anyways]
I have my /compat symlinked to /usr/compat with no problems. The root
filesystem does seem like not the best place to put it by default.
Kris
-----
(ASP) Microsoft Corporation (MSFT) announced today that the release of its
productivity suite, Office 2000, will be delayed until the first quarter
of 1901.
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Wed Jan 27 14:55:43 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id OAA25440
for freebsd-current-outgoing; Wed, 27 Jan 1999 14:55:43 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from adelphi.physics.adelaide.edu.au (adelphi.physics.adelaide.edu.au [129.127.36.247])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA25435
for <current@freebsd.org>; Wed, 27 Jan 1999 14:55:40 -0800 (PST)
(envelope-from kkennawa@physics.adelaide.edu.au)
Received: from bragg (bragg [129.127.36.34])
by adelphi.physics.adelaide.edu.au (8.8.8/8.8.8/UofA-1.5) with SMTP id JAA23976;
Thu, 28 Jan 1999 09:25:36 +1030 (CST)
Received: from localhost by bragg; (5.65/1.1.8.2/05Aug95-0227PM)
id AA30315; Thu, 28 Jan 1999 09:25:34 +1030
Date: Thu, 28 Jan 1999 09:25:33 +1030 (CST)
From: Kris Kennaway <kkennawa@physics.adelaide.edu.au>
X-Sender: kkennawa@bragg
To: sthaug@nethelp.no
Cc: green@unixhelp.org, asmodai@wxs.nl, current@FreeBSD.ORG
Subject: RE: One answer, one question.
In-Reply-To: <20704.917451203@verdi.nethelp.no>
Message-Id: <Pine.OSF.4.05.9901280922300.22605-100000@bragg>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
On Wed, 27 Jan 1999 sthaug@nethelp.no wrote:
> > I haven't really messed with it too much, so right now I think it's related
> > because testing makes it appear to be. i.e. if I have a kernel with VM_STACK
> > Netscape will sig11 right after loading; without VM_STACK it's as stable as
> > ever. I'd love to figure out why ps isn't working, though...
>
> Unfortunately, for some of us Netscape dying is not the problem. Netscape
> *hanging* is the problem. For me, it appears to be related to DNS lookups
> *and FreeBSD 3.0.
>
> If I run with MOZILLA_NO_ASYNC_DNS (ie. no DNS helper process), I often
> get hangs. This did not happen with FreeBSD 2.2.8. It appears to happen if
> name lookups take "too long". If I prime the cache on the DNS server (eg.
> by looking up the name manually beforehand), *or* if I let Netscape start
> a DNS helper process, I don't get these hangs.
My solution to this is to run a local copy of squid to do all the actual page
fetching, and to turn netscape's memory and disk cache to 0 (this might not be
necessary any more, but at some point it was claimed to help for something).
Running 4.5 like this has been flawless (except when I disable the proxy for
whatever reason and forget, which leads to NS hanging in fairly short order
:-)
Kris
-----
(ASP) Microsoft Corporation (MSFT) announced today that the release of its
productivity suite, Office 2000, will be delayed until the first quarter
of 1901.
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Wed Jan 27 14:58:23 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id OAA25749
for freebsd-current-outgoing; Wed, 27 Jan 1999 14:58:23 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA25742
for <current@FreeBSD.ORG>; Wed, 27 Jan 1999 14:58:22 -0800 (PST)
(envelope-from dillon@apollo.backplane.com)
Received: (from dillon@localhost)
by apollo.backplane.com (8.9.2/8.9.1) id OAA67227;
Wed, 27 Jan 1999 14:58:21 -0800 (PST)
(envelope-from dillon)
Date: Wed, 27 Jan 1999 14:58:21 -0800 (PST)
From: Matthew Dillon <dillon@apollo.backplane.com>
Message-Id: <199901272258.OAA67227@apollo.backplane.com>
To: current@FreeBSD.ORG
Subject: -Wall, -Wcast-qual has been turned on
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
-Wall and -Wcast-qual has been turned on in /usr/src/share/mk/bsd.kern.mk.
Please note that you will see a lot of warnings ( but no fatal errors )
while compiling the kernel now until we can get it all cleaned up.
I am working a first-pass cleanup now.
Do not 'cleanup' the code unless you know what you are doing, there are
some odd things in there that are being caught now. Specifically, nobody
should clean up the enumeration warnings or the &&/|| warnings unless
they know exactly what they are doing.
The volatile warnings also need esspecial attention. If you are not
familiar with how volatile is used with memory-mapped I/O, do not try to
clean these up.
-Matt
Matthew Dillon
<dillon@backplane.com>
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Wed Jan 27 15:02:25 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id PAA26305
for freebsd-current-outgoing; Wed, 27 Jan 1999 15:02:25 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from kithrup.com (kithrup.com [205.179.156.40])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA26299
for <current@freebsd.org>; Wed, 27 Jan 1999 15:02:21 -0800 (PST)
(envelope-from sef@kithrup.com)
Received: (from sef@localhost)
by kithrup.com (8.8.8/8.8.8) id PAA02846;
Wed, 27 Jan 1999 15:02:20 -0800 (PST)
(envelope-from sef)
Date: Wed, 27 Jan 1999 15:02:20 -0800 (PST)
From: Sean Eric Fagan <sef@kithrup.com>
Message-Id: <199901272302.PAA02846@kithrup.com>
To: current@FreeBSD.ORG
Subject: Re: "JAIL" code headed for -current.
In-Reply-To: <199901271944.LAA15317.kithrup.freebsd.current@kithrup.com>
References: <29763.917434096.kithrup.freebsd.current@critter.freebsd.dk>
Organization: Kithrup Enterprises, Ltd.
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
In article <199901271944.LAA15317.kithrup.freebsd.current@kithrup.com> you write:
>>all over the kernel:
>>
>> suser(NOJAIL, bla, bla);
>>or
>> suser(0, bla, bla);
>Oh, goody, more gratuitious incomaptibilities with everyone else.
And to followup to my own message, since nobody else has:
This is stupid. While I don't object to the concept (and even know people who
have requested it), that particular implementation sucks. It breaks an
existing API *and* ABI.
I would suggest using a different routine name than suser(); suser() can be
made into a macro or stub routine that calls the new routine with a first
argument of 0 (or, of course, both a macro *and* a stub routine).
Any time there's a change, "all over the kernel," THIS SHOULD RAISE WARNING
FLAGS, PEOPLE!
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Wed Jan 27 15:22:03 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id PAA29076
for freebsd-current-outgoing; Wed, 27 Jan 1999 15:22:03 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA29044
for <current@FreeBSD.ORG>; Wed, 27 Jan 1999 15:21:56 -0800 (PST)
(envelope-from julian@whistle.com)
Received: (from daemon@localhost)
by alpo.whistle.com (8.8.5/8.8.5) id PAA09264;
Wed, 27 Jan 1999 15:13:11 -0800 (PST)
Received: from current1.whistle.com(207.76.205.22)
via SMTP by alpo.whistle.com, id smtpdLg9254; Wed Jan 27 23:13:01 1999
Date: Wed, 27 Jan 1999 15:12:53 -0800 (PST)
From: Julian Elischer <julian@whistle.com>
To: Matthew Dillon <dillon@apollo.backplane.com>
cc: current@FreeBSD.ORG
Subject: Re: bug in devfs_strategy() ???
In-Reply-To: <199901272201.OAA61764@apollo.backplane.com>
Message-ID: <Pine.BSF.3.95.990127150747.10452P-100000@current1.whistle.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
yes, though luckily it turns out to not matter.
except possibly on tapes..
the 2nd call in the raw case will probably finish immediatly
as the B_DONE flag will be set.
On Wed, 27 Jan 1999, Matthew Dillon wrote:
> Aren't there are few BREAK statements missing from this ?
>
> -Matt
> Matthew Dillon
> <dillon@backplane.com>
>
> static int
> devfs_strategy(struct vop_strategy_args *ap)
> {
> ...
> switch (ap->a_vp->v_type) {
> case VCHR:
> (*dnp->by.Cdev.cdevsw->d_strategy)(bp);
> case VBLK:
> (*dnp->by.Bdev.bdevsw->d_strategy)(bp);
> }
> return (0);
> }
>
>
>
> To Unsubscribe: send mail to majordomo@FreeBSD.org
> with "unsubscribe freebsd-current" in the body of the message
>
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Wed Jan 27 15:25:57 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id PAA29561
for freebsd-current-outgoing; Wed, 27 Jan 1999 15:25:57 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from adelphi.physics.adelaide.edu.au (adelphi.physics.adelaide.edu.au [129.127.36.247])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA29545
for <current@freebsd.org>; Wed, 27 Jan 1999 15:25:53 -0800 (PST)
(envelope-from kkennawa@physics.adelaide.edu.au)
Received: from bragg (bragg [129.127.36.34])
by adelphi.physics.adelaide.edu.au (8.8.8/8.8.8/UofA-1.5) with SMTP id JAA23336;
Thu, 28 Jan 1999 09:55:49 +1030 (CST)
Received: from localhost by bragg; (5.65/1.1.8.2/05Aug95-0227PM)
id AA31585; Thu, 28 Jan 1999 09:55:48 +1030
Date: Thu, 28 Jan 1999 09:55:47 +1030 (CST)
From: Kris Kennaway <kkennawa@physics.adelaide.edu.au>
X-Sender: kkennawa@bragg
To: Jeroen Ruigrok/Asmodai <asmodai@wxs.nl>
Cc: Brian Feldman <green@unixhelp.org>, current@FreeBSD.ORG
Subject: RE: One answer, one question.
In-Reply-To: <XFMail.990127162827.asmodai@wxs.nl>
Message-Id: <Pine.OSF.4.05.9901280927530.22605-100000@bragg>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
On Wed, 27 Jan 1999, Jeroen Ruigrok/Asmodai wrote:
> On 27-Jan-99 Brian Feldman wrote:
> > I am certain VM_STACK is breaking Netscape. Ps isn't related, but I am
> > having problems with it, even after rebuilding everything, kvm_mkdb'ing...
> > :(
>
> OK, I'm going to rebuild NetScape against the latest sources et al, I last
> compiled it against a 3.0 CURRENT in December...
What's there to compile with netscape? It's provided in binary form, which
means it's statically linked with some libraries at build time by the netscape
people (e.g. the motif library), and is dynamically linked against some of the
a.out libraries on your system (which means that nothing changes in the binary
because it's, well, dynamic). In either case there's nothing to be changed by
re-extracting the binary and installing it.
Do you perhaps mean Mozilla (which is, last I heard, wildly unstable and
incomplete development code)?
Kris
-----
(ASP) Microsoft Corporation (MSFT) announced today that the release of its
productivity suite, Office 2000, will be delayed until the first quarter
of 1901.
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Wed Jan 27 15:30:18 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id PAA29967
for freebsd-current-outgoing; Wed, 27 Jan 1999 15:30:18 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from fledge.watson.org (FLEDGE.RES.CMU.EDU [128.2.93.229])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA29962
for <freebsd-current@freebsd.org>; Wed, 27 Jan 1999 15:30:17 -0800 (PST)
(envelope-from robert@cyrus.watson.org)
Received: from fledge.watson.org (robert@fledge.pr.watson.org [192.0.2.3])
by fledge.watson.org (8.8.8/8.8.8) with SMTP id SAA08175
for <freebsd-current@freebsd.org>; Wed, 27 Jan 1999 18:30:15 -0500 (EST)
Date: Wed, 27 Jan 1999 18:30:15 -0500 (EST)
From: Robert Watson <robert@cyrus.watson.org>
X-Sender: robert@fledge.watson.org
Reply-To: Robert Watson <robert@cyrus.watson.org>
To: freebsd-current@FreeBSD.ORG
Subject: Naming files in sys/kern
Message-ID: <Pine.BSF.3.96.990127181407.8092A-100000@fledge.watson.org>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
I was wondering what the naming scheme for files in /usr/src/sys/kern was
:). There seem to be several sorts of files there--
bus_if.m device_.m imgact_*.c
inflate.c init_*.c kern_*.c
link_*.c make*.{pl,sh} md5c.c
subr_*.c sys_*.c syscalls.*
sysv_*.c tty.c tty_*.c
uipc_*.c vfs_*.c vnode_if.{sh,src}
It's not clear to me, when thinking of introducing a new file (say, for
auditing support :), what I should name it. Would it be kern_audit.c or
sys_audit.c? Or, if it is POSIX.1e, would it go into a
/usr/src/sys/posix1e directory as the posix4 realtime stuff did (assuming
that support for additional features from that posix draft were going to
be forthcoming)? Given the past discussion of how to ]fail to]
restructure the source tree, I assume this issue is non-trivial :).
style(9) doesn't appear to provide any pointers.
Robert N Watson
robert@fledge.watson.org http://www.watson.org/~robert/
PGP key fingerprint: 03 01 DD 8E 15 67 48 73 25 6D 10 FC EC 68 C1 1C
Carnegie Mellon University http://www.cmu.edu/
TIS Labs at Network Associates, Inc. http://www.tis.com/
SafePort Network Services http://www.safeport.com/
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Wed Jan 27 15:32:02 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id PAA00284
for freebsd-current-outgoing; Wed, 27 Jan 1999 15:32:02 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA00249
for <current@FreeBSD.ORG>; Wed, 27 Jan 1999 15:31:53 -0800 (PST)
(envelope-from julian@whistle.com)
Received: (from daemon@localhost)
by alpo.whistle.com (8.8.5/8.8.5) id PAA09626;
Wed, 27 Jan 1999 15:23:32 -0800 (PST)
Received: from current1.whistle.com(207.76.205.22)
via SMTP by alpo.whistle.com, id smtpdNO9622; Wed Jan 27 23:23:21 1999
Date: Wed, 27 Jan 1999 15:23:18 -0800 (PST)
From: Julian Elischer <julian@whistle.com>
To: Sean Eric Fagan <sef@kithrup.com>
cc: current@FreeBSD.ORG
Subject: Re: "JAIL" code headed for -current.
In-Reply-To: <199901272302.PAA02846@kithrup.com>
Message-ID: <Pine.BSF.3.95.990127152030.10452Q-100000@current1.whistle.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
Ah now I see what sean is aguing about..
He has a point..
maybe using jailsuser() or something might be a better idea?
(On the other hand at 3.x existing KLD modules are not YET a problem
except for OSS)
On Wed, 27 Jan 1999, Sean Eric Fagan wrote:
> In article <199901271944.LAA15317.kithrup.freebsd.current@kithrup.com> you write:
> >>all over the kernel:
> >>
> >> suser(NOJAIL, bla, bla);
> >>or
> >> suser(0, bla, bla);
> >Oh, goody, more gratuitious incomaptibilities with everyone else.
>
> And to followup to my own message, since nobody else has:
>
> This is stupid. While I don't object to the concept (and even know people who
> have requested it), that particular implementation sucks. It breaks an
> existing API *and* ABI.
>
> I would suggest using a different routine name than suser(); suser() can be
> made into a macro or stub routine that calls the new routine with a first
> argument of 0 (or, of course, both a macro *and* a stub routine).
>
> Any time there's a change, "all over the kernel," THIS SHOULD RAISE WARNING
> FLAGS, PEOPLE!
>
>
> To Unsubscribe: send mail to majordomo@FreeBSD.org
> with "unsubscribe freebsd-current" in the body of the message
>
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Wed Jan 27 15:33:32 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id PAA00479
for freebsd-current-outgoing; Wed, 27 Jan 1999 15:33:32 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from ns.mt.sri.com (sri-gw.MT.net [206.127.105.141])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA00472
for <current@FreeBSD.ORG>; Wed, 27 Jan 1999 15:33:30 -0800 (PST)
(envelope-from nate@mt.sri.com)
Received: from mt.sri.com (rocky.mt.sri.com [206.127.76.100])
by ns.mt.sri.com (8.8.8/8.8.8) with SMTP id QAA07877;
Wed, 27 Jan 1999 16:33:25 -0700 (MST)
(envelope-from nate@rocky.mt.sri.com)
Received: by mt.sri.com (SMI-8.6/SMI-SVR4)
id QAA24533; Wed, 27 Jan 1999 16:33:24 -0700
Date: Wed, 27 Jan 1999 16:33:24 -0700
Message-Id: <199901272333.QAA24533@mt.sri.com>
From: Nate Williams <nate@mt.sri.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
To: Julian Elischer <julian@whistle.com>
Cc: Sean Eric Fagan <sef@kithrup.com>, current@FreeBSD.ORG
Subject: Re: "JAIL" code headed for -current.
In-Reply-To: <Pine.BSF.3.95.990127152030.10452Q-100000@current1.whistle.com>
References: <199901272302.PAA02846@kithrup.com>
<Pine.BSF.3.95.990127152030.10452Q-100000@current1.whistle.com>
X-Mailer: VM 6.34 under 19.16 "Lille" XEmacs Lucid
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
> Ah now I see what sean is aguing about..
> He has a point..
>
> maybe using jailsuser() or something might be a better idea?
> (On the other hand at 3.x existing KLD modules are not YET a problem
> except for OSS)
But then we're still having an API change that doesn't have to be there.
Nate
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Wed Jan 27 15:34:54 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id PAA00590
for freebsd-current-outgoing; Wed, 27 Jan 1999 15:34:54 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from zed.ludd.luth.se (zed.ludd.luth.se [130.240.16.33])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA00582
for <freebsd-current@freebsd.org>; Wed, 27 Jan 1999 15:34:52 -0800 (PST)
(envelope-from pantzer@sister.ludd.luth.se)
Received: from sister.ludd.luth.se (pantzer@sister.ludd.luth.se [130.240.16.77])
by zed.ludd.luth.se (8.8.5/8.8.5) with SMTP id AAA24081;
Thu, 28 Jan 1999 00:34:32 +0100
Message-Id: <199901272334.AAA24081@zed.ludd.luth.se>
X-Mailer: exmh version 2.0.2 2/24/98
To: Sheldon Hearn <axl@iafrica.com>
cc: freebsd-current@FreeBSD.ORG
Subject: Re: NIS with HPUX 10.20
In-reply-to: Your message of "Wed, 27 Jan 1999 15:16:59 +0200."
<90210.917443019@axl.noc.iafrica.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Thu, 28 Jan 1999 00:34:30 +0100
From: Mattias Pantzare <pantzer@ludd.luth.se>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
> > No. installworld more or less assumes single user.
>
> This is really what I'm getting at. :-)
>
> If installworld assumes single-user mode, why do we install -C
> ld-elf.so.1 ? The first time I asked this question, I didn't mention
> single-user mode and your answer was that it's to protect "live
> systems". What's so live about a single-user system that we can't assume
> nothing else needs ld-elf.so.1 while we're smacking it?
Why _not_ use -C? What is the point in replacing a file with the same file?
install -C will replace the file if the new file is diffrent.
That is realy good if you do backups as only the new files will be in the
backup.
And it is good if installworld works on a active system even if it is not
supported.
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Wed Jan 27 15:45:33 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id PAA01538
for freebsd-current-outgoing; Wed, 27 Jan 1999 15:45:33 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from kithrup.com (kithrup.com [205.179.156.40])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA01532
for <current@FreeBSD.ORG>; Wed, 27 Jan 1999 15:45:29 -0800 (PST)
(envelope-from sef@kithrup.com)
Received: (from sef@localhost)
by kithrup.com (8.8.8/8.8.8) id PAA06079;
Wed, 27 Jan 1999 15:43:19 -0800 (PST)
(envelope-from sef)
Date: Wed, 27 Jan 1999 15:43:19 -0800 (PST)
From: Sean Eric Fagan <sef@kithrup.com>
Message-Id: <199901272343.PAA06079@kithrup.com>
To: nate@mt.sri.com
Subject: Re: "JAIL" code headed for -current.
Cc: current@FreeBSD.ORG, julian@whistle.com
In-Reply-To: <199901272333.QAA24533@mt.sri.com>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
>But then we're still having an API change that doesn't have to be there.
No, it's not.
If you change suser() to:
int
suser(uc, ac)
struct ucred *uc;
u_short *ac; {
return JAILsuser(0, uc, ac);
}
then suser() continues to have the same semantics and calling convention; you
can speed this up a bit by having:
#define suser(a,b) JAILsuser(0, a, b)
in <sys/ucred.h> (where suser's prototype is).
Then you can simply change the calls from suser() to JAILsuser() as needed.
(Actually, JAILsuser is a bad name, really, since this could also be used to
move to a more-capability-based mechanism, with the "jail" being simply one
set of resources to compare the requested capability against. But that's just
a thought that has occurred to me, and I haven't spent any time making it
coherent ;).)
Doing it this way should result in a superset, and minimal source code
changes; doing it with just the stub routine would result in minimal binary
impact as well.
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Wed Jan 27 15:46:46 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id PAA01670
for freebsd-current-outgoing; Wed, 27 Jan 1999 15:46:46 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from ns.mt.sri.com (sri-gw.MT.net [206.127.105.141])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA01659
for <current@FreeBSD.ORG>; Wed, 27 Jan 1999 15:46:42 -0800 (PST)
(envelope-from nate@mt.sri.com)
Received: from mt.sri.com (rocky.mt.sri.com [206.127.76.100])
by ns.mt.sri.com (8.8.8/8.8.8) with SMTP id QAA08012;
Wed, 27 Jan 1999 16:46:40 -0700 (MST)
(envelope-from nate@rocky.mt.sri.com)
Received: by mt.sri.com (SMI-8.6/SMI-SVR4)
id QAA24692; Wed, 27 Jan 1999 16:46:39 -0700
Date: Wed, 27 Jan 1999 16:46:39 -0700
Message-Id: <199901272346.QAA24692@mt.sri.com>
From: Nate Williams <nate@mt.sri.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
To: Sean Eric Fagan <sef@kithrup.com>
Cc: nate@mt.sri.com, current@FreeBSD.ORG, julian@whistle.com
Subject: Re: "JAIL" code headed for -current.
In-Reply-To: <199901272343.PAA06079@kithrup.com>
References: <199901272333.QAA24533@mt.sri.com>
<199901272343.PAA06079@kithrup.com>
X-Mailer: VM 6.34 under 19.16 "Lille" XEmacs Lucid
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
> >But then we're still having an API change that doesn't have to be there.
>
> No, it's not.
You missed the point. Julian mentioned that since there were no 3.0
lkm's that might user 'suser()', there is no ABI to stay compatible
with, hence it's an ABI change that doesn't affect anything given that
ELF is the new 'binary' format.
My point was that even though we could still live with the ABI change,
we'd still have an API change by adding the first parameter to suser().
Nate
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Wed Jan 27 16:02:49 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id QAA04699
for freebsd-current-outgoing; Wed, 27 Jan 1999 16:02:49 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from cain.gsoft.com.au (genesi.lnk.telstra.net [139.130.136.161])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA04613
for <current@FreeBSD.ORG>; Wed, 27 Jan 1999 16:02:45 -0800 (PST)
(envelope-from doconnor@gsoft.com.au)
Received: from lot.gsoft.com.au (doconnor@lot.gsoft.com.au [203.38.152.106])
by cain.gsoft.com.au (8.8.8/8.8.8) with ESMTP id KAA27197;
Thu, 28 Jan 1999 10:32:20 +1030 (CST)
(envelope-from doconnor@gsoft.com.au)
Message-ID: <XFMail.990128104106.doconnor@gsoft.com.au>
X-Mailer: XFMail 1.3 [p0] on FreeBSD
X-Priority: 3 (Normal)
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 8bit
MIME-Version: 1.0
In-Reply-To: <199901272124.NAA15248@bubba.whistle.com>
Date: Thu, 28 Jan 1999 10:41:06 +1030 (CST)
From: "Daniel O'Connor" <doconnor@gsoft.com.au>
To: Archie Cobbs <archie@whistle.com>
Subject: Re: DEVFS, the time has come...
Cc: current@FreeBSD.ORG, (Doug Rabson) <dfr@nlsystems.com>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
On 27-Jan-99 Archie Cobbs wrote:
> I agree.. and same thing goes for Ethernet drivers. I actually
> like the way Linux always has "eth0", "eth1", ... (which we could
> do using netgraph, with some work).
Me too :)
Of course you'd have to be able to do things like 'wire down' your ethernet card etc..
But the idea is nice IMHO :)
---
Daniel O'Connor software and network engineer
for Genesis Software - http://www.gsoft.com.au
"The nice thing about standards is that there
are so many of them to choose from."
-- Andrew Tanenbaum
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Wed Jan 27 16:34:05 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id QAA08810
for freebsd-current-outgoing; Wed, 27 Jan 1999 16:34:05 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from whistle.com (s205m131.whistle.com [207.76.205.131])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA08764
for <current@FreeBSD.ORG>; Wed, 27 Jan 1999 16:34:01 -0800 (PST)
(envelope-from archie@whistle.com)
Received: (from smap@localhost) by whistle.com (8.7.5/8.6.12) id QAA24256; Wed, 27 Jan 1999 16:33:20 -0800 (PST)
Received: from bubba.whistle.com( 207.76.205.7) by whistle.com via smap (V2.0)
id xma024252; Wed, 27 Jan 99 16:33:11 -0800
Received: (from archie@localhost) by bubba.whistle.com (8.8.7/8.6.12) id QAA17991; Wed, 27 Jan 1999 16:33:10 -0800 (PST)
From: Archie Cobbs <archie@whistle.com>
Message-Id: <199901280033.QAA17991@bubba.whistle.com>
Subject: Re: DEVFS, the time has come...
In-Reply-To: <XFMail.990128104106.doconnor@gsoft.com.au> from Daniel O'Connor at "Jan 28, 99 10:41:06 am"
To: doconnor@gsoft.com.au (Daniel O'Connor)
Date: Wed, 27 Jan 1999 16:33:10 -0800 (PST)
Cc: current@FreeBSD.ORG
X-Mailer: ELM [version 2.4ME+ PL38 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
Daniel O'Connor writes:
> On 27-Jan-99 Archie Cobbs wrote:
> > I agree.. and same thing goes for Ethernet drivers. I actually
> > like the way Linux always has "eth0", "eth1", ... (which we could
> > do using netgraph, with some work).
> Me too :)
>
> Of course you'd have to be able to do things like 'wire down' your
> ethernet card etc.. But the idea is nice IMHO :)
That would be easy part! :-) Something like this...
$ ngctl mkpeer ed0: eth_iface upstream downstream
-Archie
___________________________________________________________________________
Archie Cobbs * Whistle Communications, Inc. * http://www.whistle.com
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Wed Jan 27 16:37:39 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id QAA09077
for freebsd-current-outgoing; Wed, 27 Jan 1999 16:37:39 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA09071
for <current@freebsd.org>; Wed, 27 Jan 1999 16:37:37 -0800 (PST)
(envelope-from jdp@polstra.com)
Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13])
by wall.polstra.com (8.9.1/8.9.1) with ESMTP id QAA02156;
Wed, 27 Jan 1999 16:37:36 -0800 (PST)
(envelope-from jdp@polstra.com)
From: John Polstra <jdp@polstra.com>
Received: (from jdp@localhost)
by vashon.polstra.com (8.9.1/8.9.1) id QAA27694;
Wed, 27 Jan 1999 16:37:35 -0800 (PST)
(envelope-from jdp@polstra.com)
Date: Wed, 27 Jan 1999 16:37:35 -0800 (PST)
Message-Id: <199901280037.QAA27694@vashon.polstra.com>
To: dillon@apollo.backplane.com
Subject: Re: btokup() macro in sys/malloc.h
Newsgroups: polstra.freebsd.current
In-Reply-To: <199901272128.NAA56542@apollo.backplane.com>
Organization: Polstra & Co., Seattle, WA
Cc: current@FreeBSD.ORG
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
In article <199901272128.NAA56542@apollo.backplane.com>,
Matthew Dillon <dillon@apollo.backplane.com> wrote:
> Is this parenthesization correct ?
>
> OLD
>
> #define btokup(addr) (&kmemusage[(caddr_t)(addr) - kmembase >> PAGE_SHIFT])
>
> NEW
>
> #define btokup(addr) (&kmemusage[((caddr_t)(addr) - kmembase) >> PAGE_SHIFT])
The added parentheses don't make any difference, semantically. This
change probably wouldn't meet the criteria spelled out in style(9):
Unary operators don't require spaces, binary operators do. Don't use
parentheses unless they're required for precedence, or the statement is
really confusing without them.
a = b->c[0] + ~d == (e || f) || g && h ? i : j >> 1;
k = !(l & FLAGS);
John
--
John Polstra jdp@polstra.com
John D. Polstra & Co., Inc. Seattle, Washington USA
"Nobody ever went broke underestimating the taste of the American public."
-- H. L. Mencken
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Wed Jan 27 16:39:00 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id QAA09329
for freebsd-current-outgoing; Wed, 27 Jan 1999 16:39:00 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from cain.gsoft.com.au (genesi.lnk.telstra.net [139.130.136.161])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA09324
for <current@FreeBSD.ORG>; Wed, 27 Jan 1999 16:38:57 -0800 (PST)
(envelope-from doconnor@gsoft.com.au)
Received: from lot.gsoft.com.au (doconnor@lot.gsoft.com.au [203.38.152.106])
by cain.gsoft.com.au (8.8.8/8.8.8) with ESMTP id LAA27379;
Thu, 28 Jan 1999 11:08:50 +1030 (CST)
(envelope-from doconnor@gsoft.com.au)
Message-ID: <XFMail.990128111737.doconnor@gsoft.com.au>
X-Mailer: XFMail 1.3 [p0] on FreeBSD
X-Priority: 3 (Normal)
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 8bit
MIME-Version: 1.0
In-Reply-To: <199901280033.QAA17991@bubba.whistle.com>
Date: Thu, 28 Jan 1999 11:17:37 +1030 (CST)
From: "Daniel O'Connor" <doconnor@gsoft.com.au>
To: Archie Cobbs <archie@whistle.com>
Subject: Re: DEVFS, the time has come...
Cc: current@FreeBSD.ORG
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
On 28-Jan-99 Archie Cobbs wrote:
> That would be easy part! :-) Something like this...
> $ ngctl mkpeer ed0: eth_iface upstream downstream
Heh.. It would be nice if it was automagic though..
(Where's my kernel config option :)
---
Daniel O'Connor software and network engineer
for Genesis Software - http://www.gsoft.com.au
"The nice thing about standards is that there
are so many of them to choose from."
-- Andrew Tanenbaum
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Wed Jan 27 16:41:58 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id QAA09697
for freebsd-current-outgoing; Wed, 27 Jan 1999 16:41:58 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from poboxer.pobox.com (port25.prairietech.net [208.141.230.102])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA09668
for <current@freebsd.org>; Wed, 27 Jan 1999 16:41:52 -0800 (PST)
(envelope-from alk@poboxer.pobox.com)
Received: (from alk@localhost)
by poboxer.pobox.com (8.9.2/8.9.1) id SAA62002;
Wed, 27 Jan 1999 18:41:45 -0600 (CST)
(envelope-from alk)
From: Tony Kimball <alk@pobox.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Date: Wed, 27 Jan 1999 18:41:44 -0600 (CST)
X-Face: \h9Jg:Cuivl4S*UP-)gO.6O=T]]@ncM*tn4zG);)lk#4|lqEx=*talx?.<li^!8ecK]}3L-
6`ZQW3}kxy*5]B<KA"&iBl58"/$W-0PP`B7c%'XczR)8T0VN47L`rQlu8qBIX4TJ|v'D%:k7GO%v4A
Os>Gk,dMQU2)ptPC17cpBzm(l'M|H8BUF1&]dDCxZ.c~Wy6-j,^V1E(NtX$FpkkdnJixsJHE95JlhO
5\M3jh'YiO7KPCn0~W`Ro44_TB@&JuuqRqgPL'0/{):7rU-%.*@/>q?1&Ed
Reply-To: alk@pobox.com
To: current@FreeBSD.ORG
Subject: Re: removing f2c from base distribution
X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid
Message-ID: <13999.45566.549049.506346@avalon.east>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
: A lot of people use a lot of things out of ports. Why should Fortran
: be different?
For g77, because it is integrated with the C compiler. The system has
a lower maintenance cost if it is included.
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Wed Jan 27 16:45:36 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id QAA10124
for freebsd-current-outgoing; Wed, 27 Jan 1999 16:45:36 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA10118
for <current@FreeBSD.ORG>; Wed, 27 Jan 1999 16:45:34 -0800 (PST)
(envelope-from dillon@apollo.backplane.com)
Received: (from dillon@localhost)
by apollo.backplane.com (8.9.2/8.9.1) id QAA77982;
Wed, 27 Jan 1999 16:45:31 -0800 (PST)
(envelope-from dillon)
Date: Wed, 27 Jan 1999 16:45:31 -0800 (PST)
From: Matthew Dillon <dillon@apollo.backplane.com>
Message-Id: <199901280045.QAA77982@apollo.backplane.com>
To: John Polstra <jdp@polstra.com>
Cc: current@FreeBSD.ORG
Subject: Re: btokup() macro in sys/malloc.h
References: <199901280037.QAA27694@vashon.polstra.com>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
:> NEW
:>
:> #define btokup(addr) (&kmemusage[((caddr_t)(addr) - kmembase) >> PAGE_SHIFT])
:
:The added parentheses don't make any difference, semantically. This
:change probably wouldn't meet the criteria spelled out in style(9):
Then style(9) needs to be updated, because we have to add parenthesis
to be able to not get warnings with -Wall.
-Matt
:John
:--
: John Polstra jdp@polstra.com
: John D. Polstra & Co., Inc. Seattle, Washington USA
: "Nobody ever went broke underestimating the taste of the American public."
: -- H. L. Mencken
:
:To Unsubscribe: send mail to majordomo@FreeBSD.org
:with "unsubscribe freebsd-current" in the body of the message
:
Matthew Dillon
<dillon@backplane.com>
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Wed Jan 27 16:46:11 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id QAA10253
for freebsd-current-outgoing; Wed, 27 Jan 1999 16:46:11 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from k6n1.znh.org ([207.109.235.13])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA10138
for <freebsd-current@freebsd.org>; Wed, 27 Jan 1999 16:45:40 -0800 (PST)
(envelope-from zach@uffdaonline.net)
Received: (from zach@localhost)
by k6n1.znh.org (8.9.1/8.9.1) id AAA65250;
Thu, 28 Jan 1999 00:42:03 GMT
(envelope-from zach)
Message-ID: <19990127184203.A63814@znh.org>
Date: Wed, 27 Jan 1999 18:42:03 -0600
From: Zach Heilig <zach@uffdaonline.net>
To: Sheldon Hearn <axl@iafrica.com>, Bruce Evans <bde@zeta.org.au>
Cc: mike@smith.net.au, bonnetf@bart.esiee.fr, dhw@whistle.com,
freebsd-current@FreeBSD.ORG, meyerd1@fang.cs.sunyit.edu
Subject: Re: NIS with HPUX 10.20
References: <199901271141.WAA14759@godzilla.zeta.org.au> <78213.917439130@axl.noc.iafrica.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.93.2i
In-Reply-To: <78213.917439130@axl.noc.iafrica.com>; from Sheldon Hearn on Wed, Jan 27, 1999 at 02:12:10PM +0200
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
On Wed, Jan 27, 1999 at 02:12:10PM +0200, Sheldon Hearn wrote:
> On Wed, 27 Jan 1999 22:41:46 +1100, Bruce Evans wrote:
> > So that ld-elf.so.1 can be installed safely on an active system.
> I assume I should take your "installed safely" to mean "not installed"?
It is not installed because the binaries are identical (and install -C copies
to a temporary file (say ld-elf.so.1.tmp), and compares to ld-elf.so.1. Then
it compares and either deletes ld-elf.so.1.tmp or renames it over top of
ld-elf.so.1). It does update the 'ctime' entry of ld-elf.so.1, so using
'find /usr \! -ctime 1 -print' right after make world will find all the "old"
files. (^ this is how many days ago you made world, rounded up)
If it were installed normally, it would first delete ld-elf.so.1, then copy
the new one into place (with mode 000 while the copy takes place). This is
VERY bad in a running system.
The 'find' works better if /usr/local and /usr/X11R6 are symlinks, or set the
option to not recurse into those directories. And, 'perl' has to be checked
manually.
> Are there a lot of files that aren't installed for similar reasons
> during an installworld? If there are, I'd be interested in hearing about
> them so that I can update them manually.
Yes, in:
/usr/include <- this falls to 'find -ctime'.
/usr/libdata/perl <- you are better off ignoring "old" files in here.
The dates on symlinks aren't changed. There are a few files in /usr/share
that are "local" files and are never updated. There may be more, but these
are pointed out by the 'find' above.
--
Zach Heilig <zach@uffdaonline.net> / Zach Heilig <zach@gaffaneys.com>
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Wed Jan 27 17:01:59 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id RAA11412
for freebsd-current-outgoing; Wed, 27 Jan 1999 17:01:59 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from telos.odyssey.cs.cmu.edu (TELOS.ODYSSEY.CS.CMU.EDU [128.2.185.175])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA11395;
Wed, 27 Jan 1999 17:01:57 -0800 (PST)
(envelope-from jaharkes@telos.odyssey.cs.cmu.edu)
Received: (from jaharkes@localhost)
by telos.odyssey.cs.cmu.edu (8.8.7/8.8.7) id TAA03989;
Wed, 27 Jan 1999 19:47:21 -0500
From: jaharkes@cs.cmu.edu
Message-Id: <199901280047.TAA03989@telos.odyssey.cs.cmu.edu>
Subject: Coda Distributed Filesystem 5.0.1
To: coda-announce@TELEMANN.coda.cs.cmu.edu, codalist@TELEMANN.coda.cs.cmu.edu,
linux-fsdevel@vger.rutgers.edu, linux-kernel@vger.rutgers.edu,
current-users@netbsd.org, port-i386@netbsd.org, current@FreeBSD.ORG,
freebsd-afs@FreeBSD.ORG
Date: Wed, 27 Jan 1999 19:47:21 -0500 (EST)
Reply-To: codalist@TELEMANN.coda.cs.cmu.edu
Content-Type: text
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
Coda Distributed File System, version 5.0.1
Coda is a distributed file system like NFS and AFS. It is freely
available under the GPL. It functions somewhat like AFS in being a
"stateful" file system. Coda and AFS cache files on your local
machine to improve performance. But Coda goes a step further than AFS
by letting you access the cached files when there is no available
network, viz. disconnected laptops and network outages. Coda also has
read write replication servers. The Coda file server is outside the
kernel and on the client theCoda cache manager Venus is again outside
of the kernel, but on clients one needs a kernel module.
To get more information on Coda, check out
http://www.coda.cs.cmu.edu
There is a wealth of documents, papers, and theses there. There is
also a good introduction to the Coda File System in
http://www.coda.cs.cmu.edu/ljpaper/lj.html
and a Coda-HOWTO:
http://www.coda.cs.cmu.edu/coda-howto.html
Coda was originally developed as an academic prototype/testbed. It is
being polished and rewritten where necessary. Coda is a work in
progress and does have bugs. It is, though, very usable. Our
interest is in making Coda available to as many people as possible and
to have Coda evolve and flourish.
The bulk of the Coda file system code supports the Coda client
program, the Coda server program and the utilities needed by both.
All these programs are unix programs and can run equally well on any
Unix platform. Our main development thrust is improving these
programs. There is a small part of Coda that deals with the kernel to
file system interface. This code is OS specific (but should not be
platform specific).
Coda is currently available for several OS's and platforms:
linux 2.0: i386 & sparc
linux 2.2: i386 & sparc
Freebsd-2.2.x: i386
Freebsd -current: i386
NetBSD 1.3x: i386
NetBSD -current: i386
There are also alpha releases for:
Windows 95 -- Coda client
Windows NT -- Coda server
The relevant sources, binaries, and docs can be found in
ftp://ftp.coda.cs.cmu.edu/pub/coda/
There are several mailing lists @coda.cs.cmu.edu that discuss coda:
coda-announce and codalist. We appreciate comments, feedback, bug reports,
bug fixes, enhancements, etc.
Changes since our previous release are mostly to fix reported bugs.
- A fully qualified domainname was not correctly recognized by clog.
- The inet_aton function for Win95 handle non IP- addresses correctly.
- New glibc libraries crashed on NULL args given to getservbyname.
- egcs compilations were hit by a dangling else bug.
- A bunch of compilation fixes.
Please let us know about problems, since we will try to fix them right away.
Compatibility with previous versions:
- network protocol: can coexists with 4.6.7 and later
- disk format client: can only coexists with 5.0pre1
- disk format for server: backward compatible
The Coda Team
-------------
Peter Braam
Bob Baron
Jan Harkes
Marc Schnieder
coda@cs.cmu.edu
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Wed Jan 27 17:06:59 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id RAA11988
for freebsd-current-outgoing; Wed, 27 Jan 1999 17:06:59 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA11982
for <current@FreeBSD.ORG>; Wed, 27 Jan 1999 17:06:57 -0800 (PST)
(envelope-from dillon@apollo.backplane.com)
Received: (from dillon@localhost)
by apollo.backplane.com (8.9.2/8.9.1) id RAA81012;
Wed, 27 Jan 1999 17:06:56 -0800 (PST)
(envelope-from dillon)
Date: Wed, 27 Jan 1999 17:06:56 -0800 (PST)
From: Matthew Dillon <dillon@apollo.backplane.com>
Message-Id: <199901280106.RAA81012@apollo.backplane.com>
To: current@FreeBSD.ORG
Subject: bug in i386/eisa/ahb.c
References: <199901272244.OAA64912@apollo.backplane.com>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
static __inline void
ahbqueuembox(struct ahb_softc *ahb, u_int32_t mboxval, u_int attn_code)
{
u_int loopmax = 300;
while (--loopmax) {
u_int status;
status = ahb_inb(ahb, HOSTSTAT);
if ((status & HOSTSTAT_MBOX_EMPTY|HOSTSTAT_BUSY)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
!= HOSTSTAT_MBOX_EMPTY)
break;
DELAY(20);
}
if (loopmax == 0)
panic("ahb%ld: adapter not taking commands\n", ahb->unit);
ahb_outl(ahb, MBOXOUT0, mboxval);
ahb_outb(ahb, ATTN, attn_code);
}
& has higher precedence, so this is equivalently:
if (((status & HOSTSTAT_MBOX_EMPTY) | HOSTSTAT_BUSY) ...
Rather then:
if ((status & (HOSTSTAT_MBOX_EMPTYHOSTSTAT_BUSY)) ...
Fixed.
-Matt
Matthew Dillon
<dillon@backplane.com>
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Wed Jan 27 17:11:04 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id RAA12408
for freebsd-current-outgoing; Wed, 27 Jan 1999 17:11:04 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA12403
for <current@FreeBSD.ORG>; Wed, 27 Jan 1999 17:11:02 -0800 (PST)
(envelope-from dillon@apollo.backplane.com)
Received: (from dillon@localhost)
by apollo.backplane.com (8.9.2/8.9.1) id RAA81035;
Wed, 27 Jan 1999 17:11:02 -0800 (PST)
(envelope-from dillon)
Date: Wed, 27 Jan 1999 17:11:02 -0800 (PST)
From: Matthew Dillon <dillon@apollo.backplane.com>
Message-Id: <199901280111.RAA81035@apollo.backplane.com>
To: current@FreeBSD.ORG
Subject: Hmmm.. more on the eis ahb bug
References: <199901272244.OAA64912@apollo.backplane.com>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
Hmmm. Actually, this looks broken either way. It looks like
it is trying to wait until the mbox is empty? But it breaks
out of the loop if the mbox is busy or not-empty, from what
I can tell.
Could an Adaptec SCSI guru take a look at this code ? There's
probably some poor sob running EISA who's scratching his head right
now :-)
-Matt
static __inline void
ahbqueuembox(struct ahb_softc *ahb, u_int32_t mboxval, u_int attn_code)
{
u_int loopmax = 300;
while (--loopmax) {
u_int status;
status = ahb_inb(ahb, HOSTSTAT);
if ((status & HOSTSTAT_MBOX_EMPTY|HOSTSTAT_BUSY)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
!= HOSTSTAT_MBOX_EMPTY)
break;
DELAY(20);
}
if (loopmax == 0)
panic("ahb%ld: adapter not taking commands\n", ahb->unit);
ahb_outl(ahb, MBOXOUT0, mboxval);
ahb_outb(ahb, ATTN, attn_code);
}
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Wed Jan 27 17:17:18 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id RAA12763
for freebsd-current-outgoing; Wed, 27 Jan 1999 17:17:18 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.95.76.54])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA12753
for <current@FreeBSD.ORG>; Wed, 27 Jan 1999 17:17:17 -0800 (PST)
(envelope-from sgk@troutmask.apl.washington.edu)
Received: (from sgk@localhost)
by troutmask.apl.washington.edu (8.9.1/8.9.1) id RAA00914;
Wed, 27 Jan 1999 17:18:41 -0800 (PST)
(envelope-from sgk)
From: Steve Kargl <sgk@troutmask.apl.washington.edu>
Message-Id: <199901280118.RAA00914@troutmask.apl.washington.edu>
Subject: Re: Hmmm.. more on the eis ahb bug
In-Reply-To: <199901280111.RAA81035@apollo.backplane.com> from Matthew Dillon at "Jan 27, 1999 5:11: 2 pm"
To: dillon@apollo.backplane.com (Matthew Dillon)
Date: Wed, 27 Jan 1999 17:18:41 -0800 (PST)
Cc: current@FreeBSD.ORG
X-Mailer: ELM [version 2.4ME+ PL43 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
Matthew Dillon wrote:
> Could an Adaptec SCSI guru take a look at this code ? There's
> probably some poor sob running EISA who's scratching his head right
> now :-)
I'm not a guru, but I have been running a 1742 at home for 4 to
5 years without any problems. If the code could cause problems,
it must not be exercised very often.
--
Steve
finger kargl@troutmask.apl.washington.edu
http://troutmask.apl.washington.edu/~clesceri/kargl.html
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Wed Jan 27 17:41:30 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id RAA15349
for freebsd-current-outgoing; Wed, 27 Jan 1999 17:41:30 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA15342
for <current@FreeBSD.ORG>; Wed, 27 Jan 1999 17:41:27 -0800 (PST)
(envelope-from julian@whistle.com)
Received: (from daemon@localhost)
by alpo.whistle.com (8.8.5/8.8.5) id RAA14892;
Wed, 27 Jan 1999 17:36:36 -0800 (PST)
Received: from current1.whistle.com(207.76.205.22)
via SMTP by alpo.whistle.com, id smtpdO14888; Thu Jan 28 01:36:33 1999
Date: Wed, 27 Jan 1999 17:36:28 -0800 (PST)
From: Julian Elischer <julian@whistle.com>
To: Steve Kargl <sgk@troutmask.apl.washington.edu>
cc: Matthew Dillon <dillon@apollo.backplane.com>, current@FreeBSD.ORG
Subject: Re: Hmmm.. more on the eis ahb bug
In-Reply-To: <199901280118.RAA00914@troutmask.apl.washington.edu>
Message-ID: <Pine.BSF.3.95.990127173619.10889B-100000@current1.whistle.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
this is new code (CAM)
On Wed, 27 Jan 1999, Steve Kargl wrote:
> Matthew Dillon wrote:
> > Could an Adaptec SCSI guru take a look at this code ? There's
> > probably some poor sob running EISA who's scratching his head right
> > now :-)
>
> I'm not a guru, but I have been running a 1742 at home for 4 to
> 5 years without any problems. If the code could cause problems,
> it must not be exercised very often.
>
> --
> Steve
>
> finger kargl@troutmask.apl.washington.edu
> http://troutmask.apl.washington.edu/~clesceri/kargl.html
>
> To Unsubscribe: send mail to majordomo@FreeBSD.org
> with "unsubscribe freebsd-current" in the body of the message
>
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Wed Jan 27 17:41:47 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id RAA15560
for freebsd-current-outgoing; Wed, 27 Jan 1999 17:41:47 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA15555
for <current@FreeBSD.ORG>; Wed, 27 Jan 1999 17:41:45 -0800 (PST)
(envelope-from julian@whistle.com)
Received: (from daemon@localhost)
by alpo.whistle.com (8.8.5/8.8.5) id RAA14794;
Wed, 27 Jan 1999 17:33:09 -0800 (PST)
Received: from current1.whistle.com(207.76.205.22)
via SMTP by alpo.whistle.com, id smtpdT14782; Thu Jan 28 01:32:57 1999
Date: Wed, 27 Jan 1999 17:32:51 -0800 (PST)
From: Julian Elischer <julian@whistle.com>
To: John Polstra <jdp@polstra.com>
cc: dillon@apollo.backplane.com, current@FreeBSD.ORG
Subject: Re: btokup() macro in sys/malloc.h
In-Reply-To: <199901280037.QAA27694@vashon.polstra.com>
Message-ID: <Pine.BSF.3.95.990127172517.10889A-100000@current1.whistle.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
that line was confusing enough for me...
I think style (9) needs to be relaxed a bit on that
I think the bit about parns just intriduces bug "opportunities"
and certainly the bit about braces DEFINATLY introduces bugs.
Braces and parens allow humans to understand the and read the code with
less chance of misunderstanding. It doesn't help the compiler at all to
remove them and it does allow people like me (who can never get the
precedence write in different languages) to be sure of what they are
looking at.
"unambiguous to the compiler and unambiguous to the casual reader
are not the same thing". I would certainly have added the parens.
I always add then when there ar emore than two operands and one of
<< >> && == || (cast) & |
in fact I personally tend to disambiguate any operation more complicated
than a string of additions.
julian
On Wed, 27 Jan 1999, John Polstra wrote:
> In article <199901272128.NAA56542@apollo.backplane.com>,
> Matthew Dillon <dillon@apollo.backplane.com> wrote:
> > Is this parenthesization correct ?
> >
> > OLD
> >
> > #define btokup(addr) (&kmemusage[(caddr_t)(addr) - kmembase >> PAGE_SHIFT])
> >
> > NEW
> >
> > #define btokup(addr) (&kmemusage[((caddr_t)(addr) - kmembase) >> PAGE_SHIFT])
>
> The added parentheses don't make any difference, semantically. This
> change probably wouldn't meet the criteria spelled out in style(9):
>
> Unary operators don't require spaces, binary operators do. Don't use
> parentheses unless they're required for precedence, or the statement is
> really confusing without them.
>
> a = b->c[0] + ~d == (e || f) || g && h ? i : j >> 1;
> k = !(l & FLAGS);
>
> John
> --
> John Polstra jdp@polstra.com
> John D. Polstra & Co., Inc. Seattle, Washington USA
> "Nobody ever went broke underestimating the taste of the American public."
> -- H. L. Mencken
>
> To Unsubscribe: send mail to majordomo@FreeBSD.org
> with "unsubscribe freebsd-current" in the body of the message
>
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Wed Jan 27 17:48:01 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id RAA15943
for freebsd-current-outgoing; Wed, 27 Jan 1999 17:48:01 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from whistle.com (s205m131.whistle.com [207.76.205.131])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA15923
for <current@FreeBSD.ORG>; Wed, 27 Jan 1999 17:48:00 -0800 (PST)
(envelope-from archie@whistle.com)
Received: (from smap@localhost) by whistle.com (8.7.5/8.6.12) id RAA25182; Wed, 27 Jan 1999 17:47:22 -0800 (PST)
Received: from bubba.whistle.com( 207.76.205.7) by whistle.com via smap (V2.0)
id xma025178; Wed, 27 Jan 99 17:47:21 -0800
Received: (from archie@localhost) by bubba.whistle.com (8.8.7/8.6.12) id RAA19828; Wed, 27 Jan 1999 17:47:21 -0800 (PST)
From: Archie Cobbs <archie@whistle.com>
Message-Id: <199901280147.RAA19828@bubba.whistle.com>
Subject: Re: DEVFS, the time has come...
In-Reply-To: <XFMail.990128111737.doconnor@gsoft.com.au> from Daniel O'Connor at "Jan 28, 99 11:17:37 am"
To: doconnor@gsoft.com.au (Daniel O'Connor)
Date: Wed, 27 Jan 1999 17:47:20 -0800 (PST)
Cc: current@FreeBSD.ORG
X-Mailer: ELM [version 2.4ME+ PL38 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
Daniel O'Connor writes:
> On 28-Jan-99 Archie Cobbs wrote:
> > That would be easy part! :-) Something like this...
> > $ ngctl mkpeer ed0: eth_iface upstream downstream
> Heh.. It would be nice if it was automagic though..
Well, if it's automatic then you can't necessarily wire it down
the way you want to.. you can't have both at the same time.
Anyway, it's not automatic now either:
network_interfaces="lo0 ed0" # List of network interfaces (lo0 is loopback).
ifconfig_lo0="inet 127.0.0.1" # default loopback device configuration.
ifconfig_ed0="inet 192.168.1.1"
...etc...
-Archie
___________________________________________________________________________
Archie Cobbs * Whistle Communications, Inc. * http://www.whistle.com
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Wed Jan 27 17:48:14 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id RAA16161
for freebsd-current-outgoing; Wed, 27 Jan 1999 17:48:14 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.95.76.54])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA16136
for <current@FreeBSD.ORG>; Wed, 27 Jan 1999 17:48:13 -0800 (PST)
(envelope-from sgk@troutmask.apl.washington.edu)
Received: (from sgk@localhost)
by troutmask.apl.washington.edu (8.9.1/8.9.1) id RAA01110;
Wed, 27 Jan 1999 17:49:36 -0800 (PST)
(envelope-from sgk)
From: Steve Kargl <sgk@troutmask.apl.washington.edu>
Message-Id: <199901280149.RAA01110@troutmask.apl.washington.edu>
Subject: Re: Hmmm.. more on the eis ahb bug
In-Reply-To: <Pine.BSF.3.95.990127173619.10889B-100000@current1.whistle.com> from Julian Elischer at "Jan 27, 1999 5:36:28 pm"
To: julian@whistle.com (Julian Elischer)
Date: Wed, 27 Jan 1999 17:49:36 -0800 (PST)
Cc: dillon@apollo.backplane.com, current@FreeBSD.ORG
X-Mailer: ELM [version 2.4ME+ PL43 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
Julian Elischer wrote:
> this is new code (CAM)
>
Whoops. Well, I've been running CAM at home 5 to 6 months
without a problem.
>
> On Wed, 27 Jan 1999, Steve Kargl wrote:
>
> > Matthew Dillon wrote:
> > > Could an Adaptec SCSI guru take a look at this code ? There's
> > > probably some poor sob running EISA who's scratching his head right
> > > now :-)
> >
> > I'm not a guru, but I have been running a 1742 at home for 4 to
> > 5 years without any problems. If the code could cause problems,
> > it must not be exercised very often.
> >
--
Steve
finger kargl@troutmask.apl.washington.edu
http://troutmask.apl.washington.edu/~clesceri/kargl.html
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Wed Jan 27 18:01:54 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id SAA17573
for freebsd-current-outgoing; Wed, 27 Jan 1999 18:01:54 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from whistle.com (s205m131.whistle.com [207.76.205.131])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA17568
for <current@FreeBSD.ORG>; Wed, 27 Jan 1999 18:01:53 -0800 (PST)
(envelope-from archie@whistle.com)
Received: (from smap@localhost) by whistle.com (8.7.5/8.6.12) id SAA25378; Wed, 27 Jan 1999 18:01:22 -0800 (PST)
Received: from bubba.whistle.com( 207.76.205.7) by whistle.com via smap (V2.0)
id xma025374; Wed, 27 Jan 99 18:00:54 -0800
Received: (from archie@localhost) by bubba.whistle.com (8.8.7/8.6.12) id SAA19958; Wed, 27 Jan 1999 18:00:54 -0800 (PST)
From: Archie Cobbs <archie@whistle.com>
Message-Id: <199901280200.SAA19958@bubba.whistle.com>
Subject: Re: btokup() macro in sys/malloc.h
In-Reply-To: <199901280045.QAA77982@apollo.backplane.com> from Matthew Dillon at "Jan 27, 99 04:45:31 pm"
To: dillon@apollo.backplane.com (Matthew Dillon)
Date: Wed, 27 Jan 1999 18:00:54 -0800 (PST)
Cc: current@FreeBSD.ORG
X-Mailer: ELM [version 2.4ME+ PL38 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
Matthew Dillon writes:
> :> #define btokup(addr) (&kmemusage[((caddr_t)(addr) - kmembase) >> PAGE_SHIFT])
> :
> :The added parentheses don't make any difference, semantically. This
> :change probably wouldn't meet the criteria spelled out in style(9):
>
> Then style(9) needs to be updated, because we have to add parenthesis
> to be able to not get warnings with -Wall.
Please do go ahead and update it.. the experts agree!
-Archie
___________________________________________________________________________
Archie Cobbs * Whistle Communications, Inc. * http://www.whistle.com
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Wed Jan 27 18:05:27 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id SAA18029
for freebsd-current-outgoing; Wed, 27 Jan 1999 18:05:27 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from whistle.com (s205m131.whistle.com [207.76.205.131])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA18024
for <current@FreeBSD.ORG>; Wed, 27 Jan 1999 18:05:26 -0800 (PST)
(envelope-from archie@whistle.com)
Received: (from smap@localhost) by whistle.com (8.7.5/8.6.12) id SAA25444; Wed, 27 Jan 1999 18:04:52 -0800 (PST)
Received: from bubba.whistle.com( 207.76.205.7) by whistle.com via smap (V2.0)
id xma025440; Wed, 27 Jan 99 18:04:45 -0800
Received: (from archie@localhost) by bubba.whistle.com (8.8.7/8.6.12) id SAA19979; Wed, 27 Jan 1999 18:04:45 -0800 (PST)
From: Archie Cobbs <archie@whistle.com>
Message-Id: <199901280204.SAA19979@bubba.whistle.com>
Subject: Re: kern/subr_scanf array index of signed char
In-Reply-To: <199901272135.NAA57832@apollo.backplane.com> from Matthew Dillon at "Jan 27, 99 01:35:08 pm"
To: dillon@apollo.backplane.com (Matthew Dillon)
Date: Wed, 27 Jan 1999 18:04:45 -0800 (PST)
Cc: current@FreeBSD.ORG
X-Mailer: ELM [version 2.4ME+ PL38 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
Matthew Dillon writes:
> goto match_failure;
> } else {
> p0 = p = va_arg(ap, char *);
> - while (ccltab[*inp]) {
> + while (ccltab[(int)(unsigned char)*inp]) {
> inr--;
> *p++ = *inp++;
> if (--width == 0)
Just curious.. why do you need the "(int)" cast?
-Archie
___________________________________________________________________________
Archie Cobbs * Whistle Communications, Inc. * http://www.whistle.com
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Wed Jan 27 18:07:23 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id SAA18403
for freebsd-current-outgoing; Wed, 27 Jan 1999 18:07:23 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA18391
for <current@FreeBSD.ORG>; Wed, 27 Jan 1999 18:07:19 -0800 (PST)
(envelope-from dillon@apollo.backplane.com)
Received: (from dillon@localhost)
by apollo.backplane.com (8.9.2/8.9.1) id SAA88572;
Wed, 27 Jan 1999 18:07:18 -0800 (PST)
(envelope-from dillon)
Date: Wed, 27 Jan 1999 18:07:18 -0800 (PST)
From: Matthew Dillon <dillon@apollo.backplane.com>
Message-Id: <199901280207.SAA88572@apollo.backplane.com>
To: Archie Cobbs <archie@whistle.com>
Cc: current@FreeBSD.ORG
Subject: Re: kern/subr_scanf array index of signed char
References: <199901280204.SAA19979@bubba.whistle.com>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
:Matthew Dillon writes:
:> goto match_failure;
:> } else {
:> p0 = p = va_arg(ap, char *);
:> - while (ccltab[*inp]) {
:> + while (ccltab[(int)(unsigned char)*inp]) {
:> inr--;
:> *p++ = *inp++;
:> if (--width == 0)
:
:Just curious.. why do you need the "(int)" cast?
:
:-Archie
Actually, it could very well be that I don't. I didn't want to spend
the time to check to see if the compiler warned on unsigned-char array
indexes. You can change it back if unsigned char array indexes do not
produce a warning.
-Matt
:___________________________________________________________________________
:Archie Cobbs * Whistle Communications, Inc. * http://www.whistle.com
:
:To Unsubscribe: send mail to majordomo@FreeBSD.org
:with "unsubscribe freebsd-current" in the body of the message
:
Matthew Dillon
<dillon@backplane.com>
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Wed Jan 27 18:07:50 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id SAA18455
for freebsd-current-outgoing; Wed, 27 Jan 1999 18:07:50 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from bright.fx.genx.net (bright.fx.genx.net [206.64.4.154])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA18450
for <current@FreeBSD.ORG>; Wed, 27 Jan 1999 18:07:47 -0800 (PST)
(envelope-from bright@hotjobs.com)
Received: from localhost (bright@localhost)
by bright.fx.genx.net (8.9.1/8.9.1) with ESMTP id VAA19763;
Wed, 27 Jan 1999 21:14:22 -0500 (EST)
(envelope-from bright@hotjobs.com)
X-Authentication-Warning: bright.fx.genx.net: bright owned process doing -bs
Date: Wed, 27 Jan 1999 21:14:22 -0500 (EST)
From: Alfred Perlstein <bright@hotjobs.com>
X-Sender: bright@bright.fx.genx.net
To: Archie Cobbs <archie@whistle.com>
cc: Matthew Dillon <dillon@apollo.backplane.com>, current@FreeBSD.ORG
Subject: Re: kern/subr_scanf array index of signed char
In-Reply-To: <199901280204.SAA19979@bubba.whistle.com>
Message-ID: <Pine.BSF.4.05.9901272113380.81323-100000@bright.fx.genx.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
On Wed, 27 Jan 1999, Archie Cobbs wrote:
> Matthew Dillon writes:
> > - while (ccltab[*inp]) {
> > + while (ccltab[(int)(unsigned char)*inp]) {
>
> Just curious.. why do you need the "(int)" cast?
avoids a warning.
-Alfred
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Wed Jan 27 18:11:34 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id SAA18918
for freebsd-current-outgoing; Wed, 27 Jan 1999 18:11:34 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA18912
for <current@FreeBSD.ORG>; Wed, 27 Jan 1999 18:11:32 -0800 (PST)
(envelope-from dillon@apollo.backplane.com)
Received: (from dillon@localhost)
by apollo.backplane.com (8.9.2/8.9.1) id SAA89748;
Wed, 27 Jan 1999 18:11:31 -0800 (PST)
(envelope-from dillon)
Date: Wed, 27 Jan 1999 18:11:31 -0800 (PST)
From: Matthew Dillon <dillon@apollo.backplane.com>
Message-Id: <199901280211.SAA89748@apollo.backplane.com>
To: Matthew Dillon <dillon@apollo.backplane.com>
Cc: Archie Cobbs <archie@whistle.com>, current@FreeBSD.ORG
Subject: Re: kern/subr_scanf array index of signed char
References: <199901280204.SAA19979@bubba.whistle.com> <199901280207.SAA88572@apollo.backplane.com>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
::> - while (ccltab[*inp]) {
::> + while (ccltab[(int)(unsigned char)*inp]) {
:
: Actually, it could very well be that I don't. I didn't want to spend
: the time to check to see if the compiler warned on unsigned-char array
: indexes. You can change it back if unsigned char array indexes do not
: produce a warning.
Eer, by 'change it back' I meant 'remove the (int)'. You have to keep
the (unsigned char) cast, of course.
-Matt
Matthew Dillon
<dillon@backplane.com>
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Wed Jan 27 18:16:14 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id SAA19213
for freebsd-current-outgoing; Wed, 27 Jan 1999 18:16:14 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA19208
for <current@FreeBSD.ORG>; Wed, 27 Jan 1999 18:16:12 -0800 (PST)
(envelope-from dillon@apollo.backplane.com)
Received: (from dillon@localhost)
by apollo.backplane.com (8.9.2/8.9.1) id SAA90783;
Wed, 27 Jan 1999 18:16:12 -0800 (PST)
(envelope-from dillon)
Date: Wed, 27 Jan 1999 18:16:12 -0800 (PST)
From: Matthew Dillon <dillon@apollo.backplane.com>
Message-Id: <199901280216.SAA90783@apollo.backplane.com>
To: current@FreeBSD.ORG
Subject: Changing bzero, bcopy, memset, memcpy, etc... prototypes
References: <Pine.BSF.4.05.9901272113380.81323-100000@bright.fx.genx.net>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
I would like to propose changing the prototype for the kernel memory
zeroing and copying routines.
Basically, the problem is that a whole hellofalot of drivers run
bzero and bcopy on volatile memory. The only way to remove the
warnings is to volatilize bzero and bcopy.
The compiler will, I believe, upgrade a pointer to a non-volatile
(aka char *) to a pointer to a volatile (aka volatile char *) without
issuing any warnings.
This change should be fully backwards compatible.
So I propose changing
FROM
void bzero __P((void *buf, size_t len));
void bcopy __P((const void *from, void *to, size_t len));
TO
void bzero __P((volatile void *buf, size_t len));
void bcopy __P((volatile const void *from, volatile void *to, size_t len));
Comments?
-Matt
Matthew Dillon
<dillon@backplane.com>
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Wed Jan 27 18:22:49 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id SAA20047
for freebsd-current-outgoing; Wed, 27 Jan 1999 18:22:49 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from khavrinen.lcs.mit.edu (khavrinen.lcs.mit.edu [18.24.4.193])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA20033
for <current@FreeBSD.ORG>; Wed, 27 Jan 1999 18:22:45 -0800 (PST)
(envelope-from wollman@khavrinen.lcs.mit.edu)
Received: (from wollman@localhost)
by khavrinen.lcs.mit.edu (8.9.1/8.9.1) id VAA14212;
Wed, 27 Jan 1999 21:22:43 -0500 (EST)
(envelope-from wollman)
Date: Wed, 27 Jan 1999 21:22:43 -0500 (EST)
From: Garrett Wollman <wollman@khavrinen.lcs.mit.edu>
Message-Id: <199901280222.VAA14212@khavrinen.lcs.mit.edu>
To: Archie Cobbs <archie@whistle.com>
Cc: current@FreeBSD.ORG
Subject: Re: btokup() macro in sys/malloc.h
In-Reply-To: <199901280200.SAA19958@bubba.whistle.com>
References: <199901280045.QAA77982@apollo.backplane.com>
<199901280200.SAA19958@bubba.whistle.com>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
<<On Wed, 27 Jan 1999 18:00:54 -0800 (PST), Archie Cobbs <archie@whistle.com> said:
> Please do go ahead and update it.. the experts agree!
I haven't seen any experts involved in this discussion yet. It's
probably after bedtime down there in oz.
-GAWollman
--
Garrett A. Wollman | O Siem / We are all family / O Siem / We're all the same
wollman@lcs.mit.edu | O Siem / The fires of freedom
Opinions not those of| Dance in the burning flame
MIT, LCS, CRS, or NSA| - Susan Aglukark and Chad Irschick
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Wed Jan 27 18:22:56 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id SAA20074
for freebsd-current-outgoing; Wed, 27 Jan 1999 18:22:56 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from whistle.com (s205m131.whistle.com [207.76.205.131])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA20061
for <current@FreeBSD.ORG>; Wed, 27 Jan 1999 18:22:51 -0800 (PST)
(envelope-from archie@whistle.com)
Received: (from smap@localhost) by whistle.com (8.7.5/8.6.12) id SAA25643; Wed, 27 Jan 1999 18:22:22 -0800 (PST)
Received: from bubba.whistle.com( 207.76.205.7) by whistle.com via smap (V2.0)
id xma025637; Wed, 27 Jan 99 18:22:13 -0800
Received: (from archie@localhost) by bubba.whistle.com (8.8.7/8.6.12) id SAA20135; Wed, 27 Jan 1999 18:22:13 -0800 (PST)
From: Archie Cobbs <archie@whistle.com>
Message-Id: <199901280222.SAA20135@bubba.whistle.com>
Subject: Re: kern/subr_scanf array index of signed char
In-Reply-To: <Pine.BSF.4.05.9901272113380.81323-100000@bright.fx.genx.net> from Alfred Perlstein at "Jan 27, 99 09:14:22 pm"
To: bright@hotjobs.com (Alfred Perlstein)
Date: Wed, 27 Jan 1999 18:22:13 -0800 (PST)
Cc: current@FreeBSD.ORG
X-Mailer: ELM [version 2.4ME+ PL38 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
Alfred Perlstein writes:
> > Matthew Dillon writes:
> > > - while (ccltab[*inp]) {
> > > + while (ccltab[(int)(unsigned char)*inp]) {
> >
> > Just curious.. why do you need the "(int)" cast?
>
> avoids a warning.
No it doesn't. The "(unsigned char)" avoids the warning:
$ cat > foo.c
int foo(int *array, unsigned char index) { return array[index]; }
$ gcc -c -Wall -o foo foo.c
$
-Archie
___________________________________________________________________________
Archie Cobbs * Whistle Communications, Inc. * http://www.whistle.com
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Wed Jan 27 18:27:34 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id SAA20750
for freebsd-current-outgoing; Wed, 27 Jan 1999 18:27:34 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from alcanet.com.au (border.alcanet.com.au [203.62.196.10])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA20733
for <current@FreeBSD.ORG>; Wed, 27 Jan 1999 18:27:31 -0800 (PST)
(envelope-from peter.jeremy@auss2.alcatel.com.au)
Received: by border.alcanet.com.au id <40347>; Thu, 28 Jan 1999 13:17:53 +1100
Date: Thu, 28 Jan 1999 13:27:16 +1100
From: Peter Jeremy <peter.jeremy@auss2.alcatel.com.au>
Subject: Re: btokup() macro in sys/malloc.h
To: current@FreeBSD.ORG
Message-Id: <99Jan28.131753est.40347@border.alcanet.com.au>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
Matthew Dillon <dillon@apollo.backplane.com> wrote:
>:> NEW
>:>
>:> #define btokup(addr) (&kmemusage[((caddr_t)(addr) - kmembase) >> PAGE_SHIFT])
>:
>:The added parentheses don't make any difference, semantically. This
>:change probably wouldn't meet the criteria spelled out in style(9):
>
> Then style(9) needs to be updated, because we have to add parenthesis
> to be able to not get warnings with -Wall.
I'll support that. The example given in style(9):
a = b->c[0] + ~d == (e || f) || g && h ? i : j >> 1;
should rate as an entry in the Obfuscated C competition rather than
an example of maintainable code.
style(9) should emphasize legibility and maintainability, rather than
minimizing the number of extraneous (from the compiler's perspective)
parenthesis. The code you're writing has to be maintained for many years
- and the maintainers will not always have your in-depth expertise.
The code also forms a `reference implementation' for someone who wants
to do something similar.
Peter
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Wed Jan 27 18:28:51 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id SAA21012
for freebsd-current-outgoing; Wed, 27 Jan 1999 18:28:51 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from khavrinen.lcs.mit.edu (khavrinen.lcs.mit.edu [18.24.4.193])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA21003
for <freebsd-current@FreeBSD.ORG>; Wed, 27 Jan 1999 18:28:49 -0800 (PST)
(envelope-from wollman@khavrinen.lcs.mit.edu)
Received: (from wollman@localhost)
by khavrinen.lcs.mit.edu (8.9.1/8.9.1) id VAA14247;
Wed, 27 Jan 1999 21:28:47 -0500 (EST)
(envelope-from wollman)
Date: Wed, 27 Jan 1999 21:28:47 -0500 (EST)
From: Garrett Wollman <wollman@khavrinen.lcs.mit.edu>
Message-Id: <199901280228.VAA14247@khavrinen.lcs.mit.edu>
To: Robert Watson <robert@cyrus.watson.org>
Cc: freebsd-current@FreeBSD.ORG
Subject: Naming files in sys/kern
In-Reply-To: <Pine.BSF.3.96.990127181407.8092A-100000@fledge.watson.org>
References: <Pine.BSF.3.96.990127181407.8092A-100000@fledge.watson.org>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
<<On Wed, 27 Jan 1999 18:30:15 -0500 (EST), Robert Watson <robert@cyrus.watson.org> said:
> It's not clear to me, when thinking of introducing a new file (say, for
> auditing support :), what I should name it. Would it be kern_audit.c or
> sys_audit.c?
Depends on what it is auditing. If it only auditing the basic I/O
operations, then it would go in sys_*.c. If it's a more general
kernel facility, then it goes in kern_*.c.
> Or, if it is POSIX.1e, would it go into a /usr/src/sys/posix1e
> directory as the posix4 realtime stuff did (assuming that support
> for additional features from that posix draft were going to be
> forthcoming)?
Giving the unhelpful tendency of Project 1003 to renumber its
standards after-the-fact (or fold them into the main 1003.1 document),
I would suggest against using committee identifiers like this.
If it's controlled by a compile-time option, it should probably be
called POSIX_AUDITING rather than POSIX_1e or something of that
nature, since your statement implies that there is a useful
granularity of features.
-GAWollman
--
Garrett A. Wollman | O Siem / We are all family / O Siem / We're all the same
wollman@lcs.mit.edu | O Siem / The fires of freedom
Opinions not those of| Dance in the burning flame
MIT, LCS, CRS, or NSA| - Susan Aglukark and Chad Irschick
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Wed Jan 27 18:30:30 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id SAA21384
for freebsd-current-outgoing; Wed, 27 Jan 1999 18:30:30 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from whistle.com (s205m131.whistle.com [207.76.205.131])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA21371
for <current@FreeBSD.ORG>; Wed, 27 Jan 1999 18:30:28 -0800 (PST)
(envelope-from archie@whistle.com)
Received: (from smap@localhost) by whistle.com (8.7.5/8.6.12) id SAA25722; Wed, 27 Jan 1999 18:29:52 -0800 (PST)
Received: from bubba.whistle.com( 207.76.205.7) by whistle.com via smap (V2.0)
id xma025717; Wed, 27 Jan 99 18:29:33 -0800
Received: (from archie@localhost) by bubba.whistle.com (8.8.7/8.6.12) id SAA20207; Wed, 27 Jan 1999 18:29:33 -0800 (PST)
From: Archie Cobbs <archie@whistle.com>
Message-Id: <199901280229.SAA20207@bubba.whistle.com>
Subject: Re: btokup() macro in sys/malloc.h
In-Reply-To: <199901280222.VAA14212@khavrinen.lcs.mit.edu> from Garrett Wollman at "Jan 27, 99 09:22:43 pm"
To: wollman@khavrinen.lcs.mit.edu (Garrett Wollman)
Date: Wed, 27 Jan 1999 18:29:33 -0800 (PST)
Cc: current@FreeBSD.ORG
X-Mailer: ELM [version 2.4ME+ PL38 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
Garrett Wollman writes:
> > Please do go ahead and update it.. the experts agree!
>
> I haven't seen any experts involved in this discussion yet. It's
> probably after bedtime down there in oz.
It was discussed before a couple of weeks ago, and I didn't hear
anybody on the other side. I could be mistaken though.
Anyway, if we're going to -Wall'ify the kernel (as we should)
then we need to update sytle(9) to reflect that.
In fact, style(9) should say:
If at all possible, your code should compile without warnings
when the gcc -Wall flag is given.
As it stands now (and I QUOTE!) it says:
Don't use parentheses unless they're required for precedence, or
the statement is really confusing without them.
a = b->c[0] + ~d == (e || f) || g && h ? i : j >> 1;
That's ridiculous!
If you're telling me that line is not 'really confusing' then..
hell, I don't know what. I guess I just strongly disagree.
-Archie
___________________________________________________________________________
Archie Cobbs * Whistle Communications, Inc. * http://www.whistle.com
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Wed Jan 27 18:31:39 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id SAA21458
for freebsd-current-outgoing; Wed, 27 Jan 1999 18:31:39 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from allegro.lemis.com (allegro.lemis.com [192.109.197.134])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA21442
for <freebsd-current@FreeBSD.ORG>; Wed, 27 Jan 1999 18:31:35 -0800 (PST)
(envelope-from grog@freebie.lemis.com)
Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137])
by allegro.lemis.com (8.9.1/8.9.0) with ESMTP id NAA16647;
Thu, 28 Jan 1999 13:01:32 +1030 (CST)
Received: (from grog@localhost)
by freebie.lemis.com (8.9.2/8.9.0) id NAA05619;
Thu, 28 Jan 1999 13:01:32 +1030 (CST)
Date: Thu, 28 Jan 1999 13:01:31 +1030
From: Greg Lehey <grog@lemis.com>
To: "Mike O'Dell" <mo@servo.ccr.org>,
Garrett Wollman <wollman@khavrinen.lcs.mit.edu>
Cc: freebsd-current@FreeBSD.ORG
Subject: Re: "Argument by Authority"
Message-ID: <19990128130131.J4819@freebie.lemis.com>
References: <199901272004.PAA08973@khavrinen.lcs.mit.edu> <199901272059.PAA50894@servo.ccr.org> <199901271938.OAA50778@servo.ccr.org> <199901272004.PAA08973@khavrinen.lcs.mit.edu> <199901271938.OAA50778@servo.ccr.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.95.1i
In-Reply-To: <199901271938.OAA50778@servo.ccr.org>; from Mike O'Dell on Wed, Jan 27, 1999 at 02:38:23PM -0500
WWW-Home-Page: http://www.lemis.com/~grog
Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia
Phone: +61-8-8388-8286
Fax: +61-8-8388-8725
Mobile: +61-41-739-7062
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
On Wednesday, 27 January 1999 at 14:38:23 -0500, Mike O'Dell wrote:
>
> just for a calibration,
> i asked Dennis Ritchie his opinion of "the right behavior"
>
> his comment about posix might be the trump card, although
> i'd like to see chapter and verse if that's the case.
>
> for what it's worth.
>
> -mo
>
>
> ------- Forwarded Message
>
> MessageName: (Message 47)
> From: dmr@plan9.bell-labs.com
> Date: Wed, 27 Jan 1999 14:30:59 -0500
> To: mo@servo.ccr.org
>
> Well the research systems from v7 (just looked) through Brazil
> produce no diagnostic. So much for "should."
>
> Irix complains, suppressible with -f. I wonder if it's in posix?
>
> Dennis
>
> ------- End of Forwarded Message
On Wednesday, 27 January 1999 at 15:04:38 -0500, Garrett Wollman wrote:
> <<On Wed, 27 Jan 1999 14:38:23 -0500, "Mike O'Dell" <mo@servo.ccr.org> said:
>
>> i asked Dennis Ritchie his opinion of "the right behavior"
>
> The right behavior of what?
>
> -GAWollman
On Wednesday, 27 January 1999 at 15:59:13 -0500, Mike O'Dell wrote:
>
> i asked his notion of the right behavior of "rm"
Well, between you and dmr, you manage to remain completely obfuscated.
How about including some of the previous history?
Are you talking about whether rm without -f will fail when it can't do
its job? Even that doesn't seem to make much sense.
Greg
--
See complete headers for address, home page and phone numbers
finger grog@lemis.com for PGP public key
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Wed Jan 27 18:33:10 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id SAA21574
for freebsd-current-outgoing; Wed, 27 Jan 1999 18:33:10 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA21568
for <current@FreeBSD.ORG>; Wed, 27 Jan 1999 18:33:09 -0800 (PST)
(envelope-from dillon@apollo.backplane.com)
Received: (from dillon@localhost)
by apollo.backplane.com (8.9.2/8.9.1) id SAA92303;
Wed, 27 Jan 1999 18:33:01 -0800 (PST)
(envelope-from dillon)
Date: Wed, 27 Jan 1999 18:33:01 -0800 (PST)
From: Matthew Dillon <dillon@apollo.backplane.com>
Message-Id: <199901280233.SAA92303@apollo.backplane.com>
To: Peter Jeremy <peter.jeremy@auss2.alcatel.com.au>
Cc: current@FreeBSD.ORG
Subject: Re: btokup() macro in sys/malloc.h
References: <99Jan28.131753est.40347@border.alcanet.com.au>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
:Matthew Dillon <dillon@apollo.backplane.com> wrote:
:>:> NEW
:>:>
:>:> #define btokup(addr) (&kmemusage[((caddr_t)(addr) - kmembase) >> PAGE_SHIFT])
:>:
:>:The added parentheses don't make any difference, semantically. This
:>:change probably wouldn't meet the criteria spelled out in style(9):
:>
:> Then style(9) needs to be updated, because we have to add parenthesis
:> to be able to not get warnings with -Wall.
:
:I'll support that. The example given in style(9):
:
: a = b->c[0] + ~d == (e || f) || g && h ? i : j >> 1;
:
:should rate as an entry in the Obfuscated C competition rather than
:an example of maintainable code.
:
:style(9) should emphasize legibility and maintainability, rather than
:minimizing the number of extraneous (from the compiler's perspective)
:parenthesis. The code you're writing has to be maintained for many years
:- and the maintainers will not always have your in-depth expertise.
:The code also forms a `reference implementation' for someone who wants
:to do something similar.
:
:Peter
As far as parenthesis go, it's irrelevant because -Wall pretty much
covers the most common mistakes. If your code compiles without generating
a warning, your parenthesization is in good shape.
Braces and indentation and other purely visual effects are a different
matter.
-Matt
Matthew Dillon
<dillon@backplane.com>
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Wed Jan 27 18:43:33 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id SAA22680
for freebsd-current-outgoing; Wed, 27 Jan 1999 18:43:33 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from janus.syracuse.net (janus.syracuse.net [205.232.47.15])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA22668
for <current@FreeBSD.ORG>; Wed, 27 Jan 1999 18:43:25 -0800 (PST)
(envelope-from green@unixhelp.org)
Received: from localhost (green@localhost)
by janus.syracuse.net (8.8.8/8.8.7) with ESMTP id VAA11735;
Wed, 27 Jan 1999 21:43:22 -0500 (EST)
Date: Wed, 27 Jan 1999 21:43:21 -0500 (EST)
From: Brian Feldman <green@unixhelp.org>
X-Sender: green@janus.syracuse.net
To: Peter Jeremy <peter.jeremy@auss2.alcatel.com.au>
cc: current@FreeBSD.ORG
Subject: Re: btokup() macro in sys/malloc.h
In-Reply-To: <99Jan28.131753est.40347@border.alcanet.com.au>
Message-ID: <Pine.BSF.4.05.9901272141490.10509-100000@janus.syracuse.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
On Thu, 28 Jan 1999, Peter Jeremy wrote:
> Matthew Dillon <dillon@apollo.backplane.com> wrote:
> >:> NEW
> >:>
> >:> #define btokup(addr) (&kmemusage[((caddr_t)(addr) - kmembase) >> PAGE_SHIFT])
> >:
> >:The added parentheses don't make any difference, semantically. This
> >:change probably wouldn't meet the criteria spelled out in style(9):
> >
> > Then style(9) needs to be updated, because we have to add parenthesis
> > to be able to not get warnings with -Wall.
>
> I'll support that. The example given in style(9):
>
> a = b->c[0] + ~d == (e || f) || g && h ? i : j >> 1;
>
> should rate as an entry in the Obfuscated C competition rather than
> an example of maintainable code.
>
> style(9) should emphasize legibility and maintainability, rather than
> minimizing the number of extraneous (from the compiler's perspective)
> parenthesis. The code you're writing has to be maintained for many years
> - and the maintainers will not always have your in-depth expertise.
> The code also forms a `reference implementation' for someone who wants
> to do something similar.
Here's another vote from someone who uses liberal parentheses! I think of it
like this: it may be correct, but if I can't understand it after I've written
it, what good is the code? Saving a few bytes isn't worth obfuscating code.
Style(9) should /dons flame-retardant suit/ encourage usage of extra parens
that make code more readable to humans.
>
> Peter
>
> To Unsubscribe: send mail to majordomo@FreeBSD.org
> with "unsubscribe freebsd-current" in the body of the message
>
Brian Feldman _ __ ___ ___ ___
green@unixhelp.org _ __ ___ | _ ) __| \
http://www.freebsd.org/ _ __ ___ ____ | _ \__ \ |) |
FreeBSD: The Power to Serve! _ __ ___ ____ _____ |___/___/___/
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Wed Jan 27 18:50:03 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id SAA23557
for freebsd-current-outgoing; Wed, 27 Jan 1999 18:50:03 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from bright.fx.genx.net (bright.fx.genx.net [206.64.4.154])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA23484
for <current@FreeBSD.ORG>; Wed, 27 Jan 1999 18:50:00 -0800 (PST)
(envelope-from bright@hotjobs.com)
Received: from localhost (bright@localhost)
by bright.fx.genx.net (8.9.1/8.9.1) with ESMTP id VAA19805;
Wed, 27 Jan 1999 21:56:39 -0500 (EST)
(envelope-from bright@hotjobs.com)
X-Authentication-Warning: bright.fx.genx.net: bright owned process doing -bs
Date: Wed, 27 Jan 1999 21:56:39 -0500 (EST)
From: Alfred Perlstein <bright@hotjobs.com>
X-Sender: bright@bright.fx.genx.net
To: Archie Cobbs <archie@whistle.com>
cc: current@FreeBSD.ORG
Subject: Re: kern/subr_scanf array index of signed char
In-Reply-To: <199901280222.SAA20135@bubba.whistle.com>
Message-ID: <Pine.BSF.4.05.9901272143350.81323-100000@bright.fx.genx.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
On Wed, 27 Jan 1999, Archie Cobbs wrote:
> Alfred Perlstein writes:
> > avoids a warning.
>
> No it doesn't. The "(unsigned char)" avoids the warning:
>
> $ cat > foo.c
> int foo(int *array, unsigned char index) { return array[index]; }
> $ gcc -c -Wall -o foo foo.c
> $
doh' yes, it is when you use a signed char that i've had warnings.
-Alfred
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Wed Jan 27 18:51:26 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id SAA23920
for freebsd-current-outgoing; Wed, 27 Jan 1999 18:51:26 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.26.10.9])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA23892
for <current@FreeBSD.ORG>; Wed, 27 Jan 1999 18:51:22 -0800 (PST)
(envelope-from bde@godzilla.zeta.org.au)
Received: (from bde@localhost)
by godzilla.zeta.org.au (8.8.7/8.8.7) id NAA23946;
Thu, 28 Jan 1999 13:51:15 +1100
Date: Thu, 28 Jan 1999 13:51:15 +1100
From: Bruce Evans <bde@zeta.org.au>
Message-Id: <199901280251.NAA23946@godzilla.zeta.org.au>
To: archie@whistle.com, wollman@khavrinen.lcs.mit.edu
Subject: Re: btokup() macro in sys/malloc.h
Cc: current@FreeBSD.ORG
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
>Anyway, if we're going to -Wall'ify the kernel (as we should)
>then we need to update sytle(9) to reflect that.
>
>In fact, style(9) should say:
>
> If at all possible, your code should compile without warnings
> when the gcc -Wall flag is given.
Avoiding warnings is more an engineering than a stylistic matter.
You turn on warnings to help avoid bugs that the compiler can find
easily. You ask everyone else to turn on warnings so that compiling
their sources with the same CFLAGS as your sources doesn't cause a
spew of warnings.
>As it stands now (and I QUOTE!) it says:
>
> Don't use parentheses unless they're required for precedence, or
> the statement is really confusing without them.
>
> a = b->c[0] + ~d == (e || f) || g && h ? i : j >> 1;
>
>That's ridiculous!
I think it's trying to be funny. This makes it a bad example either
way. Perhaps its point is that complicated expressions can't be made
less confusing by adding parentheses.
Bruce
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Wed Jan 27 18:52:49 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id SAA24391
for freebsd-current-outgoing; Wed, 27 Jan 1999 18:52:49 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from krdl.org.sg (rodin.krdl.org.sg [137.132.252.27])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA24380
for <current@freebsd.org>; Wed, 27 Jan 1999 18:52:46 -0800 (PST)
(envelope-from joerg@mailbox.iss.nus.sg)
Received: from mailhost.krdl.org.sg (mailbox.krdl.org.sg [137.132.247.30])
by krdl.org.sg (8.9.2/8.9.2) with ESMTP id KAA04898;
Thu, 28 Jan 1999 10:58:03 +0800 (SGT)
Received: from negara.nus.sg (negara [137.132.248.175])
by mailhost.krdl.org.sg (8.9.0/8.9.0) with ESMTP id KAA01267;
Thu, 28 Jan 1999 10:52:06 +0800 (SGT)
Received: (from joerg@localhost)
by negara.nus.sg (8.9.1b+Sun/8.9.1) id DAA01537;
Thu, 28 Jan 1999 03:53:36 +0800 (SGT)
Message-ID: <19990128035336.V496@krdl.org.sg>
Date: Thu, 28 Jan 1999 03:53:36 +0800
From: "Joerg B. Micheel" <joerg@krdl.org.sg>
To: Matthew Dillon <dillon@apollo.backplane.com>, current@FreeBSD.ORG
Subject: Re: bug in netatm/atm_cm.c ?
References: <199901272215.OAA63874@apollo.backplane.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
In-Reply-To: <199901272215.OAA63874@apollo.backplane.com>; from Matthew Dillon on Wed, Jan 27, 1999 at 02:15:11PM -0800
Organization: Kent Ridge Digital Labs, Singapore
Project: SingAREN, the Singapore Advanced Research and Education Network
Operating-System: ... drained by Solaris 7 Intel
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
On Wed, Jan 27, 1999 at 02:15:11PM -0800, Matthew Dillon wrote:
> around line 2192. Shouldn't this be ap->aal.type == ATM_AAL5 ???
It definitely should, as the } else { branch on line 2211 is never reached.
The reason it has not been discovered is that noone hardly ever uses anything
other than AAL5 (as of today) and this code always defaults to it. Just wondering
why nobody ever got a compiler warning with the AAL4 code never reached.
Joerg
--
Joerg B. Micheel Email: <joerg@krdl.org.sg>
SingAREN Technology Center Phone: +65 8742582
Kent Ridge Digital Labs, Rm 3-65, C041 Fax: +65 7744990
21 Heng Mui Keng Terrace Pager: +65 96016020
Singapore 119613 Plan: Troubleshooting ATM
Republic of Singapore Networks and Applications
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Wed Jan 27 19:00:44 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id TAA25669
for freebsd-current-outgoing; Wed, 27 Jan 1999 19:00:44 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from cain.gsoft.com.au (genesi.lnk.telstra.net [139.130.136.161])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA25635
for <current@FreeBSD.ORG>; Wed, 27 Jan 1999 19:00:34 -0800 (PST)
(envelope-from doconnor@gsoft.com.au)
Received: from lot.gsoft.com.au (doconnor@lot.gsoft.com.au [203.38.152.106])
by cain.gsoft.com.au (8.8.8/8.8.8) with ESMTP id NAA28211;
Thu, 28 Jan 1999 13:30:27 +1030 (CST)
(envelope-from doconnor@gsoft.com.au)
Message-ID: <XFMail.990128133917.doconnor@gsoft.com.au>
X-Mailer: XFMail 1.3 [p0] on FreeBSD
X-Priority: 3 (Normal)
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 8bit
MIME-Version: 1.0
In-Reply-To: <199901280147.RAA19828@bubba.whistle.com>
Date: Thu, 28 Jan 1999 13:39:17 +1030 (CST)
From: "Daniel O'Connor" <doconnor@gsoft.com.au>
To: Archie Cobbs <archie@whistle.com>
Subject: Re: DEVFS, the time has come...
Cc: current@FreeBSD.ORG
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
On 28-Jan-99 Archie Cobbs wrote:
> Well, if it's automatic then you can't necessarily wire it down
> the way you want to.. you can't have both at the same time.
>
> Anyway, it's not automatic now either:
>
> network_interfaces="lo0 ed0" # List of network interfaces (lo0 is loopback).
> ifconfig_lo0="inet 127.0.0.1" # default loopback device configuration.
> ifconfig_ed0="inet 192.168.1.1"
> ...etc...
I suppose thats true..
So whens do the patches for it arrive? ;)
---
Daniel O'Connor software and network engineer
for Genesis Software - http://www.gsoft.com.au
"The nice thing about standards is that there
are so many of them to choose from."
-- Andrew Tanenbaum
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Wed Jan 27 19:01:52 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id TAA25784
for freebsd-current-outgoing; Wed, 27 Jan 1999 19:01:52 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.26.10.9])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA25771
for <current@FreeBSD.ORG>; Wed, 27 Jan 1999 19:01:43 -0800 (PST)
(envelope-from bde@godzilla.zeta.org.au)
Received: (from bde@localhost)
by godzilla.zeta.org.au (8.8.7/8.8.7) id OAA25274;
Thu, 28 Jan 1999 14:01:40 +1100
Date: Thu, 28 Jan 1999 14:01:40 +1100
From: Bruce Evans <bde@zeta.org.au>
Message-Id: <199901280301.OAA25274@godzilla.zeta.org.au>
To: current@FreeBSD.ORG, dillon@apollo.backplane.com
Subject: Re: Changing bzero, bcopy, memset, memcpy, etc... prototypes
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
> I would like to propose changing the prototype for the kernel memory
> zeroing and copying routines.
>
> Basically, the problem is that a whole hellofalot of drivers run
> bzero and bcopy on volatile memory. The only way to remove the
> warnings is to volatilize bzero and bcopy.
No. bzero() and bcopy() are for handling ordinary memory. There is no
proper way to volatilize them without pessimizing them. Adding volatile
to their prototypes won't actually make them handle volatile memory; it
just breaks the warnings. Some of the i586-optimized versions in fact
don't handle volatile memory properly - they do things like reading some
locations twice to prefetch the cache lines. Even ordinary bcopy() via
movsl accesses memory backwards in some cases.
Drivers should use the bus access macros.
Bruce
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Wed Jan 27 19:04:40 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id TAA26154
for freebsd-current-outgoing; Wed, 27 Jan 1999 19:04:40 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from alcanet.com.au (border.alcanet.com.au [203.62.196.10])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA26146
for <current@FreeBSD.ORG>; Wed, 27 Jan 1999 19:04:38 -0800 (PST)
(envelope-from peter.jeremy@auss2.alcatel.com.au)
Received: by border.alcanet.com.au id <40356>; Thu, 28 Jan 1999 13:55:01 +1100
Date: Thu, 28 Jan 1999 14:04:20 +1100
From: Peter Jeremy <peter.jeremy@auss2.alcatel.com.au>
Subject: Re: btokup() macro in sys/malloc.h
To: current@FreeBSD.ORG
Message-Id: <99Jan28.135501est.40356@border.alcanet.com.au>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
Matthew Dillon <dillon@apollo.backplane.com> wrote:
>:style(9) should emphasize legibility and maintainability, rather than
>:minimizing the number of extraneous (from the compiler's perspective)
>:parenthesis.
> As far as parenthesis go, it's irrelevant because -Wall pretty much
> covers the most common mistakes.
I was thinking in terms of the parenthesis required as a result of the
operator precedences (from K&R), rather than gcc -Wall.
> If your code compiles without generating
> a warning, your parenthesization is in good shape.
Agreed.
> Braces and indentation and other purely visual effects are a different
> matter.
Agreed. I think style(9) errs on the side of too few braces as well.
My preference is for braces whenever you exceed 1 physical line rather
than 1 statement. eg
if (this &&
that) {
foo();
}
if (this) {
if (that)
a = b;
else
c = d;
}
Unfortunately (or maybe fortunately), gcc doesn't have an option to
warn you that your indentation doesn't doesn't match its parsing.
eg:
if (a)
if (b)
foo();
else
bar();
baz();
It would be nice if style(9) documented the options to give indent(1)
to match the `approved' layout convections. (This would reduce the
effort involved in importing large chunks of code).
Peter
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Wed Jan 27 19:13:03 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id TAA27513
for freebsd-current-outgoing; Wed, 27 Jan 1999 19:13:03 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA27508
for <current@FreeBSD.ORG>; Wed, 27 Jan 1999 19:13:02 -0800 (PST)
(envelope-from dillon@apollo.backplane.com)
Received: (from dillon@localhost)
by apollo.backplane.com (8.9.2/8.9.1) id TAA92729;
Wed, 27 Jan 1999 19:12:51 -0800 (PST)
(envelope-from dillon)
Date: Wed, 27 Jan 1999 19:12:51 -0800 (PST)
From: Matthew Dillon <dillon@apollo.backplane.com>
Message-Id: <199901280312.TAA92729@apollo.backplane.com>
To: Bruce Evans <bde@zeta.org.au>
Cc: current@FreeBSD.ORG
Subject: Re: Changing bzero, bcopy, memset, memcpy, etc... prototypes
References: <199901280301.OAA25274@godzilla.zeta.org.au>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
:
:No. bzero() and bcopy() are for handling ordinary memory. There is no
:proper way to volatilize them without pessimizing them. Adding volatile
:to their prototypes won't actually make them handle volatile memory; it
:just breaks the warnings. Some of the i586-optimized versions in fact
:don't handle volatile memory properly - they do things like reading some
:locations twice to prefetch the cache lines. Even ordinary bcopy() via
:movsl accesses memory backwards in some cases.
:
:Drivers should use the bus access macros.
:
:Bruce
Hmmm.. quite a bit more work.
-Matt
Matthew Dillon
<dillon@backplane.com>
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Wed Jan 27 19:16:30 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id TAA27794
for freebsd-current-outgoing; Wed, 27 Jan 1999 19:16:30 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.26.10.9])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA27787
for <current@FreeBSD.ORG>; Wed, 27 Jan 1999 19:16:27 -0800 (PST)
(envelope-from bde@godzilla.zeta.org.au)
Received: (from bde@localhost)
by godzilla.zeta.org.au (8.8.7/8.8.7) id OAA26849;
Thu, 28 Jan 1999 14:16:25 +1100
Date: Thu, 28 Jan 1999 14:16:25 +1100
From: Bruce Evans <bde@zeta.org.au>
Message-Id: <199901280316.OAA26849@godzilla.zeta.org.au>
To: current@FreeBSD.ORG, peter.jeremy@auss2.alcatel.com.au
Subject: Re: btokup() macro in sys/malloc.h
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
>It would be nice if style(9) documented the options to give indent(1)
>to match the `approved' layout convections. (This would reduce the
>effort involved in importing large chunks of code).
This is impossible, since indent(1) is buggy and out of date with both
KNF and C.
Bruce
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Wed Jan 27 19:17:53 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id TAA28047
for freebsd-current-outgoing; Wed, 27 Jan 1999 19:17:53 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from whistle.com (s205m131.whistle.com [207.76.205.131])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA28031
for <current@FreeBSD.ORG>; Wed, 27 Jan 1999 19:17:48 -0800 (PST)
(envelope-from archie@whistle.com)
Received: (from smap@localhost) by whistle.com (8.7.5/8.6.12) id TAA26411; Wed, 27 Jan 1999 19:17:01 -0800 (PST)
Received: from bubba.whistle.com( 207.76.205.7) by whistle.com via smap (V2.0)
id xma026409; Wed, 27 Jan 99 19:16:45 -0800
Received: (from archie@localhost) by bubba.whistle.com (8.8.7/8.6.12) id TAA17719; Wed, 27 Jan 1999 19:16:44 -0800 (PST)
From: Archie Cobbs <archie@whistle.com>
Message-Id: <199901280316.TAA17719@bubba.whistle.com>
Subject: Re: DEVFS, the time has come...
In-Reply-To: <XFMail.990128133917.doconnor@gsoft.com.au> from Daniel O'Connor at "Jan 28, 99 01:39:17 pm"
To: doconnor@gsoft.com.au (Daniel O'Connor)
Date: Wed, 27 Jan 1999 19:16:44 -0800 (PST)
Cc: current@FreeBSD.ORG, julian@whistle.com (Julian Elischer)
X-Mailer: ELM [version 2.4ME+ PL38 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
Daniel O'Connor writes:
> > Anyway, it's not automatic now either:
> >
> > network_interfaces="lo0 ed0" # List of network interfaces (lo0 is loopback).
> > ifconfig_lo0="inet 127.0.0.1" # default loopback device configuration.
> > ifconfig_ed0="inet 192.168.1.1"
> > ...etc...
> I suppose thats true..
> So whens do the patches for it arrive? ;)
I think Julian is going to create some patches to if_ethersubr.c
so that all your Ethernet interfaces appear as netgraph nodes.
Then you can do some fun things..
-Archie
___________________________________________________________________________
Archie Cobbs * Whistle Communications, Inc. * http://www.whistle.com
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Wed Jan 27 19:33:52 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id TAA00133
for freebsd-current-outgoing; Wed, 27 Jan 1999 19:33:52 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from mail.atl.bellsouth.net (mail.atl.bellsouth.net [205.152.0.21])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA00121
for <freebsd-current@FreeBSD.ORG>; Wed, 27 Jan 1999 19:33:47 -0800 (PST)
(envelope-from wghicks@bellsouth.net)
Received: from wghicks.bellsouth.net (root@host-209-214-71-142.atl.bellsouth.net [209.214.71.142])
by mail.atl.bellsouth.net (8.8.8-spamdog/8.8.5) with ESMTP id WAA11904;
Wed, 27 Jan 1999 22:33:37 -0500 (EST)
Received: from localhost (wghicks@localhost [127.0.0.1])
by wghicks.bellsouth.net (8.9.2/8.9.2) with ESMTP id WAA75343;
Wed, 27 Jan 1999 22:50:20 -0500 (EST)
(envelope-from wghicks@wghicks.bellsouth.net)
To: dcs@newsguy.com
Cc: mark@grondar.za, obrien@NUXI.com, sgk@troutmask.apl.washington.edu,
freebsd-current@FreeBSD.ORG
Subject: Re: removing f2c from base distribution
In-Reply-To: Your message of "Wed, 27 Jan 1999 20:44:33 +0900"
<36AEFC21.A9B32C67@newsguy.com>
References: <36AEFC21.A9B32C67@newsguy.com>
X-Mailer: Mew version 1.93 on XEmacs 20.4 (Emerald)
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-Id: <19990127225019J.wghicks@wghicks.bellsouth.net>
Date: Wed, 27 Jan 1999 22:50:19 -0500
From: W Gerald Hicks <wghicks@bellsouth.net>
X-Dispatcher: imput version 980905(IM100)
Lines: 22
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
From: "Daniel C. Sobral" <dcs@newsguy.com>
>
> A lot of people use a lot of things out of ports. Why should Fortran
> be different?
>
Right on. If anything, I'd like to see the "ports" system continue
its evolution to becoming able to build nearly any component of the
system. (including patched kernel builds and release generation).
One thing I'd like to understand is how to add CVSup and anonCVS
fetching capability. This would be very useful for constructing
'ports' which are derived from FreeBSD sources (like an enhanced
userland Ficl).
This capability would also be useful for software like EGCS which has
public anonCVS access.
Cheers,
Jerry Hicks
wghicks@bellsouth.net
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Wed Jan 27 19:35:36 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id TAA00353
for freebsd-current-outgoing; Wed, 27 Jan 1999 19:35:36 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from abby.skypoint.net (abby.skypoint.net [199.86.32.252])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA00338
for <freebsd-current@FreeBSD.ORG>; Wed, 27 Jan 1999 19:35:28 -0800 (PST)
(envelope-from bruce@zuhause.mn.org)
Received: (from uucp@localhost)
by abby.skypoint.net (8.8.7/jl 1.3) with UUCP id VAA26864
for freebsd-current@FreeBSD.ORG; Wed, 27 Jan 1999 21:35:26 -0600 (CST)
Received: (from bruce@localhost)
by zuhause.mn.org (8.9.2/8.9.1) id VAA23998;
Wed, 27 Jan 1999 21:32:00 -0600 (CST)
(envelope-from bruce)
From: Bruce Albrecht <bruce@zuhause.mn.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <13999.55856.37120.423504@zuhause.zuhause.mn.org>
Date: Wed, 27 Jan 1999 21:32:00 -0600 (CST)
To: freebsd-current@FreeBSD.ORG
Subject: Re: removing f2c from base distribution
In-Reply-To: <199901271623.LAA07822@khavrinen.lcs.mit.edu>
References: <199901270504.WAA18271@mt.sri.com>
<199901270555.VAA09197@troutmask.apl.washington.edu>
<19990126220644.A7037@relay.nuxi.com>
<199901270623.IAA01480@greenpeace.grondar.za>
<36AEFC21.A9B32C67@newsguy.com>
<199901271623.LAA07822@khavrinen.lcs.mit.edu>
X-Mailer: VM 6.62 under 20.4 "Emerald" XEmacs Lucid
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
Garrett Wollman writes:
> <<On Wed, 27 Jan 1999 20:44:33 +0900, "Daniel C. Sobral" <dcs@newsguy.com> said:
>
>
> > A lot of people use a lot of things out of ports. Why should Fortran
> > be different?
>
> Because Berkeley Unix has /always/ included a FORTRAN compiler.
So FreeBSD v12.4, released in 2026, had better include a FORTRAN
compiler, because Berkely Unix has /always/ included a FORTRAN compiler?
I'm sure there are a fair number of ways FreeBSD has diverged from the
way Berkeley Unix has always done things (for example, to conform to
POSIX), is that such a bad thing? If it's a port, and sysinstall gives
the user an option to install a FORTRAN compiler, is that so radically
different from Berkeley Unix /always/ including a FORTRAN compiler?
Is it wrong to move things that most people installing FreeBSD don't use
out of the core and into ports? I've never used the FreeBSD FORTRAN
compiler, but I do use something that a lot of other people single out as
being in this category (uucp), but if uucp were to move to the ports, I'd
still use it and FreeBSD. Are there any programs in the base sources for
FreeBSD that are written in FORTRAN?
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Wed Jan 27 19:46:47 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id TAA01806
for freebsd-current-outgoing; Wed, 27 Jan 1999 19:46:47 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from whistle.com (s205m131.whistle.com [207.76.205.131])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA01794
for <current@FreeBSD.ORG>; Wed, 27 Jan 1999 19:46:44 -0800 (PST)
(envelope-from archie@whistle.com)
Received: (from smap@localhost) by whistle.com (8.7.5/8.6.12) id TAA26822; Wed, 27 Jan 1999 19:46:02 -0800 (PST)
Received: from bubba.whistle.com( 207.76.205.7) by whistle.com via smap (V2.0)
id xma026813; Wed, 27 Jan 99 19:45:56 -0800
Received: (from archie@localhost) by bubba.whistle.com (8.8.7/8.6.12) id TAA04081; Wed, 27 Jan 1999 19:45:55 -0800 (PST)
From: Archie Cobbs <archie@whistle.com>
Message-Id: <199901280345.TAA04081@bubba.whistle.com>
Subject: Re: btokup() macro in sys/malloc.h
In-Reply-To: <199901280251.NAA23946@godzilla.zeta.org.au> from Bruce Evans at "Jan 28, 99 01:51:15 pm"
To: bde@zeta.org.au (Bruce Evans)
Date: Wed, 27 Jan 1999 19:45:55 -0800 (PST)
Cc: wollman@khavrinen.lcs.mit.edu, current@FreeBSD.ORG
X-Mailer: ELM [version 2.4ME+ PL38 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
Bruce Evans writes:
> >In fact, style(9) should say:
> >
> > If at all possible, your code should compile without warnings
> > when the gcc -Wall flag is given.
>
> Avoiding warnings is more an engineering than a stylistic matter.
> You turn on warnings to help avoid bugs that the compiler can find
> easily. You ask everyone else to turn on warnings so that compiling
> their sources with the same CFLAGS as your sources doesn't cause a
> spew of warnings.
Well said. Personally, it would take me twice as long to debug code
without -Wall.
> >As it stands now (and I QUOTE!) it says:
> >
> > Don't use parentheses unless they're required for precedence, or
> > the statement is really confusing without them.
> >
> > a = b->c[0] + ~d == (e || f) || g && h ? i : j >> 1;
> >
> >That's ridiculous!
>
> I think it's trying to be funny. This makes it a bad example either
> way. Perhaps its point is that complicated expressions can't be made
> less confusing by adding parentheses.
Guess I missed the joke then.. :-)
You're right, some things are inherently complicated. I think
line formatting is as importatn as parentheses, for example.
-Archie
___________________________________________________________________________
Archie Cobbs * Whistle Communications, Inc. * http://www.whistle.com
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Wed Jan 27 19:50:14 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id TAA02233
for freebsd-current-outgoing; Wed, 27 Jan 1999 19:50:14 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from ceia.nordier.com (m2-44-dbn.dial-up.net [196.34.155.108])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA02212
for <freebsd-current@FreeBSD.ORG>; Wed, 27 Jan 1999 19:50:06 -0800 (PST)
(envelope-from rnordier@nordier.com)
Received: (from rnordier@localhost) by ceia.nordier.com (8.8.7/8.6.12) id FAA29674; Thu, 28 Jan 1999 05:48:34 +0200 (SAT)
From: Robert Nordier <rnordier@nordier.com>
Message-Id: <199901280348.FAA29674@ceia.nordier.com>
Subject: Re: "Argument by Authority"
In-Reply-To: <19990128130131.J4819@freebie.lemis.com> from Greg Lehey at "Jan 28, 99 01:01:31 pm"
To: grog@lemis.com (Greg Lehey)
Date: Thu, 28 Jan 1999 05:48:31 +0200 (SAT)
Cc: mo@servo.ccr.org, wollman@khavrinen.lcs.mit.edu,
freebsd-current@FreeBSD.ORG
X-Mailer: ELM [version 2.4ME+ PL31 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
Greg Lehey wrote:
> On Wednesday, 27 January 1999 at 14:38:23 -0500, Mike O'Dell wrote:
> >
> > just for a calibration,
> > i asked Dennis Ritchie his opinion of "the right behavior"
> >
> > his comment about posix might be the trump card, although
> > i'd like to see chapter and verse if that's the case.
> >
> > for what it's worth.
> >
> > -mo
> >
> >
> > ------- Forwarded Message
> >
> > MessageName: (Message 47)
> > From: dmr@plan9.bell-labs.com
> > Date: Wed, 27 Jan 1999 14:30:59 -0500
> > To: mo@servo.ccr.org
> >
> > Well the research systems from v7 (just looked) through Brazil
> > produce no diagnostic. So much for "should."
> >
> > Irix complains, suppressible with -f. I wonder if it's in posix?
> >
> > Dennis
> >
> > ------- End of Forwarded Message
>
> On Wednesday, 27 January 1999 at 15:04:38 -0500, Garrett Wollman wrote:
> > <<On Wed, 27 Jan 1999 14:38:23 -0500, "Mike O'Dell" <mo@servo.ccr.org> said:
> >
> >> i asked Dennis Ritchie his opinion of "the right behavior"
> >
> > The right behavior of what?
> >
> > -GAWollman
>
> On Wednesday, 27 January 1999 at 15:59:13 -0500, Mike O'Dell wrote:
> >
> > i asked his notion of the right behavior of "rm"
>
> Well, between you and dmr, you manage to remain completely obfuscated.
> How about including some of the previous history?
>
> Are you talking about whether rm without -f will fail when it can't do
> its job? Even that doesn't seem to make much sense.
This relates to a thread on -stable "rm with no arguments" and was
probably posted to -current by mistake.
>From the man page:
| COMPATIBILITY
| The rm utility differs from historical implementations in that
| the -f option only masks attempts to remove non-existent
| files instead of masking a large variety of errors.
--
Robert Nordier
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Wed Jan 27 20:02:25 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id UAA04034
for freebsd-current-outgoing; Wed, 27 Jan 1999 20:02:25 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from peach.ocn.ne.jp (peach.ocn.ne.jp [210.145.254.87])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA04028
for <freebsd-current@FreeBSD.ORG>; Wed, 27 Jan 1999 20:02:23 -0800 (PST)
(envelope-from dcs@newsguy.com)
Received: from newsguy.com by peach.ocn.ne.jp (8.9.1a/OCN) id NAA12557; Thu, 28 Jan 1999 13:02:04 +0900 (JST)
Message-ID: <36AF4B0F.4D97F8E@newsguy.com>
Date: Thu, 28 Jan 1999 02:21:19 +0900
From: "Daniel C. Sobral" <dcs@newsguy.com>
X-Mailer: Mozilla 4.5 [en] (Win98; I)
X-Accept-Language: pt-BR,ja
MIME-Version: 1.0
To: Nate Williams <nate@mt.sri.com>
CC: Garrett Wollman <wollman@khavrinen.lcs.mit.edu>,
freebsd-current@FreeBSD.ORG
Subject: Re: removing f2c from base distribution
References: <199901270504.WAA18271@mt.sri.com>
<199901270555.VAA09197@troutmask.apl.washington.edu>
<19990126220644.A7037@relay.nuxi.com>
<199901270623.IAA01480@greenpeace.grondar.za>
<36AEFC21.A9B32C67@newsguy.com>
<199901271623.LAA07822@khavrinen.lcs.mit.edu> <199901271706.KAA21389@mt.sri.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
Nate Williams wrote:
>
> > > A lot of people use a lot of things out of ports. Why should Fortran
> > > be different?
> >
> > Because Berkeley Unix has /always/ included a FORTRAN compiler.
>
> And they have /always/ included games. Next issue.
Mmmm... can I get a VAX port going with this argument? :-)
--
Daniel C. Sobral (8-DCS)
dcs@newsguy.com
If you sell your soul to the Devil and all you get is an MCSE from
it, you haven't gotten market rate.
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Wed Jan 27 20:24:47 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id UAA06514
for freebsd-current-outgoing; Wed, 27 Jan 1999 20:24:47 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.26.10.9])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA06509
for <current@FreeBSD.ORG>; Wed, 27 Jan 1999 20:24:43 -0800 (PST)
(envelope-from bde@godzilla.zeta.org.au)
Received: (from bde@localhost)
by godzilla.zeta.org.au (8.8.7/8.8.7) id PAA01617;
Thu, 28 Jan 1999 15:24:35 +1100
Date: Thu, 28 Jan 1999 15:24:35 +1100
From: Bruce Evans <bde@zeta.org.au>
Message-Id: <199901280424.PAA01617@godzilla.zeta.org.au>
To: archie@whistle.com, dillon@apollo.backplane.com
Subject: Re: kern/subr_scanf array index of signed char
Cc: current@FreeBSD.ORG
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
>:Matthew Dillon writes:
>:> goto match_failure;
>:> } else {
>:> p0 = p = va_arg(ap, char *);
>:> - while (ccltab[*inp]) {
>:> + while (ccltab[(int)(unsigned char)*inp]) {
>:> inr--;
>:> *p++ = *inp++;
>:> if (--width == 0)
>:
>:Just curious.. why do you need the "(int)" cast?
>:
>:-Archie
>
> Actually, it could very well be that I don't. I didn't want to spend
> the time to check to see if the compiler warned on unsigned-char array
> indexes. You can change it back if unsigned char array indexes do not
> produce a warning.
Sloppy thinking. How would you know if you fixed the bug unless you checked
that you fixed the bug instead of breaking the warning? The bug was that
on systems with signed chars, *inp gave negative array indexes if the
caller passes a format string with negative characters in certain positions.
There are still lots of related isfoo(*inp) bugs. All these bugs are more
serious in the userland.
Bruce
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Wed Jan 27 20:37:45 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id UAA08298
for freebsd-current-outgoing; Wed, 27 Jan 1999 20:37:45 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from picnic.mat.net (b133.mat.net [206.246.122.133] (may be forged))
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA08293
for <freebsd-current@FreeBSD.ORG>; Wed, 27 Jan 1999 20:37:42 -0800 (PST)
(envelope-from chuckr@mat.net)
Received: from localhost (chuckr@localhost)
by picnic.mat.net (8.9.2/8.8.5) with ESMTP id XAA78467;
Wed, 27 Jan 1999 23:35:20 -0500 (EST)
Date: Wed, 27 Jan 1999 23:35:19 -0500 (EST)
From: Chuck Robey <chuckr@mat.net>
To: "Daniel C. Sobral" <dcs@newsguy.com>
cc: Nate Williams <nate@mt.sri.com>,
Garrett Wollman <wollman@khavrinen.lcs.mit.edu>,
freebsd-current@FreeBSD.ORG
Subject: Re: removing f2c from base distribution
In-Reply-To: <36AF4B0F.4D97F8E@newsguy.com>
Message-ID: <Pine.BSF.4.05.9901272330540.375-100000@picnic.mat.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
On Thu, 28 Jan 1999, Daniel C. Sobral wrote:
> Nate Williams wrote:
> >
> > > > A lot of people use a lot of things out of ports. Why should Fortran
> > > > be different?
> > >
> > > Because Berkeley Unix has /always/ included a FORTRAN compiler.
> >
> > And they have /always/ included games. Next issue.
Well, there's a little more to this argument. I'm not saying I'm
necessarily in favor *myself* of programming in fortran (I like going to
the dentist a whole lot more) but to many people, having a fortran
compiler that works in FreeBSD is something of a badge of authenticity.
Most of these folks are heavy research types, but it's certainly true
that having the compiler at least *did* increase FreeBSD's reputation to
some degree.
I'm not sure if this argument is worth pushing anymore, because
FreeBSD's stability and usefulness has become much more well known, but
it did contribute at some point, and I think that is the idea that
Daniel was trying to convey.
Right?
----------------------------+-----------------------------------------------
Chuck Robey | Interests include any kind of voice or data
chuckr@glue.umd.edu | communications topic, C programming, and Unix.
213 Lakeside Drive Apt T-1 |
Greenbelt, MD 20770 | I run Journey2 and picnic (FreeBSD-current)
(301) 220-2114 | and jaunt (NetBSD).
----------------------------+-----------------------------------------------
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Wed Jan 27 20:37:52 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id UAA08329
for freebsd-current-outgoing; Wed, 27 Jan 1999 20:37:52 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from allegro.lemis.com (allegro.lemis.com [192.109.197.134])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA08286
for <freebsd-current@FreeBSD.ORG>; Wed, 27 Jan 1999 20:37:35 -0800 (PST)
(envelope-from grog@freebie.lemis.com)
Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137])
by allegro.lemis.com (8.9.1/8.9.0) with ESMTP id PAA22968;
Thu, 28 Jan 1999 15:07:10 +1030 (CST)
Received: (from grog@localhost)
by freebie.lemis.com (8.9.2/8.9.0) id PAA06433;
Thu, 28 Jan 1999 15:06:42 +1030 (CST)
Date: Thu, 28 Jan 1999 15:06:42 +1030
From: Greg Lehey <grog@lemis.com>
To: Robert Nordier <rnordier@nordier.com>
Cc: mo@servo.ccr.org, wollman@khavrinen.lcs.mit.edu,
freebsd-current@FreeBSD.ORG
Subject: Re: "Argument by Authority"
Message-ID: <19990128150642.S4819@freebie.lemis.com>
References: <19990128130131.J4819@freebie.lemis.com> <199901280348.FAA29674@ceia.nordier.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.95.1i
In-Reply-To: <199901280348.FAA29674@ceia.nordier.com>; from Robert Nordier on Thu, Jan 28, 1999 at 05:48:31AM +0200
WWW-Home-Page: http://www.lemis.com/~grog
Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia
Phone: +61-8-8388-8286
Fax: +61-8-8388-8725
Mobile: +61-41-739-7062
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
On Thursday, 28 January 1999 at 5:48:31 +0200, Robert Nordier wrote:
> Greg Lehey wrote:
>
>> On Wednesday, 27 January 1999 at 14:38:23 -0500, Mike O'Dell wrote:
>>>
>>> just for a calibration,
>>> i asked Dennis Ritchie his opinion of "the right behavior"
>>>
>>> his comment about posix might be the trump card, although
>>> i'd like to see chapter and verse if that's the case.
>>>
>>> ------- Forwarded Message
>>>
>>> MessageName: (Message 47)
>>> From: dmr@plan9.bell-labs.com
>>> Date: Wed, 27 Jan 1999 14:30:59 -0500
>>> To: mo@servo.ccr.org
>>>
>>> Well the research systems from v7 (just looked) through Brazil
>>> produce no diagnostic. So much for "should."
>>>
>>> Irix complains, suppressible with -f. I wonder if it's in posix?
>>>
>>> Dennis
>>>
>>> ------- End of Forwarded Message
>>
>> On Wednesday, 27 January 1999 at 15:04:38 -0500, Garrett Wollman wrote:
>>> <<On Wed, 27 Jan 1999 14:38:23 -0500, "Mike O'Dell" <mo@servo.ccr.org> said:
>>>
>>>> i asked Dennis Ritchie his opinion of "the right behavior"
>>>
>>> The right behavior of what?
>>>
>>> -GAWollman
>>
>> On Wednesday, 27 January 1999 at 15:59:13 -0500, Mike O'Dell wrote:
>>>
>>> i asked his notion of the right behavior of "rm"
>>
>> Well, between you and dmr, you manage to remain completely obfuscated.
>> How about including some of the previous history?
>>
>> Are you talking about whether rm without -f will fail when it can't do
>> its job? Even that doesn't seem to make much sense.
>
> This relates to a thread on -stable "rm with no arguments" and was
> probably posted to -current by mistake.
>
>> COMPATIBILITY
>> The rm utility differs from historical implementations in that
>> the -f option only masks attempts to remove non-existent
>> files instead of masking a large variety of errors.
Ah, yes, that makes sense. Amazing what a bit of context does, eh?
Greg
--
See complete headers for address, home page and phone numbers
finger grog@lemis.com for PGP public key
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Wed Jan 27 20:59:16 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id UAA11092
for freebsd-current-outgoing; Wed, 27 Jan 1999 20:59:16 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from uni4nn.gn.iaf.nl (osmium.gn.iaf.nl [193.67.144.12])
by hub.freebsd.org (8.8.8/8.8.8) with SMTP id UAA11082
for <current@FreeBSD.ORG>; Wed, 27 Jan 1999 20:59:13 -0800 (PST)
(envelope-from wilko@yedi.iaf.nl)
Received: by uni4nn.gn.iaf.nl with UUCP id AA23211
(5.67b/IDA-1.5); Thu, 28 Jan 1999 05:57:05 +0100
Received: (from wilko@localhost) by yedi.iaf.nl (8.8.8/8.6.12) id XAA03458; Wed, 27 Jan 1999 23:12:18 +0100 (CET)
From: Wilko Bulte <wilko@yedi.iaf.nl>
Message-Id: <199901272212.XAA03458@yedi.iaf.nl>
Subject: Re: DEVFS, the time has come...
In-Reply-To: <199901272124.NAA15248@bubba.whistle.com> from Archie Cobbs at "Jan 27, 99 01:24:01 pm"
To: archie@whistle.com (Archie Cobbs)
Date: Wed, 27 Jan 1999 23:12:18 +0100 (CET)
Cc: dfr@nlsystems.com, current@FreeBSD.ORG
X-Organisation: Private FreeBSD site - Arnhem, The Netherlands
X-Pgp-Info: PGP public key at 'finger wilko@freefall.freebsd.org'
X-Mailer: ELM [version 2.4ME+ PL38 (25)]
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
As Archie Cobbs wrote...
> Doug Rabson writes:
> > And another thing. Why can't we use a non-driver-specific name for the
> > disk? Most users simply don't care whether the driver was fd, wfd, wd or
> > anything. They just want to get to their files without any fuss.
>
> I agree.. and same thing goes for Ethernet drivers. I actually
> like the way Linux always has "eth0", "eth1", ... (which we could
Yeagh... what is wrong with ed0, de0, fxp0 etc that needs changing? Is this
just a matter of taste or is there more to it? I for one don't see any
advantage in eth[0-9] style device naming.
Wilko
_ ______________________________________________________________________
| / o / / _ Bulte email: wilko@yedi.iaf.nl
|/|/ / / /( (_) Arnhem, The Netherlands WWW : http://www.tcja.nl
______________________________________________ Powered by FreeBSD __________
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Wed Jan 27 21:02:20 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id VAA11517
for freebsd-current-outgoing; Wed, 27 Jan 1999 21:02:20 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from peach.ocn.ne.jp (peach.ocn.ne.jp [210.145.254.87])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA11507
for <freebsd-current@FreeBSD.ORG>; Wed, 27 Jan 1999 21:02:17 -0800 (PST)
(envelope-from dcs@newsguy.com)
Received: from newsguy.com by peach.ocn.ne.jp (8.9.1a/OCN) id OAA21009; Thu, 28 Jan 1999 14:01:56 +0900 (JST)
Message-ID: <36AF4B0F.4D97F8E@newsguy.com>
Date: Thu, 28 Jan 1999 02:21:19 +0900
From: "Daniel C. Sobral" <dcs@newsguy.com>
X-Mailer: Mozilla 4.5 [en] (Win98; I)
X-Accept-Language: pt-BR,ja
MIME-Version: 1.0
To: Nate Williams <nate@mt.sri.com>
CC: Garrett Wollman <wollman@khavrinen.lcs.mit.edu>,
freebsd-current@FreeBSD.ORG
Subject: Re: removing f2c from base distribution
References: <199901270504.WAA18271@mt.sri.com>
<199901270555.VAA09197@troutmask.apl.washington.edu>
<19990126220644.A7037@relay.nuxi.com>
<199901270623.IAA01480@greenpeace.grondar.za>
<36AEFC21.A9B32C67@newsguy.com>
<199901271623.LAA07822@khavrinen.lcs.mit.edu> <199901271706.KAA21389@mt.sri.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
Nate Williams wrote:
>
> > > A lot of people use a lot of things out of ports. Why should Fortran
> > > be different?
> >
> > Because Berkeley Unix has /always/ included a FORTRAN compiler.
>
> And they have /always/ included games. Next issue.
Mmmm... can I get a VAX port going with this argument? :-)
--
Daniel C. Sobral (8-DCS)
dcs@newsguy.com
If you sell your soul to the Devil and all you get is an MCSE from
it, you haven't gotten market rate.
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Wed Jan 27 21:02:32 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id VAA11704
for freebsd-current-outgoing; Wed, 27 Jan 1999 21:02:32 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from peach.ocn.ne.jp (peach.ocn.ne.jp [210.145.254.87])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA11699
for <current@FreeBSD.ORG>; Wed, 27 Jan 1999 21:02:30 -0800 (PST)
(envelope-from dcs@newsguy.com)
Received: from newsguy.com by peach.ocn.ne.jp (8.9.1a/OCN) id OAA21059; Thu, 28 Jan 1999 14:02:15 +0900 (JST)
Message-ID: <36AFE842.4D040D83@newsguy.com>
Date: Thu, 28 Jan 1999 13:32:02 +0900
From: "Daniel C. Sobral" <dcs@newsguy.com>
X-Mailer: Mozilla 4.5 [en] (Win98; I)
X-Accept-Language: pt-BR,ja
MIME-Version: 1.0
To: Sean Eric Fagan <sef@kithrup.com>
CC: current@FreeBSD.ORG
Subject: Re: "JAIL" code headed for -current.
References: <199901271944.LAA15317@kithrup.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
Sean Eric Fagan wrote:
>
> > suser(NOJAIL, bla, bla);
> >or
> > suser(0, bla, bla);
>
> Oh, goody, more gratuitious incomaptibilities with everyone else.
Incompatibility, yes, but gratuitous?
--
Daniel C. Sobral (8-DCS)
dcs@newsguy.com
If you sell your soul to the Devil and all you get is an MCSE from
it, you haven't gotten market rate.
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Wed Jan 27 21:03:33 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id VAA11853
for freebsd-current-outgoing; Wed, 27 Jan 1999 21:03:33 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.26.10.9])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA11842
for <current@FreeBSD.ORG>; Wed, 27 Jan 1999 21:03:29 -0800 (PST)
(envelope-from bde@godzilla.zeta.org.au)
Received: (from bde@localhost)
by godzilla.zeta.org.au (8.8.7/8.8.7) id QAA05872;
Thu, 28 Jan 1999 16:03:25 +1100
Date: Thu, 28 Jan 1999 16:03:25 +1100
From: Bruce Evans <bde@zeta.org.au>
Message-Id: <199901280503.QAA05872@godzilla.zeta.org.au>
To: dillon@apollo.backplane.com, jdp@polstra.com
Subject: Re: btokup() macro in sys/malloc.h
Cc: current@FreeBSD.ORG
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
>> Is this parenthesization correct ?
>>
>> OLD
>>
>> #define btokup(addr) (&kmemusage[(caddr_t)(addr) - kmembase >> PAGE_SHIFT])
>>
>> NEW
>>
>> #define btokup(addr) (&kmemusage[((caddr_t)(addr) - kmembase) >> PAGE_SHIFT])
Yes. It is the same as before the "cleanup" in rev.1.13.
>The added parentheses don't make any difference, semantically. This
>change probably wouldn't meet the criteria spelled out in style(9):
>
> Unary operators don't require spaces, binary operators do. Don't use
> parentheses unless they're required for precedence, or the statement is
> really confusing without them.
>
> a = b->c[0] + ~d == (e || f) || g && h ? i : j >> 1;
> k = !(l & FLAGS);
Nah, style(9), not to mention the example of btokup() in Lite1 and Lite2,
requires paretheses here (in btokup(), and probably in the bad example in
style(9), because the expression would be really confusing without them :-).
Bruce
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Wed Jan 27 21:21:19 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id VAA13339
for freebsd-current-outgoing; Wed, 27 Jan 1999 21:21:19 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from cain.gsoft.com.au (genesi.lnk.telstra.net [139.130.136.161])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA13334
for <current@FreeBSD.ORG>; Wed, 27 Jan 1999 21:21:16 -0800 (PST)
(envelope-from doconnor@gsoft.com.au)
Received: from lot.gsoft.com.au (doconnor@lot.gsoft.com.au [203.38.152.106])
by cain.gsoft.com.au (8.8.8/8.8.8) with ESMTP id PAA29364;
Thu, 28 Jan 1999 15:51:00 +1030 (CST)
(envelope-from doconnor@gsoft.com.au)
Message-ID: <XFMail.990128155952.doconnor@gsoft.com.au>
X-Mailer: XFMail 1.3 [p0] on FreeBSD
X-Priority: 3 (Normal)
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 8bit
MIME-Version: 1.0
In-Reply-To: <199901272212.XAA03458@yedi.iaf.nl>
Date: Thu, 28 Jan 1999 15:59:52 +1030 (CST)
From: "Daniel O'Connor" <doconnor@gsoft.com.au>
To: Wilko Bulte <wilko@yedi.iaf.nl>
Subject: Re: DEVFS, the time has come...
Cc: current@FreeBSD.ORG, dfr@nlsystems.com,
(Archie Cobbs) <archie@whistle.com>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
On 27-Jan-99 Wilko Bulte wrote:
> > I agree.. and same thing goes for Ethernet drivers. I actually
> > like the way Linux always has "eth0", "eth1", ... (which we could
> Yeagh... what is wrong with ed0, de0, fxp0 etc that needs changing? Is this
> just a matter of taste or is there more to it? I for one don't see any
> advantage in eth[0-9] style device naming.
Well, for one its sucks trying to get newbies to work out what their network card is
called..
Also the eth[0..x] thing means you can replace your ethernet card with a new one of a
different type without having to look through your config code for references to ed0 or
whatever.
Another thing.. we get to be more Linux like, which is a good thing, right? *duck*
---
Daniel O'Connor software and network engineer
for Genesis Software - http://www.gsoft.com.au
"The nice thing about standards is that there
are so many of them to choose from."
-- Andrew Tanenbaum
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Wed Jan 27 21:23:48 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id VAA13668
for freebsd-current-outgoing; Wed, 27 Jan 1999 21:23:48 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from labinfo.iet.unipi.it (labinfo.iet.unipi.it [131.114.9.5])
by hub.freebsd.org (8.8.8/8.8.8) with SMTP id VAA13659
for <freebsd-current@FreeBSD.ORG>; Wed, 27 Jan 1999 21:23:43 -0800 (PST)
(envelope-from luigi@labinfo.iet.unipi.it)
Received: from localhost (luigi@localhost) by labinfo.iet.unipi.it (8.6.5/8.6.5) id EAA07485; Thu, 28 Jan 1999 04:11:16 +0100
From: Luigi Rizzo <luigi@labinfo.iet.unipi.it>
Message-Id: <199901280311.EAA07485@labinfo.iet.unipi.it>
Subject: Re: About to commit NTFS driver
To: semen@iclub.nsu.ru (Ustimenko Semen)
Date: Thu, 28 Jan 1999 04:11:16 +0100 (MET)
Cc: freebsd-current@FreeBSD.ORG
In-Reply-To: <Pine.BSF.3.96.990128024451.49866B-100000@iclub.nsu.ru> from "Ustimenko Semen" at Jan 28, 99 02:46:09 am
X-Mailer: ELM [version 2.4 PL23]
Content-Type: text
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
> Hello!
>
> Are there any disagrees with an idea to commit a NTFS
> driver into current:
...
> Driver is readonly, specialy developed for freebsd,
> supports most of NTFS's features.
while readonly access is great, a problem i always have with NT machines
is to access the NTFS (or a file on it) to have a local swapfile when
using the machine as a diskless FreeBSD.
Any idea on how to achieve at least a restricted form of write access
(e.g. without letting one change file size or attributes, only data
blocks) ?
This way i could create zeroed swapfiles/MFS images of the right size
while in NT, and then have them usable when booting FreeBSD.
thanks
luigi
-----------------------------------+-------------------------------------
Luigi RIZZO .
EMAIL: luigi@iet.unipi.it . Dip. di Ing. dell'Informazione
HTTP://www.iet.unipi.it/~luigi/ . Universita` di Pisa
TEL/FAX: +39-050-568.533/522 . via Diotisalvi 2, 56126 PISA (Italy)
-----------------------------------+-------------------------------------
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Wed Jan 27 21:40:22 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id VAA15956
for freebsd-current-outgoing; Wed, 27 Jan 1999 21:40:22 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from ns.mt.sri.com (sri-gw.MT.net [206.127.105.141])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA15940
for <current@FreeBSD.ORG>; Wed, 27 Jan 1999 21:40:19 -0800 (PST)
(envelope-from nate@mt.sri.com)
Received: from mt.sri.com (rocky.mt.sri.com [206.127.76.100])
by ns.mt.sri.com (8.8.8/8.8.8) with SMTP id WAA10707;
Wed, 27 Jan 1999 22:40:17 -0700 (MST)
(envelope-from nate@rocky.mt.sri.com)
Received: by mt.sri.com (SMI-8.6/SMI-SVR4)
id WAA26288; Wed, 27 Jan 1999 22:40:16 -0700
Date: Wed, 27 Jan 1999 22:40:16 -0700
Message-Id: <199901280540.WAA26288@mt.sri.com>
From: Nate Williams <nate@mt.sri.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
To: Archie Cobbs <archie@whistle.com>
Cc: wollman@khavrinen.lcs.mit.edu (Garrett Wollman), current@FreeBSD.ORG
Subject: Re: btokup() macro in sys/malloc.h
In-Reply-To: <199901280229.SAA20207@bubba.whistle.com>
References: <199901280222.VAA14212@khavrinen.lcs.mit.edu>
<199901280229.SAA20207@bubba.whistle.com>
X-Mailer: VM 6.34 under 19.16 "Lille" XEmacs Lucid
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
> Anyway, if we're going to -Wall'ify the kernel (as we should)
> then we need to update sytle(9) to reflect that.
>
> In fact, style(9) should say:
>
> If at all possible, your code should compile without warnings
> when the gcc -Wall flag is given.
I disagree. As has been shown many times in the past (and I suspect the
down-under constituent will show that at least a couple of the
'warnings' fixes will be wrong and hide bogus code), making -Wall a goal
causes people to cover up bad code with bad casts and such.
'-Wall' is *NOT* a good design goal.
Nate
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Wed Jan 27 21:45:15 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id VAA16522
for freebsd-current-outgoing; Wed, 27 Jan 1999 21:45:15 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA16515
for <current@FreeBSD.ORG>; Wed, 27 Jan 1999 21:45:14 -0800 (PST)
(envelope-from jdp@polstra.com)
Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13])
by wall.polstra.com (8.9.1/8.9.1) with ESMTP id VAA03490;
Wed, 27 Jan 1999 21:45:12 -0800 (PST)
(envelope-from jdp@polstra.com)
Received: (from jdp@localhost)
by vashon.polstra.com (8.9.1/8.9.1) id VAA07169;
Wed, 27 Jan 1999 21:45:11 -0800 (PST)
(envelope-from jdp@polstra.com)
Message-ID: <XFMail.990127214511.jdp@polstra.com>
X-Mailer: XFMail 1.3 [p0] on FreeBSD
X-Priority: 3 (Normal)
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 8bit
MIME-Version: 1.0
In-Reply-To: <199901280503.QAA05872@godzilla.zeta.org.au>
Date: Wed, 27 Jan 1999 21:45:11 -0800 (PST)
Organization: Polstra & Co., Inc.
From: John Polstra <jdp@polstra.com>
To: Bruce Evans <bde@zeta.org.au>
Subject: Re: btokup() macro in sys/malloc.h
Cc: current@FreeBSD.ORG
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
On 28-Jan-99 Bruce Evans wrote:
>>The added parentheses don't make any difference, semantically. This
>>change probably wouldn't meet the criteria spelled out in style(9):
>>
>> Unary operators don't require spaces, binary operators do. Don't use
>> parentheses unless they're required for precedence, or the statement is
>> really confusing without them.
>>
>> a = b->c[0] + ~d == (e || f) || g && h ? i : j >> 1;
>> k = !(l & FLAGS);
>
> Nah, style(9), not to mention the example of btokup() in Lite1 and Lite2,
> requires paretheses here (in btokup(), and probably in the bad example in
> style(9), because the expression would be really confusing without them :-).
Hear ye, hear ye! Be it here noted and archived for all eternity that
on January 27, 1999 Pacific Time, John Polstra was, for one fleeting
moment, purer than Bruce! :-)
John
---
John Polstra jdp@polstra.com
John D. Polstra & Co., Inc. Seattle, Washington USA
"Nobody ever went broke underestimating the taste of the American public."
-- H. L. Mencken
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Wed Jan 27 21:48:52 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id VAA16987
for freebsd-current-outgoing; Wed, 27 Jan 1999 21:48:52 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from ns.mt.sri.com (sri-gw.MT.net [206.127.105.141])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA16980
for <current@FreeBSD.ORG>; Wed, 27 Jan 1999 21:48:50 -0800 (PST)
(envelope-from nate@mt.sri.com)
Received: from mt.sri.com (rocky.mt.sri.com [206.127.76.100])
by ns.mt.sri.com (8.8.8/8.8.8) with SMTP id WAA10790;
Wed, 27 Jan 1999 22:48:41 -0700 (MST)
(envelope-from nate@rocky.mt.sri.com)
Received: by mt.sri.com (SMI-8.6/SMI-SVR4)
id WAA26377; Wed, 27 Jan 1999 22:48:40 -0700
Date: Wed, 27 Jan 1999 22:48:40 -0700
Message-Id: <199901280548.WAA26377@mt.sri.com>
From: Nate Williams <nate@mt.sri.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
To: "Daniel C. Sobral" <dcs@newsguy.com>
Cc: Sean Eric Fagan <sef@kithrup.com>, current@FreeBSD.ORG
Subject: Re: "JAIL" code headed for -current.
In-Reply-To: <36AFE842.4D040D83@newsguy.com>
References: <199901271944.LAA15317@kithrup.com>
<36AFE842.4D040D83@newsguy.com>
X-Mailer: VM 6.34 under 19.16 "Lille" XEmacs Lucid
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
> > > suser(NOJAIL, bla, bla);
> > >or
> > > suser(0, bla, bla);
> >
> > Oh, goody, more gratuitious incomaptibilities with everyone else.
>
> Incompatibility, yes, but gratuitous?
Sure. It could be done by adding a new call w/out being gratitious and
still giving the same functionality. See SEF's followup posting.
Nate
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Wed Jan 27 21:54:27 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id VAA17770
for freebsd-current-outgoing; Wed, 27 Jan 1999 21:54:27 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from cimlogic.com.au (cimlog.lnk.telstra.net [139.130.51.31])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA17765
for <current@FreeBSD.ORG>; Wed, 27 Jan 1999 21:54:24 -0800 (PST)
(envelope-from jb@cimlogic.com.au)
Received: (from jb@localhost)
by cimlogic.com.au (8.9.1/8.9.1) id QAA07918;
Thu, 28 Jan 1999 16:58:06 +1100 (EST)
(envelope-from jb)
From: John Birrell <jb@cimlogic.com.au>
Message-Id: <199901280558.QAA07918@cimlogic.com.au>
Subject: Re: btokup() macro in sys/malloc.h
In-Reply-To: <199901280540.WAA26288@mt.sri.com> from Nate Williams at "Jan 27, 1999 10:40:16 pm"
To: nate@mt.sri.com (Nate Williams)
Date: Thu, 28 Jan 1999 16:58:06 +1100 (EST)
Cc: archie@whistle.com, wollman@khavrinen.lcs.mit.edu, current@FreeBSD.ORG
X-Mailer: ELM [version 2.4ME+ PL43 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
Nate Williams wrote:
> > Anyway, if we're going to -Wall'ify the kernel (as we should)
> > then we need to update sytle(9) to reflect that.
> >
> > In fact, style(9) should say:
> >
> > If at all possible, your code should compile without warnings
> > when the gcc -Wall flag is given.
>
> I disagree. As has been shown many times in the past (and I suspect the
> down-under constituent will show that at least a couple of the
I think you must mean the "Sydney-down-under constituent". There *is*
a difference. 8-)
> 'warnings' fixes will be wrong and hide bogus code), making -Wall a goal
> causes people to cover up bad code with bad casts and such.
>
> '-Wall' is *NOT* a good design goal.
Fixing warnings with bad casts is a problem, sure, but asking people
to write code without casts (if possible) that will compile cleanly with
-Wall is a reasonable thing to ask IMO. In my experience, the resulting
code tends to be more portable across architectures with different
pointer/long sizes and endian-ness.
Just my 0.02, and I hate style(9) anyway.
--
John Birrell - jb@cimlogic.com.au; jb@freebsd.org http://www.cimlogic.com.au/
CIMlogic Pty Ltd, GPO Box 117A, Melbourne Vic 3001, Australia +61 418 353 137
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Wed Jan 27 21:56:55 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id VAA18170
for freebsd-current-outgoing; Wed, 27 Jan 1999 21:56:55 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from cimlogic.com.au (cimlog.lnk.telstra.net [139.130.51.31])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA18162
for <current@FreeBSD.ORG>; Wed, 27 Jan 1999 21:56:52 -0800 (PST)
(envelope-from jb@cimlogic.com.au)
Received: (from jb@localhost)
by cimlogic.com.au (8.9.1/8.9.1) id RAA07941;
Thu, 28 Jan 1999 17:00:57 +1100 (EST)
(envelope-from jb)
From: John Birrell <jb@cimlogic.com.au>
Message-Id: <199901280600.RAA07941@cimlogic.com.au>
Subject: Re: btokup() macro in sys/malloc.h
In-Reply-To: <XFMail.990127214511.jdp@polstra.com> from John Polstra at "Jan 27, 1999 9:45:11 pm"
To: jdp@polstra.com (John Polstra)
Date: Thu, 28 Jan 1999 17:00:57 +1100 (EST)
Cc: bde@zeta.org.au, current@FreeBSD.ORG
X-Mailer: ELM [version 2.4ME+ PL43 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
John Polstra wrote:
> On 28-Jan-99 Bruce Evans wrote:
> > Nah, style(9), not to mention the example of btokup() in Lite1 and Lite2,
> > requires paretheses here (in btokup(), and probably in the bad example in
> > style(9), because the expression would be really confusing without them :-).
>
> Hear ye, hear ye! Be it here noted and archived for all eternity that
> on January 27, 1999 Pacific Time, John Polstra was, for one fleeting
> moment, purer than Bruce! :-)
OK, so now we have to shoot you too. Oh well, so be it....
Are there any others who would like to join these purists? Come on,
we have bullets for you all...
--
John Birrell - jb@cimlogic.com.au; jb@freebsd.org http://www.cimlogic.com.au/
CIMlogic Pty Ltd, GPO Box 117A, Melbourne Vic 3001, Australia +61 418 353 137
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Wed Jan 27 22:00:02 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id WAA18550
for freebsd-current-outgoing; Wed, 27 Jan 1999 22:00:02 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA18502
for <current@FreeBSD.ORG>; Wed, 27 Jan 1999 22:00:00 -0800 (PST)
(envelope-from dillon@apollo.backplane.com)
Received: (from dillon@localhost)
by apollo.backplane.com (8.9.2/8.9.1) id VAA93563;
Wed, 27 Jan 1999 21:59:53 -0800 (PST)
(envelope-from dillon)
Date: Wed, 27 Jan 1999 21:59:53 -0800 (PST)
From: Matthew Dillon <dillon@apollo.backplane.com>
Message-Id: <199901280559.VAA93563@apollo.backplane.com>
To: Bruce Evans <bde@zeta.org.au>
Cc: archie@whistle.com, current@FreeBSD.ORG
Subject: Re: kern/subr_scanf array index of signed char
References: <199901280424.PAA01617@godzilla.zeta.org.au>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
:> Actually, it could very well be that I don't. I didn't want to spend
:> the time to check to see if the compiler warned on unsigned-char array
:> indexes. You can change it back if unsigned char array indexes do not
:> produce a warning.
:
:Sloppy thinking. How would you know if you fixed the bug unless you checked
:that you fixed the bug instead of breaking the warning? The bug was that
:on systems with signed chars, *inp gave negative array indexes if the
:caller passes a format string with negative characters in certain positions.
:There are still lots of related isfoo(*inp) bugs. All these bugs are more
:serious in the userland.
:
:Bruce
Oh come on, give me some credit -- I knew I fixed the bug by casting
it to unsigned char. But after spending over 8 hours working the
files over so people compiling the kernel don't get overwhelmed
with warnings I was getting a bit fermented in the chair.
-Matt
Matthew Dillon
<dillon@backplane.com>
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Wed Jan 27 22:03:47 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id WAA18912
for freebsd-current-outgoing; Wed, 27 Jan 1999 22:03:47 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA18899
for <current@FreeBSD.ORG>; Wed, 27 Jan 1999 22:03:44 -0800 (PST)
(envelope-from dillon@apollo.backplane.com)
Received: (from dillon@localhost)
by apollo.backplane.com (8.9.2/8.9.1) id WAA93627;
Wed, 27 Jan 1999 22:03:41 -0800 (PST)
(envelope-from dillon)
Date: Wed, 27 Jan 1999 22:03:41 -0800 (PST)
From: Matthew Dillon <dillon@apollo.backplane.com>
Message-Id: <199901280603.WAA93627@apollo.backplane.com>
To: Nate Williams <nate@mt.sri.com>
Cc: Archie Cobbs <archie@whistle.com>,
wollman@khavrinen.lcs.mit.edu (Garrett Wollman), current@FreeBSD.ORG
Subject: Re: btokup() macro in sys/malloc.h
References: <199901280222.VAA14212@khavrinen.lcs.mit.edu>
<199901280229.SAA20207@bubba.whistle.com> <199901280540.WAA26288@mt.sri.com>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
:> then we need to update sytle(9) to reflect that.
:>
:> In fact, style(9) should say:
:>
:> If at all possible, your code should compile without warnings
:> when the gcc -Wall flag is given.
:
:I disagree. As has been shown many times in the past (and I suspect the
:down-under constituent will show that at least a couple of the
:'warnings' fixes will be wrong and hide bogus code), making -Wall a goal
:causes people to cover up bad code with bad casts and such.
:
:'-Wall' is *NOT* a good design goal.
Nonsense. -Wall does *NOT* contribute to a bad programmer programming
badly, and I found at least three fairly serious mistakes when I turned
it on.
I mean, come on... by your argument the compiler might as well give up
and not bother warning you about anything!
-Matt
Matthew Dillon
<dillon@backplane.com>
:Nate
:
:To Unsubscribe: send mail to majordomo@FreeBSD.org
:with "unsubscribe freebsd-current" in the body of the message
:
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Wed Jan 27 22:03:47 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id WAA18913
for freebsd-current-outgoing; Wed, 27 Jan 1999 22:03:47 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from smtp04.wxs.nl (smtp04.wxs.nl [195.121.6.59])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA18896
for <current@freebsd.org>; Wed, 27 Jan 1999 22:03:44 -0800 (PST)
(envelope-from asmodai@wxs.nl)
Received: from daemon.ninth-circle.org ([195.121.57.231]) by smtp04.wxs.nl
(Netscape Messaging Server 3.6) with ESMTP id AAA175F;
Thu, 28 Jan 1999 07:03:41 +0100
Message-ID: <XFMail.990128071216.asmodai@wxs.nl>
X-Mailer: XFMail 1.3 [p0] on FreeBSD
X-Priority: 3 (Normal)
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 8bit
MIME-Version: 1.0
In-Reply-To: <Pine.OSF.4.05.9901280927530.22605-100000@bragg>
Date: Thu, 28 Jan 1999 07:12:16 +0100 (CET)
Organization: Ninth Circle Enterprises
From: Jeroen Ruigrok/Asmodai <asmodai@wxs.nl>
To: Kris Kennaway <kkennawa@physics.adelaide.edu.au>
Subject: RE: One answer, one question.
Cc: current@FreeBSD.ORG, Brian Feldman <green@unixhelp.org>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
On 27-Jan-99 Kris Kennaway wrote:
> What's there to compile with netscape? It's provided in binary form,
> which means it's statically linked with some libraries at build time by
> the netscape people (e.g. the motif library), and is dynamically linked
> against some of the a.out libraries on your system (which means that
> nothing changes in the binary because it's, well, dynamic). In either
> case there's nothing to be changed by re-extracting the binary and
> installing it.
Nah, I was mixing two terms: compiling and remaking the port. I meant the
latter, but saw when remaking that it wasn't the average source-like port.
sorry for the misunderstanding...
---
Jeroen Ruigrok van der Werven It's a Dance of Energy,
asmodai(at)wxs.nl when the Mind goes Binary...
Network/Security Specialist <http://home.wxs.nl/~asmodai>
BSD & picoBSD: The Power to Serve <http://www.freebsd.org>
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Wed Jan 27 22:04:16 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id WAA19044
for freebsd-current-outgoing; Wed, 27 Jan 1999 22:04:16 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from pcpsj.pfcs.com (harlan.clark.net [168.143.10.179])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA19036
for <current@FreeBSD.ORG>; Wed, 27 Jan 1999 22:04:12 -0800 (PST)
(envelope-from Harlan.Stenn@pfcs.com)
Received: from mumps.pfcs.com [192.52.69.11] (HELO mumps.pfcs.com)
by pcpsj.pfcs.com (8.8.8/8.8.8) via ESMTP
id <BAA12489-Harlan.Stenn@pfcs.com>;
Thu, 28 Jan 1999 01:02:15 -0500 (EST)
Received: from brown.pfcs.com [192.52.69.44] (HELO brown.pfcs.com)
by mumps.pfcs.com (8.8.8/8.8.8) via ESMTP
id <WAA02152-harlan@pfcs.com>;
Wed, 27 Jan 1999 22:02:13 -0800 (PST)
Received: from localhost [127.0.0.1] (HELO brown.pfcs.com)
by brown.pfcs.com (8.8.8/8.8.8) via ESMTP
id <BAA20944-harlan@pfcs.com>;
Thu, 28 Jan 1999 01:01:31 -0500 (EST)
X-Mailer: exmh version 2.0.2 2/24/98
To: "Daniel O'Connor" <doconnor@gsoft.com.au>
cc: Wilko Bulte <wilko@yedi.iaf.nl>, current@FreeBSD.ORG, dfr@nlsystems.com,
archie@whistle.com (Archie Cobbs)
Subject: Re: DEVFS, the time has come...
In-Reply-To: "Daniel O'Connor"'s (doconnor@gsoft.com.au) message
dated Thu, 28 Jan 1999 15:59:52. <XFMail.990128155952.doconnor@gsoft.com.au>
X-Face: "csXK}xnnsH\h_ce`T#|pM]tG,6Xu.{3Rb\]&XJgVyTS'w{E+|-(}n<m88'RZQA.<2]zo&R
I8nHuPumSNjsAN&WGhll?v}1#%)~2%QI~4Vs%IuWb#OmZmKck_1Ee&C\k&vJ}BWx:Bb#Mx8>:c(Cc*
$cbtusxDP6T)Hr'k&zrwq0.3&~bAI~YJco[r.mE+K|(q]F=ZNXug:s6tyOk{VTqARy0#axm6BWti9C
d
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Thu, 28 Jan 1999 01:01:30 -0500
Message-ID: <20942.917503290@brown.pfcs.com>
From: Harlan Stenn <Harlan.Stenn@pfcs.com>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
> Also the eth[0..x] thing means you can replace your ethernet card with a
> new one of a different type without having to look through your config
> code for references to ed0 or whatever.
Just to ask, what happens when the probe order changes and your multiple
NICs start popping up on the wrong eth port?
This may be *much* more difficult when one of several cards die (how do you
know which one broke?) and then you replace it and discover the new probe
order is different...
Or will be be able to wire them down in the config file (which will at
least address part of the problem)?
H
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Wed Jan 27 22:04:21 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id WAA19057
for freebsd-current-outgoing; Wed, 27 Jan 1999 22:04:21 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA19039
for <current@FreeBSD.ORG>; Wed, 27 Jan 1999 22:04:15 -0800 (PST)
(envelope-from jdp@polstra.com)
Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13])
by wall.polstra.com (8.9.1/8.9.1) with ESMTP id WAA03599;
Wed, 27 Jan 1999 22:03:40 -0800 (PST)
(envelope-from jdp@polstra.com)
Received: (from jdp@localhost)
by vashon.polstra.com (8.9.1/8.9.1) id WAA07249;
Wed, 27 Jan 1999 22:03:40 -0800 (PST)
(envelope-from jdp@polstra.com)
Message-ID: <XFMail.990127220340.jdp@polstra.com>
X-Mailer: XFMail 1.3 [p0] on FreeBSD
X-Priority: 3 (Normal)
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 8bit
MIME-Version: 1.0
In-Reply-To: <199901280600.RAA07941@cimlogic.com.au>
Date: Wed, 27 Jan 1999 22:03:40 -0800 (PST)
Organization: Polstra & Co., Inc.
From: John Polstra <jdp@polstra.com>
To: John Birrell <jb@cimlogic.com.au>
Subject: Re: btokup() macro in sys/malloc.h
Cc: current@FreeBSD.ORG, bde@zeta.org.au
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
On 28-Jan-99 John Birrell wrote:
> John Polstra wrote:
>>
>> Hear ye, hear ye! Be it here noted and archived for all eternity that
>> on January 27, 1999 Pacific Time, John Polstra was, for one fleeting
>> moment, purer than Bruce! :-)
>
> OK, so now we have to shoot you too. Oh well, so be it....
>
> Are there any others who would like to join these purists? Come on,
> we have bullets for you all...
Bah! You might be able to hit Bruce over there in oz. But to hit me,
you'd need an ICBM. Give me purity or give me death! Bwahahahahah!
John
---
John Polstra jdp@polstra.com
John D. Polstra & Co., Inc. Seattle, Washington USA
"Nobody ever went broke underestimating the taste of the American public."
-- H. L. Mencken
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Wed Jan 27 22:09:06 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id WAA19721
for freebsd-current-outgoing; Wed, 27 Jan 1999 22:09:06 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from cain.gsoft.com.au (genesi.lnk.telstra.net [139.130.136.161])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA19710
for <current@FreeBSD.ORG>; Wed, 27 Jan 1999 22:09:02 -0800 (PST)
(envelope-from doconnor@gsoft.com.au)
Received: from lot.gsoft.com.au (doconnor@lot.gsoft.com.au [203.38.152.106])
by cain.gsoft.com.au (8.8.8/8.8.8) with ESMTP id QAA29748;
Thu, 28 Jan 1999 16:37:45 +1030 (CST)
(envelope-from doconnor@gsoft.com.au)
Message-ID: <XFMail.990128164639.doconnor@gsoft.com.au>
X-Mailer: XFMail 1.3 [p0] on FreeBSD
X-Priority: 3 (Normal)
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 8bit
MIME-Version: 1.0
In-Reply-To: <20942.917503290@brown.pfcs.com>
Date: Thu, 28 Jan 1999 16:46:39 +1030 (CST)
From: "Daniel O'Connor" <doconnor@gsoft.com.au>
To: Harlan Stenn <Harlan.Stenn@pfcs.com>
Subject: Re: DEVFS, the time has come...
Cc: (Archie Cobbs) <archie@whistle.com>, dfr@nlsystems.com,
current@FreeBSD.ORG, Wilko Bulte <wilko@yedi.iaf.nl>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
On 28-Jan-99 Harlan Stenn wrote:
> > code for references to ed0 or whatever.
> Just to ask, what happens when the probe order changes and your multiple
> NICs start popping up on the wrong eth port?
Thats why I mentioned wiring them down a la SCSI.
> Or will be be able to wire them down in the config file (which will at
> least address part of the problem)?
IMHO it would address ALL of the problem..
---
Daniel O'Connor software and network engineer
for Genesis Software - http://www.gsoft.com.au
"The nice thing about standards is that there
are so many of them to choose from."
-- Andrew Tanenbaum
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Wed Jan 27 22:12:50 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id WAA20187
for freebsd-current-outgoing; Wed, 27 Jan 1999 22:12:50 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA20176
for <current@FreeBSD.ORG>; Wed, 27 Jan 1999 22:12:48 -0800 (PST)
(envelope-from dillon@apollo.backplane.com)
Received: (from dillon@localhost)
by apollo.backplane.com (8.9.2/8.9.1) id WAA93764;
Wed, 27 Jan 1999 22:12:31 -0800 (PST)
(envelope-from dillon)
Date: Wed, 27 Jan 1999 22:12:31 -0800 (PST)
From: Matthew Dillon <dillon@apollo.backplane.com>
Message-Id: <199901280612.WAA93764@apollo.backplane.com>
To: John Birrell <jb@cimlogic.com.au>
Cc: nate@mt.sri.com (Nate Williams), archie@whistle.com,
wollman@khavrinen.lcs.mit.edu, current@FreeBSD.ORG
Subject: Re: btokup() macro in sys/malloc.h
References: <199901280558.QAA07918@cimlogic.com.au>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
:I think you must mean the "Sydney-down-under constituent". There *is*
:a difference. 8-)
:
:> 'warnings' fixes will be wrong and hide bogus code), making -Wall a goal
:> causes people to cover up bad code with bad casts and such.
:>
:> '-Wall' is *NOT* a good design goal.
:
:Fixing warnings with bad casts is a problem, sure, but asking people
:to write code without casts (if possible) that will compile cleanly with
:-Wall is a reasonable thing to ask IMO. In my experience, the resulting
:code tends to be more portable across architectures with different
:pointer/long sizes and endian-ness.
:
:Just my 0.02, and I hate style(9) anyway.
Not to mention that I was also able to enable -Wcast-qual. That is a
MAJOR step forward, people. Just for starters it caught a serious bug
in the kernel getenv(). Being able to use const the way it's supposed
to be used is important... VERY important, and until now the kernel's
been casting things in and out of const and volatile almost at will,
not mention improperly declaring const pointers verses pointer-to-const
and other things.
-Matt
Matthew Dillon
<dillon@backplane.com>
:--
:John Birrell - jb@cimlogic.com.au; jb@freebsd.org http://www.cimlogic.com.au/
:CIMlogic Pty Ltd, GPO Box 117A, Melbourne Vic 3001, Australia +61 418 353 137
:
:To Unsubscribe: send mail to majordomo@FreeBSD.org
:with "unsubscribe freebsd-current" in the body of the message
:
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Wed Jan 27 22:13:18 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id WAA20241
for freebsd-current-outgoing; Wed, 27 Jan 1999 22:13:18 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.26.10.9])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA20236
for <freebsd-current@FreeBSD.ORG>; Wed, 27 Jan 1999 22:13:14 -0800 (PST)
(envelope-from bde@godzilla.zeta.org.au)
Received: (from bde@localhost)
by godzilla.zeta.org.au (8.8.7/8.8.7) id RAA13010;
Thu, 28 Jan 1999 17:12:43 +1100
Date: Thu, 28 Jan 1999 17:12:43 +1100
From: Bruce Evans <bde@zeta.org.au>
Message-Id: <199901280612.RAA13010@godzilla.zeta.org.au>
To: axl@iafrica.com, pantzer@ludd.luth.se
Subject: Re: NIS with HPUX 10.20
Cc: freebsd-current@FreeBSD.ORG
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
>> If installworld assumes single-user mode, why do we install -C
>> ld-elf.so.1 ? The first time I asked this question, I didn't mention
>> ...
>Why _not_ use -C? What is the point in replacing a file with the same file?
>install -C will replace the file if the new file is diffrent.
Plain install may be a bit faster, and some people may like all timestamps
to be set to the time of the install.
Using -C is optional. I always use it (and -p).
>That is realy good if you do backups as only the new files will be in the
>backup.
That's the main reason for -C.
>And it is good if installworld works on a active system even if it is not
>supported.
Plain install should work just as well for that (it doesn't).
Bruce
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Wed Jan 27 22:19:31 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id WAA20803
for freebsd-current-outgoing; Wed, 27 Jan 1999 22:19:31 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from cimlogic.com.au (cimlog.lnk.telstra.net [139.130.51.31])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA20767
for <current@FreeBSD.ORG>; Wed, 27 Jan 1999 22:19:26 -0800 (PST)
(envelope-from jb@cimlogic.com.au)
Received: (from jb@localhost)
by cimlogic.com.au (8.9.1/8.9.1) id RAA08026;
Thu, 28 Jan 1999 17:23:42 +1100 (EST)
(envelope-from jb)
From: John Birrell <jb@cimlogic.com.au>
Message-Id: <199901280623.RAA08026@cimlogic.com.au>
Subject: Re: btokup() macro in sys/malloc.h
In-Reply-To: <XFMail.990127220340.jdp@polstra.com> from John Polstra at "Jan 27, 1999 10: 3:40 pm"
To: jdp@polstra.com (John Polstra)
Date: Thu, 28 Jan 1999 17:23:41 +1100 (EST)
Cc: jb@cimlogic.com.au, current@FreeBSD.ORG, bde@zeta.org.au
X-Mailer: ELM [version 2.4ME+ PL43 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
John Polstra wrote:
> Bah! You might be able to hit Bruce over there in oz. But to hit me,
> you'd need an ICBM. Give me purity or give me death! Bwahahahahah!
Nah, I even tried poisoning Sydney's water with something I can't spell,
but even that didn't kill off Bruce. The government told people not to
drink the water. Sigh.
My fallback strategy was to win the Olympics for Sydney and then hope
they get bombed. Time will tell...
--
John Birrell - jb@cimlogic.com.au; jb@freebsd.org http://www.cimlogic.com.au/
CIMlogic Pty Ltd, GPO Box 117A, Melbourne Vic 3001, Australia +61 418 353 137
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Wed Jan 27 22:20:15 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id WAA20964
for freebsd-current-outgoing; Wed, 27 Jan 1999 22:20:15 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from ns.mt.sri.com (sri-gw.MT.net [206.127.105.141])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA20949
for <current@FreeBSD.ORG>; Wed, 27 Jan 1999 22:20:11 -0800 (PST)
(envelope-from nate@mt.sri.com)
Received: from mt.sri.com (rocky.mt.sri.com [206.127.76.100])
by ns.mt.sri.com (8.8.8/8.8.8) with SMTP id XAA11103;
Wed, 27 Jan 1999 23:20:07 -0700 (MST)
(envelope-from nate@rocky.mt.sri.com)
Received: by mt.sri.com (SMI-8.6/SMI-SVR4)
id XAA26671; Wed, 27 Jan 1999 23:20:06 -0700
Date: Wed, 27 Jan 1999 23:20:06 -0700
Message-Id: <199901280620.XAA26671@mt.sri.com>
From: Nate Williams <nate@mt.sri.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
To: John Birrell <jb@cimlogic.com.au>
Cc: nate@mt.sri.com (Nate Williams), archie@whistle.com,
wollman@khavrinen.lcs.mit.edu, current@FreeBSD.ORG
Subject: Re: btokup() macro in sys/malloc.h
In-Reply-To: <199901280558.QAA07918@cimlogic.com.au>
References: <199901280540.WAA26288@mt.sri.com>
<199901280558.QAA07918@cimlogic.com.au>
X-Mailer: VM 6.34 under 19.16 "Lille" XEmacs Lucid
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
> > 'warnings' fixes will be wrong and hide bogus code), making -Wall a goal
> > causes people to cover up bad code with bad casts and such.
> >
> > '-Wall' is *NOT* a good design goal.
>
> Fixing warnings with bad casts is a problem, sure, but asking people
> to write code without casts (if possible) that will compile cleanly with
> -Wall is a reasonable thing to ask IMO.
Agreed. But most of the new code written does indeed compile with
-Wall. It's the code we've 'inherited' that doesn't.
> In my experience, the resulting
> code tends to be more portable across architectures with different
> pointer/long sizes and endian-ness.
This is where I disagree. Too often people cast away the bugs and end
up with overflow and sign problems.
Nate
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Wed Jan 27 22:23:27 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id WAA21216
for freebsd-current-outgoing; Wed, 27 Jan 1999 22:23:27 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from zeus.theinternet.com.au (zeus.theinternet.com.au [203.34.176.2])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA21210
for <current@FreeBSD.ORG>; Wed, 27 Jan 1999 22:23:23 -0800 (PST)
(envelope-from akm@zeus.theinternet.com.au)
Received: (from akm@localhost)
by zeus.theinternet.com.au (8.8.7/8.8.7) id QAA12949;
Thu, 28 Jan 1999 16:23:04 +1000 (EST)
(envelope-from akm)
From: Andrew Kenneth Milton <akm@zeus.theinternet.com.au>
Message-Id: <199901280623.QAA12949@zeus.theinternet.com.au>
Subject: Re: btokup() macro in sys/malloc.h
In-Reply-To: <199901280623.RAA08026@cimlogic.com.au> from John Birrell at "Jan 28, 99 05:23:41 pm"
To: jb@cimlogic.com.au (John Birrell)
Date: Thu, 28 Jan 1999 16:23:04 +1000 (EST)
Cc: jdp@polstra.com, jb@cimlogic.com.au, current@FreeBSD.ORG, bde@zeta.org.au
X-Mailer: ELM [version 2.4ME+ PL32 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
+----[ John Birrell ]---------------------------------------------
| John Polstra wrote:
| > Bah! You might be able to hit Bruce over there in oz. But to hit me,
| > you'd need an ICBM. Give me purity or give me death! Bwahahahahah!
|
| Nah, I even tried poisoning Sydney's water with something I can't spell,
| but even that didn't kill off Bruce. The government told people not to
| drink the water. Sigh.
|
| My fallback strategy was to win the Olympics for Sydney and then hope
| they get bombed. Time will tell...
Living in Sydney is a fate worse than death anyway :-)
--
Totally Holistic Enterprises Internet| P:+61 7 3870 0066 | Andrew
The Internet (Aust) Pty Ltd | F:+61 7 3870 4477 | Milton
ACN: 082 081 472 | M:+61 416 022 411 |72 Col .Sig
PO Box 837 Indooroopilly QLD 4068 |akm@theinternet.com.au|Specialist
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Wed Jan 27 22:26:04 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id WAA21382
for freebsd-current-outgoing; Wed, 27 Jan 1999 22:25:43 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from cimlogic.com.au (cimlog.lnk.telstra.net [139.130.51.31])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA21374
for <current@FreeBSD.ORG>; Wed, 27 Jan 1999 22:25:39 -0800 (PST)
(envelope-from jb@cimlogic.com.au)
Received: (from jb@localhost)
by cimlogic.com.au (8.9.1/8.9.1) id RAA08066;
Thu, 28 Jan 1999 17:29:41 +1100 (EST)
(envelope-from jb)
From: John Birrell <jb@cimlogic.com.au>
Message-Id: <199901280629.RAA08066@cimlogic.com.au>
Subject: Re: btokup() macro in sys/malloc.h
In-Reply-To: <199901280620.XAA26671@mt.sri.com> from Nate Williams at "Jan 27, 1999 11:20: 6 pm"
To: nate@mt.sri.com (Nate Williams)
Date: Thu, 28 Jan 1999 17:29:41 +1100 (EST)
Cc: jb@cimlogic.com.au, nate@mt.sri.com, archie@whistle.com,
wollman@khavrinen.lcs.mit.edu, current@FreeBSD.ORG
X-Mailer: ELM [version 2.4ME+ PL43 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
Nate Williams wrote:
> > Fixing warnings with bad casts is a problem, sure, but asking people
> > to write code without casts (if possible) that will compile cleanly with
> > -Wall is a reasonable thing to ask IMO.
>
> Agreed. But most of the new code written does indeed compile with
> -Wall. It's the code we've 'inherited' that doesn't.
OK, so we can review the fixes and improve things for the future.
> > In my experience, the resulting
> > code tends to be more portable across architectures with different
> > pointer/long sizes and endian-ness.
>
> This is where I disagree. Too often people cast away the bugs and end
> up with overflow and sign problems.
We still have Bruce to review code for inappropriate casts etc. Try and
stop him. 8-)
--
John Birrell - jb@cimlogic.com.au; jb@freebsd.org http://www.cimlogic.com.au/
CIMlogic Pty Ltd, GPO Box 117A, Melbourne Vic 3001, Australia +61 418 353 137
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Wed Jan 27 22:27:51 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id WAA21567
for freebsd-current-outgoing; Wed, 27 Jan 1999 22:27:51 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from ns.mt.sri.com (sri-gw.MT.net [206.127.105.141])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA21556
for <current@FreeBSD.ORG>; Wed, 27 Jan 1999 22:27:48 -0800 (PST)
(envelope-from nate@mt.sri.com)
Received: from mt.sri.com (rocky.mt.sri.com [206.127.76.100])
by ns.mt.sri.com (8.8.8/8.8.8) with SMTP id XAA11175;
Wed, 27 Jan 1999 23:27:44 -0700 (MST)
(envelope-from nate@rocky.mt.sri.com)
Received: by mt.sri.com (SMI-8.6/SMI-SVR4)
id XAA26773; Wed, 27 Jan 1999 23:27:43 -0700
Date: Wed, 27 Jan 1999 23:27:43 -0700
Message-Id: <199901280627.XAA26773@mt.sri.com>
From: Nate Williams <nate@mt.sri.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
To: John Birrell <jb@cimlogic.com.au>
Cc: nate@mt.sri.com (Nate Williams), archie@whistle.com,
wollman@khavrinen.lcs.mit.edu, current@FreeBSD.ORG
Subject: Re: btokup() macro in sys/malloc.h
In-Reply-To: <199901280629.RAA08066@cimlogic.com.au>
References: <199901280620.XAA26671@mt.sri.com>
<199901280629.RAA08066@cimlogic.com.au>
X-Mailer: VM 6.34 under 19.16 "Lille" XEmacs Lucid
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
> > > Fixing warnings with bad casts is a problem, sure, but asking people
> > > to write code without casts (if possible) that will compile cleanly with
> > > -Wall is a reasonable thing to ask IMO.
> >
> > Agreed. But most of the new code written does indeed compile with
> > -Wall. It's the code we've 'inherited' that doesn't.
>
> OK, so we can review the fixes and improve things for the future.
>
> > > In my experience, the resulting
> > > code tends to be more portable across architectures with different
> > > pointer/long sizes and endian-ness.
> >
> > This is where I disagree. Too often people cast away the bugs and end
> > up with overflow and sign problems.
>
> We still have Bruce to review code for inappropriate casts etc. Try and
> stop him. 8-)
Bruce can not and should not be the *ONLY* reviewer we have. Matt's
fixes are overwhelming even for him.
Nate
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Wed Jan 27 22:29:44 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id WAA21710
for freebsd-current-outgoing; Wed, 27 Jan 1999 22:29:44 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from ns.mt.sri.com (sri-gw.MT.net [206.127.105.141])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA21704
for <current@FreeBSD.ORG>; Wed, 27 Jan 1999 22:29:41 -0800 (PST)
(envelope-from nate@mt.sri.com)
Received: from mt.sri.com (rocky.mt.sri.com [206.127.76.100])
by ns.mt.sri.com (8.8.8/8.8.8) with SMTP id XAA11205;
Wed, 27 Jan 1999 23:29:38 -0700 (MST)
(envelope-from nate@rocky.mt.sri.com)
Received: by mt.sri.com (SMI-8.6/SMI-SVR4)
id XAA26798; Wed, 27 Jan 1999 23:29:37 -0700
Date: Wed, 27 Jan 1999 23:29:37 -0700
Message-Id: <199901280629.XAA26798@mt.sri.com>
From: Nate Williams <nate@mt.sri.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
To: Matthew Dillon <dillon@apollo.backplane.com>
Cc: Nate Williams <nate@mt.sri.com>, Archie Cobbs <archie@whistle.com>,
wollman@khavrinen.lcs.mit.edu (Garrett Wollman), current@FreeBSD.ORG
Subject: Re: btokup() macro in sys/malloc.h
In-Reply-To: <199901280603.WAA93627@apollo.backplane.com>
References: <199901280222.VAA14212@khavrinen.lcs.mit.edu>
<199901280229.SAA20207@bubba.whistle.com>
<199901280540.WAA26288@mt.sri.com>
<199901280603.WAA93627@apollo.backplane.com>
X-Mailer: VM 6.34 under 19.16 "Lille" XEmacs Lucid
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
> :> then we need to update sytle(9) to reflect that.
> :>
> :> In fact, style(9) should say:
> :>
> :> If at all possible, your code should compile without warnings
> :> when the gcc -Wall flag is given.
> :
> :I disagree. As has been shown many times in the past (and I suspect the
> :down-under constituent will show that at least a couple of the
> :'warnings' fixes will be wrong and hide bogus code), making -Wall a goal
> :causes people to cover up bad code with bad casts and such.
> :
> :'-Wall' is *NOT* a good design goal.
>
> Nonsense. -Wall does *NOT* contribute to a bad programmer programming
> badly, and I found at least three fairly serious mistakes when I turned
> it on.
And introduced at least one. If you were a programmer under my charge,
I'd tell you to use the warnings to fix only those bugs you are sure of
and leave the others alone.
> I mean, come on... by your argument the compiler might as well give up
> and not bother warning you about anything!
A warning is just that. It's not an error, so don't treat it like one.
Nate
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Wed Jan 27 22:41:11 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id WAA23073
for freebsd-current-outgoing; Wed, 27 Jan 1999 22:41:11 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA23068
for <current@FreeBSD.ORG>; Wed, 27 Jan 1999 22:41:10 -0800 (PST)
(envelope-from dillon@apollo.backplane.com)
Received: (from dillon@localhost)
by apollo.backplane.com (8.9.2/8.9.1) id WAA96133;
Wed, 27 Jan 1999 22:41:04 -0800 (PST)
(envelope-from dillon)
Date: Wed, 27 Jan 1999 22:41:04 -0800 (PST)
From: Matthew Dillon <dillon@apollo.backplane.com>
Message-Id: <199901280641.WAA96133@apollo.backplane.com>
To: Nate Williams <nate@mt.sri.com>
Cc: Archie Cobbs <archie@whistle.com>,
wollman@khavrinen.lcs.mit.edu (Garrett Wollman), current@FreeBSD.ORG
Subject: Re: btokup() macro in sys/malloc.h
References: <199901280222.VAA14212@khavrinen.lcs.mit.edu>
<199901280229.SAA20207@bubba.whistle.com>
<199901280540.WAA26288@mt.sri.com>
<199901280603.WAA93627@apollo.backplane.com> <199901280629.XAA26798@mt.sri.com>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
:
:And introduced at least one. If you were a programmer under my charge,
:I'd tell you to use the warnings to fix only those bugs you are sure of
:and leave the others alone.
Nate, if you were a programmer under my charge you'd be heading out
the door with your final paycheck. Your attitude smacks of a
superiority complex that leaves a bad taste in my mouth. You don't
know shit about me, so don't expect to get away with talking down
to me. I'm not a fucking 16 year old. Right now, my opinion of
*your* skills is rather at a low point.
-Matt
Matthew Dillon
<dillon@backplane.com>
:
:Nate
:
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Wed Jan 27 22:46:34 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id WAA23844
for freebsd-current-outgoing; Wed, 27 Jan 1999 22:46:34 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from ns.mt.sri.com (sri-gw.MT.net [206.127.105.141])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA23819
for <current@FreeBSD.ORG>; Wed, 27 Jan 1999 22:46:29 -0800 (PST)
(envelope-from nate@mt.sri.com)
Received: from mt.sri.com (rocky.mt.sri.com [206.127.76.100])
by ns.mt.sri.com (8.8.8/8.8.8) with SMTP id XAA11363;
Wed, 27 Jan 1999 23:46:26 -0700 (MST)
(envelope-from nate@rocky.mt.sri.com)
Received: by mt.sri.com (SMI-8.6/SMI-SVR4)
id XAA26976; Wed, 27 Jan 1999 23:46:25 -0700
Date: Wed, 27 Jan 1999 23:46:25 -0700
Message-Id: <199901280646.XAA26976@mt.sri.com>
From: Nate Williams <nate@mt.sri.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
To: Matthew Dillon <dillon@apollo.backplane.com>
Cc: Nate Williams <nate@mt.sri.com>, current@FreeBSD.ORG
Subject: Re: btokup() macro in sys/malloc.h
In-Reply-To: <199901280641.WAA96133@apollo.backplane.com>
References: <199901280222.VAA14212@khavrinen.lcs.mit.edu>
<199901280229.SAA20207@bubba.whistle.com>
<199901280540.WAA26288@mt.sri.com>
<199901280603.WAA93627@apollo.backplane.com>
<199901280629.XAA26798@mt.sri.com>
<199901280641.WAA96133@apollo.backplane.com>
X-Mailer: VM 6.34 under 19.16 "Lille" XEmacs Lucid
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
> :And introduced at least one. If you were a programmer under my charge,
> :I'd tell you to use the warnings to fix only those bugs you are sure of
> :and leave the others alone.
>
> Nate, if you were a programmer under my charge you'd be heading out
> the door with your final paycheck. Your attitude smacks of a
> superiority complex that leaves a bad taste in my mouth.
Your the one introducing bugs, not me.
> You don't
> know shit about me, so don't expect to get away with talking down
> to me.
I'm not talking down to you.
> I'm not a fucking 16 year old.
No, you know more than me and everyone else, and you've been talking
down to everyone. You've got the attitude problem.
> Right now, my opinion of *your* skills is rather at a low
> point.
My people skills have never been great, but I can live with that. But,
I'm not the person defending introduction of bugs in FreeBSD as a 'good
thing'.
Nate
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Wed Jan 27 22:51:13 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id WAA24370
for freebsd-current-outgoing; Wed, 27 Jan 1999 22:51:13 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from whistle.com (s205m131.whistle.com [207.76.205.131])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA24364
for <current@FreeBSD.ORG>; Wed, 27 Jan 1999 22:51:12 -0800 (PST)
(envelope-from archie@whistle.com)
Received: (from smap@localhost) by whistle.com (8.7.5/8.6.12) id WAA29227; Wed, 27 Jan 1999 22:50:40 -0800 (PST)
Received: from bubba.whistle.com( 207.76.205.7) by whistle.com via smap (V2.0)
id xma029225; Wed, 27 Jan 99 22:50:23 -0800
Received: (from archie@localhost) by bubba.whistle.com (8.8.7/8.6.12) id WAA24262; Wed, 27 Jan 1999 22:50:23 -0800 (PST)
From: Archie Cobbs <archie@whistle.com>
Message-Id: <199901280650.WAA24262@bubba.whistle.com>
Subject: Re: btokup() macro in sys/malloc.h
In-Reply-To: <199901280540.WAA26288@mt.sri.com> from Nate Williams at "Jan 27, 99 10:40:16 pm"
To: nate@mt.sri.com (Nate Williams)
Date: Wed, 27 Jan 1999 22:50:23 -0800 (PST)
Cc: current@FreeBSD.ORG
X-Mailer: ELM [version 2.4ME+ PL38 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
Nate Williams writes:
> > In fact, style(9) should say:
> >
> > If at all possible, your code should compile without warnings
> > when the gcc -Wall flag is given.
>
> I disagree. As has been shown many times in the past (and I suspect the
> down-under constituent will show that at least a couple of the
> 'warnings' fixes will be wrong and hide bogus code), making -Wall a goal
> causes people to cover up bad code with bad casts and such.
>
> '-Wall' is *NOT* a good design goal.
Well, I respectfully disagree with that. If you're "fixing" warnings
by hiding them, then the problem is with the programmer, not the
compiler.
-Archie
___________________________________________________________________________
Archie Cobbs * Whistle Communications, Inc. * http://www.whistle.com
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Wed Jan 27 22:56:13 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id WAA25010
for freebsd-current-outgoing; Wed, 27 Jan 1999 22:56:13 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from whistle.com (s205m131.whistle.com [207.76.205.131])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA25003
for <current@FreeBSD.ORG>; Wed, 27 Jan 1999 22:56:12 -0800 (PST)
(envelope-from archie@whistle.com)
Received: (from smap@localhost) by whistle.com (8.7.5/8.6.12) id WAA29273; Wed, 27 Jan 1999 22:55:41 -0800 (PST)
Received: from bubba.whistle.com( 207.76.205.7) by whistle.com via smap (V2.0)
id xma029266; Wed, 27 Jan 99 22:55:30 -0800
Received: (from archie@localhost) by bubba.whistle.com (8.8.7/8.6.12) id WAA24290; Wed, 27 Jan 1999 22:55:29 -0800 (PST)
From: Archie Cobbs <archie@whistle.com>
Message-Id: <199901280655.WAA24290@bubba.whistle.com>
Subject: Re: kern/subr_scanf array index of signed char
In-Reply-To: <199901280559.VAA93563@apollo.backplane.com> from Matthew Dillon at "Jan 27, 99 09:59:53 pm"
To: dillon@apollo.backplane.com (Matthew Dillon)
Date: Wed, 27 Jan 1999 22:55:29 -0800 (PST)
Cc: current@FreeBSD.ORG
X-Mailer: ELM [version 2.4ME+ PL38 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
Matthew Dillon writes:
> :> Actually, it could very well be that I don't. I didn't want to spend
> :> the time to check to see if the compiler warned on unsigned-char array
> :> indexes. You can change it back if unsigned char array indexes do not
> :> produce a warning.
> :
> :Sloppy thinking. How would you know if you fixed the bug unless you checked
> :that you fixed the bug instead of breaking the warning? The bug was that
> :on systems with signed chars, *inp gave negative array indexes if the
> :caller passes a format string with negative characters in certain positions.
> :There are still lots of related isfoo(*inp) bugs. All these bugs are more
> :serious in the userland.
> :
> :Bruce
>
> Oh come on, give me some credit -- I knew I fixed the bug by casting
> it to unsigned char. But after spending over 8 hours working the
> files over so people compiling the kernel don't get overwhelmed
> with warnings I was getting a bit fermented in the chair.
I know how you feel Matt. After I did a bunch of -Wunused fixes
(literally over a hundred files) the responses I got contained a
couple of positive comments, one 'stop touching my code!', and one
nit picky email long on criticism and short on constructivity.
Damn the torpedoes, full steam ahead! :-)
Actually I think most people are just very 'interested' .. and
justifiably so .. it just comes across the wrong way sometimes.
-Archie
___________________________________________________________________________
Archie Cobbs * Whistle Communications, Inc. * http://www.whistle.com
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Wed Jan 27 22:56:32 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id WAA25064
for freebsd-current-outgoing; Wed, 27 Jan 1999 22:56:32 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from dingo.cdrom.com (castles73.castles.com [208.214.165.73])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA25058
for <current@FreeBSD.ORG>; Wed, 27 Jan 1999 22:56:30 -0800 (PST)
(envelope-from mike@dingo.cdrom.com)
Received: from dingo.cdrom.com (localhost [127.0.0.1])
by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id WAA01695;
Wed, 27 Jan 1999 22:52:16 -0800 (PST)
(envelope-from mike@dingo.cdrom.com)
Message-Id: <199901280652.WAA01695@dingo.cdrom.com>
X-Mailer: exmh version 2.0.2 2/24/98
To: Nate Williams <nate@mt.sri.com>
cc: John Birrell <jb@cimlogic.com.au>, archie@whistle.com,
wollman@khavrinen.lcs.mit.edu, current@FreeBSD.ORG
Subject: Re: btokup() macro in sys/malloc.h
In-reply-to: Your message of "Wed, 27 Jan 1999 23:20:06 MST."
<199901280620.XAA26671@mt.sri.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Wed, 27 Jan 1999 22:52:16 -0800
From: Mike Smith <mike@smith.net.au>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
> > In my experience, the resulting
> > code tends to be more portable across architectures with different
> > pointer/long sizes and endian-ness.
>
> This is where I disagree. Too often people cast away the bugs and end
> up with overflow and sign problems.
Since we haven't tried this yet, and since without the warnings you'd
never know about the problems in the first place, at least we have an
improvement over the status quo.
If it sucks, we can back it out. If not, then we can keep it.
Relax, both of you. This is -current, remember?
--
\\ Sometimes you're ahead, \\ Mike Smith
\\ sometimes you're behind. \\ mike@smith.net.au
\\ The race is long, and in the \\ msmith@freebsd.org
\\ end it's only with yourself. \\ msmith@cdrom.com
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Wed Jan 27 23:00:36 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id XAA25560
for freebsd-current-outgoing; Wed, 27 Jan 1999 23:00:36 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from whistle.com (s205m131.whistle.com [207.76.205.131])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA25555
for <current@FreeBSD.ORG>; Wed, 27 Jan 1999 23:00:35 -0800 (PST)
(envelope-from archie@whistle.com)
Received: (from smap@localhost) by whistle.com (8.7.5/8.6.12) id WAA29300; Wed, 27 Jan 1999 22:58:40 -0800 (PST)
Received: from bubba.whistle.com( 207.76.205.7) by whistle.com via smap (V2.0)
id xma029298; Wed, 27 Jan 99 22:58:18 -0800
Received: (from archie@localhost) by bubba.whistle.com (8.8.7/8.6.12) id WAA24316; Wed, 27 Jan 1999 22:58:18 -0800 (PST)
From: Archie Cobbs <archie@whistle.com>
Message-Id: <199901280658.WAA24316@bubba.whistle.com>
Subject: Re: DEVFS, the time has come...
In-Reply-To: <20942.917503290@brown.pfcs.com> from Harlan Stenn at "Jan 28, 99 01:01:30 am"
To: Harlan.Stenn@pfcs.com (Harlan Stenn)
Date: Wed, 27 Jan 1999 22:58:18 -0800 (PST)
Cc: current@FreeBSD.ORG
X-Mailer: ELM [version 2.4ME+ PL38 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
Harlan Stenn writes:
> > Also the eth[0..x] thing means you can replace your ethernet card with a
> > new one of a different type without having to look through your config
> > code for references to ed0 or whatever.
>
> Just to ask, what happens when the probe order changes and your multiple
> NICs start popping up on the wrong eth port?
It wouldn't be based on probe order, unless you wanted it to be
fully automatic (read: newbies). The rest of us would use an explict
rc.network (or whatever) configuration that linked up specific
ethernet drivers with interfaces.
I think Solaris (?) requires you to do this, it's called "plumbing
your interfaces" or something (according to Julian).
-Archie
___________________________________________________________________________
Archie Cobbs * Whistle Communications, Inc. * http://www.whistle.com
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Wed Jan 27 23:09:24 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id XAA26843
for freebsd-current-outgoing; Wed, 27 Jan 1999 23:09:24 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from arnold.neland.dk (mail.swimsuit.internet.dk [194.255.12.232])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA26825
for <current@FreeBSD.ORG>; Wed, 27 Jan 1999 23:09:22 -0800 (PST)
(envelope-from leif@neland.dk)
Received: from localhost (leif@localhost)
by arnold.neland.dk (8.9.2/8.9.1) with ESMTP id IAA11191;
Thu, 28 Jan 1999 08:09:02 +0100 (CET)
(envelope-from leif@arnold.neland.dk)
Date: Thu, 28 Jan 1999 08:09:02 +0100 (CET)
From: Leif Neland <leif@neland.dk>
To: Archie Cobbs <archie@whistle.com>
cc: Doug Rabson <dfr@nlsystems.com>, current@FreeBSD.ORG
Subject: Re: DEVFS, the time has come...
In-Reply-To: <199901272124.NAA15248@bubba.whistle.com>
Message-ID: <Pine.BSF.4.05.9901280807390.11164-100000@arnold.neland.dk>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
On Wed, 27 Jan 1999, Archie Cobbs wrote:
> Doug Rabson writes:
> > And another thing. Why can't we use a non-driver-specific name for the
> > disk? Most users simply don't care whether the driver was fd, wfd, wd or
> > anything. They just want to get to their files without any fuss.
>
> I agree.. and same thing goes for Ethernet drivers. I actually
> like the way Linux always has "eth0", "eth1", ... (which we could
> do using netgraph, with some work).
>
Just symlink eth0 to which card you like, just as /dev/mixer happens to be
a symlink to /dev/mixer1 on my system.
Leif
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Wed Jan 27 23:10:49 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id XAA27258
for freebsd-current-outgoing; Wed, 27 Jan 1999 23:10:49 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA27249
for <current@FreeBSD.ORG>; Wed, 27 Jan 1999 23:10:47 -0800 (PST)
(envelope-from julian@whistle.com)
Received: (from daemon@localhost)
by alpo.whistle.com (8.8.5/8.8.5) id XAA23027;
Wed, 27 Jan 1999 23:08:08 -0800 (PST)
Received: from s204m82.isp.whistle.com(207.76.204.82)
via SMTP by alpo.whistle.com, id smtpdi23022; Thu Jan 28 07:08:03 1999
Date: Wed, 27 Jan 1999 23:08:00 -0800 (PST)
From: Julian Elischer <julian@whistle.com>
X-Sender: julian@s204m82.isp.whistle.com
To: John Birrell <jb@cimlogic.com.au>
cc: John Polstra <jdp@polstra.com>, bde@zeta.org.au, current@FreeBSD.ORG
Subject: Re: btokup().. STYLE(9)
In-Reply-To: <199901280600.RAA07941@cimlogic.com.au>
Message-ID: <Pine.BSF.4.05.9901272302460.304-100000@s204m82.isp.whistle.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
I think that style(9) should be modified to include
"Parenthesis may be used to improve the readbility of complex
expressions even if not strictly required."
instead of the stupid phrase presently there.
also:
"Braces around code blocks should be allowable even when not strictly
needed, for the purpose of readbility."
The aim is to produce readble maintainable code, not to save bytes in
sourcecode!
julian
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Wed Jan 27 23:11:25 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id XAA27374
for freebsd-current-outgoing; Wed, 27 Jan 1999 23:11:25 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from panzer.plutotech.com (panzer.plutotech.com [206.168.67.125])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA27351
for <current@FreeBSD.ORG>; Wed, 27 Jan 1999 23:11:21 -0800 (PST)
(envelope-from ken@panzer.plutotech.com)
Received: (from ken@localhost)
by panzer.plutotech.com (8.9.2/8.8.5) id AAA57155;
Thu, 28 Jan 1999 00:11:07 -0700 (MST)
From: "Kenneth D. Merry" <ken@plutotech.com>
Message-Id: <199901280711.AAA57155@panzer.plutotech.com>
Subject: Re: DEVFS, the time has come...
In-Reply-To: <Pine.BSF.4.05.9901280807390.11164-100000@arnold.neland.dk> from Leif Neland at "Jan 28, 99 08:09:02 am"
To: leif@neland.dk (Leif Neland)
Date: Thu, 28 Jan 1999 00:11:07 -0700 (MST)
Cc: archie@whistle.com, dfr@nlsystems.com, current@FreeBSD.ORG
X-Mailer: ELM [version 2.4ME+ PL28s (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
Leif Neland wrote...
>
>
> On Wed, 27 Jan 1999, Archie Cobbs wrote:
>
> > Doug Rabson writes:
> > > And another thing. Why can't we use a non-driver-specific name for the
> > > disk? Most users simply don't care whether the driver was fd, wfd, wd or
> > > anything. They just want to get to their files without any fuss.
> >
> > I agree.. and same thing goes for Ethernet drivers. I actually
> > like the way Linux always has "eth0", "eth1", ... (which we could
> > do using netgraph, with some work).
> >
> Just symlink eth0 to which card you like, just as /dev/mixer happens to be
> a symlink to /dev/mixer1 on my system.
How are you going to do that, when network drivers don't have device nodes?
Ken
--
Kenneth Merry
ken@plutotech.com
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Wed Jan 27 23:15:22 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id XAA27971
for freebsd-current-outgoing; Wed, 27 Jan 1999 23:15:22 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from cs.ucla.edu (Ulfus.CS.UCLA.EDU [131.179.48.35])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA27965
for <freebsd-current@freebsd.org>; Wed, 27 Jan 1999 23:15:21 -0800 (PST)
(envelope-from scottm@ulfus.cs.ucla.edu)
Received: from ulfus.cs.ucla.edu (localhost [127.0.0.1])
by cs.ucla.edu (8.8.7/8.8.8) with ESMTP id XAA10746;
Wed, 27 Jan 1999 23:14:59 -0800
Message-Id: <199901280714.XAA10746@cs.ucla.edu>
X-Mailer: exmh version 2.0.2
To: Archie Cobbs <archie@whistle.com>
cc: freebsd-current@FreeBSD.ORG
Subject: Re: DEVFS, the time has come...
In-Reply-To: Your message of "Wed, 27 Jan 1999 22:58:18 PST."
<199901280658.WAA24316@bubba.whistle.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Wed, 27 Jan 1999 23:14:58 -0800
From: Scott Michel <scottm@ulfus.cs.ucla.edu>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
> I think Solaris (?) requires you to do this, it's called "plumbing
> your interfaces" or something (according to Julian).
Solaris requires "interface plumbing" as the result of STREAMS; you
have to push IP on top of the interface driver. For all intents and
purposes, the device name identifies a particular driver (i.e. "le",
"qe", "hme", "fa", &c). The number identifies an instance of the
device which depends on probe order. [*]
Fortunately, the BSD world avoided this particular form of brain
damage, thank <insert deity name here>! OTOH, as ph--ked as STREAMS
happens to be, it does have a certain appeal wrt dynamically building
and tearing down network stacks. The AT&T model just didn't have IP
in mind when it was designed.
-scooter
[*] I'd written a hacked version of ifconfig based on the output of
'truss' and managed to get it right in a limited way, as in ifconfig
only plumbs IP on top of devices.
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Wed Jan 27 23:17:18 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id XAA28219
for freebsd-current-outgoing; Wed, 27 Jan 1999 23:17:18 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from bright.fx.genx.net (bright.fx.genx.net [206.64.4.154])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA28214
for <current@FreeBSD.ORG>; Wed, 27 Jan 1999 23:17:17 -0800 (PST)
(envelope-from bright@hotjobs.com)
Received: from localhost (bright@localhost)
by bright.fx.genx.net (8.9.1/8.9.1) with ESMTP id CAA20204;
Thu, 28 Jan 1999 02:23:06 -0500 (EST)
(envelope-from bright@hotjobs.com)
X-Authentication-Warning: bright.fx.genx.net: bright owned process doing -bs
Date: Thu, 28 Jan 1999 02:23:06 -0500 (EST)
From: Alfred Perlstein <bright@hotjobs.com>
X-Sender: bright@bright.fx.genx.net
To: Archie Cobbs <archie@whistle.com>
cc: Harlan Stenn <Harlan.Stenn@pfcs.com>, current@FreeBSD.ORG
Subject: Re: DEVFS, the time has come...
In-Reply-To: <199901280658.WAA24316@bubba.whistle.com>
Message-ID: <Pine.BSF.4.05.9901280219210.81323-100000@bright.fx.genx.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
On Wed, 27 Jan 1999, Archie Cobbs wrote:
> Harlan Stenn writes:
> > > Also the eth[0..x] thing means you can replace your ethernet card with a
> > > new one of a different type without having to look through your config
> > > code for references to ed0 or whatever.
> >
> > Just to ask, what happens when the probe order changes and your multiple
> > NICs start popping up on the wrong eth port?
>
> It wouldn't be based on probe order, unless you wanted it to be
> fully automatic (read: newbies). The rest of us would use an explict
> rc.network (or whatever) configuration that linked up specific
> ethernet drivers with interfaces.
>
> I think Solaris (?) requires you to do this, it's called "plumbing
> your interfaces" or something (according to Julian).
please god no... i spent a long while figuring that out the first time i
played with a solaris box, it's NOT intuative.
i like the idea of aliases and wiring aliases to real names:
xl0 -> eth0
fxp0 -> eth1
...
thanks,
-Alfred
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Wed Jan 27 23:20:44 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id XAA28757
for freebsd-current-outgoing; Wed, 27 Jan 1999 23:20:44 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA28748
for <current@FreeBSD.ORG>; Wed, 27 Jan 1999 23:20:43 -0800 (PST)
(envelope-from julian@whistle.com)
Received: (from daemon@localhost)
by alpo.whistle.com (8.8.5/8.8.5) id XAA23118;
Wed, 27 Jan 1999 23:10:59 -0800 (PST)
Received: from s204m82.isp.whistle.com(207.76.204.82)
via SMTP by alpo.whistle.com, id smtpdv23109; Thu Jan 28 07:10:51 1999
Date: Wed, 27 Jan 1999 23:10:48 -0800 (PST)
From: Julian Elischer <julian@whistle.com>
X-Sender: julian@s204m82.isp.whistle.com
To: John Polstra <jdp@polstra.com>
cc: John Birrell <jb@cimlogic.com.au>, current@FreeBSD.ORG, bde@zeta.org.au
Subject: Re: btokup() macro in sys/malloc.h
In-Reply-To: <XFMail.990127220340.jdp@polstra.com>
Message-ID: <Pine.BSF.4.05.9901272310210.304-100000@s204m82.isp.whistle.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
I could drive there from here :-)
On Wed, 27 Jan 1999, John Polstra wrote:
>
> On 28-Jan-99 John Birrell wrote:
> > John Polstra wrote:
> >>
> >> Hear ye, hear ye! Be it here noted and archived for all eternity that
> >> on January 27, 1999 Pacific Time, John Polstra was, for one fleeting
> >> moment, purer than Bruce! :-)
> >
> > OK, so now we have to shoot you too. Oh well, so be it....
> >
> > Are there any others who would like to join these purists? Come on,
> > we have bullets for you all...
>
> Bah! You might be able to hit Bruce over there in oz. But to hit me,
> you'd need an ICBM. Give me purity or give me death! Bwahahahahah!
>
> John
> ---
> John Polstra jdp@polstra.com
> John D. Polstra & Co., Inc. Seattle, Washington USA
> "Nobody ever went broke underestimating the taste of the American public."
> -- H. L. Mencken
>
> To Unsubscribe: send mail to majordomo@FreeBSD.org
> with "unsubscribe freebsd-current" in the body of the message
>
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Wed Jan 27 23:21:49 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id XAA29056
for freebsd-current-outgoing; Wed, 27 Jan 1999 23:21:49 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA29048
for <current@freebsd.org>; Wed, 27 Jan 1999 23:21:47 -0800 (PST)
(envelope-from dillon@apollo.backplane.com)
Received: (from dillon@localhost)
by apollo.backplane.com (8.9.2/8.9.1) id XAA98105;
Wed, 27 Jan 1999 23:21:46 -0800 (PST)
(envelope-from dillon)
Date: Wed, 27 Jan 1999 23:21:46 -0800 (PST)
From: Matthew Dillon <dillon@apollo.backplane.com>
Message-Id: <199901280721.XAA98105@apollo.backplane.com>
To: Archie Cobbs <archie@whistle.com>
Cc: current@FreeBSD.ORG
Subject: Re: cvs commit: src/sys/i386/eisa ahb.c
References: <199901280709.XAA24410@bubba.whistle.com>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
:> > Bullshit. You don't know what the fuck you are talking about.
:>
:> I don't know that you screwed up in your quest to fix a warning? Gee,
:> forgive me for sounding suprised, but:
:>
:> "Matt, you screwed up with your fix that tried to fix a -Wall warning".
:> The fix was wrong. Wrong. Wrong. If you don't understand it, don't
:> fix it and leave the warning. The warning is there for a reason, and
:> making it go away because it bothers you is *WRONG* WRONG *WRONG*.
:
:Please disregard previous email asking what the bug was.. :-)
:
:-Archie
:
:___________________________________________________________________________
:Archie Cobbs * Whistle Communications, Inc. * http://www.whistle.com
The eisa code was already broken, just not badly enough to crash the
machine instantly. I comitted a fix that was essentially what I
believed the author meant to do, but the code still didn't look
right so I also brought it up on the lists and kept it dog-ear'd.
How Mr. ignoromous Nate could construe this to mean that I was trying
to brush something under the rug is beyond me. As I said to Julian,
I probably shouldn't have made the committ, but the fact is that I
not only left the module on my hotlist, I also immediately brought
the potential problem to the attention of the entire list and thence,
when reminded, onto the scsi list as well -- the problem was NOT
being ignored or brushed under the rug. It had NOTHING whatsoever to
do with cleaning up a compiler warning.
As mistakes go, this was a pretty minor one. Only an idiot would
come to a different conclusion.
-Matt
Matthew Dillon
<dillon@backplane.com>
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Wed Jan 27 23:28:27 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id XAA29759
for freebsd-current-outgoing; Wed, 27 Jan 1999 23:28:27 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA29748
for <current@FreeBSD.ORG>; Wed, 27 Jan 1999 23:28:24 -0800 (PST)
(envelope-from dillon@apollo.backplane.com)
Received: (from dillon@localhost)
by apollo.backplane.com (8.9.2/8.9.1) id XAA98161;
Wed, 27 Jan 1999 23:28:20 -0800 (PST)
(envelope-from dillon)
Date: Wed, 27 Jan 1999 23:28:20 -0800 (PST)
From: Matthew Dillon <dillon@apollo.backplane.com>
Message-Id: <199901280728.XAA98161@apollo.backplane.com>
To: Julian Elischer <julian@whistle.com>
Cc: John Birrell <jb@cimlogic.com.au>, John Polstra <jdp@polstra.com>,
bde@zeta.org.au, current@FreeBSD.ORG
Subject: Re: btokup().. STYLE(9)
References: <Pine.BSF.4.05.9901272302460.304-100000@s204m82.isp.whistle.com>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
:I think that style(9) should be modified to include
:"Parenthesis may be used to improve the readbility of complex
:expressions even if not strictly required."
:instead of the stupid phrase presently there.
:also:
:"Braces around code blocks should be allowable even when not strictly
:needed, for the purpose of readbility."
:
:The aim is to produce readble maintainable code, not to save bytes in
:sourcecode!
:
:julian
I agree completely. I've already gotten into the habit of added
braces when conditonal expressions exceed one line, even though there
may be only one statement. Otherwise the code is just too unreadable.
if (expression)
single_line_stmt;
else
single_line_stmt;
if (some really
complex expression) {
single_line_stmt;
} else {
single_line_stmt;
}
if (expression) {
single_line_stmt;
} else {
multi_line_stmt;
multi_line_stmt;
}
if (expression) {
multi_line_stmt;
multi_line_stmt;
} else {
single_line_stmt;
}
All too often I see this:
if (expression) {
multi_line_stmt;
multi_line_stmt;
multi_line_stmt;
multi_line_stmt;
multi_line_stmt;
multi_line_stmt;
multi_line_stmt;
multi_line_stmt;
multi_line_stmt;
multi_line_stmt;
} else
single_line_stmt;
some other code here
Or here.
while (some really
complex expression
that takes a bunch of room) {
single_line_stmt;
}
or
while (some really
complex expression
that takes a bunch of room
) {
single_line_stmt;
}
And I'll tell you, it just isn't readable, especially when you get into
while()'s and do's and such with HUGE expressions and single-line
bodies.
If any part of the if () needs braces, I put the other part in braces
as well. It would be nice if that were formalized. The issue with
where to put the ') {' is a harder one to formalize... Probably half
the people like it one way and half the people like it the other.
IMHO.
-Matt
Matthew Dillon
<dillon@backplane.com>
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Wed Jan 27 23:30:28 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id XAA00288
for freebsd-current-outgoing; Wed, 27 Jan 1999 23:30:28 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from freebsd.dk (freebsd.dk [212.242.42.178])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA00279
for <freebsd-current@FreeBSD.ORG>; Wed, 27 Jan 1999 23:30:26 -0800 (PST)
(envelope-from sos@freebsd.dk)
Received: (from sos@localhost)
by freebsd.dk (8.9.1/8.9.1) id IAA37189;
Thu, 28 Jan 1999 08:30:12 +0100 (CET)
(envelope-from sos)
From: Søren Schmidt <sos@freebsd.dk>
Message-Id: <199901280730.IAA37189@freebsd.dk>
Subject: Re: devstat and atapi-cd.c
In-Reply-To: <199901272110.OAA53490@panzer.plutotech.com> from "Kenneth D. Merry" at "Jan 27, 1999 2:10:17 pm"
To: ken@plutotech.com (Kenneth D. Merry)
Date: Thu, 28 Jan 1999 08:30:11 +0100 (CET)
Cc: garyj@muc.de, freebsd-current@FreeBSD.ORG
X-Mailer: ELM [version 2.4ME+ PL43 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
It seems Kenneth D. Merry wrote:
> Gary Jennejohn wrote...
> > Are there any plans to add devstat support to atapi-cd.c, a la scsi_cd.c ?
> >
> > Is it even considered to be desirable ?
>
> I think it is desireable. I think the best person to do it is probably
> Soren or someone else who is familar with the driver.
I have it in a patch here somewhere, I'll get it committed as soon as I
get my head above waters...
-Søren
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Wed Jan 27 23:35:54 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id XAA01279
for freebsd-current-outgoing; Wed, 27 Jan 1999 23:35:54 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from allegro.lemis.com (allegro.lemis.com [192.109.197.134])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA01267
for <current@FreeBSD.ORG>; Wed, 27 Jan 1999 23:35:50 -0800 (PST)
(envelope-from grog@freebie.lemis.com)
Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137])
by allegro.lemis.com (8.9.1/8.9.0) with ESMTP id SAA23794;
Thu, 28 Jan 1999 18:05:38 +1030 (CST)
Received: (from grog@localhost)
by freebie.lemis.com (8.9.2/8.9.0) id SAA08562;
Thu, 28 Jan 1999 18:05:38 +1030 (CST)
Date: Thu, 28 Jan 1999 18:05:37 +1030
From: Greg Lehey <grog@lemis.com>
To: Bruce Evans <bde@zeta.org.au>
Cc: current@FreeBSD.ORG, peter.jeremy@auss2.alcatel.com.au
Subject: indent(1) and style(9) (was: btokup() macro in sys/malloc.h)
Message-ID: <19990128180537.B8473@freebie.lemis.com>
References: <199901280316.OAA26849@godzilla.zeta.org.au>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.95.1i
In-Reply-To: <199901280316.OAA26849@godzilla.zeta.org.au>; from Bruce Evans on Thu, Jan 28, 1999 at 02:16:25PM +1100
WWW-Home-Page: http://www.lemis.com/~grog
Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia
Phone: +61-8-8388-8286
Fax: +61-8-8388-8725
Mobile: +61-41-739-7062
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
On Thursday, 28 January 1999 at 14:16:25 +1100, Bruce Evans wrote:
>> It would be nice if style(9) documented the options to give indent(1)
>> to match the `approved' layout convections. (This would reduce the
>> effort involved in importing large chunks of code).
>
> This is impossible, since indent(1) is buggy and out of date with both
> KNF and C.
Well, you can do a certain amount. In fact, I use GNU indent and
achieve a reasonable approximation. It would be nice to import it,
but it doesn't comply with style(9) :-)
Greg
--
See complete headers for address, home page and phone numbers
finger grog@lemis.com for PGP public key
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Wed Jan 27 23:53:03 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id XAA02953
for freebsd-current-outgoing; Wed, 27 Jan 1999 23:53:03 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA02948
for <current@FreeBSD.ORG>; Wed, 27 Jan 1999 23:53:01 -0800 (PST)
(envelope-from dillon@apollo.backplane.com)
Received: (from dillon@localhost)
by apollo.backplane.com (8.9.2/8.9.1) id XAA98980;
Wed, 27 Jan 1999 23:53:00 -0800 (PST)
(envelope-from dillon)
Date: Wed, 27 Jan 1999 23:53:00 -0800 (PST)
From: Matthew Dillon <dillon@apollo.backplane.com>
Message-Id: <199901280753.XAA98980@apollo.backplane.com>
To: current@FreeBSD.ORG
Subject: -Wall -Wcast-qual and SYSINIT
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
Right now we have a problem with struct sysinit.
The problem is that some SYSINIT functions supply a function taking
a const void * and a const pointer for data, and other SYSINIT
functions supply a function taking a void * and a non-const pointer
for data.
What this means, effectively, is that we want one of two SYSINIT
structures where both the function argument and udata are of the
same type. Something like the union shown below. If the function
argument type does not match the data type we want the initialization
to generate a warning.
struct sysinit {
unsigned int subsystem; /* subsystem identifier*/
unsigned int order; /* init order within subsystem*/
union {
struct {
void (*func) __P((void *));
void *udata; /* multiplexer/argument */
} n;
struct {
void (*func) __P((const void *));
const void *udata; /* multiplexer/argument */
} c;
} u;
si_elem_t type; /* sysinit_elem_type*/
};
Unfortunately, GCC isn't smart enough to match the function type
to the correct structure - it always stuffs it into the first structure.
So the above cool hack will not work :-(.
I can't think of how to do this without actually having two different
sysinit structures - on that uses a non-const function and data element,
and one that uses a const function and data element. While having two
sysinit structures would work, it would be a little iffy keeping them
in sync with each other so the kernel init call code doesn't have to deal
with both types.
struct c_sysinit {
unsigned int subsystem; /* subsystem identifier*/
unsigned int order; /* init order within subsystem*/
void (*func) __P((void *));
void *udata; /* multiplexer/argument */
si_elem_t type; /* sysinit_elem_type*/
};
struct n_sysinit {
unsigned int subsystem; /* subsystem identifier*/
unsigned int order; /* init order within subsystem*/
void (*func) __P((const void *));
const void *udata; /* multiplexer/argument */
si_elem_t type; /* sysinit_elem_type*/
};
The SYSINIT problem accounts for about half the remaining compilation
warnings. I would like to find a good solution for it.
-Matt
Matthew Dillon
<dillon@backplane.com>
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Thu Jan 28 00:04:04 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id AAA04413
for freebsd-current-outgoing; Thu, 28 Jan 1999 00:04:04 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from axl.noc.iafrica.com (axl.noc.iafrica.com [196.31.1.175])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA04402
for <freebsd-current@freebsd.org>; Thu, 28 Jan 1999 00:04:00 -0800 (PST)
(envelope-from sheldonh@axl.noc.iafrica.com)
Received: from sheldonh (helo=axl.noc.iafrica.com)
by axl.noc.iafrica.com with local-esmtp (Exim 2.11 #1)
id 105mQI-000Bss-00; Thu, 28 Jan 1999 10:03:34 +0200
From: Sheldon Hearn <axl@iafrica.com>
To: Mattias Pantzare <pantzer@ludd.luth.se>
cc: freebsd-current@FreeBSD.ORG
Subject: Re: NIS with HPUX 10.20
In-reply-to: Your message of "Thu, 28 Jan 1999 00:34:30 +0100."
<199901272334.AAA24081@zed.ludd.luth.se>
Date: Thu, 28 Jan 1999 10:03:34 +0200
Message-ID: <45685.917510614@axl.noc.iafrica.com>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
On Thu, 28 Jan 1999 00:34:30 +0100, Mattias Pantzare wrote:
> Why _not_ use -C? What is the point in replacing a file with the same file?
> install -C will replace the file if the new file is diffrent.
Aaaaaaaah, thank you. I misread the manpage description of -C and didn't
notice "and the files are the same"...
Cleared up, head back on straight. :-)
Thanks,
Sheldon.
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Thu Jan 28 00:12:29 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id AAA05590
for freebsd-current-outgoing; Thu, 28 Jan 1999 00:12:29 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from axl.noc.iafrica.com (axl.noc.iafrica.com [196.31.1.175])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA05572
for <freebsd-current@freebsd.org>; Thu, 28 Jan 1999 00:12:24 -0800 (PST)
(envelope-from sheldonh@axl.noc.iafrica.com)
Received: from sheldonh (helo=axl.noc.iafrica.com)
by axl.noc.iafrica.com with local-esmtp (Exim 2.11 #1)
id 105mWc-000DRd-00; Thu, 28 Jan 1999 10:10:06 +0200
From: Sheldon Hearn <axl@iafrica.com>
To: Zach Heilig <zach@uffdaonline.net>
cc: Bruce Evans <bde@zeta.org.au>, mike@smith.net.au, bonnetf@bart.esiee.fr,
dhw@whistle.com, freebsd-current@FreeBSD.ORG,
meyerd1@fang.cs.sunyit.edu
Subject: Re: NIS with HPUX 10.20
In-reply-to: Your message of "Wed, 27 Jan 1999 18:42:03 CST."
<19990127184203.A63814@znh.org>
Date: Thu, 28 Jan 1999 10:10:04 +0200
Message-ID: <51683.917511004@axl.noc.iafrica.com>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
On Wed, 27 Jan 1999 18:42:03 CST, Zach Heilig wrote:
> It does update the 'ctime' entry of ld-elf.so.1, so using 'find /usr
> \! -ctime 1 -print' right after make world will find all the "old"
> files.
That's fine, then. I figured install -C wouldn't adjust ctime for files
that hadn't changed.
> The 'find' works better if /usr/local and /usr/X11R6 are symlinks, or set the
> option to not recurse into those directories. And, 'perl' has to be checked
> manually.
Well I tend to rebuild ports and X after ``make world'' and before the
find -ctime check.
> /usr/include <- this falls to 'find -ctime'.
> /usr/libdata/perl <- you are better off ignoring "old" files in here.
Someone explained how to solve for /usr/include with ``make -DCLOBBER
includes'' and I have a nasty hack for perl5 that updates
/usr/libdata/perl .
Thanks,
Sheldon.
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Thu Jan 28 00:15:45 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id AAA05815
for freebsd-current-outgoing; Thu, 28 Jan 1999 00:15:45 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA05808
for <current@FreeBSD.ORG>; Thu, 28 Jan 1999 00:15:43 -0800 (PST)
(envelope-from phk@critter.freebsd.dk)
Received: from critter.freebsd.dk (localhost [127.0.0.1])
by critter.freebsd.dk (8.9.1/8.8.5) with ESMTP id JAA33687;
Thu, 28 Jan 1999 09:14:38 +0100 (CET)
To: Garrett Wollman <wollman@khavrinen.lcs.mit.edu>
cc: Archie Cobbs <archie@whistle.com>, current@FreeBSD.ORG
Subject: Re: btokup() macro in sys/malloc.h
In-reply-to: Your message of "Wed, 27 Jan 1999 21:22:43 EST."
<199901280222.VAA14212@khavrinen.lcs.mit.edu>
Date: Thu, 28 Jan 1999 09:14:35 +0100
Message-ID: <33685.917511275@critter.freebsd.dk>
From: Poul-Henning Kamp <phk@critter.freebsd.dk>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
In message <199901280222.VAA14212@khavrinen.lcs.mit.edu>, Garrett Wollman writes:
><<On Wed, 27 Jan 1999 18:00:54 -0800 (PST), Archie Cobbs <archie@whistle.com> said:
>
>> Please do go ahead and update it.. the experts agree!
>
>I haven't seen any experts involved in this discussion yet. It's
>probably after bedtime down there in oz.
It's been discussed before and agreed upon.
--
Poul-Henning Kamp FreeBSD coreteam member
phk@FreeBSD.ORG "Real hackers run -current on their laptop."
FreeBSD -- It will take a long time before progress goes too far!
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Thu Jan 28 00:17:45 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id AAA05928
for freebsd-current-outgoing; Thu, 28 Jan 1999 00:17:45 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from relay.nuxi.com ([169.237.7.38])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA05923
for <current@FreeBSD.ORG>; Thu, 28 Jan 1999 00:17:44 -0800 (PST)
(envelope-from obrien@NUXI.com)
Received: (from obrien@localhost)
by relay.nuxi.com (8.9.1/8.9.1) id AAA00894;
Thu, 28 Jan 1999 00:17:43 -0800 (PST)
(envelope-from obrien)
Date: Thu, 28 Jan 1999 00:17:43 -0800
From: "David O'Brien" <obrien@NUXI.com>
To: Matthew Dillon <dillon@apollo.backplane.com>
Cc: current@FreeBSD.ORG
Subject: Re: kern/subr_scanf array index of signed char
Message-ID: <19990128001743.A563@relay.nuxi.com>
Reply-To: obrien@NUXI.com
References: <199901280204.SAA19979@bubba.whistle.com> <199901280207.SAA88572@apollo.backplane.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.95i
In-Reply-To: <199901280207.SAA88572@apollo.backplane.com>; from Matthew Dillon on Wed, Jan 27, 1999 at 06:07:18PM -0800
X-Operating-System: FreeBSD 3.0-CURRENT
Organization: The NUXI BSD group
X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A
X-Pgp-Keyid: 34F9F9D5
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
> :Just curious.. why do you need the "(int)" cast?
>
> Actually, it could very well be that I don't. I didn't want to spend
> the time to check to see if the compiler warned on unsigned-char array
> indexes.
When you add casts to quite warnings, please use the minium number of
them. Even if it takes a little more time to test. I would much rather
have the warnings than obfuscated code.
--
-- David (obrien@NUXI.com -or- obrien@FreeBSD.org)
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Thu Jan 28 00:19:19 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id AAA06047
for freebsd-current-outgoing; Thu, 28 Jan 1999 00:19:19 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.26.10.9])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA06033
for <current@FreeBSD.ORG>; Thu, 28 Jan 1999 00:19:16 -0800 (PST)
(envelope-from bde@godzilla.zeta.org.au)
Received: (from bde@localhost)
by godzilla.zeta.org.au (8.8.7/8.8.7) id TAA23954;
Thu, 28 Jan 1999 19:19:12 +1100
Date: Thu, 28 Jan 1999 19:19:12 +1100
From: Bruce Evans <bde@zeta.org.au>
Message-Id: <199901280819.TAA23954@godzilla.zeta.org.au>
To: bde@zeta.org.au, grog@lemis.com
Subject: Re: indent(1) and style(9) (was: btokup() macro in sys/malloc.h)
Cc: current@FreeBSD.ORG, peter.jeremy@auss2.alcatel.com.au
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
>>> It would be nice if style(9) documented the options to give indent(1)
>>> to match the `approved' layout convections. (This would reduce the
>>> effort involved in importing large chunks of code).
>>
>> This is impossible, since indent(1) is buggy and out of date with both
>> KNF and C.
>
>Well, you can do a certain amount. In fact, I use GNU indent and
>achieve a reasonable approximation.
I see no evidence of this. vinum sources don't seem to have a single
line in KNF, except accidentally. They have an indentation of 4
instead of 8, lots of per-statement comments, lots of lines longer
than 80 characters, lots of block comments without `/*' and `*/' on
a line by themself, ...
>It would be nice to import it,
>but it doesn't comply with style(9) :-)
style(9) only applies to non-contrib'ed sources. e.g., vinum :-).
Bruce
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Thu Jan 28 00:20:24 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id AAA06220
for freebsd-current-outgoing; Thu, 28 Jan 1999 00:20:24 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA06215
for <current@FreeBSD.ORG>; Thu, 28 Jan 1999 00:20:23 -0800 (PST)
(envelope-from julian@whistle.com)
Received: (from daemon@localhost)
by alpo.whistle.com (8.8.5/8.8.5) id AAA24422;
Thu, 28 Jan 1999 00:19:31 -0800 (PST)
Received: from s204m82.isp.whistle.com(207.76.204.82)
via SMTP by alpo.whistle.com, id smtpdR24420; Thu Jan 28 08:19:22 1999
Date: Thu, 28 Jan 1999 00:19:20 -0800 (PST)
From: Julian Elischer <julian@whistle.com>
X-Sender: julian@s204m82.isp.whistle.com
To: Matthew Dillon <dillon@apollo.backplane.com>
cc: current@FreeBSD.ORG
Subject: Re: -Wall -Wcast-qual and SYSINIT
In-Reply-To: <199901280753.XAA98980@apollo.backplane.com>
Message-ID: <Pine.BSF.4.05.9901280014520.304-100000@s204m82.isp.whistle.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
>From my uderstanding, SYSINIT should always point to a function with a
CONST argument because the argument is fixed as a constant at link/compile
time.
what functions don't expect a const? and why not?
or am I mising something?
julian
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Thu Jan 28 00:26:19 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id AAA07403
for freebsd-current-outgoing; Thu, 28 Jan 1999 00:26:19 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA07396
for <current@FreeBSD.ORG>; Thu, 28 Jan 1999 00:26:17 -0800 (PST)
(envelope-from dillon@apollo.backplane.com)
Received: (from dillon@localhost)
by apollo.backplane.com (8.9.2/8.9.1) id AAA02016;
Thu, 28 Jan 1999 00:26:17 -0800 (PST)
(envelope-from dillon)
Date: Thu, 28 Jan 1999 00:26:17 -0800 (PST)
From: Matthew Dillon <dillon@apollo.backplane.com>
Message-Id: <199901280826.AAA02016@apollo.backplane.com>
To: Julian Elischer <julian@whistle.com>
Cc: current@FreeBSD.ORG
Subject: Re: -Wall -Wcast-qual and SYSINIT
References: <Pine.BSF.4.05.9901280014520.304-100000@s204m82.isp.whistle.com>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
:
:>From my uderstanding, SYSINIT should always point to a function with a
:CONST argument because the argument is fixed as a constant at link/compile
:time.
:
:what functions don't expect a const? and why not?
:
:or am I mising something?
:
:julian
Most of the functions do not expect a const argument, though that
may simply be because they didn't bother to use const when they
could have.
However, I know at least the MALLOC initialization objects *can't*
use const objects because the malloc initialization routine modifies
the data object.
I'm sure that a non-trivial number of the sysinits also modify their
data objects. So we need to handle both cases.
Matthew Dillon
<dillon@backplane.com>
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Thu Jan 28 00:27:16 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id AAA07468
for freebsd-current-outgoing; Thu, 28 Jan 1999 00:27:16 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from allegro.lemis.com (allegro.lemis.com [192.109.197.134])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA07461
for <current@FreeBSD.ORG>; Thu, 28 Jan 1999 00:27:10 -0800 (PST)
(envelope-from grog@freebie.lemis.com)
Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137])
by allegro.lemis.com (8.9.1/8.9.0) with ESMTP id SAA23962;
Thu, 28 Jan 1999 18:57:05 +1030 (CST)
Received: (from grog@localhost)
by freebie.lemis.com (8.9.2/8.9.0) id SAA08842;
Thu, 28 Jan 1999 18:57:05 +1030 (CST)
Date: Thu, 28 Jan 1999 18:57:05 +1030
From: Greg Lehey <grog@lemis.com>
To: Bruce Evans <bde@zeta.org.au>
Cc: current@FreeBSD.ORG, peter.jeremy@auss2.alcatel.com.au
Subject: Re: indent(1) and style(9) (was: btokup() macro in sys/malloc.h)
Message-ID: <19990128185705.G8473@freebie.lemis.com>
References: <199901280819.TAA23954@godzilla.zeta.org.au>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.95.1i
In-Reply-To: <199901280819.TAA23954@godzilla.zeta.org.au>; from Bruce Evans on Thu, Jan 28, 1999 at 07:19:12PM +1100
WWW-Home-Page: http://www.lemis.com/~grog
Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia
Phone: +61-8-8388-8286
Fax: +61-8-8388-8725
Mobile: +61-41-739-7062
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
On Thursday, 28 January 1999 at 19:19:12 +1100, Bruce Evans wrote:
>>>> It would be nice if style(9) documented the options to give indent(1)
>>>> to match the `approved' layout convections. (This would reduce the
>>>> effort involved in importing large chunks of code).
>>>
>>> This is impossible, since indent(1) is buggy and out of date with both
>>> KNF and C.
>>
>> Well, you can do a certain amount. In fact, I use GNU indent and
>> achieve a reasonable approximation.
>
> I see no evidence of this. vinum sources don't seem to have a single
> line in KNF, except accidentally. They have an indentation of 4
> instead of 8, lots of per-statement comments, lots of lines longer
> than 80 characters, lots of block comments without `/*' and `*/' on
> a line by themself, ...
Well, I call that an approximation. Sorry I have so many comments.
I'll fix the individual line /* and */; it wasn't evident from
style(9) that this was a requirement.
>> It would be nice to import it,
>> but it doesn't comply with style(9) :-)
>
> style(9) only applies to non-contrib'ed sources. e.g., vinum :-).
Don't spoil a good story by sticking too closely to the facts.
Greg
--
See complete headers for address, home page and phone numbers
finger grog@lemis.com for PGP public key
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Thu Jan 28 00:28:52 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id AAA07597
for freebsd-current-outgoing; Thu, 28 Jan 1999 00:28:52 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA07587
for <current@FreeBSD.ORG>; Thu, 28 Jan 1999 00:28:50 -0800 (PST)
(envelope-from phk@critter.freebsd.dk)
Received: from critter.freebsd.dk (localhost [127.0.0.1])
by critter.freebsd.dk (8.9.1/8.8.5) with ESMTP id JAA33902;
Thu, 28 Jan 1999 09:26:35 +0100 (CET)
To: Matthew Dillon <dillon@apollo.backplane.com>
cc: Nate Williams <nate@mt.sri.com>, Archie Cobbs <archie@whistle.com>,
wollman@khavrinen.lcs.mit.edu (Garrett Wollman), current@FreeBSD.ORG
Subject: Re: btokup() macro in sys/malloc.h
In-reply-to: Your message of "Wed, 27 Jan 1999 22:41:04 PST."
<199901280641.WAA96133@apollo.backplane.com>
Date: Thu, 28 Jan 1999 09:26:35 +0100
Message-ID: <33900.917511995@critter.freebsd.dk>
From: Poul-Henning Kamp <phk@critter.freebsd.dk>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
Matt,
By now we do know a GREAT deal about you from the way you behave.
Trying to judge your age from that data, 16 years can certainly not
be ruled out conclusively.
I will make no secret of the fact that I was not at all happy with
you becoming a committer, and your behaviour the last couple of
days is exactly what I feared and expected would happen.
Please go out and get yourself some fresh air & some perspective.
This is FreeBSD, not MattBSD.
Poul-Henning
In message <199901280641.WAA96133@apollo.backplane.com>, Matthew Dillon writes:
>
>:
>:And introduced at least one. If you were a programmer under my charge,
>:I'd tell you to use the warnings to fix only those bugs you are sure of
>:and leave the others alone.
>
> Nate, if you were a programmer under my charge you'd be heading out
> the door with your final paycheck. Your attitude smacks of a
> superiority complex that leaves a bad taste in my mouth. You don't
> know shit about me, so don't expect to get away with talking down
> to me. I'm not a fucking 16 year old. Right now, my opinion of
> *your* skills is rather at a low point.
>
> -Matt
> Matthew Dillon
> <dillon@backplane.com>
--
Poul-Henning Kamp FreeBSD coreteam member
phk@FreeBSD.ORG "Real hackers run -current on their laptop."
FreeBSD -- It will take a long time before progress goes too far!
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Thu Jan 28 00:34:33 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id AAA08253
for freebsd-current-outgoing; Thu, 28 Jan 1999 00:34:33 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from zeus.theinternet.com.au (zeus.theinternet.com.au [203.34.176.2])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA08245
for <current@FreeBSD.ORG>; Thu, 28 Jan 1999 00:34:28 -0800 (PST)
(envelope-from akm@zeus.theinternet.com.au)
Received: (from akm@localhost)
by zeus.theinternet.com.au (8.8.7/8.8.7) id SAA14617;
Thu, 28 Jan 1999 18:33:46 +1000 (EST)
(envelope-from akm)
From: Andrew Kenneth Milton <akm@zeus.theinternet.com.au>
Message-Id: <199901280833.SAA14617@zeus.theinternet.com.au>
Subject: Re: btokup().. STYLE(9)
In-Reply-To: <199901280728.XAA98161@apollo.backplane.com> from Matthew Dillon at "Jan 27, 99 11:28:20 pm"
To: dillon@apollo.backplane.com (Matthew Dillon)
Date: Thu, 28 Jan 1999 18:33:46 +1000 (EST)
Cc: julian@whistle.com, jb@cimlogic.com.au, jdp@polstra.com, bde@zeta.org.au,
current@FreeBSD.ORG
X-Mailer: ELM [version 2.4ME+ PL32 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
+----[ Matthew Dillon ]---------------------------------------------
|
| :I think that style(9) should be modified to include
| :"Parenthesis may be used to improve the readbility of complex
| :expressions even if not strictly required."
| :instead of the stupid phrase presently there.
| :also:
| :"Braces around code blocks should be allowable even when not strictly
| :needed, for the purpose of readbility."
| :
| :The aim is to produce readble maintainable code, not to save bytes in
| :sourcecode!
|
| I agree completely. I've already gotten into the habit of added
| braces when conditonal expressions exceed one line, even though there
| may be only one statement. Otherwise the code is just too unreadable.
Is there an ident style for (x)emacs to enforce/promote this style?
A set of macros for the *macs family that conforms to whatever
style(9) is for that day would be pretty neat.
I don't know about coral et. al or about how extensible they are
but, gurus for those other editors could also contribute configs
for a port?
Just a thought.
--
Totally Holistic Enterprises Internet| P:+61 7 3870 0066 | Andrew
The Internet (Aust) Pty Ltd | F:+61 7 3870 4477 | Milton
ACN: 082 081 472 | M:+61 416 022 411 |72 Col .Sig
PO Box 837 Indooroopilly QLD 4068 |akm@theinternet.com.au|Specialist
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Thu Jan 28 00:36:18 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id AAA08427
for freebsd-current-outgoing; Thu, 28 Jan 1999 00:36:18 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from shell.futuresouth.com (shell.futuresouth.com [198.78.58.28])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA08422
for <current@FreeBSD.ORG>; Thu, 28 Jan 1999 00:36:16 -0800 (PST)
(envelope-from fullermd@futuresouth.com)
Received: (from fullermd@localhost)
by shell.futuresouth.com (8.9.1a/8.9.1) id CAA26619;
Thu, 28 Jan 1999 02:35:56 -0600 (CST)
Message-ID: <19990128023555.B16540@futuresouth.com>
Date: Thu, 28 Jan 1999 02:35:55 -0600
From: "Matthew D. Fuller" <fullermd@futuresouth.com>
To: Greg Lehey <grog@lemis.com>
Cc: current@FreeBSD.ORG
Subject: Re: indent(1) and style(9) (was: btokup() macro in sys/malloc.h)
References: <199901280316.OAA26849@godzilla.zeta.org.au> <19990128180537.B8473@freebie.lemis.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.93.2i
In-Reply-To: <19990128180537.B8473@freebie.lemis.com>; from Greg Lehey on Thu, Jan 28, 1999 at 06:05:37PM +1030
X-OS: FreeBSD <http://www.freebsd.org>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
On Thu, Jan 28, 1999 at 06:05:37PM +1030, a little birdie told me
that Greg Lehey remarked
> On Thursday, 28 January 1999 at 14:16:25 +1100, Bruce Evans wrote:
> >> It would be nice if style(9) documented the options to give indent(1)
> >> to match the `approved' layout convections. (This would reduce the
> >> effort involved in importing large chunks of code).
> >
> > This is impossible, since indent(1) is buggy and out of date with both
> > KNF and C.
>
> Well, you can do a certain amount. In fact, I use GNU indent and
> achieve a reasonable approximation. It would be nice to import it,
> but it doesn't comply with style(9) :-)
indent(1) is EVIL! :)
I just recently (~month.5) had to completely reformat a mid-sized program
(~70k lines), and I had to rereformat the whole thing after indent got
done with it. It couldn't even handle:
}
else /* comment */
{
It would extend the comment over the ENTIRE following code block until it
hit another comment to end it.
Sorry, I still get twitchy when the word 'indent' is said...
---
*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*
| Matthew Fuller http://www.over-yonder.net/~fullermd |
* fullermd@futuresouth.com fullermd@over-yonder.net *
| UNIX Systems Administrator Specializing in FreeBSD |
* FutureSouth Communications ISPHelp ISP Consulting *
| "The only reason I'm burning my candle at both ends, |
* is because I haven't figured out how to light the *
| middle yet" |
*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Thu Jan 28 00:41:34 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id AAA08822
for freebsd-current-outgoing; Thu, 28 Jan 1999 00:41:34 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from janus.syracuse.net (janus.syracuse.net [205.232.47.15])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA08812
for <current@FreeBSD.ORG>; Thu, 28 Jan 1999 00:41:30 -0800 (PST)
(envelope-from green@unixhelp.org)
Received: from localhost (green@localhost)
by janus.syracuse.net (8.8.8/8.8.7) with ESMTP id DAA28774;
Thu, 28 Jan 1999 03:41:25 -0500 (EST)
Date: Thu, 28 Jan 1999 03:41:25 -0500 (EST)
From: Brian Feldman <green@unixhelp.org>
X-Sender: green@janus.syracuse.net
To: John Birrell <jb@cimlogic.com.au>
cc: Nate Williams <nate@mt.sri.com>, archie@whistle.com,
wollman@khavrinen.lcs.mit.edu, current@FreeBSD.ORG
Subject: Re: btokup() macro in sys/malloc.h
In-Reply-To: <199901280558.QAA07918@cimlogic.com.au>
Message-ID: <Pine.BSF.4.05.9901280334400.28225-100000@janus.syracuse.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
On Thu, 28 Jan 1999, John Birrell wrote:
> Nate Williams wrote:
> > > Anyway, if we're going to -Wall'ify the kernel (as we should)
> > > then we need to update sytle(9) to reflect that.
> > >
> > > In fact, style(9) should say:
> > >
> > > If at all possible, your code should compile without warnings
> > > when the gcc -Wall flag is given.
> >
> > I disagree. As has been shown many times in the past (and I suspect the
> > down-under constituent will show that at least a couple of the
>
> I think you must mean the "Sydney-down-under constituent". There *is*
> a difference. 8-)
>
> > 'warnings' fixes will be wrong and hide bogus code), making -Wall a goal
> > causes people to cover up bad code with bad casts and such.
> >
> > '-Wall' is *NOT* a good design goal.
>
> Fixing warnings with bad casts is a problem, sure, but asking people
> to write code without casts (if possible) that will compile cleanly with
> -Wall is a reasonable thing to ask IMO. In my experience, the resulting
> code tends to be more portable across architectures with different
> pointer/long sizes and endian-ness.
>
> Just my 0.02, and I hate style(9) anyway.
>
In cases, -Wall is bogus anyway. Here's one:
foo.c:89: warning: char format, void arg (arg 2)
void *region;
printf("mem open failed: %s\n", region);
According to standards, a void pointer may be freely used instead of any
other type of pointer, both as an lvalue and to assign to the other pointer.
Printf(), hence, wouldn't see a difference (of course). Gcc should not
complain about various void pointer things like this.
> --
> John Birrell - jb@cimlogic.com.au; jb@freebsd.org http://www.cimlogic.com.au/
> CIMlogic Pty Ltd, GPO Box 117A, Melbourne Vic 3001, Australia +61 418 353 137
>
> To Unsubscribe: send mail to majordomo@FreeBSD.org
> with "unsubscribe freebsd-current" in the body of the message
>
Brian Feldman _ __ ___ ___ ___
green@unixhelp.org _ __ ___ | _ ) __| \
http://www.freebsd.org/ _ __ ___ ____ | _ \__ \ |) |
FreeBSD: The Power to Serve! _ __ ___ ____ _____ |___/___/___/
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Thu Jan 28 00:47:25 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id AAA09480
for freebsd-current-outgoing; Thu, 28 Jan 1999 00:47:25 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from janus.syracuse.net (janus.syracuse.net [205.232.47.15])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA09474
for <current@FreeBSD.ORG>; Thu, 28 Jan 1999 00:47:24 -0800 (PST)
(envelope-from green@unixhelp.org)
Received: from localhost (green@localhost)
by janus.syracuse.net (8.8.8/8.8.7) with ESMTP id DAA29006;
Thu, 28 Jan 1999 03:47:27 -0500 (EST)
Date: Thu, 28 Jan 1999 03:47:27 -0500 (EST)
From: Brian Feldman <green@unixhelp.org>
X-Sender: green@janus.syracuse.net
To: Matthew Dillon <dillon@apollo.backplane.com>
cc: Nate Williams <nate@mt.sri.com>, Archie Cobbs <archie@whistle.com>,
Garrett Wollman <wollman@khavrinen.lcs.mit.edu>, current@FreeBSD.ORG
Subject: Re: btokup() macro in sys/malloc.h
In-Reply-To: <199901280603.WAA93627@apollo.backplane.com>
Message-ID: <Pine.BSF.4.05.9901280345020.28225-100000@janus.syracuse.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
On Wed, 27 Jan 1999, Matthew Dillon wrote:
>
> :> then we need to update sytle(9) to reflect that.
> :>
> :> In fact, style(9) should say:
> :>
> :> If at all possible, your code should compile without warnings
> :> when the gcc -Wall flag is given.
> :
> :I disagree. As has been shown many times in the past (and I suspect the
> :down-under constituent will show that at least a couple of the
> :'warnings' fixes will be wrong and hide bogus code), making -Wall a goal
> :causes people to cover up bad code with bad casts and such.
> :
> :'-Wall' is *NOT* a good design goal.
>
> Nonsense. -Wall does *NOT* contribute to a bad programmer programming
> badly, and I found at least three fairly serious mistakes when I turned
> it on.
>
> I mean, come on... by your argument the compiler might as well give up
> and not bother warning you about anything!
And for the exact antithesis of silence, TenDRA has the most wonderful warnings,
and it's a great free linter (but does its job better than standard lint),
while producing as good code as GCC most of the time. That takes not into
account once when I ran into some glaring bugs in the compilation, but at
least the warnings were correct :)
>
> -Matt
> Matthew Dillon
> <dillon@backplane.com>
>
> :Nate
> :
> :To Unsubscribe: send mail to majordomo@FreeBSD.org
> :with "unsubscribe freebsd-current" in the body of the message
> :
>
>
> To Unsubscribe: send mail to majordomo@FreeBSD.org
> with "unsubscribe freebsd-current" in the body of the message
>
Brian Feldman _ __ ___ ___ ___
green@unixhelp.org _ __ ___ | _ ) __| \
http://www.freebsd.org/ _ __ ___ ____ | _ \__ \ |) |
FreeBSD: The Power to Serve! _ __ ___ ____ _____ |___/___/___/
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Thu Jan 28 00:47:59 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id AAA09547
for freebsd-current-outgoing; Thu, 28 Jan 1999 00:47:59 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA09538
for <current@FreeBSD.ORG>; Thu, 28 Jan 1999 00:47:57 -0800 (PST)
(envelope-from jkh@zippy.cdrom.com)
Received: from zippy.cdrom.com (localhost.cdrom.com [127.0.0.1])
by zippy.cdrom.com (8.9.2/8.9.1) with ESMTP id AAA83915;
Thu, 28 Jan 1999 00:48:22 -0800 (PST)
To: Matthew Dillon <dillon@apollo.backplane.com>
cc: Archie Cobbs <archie@whistle.com>, current@FreeBSD.ORG
Subject: Re: cvs commit: src/sys/i386/eisa ahb.c
In-reply-to: Your message of "Wed, 27 Jan 1999 23:21:46 PST."
<199901280721.XAA98105@apollo.backplane.com>
Date: Thu, 28 Jan 1999 00:48:21 -0800
Message-ID: <83910.917513301@zippy.cdrom.com>
From: "Jordan K. Hubbard" <jkh@zippy.cdrom.com>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
> How Mr. ignoromous Nate could construe this to mean that I was trying
> to brush something under the rug is beyond me. As I said to Julian,
> I probably shouldn't have made the committ, but the fact is that I
> not only left the module on my hotlist, I also immediately brought
> the potential problem to the attention of the entire list and thence,
I think this whole tangled thread can probably be summed up thusly:
There will always be those remarking from the sidelines about any
change which goes into the FreeBSD source tree, and I do mean ANY
change, the amount of commentary usually in inverse proportion to the
importance of the change. This is just a given. It's also a given
that some of these people will have far less clue than others and even
those who have a clue will often express their comments in such a way
as to come across as criticising or carping, even though they may not
have meant to. There are a lot of engineers here and human
interaction is rarely their strong suit.
In any case, rather than getting into a protracted furball with each
and every commentator and perhaps using inappropriate language in a
public mailing list in the process, you've gotta do what pro golfers
and ballplayers do - learn to ignore the crowd when it hasn't got
anything useful to say. Any other strategy will, eventually, have you
charging around the crowd, waving your golf club and slobbering
maniacally - not really the kind of public image you want to be
cultivating here. :-)
- Jordan
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Thu Jan 28 00:48:36 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id AAA09611
for freebsd-current-outgoing; Thu, 28 Jan 1999 00:48:36 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA09603
for <current@FreeBSD.ORG>; Thu, 28 Jan 1999 00:48:34 -0800 (PST)
(envelope-from dillon@apollo.backplane.com)
Received: (from dillon@localhost)
by apollo.backplane.com (8.9.2/8.9.1) id AAA02175;
Thu, 28 Jan 1999 00:45:31 -0800 (PST)
(envelope-from dillon)
Date: Thu, 28 Jan 1999 00:45:31 -0800 (PST)
From: Matthew Dillon <dillon@apollo.backplane.com>
Message-Id: <199901280845.AAA02175@apollo.backplane.com>
To: Poul-Henning Kamp <phk@critter.freebsd.dk>
Cc: Nate Williams <nate@mt.sri.com>, Archie Cobbs <archie@whistle.com>,
wollman@khavrinen.lcs.mit.edu (Garrett Wollman), current@FreeBSD.ORG
Subject: Re: btokup() macro in sys/malloc.h
References: <33900.917511995@critter.freebsd.dk>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
:Matt,
:
:By now we do know a GREAT deal about you from the way you behave.
:
:Trying to judge your age from that data, 16 years can certainly not
:be ruled out conclusively.
:
:I will make no secret of the fact that I was not at all happy with
:you becoming a committer, and your behaviour the last couple of
:days is exactly what I feared and expected would happen.
:
:Please go out and get yourself some fresh air & some perspective.
:
:This is FreeBSD, not MattBSD.
:
:Poul-Henning
Behavior? Oh, you mean spending 8 hours getting -Wall to work?
Or do you mean the new swapper? Or the huge amount of work we did
to solve the dirty cache vm_page_t problem?
Perhaps it was the discussion about DOS attacks against the system
and why load-average-based algorithms don't work well.
Lets see, what else is in my archive. Gee, looks like helpful posts
for the most part!
Could it be cpdup that you don't like?
Maybe the scheduler discussions grated on your nerves?
The diskless mods? I don't recall doing anything against people's
wishes there. The sysctl mods were backed out relatively quickly...
or did you bother to note that?
Do you think I just commit things and then sit on them like a stone
statue? If you look, carefully, you will find that I'm usually the
first to admit when I've made a mistake and I fix things very quickly.
As far as I know, there is nothing currently committed that anyone has
a problem with except, perhaps /etc/rc.conf.local ... but I stood
by that and it seems to have grown on people considering the recent
discussions to expand the stacked configuration mechanisms.
--
Since you seem to see it fit to accuse me of something in public,
back it up on this forum. I have a complete archive, we can swap
examples.
I'll be plain: I'm a nice guy, and if you treat me fairly I'll treat
you fairly. But I don't let people talk shit about me or shit to me
if I think I'm in the right. I don't like vague accusations, either.
If someone accuses me of something on a public forum, I answer on that
forum, plain and simple.
-Matt
Matthew Dillon
<dillon@backplane.com>
:--
:Poul-Henning Kamp FreeBSD coreteam member
:phk@FreeBSD.ORG "Real hackers run -current on their laptop."
:FreeBSD -- It will take a long time before progress goes too far!
:
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Thu Jan 28 00:50:08 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id AAA09831
for freebsd-current-outgoing; Thu, 28 Jan 1999 00:50:08 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from relay.nuxi.com ([169.237.7.38])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA09820
for <current@FreeBSD.ORG>; Thu, 28 Jan 1999 00:50:05 -0800 (PST)
(envelope-from obrien@NUXI.com)
Received: (from obrien@localhost)
by relay.nuxi.com (8.9.1/8.9.1) id AAA01432;
Thu, 28 Jan 1999 00:49:59 -0800 (PST)
(envelope-from obrien)
Date: Thu, 28 Jan 1999 00:49:59 -0800
From: "David O'Brien" <obrien@NUXI.com>
To: Glenn Johnson <gjohnson@nola.srrc.usda.gov>
Cc: current@FreeBSD.ORG
Subject: Re: removing f2c from base distribution
Message-ID: <19990128004959.C563@relay.nuxi.com>
Reply-To: obrien@NUXI.com
References: <19990127005850.A10486@gforce.johnson.home> <199901271314.FAA65788@silvia.hip.berkeley.edu> <19990127102301.A80336@symbion.srrc.usda.gov>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.95i
In-Reply-To: <19990127102301.A80336@symbion.srrc.usda.gov>; from Glenn Johnson on Wed, Jan 27, 1999 at 10:23:01AM -0600
X-Operating-System: FreeBSD 3.0-CURRENT
Organization: The NUXI BSD group
X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A
X-Pgp-Keyid: 34F9F9D5
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
> If it is decided that Fortran support will disappear from the base
> system and nobody else wants to maintain g77, I will gladly do it.
> However, I will only maintain a version that I am using so that means I
> will maintain a port once gcc 2.8 is officially brought in as the stock
> compiler.
Lets just crush the g77 port and tell people to install EGCS. I build
g77 as part of that port. I welcome patches and feedback on the
usablability of g77 w/in EGCS.
--
-- David (obrien@NUXI.com -or- obrien@FreeBSD.org)
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Thu Jan 28 00:50:18 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id AAA09864
for freebsd-current-outgoing; Thu, 28 Jan 1999 00:50:18 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA09858
for <current@FreeBSD.ORG>; Thu, 28 Jan 1999 00:50:17 -0800 (PST)
(envelope-from julian@whistle.com)
Received: (from daemon@localhost)
by alpo.whistle.com (8.8.5/8.8.5) id AAA24819;
Thu, 28 Jan 1999 00:43:20 -0800 (PST)
Received: from s204m82.isp.whistle.com(207.76.204.82)
via SMTP by alpo.whistle.com, id smtpdn24815; Thu Jan 28 08:43:11 1999
Date: Thu, 28 Jan 1999 00:43:07 -0800 (PST)
From: Julian Elischer <julian@whistle.com>
X-Sender: julian@s204m82.isp.whistle.com
To: Matthew Dillon <dillon@apollo.backplane.com>
cc: current@FreeBSD.ORG
Subject: Re: -Wall -Wcast-qual and SYSINIT
In-Reply-To: <199901280826.AAA02016@apollo.backplane.com>
Message-ID: <Pine.BSF.4.05.9901280034480.304-100000@s204m82.isp.whistle.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
On Thu, 28 Jan 1999, Matthew Dillon wrote:
> Most of the functions do not expect a const argument, though that
> may simply be because they didn't bother to use const when they
> could have.
>
> However, I know at least the MALLOC initialization objects *can't*
> use const objects because the malloc initialization routine modifies
> the data object.
OK I understand now..
theoretically I guess you should have two types of SYSINIT,
however you are already not able to check the TYPE of the argument due to
it being passed through the void form, so losing the 'const'-ness is not
that much of a loss. The pragmetic answer may just be to 'cast' in the
macro.
>
> I'm sure that a non-trivial number of the sysinits also modify their
> data objects. So we need to handle both cases.
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Thu Jan 28 00:52:01 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id AAA09975
for freebsd-current-outgoing; Thu, 28 Jan 1999 00:52:01 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from relay.nuxi.com ([169.237.7.38])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA09961
for <current@FreeBSD.ORG>; Thu, 28 Jan 1999 00:51:59 -0800 (PST)
(envelope-from obrien@NUXI.com)
Received: (from obrien@localhost)
by relay.nuxi.com (8.9.1/8.9.1) id AAA01477;
Thu, 28 Jan 1999 00:51:57 -0800 (PST)
(envelope-from obrien)
Date: Thu, 28 Jan 1999 00:51:57 -0800
From: "David O'Brien" <obrien@NUXI.com>
To: Glenn Johnson <gjohnson@nola.srrc.usda.gov>
Cc: current@FreeBSD.ORG
Subject: Re: removing f2c from base distribution
Message-ID: <19990128005157.D563@relay.nuxi.com>
Reply-To: obrien@NUXI.com
References: <199901271718.JAA11594@troutmask.apl.washington.edu> <199901271729.JAA67196@silvia.hip.berkeley.edu> <19990127122008.A17603@symbion.srrc.usda.gov>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.95i
In-Reply-To: <19990127122008.A17603@symbion.srrc.usda.gov>; from Glenn Johnson on Wed, Jan 27, 1999 at 12:20:08PM -0600
X-Operating-System: FreeBSD 3.0-CURRENT
Organization: The NUXI BSD group
X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A
X-Pgp-Keyid: 34F9F9D5
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
> Getting g77 from egcs is the best option right now. However, it seems to
> me that this adds a lot of bloat (duplication of C, C++, etc.) to the
> system for someone wanting to use FreeBSD as a scientific workstation
> platform.
Then update the g77 port to fetch egcs-core-XYZ.tar.gz and
egcs-g77-XYZ.tar.gz and build it that way. You will have no C, C++ or
objC support in the result.
--
-- David (obrien@NUXI.com -or- obrien@FreeBSD.org)
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Thu Jan 28 01:02:18 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id BAA11298
for freebsd-current-outgoing; Thu, 28 Jan 1999 01:02:18 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA11268
for <current@FreeBSD.ORG>; Thu, 28 Jan 1999 01:02:13 -0800 (PST)
(envelope-from phk@critter.freebsd.dk)
Received: from critter.freebsd.dk (localhost [127.0.0.1])
by critter.freebsd.dk (8.9.1/8.8.5) with ESMTP id JAA34081;
Thu, 28 Jan 1999 09:56:19 +0100 (CET)
To: Matthew Dillon <dillon@apollo.backplane.com>
cc: Nate Williams <nate@mt.sri.com>, Archie Cobbs <archie@whistle.com>,
wollman@khavrinen.lcs.mit.edu (Garrett Wollman), current@FreeBSD.ORG
Subject: Re: btokup() macro in sys/malloc.h
In-reply-to: Your message of "Thu, 28 Jan 1999 00:45:31 PST."
<199901280845.AAA02175@apollo.backplane.com>
Date: Thu, 28 Jan 1999 09:56:13 +0100
Message-ID: <34079.917513773@critter.freebsd.dk>
From: Poul-Henning Kamp <phk@critter.freebsd.dk>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
Matt,
Please leave your keyboard now.
Get some sleep, some rest and a couple of days off.
You need it, we need it.
Poul-Henning
--
Poul-Henning Kamp FreeBSD coreteam member
phk@FreeBSD.ORG "Real hackers run -current on their laptop."
FreeBSD -- It will take a long time before progress goes too far!
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Thu Jan 28 01:04:56 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id BAA11531
for freebsd-current-outgoing; Thu, 28 Jan 1999 01:04:56 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from janus.syracuse.net (janus.syracuse.net [205.232.47.15])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA11526
for <current@FreeBSD.ORG>; Thu, 28 Jan 1999 01:04:54 -0800 (PST)
(envelope-from green@unixhelp.org)
Received: from localhost (green@localhost)
by janus.syracuse.net (8.8.8/8.8.7) with ESMTP id EAA29777;
Thu, 28 Jan 1999 04:05:02 -0500 (EST)
Date: Thu, 28 Jan 1999 04:05:02 -0500 (EST)
From: Brian Feldman <green@unixhelp.org>
X-Sender: green@janus.syracuse.net
To: Matthew Dillon <dillon@apollo.backplane.com>
cc: current@FreeBSD.ORG
Subject: Re: -Wall -Wcast-qual and SYSINIT
In-Reply-To: <199901280753.XAA98980@apollo.backplane.com>
Message-ID: <Pine.BSF.4.05.9901280404120.28225-100000@janus.syracuse.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
On Wed, 27 Jan 1999, Matthew Dillon wrote:
> Right now we have a problem with struct sysinit.
>
> The problem is that some SYSINIT functions supply a function taking
> a const void * and a const pointer for data, and other SYSINIT
> functions supply a function taking a void * and a non-const pointer
> for data.
>
> What this means, effectively, is that we want one of two SYSINIT
> structures where both the function argument and udata are of the
> same type. Something like the union shown below. If the function
> argument type does not match the data type we want the initialization
> to generate a warning.
>
> struct sysinit {
> unsigned int subsystem; /* subsystem identifier*/
> unsigned int order; /* init order within subsystem*/
> union {
> struct {
> void (*func) __P((void *));
> void *udata; /* multiplexer/argument */
> } n;
> struct {
> void (*func) __P((const void *));
> const void *udata; /* multiplexer/argument */
> } c;
> } u;
> si_elem_t type; /* sysinit_elem_type*/
> };
>
> Unfortunately, GCC isn't smart enough to match the function type
> to the correct structure - it always stuffs it into the first structure.
Overloading a struct? Yuck :(
>
> So the above cool hack will not work :-(.
Overloading is just a bad hack in concept.
>
> I can't think of how to do this without actually having two different
> sysinit structures - on that uses a non-const function and data element,
> and one that uses a const function and data element. While having two
> sysinit structures would work, it would be a little iffy keeping them
> in sync with each other so the kernel init call code doesn't have to deal
> with both types.
>
> struct c_sysinit {
> unsigned int subsystem; /* subsystem identifier*/
> unsigned int order; /* init order within subsystem*/
> void (*func) __P((void *));
> void *udata; /* multiplexer/argument */
> si_elem_t type; /* sysinit_elem_type*/
> };
>
> struct n_sysinit {
> unsigned int subsystem; /* subsystem identifier*/
> unsigned int order; /* init order within subsystem*/
> void (*func) __P((const void *));
> const void *udata; /* multiplexer/argument */
> si_elem_t type; /* sysinit_elem_type*/
> };
>
> The SYSINIT problem accounts for about half the remaining compilation
> warnings. I would like to find a good solution for it.
>
> -Matt
> Matthew Dillon
> <dillon@backplane.com>
>
>
> To Unsubscribe: send mail to majordomo@FreeBSD.org
> with "unsubscribe freebsd-current" in the body of the message
>
Brian Feldman _ __ ___ ___ ___
green@unixhelp.org _ __ ___ | _ ) __| \
http://www.freebsd.org/ _ __ ___ ____ | _ \__ \ |) |
FreeBSD: The Power to Serve! _ __ ___ ____ _____ |___/___/___/
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Thu Jan 28 01:07:22 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id BAA11828
for freebsd-current-outgoing; Thu, 28 Jan 1999 01:07:22 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from verdi.nethelp.no (verdi.nethelp.no [158.36.41.162])
by hub.freebsd.org (8.8.8/8.8.8) with SMTP id BAA11817
for <current@FreeBSD.ORG>; Thu, 28 Jan 1999 01:07:18 -0800 (PST)
(envelope-from sthaug@nethelp.no)
From: sthaug@nethelp.no
Received: (qmail 7989 invoked by uid 1001); 28 Jan 1999 09:07:15 +0000 (GMT)
To: wilko@yedi.iaf.nl
Cc: archie@whistle.com, dfr@nlsystems.com, current@FreeBSD.ORG
Subject: Re: DEVFS, the time has come...
In-Reply-To: Your message of "Wed, 27 Jan 1999 23:12:18 +0100 (CET)"
References: <199901272212.XAA03458@yedi.iaf.nl>
X-Mailer: Mew version 1.05+ on Emacs 19.34.2
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Date: Thu, 28 Jan 1999 10:07:15 +0100
Message-ID: <7987.917514435@verdi.nethelp.no>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
> > I agree.. and same thing goes for Ethernet drivers. I actually
> > like the way Linux always has "eth0", "eth1", ... (which we could
>
> Yeagh... what is wrong with ed0, de0, fxp0 etc that needs changing? Is this
> just a matter of taste or is there more to it? I for one don't see any
> advantage in eth[0-9] style device naming.
I can give you one example. We run a FreeBSD box here which receives
all of the traffic (port mirroring) from some Ethernet switches. On
the FreeBSD box, we run nnstat, tcpdump etc. for monitoring purposes.
Recently I changed some of the DEC 21x4x based cards on this box to
Intel cards. Thus the interface names changed from deN to fxpN. This
meant we had to update a bunch of Perl and shell scripts. It would
have been much nicer (no need to update) if the interfaces were simply
named ethN.
Personally, I'd also prefer to have IDE disks named daN, but that's
another matter...
Steinar Haug, Nethelp consulting, sthaug@nethelp.no
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Thu Jan 28 01:07:33 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id BAA11852
for freebsd-current-outgoing; Thu, 28 Jan 1999 01:07:33 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.26.10.9])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA11844
for <freebsd-current@FreeBSD.ORG>; Thu, 28 Jan 1999 01:07:29 -0800 (PST)
(envelope-from bde@godzilla.zeta.org.au)
Received: (from bde@localhost)
by godzilla.zeta.org.au (8.8.7/8.8.7) id UAA27849;
Thu, 28 Jan 1999 20:06:58 +1100
Date: Thu, 28 Jan 1999 20:06:58 +1100
From: Bruce Evans <bde@zeta.org.au>
Message-Id: <199901280906.UAA27849@godzilla.zeta.org.au>
To: axl@iafrica.com, pantzer@ludd.luth.se
Subject: Re: NIS with HPUX 10.20
Cc: freebsd-current@FreeBSD.ORG
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
>> Why _not_ use -C? What is the point in replacing a file with the same file?
>> install -C will replace the file if the new file is diffrent.
>
>Aaaaaaaah, thank you. I misread the manpage description of -C and didn't
>notice "and the files are the same"...
>
>Cleared up, head back on straight. :-)
This is not so clear :-). -C always does a complete replacement of the
file, as does -c, but the man page bogusly claims that the target file
is overwritten. The complete replacement is necessary to snap any links
(another undocumented feature).
Someday -C should avoid touching the file if possible, so that it
doesn't clobber the file's ctime and backups based on ctimes don't do
unnecessary work. This is possible if none of the attributes except
the file times would change, and fairly easy to implement if the file
doesn't have any links.
Bruce
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Thu Jan 28 01:07:58 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id BAA11885
for freebsd-current-outgoing; Thu, 28 Jan 1999 01:07:58 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA11880
for <current@FreeBSD.ORG>; Thu, 28 Jan 1999 01:07:56 -0800 (PST)
(envelope-from dillon@apollo.backplane.com)
Received: (from dillon@localhost)
by apollo.backplane.com (8.9.2/8.9.1) id BAA02505;
Thu, 28 Jan 1999 01:07:49 -0800 (PST)
(envelope-from dillon)
Date: Thu, 28 Jan 1999 01:07:49 -0800 (PST)
From: Matthew Dillon <dillon@apollo.backplane.com>
Message-Id: <199901280907.BAA02505@apollo.backplane.com>
To: Brian Feldman <green@unixhelp.org>
Cc: current@FreeBSD.ORG
Subject: Re: -Wall -Wcast-qual and SYSINIT
References: <Pine.BSF.4.05.9901280404120.28225-100000@janus.syracuse.net>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
:
:Overloading a struct? Yuck :(
:
:>
:> So the above cool hack will not work :-(.
:
:Overloading is just a bad hack in concept.
Tell me something I don't know. If it were simple and straightforward,
I'd have simply committed it.
-Matt
: Brian Feldman _ __ ___ ___ ___
: green@unixhelp.org _ __ ___ | _ ) __| \
Matthew Dillon
<dillon@backplane.com>
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Thu Jan 28 01:10:24 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id BAA12072
for freebsd-current-outgoing; Thu, 28 Jan 1999 01:10:24 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from nlsystems.com (nlsys.demon.co.uk [158.152.125.33])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA12063
for <current@FreeBSD.ORG>; Thu, 28 Jan 1999 01:10:19 -0800 (PST)
(envelope-from dfr@nlsystems.com)
Received: from localhost (dfr@localhost)
by nlsystems.com (8.9.1/8.8.5) with SMTP id JAA00584;
Thu, 28 Jan 1999 09:11:42 GMT
Date: Thu, 28 Jan 1999 09:11:42 +0000 (GMT)
From: Doug Rabson <dfr@nlsystems.com>
To: Harlan Stenn <Harlan.Stenn@pfcs.com>
cc: "Daniel O'Connor" <doconnor@gsoft.com.au>, Wilko Bulte <wilko@yedi.iaf.nl>,
current@FreeBSD.ORG, Archie Cobbs <archie@whistle.com>
Subject: Re: DEVFS, the time has come...
In-Reply-To: <20942.917503290@brown.pfcs.com>
Message-ID: <Pine.BSF.4.01.9901280910080.95594-100000@herring.nlsystems.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
On Thu, 28 Jan 1999, Harlan Stenn wrote:
> > Also the eth[0..x] thing means you can replace your ethernet card with a
> > new one of a different type without having to look through your config
> > code for references to ed0 or whatever.
>
> Just to ask, what happens when the probe order changes and your multiple
> NICs start popping up on the wrong eth port?
>
> This may be *much* more difficult when one of several cards die (how do you
> know which one broke?) and then you replace it and discover the new probe
> order is different...
>
> Or will be be able to wire them down in the config file (which will at
> least address part of the problem)?
If we did this, there would obviously have to be some kind of wiring
system. The same problem exists in a much smaller way for machines with
more that one of the same type of card.
--
Doug Rabson Mail: dfr@nlsystems.com
Nonlinear Systems Ltd. Phone: +44 181 442 9037
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Thu Jan 28 01:12:35 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id BAA12286
for freebsd-current-outgoing; Thu, 28 Jan 1999 01:12:35 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from nlsystems.com (nlsys.demon.co.uk [158.152.125.33])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA12277
for <current@FreeBSD.ORG>; Thu, 28 Jan 1999 01:12:32 -0800 (PST)
(envelope-from dfr@nlsystems.com)
Received: from localhost (dfr@localhost)
by nlsystems.com (8.9.1/8.8.5) with SMTP id JAA00826;
Thu, 28 Jan 1999 09:15:06 GMT
Date: Thu, 28 Jan 1999 09:15:06 +0000 (GMT)
From: Doug Rabson <dfr@nlsystems.com>
To: Leif Neland <leif@neland.dk>
cc: Archie Cobbs <archie@whistle.com>, current@FreeBSD.ORG
Subject: Re: DEVFS, the time has come...
In-Reply-To: <Pine.BSF.4.05.9901280807390.11164-100000@arnold.neland.dk>
Message-ID: <Pine.BSF.4.01.9901280914450.95594-100000@herring.nlsystems.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
On Thu, 28 Jan 1999, Leif Neland wrote:
>
>
> On Wed, 27 Jan 1999, Archie Cobbs wrote:
>
> > Doug Rabson writes:
> > > And another thing. Why can't we use a non-driver-specific name for the
> > > disk? Most users simply don't care whether the driver was fd, wfd, wd or
> > > anything. They just want to get to their files without any fuss.
> >
> > I agree.. and same thing goes for Ethernet drivers. I actually
> > like the way Linux always has "eth0", "eth1", ... (which we could
> > do using netgraph, with some work).
> >
> Just symlink eth0 to which card you like, just as /dev/mixer happens to be
> a symlink to /dev/mixer1 on my system.
Unfortunately network devices aren't represented in /dev on BSD systems.
--
Doug Rabson Mail: dfr@nlsystems.com
Nonlinear Systems Ltd. Phone: +44 181 442 9037
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Thu Jan 28 01:13:47 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id BAA12479
for freebsd-current-outgoing; Thu, 28 Jan 1999 01:13:47 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from labinfo.iet.unipi.it (labinfo.iet.unipi.it [131.114.9.5])
by hub.freebsd.org (8.8.8/8.8.8) with SMTP id BAA12465
for <current@FreeBSD.ORG>; Thu, 28 Jan 1999 01:13:37 -0800 (PST)
(envelope-from luigi@labinfo.iet.unipi.it)
Received: from localhost (luigi@localhost) by labinfo.iet.unipi.it (8.6.5/8.6.5) id IAA08320; Thu, 28 Jan 1999 08:01:33 +0100
From: Luigi Rizzo <luigi@labinfo.iet.unipi.it>
Message-Id: <199901280701.IAA08320@labinfo.iet.unipi.it>
Subject: Re: indent(1) and style(9) (was: btokup() macro in sys/malloc.h)
To: bde@zeta.org.au (Bruce Evans)
Date: Thu, 28 Jan 1999 08:01:33 +0100 (MET)
Cc: bde@zeta.org.au, grog@lemis.com, current@FreeBSD.ORG,
peter.jeremy@auss2.alcatel.com.au
In-Reply-To: <199901280819.TAA23954@godzilla.zeta.org.au> from "Bruce Evans" at Jan 28, 99 07:18:53 pm
X-Mailer: ELM [version 2.4 PL23]
Content-Type: text
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
> I see no evidence of this. vinum sources don't seem to have a single
> line in KNF, except accidentally. They have an indentation of 4
> instead of 8, lots of per-statement comments, lots of lines longer
> than 80 characters, lots of block comments without `/*' and `*/' on
> a line by themself, ...
not speaking about vinum, but to me, the indentation of 8 char and
line length of 80 chars are almost mutually exclusive.
See e.g. tcp_input.c ip_input.c and many network device drivers as
an example -- basically all places where, for efficiency reasons,
the code tries to expand in-line various block, the depth of
indentation pushes everything to the right end leaving only 20-30
useful chars per line.
cheers
luigi
-----------------------------------+-------------------------------------
Luigi RIZZO .
EMAIL: luigi@iet.unipi.it . Dip. di Ing. dell'Informazione
HTTP://www.iet.unipi.it/~luigi/ . Universita` di Pisa
TEL/FAX: +39-050-568.533/522 . via Diotisalvi 2, 56126 PISA (Italy)
-----------------------------------+-------------------------------------
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Thu Jan 28 01:14:03 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id BAA12537
for freebsd-current-outgoing; Thu, 28 Jan 1999 01:14:03 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.26.10.9])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA12495
for <current@FreeBSD.ORG>; Thu, 28 Jan 1999 01:13:59 -0800 (PST)
(envelope-from bde@godzilla.zeta.org.au)
Received: (from bde@localhost)
by godzilla.zeta.org.au (8.8.7/8.8.7) id UAA28491;
Thu, 28 Jan 1999 20:13:53 +1100
Date: Thu, 28 Jan 1999 20:13:53 +1100
From: Bruce Evans <bde@zeta.org.au>
Message-Id: <199901280913.UAA28491@godzilla.zeta.org.au>
To: phk@critter.freebsd.dk, wollman@khavrinen.lcs.mit.edu
Subject: Re: btokup() macro in sys/malloc.h
Cc: archie@whistle.com, current@FreeBSD.ORG
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
>>> Please do go ahead and update it.. the experts agree!
>>
>>I haven't seen any experts involved in this discussion yet. It's
>>probably after bedtime down there in oz.
>
>It's been discussed before and agreed upon.
There was only agreement long ago when the BSD4.4 /usr/src/admin/style
was converted to a man page.
Bruce
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Thu Jan 28 01:15:57 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id BAA12793
for freebsd-current-outgoing; Thu, 28 Jan 1999 01:15:57 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA12781
for <current@FreeBSD.ORG>; Thu, 28 Jan 1999 01:15:55 -0800 (PST)
(envelope-from dillon@apollo.backplane.com)
Received: (from dillon@localhost)
by apollo.backplane.com (8.9.2/8.9.1) id BAA02632;
Thu, 28 Jan 1999 01:15:54 -0800 (PST)
(envelope-from dillon)
Date: Thu, 28 Jan 1999 01:15:54 -0800 (PST)
From: Matthew Dillon <dillon@apollo.backplane.com>
Message-Id: <199901280915.BAA02632@apollo.backplane.com>
To: Julian Elischer <julian@whistle.com>
Cc: current@FreeBSD.ORG
Subject: Re: -Wall -Wcast-qual and SYSINIT
References: <Pine.BSF.4.05.9901280034480.304-100000@s204m82.isp.whistle.com>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
:On Thu, 28 Jan 1999, Matthew Dillon wrote:
:
:OK I understand now..
:theoretically I guess you should have two types of SYSINIT,
:however you are already not able to check the TYPE of the argument due to
:it being passed through the void form, so losing the 'const'-ness is not
:that much of a loss. The pragmetic answer may just be to 'cast' in the
:macro.
I'd kinda like to keep the const-ness because I can see device drivers
putting static structures in const ( i.e. read-only TEXT ) space and
would like to have the safety factor of knowing that they aren't actually
modified - not just not modified by the initialization routine, but also
not modified later on in the device driver code.
But I also want to eventually quiet the warning -- I agree that for
SYSINIT's, loosing const is not a huge issue. Quieting the warning
without fixing the problem with -Wcast-qual enabled is not pretty, though.
I think -Wcast-qual is pretty important if we intend to fix the volatile
conversion mess.
-Matt
Matthew Dillon
<dillon@backplane.com>
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Thu Jan 28 01:19:59 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id BAA13616
for freebsd-current-outgoing; Thu, 28 Jan 1999 01:19:59 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from aire.open.ac.uk (aire.open.ac.uk [137.108.40.21])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA13608
for <current@freebsd.org>; Thu, 28 Jan 1999 01:19:55 -0800 (PST)
(envelope-from A.M.Zanker@open.ac.uk)
Received: from mallard.open.ac.uk ([137.108.40.50] helo=mallard)
by aire.open.ac.uk with smtp (Exim 2.11 #1)
id 105nc8-0002eg-00
for current@freebsd.org; Thu, 28 Jan 1999 09:19:52 +0000
Message-Id: <4.1.19990128091540.00ad0680@aire.open.ac.uk>
X-Sender: mikez@aire.open.ac.uk
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.1
Date: Thu, 28 Jan 1999 09:19:52 +0000
To: current@FreeBSD.ORG
From: Mike Zanker <A.M.Zanker@open.ac.uk>
Subject: Celeron 333 kernel panic
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
Having just upgraded my motherboard/CPU to a BX chip set and Celeron 333 I
attempted to boot into my 3.0-STABLE system. However, as soon as the kernel
starts to boot I get
panic: cpu class not configured
and the machine reboots (and so on...)
Is this cpu supported?
Thanks,
Mike
--
Mike Zanker | Email: A.M.Zanker@open.ac.uk
Network and Computer Services Group | Tel : +44 1908 652726
The Open University | Fax : +44 1908 652193
Milton Keynes, UK | PGP public key available
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Thu Jan 28 01:22:25 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id BAA13962
for freebsd-current-outgoing; Thu, 28 Jan 1999 01:22:25 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA13955
for <current@FreeBSD.ORG>; Thu, 28 Jan 1999 01:22:24 -0800 (PST)
(envelope-from dillon@apollo.backplane.com)
Received: (from dillon@localhost)
by apollo.backplane.com (8.9.2/8.9.1) id BAA02697;
Thu, 28 Jan 1999 01:21:04 -0800 (PST)
(envelope-from dillon)
Date: Thu, 28 Jan 1999 01:21:04 -0800 (PST)
From: Matthew Dillon <dillon@apollo.backplane.com>
Message-Id: <199901280921.BAA02697@apollo.backplane.com>
To: Brian Feldman <green@unixhelp.org>
Cc: John Birrell <jb@cimlogic.com.au>, Nate Williams <nate@mt.sri.com>,
archie@whistle.com, wollman@khavrinen.lcs.mit.edu, current@FreeBSD.ORG
Subject: Re: btokup() macro in sys/malloc.h
References: <Pine.BSF.4.05.9901280334400.28225-100000@janus.syracuse.net>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
:In cases, -Wall is bogus anyway. Here's one:
:foo.c:89: warning: char format, void arg (arg 2)
: void *region;
: printf("mem open failed: %s\n", region);
:
:According to standards, a void pointer may be freely used instead of any
:other type of pointer, both as an lvalue and to assign to the other pointer.
:Printf(), hence, wouldn't see a difference (of course). Gcc should not
:complain about various void pointer things like this.
I think that's an appropriate warning... if you want to treat 'region'
as a char *, you have to cast it to one. The standards do not cover
GCC's automatic var-args checking for printf() and related routines
anyway. I consider them 'weird' cases myself... not really standard,
but helpful.
-Matt
Matthew Dillon
<dillon@backplane.com>
: Brian Feldman _ __ ___ ___ ___
: green@unixhelp.org _ __ ___ | _ ) __| \
: http://www.freebsd.org/ _ __ ___ ____ | _ \__ \ |) |
: FreeBSD: The Power to Serve! _ __ ___ ____ _____ |___/___/___/
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Thu Jan 28 01:30:28 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id BAA15318
for freebsd-current-outgoing; Thu, 28 Jan 1999 01:30:28 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA15289
for <current@FreeBSD.ORG>; Thu, 28 Jan 1999 01:30:24 -0800 (PST)
(envelope-from julian@whistle.com)
Received: (from daemon@localhost)
by alpo.whistle.com (8.8.5/8.8.5) id BAA25554;
Thu, 28 Jan 1999 01:21:47 -0800 (PST)
Received: from s204m82.isp.whistle.com(207.76.204.82)
via SMTP by alpo.whistle.com, id smtpdL25551; Thu Jan 28 09:21:40 1999
Date: Thu, 28 Jan 1999 01:21:34 -0800 (PST)
From: Julian Elischer <julian@whistle.com>
X-Sender: julian@s204m82.isp.whistle.com
To: Poul-Henning Kamp <phk@critter.freebsd.dk>
cc: Garrett Wollman <wollman@khavrinen.lcs.mit.edu>,
Archie Cobbs <archie@whistle.com>, current@FreeBSD.ORG
Subject: Re: btokup() macro in sys/malloc.h
In-Reply-To: <33685.917511275@critter.freebsd.dk>
Message-ID: <Pine.BSF.4.05.9901280116340.304-100000@s204m82.isp.whistle.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
On Thu, 28 Jan 1999, Poul-Henning Kamp wrote:
> In message <199901280222.VAA14212@khavrinen.lcs.mit.edu>, Garrett Wollman writes:
> ><<On Wed, 27 Jan 1999 18:00:54 -0800 (PST), Archie Cobbs <archie@whistle.com> said:
> >
> >> Please do go ahead and update it.. the experts agree!
> >
> >I haven't seen any experts involved in this discussion yet. It's
> >probably after bedtime down there in oz.
>
> It's been discussed before and agreed upon.
Actually it was discussed before and no agreement was reached..
The people with the biggest mouths yelled longest and loudest as usual
and the sensible people said. "It's like talking to 6
year olds", and gave up.
There are times when extra braced and parens stop bugs from being
introduced, due to the form of the code. There is no mention in style(9)
of "readability" being a criteria for braces, which is ludicrus.
julian
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Thu Jan 28 01:33:04 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id BAA15909
for freebsd-current-outgoing; Thu, 28 Jan 1999 01:33:04 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from nlsystems.com (nlsys.demon.co.uk [158.152.125.33])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA15901
for <current@freebsd.org>; Thu, 28 Jan 1999 01:33:02 -0800 (PST)
(envelope-from dfr@nlsystems.com)
Received: from localhost (dfr@localhost)
by nlsystems.com (8.9.1/8.8.5) with SMTP id JAA00871;
Thu, 28 Jan 1999 09:35:34 GMT
Date: Thu, 28 Jan 1999 09:35:34 +0000 (GMT)
From: Doug Rabson <dfr@nlsystems.com>
To: Matthew Dillon <dillon@apollo.backplane.com>
cc: current@FreeBSD.ORG
Subject: Re: bug in nfs_access()
In-Reply-To: <199901272244.OAA64912@apollo.backplane.com>
Message-ID: <Pine.BSF.4.01.9901280935030.95594-100000@herring.nlsystems.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
On Wed, 27 Jan 1999, Matthew Dillon wrote:
> bug in nfs_access(). nfs/nfs_vnops.c, line 414 or so.
>
> Fixed!
>
> This is a nasty one. I'm surprised it hasn't caused grief before
I can't see the problem in this code. What was the bug?
--
Doug Rabson Mail: dfr@nlsystems.com
Nonlinear Systems Ltd. Phone: +44 181 442 9037
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Thu Jan 28 01:35:49 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id BAA16216
for freebsd-current-outgoing; Thu, 28 Jan 1999 01:35:49 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA16210
for <current@FreeBSD.ORG>; Thu, 28 Jan 1999 01:35:48 -0800 (PST)
(envelope-from dillon@apollo.backplane.com)
Received: (from dillon@localhost)
by apollo.backplane.com (8.9.2/8.9.1) id BAA02961;
Thu, 28 Jan 1999 01:35:43 -0800 (PST)
(envelope-from dillon)
Date: Thu, 28 Jan 1999 01:35:43 -0800 (PST)
From: Matthew Dillon <dillon@apollo.backplane.com>
Message-Id: <199901280935.BAA02961@apollo.backplane.com>
To: Doug Rabson <dfr@nlsystems.com>
Cc: current@FreeBSD.ORG
Subject: Re: bug in nfs_access()
References: <Pine.BSF.4.01.9901280935030.95594-100000@herring.nlsystems.com>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
:
:On Wed, 27 Jan 1999, Matthew Dillon wrote:
:
:> bug in nfs_access(). nfs/nfs_vnops.c, line 414 or so.
:>
:> Fixed!
:>
:> This is a nasty one. I'm surprised it hasn't caused grief before
:
:I can't see the problem in this code. What was the bug?
--- nfs_vnops.c 1999/01/27 22:45:13 1.118
+++ nfs_vnops.c 1999/01/27 22:45:49 1.119
@@ -34,7 +34,7 @@
* SUCH DAMAGE.
*
* @(#)nfs_vnops.c 8.16 (Berkeley) 5/27/95
- * $Id: nfs_vnops.c,v 1.118 1999/01/27 22:45:13 dillon Exp $
+ * $Id: nfs_vnops.c,v 1.119 1999/01/27 22:45:49 dillon Exp $
*/
@@ -411,7 +411,7 @@
aiov.iov_len = auio.uio_resid = NFS_DIRBLKSIZ;
error = nfs_readdirrpc(vp, &auio, ap->a_cred);
free(bp, M_TEMP);
- } else if (vp->v_type = VLNK)
+ } else if (vp->v_type == VLNK)
error = nfs_readlinkrpc(vp, &auio, ap->a_cred);
else
error = EACCES;
I believe the assignment to VLNK is incorrect and that it is supposed
to be a comparison against VLNK instead.
-Matt
Matthew Dillon
<dillon@backplane.com>
:--
:Doug Rabson Mail: dfr@nlsystems.com
:Nonlinear Systems Ltd. Phone: +44 181 442 9037
:
:
:
:To Unsubscribe: send mail to majordomo@FreeBSD.org
:with "unsubscribe freebsd-current" in the body of the message
:
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Thu Jan 28 01:36:39 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id BAA16448
for freebsd-current-outgoing; Thu, 28 Jan 1999 01:36:39 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from top.worldcontrol.com (snblitz.sc.scruznet.com [165.227.132.84])
by hub.freebsd.org (8.8.8/8.8.8) with SMTP id BAA16442
for <freebsd-current@freebsd.org>; Thu, 28 Jan 1999 01:36:37 -0800 (PST)
(envelope-from brian@worldcontrol.com)
From: brian@worldcontrol.com
Received: (qmail 380 invoked by uid 100); 28 Jan 1999 09:37:44 -0000
Date: Thu, 28 Jan 1999 01:37:44 -0800
To: freebsd-current@FreeBSD.ORG
Subject: pcm0: thumbs up,down,up
Message-ID: <19990128013744.A332@top.worldcontrol.com>
Mail-Followup-To: freebsd-current@freebsd.org
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.95.1i
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
pcm is again working correctly with the Yamaha YMF715 based sound system
of my laptop.
It had been working fine up till shortly before secure/libcrypt broke on
-current.
Then I had an array of strange problems.
After testing and logging the various failures with cat, mpg123,
xanim, rvplayer, and mtv threaded and unthreaded,
I rebuilt the kernel with voxware and found that everything worked.
I then rebuilt the kernel with pcm again and found that everything
worked too.
Well not exactly everything works. They each then and continue today to
exhibit their unique little toubles.
(volume doesn't work right under pcm (I have a patch), some
versions of mtv audio don't work quite right via voxware, ...)
--
Brian Litzinger <brian@litzinger.com>
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Thu Jan 28 01:39:13 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id BAA16667
for freebsd-current-outgoing; Thu, 28 Jan 1999 01:39:13 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.26.10.9])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA16662
for <current@FreeBSD.ORG>; Thu, 28 Jan 1999 01:39:10 -0800 (PST)
(envelope-from bde@godzilla.zeta.org.au)
Received: (from bde@localhost)
by godzilla.zeta.org.au (8.8.7/8.8.7) id UAA30919;
Thu, 28 Jan 1999 20:39:03 +1100
Date: Thu, 28 Jan 1999 20:39:03 +1100
From: Bruce Evans <bde@zeta.org.au>
Message-Id: <199901280939.UAA30919@godzilla.zeta.org.au>
To: bde@zeta.org.au, luigi@labinfo.iet.unipi.it
Subject: Re: indent(1) and style(9) (was: btokup() macro in sys/malloc.h)
Cc: current@FreeBSD.ORG, grog@lemis.com, peter.jeremy@auss2.alcatel.com.au
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
>not speaking about vinum, but to me, the indentation of 8 char and
>line length of 80 chars are almost mutually exclusive.
>
>See e.g. tcp_input.c ip_input.c and many network device drivers as
>an example -- basically all places where, for efficiency reasons,
>the code tries to expand in-line various block, the depth of
>indentation pushes everything to the right end leaving only 20-30
>useful chars per line.
See the Linux style guide (linux/Documentation/CodingStyle) for
strong opinions about this: "if you need more than 3 levels of
indentation, you're screwed anyway, and should fix your program".
I almost agree.
Bruce
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Thu Jan 28 01:44:09 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id BAA17290
for freebsd-current-outgoing; Thu, 28 Jan 1999 01:44:09 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from nlsystems.com (nlsys.demon.co.uk [158.152.125.33])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA17274
for <current@freebsd.org>; Thu, 28 Jan 1999 01:44:04 -0800 (PST)
(envelope-from dfr@nlsystems.com)
Received: from localhost (dfr@localhost)
by nlsystems.com (8.9.1/8.8.5) with SMTP id JAA00892;
Thu, 28 Jan 1999 09:46:37 GMT
Date: Thu, 28 Jan 1999 09:46:37 +0000 (GMT)
From: Doug Rabson <dfr@nlsystems.com>
To: Matthew Dillon <dillon@apollo.backplane.com>
cc: current@FreeBSD.ORG
Subject: Re: bug in nfs_access()
In-Reply-To: <199901272244.OAA64912@apollo.backplane.com>
Message-ID: <Pine.BSF.4.01.9901280945560.95594-100000@herring.nlsystems.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
On Wed, 27 Jan 1999, Matthew Dillon wrote:
> bug in nfs_access(). nfs/nfs_vnops.c, line 414 or so.
>
> Fixed!
>
> This is a nasty one. I'm surprised it hasn't caused grief before
Never mind, I just read the commit message and managed to actually see the
mistake. I hate those ones...
--
Doug Rabson Mail: dfr@nlsystems.com
Nonlinear Systems Ltd. Phone: +44 181 442 9037
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Thu Jan 28 01:46:33 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id BAA17620
for freebsd-current-outgoing; Thu, 28 Jan 1999 01:46:33 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from labinfo.iet.unipi.it (labinfo.iet.unipi.it [131.114.9.5])
by hub.freebsd.org (8.8.8/8.8.8) with SMTP id BAA17611
for <current@FreeBSD.ORG>; Thu, 28 Jan 1999 01:46:30 -0800 (PST)
(envelope-from luigi@labinfo.iet.unipi.it)
Received: from localhost (luigi@localhost) by labinfo.iet.unipi.it (8.6.5/8.6.5) id IAA08539; Thu, 28 Jan 1999 08:35:34 +0100
From: Luigi Rizzo <luigi@labinfo.iet.unipi.it>
Message-Id: <199901280735.IAA08539@labinfo.iet.unipi.it>
Subject: Re: indent(1) and style(9) (was: btokup() macro in sys/malloc.h)
To: bde@zeta.org.au (Bruce Evans)
Date: Thu, 28 Jan 1999 08:35:33 +0100 (MET)
Cc: bde@zeta.org.au, current@FreeBSD.ORG, grog@lemis.com,
peter.jeremy@auss2.alcatel.com.au
In-Reply-To: <199901280939.UAA30919@godzilla.zeta.org.au> from "Bruce Evans" at Jan 28, 99 08:38:44 pm
X-Mailer: ELM [version 2.4 PL23]
Content-Type: text
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
> >an example -- basically all places where, for efficiency reasons,
> >the code tries to expand in-line various block, the depth of
> >indentation pushes everything to the right end leaving only 20-30
> >useful chars per line.
>
> See the Linux style guide (linux/Documentation/CodingStyle) for
> strong opinions about this: "if you need more than 3 levels of
> indentation, you're screwed anyway, and should fix your program".
>
> I almost agree.
in userland, probably me too. In the kernel, i am not so sure.
luigi
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Thu Jan 28 01:47:25 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id BAA17733
for freebsd-current-outgoing; Thu, 28 Jan 1999 01:47:25 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from nlsystems.com (nlsys.demon.co.uk [158.152.125.33])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA17710
for <current@FreeBSD.ORG>; Thu, 28 Jan 1999 01:47:17 -0800 (PST)
(envelope-from dfr@nlsystems.com)
Received: from localhost (dfr@localhost)
by nlsystems.com (8.9.1/8.8.5) with SMTP id JAA00971;
Thu, 28 Jan 1999 09:49:48 GMT
Date: Thu, 28 Jan 1999 09:49:48 +0000 (GMT)
From: Doug Rabson <dfr@nlsystems.com>
To: Matthew Dillon <dillon@apollo.backplane.com>
cc: current@FreeBSD.ORG
Subject: Re: bug in nfs_access()
In-Reply-To: <199901280935.BAA02961@apollo.backplane.com>
Message-ID: <Pine.BSF.4.01.9901280948030.95594-100000@herring.nlsystems.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
On Thu, 28 Jan 1999, Matthew Dillon wrote:
> :
> :On Wed, 27 Jan 1999, Matthew Dillon wrote:
> :
> :> bug in nfs_access(). nfs/nfs_vnops.c, line 414 or so.
> :>
> :> Fixed!
> :>
> :> This is a nasty one. I'm surprised it hasn't caused grief before
> :
> :I can't see the problem in this code. What was the bug?
>
>
> --- nfs_vnops.c 1999/01/27 22:45:13 1.118
> +++ nfs_vnops.c 1999/01/27 22:45:49 1.119
> @@ -34,7 +34,7 @@
> * SUCH DAMAGE.
> *
> * @(#)nfs_vnops.c 8.16 (Berkeley) 5/27/95
> - * $Id: nfs_vnops.c,v 1.118 1999/01/27 22:45:13 dillon Exp $
> + * $Id: nfs_vnops.c,v 1.119 1999/01/27 22:45:49 dillon Exp $
> */
>
>
> @@ -411,7 +411,7 @@
> aiov.iov_len = auio.uio_resid = NFS_DIRBLKSIZ;
> error = nfs_readdirrpc(vp, &auio, ap->a_cred);
> free(bp, M_TEMP);
> - } else if (vp->v_type = VLNK)
> + } else if (vp->v_type == VLNK)
> error = nfs_readlinkrpc(vp, &auio, ap->a_cred);
> else
> error = EACCES;
>
>
> I believe the assignment to VLNK is incorrect and that it is supposed
> to be a comparison against VLNK instead.
You are absolutely correct (I must still be half asleep). I guess that
attempts to read from other filetypes didn't reach here or generated calls
to the server which returned errors.
--
Doug Rabson Mail: dfr@nlsystems.com
Nonlinear Systems Ltd. Phone: +44 181 442 9037
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Thu Jan 28 01:51:17 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id BAA18164
for freebsd-current-outgoing; Thu, 28 Jan 1999 01:51:17 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from allegro.lemis.com (allegro.lemis.com [192.109.197.134])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA18159
for <current@FreeBSD.ORG>; Thu, 28 Jan 1999 01:51:13 -0800 (PST)
(envelope-from grog@freebie.lemis.com)
Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137])
by allegro.lemis.com (8.9.1/8.9.0) with ESMTP id UAA24323;
Thu, 28 Jan 1999 20:21:07 +1030 (CST)
Received: (from grog@localhost)
by freebie.lemis.com (8.9.2/8.9.0) id UAA09037;
Thu, 28 Jan 1999 20:21:06 +1030 (CST)
Date: Thu, 28 Jan 1999 20:21:06 +1030
From: Greg Lehey <grog@lemis.com>
To: Bruce Evans <bde@zeta.org.au>
Cc: luigi@labinfo.iet.unipi.it, current@FreeBSD.ORG,
peter.jeremy@auss2.alcatel.com.au
Subject: Nesting levels (was: indent(1) and style(9) (was: btokup() macro in sys/malloc.h))
Message-ID: <19990128202106.I8473@freebie.lemis.com>
References: <199901280939.UAA30919@godzilla.zeta.org.au>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.95.1i
In-Reply-To: <199901280939.UAA30919@godzilla.zeta.org.au>; from Bruce Evans on Thu, Jan 28, 1999 at 08:39:03PM +1100
WWW-Home-Page: http://www.lemis.com/~grog
Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia
Phone: +61-8-8388-8286
Fax: +61-8-8388-8725
Mobile: +61-41-739-7062
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
On Thursday, 28 January 1999 at 20:39:03 +1100, Bruce Evans wrote:
>> not speaking about vinum, but to me, the indentation of 8 char and
>> line length of 80 chars are almost mutually exclusive.
>>
>> See e.g. tcp_input.c ip_input.c and many network device drivers as
>> an example -- basically all places where, for efficiency reasons,
>> the code tries to expand in-line various block, the depth of
>> indentation pushes everything to the right end leaving only 20-30
>> useful chars per line.
>
> See the Linux style guide
Wave a red rag at a bull?
> (linux/Documentation/CodingStyle) for strong opinions about this:
> "if you need more than 3 levels of indentation, you're screwed
> anyway, and should fix your program".
I think this is the bottom line. If you're using 8 character indents,
then yes, you're screwed. If you're using Microsoft and trying to
write clever shell scripts, you're screwed too. Your tools limit what
you can do. I believe that, in the matter of indentation, style(9)
limits legibility to a point where you really are screwed if you have
multiple indentation. But it's not because the code's bad.
Greg
--
See complete headers for address, home page and phone numbers
finger grog@lemis.com for PGP public key
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Thu Jan 28 01:53:24 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id BAA18679
for freebsd-current-outgoing; Thu, 28 Jan 1999 01:53:24 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from caladan.tdx.co.uk (caladan.tdx.co.uk [195.188.177.4])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA18672
for <current@FreeBSD.ORG>; Thu, 28 Jan 1999 01:53:22 -0800 (PST)
(envelope-from kpielorz@tdx.co.uk)
Received: from tdx.co.uk (lorca-tx.tdx.co.uk [195.188.177.242])
by caladan.tdx.co.uk (8.9.2/8.9.2) with ESMTP id JAA90840;
Thu, 28 Jan 1999 09:53:17 GMT
Message-ID: <36B0338C.B6B5D825@tdx.co.uk>
Date: Thu, 28 Jan 1999 09:53:16 +0000
From: Karl Pielorz <kpielorz@tdx.co.uk>
Organization: TDX - The Digital eXchange
X-Mailer: Mozilla 4.5 [en] (WinNT; I)
X-Accept-Language: en
MIME-Version: 1.0
To: Mike Zanker <A.M.Zanker@open.ac.uk>
CC: current@FreeBSD.ORG
Subject: Re: Celeron 333 kernel panic
References: <4.1.19990128091540.00ad0680@aire.open.ac.uk>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
Mike Zanker wrote:
>
> Having just upgraded my motherboard/CPU to a BX chip set and Celeron 333 I
> attempted to boot into my 3.0-STABLE system. However, as soon as the kernel
> starts to boot I get
>
> panic: cpu class not configured
>
> and the machine reboots (and so on...)
>
> Is this cpu supported?
AFAIK it is support - are you sure you had
cpu "I686_CPU"
In your kernel config?
-Kp
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Thu Jan 28 01:53:34 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id BAA18709
for freebsd-current-outgoing; Thu, 28 Jan 1999 01:53:34 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from sis.bytes.gen.nz ([203.97.44.56])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA18692
for <current@FreeBSD.ORG>; Thu, 28 Jan 1999 01:53:25 -0800 (PST)
(envelope-from phillip@sis.bytes.gen.nz)
Received: from localhost (phillip@localhost)
by sis.bytes.gen.nz (8.9.2/8.9.2) with ESMTP id WAA54159;
Thu, 28 Jan 1999 22:52:51 +1300 (NZDT)
(envelope-from phillip@sis.bytes.gen.nz)
Date: Thu, 28 Jan 1999 22:52:50 +1300 (NZDT)
From: Phillip Hardy <phillip@sis.bytes.gen.nz>
X-Sender: phillip@sis
To: Mike Zanker <A.M.Zanker@open.ac.uk>
cc: current@FreeBSD.ORG
Subject: Re: Celeron 333 kernel panic
In-Reply-To: <4.1.19990128091540.00ad0680@aire.open.ac.uk>
Message-ID: <Pine.BSF.4.05.9901282249360.52708-100000@sis>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
On Thu, 28 Jan 1999, Mike Zanker wrote:
> Having just upgraded my motherboard/CPU to a BX chip set and Celeron 333 I
> attempted to boot into my 3.0-STABLE system. However, as soon as the kernel
> starts to boot I get
>
> panic: cpu class not configured
>
> and the machine reboots (and so on...)
>
> Is this cpu supported?
Hi Did you Come from a Non Pentium II motherboard?
have you tryed Recompileing your kernel for the 686 Class CPU's?
if not then that is more likely to be the problem
--
Phillip W. Hardy phillip@sis.bytes.gen.nz
Secure Infomation Servics Software/Hardware Debugger
"FreeBSD the Choice of a GNU Generation" - www.freebsd.org
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Thu Jan 28 02:03:42 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id CAA20290
for freebsd-current-outgoing; Thu, 28 Jan 1999 02:03:42 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.26.10.9])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA20266
for <current@FreeBSD.ORG>; Thu, 28 Jan 1999 02:03:22 -0800 (PST)
(envelope-from bde@godzilla.zeta.org.au)
Received: (from bde@localhost)
by godzilla.zeta.org.au (8.8.7/8.8.7) id VAA00218;
Thu, 28 Jan 1999 21:03:12 +1100
Date: Thu, 28 Jan 1999 21:03:12 +1100
From: Bruce Evans <bde@zeta.org.au>
Message-Id: <199901281003.VAA00218@godzilla.zeta.org.au>
To: green@unixhelp.org, jb@cimlogic.com.au
Subject: Re: btokup() macro in sys/malloc.h
Cc: archie@whistle.com, current@FreeBSD.ORG, nate@mt.sri.com,
wollman@khavrinen.lcs.mit.edu
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
>In cases, -Wall is bogus anyway. Here's one:
>foo.c:89: warning: char format, void arg (arg 2)
> void *region;
> printf("mem open failed: %s\n", region);
Yes, it should say "warning: char * format, void * arg (arg 2)".
>According to standards, a void pointer may be freely used instead of any
>other type of pointer, both as an lvalue and to assign to the other pointer.
There are no lvalues or assigns to another pointer here. The code does
what you want (if `region' is a char * represented as a void *) only
because void * has the same representation as char *.
Bruce
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Thu Jan 28 02:11:14 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id CAA21211
for freebsd-current-outgoing; Thu, 28 Jan 1999 02:11:14 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from darkstar.psa.at (darkstar.psa.at [194.152.163.137])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA21203
for <current@freebsd.org>; Thu, 28 Jan 1999 02:11:08 -0800 (PST)
(envelope-from root@psa.at)
Received: from uvo-15.univie.ac.at ([131.130.230.15] helo=entropy.quake.at)
by darkstar.psa.at with esmtp (Exim 2.05 #1)
id 105od2-0004E2-00; Thu, 28 Jan 1999 11:24:53 +0100
Received: from localhost ([127.0.0.1])
by entropy.quake.at with esmtp (Exim 2.10 #2)
id 105oIt-00004I-00; Thu, 28 Jan 1999 11:04:04 +0100
Date: Thu, 28 Jan 1999 11:04:03 +0100 (CET)
From: Alexander Sanda <as@psa.at>
X-Sender: root@darkstar.vmx
To: Brian Somers <brian@Awfulhak.org>
cc: current@FreeBSD.ORG
Subject: Re: PPP (userland) troubles ?
In-Reply-To: <199901270059.AAA15871@keep.lan.Awfulhak.org>
Message-ID: <Pine.BSF.4.05.9901281049140.244-100000@darkstar.vmx>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
On Wed, 27 Jan 1999, Brian Somers wrote:
> To find out if this is the problem, can you try connecting
> interactively. You should see the same delay. You can then try
> again, but during the delay, pressing return a few times at the
> prompt should wake ppp up. Is this happening ?
Well, I tried and didn't find any relationship between pressing return
and triggering the wakeup. This is someway hard to find, since ppp wakes
up automagically a few couple of seconds after the connection has been
established.
However: I noticed a real big commit to ppp last night, so I decided to
wipe out /usr/src/usr.sbin/ppp + /usr/src/sys completely, recvsup'd,
recompiled kernel, ppp and tested again - problems are gone.
So there are now 2 possibilities for this problem:
a) I was out of sync :(
b) Someone fixed ppp
--
# /AS/ http://privat.schlund.de/entropy/ #
# #
# XX has detected, that your mouse cursor has changed position. Please #
# restart XX, so it can be updated. -- From The Gimp manual #
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Thu Jan 28 02:13:39 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id CAA21451
for freebsd-current-outgoing; Thu, 28 Jan 1999 02:13:39 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from aire.open.ac.uk (aire.open.ac.uk [137.108.40.21])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA21431
for <current@freebsd.org>; Thu, 28 Jan 1999 02:13:27 -0800 (PST)
(envelope-from A.M.Zanker@open.ac.uk)
Received: from mallard.open.ac.uk ([137.108.40.50] helo=mallard)
by aire.open.ac.uk with smtp (Exim 2.11 #1)
id 105oRo-0002j8-00
for current@FreeBSD.ORG; Thu, 28 Jan 1999 10:13:17 +0000
Message-Id: <4.1.19990128101137.04065170@aire.open.ac.uk>
X-Sender: mikez@aire.open.ac.uk
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.1
Date: Thu, 28 Jan 1999 10:13:16 +0000
To: current@FreeBSD.ORG
From: Mike Zanker <A.M.Zanker@open.ac.uk>
Subject: Re: Celeron 333 kernel panic
In-Reply-To: <36B0338C.B6B5D825@tdx.co.uk>
References: <4.1.19990128091540.00ad0680@aire.open.ac.uk>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
At 09:53 28/01/99 , Karl Pielorz wrote:
>AFAIK it is support - are you sure you had
>
>cpu "I686_CPU"
>
>In your kernel config?
Thanks, this is the problem - I've only got I586_CPU in my config. I *knew*
I should have kept a GENERIC kernel around!
Thanks to all who answered,
Mike
--
Mike Zanker | Email: A.M.Zanker@open.ac.uk
Network and Computer Services Group | Tel : +44 1908 652726
The Open University | Fax : +44 1908 652193
Milton Keynes, UK | PGP public key available
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Thu Jan 28 02:18:27 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id CAA22159
for freebsd-current-outgoing; Thu, 28 Jan 1999 02:18:27 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from hda.hda.com (hda-bicnet.bicnet.net [209.244.238.132] (may be forged))
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA22151
for <current@FreeBSD.ORG>; Thu, 28 Jan 1999 02:18:22 -0800 (PST)
(envelope-from dufault@hda.hda.com)
Received: (from dufault@localhost)
by hda.hda.com (8.8.5/8.8.5) id FAA10811;
Thu, 28 Jan 1999 05:12:25 -0500 (EST)
From: Peter Dufault <dufault@hda.com>
Message-Id: <199901281012.FAA10811@hda.hda.com>
Subject: Re: btokup() macro in sys/malloc.h
In-Reply-To: <199901280629.XAA26798@mt.sri.com> from Nate Williams at "Jan 27, 99 11:29:37 pm"
To: nate@mt.sri.com (Nate Williams)
Date: Thu, 28 Jan 1999 05:12:24 -0500 (EST)
Cc: dillon@apollo.backplane.com, nate@mt.sri.com, archie@whistle.com,
wollman@khavrinen.lcs.mit.edu, current@FreeBSD.ORG
X-Mailer: ELM [version 2.4ME+ PL25 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
> A warning is just that. It's not an error, so don't treat it like one.
I use different productions to enable different warnings on code with
different histories. For one thing, new revs of the compiler will
otherwise cause trouble when the warning behavior changes.
I also use -Werror. Eliminating warnings is almost pointless without
this. And yeah, I have a NO_WERROR flag for when I'm in a rush.
I know -Werror is the eventual goal.
So I disagree with Nate about ignoring warnings you've enabled -
it is too easy to ignore a new problem. I agree with him that
gratuitous casts and similar fixes during damn-the-torpedos
mass conversions of large bodies of code are bad in that they
can effectively hide latent problems more deeply than they were
hidden before such a conversion.
So IMHO:
Eliminating warnings is good;
Any mechanistic change to eliminate warnings
that can mask problems can not be used.
Peter
--
Peter Dufault (dufault@hda.com) Realtime development, Machine control,
HD Associates, Inc. Safety critical systems, Agency approval
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Thu Jan 28 02:34:09 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id CAA23812
for freebsd-current-outgoing; Thu, 28 Jan 1999 02:34:09 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from peach.ocn.ne.jp (peach.ocn.ne.jp [210.145.254.87])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA23805
for <freebsd-current@FreeBSD.ORG>; Thu, 28 Jan 1999 02:34:07 -0800 (PST)
(envelope-from dcs@newsguy.com)
Received: from newsguy.com by peach.ocn.ne.jp (8.9.1a/OCN) id TAA29767; Thu, 28 Jan 1999 19:33:53 +0900 (JST)
Message-ID: <36AFF021.509E686B@newsguy.com>
Date: Thu, 28 Jan 1999 14:05:37 +0900
From: "Daniel C. Sobral" <dcs@newsguy.com>
X-Mailer: Mozilla 4.5 [en] (Win98; I)
X-Accept-Language: pt-BR,ja
MIME-Version: 1.0
To: Chuck Robey <chuckr@mat.net>
CC: Nate Williams <nate@mt.sri.com>,
Garrett Wollman <wollman@khavrinen.lcs.mit.edu>,
freebsd-current@FreeBSD.ORG
Subject: Re: removing f2c from base distribution
References: <Pine.BSF.4.05.9901272330540.375-100000@picnic.mat.net>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
Chuck Robey wrote:
>
> I'm not sure if this argument is worth pushing anymore, because
> FreeBSD's stability and usefulness has become much more well known, but
> it did contribute at some point, and I think that is the idea that
> Daniel was trying to convey.
>
> Right?
Me? No... Maybe Garret... :-)
--
Daniel C. Sobral (8-DCS)
dcs@newsguy.com
If you sell your soul to the Devil and all you get is an MCSE from
it, you haven't gotten market rate.
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Thu Jan 28 02:40:48 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id CAA24376
for freebsd-current-outgoing; Thu, 28 Jan 1999 02:40:48 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.26.10.9])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA24369
for <current@FreeBSD.ORG>; Thu, 28 Jan 1999 02:40:44 -0800 (PST)
(envelope-from bde@godzilla.zeta.org.au)
Received: (from bde@localhost)
by godzilla.zeta.org.au (8.8.7/8.8.7) id VAA03357;
Thu, 28 Jan 1999 21:40:39 +1100
Date: Thu, 28 Jan 1999 21:40:39 +1100
From: Bruce Evans <bde@zeta.org.au>
Message-Id: <199901281040.VAA03357@godzilla.zeta.org.au>
To: dillon@apollo.backplane.com, julian@whistle.com
Subject: Re: -Wall -Wcast-qual and SYSINIT
Cc: current@FreeBSD.ORG
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
>>From my uderstanding, SYSINIT should always point to a function with a
>CONST argument because the argument is fixed as a constant at link/compile
>time.
>
>what functions don't expect a const? and why not?
Probably most.
>or am I mising something?
Only the initial value of the arg is determined at link/compile time.
The arg can point to non-const storage, and it is not unreasonable to
put the initial value in non-const storage so that it can be frobbed.
Linker sets sometimes get frobbed. I once made execsw_set const and
had to change it back after it started causing warnings.
Bruce
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Thu Jan 28 02:43:49 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id CAA24551
for freebsd-current-outgoing; Thu, 28 Jan 1999 02:43:49 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from hda.hda.com (hda-bicnet.bicnet.net [209.244.238.132] (may be forged))
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA24540
for <freebsd-current@FreeBSD.ORG>; Thu, 28 Jan 1999 02:43:46 -0800 (PST)
(envelope-from dufault@hda.hda.com)
Received: (from dufault@localhost)
by hda.hda.com (8.8.5/8.8.5) id FAA10916;
Thu, 28 Jan 1999 05:37:18 -0500 (EST)
From: Peter Dufault <dufault@hda.com>
Message-Id: <199901281037.FAA10916@hda.hda.com>
Subject: Re: Naming files in sys/kern
In-Reply-To: <199901280228.VAA14247@khavrinen.lcs.mit.edu> from Garrett Wollman at "Jan 27, 99 09:28:47 pm"
To: wollman@khavrinen.lcs.mit.edu (Garrett Wollman)
Date: Thu, 28 Jan 1999 05:37:18 -0500 (EST)
Cc: robert@cyrus.watson.org, freebsd-current@FreeBSD.ORG
X-Mailer: ELM [version 2.4ME+ PL25 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
> <<On Wed, 27 Jan 1999 18:30:15 -0500 (EST), Robert Watson <robert@cyrus.watson.org> said:
>
> > It's not clear to me, when thinking of introducing a new file (say, for
> > auditing support :), what I should name it. Would it be kern_audit.c or
> > sys_audit.c?
>
> Depends on what it is auditing. If it only auditing the basic I/O
> operations, then it would go in sys_*.c. If it's a more general
> kernel facility, then it goes in kern_*.c.
>
> > Or, if it is POSIX.1e, would it go into a /usr/src/sys/posix1e
> > directory as the posix4 realtime stuff did (assuming that support
> > for additional features from that posix draft were going to be
> > forthcoming)?
>
> Giving the unhelpful tendency of Project 1003 to renumber its
> standards after-the-fact (or fold them into the main 1003.1 document),
> I would suggest against using committee identifiers like this.
This is posix4 due to my stupidity - I bought the O'Reilly "posix.4"
book and changed the name to that even though I used to know
better.
I started with this in its own directory since it is supposed to
be able to be enabled/disabled en masse via feature test macros,
and because I wanted to keep all the posixy stuff in one place with
calls out into the regular BSD kernel. Since the name is wrong,
I think right thing to do now is make this directory something that
means "posix_subsystem" and put similar chunks that follow similar
rules there. That keeps the code associated with twisty standardized
feature test macros in one place.
Peter
--
Peter Dufault (dufault@hda.com) Realtime development, Machine control,
HD Associates, Inc. Safety critical systems, Agency approval
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Thu Jan 28 02:51:39 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id CAA25370
for freebsd-current-outgoing; Thu, 28 Jan 1999 02:51:39 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from awfulhak.org (awfulhak.force9.co.uk [195.166.136.63])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA25359
for <current@FreeBSD.ORG>; Thu, 28 Jan 1999 02:51:36 -0800 (PST)
(envelope-from brian@Awfulhak.org)
Received: from keep.lan.Awfulhak.org (brian@keep.lan.Awfulhak.org [172.16.0.8])
by awfulhak.org (8.8.8/8.8.8) with ESMTP id KAA05938;
Thu, 28 Jan 1999 10:51:18 GMT
(envelope-from brian@Awfulhak.org)
Received: from keep.lan.Awfulhak.org (brian@localhost [127.0.0.1])
by keep.lan.Awfulhak.org (8.9.2/8.9.2) with ESMTP id KAA93830;
Thu, 28 Jan 1999 10:29:32 GMT
(envelope-from brian@keep.lan.Awfulhak.org)
Message-Id: <199901281029.KAA93830@keep.lan.Awfulhak.org>
X-Mailer: exmh version 2.0.2 2/24/98
To: Bruce Evans <bde@zeta.org.au>
cc: grog@lemis.com, current@FreeBSD.ORG, peter.jeremy@auss2.alcatel.com.au
Subject: Re: indent(1) and style(9) (was: btokup() macro in sys/malloc.h)
In-reply-to: Your message of "Thu, 28 Jan 1999 19:19:12 +1100."
<199901280819.TAA23954@godzilla.zeta.org.au>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Thu, 28 Jan 1999 10:29:32 +0000
From: Brian Somers <brian@Awfulhak.org>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
> They have an indentation of 4
> instead of 8,
[.....]
8 spaces is almost always *way* too much if a maximum of 80 columns
is expected. IMHO, the requirement should be to either use TABs and
only TABs or else two or more spaces.
Either way, perhaps it's time someone fixed indent(1) so that it
applies style(9)...
> Bruce
--
Brian <brian@Awfulhak.org> <brian@FreeBSD.org> <brian@OpenBSD.org>
<http://www.Awfulhak.org>
Don't _EVER_ lose your sense of humour !
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Thu Jan 28 02:51:57 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id CAA25459
for freebsd-current-outgoing; Thu, 28 Jan 1999 02:51:57 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from awfulhak.org (awfulhak.force9.co.uk [195.166.136.63])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA25449
for <current@FreeBSD.ORG>; Thu, 28 Jan 1999 02:51:53 -0800 (PST)
(envelope-from brian@Awfulhak.org)
Received: from keep.lan.Awfulhak.org (brian@keep.lan.Awfulhak.org [172.16.0.8])
by awfulhak.org (8.8.8/8.8.8) with ESMTP id KAA05941;
Thu, 28 Jan 1999 10:51:24 GMT
(envelope-from brian@Awfulhak.org)
Received: from keep.lan.Awfulhak.org (brian@localhost [127.0.0.1])
by keep.lan.Awfulhak.org (8.9.2/8.9.2) with ESMTP id KAA93866;
Thu, 28 Jan 1999 10:35:23 GMT
(envelope-from brian@keep.lan.Awfulhak.org)
Message-Id: <199901281035.KAA93866@keep.lan.Awfulhak.org>
X-Mailer: exmh version 2.0.2 2/24/98
To: Bruce Evans <bde@zeta.org.au>
cc: luigi@labinfo.iet.unipi.it, current@FreeBSD.ORG, grog@lemis.com,
peter.jeremy@auss2.alcatel.com.au
Subject: Re: indent(1) and style(9) (was: btokup() macro in sys/malloc.h)
In-reply-to: Your message of "Thu, 28 Jan 1999 20:39:03 +1100."
<199901280939.UAA30919@godzilla.zeta.org.au>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Thu, 28 Jan 1999 10:35:23 +0000
From: Brian Somers <brian@Awfulhak.org>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
> See the Linux style guide (linux/Documentation/CodingStyle) for
Looks like an oxymoron to me.
> Bruce
--
Brian <brian@Awfulhak.org> <brian@FreeBSD.org> <brian@OpenBSD.org>
<http://www.Awfulhak.org>
Don't _EVER_ lose your sense of humour !
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Thu Jan 28 02:51:58 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id CAA25475
for freebsd-current-outgoing; Thu, 28 Jan 1999 02:51:58 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from awfulhak.org (awfulhak.force9.co.uk [195.166.136.63])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA25452
for <current@FreeBSD.ORG>; Thu, 28 Jan 1999 02:51:54 -0800 (PST)
(envelope-from brian@Awfulhak.org)
Received: from keep.lan.Awfulhak.org (brian@keep.lan.Awfulhak.org [172.16.0.8])
by awfulhak.org (8.8.8/8.8.8) with ESMTP id KAA05944;
Thu, 28 Jan 1999 10:51:30 GMT
(envelope-from brian@Awfulhak.org)
Received: from keep.lan.Awfulhak.org (brian@localhost [127.0.0.1])
by keep.lan.Awfulhak.org (8.9.2/8.9.2) with ESMTP id KAA93851;
Thu, 28 Jan 1999 10:34:32 GMT
(envelope-from brian@keep.lan.Awfulhak.org)
Message-Id: <199901281034.KAA93851@keep.lan.Awfulhak.org>
X-Mailer: exmh version 2.0.2 2/24/98
To: Luigi Rizzo <luigi@labinfo.iet.unipi.it>
cc: bde@zeta.org.au (Bruce Evans), current@FreeBSD.ORG, grog@lemis.com,
peter.jeremy@auss2.alcatel.com.au
Subject: Re: indent(1) and style(9) (was: btokup() macro in sys/malloc.h)
In-reply-to: Your message of "Thu, 28 Jan 1999 08:35:33 +0100."
<199901280735.IAA08539@labinfo.iet.unipi.it>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Thu, 28 Jan 1999 10:34:32 +0000
From: Brian Somers <brian@Awfulhak.org>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
> > >an example -- basically all places where, for efficiency reasons,
> > >the code tries to expand in-line various block, the depth of
> > >indentation pushes everything to the right end leaving only 20-30
> > >useful chars per line.
> >
> > See the Linux style guide (linux/Documentation/CodingStyle) for
> > strong opinions about this: "if you need more than 3 levels of
> > indentation, you're screwed anyway, and should fix your program".
> >
> > I almost agree.
>
> in userland, probably me too. In the kernel, i am not so sure.
What's the difference ? I've heard people suggesting the opposite in
the past - ``low level code is long and thin, high level code is
wider''. But the kernel isn't the only place you find low level code.
> luigi
--
Brian <brian@Awfulhak.org> <brian@FreeBSD.org> <brian@OpenBSD.org>
<http://www.Awfulhak.org>
Don't _EVER_ lose your sense of humour !
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Thu Jan 28 03:03:19 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id DAA26895
for freebsd-current-outgoing; Thu, 28 Jan 1999 03:03:19 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from awfulhak.org (awfulhak.force9.co.uk [195.166.136.63])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA26882
for <current@FreeBSD.ORG>; Thu, 28 Jan 1999 03:03:15 -0800 (PST)
(envelope-from brian@Awfulhak.org)
Received: from keep.lan.Awfulhak.org (root@keep.lan.Awfulhak.org [172.16.0.8])
by awfulhak.org (8.8.8/8.8.8) with ESMTP id LAA06527;
Thu, 28 Jan 1999 11:03:12 GMT
(envelope-from brian@Awfulhak.org)
Received: from keep.lan.Awfulhak.org (brian@localhost [127.0.0.1])
by keep.lan.Awfulhak.org (8.9.2/8.9.2) with ESMTP id LAA94389;
Thu, 28 Jan 1999 11:04:42 GMT
(envelope-from brian@keep.lan.Awfulhak.org)
Message-Id: <199901281104.LAA94389@keep.lan.Awfulhak.org>
X-Mailer: exmh version 2.0.2 2/24/98
To: Alexander Sanda <as@psa.at>
cc: Brian Somers <brian@Awfulhak.org>, current@FreeBSD.ORG
Subject: Re: PPP (userland) troubles ?
In-reply-to: Your message of "Thu, 28 Jan 1999 11:04:03 +0100."
<Pine.BSF.4.05.9901281049140.244-100000@darkstar.vmx>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Thu, 28 Jan 1999 11:04:42 +0000
From: Brian Somers <brian@Awfulhak.org>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
> So there are now 2 possibilities for this problem:
>
> a) I was out of sync :(
> b) Someone fixed ppp
Last nights commit was for RADIUS support in ppp. There was another
latency problem that I fixed about a week ago - maybe that was it :-)
> --
> # /AS/ http://privat.schlund.de/entropy/ #
> # #
> # XX has detected, that your mouse cursor has changed position. Please #
> # restart XX, so it can be updated. -- From The Gimp manual #
--
Brian <brian@Awfulhak.org> <brian@FreeBSD.org> <brian@OpenBSD.org>
<http://www.Awfulhak.org>
Don't _EVER_ lose your sense of humour !
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Thu Jan 28 03:12:46 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id DAA27990
for freebsd-current-outgoing; Thu, 28 Jan 1999 03:12:46 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from vader.cs.berkeley.edu (vader.CS.Berkeley.EDU [128.32.38.234])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA27985
for <current@FreeBSD.ORG>; Thu, 28 Jan 1999 03:12:45 -0800 (PST)
(envelope-from asami@vader.cs.berkeley.edu)
Received: from silvia.hip.berkeley.edu (sji-ca13-237.ix.netcom.com [209.109.238.237]) by vader.cs.berkeley.edu (8.8.7/8.7.3) with ESMTP id DAA06410; Thu, 28 Jan 1999 03:12:42 -0800 (PST)
Received: (from asami@localhost) by silvia.hip.berkeley.edu (8.9.1/8.6.9) id DAA69718; Thu, 28 Jan 1999 03:12:37 -0800 (PST)
Date: Thu, 28 Jan 1999 03:12:37 -0800 (PST)
Message-Id: <199901281112.DAA69718@silvia.hip.berkeley.edu>
To: lh@aus.org
CC: jcwells@u.washington.edu, current@FreeBSD.ORG, steveo@iol.ie
In-reply-to: <199901271901.OAA22237@ayukawa.aus.org> (message from Luke on
Wed, 27 Jan 1999 14:20:32 -0500 (EST))
Subject: Re: Netscape | Mozilla
From: asami@FreeBSD.ORG (Satoshi Asami)
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
* From: Luke <lh@aus.org>
* linux_lib port. [why does it install into / anyways]
You can put it anywhere and symlink to it, like sysinstall does now,
but it has to be called "/compat" (or some other well-known place)
because of the implementation. The string "/compat/linux" has to be
hardcoded in the linux emulator binary. (If we move it to
"/usr/local/compat", people who use LOCALBASE other than "/usr/local"
will be screwed, etc.)
I know, I tried to change it before until I realized that it's not
that easy.
Satoshi
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Thu Jan 28 03:30:35 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id DAA01147
for freebsd-current-outgoing; Thu, 28 Jan 1999 03:30:35 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from peach.ocn.ne.jp (peach.ocn.ne.jp [210.145.254.87])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA01138
for <current@FreeBSD.ORG>; Thu, 28 Jan 1999 03:30:33 -0800 (PST)
(envelope-from dcs@newsguy.com)
Received: from newsguy.com by peach.ocn.ne.jp (8.9.1a/OCN) id UAA06204; Thu, 28 Jan 1999 20:30:26 +0900 (JST)
Message-ID: <36B04265.842788DA@newsguy.com>
Date: Thu, 28 Jan 1999 19:56:37 +0900
From: "Daniel C. Sobral" <dcs@newsguy.com>
X-Mailer: Mozilla 4.5 [en] (Win98; I)
X-Accept-Language: pt-BR,ja
MIME-Version: 1.0
To: Peter Jeremy <peter.jeremy@auss2.alcatel.com.au>
CC: current@FreeBSD.ORG
Subject: Re: btokup() macro in sys/malloc.h
References: <99Jan28.131753est.40347@border.alcanet.com.au>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
Peter Jeremy wrote:
>
> I'll support that. The example given in style(9):
>
> a = b->c[0] + ~d == (e || f) || g && h ? i : j >> 1;
>
> should rate as an entry in the Obfuscated C competition rather than
> an example of maintainable code.
As a matter of fact, what's the reasoning behind this particular
style(9) recommendation?
--
Daniel C. Sobral (8-DCS)
dcs@newsguy.com
If you sell your soul to the Devil and all you get is an MCSE from
it, you haven't gotten market rate.
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Thu Jan 28 03:30:42 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id DAA01188
for freebsd-current-outgoing; Thu, 28 Jan 1999 03:30:42 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from peach.ocn.ne.jp (peach.ocn.ne.jp [210.145.254.87])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA01165
for <current@FreeBSD.ORG>; Thu, 28 Jan 1999 03:30:38 -0800 (PST)
(envelope-from dcs@newsguy.com)
Received: from newsguy.com by peach.ocn.ne.jp (8.9.1a/OCN) id UAA06211; Thu, 28 Jan 1999 20:30:29 +0900 (JST)
Message-ID: <36B0436B.F4C0C7FA@newsguy.com>
Date: Thu, 28 Jan 1999 20:00:59 +0900
From: "Daniel C. Sobral" <dcs@newsguy.com>
X-Mailer: Mozilla 4.5 [en] (Win98; I)
X-Accept-Language: pt-BR,ja
MIME-Version: 1.0
To: Bruce Evans <bde@zeta.org.au>
CC: current@FreeBSD.ORG, peter.jeremy@auss2.alcatel.com.au
Subject: Re: btokup() macro in sys/malloc.h
References: <199901280316.OAA26849@godzilla.zeta.org.au>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
Bruce Evans wrote:
>
> >It would be nice if style(9) documented the options to give indent(1)
> >to match the `approved' layout convections. (This would reduce the
> >effort involved in importing large chunks of code).
>
> This is impossible, since indent(1) is buggy and out of date with both
> KNF and C.
Well... add it to the "projects" in the handbook... :-)
(seriously...)
--
Daniel C. Sobral (8-DCS)
dcs@newsguy.com
If you sell your soul to the Devil and all you get is an MCSE from
it, you haven't gotten market rate.
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Thu Jan 28 03:33:10 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id DAA01592
for freebsd-current-outgoing; Thu, 28 Jan 1999 03:33:10 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from atdot.dotat.org (atdot.dotat.org [203.23.150.35])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA01586
for <current@freebsd.org>; Thu, 28 Jan 1999 03:33:08 -0800 (PST)
(envelope-from newton@atdot.dotat.org)
Received: (from newton@localhost) by atdot.dotat.org (8.9.2/8.7) id WAA00464 for current@freebsd.org; Thu, 28 Jan 1999 22:02:01 +1030 (CST)
Date: Thu, 28 Jan 1999 22:02:01 +1030 (CST)
From: Mark Newton <newton@atdot.dotat.org>
Message-Id: <199901281132.WAA00464@atdot.dotat.org>
To: current@FreeBSD.ORG
Subject: LDT changes to support SysVR4 emulator
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
Ok, people, heads up -- I'm about to commit a patch to /sys/i386
which changes the way FreeBSD uses the x86 LDT. Specifically,
I'm moving LUDATA_SEL from LDT entry 4 to 5 (Why 5? Why not?)
and re-using entry 4 as a call gate for SysV system calls made
by library stubs from Solaris 2.6 and higher.
I've been running with these mods for about a month now with no
problems at all (there are no userland implications AFAICT).
Nevertheless, I'm going to leave this in for a couple of days
before committing the rest of the emulator to give interested
parties a chance to bitch at me :-)
Cheers,
- mark
--------------------------------------------------------------------
I tried an internal modem, newton@atdot.dotat.org
but it hurt when I walked. Mark Newton
----- Voice: +61-4-1958-3414 ------------- Fax: +61-8-83034403 -----
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Thu Jan 28 03:37:20 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id DAA02255
for freebsd-current-outgoing; Thu, 28 Jan 1999 03:37:20 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from vader.cs.berkeley.edu (vader.CS.Berkeley.EDU [128.32.38.234])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA02244
for <current@FreeBSD.ORG>; Thu, 28 Jan 1999 03:37:16 -0800 (PST)
(envelope-from asami@vader.cs.berkeley.edu)
Received: from silvia.hip.berkeley.edu (sji-ca13-237.ix.netcom.com [209.109.238.237]) by vader.cs.berkeley.edu (8.8.7/8.7.3) with ESMTP id DAA06440; Thu, 28 Jan 1999 03:37:00 -0800 (PST)
Received: (from asami@localhost) by silvia.hip.berkeley.edu (8.9.1/8.6.9) id DAA69797; Thu, 28 Jan 1999 03:36:56 -0800 (PST)
Date: Thu, 28 Jan 1999 03:36:56 -0800 (PST)
Message-Id: <199901281136.DAA69797@silvia.hip.berkeley.edu>
To: jdp@polstra.com
CC: bde@zeta.org.au, current@FreeBSD.ORG
In-reply-to: <XFMail.990127214511.jdp@polstra.com> (message from John Polstra
on Wed, 27 Jan 1999 21:45:11 -0800 (PST))
Subject: Re: btokup() macro in sys/malloc.h
From: asami@FreeBSD.ORG (Satoshi Asami)
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
* From: John Polstra <jdp@polstra.com>
* On 28-Jan-99 Bruce Evans wrote:
Hey John, are you sure your mailer is Y2K compliant?
Satoshi
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Thu Jan 28 03:40:41 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id DAA02451
for freebsd-current-outgoing; Thu, 28 Jan 1999 03:40:41 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA02443
for <current@freebsd.org>; Thu, 28 Jan 1999 03:40:39 -0800 (PST)
(envelope-from julian@whistle.com)
Received: (from daemon@localhost)
by alpo.whistle.com (8.8.5/8.8.5) id DAA28482
for <current@freebsd.org>; Thu, 28 Jan 1999 03:38:44 -0800 (PST)
Received: from s204m82.isp.whistle.com(207.76.204.82)
via SMTP by alpo.whistle.com, id smtpdg28479; Thu Jan 28 11:38:33 1999
Date: Thu, 28 Jan 1999 03:38:31 -0800 (PST)
From: Julian Elischer <julian@whistle.com>
X-Sender: julian@s204m82.isp.whistle.com
To: current@FreeBSD.ORG
Subject: Re: btokup().. patch to STYLE(9) (fwd)
Message-ID: <Pine.BSF.4.05.9901280335450.304-100000@s204m82.isp.whistle.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
Some people when confronted by people wanting to have extra braces
say "change style(9)".
Well, here is my change..
I think theere is enough support for this that this should be discussed
seriously, and "It's not like in the good old days", or
"I'm not used to extra parenthesis" are not going to be considerred as
good reasons for not committing this.. Anyone can have reasons of that
level.
The aim to allow more braces and parens when needed for clarity.
"Clarity" is decided by the person who get's confused because they ar enot
there.
Index: style.9
===================================================================
RCS file: /cvs/freebsd/src/share/man/man9/style.9,v
retrieving revision 1.22
diff -u -r1.22 style.9
--- style.9 1997/12/07 20:25:45 1.22
+++ style.9 1999/01/28 09:07:46
@@ -256,13 +256,23 @@
.Ed
.Pp
Space after keywords (if, while, for, return, switch). No braces are
-used for control statements with zero or only a single statement.
+used for control statements with zero or only a single statement unless that
+statement is more than a single line in which case they are permitted.
Forever loops are done with for's, not while's.
.Bd -literal -offset 0i
for (p = buf; *p != '\e0'; ++p)
; /* nothing */
for (;;)
stmt;
+ for (;;) {
+ z = a + really + long + statement + that + needs +
+ two lines + gets + indented + four + spaces +
+ on + the + second + and + subsequent + lines;
+ }
+ for (;;) {
+ if (cond)
+ stmt;
+ }
if (val != NULL)
val = realloc(val, newsize);
.Ed
@@ -290,7 +300,7 @@
and do not use spaces in front of tabs.
.Pp
Closing and opening braces go on the same line as the else.
-Don't add braces that aren't necessary.
+Braces that aren't necessary may be left out.
.Bd -literal -offset 0i
if (test)
stmt;
@@ -318,7 +328,8 @@
.Pp
Unary operators don't require spaces, binary operators do. Don't
use parentheses unless they're required for precedence, or the
-statement is really confusing without them.
+statement is confusing without them. Remember that other people may
+confuse easier then you. Do YOU understand the following?
.Bd -literal -offset 0i
a = b->c[0] + ~d == (e || f) || g && h ? i : j >> 1;
k = !(l & FLAGS);
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Thu Jan 28 03:54:05 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id DAA03713
for freebsd-current-outgoing; Thu, 28 Jan 1999 03:54:05 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from opi.flirtbox.ch ([62.48.0.50])
by hub.freebsd.org (8.8.8/8.8.8) with SMTP id DAA03708
for <current@FreeBSD.ORG>; Thu, 28 Jan 1999 03:54:03 -0800 (PST)
(envelope-from oppermann@pipeline.ch)
Received: (qmail 88632 invoked from network); 28 Jan 1999 11:53:57 -0000
Received: from unknown (HELO pipeline.ch) (195.134.128.41)
by opi.flirtbox.ch with SMTP; 28 Jan 1999 11:53:57 -0000
Message-ID: <36B04FB6.B2B54FD1@pipeline.ch>
Date: Thu, 28 Jan 1999 12:53:26 +0100
From: Andre Oppermann <oppermann@pipeline.ch>
X-Mailer: Mozilla 4.03 [en] (WinNT; U)
MIME-Version: 1.0
To: Brian Somers <brian@Awfulhak.org>
CC: current@FreeBSD.ORG
Subject: Re: PPP (userland) troubles ?
References: <199901281104.LAA94389@keep.lan.Awfulhak.org>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
Brian Somers wrote:
>
> > So there are now 2 possibilities for this problem:
> >
> > a) I was out of sync :(
> > b) Someone fixed ppp
>
> Last nights commit was for RADIUS support in ppp. There was another
> latency problem that I fixed about a week ago - maybe that was it :-)
Yuck! (jumping in the air and clapping with my feet!!)
--
Andre
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Thu Jan 28 04:14:11 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id EAA08623
for freebsd-current-outgoing; Thu, 28 Jan 1999 04:14:11 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from aire.open.ac.uk (aire.open.ac.uk [137.108.40.21])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA08614
for <current@freebsd.org>; Thu, 28 Jan 1999 04:14:02 -0800 (PST)
(envelope-from A.M.Zanker@open.ac.uk)
Received: from mallard.open.ac.uk ([137.108.40.50] helo=mallard)
by aire.open.ac.uk with smtp (Exim 2.11 #1)
id 105qKV-0002ps-00
for current@FreeBSD.ORG; Thu, 28 Jan 1999 12:13:51 +0000
Message-Id: <4.1.19990128120838.00b2e350@aire.open.ac.uk>
X-Sender: mikez@aire.open.ac.uk
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.1
Date: Thu, 28 Jan 1999 12:13:50 +0000
To: current@FreeBSD.ORG
From: Mike Zanker <A.M.Zanker@open.ac.uk>
Subject: Re: Celeron 333 kernel panic
In-Reply-To: <4.1.19990128101137.04065170@aire.open.ac.uk>
References: <36B0338C.B6B5D825@tdx.co.uk>
<4.1.19990128091540.00ad0680@aire.open.ac.uk>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
At 10:13 28/01/99 , Mike Zanker wrote:
>Thanks, this is the problem - I've only got I586_CPU in my config. I *knew*
>I should have kept a GENERIC kernel around!
OK, I've been very, very silly and not kept a GENERIC kernel around and
cannot boot with my existing kernel. Is there some way of booting from
floppy (e.g. boot.flp from 3.0-RELEASE or 3.0-SNAP) and copying a GENERIC
kernel to my existing root partition. I should be very grateful if someone
could point me in the direction of any documentation.
Thanks in advance,
Mike
--
Mike Zanker | Email: A.M.Zanker@open.ac.uk
Network and Computer Services Group | Tel : +44 1908 652726
The Open University | Fax : +44 1908 652193
Milton Keynes, UK | PGP public key available
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Thu Jan 28 04:40:49 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id EAA11519
for freebsd-current-outgoing; Thu, 28 Jan 1999 04:40:49 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from sis.bytes.gen.nz ([203.97.44.233])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA11510
for <current@FreeBSD.ORG>; Thu, 28 Jan 1999 04:40:19 -0800 (PST)
(envelope-from phillip@sis.bytes.gen.nz)
Received: from localhost (phillip@localhost)
by sis.bytes.gen.nz (8.9.2/8.9.2) with ESMTP id BAA01225;
Fri, 29 Jan 1999 01:38:39 +1300 (NZDT)
(envelope-from phillip@sis.bytes.gen.nz)
Date: Fri, 29 Jan 1999 01:38:32 +1300 (NZDT)
From: Phillip Hardy <phillip@sis.bytes.gen.nz>
X-Sender: phillip@sis
To: Mike Zanker <A.M.Zanker@open.ac.uk>
cc: current@FreeBSD.ORG
Subject: Re: Celeron 333 kernel panic
In-Reply-To: <4.1.19990128120838.00b2e350@aire.open.ac.uk>
Message-ID: <Pine.BSF.4.05.9901290135090.1200-100000@sis>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
On Thu, 28 Jan 1999, Mike Zanker wrote:
> OK, I've been very, very silly and not kept a GENERIC kernel around and
> cannot boot with my existing kernel. Is there some way of booting from
> floppy (e.g. boot.flp from 3.0-RELEASE or 3.0-SNAP) and copying a GENERIC
> kernel to my existing root partition. I should be very grateful if someone
> could point me in the direction of any documentation.
>
Hi Mike
Tryed usering Fixit floppy...
useing the fixit floppy you can then mount your root filesystem..
and start mounting other filesystems like /var /usr etc.
and then goto /usr/src/sys/i386/conf
edit your hostnamefile.. Add 686 support
config hostname ; cd ../../compile/hostname
make clean ; make depend ; make ; make install
Reboot (x fingers) and hopefully you will be back with us)
Phill
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Thu Jan 28 05:04:22 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id FAA13403
for freebsd-current-outgoing; Thu, 28 Jan 1999 05:04:22 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from atdot.dotat.org (atdot.dotat.org [203.23.150.35])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA13398
for <current@freebsd.org>; Thu, 28 Jan 1999 05:04:20 -0800 (PST)
(envelope-from newton@atdot.dotat.org)
Received: (from newton@localhost) by atdot.dotat.org (8.9.2/8.7) id XAA02492; Thu, 28 Jan 1999 23:33:09 +1030 (CST)
Date: Thu, 28 Jan 1999 23:33:09 +1030 (CST)
From: Mark Newton <newton@atdot.dotat.org>
Message-Id: <199901281303.XAA02492@atdot.dotat.org>
To: current@FreeBSD.ORG
Subject: Re: btokup() macro in sys/malloc.h
Cc: jdp@polstra.com
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
John Polstra <jdp@polstra.com> wrote:
> On 28-Jan-99 John Birrell wrote:
> > John Polstra wrote:
> >>
> >> Hear ye, hear ye! Be it here noted and archived for all eternity that
> >> on January 27, 1999 Pacific Time, John Polstra was, for one fleeting
> >> moment, purer than Bruce! :-)
> >
> >OK, so now we have to shoot you too. Oh well, so be it....
> >
> >Are there any others who would like to join these purists? Come on,
> >we have bullets for you all...
>
> Bah! You might be able to hit Bruce over there in oz. But to hit me,
> you'd need an ICBM. Give me purity or give me death! Bwahahahahah!
That's ok -- We'll give you death. We have your ICBM address:
> John Polstra jdp@polstra.com
> John D. Polstra & Co., Inc. Seattle, Washington USA
^^^^^^^^^^^^^^^^^^^^
Come to think of it, that might solve a few other problems too.
Linus Torvalds may want world domination, but I think our way has
the potential to be quicker...
- mark :-)
--------------------------------------------------------------------
I tried an internal modem, newton@atdot.dotat.org
but it hurt when I walked. Mark Newton
----- Voice: +61-4-1958-3414 ------------- Fax: +61-8-83034403 -----
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Thu Jan 28 05:29:37 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id FAA16303
for freebsd-current-outgoing; Thu, 28 Jan 1999 05:29:37 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from spoon.beta.com (mcgovern.ne.mediaone.net [24.128.106.170])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA16292
for <current@freebsd.org>; Thu, 28 Jan 1999 05:29:35 -0800 (PST)
(envelope-from mcgovern@spoon.beta.com)
Received: from spoon.beta.com (localhost.beta.com [127.0.0.1])
by spoon.beta.com (8.8.8/8.8.8) with ESMTP id IAA22988
for <current@freebsd.org>; Thu, 28 Jan 1999 08:30:27 -0500 (EST)
(envelope-from mcgovern@spoon.beta.com)
Message-Id: <199901281330.IAA22988@spoon.beta.com>
To: current@FreeBSD.ORG
Subject: boot.flp in 1/27/98 -STABLE...
Date: Thu, 28 Jan 1999 08:30:27 -0500
From: "Brian J. McGovern" <mcgovern@spoon.beta.com>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
I've just finished building my n'th release of -STABLE, and that dang boot
floppy is still too big. I know I came in on the trailing edge of the
discussion to change the whole boot thing, but after poking through a few
ideas, and testing them out, I came up with a few that might make for
a reasonable transition... So people that wanted to use -STABLE could boot
from a floppy or CD while the 'real solution' was worked out, without
having to install 3.0-RELEASE, then go through the upgrade process....
My first thought was to use a 2.88MB floppy image. I've heard mixed results
on LS-120 drives, but I know that CDs can use them, solving at least half
the problem.
My second thought was to possibly use the "Stressed" floppy formats. The
fd1720 looks more than big enough to hold the whole thing, as it appears
that the only thing missing from boot.flp is the boot directory, coming
in at 200-and-something K (lets just say < 300K, its been a few hours since
I looked at it). If this stressed format is actually real, it should work. I
haven't checked to see if a CD boot program will recognize this or not, so
that may be a gotcha....
In any event, a 2 floppy boot works, but its a pain to tote two floppies
around when you're used to just popping the CD in....
Anyhow, just making some "band aid" suggestions to try to increase the
exposure of -STABLE so we can use it a lot more, and find more bugs....
-Brian
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Thu Jan 28 06:23:48 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id GAA22163
for freebsd-current-outgoing; Thu, 28 Jan 1999 06:23:48 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from k6n1.znh.org ([207.109.235.12])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA22050
for <freebsd-current@freebsd.org>; Thu, 28 Jan 1999 06:23:28 -0800 (PST)
(envelope-from zach@uffdaonline.net)
Received: (from zach@localhost)
by k6n1.znh.org (8.9.1/8.9.1) id OAA68236;
Thu, 28 Jan 1999 14:22:22 GMT
(envelope-from zach)
Message-ID: <19990128082222.B67166@znh.org>
Date: Thu, 28 Jan 1999 08:22:22 -0600
From: Zach Heilig <zach@uffdaonline.net>
To: Bruce Evans <bde@zeta.org.au>, axl@iafrica.com, pantzer@ludd.luth.se
Cc: freebsd-current@FreeBSD.ORG
Subject: Re: NIS with HPUX 10.20
References: <199901280906.UAA27849@godzilla.zeta.org.au>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.93.2i
In-Reply-To: <199901280906.UAA27849@godzilla.zeta.org.au>; from Bruce Evans on Thu, Jan 28, 1999 at 08:06:58PM +1100
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
On Thu, Jan 28, 1999 at 08:06:58PM +1100, Bruce Evans wrote:
> Someday -C should avoid touching the file if possible, so that it
> doesn't clobber the file's ctime and backups based on ctimes don't do
> unnecessary work. This is possible if none of the attributes except
> the file times would change, and fairly easy to implement if the file
> doesn't have any links.
Hm... Two conflicting goals:
Avoid backing up too much.
Identify deprecated files.
The solutions I can think of (so far) are quite ugly...
--
Zach Heilig <zach@uffdaonline.net> / Zach Heilig <zach@gaffaneys.com>
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Thu Jan 28 06:29:17 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id GAA22649
for freebsd-current-outgoing; Thu, 28 Jan 1999 06:29:17 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from fledge.watson.org (FLEDGE.RES.CMU.EDU [128.2.93.229])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA22644
for <freebsd-current@FreeBSD.ORG>; Thu, 28 Jan 1999 06:29:16 -0800 (PST)
(envelope-from robert@cyrus.watson.org)
Received: from fledge.watson.org (robert@fledge.pr.watson.org [192.0.2.3])
by fledge.watson.org (8.8.8/8.8.8) with SMTP id JAA11446;
Thu, 28 Jan 1999 09:29:14 -0500 (EST)
Date: Thu, 28 Jan 1999 09:29:14 -0500 (EST)
From: Robert Watson <robert@cyrus.watson.org>
X-Sender: robert@fledge.watson.org
Reply-To: Robert Watson <robert+freebsd@cyrus.watson.org>
To: Garrett Wollman <wollman@khavrinen.lcs.mit.edu>
cc: freebsd-current@FreeBSD.ORG
Subject: Re: Naming files in sys/kern
In-Reply-To: <199901280228.VAA14247@khavrinen.lcs.mit.edu>
Message-ID: <Pine.BSF.3.96.990128092054.8847A-100000@fledge.watson.org>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
On Wed, 27 Jan 1999, Garrett Wollman wrote:
> <<On Wed, 27 Jan 1999 18:30:15 -0500 (EST), Robert Watson <robert@cyrus.watson.org> said:
>
> > It's not clear to me, when thinking of introducing a new file (say, for
> > auditing support :), what I should name it. Would it be kern_audit.c or
> > sys_audit.c?
>
> Depends on what it is auditing. If it only auditing the basic I/O
> operations, then it would go in sys_*.c. If it's a more general
> kernel facility, then it goes in kern_*.c.
The spec has audit records describing all POSIX.1 calls (fork, etc). They
also allow for additional audit records that are application or system
defined (such as a login audit record, or a socket audit record). As
such, I'll assume kern_audit.c. I do notice, however, that subr_log.c is
fairly similar to what I'm doing (at least in that it has a /dev/log for a
userland process, and is referenced hither and thither).
> > Or, if it is POSIX.1e, would it go into a /usr/src/sys/posix1e
> > directory as the posix4 realtime stuff did (assuming that support
> > for additional features from that posix draft were going to be
> > forthcoming)?
>
> Giving the unhelpful tendency of Project 1003 to renumber its
> standards after-the-fact (or fold them into the main 1003.1 document),
> I would suggest against using committee identifiers like this.
This is further confused by the fact that this draft (as I understand it)
will not be made a standard. However, Solaris and Linux both seem to have
ACL implementations, and Linux the Capabilities implementation. (Linux
does not have file system support for these, however) The auditing code
will be useful for a project I'm working on, so I figured I'd do that
first.
> If it's controlled by a compile-time option, it should probably be
> called POSIX_AUDITING rather than POSIX_1e or something of that
> nature, since your statement implies that there is a useful
> granularity of features.
The components of 1e (and 2c, the userland utilities associated with 1e):
ACLs
Capabilities
Auditing
MAC
Information Labels
The order of interest for me is Auditing, Capabilities, ACLs, and then the
remaining two. Auditing has immediate benefit to a project of mine; it
requires fairly comprehensive userland library support, so it may take a
few weeks. To do ACLs, I need some place to store ACLs, such as
additional file forks or a centralized file like quotas use--I'm not sure
I want to deal with them yet, although they would be nice to have. I have
not reviewed Capabilities in detail--they don't seem horribly useful to me
in terms of the standard capabilities they define--however, adding some of
our own that are more tailored to BSD would be useful. MAC and
Information Labels are clearly useful--that is, if someone wants to try
and make FreeBSD Bx rated :). I'll do these if I have time, probably this
summer.
For now, I'll add options:
POSIX_AUD
POSIX_ACL
POSIX_CAP
POSIX_MAC
POSIX_INF
Which are consistent with the run-time defines associated with the
features (the run-time defines have _'s in front).
Robert N Watson
robert@fledge.watson.org http://www.watson.org/~robert/
PGP key fingerprint: 03 01 DD 8E 15 67 48 73 25 6D 10 FC EC 68 C1 1C
Carnegie Mellon University http://www.cmu.edu/
TIS Labs at Network Associates, Inc. http://www.tis.com/
SafePort Network Services http://www.safeport.com/
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Thu Jan 28 06:41:14 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id GAA24399
for freebsd-current-outgoing; Thu, 28 Jan 1999 06:41:14 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.26.10.9])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA24388
for <freebsd-current@FreeBSD.ORG>; Thu, 28 Jan 1999 06:41:06 -0800 (PST)
(envelope-from bde@godzilla.zeta.org.au)
Received: (from bde@localhost)
by godzilla.zeta.org.au (8.8.7/8.8.7) id BAA21370;
Fri, 29 Jan 1999 01:39:47 +1100
Date: Fri, 29 Jan 1999 01:39:47 +1100
From: Bruce Evans <bde@zeta.org.au>
Message-Id: <199901281439.BAA21370@godzilla.zeta.org.au>
To: axl@iafrica.com, bde@zeta.org.au
Subject: Re: NIS with HPUX 10.20
Cc: bonnetf@bart.esiee.fr, dhw@whistle.com, freebsd-current@FreeBSD.ORG,
meyerd1@fang.cs.sunyit.edu, mike@smith.net.au
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
>> No. installworld more or less assumes single user.
>
>This is really what I'm getting at. :-)
>
>If installworld assumes single-user mode, why do we install -C
>ld-elf.so.1 ? The first time I asked this question, I didn't mention
>single-user mode and your answer was that it's to protect "live
>systems". What's so live about a single-user system that we can't assume
>nothing else needs ld-elf.so.1 while we're smacking it?
For ld.so, it seems to have been just to make things work in multi-user
mode:
> RCS file: /home/ncvs/src/libexec/rtld-aout/Makefile,v
> Working file: Makefile
> head: 1.27
> ...
> ----------------------------
> revision 1.16
> date: 1996/01/11 03:45:55; author: jdp; state: Exp; lines: +13 -2
> Install ld.so in a way that is safe even on a running system.
> ----------------------------
Perhaps it is useful even in single user mode for `make -j2 world'.
Bruce
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Thu Jan 28 06:46:02 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id GAA24970
for freebsd-current-outgoing; Thu, 28 Jan 1999 06:46:02 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from darkstar.psa.at (darkstar.psa.at [194.152.163.137])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA24943
for <current@freebsd.org>; Thu, 28 Jan 1999 06:45:54 -0800 (PST)
(envelope-from root@psa.at)
Received: from unet3-191.univie.ac.at ([131.130.232.191] helo=entropy.quake.at)
by darkstar.psa.at with esmtp (Exim 2.05 #1)
id 105sv1-0004LY-00; Thu, 28 Jan 1999 15:59:44 +0100
Received: from localhost ([127.0.0.1])
by entropy.quake.at with esmtp (Exim 2.10 #2)
id 105ohg-00009r-00; Thu, 28 Jan 1999 11:29:40 +0100
Date: Thu, 28 Jan 1999 11:29:40 +0100 (CET)
From: Alexander Sanda <as@psa.at>
X-Sender: root@darkstar.vmx
To: Mike Zanker <A.M.Zanker@open.ac.uk>
cc: current@FreeBSD.ORG
Subject: Re: Celeron 333 kernel panic
In-Reply-To: <4.1.19990128091540.00ad0680@aire.open.ac.uk>
Message-ID: <Pine.BSF.4.05.9901281125000.520-100000@darkstar.vmx>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
On Thu, 28 Jan 1999, Mike Zanker wrote:
> Having just upgraded my motherboard/CPU to a BX chip set and Celeron 333 I
> attempted to boot into my 3.0-STABLE system. However, as soon as the kernel
> starts to boot I get
>
> panic: cpu class not configured
>
> and the machine reboots (and so on...)
>
> Is this cpu supported?
As far as I know, yes. Check your kernel config and include cpu
"I686_CPU" (valid for Pentium Pro, P2 and probably celerons).
You could comment out the other cpu options, but this isn't 100%
necessary. They don't do any harm, but they *might* have an impact on
performance and probably bloat the kernel a bit.
(the GENERIC kernel always includes all cpu types, that's why it is
called "GENERIC", i think :)
--
# /AS/ http://privat.schlund.de/entropy/ #
# #
# XX has detected, that your mouse cursor has changed position. Please #
# restart XX, so it can be updated. -- From The Gimp manual #
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Thu Jan 28 08:10:22 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id IAA05341
for freebsd-current-outgoing; Thu, 28 Jan 1999 08:10:22 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from friley-184-92.res.iastate.edu (friley-184-92.res.iastate.edu [129.186.184.92])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA05336
for <freebsd-current@freebsd.org>; Thu, 28 Jan 1999 08:10:21 -0800 (PST)
(envelope-from mystify@friley-184-92.res.iastate.edu)
Received: from friley-184-92.res.iastate.edu (localhost.res.iastate.edu [127.0.0.1])
by friley-184-92.res.iastate.edu (8.9.2/8.9.1) with ESMTP id KAA04600
for <freebsd-current@freebsd.org>; Thu, 28 Jan 1999 10:10:20 -0600 (CST)
(envelope-from mystify@friley-184-92.res.iastate.edu)
Message-Id: <199901281610.KAA04600@friley-184-92.res.iastate.edu>
To: freebsd-current@FreeBSD.ORG
Subject: Reading a text file with BTX
Date: Thu, 28 Jan 1999 10:10:20 -0600
From: Patrick Hartling <mystify@friley-184-92.res.iastate.edu>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
Is there a way to view the contents of a text file (specifically,
/boot/loader.rc) with BTX? Now that there are all these nifty new modules,
my kernel is a lot smaller and my /boot/loader.rc is a lot longer. The way
I have my /boot/loader.rc setup is such that it unloads everythin
automatically loaded if I drop to the BTX prompt instead of autobooting.
This is fairly convenient except when I want to boot an alternate kernel but
still load all the same modules that I use in my default kernel. If there
isn't such a feature, it would be really nice if there were a 'cat' command
or something along those lines so that I could read the contents of
/boot/loader.rc and get everything properly reloaded by hand. Could it be
added or could I just make my own somehow? Thanks a bunch.
-Patrick
Patrick L. Hartling | Research Assistant, ICEMT
mystify@friley-184-92.res.iastate.edu | Carver Lab - 0095E Black Engineering
http://www.public.iastate.edu/~oz/ | http://www.icemt.iastate.edu/
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Thu Jan 28 08:32:45 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id IAA08068
for freebsd-current-outgoing; Thu, 28 Jan 1999 08:32:45 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from khavrinen.lcs.mit.edu (khavrinen.lcs.mit.edu [18.24.4.193])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA08059
for <current@FreeBSD.ORG>; Thu, 28 Jan 1999 08:32:43 -0800 (PST)
(envelope-from wollman@khavrinen.lcs.mit.edu)
Received: (from wollman@localhost)
by khavrinen.lcs.mit.edu (8.9.1/8.9.1) id LAA17377;
Thu, 28 Jan 1999 11:32:35 -0500 (EST)
(envelope-from wollman)
Date: Thu, 28 Jan 1999 11:32:35 -0500 (EST)
From: Garrett Wollman <wollman@khavrinen.lcs.mit.edu>
Message-Id: <199901281632.LAA17377@khavrinen.lcs.mit.edu>
To: "Daniel C. Sobral" <dcs@newsguy.com>
Cc: current@FreeBSD.ORG
Subject: Re: btokup() macro in sys/malloc.h
In-Reply-To: <36B04265.842788DA@newsguy.com>
References: <99Jan28.131753est.40347@border.alcanet.com.au>
<36B04265.842788DA@newsguy.com>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
<<On Thu, 28 Jan 1999 19:56:37 +0900, "Daniel C. Sobral" <dcs@newsguy.com> said:
> Peter Jeremy wrote:
>>
>> I'll support that. The example given in style(9):
>>
>> a = b->c[0] + ~d == (e || f) || g && h ? i : j >> 1;
>>
>> should rate as an entry in the Obfuscated C competition rather than
>> an example of maintainable code.
> As a matter of fact, what's the reasoning behind this particular
> style(9) recommendation?
I believe that it was an attempt on Berkeley's part to ``raise the
bar'' for kernel coders -- `if you don't know the C operator precedence
table by heart, you shouldn't be writing kernel code'. Obviously, it
didn't work, or we wouldn't be here today.
-GAWollman
--
Garrett A. Wollman | O Siem / We are all family / O Siem / We're all the same
wollman@lcs.mit.edu | O Siem / The fires of freedom
Opinions not those of| Dance in the burning flame
MIT, LCS, CRS, or NSA| - Susan Aglukark and Chad Irschick
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Thu Jan 28 08:45:04 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id IAA09282
for freebsd-current-outgoing; Thu, 28 Jan 1999 08:45:04 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from ns.mt.sri.com (sri-gw.MT.net [206.127.105.141])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA09271
for <current@FreeBSD.ORG>; Thu, 28 Jan 1999 08:45:03 -0800 (PST)
(envelope-from nate@mt.sri.com)
Received: from mt.sri.com (rocky.mt.sri.com [206.127.76.100])
by ns.mt.sri.com (8.8.8/8.8.8) with SMTP id JAA15752;
Thu, 28 Jan 1999 09:29:54 -0700 (MST)
(envelope-from nate@rocky.mt.sri.com)
Received: by mt.sri.com (SMI-8.6/SMI-SVR4)
id JAA29626; Thu, 28 Jan 1999 09:29:48 -0700
Date: Thu, 28 Jan 1999 09:29:48 -0700
Message-Id: <199901281629.JAA29626@mt.sri.com>
From: Nate Williams <nate@mt.sri.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
To: Andrew Kenneth Milton <akm@zeus.theinternet.com.au>
Cc: current@FreeBSD.ORG
Subject: Style (was Re: btokup()..)
In-Reply-To: <199901280833.SAA14617@zeus.theinternet.com.au>
References: <199901280728.XAA98161@apollo.backplane.com>
<199901280833.SAA14617@zeus.theinternet.com.au>
X-Mailer: VM 6.34 under 19.16 "Lille" XEmacs Lucid
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
> | :I think that style(9) should be modified to include
> | :"Parenthesis may be used to improve the readbility of complex
> | :expressions even if not strictly required."
> | :instead of the stupid phrase presently there.
> | :also:
> | :"Braces around code blocks should be allowable even when not strictly
> | :needed, for the purpose of readbility."
> | :
> | :The aim is to produce readble maintainable code, not to save bytes in
> | :sourcecode!
> |
> | I agree completely. I've already gotten into the habit of added
> | braces when conditonal expressions exceed one line, even though there
> | may be only one statement. Otherwise the code is just too unreadable.
>
> Is there an ident style for (x)emacs to enforce/promote this style?
*emacs never inserts code, so you couldn't get it to 'add' parentheses
or braces to code. It doesn't even whine about them. The only thing
that it does is move your white-space around.
Nate
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Thu Jan 28 08:58:09 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id IAA10912
for freebsd-current-outgoing; Thu, 28 Jan 1999 08:58:09 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from dingo.cdrom.com (castles198.castles.com [208.214.165.198])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA10842;
Thu, 28 Jan 1999 08:58:00 -0800 (PST)
(envelope-from mike@dingo.cdrom.com)
Received: from dingo.cdrom.com (localhost [127.0.0.1])
by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id IAA04657;
Thu, 28 Jan 1999 08:26:43 -0800 (PST)
(envelope-from mike@dingo.cdrom.com)
Message-Id: <199901281626.IAA04657@dingo.cdrom.com>
X-Mailer: exmh version 2.0.2 2/24/98
To: asami@FreeBSD.ORG (Satoshi Asami)
cc: lh@aus.org, jcwells@u.washington.edu, current@FreeBSD.ORG, steveo@iol.ie
Subject: Re: Netscape | Mozilla
In-reply-to: Your message of "Thu, 28 Jan 1999 03:12:37 PST."
<199901281112.DAA69718@silvia.hip.berkeley.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Thu, 28 Jan 1999 08:26:42 -0800
From: Mike Smith <mike@smith.net.au>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
> * From: Luke <lh@aus.org>
>
> * linux_lib port. [why does it install into / anyways]
>
> You can put it anywhere and symlink to it, like sysinstall does now,
> but it has to be called "/compat" (or some other well-known place)
> because of the implementation. The string "/compat/linux" has to be
> hardcoded in the linux emulator binary. (If we move it to
> "/usr/local/compat", people who use LOCALBASE other than "/usr/local"
> will be screwed, etc.)
>
> I know, I tried to change it before until I realized that it's not
> that easy.
Install it in $PREFIX/compat and then make a symlink from /compat to
${PREFIX}/compat. This only fails if you then install the SVR4 stuff
with a different ${PREFIX}, which will screw you anyway. 8)
--
\\ Sometimes you're ahead, \\ Mike Smith
\\ sometimes you're behind. \\ mike@smith.net.au
\\ The race is long, and in the \\ msmith@freebsd.org
\\ end it's only with yourself. \\ msmith@cdrom.com
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Thu Jan 28 09:03:20 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id JAA11435
for freebsd-current-outgoing; Thu, 28 Jan 1999 09:03:20 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.95.76.54])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA11430
for <current@FreeBSD.ORG>; Thu, 28 Jan 1999 09:03:19 -0800 (PST)
(envelope-from sgk@troutmask.apl.washington.edu)
Received: (from sgk@localhost)
by troutmask.apl.washington.edu (8.9.1/8.9.1) id JAA11465;
Thu, 28 Jan 1999 09:04:32 -0800 (PST)
(envelope-from sgk)
From: Steve Kargl <sgk@troutmask.apl.washington.edu>
Message-Id: <199901281704.JAA11465@troutmask.apl.washington.edu>
Subject: Re: LDT changes to support SysVR4 emulator
In-Reply-To: <199901281132.WAA00464@atdot.dotat.org> from Mark Newton at "Jan 28, 1999 10: 2: 1 pm"
To: newton@atdot.dotat.org (Mark Newton)
Date: Thu, 28 Jan 1999 09:04:32 -0800 (PST)
Cc: current@FreeBSD.ORG
X-Mailer: ELM [version 2.4ME+ PL43 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
Mark Newton wrote:
> Ok, people, heads up -- I'm about to commit a patch to /sys/i386
> which changes the way FreeBSD uses the x86 LDT. Specifically,
> I'm moving LUDATA_SEL from LDT entry 4 to 5 (Why 5? Why not?)
> and re-using entry 4 as a call gate for SysV system calls made
> by library stubs from Solaris 2.6 and higher.
>
Have you tested how this might affect wine?
--
Steve
finger kargl@troutmask.apl.washington.edu
http://troutmask.apl.washington.edu/~clesceri/kargl.html
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Thu Jan 28 09:05:06 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id JAA11710
for freebsd-current-outgoing; Thu, 28 Jan 1999 09:05:06 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from dt050n08.san.rr.com (dt050n08.san.rr.com [204.210.31.8])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA11699
for <current@FreeBSD.ORG>; Thu, 28 Jan 1999 09:05:03 -0800 (PST)
(envelope-from Studded@gorean.org)
Received: from gorean.org (master [10.0.0.2])
by dt050n08.san.rr.com (8.8.8/8.8.8) with ESMTP id JAA05957;
Thu, 28 Jan 1999 09:04:57 -0800 (PST)
(envelope-from Studded@gorean.org)
Message-ID: <36B098B5.9545E900@gorean.org>
Date: Thu, 28 Jan 1999 09:04:53 -0800
From: Studded <Studded@gorean.org>
Organization: Triborough Bridge & Tunnel Authority
X-Mailer: Mozilla 4.5 [en] (Win98; I)
X-Accept-Language: en
MIME-Version: 1.0
To: Jaye Mathisen <mrcpu@internetcds.com>
CC: current@FreeBSD.ORG
Subject: Re: mergemaster should be merged in to the main tree.
References: <Pine.NEB.3.95.990106105832.634d-100000@schizo.cdsnet.net>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
Jaye Mathisen wrote:
>
> This utility is too valuable for all the update not to at least have a
> mention of it.
Thank you. :) The occasional compliment makes the hard work worthwhile.
> At the very least, references should be made to it in /usr/src/Makefile as
> part of the conversion process, and inthe /usr/src/UPDATING file.
I wouldn't object to it being publicized more than it is.. I don't have
a /usr/src/UPDATING file though, is that something new in 3.x?
> I would be willing to get permission from the author if people think it's
> a good idea.
*Wave* I don't think putting it in the base is really feasible, since
the chances of me getting commit privileges to do that are very small.
:) Besides, I would much rather see the installation routine modified to
include various things from the ports/packages tree rather than
continuing to add (arguably) non-critical things to the base. There are
a lot of people who install FreeBSD who don't upgrade very often, and to
them something like mergemaster would be bloat.
What I'd like to see is a section of sysinstall that asks what the user
is going to do with freebsd, and suggests some packages to install.
E.g., "Are you planning to upgrade your system on a regular basis?" Ok,
here's some things you should install, like cvsup, mergemaster, etc.
Doug
--
*** Chief Operations Officer, DALnet IRC network ***
Like desperadoes waiting for a train . . .
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Thu Jan 28 09:09:39 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id JAA12216
for freebsd-current-outgoing; Thu, 28 Jan 1999 09:09:39 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA12186
for <current@freebsd.org>; Thu, 28 Jan 1999 09:09:35 -0800 (PST)
(envelope-from jdp@polstra.com)
Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13])
by wall.polstra.com (8.9.1/8.9.1) with ESMTP id JAA07304
for <current@freebsd.org>; Thu, 28 Jan 1999 09:09:33 -0800 (PST)
(envelope-from jdp@polstra.com)
From: John Polstra <jdp@polstra.com>
Received: (from jdp@localhost)
by vashon.polstra.com (8.9.1/8.9.1) id JAA11280;
Thu, 28 Jan 1999 09:09:33 -0800 (PST)
(envelope-from jdp@polstra.com)
Date: Thu, 28 Jan 1999 09:09:33 -0800 (PST)
Message-Id: <199901281709.JAA11280@vashon.polstra.com>
To: current@FreeBSD.ORG
Subject: Re: -Wall -Wcast-qual and SYSINIT
Newsgroups: polstra.freebsd.current
In-Reply-To: <199901280753.XAA98980@apollo.backplane.com>
Organization: Polstra & Co., Seattle, WA
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
In article <199901280753.XAA98980@apollo.backplane.com>,
Matthew Dillon <dillon@apollo.backplane.com> wrote:
>
> Unfortunately, GCC isn't smart enough to match the function type
> to the correct structure - it always stuffs it into the first structure.
Don't blame GCC. The C standard requires it to behave the way it
does.
Anyway, GCC actually does have an extension that addresses this
problem. See "Labeled Elements in Initializers" in the info pages.
Note, this extension should NOT be used, in my opinion.
John
--
John Polstra jdp@polstra.com
John D. Polstra & Co., Inc. Seattle, Washington USA
"Nobody ever went broke underestimating the taste of the American public."
-- H. L. Mencken
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Thu Jan 28 09:28:44 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id JAA15082
for freebsd-current-outgoing; Thu, 28 Jan 1999 09:28:44 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA15077
for <current@FreeBSD.ORG>; Thu, 28 Jan 1999 09:28:42 -0800 (PST)
(envelope-from dillon@apollo.backplane.com)
Received: (from dillon@localhost)
by apollo.backplane.com (8.9.2/8.9.1) id JAA09568;
Thu, 28 Jan 1999 09:28:38 -0800 (PST)
(envelope-from dillon)
Date: Thu, 28 Jan 1999 09:28:38 -0800 (PST)
From: Matthew Dillon <dillon@apollo.backplane.com>
Message-Id: <199901281728.JAA09568@apollo.backplane.com>
To: John Polstra <jdp@polstra.com>
Cc: current@FreeBSD.ORG
Subject: Re: -Wall -Wcast-qual and SYSINIT
References: <199901281709.JAA11280@vashon.polstra.com>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
:Anyway, GCC actually does have an extension that addresses this
:problem. See "Labeled Elements in Initializers" in the info pages.
:Note, this extension should NOT be used, in my opinion.
:
:John
:--
: John Polstra jdp@polstra.com
: John D. Polstra & Co., Inc. Seattle, Washington USA
I'm going to clarify the situation by comitting a separation of
SYSINIT to SYSINIT ( for void * stuff ) and C_SYSINIT ( for const void *
stuff ). However, they will use the same structure and thus will
not address the warning at all. This is simply a clarification of
the problem. This is in sys/kernel.h, of course. The auxillary
macros, such as in sys/vnode.h, simply use the 'correct' *SYSINIT
macro.
What we need is a solution for C_SYSINIT that allows the const void *
callback and data case through without warning, but does not allow
the void * callback and data case. Just as the current SYSINIT case
allows the void * callback/data case without warning but complaints
on const void * callback/data.
-Matt
Matthew Dillon
<dillon@backplane.com>
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Thu Jan 28 09:38:36 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id JAA16719
for freebsd-current-outgoing; Thu, 28 Jan 1999 09:38:36 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from fleming.cs.strath.ac.uk (fleming.cs.strath.ac.uk [130.159.196.126])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA16690;
Thu, 28 Jan 1999 09:38:33 -0800 (PST)
(envelope-from roger@cs.strath.ac.uk)
Received: from cs.strath.ac.uk (posh.dmem.strath.ac.uk [130.159.202.3])
by fleming.cs.strath.ac.uk (8.8.8/8.8.8) with ESMTP id RAA08961
Thu, 28 Jan 1999 17:38:30 GMT
Message-ID: <36B0A093.B5173850@cs.strath.ac.uk>
Date: Thu, 28 Jan 1999 17:38:27 +0000
From: Roger Hardiman <roger@cs.strath.ac.uk>
Organization: Strathclyde University
X-Mailer: Mozilla 4.07 [en] (X11; I; FreeBSD 3.0-STABLE i386)
MIME-Version: 1.0
To: multimedia@FreeBSD.ORG, current@FreeBSD.ORG
Subject: Change to SVIDEO on bt848 driver
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
Hi,
I have finally corrected a long standing bug in the bt848 driver
with regard to selecting the SVIDEO input for true SVIDEO camera and for
the many normal cameras connected via the SVIDEO port (eg the bundled
hauppauge camera).
As a result some applications which select SVIDEO input sources and
incorrcetly used METEOR_INPUT_DEV2 for the METEORSFORMAT ioctl will now
see a monochrome picture.
The fix is to change the code to pass METEOR_INPUT_DEV_SVIDEO as the
parameter
for the METEORSFORMAT ioctl.
I know this fix is ok with vic but breaks fxtv 0.47 when used with true
s-video sources.
I have sent patches to Randall, but for now, you can download a new fxtv
tarball from me. This is available upon request to prevent a mixup of
official fxtv and 'rogers fxtv patch'.
email to roger@cs.strath.ac.uk please.
Thanks
Roger
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Thu Jan 28 09:42:31 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id JAA17337
for freebsd-current-outgoing; Thu, 28 Jan 1999 09:42:31 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from khavrinen.lcs.mit.edu (khavrinen.lcs.mit.edu [18.24.4.193])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA17292
for <freebsd-current@FreeBSD.ORG>; Thu, 28 Jan 1999 09:42:14 -0800 (PST)
(envelope-from wollman@khavrinen.lcs.mit.edu)
Received: (from wollman@localhost)
by khavrinen.lcs.mit.edu (8.9.1/8.9.1) id MAA17874;
Thu, 28 Jan 1999 12:41:10 -0500 (EST)
(envelope-from wollman)
Date: Thu, 28 Jan 1999 12:41:10 -0500 (EST)
From: Garrett Wollman <wollman@khavrinen.lcs.mit.edu>
Message-Id: <199901281741.MAA17874@khavrinen.lcs.mit.edu>
To: Robert Nordier <rnordier@nordier.com>
Cc: freebsd-current@FreeBSD.ORG
Subject: Re: "Argument by Authority"
In-Reply-To: <199901280348.FAA29674@ceia.nordier.com>
References: <19990128130131.J4819@freebie.lemis.com>
<199901280348.FAA29674@ceia.nordier.com>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
<<On Thu, 28 Jan 1999 05:48:31 +0200 (SAT), Robert Nordier <rnordier@nordier.com> said:
> | COMPATIBILITY
> | The rm utility differs from historical implementations in that
> | the -f option only masks attempts to remove non-existent
> | files instead of masking a large variety of errors.
I went down to our reading room and examined 1003.2. It says quite
clearly that `-f' has ONLY the following two effects:
1) Suppress warnings for non-existent files specified on the
command line.
2) Suppress interaction when removing an unwritable file even
when standard input is connected to a terminal.
It specifically requires that diagnostics be generated for any errors
resulting from unlink() or rmdir(). (The rationale dismisses the
historic behavior by describing it as ``hardly doing a service to
either shell programmers or interactive users''.)
The synopsis given is:
rm [-firR] file ...
...which indicates that at least one `file' argument is required. It
also indicates that `-f' and `-i' are not mutually exclusive.
Furthermore, 1003.2 prohibits our `-d' flag; `rm' is always required
to call rmdir() when a directory is specifed on the command line.
-GAWollman
--
Garrett A. Wollman | O Siem / We are all family / O Siem / We're all the same
wollman@lcs.mit.edu | O Siem / The fires of freedom
Opinions not those of| Dance in the burning flame
MIT, LCS, CRS, or NSA| - Susan Aglukark and Chad Irschick
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Thu Jan 28 09:44:31 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id JAA17510
for freebsd-current-outgoing; Thu, 28 Jan 1999 09:44:31 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from pau-amma.whistle.com (s205m64.whistle.com [207.76.205.64])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA17501
for <freebsd-current@freebsd.org>; Thu, 28 Jan 1999 09:44:29 -0800 (PST)
(envelope-from dhw@whistle.com)
Received: (from dhw@localhost)
by pau-amma.whistle.com (8.9.1/8.9.1) id JAA19684
for freebsd-current@freebsd.org; Thu, 28 Jan 1999 09:43:33 -0800 (PST)
(envelope-from dhw)
Date: Thu, 28 Jan 1999 09:43:33 -0800 (PST)
From: David Wolfskill <dhw@whistle.com>
Message-Id: <199901281743.JAA19684@pau-amma.whistle.com>
To: freebsd-current@FreeBSD.ORG
Subject: Re: DEVFS, the time has come...
In-Reply-To: <199901272212.XAA03458@yedi.iaf.nl>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
>From: Wilko Bulte <wilko@yedi.iaf.nl>
>Date: Wed, 27 Jan 1999 23:12:18 +0100 (CET)
>Yeagh... what is wrong with ed0, de0, fxp0 etc that needs changing? Is this
>just a matter of taste or is there more to it? I for one don't see any
>advantage in eth[0-9] style device naming.
It's a matter of whether you want the name to reflect the implementation
vs. the function.
For someone involved in the details of the implementation, being
(acutely!) aware of those details can be very important.
For someone who merely wants to have a certain physical port on the
machine connected to a particular network, that level of detail is not
always appropriate.
It depends on your focus.
Cheers,
david
--
David Wolfskill UNIX System Administrator
dhw@whistle.com voice: (650) 577-7158 pager: (650) 371-4621
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Thu Jan 28 09:55:04 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id JAA18457
for freebsd-current-outgoing; Thu, 28 Jan 1999 09:55:04 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from sasami.jurai.net (sasami.jurai.net [207.153.65.3])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA18423
for <current@FreeBSD.ORG>; Thu, 28 Jan 1999 09:54:57 -0800 (PST)
(envelope-from winter@jurai.net)
Received: from localhost (winter@localhost)
by sasami.jurai.net (8.8.8/8.8.7) with SMTP id MAA15493;
Thu, 28 Jan 1999 12:54:51 -0500 (EST)
Date: Thu, 28 Jan 1999 12:54:50 -0500 (EST)
From: "Matthew N. Dodd" <winter@jurai.net>
To: Matthew Dillon <dillon@apollo.backplane.com>
cc: current@FreeBSD.ORG
Subject: Re: Hmmm.. more on the eis ahb bug
In-Reply-To: <199901280111.RAA81035@apollo.backplane.com>
Message-ID: <Pine.BSF.4.02.9901281253580.8926-100000@sasami.jurai.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
On Wed, 27 Jan 1999, Matthew Dillon wrote:
> Could an Adaptec SCSI guru take a look at this code ? There's
> probably some poor sob running EISA who's scratching his head right
> now :-)
Hey!
Actually, my EISA box with a 1742 has been having weird lockups. Not sure
if that has anything to do with this bug.
--
| Matthew N. Dodd | 78 280Z | 75 164E | 84 245DL | FreeBSD/NetBSD/Sprite/VMS |
| winter@jurai.net | This Space For Rent | ix86,sparc,m68k,pmax,vax |
| http://www.jurai.net/~winter | Are you k-rad elite enough for my webpage? |
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Thu Jan 28 10:15:16 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id KAA21115
for freebsd-current-outgoing; Thu, 28 Jan 1999 10:15:16 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from bright.fx.genx.net (bright.fx.genx.net [206.64.4.154])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA21101
for <current@FreeBSD.ORG>; Thu, 28 Jan 1999 10:15:12 -0800 (PST)
(envelope-from bright@hotjobs.com)
Received: from localhost (bright@localhost)
by bright.fx.genx.net (8.9.1/8.9.1) with ESMTP id NAA20779;
Thu, 28 Jan 1999 13:21:01 -0500 (EST)
(envelope-from bright@hotjobs.com)
X-Authentication-Warning: bright.fx.genx.net: bright owned process doing -bs
Date: Thu, 28 Jan 1999 13:21:01 -0500 (EST)
From: Alfred Perlstein <bright@hotjobs.com>
X-Sender: bright@bright.fx.genx.net
To: Greg Lehey <grog@lemis.com>
cc: Bruce Evans <bde@zeta.org.au>, luigi@labinfo.iet.unipi.it,
current@FreeBSD.ORG, peter.jeremy@auss2.alcatel.com.au
Subject: Re: Nesting levels (was: indent(1) and style(9) (was: btokup() macro
in sys/malloc.h))
In-Reply-To: <19990128202106.I8473@freebie.lemis.com>
Message-ID: <Pine.BSF.4.05.9901281315190.81323-100000@bright.fx.genx.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
On Thu, 28 Jan 1999, Greg Lehey wrote:
> On Thursday, 28 January 1999 at 20:39:03 +1100, Bruce Evans wrote:
> >> See e.g. tcp_input.c ip_input.c and many network device drivers as
> >> an example -- basically all places where, for efficiency reasons,
> >> the code tries to expand in-line various block, the depth of
> >> indentation pushes everything to the right end leaving only 20-30
> >> useful chars per line.
> >
> > See the Linux style guide
>
> Wave a red rag at a bull?
:)
> > (linux/Documentation/CodingStyle) for strong opinions about this:
> > "if you need more than 3 levels of indentation, you're screwed
> > anyway, and should fix your program".
>
> I think this is the bottom line. If you're using 8 character indents,
> then yes, you're screwed. If you're using Microsoft and trying to
> write clever shell scripts, you're screwed too. Your tools limit what
> you can do. I believe that, in the matter of indentation, style(9)
> limits legibility to a point where you really are screwed if you have
> multiple indentation. But it's not because the code's bad.
I really wish style(9) had some suggestions for configuring editors to
make it easier to conform to the standards.
Telling people "add this to your exrc/gvimrc/emacsrc" would help people
trying to adopt the guidlines supplied in the manpage.
Anyone want to commit thier editor's rc file to some place in
/usr/share/examples?
It'd be much appreciated.
thanks,
-Alfred
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Thu Jan 28 10:54:31 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id KAA24454
for freebsd-current-outgoing; Thu, 28 Jan 1999 10:54:31 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from peach.ocn.ne.jp (peach.ocn.ne.jp [210.145.254.87])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA24448
for <freebsd-current@FreeBSD.ORG>; Thu, 28 Jan 1999 10:54:27 -0800 (PST)
(envelope-from dcs@newsguy.com)
Received: from newsguy.com by peach.ocn.ne.jp (8.9.1a/OCN) id DAA25260; Fri, 29 Jan 1999 03:54:12 +0900 (JST)
Message-ID: <36B0B085.114163@newsguy.com>
Date: Fri, 29 Jan 1999 03:46:29 +0900
From: "Daniel C. Sobral" <dcs@newsguy.com>
X-Mailer: Mozilla 4.5 [en] (Win98; I)
X-Accept-Language: pt-BR,ja
MIME-Version: 1.0
To: Patrick Hartling <mystify@friley-184-92.res.iastate.edu>
CC: freebsd-current@FreeBSD.ORG
Subject: Re: Reading a text file with BTX
References: <199901281610.KAA04600@friley-184-92.res.iastate.edu>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
Patrick Hartling wrote:
>
> Is there a way to view the contents of a text file (specifically,
> /boot/loader.rc) with BTX? Now that there are all these nifty new modules,
> my kernel is a lot smaller and my /boot/loader.rc is a lot longer. The way
> I have my /boot/loader.rc setup is such that it unloads everythin
> automatically loaded if I drop to the BTX prompt instead of autobooting.
> This is fairly convenient except when I want to boot an alternate kernel but
> still load all the same modules that I use in my default kernel. If there
> isn't such a feature, it would be really nice if there were a 'cat' command
> or something along those lines so that I could read the contents of
> /boot/loader.rc and get everything properly reloaded by hand. Could it be
> added or could I just make my own somehow? Thanks a bunch.
You might be refering to the loader prompt, not the btx prompt. If
you type something as soon as the first "|" is shown, that's btx. If
you wait a little, or enter /boot/loader, then you get loader.
Specifically, if it has processed loader.rc, then you are inside
loader, not btx.
Loader has a command called "autoboot", which runs by default with
10 seconds wait. This one shows a countdown of seconds. If you
interrupt here, you are in loader.
Now, I don't know about btx, but here is what is in for you with
loader...
Conditional loading is possible, though Mike committed it to
RELENG_3 instead of -current, and has not corrected that yet.
bin/9662, in case you want. You can put that code inside
/boot/boot.4th, and it will be loaded before loader.rc, so you
*could* use it inside loader.rc. Unfortunately, *that* still doesn't
work. I have it almost working on my system. I think I'm down to the
last bug (I think that because it works perfectly as long as no
error happens inside the script).
Showing contents of a file happens to be possible too, as soon as
bin/9753 gets in. Jordan promised cat and more for us, but since he
is too busy with his update targets, I decided to get "more" in. :-)
--
Daniel C. Sobral (8-DCS)
dcs@newsguy.com
If you sell your soul to the Devil and all you get is an MCSE from
it, you haven't gotten market rate.
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Thu Jan 28 11:12:57 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id LAA26780
for freebsd-current-outgoing; Thu, 28 Jan 1999 11:12:57 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from friley-184-92.res.iastate.edu (friley-184-92.res.iastate.edu [129.186.184.92])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA26768
for <freebsd-current@FreeBSD.ORG>; Thu, 28 Jan 1999 11:12:55 -0800 (PST)
(envelope-from mystify@friley-184-92.res.iastate.edu)
Received: from friley-184-92.res.iastate.edu (localhost.res.iastate.edu [127.0.0.1])
by friley-184-92.res.iastate.edu (8.9.2/8.9.1) with ESMTP id NAA05304;
Thu, 28 Jan 1999 13:10:19 -0600 (CST)
(envelope-from mystify@friley-184-92.res.iastate.edu)
Message-Id: <199901281910.NAA05304@friley-184-92.res.iastate.edu>
To: "Daniel C. Sobral" <dcs@newsguy.com>
cc: freebsd-current@FreeBSD.ORG
Subject: Re: Reading a text file with BTX
In-reply-to: Message from "Daniel C. Sobral" <dcs@newsguy.com>
of "Fri, 29 Jan 1999 03:46:29 +0900." <36B0B085.114163@newsguy.com>
Date: Thu, 28 Jan 1999 13:10:19 -0600
From: Patrick Hartling <mystify@friley-184-92.res.iastate.edu>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
"Daniel C. Sobral" <dcs@newsguy.com> wrote:
} Patrick Hartling wrote:
} >
} > Is there a way to view the contents of a text file (specifically,
} > /boot/loader.rc) with BTX? Now that there are all these nifty new modules,
} > my kernel is a lot smaller and my /boot/loader.rc is a lot longer. The way
} > I have my /boot/loader.rc setup is such that it unloads everythin
} > automatically loaded if I drop to the BTX prompt instead of autobooting.
} > This is fairly convenient except when I want to boot an alternate kernel but
} > still load all the same modules that I use in my default kernel. If there
} > isn't such a feature, it would be really nice if there were a 'cat' command
} > or something along those lines so that I could read the contents of
} > /boot/loader.rc and get everything properly reloaded by hand. Could it be
} > added or could I just make my own somehow? Thanks a bunch.
}
} You might be refering to the loader prompt, not the btx prompt. If
} you type something as soon as the first "|" is shown, that's btx. If
} you wait a little, or enter /boot/loader, then you get loader.
} Specifically, if it has processed loader.rc, then you are inside
} loader, not btx.
Ah, I see. Sorry for using the wrong name, but you did figure out what I
meant which is good. :)
} Showing contents of a file happens to be possible too, as soon as
} bin/9753 gets in. Jordan promised cat and more for us, but since he
} is too busy with his update targets, I decided to get "more" in. :-)
Cool beans, that's what I was curious about. Thanks for the info.
-Patrick
Patrick L. Hartling | Research Assistant, ICEMT
mystify@friley-184-92.res.iastate.edu | Carver Lab - 0095E Black Engineering
http://www.public.iastate.edu/~oz/ | http://www.icemt.iastate.edu/
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Thu Jan 28 11:32:36 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id LAA29353
for freebsd-current-outgoing; Thu, 28 Jan 1999 11:32:36 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from uni4nn.gn.iaf.nl (osmium.gn.iaf.nl [193.67.144.12])
by hub.freebsd.org (8.8.8/8.8.8) with SMTP id LAA29346
for <current@FreeBSD.ORG>; Thu, 28 Jan 1999 11:32:33 -0800 (PST)
(envelope-from wilko@yedi.iaf.nl)
Received: by uni4nn.gn.iaf.nl with UUCP id AA09518
(5.67b/IDA-1.5); Thu, 28 Jan 1999 20:15:11 +0100
Received: (from wilko@localhost) by yedi.iaf.nl (8.8.8/8.6.12) id TAA00473; Thu, 28 Jan 1999 19:31:21 +0100 (CET)
From: Wilko Bulte <wilko@yedi.iaf.nl>
Message-Id: <199901281831.TAA00473@yedi.iaf.nl>
Subject: Re: DEVFS, the time has come...
In-Reply-To: <7987.917514435@verdi.nethelp.no> from "sthaug@nethelp.no" at "Jan 28, 99 10:07:15 am"
To: sthaug@nethelp.no
Date: Thu, 28 Jan 1999 19:31:21 +0100 (CET)
Cc: archie@whistle.com, dfr@nlsystems.com, current@FreeBSD.ORG
X-Organisation: Private FreeBSD site - Arnhem, The Netherlands
X-Pgp-Info: PGP public key at 'finger wilko@freefall.freebsd.org'
X-Mailer: ELM [version 2.4ME+ PL38 (25)]
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
As sthaug@nethelp.no wrote...
> > > I agree.. and same thing goes for Ethernet drivers. I actually
> > > like the way Linux always has "eth0", "eth1", ... (which we could
> >
> > Yeagh... what is wrong with ed0, de0, fxp0 etc that needs changing? Is this
> > just a matter of taste or is there more to it? I for one don't see any
> > advantage in eth[0-9] style device naming.
>
> I can give you one example. We run a FreeBSD box here which receives
> all of the traffic (port mirroring) from some Ethernet switches. On
> the FreeBSD box, we run nnstat, tcpdump etc. for monitoring purposes.
>
> Recently I changed some of the DEC 21x4x based cards on this box to
> Intel cards. Thus the interface names changed from deN to fxpN. This
> meant we had to update a bunch of Perl and shell scripts. It would
> have been much nicer (no need to update) if the interfaces were simply
> named ethN.
Hmmm. Well I happen to like the concept of being able to tell straight
away what device I'm talking to. eth# style naming does not allow that.
But I can understand that other people might feel otherwise.
Wilko
_ ______________________________________________________________________
| / o / / _ Bulte email: wilko@yedi.iaf.nl
|/|/ / / /( (_) Arnhem, The Netherlands WWW : http://www.tcja.nl
______________________________________________ Powered by FreeBSD __________
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Thu Jan 28 11:32:53 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id LAA29390
for freebsd-current-outgoing; Thu, 28 Jan 1999 11:32:53 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from uni4nn.gn.iaf.nl (osmium.gn.iaf.nl [193.67.144.12])
by hub.freebsd.org (8.8.8/8.8.8) with SMTP id LAA29385
for <current@FreeBSD.ORG>; Thu, 28 Jan 1999 11:32:51 -0800 (PST)
(envelope-from wilko@yedi.iaf.nl)
Received: by uni4nn.gn.iaf.nl with UUCP id AA09524
(5.67b/IDA-1.5); Thu, 28 Jan 1999 20:15:12 +0100
Received: (from wilko@localhost) by yedi.iaf.nl (8.8.8/8.6.12) id TAA00524; Thu, 28 Jan 1999 19:38:45 +0100 (CET)
From: Wilko Bulte <wilko@yedi.iaf.nl>
Message-Id: <199901281838.TAA00524@yedi.iaf.nl>
Subject: Re: DEVFS, the time has come...
In-Reply-To: <XFMail.990128155952.doconnor@gsoft.com.au> from Daniel O'Connor at "Jan 28, 99 03:59:52 pm"
To: doconnor@gsoft.com.au (Daniel O'Connor)
Date: Thu, 28 Jan 1999 19:38:45 +0100 (CET)
Cc: current@FreeBSD.ORG, dfr@nlsystems.com, archie@whistle.com
X-Organisation: Private FreeBSD site - Arnhem, The Netherlands
X-Pgp-Info: PGP public key at 'finger wilko@freefall.freebsd.org'
X-Mailer: ELM [version 2.4ME+ PL38 (25)]
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
As Daniel O'Connor wrote...
> On 27-Jan-99 Wilko Bulte wrote:
> > > I agree.. and same thing goes for Ethernet drivers. I actually
> > > like the way Linux always has "eth0", "eth1", ... (which we could
> > Yeagh... what is wrong with ed0, de0, fxp0 etc that needs changing? Is this
> > just a matter of taste or is there more to it? I for one don't see any
> > advantage in eth[0-9] style device naming.
> Well, for one its sucks trying to get newbies to work out what their network card is
> called..
Not true IMO. You still need to know what hardware you have before you can build your
own kernels etc etc.
> Also the eth[0..x] thing means you can replace your ethernet card with a new one of a
> different type without having to look through your config code for references to ed0 or
> whatever.
True.
> Another thing.. we get to be more Linux like, which is a good thing, right? *duck*
Ducking does not help with todays laser-guided precision ammo ;-) ;-)
And to answer your question: the day FreeBSD aims to become like Linux
I'm likely to install NT.
Wilko
_ ______________________________________________________________________
| / o / / _ Bulte email: wilko@yedi.iaf.nl
|/|/ / / /( (_) Arnhem, The Netherlands WWW : http://www.tcja.nl
______________________________________________ Powered by FreeBSD __________
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Thu Jan 28 11:34:23 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id LAA29667
for freebsd-current-outgoing; Thu, 28 Jan 1999 11:34:23 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from uni4nn.gn.iaf.nl (osmium.gn.iaf.nl [193.67.144.12])
by hub.freebsd.org (8.8.8/8.8.8) with SMTP id LAA29662
for <current@FreeBSD.ORG>; Thu, 28 Jan 1999 11:34:19 -0800 (PST)
(envelope-from wilko@yedi.iaf.nl)
Received: by uni4nn.gn.iaf.nl with UUCP id AA09584
(5.67b/IDA-1.5); Thu, 28 Jan 1999 20:15:25 +0100
Received: (from wilko@localhost) by yedi.iaf.nl (8.8.8/8.6.12) id TAA00482; Thu, 28 Jan 1999 19:33:12 +0100 (CET)
From: Wilko Bulte <wilko@yedi.iaf.nl>
Message-Id: <199901281833.TAA00482@yedi.iaf.nl>
Subject: Re: cvs commit: src/sys/i386/eisa ahb.c
In-Reply-To: <83910.917513301@zippy.cdrom.com> from "Jordan K. Hubbard" at "Jan 28, 99 00:48:21 am"
To: jkh@zippy.cdrom.com (Jordan K. Hubbard)
Date: Thu, 28 Jan 1999 19:33:12 +0100 (CET)
Cc: dillon@apollo.backplane.com, archie@whistle.com, current@FreeBSD.ORG
X-Organisation: Private FreeBSD site - Arnhem, The Netherlands
X-Pgp-Info: PGP public key at 'finger wilko@freefall.freebsd.org'
X-Mailer: ELM [version 2.4ME+ PL38 (25)]
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
As Jordan K. Hubbard wrote...
> > How Mr. ignoromous Nate could construe this to mean that I was trying
> > to brush something under the rug is beyond me. As I said to Julian,
> > I probably shouldn't have made the committ, but the fact is that I
> > not only left the module on my hotlist, I also immediately brought
> > the potential problem to the attention of the entire list and thence,
>
> I think this whole tangled thread can probably be summed up thusly:
>
> There will always be those remarking from the sidelines about any
> change which goes into the FreeBSD source tree, and I do mean ANY
> change, the amount of commentary usually in inverse proportion to the
> importance of the change. This is just a given. It's also a given
> that some of these people will have far less clue than others and even
> those who have a clue will often express their comments in such a way
> as to come across as criticising or carping, even though they may not
> have meant to. There are a lot of engineers here and human
> interaction is rarely their strong suit.
>
> In any case, rather than getting into a protracted furball with each
> and every commentator and perhaps using inappropriate language in a
> public mailing list in the process, you've gotta do what pro golfers
> and ballplayers do - learn to ignore the crowd when it hasn't got
Ah, you mean like John McEnroe ? ;-)
Wilko
_ ______________________________________________________________________
| / o / / _ Bulte email: wilko@yedi.iaf.nl
|/|/ / / /( (_) Arnhem, The Netherlands WWW : http://www.tcja.nl
______________________________________________ Powered by FreeBSD __________
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Thu Jan 28 11:50:44 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id LAA02267
for freebsd-current-outgoing; Thu, 28 Jan 1999 11:50:44 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA02247
for <current@FreeBSD.ORG>; Thu, 28 Jan 1999 11:50:38 -0800 (PST)
(envelope-from julian@whistle.com)
Received: (from daemon@localhost)
by alpo.whistle.com (8.8.5/8.8.5) id LAA11086
for <current@FreeBSD.ORG>; Thu, 28 Jan 1999 11:48:28 -0800 (PST)
Received: from s204m82.isp.whistle.com(207.76.204.82)
via SMTP by alpo.whistle.com, id smtpdn11082; Thu Jan 28 19:48:26 1999
Date: Thu, 28 Jan 1999 11:48:23 -0800 (PST)
From: Julian Elischer <julian@whistle.com>
X-Sender: julian@s204m82.isp.whistle.com
To: current@FreeBSD.ORG
Subject: Re: btokup().. patch to STYLE(9) (fwd)
In-Reply-To: <Pine.BSF.4.05.9901280335450.304-100000@s204m82.isp.whistle.com>
Message-ID: <Pine.BSF.4.05.9901281147360.304-100000@s204m82.isp.whistle.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
On Thu, 28 Jan 1999, Julian Elischer wrote:
>
> Some people when confronted by people wanting to have extra braces
> say "change style(9)".
>
Amazingly there hasn't been a SINGLE comment!
(after a whole 8 hours!)
julian
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Thu Jan 28 11:56:54 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id LAA03129
for freebsd-current-outgoing; Thu, 28 Jan 1999 11:56:54 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from whistle.com (s205m131.whistle.com [207.76.205.131])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA03124
for <current@FreeBSD.ORG>; Thu, 28 Jan 1999 11:56:50 -0800 (PST)
(envelope-from archie@whistle.com)
Received: (from smap@localhost) by whistle.com (8.7.5/8.6.12) id LAA08399; Thu, 28 Jan 1999 11:56:36 -0800 (PST)
Received: from bubba.whistle.com( 207.76.205.7) by whistle.com via smap (V2.0)
id xma008388; Thu, 28 Jan 99 11:56:13 -0800
Received: (from archie@localhost) by bubba.whistle.com (8.8.7/8.6.12) id LAA22422; Thu, 28 Jan 1999 11:56:12 -0800 (PST)
From: Archie Cobbs <archie@whistle.com>
Message-Id: <199901281956.LAA22422@bubba.whistle.com>
Subject: Re: btokup().. patch to STYLE(9) (fwd)
In-Reply-To: <Pine.BSF.4.05.9901280335450.304-100000@s204m82.isp.whistle.com> from Julian Elischer at "Jan 28, 99 03:38:31 am"
To: julian@whistle.com (Julian Elischer)
Date: Thu, 28 Jan 1999 11:56:12 -0800 (PST)
Cc: current@FreeBSD.ORG
X-Mailer: ELM [version 2.4ME+ PL38 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
Julian Elischer writes:
> Some people when confronted by people wanting to have extra braces
> say "change style(9)".
>
> Well, here is my change..
You can count my vote.
I would also add a paragraph like this:
If possible code should complile cleanly with gcc's -Wall flag.
Note however that this does not imply that it's OK to eliminate
warnings simply by covering them up with typecasts, etc., as that
actually does more harm than good.
I hope that wording is sufficiently unoffensive to the -Wall haters.
-Archie
___________________________________________________________________________
Archie Cobbs * Whistle Communications, Inc. * http://www.whistle.com
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Thu Jan 28 12:02:29 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id MAA04148
for freebsd-current-outgoing; Thu, 28 Jan 1999 12:02:29 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from cs.ucla.edu (Ulfus.CS.UCLA.EDU [131.179.48.35])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA04122
for <freebsd-current@freebsd.org>; Thu, 28 Jan 1999 12:02:26 -0800 (PST)
(envelope-from scottm@ulfus.cs.ucla.edu)
Received: from ulfus.cs.ucla.edu (localhost [127.0.0.1])
by cs.ucla.edu (8.8.7/8.8.8) with ESMTP id MAA11620;
Thu, 28 Jan 1999 12:01:57 -0800
Message-Id: <199901282001.MAA11620@cs.ucla.edu>
X-Mailer: exmh version 2.0.2
To: Wilko Bulte <wilko@yedi.iaf.nl>
cc: freebsd-current@FreeBSD.ORG
Subject: Re: DEVFS, the time has come...
In-Reply-To: Your message of "Thu, 28 Jan 1999 19:38:45 +0100."
<199901281838.TAA00524@yedi.iaf.nl>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Thu, 28 Jan 1999 12:01:57 -0800
From: Scott Michel <scottm@ulfus.cs.ucla.edu>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
> Not true IMO. You still need to know what hardware you have before you
> can build your own kernels etc etc.
>
> > Also the eth[0..x] thing means you can replace your ethernet card
> > with a new one of a different type without having to look through
> > your config code for references to ed0 or whatever.
>
> True.
There's no reason why the devfs code couldn't create the equivalent
of symbolic links in its file system so that ed0 and eth0 show up.
Yes, I know, this opens up a can of worms when new hardware is added
and suddenly the probe order changes such that a newbie finds that
eth0 is no longer what he/she/it thought it was going to be. But it's
a start.
-scooter
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Thu Jan 28 12:07:02 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id MAA05125
for freebsd-current-outgoing; Thu, 28 Jan 1999 12:07:02 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from earth.wnm.net (earth.wnm.net [208.246.240.243])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA05110
for <freebsd-current@freebsd.org>; Thu, 28 Jan 1999 12:07:00 -0800 (PST)
(envelope-from jrz@WNM.NET)
Received: from earth.wnm.net (earth.wnm.net [208.246.240.243])
by earth.wnm.net (8.8.8/8.8.8) with SMTP id OAA16495
for <freebsd-current@freebsd.org>; Thu, 28 Jan 1999 14:14:21 -0600 (CST)
Date: Thu, 28 Jan 1999 14:14:21 -0600 (CST)
From: Jacob Zehnder <jrz@WNM.NET>
To: freebsd-current@FreeBSD.ORG
Subject: subscribe
Message-ID: <Pine.BSI.3.95.990128141412.16482A-100000@earth.wnm.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Thu Jan 28 12:07:42 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id MAA05238
for freebsd-current-outgoing; Thu, 28 Jan 1999 12:07:42 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA05228
for <current@FreeBSD.ORG>; Thu, 28 Jan 1999 12:07:40 -0800 (PST)
(envelope-from jkh@zippy.cdrom.com)
Received: from zippy.cdrom.com (localhost.cdrom.com [127.0.0.1])
by zippy.cdrom.com (8.9.2/8.9.1) with ESMTP id MAA04613;
Thu, 28 Jan 1999 12:07:11 -0800 (PST)
To: Wilko Bulte <wilko@yedi.iaf.nl>
cc: dillon@apollo.backplane.com, archie@whistle.com, current@FreeBSD.ORG
Subject: Re: cvs commit: src/sys/i386/eisa ahb.c
In-reply-to: Your message of "Thu, 28 Jan 1999 19:33:12 +0100."
<199901281833.TAA00482@yedi.iaf.nl>
Date: Thu, 28 Jan 1999 12:07:11 -0800
Message-ID: <4610.917554031@zippy.cdrom.com>
From: "Jordan K. Hubbard" <jkh@zippy.cdrom.com>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
> Ah, you mean like John McEnroe ? ;-)
Specifically NOT like John McEnroe. :-)
- Jordan
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Thu Jan 28 12:09:49 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id MAA05478
for freebsd-current-outgoing; Thu, 28 Jan 1999 12:09:49 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from earth.wnm.net (earth.wnm.net [208.246.240.243])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA05471
for <freebsd-current@freebsd.org>; Thu, 28 Jan 1999 12:09:47 -0800 (PST)
(envelope-from jrz@WNM.NET)
Received: from earth.wnm.net (earth.wnm.net [208.246.240.243])
by earth.wnm.net (8.8.8/8.8.8) with SMTP id OAA16635
for <freebsd-current@freebsd.org>; Thu, 28 Jan 1999 14:17:09 -0600 (CST)
Date: Thu, 28 Jan 1999 14:17:09 -0600 (CST)
From: Jacob Zehnder <jrz@WNM.NET>
To: freebsd-current@FreeBSD.ORG
Message-ID: <Pine.BSI.3.95.990128141658.16629A-100000@earth.wnm.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
subscribe
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Thu Jan 28 12:38:33 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id MAA10413
for freebsd-current-outgoing; Thu, 28 Jan 1999 12:38:33 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from resnet.uoregon.edu (resnet.uoregon.edu [128.223.144.32])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA10408
for <current@FreeBSD.ORG>; Thu, 28 Jan 1999 12:38:30 -0800 (PST)
(envelope-from dwhite@resnet.uoregon.edu)
Received: from localhost (dwhite@localhost)
by resnet.uoregon.edu (8.8.8/8.8.8) with ESMTP id MAA21974;
Thu, 28 Jan 1999 12:38:03 -0800 (PST)
(envelope-from dwhite@resnet.uoregon.edu)
Date: Thu, 28 Jan 1999 12:38:02 -0800 (PST)
From: Doug White <dwhite@resnet.uoregon.edu>
To: "Jordan K. Hubbard" <jkh@zippy.cdrom.com>
cc: "D. Rock" <rock@cs.uni-sb.de>, current@FreeBSD.ORG
Subject: Re: No CD-ROM support in boot.flp?
In-Reply-To: <79650.917447176@zippy.cdrom.com>
Message-ID: <Pine.BSF.4.03.9901281235470.13474-100000@resnet.uoregon.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
On Wed, 27 Jan 1999, Jordan K. Hubbard wrote:
> > Are there any plans to create another boot disk (cdrom.flp?), 2.88MB
> > in size especially for CD-ROM boots?
>
> Yes.
Yummy. Reminds me of the atapi.flp fiasco a few years back. :-(
Doug White
Internet: dwhite@resnet.uoregon.edu | FreeBSD: The Power to Serve
http://gladstone.uoregon.edu/~dwhite | www.freebsd.org
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Thu Jan 28 12:54:40 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id MAA13591
for freebsd-current-outgoing; Thu, 28 Jan 1999 12:54:40 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from alcanet.com.au (border.alcanet.com.au [203.62.196.10])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA13565
for <current@FreeBSD.ORG>; Thu, 28 Jan 1999 12:54:33 -0800 (PST)
(envelope-from peter.jeremy@auss2.alcatel.com.au)
Received: by border.alcanet.com.au id <40330>; Fri, 29 Jan 1999 07:44:52 +1100
Date: Fri, 29 Jan 1999 07:54:18 +1100
From: Peter Jeremy <peter.jeremy@auss2.alcatel.com.au>
Subject: Re: indent(1) and style(9) (was: btokup() macro in sys/malloc.h)
To: current@FreeBSD.ORG
Message-Id: <99Jan29.074452est.40330@border.alcanet.com.au>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
Luigi Rizzo <luigi@labinfo.iet.unipi.it>
>not speaking about vinum, but to me, the indentation of 8 char and
>line length of 80 chars are almost mutually exclusive.
>
>See e.g. tcp_input.c ip_input.c and many network device drivers as
>an example -- basically all places where, for efficiency reasons,
>the code tries to expand in-line various block,
According to most of the coding standards I've read, readability
(and hence maintainability) come before efficiency. That said, I
agree that efficiency _is_ an issue within the kernel's critical
paths (the TCP/IP code being one).
Judicious use of inline functions (and macros) should help move
code to the left - and may even make it more understandable.
Peter
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Thu Jan 28 12:59:26 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id MAA14293
for freebsd-current-outgoing; Thu, 28 Jan 1999 12:59:26 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from uni4nn.gn.iaf.nl (osmium.gn.iaf.nl [193.67.144.12])
by hub.freebsd.org (8.8.8/8.8.8) with SMTP id MAA14283
for <freebsd-current@FreeBSD.ORG>; Thu, 28 Jan 1999 12:59:21 -0800 (PST)
(envelope-from wilko@yedi.iaf.nl)
Received: by uni4nn.gn.iaf.nl with UUCP id AA13558
(5.67b/IDA-1.5); Thu, 28 Jan 1999 21:31:52 +0100
Received: (from wilko@localhost) by yedi.iaf.nl (8.8.8/8.6.12) id VAA01522; Thu, 28 Jan 1999 21:04:25 +0100 (CET)
From: Wilko Bulte <wilko@yedi.iaf.nl>
Message-Id: <199901282004.VAA01522@yedi.iaf.nl>
Subject: Re: DEVFS, the time has come...
In-Reply-To: <199901281743.JAA19684@pau-amma.whistle.com> from David Wolfskill at "Jan 28, 99 09:43:33 am"
To: dhw@whistle.com (David Wolfskill)
Date: Thu, 28 Jan 1999 21:04:24 +0100 (CET)
Cc: freebsd-current@FreeBSD.ORG
X-Organisation: Private FreeBSD site - Arnhem, The Netherlands
X-Pgp-Info: PGP public key at 'finger wilko@freefall.freebsd.org'
X-Mailer: ELM [version 2.4ME+ PL38 (25)]
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
As David Wolfskill wrote...
> >From: Wilko Bulte <wilko@yedi.iaf.nl>
> >Date: Wed, 27 Jan 1999 23:12:18 +0100 (CET)
>
> >Yeagh... what is wrong with ed0, de0, fxp0 etc that needs changing? Is this
> >just a matter of taste or is there more to it? I for one don't see any
> >advantage in eth[0-9] style device naming.
>
> It's a matter of whether you want the name to reflect the implementation
> vs. the function.
>
> For someone involved in the details of the implementation, being
> (acutely!) aware of those details can be very important.
Guilty your honor ;-) My daily work is in supporting customers, so I can
really do without mapping 'convenient names' to physical stuff. For
an example: look at the Solaris symlink jungle for device naming.
> For someone who merely wants to have a certain physical port on the
> machine connected to a particular network, that level of detail is not
> always appropriate.
>
> It depends on your focus.
Agreed.
Wilko
_ ______________________________________________________________________
| / o / / _ Bulte email: wilko@yedi.iaf.nl
|/|/ / / /( (_) Arnhem, The Netherlands WWW : http://www.tcja.nl
______________________________________________ Powered by FreeBSD __________
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Thu Jan 28 13:05:53 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id NAA15609
for freebsd-current-outgoing; Thu, 28 Jan 1999 13:05:53 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from alcanet.com.au (border.alcanet.com.au [203.62.196.10])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA15598
for <current@FreeBSD.ORG>; Thu, 28 Jan 1999 13:05:50 -0800 (PST)
(envelope-from peter.jeremy@auss2.alcatel.com.au)
Received: by border.alcanet.com.au id <40324>; Fri, 29 Jan 1999 07:56:09 +1100
Date: Fri, 29 Jan 1999 08:05:37 +1100
From: Peter Jeremy <peter.jeremy@auss2.alcatel.com.au>
Subject: Re: btokup().. patch to STYLE(9) (fwd)
To: julian@whistle.com
Cc: current@FreeBSD.ORG
Message-Id: <99Jan29.075609est.40324@border.alcanet.com.au>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
Julian Elischer <julian@whistle.com> wrote:
>Well, here is my change..
I think it's a good move and I'll support it (FWIW).
>@@ -256,13 +256,23 @@
> .Ed
> .Pp
> Space after keywords (if, while, for, return, switch). No braces are
>-used for control statements with zero or only a single statement.
>+used for control statements with zero or only a single statement unless that
>+statement is more than a single line in which case they are permitted.
^^^^^^^^^
I'd prefer `recommended'.
And sometime later he wrote:
>Amazingly there hasn't been a SINGLE comment!
>(after a whole 8 hours!)
I'd treat that as total agreement and commit the change :-).
Everyone's probably still recovering from our latest flamefest (how
about we get Jordan to create a FreeBSD-flame list to allow people to
try out the latest fashion in asbestos clothing and supercharged
flamethrowers).
Peter
--
Peter Jeremy (VK2PJ) peter.jeremy@alcatel.com.au
Alcatel Australia Limited
41 Mandible St Phone: +61 2 9690 5019
ALEXANDRIA NSW 2015 Fax: +61 2 9690 5982
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Thu Jan 28 13:07:54 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id NAA16056
for freebsd-current-outgoing; Thu, 28 Jan 1999 13:07:54 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from bright.fx.genx.net (bright.fx.genx.net [206.64.4.154])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA16030
for <current@FreeBSD.ORG>; Thu, 28 Jan 1999 13:07:46 -0800 (PST)
(envelope-from bright@hotjobs.com)
Received: from localhost (bright@localhost)
by bright.fx.genx.net (8.9.1/8.9.1) with ESMTP id QAA38573;
Thu, 28 Jan 1999 16:12:53 -0500 (EST)
(envelope-from bright@hotjobs.com)
X-Authentication-Warning: bright.fx.genx.net: bright owned process doing -bs
Date: Thu, 28 Jan 1999 16:12:53 -0500 (EST)
From: Alfred Perlstein <bright@hotjobs.com>
X-Sender: bright@bright.fx.genx.net
To: sthaug@nethelp.no
cc: wilko@yedi.iaf.nl, archie@whistle.com, dfr@nlsystems.com,
current@FreeBSD.ORG
Subject: Re: DEVFS, the time has come...
In-Reply-To: <7987.917514435@verdi.nethelp.no>
Message-ID: <Pine.BSF.4.05.9901281610530.81323-100000@bright.fx.genx.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
On Thu, 28 Jan 1999 sthaug@nethelp.no wrote:
> > > I agree.. and same thing goes for Ethernet drivers. I actually
> > > like the way Linux always has "eth0", "eth1", ... (which we could
> >
> > Yeagh... what is wrong with ed0, de0, fxp0 etc that needs changing? Is this
> > just a matter of taste or is there more to it? I for one don't see any
> > advantage in eth[0-9] style device naming.
>
> I can give you one example. We run a FreeBSD box here which receives
> all of the traffic (port mirroring) from some Ethernet switches. On
> the FreeBSD box, we run nnstat, tcpdump etc. for monitoring purposes.
>
> Recently I changed some of the DEC 21x4x based cards on this box to
> Intel cards. Thus the interface names changed from deN to fxpN. This
> meant we had to update a bunch of Perl and shell scripts. It would
> have been much nicer (no need to update) if the interfaces were simply
> named ethN.
That's why you don't hard code the interfaces into all the scripts.
Instead source a file that gives the definitions ala rc.conf.
> Personally, I'd also prefer to have IDE disks named daN, but that's
> another matter...
:)
-Alfred
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Thu Jan 28 13:14:26 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id NAA17386
for freebsd-current-outgoing; Thu, 28 Jan 1999 13:14:26 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from speed.rcc.on.ca (radio163.mipps.net [205.189.197.163] (may be forged))
by hub.freebsd.org (8.8.8/8.8.8) with SMTP id NAA17381
for <current@freebsd.org>; Thu, 28 Jan 1999 13:14:24 -0800 (PST)
(envelope-from oscentral@usa.net)
Received: from HOMER.rcc.net (homer [205.189.197.165]) by speed.rcc.on.ca (8.6.12/8.6.9) with SMTP id RAA32294 for <current@freebsd.org>; Thu, 28 Jan 1999 17:23:33 -0500
Date: Thu, 28 Jan 1999 17:23:33 -0500
Message-Id: <199901282223.RAA32294@speed.rcc.on.ca>
X-Sender: tr49986@rcc.on.ca
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
To: current@FreeBSD.ORG
From: oscentral@usa.net (Rod Taylor)
Subject: Ne2000 PCI Card
X-Mailer: <PC Eudora Version 1.4>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
I have 2 cheap 100mbit nics (rj45 only). Both use the ReaTek 8139 chipset
(from the best that I can tell). Both are PCI.
I've attempted to use both cards in several PCI slots, under 2.2.8 and 3.0
boot floppies, and a 3.0-stable (updated 2 days ago). None of these
releases found either card in any situation.
I believe the card should be detected as Ed0 (possibly ed1). I have used
3com pci cards in both machines under freebsd sucessfully and the ne2000
cards function under windows and os/2.
What can I do? If someone wants to see, I'm willing to give root to a
person who wishes to help fix this problem (or make appropriate additions to
the driver). Have any changes been applied to 4.0-current which may solve
my situation?
Tried to get help in #freebsd in efnet, but no-one had suggestions that
helped me... (Thanks anyhow Xanne)
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Thu Jan 28 13:30:48 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id NAA19901
for freebsd-current-outgoing; Thu, 28 Jan 1999 13:30:48 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from highwind.com (hurricane.highwind.com [209.61.45.50])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA19892
for <current@FreeBSD.ORG>; Thu, 28 Jan 1999 13:30:44 -0800 (PST)
(envelope-from info@highwind.com)
Received: (from info@localhost)
by highwind.com (8.8.6/8.8.6) id QAA13214;
Thu, 28 Jan 1999 16:30:30 -0500 (EST)
Date: Thu, 28 Jan 1999 16:30:30 -0500 (EST)
Message-Id: <199901282130.QAA13214@highwind.com>
From: HighWind Software Information <info@highwind.com>
To: current@FreeBSD.ORG
Subject: Locked at 100% User CPU
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
In libc_r, I don't think the code in uthread_kern.c's
_thread_kern_select() scales at all.
As the number of network connections (TCP) to my application grows, I
believe this routine takes longer and longer and my CPU goes to 100%
user space.
Something makes me believe that this routine has an n^2 (or worse)
problem. Seems to relate to the number of fd's to select() on. At
about 300-400, even a P2 400Mhz gets max'd out and gets nothing done.
Anybody have a feeling as to what is wrong here?
-Rob
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Thu Jan 28 13:35:52 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id NAA20376
for freebsd-current-outgoing; Thu, 28 Jan 1999 13:35:52 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from server.amis.net (server.amis.net [195.10.52.10])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA20367
for <current@FreeBSD.ORG>; Thu, 28 Jan 1999 13:35:48 -0800 (PST)
(envelope-from blaz@gold.amis.net)
Received: (from uucp@localhost)
by server.amis.net (8.8.8/8.8.8) with UUCP id WAA12951
for current@FreeBSD.ORG; Thu, 28 Jan 1999 22:35:32 +0100 (CET)
Received: (qmail 1003 invoked by uid 1000); 28 Jan 1999 21:35:03 -0000
Received: from localhost (sendmail-bs@127.0.0.1)
by localhost with SMTP; 28 Jan 1999 21:35:03 -0000
Date: Thu, 28 Jan 1999 22:35:03 +0100 (CET)
From: Blaz Zupan <blaz@gold.amis.net>
To: Rod Taylor <oscentral@usa.net>
cc: current@FreeBSD.ORG
Subject: Re: Ne2000 PCI Card
In-Reply-To: <199901282223.RAA32294@speed.rcc.on.ca>
Message-ID: <Pine.BSF.4.05.9901282232350.962-100000@gold.amis.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
> I have 2 cheap 100mbit nics (rj45 only). Both use the ReaTek 8139 chipset
> (from the best that I can tell). Both are PCI.
They are supported in 4.0-CURRENT by the rl driver. I belive they are also
included in 3.0-STABLE, but I'm not sure if they are on the boot floppy.
And before using this card, you should consider the following comment from
the driver source:
* The RealTek 8139 PCI NIC redefines the meaning of 'low end.' This is
* probably the worst PCI ethernet controller ever made, with the possible
* exception of the FEAST chip made by SMC. The 8139 supports bus-master
* DMA, but it has a terrible interface that nullifies any performance
* gains that bus-master DMA usually offers.
So don't expect too much ;)
Blaz Zupan, blaz@medinet.si, http://home.amis.net/blaz
Medinet d.o.o., Linhartova 21, 2000 Maribor, Slovenia
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Thu Jan 28 13:54:39 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id NAA22476
for freebsd-current-outgoing; Thu, 28 Jan 1999 13:54:39 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from smarter.than.nu (lal-99-91.Reshall.Berkeley.EDU [169.229.99.91])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA22469
for <current@FreeBSD.ORG>; Thu, 28 Jan 1999 13:54:36 -0800 (PST)
(envelope-from brian@CSUA.Berkeley.EDU)
Received: from localhost (localhost [127.0.0.1])
by smarter.than.nu (8.9.1/8.9.1) with ESMTP id NAA12322;
Thu, 28 Jan 1999 13:54:34 -0800 (PST)
(envelope-from brian@CSUA.Berkeley.EDU)
Date: Thu, 28 Jan 1999 13:54:34 -0800 (PST)
From: "Brian W. Buchanan" <brian@CSUA.Berkeley.EDU>
X-Sender: brian@smarter.than.nu
To: Rod Taylor <oscentral@usa.net>
cc: current@FreeBSD.ORG
Subject: Re: Ne2000 PCI Card
In-Reply-To: <199901282223.RAA32294@speed.rcc.on.ca>
Message-ID: <Pine.BSF.4.05.9901281353210.9574-100000@smarter.than.nu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
On Thu, 28 Jan 1999, Rod Taylor wrote:
> I have 2 cheap 100mbit nics (rj45 only). Both use the ReaTek 8139 chipset
> (from the best that I can tell). Both are PCI.
>
> I've attempted to use both cards in several PCI slots, under 2.2.8 and 3.0
> boot floppies, and a 3.0-stable (updated 2 days ago). None of these
> releases found either card in any situation.
>
> I believe the card should be detected as Ed0 (possibly ed1). I have used
> 3com pci cards in both machines under freebsd sucessfully and the ne2000
> cards function under windows and os/2.
Try the rl0 driver:
On my system:
rl0: <RealTek 8139 10/100BaseTX> rev 0x10 int a irq 12 on pci0.9.0
--
Brian Buchanan brian@CSUA.Berkeley.EDU
--------------------------------------------------------------------------
FreeBSD - The Power to Serve! http://www.freebsd.org
daemon(n): 1. an attendant power or spirit : GENIUS
2. the cute little mascot of the FreeBSD operating system
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Thu Jan 28 14:02:06 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id OAA23612
for freebsd-current-outgoing; Thu, 28 Jan 1999 14:02:06 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from bright.fx.genx.net (bright.fx.genx.net [206.64.4.154])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA23542
for <current@FreeBSD.ORG>; Thu, 28 Jan 1999 14:01:58 -0800 (PST)
(envelope-from bright@hotjobs.com)
Received: from localhost (bright@localhost)
by bright.fx.genx.net (8.9.1/8.9.1) with ESMTP id RAA38672;
Thu, 28 Jan 1999 17:08:39 -0500 (EST)
(envelope-from bright@hotjobs.com)
X-Authentication-Warning: bright.fx.genx.net: bright owned process doing -bs
Date: Thu, 28 Jan 1999 17:08:39 -0500 (EST)
From: Alfred Perlstein <bright@hotjobs.com>
X-Sender: bright@bright.fx.genx.net
To: Rod Taylor <oscentral@usa.net>
cc: current@FreeBSD.ORG
Subject: Re: Ne2000 PCI Card
In-Reply-To: <199901282223.RAA32294@speed.rcc.on.ca>
Message-ID: <Pine.BSF.4.05.9901281704550.81323-100000@bright.fx.genx.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
On Thu, 28 Jan 1999, Rod Taylor wrote:
> I have 2 cheap 100mbit nics (rj45 only). Both use the ReaTek 8139 chipset
> (from the best that I can tell). Both are PCI.
...snip
> Tried to get help in #freebsd in efnet, but no-one had suggestions that
> helped me... (Thanks anyhow Xanne)
compile a kernel with:
device rl0
that should work, and if you want to know why the cards are so cheap:
/usr/src/sys/pci/if_rl.c
wpaul explains it quite well. :)
Alfred Perlstein - Programmer, HotJobs Inc. - www.hotjobs.com
-- There are operating systems, and then there's FreeBSD.
-- http://www.freebsd.org/ 4.0-current
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Thu Jan 28 14:02:19 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id OAA23673
for freebsd-current-outgoing; Thu, 28 Jan 1999 14:02:19 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from cia.com.au ([203.17.36.22])
by hub.freebsd.org (8.8.8/8.8.8) with SMTP id OAA23659
for <freebsd-current@freebsd.org>; Thu, 28 Jan 1999 14:02:10 -0800 (PST)
(envelope-from davidh@progmatics.com.au)
Received: (qmail 28902 invoked from network); 28 Jan 1999 22:02:06 -0000
Received: from unknown (HELO clarence.progmatics.com.au) (203.28.49.193)
by cia.com.au with SMTP; 28 Jan 1999 22:02:06 -0000
Received: from progmatics.com.au (192.168.0.69) by clarence.progmatics.com.au (Worldmail 1.3.167) for freebsd-current@freebsd.org; 29 Jan 1999 09:02:06 +1100
Message-ID: <36B0DED7.5C646381@progmatics.com.au>
Date: Fri, 29 Jan 1999 09:04:07 +1100
From: David Hobley <davidh@progmatics.com.au>
Organization: Progmatics Pty Ltd
X-Mailer: Mozilla 4.5 [en] (WinNT; U)
X-Accept-Language: en
MIME-Version: 1.0
To: freebsd-current@FreeBSD.ORG
Subject: problem booting with ELF kernel
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
Hello,
I thought I would upgrade my system to the latest -current
(as of a few days ago) so I could try the LinuxThreads stuff out.
I was running a -current of around November last year. I had no
problems upgrading my ELF userland and the bootblocks (my old aout
kernel boots fine), but when I try and boot my sparkling new ELF
kernel it gets up to right before the aout kernel tells me what
device
it is going to swap onto (ie. it has done the CAM SCSI probes and
reported back on my SCSI disk and CDROM) and just hangs.
I have 2 primary IDE discs across 2 controllers, and an IDE CDROM as
a
slave on the primary controller and the SCSI disk and CDROM.
My root is on the primary master IDE drive so I assume I don't
need to set num_ide_disks (I did try that interactively to no
effect).
Could someone let me know how to get more diagnostics in there so I
can pinpoint the problem? Or the solution :-)
--
Cheers,
david davidh@progmatics.com.au
Progmatics Pty Ltd - Architects of IT and Internet Solutions
Level 8, 191 Clarence Street Phone +61 2 9262 4933
Sydney NSW Australia Fax +61 2 9262 4045
http://www.progmatics.com.au/
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Thu Jan 28 14:15:17 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id OAA25189
for freebsd-current-outgoing; Thu, 28 Jan 1999 14:15:17 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from midget.dons.net.au (daniel.lnk.telstra.net [139.130.137.70])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA25173
for <current@FreeBSD.ORG>; Thu, 28 Jan 1999 14:15:06 -0800 (PST)
(envelope-from darius@dons.net.au)
Received: from dons.net.au (holly.dons.net.au [203.31.81.8])
by midget.dons.net.au (8.9.2/8.9.1) with ESMTP id IAA35117;
Fri, 29 Jan 1999 08:44:46 +1030 (CST)
(envelope-from darius@dons.net.au)
Message-ID: <36B0E140.796E71E8@dons.net.au>
Date: Fri, 29 Jan 1999 08:44:24 +1030
From: "Daniel O'Connor" <darius@dons.net.au>
X-Mailer: Mozilla 4.5 [en] (Win95; I)
X-Accept-Language: en
MIME-Version: 1.0
To: Wilko Bulte <wilko@yedi.iaf.nl>
CC: "Daniel O'Connor" <doconnor@gsoft.com.au>, current@FreeBSD.ORG,
dfr@nlsystems.com, archie@whistle.com
Subject: Re: DEVFS, the time has come...
References: <199901281838.TAA00524@yedi.iaf.nl>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
Wilko Bulte wrote:
> > Well, for one its sucks trying to get newbies to work out what their network card is
> > called..
> Not true IMO. You still need to know what hardware you have before you can build your
> own kernels etc etc.
Yes, this is true, but when they have just installed then its true :)
Also, hopefully when we have the autodetection of hardware and loading
KLD's for network cards etc, this would be so much nicer IMHO.. Just
'tidier'..
---
Daniel O'Connor software and network engineer
for Genesis Software - http://www.gsoft.com.au
"The nice thing about standards is that there
are so many of them to choose from."
-- Andnew Tanenbaum
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Thu Jan 28 14:33:48 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id OAA27433
for freebsd-current-outgoing; Thu, 28 Jan 1999 14:33:48 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from zeus.theinternet.com.au (zeus.theinternet.com.au [203.34.176.2])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA27423
for <current@FreeBSD.ORG>; Thu, 28 Jan 1999 14:33:42 -0800 (PST)
(envelope-from akm@zeus.theinternet.com.au)
Received: (from akm@localhost)
by zeus.theinternet.com.au (8.8.7/8.8.7) id IAA22472;
Fri, 29 Jan 1999 08:33:32 +1000 (EST)
(envelope-from akm)
From: Andrew Kenneth Milton <akm@zeus.theinternet.com.au>
Message-Id: <199901282233.IAA22472@zeus.theinternet.com.au>
Subject: Re: Style (was Re: btokup()..)
In-Reply-To: <199901281629.JAA29626@mt.sri.com> from Nate Williams at "Jan 28, 99 09:29:48 am"
To: nate@mt.sri.com (Nate Williams)
Date: Fri, 29 Jan 1999 08:33:32 +1000 (EST)
Cc: current@FreeBSD.ORG
X-Mailer: ELM [version 2.4ME+ PL32 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
+----[ Nate Williams ]---------------------------------------------
| > | :I think that style(9) should be modified to include
| > | :"Parenthesis may be used to improve the readbility of complex
| > | :expressions even if not strictly required."
| > | :instead of the stupid phrase presently there.
| > | :also:
| > | :"Braces around code blocks should be allowable even when not strictly
| > | :needed, for the purpose of readbility."
| > | :
| > | :The aim is to produce readble maintainable code, not to save bytes in
| > | :sourcecode!
| > |
| > | I agree completely. I've already gotten into the habit of added
| > | braces when conditonal expressions exceed one line, even though there
| > | may be only one statement. Otherwise the code is just too unreadable.
| >
| > Is there an ident style for (x)emacs to enforce/promote this style?
|
| *emacs never inserts code, so you couldn't get it to 'add' parentheses
| or braces to code. It doesn't even whine about them. The only thing
| that it does is move your white-space around.
Sure it does, just not based on indent style. I'm sure you can make
it do it if you wanted to. If it can work out when it should indent,
it can work out how to add a brace and then indent.
I can't do lisp, I've never been able to do lisp, prolog yes, lisp no.
Must be the prefix notation that screws me.
One company I was at had it automatically inserting comment banners
whenever you created a new file, and building comment blocks when you
opened a new function.
--
Totally Holistic Enterprises Internet| P:+61 7 3870 0066 | Andrew
The Internet (Aust) Pty Ltd | F:+61 7 3870 4477 | Milton
ACN: 082 081 472 | M:+61 416 022 411 |72 Col .Sig
PO Box 837 Indooroopilly QLD 4068 |akm@theinternet.com.au|Specialist
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Thu Jan 28 14:49:32 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id OAA00197
for freebsd-current-outgoing; Thu, 28 Jan 1999 14:49:32 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA00192
for <freebsd-current@FreeBSD.ORG>; Thu, 28 Jan 1999 14:49:31 -0800 (PST)
(envelope-from mike@dingo.cdrom.com)
Received: from dingo.cdrom.com (localhost.cdrom.com [127.0.0.1])
by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id OAA00567;
Thu, 28 Jan 1999 14:43:16 -0800 (PST)
(envelope-from mike@dingo.cdrom.com)
Message-Id: <199901282243.OAA00567@dingo.cdrom.com>
X-Mailer: exmh version 2.0.2 2/24/98
To: "Daniel C. Sobral" <dcs@newsguy.com>
cc: Patrick Hartling <mystify@friley-184-92.res.iastate.edu>,
freebsd-current@FreeBSD.ORG
Subject: Re: Reading a text file with BTX
In-reply-to: Your message of "Fri, 29 Jan 1999 03:46:29 +0900."
<36B0B085.114163@newsguy.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Thu, 28 Jan 1999 14:43:15 -0800
From: Mike Smith <mike@smith.net.au>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
> Patrick Hartling wrote:
> >
> > Is there a way to view the contents of a text file (specifically,
> > /boot/loader.rc) with BTX? Now that there are all these nifty new modules,
...
> You might be refering to the loader prompt, not the btx prompt. If
> you type something as soon as the first "|" is shown, that's btx. If
> you wait a little, or enter /boot/loader, then you get loader.
> Specifically, if it has processed loader.rc, then you are inside
> loader, not btx.
Ugh. No. BTX is the kernel that boot2 and the loader use.
boot0 is the module that gives you the F? prompt
boot1 is invisible, it just loads boot2
boot2 spins the | to begin with, and if you hit a key while it's paused,
you get it's prompt 'boot:', it starts the loader.
> Conditional loading is possible, though Mike committed it to
> RELENG_3 instead of -current, and has not corrected that yet.
Gah. Thanks for the PR reference.
--
\\ Sometimes you're ahead, \\ Mike Smith
\\ sometimes you're behind. \\ mike@smith.net.au
\\ The race is long, and in the \\ msmith@freebsd.org
\\ end it's only with yourself. \\ msmith@cdrom.com
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Thu Jan 28 15:09:18 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id PAA03390
for freebsd-current-outgoing; Thu, 28 Jan 1999 15:09:18 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from arnold.neland.dk (mail.swimsuit.internet.dk [194.255.12.232])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA02879
for <current@FreeBSD.ORG>; Thu, 28 Jan 1999 15:05:08 -0800 (PST)
(envelope-from leif@neland.dk)
Received: from localhost (leif@localhost)
by arnold.neland.dk (8.9.2/8.9.1) with ESMTP id AAA13001;
Fri, 29 Jan 1999 00:03:54 +0100 (CET)
(envelope-from leif@arnold.neland.dk)
Date: Fri, 29 Jan 1999 00:03:53 +0100 (CET)
From: Leif Neland <leif@neland.dk>
To: "Kenneth D. Merry" <ken@plutotech.com>
cc: archie@whistle.com, dfr@nlsystems.com, current@FreeBSD.ORG
Subject: Re: DEVFS, the time has come...
In-Reply-To: <199901280711.AAA57155@panzer.plutotech.com>
Message-ID: <Pine.BSF.4.05.9901290003040.12987-100000@arnold.neland.dk>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
On Thu, 28 Jan 1999, Kenneth D. Merry wrote:
> > Just symlink eth0 to which card you like, just as /dev/mixer happens to be
> > a symlink to /dev/mixer1 on my system.
>
> How are you going to do that, when network drivers don't have device nodes?
>
Minor point :-)
Sorry, I missed that.
Leif
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Thu Jan 28 15:22:10 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id PAA05691
for freebsd-current-outgoing; Thu, 28 Jan 1999 15:22:10 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from arnold.neland.dk (mail.swimsuit.internet.dk [194.255.12.232])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA04768
for <current@FreeBSD.ORG>; Thu, 28 Jan 1999 15:17:23 -0800 (PST)
(envelope-from leif@neland.dk)
Received: from localhost (leif@localhost)
by arnold.neland.dk (8.9.2/8.9.1) with ESMTP id AAA13037;
Fri, 29 Jan 1999 00:16:40 +0100 (CET)
(envelope-from leif@arnold.neland.dk)
Date: Fri, 29 Jan 1999 00:16:39 +0100 (CET)
From: Leif Neland <leif@neland.dk>
To: Brian Somers <brian@Awfulhak.org>
cc: current@FreeBSD.ORG
Subject: PPP (userland) troubles ?
In-Reply-To: <199901281104.LAA94389@keep.lan.Awfulhak.org>
Message-ID: <Pine.BSF.4.05.9901290010480.12987-100000@arnold.neland.dk>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
Would it be possible to add an exponential delay when connecting fails for
either reason?
I just received my specified phone-bill. It filled 42 pages, with hundreds
of calls with a duration of 17 seconds. (Because my modem needs to be
software-reset; I have mentioned this before).
Each call costs a few cents; I'm billed both for each connect, and for
connect time. It all adds up. And I'm connected to the other modem, even
if the handshake doesn't work.
Leif
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Thu Jan 28 15:31:03 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id PAA06888
for freebsd-current-outgoing; Thu, 28 Jan 1999 15:31:03 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from frmug.org (frmug-gw.frmug.org [193.56.58.252])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA06881
for <current@FreeBSD.ORG>; Thu, 28 Jan 1999 15:30:59 -0800 (PST)
(envelope-from roberto@keltia.freenix.fr)
Received: (from uucp@localhost)
by frmug.org (8.9.1/frmug-2.3/nospam) with UUCP id AAA25365
for current@FreeBSD.ORG; Fri, 29 Jan 1999 00:30:46 +0100 (CET)
(envelope-from roberto@keltia.freenix.fr)
Received: by keltia.freenix.fr (Postfix, from userid 101)
id 234DE1506; Thu, 28 Jan 1999 23:51:50 +0100 (CET)
Date: Thu, 28 Jan 1999 23:51:50 +0100
From: Ollivier Robert <roberto@keltia.freenix.fr>
To: FreeBSD Current <current@FreeBSD.ORG>
Subject: Re: Netscape | Mozilla
Message-ID: <19990128235149.A90958@keltia.freenix.fr>
Mail-Followup-To: FreeBSD Current <current@FreeBSD.ORG>
References: <Pine.BSF.4.05.9901271815420.4709-100000@s8-37-26.student.washington.edu> <199901271901.OAA22237@ayukawa.aus.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.95i
In-Reply-To: <199901271901.OAA22237@ayukawa.aus.org>; from Luke on Wed, Jan 27, 1999 at 02:20:32PM -0500
X-Operating-System: FreeBSD 3.0-CURRENT/ELF ctm#4994 AMD-K6 MMX @ 200 MHz
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
According to Luke:
> linux_lib port. [why does it install into / anyways]
The standard sysinstall has been making a link into /usr/compat for months
if not years :-)
----------------------------
revision 1.193
date: 1997/07/16 11:45:48; author: jkh; state: Exp; lines: +5 -1
ln /compat to /usr/compat on initial installation; this will
prevent the later addition of compat libs from overflowing /
----------------------------
--
Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- roberto@keltia.freenix.fr
FreeBSD keltia.freenix.fr 3.0-CURRENT #69: Mon Jan 18 02:02:12 CET 1999
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Thu Jan 28 15:31:15 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id PAA06909
for freebsd-current-outgoing; Thu, 28 Jan 1999 15:31:15 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from frmug.org (frmug-gw.frmug.org [193.56.58.252])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA06903
for <current@FreeBSD.ORG>; Thu, 28 Jan 1999 15:31:09 -0800 (PST)
(envelope-from roberto@keltia.freenix.fr)
Received: (from uucp@localhost)
by frmug.org (8.9.1/frmug-2.3/nospam) with UUCP id AAA25371
for current@FreeBSD.ORG; Fri, 29 Jan 1999 00:31:05 +0100 (CET)
(envelope-from roberto@keltia.freenix.fr)
Received: by keltia.freenix.fr (Postfix, from userid 101)
id 0D2331506; Thu, 28 Jan 1999 23:53:33 +0100 (CET)
Date: Thu, 28 Jan 1999 23:53:33 +0100
From: Ollivier Robert <roberto@keltia.freenix.fr>
To: current@FreeBSD.ORG
Subject: Re: Netscape | Mozilla
Message-ID: <19990128235333.B90958@keltia.freenix.fr>
Mail-Followup-To: current@FreeBSD.ORG
References: <XFMail.990127180059.asmodai@wxs.nl> <199901271716.MAA20727@ayukawa.aus.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.95i
In-Reply-To: <199901271716.MAA20727@ayukawa.aus.org>; from Luke on Wed, Jan 27, 1999 at 12:35:09PM -0500
X-Operating-System: FreeBSD 3.0-CURRENT/ELF ctm#4994 AMD-K6 MMX @ 200 MHz
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
According to Luke:
> This is 4.5b1 communicator, and locks up X often enough I dont use it.
Beta versions of 4.5 were bad (in that case b2 was far worse than b1)
whereas 4.5 release is more or less stable. (it still crashes from time to
time but not that often).
--
Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- roberto@keltia.freenix.fr
FreeBSD keltia.freenix.fr 3.0-CURRENT #69: Mon Jan 18 02:02:12 CET 1999
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Thu Jan 28 16:10:55 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id QAA15309
for freebsd-current-outgoing; Thu, 28 Jan 1999 16:10:55 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA15301
for <current@FreeBSD.ORG>; Thu, 28 Jan 1999 16:10:52 -0800 (PST)
(envelope-from dillon@apollo.backplane.com)
Received: (from dillon@localhost)
by apollo.backplane.com (8.9.2/8.9.1) id QAA11960;
Thu, 28 Jan 1999 16:10:26 -0800 (PST)
(envelope-from dillon)
Date: Thu, 28 Jan 1999 16:10:26 -0800 (PST)
From: Matthew Dillon <dillon@apollo.backplane.com>
Message-Id: <199901290010.QAA11960@apollo.backplane.com>
To: HighWind Software Information <info@highwind.com>
Cc: current@FreeBSD.ORG
Subject: Re: Locked at 100% User CPU
References: <199901282130.QAA13214@highwind.com>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
:In libc_r, I don't think the code in uthread_kern.c's
:_thread_kern_select() scales at all.
:
:As the number of network connections (TCP) to my application grows, I
:believe this routine takes longer and longer and my CPU goes to 100%
:user space.
:
:Something makes me believe that this routine has an n^2 (or worse)
:problem. Seems to relate to the number of fd's to select() on. At
:about 300-400, even a P2 400Mhz gets max'd out and gets nothing done.
:
:Anybody have a feeling as to what is wrong here?
:
:-Rob
This code looks pretty bad, all right. It looks like it is O(N^2)
in PS_SELECT_WAIT(), especially if descriptors get randomly strewn
amoungst the threads. It also looks like it is regenerating the FDS masks
on each call completely from scratch. It also looks like it is
scanning the entire thread list - both waiting and running threads,
to prioritize the next thread to run and then scanning it again
to select the thread priority, then scanning the whole list yet
again to find the one it wants to run.
This is massively unscaleable code. Is anyone actively working on
it?
-Matt
Matthew Dillon
<dillon@backplane.com>
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Thu Jan 28 16:26:31 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id QAA16984
for freebsd-current-outgoing; Thu, 28 Jan 1999 16:26:31 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from ayukawa.aus.org (ayukawa.aus.org [199.166.246.1])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA16973
for <current@FreeBSD.ORG>; Thu, 28 Jan 1999 16:26:28 -0800 (PST)
(envelope-from lh@aus.org)
Received: from bsd.aus.org (lh@zer0.net [199.166.246.189]) by ayukawa.aus.org (8.8.7/8.7.3) with ESMTP id TAA04496; Thu, 28 Jan 1999 19:26:11 -0500 (EST)
Message-Id: <199901290026.TAA04496@ayukawa.aus.org>
X-Mailer: XFMail 1.3-beta-042198 [p0] on FreeBSD
X-Priority: 3 (Normal)
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 8bit
MIME-Version: 1.0
In-Reply-To: <19990128235149.A90958@keltia.freenix.fr>
Date: Thu, 28 Jan 1999 19:26:12 -0500 (EST)
Reply-To: lh@aus.org
From: Luke <lh@aus.org>
To: Ollivier Robert <roberto@keltia.freenix.fr>
Subject: Re: Netscape | Mozilla
Cc: FreeBSD Current <current@FreeBSD.ORG>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
On 28-Jan-99 Ollivier Robert wrote:
> According to Luke:
>> linux_lib port. [why does it install into / anyways]
>
> The standard sysinstall has been making a link into /usr/compat for months
> if not years :-)
Some people haven't used sysinstall for years :>
E-Mail: Luke <lh@aus.org>
Sent by XFMail
----------------------------------
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Thu Jan 28 16:27:33 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id QAA17069
for freebsd-current-outgoing; Thu, 28 Jan 1999 16:27:33 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from ayukawa.aus.org (ayukawa.aus.org [199.166.246.1])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA17059
for <current@FreeBSD.ORG>; Thu, 28 Jan 1999 16:27:30 -0800 (PST)
(envelope-from lh@aus.org)
Received: from bsd.aus.org (lh@zer0.net [199.166.246.189]) by ayukawa.aus.org (8.8.7/8.7.3) with ESMTP id TAA04507; Thu, 28 Jan 1999 19:27:18 -0500 (EST)
Message-Id: <199901290027.TAA04507@ayukawa.aus.org>
X-Mailer: XFMail 1.3-beta-042198 [p0] on FreeBSD
X-Priority: 3 (Normal)
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 8bit
MIME-Version: 1.0
In-Reply-To: <19990128235333.B90958@keltia.freenix.fr>
Date: Thu, 28 Jan 1999 19:27:19 -0500 (EST)
Reply-To: lh@aus.org
From: Luke <lh@aus.org>
To: Ollivier Robert <roberto@keltia.freenix.fr>
Subject: Re: Netscape | Mozilla
Cc: current@FreeBSD.ORG
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
On 28-Jan-99 Ollivier Robert wrote:
> According to Luke:
>> This is 4.5b1 communicator, and locks up X often enough I dont use it.
>
> Beta versions of 4.5 were bad (in that case b2 was far worse than b1)
> whereas 4.5 release is more or less stable. (it still crashes from time to
> time but not that often).
I think my netscape problem is solved, I installed ports/linux_lib and
www/linux_netscape, and so far its working well, even after trying to crash it.
---
E-Mail: Luke <lh@aus.org>
Sent by XFMail
----------------------------------
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Thu Jan 28 16:33:19 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id QAA17674
for freebsd-current-outgoing; Thu, 28 Jan 1999 16:33:19 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from awfulhak.org (awfulhak.force9.co.uk [195.166.136.63])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA17661
for <current@FreeBSD.ORG>; Thu, 28 Jan 1999 16:33:16 -0800 (PST)
(envelope-from brian@Awfulhak.org)
Received: from keep.lan.Awfulhak.org (brian@keep.lan.Awfulhak.org [172.16.0.8])
by awfulhak.org (8.8.8/8.8.8) with ESMTP id AAA29087;
Fri, 29 Jan 1999 00:33:17 GMT
(envelope-from brian@Awfulhak.org)
Received: from keep.lan.Awfulhak.org (brian@localhost [127.0.0.1])
by keep.lan.Awfulhak.org (8.9.2/8.9.2) with ESMTP id PAA95452;
Thu, 28 Jan 1999 15:15:57 GMT
(envelope-from brian@keep.lan.Awfulhak.org)
Message-Id: <199901281515.PAA95452@keep.lan.Awfulhak.org>
X-Mailer: exmh version 2.0.2 2/24/98
To: Andre Oppermann <oppermann@pipeline.ch>
cc: Brian Somers <brian@Awfulhak.org>, current@FreeBSD.ORG
Subject: Re: PPP (userland) troubles ?
In-reply-to: Your message of "Thu, 28 Jan 1999 12:53:26 +0100."
<36B04FB6.B2B54FD1@pipeline.ch>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Thu, 28 Jan 1999 15:15:57 +0000
From: Brian Somers <brian@Awfulhak.org>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
> Brian Somers wrote:
> >
> > > So there are now 2 possibilities for this problem:
> > >
> > > a) I was out of sync :(
> > > b) Someone fixed ppp
> >
> > Last nights commit was for RADIUS support in ppp. There was another
> > latency problem that I fixed about a week ago - maybe that was it :-)
>
> Yuck! (jumping in the air and clapping with my feet!!)
It may be a bit raw as yet..... this way someone might do some
testing for me :-)
> --
> Andre
>
--
Brian <brian@Awfulhak.org> <brian@FreeBSD.org> <brian@OpenBSD.org>
<http://www.Awfulhak.org>
Don't _EVER_ lose your sense of humour !
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Thu Jan 28 16:33:23 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id QAA17691
for freebsd-current-outgoing; Thu, 28 Jan 1999 16:33:23 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA17673
for <current@FreeBSD.ORG>; Thu, 28 Jan 1999 16:33:19 -0800 (PST)
(envelope-from dillon@apollo.backplane.com)
Received: (from dillon@localhost)
by apollo.backplane.com (8.9.2/8.9.1) id QAA12211;
Thu, 28 Jan 1999 16:33:12 -0800 (PST)
(envelope-from dillon)
Date: Thu, 28 Jan 1999 16:33:12 -0800 (PST)
From: Matthew Dillon <dillon@apollo.backplane.com>
Message-Id: <199901290033.QAA12211@apollo.backplane.com>
To: Peter Jeremy <peter.jeremy@auss2.alcatel.com.au>
Cc: current@FreeBSD.ORG
Subject: Re: indent(1) and style(9) (was: btokup() macro in sys/malloc.h)
References: <99Jan29.074452est.40330@border.alcanet.com.au>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
:Luigi Rizzo <luigi@labinfo.iet.unipi.it>
:>not speaking about vinum, but to me, the indentation of 8 char and
:...
:
:According to most of the coding standards I've read, readability
:(and hence maintainability) come before efficiency. That said, I
:agree that efficiency _is_ an issue within the kernel's critical
:paths (the TCP/IP code being one).
:
:Judicious use of inline functions (and macros) should help move
:code to the left - and may even make it more understandable.
:
:Peter
More then judicious use -- inlines are an incredible advantage. Most
people don't realize that GCC will optimize constant arguments through
an inline call. Try this:
static __inline
fubar(int c)
{
if (c & 1)
++c;
if (c & 2)
++c;
return(c);
}
void
fubar2(void)
{
volatile int x;
x = fubar(0);
x = fubar(1);
x = fubar(2);
x = fubar(3);
}
% cc -S -O2 x.c
% cat x.s
fubar2:
pushl %ebp
movl %esp,%ebp
subl $4,%esp
xorl %eax,%eax <----- fubar (0)
movl %eax,-4(%ebp)
movl $3,-4(%ebp) <----- fubar (1)
movl $3,-4(%ebp) <----- fubar (2)
movl $4,-4(%ebp) <----- fubar (3)
leave
ret
For some good examples of inlines and inherent optimizeable code,
take a look at vm/vm_page.h.
For example, look at vm_page_sleep_busy() keeping in mind that the
also_m_busy and msg arguments are usually constants.
Another example: vm_page_protect(), where 'prot' is usually passed
as a constant.
For that matter, we could probably inline a good chunk of the smaller
pmap_*() functions as well, such as pmap_page_protect ( currently in
i386/i386/pmap.c ). This would get rid of an entire subroutine call
layer without reducing readability at all.
-Matt
Matthew Dillon
<dillon@backplane.com>
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Thu Jan 28 16:38:17 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id QAA18345
for freebsd-current-outgoing; Thu, 28 Jan 1999 16:38:17 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from ns.mt.sri.com (sri-gw.MT.net [206.127.105.141])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA18340
for <current@FreeBSD.ORG>; Thu, 28 Jan 1999 16:38:15 -0800 (PST)
(envelope-from nate@mt.sri.com)
Received: from mt.sri.com (rocky.mt.sri.com [206.127.76.100])
by ns.mt.sri.com (8.8.8/8.8.8) with SMTP id RAA19791;
Thu, 28 Jan 1999 17:38:09 -0700 (MST)
(envelope-from nate@rocky.mt.sri.com)
Received: by mt.sri.com (SMI-8.6/SMI-SVR4)
id RAA02885; Thu, 28 Jan 1999 17:38:09 -0700
Date: Thu, 28 Jan 1999 17:38:09 -0700
Message-Id: <199901290038.RAA02885@mt.sri.com>
From: Nate Williams <nate@mt.sri.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
To: Archie Cobbs <archie@whistle.com>
Cc: julian@whistle.com (Julian Elischer), current@FreeBSD.ORG
Subject: Re: btokup().. patch to STYLE(9) (fwd)
In-Reply-To: <199901281956.LAA22422@bubba.whistle.com>
References: <Pine.BSF.4.05.9901280335450.304-100000@s204m82.isp.whistle.com>
<199901281956.LAA22422@bubba.whistle.com>
X-Mailer: VM 6.34 under 19.16 "Lille" XEmacs Lucid
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
> > Some people when confronted by people wanting to have extra braces
> > say "change style(9)".
> >
> > Well, here is my change..
>
> You can count my vote.
>
> I would also add a paragraph like this:
>
> If possible code should complile cleanly with gcc's -Wall flag.
> Note however that this does not imply that it's OK to eliminate
> warnings simply by covering them up with typecasts, etc., as that
> actually does more harm than good.
>
> I hope that wording is sufficiently unoffensive to the -Wall haters.
'-Wall haters'. That almost sounds like 'Wall-flowers' or something. :)
Agreed, but that's not the only reason I dislike '-Wall'. The other
reason is that some of the warnings enabled in -Wall are purely
stylistic, and are not even warnings.
Making all software compile quietly with gcc -Wall means complying with
what the GNU folks thinks is the correct 'style' of writing software,
rather than having style issues ignored. In other words, you end up
making change change for the sake of change, which is silly just to
please the compiler.
But, after the recent flame fiasco I'm not saying anything more.
Nate
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Thu Jan 28 16:56:57 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id QAA20787
for freebsd-current-outgoing; Thu, 28 Jan 1999 16:56:57 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA20779
for <freebsd-current@FreeBSD.ORG>; Thu, 28 Jan 1999 16:56:55 -0800 (PST)
(envelope-from mike@dingo.cdrom.com)
Received: from dingo.cdrom.com (localhost.cdrom.com [127.0.0.1])
by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id QAA01195;
Thu, 28 Jan 1999 16:50:35 -0800 (PST)
(envelope-from mike@dingo.cdrom.com)
Message-Id: <199901290050.QAA01195@dingo.cdrom.com>
X-Mailer: exmh version 2.0.2 2/24/98
To: Ustimenko Semen <semen@iclub.nsu.ru>
cc: freebsd-current@FreeBSD.ORG
Subject: Re: About to commit NTFS driver
In-reply-to: Your message of "Thu, 28 Jan 1999 02:46:28 +0600."
<Pine.BSF.3.96.990128024451.49866B-100000@iclub.nsu.ru>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Thu, 28 Jan 1999 16:50:35 -0800
From: Mike Smith <mike@smith.net.au>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
>
> Are there any disagrees with an idea to commit a NTFS
> driver into current:
>
> I can commit/maintain driver mentioned at
> http://www.freebsd.org/projects/
>
> Driver is readonly, specialy developed for freebsd,
> supports most of NTFS's features.
> Source is at http://iclub.nsu.ru/~semen/ntfs/
Sounds like a good idea. Do you have a reviewer?
--
\\ Sometimes you're ahead, \\ Mike Smith
\\ sometimes you're behind. \\ mike@smith.net.au
\\ The race is long, and in the \\ msmith@freebsd.org
\\ end it's only with yourself. \\ msmith@cdrom.com
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Thu Jan 28 16:57:43 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id QAA20893
for freebsd-current-outgoing; Thu, 28 Jan 1999 16:57:43 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from whistle.com (s205m131.whistle.com [207.76.205.131])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA20886
for <current@FreeBSD.ORG>; Thu, 28 Jan 1999 16:57:42 -0800 (PST)
(envelope-from archie@whistle.com)
Received: (from smap@localhost) by whistle.com (8.7.5/8.6.12) id QAA12964; Thu, 28 Jan 1999 16:57:09 -0800 (PST)
Received: from bubba.whistle.com( 207.76.205.7) by whistle.com via smap (V2.0)
id xma012960; Thu, 28 Jan 99 16:56:59 -0800
Received: (from archie@localhost) by bubba.whistle.com (8.8.7/8.6.12) id QAA07338; Thu, 28 Jan 1999 16:56:59 -0800 (PST)
From: Archie Cobbs <archie@whistle.com>
Message-Id: <199901290056.QAA07338@bubba.whistle.com>
Subject: Re: btokup().. patch to STYLE(9) (fwd)
In-Reply-To: <199901290038.RAA02885@mt.sri.com> from Nate Williams at "Jan 28, 99 05:38:09 pm"
To: nate@mt.sri.com (Nate Williams)
Date: Thu, 28 Jan 1999 16:56:59 -0800 (PST)
Cc: current@FreeBSD.ORG
X-Mailer: ELM [version 2.4ME+ PL38 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
Nate Williams writes:
> > I hope that wording is sufficiently unoffensive to the -Wall haters.
>
> '-Wall haters'. That almost sounds like 'Wall-flowers' or something. :)
:-)
> Agreed, but that's not the only reason I dislike '-Wall'. The other
> reason is that some of the warnings enabled in -Wall are purely
> stylistic, and are not even warnings.
>
> Making all software compile quietly with gcc -Wall means complying with
> what the GNU folks thinks is the correct 'style' of writing software,
> rather than having style issues ignored. In other words, you end up
> making change change for the sake of change, which is silly just to
> please the compiler.
Yes, that's true... but on balance I (personally) find it's worth
the tradeoff.
On the other hand, I can't stand the GNU coding style..
-Archie
___________________________________________________________________________
Archie Cobbs * Whistle Communications, Inc. * http://www.whistle.com
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Thu Jan 28 17:20:44 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id RAA23606
for freebsd-current-outgoing; Thu, 28 Jan 1999 17:20:44 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.95.76.54])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA23600
for <current@FreeBSD.ORG>; Thu, 28 Jan 1999 17:20:43 -0800 (PST)
(envelope-from sgk@troutmask.apl.washington.edu)
Received: (from sgk@localhost)
by troutmask.apl.washington.edu (8.9.2/8.9.1) id RAA27878;
Thu, 28 Jan 1999 17:22:01 -0800 (PST)
(envelope-from sgk)
From: Steve Kargl <sgk@troutmask.apl.washington.edu>
Message-Id: <199901290122.RAA27878@troutmask.apl.washington.edu>
Subject: Re: indent(1) and style(9) (was: btokup() macro in sys/malloc.h)
In-Reply-To: <199901290033.QAA12211@apollo.backplane.com> from Matthew Dillon at "Jan 28, 1999 4:33:12 pm"
To: dillon@apollo.backplane.com (Matthew Dillon)
Date: Thu, 28 Jan 1999 17:22:01 -0800 (PST)
Cc: peter.jeremy@auss2.alcatel.com.au, current@FreeBSD.ORG
X-Mailer: ELM [version 2.4ME+ PL43 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
Matthew Dillon wrote:
> :Luigi Rizzo <luigi@labinfo.iet.unipi.it>
> :>not speaking about vinum, but to me, the indentation of 8 char and
> :...
> :
> :According to most of the coding standards I've read, readability
> :(and hence maintainability) come before efficiency. That said, I
> :agree that efficiency _is_ an issue within the kernel's critical
> :paths (the TCP/IP code being one).
> :
> :Judicious use of inline functions (and macros) should help move
> :code to the left - and may even make it more understandable.
> :
> :Peter
>
> More then judicious use -- inlines are an incredible advantage. Most
> people don't realize that GCC will optimize constant arguments through
> an inline call. Try this:
>
> static __inline
Matt,
int
fubar(int c)
{
if (c & 1)
++c;
if (c & 2)
++c;
return(c);
}
void
fubar2(void)
{
volatile int x;
x = fubar(0);
x = fubar(1);
x = fubar(2);
x = fubar(3);
}
% cc -S -O3 x.c
% cat x.s
fubar2:
pushl %ebp
movl %esp,%ebp
subl $4,%esp
xorl %eax,%eax <----- fubar (0)
movl %eax,-4(%ebp)
movl $3,-4(%ebp) <----- fubar (1)
movl $3,-4(%ebp) <----- fubar (2)
movl $4,-4(%ebp) <----- fubar (3)
leave
ret
--
Steve
finger kargl@troutmask.apl.washington.edu
http://troutmask.apl.washington.edu/~clesceri/kargl.html
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Thu Jan 28 17:30:01 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id RAA24627
for freebsd-current-outgoing; Thu, 28 Jan 1999 17:30:01 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA24575
for <current@FreeBSD.ORG>; Thu, 28 Jan 1999 17:29:59 -0800 (PST)
(envelope-from dillon@apollo.backplane.com)
Received: (from dillon@localhost)
by apollo.backplane.com (8.9.2/8.9.1) id RAA16381;
Thu, 28 Jan 1999 17:29:57 -0800 (PST)
(envelope-from dillon)
Date: Thu, 28 Jan 1999 17:29:57 -0800 (PST)
From: Matthew Dillon <dillon@apollo.backplane.com>
Message-Id: <199901290129.RAA16381@apollo.backplane.com>
To: Steve Kargl <sgk@troutmask.apl.washington.edu>
Cc: peter.jeremy@auss2.alcatel.com.au, current@FreeBSD.ORG
Subject: Re: indent(1) and style(9) (was: btokup() macro in sys/malloc.h)
References: <199901290122.RAA27878@troutmask.apl.washington.edu>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
:>
:> More then judicious use -- inlines are an incredible advantage. Most
:> people don't realize that GCC will optimize constant arguments through
:> an inline call. Try this:
:>
:> static __inline
Yah, and if it's static it will not even output code for fubar.
I've never trusted -O3, though, and you can't put static procedures
in header files ( because then you can't fall back to -O2 ). Thus,
for this sort of optimization to work the procedure must be in the same
source file, which kills the modularity. Also, on top of all of that,
GCC may not make a good decision on whether to actually inline the
static or whether to call it - it might wind up inlining a large
routine that you call many times in your module and both bloat the code
and destroy the L1 cache.
I think it's better to make things explicitly __inline and to put them in
the proper subsystem's header files. It isn't worth depending on -O3
for things to compile:
-O3 Optimize yet more. This turns on everything -O2
does, along with also turning on -finline-func-
tions.
-Matt
:Matt,
:
:int
:fubar(int c)
:{
: if (c & 1)
: ++c;
: if (c & 2)
: ++c;
: return(c);
:}
:
:void
:fubar2(void)
:{
: volatile int x;
:
: x = fubar(0);
: x = fubar(1);
: x = fubar(2);
: x = fubar(3);
:}
:
:% cc -S -O3 x.c
:% cat x.s
:
:fubar2:
: pushl %ebp
: movl %esp,%ebp
: subl $4,%esp
: xorl %eax,%eax <----- fubar (0)
: movl %eax,-4(%ebp)
: movl $3,-4(%ebp) <----- fubar (1)
: movl $3,-4(%ebp) <----- fubar (2)
: movl $4,-4(%ebp) <----- fubar (3)
: leave
: ret
:
:--
:Steve
:
:finger kargl@troutmask.apl.washington.edu
:http://troutmask.apl.washington.edu/~clesceri/kargl.html
:
Matthew Dillon
<dillon@backplane.com>
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Thu Jan 28 17:38:55 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id RAA25564
for freebsd-current-outgoing; Thu, 28 Jan 1999 17:38:55 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA25557
for <current@FreeBSD.ORG>; Thu, 28 Jan 1999 17:38:53 -0800 (PST)
(envelope-from dillon@apollo.backplane.com)
Received: (from dillon@localhost)
by apollo.backplane.com (8.9.2/8.9.1) id RAA16433;
Thu, 28 Jan 1999 17:38:52 -0800 (PST)
(envelope-from dillon)
Date: Thu, 28 Jan 1999 17:38:52 -0800 (PST)
From: Matthew Dillon <dillon@apollo.backplane.com>
Message-Id: <199901290138.RAA16433@apollo.backplane.com>
To: Archie Cobbs <archie@whistle.com>
Cc: nate@mt.sri.com (Nate Williams), current@FreeBSD.ORG
Subject: Re: btokup().. patch to STYLE(9) (fwd)
References: <199901290056.QAA07338@bubba.whistle.com>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
:Yes, that's true... but on balance I (personally) find it's worth
:the tradeoff.
:
:On the other hand, I can't stand the GNU coding style..
:
:-Archie
:
:___________________________________________________________________________
:Archie Cobbs * Whistle Communications, Inc. * http://www.whistle.com
Well, not to start a flame war, but I happen to like GCC's choices
for warnings with -Wall. They aren't all that bad, really... they
warn you if you have an assignment in a boolean statement like:
if (a = b) because it is a *very* common mistake to intend '==' rather
then '='. I found a couple of those when I turned it on the kernel
tree, for example.
I used to use assignments in condtionals all the time myself, until one
day it bit so hard it took 30 hours to find the bug - which turned out
to be an assignment in a conditional that was supposed to be an ==. From
that day on, I never put assignments in conditionals with an explicit
boolean test, aka if ((a = b) != 0) { ... }.
Beyond that it's pretty much just &/| and &&/|| precedences. I personally
*never* liked the fact that C gave & and | ( and && and || ) differentl
precedences. IMHO, the arithmatic-vs-shift parenthesization is something
I've *always* done myself, so I don't mind those warnings either.
-Wall also turns on -Wswitch which warns of switch()'d on enumerated types
which lack a default.
All the remaining warnings that -Wall turns on are pretty standard -
for example, weak-typing warnings. I advocate prototyping and relatively
strong typing myself. Weak typing warnings are a good thing.
-Matt
Matthew Dillon
<dillon@backplane.com>
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Thu Jan 28 17:47:18 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id RAA26325
for freebsd-current-outgoing; Thu, 28 Jan 1999 17:47:18 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA26316
for <current@FreeBSD.ORG>; Thu, 28 Jan 1999 17:47:16 -0800 (PST)
(envelope-from mike@dingo.cdrom.com)
Received: from dingo.cdrom.com (localhost.cdrom.com [127.0.0.1])
by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id RAA01512;
Thu, 28 Jan 1999 17:42:31 -0800 (PST)
(envelope-from mike@dingo.cdrom.com)
Message-Id: <199901290142.RAA01512@dingo.cdrom.com>
X-Mailer: exmh version 2.0.2 2/24/98
To: Matthew Dillon <dillon@apollo.backplane.com>
cc: Archie Cobbs <archie@whistle.com>, nate@mt.sri.com (Nate Williams),
current@FreeBSD.ORG
Subject: Re: btokup().. patch to STYLE(9) (fwd)
In-reply-to: Your message of "Thu, 28 Jan 1999 17:38:52 PST."
<199901290138.RAA16433@apollo.backplane.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Thu, 28 Jan 1999 17:42:29 -0800
From: Mike Smith <mike@smith.net.au>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
> Beyond that it's pretty much just &/| and &&/|| precedences. I personally
> *never* liked the fact that C gave & and | ( and && and || ) differentl
> precedences. IMHO, the arithmatic-vs-shift parenthesization is something
> I've *always* done myself, so I don't mind those warnings either.
This comes straight from elementary boolean algebra. Not doing this
would be unthinkable.
--
\\ Sometimes you're ahead, \\ Mike Smith
\\ sometimes you're behind. \\ mike@smith.net.au
\\ The race is long, and in the \\ msmith@freebsd.org
\\ end it's only with yourself. \\ msmith@cdrom.com
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Thu Jan 28 17:57:49 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id RAA27319
for freebsd-current-outgoing; Thu, 28 Jan 1999 17:57:49 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA27311
for <current@FreeBSD.ORG>; Thu, 28 Jan 1999 17:57:46 -0800 (PST)
(envelope-from julian@whistle.com)
Received: (from daemon@localhost)
by alpo.whistle.com (8.8.5/8.8.5) id RAA25137;
Thu, 28 Jan 1999 17:54:51 -0800 (PST)
Received: from current1.whistle.com(207.76.205.22)
via SMTP by alpo.whistle.com, id smtpde25133; Fri Jan 29 01:54:41 1999
Date: Thu, 28 Jan 1999 17:54:34 -0800 (PST)
From: Julian Elischer <julian@whistle.com>
To: Mike Smith <mike@smith.net.au>
cc: Matthew Dillon <dillon@apollo.backplane.com>,
Archie Cobbs <archie@whistle.com>, Nate Williams <nate@mt.sri.com>,
current@FreeBSD.ORG
Subject: Re: btokup().. patch to STYLE(9) (fwd)
In-Reply-To: <199901290142.RAA01512@dingo.cdrom.com>
Message-ID: <Pine.BSF.3.95.990128175221.11856L-100000@current1.whistle.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
yeah but not a SINGLE person has said to not commit the patch to style(9)
so I'm going to do it later tonight..
(It doesn't make extra braces MANDATORY but it does ALLOW them.)
julian
(if this doesn't bring some NEYs I'll be amazed..)
On Thu, 28 Jan 1999, Mike Smith wrote:
> > Beyond that it's pretty much just &/| and &&/|| precedences. I personally
> > *never* liked the fact that C gave & and | ( and && and || ) differentl
> > precedences. IMHO, the arithmatic-vs-shift parenthesization is something
> > I've *always* done myself, so I don't mind those warnings either.
>
> This comes straight from elementary boolean algebra. Not doing this
> would be unthinkable.
>
> --
> \\ Sometimes you're ahead, \\ Mike Smith
> \\ sometimes you're behind. \\ mike@smith.net.au
> \\ The race is long, and in the \\ msmith@freebsd.org
> \\ end it's only with yourself. \\ msmith@cdrom.com
>
>
>
> To Unsubscribe: send mail to majordomo@FreeBSD.org
> with "unsubscribe freebsd-current" in the body of the message
>
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Thu Jan 28 18:05:07 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id SAA28098
for freebsd-current-outgoing; Thu, 28 Jan 1999 18:05:07 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA28082
for <current@FreeBSD.ORG>; Thu, 28 Jan 1999 18:05:03 -0800 (PST)
(envelope-from dillon@apollo.backplane.com)
Received: (from dillon@localhost)
by apollo.backplane.com (8.9.2/8.9.1) id SAA16649;
Thu, 28 Jan 1999 18:05:02 -0800 (PST)
(envelope-from dillon)
Date: Thu, 28 Jan 1999 18:05:02 -0800 (PST)
From: Matthew Dillon <dillon@apollo.backplane.com>
Message-Id: <199901290205.SAA16649@apollo.backplane.com>
To: Matthew Dillon <dillon@apollo.backplane.com>
Cc: Archie Cobbs <archie@whistle.com>, nate@mt.sri.com (Nate Williams),
current@FreeBSD.ORG
Subject: Re: btokup().. patch to STYLE(9) (fwd)
References: <199901290056.QAA07338@bubba.whistle.com> <199901290138.RAA16433@apollo.backplane.com>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
: that day on, I never put assignments in conditionals with an explicit
: boolean test, aka if ((a = b) != 0) { ... }.
Oops, I meant 'without an explicit boolean test'.
-Matt
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Thu Jan 28 18:25:20 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id SAA01151
for freebsd-current-outgoing; Thu, 28 Jan 1999 18:25:20 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.26.10.9])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA01141
for <current@FreeBSD.ORG>; Thu, 28 Jan 1999 18:25:17 -0800 (PST)
(envelope-from bde@godzilla.zeta.org.au)
Received: (from bde@localhost)
by godzilla.zeta.org.au (8.8.7/8.8.7) id NAA16113;
Fri, 29 Jan 1999 13:25:07 +1100
Date: Fri, 29 Jan 1999 13:25:07 +1100
From: Bruce Evans <bde@zeta.org.au>
Message-Id: <199901290225.NAA16113@godzilla.zeta.org.au>
To: julian@whistle.com, mike@smith.net.au
Subject: Re: btokup().. patch to STYLE(9) (fwd)
Cc: archie@whistle.com, current@FreeBSD.ORG, dillon@apollo.backplane.com,
nate@mt.sri.com
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
>yeah but not a SINGLE person has said to not commit the patch to style(9)
Of course I object.
>so I'm going to do it later tonight..
If you commit it, then I will back it out.
Bruce
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Thu Jan 28 18:37:16 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id SAA02542
for freebsd-current-outgoing; Thu, 28 Jan 1999 18:37:16 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from cheddar.netmonger.net (cheddar.netmonger.net [209.54.21.140])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA02528
for <current@freebsd.org>; Thu, 28 Jan 1999 18:37:13 -0800 (PST)
(envelope-from chris@cheddar.netmonger.net)
Received: (from chris@localhost)
by cheddar.netmonger.net (8.8.8/8.8.8) id VAA26550;
Thu, 28 Jan 1999 21:37:11 -0500 (EST)
Message-ID: <19990128213707.A25313@netmonger.net>
Date: Thu, 28 Jan 1999 21:37:10 -0500
From: Christopher Masto <chris@netmonger.net>
To: current@FreeBSD.ORG
Subject: Re: btokup().. patch to STYLE(9) (fwd)
References: <199901290225.NAA16113@godzilla.zeta.org.au>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.91.1i
In-Reply-To: <199901290225.NAA16113@godzilla.zeta.org.au>; from Bruce Evans on Fri, Jan 29, 1999 at 01:25:07PM +1100
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
On Fri, Jan 29, 1999 at 01:25:07PM +1100, Bruce Evans wrote:
> >yeah but not a SINGLE person has said to not commit the patch to style(9)
>
> Of course I object.
My mail system appears to have accidentally deleted your excellent and
well-considered reasons for not allowing style(9) to say "it's OK to
use extra braces or parenthesis when it makes your code more
comprehensible". Perhaps you could repeat it?
> >so I'm going to do it later tonight..
>
> If you commit it, then I will back it out.
This list is getting almost as bad as perl5-porters.
--
Christopher Masto Director of Operations NetMonger Communications
chris@netmonger.net info@netmonger.net http://www.netmonger.net
"Good tools allow users to do stupid things." -- Clay Shirky
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Thu Jan 28 18:45:47 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id SAA03728
for freebsd-current-outgoing; Thu, 28 Jan 1999 18:45:47 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA03723
for <current@FreeBSD.ORG>; Thu, 28 Jan 1999 18:45:46 -0800 (PST)
(envelope-from julian@whistle.com)
Received: (from daemon@localhost)
by alpo.whistle.com (8.8.5/8.8.5) id SAA27213;
Thu, 28 Jan 1999 18:42:30 -0800 (PST)
Received: from current1.whistle.com(207.76.205.22)
via SMTP by alpo.whistle.com, id smtpda27206; Fri Jan 29 02:42:28 1999
Date: Thu, 28 Jan 1999 18:42:22 -0800 (PST)
From: Julian Elischer <julian@whistle.com>
To: Bruce Evans <bde@zeta.org.au>
cc: mike@smith.net.au, archie@whistle.com, current@FreeBSD.ORG,
dillon@apollo.backplane.com, nate@mt.sri.com
Subject: Re: btokup().. patch to STYLE(9) (fwd)
In-Reply-To: <199901290225.NAA16113@godzilla.zeta.org.au>
Message-ID: <Pine.BSF.3.95.990128184127.11856M-100000@current1.whistle.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
so far you are the first and only objector..
which makes you outnumbered by 10 to 1 on email counts..
On Fri, 29 Jan 1999, Bruce Evans wrote:
> >yeah but not a SINGLE person has said to not commit the patch to style(9)
>
> Of course I object.
>
> >so I'm going to do it later tonight..
>
> If you commit it, then I will back it out.
>
> Bruce
>
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Thu Jan 28 18:46:18 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id SAA03834
for freebsd-current-outgoing; Thu, 28 Jan 1999 18:46:18 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from speed.rcc.on.ca (radio163.mipps.net [205.189.197.163] (may be forged))
by hub.freebsd.org (8.8.8/8.8.8) with SMTP id SAA03821
for <current@FreeBSD.ORG>; Thu, 28 Jan 1999 18:46:16 -0800 (PST)
(envelope-from idiotswitch@beer.com)
Received: from chopper ([207.164.233.119]) by speed.rcc.on.ca (8.6.12/8.6.9) with SMTP id WAA00211 for <current@FreeBSD.ORG>; Thu, 28 Jan 1999 22:55:42 -0500
Message-ID: <001e01be4a68$1f4ac2c0$1900000a@chopper.my.intranet>
Reply-To: "IdiotSwitch Editor" <idiotswitch@beer.com>
From: "IdiotSwitch Editor" <idiotswitch@beer.com>
To: <current@FreeBSD.ORG>
Subject: Ideas?
Date: Wed, 27 Jan 1999 21:44:18 -0500
MIME-Version: 1.0
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 4.72.3155.0
X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3155.0
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
I can't code, so I wouldn't know how to implement these. Or even if it's
possible.
Parallel device loading. I know that freebsd's boot sequence can continue
loading new devices while waiting for other devices to respond with irq's
and whatnot. However, could this be taken a step further and have multiple
devices actually searched in parallel? Things such as network cards could
be scanned for at the same time as harddisks. Would that save time? I know
harddisks (IDE ones anyway) take a little while to respond.
The other thing I notice is that fsck, when it runs only does one disk at a
given time. I can see only doing one partition of a disk at a time (for
obvious reasons), but would it not be possible to run it on say wd0 and wd2
at the same time? Yeah.. I know, shut down properly and I won't have that
problem :) Thing is, various things have crashed my system twice, and
that's the most annoying part.
Anyhow. Like I said. I can't do it myself, but leave it up to you to
consider the importance and possibly implementation strategy.
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Thu Jan 28 19:01:21 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id TAA05518
for freebsd-current-outgoing; Thu, 28 Jan 1999 19:01:21 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA05508
for <current@FreeBSD.ORG>; Thu, 28 Jan 1999 19:01:18 -0800 (PST)
(envelope-from julian@whistle.com)
Received: (from daemon@localhost)
by alpo.whistle.com (8.8.5/8.8.5) id SAA27559;
Thu, 28 Jan 1999 18:55:57 -0800 (PST)
Received: from current1.whistle.com(207.76.205.22)
via SMTP by alpo.whistle.com, id smtpdp27553; Fri Jan 29 02:55:47 1999
Date: Thu, 28 Jan 1999 18:55:42 -0800 (PST)
From: Julian Elischer <julian@whistle.com>
To: IdiotSwitch Editor <idiotswitch@beer.com>
cc: current@FreeBSD.ORG
Subject: Re: Ideas?
In-Reply-To: <001e01be4a68$1f4ac2c0$1900000a@chopper.my.intranet>
Message-ID: <Pine.BSF.3.95.990128185403.11856O-100000@current1.whistle.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
On Wed, 27 Jan 1999, IdiotSwitch Editor wrote:
> I can't code, so I wouldn't know how to implement these. Or even if it's
> possible.
>
> Parallel device loading. I know that freebsd's boot sequence can continue
> loading new devices while waiting for other devices to respond with irq's
> and whatnot. However, could this be taken a step further and have multiple
> devices actually searched in parallel? Things such as network cards could
> be scanned for at the same time as harddisks. Would that save time? I know
> harddisks (IDE ones anyway) take a little while to respond.
Already being worked on..
>
> The other thing I notice is that fsck, when it runs only does one disk at a
> given time. I can see only doing one partition of a disk at a time (for
> obvious reasons), but would it not be possible to run it on say wd0 and wd2
> at the same time? Yeah.. I know, shut down properly and I won't have that
> problem :) Thing is, various things have crashed my system twice, and
> that's the most annoying part.
fsck already does this in some cases..
(read the man page for full details I guess)
>
> Anyhow. Like I said. I can't do it myself, but leave it up to you to
> consider the importance and possibly implementation strategy.
good try.
:-)
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Thu Jan 28 19:09:30 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id TAA06221
for freebsd-current-outgoing; Thu, 28 Jan 1999 19:09:30 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA06213
for <current@freebsd.org>; Thu, 28 Jan 1999 19:09:28 -0800 (PST)
(envelope-from jdp@polstra.com)
Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13])
by wall.polstra.com (8.9.1/8.9.1) with ESMTP id TAA10489;
Thu, 28 Jan 1999 19:09:27 -0800 (PST)
(envelope-from jdp@polstra.com)
From: John Polstra <jdp@polstra.com>
Received: (from jdp@localhost)
by vashon.polstra.com (8.9.1/8.9.1) id TAA13468;
Thu, 28 Jan 1999 19:09:27 -0800 (PST)
(envelope-from jdp@polstra.com)
Date: Thu, 28 Jan 1999 19:09:27 -0800 (PST)
Message-Id: <199901290309.TAA13468@vashon.polstra.com>
To: julian@whistle.com
Subject: Re: btokup().. patch to STYLE(9) (fwd)
In-Reply-To: <Pine.BSF.3.95.990128184127.11856M-100000@current1.whistle.com>
Organization: Polstra & Co., Seattle, WA
Cc: current@FreeBSD.ORG
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
In article <Pine.BSF.3.95.990128184127.11856M-100000@current1.whistle.com>,
Julian Elischer <julian@whistle.com> wrote:
> so far you are the first and only objector..
> which makes you outnumbered by 10 to 1 on email counts..
Uh, votes last longer than 8 hours around here. You should give
people 3 days minimum to respond. We don't all have pagers hooked
up to our mail systems so that we can instantly find out your latest
thoughts, you know. :-)
Even on the core list we allow 3 days.
John
--
John Polstra jdp@polstra.com
John D. Polstra & Co., Inc. Seattle, Washington USA
"Nobody ever went broke underestimating the taste of the American public."
-- H. L. Mencken
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Thu Jan 28 19:10:30 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id TAA06433
for freebsd-current-outgoing; Thu, 28 Jan 1999 19:10:30 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from zeus.theinternet.com.au (zeus.theinternet.com.au [203.34.176.2])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA06423
for <current@FreeBSD.ORG>; Thu, 28 Jan 1999 19:10:26 -0800 (PST)
(envelope-from akm@zeus.theinternet.com.au)
Received: (from akm@localhost)
by zeus.theinternet.com.au (8.8.7/8.8.7) id NAA25300;
Fri, 29 Jan 1999 13:09:55 +1000 (EST)
(envelope-from akm)
From: Andrew Kenneth Milton <akm@zeus.theinternet.com.au>
Message-Id: <199901290309.NAA25300@zeus.theinternet.com.au>
Subject: Re: btokup().. patch to STYLE(9) (fwd)
In-Reply-To: <Pine.BSF.3.95.990128175221.11856L-100000@current1.whistle.com> from Julian Elischer at "Jan 28, 99 05:54:34 pm"
To: julian@whistle.com (Julian Elischer)
Date: Fri, 29 Jan 1999 13:09:55 +1000 (EST)
Cc: mike@smith.net.au, dillon@apollo.backplane.com, archie@whistle.com,
nate@mt.sri.com, current@FreeBSD.ORG
X-Mailer: ELM [version 2.4ME+ PL32 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
+----[ Julian Elischer ]---------------------------------------------
| yeah but not a SINGLE person has said to not commit the patch to style(9)
| so I'm going to do it later tonight..
| (It doesn't make extra braces MANDATORY but it does ALLOW them.)
|
| julian
| (if this doesn't bring some NEYs I'll be amazed..)
Only from people who don't seem to cut code in the real world.
Every "Coding Standards" document I've seen requires the braces. I've
worked in more than one AS3563/ISO9001 certified environment, none of
those had braces as optional.
There are only disadvantages to leaving them out.
FreeBSD is a large project, it is worked on by a large number of
people, some of whom won't hang around to maintain what they've done.
Adoption of corporate type standards for code review should not come
as a surprise to anyone, and egos aside, shouldn't meet with any
resistance.
On a parallel note, anyone know what the procedure is for accreditation
in the US for ISO9001 (I know it used to be both lengthy and expensive
here for AS3563 [which is now ISO9001 for software]).
That'd be a nice logo to put on the CD Cover, which might also give
FreeBSD some more corporate acceptance (note I didn't say it was
meaningful).
--
Totally Holistic Enterprises Internet| P:+61 7 3870 0066 | Andrew
The Internet (Aust) Pty Ltd | F:+61 7 3870 4477 | Milton
ACN: 082 081 472 | M:+61 416 022 411 |72 Col .Sig
PO Box 837 Indooroopilly QLD 4068 |akm@theinternet.com.au|Specialist
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Thu Jan 28 19:21:16 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id TAA08377
for freebsd-current-outgoing; Thu, 28 Jan 1999 19:21:16 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA08362
for <current@freebsd.org>; Thu, 28 Jan 1999 19:21:14 -0800 (PST)
(envelope-from julian@whistle.com)
Received: (from daemon@localhost)
by alpo.whistle.com (8.8.5/8.8.5) id TAA28161;
Thu, 28 Jan 1999 19:18:30 -0800 (PST)
Received: from current1.whistle.com(207.76.205.22)
via SMTP by alpo.whistle.com, id smtpdh28159; Fri Jan 29 03:18:24 1999
Date: Thu, 28 Jan 1999 19:18:20 -0800 (PST)
From: Julian Elischer <julian@whistle.com>
To: John Polstra <jdp@polstra.com>
cc: current@FreeBSD.ORG
Subject: Re: btokup().. patch to STYLE(9) (fwd)
In-Reply-To: <199901290309.TAA13468@vashon.polstra.com>
Message-ID: <Pine.BSF.3.95.990128191353.11856Q-100000@current1.whistle.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
On Thu, 28 Jan 1999, John Polstra wrote:
> In article <Pine.BSF.3.95.990128184127.11856M-100000@current1.whistle.com>,
> Julian Elischer <julian@whistle.com> wrote:
> > so far you are the first and only objector..
> > which makes you outnumbered by 10 to 1 on email counts..
>
> Uh, votes last longer than 8 hours around here. You should give
> people 3 days minimum to respond. We don't all have pagers hooked
> up to our mail systems so that we can instantly find out your latest
> thoughts, you know. :-)
Actually it's been well over 8 hours.. I did it last night so
it's nearing a day. I wasn't saying I had decided the matter, I was saying
that I'm completely amazed that there has been only one negative email
on the suggestion so far..
I didn't call for a vote, I called for comments. :-)
>
> Even on the core list we allow 3 days.
I wouldn't know, since the core cabal is a closed group.
julian
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Thu Jan 28 19:27:10 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id TAA09073
for freebsd-current-outgoing; Thu, 28 Jan 1999 19:27:10 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.26.10.9])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA09050
for <current@FreeBSD.ORG>; Thu, 28 Jan 1999 19:27:01 -0800 (PST)
(envelope-from bde@godzilla.zeta.org.au)
Received: (from bde@localhost)
by godzilla.zeta.org.au (8.8.7/8.8.7) id OAA22743;
Fri, 29 Jan 1999 14:26:51 +1100
Date: Fri, 29 Jan 1999 14:26:51 +1100
From: Bruce Evans <bde@zeta.org.au>
Message-Id: <199901290326.OAA22743@godzilla.zeta.org.au>
To: chris@netmonger.net, current@FreeBSD.ORG
Subject: Re: btokup().. patch to STYLE(9) (fwd)
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
>> Of course I object.
>
>My mail system appears to have accidentally deleted your excellent and
>well-considered reasons for not allowing style(9) to say "it's OK to
>use extra braces or parenthesis when it makes your code more
>comprehensible".
Perhaps it is in some of your backups from 5 years ago.
>Perhaps you could repeat it?
style(9) is supposed to document KNF. It is not supposed to document
best coding practices, julian's preferences or bde's preferences.
Bruce
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Thu Jan 28 19:31:07 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id TAA09569
for freebsd-current-outgoing; Thu, 28 Jan 1999 19:31:07 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from peach.ocn.ne.jp (peach.ocn.ne.jp [210.145.254.87])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA09564
for <freebsd-current@FreeBSD.ORG>; Thu, 28 Jan 1999 19:31:05 -0800 (PST)
(envelope-from dcs@newsguy.com)
Received: from newsguy.com by peach.ocn.ne.jp (8.9.1a/OCN) id MAA27490; Fri, 29 Jan 1999 12:30:51 +0900 (JST)
Message-ID: <36B12B51.9B9167DE@newsguy.com>
Date: Fri, 29 Jan 1999 12:30:25 +0900
From: "Daniel C. Sobral" <dcs@newsguy.com>
X-Mailer: Mozilla 4.5 [en] (Win98; I)
X-Accept-Language: pt-BR,ja
MIME-Version: 1.0
To: Mike Smith <mike@smith.net.au>
CC: Patrick Hartling <mystify@friley-184-92.res.iastate.edu>,
freebsd-current@FreeBSD.ORG
Subject: Re: Reading a text file with BTX
References: <199901282243.OAA00567@dingo.cdrom.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
Mike Smith wrote:
>
> Ugh. No. BTX is the kernel that boot2 and the loader use.
Well, that much I knew... It's just that I took to calling boot2 as
"btx"... :-)
> boot0 is the module that gives you the F? prompt
What F? prompt???
> boot1 is invisible, it just loads boot2
> boot2 spins the | to begin with, and if you hit a key while it's paused,
> you get it's prompt 'boot:', it starts the loader.
Thanks. I have a clearer idea of it now. In which part of the disk
each one of these resides?
--
Daniel C. Sobral (8-DCS)
dcs@newsguy.com
If you sell your soul to the Devil and all you get is an MCSE from
it, you haven't gotten market rate.
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Thu Jan 28 19:51:05 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id TAA12096
for freebsd-current-outgoing; Thu, 28 Jan 1999 19:51:05 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA12091
for <current@FreeBSD.ORG>; Thu, 28 Jan 1999 19:51:04 -0800 (PST)
(envelope-from julian@whistle.com)
Received: (from daemon@localhost)
by alpo.whistle.com (8.8.5/8.8.5) id TAA28843;
Thu, 28 Jan 1999 19:41:35 -0800 (PST)
Received: from current1.whistle.com(207.76.205.22)
via SMTP by alpo.whistle.com, id smtpdN28841; Fri Jan 29 03:41:32 1999
Date: Thu, 28 Jan 1999 19:41:29 -0800 (PST)
From: Julian Elischer <julian@whistle.com>
To: Bruce Evans <bde@zeta.org.au>
cc: chris@netmonger.net, current@FreeBSD.ORG
Subject: Re: btokup().. patch to STYLE(9) (fwd)
In-Reply-To: <199901290326.OAA22743@godzilla.zeta.org.au>
Message-ID: <Pine.BSF.3.95.990128193713.11856S-100000@current1.whistle.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
On Fri, 29 Jan 1999, Bruce Evans wrote:
> style(9) is supposed to document KNF. It is not supposed to document
> best coding practices, julian's preferences or bde's preferences.
KNF is not a static thing that cannot be changed.
KNF is in effect whatever is written in style(9).
In case I hadn't made myself clear, I'm suggesting that we effectively
revise some aspects of FreeBSD's KNF.
The resounding responce SO FAR (except for you) has been either
"I don't really care about those changes" or "YES please!"
julian
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Thu Jan 28 19:57:18 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id TAA12908
for freebsd-current-outgoing; Thu, 28 Jan 1999 19:57:18 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from zeus.theinternet.com.au (zeus.theinternet.com.au [203.34.176.2])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA12903
for <current@FreeBSD.ORG>; Thu, 28 Jan 1999 19:57:15 -0800 (PST)
(envelope-from akm@zeus.theinternet.com.au)
Received: (from akm@localhost)
by zeus.theinternet.com.au (8.8.7/8.8.7) id NAA25923;
Fri, 29 Jan 1999 13:56:44 +1000 (EST)
(envelope-from akm)
From: Andrew Kenneth Milton <akm@zeus.theinternet.com.au>
Message-Id: <199901290356.NAA25923@zeus.theinternet.com.au>
Subject: Re: btokup().. patch to STYLE(9) (fwd)
In-Reply-To: <Pine.BSF.3.95.990128193713.11856S-100000@current1.whistle.com> from Julian Elischer at "Jan 28, 99 07:41:29 pm"
To: julian@whistle.com (Julian Elischer)
Date: Fri, 29 Jan 1999 13:56:44 +1000 (EST)
Cc: bde@zeta.org.au, chris@netmonger.net, current@FreeBSD.ORG
X-Mailer: ELM [version 2.4ME+ PL32 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
+----[ Julian Elischer ]---------------------------------------------
|
| On Fri, 29 Jan 1999, Bruce Evans wrote:
| > style(9) is supposed to document KNF. It is not supposed to document
| > best coding practices, julian's preferences or bde's preferences.
|
| KNF is not a static thing that cannot be changed.
| KNF is in effect whatever is written in style(9).
HISTORY
This man page is largely based on the src/admin/style/style file from the
BSD 4.4-Lite2 release, with a few updates to reflect the current practice
and desire of the FreeBSD project.
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
--
Totally Holistic Enterprises Internet| P:+61 7 3870 0066 | Andrew
The Internet (Aust) Pty Ltd | F:+61 7 3870 4477 | Milton
ACN: 082 081 472 | M:+61 416 022 411 |72 Col .Sig
PO Box 837 Indooroopilly QLD 4068 |akm@theinternet.com.au|Specialist
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Thu Jan 28 20:00:29 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id UAA13417
for freebsd-current-outgoing; Thu, 28 Jan 1999 20:00:29 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from spinner.netplex.com.au (spinner.netplex.com.au [202.12.86.3])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA13406
for <current@FreeBSD.ORG>; Thu, 28 Jan 1999 20:00:23 -0800 (PST)
(envelope-from peter@netplex.com.au)
Received: from spinner.netplex.com.au (localhost [127.0.0.1])
by spinner.netplex.com.au (8.9.2/8.9.2/Netplex) with ESMTP id LAA21875;
Fri, 29 Jan 1999 11:59:54 +0800 (WST)
(envelope-from peter@spinner.netplex.com.au)
Message-Id: <199901290359.LAA21875@spinner.netplex.com.au>
X-Mailer: exmh version 2.0.2 2/24/98
To: Bruce Evans <bde@zeta.org.au>
cc: chris@netmonger.net, current@FreeBSD.ORG
Subject: Re: btokup().. patch to STYLE(9) (fwd)
In-reply-to: Your message of "Fri, 29 Jan 1999 14:26:51 +1100."
<199901290326.OAA22743@godzilla.zeta.org.au>
Date: Fri, 29 Jan 1999 11:59:53 +0800
From: Peter Wemm <peter@netplex.com.au>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
Bruce Evans wrote:
[..]
> >Perhaps you could repeat it?
>
> style(9) is supposed to document KNF. It is not supposed to document
> best coding practices, julian's preferences or bde's preferences.
style(9) is not KNF, and never was intended to be. It's a FreeBSD style
guide that bears similarity to KNF because that's what it used as a
starting point.
As it has evolved it has *departed* from KNF to become more realistic and
useable in today's programming environment and practices.
Adding the freedom to add extra brackets and braces for readability has
been discussed a number of times and concensis each time (including at
least once in core, if my memory is correct) has been to add that
freedom - but it has just never actually been committed.
> Bruce
Cheers,
-Peter
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Thu Jan 28 20:02:33 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id UAA13606
for freebsd-current-outgoing; Thu, 28 Jan 1999 20:02:33 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from cheddar.netmonger.net (cheddar.netmonger.net [209.54.21.140])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA13594
for <current@FreeBSD.ORG>; Thu, 28 Jan 1999 20:02:30 -0800 (PST)
(envelope-from chris@cheddar.netmonger.net)
Received: (from chris@localhost)
by cheddar.netmonger.net (8.8.8/8.8.8) id XAA03888;
Thu, 28 Jan 1999 23:02:23 -0500 (EST)
Message-ID: <19990128230223.A1973@netmonger.net>
Date: Thu, 28 Jan 1999 23:02:23 -0500
From: Christopher Masto <chris@netmonger.net>
To: Bruce Evans <bde@zeta.org.au>, current@FreeBSD.ORG
Subject: Re: btokup().. patch to STYLE(9) (fwd)
References: <199901290326.OAA22743@godzilla.zeta.org.au>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.91.1i
In-Reply-To: <199901290326.OAA22743@godzilla.zeta.org.au>; from Bruce Evans on Fri, Jan 29, 1999 at 02:26:51PM +1100
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
On Fri, Jan 29, 1999 at 02:26:51PM +1100, Bruce Evans wrote:
> >My mail system appears to have accidentally deleted your excellent and
> >well-considered reasons for not allowing style(9) to say "it's OK to
> >use extra braces or parenthesis when it makes your code more
> >comprehensible".
>
> Perhaps it is in some of your backups from 5 years ago.
>
> >Perhaps you could repeat it?
>
> style(9) is supposed to document KNF. It is not supposed to document
> best coding practices, julian's preferences or bde's preferences.
So kernel code should not follow best coding practices (remember, the
current style guide says "Don't use parenthesis unless they're
required for precedence"). It should be a _restriction_ on FreeBSD
code (and not just kernel code:
This file specifies the preferred style for kernel source files in the
FreeBSD source tree. It is also a guide for preferred user land code
style.
) that parenthesis are not allowed, even if they aid readability and
maintainability, just because they are not required for precedence.
The document is in error one way or the other. It calls itself a
"style guide", starts out using the word "preferred", and contains
lots of "dos" and "don'ts". If it is going to make coding style
suggestions, they should be useful suggestions. "Parenthesis are
allowed to make your code easier to read, even if not strictly
required by the compiler" is a much more useful suggestion than what
is currently there. If it's not making coding suggestions, then it
should not use words like "do" and "don't", and the introduction
should be rewritten. And in my opinion, it should then be deleted
because it would be of no value.
Not everyone comes to FreeBSD with the same background and
expectations. People WILL read a document called "FreeBSD Style
Guide" and expect that it DOES contain "best coding practices", or at
least the preferences of the FreeBSD core team. Such a document
should either not be provided, peppered with disclaimers about its
purpose, or (IMHO preferably) contain correct recommendations.
The inertia here sometimes is truly astounding. The apparent
infallability of code and historical documents anyone tries
to update suggests that the Pope was involved with CSRG.
Encouraging unreadable code is something I find highly questionable.
--
Christopher Masto Director of Operations NetMonger Communications
chris@netmonger.net info@netmonger.net http://www.netmonger.net
"Good tools allow users to do stupid things." -- Clay Shirky
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Thu Jan 28 20:03:39 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id UAA13710
for freebsd-current-outgoing; Thu, 28 Jan 1999 20:03:39 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from allegro.lemis.com (allegro.lemis.com [192.109.197.134])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA13698
for <current@FreeBSD.ORG>; Thu, 28 Jan 1999 20:03:35 -0800 (PST)
(envelope-from grog@freebie.lemis.com)
Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137])
by allegro.lemis.com (8.9.1/8.9.0) with ESMTP id OAA29020;
Fri, 29 Jan 1999 14:33:19 +1030 (CST)
Received: (from grog@localhost)
by freebie.lemis.com (8.9.2/8.9.0) id OAA14555;
Fri, 29 Jan 1999 14:32:40 +1030 (CST)
Date: Fri, 29 Jan 1999 14:32:40 +1030
From: Greg Lehey <grog@lemis.com>
To: Peter Jeremy <peter.jeremy@auss2.alcatel.com.au>
Cc: current@FreeBSD.ORG
Subject: Re: indent(1) and style(9) (was: btokup() macro in sys/malloc.h)
Message-ID: <19990129143239.J8473@freebie.lemis.com>
References: <99Jan29.074452est.40330@border.alcanet.com.au>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.95.1i
In-Reply-To: <99Jan29.074452est.40330@border.alcanet.com.au>; from Peter Jeremy on Fri, Jan 29, 1999 at 07:54:18AM +1100
WWW-Home-Page: http://www.lemis.com/~grog
Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia
Phone: +61-8-8388-8286
Fax: +61-8-8388-8725
Mobile: +61-41-739-7062
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
On Friday, 29 January 1999 at 7:54:18 +1100, Peter Jeremy wrote:
> Luigi Rizzo <luigi@labinfo.iet.unipi.it>
>> not speaking about vinum, but to me, the indentation of 8 char and
>> line length of 80 chars are almost mutually exclusive.
>>
>> See e.g. tcp_input.c ip_input.c and many network device drivers as
>> an example -- basically all places where, for efficiency reasons,
>> the code tries to expand in-line various block,
>
> According to most of the coding standards I've read, readability
> (and hence maintainability) come before efficiency. That said, I
> agree that efficiency _is_ an issue within the kernel's critical
> paths (the TCP/IP code being one).
>
> Judicious use of inline functions (and macros) should help move
> code to the left - and may even make it more understandable.
One man's readability is another man's illegibility. I certainly
think that macros can really obfuscate things. And moving code away
into separate functions also makes it difficult to see the Big
Picture. My real issue with style(9) is that it perpetuates the style
of the early 70s for no good reason. On the other hand, I very much
*do* support a consistent coding style.
Greg
--
See complete headers for address, home page and phone numbers
finger grog@lemis.com for PGP public key
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Thu Jan 28 20:17:07 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id UAA14830
for freebsd-current-outgoing; Thu, 28 Jan 1999 20:17:07 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from rover.village.org (rover.village.org [204.144.255.49])
by hub.freebsd.org (8.8.8/8.8.8) with SMTP id UAA14823
for <current@freebsd.org>; Thu, 28 Jan 1999 20:17:04 -0800 (PST)
(envelope-from imp@village.org)
Received: from harmony [10.0.0.6]
by rover.village.org with esmtp (Exim 1.71 #1)
id 1065Ma-0005ly-00; Thu, 28 Jan 1999 21:17:00 -0700
Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.1/8.8.3) with ESMTP id VAA62851; Thu, 28 Jan 1999 21:16:15 -0700 (MST)
Message-Id: <199901290416.VAA62851@harmony.village.org>
To: "Jordan K. Hubbard" <jkh@zippy.cdrom.com>
Subject: Re: cvs commit: src/sys/i386/eisa ahb.c
Cc: current@FreeBSD.ORG
In-reply-to: Your message of "Thu, 28 Jan 1999 00:48:21 PST."
<83910.917513301@zippy.cdrom.com>
References: <83910.917513301@zippy.cdrom.com>
Date: Thu, 28 Jan 1999 21:16:15 -0700
From: Warner Losh <imp@village.org>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
In message <83910.917513301@zippy.cdrom.com> "Jordan K. Hubbard" writes:
: Any other strategy will, eventually, have you
: charging around the crowd, waving your golf club and slobbering
: maniacally - not really the kind of public image you want to be
: cultivating here. :-)
I'm sure there are many examples of this in the bsd community.
Given that there is a good potential to introduce bugs, the age old
"have another committer review it" would likely allay many of the
fears that have been expressed. In the past that has been the MO for
this group.
Warner
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Thu Jan 28 20:35:42 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id UAA17147
for freebsd-current-outgoing; Thu, 28 Jan 1999 20:35:42 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from abby.skypoint.net (abby.skypoint.net [199.86.32.252])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA17135
for <current@FreeBSD.ORG>; Thu, 28 Jan 1999 20:35:40 -0800 (PST)
(envelope-from bruce@zuhause.mn.org)
Received: (from uucp@localhost)
by abby.skypoint.net (8.8.7/jl 1.3) with UUCP id WAA11222; Thu, 28 Jan 1999 22:35:37 -0600 (CST)
Received: (from bruce@localhost)
by zuhause.mn.org (8.9.2/8.9.1) id WAA29005;
Thu, 28 Jan 1999 22:33:20 -0600 (CST)
(envelope-from bruce)
From: Bruce Albrecht <bruce@zuhause.mn.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <14001.14864.712443.443655@zuhause.zuhause.mn.org>
Date: Thu, 28 Jan 1999 22:33:20 -0600 (CST)
To: oscentral@usa.net (Rod Taylor)
Cc: current@FreeBSD.ORG
Subject: Re: Ne2000 PCI Card
In-Reply-To: <199901282223.RAA32294@speed.rcc.on.ca>
References: <199901282223.RAA32294@speed.rcc.on.ca>
X-Mailer: VM 6.62 under 20.4 "Emerald" XEmacs Lucid
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
Rod Taylor writes:
> I have 2 cheap 100mbit nics (rj45 only). Both use the ReaTek 8139 chipset
> (from the best that I can tell). Both are PCI.
>
> I've attempted to use both cards in several PCI slots, under 2.2.8 and 3.0
> boot floppies, and a 3.0-stable (updated 2 days ago). None of these
> releases found either card in any situation.
>
> I believe the card should be detected as Ed0 (possibly ed1). I have used
> 3com pci cards in both machines under freebsd sucessfully and the ne2000
> cards function under windows and os/2.
The RealTek 8139 chipset is supported with the rl0 driver, and has
been supported since 3.0 was released. Bill Paul is the maintainer of
the driver. I think the GENERIC kernel should have been able to find
them. I've got a 8139 based NIC, and I have no complaints about its
performance at 10 Mbps, but it's a real dog at 100 Mbps. I'm only
able to achieve 45-50 Mbps throughput with a dual P6-200 machine, and
it uses nearly 30% of the CPU to do it.
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Thu Jan 28 20:35:54 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id UAA17202
for freebsd-current-outgoing; Thu, 28 Jan 1999 20:35:54 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from rover.village.org (rover.village.org [204.144.255.49])
by hub.freebsd.org (8.8.8/8.8.8) with SMTP id UAA17174
for <current@freebsd.org>; Thu, 28 Jan 1999 20:35:51 -0800 (PST)
(envelope-from imp@village.org)
Received: from harmony [10.0.0.6]
by rover.village.org with esmtp (Exim 1.71 #1)
id 1065en-0005mW-00; Thu, 28 Jan 1999 21:35:49 -0700
Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.1/8.8.3) with ESMTP id VAA62940; Thu, 28 Jan 1999 21:35:04 -0700 (MST)
Message-Id: <199901290435.VAA62940@harmony.village.org>
To: Julian Elischer <julian@whistle.com>
Subject: Re: btokup().. patch to STYLE(9) (fwd)
Cc: current@FreeBSD.ORG
In-reply-to: Your message of "Thu, 28 Jan 1999 18:42:22 PST."
<Pine.BSF.3.95.990128184127.11856M-100000@current1.whistle.com>
References: <Pine.BSF.3.95.990128184127.11856M-100000@current1.whistle.com>
Date: Thu, 28 Jan 1999 21:35:04 -0700
From: Warner Losh <imp@village.org>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
In message
<Pine.BSF.3.95.990128184127.11856M-100000@current1.whistle.com> Julian
Elischer writes:
: so far you are the first and only objector..
: which makes you outnumbered by 10 to 1 on email counts..
Unless things have changed a lot, bde counts 50x most people. This
isn't a democracy.
Warner
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Thu Jan 28 20:37:04 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id UAA17329
for freebsd-current-outgoing; Thu, 28 Jan 1999 20:37:04 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from ns.mt.sri.com (sri-gw.MT.net [206.127.105.141])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA17323
for <current@FreeBSD.ORG>; Thu, 28 Jan 1999 20:37:02 -0800 (PST)
(envelope-from nate@mt.sri.com)
Received: from mt.sri.com (rocky.mt.sri.com [206.127.76.100])
by ns.mt.sri.com (8.8.8/8.8.8) with SMTP id VAA21596;
Thu, 28 Jan 1999 21:36:44 -0700 (MST)
(envelope-from nate@rocky.mt.sri.com)
Received: by mt.sri.com (SMI-8.6/SMI-SVR4)
id VAA03963; Thu, 28 Jan 1999 21:36:43 -0700
Date: Thu, 28 Jan 1999 21:36:43 -0700
Message-Id: <199901290436.VAA03963@mt.sri.com>
From: Nate Williams <nate@mt.sri.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
To: Julian Elischer <julian@whistle.com>
Cc: Bruce Evans <bde@zeta.org.au>, chris@netmonger.net, current@FreeBSD.ORG
Subject: Re: btokup().. patch to STYLE(9) (fwd)
In-Reply-To: <Pine.BSF.3.95.990128193713.11856S-100000@current1.whistle.com>
References: <199901290326.OAA22743@godzilla.zeta.org.au>
<Pine.BSF.3.95.990128193713.11856S-100000@current1.whistle.com>
X-Mailer: VM 6.34 under 19.16 "Lille" XEmacs Lucid
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
> The resounding responce SO FAR (except for you) has been either
> "I don't really care about those changes" or "YES please!"
I've heard 3 'yes' votes, and I've abstained from commenting at this
time because I got beat up last time I mentioned something.
Nate
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Thu Jan 28 20:39:28 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id UAA17552
for freebsd-current-outgoing; Thu, 28 Jan 1999 20:39:28 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from rover.village.org (rover.village.org [204.144.255.49])
by hub.freebsd.org (8.8.8/8.8.8) with SMTP id UAA17547
for <current@freebsd.org>; Thu, 28 Jan 1999 20:39:25 -0800 (PST)
(envelope-from imp@village.org)
Received: from harmony [10.0.0.6]
by rover.village.org with esmtp (Exim 1.71 #1)
id 1065iF-0005mc-00; Thu, 28 Jan 1999 21:39:23 -0700
Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.1/8.8.3) with ESMTP id VAA62972; Thu, 28 Jan 1999 21:38:39 -0700 (MST)
Message-Id: <199901290438.VAA62972@harmony.village.org>
To: Christopher Masto <chris@netmonger.net>
Subject: Re: btokup().. patch to STYLE(9) (fwd)
Cc: current@FreeBSD.ORG
In-reply-to: Your message of "Thu, 28 Jan 1999 23:02:23 EST."
<19990128230223.A1973@netmonger.net>
References: <19990128230223.A1973@netmonger.net> <199901290326.OAA22743@godzilla.zeta.org.au>
Date: Thu, 28 Jan 1999 21:38:38 -0700
From: Warner Losh <imp@village.org>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
In message <19990128230223.A1973@netmonger.net> Christopher Masto writes:
: Encouraging unreadable code is something I find highly questionable.
Sadly, unreadable is in the eyes of the beholder. Code style is a
highly religious and contentious issue...
Warner
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Thu Jan 28 20:39:46 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id UAA17588
for freebsd-current-outgoing; Thu, 28 Jan 1999 20:39:46 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from ns.mt.sri.com (sri-gw.MT.net [206.127.105.141])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA17579
for <current@FreeBSD.ORG>; Thu, 28 Jan 1999 20:39:43 -0800 (PST)
(envelope-from nate@mt.sri.com)
Received: from mt.sri.com (rocky.mt.sri.com [206.127.76.100])
by ns.mt.sri.com (8.8.8/8.8.8) with SMTP id VAA21611;
Thu, 28 Jan 1999 21:39:37 -0700 (MST)
(envelope-from nate@rocky.mt.sri.com)
Received: by mt.sri.com (SMI-8.6/SMI-SVR4)
id VAA03999; Thu, 28 Jan 1999 21:39:36 -0700
Date: Thu, 28 Jan 1999 21:39:36 -0700
Message-Id: <199901290439.VAA03999@mt.sri.com>
From: Nate Williams <nate@mt.sri.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
To: Christopher Masto <chris@netmonger.net>
Cc: Bruce Evans <bde@zeta.org.au>, current@FreeBSD.ORG
Subject: Re: btokup().. patch to STYLE(9) (fwd)
In-Reply-To: <19990128230223.A1973@netmonger.net>
References: <199901290326.OAA22743@godzilla.zeta.org.au>
<19990128230223.A1973@netmonger.net>
X-Mailer: VM 6.34 under 19.16 "Lille" XEmacs Lucid
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
> The apparent infallability of code and historical documents anyone
> tries to update suggests that the Pope was involved with CSRG.
No, but in general the combined experience of the CSRG folks is greater
than most of the programmers here.
> Encouraging unreadable code is something I find highly questionable.
I find the KNF style highly readable. As a matter of fact, I find the
extra parentheses *often* to be a bunch of noise.
And, as Bruce implied, if you don't know your precedence rules, you
shouldn't be doing kernel programming.
Nate
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Thu Jan 28 20:40:56 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id UAA17765
for freebsd-current-outgoing; Thu, 28 Jan 1999 20:40:56 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from ns.mt.sri.com (sri-gw.MT.net [206.127.105.141])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA17758
for <current@FreeBSD.ORG>; Thu, 28 Jan 1999 20:40:53 -0800 (PST)
(envelope-from nate@mt.sri.com)
Received: from mt.sri.com (rocky.mt.sri.com [206.127.76.100])
by ns.mt.sri.com (8.8.8/8.8.8) with SMTP id VAA21643;
Thu, 28 Jan 1999 21:40:47 -0700 (MST)
(envelope-from nate@rocky.mt.sri.com)
Received: by mt.sri.com (SMI-8.6/SMI-SVR4)
id VAA04026; Thu, 28 Jan 1999 21:40:47 -0700
Date: Thu, 28 Jan 1999 21:40:47 -0700
Message-Id: <199901290440.VAA04026@mt.sri.com>
From: Nate Williams <nate@mt.sri.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
To: Warner Losh <imp@village.org>
Cc: "Jordan K. Hubbard" <jkh@zippy.cdrom.com>, current@FreeBSD.ORG
Subject: Re: cvs commit: src/sys/i386/eisa ahb.c
In-Reply-To: <199901290416.VAA62851@harmony.village.org>
References: <83910.917513301@zippy.cdrom.com>
<199901290416.VAA62851@harmony.village.org>
X-Mailer: VM 6.34 under 19.16 "Lille" XEmacs Lucid
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
> : Any other strategy will, eventually, have you
> : charging around the crowd, waving your golf club and slobbering
> : maniacally - not really the kind of public image you want to be
> : cultivating here. :-)
>
> Given that there is a good potential to introduce bugs, the age old
> "have another committer review it" would likely allay many of the
> fears that have been expressed. In the past that has been the MO for
> this group.
Thanks. This is what did not communicate, but intended to say. :)
Nate
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Thu Jan 28 20:55:37 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id UAA19977
for freebsd-current-outgoing; Thu, 28 Jan 1999 20:55:37 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from ceia.nordier.com (m2-34-dbn.dial-up.net [196.34.155.98])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA19962
for <freebsd-current@FreeBSD.ORG>; Thu, 28 Jan 1999 20:55:32 -0800 (PST)
(envelope-from rnordier@nordier.com)
Received: (from rnordier@localhost) by ceia.nordier.com (8.8.7/8.6.12) id GAA07540; Fri, 29 Jan 1999 06:53:34 +0200 (SAT)
From: Robert Nordier <rnordier@nordier.com>
Message-Id: <199901290453.GAA07540@ceia.nordier.com>
Subject: Re: Reading a text file with BTX
In-Reply-To: <36B12B51.9B9167DE@newsguy.com> from "Daniel C. Sobral" at "Jan 29, 99 12:30:25 pm"
To: dcs@newsguy.com (Daniel C. Sobral)
Date: Fri, 29 Jan 1999 06:53:30 +0200 (SAT)
Cc: mike@smith.net.au, mystify@friley-184-92.res.iastate.edu,
freebsd-current@FreeBSD.ORG
X-Mailer: ELM [version 2.4ME+ PL31 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
Daniel C. Sobral wrote:
> Mike Smith wrote:
> > boot0 is the module that gives you the F? prompt
>
> What F? prompt???
The boot manager menu, for example
F1 FreeBSD
F2 UNIX
F5 Drive 1
Default: F1
> > boot1 is invisible, it just loads boot2
> > boot2 spins the | to begin with, and if you hit a key while it's paused,
> > you get it's prompt 'boot:', it starts the loader.
>
> Thanks. I have a clearer idea of it now. In which part of the disk
> each one of these resides?
boot0 occupies the master boot record (sector 0 of the disk). Only
sliced disks (not "dangerously dedicated") have a proper mbr.
boot1 and boot2 occupy the boot blocks (the first 8K sectors of a ufs
partition) with the default being the 'a' partition.
--
Robert Nordier
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Thu Jan 28 20:56:10 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id UAA20103
for freebsd-current-outgoing; Thu, 28 Jan 1999 20:56:10 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from kot.ne.mediaone.net (kot.ne.mediaone.net [24.128.29.136])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA20098
for <current@freebsd.org>; Thu, 28 Jan 1999 20:56:09 -0800 (PST)
(envelope-from mi@kot.ne.mediaone.net)
Received: (from mi@localhost)
by kot.ne.mediaone.net (8.9.1a/8.9.1) id XAA28545
for current@freebsd.org; Thu, 28 Jan 1999 23:55:49 -0500 (EST)
From: Mikhail Teterin <mi@kot.ne.mediaone.net>
Message-Id: <199901290455.XAA28545@kot.ne.mediaone.net>
Subject: patch to STYLE(9) -- the other side
In-Reply-To: <19990128230223.A1973@netmonger.net> from Christopher Masto at "Jan 28, 1999 11:02:23 pm"
To: current@FreeBSD.ORG
Date: Thu, 28 Jan 1999 23:55:49 -0500 (EST)
X-Face: %UW#n0|w>ydeGt/b@1-.UFP=K^~-:0f#O:D7w<gv/&E-lL7twZCT8B~/PA4|\t$ti+22K">
hJ5G_<5143Bb3kOIs9XpX+"V+~$adGP:J|SLieM31VIhqXeLBli"<kcG^EOVih
y+z3/UR{6SCQ
X-Mailer: ELM [version 2.4ME+ PL49 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
Christopher Masto once stated:
=suggestions, they should be useful suggestions. "Parenthesis are
=allowed to make your code easier to read, even if not strictly
=required by the compiler" is a much more useful suggestion than what
=is currently there.
Some safeguard should be put to prevent falling from the other side,
such as in some places in TCL internals (restored by memory):
result = Tcl_CallSomething(.....);
if(result == TCL_OK) {
return TCL_OK;
};
return result;
Very readable...
-mi
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Thu Jan 28 20:58:55 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id UAA20406
for freebsd-current-outgoing; Thu, 28 Jan 1999 20:58:55 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from allegro.lemis.com (allegro.lemis.com [192.109.197.134])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA20391
for <current@FreeBSD.ORG>; Thu, 28 Jan 1999 20:58:51 -0800 (PST)
(envelope-from grog@freebie.lemis.com)
Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137])
by allegro.lemis.com (8.9.1/8.9.0) with ESMTP id PAA29280;
Fri, 29 Jan 1999 15:28:47 +1030 (CST)
Received: (from grog@localhost)
by freebie.lemis.com (8.9.2/8.9.0) id PAA14993;
Fri, 29 Jan 1999 15:28:38 +1030 (CST)
Date: Fri, 29 Jan 1999 15:28:38 +1030
From: Greg Lehey <grog@lemis.com>
To: Julian Elischer <julian@whistle.com>
Cc: Bruce Evans <bde@zeta.org.au>, chris@netmonger.net, current@FreeBSD.ORG
Subject: Re: btokup().. patch to STYLE(9) (fwd)
Message-ID: <19990129152838.L8473@freebie.lemis.com>
References: <199901290326.OAA22743@godzilla.zeta.org.au> <Pine.BSF.3.95.990128193713.11856S-100000@current1.whistle.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.95.1i
In-Reply-To: <Pine.BSF.3.95.990128193713.11856S-100000@current1.whistle.com>; from Julian Elischer on Thu, Jan 28, 1999 at 07:41:29PM -0800
WWW-Home-Page: http://www.lemis.com/~grog
Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia
Phone: +61-8-8388-8286
Fax: +61-8-8388-8725
Mobile: +61-41-739-7062
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
On Thursday, 28 January 1999 at 19:41:29 -0800, Julian Elischer wrote:
>
> On Fri, 29 Jan 1999, Bruce Evans wrote:
>> style(9) is supposed to document KNF. It is not supposed to document
>> best coding practices, julian's preferences or bde's preferences.
>
> KNF is not a static thing that cannot be changed.
> KNF is in effect whatever is written in style(9).
>
> In case I hadn't made myself clear, I'm suggesting that we effectively
> revise some aspects of FreeBSD's KNF.
>
> The resounding responce SO FAR (except for you) has been either
> "I don't really care about those changes" or "YES please!"
I don't think they're a good idea. Sure, I don't like style(9), but
if we're going to overhaul it, we should do it properly. Given the
diversity of opinion expressed every time anybody has tried the
smallest change, I don't see that happening, so why don't we just
forget the whole thing?
Greg
--
See complete headers for address, home page and phone numbers
finger grog@lemis.com for PGP public key
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Thu Jan 28 21:09:49 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id VAA21538
for freebsd-current-outgoing; Thu, 28 Jan 1999 21:09:49 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from allegro.lemis.com (allegro.lemis.com [192.109.197.134])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA21531
for <FreeBSD-current@FreeBSD.ORG>; Thu, 28 Jan 1999 21:09:46 -0800 (PST)
(envelope-from grog@freebie.lemis.com)
Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137])
by allegro.lemis.com (8.9.1/8.9.0) with ESMTP id PAA29303
for <FreeBSD-current@FreeBSD.ORG>; Fri, 29 Jan 1999 15:39:43 +1030 (CST)
Received: (from grog@localhost)
by freebie.lemis.com (8.9.2/8.9.0) id PAA15032
for FreeBSD-current@FreeBSD.ORG; Fri, 29 Jan 1999 15:39:41 +1030 (CST)
Date: Fri, 29 Jan 1999 15:39:41 +1030
From: Greg Lehey <grog@lemis.com>
To: FreeBSD current users <FreeBSD-current@FreeBSD.ORG>
Subject: The future of a.out support?
Message-ID: <19990129153941.M8473@freebie.lemis.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.95.1i
WWW-Home-Page: http://www.lemis.com/~grog
Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia
Phone: +61-8-8388-8286
Fax: +61-8-8388-8725
Mobile: +61-41-739-7062
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
Somebody just drew my attention to /usr/src/Makefile:
# Unless -DNOAOUT is specified, a `make world' with OBJFORMAT=elf will
# update the legacy support for aout. This includes all libraries, ld.so
# and boot objects. This part of build should be regarded as
# deprecated and you should _not_ expect to be able to do this past the
# release of 3.1. You have exactly one major release to move entirely
# to elf.
It was my understanding that the kernel would continue to support
a.out, and I think that's important. If FreeBSD can support SCO,
Linux, Solaris, BSDI, NetBSD and OpenBSD, it seems important that it
should also contain support for FreeBSD, even old, obsolete versions.
May I assume that this is the case, and that the comment applies only
to what ``make world'' builds? Even so, though, I think that it
is important to provide a way to build the libraries and ld.so if
necessary, though probably not in the world target.
Greg
--
See complete headers for address, home page and phone numbers
finger grog@lemis.com for PGP public key
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Thu Jan 28 21:22:43 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id VAA22725
for freebsd-current-outgoing; Thu, 28 Jan 1999 21:22:43 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from cimlogic.com.au (cimlog.lnk.telstra.net [139.130.51.31])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA22720
for <current@FreeBSD.ORG>; Thu, 28 Jan 1999 21:22:39 -0800 (PST)
(envelope-from jb@cimlogic.com.au)
Received: (from jb@localhost)
by cimlogic.com.au (8.9.1/8.9.1) id QAA12656;
Fri, 29 Jan 1999 16:26:53 +1100 (EST)
(envelope-from jb)
From: John Birrell <jb@cimlogic.com.au>
Message-Id: <199901290526.QAA12656@cimlogic.com.au>
Subject: Re: btokup().. patch to STYLE(9) (fwd)
In-Reply-To: <19990129152838.L8473@freebie.lemis.com> from Greg Lehey at "Jan 29, 1999 3:28:38 pm"
To: grog@lemis.com (Greg Lehey)
Date: Fri, 29 Jan 1999 16:26:53 +1100 (EST)
Cc: julian@whistle.com, bde@zeta.org.au, chris@netmonger.net,
current@FreeBSD.ORG
X-Mailer: ELM [version 2.4ME+ PL43 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
Greg Lehey wrote:
> I don't think they're a good idea. Sure, I don't like style(9), but
> if we're going to overhaul it, we should do it properly. Given the
> diversity of opinion expressed every time anybody has tried the
> smallest change, I don't see that happening, so why don't we just
> forget the whole thing?
Do you mean "forget changing style(9)" or "forget style(9) and
delete it"? I think you probably mean the former, despite the fact
that I was hoping for the latter. 8-)
I can image a new subscriber to this list reading a few of these messages
and thinking: "why would I want to use an OS developed by these people?".
We spend so much of our time looking up our own collective asses searching
for the meaning of life that it is no wonder FreeBSD doesn't feel like it
has a clear direction for the future. All people seem to want to do is
stomp on others who try to contribute something.
--
John Birrell - jb@cimlogic.com.au; jb@freebsd.org http://www.cimlogic.com.au/
CIMlogic Pty Ltd, GPO Box 117A, Melbourne Vic 3001, Australia +61 418 353 137
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Thu Jan 28 21:29:27 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id VAA23420
for freebsd-current-outgoing; Thu, 28 Jan 1999 21:29:27 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from allegro.lemis.com (allegro.lemis.com [192.109.197.134])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA23411
for <current@FreeBSD.ORG>; Thu, 28 Jan 1999 21:29:20 -0800 (PST)
(envelope-from grog@freebie.lemis.com)
Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137])
by allegro.lemis.com (8.9.1/8.9.0) with ESMTP id PAA29407;
Fri, 29 Jan 1999 15:59:12 +1030 (CST)
Received: (from grog@localhost)
by freebie.lemis.com (8.9.2/8.9.0) id PAA15170;
Fri, 29 Jan 1999 15:59:11 +1030 (CST)
Date: Fri, 29 Jan 1999 15:59:11 +1030
From: Greg Lehey <grog@lemis.com>
To: John Birrell <jb@cimlogic.com.au>
Cc: julian@whistle.com, bde@zeta.org.au, chris@netmonger.net,
current@FreeBSD.ORG
Subject: Re: btokup().. patch to STYLE(9) (fwd)
Message-ID: <19990129155911.Q8473@freebie.lemis.com>
References: <19990129152838.L8473@freebie.lemis.com> <199901290526.QAA12656@cimlogic.com.au>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.95.1i
In-Reply-To: <199901290526.QAA12656@cimlogic.com.au>; from John Birrell on Fri, Jan 29, 1999 at 04:26:53PM +1100
WWW-Home-Page: http://www.lemis.com/~grog
Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia
Phone: +61-8-8388-8286
Fax: +61-8-8388-8725
Mobile: +61-41-739-7062
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
On Friday, 29 January 1999 at 16:26:53 +1100, John Birrell wrote:
> Greg Lehey wrote:
>> I don't think they're a good idea. Sure, I don't like style(9), but
>> if we're going to overhaul it, we should do it properly. Given the
>> diversity of opinion expressed every time anybody has tried the
>> smallest change, I don't see that happening, so why don't we just
>> forget the whole thing?
>
> Do you mean "forget changing style(9)" or "forget style(9) and
> delete it"? I think you probably mean the former, despite the fact
> that I was hoping for the latter. 8-)
Yes, of course the former.
> I can image a new subscriber to this list reading a few of these
> messages and thinking: "why would I want to use an OS developed by
> these people?".
I'm sure they might. But they'd be wrong. I do believe that
maintaining a coherent style is a Good Thing. I just dislike the
particular style, but since it doesn't significantly lower my standard
of living, I put up with it :-)
Greg
--
See complete headers for address, home page and phone numbers
finger grog@lemis.com for PGP public key
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Thu Jan 28 21:36:49 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id VAA24034
for freebsd-current-outgoing; Thu, 28 Jan 1999 21:36:49 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from psf.Pinyon.ORG (ppp1-222.presc.dialup.futureone.com [209.250.11.222])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA24023
for <current@FreeBSD.ORG>; Thu, 28 Jan 1999 21:36:45 -0800 (PST)
(envelope-from rcarter@psf.Pinyon.ORG)
Received: from psf.Pinyon.ORG (localhost [127.0.0.1])
by psf.Pinyon.ORG (8.9.2/8.9.2) with ESMTP id WAA66051;
Thu, 28 Jan 1999 22:33:18 -0700 (MST)
(envelope-from rcarter@psf.Pinyon.ORG)
Message-Id: <199901290533.WAA66051@psf.Pinyon.ORG>
X-Mailer: exmh version 2.0.2 2/24/98
To: John Birrell <jb@cimlogic.com.au>
cc: current@FreeBSD.ORG
Subject: Re: btokup().. patch to STYLE(9) (fwd)
In-reply-to: Your message of "Fri, 29 Jan 1999 16:26:53 +1100."
<199901290526.QAA12656@cimlogic.com.au>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Thu, 28 Jan 1999 22:33:18 -0700
From: "Russell L. Carter" <rcarter@pinyon.org>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
[...]
%We spend so much of our time looking up our own collective asses searching
%for the meaning of life that it is no wonder FreeBSD doesn't feel like it
%has a clear direction for the future. All people seem to want to do is
%stomp on others who try to contribute something.
Come on John, this has *meaning*. For or against -Wall
*stands* for something! We have constitutional procedures
to solve this thing!
Ahem.
<regaining his senses>
Hear hear!
Russell
%
%--
%John Birrell - jb@cimlogic.com.au; jb@freebsd.org http://www.cimlogic.com.au/
%CIMlogic Pty Ltd, GPO Box 117A, Melbourne Vic 3001, Australia +61 418 353 137
%
%To Unsubscribe: send mail to majordomo@FreeBSD.org
%with "unsubscribe freebsd-current" in the body of the message
%
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Thu Jan 28 21:42:06 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id VAA24632
for freebsd-current-outgoing; Thu, 28 Jan 1999 21:42:06 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA24623
for <current@FreeBSD.ORG>; Thu, 28 Jan 1999 21:42:05 -0800 (PST)
(envelope-from dillon@apollo.backplane.com)
Received: (from dillon@localhost)
by apollo.backplane.com (8.9.2/8.9.1) id VAA00709;
Thu, 28 Jan 1999 21:41:51 -0800 (PST)
(envelope-from dillon)
Date: Thu, 28 Jan 1999 21:41:51 -0800 (PST)
From: Matthew Dillon <dillon@apollo.backplane.com>
Message-Id: <199901290541.VAA00709@apollo.backplane.com>
To: Bruce Evans <bde@zeta.org.au>
Cc: julian@whistle.com, mike@smith.net.au, archie@whistle.com,
current@FreeBSD.ORG
Subject: Re: btokup().. patch to STYLE(9) (fwd)
References: <199901290225.NAA16113@godzilla.zeta.org.au>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
The changes seem pretty reasonable, to me. I don't see why you are
so rabid about not allowing a few extra braces for clarity. It would
make the code more readable.
Besides, a great deal of the preexisting code already uses braces
even in single statement if()'s... and a great deal does not.
-Matt
Matthew Dillon
<dillon@backplane.com>
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Thu Jan 28 21:47:54 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id VAA25331
for freebsd-current-outgoing; Thu, 28 Jan 1999 21:47:54 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from cheddar.netmonger.net (cheddar.netmonger.net [209.54.21.140])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA25326
for <current@freebsd.org>; Thu, 28 Jan 1999 21:47:52 -0800 (PST)
(envelope-from chris@cheddar.netmonger.net)
Received: (from chris@localhost)
by cheddar.netmonger.net (8.8.8/8.8.8) id AAA11806;
Fri, 29 Jan 1999 00:47:49 -0500 (EST)
Message-ID: <19990129004749.A8899@netmonger.net>
Date: Fri, 29 Jan 1999 00:47:49 -0500
From: Christopher Masto <chris@netmonger.net>
To: current@FreeBSD.ORG
Subject: Re: btokup().. patch to STYLE(9) (fwd)
References: <199901290326.OAA22743@godzilla.zeta.org.au> <19990128230223.A1973@netmonger.net> <199901290439.VAA03999@mt.sri.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.91.1i
In-Reply-To: <199901290439.VAA03999@mt.sri.com>; from Nate Williams on Thu, Jan 28, 1999 at 09:39:36PM -0700
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
On Thu, Jan 28, 1999 at 09:39:36PM -0700, Nate Williams wrote:
> > Encouraging unreadable code is something I find highly questionable.
>
> I find the KNF style highly readable. As a matter of fact, I find the
> extra parentheses *often* to be a bunch of noise.
>
> And, as Bruce implied, if you don't know your precedence rules, you
> shouldn't be doing kernel programming.
Then either delete the style guide or write "DO NOT READ THIS UNLESS
YOU ARE AN APPROVED KERNEL PROGRAMMER" at the top.
Look, I program mainly in perl. I know the difference between
readability and noise. I know when it works just fine but it's making
trouble for those who come after you. And I know the difference
between a clever hack and a critical piece of production code.
Programming, particularly for a widely-used piece of critical system
software, should not be centered on showing off your incredible
prowess with precedence rules. Don't put "unnecessary" parens and
braces in your code if you don't want to. But if someone feels that
an expression is complicated enough to deserve giving the next person
to look at it a few hints as to its intended order of operations, then
please don't say they're not allowed to do so.
Even the great Berkeley gods have made mistakes. Anything that helps
avoid those mistakes, including -Wall, or extra parens and braces just
to make it more obvious what you're doing, is a good thing. It means
that FreeBSD will have fewer errors, fewer panics, and bugs will be
found more quickly.
Correct software is becoming an endangered species these days. When a
proposal is made that has no effect other than to allow a tiny bit of
freedom in the direction of enhanced correctness and maintainability,
please don't stand in the way.
As for noise, there are situations where excess punctuation is just
noise, and there are situations that benefit from more than the bare
minumum of decorations. Anyone doing kernel programming ought to know
the difference, just as they ought to know their precedence rules.
And there's always peer review for mere mortals who actually still
have peers.
I end with someone else's style guide, if only because of my evil streak:
o Just because you CAN do something a particular way
doesn't mean that you SHOULD do it that way.
[...]
Along the same lines, just because you CAN omit
parentheses in many places doesn't mean that you ought
to:
return print reverse sort num values %array;
return print(reverse(sort num (values(%array))));
When in doubt, parenthesize. At the very least it
will let some poor schmuck bounce on the % key in vi.
Even if you aren't in doubt, consider the mental
welfare of the person who has to maintain the code
after you, and who will probably put parentheses in
the wrong place.
--
Christopher Masto Director of Operations NetMonger Communications
chris@netmonger.net info@netmonger.net http://www.netmonger.net
"Good tools allow users to do stupid things." -- Clay Shirky
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Thu Jan 28 21:50:42 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id VAA25641
for freebsd-current-outgoing; Thu, 28 Jan 1999 21:50:42 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA25634
for <current@FreeBSD.ORG>; Thu, 28 Jan 1999 21:50:40 -0800 (PST)
(envelope-from julian@whistle.com)
Received: (from daemon@localhost)
by alpo.whistle.com (8.8.5/8.8.5) id VAA01443;
Thu, 28 Jan 1999 21:43:53 -0800 (PST)
Received: from current1.whistle.com(207.76.205.22)
via SMTP by alpo.whistle.com, id smtpdFe1440; Fri Jan 29 05:43:44 1999
Date: Thu, 28 Jan 1999 21:43:41 -0800 (PST)
From: Julian Elischer <julian@whistle.com>
To: Greg Lehey <grog@lemis.com>
cc: current@FreeBSD.ORG
Subject: Re: btokup().. patch to STYLE(9) (fwd)
In-Reply-To: <19990129155911.Q8473@freebie.lemis.com>
Message-ID: <Pine.BSF.3.95.990128213330.11856X-100000@current1.whistle.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
On Fri, 29 Jan 1999, Greg Lehey wrote:
> On Friday, 29 January 1999 at 16:26:53 +1100, John Birrell wrote:
>
> I'm sure they might. But they'd be wrong. I do believe that
> maintaining a coherent style is a Good Thing. I just dislike the
> particular style, but since it doesn't significantly lower my standard
> of living, I put up with it :-)
I know that there are times when I've been working on code, and that I've
added parens to help me (who now understands the code) feel comfortable
that I will understand it next time I'm visiting it, and when I've
committed it someone rips out the parens with the comment.. "make it
KNF".
Now if I'm working on some piece of code and feel that it could do with
some parens then surely KNF should be flexible enough to allow them..
I don't know how many bugs have ben revealed by adding parens and braces..
I know that one of the first things I do when looking for a bug is add as
many as I can in parts of the code that are suspect.
It's amazing how often it shows up the problem.
KNF is propogating what I consider to be bad practice, and that annoys me.
I'm happy to say that often they should be dropped, but to FORCE the
dropping of braces etc. with no regard to readbility is too much.
julian
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Thu Jan 28 21:52:51 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id VAA25818
for freebsd-current-outgoing; Thu, 28 Jan 1999 21:52:51 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from allegro.lemis.com (allegro.lemis.com [192.109.197.134])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA25812
for <current@FreeBSD.ORG>; Thu, 28 Jan 1999 21:52:47 -0800 (PST)
(envelope-from grog@freebie.lemis.com)
Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137])
by allegro.lemis.com (8.9.1/8.9.0) with ESMTP id QAA29572;
Fri, 29 Jan 1999 16:22:44 +1030 (CST)
Received: (from grog@localhost)
by freebie.lemis.com (8.9.2/8.9.0) id QAA16089;
Fri, 29 Jan 1999 16:22:44 +1030 (CST)
Date: Fri, 29 Jan 1999 16:22:44 +1030
From: Greg Lehey <grog@lemis.com>
To: Julian Elischer <julian@whistle.com>
Cc: current@FreeBSD.ORG
Subject: Re: btokup().. patch to STYLE(9) (fwd)
Message-ID: <19990129162243.V8473@freebie.lemis.com>
References: <19990129155911.Q8473@freebie.lemis.com> <Pine.BSF.3.95.990128213330.11856X-100000@current1.whistle.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.95.1i
In-Reply-To: <Pine.BSF.3.95.990128213330.11856X-100000@current1.whistle.com>; from Julian Elischer on Thu, Jan 28, 1999 at 09:43:41PM -0800
WWW-Home-Page: http://www.lemis.com/~grog
Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia
Phone: +61-8-8388-8286
Fax: +61-8-8388-8725
Mobile: +61-41-739-7062
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
On Thursday, 28 January 1999 at 21:43:41 -0800, Julian Elischer wrote:
>
>
> On Fri, 29 Jan 1999, Greg Lehey wrote:
>
>> On Friday, 29 January 1999 at 16:26:53 +1100, John Birrell wrote:
>>
>> I'm sure they might. But they'd be wrong. I do believe that
>> maintaining a coherent style is a Good Thing. I just dislike the
>> particular style, but since it doesn't significantly lower my standard
>> of living, I put up with it :-)
>
> I know that there are times when I've been working on code, and that I've
> added parens to help me (who now understands the code) feel comfortable
> that I will understand it next time I'm visiting it, and when I've
> committed it someone rips out the parens with the comment.. "make it
> KNF".
>
> Now if I'm working on some piece of code and feel that it could do with
> some parens then surely KNF should be flexible enough to allow them..
>
> I don't know how many bugs have ben revealed by adding parens and braces..
> I know that one of the first things I do when looking for a bug is add as
> many as I can in parts of the code that are suspect.
>
> It's amazing how often it shows up the problem.
>
> KNF is propogating what I consider to be bad practice, and that annoys me.
> I'm happy to say that often they should be dropped, but to FORCE the
> dropping of braces etc. with no regard to readbility is too much.
Don't get me wrong. I'm not disagreeing with you. I'm just saying I
don't think it's worth fighting for. If you really want to fight,
fight for a complete reform, so that the code looks like the way I
prefer :-)
Greg
--
See complete headers for address, home page and phone numbers
finger grog@lemis.com for PGP public key
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Thu Jan 28 21:55:43 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id VAA26023
for freebsd-current-outgoing; Thu, 28 Jan 1999 21:55:43 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from kot.ne.mediaone.net (kot.ne.mediaone.net [24.128.29.136])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA26017
for <current@freebsd.org>; Thu, 28 Jan 1999 21:55:41 -0800 (PST)
(envelope-from mi@kot.ne.mediaone.net)
Received: (from mi@localhost)
by kot.ne.mediaone.net (8.9.1a/8.9.1) id AAA28927
for current@freebsd.org; Fri, 29 Jan 1999 00:55:22 -0500 (EST)
From: Mikhail Teterin <mi@kot.ne.mediaone.net>
Message-Id: <199901290555.AAA28927@kot.ne.mediaone.net>
Subject: Re: btokup().. patch to STYLE(9) (fwd)
In-Reply-To: <199901290541.VAA00709@apollo.backplane.com> from Matthew Dillon at "Jan 28, 1999 09:41:51 pm"
To: current@FreeBSD.ORG
Date: Fri, 29 Jan 1999 00:55:21 -0500 (EST)
X-Face: %UW#n0|w>ydeGt/b@1-.UFP=K^~-:0f#O:D7w<gv/&E-lL7twZCT8B~/PA4|\t$ti+22K">
hJ5G_<5143Bb3kOIs9XpX+"V+~$adGP:J|SLieM31VIhqXeLBli"<kcG^EOVih
y+z3/UR{6SCQ
X-Mailer: ELM [version 2.4ME+ PL49 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
Matthew Dillon once stated:
= The changes seem pretty reasonable, to me. I don't see why you are
= so rabid about not allowing a few extra braces for clarity. It
= would make the code more readable.
Somehow, this just reminded me of the US Communication Decency Act,
where indecency was defined by "community standards". The opponents
were pointing out, that the "communities" are different, and something
originating in a place where it is deemed "decent" would be prosecuted
because it is deemed "indecent" in some other "community".
It appears, there are at least two communities here, trying to adopt a
single law (style-document) based on the notion of "readable" by the
"community standards".
Everybody's goal is to keep/make code readable (accusations of "trying
to obfuscate" are silly). You, people, are just not agreeing what
"readable" means. Hoping to aid in the ending of this thread(s),
-mi
= Besides, a great deal of the preexisting code already uses braces
= even in single statement if()'s... and a great deal does not.
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Thu Jan 28 21:57:33 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id VAA26234
for freebsd-current-outgoing; Thu, 28 Jan 1999 21:57:33 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from cimlogic.com.au (cimlog.lnk.telstra.net [139.130.51.31])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA26229
for <current@FreeBSD.ORG>; Thu, 28 Jan 1999 21:57:29 -0800 (PST)
(envelope-from jb@cimlogic.com.au)
Received: (from jb@localhost)
by cimlogic.com.au (8.9.1/8.9.1) id RAA12806;
Fri, 29 Jan 1999 17:01:57 +1100 (EST)
(envelope-from jb)
From: John Birrell <jb@cimlogic.com.au>
Message-Id: <199901290601.RAA12806@cimlogic.com.au>
Subject: Re: btokup().. patch to STYLE(9) (fwd)
In-Reply-To: <199901290533.WAA66051@psf.Pinyon.ORG> from "Russell L. Carter" at "Jan 28, 1999 10:33:18 pm"
To: rcarter@pinyon.org (Russell L. Carter)
Date: Fri, 29 Jan 1999 17:01:57 +1100 (EST)
Cc: jb@cimlogic.com.au, current@FreeBSD.ORG
X-Mailer: ELM [version 2.4ME+ PL43 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
Russell L. Carter wrote:
> Come on John, this has *meaning*. For or against -Wall
> *stands* for something! We have constitutional procedures
> to solve this thing!
The "constitutional procedures" just stomp on things because the
few who complain the loudest drown out those who silently or
not-so-loudly agree. Ask yourself: in the last 6 months, how many
things have been shot down and what has survived? From my point
of view, not much progress has been achieved. As far as I can see,
FreeBSD has reached critical mass and for each new developer coming
on board, one drops off or goes inactive.
--
John Birrell - jb@cimlogic.com.au; jb@freebsd.org http://www.cimlogic.com.au/
CIMlogic Pty Ltd, GPO Box 117A, Melbourne Vic 3001, Australia +61 418 353 137
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Thu Jan 28 23:14:12 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id XAA03579
for freebsd-current-outgoing; Thu, 28 Jan 1999 23:14:12 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from room101.wuppy.rcs.ru (room101.wuppy.rcs.ru [194.84.206.44])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA03480
for <current@FreeBSD.ORG>; Thu, 28 Jan 1999 23:12:00 -0800 (PST)
(envelope-from romanp@wuppy.rcs.ru)
Received: from room101.wuppy.rcs.ru (room101.wuppy.rcs.ru [194.84.206.44])
by room101.wuppy.rcs.ru (8.9.2.local/8.9.0) with ESMTP id KAA05134
for <current@FreeBSD.ORG>; Fri, 29 Jan 1999 10:06:53 +0300 (MSK/MSD)
Date: Fri, 29 Jan 1999 10:06:53 +0300 (MSK/MSD)
From: "Roman V. Palagin" <romanp@wuppy.rcs.ru>
To: current@FreeBSD.ORG
Subject: 3.0-STABLE and 4.0-CURRENT snapshots
Message-ID: <Pine.BSI.4.05.SK+PRV.9901291004030.5132-100000@room101.wuppy.rcs.ru>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
Hello!
Where I can find snapshot for -stable & -current? I've tried
current.freebsd.org, but 'cd /pub/FreeBSD' says 'Permission denied'.
And there is nothing at
ftp://ftp.freebsd.org/pub/FreeBSD/release/snapshots/i386
-------------------------------------------------------------------------
Roman V. Palagin | RVP1-6BONE | Just because you're paranoid
Network Administrator | RP40-RIPE | doesn't mean they AREN'T after you
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Thu Jan 28 23:38:02 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id XAA06036
for freebsd-current-outgoing; Thu, 28 Jan 1999 23:38:02 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from nagual.pp.ru (nagual.pp.ru [193.125.27.73])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA06019
for <current@freebsd.org>; Thu, 28 Jan 1999 23:37:59 -0800 (PST)
(envelope-from ache@nagual.pp.ru)
Received: (from ache@localhost)
by nagual.pp.ru (8.9.2/8.9.2) id KAA00443
for current@freebsd.org; Fri, 29 Jan 1999 10:37:58 +0300 (MSK)
(envelope-from ache)
Date: Fri, 29 Jan 1999 10:37:58 +0300
From: "Andrey A. Chernov" <ache@nagual.pp.ru>
To: current@FreeBSD.ORG
Subject: panic: soaccept: !NOFDREF
Message-ID: <19990129103757.A410@nagual.pp.ru>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.95.1i
Organization: Biomechanoid
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
I saw it several times with very recent -current
--
Andrey A. Chernov
ache@null.net
MTH/SH/HE S-- W-- N+ PEC>+ D A a++ C G>+ QH+(++) 666+>++ Y
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Thu Jan 28 23:44:07 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id XAA07165
for freebsd-current-outgoing; Thu, 28 Jan 1999 23:44:07 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from gjp.erols.com (alex-va-n008c079.moon.jic.com [206.156.18.89])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA07155
for <freebsd-current@FreeBSD.ORG>; Thu, 28 Jan 1999 23:44:05 -0800 (PST)
(envelope-from gjp@gjp.erols.com)
Received: from gjp.erols.com (localhost.erols.com [127.0.0.1])
by gjp.erols.com (8.9.1/8.8.7) with ESMTP id CAA54933
for <freebsd-current@FreeBSD.ORG>; Fri, 29 Jan 1999 02:44:04 -0500 (EST)
(envelope-from gjp@gjp.erols.com)
X-Mailer: exmh version 2.0.1 12/23/97
To: freebsd-current@FreeBSD.ORG
From: "Gary Palmer" <gpalmer@FreeBSD.ORG>
Subject: Re: make release - Party Time! (but not for the AXP)
In-reply-to: Your message of "Wed, 27 Jan 1999 09:33:14 EST."
<199901271433.JAA75703@bb01f39.unx.sas.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Fri, 29 Jan 1999 02:44:04 -0500
Message-ID: <54929.917595844@gjp.erols.com>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
"John W. DeBoskey" wrote in message ID
<199901271433.JAA75703@bb01f39.unx.sas.com>:
> A note of thanks to Jordan and everyone else who's been working
> on the new 4.0 code... We have our first complete processing of
> cd /usr/src && make world && cd release && make release.
Unfortunately the AXP is still hosed :(
Making the regular boot floppy.
Compressing doc files...
disklabel: ioctl DIOCWLABEL: Operation not supported by device
Warning: Block size restricts cylinders per group to 6.
Warning: 1216 sector(s) in last cylinder unallocated
/dev/rvn0c: 2880 sectors in 1 cylinders of 1 tracks, 4096 sectors
1.4MB in 1 cyl groups (6 c/g, 12.00MB/g, 192 i/g)
super-block backups (for fsck -b #) at:
32,
cpio: write error: No space left on device
*** Error code 1 (ignored)
*** Error code 1
Stop.
*** Error code 1
Stop.
gjp@sloth:/home/release/R/stage/crunch> l
total 3906
drwxr-xr-x 2 root wheel - 512 Jan 28 11:55 .
drwxr-xr-x 8 root wheel - 512 Jan 28 12:43 ..
-r-xr-xr-x 20 root wheel - 2015104 Jan 28 11:51 boot
-rwxr-xr-x 1 root wheel - 1961496 Jan 28 11:55 fixit
I somehow doubt that those will fit on a 1.4Mb floppy :)
Anyone working to get gzip functional under ELF?
Gary
--
Gary Palmer FreeBSD Core Team Member
FreeBSD: Turning PC's into workstations. See http://www.FreeBSD.ORG/ for info
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Thu Jan 28 23:57:25 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id XAA08792
for freebsd-current-outgoing; Thu, 28 Jan 1999 23:57:25 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from relay.nuxi.com ([169.237.7.38])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA08786
for <freebsd-current@FreeBSD.ORG>; Thu, 28 Jan 1999 23:57:23 -0800 (PST)
(envelope-from obrien@NUXI.com)
Received: (from obrien@localhost)
by relay.nuxi.com (8.9.1/8.9.1) id XAA25186;
Thu, 28 Jan 1999 23:55:11 -0800 (PST)
(envelope-from obrien)
Date: Thu, 28 Jan 1999 23:55:11 -0800
From: "David O'Brien" <obrien@NUXI.com>
To: Mike Smith <mike@smith.net.au>
Cc: Ustimenko Semen <semen@iclub.nsu.ru>, freebsd-current@FreeBSD.ORG
Subject: Re: About to commit NTFS driver
Message-ID: <19990128235511.A24267@relay.nuxi.com>
Reply-To: obrien@NUXI.com
References: <Pine.BSF.3.96.990128024451.49866B-100000@iclub.nsu.ru> <199901290050.QAA01195@dingo.cdrom.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.95i
In-Reply-To: <199901290050.QAA01195@dingo.cdrom.com>; from Mike Smith on Thu, Jan 28, 1999 at 04:50:35PM -0800
X-Operating-System: FreeBSD 3.0-CURRENT
Organization: The NUXI BSD group
X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A
X-Pgp-Keyid: 34F9F9D5
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
> > Driver is readonly, specialy developed for freebsd,
> > supports most of NTFS's features.
> > Source is at http://iclub.nsu.ru/~semen/ntfs/
>
> Sounds like a good idea. Do you have a reviewer?
I'm looking at it now for 4.0-C.
--
-- David (obrien@NUXI.com -or- obrien@FreeBSD.org)
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Thu Jan 28 23:59:04 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id XAA08952
for freebsd-current-outgoing; Thu, 28 Jan 1999 23:59:04 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA08947
for <current@FreeBSD.ORG>; Thu, 28 Jan 1999 23:59:03 -0800 (PST)
(envelope-from jkh@zippy.cdrom.com)
Received: from zippy.cdrom.com (localhost.cdrom.com [127.0.0.1])
by zippy.cdrom.com (8.9.2/8.9.1) with ESMTP id XAA06896;
Thu, 28 Jan 1999 23:59:15 -0800 (PST)
To: Peter Wemm <peter@netplex.com.au>
cc: Bruce Evans <bde@zeta.org.au>, chris@netmonger.net, current@FreeBSD.ORG
Subject: Re: btokup().. patch to STYLE(9) (fwd)
In-reply-to: Your message of "Fri, 29 Jan 1999 11:59:53 +0800."
<199901290359.LAA21875@spinner.netplex.com.au>
Date: Thu, 28 Jan 1999 23:59:14 -0800
Message-ID: <6892.917596754@zippy.cdrom.com>
From: "Jordan K. Hubbard" <jkh@zippy.cdrom.com>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
> style(9) is not KNF, and never was intended to be. It's a FreeBSD style
> guide that bears similarity to KNF because that's what it used as a
> starting point.
I think we can safely presume that Bruce has been overruled on this
one. If the collective definition is different than his, and it seems
to be, then the collective definition prevails. I very much enjoy the
work Bruce does in keeping us honest in various ways, but I don't
recall ever handing him the keys to the city and carte blanche over
all commits. :-)
- Jordan
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Fri Jan 29 00:04:52 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id AAA09612
for freebsd-current-outgoing; Fri, 29 Jan 1999 00:04:52 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA09607
for <current@FreeBSD.ORG>; Fri, 29 Jan 1999 00:04:51 -0800 (PST)
(envelope-from jkh@zippy.cdrom.com)
Received: from zippy.cdrom.com (localhost.cdrom.com [127.0.0.1])
by zippy.cdrom.com (8.9.2/8.9.1) with ESMTP id AAA06932;
Fri, 29 Jan 1999 00:05:24 -0800 (PST)
To: Warner Losh <imp@village.org>
cc: Julian Elischer <julian@whistle.com>, current@FreeBSD.ORG
Subject: Re: btokup().. patch to STYLE(9) (fwd)
In-reply-to: Your message of "Thu, 28 Jan 1999 21:35:04 MST."
<199901290435.VAA62940@harmony.village.org>
Date: Fri, 29 Jan 1999 00:05:24 -0800
Message-ID: <6928.917597124@zippy.cdrom.com>
From: "Jordan K. Hubbard" <jkh@zippy.cdrom.com>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
> Unless things have changed a lot, bde counts 50x most people. This
> isn't a democracy.
It may not be a democracy, but it's also not a monarchy. :-)
If recent core events have taught us anything at all, it's that nobody
in core escapes being accountable to the developers at large and if
the consensus opinion supports a given change then that change should
be made. Anyone backing out such a change on his own recognizance
will find his own commit privileges somewhat emperiled, and that goes
for *anyone* in committers.
Bruce only gets "50x the vote" on occasion by generally being the only
one to comment at all. People should not take that as indicative of
any special powers and, last I checked, Bruce was quite vulnerable to
Kryptonite. :-)
- Jordan
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Fri Jan 29 00:14:14 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id AAA10842
for freebsd-current-outgoing; Fri, 29 Jan 1999 00:14:14 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA10833
for <current@freebsd.org>; Fri, 29 Jan 1999 00:14:11 -0800 (PST)
(envelope-from phk@critter.freebsd.dk)
Received: from critter.freebsd.dk (localhost [127.0.0.1])
by critter.freebsd.dk (8.9.1/8.8.5) with ESMTP id JAA02213
for <current@freebsd.org>; Fri, 29 Jan 1999 09:13:40 +0100 (CET)
To: current@FreeBSD.ORG
Subject: Re: btokup().. patch to STYLE(9) (fwd)
In-reply-to: Your message of "Thu, 28 Jan 1999 23:59:14 PST."
<6892.917596754@zippy.cdrom.com>
Date: Fri, 29 Jan 1999 09:13:39 +0100
Message-ID: <2211.917597619@critter.freebsd.dk>
From: Poul-Henning Kamp <phk@critter.freebsd.dk>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
In message <6892.917596754@zippy.cdrom.com>, "Jordan K. Hubbard" writes:
>> style(9) is not KNF, and never was intended to be. It's a FreeBSD style
>> guide that bears similarity to KNF because that's what it used as a
>> starting point.
>
>I think we can safely presume that Bruce has been overruled on this
>one. If the collective definition is different than his, and it seems
>to be, then the collective definition prevails. I very much enjoy the
>work Bruce does in keeping us honest in various ways, but I don't
>recall ever handing him the keys to the city and carte blanche over
>all commits. :-)
I also value what Bruce is doing (very much so!), but I tend to
agree with Jordan here, style(9) needs to be a little bit more
tolerant than KNF.
On the other hand style(9) should still firmly outlaw stuff like:
/* wait 10 ms */
if (((error = tsleep((caddr_t)dev, PPBPRI | PCATCH,
"ppbpoll", hz/100)) != EWOULDBLOCK) != 0) {
return (error);
}
(The identity of the guilty party is known to the CVS repository)
My two personal problems with style(9) are the same which many
others have been complaining about: more tolerant of {} and ()
added for readability.
It would also be nice if somebody whould coerse ident to DTRT.
--
Poul-Henning Kamp FreeBSD coreteam member
phk@FreeBSD.ORG "Real hackers run -current on their laptop."
FreeBSD -- It will take a long time before progress goes too far!
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Fri Jan 29 00:16:56 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id AAA11121
for freebsd-current-outgoing; Fri, 29 Jan 1999 00:16:56 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA11112
for <current@FreeBSD.ORG>; Fri, 29 Jan 1999 00:16:54 -0800 (PST)
(envelope-from jkh@zippy.cdrom.com)
Received: from zippy.cdrom.com (localhost.cdrom.com [127.0.0.1])
by zippy.cdrom.com (8.9.2/8.9.1) with ESMTP id AAA07008;
Fri, 29 Jan 1999 00:16:54 -0800 (PST)
To: John Birrell <jb@cimlogic.com.au>
cc: grog@lemis.com (Greg Lehey), julian@whistle.com, bde@zeta.org.au,
chris@netmonger.net, current@FreeBSD.ORG
Subject: Re: btokup().. patch to STYLE(9) (fwd)
In-reply-to: Your message of "Fri, 29 Jan 1999 16:26:53 +1100."
<199901290526.QAA12656@cimlogic.com.au>
Date: Fri, 29 Jan 1999 00:16:53 -0800
Message-ID: <7004.917597813@zippy.cdrom.com>
From: "Jordan K. Hubbard" <jkh@zippy.cdrom.com>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
> We spend so much of our time looking up our own collective asses searching
> for the meaning of life that it is no wonder FreeBSD doesn't feel like it
> has a clear direction for the future. All people seem to want to do is
> stomp on others who try to contribute something.
I think the amount of finger stomping could definitely go down and I
would support such an initiative highly, but I would just like to also
point out, before people throw the baby out with the bathwater here,
that our collective stodginess can often be a real plus in an
environment where many things are changing rapidly, too.
It's a common impulse among engineers to attack each and every problem
as it comes up, solve it "somehow", and then move on to the next
challenge. Unfortunately, these early solutions are often proven to be
wrong or just plain evil, and we've definitely stopped ourselves from
doing stupid things at least 5 times for every time we've also stopped
ourselves from doing something useful. Obviously one would prefer a
situation where one NEVER held back from doing useful things, but it's
not always possible to tell the difference until hindsight has kicked
in. :-)
Let's also not forget the fact that most of us have no clue about
where FreeBSD is going, even those "at the helm", and it would be
foolish to make a bunch of 5 year plans without really knowing what
the next year held in store for us. I could perhaps try to make some
predictions about this and formulate strategy, but I'd probably be
wrong since I'm also the guy who sold Yahoo stock at $37. Don't
listen to me at all when it comes to predicting this industry's
trends. :-)
- Jordan
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Fri Jan 29 00:21:39 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id AAA11638
for freebsd-current-outgoing; Fri, 29 Jan 1999 00:21:39 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from alcanet.com.au (border.alcanet.com.au [203.62.196.10])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA11633
for <current@FreeBSD.ORG>; Fri, 29 Jan 1999 00:21:36 -0800 (PST)
(envelope-from peter.jeremy@auss2.alcatel.com.au)
Received: by border.alcanet.com.au id <40324>; Fri, 29 Jan 1999 19:11:55 +1100
Date: Fri, 29 Jan 1999 19:21:23 +1100
From: Peter Jeremy <peter.jeremy@auss2.alcatel.com.au>
Subject: Re: indent(1) and style(9) (was: btokup() macro in sys/malloc.h)
To: dillon@apollo.backplane.com, grog@lemis.com
Cc: current@FreeBSD.ORG
Message-Id: <99Jan29.191155est.40324@border.alcanet.com.au>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
Matthew Dillon <dillon@apollo.backplane.com> wrote:
>:Judicious use of inline functions (and macros) should help move
>:code to the left - and may even make it more understandable.
>
> More then judicious use -- inlines are an incredible advantage. Most
> people don't realize that GCC will optimize constant arguments through
> an inline call.
GCC inserts the called function's parse tree into the calling function
and then optimises the overall parse tree.
inline functions are not a total panacea. They don't work in the
following situations:
1) If the inlined function is just a thrown-together collection of
miscellaneous statements, the final result will be less readible
than the original.
2) The block of code needs to alter the value of more than one variable.
3) The block of code refers to a large number of local (to the calling
function) variables.
4) The block of code includes return's or goto's.
Greg Lehey <grog@lemis.com> wrote:
>One man's readability is another man's illegibility.
Agreed. We are discussing highly subjective issues.
> I certainly think that macros can really obfuscate things.
I'm less keen on macros. Their sole advantage (also a major
disadvantage) over inline functions is that they share the same
namespace as the calling function.
> And moving code away
>into separate functions also makes it difficult to see the Big
>Picture.
If the functional decomposition is done appropriately, and the inlined
functions are given meaningful names, then it should become _easier_
to see the Big Picture - because the calling function is not so
cluttered.
> On the other hand, I very much *do* support a consistent coding style.
The FreeBSD probject _does_ need a documented coding style - which is
followed. style(9) meets this requirement.
I don't believe that style(9) should be treated as infallible
doctrine, written in stone. Coding practices need to evolve to meet
changing requirements and expectactions - otherwise we'd all still be
programming in machine language, following the guidelines laid out in
Wilkes, Wheeler, Gill[1].
As a further discussion point, can I suggest reference to one or more
of the following:
I found most of these in ftp://archive.cis.ohio-state.edu/pub/style-guide,
but that was several years ago.
L. W. Cannon et al, "Recommended C Style and Coding Standards", 1989
A. Dolenc et al, "Notes on Writing Portable Programs in C", 1990
Expert Systems Australia, "C Style Guide", 1991
R. Pike, "Notes on Programming in C",
H. Spencer, "The Ten Commandments for C Programmers", Annotated Edition.
H. Spencer, "How to Steal Code or Inventing the Wheel Only Once",
R. Stallman, "GNU Coding Standards",
D. Straker, "C Style: Standards and Guidelines", Prentice Hall, 1992.
[1]: M Wilkes, D Wheeler, S Gill, "The Preparation of Programs for
an Electronic Digital Computer", Addison-Wesley, 1951.
Peter
--
Peter Jeremy (VK2PJ) peter.jeremy@alcatel.com.au
Alcatel Australia Limited
41 Mandible St Phone: +61 2 9690 5019
ALEXANDRIA NSW 2015 Fax: +61 2 9690 5982
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Fri Jan 29 00:24:18 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id AAA11831
for freebsd-current-outgoing; Fri, 29 Jan 1999 00:24:18 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA11824
for <current@FreeBSD.ORG>; Fri, 29 Jan 1999 00:24:16 -0800 (PST)
(envelope-from jkh@zippy.cdrom.com)
Received: from zippy.cdrom.com (localhost.cdrom.com [127.0.0.1])
by zippy.cdrom.com (8.9.2/8.9.1) with ESMTP id AAA07036;
Fri, 29 Jan 1999 00:24:41 -0800 (PST)
To: Julian Elischer <julian@whistle.com>
cc: Greg Lehey <grog@lemis.com>, current@FreeBSD.ORG
Subject: Re: btokup().. patch to STYLE(9) (fwd)
In-reply-to: Your message of "Thu, 28 Jan 1999 21:43:41 PST."
<Pine.BSF.3.95.990128213330.11856X-100000@current1.whistle.com>
Date: Fri, 29 Jan 1999 00:24:39 -0800
Message-ID: <7032.917598279@zippy.cdrom.com>
From: "Jordan K. Hubbard" <jkh@zippy.cdrom.com>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
> KNF is propogating what I consider to be bad practice, and that annoys me.
> I'm happy to say that often they should be dropped, but to FORCE the
> dropping of braces etc. with no regard to readbility is too much.
I wasn't aware that KNF or style(9) actually "forced" anything so much
as "suggested it strongly."
I haven't changed my coding style one iota since we formed the
project, for example, and I have no intention of doing so at any point
in the future. Anyone sending me complaints about how I should have
intented something differently either gets told to kiss my white
behind or, if I'm feeling less energetic, simply has their comments
deleted with a shrug.
How one codes is a highly individualistic decision and I'd just as
soon try and institute a dress code for trade shows where FreeBSD
people are involved. Such a code would undoubtedly give a more
professional appearance to the project and make us look like
business-aware types who are not afraid to wear a tie when such is
called for, but it would hardly be my place to insist on such a thing
nor would it be a constructive move in the long term. So it goes with
enforcing style(9). A strong suggestion, sure. A requirement? Hell
no. Many of us refuse to follow style(9), will NEVER follow style(9),
and to insist on it for others would be hypocritical at best. Bruce
is more of a microcosm and shouldn't be taken as indicative of general
trends. :)
- Jordan
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Fri Jan 29 00:27:25 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id AAA12124
for freebsd-current-outgoing; Fri, 29 Jan 1999 00:27:25 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from axl.noc.iafrica.com (axl.noc.iafrica.com [196.31.1.175])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA12112
for <current@freebsd.org>; Fri, 29 Jan 1999 00:27:19 -0800 (PST)
(envelope-from sheldonh@axl.noc.iafrica.com)
Received: from sheldonh (helo=axl.noc.iafrica.com)
by axl.noc.iafrica.com with local-esmtp (Exim 2.11 #1)
id 1069GW-000N2v-00; Fri, 29 Jan 1999 10:27:00 +0200
From: Sheldon Hearn <axl@iafrica.com>
To: Mikhail Teterin <mi@kot.ne.mediaone.net>
cc: current@FreeBSD.ORG
Subject: Re: btokup().. patch to STYLE(9) (fwd)
In-reply-to: Your message of "Fri, 29 Jan 1999 00:55:21 EST."
<199901290555.AAA28927@kot.ne.mediaone.net>
Date: Fri, 29 Jan 1999 10:27:00 +0200
Message-ID: <88592.917598420@axl.noc.iafrica.com>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
On Fri, 29 Jan 1999 00:55:21 EST, Mikhail Teterin wrote:
> Everybody's goal is to keep/make code readable (accusations of "trying
> to obfuscate" are silly). You, people, are just not agreeing what
> "readable" means. Hoping to aid in the ending of this thread(s),
Thank you very much. This is _exactly_ the point here.
As far as I see it, there are a lot of people who are saying
"I want to use parens to improve readability"
when what they really mean is
"I want to use parens to obviate the need to learn operator precedence."
I can't imagine how unnecessary parens are going to improve
"readability" for anyone who knows his/her operator precedence. What
it does is allow folks who aren't sure about what they're doing to get
around doing things properly.
Ciao,
Sheldon.
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Fri Jan 29 00:28:26 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id AAA12254
for freebsd-current-outgoing; Fri, 29 Jan 1999 00:28:26 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA12248
for <current@FreeBSD.ORG>; Fri, 29 Jan 1999 00:28:25 -0800 (PST)
(envelope-from jkh@zippy.cdrom.com)
Received: from zippy.cdrom.com (localhost.cdrom.com [127.0.0.1])
by zippy.cdrom.com (8.9.2/8.9.1) with ESMTP id AAA07065;
Fri, 29 Jan 1999 00:28:45 -0800 (PST)
To: John Birrell <jb@cimlogic.com.au>
cc: rcarter@pinyon.org (Russell L. Carter), current@FreeBSD.ORG
Subject: Re: btokup().. patch to STYLE(9) (fwd)
In-reply-to: Your message of "Fri, 29 Jan 1999 17:01:57 +1100."
<199901290601.RAA12806@cimlogic.com.au>
Date: Fri, 29 Jan 1999 00:28:44 -0800
Message-ID: <7061.917598524@zippy.cdrom.com>
From: "Jordan K. Hubbard" <jkh@zippy.cdrom.com>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
> not-so-loudly agree. Ask yourself: in the last 6 months, how many
> things have been shot down and what has survived? From my point
> of view, not much progress has been achieved. As far as I can see,
> FreeBSD has reached critical mass and for each new developer coming
> on board, one drops off or goes inactive.
Actually, that's a bad example. :)
More people have joined the project in the last 6 months, and without
anyone dropping off in any truly noticeable way, than ever before.
People have _always_ gone missing for extended periods ever since the
project began and I don't see that this has increased appreciably.
We also completed a fairly MAJOR set of milestones with ELF and the
Alpha port (for which you deserve a good share of the credit) along
with several other things which had been stalled for literally years
or more. We've made a lot of progress in the last 6 months - more
than I'm typically used to. Any more rapid progress than this and
most of us will no longer be able to keep up. :)
- Jordan
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Fri Jan 29 00:29:43 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id AAA12402
for freebsd-current-outgoing; Fri, 29 Jan 1999 00:29:43 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA12397
for <current@FreeBSD.ORG>; Fri, 29 Jan 1999 00:29:42 -0800 (PST)
(envelope-from jkh@zippy.cdrom.com)
Received: from zippy.cdrom.com (localhost.cdrom.com [127.0.0.1])
by zippy.cdrom.com (8.9.2/8.9.1) with ESMTP id AAA07091;
Fri, 29 Jan 1999 00:30:17 -0800 (PST)
To: Warner Losh <imp@village.org>
cc: current@FreeBSD.ORG
Subject: Re: cvs commit: src/sys/i386/eisa ahb.c
In-reply-to: Your message of "Thu, 28 Jan 1999 21:16:15 MST."
<199901290416.VAA62851@harmony.village.org>
Date: Fri, 29 Jan 1999 00:30:17 -0800
Message-ID: <7088.917598617@zippy.cdrom.com>
From: "Jordan K. Hubbard" <jkh@zippy.cdrom.com>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
> Given that there is a good potential to introduce bugs, the age old
> "have another committer review it" would likely allay many of the
> fears that have been expressed. In the past that has been the MO for
> this group.
Are you volunteering to review Matt's stuff? It's something I'm sure
he'd be more than happy to take you up on, Warner! :-) As usual, the
amount of work which various folks would more than love to have
reviewed outstrips the number of people willing to do such review work
in any serious way.
- Jordan
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Fri Jan 29 00:45:04 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id AAA14723
for freebsd-current-outgoing; Fri, 29 Jan 1999 00:45:04 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA14693
for <current@FreeBSD.ORG>; Fri, 29 Jan 1999 00:45:01 -0800 (PST)
(envelope-from phk@critter.freebsd.dk)
Received: from critter.freebsd.dk (localhost [127.0.0.1])
by critter.freebsd.dk (8.9.1/8.8.5) with ESMTP id JAA02394;
Fri, 29 Jan 1999 09:43:15 +0100 (CET)
To: "Jordan K. Hubbard" <jkh@zippy.cdrom.com>
cc: Julian Elischer <julian@whistle.com>, Greg Lehey <grog@lemis.com>,
current@FreeBSD.ORG
Subject: Re: btokup().. patch to STYLE(9) (fwd)
In-reply-to: Your message of "Fri, 29 Jan 1999 00:24:39 PST."
<7032.917598279@zippy.cdrom.com>
Date: Fri, 29 Jan 1999 09:43:14 +0100
Message-ID: <2392.917599394@critter.freebsd.dk>
From: Poul-Henning Kamp <phk@critter.freebsd.dk>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
In message <7032.917598279@zippy.cdrom.com>, "Jordan K. Hubbard" writes:
>Many of us refuse to follow style(9), will NEVER follow style(9),
>and to insist on it for others would be hypocritical at best. Bruce
>is more of a microcosm and shouldn't be taken as indicative of general
>trends. :)
... Unless we're talking about modifications to existing files where
either style(9) or other systematic styles apply, in which case we
should all try to adapt our changes to that style to avoid babelized
codelayout.
--
Poul-Henning Kamp FreeBSD coreteam member
phk@FreeBSD.ORG "Real hackers run -current on their laptop."
FreeBSD -- It will take a long time before progress goes too far!
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Fri Jan 29 00:47:37 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id AAA15437
for freebsd-current-outgoing; Fri, 29 Jan 1999 00:47:37 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from frolic.no-support.loc (ppp39-55.hrz.uni-bielefeld.de [129.70.39.55])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA15419;
Fri, 29 Jan 1999 00:47:32 -0800 (PST)
(envelope-from bfischer@Techfak.Uni-Bielefeld.DE)
Received: (from bjoern@localhost)
by frolic.no-support.loc (8.9.2/8.8.8/Debian/GNU) id JAA00755;
Fri, 29 Jan 1999 09:46:17 +0100 (CET)
From: Bjoern Fischer <bfischer@Techfak.Uni-Bielefeld.DE>
Date: Fri, 29 Jan 1999 09:46:16 +0100
To: Matthew Dillon <dillon@apollo.backplane.com>
Cc: freebsd-stable@FreeBSD.ORG, freebsd-current@FreeBSD.ORG
Subject: nuts'n'bolts in vfs_bio
Message-ID: <19990129094616.A555@frolic.no-support.loc>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.95i
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
Hello,
as Matthew said in freebsd-current@ vfs_bio:getblk() still
needs work (B_CACHE/B_DELWRI stuff).
Running 3.0-stable (Jan 26) it still happens that some NFS
writes seem to remain uncommited on the server.
Is there a chance to get it into -stable before releasing
in mid February?
Thanks,
Bjoern
--
-----BEGIN GEEK CODE BLOCK-----
GCS d--(+) s++: a- C+++(-) UBL++++OSI++++$ P+++(-) L+++(-) !E W- N+ o>+
K- !w !O !M !V PS++ PE- PGP++ t+++ !5 X++ tv- b+++ D++ G e+ h-- y+
------END GEEK CODE BLOCK------
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Fri Jan 29 00:51:01 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id AAA13704
for freebsd-current-outgoing; Fri, 29 Jan 1999 00:39:35 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA13685;
Fri, 29 Jan 1999 00:39:31 -0800 (PST)
(envelope-from jkh@zippy.cdrom.com)
Received: from zippy.cdrom.com (localhost.cdrom.com [127.0.0.1])
by zippy.cdrom.com (8.9.2/8.9.1) with ESMTP id AAA07202;
Fri, 29 Jan 1999 00:40:10 -0800 (PST)
To: "Gary Palmer" <gpalmer@FreeBSD.ORG>
cc: freebsd-current@FreeBSD.ORG
Subject: Re: make release - Party Time! (but not for the AXP)
In-reply-to: Your message of "Fri, 29 Jan 1999 02:44:04 EST."
<54929.917595844@gjp.erols.com>
Date: Fri, 29 Jan 1999 00:40:09 -0800
Message-ID: <7197.917599209@zippy.cdrom.com>
From: "Jordan K. Hubbard" <jkh@zippy.cdrom.com>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
> Unfortunately the AXP is still hosed :(
Hmmm. Let me look at this - I may have failed to adjust one of the
constants for the AXP case.
- Jordan
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Fri Jan 29 00:51:02 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id AAA13697
for freebsd-current-outgoing; Fri, 29 Jan 1999 00:39:33 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA13684
for <current@FreeBSD.ORG>; Fri, 29 Jan 1999 00:39:30 -0800 (PST)
(envelope-from dillon@apollo.backplane.com)
Received: (from dillon@localhost)
by apollo.backplane.com (8.9.2/8.9.1) id AAA40002;
Fri, 29 Jan 1999 00:39:27 -0800 (PST)
(envelope-from dillon)
Date: Fri, 29 Jan 1999 00:39:27 -0800 (PST)
From: Matthew Dillon <dillon@apollo.backplane.com>
Message-Id: <199901290839.AAA40002@apollo.backplane.com>
To: "Jordan K. Hubbard" <jkh@zippy.cdrom.com>
Cc: Warner Losh <imp@village.org>, current@FreeBSD.ORG
Subject: Re: cvs commit: src/sys/i386/eisa ahb.c
References: <7088.917598617@zippy.cdrom.com>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
:> Given that there is a good potential to introduce bugs, the age old
:> "have another committer review it" would likely allay many of the
:> fears that have been expressed. In the past that has been the MO for
:> this group.
:
:Are you volunteering to review Matt's stuff? It's something I'm sure
:he'd be more than happy to take you up on, Warner! :-) As usual, the
:amount of work which various folks would more than love to have
:reviewed outstrips the number of people willing to do such review work
:in any serious way.
:
:- Jordan
( Matt mumbles something about what trying to review dozens of commits
with hundreds of modifications day after day would do to someone's sanity )
-Matt
Matthew Dillon
<dillon@backplane.com>
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Fri Jan 29 00:55:15 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id AAA16606
for freebsd-current-outgoing; Fri, 29 Jan 1999 00:55:15 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA16599
for <current@FreeBSD.ORG>; Fri, 29 Jan 1999 00:55:13 -0800 (PST)
(envelope-from phk@critter.freebsd.dk)
Received: from critter.freebsd.dk (localhost [127.0.0.1])
by critter.freebsd.dk (8.9.1/8.8.5) with ESMTP id JAA02470;
Fri, 29 Jan 1999 09:53:09 +0100 (CET)
To: Sheldon Hearn <axl@iafrica.com>
cc: Mikhail Teterin <mi@kot.ne.mediaone.net>, current@FreeBSD.ORG
Subject: Re: btokup().. patch to STYLE(9) (fwd)
In-reply-to: Your message of "Fri, 29 Jan 1999 10:27:00 +0200."
<88592.917598420@axl.noc.iafrica.com>
Date: Fri, 29 Jan 1999 09:53:08 +0100
Message-ID: <2468.917599988@critter.freebsd.dk>
From: Poul-Henning Kamp <phk@critter.freebsd.dk>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
In message <88592.917598420@axl.noc.iafrica.com>, Sheldon Hearn writes:
>
>
>On Fri, 29 Jan 1999 00:55:21 EST, Mikhail Teterin wrote:
>
>> Everybody's goal is to keep/make code readable (accusations of "trying
>> to obfuscate" are silly). You, people, are just not agreeing what
>> "readable" means. Hoping to aid in the ending of this thread(s),
>
>Thank you very much. This is _exactly_ the point here.
>
>As far as I see it, there are a lot of people who are saying
>
>"I want to use parens to improve readability"
>
>when what they really mean is
>
>"I want to use parens to obviate the need to learn operator precedence."
>
>I can't imagine how unnecessary parens are going to improve
>"readability" for anyone who knows his/her operator precedence.
The parans have the same function as commas in most latin alphabet
based languages: to convey structure.
The fact that vi(1) has this neat '%' feature makes complex
expressions with a couple of extra parens much easier to dissect
than if there are no parens even if they are strictly speaking not
needed for correct compilation of the expression in the first
place.
I hope you didn't mind the commas I left out of the previous sentence,
they're strictly speaking not needed for understanding that sentence.
--
Poul-Henning Kamp FreeBSD coreteam member
phk@FreeBSD.ORG "Real hackers run -current on their laptop."
FreeBSD -- It will take a long time before progress goes too far!
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Fri Jan 29 00:56:03 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id AAA16282
for freebsd-current-outgoing; Fri, 29 Jan 1999 00:52:19 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA16270
for <current@FreeBSD.ORG>; Fri, 29 Jan 1999 00:52:16 -0800 (PST)
(envelope-from jkh@zippy.cdrom.com)
Received: from zippy.cdrom.com (localhost.cdrom.com [127.0.0.1])
by zippy.cdrom.com (8.9.2/8.9.1) with ESMTP id AAA07280;
Fri, 29 Jan 1999 00:49:11 -0800 (PST)
To: Poul-Henning Kamp <phk@critter.freebsd.dk>
cc: Julian Elischer <julian@whistle.com>, Greg Lehey <grog@lemis.com>,
current@FreeBSD.ORG
Subject: Re: btokup().. patch to STYLE(9) (fwd)
In-reply-to: Your message of "Fri, 29 Jan 1999 09:43:14 +0100."
<2392.917599394@critter.freebsd.dk>
Date: Fri, 29 Jan 1999 00:49:10 -0800
Message-ID: <7276.917599750@zippy.cdrom.com>
From: "Jordan K. Hubbard" <jkh@zippy.cdrom.com>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
> ... Unless we're talking about modifications to existing files where
> either style(9) or other systematic styles apply, in which case we
> should all try to adapt our changes to that style to avoid babelized
> codelayout.
Absolutely. I was talking only about my own code, and code which I
modify falls under a different set of rules. Basically, I just use
whatever "style" the author is already using, even if there are no
spaces between operators and they've written code which looks like:
``for(i=0;i<10;i++) blah;'' :-)
It would be far too confusing otherwise to be reading through some
body of code and suddenly see that for a short block in the middle,
the style has just changed completely. Code which I *adopt*, of
course, goes through my emacs re-indenting and formatting elisp
function. :)
- Jordan
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Fri Jan 29 00:57:31 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id AAA16844
for freebsd-current-outgoing; Fri, 29 Jan 1999 00:57:31 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from rover.village.org (rover.village.org [204.144.255.49])
by hub.freebsd.org (8.8.8/8.8.8) with SMTP id AAA16838
for <current@freebsd.org>; Fri, 29 Jan 1999 00:57:29 -0800 (PST)
(envelope-from imp@village.org)
Received: from harmony [10.0.0.6]
by rover.village.org with esmtp (Exim 1.71 #1)
id 1069jy-0005ua-00; Fri, 29 Jan 1999 01:57:26 -0700
Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.1/8.8.3) with ESMTP id BAA64480; Fri, 29 Jan 1999 01:57:28 -0700 (MST)
Message-Id: <199901290857.BAA64480@harmony.village.org>
To: Matthew Dillon <dillon@apollo.backplane.com>
Subject: Re: cvs commit: src/sys/i386/eisa ahb.c
Cc: "Jordan K. Hubbard" <jkh@zippy.cdrom.com>, current@FreeBSD.ORG
In-reply-to: Your message of "Fri, 29 Jan 1999 00:39:27 PST."
<199901290839.AAA40002@apollo.backplane.com>
References: <199901290839.AAA40002@apollo.backplane.com> <7088.917598617@zippy.cdrom.com>
Date: Fri, 29 Jan 1999 01:57:28 -0700
From: Warner Losh <imp@village.org>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
:Are you volunteering to review Matt's stuff? It's something I'm sure
:he'd be more than happy to take you up on, Warner! :-) As usual, the
:amount of work which various folks would more than love to have
:reviewed outstrips the number of people willing to do such review work
:in any serious way.
Yes. I'd review the changes with a 48 hour turn around time (usually
better). Generally they are somewhat obvious changes, but some of
them require a bit of thought to ensure that they are right. I can
handle that.
Warner
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Fri Jan 29 01:06:14 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id BAA18318
for freebsd-current-outgoing; Fri, 29 Jan 1999 01:06:14 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from axl.noc.iafrica.com (axl.noc.iafrica.com [196.31.1.175])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA18296
for <current@freebsd.org>; Fri, 29 Jan 1999 01:06:07 -0800 (PST)
(envelope-from sheldonh@axl.noc.iafrica.com)
Received: from sheldonh (helo=axl.noc.iafrica.com)
by axl.noc.iafrica.com with local-esmtp (Exim 2.11 #1)
id 1069oa-000NQo-00; Fri, 29 Jan 1999 11:02:12 +0200
From: Sheldon Hearn <axl@iafrica.com>
To: Poul-Henning Kamp <phk@critter.freebsd.dk>
cc: Mikhail Teterin <mi@kot.ne.mediaone.net>, current@FreeBSD.ORG
Subject: Re: btokup().. patch to STYLE(9) (fwd)
In-reply-to: Your message of "Fri, 29 Jan 1999 09:53:08 +0100."
<2468.917599988@critter.freebsd.dk>
Date: Fri, 29 Jan 1999 11:02:12 +0200
Message-ID: <90073.917600532@axl.noc.iafrica.com>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
On Fri, 29 Jan 1999 09:53:08 +0100, Poul-Henning Kamp wrote:
> The parans have the same function as commas in most latin alphabet
> based languages: to convey structure.
I think you've picked the wrong analogy. The rules of the language
dictate certain cases in which commas are required. Extraneous use of
commas decreases readability.
> The fact that vi(1) has this neat '%' feature makes complex
> expressions with a couple of extra parens much easier to dissect
> than if there are no parens even if they are strictly speaking not
> needed for correct compilation of the expression in the first
> place.
>
> I hope you didn't mind the commas I left out of the previous sentence,
> they're strictly speaking not needed for understanding that sentence.
I didn't have a problem reading the sentence, even though you left out
required commas. The only thing that caused a problem was your use of
split infinitive. ;-)
When it comes to code, do you not agree that the trained eye knows which
operators to seek to first in an expression? I can't think of an analogy
in the English language, since one doesn't "seek to" commas, one simply
reads from left to right.
Ciao,
Sheldon.
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Fri Jan 29 01:16:59 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id BAA19991
for freebsd-current-outgoing; Fri, 29 Jan 1999 01:16:59 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA19971;
Fri, 29 Jan 1999 01:16:57 -0800 (PST)
(envelope-from dillon@apollo.backplane.com)
Received: (from dillon@localhost)
by apollo.backplane.com (8.9.2/8.9.1) id BAA71193;
Fri, 29 Jan 1999 01:16:44 -0800 (PST)
(envelope-from dillon)
Date: Fri, 29 Jan 1999 01:16:44 -0800 (PST)
From: Matthew Dillon <dillon@apollo.backplane.com>
Message-Id: <199901290916.BAA71193@apollo.backplane.com>
To: Bjoern Fischer <bfischer@Techfak.Uni-Bielefeld.DE>
Cc: freebsd-stable@FreeBSD.ORG, freebsd-current@FreeBSD.ORG
Subject: Re: nuts'n'bolts in vfs_bio
References: <19990129094616.A555@frolic.no-support.loc>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
:Hello,
:
:as Matthew said in freebsd-current@ vfs_bio:getblk() still
:needs work (B_CACHE/B_DELWRI stuff).
:
:Running 3.0-stable (Jan 26) it still happens that some NFS
:writes seem to remain uncommited on the server.
:
:Is there a chance to get it into -stable before releasing
:in mid February?
:
: Thanks,
:
: Bjoern
Absolutely! I thought I had backported everything but I
could have missed something. I'll go through and review
it.
-Matt
:--
:-----BEGIN GEEK CODE BLOCK-----
:GCS d--(+) s++: a- C+++(-) UBL++++OSI++++$ P+++(-) L+++(-) !E W- N+ o>+
:K- !w !O !M !V PS++ PE- PGP++ t+++ !5 X++ tv- b+++ D++ G e+ h-- y+
:------END GEEK CODE BLOCK------
:
:To Unsubscribe: send mail to majordomo@FreeBSD.org
:with "unsubscribe freebsd-current" in the body of the message
:
Matthew Dillon
<dillon@backplane.com>
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Fri Jan 29 01:23:13 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id BAA20776
for freebsd-current-outgoing; Fri, 29 Jan 1999 01:23:13 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA20759;
Fri, 29 Jan 1999 01:23:09 -0800 (PST)
(envelope-from dillon@apollo.backplane.com)
Received: (from dillon@localhost)
by apollo.backplane.com (8.9.2/8.9.1) id BAA75985;
Fri, 29 Jan 1999 01:23:05 -0800 (PST)
(envelope-from dillon)
Date: Fri, 29 Jan 1999 01:23:05 -0800 (PST)
From: Matthew Dillon <dillon@apollo.backplane.com>
Message-Id: <199901290923.BAA75985@apollo.backplane.com>
To: Bjoern Fischer <bfischer@Techfak.Uni-Bielefeld.DE>
Cc: freebsd-stable@FreeBSD.ORG, freebsd-current@FreeBSD.ORG
Subject: Re: nuts'n'bolts in vfs_bio
References: <19990129094616.A555@frolic.no-support.loc>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
:Hello,
:
:as Matthew said in freebsd-current@ vfs_bio:getblk() still
:needs work (B_CACHE/B_DELWRI stuff).
:
:Running 3.0-stable (Jan 26) it still happens that some NFS
:writes seem to remain uncommited on the server.
:
:Is there a chance to get it into -stable before releasing
:in mid February?
:
: Thanks,
:
: Bjoern
Please try this diff ( against RELENG_3 kern/vfs_bio.c ) and
tell me if it works.
This is for STABLE only. Current already has this patch.
-Matt
Matthew Dillon
<dillon@backplane.com>
Index: sys/kern/vfs_bio.c
===================================================================
RCS file: /home/ncvs/src/sys/kern/vfs_bio.c,v
retrieving revision 1.193.2.2
diff -u -r1.193.2.2 vfs_bio.c
--- vfs_bio.c 1999/01/25 01:59:26 1.193.2.2
+++ vfs_bio.c 1999/01/29 09:22:32
@@ -1466,7 +1466,10 @@
* contain fully valid pages. Normal (old-style) buffers
* should be fully valid.
*/
- if (bp->b_flags & B_VMIO) {
+ if (
+ (bp->b_flags & (B_VMIO|B_CACHE)) == (B_VMIO|B_CACHE) &&
+ (bp->b_vp->v_tag != VT_NFS || bp->b_validend <= 0)
+ ) {
int checksize = bp->b_bufsize;
int poffset = bp->b_offset & PAGE_MASK;
int resid;
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Fri Jan 29 01:31:38 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id BAA21690
for freebsd-current-outgoing; Fri, 29 Jan 1999 01:31:38 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from allegro.lemis.com (allegro.lemis.com [192.109.197.134])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA21684
for <current@FreeBSD.ORG>; Fri, 29 Jan 1999 01:31:34 -0800 (PST)
(envelope-from grog@freebie.lemis.com)
Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137])
by allegro.lemis.com (8.9.1/8.9.0) with ESMTP id UAA00391;
Fri, 29 Jan 1999 20:01:26 +1030 (CST)
Received: (from grog@localhost)
by freebie.lemis.com (8.9.2/8.9.0) id UAA17655;
Fri, 29 Jan 1999 20:01:24 +1030 (CST)
Date: Fri, 29 Jan 1999 20:01:23 +1030
From: Greg Lehey <grog@lemis.com>
To: Sheldon Hearn <axl@iafrica.com>
Cc: Mikhail Teterin <mi@kot.ne.mediaone.net>, current@FreeBSD.ORG
Subject: Re: btokup().. patch to STYLE(9) (fwd)
Message-ID: <19990129200123.I8473@freebie.lemis.com>
References: <199901290555.AAA28927@kot.ne.mediaone.net> <88592.917598420@axl.noc.iafrica.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.95.1i
In-Reply-To: <88592.917598420@axl.noc.iafrica.com>; from Sheldon Hearn on Fri, Jan 29, 1999 at 10:27:00AM +0200
WWW-Home-Page: http://www.lemis.com/~grog
Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia
Phone: +61-8-8388-8286
Fax: +61-8-8388-8725
Mobile: +61-41-739-7062
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
On Friday, 29 January 1999 at 10:27:00 +0200, Sheldon Hearn wrote:
> On Fri, 29 Jan 1999 00:55:21 EST, Mikhail Teterin wrote:
>> Everybody's goal is to keep/make code readable (accusations of "trying
>> to obfuscate" are silly). You, people, are just not agreeing what
>> "readable" means. Hoping to aid in the ending of this thread(s),
>
> Thank you very much. This is _exactly_ the point here.
>
> As far as I see it, there are a lot of people who are saying
>
> "I want to use parens to improve readability"
>
> when what they really mean is
>
> "I want to use parens to obviate the need to learn operator precedence."
I suppose that depends on whether you consider the code write-only or
read-write.
> I can't imagine how unnecessary parens are going to improve
> "readability" for anyone who knows his/her operator precedence.
What about the others?
> What it does is allow folks who aren't sure about what they're doing
> to get around doing things properly.
Remember, we're not talking about the writer now, we're talking about
the reader, who in the general case is not the same person.
To quote ``Design and implementation'':
Documentation is the castor oil of programming. Managers know it
must be good because the programmers hate it so much.
Adding the occasional superfluous brace or paren pair can help a lot
there. And if superfluous parens are so bad, explain why the kernel
is full of things like:
return (error);
Greg
--
See complete headers for address, home page and phone numbers
finger grog@lemis.com for PGP public key
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Fri Jan 29 01:39:47 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id BAA22781
for freebsd-current-outgoing; Fri, 29 Jan 1999 01:39:47 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA22775
for <current@FreeBSD.ORG>; Fri, 29 Jan 1999 01:39:45 -0800 (PST)
(envelope-from phk@critter.freebsd.dk)
Received: from critter.freebsd.dk (localhost [127.0.0.1])
by critter.freebsd.dk (8.9.1/8.8.5) with ESMTP id KAA02620;
Fri, 29 Jan 1999 10:37:29 +0100 (CET)
To: Sheldon Hearn <axl@iafrica.com>
cc: Mikhail Teterin <mi@kot.ne.mediaone.net>, current@FreeBSD.ORG
Subject: Re: btokup().. patch to STYLE(9) (fwd)
In-reply-to: Your message of "Fri, 29 Jan 1999 11:02:12 +0200."
<90073.917600532@axl.noc.iafrica.com>
Date: Fri, 29 Jan 1999 10:37:28 +0100
Message-ID: <2618.917602648@critter.freebsd.dk>
From: Poul-Henning Kamp <phk@critter.freebsd.dk>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
>
>> The parans have the same function as commas in most latin alphabet
>> based languages: to convey structure.
>
>I think you've picked the wrong analogy. The rules of the language
>dictate certain cases in which commas are required. Extraneous use of
>commas decreases readability.
Wrong, there are 3 major systems for commas, but lets not open
that discussion now.
>When it comes to code, do you not agree that the trained eye knows which
>operators to seek to first in an expression? I can't think of an analogy
>in the English language, since one doesn't "seek to" commas, one simply
>reads from left to right.
A little to little or a little too much is equally evil. I personally
prefer more parans than my C compiler needs.
--
Poul-Henning Kamp FreeBSD coreteam member
phk@FreeBSD.ORG "Real hackers run -current on their laptop."
FreeBSD -- It will take a long time before progress goes too far!
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Fri Jan 29 01:47:25 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id BAA23591
for freebsd-current-outgoing; Fri, 29 Jan 1999 01:47:25 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from nlsystems.com (nlsys.demon.co.uk [158.152.125.33])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA23582;
Fri, 29 Jan 1999 01:47:16 -0800 (PST)
(envelope-from dfr@nlsystems.com)
Received: from localhost (dfr@localhost)
by nlsystems.com (8.9.1/8.8.5) with SMTP id JAA06664;
Fri, 29 Jan 1999 09:50:02 GMT
Date: Fri, 29 Jan 1999 09:50:01 +0000 (GMT)
From: Doug Rabson <dfr@nlsystems.com>
To: Gary Palmer <gpalmer@FreeBSD.ORG>
cc: freebsd-current@FreeBSD.ORG
Subject: Re: make release - Party Time! (but not for the AXP)
In-Reply-To: <54929.917595844@gjp.erols.com>
Message-ID: <Pine.BSF.4.01.9901290949230.95594-100000@herring.nlsystems.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
On Fri, 29 Jan 1999, Gary Palmer wrote:
> "John W. DeBoskey" wrote in message ID
> <199901271433.JAA75703@bb01f39.unx.sas.com>:
> > A note of thanks to Jordan and everyone else who's been working
> > on the new 4.0 code... We have our first complete processing of
> > cd /usr/src && make world && cd release && make release.
>
> Unfortunately the AXP is still hosed :(
>
> ...
>
> I somehow doubt that those will fit on a 1.4Mb floppy :)
I just sent patches to Jordan which include a fix for this.
>
> Anyone working to get gzip functional under ELF?
No idea.
--
Doug Rabson Mail: dfr@nlsystems.com
Nonlinear Systems Ltd. Phone: +44 181 442 9037
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Fri Jan 29 02:00:45 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id CAA25204
for freebsd-current-outgoing; Fri, 29 Jan 1999 02:00:45 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from news.IAEhv.nl (news.IAEhv.nl [194.151.64.4])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA25199
for <current@FreeBSD.ORG>; Fri, 29 Jan 1999 02:00:41 -0800 (PST)
(envelope-from marc@bowtie.nl)
Received: (from uucp@localhost)
by news.IAEhv.nl (8.9.1/8.9.1) with IAEhv.nl id LAA19542;
Fri, 29 Jan 1999 11:00:06 +0100 (MET)
Received: from localhost (localhost [127.0.0.1])
by bowtie.nl (8.8.8/8.8.8) with ESMTP id KAA18903;
Fri, 29 Jan 1999 10:56:17 +0100 (CET)
(envelope-from marc@bowtie.nl)
Message-Id: <199901290956.KAA18903@bowtie.nl>
X-Mailer: exmh version 2.0.2 2/24/98
To: Julian Elischer <julian@whistle.com>
cc: Bruce Evans <bde@zeta.org.au>, mike@smith.net.au, archie@whistle.com,
current@FreeBSD.ORG, dillon@apollo.backplane.com, nate@mt.sri.com
Subject: Re: btokup().. patch to STYLE(9) (fwd)
In-reply-to: julian's message of Thu, 28 Jan 1999 18:42:22 -0800.
<Pine.BSF.3.95.990128184127.11856M-100000@current1.whistle.com>
Reply-to: marc@bowtie.nl
Date: Fri, 29 Jan 1999 10:56:16 +0100
From: Marc van Kempen <marc@bowtie.nl>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
> so far you are the first and only objector..
> which makes you outnumbered by 10 to 1 on email counts..
>
I agree completely, saving a few bytes in the source code is not
worth the obfuscation that results, writing correct programs is hard
enough as it is, without having to suffer from obfuscation.
Marc.
----------------------------------------------------
Marc van Kempen BowTie Technology
Email: marc@bowtie.nl WWW & Databases
tel. +31 40 2 43 20 65
fax. +31 40 2 44 21 86 http://www.bowtie.nl
----------------------------------------------------
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Fri Jan 29 02:05:41 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id CAA25488
for freebsd-current-outgoing; Fri, 29 Jan 1999 02:05:41 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from axl.noc.iafrica.com (axl.noc.iafrica.com [196.31.1.175])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA25481
for <current@freebsd.org>; Fri, 29 Jan 1999 02:05:32 -0800 (PST)
(envelope-from sheldonh@axl.noc.iafrica.com)
Received: from sheldonh (helo=axl.noc.iafrica.com)
by axl.noc.iafrica.com with local-esmtp (Exim 2.11 #1)
id 106AnQ-000O5J-00; Fri, 29 Jan 1999 12:05:04 +0200
From: Sheldon Hearn <axl@iafrica.com>
To: Greg Lehey <grog@lemis.com>
cc: current@FreeBSD.ORG
Subject: Re: btokup().. patch to STYLE(9) (fwd)
In-reply-to: Your message of "Fri, 29 Jan 1999 20:01:23 +1030."
<19990129200123.I8473@freebie.lemis.com>
Date: Fri, 29 Jan 1999 12:05:04 +0200
Message-ID: <92584.917604304@axl.noc.iafrica.com>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
On Fri, 29 Jan 1999 20:01:23 +1030, Greg Lehey wrote:
> > I can't imagine how unnecessary parens are going to improve
> > "readability" for anyone who knows his/her operator precedence.
>
> What about the others?
I'd like to know that people who don't know operator precedence are
leaving the kernel code alone, eh? :-)
> Remember, we're not talking about the writer now, we're talking about
> the reader, who in the general case is not the same person.
Operator precedence is not a matter of perspective. A different person,
who knows his or her operator precedence, will find the expression as
easy to read as the writer.
> Documentation is the castor oil of programming. Managers know it
> must be good because the programmers hate it so much.
I take this to mean "provide above your expression a comment that
explains what you're doing", not "clutter your expression with
unnecessary parens in case you've made a mistake that nobody will spot
because you haven't commented your code properly."
The reason I'm interested in this (now tiresome) thread is that I'd much
rather have to read
/*
* Bail out if the time left to next transaction is less than
* the duration of the previous transaction.
*/
if (t % u - n % u < d % u) {
than
if (((t % u) - (n % u)) < (d % u)) {
Giving folks the go-ahead to use parens as a form of documentation is
misguided and will end in tears. MHO.
Ciao,
Sheldon.
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Fri Jan 29 02:46:44 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id CAA28717
for freebsd-current-outgoing; Fri, 29 Jan 1999 02:46:44 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from nlsystems.com (nlsys.demon.co.uk [158.152.125.33])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA28711
for <current@freebsd.org>; Fri, 29 Jan 1999 02:46:41 -0800 (PST)
(envelope-from dfr@nlsystems.com)
Received: from localhost (dfr@localhost)
by nlsystems.com (8.9.1/8.8.5) with SMTP id KAA09325;
Fri, 29 Jan 1999 10:49:13 GMT
Date: Fri, 29 Jan 1999 10:49:12 +0000 (GMT)
From: Doug Rabson <dfr@nlsystems.com>
To: Sheldon Hearn <axl@iafrica.com>
cc: Greg Lehey <grog@lemis.com>, current@FreeBSD.ORG
Subject: Re: btokup().. patch to STYLE(9) (fwd)
In-Reply-To: <92584.917604304@axl.noc.iafrica.com>
Message-ID: <Pine.BSF.4.01.9901291044130.95594-100000@herring.nlsystems.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
On Fri, 29 Jan 1999, Sheldon Hearn wrote:
>
>
> On Fri, 29 Jan 1999 20:01:23 +1030, Greg Lehey wrote:
>
> > > I can't imagine how unnecessary parens are going to improve
> > > "readability" for anyone who knows his/her operator precedence.
> >
> > What about the others?
>
> I'd like to know that people who don't know operator precedence are
> leaving the kernel code alone, eh? :-)
I am a kernel developer. I also sometimes forget some of the precedence
rules. Often enough that I use strict parenthesising when I use those
operators.
>
> > Remember, we're not talking about the writer now, we're talking about
> > the reader, who in the general case is not the same person.
>
> Operator precedence is not a matter of perspective. A different person,
> who knows his or her operator precedence, will find the expression as
> easy to read as the writer.
I don't agree. If you have to stop and think about the stupid precedence
rules three times in an expression, the expression is too complicated and
should be simplified.
>
> > Documentation is the castor oil of programming. Managers know it
> > must be good because the programmers hate it so much.
>
> I take this to mean "provide above your expression a comment that
> explains what you're doing", not "clutter your expression with
> unnecessary parens in case you've made a mistake that nobody will spot
> because you haven't commented your code properly."
>
> The reason I'm interested in this (now tiresome) thread is that I'd much
> rather have to read
>
> /*
> * Bail out if the time left to next transaction is less than
> * the duration of the previous transaction.
> */
> if (t % u - n % u < d % u) {
>
> than
>
> if (((t % u) - (n % u)) < (d % u)) {
This is a strawman. The original expression is perfectly fine (by my
rules). One could make a case for:
if ((t % u) - (n % u) < d % u)
>
> Giving folks the go-ahead to use parens as a form of documentation is
> misguided and will end in tears. MHO.
I don't agree, obviously.
--
Doug Rabson Mail: dfr@nlsystems.com
Nonlinear Systems Ltd. Phone: +44 181 442 9037
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Fri Jan 29 03:02:48 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id DAA00296
for freebsd-current-outgoing; Fri, 29 Jan 1999 03:02:48 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from peach.ocn.ne.jp (peach.ocn.ne.jp [210.145.254.87])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA00290
for <freebsd-current@FreeBSD.ORG>; Fri, 29 Jan 1999 03:02:46 -0800 (PST)
(envelope-from dcs@newsguy.com)
Received: from newsguy.com by peach.ocn.ne.jp (8.9.1a/OCN) id UAA13701; Fri, 29 Jan 1999 20:01:48 +0900 (JST)
Message-ID: <36B19501.B55A19D0@newsguy.com>
Date: Fri, 29 Jan 1999 20:01:21 +0900
From: "Daniel C. Sobral" <dcs@newsguy.com>
X-Mailer: Mozilla 4.5 [en] (Win98; I)
X-Accept-Language: pt-BR,ja
MIME-Version: 1.0
To: Robert Nordier <rnordier@nordier.com>
CC: mike@smith.net.au, mystify@friley-184-92.res.iastate.edu,
freebsd-current@FreeBSD.ORG
Subject: Re: Reading a text file with BTX
References: <199901290453.GAA07540@ceia.nordier.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
Robert Nordier wrote:
>
> The boot manager menu, for example
>
> F1 FreeBSD
> F2 UNIX
> F5 Drive 1
>
> Default: F1
Y'know, in my computer that F5 is "Drive 0", and the system will not
boot unless I select it first. Selecting it, makes the OSes boot and
F5 disappear.
--
Daniel C. Sobral (8-DCS)
dcs@newsguy.com
If you sell your soul to the Devil and all you get is an MCSE from
it, you haven't gotten market rate.
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Fri Jan 29 03:17:35 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id DAA01892
for freebsd-current-outgoing; Fri, 29 Jan 1999 03:17:35 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from implode.root.com (root.com [208.221.12.98])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA01886
for <FreeBSD-current@FreeBSD.ORG>; Fri, 29 Jan 1999 03:17:33 -0800 (PST)
(envelope-from root@implode.root.com)
Received: from implode.root.com (localhost [127.0.0.1])
by implode.root.com (8.8.8/8.8.5) with ESMTP id DAA16869;
Fri, 29 Jan 1999 03:16:34 -0800 (PST)
Message-Id: <199901291116.DAA16869@implode.root.com>
To: Greg Lehey <grog@lemis.com>
cc: FreeBSD current users <FreeBSD-current@FreeBSD.ORG>
Subject: Re: The future of a.out support?
In-reply-to: Your message of "Fri, 29 Jan 1999 15:39:41 +1030."
<19990129153941.M8473@freebie.lemis.com>
From: David Greenman <dg@root.com>
Reply-To: dg@root.com
Date: Fri, 29 Jan 1999 03:16:34 -0800
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
>It was my understanding that the kernel would continue to support
>a.out, and I think that's important. If FreeBSD can support SCO,
>Linux, Solaris, BSDI, NetBSD and OpenBSD, it seems important that it
>should also contain support for FreeBSD, even old, obsolete versions.
>
>May I assume that this is the case, and that the comment applies only
>to what ``make world'' builds? Even so, though, I think that it
>is important to provide a way to build the libraries and ld.so if
>necessary, though probably not in the world target.
Yes, a.out execution support will be standard in FreeBSD for at least
several more years. At some point it may become an option, but that's a
long way off.
The only thing people are talking about is support for building the
system binaries in a.out. We're moving to ELF because at some point our
"make world" source build system, not to mention the compiler toolchain,
will no longer support building a.out binaries.
-DG
David Greenman
Co-founder/Principal Architect, The FreeBSD Project
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Fri Jan 29 03:22:46 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id DAA02351
for freebsd-current-outgoing; Fri, 29 Jan 1999 03:22:46 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from zeus.theinternet.com.au (zeus.theinternet.com.au [203.34.176.2])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA02332
for <current@FreeBSD.ORG>; Fri, 29 Jan 1999 03:22:43 -0800 (PST)
(envelope-from akm@zeus.theinternet.com.au)
Received: (from akm@localhost)
by zeus.theinternet.com.au (8.8.7/8.8.7) id VAA01208;
Fri, 29 Jan 1999 21:21:55 +1000 (EST)
(envelope-from akm)
From: Andrew Kenneth Milton <akm@zeus.theinternet.com.au>
Message-Id: <199901291121.VAA01208@zeus.theinternet.com.au>
Subject: Re: btokup().. patch to STYLE(9) (fwd)
In-Reply-To: <Pine.BSF.4.01.9901291044130.95594-100000@herring.nlsystems.com> from Doug Rabson at "Jan 29, 99 10:49:12 am"
To: dfr@nlsystems.com (Doug Rabson)
Date: Fri, 29 Jan 1999 21:21:55 +1000 (EST)
Cc: axl@iafrica.com, grog@lemis.com, current@FreeBSD.ORG
X-Mailer: ELM [version 2.4ME+ PL32 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
+----[ Doug Rabson ]---------------------------------------------
| On Fri, 29 Jan 1999, Sheldon Hearn wrote:
| >
| > The reason I'm interested in this (now tiresome) thread is that I'd much
| > rather have to read
| >
| > /*
| > * Bail out if the time left to next transaction is less than
| > * the duration of the previous transaction.
| > */
| > if (t % u - n % u < d % u) {
| >
| > than
| >
| > if (((t % u) - (n % u)) < (d % u)) {
|
| This is a strawman. The original expression is perfectly fine (by my
| rules). One could make a case for:
|
| if ((t % u) - (n % u) < d % u)
It also does not imply perfection. I don't think being a 'kernel
programmer' confers any more perfection than any other type of
programmer. It also does not imply immortality.
All this about "I don't need parens/braces/whitespace, and anyone that
does shouldn't touch my/the/kernel code" is egotistcal elitist crap.
The only arguments I've seen for less 'punctuation' are
a) "I" don't need them
b) "I" don't like what it looks like with them
c) There might be bugs introduced due to parens.
Well a and b are crap, and c is no worse off than we are now, since
there seems to be bugs caused by a lack of them.
As it is you don't have to use the extra punctuation if you don't
want to, it was proposed as *optional*. If you don't like code with
the punctuation, don't work on it (or change it back to whatever you
like when you next have to work on it).
--
Totally Holistic Enterprises Internet| P:+61 7 3870 0066 | Andrew
The Internet (Aust) Pty Ltd | F:+61 7 3870 4477 | Milton
ACN: 082 081 472 | M:+61 416 022 411 |72 Col .Sig
PO Box 837 Indooroopilly QLD 4068 |akm@theinternet.com.au|Specialist
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Fri Jan 29 03:49:47 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id DAA04688
for freebsd-current-outgoing; Fri, 29 Jan 1999 03:49:47 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from ns1.yes.no (ns1.yes.no [195.204.136.10])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA04676;
Fri, 29 Jan 1999 03:49:40 -0800 (PST)
(envelope-from eivind@bitbox.follo.net)
Received: from bitbox.follo.net (bitbox.follo.net [195.204.143.218])
by ns1.yes.no (8.9.1a/8.9.1) with ESMTP id MAA05345;
Fri, 29 Jan 1999 12:49:34 +0100 (CET)
Received: (from eivind@localhost)
by bitbox.follo.net (8.8.8/8.8.6) id MAA35165;
Fri, 29 Jan 1999 12:49:33 +0100 (MET)
Date: Fri, 29 Jan 1999 12:49:33 +0100
From: Eivind Eklund <eivind@FreeBSD.ORG>
To: arch@FreeBSD.ORG
Subject: Re: "JAIL" code headed for -current.
Message-ID: <19990129124932.A34859@bitbox.follo.net>
References: <29763.917434096.kithrup.freebsd.current@critter.freebsd.dk> <199901271944.LAA15317@kithrup.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.95.1i
In-Reply-To: <199901271944.LAA15317@kithrup.com>; from Sean Eric Fagan on Wed, Jan 27, 1999 at 11:44:35AM -0800
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
I'm moving this to FreeBSD-arch, due to taking the discussion quite a
bit in that direction.
On Wed, Jan 27, 1999 at 11:44:35AM -0800, Sean Eric Fagan wrote:
> In article
> <29763.917434096.kithrup.freebsd.current@critter.freebsd.dk> you
> write:
> >The biggest impact of this is a new argument to the suser() call
> >all over the kernel:
> >
> > suser(NOJAIL, bla, bla);
> >or
> > suser(0, bla, bla);
>
> Oh, goody, more gratuitous incompatibilities with everyone else.
suser() is not generally compatible; the return value has different
(opposite) meanings in different OSes.
I do, however, think there are a couple of problems with the
implementation as outlined above, even if we ignore any
incompatibility arguments:
1. It is insecure in the face of changes. Any security policy should
default to deny; the above policy default to 'accept'. Later
kernel mods are likely to introduce security holes.
2. If more similar authentication mods are made, they also require
changes all over the system.
3. Policy is distributed everywhere, instead of a being concentrated
in one place, which makes it hard to verify.
I have been planning some changes for much of the same purpose. My
approach is to introduce a string identifing each context for suser(),
to allow people that want to hack on the authentication system an easy
place to start from. In a similar setting before, I've successfully
used a hierarchical system, going from less to more specific context
specification.
Example: a chflags in an FFS would be something like
"fs/chflag/ufs/ffs" while in an lfs, it would be "fs/chflag/ufs/lfs".
I've not thought much about the backend for this - if it is to be used
in general (instead of just as a good starting point for people that
want to do some authentication hacks on their machine), there should
probably be some way to express interest in just some of the nodes of
the tree the different authentication types form, and caching to avoid
string parsing.
If phk would be satisfied with a slightly hackish solution for the
time being, we could introduce the above, and just use string compares
for his acceptable cases for the time being. This could be done as a
binary tree, so it wouldn't be quite as expensive as it sounds.
Context for the people not having done their own source investigation
of credentials use:
We have approx 180 root checks using suser():
eivind(bitbox)--% glimpse -y suser | wc -l
185
We have approx 90 checks for root that are NOT done using suser(),
rather using explict comparisons with 0:
eivind(bitbox)--% glimpse -y cr_uid | grep 0 | wc -l
94
Another interesting statistic for root mods probably is the number of
cr_uid references in the kernel (all of these should be inspected):
eivind(bitbox)--% glimpse -y cr_uid | wc -l
283
If you're thinking of a full-blown look at capabilities, cr_gid is
used 28 places, cr_groups 60, and cr_ngroups 52. Given the relatively
low number of credentials uses (less than 400), it shouldn't be more
than a couple of evenings worth of work to collapse it all back to a
set of function or macro calls, creating a much more suitable
environment for capabilities hacking.
Eivind.
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Fri Jan 29 04:06:48 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id EAA08302
for freebsd-current-outgoing; Fri, 29 Jan 1999 04:06:48 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from vader.cs.berkeley.edu (vader.CS.Berkeley.EDU [128.32.38.234])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA08296
for <FreeBSD-current@FreeBSD.ORG>; Fri, 29 Jan 1999 04:06:46 -0800 (PST)
(envelope-from asami@vader.cs.berkeley.edu)
Received: from silvia.hip.berkeley.edu (sji-ca34-116.ix.netcom.com [205.186.215.244]) by vader.cs.berkeley.edu (8.8.7/8.7.3) with ESMTP id EAA07831; Fri, 29 Jan 1999 04:06:37 -0800 (PST)
Received: (from asami@localhost) by silvia.hip.berkeley.edu (8.9.1/8.6.9) id EAA73205; Fri, 29 Jan 1999 04:06:32 -0800 (PST)
Date: Fri, 29 Jan 1999 04:06:32 -0800 (PST)
Message-Id: <199901291206.EAA73205@silvia.hip.berkeley.edu>
To: dg@root.com
CC: grog@lemis.com, FreeBSD-current@FreeBSD.ORG
In-reply-to: <199901291116.DAA16869@implode.root.com> (message from David
Greenman on Fri, 29 Jan 1999 03:16:34 -0800)
Subject: Re: The future of a.out support?
From: asami@FreeBSD.ORG (Satoshi Asami)
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
* Yes, a.out execution support will be standard in FreeBSD for at least
* several more years. At some point it may become an option, but that's a
* long way off.
* The only thing people are talking about is support for building the
* system binaries in a.out. We're moving to ELF because at some point our
* "make world" source build system, not to mention the compiler toolchain,
* will no longer support building a.out binaries.
That sounds fine. However, there are still people stuck with a.out
libraries out there (netscape comes to mind). Is the 3.1R installer
going to include a.out libraries as an option?
Satoshi
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Fri Jan 29 04:29:10 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id EAA09964
for freebsd-current-outgoing; Fri, 29 Jan 1999 04:29:10 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from ns1.yes.no (ns1.yes.no [195.204.136.10])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA09959
for <current@FreeBSD.ORG>; Fri, 29 Jan 1999 04:29:04 -0800 (PST)
(envelope-from eivind@bitbox.follo.net)
Received: from bitbox.follo.net (bitbox.follo.net [195.204.143.218])
by ns1.yes.no (8.9.1a/8.9.1) with ESMTP id NAA10570;
Fri, 29 Jan 1999 13:28:54 +0100 (CET)
Received: (from eivind@localhost)
by bitbox.follo.net (8.8.8/8.8.6) id NAA35350;
Fri, 29 Jan 1999 13:28:53 +0100 (MET)
Date: Fri, 29 Jan 1999 13:28:53 +0100
From: Eivind Eklund <eivind@FreeBSD.ORG>
To: Sheldon Hearn <axl@iafrica.com>
Cc: current@FreeBSD.ORG
Subject: Re: btokup().. patch to STYLE(9) (fwd)
Message-ID: <19990129132853.B34859@bitbox.follo.net>
References: <19990129200123.I8473@freebie.lemis.com> <92584.917604304@axl.noc.iafrica.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.95.1i
In-Reply-To: <92584.917604304@axl.noc.iafrica.com>; from Sheldon Hearn on Fri, Jan 29, 1999 at 12:05:04PM +0200
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
On Fri, Jan 29, 1999 at 12:05:04PM +0200, Sheldon Hearn wrote:
>
>
> On Fri, 29 Jan 1999 20:01:23 +1030, Greg Lehey wrote:
>
> > > I can't imagine how unnecessary parens are going to improve
> > > "readability" for anyone who knows his/her operator precedence.
> >
> > What about the others?
>
> I'd like to know that people who don't know operator precedence are
> leaving the kernel code alone, eh? :-)
I know my operator precedence. I still often find that using extra
parentheses make code more readable. I don't do it in FreeBSD, but I
regularly use more parentheses than strictly necessary for non-FreeBSD
code.
I also am in favour of the change to style(9).
Eivind.
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Fri Jan 29 04:58:35 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id EAA12987
for freebsd-current-outgoing; Fri, 29 Jan 1999 04:58:35 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from quackerjack.cc.vt.edu (quackerjack.cc.vt.edu [198.82.160.250])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA12963
for <current@FreeBSD.ORG>; Fri, 29 Jan 1999 04:58:31 -0800 (PST)
(envelope-from jobaldwi@vt.edu)
Received: from sable.cc.vt.edu (sable.cc.vt.edu [128.173.16.30])
by quackerjack.cc.vt.edu (8.8.8/8.8.8) with ESMTP id HAA08927;
Fri, 29 Jan 1999 07:56:25 -0500 (EST)
Received: from john.baldwin.cx (jobaldwi.campus.vt.edu [198.82.67.63])
by sable.cc.vt.edu (8.8.8/8.8.8) with ESMTP id HAA16241;
Fri, 29 Jan 1999 07:56:24 -0500 (EST)
Message-ID: <XFMail.990129025626.jobaldwi@vt.edu>
X-Mailer: XFMail 1.3 [p0] on FreeBSD
X-Priority: 3 (Normal)
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 8bit
MIME-Version: 1.0
In-Reply-To: <90073.917600532@axl.noc.iafrica.com>
Date: Fri, 29 Jan 1999 02:56:26 -0500 (EST)
From: John Baldwin <jobaldwi@vt.edu>
To: Sheldon Hearn <axl@iafrica.com>
Subject: Re: btokup().. patch to STYLE(9) (fwd)
Cc: current@FreeBSD.ORG, Poul-Henning Kamp <phk@critter.freebsd.dk>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
-----BEGIN PGP SIGNED MESSAGE-----
On 29-Jan-99 Sheldon Hearn wrote:
> When it comes to code, do you not agree that the trained eye knows which
> operators to seek to first in an expression? I can't think of an analogy
> in the English language, since one doesn't "seek to" commas, one simply
> reads from left to right.
I've watched this thread for a while now and I think I have a comment from a
point of view that hasn't been expressed much. I am *not* a kernel coder at
the moment. I would like to be one, but I still have much to learn about the
internals and whats going on. Now, as someone who is new to the source code,
I'm need to use as much brain power as I can to understand the concepts and the
'big picture'. I'd rather not waste part of that by picking apart every
expression I see. It's not that I don't know the order of operations, but I
still have to decipher every expression regardless, and it's just a tad bit
easier sometimes if a few extra parens are thrown in for readability.
By running an open source project, you are in a unique position in that
there are other programmers who can look at your code and learn from it.
Hopefully they will eventually use that knowledge to contribute back to the
project, as I hope to. The more readable the code, the easier it is for them to
learn from it.
- ---
John Baldwin <jobaldwi@vt.edu> -- http://members.freedomnet.com/~jbaldwin/
PGP Key: http://members.freedomnet.com/~jbaldwin/pgpkey.asc
-----BEGIN PGP SIGNATURE-----
Version: 2.6.2
iQCVAwUBNrFmWLaE8XzBCodNAQGs5wP9FloMv6GZe/NhlX0Os9LLoq8s27VMmH4X
e+yXJeoKVUJtAOK5Y78bs/7n/9inqAH2CpnvPqdsKbcHbGYIsB15KxUj5qQU5Rsg
liRYOIgn3+fRxHtaem80dsg2+JcSJF1gY5wAnykbdPKHy0/ebAk2GD5RgkINUTNJ
Zu5ybkbZdwE=
=GmaX
-----END PGP SIGNATURE-----
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Fri Jan 29 05:15:05 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id FAA15040
for freebsd-current-outgoing; Fri, 29 Jan 1999 05:15:05 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from awfulhak.org (awfulhak.force9.co.uk [195.166.136.63])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA14982
for <current@FreeBSD.ORG>; Fri, 29 Jan 1999 05:14:58 -0800 (PST)
(envelope-from brian@Awfulhak.org)
Received: from keep.lan.Awfulhak.org (keep.lan.Awfulhak.org [172.16.0.8])
by awfulhak.org (8.8.8/8.8.8) with ESMTP id NAA24120;
Fri, 29 Jan 1999 13:14:51 GMT
(envelope-from brian@Awfulhak.org)
Received: from keep.lan.Awfulhak.org (localhost [127.0.0.1])
by keep.lan.Awfulhak.org (8.9.2/8.9.2) with ESMTP id IAA00595;
Fri, 29 Jan 1999 08:49:01 GMT
(envelope-from brian@keep.lan.Awfulhak.org)
Message-Id: <199901290849.IAA00595@keep.lan.Awfulhak.org>
X-Mailer: exmh version 2.0.2 2/24/98
To: Leif Neland <leif@neland.dk>
cc: Brian Somers <brian@Awfulhak.org>, current@FreeBSD.ORG
Subject: Re: PPP (userland) troubles ?
In-reply-to: Your message of "Fri, 29 Jan 1999 00:16:39 +0100."
<Pine.BSF.4.05.9901290010480.12987-100000@arnold.neland.dk>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Fri, 29 Jan 1999 08:49:01 +0000
From: Brian Somers <brian@Awfulhak.org>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
> Would it be possible to add an exponential delay when connecting fails for
> either reason?
>
> I just received my specified phone-bill. It filled 42 pages, with hundreds
> of calls with a duration of 17 seconds. (Because my modem needs to be
> software-reset; I have mentioned this before).
>
> Each call costs a few cents; I'm billed both for each connect, and for
> connect time. It all adds up. And I'm connected to the other modem, even
> if the handshake doesn't work.
I've added a
set redial seconds[+add[-max]] attempts
to my TODO list.
> Leif
--
Brian <brian@Awfulhak.org> <brian@FreeBSD.org> <brian@OpenBSD.org>
<http://www.Awfulhak.org>
Don't _EVER_ lose your sense of humour !
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Fri Jan 29 05:15:19 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id FAA15133
for freebsd-current-outgoing; Fri, 29 Jan 1999 05:15:19 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from awfulhak.org (awfulhak.force9.co.uk [195.166.136.63])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA15091
for <current@FreeBSD.ORG>; Fri, 29 Jan 1999 05:15:14 -0800 (PST)
(envelope-from brian@Awfulhak.org)
Received: from keep.lan.Awfulhak.org (keep.lan.Awfulhak.org [172.16.0.8])
by awfulhak.org (8.8.8/8.8.8) with ESMTP id NAA24123;
Fri, 29 Jan 1999 13:14:56 GMT
(envelope-from brian@Awfulhak.org)
Received: from keep.lan.Awfulhak.org (localhost [127.0.0.1])
by keep.lan.Awfulhak.org (8.9.2/8.9.2) with ESMTP id IAA00519;
Fri, 29 Jan 1999 08:34:00 GMT
(envelope-from brian@keep.lan.Awfulhak.org)
Message-Id: <199901290834.IAA00519@keep.lan.Awfulhak.org>
X-Mailer: exmh version 2.0.2 2/24/98
To: Andrew Kenneth Milton <akm@zeus.theinternet.com.au>
cc: julian@whistle.com (Julian Elischer), mike@smith.net.au,
dillon@apollo.backplane.com, archie@whistle.com, nate@mt.sri.com,
current@FreeBSD.ORG
Subject: Re: btokup().. patch to STYLE(9) (fwd)
In-reply-to: Your message of "Fri, 29 Jan 1999 13:09:55 +1000."
<199901290309.NAA25300@zeus.theinternet.com.au>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Fri, 29 Jan 1999 08:34:00 +0000
From: Brian Somers <brian@Awfulhak.org>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
> +----[ Julian Elischer ]---------------------------------------------
> | yeah but not a SINGLE person has said to not commit the patch to style(9)
> | so I'm going to do it later tonight..
> | (It doesn't make extra braces MANDATORY but it does ALLOW them.)
> |
> | julian
> | (if this doesn't bring some NEYs I'll be amazed..)
>
> Only from people who don't seem to cut code in the real world.
[.....]
> There are only disadvantages to leaving them out.
I missed the original suggestion, but I have an objection to
*insisting* on extra braces (*allowing* is absolutely fine) -
such as gcc-2.8.1's idea that
if (x)
if (y)
blah1
else
blah2
should have braces around the inner if/else. As Nate has already
pointed out, it's not the compilers job to check that your style is
GNU flavoured.
I think this sort of warning should be removed from the system
compiler rather than changing all software to add the extraneous
braces.
My argument is that this sort of thing gets out of hand. I've seen
things such as
if (((a == b) || (c == d)))
where a, b, c & d are just simple variables - there are so many
redundant brackets that you have to double-check that there isn't
some weird grouping....
Also, with non-k&r style code, you can end up with so many redundant
braces that you can't see enough context on your screen to know what
the code is doing:
if (a)
{
expr1
}
else if (b)
{
expr2
}
else
....
But where do you draw the line in style(9) ? Dunno.
> --
> Totally Holistic Enterprises Internet| P:+61 7 3870 0066 | Andrew
> The Internet (Aust) Pty Ltd | F:+61 7 3870 4477 | Milton
> ACN: 082 081 472 | M:+61 416 022 411 |72 Col .Sig
> PO Box 837 Indooroopilly QLD 4068 |akm@theinternet.com.au|Specialist
--
Brian <brian@Awfulhak.org> <brian@FreeBSD.org> <brian@OpenBSD.org>
<http://www.Awfulhak.org>
Don't _EVER_ lose your sense of humour !
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Fri Jan 29 06:35:32 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id GAA21742
for freebsd-current-outgoing; Fri, 29 Jan 1999 06:35:32 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from isbalham.ist.co.uk (isbalham.ist.co.uk [192.31.26.1])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA21736
for <current@FreeBSD.ORG>; Fri, 29 Jan 1999 06:35:30 -0800 (PST)
(envelope-from rb@gid.co.uk)
Received: from gid.co.uk (uucp@localhost)
by isbalham.ist.co.uk (8.8.7/8.8.7) with UUCP id OAA13654;
Fri, 29 Jan 1999 14:35:28 GMT
(envelope-from rb@gid.co.uk)
Received: from localhost by seagoon.gid.co.uk; Fri, 29 Jan 1999 14:32:16 GMT
Date: Fri, 29 Jan 1999 14:32:15 +0000 (GMT)
From: Bob Bishop <rb@gid.co.uk>
X-Sender: rb@seagoon
To: Brian Somers <brian@Awfulhak.org>
cc: Andrew Kenneth Milton <akm@zeus.theinternet.com.au>,
Julian Elischer <julian@whistle.com>, mike@smith.net.au,
dillon@apollo.backplane.com, archie@whistle.com, nate@mt.sri.com,
current@FreeBSD.ORG
Subject: Re: btokup().. patch to STYLE(9) (fwd)
In-Reply-To: <199901290834.IAA00519@keep.lan.Awfulhak.org>
Message-ID: <Pine.BSF.3.96.990129143016.18157D-100000@seagoon>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
On Fri, 29 Jan 1999, Brian Somers wrote:
>[...]
> But where do you draw the line in style(9) ? Dunno.
Err on the side of redundancy, which cam be mechanically removed if you
don't happen to like it.
--
Bob Bishop +44 118 977 4017
rb@gid.co.uk fax +44 118 989 4254
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Fri Jan 29 06:53:10 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id GAA23541
for freebsd-current-outgoing; Fri, 29 Jan 1999 06:53:10 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from peach.ocn.ne.jp (peach.ocn.ne.jp [210.145.254.87])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA23377
for <current@FreeBSD.ORG>; Fri, 29 Jan 1999 06:53:06 -0800 (PST)
(envelope-from dcs@newsguy.com)
Received: from newsguy.com by peach.ocn.ne.jp (8.9.1a/OCN) id XAA12482; Fri, 29 Jan 1999 23:52:06 +0900 (JST)
Message-ID: <36B1C8CD.159C3575@newsguy.com>
Date: Fri, 29 Jan 1999 23:42:21 +0900
From: "Daniel C. Sobral" <dcs@newsguy.com>
X-Mailer: Mozilla 4.5 [en] (Win98; I)
X-Accept-Language: pt-BR,ja
MIME-Version: 1.0
To: Sheldon Hearn <axl@iafrica.com>
CC: Mikhail Teterin <mi@kot.ne.mediaone.net>, current@FreeBSD.ORG
Subject: Re: btokup().. patch to STYLE(9) (fwd)
References: <88592.917598420@axl.noc.iafrica.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
Sheldon Hearn wrote:
>
> As far as I see it, there are a lot of people who are saying
>
> "I want to use parens to improve readability"
>
> when what they really mean is
>
> "I want to use parens to obviate the need to learn operator precedence."
>
> I can't imagine how unnecessary parens are going to improve
> "readability" for anyone who knows his/her operator precedence. What
> it does is allow folks who aren't sure about what they're doing to get
> around doing things properly.
The human mind (at least the *normal* ones :) can handle a limited
number of items simultaneously. If an expression has more than five
"items" to be taken into account, you are already exceeding this
limit for some folks (though suspect most "heavy" programmers
"happen" to have higher capacities). And while expressions with more
than five *operators* to be taken into account might be uncommon, it
is not unusual for one also have to take into account what's between
them.
Just because it might be easy for you, it doesn't mean it is easy
for others, or even that is something one can learn.
--
Daniel C. Sobral (8-DCS)
dcs@newsguy.com
Would you mind not shooting at the thermonuclear weapons?
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Fri Jan 29 06:58:03 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id GAA23951
for freebsd-current-outgoing; Fri, 29 Jan 1999 06:58:03 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from peach.ocn.ne.jp (peach.ocn.ne.jp [210.145.254.87])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA23936
for <current@FreeBSD.ORG>; Fri, 29 Jan 1999 06:57:59 -0800 (PST)
(envelope-from dcs@newsguy.com)
Received: from newsguy.com by peach.ocn.ne.jp (8.9.1a/OCN) id XAA12510; Fri, 29 Jan 1999 23:52:17 +0900 (JST)
Message-ID: <36B1CABD.BCC90EC7@newsguy.com>
Date: Fri, 29 Jan 1999 23:50:37 +0900
From: "Daniel C. Sobral" <dcs@newsguy.com>
X-Mailer: Mozilla 4.5 [en] (Win98; I)
X-Accept-Language: pt-BR,ja
MIME-Version: 1.0
To: Sheldon Hearn <axl@iafrica.com>
CC: Poul-Henning Kamp <phk@critter.freebsd.dk>,
Mikhail Teterin <mi@kot.ne.mediaone.net>, current@FreeBSD.ORG
Subject: Re: btokup().. patch to STYLE(9) (fwd)
References: <90073.917600532@axl.noc.iafrica.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
Sheldon Hearn wrote:
>
> I didn't have a problem reading the sentence, even though you left out
> required commas. The only thing that caused a problem was your use of
> split infinitive. ;-)
Split infinitive is a urban legend. It has *never* been outlawed in
the english language, except for some crazy people in this century
and, I think, later last century.
In fact, when I learned this I saw some interesting examples of very
unreadable text because of lack of split infinitive. :-)
--
Daniel C. Sobral (8-DCS)
dcs@newsguy.com
Would you mind not shooting at the thermonuclear weapons?
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Fri Jan 29 07:22:16 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id HAA26656
for freebsd-current-outgoing; Fri, 29 Jan 1999 07:22:16 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from ns.tar.com (ns.tar.com [204.95.187.2])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA26649
for <current@FreeBSD.ORG>; Fri, 29 Jan 1999 07:22:14 -0800 (PST)
(envelope-from dick@ns.tar.com)
Received: (from dick@localhost)
by ns.tar.com (8.9.2/8.9.1) id JAA22708;
Fri, 29 Jan 1999 09:22:02 -0600 (CST)
(envelope-from dick)
Date: Fri, 29 Jan 1999 09:22:02 -0600
From: "Richard Seaman, Jr." <dick@tar.com>
To: Matthew Dillon <dillon@apollo.backplane.com>
Cc: HighWind Software Information <info@highwind.com>, current@FreeBSD.ORG
Subject: Re: Locked at 100% User CPU
Message-ID: <19990129092202.T421@tar.com>
References: <199901282130.QAA13214@highwind.com> <199901290010.QAA11960@apollo.backplane.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.95i
In-Reply-To: <199901290010.QAA11960@apollo.backplane.com>; from Matthew Dillon on Thu, Jan 28, 1999 at 04:10:26PM -0800
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
On Thu, Jan 28, 1999 at 04:10:26PM -0800, Matthew Dillon wrote:
> :In libc_r, I don't think the code in uthread_kern.c's
> :_thread_kern_select() scales at all.
> :
> :As the number of network connections (TCP) to my application grows, I
> :believe this routine takes longer and longer and my CPU goes to 100%
> :user space.
> :
> :Something makes me believe that this routine has an n^2 (or worse)
> :problem. Seems to relate to the number of fd's to select() on. At
> :about 300-400, even a P2 400Mhz gets max'd out and gets nothing done.
> :
> :Anybody have a feeling as to what is wrong here?
> :
> :-Rob
>
> This code looks pretty bad, all right. It looks like it is O(N^2)
> in PS_SELECT_WAIT(), especially if descriptors get randomly strewn
> amoungst the threads. It also looks like it is regenerating the FDS masks
> on each call completely from scratch. It also looks like it is
> scanning the entire thread list - both waiting and running threads,
> to prioritize the next thread to run and then scanning it again
> to select the thread priority, then scanning the whole list yet
> again to find the one it wants to run.
>
> This is massively unscaleable code. Is anyone actively working on
> it?
The uthread code does not scale well, nor perform particularly well.
I have demonstration code that suggests a 1-1 kernel threads
implemention can create threads 5-20 times faster than the uthread
code. It can do context switches (even without any fds open) from
2-3 times faster (just a few threads) to 15-20 times faster (~100
threads) to 200+ times faster (~1000 threads).
Don't know if anyone is working on uthreads. IMO rather than trying to
fix the uthread code, which would be a significant project, it would
be better to convert it to a N:M kernel thread implementation. It
wouldn't be all that much more work than getting the user thread
code in first rate shape. But, either way I think its a fairly
big project.
--
Richard Seaman, Jr. email: dick@tar.com
5182 N. Maple Lane phone: 414-367-5450
Chenequa WI 53058 fax: 414-367-5852
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Fri Jan 29 07:24:30 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id HAA26944
for freebsd-current-outgoing; Fri, 29 Jan 1999 07:24:30 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from ns.mt.sri.com (sri-gw.MT.net [206.127.105.141])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA26929
for <current@FreeBSD.ORG>; Fri, 29 Jan 1999 07:24:26 -0800 (PST)
(envelope-from nate@mt.sri.com)
Received: from mt.sri.com (rocky.mt.sri.com [206.127.76.100])
by ns.mt.sri.com (8.8.8/8.8.8) with SMTP id IAA26063;
Fri, 29 Jan 1999 08:24:21 -0700 (MST)
(envelope-from nate@rocky.mt.sri.com)
Received: by mt.sri.com (SMI-8.6/SMI-SVR4)
id IAA06015; Fri, 29 Jan 1999 08:24:20 -0700
Date: Fri, 29 Jan 1999 08:24:20 -0700
Message-Id: <199901291524.IAA06015@mt.sri.com>
From: Nate Williams <nate@mt.sri.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
To: Christopher Masto <chris@netmonger.net>
Cc: current@FreeBSD.ORG
Subject: Re: btokup().. patch to STYLE(9) (fwd)
In-Reply-To: <19990129004749.A8899@netmonger.net>
References: <199901290326.OAA22743@godzilla.zeta.org.au>
<19990128230223.A1973@netmonger.net>
<199901290439.VAA03999@mt.sri.com>
<19990129004749.A8899@netmonger.net>
X-Mailer: VM 6.34 under 19.16 "Lille" XEmacs Lucid
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
> As for noise, there are situations where excess punctuation is just
> noise, and there are situations that benefit from more than the bare
> minumum of decorations. Anyone doing kernel programming ought to know
> the difference.....
And that is where we disagree. Style is religion, and one man's 'too
much' is another's 'too little'. Obviously what you think is a minimum
is different than what I think from the conversation, so is your way
'more right' than me. Because 'consistency' is the most import
'readability' factor in source code (MHO), keeping it consistant is most
important in large software projects. I've seen what happens when
everyone uses their own style, and it doesn't work.
By making it obvious (as Style does) where the line is, there is no room
for ambiguity.
Nate
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Fri Jan 29 07:30:46 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id HAA27571
for freebsd-current-outgoing; Fri, 29 Jan 1999 07:30:46 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from ns.mt.sri.com (sri-gw.MT.net [206.127.105.141])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA27566
for <current@FreeBSD.ORG>; Fri, 29 Jan 1999 07:30:43 -0800 (PST)
(envelope-from nate@mt.sri.com)
Received: from mt.sri.com (rocky.mt.sri.com [206.127.76.100])
by ns.mt.sri.com (8.8.8/8.8.8) with SMTP id IAA26107;
Fri, 29 Jan 1999 08:30:33 -0700 (MST)
(envelope-from nate@rocky.mt.sri.com)
Received: by mt.sri.com (SMI-8.6/SMI-SVR4)
id IAA06052; Fri, 29 Jan 1999 08:30:31 -0700
Date: Fri, 29 Jan 1999 08:30:31 -0700
Message-Id: <199901291530.IAA06052@mt.sri.com>
From: Nate Williams <nate@mt.sri.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
To: "Jordan K. Hubbard" <jkh@zippy.cdrom.com>
Cc: Warner Losh <imp@village.org>, Julian Elischer <julian@whistle.com>,
current@FreeBSD.ORG
Subject: Re: btokup().. patch to STYLE(9) (fwd)
In-Reply-To: <6928.917597124@zippy.cdrom.com>
References: <199901290435.VAA62940@harmony.village.org>
<6928.917597124@zippy.cdrom.com>
X-Mailer: VM 6.34 under 19.16 "Lille" XEmacs Lucid
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
> > Unless things have changed a lot, bde counts 50x most people. This
> > isn't a democracy.
>
> It may not be a democracy, but it's also not a monarchy. :-)
...
> Bruce only gets "50x the vote" on occasion by generally being the only
> one to comment at all.
Bruce should get 50X the vote since he's the only one willing to enforce
the rules. Without Bruce the code would become inconsistant. By
over-ruling we are essentially
Most of the commits made by other developers (except a few, David being
one of the exceptions) do not follow Style anyway, and at least Bruce
attempts to keep them consistant with the rest of the tree.
My fear is that we'll end up with '?*+'BSD now.
Nate
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Fri Jan 29 08:03:09 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id IAA01790
for freebsd-current-outgoing; Fri, 29 Jan 1999 08:03:09 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from janus.syracuse.net (janus.syracuse.net [205.232.47.15])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA01784
for <current@FreeBSD.ORG>; Fri, 29 Jan 1999 08:03:06 -0800 (PST)
(envelope-from green@unixhelp.org)
Received: from localhost (green@localhost)
by janus.syracuse.net (8.8.8/8.8.7) with ESMTP id LAA20216;
Fri, 29 Jan 1999 11:03:01 -0500 (EST)
Date: Fri, 29 Jan 1999 11:03:01 -0500 (EST)
From: Brian Feldman <green@unixhelp.org>
X-Sender: green@janus.syracuse.net
To: Nate Williams <nate@mt.sri.com>
cc: Archie Cobbs <archie@whistle.com>, Julian Elischer <julian@whistle.com>,
current@FreeBSD.ORG
Subject: Re: btokup().. patch to STYLE(9) (fwd)
In-Reply-To: <199901290038.RAA02885@mt.sri.com>
Message-ID: <Pine.BSF.4.05.9901291100260.19390-100000@janus.syracuse.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
On Thu, 28 Jan 1999, Nate Williams wrote:
> > > Some people when confronted by people wanting to have extra braces
> > > say "change style(9)".
> > >
> > > Well, here is my change..
> >
> > You can count my vote.
> >
> > I would also add a paragraph like this:
> >
> > If possible code should complile cleanly with gcc's -Wall flag.
> > Note however that this does not imply that it's OK to eliminate
> > warnings simply by covering them up with typecasts, etc., as that
> > actually does more harm than good.
> >
> > I hope that wording is sufficiently unoffensive to the -Wall haters.
>
> '-Wall haters'. That almost sounds like 'Wall-flowers' or something. :)
>
> Agreed, but that's not the only reason I dislike '-Wall'. The other
> reason is that some of the warnings enabled in -Wall are purely
> stylistic, and are not even warnings.
>
> Making all software compile quietly with gcc -Wall means complying with
> what the GNU folks thinks is the correct 'style' of writing software,
> rather than having style issues ignored. In other words, you end up
> making change change for the sake of change, which is silly just to
> please the compiler.
>
> But, after the recent flame fiasco I'm not saying anything more.
>
I for one like the warning
do {foo();} while(bar=baz());
that shows up, saying parentheses should be used. YES, this is a style thing,
BUT if you use the extra parentheses and know what it means, you know that
the author meant
do {foo();} while((bar=baz())!=0);
instead of
do {foo();} while(bar==baz());
This is just one of the cases in which I agree with the "style" comments/
warnings in GCC -Wall.
>
> Nate
>
> To Unsubscribe: send mail to majordomo@FreeBSD.org
> with "unsubscribe freebsd-current" in the body of the message
>
Brian Feldman _ __ ___ ___ ___
green@unixhelp.org _ __ ___ | _ ) __| \
http://www.freebsd.org/ _ __ ___ ____ | _ \__ \ |) |
FreeBSD: The Power to Serve! _ __ ___ ____ _____ |___/___/___/
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Fri Jan 29 08:09:22 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id IAA02723
for freebsd-current-outgoing; Fri, 29 Jan 1999 08:09:22 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from fgw.netvalue.fr (fgw.netvalue.fr [194.2.38.194])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA02709
for <freebsd-current@FreeBSD.ORG>; Fri, 29 Jan 1999 08:09:18 -0800 (PST)
(envelope-from erwan@netvalue.fr)
Received: by fgw.netvalue.fr; id RAA29950; Fri, 29 Jan 1999 17:20:58 +0100 (CET)
Received: from etoile.netvalue.fr(192.168.1.11) by fgw.netvalue.fr via smap (3.0)
id xma029938; Fri, 29 Jan 99 17:20:46 +0100
Received: from netvalue.fr ([192.168.1.100]) by etoile.netvalue.fr
(Netscape Messaging Server 3.5) with ESMTP id AAA59F4;
Fri, 29 Jan 1999 17:08:19 +0100
Message-ID: <36B1DCB9.8FB42BA4@netvalue.fr>
Date: Fri, 29 Jan 1999 17:07:22 +0100
From: Erwan Arzur <erwan@netvalue.fr>
Organization: NetValue S.A.
X-Mailer: Mozilla 4.5 [en] (X11; I; FreeBSD 4.0-CURRENT i386)
X-Accept-Language: en
MIME-Version: 1.0
To: obrien@NUXI.com
CC: Mike Smith <mike@smith.net.au>, Ustimenko Semen <semen@iclub.nsu.ru>,
freebsd-current@FreeBSD.ORG
Subject: Re: About to commit NTFS driver
References: <Pine.BSF.3.96.990128024451.49866B-100000@iclub.nsu.ru> <199901290050.QAA01195@dingo.cdrom.com> <19990128235511.A24267@relay.nuxi.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
David O'Brien wrote:
> > > Driver is readonly, specialy developed for freebsd,
> > > supports most of NTFS's features.
> > > Source is at http://iclub.nsu.ru/~semen/ntfs/
> >
> > Sounds like a good idea. Do you have a reviewer?
>
> I'm looking at it now for 4.0-C.
I'm quite sure it has already been corrected right now, but when
building against a fresh 4.0-current as of this morning, you have to
change the calls to getpbuf and relpbuf in ntfs_vnops.c ...
*** ntfs_vnops.c Thu Jan 28 04:56:06 1999
--- /sys/ntfs/ntfs_vnops.c Fri Jan 29 16:31:16 1999
***************
*** 126,132 ****
* We use only the kva address for the buffer, but this is
extremely
* convienient and fast.
*/
! bp = getpbuf();
npages = btoc(count);
kva = (vm_offset_t) bp->b_data;
--- 126,132 ----
* We use only the kva address for the buffer, but this is
extremely
* convienient and fast.
*/
! bp = getpbuf(NULL);
npages = btoc(count);
kva = (vm_offset_t) bp->b_data;
***************
*** 145,151 ****
error = VOP_READ(vp, &uio, 0, cred);
pmap_qremove(kva, npages);
! relpbuf(bp);
if (error && (uio.uio_resid == count))
return VM_PAGER_ERROR;
--- 145,151 ----
error = VOP_READ(vp, &uio, 0, cred);
pmap_qremove(kva, npages);
! relpbuf(bp,NULL);
if (error && (uio.uio_resid == count))
return VM_PAGER_ERROR;
This allows the module to compile and it also runs well :
/dev/wd0s6 on /ntfs/disk_f (local)
/dev/wd0s7 on /ntfs/disk_g (local)
Considering the comments in vm_page.c where these functions are defined,
this may need some investigation (can't do this by myself, i get
confused with everything that starts with "vm", especially on FreeBSD
:-))
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Fri Jan 29 08:14:29 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id IAA03317
for freebsd-current-outgoing; Fri, 29 Jan 1999 08:14:29 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from iclub.nsu.ru (iclub.nsu.ru [193.124.222.66])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA03300;
Fri, 29 Jan 1999 08:14:17 -0800 (PST)
(envelope-from semen@iclub.nsu.ru)
Received: from localhost (semen@localhost)
by iclub.nsu.ru (8.9.2/8.8.5) with SMTP id WAA22664;
Fri, 29 Jan 1999 22:12:52 +0600 (NS)
Date: Fri, 29 Jan 1999 22:12:52 +0600 (NS)
From: Ustimenko Semen <semen@iclub.nsu.ru>
To: Mike Smith <mike@smith.net.au>
cc: freebsd-current@FreeBSD.ORG, obrien@FreeBSD.ORG
Subject: Re: About to commit NTFS driver
In-Reply-To: <199901290050.QAA01195@dingo.cdrom.com>
Message-ID: <Pine.BSF.3.96.990129220714.22530D-100000@iclub.nsu.ru>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
On Thu, 28 Jan 1999, Mike Smith wrote:
> >
> > Are there any disagrees with an idea to commit a NTFS
> > driver into current:
> >
> > I can commit/maintain driver mentioned at
> > http://www.freebsd.org/projects/
> >
> > Driver is readonly, specialy developed for freebsd,
> > supports most of NTFS's features.
> > Source is at http://iclub.nsu.ru/~semen/ntfs/
>
> Sounds like a good idea. Do you have a reviewer?
>
Looks like not. David O'Brien have just showed me points
to fix. May be he will be?
He also noticed, that it doesn't work under 4.0-current,
so it will take more time.
P.S. What about writing on NTFS volume, i think we can do
it, but without logging, as NT does.
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Fri Jan 29 08:23:12 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id IAA04113
for freebsd-current-outgoing; Fri, 29 Jan 1999 08:23:12 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from alpha.xerox.com (alpha.Xerox.COM [13.1.64.93])
by hub.freebsd.org (8.8.8/8.8.8) with SMTP id IAA04106
for <current@FreeBSD.ORG>; Fri, 29 Jan 1999 08:23:08 -0800 (PST)
(envelope-from fenner@parc.xerox.com)
Received: from mango.parc.xerox.com ([13.1.102.232]) by alpha.xerox.com with SMTP id <52491(4)>; Fri, 29 Jan 1999 08:23:01 PST
Received: from mango.parc.xerox.com (localhost.parc.xerox.com [127.0.0.1])
by mango.parc.xerox.com (8.8.8/8.8.8) with ESMTP id IAA12797;
Fri, 29 Jan 1999 08:22:38 -0800 (PST)
(envelope-from fenner@mango.parc.xerox.com)
Message-Id: <199901291622.IAA12797@mango.parc.xerox.com>
To: "Andrey A. Chernov" <ache@nagual.pp.ru>
cc: current@FreeBSD.ORG
Subject: Re: panic: soaccept: !NOFDREF
In-reply-to: Your message of "Thu, 28 Jan 1999 23:37:58 PST."
<19990129103757.A410@nagual.pp.ru>
Date: Fri, 29 Jan 1999 08:22:38 PST
From: Bill Fenner <fenner@parc.xerox.com>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
In message <19990129103757.A410@nagual.pp.ru>you write:
>I saw it several times with very recent -current
Is your machine getting a lot of incoming connections? I'd like to
try to replicate this. If it's a problem for you you can try
reverting rev 1.52 of /sys/kern/uipc_socket.c .
Thanks,
Bill
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Fri Jan 29 08:29:46 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id IAA05093
for freebsd-current-outgoing; Fri, 29 Jan 1999 08:29:46 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from janus.syracuse.net (janus.syracuse.net [205.232.47.15])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA05086
for <current@FreeBSD.ORG>; Fri, 29 Jan 1999 08:29:44 -0800 (PST)
(envelope-from green@unixhelp.org)
Received: from localhost (green@localhost)
by janus.syracuse.net (8.8.8/8.8.7) with ESMTP id LAA21532;
Fri, 29 Jan 1999 11:29:29 -0500 (EST)
Date: Fri, 29 Jan 1999 11:29:29 -0500 (EST)
From: Brian Feldman <green@unixhelp.org>
X-Sender: green@janus.syracuse.net
To: Christopher Masto <chris@netmonger.net>
cc: current@FreeBSD.ORG
Subject: Re: btokup().. patch to STYLE(9) (fwd)
In-Reply-To: <19990129004749.A8899@netmonger.net>
Message-ID: <Pine.BSF.4.05.9901291128380.21302-100000@janus.syracuse.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
I seem to remember there once was a comment in a well-known body of code, which
went something like:
"You are not supposed to understand this."
Brian Feldman _ __ ___ ___ ___
green@unixhelp.org _ __ ___ | _ ) __| \
http://www.freebsd.org/ _ __ ___ ____ | _ \__ \ |) |
FreeBSD: The Power to Serve! _ __ ___ ____ _____ |___/___/___/
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Fri Jan 29 08:33:49 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id IAA05723
for freebsd-current-outgoing; Fri, 29 Jan 1999 08:33:49 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from rover.village.org (rover.village.org [204.144.255.49])
by hub.freebsd.org (8.8.8/8.8.8) with SMTP id IAA05713
for <current@freebsd.org>; Fri, 29 Jan 1999 08:33:45 -0800 (PST)
(envelope-from imp@village.org)
Received: from harmony [10.0.0.6]
by rover.village.org with esmtp (Exim 1.71 #1)
id 106GUe-00066f-00; Fri, 29 Jan 1999 09:10:04 -0700
Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.1/8.8.3) with ESMTP id JAA66178; Fri, 29 Jan 1999 09:08:54 -0700 (MST)
Message-Id: <199901291608.JAA66178@harmony.village.org>
To: Andrew Kenneth Milton <akm@zeus.theinternet.com.au>
Subject: Re: btokup().. patch to STYLE(9) (fwd)
Cc: current@FreeBSD.ORG
In-reply-to: Your message of "Fri, 29 Jan 1999 21:21:55 +1000."
<199901291121.VAA01208@zeus.theinternet.com.au>
References: <199901291121.VAA01208@zeus.theinternet.com.au>
Date: Fri, 29 Jan 1999 09:08:54 -0700
From: Warner Losh <imp@village.org>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
In message <199901291121.VAA01208@zeus.theinternet.com.au> Andrew Kenneth Milton writes:
: The only arguments I've seen for less 'punctuation' are
:
: a) "I" don't need them
: b) "I" don't like what it looks like with them
: c) There might be bugs introduced due to parens.
:
: Well a and b are crap, and c is no worse off than we are now, since
: there seems to be bugs caused by a lack of them.
A and B aren't crap.
Style(9) should allow extra parens in very complex situations, but
still prohibit them in innane ones:
if ((a < 0) && (b < 0))
should be prohibited since the designers of C anticipated this and
made
if (a < 0 && b < 0)
do the right thing. The latter is easier on the eyes and uses the 80
columns better.
I do agree that complex things like:
if (a | b & c % d ^ e)
should really have some parents to show what is going on.
So I agree with phk on this one: Use fewer parens generally, but use
common sense in adding them in the more obscure cases where they do
legitimately add readability.
Warner
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Fri Jan 29 08:33:56 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id IAA05738
for freebsd-current-outgoing; Fri, 29 Jan 1999 08:33:56 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from rover.village.org (rover.village.org [204.144.255.49])
by hub.freebsd.org (8.8.8/8.8.8) with SMTP id IAA05733
for <current@freebsd.org>; Fri, 29 Jan 1999 08:33:51 -0800 (PST)
(envelope-from imp@village.org)
Received: from harmony [10.0.0.6]
by rover.village.org with esmtp (Exim 1.71 #1)
id 106GaG-00066n-00; Fri, 29 Jan 1999 09:15:52 -0700
Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.1/8.8.3) with ESMTP id JAA66196; Fri, 29 Jan 1999 09:15:57 -0700 (MST)
Message-Id: <199901291615.JAA66196@harmony.village.org>
To: Nate Williams <nate@mt.sri.com>
Subject: Re: btokup().. patch to STYLE(9) (fwd)
Cc: current@FreeBSD.ORG
In-reply-to: Your message of "Fri, 29 Jan 1999 08:30:31 MST."
<199901291530.IAA06052@mt.sri.com>
References: <199901291530.IAA06052@mt.sri.com> <199901290435.VAA62940@harmony.village.org> <6928.917597124@zippy.cdrom.com>
Date: Fri, 29 Jan 1999 09:15:57 -0700
From: Warner Losh <imp@village.org>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
In message <199901291530.IAA06052@mt.sri.com> Nate Williams writes:
: Bruce should get 50X the vote since he's the only one willing to enforce
: the rules. Without Bruce the code would become inconsistant. By
: over-ruling we are essentially
Essentially what?
I appreciate the work that bruce has done to make things more
consistant. I think that we should listen to him when it comes to
matters of style since he has earned, through long hours of hard work,
the right to say something about style since he's been doing something
about stlye for at least as long as I've been a comitter. When I
venture into a new area (say man pages or make files), he ensures that
things stay ordered and consistant accross the source base. He should
continue to do so, if he so chooses, imho. Makes the source base much
easier to deal with.
Once a consensus is reached, I believe that bde will adjust to that
new consensus. The trouble is that no matter what the standards are,
people will inconsistantly apply them, and bde has very sharp eyes for
that.
Warner
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Fri Jan 29 08:40:44 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id IAA06459
for freebsd-current-outgoing; Fri, 29 Jan 1999 08:40:44 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from roma.coe.ufrj.br (roma.coe.ufrj.br [146.164.53.65])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA06453;
Fri, 29 Jan 1999 08:40:37 -0800 (PST)
(envelope-from jonny@jonny.eng.br)
Received: (from jonny@localhost)
by roma.coe.ufrj.br (8.8.8/8.8.8) id OAA15306;
Fri, 29 Jan 1999 14:40:30 -0200 (EDT)
(envelope-from jonny)
From: Joao Carlos Mendes Luis <jonny@jonny.eng.br>
Message-Id: <199901291640.OAA15306@roma.coe.ufrj.br>
Subject: Re: The future of a.out support?
In-Reply-To: <199901291206.EAA73205@silvia.hip.berkeley.edu> from Satoshi Asami at "Jan 29, 1999 4: 6:32 am"
To: asami@FreeBSD.ORG (Satoshi Asami)
Date: Fri, 29 Jan 1999 14:40:30 -0200 (EDT)
Cc: dg@root.com, grog@lemis.com, FreeBSD-current@FreeBSD.ORG
X-Mailer: ELM [version 2.4ME+ PL43 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
#define quoting(Satoshi Asami)
// That sounds fine. However, there are still people stuck with a.out
// libraries out there (netscape comes to mind). Is the 3.1R installer
// going to include a.out libraries as an option?
Please, please...
compat22 would be a historical name. :)
Jonny
--
Joao Carlos Mendes Luis M.Sc. Student
jonny@jonny.eng.br Universidade Federal do Rio de Janeiro
"This .sig is not meant to be politically correct."
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Fri Jan 29 08:50:48 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id IAA08078
for freebsd-current-outgoing; Fri, 29 Jan 1999 08:50:48 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from nagual.pp.ru (nagual.pp.ru [193.125.27.73])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA08069
for <current@FreeBSD.ORG>; Fri, 29 Jan 1999 08:50:43 -0800 (PST)
(envelope-from ache@nagual.pp.ru)
Received: (from ache@localhost)
by nagual.pp.ru (8.9.2/8.9.2) id TAA11299;
Fri, 29 Jan 1999 19:50:35 +0300 (MSK)
(envelope-from ache)
Date: Fri, 29 Jan 1999 19:50:35 +0300
From: "Andrey A. Chernov" <ache@nagual.pp.ru>
To: Bill Fenner <fenner@parc.xerox.com>
Cc: current@FreeBSD.ORG
Subject: Re: panic: soaccept: !NOFDREF
Message-ID: <19990129195034.A5288@nagual.pp.ru>
References: <19990129103757.A410@nagual.pp.ru> <199901291622.IAA12797@mango.parc.xerox.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.95.1i
In-Reply-To: <199901291622.IAA12797@mango.parc.xerox.com>; from fenner@parc.xerox.com on Fri, Jan 29, 1999 at 08:22:38AM -0800
Organization: Biomechanoid
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
On Fri, Jan 29, 1999 at 08:22:38AM -0800, Bill Fenner wrote:
> Is your machine getting a lot of incoming connections? I'd like to
Yes.
> try to replicate this. If it's a problem for you you can try
> reverting rev 1.52 of /sys/kern/uipc_socket.c .
Ok, I'll revert back for a while and wait for your fix.
--
Andrey A. Chernov
ache@null.net
MTH/SH/HE S-- W-- N+ PEC>+ D A a++ C G>+ QH+(++) 666+>++ Y
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Fri Jan 29 09:18:34 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id JAA11398
for freebsd-current-outgoing; Fri, 29 Jan 1999 09:18:34 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA11393
for <current@FreeBSD.ORG>; Fri, 29 Jan 1999 09:18:32 -0800 (PST)
(envelope-from julian@whistle.com)
Received: (from daemon@localhost)
by alpo.whistle.com (8.8.5/8.8.5) id JAA15439;
Fri, 29 Jan 1999 09:10:13 -0800 (PST)
Received: from s204m82.isp.whistle.com(207.76.204.82)
via SMTP by alpo.whistle.com, id smtpdD15412; Fri Jan 29 17:10:03 1999
Date: Fri, 29 Jan 1999 09:09:54 -0800 (PST)
From: Julian Elischer <julian@whistle.com>
X-Sender: julian@s204m82.isp.whistle.com
To: Sheldon Hearn <axl@iafrica.com>
cc: Poul-Henning Kamp <phk@critter.freebsd.dk>,
Mikhail Teterin <mi@kot.ne.mediaone.net>, current@FreeBSD.ORG
Subject: Re: btokup().. patch to STYLE(9) (fwd)
In-Reply-To: <90073.917600532@axl.noc.iafrica.com>
Message-ID: <Pine.BSF.4.05.9901290900370.304-100000@s204m82.isp.whistle.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
On Fri, 29 Jan 1999, Sheldon Hearn wrote:
>
> When it comes to code, do you not agree that the trained eye knows which
> operators to seek to first in an expression? I can't think of an analogy
> in the English language, since one doesn't "seek to" commas, one simply
> reads from left to right.
>
The "trained eye" doesn't have much to do with the problem..
Firstly there are only a certain number of things the average person can
keep in context at a time, and forcing someone to work out precedence
is distracting from the job at hand. I've been doing C for 17 years now,
and there are some operators that I Still need to look up because I use
them rarely in combination. Also writing in an ISO 9000 environmemt,
Braces were REQUIRED, as were Parans wherever more than 2 elements
were in an expression (except in some simple cases like a + b + c + d).
Having worked in that environment I find the that I get REALLY distracted
by the LACK of parens and braces in expressions with more than 2 parts
because I keep having to check every expression to see what was actually
done, where with parans and braces it's explicit. Arguing against parens
and braces is like arguing against indentation. It's not required but...
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Fri Jan 29 09:21:13 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id JAA12014
for freebsd-current-outgoing; Fri, 29 Jan 1999 09:21:13 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA12009
for <current@FreeBSD.ORG>; Fri, 29 Jan 1999 09:21:12 -0800 (PST)
(envelope-from julian@whistle.com)
Received: (from daemon@localhost)
by alpo.whistle.com (8.8.5/8.8.5) id JAA15719;
Fri, 29 Jan 1999 09:16:54 -0800 (PST)
Received: from s204m82.isp.whistle.com(207.76.204.82)
via SMTP by alpo.whistle.com, id smtpdq15712; Fri Jan 29 17:16:49 1999
Date: Fri, 29 Jan 1999 09:16:46 -0800 (PST)
From: Julian Elischer <julian@whistle.com>
X-Sender: julian@s204m82.isp.whistle.com
To: Sheldon Hearn <axl@iafrica.com>
cc: Greg Lehey <grog@lemis.com>, current@FreeBSD.ORG
Subject: Re: btokup().. patch to STYLE(9) (fwd)
In-Reply-To: <92584.917604304@axl.noc.iafrica.com>
Message-ID: <Pine.BSF.4.05.9901290914500.304-100000@s204m82.isp.whistle.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
On Fri, 29 Jan 1999, Sheldon Hearn wrote:
>
> Giving folks the go-ahead to use parens as a form of documentation is
> misguided and will end in tears. MHO.
>
Giving people the ability to quickly prove that the code matches the
comments when they're upto their behinds in alligators is not going to end
in tears. Sometimes there are more important things to worry about than
proving one'es programming studdliness.
julian
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Fri Jan 29 09:28:24 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id JAA12826
for freebsd-current-outgoing; Fri, 29 Jan 1999 09:28:24 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from post.mail.demon.net (finch-post-10.mail.demon.net [194.217.242.38])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA12806
for <current@freebsd.org>; Fri, 29 Jan 1999 09:28:20 -0800 (PST)
(envelope-from bsdcurrent@scratch.demon.co.uk)
Received: from [212.228.22.156] (helo=scratch.demon.co.uk)
by post.mail.demon.net with smtp (Exim 2.11 #1)
id 106HiH-0003Yq-00
for current@FreeBSD.ORG; Fri, 29 Jan 1999 17:28:16 +0000
Message-ID: <9q$ZtHAN9es2EwEW@scratch.demon.co.uk>
Date: Fri, 29 Jan 1999 17:26:37 +0000
To: current@FreeBSD.ORG
From: Tim Preece <bsdcurrent@scratch.demon.co.uk>
Subject: Telnet and NIS queries
MIME-Version: 1.0
X-Mailer: Turnpike (32) Version 4.00 <2bL8TQCIEWg0B+1EtXWvseZtDP>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
Hi,
I am having a few problems with my v.small network.
I have 2 boxes both pc's, one running FreeBSD nearly current (Updated
begin Jan) and the other running 3.0 release.
Firstly I was able to telnet to 127.0.0.1 and log in as root, however
now even this seems to be causing problems the same as if I try to
telnet to the other box and log in as root.
This is the message that I get
scratch2 login: LOGIN root REFUSED (NOROOT) from scratch1.netlink on TTY
ttyp0
The other problem is that I am having problems with networked accounts,
unable to log on as anything from one machine except that which was
created on it
Don't know if this is anything to do with it but I get this message
scratch1 login: LOGIN FAILURE from scratch1.netlink
repeat
repeat
scratch login: NIS netgroup support not configured
reading about netgroup and creating /etc/netgroup with only + in it
and re-make the yp Makefile does not produce netgrp.byname etc
Do I need netgroup and if so what am I doing wrong, Is this a problem
with having ELF on one box and aout on the other !!!!!
any help much appreciated
Thanks
--
Tim Preece
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Fri Jan 29 09:52:12 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id JAA17403
for freebsd-current-outgoing; Fri, 29 Jan 1999 09:52:12 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA17397
for <current@FreeBSD.ORG>; Fri, 29 Jan 1999 09:52:10 -0800 (PST)
(envelope-from julian@whistle.com)
Received: (from daemon@localhost)
by alpo.whistle.com (8.8.5/8.8.5) id JAA16805;
Fri, 29 Jan 1999 09:48:25 -0800 (PST)
Received: from s204m82.isp.whistle.com(207.76.204.82)
via SMTP by alpo.whistle.com, id smtpdg16800; Fri Jan 29 17:48:22 1999
Date: Fri, 29 Jan 1999 09:48:19 -0800 (PST)
From: Julian Elischer <julian@whistle.com>
X-Sender: julian@s204m82.isp.whistle.com
To: Warner Losh <imp@village.org>
cc: Andrew Kenneth Milton <akm@zeus.theinternet.com.au>, current@FreeBSD.ORG
Subject: Re: btokup().. patch to STYLE(9) (fwd)
In-Reply-To: <199901291608.JAA66178@harmony.village.org>
Message-ID: <Pine.BSF.4.05.9901290941240.304-100000@s204m82.isp.whistle.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
On Fri, 29 Jan 1999, Warner Losh wrote:
>
> if ((a < 0) && (b < 0))
>
Personally while I KNOW (after wasting a second thinking about it) that
the example below is the same as that above, I ALWAYS code as above.
It takes me about 1/5th the time to know what it means.
> if (a < 0 && b < 0)
If I were working on this code written by someone else it'd leave my
editor looking like the top example, that's for sure. I think that
"How easy is it to edit a piece of code and still have it do what you
expect" is an important consideration, because people DO edit things.
>
>
> I do agree that complex things like:
>
> if (a | b & c % d ^ e)
>
> should really have some parents to show what is going on.
I have NO idea of what that is doing and I have plans of looking it up in
the book to work it out..
>
> So I agree with phk on this one: Use fewer parens generally, but use
> common sense in adding them in the more obscure cases where they do
> legitimately add readability.
OK so where is the line.. I find that in code I'm working on I have many
more
arens that you would like..
does that mean that I should be forced to take them out when I commit it
and therefore probably produce erorrs?
>
> Warner
>
> To Unsubscribe: send mail to majordomo@FreeBSD.org
> with "unsubscribe freebsd-current" in the body of the message
>
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Fri Jan 29 09:55:26 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id JAA17815
for freebsd-current-outgoing; Fri, 29 Jan 1999 09:55:26 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from ipt2.iptelecom.net.ua (ipt2.iptelecom.net.ua [195.123.29.2])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA17806
for <current@FreeBSD.ORG>; Fri, 29 Jan 1999 09:55:21 -0800 (PST)
(envelope-from sobomax@altavista.net)
Received: from vega.pfts.com (async2-03.iptelecom.net.ua [195.123.29.68])
by ipt2.iptelecom.net.ua (8.8.8/8.8.8) with ESMTP id TAA13867;
Fri, 29 Jan 1999 19:55:21 +0200 (EET)
(envelope-from sobomax@altavista.net)
Received: from altavista.net (big_brother [192.168.1.1])
by vega.pfts.com (8.9.2/8.9.1) with ESMTP id TAA05885;
Fri, 29 Jan 1999 19:54:24 +0200 (EET)
(envelope-from sobomax@altavista.net)
Message-ID: <36B1F5CF.C8D4D370@altavista.net>
Date: Fri, 29 Jan 1999 19:54:23 +0200
From: Maxim Sobolev <sobomax@altavista.net>
Organization: Vega International Capital
X-Mailer: Mozilla 4.5 [en] (WinNT; I)
X-Accept-Language: ru,en
MIME-Version: 1.0
To: Tim Preece <bsdcurrent@scratch.demon.co.uk>
CC: current@FreeBSD.ORG
Subject: Re: Telnet and NIS queries
References: <9q$ZtHAN9es2EwEW@scratch.demon.co.uk>
Content-Type: text/plain; charset=x-user-defined
Content-Transfer-Encoding: 8bit
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
Dear Tim,
Your "problem" with telnet session is very simple - by default FreeBSD
doesn't allow anybody to login as "root" through insecure connection (see
/etc/ttys). This can be changed by editing /etc/ttys to make Pseudo
terminals to be "secure" (hovewer it compromises the security, you need to
know what you are doing) or simply use ssh or su.
Sincerely,
Maxim
Tim Preece wrote:
> Hi,
>
> I am having a few problems with my v.small network.
>
> I have 2 boxes both pc's, one running FreeBSD nearly current (Updated
> begin Jan) and the other running 3.0 release.
>
> Firstly I was able to telnet to 127.0.0.1 and log in as root, however
> now even this seems to be causing problems the same as if I try to
> telnet to the other box and log in as root.
>
> This is the message that I get
>
> scratch2 login: LOGIN root REFUSED (NOROOT) from scratch1.netlink on TTY
> ttyp0
>
> The other problem is that I am having problems with networked accounts,
> unable to log on as anything from one machine except that which was
> created on it
>
> Don't know if this is anything to do with it but I get this message
>
> scratch1 login: LOGIN FAILURE from scratch1.netlink
> repeat
> repeat
> scratch login: NIS netgroup support not configured
>
> reading about netgroup and creating /etc/netgroup with only + in it
> and re-make the yp Makefile does not produce netgrp.byname etc
>
> Do I need netgroup and if so what am I doing wrong, Is this a problem
> with having ELF on one box and aout on the other !!!!!
>
> any help much appreciated
>
> Thanks
> --
> Tim Preece
>
> To Unsubscribe: send mail to majordomo@FreeBSD.org
> with "unsubscribe freebsd-current" in the body of the message
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Fri Jan 29 10:23:43 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id KAA21596
for freebsd-current-outgoing; Fri, 29 Jan 1999 10:23:43 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from rover.village.org (rover.village.org [204.144.255.49])
by hub.freebsd.org (8.8.8/8.8.8) with SMTP id KAA21585
for <current@freebsd.org>; Fri, 29 Jan 1999 10:23:37 -0800 (PST)
(envelope-from imp@village.org)
Received: from harmony [10.0.0.6]
by rover.village.org with esmtp (Exim 1.71 #1)
id 106IFf-0006EK-00; Fri, 29 Jan 1999 11:02:43 -0700
Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.1/8.8.3) with ESMTP id LAA67403; Fri, 29 Jan 1999 11:02:49 -0700 (MST)
Message-Id: <199901291802.LAA67403@harmony.village.org>
To: Julian Elischer <julian@whistle.com>
Subject: Re: btokup().. patch to STYLE(9) (fwd)
Cc: current@FreeBSD.ORG
In-reply-to: Your message of "Fri, 29 Jan 1999 09:48:19 PST."
<Pine.BSF.4.05.9901290941240.304-100000@s204m82.isp.whistle.com>
References: <Pine.BSF.4.05.9901290941240.304-100000@s204m82.isp.whistle.com>
Date: Fri, 29 Jan 1999 11:02:48 -0700
From: Warner Losh <imp@village.org>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
: If I were working on this code written by someone else it'd leave my
: editor looking like the top example, that's for sure. I think that
: "How easy is it to edit a piece of code and still have it do what you
: expect" is an important consideration, because people DO edit things.
Agreed.
: > I do agree that complex things like:
: >
: > if (a | b & c % d ^ e)
: >
: > should really have some parents to show what is going on.
:
: I have NO idea of what that is doing and I have plans of looking it up in
: the book to work it out..
Yes. I agree with that.
if (a | b & c % d ^ e)
should have been written as:
if (((a | (b & (c % d))) ^ e) != 0)
(then again, either way it is ugly code and should have comments).
: OK so where is the line.. I find that in code I'm working on I have many
: more
: arens that you would like..
: does that mean that I should be forced to take them out when I commit it
: and therefore probably produce erorrs?
No. Style(9), imho, is more a guide than a hard and fast thou shalt
in all cases. I don't think that you should do anything to increase
errors. I would say that if you are adding/editing code to a moudle,
you shouldn't go messing with what is there. If you are writing new
code, then do what will make the code most reliable. If you did
extensive testing with parens, think twice about removing (and vice
versa).
As a friend of mine put it: "You can't legislate common sense."
Warner
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Fri Jan 29 10:51:08 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id KAA24611
for freebsd-current-outgoing; Fri, 29 Jan 1999 10:51:08 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from highwind.com (hurricane.highwind.com [209.61.45.50])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA24606
for <current@FreeBSD.ORG>; Fri, 29 Jan 1999 10:51:06 -0800 (PST)
(envelope-from info@highwind.com)
Received: (from info@localhost)
by highwind.com (8.8.6/8.8.6) id NAA20468;
Fri, 29 Jan 1999 13:50:23 -0500 (EST)
Date: Fri, 29 Jan 1999 13:50:23 -0500 (EST)
Message-Id: <199901291850.NAA20468@highwind.com>
From: HighWind Software Information <info@highwind.com>
To: dick@tar.com
CC: dillon@apollo.backplane.com, current@FreeBSD.ORG
In-reply-to: <19990129092202.T421@tar.com> (dick@tar.com)
Subject: Re: Locked at 100% User CPU
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
> This code looks pretty bad, all right. It looks like it is O(N^2)
> in PS_SELECT_WAIT(), especially if descriptors get randomly strewn
> amoungst the threads. It also looks like it is regenerating the FDS masks
> on each call completely from scratch. It also looks like it is
> scanning the entire thread list - both waiting and running threads,
> to prioritize the next thread to run and then scanning it again
> to select the thread priority, then scanning the whole list yet
> again to find the one it wants to run.
>
> This is massively unscaleable code. Is anyone actively working on
> it?
I think if I knew exactly what this code was trying to do, I could
rewrite it. However, it is quite complex.
I'm tempted to look into Richard's stuff. However, this pthread stuff
is quite stable. (at least with a few minor tweaks). If this part
scaled a WHOLE LOT better, we'd probably be okay.
Richard: How "checked" in is your stuff? What does one have to do to
start using it? Kernel mods?
-Rob
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Fri Jan 29 10:59:06 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id KAA25851
for freebsd-current-outgoing; Fri, 29 Jan 1999 10:59:06 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from uni4nn.gn.iaf.nl (osmium.gn.iaf.nl [193.67.144.12])
by hub.freebsd.org (8.8.8/8.8.8) with SMTP id KAA25841;
Fri, 29 Jan 1999 10:58:59 -0800 (PST)
(envelope-from wilko@yedi.iaf.nl)
Received: by uni4nn.gn.iaf.nl with UUCP id AA23996
(5.67b/IDA-1.5); Fri, 29 Jan 1999 19:46:38 +0100
Received: (from wilko@localhost) by yedi.iaf.nl (8.8.8/8.6.12) id TAA01074; Fri, 29 Jan 1999 19:01:42 +0100 (CET)
From: Wilko Bulte <wilko@yedi.iaf.nl>
Message-Id: <199901291801.TAA01074@yedi.iaf.nl>
Subject: Re: make release - Party Time! (but not for the AXP)
In-Reply-To: <7197.917599209@zippy.cdrom.com> from "Jordan K. Hubbard" at "Jan 29, 99 00:40:09 am"
To: jkh@zippy.cdrom.com (Jordan K. Hubbard)
Date: Fri, 29 Jan 1999 19:01:42 +0100 (CET)
Cc: gpalmer@FreeBSD.ORG, freebsd-current@FreeBSD.ORG
X-Organisation: Private FreeBSD site - Arnhem, The Netherlands
X-Pgp-Info: PGP public key at 'finger wilko@freefall.freebsd.org'
X-Mailer: ELM [version 2.4ME+ PL38 (25)]
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
As Jordan K. Hubbard wrote...
> > Unfortunately the AXP is still hosed :(
>
> Hmmm. Let me look at this - I may have failed to adjust one of the
> constants for the AXP case.
Sidestepping a bit: will there be AXP specific CDROMs in the WC
CDROM distribution?
Wilko
_ ______________________________________________________________________
| / o / / _ Bulte email: wilko@yedi.iaf.nl
|/|/ / / /( (_) Arnhem, The Netherlands WWW : http://www.tcja.nl
______________________________________________ Powered by FreeBSD __________
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Fri Jan 29 11:56:02 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id LAA02887
for freebsd-current-outgoing; Fri, 29 Jan 1999 11:56:02 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from darkstar.psa.at (darkstar.psa.at [194.152.163.137])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA02862
for <current@freebsd.org>; Fri, 29 Jan 1999 11:55:55 -0800 (PST)
(envelope-from as@psa.at)
Received: from unet2-51.univie.ac.at ([131.130.232.51] helo=entropy.quake.at)
by darkstar.psa.at with esmtp (Exim 2.10 #2)
id 106K0k-0002eb-00
for current@freebsd.org; Fri, 29 Jan 1999 20:55:27 +0100
Received: from localhost ([127.0.0.1])
by entropy.quake.at with esmtp (Exim 2.10 #2)
id 1069Gt-000378-00
for current@freebsd.org; Fri, 29 Jan 1999 09:27:23 +0100
Date: Fri, 29 Jan 1999 09:27:23 +0100 (CET)
From: Alexander Sanda <as@psa.at>
X-Sender: root@darkstar.vmx
To: current@FreeBSD.ORG
Subject: First year of FreeBSD...
Message-ID: <Pine.BSF.4.05.9901281247180.520-100000@darkstar.vmx>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
[NOTE: this article has nothing technical, but since I assume most of
the developers are reading here, I'am posting this here.]
Tomorrow, I will "celebrate" my 1-year anniversary with FreeBSD.
When I started with fbsd, I wasn't exactly an Unix newbie. In fact, I
have been using Linux and other Unices on non-x86 platforms for years
before.
I started with a stable -RELEASE (like every newbie should) and since
this day, I have installed about 20 boxes (sure, not very much) with
fbsd. About half a year ago, I started to follow -current on my home
box.
Some of them were running linux before, some of them are completely
fresh systems. Most of those boxes are acting as typical Intra/Internet
servers, performing www, ftp, mail, news, smb and various other
services.
None of those boxes *ever* crashed or had to be taken down due to an OS
fault. None of them ever lost a single bit of data, because of an OS
failure. Nuff said, imho...
The reason for posting this here, is that I just want to say "thank you"
to all the people involved in this wonderful project. They really
deserve it and I can imagine that it is not always easy to be involved
in such a big project.
Beeing a software engineer (or developer) is not always an easy job (I
have been involved in software development for years, just on another
"level").
In my opinion, FreeBSD gets way to few attention, but - who knows -
perhaps this is a better situation than beeing hyped all the time.
--
# /AS/ http://privat.schlund.de/entropy/ #
# According to rumours, MS finally decided to delay the release of the #
# long-awaited Windows 2000 until the first quarter of 1901. -unknown #
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Fri Jan 29 12:00:05 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id MAA03408
for freebsd-current-outgoing; Fri, 29 Jan 1999 12:00:05 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA03386
for <freebsd-current@FreeBSD.ORG>; Fri, 29 Jan 1999 12:00:02 -0800 (PST)
(envelope-from dillon@apollo.backplane.com)
Received: (from dillon@localhost)
by apollo.backplane.com (8.9.2/8.9.1) id LAA80883;
Fri, 29 Jan 1999 11:59:44 -0800 (PST)
(envelope-from dillon)
Date: Fri, 29 Jan 1999 11:59:44 -0800 (PST)
From: Matthew Dillon <dillon@apollo.backplane.com>
Message-Id: <199901291959.LAA80883@apollo.backplane.com>
To: Erwan Arzur <erwan@netvalue.fr>
Cc: obrien@NUXI.com, Mike Smith <mike@smith.net.au>,
Ustimenko Semen <semen@iclub.nsu.ru>, freebsd-current@FreeBSD.ORG
Subject: Re: About to commit NTFS driver
References: <Pine.BSF.3.96.990128024451.49866B-100000@iclub.nsu.ru> <199901290050.QAA01195@dingo.cdrom.com> <19990128235511.A24267@relay.nuxi.com> <36B1DCB9.8FB42BA4@netvalue.fr>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
I should probably backport the getpbuf/relpbuf changes from -4.x to
-3.x so the drivers remain reasonably portable.
-Matt
Matthew Dillon
<dillon@backplane.com>
:
:I'm quite sure it has already been corrected right now, but when
:building against a fresh 4.0-current as of this morning, you have to
:change the calls to getpbuf and relpbuf in ntfs_vnops.c ...
:
:*** ntfs_vnops.c Thu Jan 28 04:56:06 1999
:--- /sys/ntfs/ntfs_vnops.c Fri Jan 29 16:31:16 1999
:***************
:*** 126,132 ****
: * We use only the kva address for the buffer, but this is
:extremely
: * convienient and fast.
: */
:! bp = getpbuf();
:
: npages = btoc(count);
: kva = (vm_offset_t) bp->b_data;
:--- 126,132 ----
: * We use only the kva address for the buffer, but this is
:extremely
: * convienient and fast.
: */
:! bp = getpbuf(NULL);
:
: npages = btoc(count);
: kva = (vm_offset_t) bp->b_data;
:***************
:*** 145,151 ****
: error = VOP_READ(vp, &uio, 0, cred);
: pmap_qremove(kva, npages);
:
:! relpbuf(bp);
:
: if (error && (uio.uio_resid == count))
: return VM_PAGER_ERROR;
:--- 145,151 ----
: error = VOP_READ(vp, &uio, 0, cred);
: pmap_qremove(kva, npages);
:
:! relpbuf(bp,NULL);
:
: if (error && (uio.uio_resid == count))
: return VM_PAGER_ERROR;
:
:This allows the module to compile and it also runs well :
:/dev/wd0s6 on /ntfs/disk_f (local)
:/dev/wd0s7 on /ntfs/disk_g (local)
:
:Considering the comments in vm_page.c where these functions are defined,
:this may need some investigation (can't do this by myself, i get
:confused with everything that starts with "vm", especially on FreeBSD
::-))
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Fri Jan 29 12:06:05 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id MAA04224
for freebsd-current-outgoing; Fri, 29 Jan 1999 12:06:05 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from octopus.originative.co.uk (originat.demon.co.uk [158.152.220.9])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA04159
for <current@FreeBSD.ORG>; Fri, 29 Jan 1999 12:05:41 -0800 (PST)
(envelope-from paul@originative.co.uk)
From: paul@originative.co.uk
Received: by octopus with Internet Mail Service (5.5.1960.3)
id <DZA9DY65>; Fri, 29 Jan 1999 20:04:09 -0000
Message-ID: <A6D02246E1ABD2119F5200C0F0303D10FDEA@octopus>
To: dfr@nlsystems.com, axl@iafrica.com
Cc: grog@lemis.com, current@FreeBSD.ORG
Subject: RE: btokup().. patch to STYLE(9) (fwd)
Date: Fri, 29 Jan 1999 20:04:06 -0000
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.1960.3)
Content-Type: text/plain
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
> -----Original Message-----
> From: Doug Rabson [mailto:dfr@nlsystems.com]
> Sent: 29 January 1999 10:49
> To: Sheldon Hearn
> Cc: Greg Lehey; current@FreeBSD.ORG
> Subject: Re: btokup().. patch to STYLE(9) (fwd)
>
>
> On Fri, 29 Jan 1999, Sheldon Hearn wrote:
> > On Fri, 29 Jan 1999 20:01:23 +1030, Greg Lehey wrote:
> >
...
> > > Documentation is the castor oil of programming.
> Managers know it
> > > must be good because the programmers hate it so much.
> >
> > I take this to mean "provide above your expression a comment that
> > explains what you're doing", not "clutter your expression with
> > unnecessary parens in case you've made a mistake that
> nobody will spot
> > because you haven't commented your code properly."
> >
> > The reason I'm interested in this (now tiresome) thread is
> that I'd much
> > rather have to read
> >
> > /*
> > * Bail out if the time left to next transaction is less than
> > * the duration of the previous transaction.
> > */
> > if (t % u - n % u < d % u) {
> >
> > than
> >
> > if (((t % u) - (n % u)) < (d % u)) {
>
> This is a strawman. The original expression is perfectly fine (by my
> rules). One could make a case for:
>
> if ((t % u) - (n % u) < d % u)
>
You could just as easily make a case for
if ((t % u - n % u) < (d % u))
the parens then draw your eye naturally to the central operator but
anyhow....
I think this sums up the general problem with style(9) and also this
thread. The style guide does not say anything definitive about how to
parenthesize the above expression. What style(9) says, and it's been
quoted many times already is
"Don't use parentheses unless they're required for precedence or the
statement is really confusing without them".
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Not this second bit, style(9) *ALLOWS* the use of extra parentheses when
the programmer feels the statement would be really confusing without
them. The whole argument is over what people consider to be "really
confusing" and that is definately something down to the person doing the
coding.
In my mind, adding extra parens for readibility is a good thing and I
fail to see where my opinion is in any way in conflict with style(9)
since I only add them if I feel that the expression would be more
confusing without them. I think people reading the above quote from
style(9) and interpreting it as meaning we should be minimalist in our
use of parens is misreading it.
To be honest, style(9) as it stands is worthless since it has paragraphs
such as the following in it
"In general code can be considered ``new code'' when it makes up about
50% or more of the files[s] involved. This is enough to break precedents
in the existing code and use the current style guidelines"
Over time this can only lead to a mishmash of styles throughout the
codebase. I disagree with this being acceptable practice, it's a cop-out
which basically says, "we have a style guide that encapsulates how the
current code looks but you're free to write in any style you want as
long as you write enough of it". In the long run you may as well not
bother with style(9), either there is a standard style or there isn't, a
man page documenting current style without advocating continuing
adherence is a rather pointless exercise.
It think it's a mistake to allow programmers to veer away from a common
style. Without consistency across the project it becomes difficult to
maintain code, which is why KNF exists in the first place.
Paul.
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Fri Jan 29 12:24:26 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id MAA06393
for freebsd-current-outgoing; Fri, 29 Jan 1999 12:24:26 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from octopus.originative.co.uk (originat.demon.co.uk [158.152.220.9])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA06364
for <current@FreeBSD.ORG>; Fri, 29 Jan 1999 12:24:11 -0800 (PST)
(envelope-from paul@originative.co.uk)
From: paul@originative.co.uk
Received: by octopus with Internet Mail Service (5.5.1960.3)
id <DZA9DY7V>; Fri, 29 Jan 1999 20:22:39 -0000
Message-ID: <A6D02246E1ABD2119F5200C0F0303D10FDEB@octopus>
To: julian@whistle.com, imp@village.org
Cc: akm@zeus.theinternet.com.au, current@FreeBSD.ORG
Subject: RE: btokup().. patch to STYLE(9) (fwd)
Date: Fri, 29 Jan 1999 20:22:33 -0000
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.1960.3)
Content-Type: text/plain
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
> -----Original Message-----
> From: Julian Elischer [mailto:julian@whistle.com]
> Sent: 29 January 1999 17:48
> To: Warner Losh
> Cc: Andrew Kenneth Milton; current@FreeBSD.ORG
> Subject: Re: btokup().. patch to STYLE(9) (fwd)
>
>
>
>
> On Fri, 29 Jan 1999, Warner Losh wrote:
> >
> > if ((a < 0) && (b < 0))
> >
> Personally while I KNOW (after wasting a second thinking
> about it) that
> the example below is the same as that above, I ALWAYS code as above.
> It takes me about 1/5th the time to know what it means.
>
> > if (a < 0 && b < 0)
>
> If I were working on this code written by someone else it'd leave my
> editor looking like the top example, that's for sure. I think that
> "How easy is it to edit a piece of code and still have it do what you
> expect" is an important consideration, because people DO edit things.
>
> >
> >
> > I do agree that complex things like:
> >
> > if (a | b & c % d ^ e)
> >
> > should really have some parents to show what is going on.
>
> I have NO idea of what that is doing and I have plans of
> looking it up in
> the book to work it out..
The interesting thing about this example, and there's probably something
in this, is that the first example is trivial to understand without
parens because it parses left to right as an English expression i.e.
if (a < 0 && b < 0)
"if a is less than 0 and b is less than 0"
It mirrors the way we read spoken language so it's very quick to see
what's going on. With the more difficult expression
if (a | b & c % d ^ e)
there's no spoken language analogy that flows left to right so we have
to parse it in much the same way as the compiler does. I bet that most
people are mentally putting braces around the expressions to break it up
or at least something along those lines. Therefore it makes sense to
actually put the parens there in the first place so that people can
parse it more quickly with the naked eye.
Paul.
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Fri Jan 29 14:16:59 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id OAA21274
for freebsd-current-outgoing; Fri, 29 Jan 1999 14:16:59 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from coleridge.kublai.com (coleridge.kublai.com [207.96.1.116])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA21268
for <current@FreeBSD.ORG>; Fri, 29 Jan 1999 14:16:55 -0800 (PST)
(envelope-from shmit@coleridge.kublai.com)
Received: (from shmit@localhost)
by coleridge.kublai.com (8.9.2/8.9.1) id RAA07687;
Fri, 29 Jan 1999 17:16:27 -0500 (EST)
Date: Fri, 29 Jan 1999 17:16:26 -0500
From: Brian Cully <shmit@kublai.com>
To: Luigi Rizzo <luigi@labinfo.iet.unipi.it>
Cc: Bruce Evans <bde@zeta.org.au>, grog@lemis.com, current@FreeBSD.ORG,
peter.jeremy@auss2.alcatel.com.au
Subject: Re: indent(1) and style(9) (was: btokup() macro in sys/malloc.h)
Message-ID: <19990129171626.B4540@kublai.com>
Reply-To: shmit@kublai.com
References: <199901280819.TAA23954@godzilla.zeta.org.au> <199901280701.IAA08320@labinfo.iet.unipi.it>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.95.1i
In-Reply-To: <199901280701.IAA08320@labinfo.iet.unipi.it>; from Luigi Rizzo on Thu, Jan 28, 1999 at 08:01:33AM +0100
X-Sender: If your mailer pays attention to this, it's broken.
X-PGP-Info: finger shmit@kublai.com for my public key.
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
On Thu, Jan 28, 1999 at 08:01:33AM +0100, Luigi Rizzo wrote:
> not speaking about vinum, but to me, the indentation of 8 char and
> line length of 80 chars are almost mutually exclusive.
I've managed to do this for years without much problem. When it
is un-avoidable, you can always use a macro.
-bjc
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Fri Jan 29 14:39:31 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id OAA23523
for freebsd-current-outgoing; Fri, 29 Jan 1999 14:39:31 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from cheddar.netmonger.net (cheddar.netmonger.net [209.54.21.140])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA23516;
Fri, 29 Jan 1999 14:39:27 -0800 (PST)
(envelope-from chris@cheddar.netmonger.net)
Received: (from chris@localhost)
by cheddar.netmonger.net (8.8.8/8.8.8) id RAA01940;
Fri, 29 Jan 1999 17:39:23 -0500 (EST)
Message-ID: <19990129173922.A29551@netmonger.net>
Date: Fri, 29 Jan 1999 17:39:22 -0500
From: Christopher Masto <chris@netmonger.net>
To: hardware@FreeBSD.ORG
Cc: current@FreeBSD.ORG
Subject: Network/ARP problem? Maybe pn driver?
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.91.1i
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
I hope I'm not just being really stupid, but I think there's a problem
somewhere. If it's a configuration error on my part, then I think I'd
better take a vacation, considering what my job is supposed to be.
Anyway, I have a machine that is exhibiting a weird network problem.
My guess is that ARP is not working, or perhaps something that ARP
depends on (broadcasts?) is not working.
The symptom is, quite simply, that computer A (this new one) is not
able to communicate with any other computers.. until those other
computers communicate with A.
For example, if A tries to ping B, A appears to get no response,
saying that B is down. But if B pings A, A is now able to ping B.
But A still can't ping C until C pings A as well.
All (two dozen) other machines on the network have been working fine,
some of them for years. I have ruled out problems with the hub,
cabling, etc., by swapping them. I have not swapped out the network
card (a PNIC-based NetGear 10/100), but it does work under Windows on
this same machine.
Here is what the routing table looks like during one of these episodes:
Destination Gateway Flags Refs Use Netif Expire
default 209.54.21.129 UGSc 0 0 pn0
127.0.0.1 127.0.0.1 UH 0 0 lo0
209.54.21 link#1 UC 0 0 pn0
209.54.21.129 0:e0:b0:e2:bc:79 UHLW 1 0 pn0 970
209.54.21.142 link#1 UHRLW 0 7 pn0
209.54.21.181 link#1 UHRLW 0 7 pn0
209.54.21.199 0:60:97:a3:63:e6 UHLW 1 44 pn0 1159
At this time, it is possible to talk to .129 and .199, but not .142 or
.181. Attempts to ping other addresses result in them appearing in
the table with "link#1" entries. If I ping A from the other machine,
the "link#1" is replaced by the correct hardware address.
Here's the ARP table:
bertha% arp -n -a
? (209.54.21.129) at 0:e0:b0:e2:bc:79
? (209.54.21.142) at (incomplete)
? (209.54.21.181) at (incomplete)
? (209.54.21.199) at 0:60:97:a3:63:e6
bertha% arp -n 209.54.21.142
? (209.54.21.142) at (incomplete)
It's as if machine A isn't hearing the ARP responses. Here is part of
a tcpdump done from another machine on the same segment during this
time:
17:07:06.751678 arp who-has 209.54.21.142 tell 209.54.21.233
17:07:06.751862 arp reply 209.54.21.142 is-at 0:60:97:a3:63:af
17:07:16.767849 arp who-has 209.54.21.142 tell 209.54.21.233
17:07:16.767997 arp reply 209.54.21.142 is-at 0:60:97:a3:63:af
17:07:26.783799 arp who-has 209.54.21.142 tell 209.54.21.233
17:07:26.783928 arp reply 209.54.21.142 is-at 0:60:97:a3:63:af
17:07:46.796125 arp who-has 209.54.21.142 tell 209.54.21.233
17:07:46.796279 arp reply 209.54.21.142 is-at 0:60:97:a3:63:af
The ARP is being sent out, and so is the response, but it's not being
picked up for some reason.
Here's a boot -v from the machine (at least, the part that fit in the
dmesg buffer):
06-00-00, hdrtype=0x00, mfdev=0
subordinatebus=0 secondarybus=0
chip0: <Intel 82439> rev 0x01 on pci0.0.0
found-> vendor=0x8086, dev=0x7000, revid=0x00
class=06-01-00, hdrtype=0x00, mfdev=1
subordinatebus=0 secondarybus=0
chip1: <Intel 82371SB PCI to ISA bridge> rev 0x00 on pci0.7.0
I/O Recovery Timing: 8-bit 3 clocks, 16-bit 2 clocks
Extended BIOS: enabled
Lower BIOS: disabled
Coprocessor IRQ13: enabled
Mouse IRQ12: disabled
Interrupt Routing: A: IRQ9, B: IRQ12, C: disabled, D: IRQ11
MB0: IRQ15, MB1:
found-> vendor=0x8086, dev=0x7010, revid=0x00
class=01-01-80, hdrtype=0x00, mfdev=0
subordinatebus=0 secondarybus=0
map[0]: type 4, range 32, base 00009000, size 4
ide_pci0: <Intel PIIX3 Bus-master IDE controller> rev 0x00 on pci0.7.1
intel_piix_status: primary master/slave sample = 3, master/slave recovery = 1
intel_piix_status: primary master fastDMAonly disabled, pre/post enabled,
intel_piix_status: IORDY sampling enabled,
intel_piix_status: fast PIO enabled
intel_piix_status: primary master/slave sample = 3, master/slave recovery = 1
intel_piix_status: primary slave fastDMAonly disabled, pre/post disabled,
intel_piix_status: IORDY sampling disabled,
intel_piix_status: fast PIO disabled
ide_pci: busmaster 0 status: 04 from port: 00009002
intel_piix_status: secondary master/slave sample = 3, master/slave recovery = 3
intel_piix_status: secondary master fastDMAonly disabled, pre/post enabled,
intel_piix_status: IORDY sampling enabled,
intel_piix_status: fast PIO enabled
intel_piix_status: secondary master/slave sample = 3, master/slave recovery = 3
intel_piix_status: secondary slave fastDMAonly disabled, pre/post disabled,
intel_piix_status: IORDY sampling disabled,
intel_piix_status: fast PIO disabled
ide_pci: busmaster 1 status: 04 from port: 0000900a
found-> vendor=0x8086, dev=0x7020, revid=0x00
class=0c-03-00, hdrtype=0x00, mfdev=0
subordinatebus=0 secondarybus=0
intpin=d, irq=11
map[0]: type 4, range 32, base 00006000, size 5
found-> vendor=0x5333, dev=0x8811, revid=0x40
class=03-00-00, hdrtype=0x00, mfdev=0
subordinatebus=0 secondarybus=0
intpin=a, irq=9
map[0]: type 1, range 32, base e0000000, size 26
vga0: <S3 Trio graphics accelerator> rev 0x40 int a irq 9 on pci0.17.0
found-> vendor=0x11ad, dev=0x0002, revid=0x21
class=02-00-00, hdrtype=0x00, mfdev=0
subordinatebus=0 secondarybus=0
intpin=a, irq=12
map[0]: type 4, range 32, base 00006100, size 8
map[1]: type 1, range 32, base e4000000, size 8
pn0: <82c168/82c169 PNIC 10/100BaseTX> rev 0x21 int a irq 12 on pci0.18.0
pn0: Ethernet address: 00:a0:cc:3b:66:51
pn0: probing for a PHY
pn0: checking address: 0
pn0: checking address: 1
pn0: found PHY at address 1, vendor id: 7810 device id: 0
pn0: PHY type: <Level 1 LXT970>
pn0: PHY status word: 7809
pn0: 10Mbps half-duplex mode supported
pn0: 10Mbps full-duplex mode supported
pn0: 100Mbps half-duplex mode supported
pn0: 100Mbps full-duplex mode supported
pn0: autoneg supported
pn0: autoneg complete, link status good (half-duplex, 10Mbps)
bpf: pn0 attached
Initializing PnP override table
Probing for PnP devices:
Trying Read_Port at 203
Trying Read_Port at 243
PnP: CSN 1 COMP_DEVICE_ID = 0x0006d041
CSN 1 Vendor ID: CTL0044 [0x44008c0e] Serial 0x000ca45a Comp ID: PNP0600 [0x0006d041]
Called nullpnp_probe with tag 0x00000001, type 0x44008c0e
Called nullpnp_probe with tag 0x00000001, type 0x0006d041
Probing for devices on the ISA bus:
atkbd: the current kbd controller command byte 0047
atkbd: keyboard ID 0x41ab (2)
kbdc: RESET_KBD return code:00fa
kbdc: RESET_KBD status:00aa
sc0 on isa
sc0: fb0 kbd0
sc0: VGA color <16 virtual consoles, flags=0x0>
atkbdc0 at 0x60-0x6f on motherboard
atkbd0 irq 1 on isa
kbd0: atkbd0, AT 101/102 (2), config:0x10000, flags:0x3d0000
psm0: current command byte:0047
kbdc: TEST_AUX_PORT status:0000
kbdc: RESET_AUX return code:00fe
kbdc: RESET_AUX return code:00fe
kbdc: RESET_AUX return code:00fe
kbdc: DIAGNOSE status:0055
kbdc: TEST_KBD_PORT status:0000
psm0: failed to reset the aux device.
psm0 not found
sio0: irq maps: 0x1 0x11 0x1 0x1
sio0 at 0x3f8-0x3ff irq 4 flags 0x10 on isa
sio0: type 16550A
sio1: irq maps: 0x1 0x9 0x1 0x1
sio1 at 0x2f8-0x2ff irq 3 on isa
sio1: type 16550A
ppc: parallel port found at 0x3bc
ppc0: ECP SPP ECP+EPP SPP
ppc0 at 0x3bc irq 7 on isa
ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode
ppc0: FIFO with 16/16/14 bytes threshold
nlpt0: <generic printer> on ppbus 0
nlpt0: Interrupt-driven port
ppi0: <generic parallel i/o> on ppbus 0
plip: irq 7
plip0: <PLIP network interface> on ppbus 0
bpf: lp0 attached
fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa
fdc0: FIFO enabled, 8 bytes threshold
fd0: 1.44MB 3.5in
wdc0 at 0x1f0-0x1f7 irq 14 flags 0xa0ffa0ff on isa
intel_piix_dmainit: setting multiword DMA mode 2
wd0: wdsetmode() setting transfer mode to 22
intel_piix_status: primary master sample = 3, master recovery = 1
intel_piix_status: primary master fastDMAonly disabled, pre/post enabled,
intel_piix_status: IORDY sampling enabled,
intel_piix_status: fast PIO enabled
wdc0: unit 0 (wd0): <WDC AC26400B>, DMA, 32-bit, multi-block-16
wd0: 6149MB (12594960 sectors), 13328 cyls, 15 heads, 63 S/T, 512 B/S
wd0: ATA INQUIRE valid = 0007, dmamword = 0407, apio = 0003, udma = 0007
wdc1 at 0x170-0x177 irq 15 flags 0xa0ffa0ff on isa
wdc1: unit 0 (atapi): <FX600S/P01>, removable, intr, dma, iordis
acd0: drive speed 1033KB/sec, 256KB cache
acd0: supported read types:
acd0: Audio: play, 255 volume levels
acd0: Mechanism: ejectable tray
acd0: Medium: no/blank disc inside, unlocked
wdc1: unit 1 (atapi): <IOMEGA ZIP 100 ATAPI/23.D>, removable, intr, iordis
vga0 at 0x3b0-0x3df maddr 0xa0000 msize 131072 on isa
fb0: vga0, vga, type:VGA (5), flags:0x7007f
fb0: port:0x3b0-0x3df, crtc:0x3d4, mem:0xa0000 0x20000
fb0: init mode:24, bios mode:3, current mode:24
fb0: window:0xf00b8000 size:32k gran:32k, buf:0x0 size:0k
VGA parameters upon power-up
50 18 10 00 00 00 03 00 02 67 5f 4f 50 82 55 81
bf 1f 00 4f 0e 0f 00 00 07 80 9c 8e 8f 28 1f 96
b9 a3 ff 00 01 02 03 04 05 14 07 38 39 3a 3b 3c
3d 3e 3f 0c 00 0f 08 00 00 00 00 00 10 0e 00 ff
VGA parameters in BIOS for mode 24
50 18 10 00 10 00 03 00 02 67 5f 4f 50 82 55 81
bf 1f 00 4f 0d 0e 00 00 00 00 9c 8e 8f 28 1f 96
b9 a3 ff 00 01 02 03 04 05 14 07 38 39 3a 3b 3c
3d 3e 3f 0c 00 0f 08 00 00 00 00 00 10 0e 00 ff
EGA/VGA parameters to be used for mode 24
50 18 10 00 10 00 03 00 02 67 5f 4f 50 82 55 81
bf 1f 00 4f 0d 0e 00 00 00 00 9c 8e 8f 28 1f 96
b9 a3 ff 00 01 02 03 04 05 14 07 38 39 3a 3b 3c
3d 3e 3f 0c 00 0f 08 00 00 00 00 00 10 0e 00 ff
npx0 on motherboard
npx0: INT 16 interface
apm0 flags 0x31 on isa
apm: found APM BIOS version 1.1
sb0 at 0x220 irq 5 drq 1 on isa
snd0: <SoundBlaster 16 4.13>
sbxvi0 at drq 5 on isa
snd0: <SoundBlaster 16 4.13>
sbmidi0 at 0x330 on isa
snd0: <SoundBlaster MPU-401>
imasks: bio c008c040, tty c007109a, net c007109a
BIOS Geometries:
0:00000000 0..0=1 cylinders, 0..0=1 heads, 1..0=0 sectors
1:00000000 0..0=1 cylinders, 0..0=1 heads, 1..0=0 sectors
2:00000000 0..0=1 cylinders, 0..0=1 heads, 1..0=0 sectors
3:00000000 0..0=1 cylinders, 0..0=1 heads, 1..0=0 sectors
4:00000000 0..0=1 cylinders, 0..0=1 heads, 1..0=0 sectors
5:00000000 0..0=1 cylinders, 0..0=1 heads, 1..0=0 sectors
6:00000000 0..0=1 cylinders, 0..0=1 heads, 1..0=0 sectors
7:00000000 0..0=1 cylinders, 0..0=1 heads, 1..0=0 sectors
0 accounted for
Device configuration finished.
IP packet filtering initialized, divert enabled, rule-based forwarding enabled, logging limited to 100 packets/entry
bpf: tun0 attached
bpf: sl0 attached
bpf: ppp0 attached
new masks: bio c008c040, tty c007109a, net c007109a
bpf: lo0 attached
IP Filter: initialized. Default = pass all, Logging = enabled
Considering MFS root f/s.
No MFS image available as root f/s.
Considering FFS root f/s.
changing root device to wd0s2a
wd0s1: type 0xb, start 63, end = 8193149, size 8193087 : OK
wd0s2: type 0xa5, start 8193150, end = 12594959, size 4401810 : OK
ffs_mountfs: superblock updated for soft updates
ffs_mountfs: superblock updated for soft updates
ffs_mountfs: superblock updated for soft updates
By the way, it's running:
FreeBSD 4.0-CURRENT #1: Sun Jan 24 23:39:56 EST 1999
But I had the same problems with a 3.0-CURRENT snapshot (I upgraded it
in case this problem had already been fixed).
This machine is not mine; I will only have access to it for another
week or so, but during that time I will be able to do any testing or
diagnostics needed.
I'd appreciate any ideas or suggestions.
--
Christopher Masto Director of Operations NetMonger Communications
chris@netmonger.net info@netmonger.net http://www.netmonger.net
"Good tools allow users to do stupid things." -- Clay Shirky
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Fri Jan 29 14:52:21 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id OAA25603
for freebsd-current-outgoing; Fri, 29 Jan 1999 14:52:21 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from alpha.xerox.com (alpha.Xerox.COM [13.1.64.93])
by hub.freebsd.org (8.8.8/8.8.8) with SMTP id OAA25598;
Fri, 29 Jan 1999 14:52:19 -0800 (PST)
(envelope-from fenner@parc.xerox.com)
Received: from crevenia.parc.xerox.com ([13.2.116.11]) by alpha.xerox.com with SMTP id <53867(1)>; Fri, 29 Jan 1999 14:52:15 PST
Received: by crevenia.parc.xerox.com id <177534>; Fri, 29 Jan 1999 14:52:13 -0800
From: Bill Fenner <fenner@parc.xerox.com>
To: chris@netmonger.net, hardware@FreeBSD.ORG
Subject: Re: Network/ARP problem? Maybe pn driver?
Cc: current@FreeBSD.ORG
Message-Id: <99Jan29.145213pst.177534@crevenia.parc.xerox.com>
Date: Fri, 29 Jan 1999 14:52:07 PST
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
Can you run a "tcpdump arp" on the machine that is having the problem,
as well? This could help to determine if it's a driver problem (e.g.
if the replies don't show up) or an ARP problem (e.g. if the replies
do show up but arp doesn't use them).
Bill
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Fri Jan 29 15:06:18 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id PAA27337
for freebsd-current-outgoing; Fri, 29 Jan 1999 15:06:18 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from cheddar.netmonger.net (cheddar.netmonger.net [209.54.21.140])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA27330;
Fri, 29 Jan 1999 15:06:15 -0800 (PST)
(envelope-from chris@cheddar.netmonger.net)
Received: (from chris@localhost)
by cheddar.netmonger.net (8.8.8/8.8.8) id SAA04552;
Fri, 29 Jan 1999 18:06:12 -0500 (EST)
Message-ID: <19990129180612.C3237@netmonger.net>
Date: Fri, 29 Jan 1999 18:06:12 -0500
From: Christopher Masto <chris@netmonger.net>
To: Bill Fenner <fenner@parc.xerox.com>, hardware@FreeBSD.ORG
Cc: current@FreeBSD.ORG
Subject: Re: Network/ARP problem? Maybe pn driver?
References: <99Jan29.145213pst.177534@crevenia.parc.xerox.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.91.1i
In-Reply-To: <99Jan29.145213pst.177534@crevenia.parc.xerox.com>; from Bill Fenner on Fri, Jan 29, 1999 at 02:52:07PM -0800
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
On Fri, Jan 29, 1999 at 02:52:07PM -0800, Bill Fenner wrote:
> Can you run a "tcpdump arp" on the machine that is having the problem,
> as well? This could help to determine if it's a driver problem (e.g.
> if the replies don't show up) or an ARP problem (e.g. if the replies
> do show up but arp doesn't use them).
Good idea.
Hmm. Running tcpdump seems to make the problem go away. The ARP
replies show up immediately appear in the table. Clue.
--
Christopher Masto Director of Operations NetMonger Communications
chris@netmonger.net info@netmonger.net http://www.netmonger.net
"Good tools allow users to do stupid things." -- Clay Shirky
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Fri Jan 29 15:17:35 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id PAA28632
for freebsd-current-outgoing; Fri, 29 Jan 1999 15:17:35 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA28626
for <current@FreeBSD.ORG>; Fri, 29 Jan 1999 15:17:33 -0800 (PST)
(envelope-from dillon@apollo.backplane.com)
Received: (from dillon@localhost)
by apollo.backplane.com (8.9.2/8.9.1) id PAA84062;
Fri, 29 Jan 1999 15:17:26 -0800 (PST)
(envelope-from dillon)
Date: Fri, 29 Jan 1999 15:17:26 -0800 (PST)
From: Matthew Dillon <dillon@apollo.backplane.com>
Message-Id: <199901292317.PAA84062@apollo.backplane.com>
To: Bruce Evans <bde@zeta.org.au>
Cc: current@FreeBSD.ORG
Subject: c_caddr_t
References: <99Jan29.145213pst.177534@crevenia.parc.xerox.com> <19990129180612.C3237@netmonger.net>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
bde, I don't mind you removing c_caddr_t as long as you also fix the
warnings that it fixed, but it would have been appropriate to notify
me of what you were doing rather then slamming me in the CVS commit
comments. I find that sort of behavior to be highly inappropriate.
-Matt
Matthew Dillon
<dillon@backplane.com>
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Fri Jan 29 15:22:21 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id PAA29525
for freebsd-current-outgoing; Fri, 29 Jan 1999 15:22:21 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from skynet.ctr.columbia.edu (skynet.ctr.columbia.edu [128.59.64.70])
by hub.freebsd.org (8.8.8/8.8.8) with SMTP id PAA29505;
Fri, 29 Jan 1999 15:22:15 -0800 (PST)
(envelope-from wpaul@skynet.ctr.columbia.edu)
Received: (from wpaul@localhost) by skynet.ctr.columbia.edu (8.6.12/8.6.9) id SAA26781; Fri, 29 Jan 1999 18:28:47 -0500
From: Bill Paul <wpaul@skynet.ctr.columbia.edu>
Message-Id: <199901292328.SAA26781@skynet.ctr.columbia.edu>
Subject: Re: Network/ARP problem? Maybe pn driver?
To: chris@netmonger.net (Christopher Masto)
Date: Fri, 29 Jan 1999 18:28:46 -0500 (EST)
Cc: fenner@parc.xerox.com, current@FreeBSD.ORG, hardware@FreeBSD.ORG
In-Reply-To: <19990129180612.C3237@netmonger.net> from "Christopher Masto" at Jan 29, 99 06:06:12 pm
X-Mailer: ELM [version 2.4 PL24]
Content-Type: text
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
Of all the gin joints in all the towns in all the world, Christopher
Masto had to walk into mine and say:
> On Fri, Jan 29, 1999 at 02:52:07PM -0800, Bill Fenner wrote:
> > Can you run a "tcpdump arp" on the machine that is having the problem,
> > as well? This could help to determine if it's a driver problem (e.g.
> > if the replies don't show up) or an ARP problem (e.g. if the replies
> > do show up but arp doesn't use them).
>
> Good idea.
>
> Hmm. Running tcpdump seems to make the problem go away. The ARP
> replies show up immediately appear in the table. Clue.
You should have tried that first.
There's something I'd like you to try for me. (Don't delay in trying
this; I've had a long string of people who appear suddenly, complain
about a problem of some sort, then vanish before I can extract enough
information from them to find a solution.)
I was menaced by a bug in the PNIC's receive DMA operation which, according
to all my tests, only appeared in promiscuous mode. I devised a workaround,
however it's only enabled when the IFF_PROMISC flag is set on the
interface. Running tcpdump (without the -p flag) places the interface
in promiscuous mode and enables the workaround. Given what you've said,
it's possible that we need to enable the workaround all the time, not
just in promiscuous mode.
Do me the following:
- Bring up /sys/pci/if_pn.c in your favorite editor.
- Locate the pn_rxeof() function and find the following code:
#ifdef PN_PROMISC_BUG_WAR
/*
* XXX The PNIC seems to have a bug that manifests
* when the promiscuous mode bit is set: we have to
* watch for it and work around it.
*/
if (sc->pn_promisc_war && ifp->if_flags & IFF_PROMISC) {
[...]
- Change the if() clause so that it looks like this:
if (sc->pn_promisc_war /*&& ifp->if_flags & IFF_PROMISC*/) {
(In other words, comment out the test for the IFF_PROMISC flag.)
This will enable the workaround all the time and allow the receiver bug
to be detected and handled properly.
Compile a new kernel with this change and see if the problem persists.
Report back your findings (one way or the other) so that I'll know if
I should modify the code in the repository.
-Bill
--
=============================================================================
-Bill Paul (212) 854-6020 | System Manager, Master of Unix-Fu
Work: wpaul@ctr.columbia.edu | Center for Telecommunications Research
Home: wpaul@skynet.ctr.columbia.edu | Columbia University, New York City
=============================================================================
"It is not I who am crazy; it is I who am mad!" - Ren Hoek, "Space Madness"
=============================================================================
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Fri Jan 29 15:23:22 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id PAA29647
for freebsd-current-outgoing; Fri, 29 Jan 1999 15:23:22 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from alpha.xerox.com (alpha.Xerox.COM [13.1.64.93])
by hub.freebsd.org (8.8.8/8.8.8) with SMTP id PAA29628;
Fri, 29 Jan 1999 15:23:18 -0800 (PST)
(envelope-from fenner@parc.xerox.com)
Received: from crevenia.parc.xerox.com ([13.2.116.11]) by alpha.xerox.com with SMTP id <53946(2)>; Fri, 29 Jan 1999 15:23:10 PST
Received: from localhost by crevenia.parc.xerox.com with SMTP id <177534>; Fri, 29 Jan 1999 15:23:02 -0800
To: Christopher Masto <chris@netmonger.net>
cc: Bill Fenner <fenner@parc.xerox.com>, hardware@FreeBSD.ORG,
current@FreeBSD.ORG
Subject: Re: Network/ARP problem? Maybe pn driver?
In-reply-to: Your message of "Fri, 29 Jan 99 15:06:12 PST."
<19990129180612.C3237@netmonger.net>
Date: Fri, 29 Jan 1999 15:22:55 PST
From: Bill Fenner <fenner@parc.xerox.com>
Message-Id: <99Jan29.152302pst.177534@crevenia.parc.xerox.com>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
Big Clue. Run "tcpdump -p" and see if the problem doesn't go away.
("tcpdump" puts the card in promiscuous mode, "tcpdump -p" does not).
Bill
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Fri Jan 29 15:30:51 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id PAA00711
for freebsd-current-outgoing; Fri, 29 Jan 1999 15:30:51 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from cheddar.netmonger.net (cheddar.netmonger.net [209.54.21.140])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA00700;
Fri, 29 Jan 1999 15:30:44 -0800 (PST)
(envelope-from chris@cheddar.netmonger.net)
Received: (from chris@localhost)
by cheddar.netmonger.net (8.8.8/8.8.8) id SAA03955;
Fri, 29 Jan 1999 18:00:13 -0500 (EST)
Message-ID: <19990129180013.B3237@netmonger.net>
Date: Fri, 29 Jan 1999 18:00:13 -0500
From: Christopher Masto <chris@netmonger.net>
To: Alfred Perlstein <bright@hotjobs.com>
Cc: current@FreeBSD.ORG, hardware@FreeBSD.ORG
Subject: Re: Network/ARP problem? Maybe pn driver?
References: <19990129173922.A29551@netmonger.net> <Pine.BSF.4.05.9901291801220.81323-100000@bright.fx.genx.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.91.1i
In-Reply-To: <Pine.BSF.4.05.9901291801220.81323-100000@bright.fx.genx.net>; from Alfred Perlstein on Fri, Jan 29, 1999 at 06:02:16PM -0500
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
On Fri, Jan 29, 1999 at 06:02:16PM -0500, Alfred Perlstein wrote:
> On Fri, 29 Jan 1999, Christopher Masto wrote:
> > I hope I'm not just being really stupid, but I think there's a problem
> > somewhere. If it's a configuration error on my part, then I think I'd
> > better take a vacation, considering what my job is supposed to be.
> >
> > Anyway, I have a machine that is exhibiting a weird network problem.
> > My guess is that ARP is not working, or perhaps something that ARP
> > depends on (broadcasts?) is not working.
> >
>
> i didn't see your netmask's, can you show me those please?
>
> on the broken box, and on one of the working boxes?
Yes, sorry.. I accidentally deleted that part of the message.
Here's the broken box:
pn0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
inet 209.54.21.233 netmask 0xffffff00 broadcast 209.54.21.255
ether 00:a0:cc:3b:66:51
media: 10baseT/UTP <half-duplex>
supported media: autoselect 100baseTX <full-duplex> 100baseTX <half-duplex> 100baseTX 10baseT/UTP <full-duplex> 10baseT/UTP 10baseT/UTP <half-duplex>
And here's a working one:
ep0: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> mtu 1500
inet 209.54.21.199 netmask 0xffffff00 broadcast 209.54.21.255
ether 00:60:97:a3:63:e6
The 255.255.255.0 netmask is correct here, despite the router being at
.129.
--
Christopher Masto Director of Operations NetMonger Communications
chris@netmonger.net info@netmonger.net http://www.netmonger.net
"Good tools allow users to do stupid things." -- Clay Shirky
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Fri Jan 29 15:41:37 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id PAA02168
for freebsd-current-outgoing; Fri, 29 Jan 1999 15:41:37 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from ns1.seidata.com (ns1.seidata.com [208.10.211.2])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA02163
for <current@FreeBSD.ORG>; Fri, 29 Jan 1999 15:41:35 -0800 (PST)
(envelope-from mike@seidata.com)
From: mike@seidata.com
Received: from localhost (mike@localhost)
by ns1.seidata.com (8.8.8/8.8.5) with ESMTP id SAA08903;
Fri, 29 Jan 1999 18:41:36 -0500 (EST)
Date: Fri, 29 Jan 1999 18:41:36 -0500 (EST)
To: Tim Preece <bsdcurrent@scratch.demon.co.uk>
cc: current@FreeBSD.ORG
Subject: Re: Telnet and NIS queries
In-Reply-To: <9q$ZtHAN9es2EwEW@scratch.demon.co.uk>
Message-ID: <Pine.BSF.4.05.9901291833110.6273-100000@ns1.seidata.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
On Fri, 29 Jan 1999, Tim Preece wrote:
> scratch2 login: LOGIN root REFUSED (NOROOT) from scratch1.netlink on TTY
> ttyp0
As long as I can remember, root logins have always been refused over
network connections. If you want to login as root over a network (bad
habbit, but ok for your own, private network I suppose) you have to
specifically allow it in /etc/login.access.
> reading about netgroup and creating /etc/netgroup with only + in it
> and re-make the yp Makefile does not produce netgrp.byname etc
>
> Do I need netgroup and if so what am I doing wrong, Is this a problem
> with having ELF on one box and aout on the other !!!!!
If you're wanting to use NIS, you will need netgroup... are both
systems members of the same NIS domain? Are you initializing the maps
with ypinit -m on the master server? Are you running all essential
daemons on both machines (namely, ypserv, ypxfrd and ypbind on the
master server and ypbind on the client server(s))?
Good luck...
--
Mike Hoskins
System/Network Administrator
SEI Data Network Services, Inc.
http://www.seidata.com
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Fri Jan 29 15:43:38 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id PAA02636
for freebsd-current-outgoing; Fri, 29 Jan 1999 15:43:38 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from ns1.seidata.com (ns1.seidata.com [208.10.211.2])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA02629
for <current@FreeBSD.ORG>; Fri, 29 Jan 1999 15:43:35 -0800 (PST)
(envelope-from mike@seidata.com)
From: mike@seidata.com
Received: from localhost (mike@localhost)
by ns1.seidata.com (8.8.8/8.8.5) with ESMTP id SAA09422;
Fri, 29 Jan 1999 18:43:34 -0500 (EST)
Date: Fri, 29 Jan 1999 18:43:34 -0500 (EST)
To: Maxim Sobolev <sobomax@altavista.net>
cc: Tim Preece <bsdcurrent@scratch.demon.co.uk>, current@FreeBSD.ORG
Subject: Re: Telnet and NIS queries
In-Reply-To: <36B1F5CF.C8D4D370@altavista.net>
Message-ID: <Pine.BSF.4.05.9901291842010.6273-100000@ns1.seidata.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
On Fri, 29 Jan 1999, Maxim Sobolev wrote:
> Your "problem" with telnet session is very simple - by default FreeBSD
> doesn't allow anybody to login as "root" through insecure connection (see
> /etc/ttys). This can be changed by editing /etc/ttys to make Pseudo
*doh* Yes, it's /etc/ttys *not* login.access as I said in my reply.
I agree that this is really a bad idea/habbit with serious
implications.
--
Mike Hoskins
System/Network Administrator
SEI Data Network Services, Inc.
http://www.seidata.com
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Fri Jan 29 15:46:04 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id PAA03018
for freebsd-current-outgoing; Fri, 29 Jan 1999 15:46:04 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from allegro.lemis.com (allegro.lemis.com [192.109.197.134])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA02972
for <current@FreeBSD.ORG>; Fri, 29 Jan 1999 15:45:56 -0800 (PST)
(envelope-from grog@freebie.lemis.com)
Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137])
by allegro.lemis.com (8.9.1/8.9.0) with ESMTP id KAA05590;
Sat, 30 Jan 1999 10:15:53 +1030 (CST)
Received: (from grog@localhost)
by freebie.lemis.com (8.9.2/8.9.0) id KAA23944;
Sat, 30 Jan 1999 10:15:52 +1030 (CST)
Date: Sat, 30 Jan 1999 10:15:52 +1030
From: Greg Lehey <grog@lemis.com>
To: Poul-Henning Kamp <phk@critter.freebsd.dk>
Cc: current@FreeBSD.ORG
Subject: indent (was: btokup().. patch to STYLE(9) (fwd))
Message-ID: <19990130101552.U8473@freebie.lemis.com>
References: <6892.917596754@zippy.cdrom.com> <2211.917597619@critter.freebsd.dk>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.95.1i
In-Reply-To: <2211.917597619@critter.freebsd.dk>; from Poul-Henning Kamp on Fri, Jan 29, 1999 at 09:13:39AM +0100
WWW-Home-Page: http://www.lemis.com/~grog
Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia
Phone: +61-8-8388-8286
Fax: +61-8-8388-8725
Mobile: +61-41-739-7062
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
On Friday, 29 January 1999 at 9:13:39 +0100, Poul-Henning Kamp wrote:
> It would also be nice if somebody whould coerse ident to DTRT.
I've already mentioned that I have a version of indent with DABT.
Shall I polish it up a bit?
Greg
--
See complete headers for address, home page and phone numbers
finger grog@lemis.com for PGP public key
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Fri Jan 29 15:57:04 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id PAA04000
for freebsd-current-outgoing; Fri, 29 Jan 1999 15:57:04 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from whistle.com (s205m131.whistle.com [207.76.205.131])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA03995;
Fri, 29 Jan 1999 15:57:01 -0800 (PST)
(envelope-from archie@whistle.com)
Received: (from smap@localhost) by whistle.com (8.7.5/8.6.12) id PAA28631; Fri, 29 Jan 1999 15:56:22 -0800 (PST)
Received: from bubba.whistle.com( 207.76.205.7) by whistle.com via smap (V2.0)
id xma028629; Fri, 29 Jan 99 15:56:20 -0800
Received: (from archie@localhost) by bubba.whistle.com (8.8.7/8.6.12) id PAA01669; Fri, 29 Jan 1999 15:56:20 -0800 (PST)
From: Archie Cobbs <archie@whistle.com>
Message-Id: <199901292356.PAA01669@bubba.whistle.com>
Subject: Re: Network/ARP problem? Maybe pn driver?
In-Reply-To: <19990129180612.C3237@netmonger.net> from Christopher Masto at "Jan 29, 99 06:06:12 pm"
To: chris@netmonger.net (Christopher Masto)
Date: Fri, 29 Jan 1999 15:56:20 -0800 (PST)
Cc: fenner@parc.xerox.com, hardware@FreeBSD.ORG, current@FreeBSD.ORG
X-Mailer: ELM [version 2.4ME+ PL38 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
Christopher Masto writes:
> > Can you run a "tcpdump arp" on the machine that is having the problem,
> > as well? This could help to determine if it's a driver problem (e.g.
> > if the replies don't show up) or an ARP problem (e.g. if the replies
> > do show up but arp doesn't use them).
>
> Good idea.
>
> Hmm. Running tcpdump seems to make the problem go away. The ARP
> replies show up immediately appear in the table. Clue.
Tcpdump puts the Ethernet card in promiscuous mode. So perhaps
somebody is trying to unicast you something but using the wrong
Ethernet address. Could be the local or remote ARP code. Just
a guess.
-Archie
___________________________________________________________________________
Archie Cobbs * Whistle Communications, Inc. * http://www.whistle.com
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Fri Jan 29 16:19:52 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id QAA09436
for freebsd-current-outgoing; Fri, 29 Jan 1999 16:19:52 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from allegro.lemis.com (allegro.lemis.com [192.109.197.134])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA09431
for <current@FreeBSD.ORG>; Fri, 29 Jan 1999 16:19:49 -0800 (PST)
(envelope-from grog@freebie.lemis.com)
Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137])
by allegro.lemis.com (8.9.1/8.9.0) with ESMTP id KAA05725;
Sat, 30 Jan 1999 10:49:45 +1030 (CST)
Received: (from grog@localhost)
by freebie.lemis.com (8.9.2/8.9.0) id KAA24026;
Sat, 30 Jan 1999 10:49:43 +1030 (CST)
Date: Sat, 30 Jan 1999 10:49:43 +1030
From: Greg Lehey <grog@lemis.com>
To: Warner Losh <imp@village.org>
Cc: Julian Elischer <julian@whistle.com>, current@FreeBSD.ORG
Subject: Re: btokup().. patch to STYLE(9) (fwd)
Message-ID: <19990130104943.W8473@freebie.lemis.com>
References: <Pine.BSF.4.05.9901290941240.304-100000@s204m82.isp.whistle.com> <199901291802.LAA67403@harmony.village.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.95.1i
In-Reply-To: <199901291802.LAA67403@harmony.village.org>; from Warner Losh on Fri, Jan 29, 1999 at 11:02:48AM -0700
WWW-Home-Page: http://www.lemis.com/~grog
Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia
Phone: +61-8-8388-8286
Fax: +61-8-8388-8725
Mobile: +61-41-739-7062
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
On Friday, 29 January 1999 at 11:02:48 -0700, Warner Losh wrote:
>> If I were working on this code written by someone else it'd leave my
>> editor looking like the top example, that's for sure. I think that
>> "How easy is it to edit a piece of code and still have it do what you
>> expect" is an important consideration, because people DO edit things.
>
> Agreed.
>
>>> I do agree that complex things like:
>>>
>>> if (a | b & c % d ^ e)
>>>
>>> should really have some parents to show what is going on.
>>
>> I have NO idea of what that is doing and I have plans of looking it up in
>> the book to work it out..
>
> Yes. I agree with that.
> if (a | b & c % d ^ e)
> should have been written as:
> if (((a | (b & (c % d))) ^ e) != 0)
> (then again, either way it is ugly code and should have comments).
It's interesting that this whole argument has just addressed the
syntax, and nobody has given any consideration to the semantics. In
this example, all variables are a single character. Given the fact
that this expression is probably indented 16 characters, there's a
strong incentive to keep the variable names short, even at the expense
of intelligibility. Consider one possible expansion
if (((allocationfail | (IGNOREFAILUREMASK & (incount % BLKSIZE))) ^ failures) != 0)
(yes, this still doesn't make sense, but I can't be bothered to look
for something more appropriate) This is now 99 characters wide, and
it's the kind of code which doesn't gain in legibility by being broken
into multiple lines, especially if the indentation of the follow-on
lines is independent of the structure of the expression. bde has made
it clear he considers code more than 80 characters wide to be Evil.
Question: how many people still limit their editor windows to 80
characters?
Greg
--
See complete headers for address, home page and phone numbers
finger grog@lemis.com for PGP public key
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Fri Jan 29 16:48:53 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id QAA13949
for freebsd-current-outgoing; Fri, 29 Jan 1999 16:48:53 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from awfulhak.org (awfulhak.force9.co.uk [195.166.136.63])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA13937
for <current@FreeBSD.ORG>; Fri, 29 Jan 1999 16:48:49 -0800 (PST)
(envelope-from brian@Awfulhak.org)
Received: from keep.lan.Awfulhak.org (keep.lan.Awfulhak.org [172.16.0.8])
by awfulhak.org (8.8.8/8.8.8) with ESMTP id AAA15761;
Sat, 30 Jan 1999 00:42:14 GMT
(envelope-from brian@Awfulhak.org)
Received: from keep.lan.Awfulhak.org (localhost [127.0.0.1])
by keep.lan.Awfulhak.org (8.9.2/8.9.2) with ESMTP id AAA11904;
Sat, 30 Jan 1999 00:43:42 GMT
(envelope-from brian@keep.lan.Awfulhak.org)
Message-Id: <199901300043.AAA11904@keep.lan.Awfulhak.org>
X-Mailer: exmh version 2.0.2 2/24/98
To: Greg Lehey <grog@lemis.com>
cc: Poul-Henning Kamp <phk@critter.freebsd.dk>, current@FreeBSD.ORG
Subject: Re: indent (was: btokup().. patch to STYLE(9) (fwd))
In-reply-to: Your message of "Sat, 30 Jan 1999 10:15:52 +1030."
<19990130101552.U8473@freebie.lemis.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Sat, 30 Jan 1999 00:43:42 +0000
From: Brian Somers <brian@Awfulhak.org>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
> On Friday, 29 January 1999 at 9:13:39 +0100, Poul-Henning Kamp wrote:
> > It would also be nice if somebody whould coerse ident to DTRT.
>
> I've already mentioned that I have a version of indent with DABT.
> Shall I polish it up a bit?
You've got my vote.
> Greg
> --
> See complete headers for address, home page and phone numbers
> finger grog@lemis.com for PGP public key
--
Brian <brian@Awfulhak.org> <brian@FreeBSD.org> <brian@OpenBSD.org>
<http://www.Awfulhak.org>
Don't _EVER_ lose your sense of humour !
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Fri Jan 29 16:51:41 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id QAA14359
for freebsd-current-outgoing; Fri, 29 Jan 1999 16:51:41 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from ns.mt.sri.com (sri-gw.MT.net [206.127.105.141])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA14350
for <current@FreeBSD.ORG>; Fri, 29 Jan 1999 16:51:39 -0800 (PST)
(envelope-from nate@mt.sri.com)
Received: from mt.sri.com (rocky.mt.sri.com [206.127.76.100])
by ns.mt.sri.com (8.8.8/8.8.8) with SMTP id RAA00395;
Fri, 29 Jan 1999 17:51:29 -0700 (MST)
(envelope-from nate@rocky.mt.sri.com)
Received: by mt.sri.com (SMI-8.6/SMI-SVR4)
id RAA08644; Fri, 29 Jan 1999 17:51:26 -0700
Date: Fri, 29 Jan 1999 17:51:26 -0700
Message-Id: <199901300051.RAA08644@mt.sri.com>
From: Nate Williams <nate@mt.sri.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
To: Greg Lehey <grog@lemis.com>
Cc: Warner Losh <imp@village.org>, Julian Elischer <julian@whistle.com>,
current@FreeBSD.ORG
Subject: Re: btokup().. patch to STYLE(9) (fwd)
In-Reply-To: <19990130104943.W8473@freebie.lemis.com>
References: <Pine.BSF.4.05.9901290941240.304-100000@s204m82.isp.whistle.com>
<199901291802.LAA67403@harmony.village.org>
<19990130104943.W8473@freebie.lemis.com>
X-Mailer: VM 6.34 under 19.16 "Lille" XEmacs Lucid
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
> Question: how many people still limit their editor windows to 80
> characters?
Almost everyone in my group, since alot of development is done on
laptops with small screens, or done remotely.
Nate
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Fri Jan 29 17:11:03 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id RAA17037
for freebsd-current-outgoing; Fri, 29 Jan 1999 17:11:03 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA17017
for <current@FreeBSD.ORG>; Fri, 29 Jan 1999 17:10:54 -0800 (PST)
(envelope-from julian@whistle.com)
Received: (from daemon@localhost)
by alpo.whistle.com (8.8.5/8.8.5) id RAA02261;
Fri, 29 Jan 1999 17:07:09 -0800 (PST)
Received: from current1.whistle.com(207.76.205.22)
via SMTP by alpo.whistle.com, id smtpdwC2256; Sat Jan 30 01:07:04 1999
Date: Fri, 29 Jan 1999 17:07:00 -0800 (PST)
From: Julian Elischer <julian@whistle.com>
To: Greg Lehey <grog@lemis.com>
cc: Warner Losh <imp@village.org>, current@FreeBSD.ORG
Subject: Re: btokup().. patch to STYLE(9) (fwd)
In-Reply-To: <19990130104943.W8473@freebie.lemis.com>
Message-ID: <Pine.BSF.3.95.990129165654.17781C-100000@current1.whistle.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
On Sat, 30 Jan 1999, Greg Lehey wrote:
> of intelligibility. Consider one possible expansion
>
> if (((allocationfail | (IGNOREFAILUREMASK & (incount %
BLKSIZE))) ^ failures) != 0)
or
if (((allocationfail |
(IGNOREFAILUREMASK & (incount % BLKSIZE))) ^
failures) != 0)
>
> (yes, this still doesn't make sense, but I can't be bothered to look
> for something more appropriate) This is now 99 characters wide, and
> it's the kind of code which doesn't gain in legibility by being broken
> into multiple lines,
I'll say.. I tried several different splits.. the above is as good
as I can get it or me..
> especially if the indentation of the follow-on
> lines is independent of the structure of the expression. bde has made
> it clear he considers code more than 80 characters wide to be Evil.
> Question: how many people still limit their editor windows to 80
> characters?
I do
These cases are rather rare for me, but sometimes I have to split like
shwon. Sometimes I'll use a temp variable and sometimes I'll look to see
if a macro can be used if parts of the test are done more than once.
The trouble with > 80 chars is that the console is 80 chars wide.. :-)
julian
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Fri Jan 29 17:12:05 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id RAA17273
for freebsd-current-outgoing; Fri, 29 Jan 1999 17:12:05 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA17214
for <current@FreeBSD.ORG>; Fri, 29 Jan 1999 17:12:02 -0800 (PST)
(envelope-from dillon@apollo.backplane.com)
Received: (from dillon@localhost)
by apollo.backplane.com (8.9.2/8.9.1) id RAA86555;
Fri, 29 Jan 1999 17:11:58 -0800 (PST)
(envelope-from dillon)
Date: Fri, 29 Jan 1999 17:11:58 -0800 (PST)
From: Matthew Dillon <dillon@apollo.backplane.com>
Message-Id: <199901300111.RAA86555@apollo.backplane.com>
To: Nate Williams <nate@mt.sri.com>
Cc: Greg Lehey <grog@lemis.com>, Warner Losh <imp@village.org>,
Julian Elischer <julian@whistle.com>, current@FreeBSD.ORG
Subject: Re: btokup().. patch to STYLE(9) (fwd)
References: <Pine.BSF.4.05.9901290941240.304-100000@s204m82.isp.whistle.com>
<199901291802.LAA67403@harmony.village.org>
<19990130104943.W8473@freebie.lemis.com> <199901300051.RAA08644@mt.sri.com>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
:> Question: how many people still limit their editor windows to 80
:> characters?
:
:Almost everyone in my group, since alot of development is done on
:laptops with small screens, or done remotely.
:
:Nate
I do, because if use anything larger some lines will inevitably go
over and I'll get complaints.
I don't think there is anything we can do in regards to the 8-character
tabbing. I've used indents of 4 ( but hard tabs of 8 ) for everything
in my entire life *except* the FreeBSD code. Short of us converting the
entire codebase to indents of 4, which nobody wants to do, there would be
too much confusion mixing indentation amounts.
We have similar problems with variable naming. The kernel uses pre-caps
standards so variables are named mostly all in lower case using
underscores to demark words. At least half the programmers I know
tend to use lower-upper caps for local variables, like 'hashAry' and
upper-upper caps for globals, like 'HashAry', and more are converting
every day. But, for the same reasoning as with indentation, using
anything other then a lower-lower-underscore naming scheme for the kernel
would only add mass confusion. So we have to stick to the old naming
scheme.
Style and Semantics are more maleable issues since so many of the original
hard line 'standards' are just too obfuscated to continue to use. I think
( and ignoring the really dumb examples some people have been posting to
try to prove the opposite point ) that some parenthesization and bracing
*must* be allowed for clarification. People have been doing it for years
anyway, we might as well codify it or style(9) is in extreme danger of
simply being ignored by the people who don't care for it. Complaining
that programmers do dumb things with parens and braces is a comment on
the programmers and has nothing to do with the clarification.
Style(9) is over 4 years old -- even older. 4 years ago, there were 1/10
as many committers as there are now. Accomodations must be made.
-Matt
Matthew Dillon
<dillon@backplane.com>
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Fri Jan 29 17:23:35 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id RAA19191
for freebsd-current-outgoing; Fri, 29 Jan 1999 17:23:35 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA18999;
Fri, 29 Jan 1999 17:23:31 -0800 (PST)
(envelope-from mike@dingo.cdrom.com)
Received: from dingo.cdrom.com (localhost.cdrom.com [127.0.0.1])
by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id RAA03574;
Fri, 29 Jan 1999 17:19:14 -0800 (PST)
(envelope-from mike@dingo.cdrom.com)
Message-Id: <199901300119.RAA03574@dingo.cdrom.com>
X-Mailer: exmh version 2.0.2 2/24/98
To: Christopher Masto <chris@netmonger.net>
cc: hardware@FreeBSD.ORG, current@FreeBSD.ORG
Subject: Re: Network/ARP problem? Maybe pn driver?
In-reply-to: Your message of "Fri, 29 Jan 1999 17:39:22 EST."
<19990129173922.A29551@netmonger.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Fri, 29 Jan 1999 17:19:14 -0800
From: Mike Smith <mike@smith.net.au>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
> I hope I'm not just being really stupid, but I think there's a problem
> somewhere. If it's a configuration error on my part, then I think I'd
> better take a vacation, considering what my job is supposed to be.
>
> Anyway, I have a machine that is exhibiting a weird network problem.
> My guess is that ARP is not working, or perhaps something that ARP
> depends on (broadcasts?) is not working.
>
> The symptom is, quite simply, that computer A (this new one) is not
> able to communicate with any other computers.. until those other
> computers communicate with A.
This usually means that you have the netmask wrong, so broadcasts don't
work (wrong destination address). When someone else talks to the
misconfigured machine, they create an ARP cache entry, which allows the
victim to "see" them (until it times out).
--
\\ Sometimes you're ahead, \\ Mike Smith
\\ sometimes you're behind. \\ mike@smith.net.au
\\ The race is long, and in the \\ msmith@freebsd.org
\\ end it's only with yourself. \\ msmith@cdrom.com
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Fri Jan 29 17:23:56 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id RAA19270
for freebsd-current-outgoing; Fri, 29 Jan 1999 17:23:56 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from awfulhak.org (awfulhak.force9.co.uk [195.166.136.63])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA19246
for <current@FreeBSD.ORG>; Fri, 29 Jan 1999 17:23:48 -0800 (PST)
(envelope-from brian@Awfulhak.org)
Received: from keep.lan.Awfulhak.org (keep.lan.Awfulhak.org [172.16.0.8])
by awfulhak.org (8.8.8/8.8.8) with ESMTP id AAA16261;
Sat, 30 Jan 1999 00:56:31 GMT
(envelope-from brian@Awfulhak.org)
Received: from keep.lan.Awfulhak.org (localhost [127.0.0.1])
by keep.lan.Awfulhak.org (8.9.2/8.9.2) with ESMTP id AAA12120;
Sat, 30 Jan 1999 00:57:59 GMT
(envelope-from brian@keep.lan.Awfulhak.org)
Message-Id: <199901300057.AAA12120@keep.lan.Awfulhak.org>
X-Mailer: exmh version 2.0.2 2/24/98
To: Greg Lehey <grog@lemis.com>
cc: Warner Losh <imp@village.org>, Julian Elischer <julian@whistle.com>,
current@FreeBSD.ORG
Subject: Re: btokup().. patch to STYLE(9) (fwd)
In-reply-to: Your message of "Sat, 30 Jan 1999 10:49:43 +1030."
<19990130104943.W8473@freebie.lemis.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Sat, 30 Jan 1999 00:57:59 +0000
From: Brian Somers <brian@Awfulhak.org>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
> Question: how many people still limit their editor windows to 80
> characters?
I do :-/ So that I don't write code > 80 columns.
> Greg
--
Brian <brian@Awfulhak.org> <brian@FreeBSD.org> <brian@OpenBSD.org>
<http://www.Awfulhak.org>
Don't _EVER_ lose your sense of humour !
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Fri Jan 29 17:36:52 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id RAA21863
for freebsd-current-outgoing; Fri, 29 Jan 1999 17:36:52 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from cheddar.netmonger.net (cheddar.netmonger.net [209.54.21.140])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA21850;
Fri, 29 Jan 1999 17:36:46 -0800 (PST)
(envelope-from chris@cheddar.netmonger.net)
Received: (from chris@localhost)
by cheddar.netmonger.net (8.8.8/8.8.8) id UAA16694;
Fri, 29 Jan 1999 20:36:35 -0500 (EST)
Message-ID: <19990129203635.A13393@netmonger.net>
Date: Fri, 29 Jan 1999 20:36:35 -0500
From: Christopher Masto <chris@netmonger.net>
To: Bill Paul <wpaul@skynet.ctr.columbia.edu>
Cc: fenner@parc.xerox.com, current@FreeBSD.ORG, hardware@FreeBSD.ORG
Subject: Re: Network/ARP problem? Maybe pn driver?
References: <19990129180612.C3237@netmonger.net> <199901292328.SAA26781@skynet.ctr.columbia.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.91.1i
In-Reply-To: <199901292328.SAA26781@skynet.ctr.columbia.edu>; from Bill Paul on Fri, Jan 29, 1999 at 06:28:46PM -0500
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
On Fri, Jan 29, 1999 at 06:28:46PM -0500, Bill Paul wrote:
> > Hmm. Running tcpdump seems to make the problem go away. The ARP
> > replies show up immediately appear in the table. Clue.
>
> You should have tried that first.
I'm sorry. I ran tcpdump on a different host precisely because I
didn't want to interfere with the problem and make it harder to debug.
I overlooked the obvious.
> There's something I'd like you to try for me. (Don't delay in trying
> this; I've had a long string of people who appear suddenly, complain
> about a problem of some sort, then vanish before I can extract enough
> information from them to find a solution.)
I have been active with FreeBSD for the past four years. I have not
appeared suddenly, nor do I intend to vanish. The delay in responding
to your message is solely a result of a dinner party I had to attend.
> I was menaced by a bug in the PNIC's receive DMA operation which, according
> to all my tests, only appeared in promiscuous mode. I devised a workaround,
> however it's only enabled when the IFF_PROMISC flag is set on the
> interface. Running tcpdump (without the -p flag) places the interface
> in promiscuous mode and enables the workaround. Given what you've said,
> it's possible that we need to enable the workaround all the time, not
> just in promiscuous mode.
I would say you're quite right, considering the result of tcpdump -n -p arp:
20:32:36.302468 arp who-has 209.54.21.129 tell 209.54.21.233
20:32:36.303175 arp who-has 209.54.21.129 tell 209.54.21.233
20:32:37.310842 arp who-has 209.54.21.129 tell 209.54.21.233
20:32:37.311563 arp who-has 209.54.21.129 tell 209.54.21.233
20:32:38.320858 arp who-has 209.54.21.129 tell 209.54.21.233
20:32:38.321579 arp who-has 209.54.21.129 tell 209.54.21.233
20:32:39.330866 arp who-has 209.54.21.129 tell 209.54.21.233
20:32:39.331600 arp who-has 209.54.21.129 tell 209.54.21.233
20:32:40.340883 arp who-has 209.54.21.129 tell 209.54.21.233
20:32:40.341581 arp who-has 209.54.21.129 tell 209.54.21.233
Run again without -p, and voila:
20:33:30.232549 arp who-has 209.54.21.129 tell 209.54.21.233
20:33:30.233301 arp reply 209.54.21.129 is-at 0:e0:b0:e2:bc:79
> Do me the following:
>
> - Bring up /sys/pci/if_pn.c in your favorite editor.
[...]
> Compile a new kernel with this change and see if the problem persists.
> Report back your findings (one way or the other) so that I'll know if
> I should modify the code in the repository.
I will have the results for you by tomorrow. Thank you very much for
your assistance.
--
Christopher Masto Director of Operations NetMonger Communications
chris@netmonger.net info@netmonger.net http://www.netmonger.net
"Good tools allow users to do stupid things." -- Clay Shirky
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Fri Jan 29 18:20:45 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id SAA27276
for freebsd-current-outgoing; Fri, 29 Jan 1999 18:20:45 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from rip.psg.com (rip.psg.com [147.28.0.39])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA27271
for <freebsd-current@freebsd.org>; Fri, 29 Jan 1999 18:20:44 -0800 (PST)
(envelope-from randy@psg.com)
Received: from localhost (1631 bytes) by rip.psg.com
via sendmail with P:stdio/R:inet_resolve/T:smtp
(sender: <randy>) (ident <randy> using unix)
id <m106Q1b-0008G4C@rip.psg.com>
for <freebsd-current@freebsd.org>; Fri, 29 Jan 1999 18:20:43 -0800 (PST)
(Smail-3.2.0.101 1997-Dec-17 #1 built 1998-Oct-13)
Message-Id: <m106Q1b-0008G4C@rip.psg.com>
Date: Fri, 29 Jan 1999 18:20:43 -0800 (PST)
From: Randy Bush <randy@psg.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
To: freebsd-current@FreeBSD.ORG
Subject: 4.0-current emacs locks up in startup
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
4.0-current of a few days ago.
rebuilt XFree and a bunch of other stuff
build emacs or emacs20
either runs fine in an x-term
either freezes when started with its own window
it puts up the window
paints the grey menu bar
freeze
emacs20 stack at freeze
#0 0x282c4824 in select ()
#1 0x28203e31 in _XWaitForReadable ()
#2 0x282044f4 in _XRead ()
#3 0x28204d6a in _XReply ()
#4 0x2820194b in XSync ()
#5 0x8089f3e in x_sync ()
#6 0x80826d2 in x_make_frame_visible ()
#7 0x805246f in Fmake_frame_visible ()
#8 0x80e295a in Ffuncall ()
#9 0x810740e in Fbyte_code ()
#10 0x80e2eac in funcall_lambda ()
#11 0x80e2aba in Ffuncall ()
#12 0x810740e in Fbyte_code ()
#13 0x80e2eac in funcall_lambda ()
#14 0x80e2aba in Ffuncall ()
#15 0x810740e in Fbyte_code ()
#16 0x80e2eac in funcall_lambda ()
#17 0x80e2aba in Ffuncall ()
#18 0x810740e in Fbyte_code ()
#19 0x80e2eac in funcall_lambda ()
#20 0x80e2aba in Ffuncall ()
#21 0x810740e in Fbyte_code ()
#22 0x80e2eac in funcall_lambda ()
#23 0x80e2c52 in apply_lambda ()
#24 0x80e1edd in Feval ()
#25 0x809134e in top_level_2 ()
#26 0x80e0ea0 in internal_condition_case ()
#27 0x8091375 in top_level_1 ()
#28 0x80e0b42 in internal_catch ()
#29 0x80912d6 in command_loop ()
#30 0x8090f67 in recursive_edit_1 ()
#31 0x809104d in Frecursive_edit ()
#32 0x80902ab in main ()
#33 0x804d519 in _start ()
randy
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Fri Jan 29 18:33:41 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id SAA28687
for freebsd-current-outgoing; Fri, 29 Jan 1999 18:33:41 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from khavrinen.lcs.mit.edu (khavrinen.lcs.mit.edu [18.24.4.193])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA28682
for <current@FreeBSD.ORG>; Fri, 29 Jan 1999 18:33:40 -0800 (PST)
(envelope-from wollman@khavrinen.lcs.mit.edu)
Received: (from wollman@localhost)
by khavrinen.lcs.mit.edu (8.9.1/8.9.1) id VAA01228;
Fri, 29 Jan 1999 21:33:29 -0500 (EST)
(envelope-from wollman)
Date: Fri, 29 Jan 1999 21:33:29 -0500 (EST)
From: Garrett Wollman <wollman@khavrinen.lcs.mit.edu>
Message-Id: <199901300233.VAA01228@khavrinen.lcs.mit.edu>
To: Greg Lehey <grog@lemis.com>
Cc: Warner Losh <imp@village.org>, Julian Elischer <julian@whistle.com>,
current@FreeBSD.ORG
Subject: Re: btokup().. patch to STYLE(9) (fwd)
In-Reply-To: <19990130104943.W8473@freebie.lemis.com>
References: <Pine.BSF.4.05.9901290941240.304-100000@s204m82.isp.whistle.com>
<199901291802.LAA67403@harmony.village.org>
<19990130104943.W8473@freebie.lemis.com>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
<<On Sat, 30 Jan 1999 10:49:43 +1030, Greg Lehey <grog@lemis.com> said:
> Question: how many people still limit their editor windows to 80
> characters?
Probably almost anyone who uses the default settings.
Many people like to be able to see more than one thing on the desktop
at a time. Even with a 1280x1024 display on a good 19-inch monitor, I
still can't fit two 80-character windows side-by-side if I want to be
able to read the font.
That's ignoring other issues like trying to print such documents. HP
printers don't do auto-wrap (and even if they did it wouldn't respect
any semantic value in the code). Before XFree86 3.3.3 came out, my
laptop could not run X -- presto, automatic 80-character limitation.
-GAWollman
--
Garrett A. Wollman | O Siem / We are all family / O Siem / We're all the same
wollman@lcs.mit.edu | O Siem / The fires of freedom
Opinions not those of| Dance in the burning flame
MIT, LCS, CRS, or NSA| - Susan Aglukark and Chad Irschick
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Fri Jan 29 18:43:24 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id SAA00151
for freebsd-current-outgoing; Fri, 29 Jan 1999 18:43:24 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from k6n1.znh.org ([207.109.235.38])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA00146
for <current@freebsd.org>; Fri, 29 Jan 1999 18:43:21 -0800 (PST)
(envelope-from zach@uffdaonline.net)
Received: (from zach@localhost)
by k6n1.znh.org (8.9.1/8.9.1) id CAA73886;
Sat, 30 Jan 1999 02:45:21 GMT
(envelope-from zach)
Message-ID: <19990129204521.A73046@znh.org>
Date: Fri, 29 Jan 1999 20:45:21 -0600
From: Zach Heilig <zach@uffdaonline.net>
To: Warner Losh <imp@village.org>, Julian Elischer <julian@whistle.com>
Cc: current@FreeBSD.ORG
Subject: Re: btokup().. patch to STYLE(9) (fwd)
References: <Pine.BSF.4.05.9901290941240.304-100000@s204m82.isp.whistle.com> <199901291802.LAA67403@harmony.village.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.93.2i
In-Reply-To: <199901291802.LAA67403@harmony.village.org>; from Warner Losh on Fri, Jan 29, 1999 at 11:02:48AM -0700
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
On Fri, Jan 29, 1999 at 11:02:48AM -0700, Warner Losh wrote:
> Yes. I agree with that.
> if (a | b & c % d ^ e)
> should have been written as:
> if (((a | (b & (c % d))) ^ e) != 0)
I don't know why I'm getting into this, but to prove the point that this
expression takes careful thought, it is:
(a | ((b & (c % d)) ^ e))
(^ is higher precedence than | , according to /usr/share/misc/operator).
--
Zach Heilig <zach@uffdaonline.net> / Zach Heilig <zach@gaffaneys.com>
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Fri Jan 29 19:42:52 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id TAA06588
for freebsd-current-outgoing; Fri, 29 Jan 1999 19:42:52 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA06577;
Fri, 29 Jan 1999 19:42:46 -0800 (PST)
(envelope-from jkh@zippy.cdrom.com)
Received: from zippy.cdrom.com (localhost.cdrom.com [127.0.0.1])
by zippy.cdrom.com (8.9.2/8.9.1) with ESMTP id TAA86435;
Fri, 29 Jan 1999 19:43:17 -0800 (PST)
To: Wilko Bulte <wilko@yedi.iaf.nl>
cc: gpalmer@FreeBSD.ORG, freebsd-current@FreeBSD.ORG
Subject: Re: make release - Party Time! (but not for the AXP)
In-reply-to: Your message of "Fri, 29 Jan 1999 19:01:42 +0100."
<199901291801.TAA01074@yedi.iaf.nl>
Date: Fri, 29 Jan 1999 19:43:17 -0800
Message-ID: <86431.917667797@zippy.cdrom.com>
From: "Jordan K. Hubbard" <jkh@zippy.cdrom.com>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
> Sidestepping a bit: will there be AXP specific CDROMs in the WC
> CDROM distribution?
"Probably" - it's just far too early to say.
- Jordan
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Fri Jan 29 19:50:09 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id TAA07689
for freebsd-current-outgoing; Fri, 29 Jan 1999 19:50:09 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from rover.village.org (rover.village.org [204.144.255.49])
by hub.freebsd.org (8.8.8/8.8.8) with SMTP id TAA07664
for <current@freebsd.org>; Fri, 29 Jan 1999 19:50:05 -0800 (PST)
(envelope-from imp@village.org)
Received: from harmony [10.0.0.6]
by rover.village.org with esmtp (Exim 1.71 #1)
id 106RPx-0006an-00; Fri, 29 Jan 1999 20:49:57 -0700
Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.1/8.8.3) with ESMTP id UAA72862; Fri, 29 Jan 1999 20:50:07 -0700 (MST)
Message-Id: <199901300350.UAA72862@harmony.village.org>
To: Matthew Dillon <dillon@apollo.backplane.com>
Subject: Re: c_caddr_t
Cc: Bruce Evans <bde@zeta.org.au>, current@FreeBSD.ORG
In-reply-to: Your message of "Fri, 29 Jan 1999 15:17:26 PST."
<199901292317.PAA84062@apollo.backplane.com>
References: <199901292317.PAA84062@apollo.backplane.com> <99Jan29.145213pst.177534@crevenia.parc.xerox.com> <19990129180612.C3237@netmonger.net>
Date: Fri, 29 Jan 1999 20:50:06 -0700
From: Warner Losh <imp@village.org>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
In message <199901292317.PAA84062@apollo.backplane.com> Matthew Dillon writes:
: bde, I don't mind you removing c_caddr_t as long as you also fix the
: warnings that it fixed, but it would have been appropriate to notify
: me of what you were doing rather then slamming me in the CVS commit
: comments. I find that sort of behavior to be highly inappropriate.
Matt, get over it. bde didn't slam *YOU* in the commit messages. You
were never mentioned personally. Also, taking your complaint to
-current is not proper proceedure for handling grievances.
Warner
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Fri Jan 29 19:59:45 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id TAA08605
for freebsd-current-outgoing; Fri, 29 Jan 1999 19:59:45 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA08599
for <current@FreeBSD.ORG>; Fri, 29 Jan 1999 19:59:44 -0800 (PST)
(envelope-from jkh@zippy.cdrom.com)
Received: from zippy.cdrom.com (localhost.cdrom.com [127.0.0.1])
by zippy.cdrom.com (8.9.2/8.9.1) with ESMTP id UAA86646;
Fri, 29 Jan 1999 20:00:10 -0800 (PST)
To: Matthew Dillon <dillon@apollo.backplane.com>
cc: Bruce Evans <bde@zeta.org.au>, current@FreeBSD.ORG
Subject: Re: c_caddr_t
In-reply-to: Your message of "Fri, 29 Jan 1999 15:17:26 PST."
<199901292317.PAA84062@apollo.backplane.com>
Date: Fri, 29 Jan 1999 20:00:10 -0800
Message-ID: <86642.917668810@zippy.cdrom.com>
From: "Jordan K. Hubbard" <jkh@zippy.cdrom.com>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
It's also something that bde has slammed more than a few other people
on when they do such things ["Commit messages are not for this
purpose!"] so he of all people ought to know better (stern look at
Bruce for getting hypocritical in his old age :).
- Jordan
> bde, I don't mind you removing c_caddr_t as long as you also fix the
> warnings that it fixed, but it would have been appropriate to notify
> me of what you were doing rather then slamming me in the CVS commit
> comments. I find that sort of behavior to be highly inappropriate.
>
> -Matt
> Matthew Dillon
> <dillon@backplane.com>
>
> To Unsubscribe: send mail to majordomo@FreeBSD.org
> with "unsubscribe freebsd-current" in the body of the message
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Fri Jan 29 20:05:39 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id UAA09182
for freebsd-current-outgoing; Fri, 29 Jan 1999 20:05:39 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA09177
for <current@FreeBSD.ORG>; Fri, 29 Jan 1999 20:05:37 -0800 (PST)
(envelope-from jkh@zippy.cdrom.com)
Received: from zippy.cdrom.com (localhost.cdrom.com [127.0.0.1])
by zippy.cdrom.com (8.9.2/8.9.1) with ESMTP id UAA86712;
Fri, 29 Jan 1999 20:05:57 -0800 (PST)
To: Warner Losh <imp@village.org>
cc: Matthew Dillon <dillon@apollo.backplane.com>,
Bruce Evans <bde@zeta.org.au>, current@FreeBSD.ORG
Subject: Re: c_caddr_t
In-reply-to: Your message of "Fri, 29 Jan 1999 20:50:06 MST."
<199901300350.UAA72862@harmony.village.org>
Date: Fri, 29 Jan 1999 20:05:56 -0800
Message-ID: <86708.917669156@zippy.cdrom.com>
From: "Jordan K. Hubbard" <jkh@zippy.cdrom.com>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
> Matt, get over it. bde didn't slam *YOU* in the commit messages. You
> were never mentioned personally. Also, taking your complaint to
> -current is not proper proceedure for handling grievances.
While this is true, I think the overall point he made was reasonable
considering how often Bruce has corrected others for "needless
commentary" in the commit logs and I'd be happy to see everyone follow
their own rules at the very least. :-)
- Jordan
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Fri Jan 29 20:14:45 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id UAA10230
for freebsd-current-outgoing; Fri, 29 Jan 1999 20:14:45 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from rover.village.org (rover.village.org [204.144.255.49])
by hub.freebsd.org (8.8.8/8.8.8) with SMTP id UAA10218
for <current@freebsd.org>; Fri, 29 Jan 1999 20:14:41 -0800 (PST)
(envelope-from imp@village.org)
Received: from harmony [10.0.0.6]
by rover.village.org with esmtp (Exim 1.71 #1)
id 106Rnq-0006bX-00; Fri, 29 Jan 1999 21:14:38 -0700
Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.1/8.8.3) with ESMTP id VAA73147; Fri, 29 Jan 1999 21:14:48 -0700 (MST)
Message-Id: <199901300414.VAA73147@harmony.village.org>
To: "Jordan K. Hubbard" <jkh@zippy.cdrom.com>
Subject: Re: c_caddr_t
Cc: Matthew Dillon <dillon@apollo.backplane.com>,
Bruce Evans <bde@zeta.org.au>, current@FreeBSD.ORG
In-reply-to: Your message of "Fri, 29 Jan 1999 20:05:56 PST."
<86708.917669156@zippy.cdrom.com>
References: <86708.917669156@zippy.cdrom.com>
Date: Fri, 29 Jan 1999 21:14:48 -0700
From: Warner Losh <imp@village.org>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
In message <86708.917669156@zippy.cdrom.com> "Jordan K. Hubbard" writes:
: While this is true, I think the overall point he made was reasonable
: considering how often Bruce has corrected others for "needless
: commentary" in the commit logs and I'd be happy to see everyone follow
: their own rules at the very least. :-)
I object strongly to false accusations being bandied about in a public
forum. If Matt wished to make this point, he should have done so in a
less inflamitory manner especially in such a public forum. That's
been a problem lately in this forum, and I cannot express easily in
words how strongly I object to it.
Warner
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Fri Jan 29 20:26:44 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id UAA11463
for freebsd-current-outgoing; Fri, 29 Jan 1999 20:26:44 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA11458
for <current@FreeBSD.ORG>; Fri, 29 Jan 1999 20:26:42 -0800 (PST)
(envelope-from jkh@zippy.cdrom.com)
Received: from zippy.cdrom.com (localhost.cdrom.com [127.0.0.1])
by zippy.cdrom.com (8.9.2/8.9.1) with ESMTP id UAA86834;
Fri, 29 Jan 1999 20:27:04 -0800 (PST)
To: Warner Losh <imp@village.org>
cc: Matthew Dillon <dillon@apollo.backplane.com>,
Bruce Evans <bde@zeta.org.au>, current@FreeBSD.ORG
Subject: Re: c_caddr_t
In-reply-to: Your message of "Fri, 29 Jan 1999 21:14:48 MST."
<199901300414.VAA73147@harmony.village.org>
Date: Fri, 29 Jan 1999 20:27:04 -0800
Message-ID: <86830.917670424@zippy.cdrom.com>
From: "Jordan K. Hubbard" <jkh@zippy.cdrom.com>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
> forum. If Matt wished to make this point, he should have done so in a
> less inflamitory manner especially in such a public forum. That's
> been a problem lately in this forum, and I cannot express easily in
> words how strongly I object to it.
Fair enough - maybe everyone involved should just take their chill
pills.
To put it in a somewhat larger context, none of the things which have
seen people blow up recently have been all that important, and to get
people freaking out in my mailbox over the -Wall changes or a change
to style(9) is pretty damned silly. This is one aspect to John
Birrell's accusation that our heads have gotten firmly stuck up a
certain orifice that I have to agree with. We should certainly
continue to be conservative when it comes to making major
architectural changes, but this constant griping over cosmetic stuff
isn't serving anyone's purposes at all.
- Jordan
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Fri Jan 29 22:37:25 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id WAA20239
for freebsd-current-outgoing; Fri, 29 Jan 1999 22:37:25 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from atdot.dotat.org (atdot.dotat.org [203.23.150.35])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA20231
for <current@freebsd.org>; Fri, 29 Jan 1999 22:37:22 -0800 (PST)
(envelope-from newton@atdot.dotat.org)
Received: (from newton@localhost) by atdot.dotat.org (8.9.2/8.7) id RAA20114 for current@freebsd.org; Sat, 30 Jan 1999 17:06:18 +1030 (CST)
Date: Sat, 30 Jan 1999 17:06:18 +1030 (CST)
From: Mark Newton <newton@atdot.dotat.org>
Message-Id: <199901300636.RAA20114@atdot.dotat.org>
To: current@FreeBSD.ORG
Subject: SysVR4 emulator
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
I've just committed the FreeBSD svr4 emulator, which has been built
by adapting the stirling work of Christos Zoulas from the NetBSD project
to FreeBSD.
I hope I haven't left anything out or broken the world, but I'm sure
I'll hear about it if I have :-)
To use it:
1. Add "pseudo-device streams" to your kernel config file and rebuild,
reboot.
2. Build and install the svr4 module in /sys/modules/svr4
3. Type "svr4" to start it up.
4. Grab compat_sol26.tar.gz or compat_svr4.tar.gz from
http://www.freebsd.org/~newton/freebsd-svr4 and install them in
/compat/svr4
5. Run "sh SVR4_MAKEDEV all" in /compat/svr4/dev
6. Mount a Solaris/x86 CD-ROM on /cdrom
7. Brand any executables you want to run
8. See if they work.
It's early days yet, folks -- You'll probably have trouble getting 100%
functionality out of most things (specifically, poll() on a socket doesn't
look like it works at the moment, so Netscape doesn't work (among other
things)). Patches will be appreciated.
I'll be putting the compat_*.tar.gz archives into /usr/share/examples
with a README file RSN (I haven't written a Makefile for them yet,
though, hence the delay).
Regards,
- mark
--------------------------------------------------------------------
I tried an internal modem, newton@atdot.dotat.org
but it hurt when I walked. Mark Newton
----- Voice: +61-4-1958-3414 ------------- Fax: +61-8-83034403 -----
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Fri Jan 29 22:44:04 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id WAA21111
for freebsd-current-outgoing; Fri, 29 Jan 1999 22:44:04 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from rover.village.org (rover.village.org [204.144.255.49])
by hub.freebsd.org (8.8.8/8.8.8) with SMTP id WAA21104
for <current@freebsd.org>; Fri, 29 Jan 1999 22:44:02 -0800 (PST)
(envelope-from imp@village.org)
Received: from harmony [10.0.0.6]
by rover.village.org with esmtp (Exim 1.71 #1)
id 106U8O-0006ee-00; Fri, 29 Jan 1999 23:44:00 -0700
Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.1/8.8.3) with ESMTP id XAA74217; Fri, 29 Jan 1999 23:44:13 -0700 (MST)
Message-Id: <199901300644.XAA74217@harmony.village.org>
To: Mark Newton <newton@atdot.dotat.org>
Subject: Re: SysVR4 emulator
Cc: current@FreeBSD.ORG
In-reply-to: Your message of "Sat, 30 Jan 1999 17:06:18 +1030."
<199901300636.RAA20114@atdot.dotat.org>
References: <199901300636.RAA20114@atdot.dotat.org>
Date: Fri, 29 Jan 1999 23:44:12 -0700
From: Warner Losh <imp@village.org>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
In message <199901300636.RAA20114@atdot.dotat.org> Mark Newton writes:
: It's early days yet, folks -- You'll probably have trouble getting 100%
: functionality out of most things (specifically, poll() on a socket doesn't
: look like it works at the moment, so Netscape doesn't work (among other
: things)). Patches will be appreciated.
Any idea if wabi works yet?
Warner
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Fri Jan 29 22:45:15 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id WAA21253
for freebsd-current-outgoing; Fri, 29 Jan 1999 22:45:15 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from rebma.ghostwheel.com (rebma.ghostwheel.com [207.201.56.159])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA21248
for <freebsd-current@freebsd.org>; Fri, 29 Jan 1999 22:45:13 -0800 (PST)
(envelope-from fbsd-cur@ghostwheel.com)
Received: from avalon (avalon [207.201.56.88])
by rebma.ghostwheel.com (8.8.8/8.8.8) with SMTP id WAA14709
for <freebsd-current@freebsd.org>; Fri, 29 Jan 1999 22:45:21 -0800 (PST)
(envelope-from fbsd-cur@ghostwheel.com)
Message-Id: <4.1.19990129224142.0098b100@pop2.ghostwheel.com>
X-Sender: fbsd-cur@pop2.ghostwheel.com (Unverified)
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.1
Date: Fri, 29 Jan 1999 22:41:52 -0800
To: freebsd-current@FreeBSD.ORG
From: Chris Knight <fbsd-cur@ghostwheel.com>
Subject: Why doesn't Vinum start automatically?
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
There have been changes to rc and rc.conf lately to autostart Vinum. But
on my system it does not auto load at start and I wind up manually loading
the module, reading the config and mounting the volume. Any help if
figuring out why this is not working would be appreciated.
rc.conf now sets a variable with the drives from to read the config:
vinum_slices="/dev/da1 /dev/da2 /dev/da3 /dev/da4"
and rc checks for this variable and loads vinum if it is set:
if [ -n "$vinum_slices" ]; then
if [ -r /modules/vinum.ko ]; then # jkh paranoia
kldload vinum
vinum read $vinum_slices
else
echo "Can't find /modules/vinum.ko"
fi
fi
Any ideas why this isn't working? Is it working in -current but not -stable?
-ck
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Fri Jan 29 22:48:01 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id WAA21366
for freebsd-current-outgoing; Fri, 29 Jan 1999 22:46:38 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from atdot.dotat.org (atdot.dotat.org [203.23.150.35])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA21354
for <current@FreeBSD.ORG>; Fri, 29 Jan 1999 22:46:35 -0800 (PST)
(envelope-from newton@atdot.dotat.org)
Received: (from newton@localhost) by atdot.dotat.org (8.9.2/8.7) id RAA20201; Sat, 30 Jan 1999 17:15:25 +1030 (CST)
From: Mark Newton <newton@atdot.dotat.org>
Message-Id: <199901300645.RAA20201@atdot.dotat.org>
Subject: Re: SysVR4 emulator
To: imp@village.org (Warner Losh)
Date: Sat, 30 Jan 1999 17:15:25 +1030 (CST)
Cc: current@FreeBSD.ORG
In-Reply-To: <199901300644.XAA74217@harmony.village.org> from "Warner Losh" at Jan 29, 99 11:44:12 pm
X-Mailer: ELM [version 2.4 PL25]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
Warner Losh wrote:
> In message <199901300636.RAA20114@atdot.dotat.org> Mark Newton writes:
> : It's early days yet, folks -- You'll probably have trouble getting 100%
> : functionality out of most things (specifically, poll() on a socket doesn't
> : look like it works at the moment, so Netscape doesn't work (among other
> : things)). Patches will be appreciated.
>
> Any idea if wabi works yet?
Pretty much guaranteed that it won't: I've wrapped all the LDT-manipulation
stuff in #ifdef(NOTYET) for the time being (I've been more interested in
getting it ported than working at the differences between NetBSD and
FreeBSD LDT handling. Doing signal context was bad enough (and I'm
not sure that I've done that right either)).
Perhaps an enteprising contributor can put that on a TO-DO list
somewhere :-)
- mark
--------------------------------------------------------------------
I tried an internal modem, newton@atdot.dotat.org
but it hurt when I walked. Mark Newton
----- Voice: +61-4-1958-3414 ------------- Fax: +61-8-83034403 -----
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Fri Jan 29 23:30:47 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id XAA25520
for freebsd-current-outgoing; Fri, 29 Jan 1999 23:30:47 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from relay.nuxi.com ([169.237.7.38])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA25514
for <current@freeBSD.org>; Fri, 29 Jan 1999 23:30:45 -0800 (PST)
(envelope-from obrien@NUXI.com)
Received: from dragon.nuxi.com (d60-077.leach.ucdavis.edu [169.237.60.77])
by relay.nuxi.com (8.9.1/8.9.1) with ESMTP id XAA47292;
Fri, 29 Jan 1999 23:30:35 -0800 (PST)
(envelope-from obrien@dragon.nuxi.com)
Received: (from obrien@localhost)
by dragon.nuxi.com (8.9.1/8.9.1) id HAA72344;
Sat, 30 Jan 1999 07:30:34 GMT
(envelope-from obrien)
Date: Fri, 29 Jan 1999 23:30:34 -0800
From: "David O'Brien" <obrien@NUXI.com>
To: Ustimenko Semen <semen@iclub.nsu.ru>
Cc: current@FreeBSD.ORG
Subject: Re: About to commit NTFS driver
Message-ID: <19990129233034.A40830@dragon.nuxi.com>
Reply-To: obrien@NUXI.com
References: <199901290050.QAA01195@dingo.cdrom.com> <Pine.BSF.3.96.990129220714.22530D-100000@iclub.nsu.ru>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.95i
In-Reply-To: <Pine.BSF.3.96.990129220714.22530D-100000@iclub.nsu.ru>; from Ustimenko Semen on Fri, Jan 29, 1999 at 10:12:52PM +0600
X-Operating-System: FreeBSD 3.0-CURRENT
Organization: The NUXI BSD group
X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A
X-Pgp-Keyid: 34F9F9D5
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
> Looks like not. David O'Brien have just showed me points
> to fix. May be he will be?
Willing to, but I am waiting until I can compile it and test it under
4.0-CURRENT. (esp. since that is where it will have to be added first)
--
-- David (obrien@NUXI.com -or- obrien@FreeBSD.org)
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Fri Jan 29 23:31:24 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id XAA25579
for freebsd-current-outgoing; Fri, 29 Jan 1999 23:31:24 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from atdot.dotat.org (atdot.dotat.org [203.23.150.35])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA25569
for <current@freebsd.org>; Fri, 29 Jan 1999 23:31:17 -0800 (PST)
(envelope-from newton@atdot.dotat.org)
Received: (from newton@localhost) by atdot.dotat.org (8.9.2/8.7) id SAA20522 for current@freebsd.org; Sat, 30 Jan 1999 18:00:15 +1030 (CST)
Date: Sat, 30 Jan 1999 18:00:15 +1030 (CST)
From: Mark Newton <newton@atdot.dotat.org>
Message-Id: <199901300730.SAA20522@atdot.dotat.org>
To: current@FreeBSD.ORG
Subject: *1 routines in /sys/kern
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
We currently have routines like fork1() and killpg1() in /sys/kern/*
to implement generic functionality for actions with more than one
"front-end".
NetBSD has done something similar for signals, so that emulators
with non-BSD signal semantics can implement their way of doing things
as an emulator-specific front-end without polluting the rest of the
kernel.
The SysVR4 emulator started using that stuff fairly heavily in NetBSD
from November last year. I haven't merged those changes into the FreeBSD
version because, well, the *1 routines aren't there yet.
I wanted to get a bit of discussion going before ploughing ahead with
making the change because I'm uneasy about kernel-wide changes simply
to support an emulator (unstaticizing a function here and there is one
thing, completely altering the implementation architecture of something
that already works is something else entirely).
If I split sigaction(), sigsuspend(), sigpending(), sigprocmask() and
sigaltstack() into front-end and back-end pieces a-la NetBSD so that
emulator-specific signal semantics can be imposed without totally
duplicating those routines inside the emulator (like I did with
sendit() and recvit() for socket I/O), will anyone complain?
- mark
--------------------------------------------------------------------
I tried an internal modem, newton@atdot.dotat.org
but it hurt when I walked. Mark Newton
----- Voice: +61-4-1958-3414 ------------- Fax: +61-8-83034403 -----
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Fri Jan 29 23:59:43 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id XAA27196
for freebsd-current-outgoing; Fri, 29 Jan 1999 23:59:43 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from rover.village.org (rover.village.org [204.144.255.49])
by hub.freebsd.org (8.8.8/8.8.8) with SMTP id XAA27189
for <current@freebsd.org>; Fri, 29 Jan 1999 23:59:41 -0800 (PST)
(envelope-from imp@village.org)
Received: from harmony [10.0.0.6]
by rover.village.org with esmtp (Exim 1.71 #1)
id 106VJb-0006gR-00; Sat, 30 Jan 1999 00:59:39 -0700
Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.1/8.8.3) with ESMTP id AAA74734; Sat, 30 Jan 1999 00:59:52 -0700 (MST)
Message-Id: <199901300759.AAA74734@harmony.village.org>
To: Zach Heilig <zach@uffdaonline.net>
Subject: Re: btokup().. patch to STYLE(9) (fwd)
Cc: Julian Elischer <julian@whistle.com>, current@FreeBSD.ORG
In-reply-to: Your message of "Fri, 29 Jan 1999 20:45:21 CST."
<19990129204521.A73046@znh.org>
References: <19990129204521.A73046@znh.org> <Pine.BSF.4.05.9901290941240.304-100000@s204m82.isp.whistle.com> <199901291802.LAA67403@harmony.village.org>
Date: Sat, 30 Jan 1999 00:59:52 -0700
From: Warner Losh <imp@village.org>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
In message <19990129204521.A73046@znh.org> Zach Heilig writes:
: On Fri, Jan 29, 1999 at 11:02:48AM -0700, Warner Losh wrote:
: > Yes. I agree with that.
: > if (a | b & c % d ^ e)
: > should have been written as:
: > if (((a | (b & (c % d))) ^ e) != 0)
:
: I don't know why I'm getting into this, but to prove the point that this
: expression takes careful thought, it is:
: (a | ((b & (c % d)) ^ e))
: (^ is higher precedence than | , according to /usr/share/misc/operator).
You see my point exactly. The explicit parens are what is intended in
this example. How easy it is to get it wrong and how hard it is to
prove to be right when things get that mixed up and crazy :-)
Warner
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Sat Jan 30 00:12:22 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id AAA28961
for freebsd-current-outgoing; Sat, 30 Jan 1999 00:12:22 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA28956
for <current@FreeBSD.ORG>; Sat, 30 Jan 1999 00:12:21 -0800 (PST)
(envelope-from dillon@apollo.backplane.com)
Received: (from dillon@localhost)
by apollo.backplane.com (8.9.2/8.9.1) id AAA88999;
Sat, 30 Jan 1999 00:12:20 -0800 (PST)
(envelope-from dillon)
Date: Sat, 30 Jan 1999 00:12:20 -0800 (PST)
From: Matthew Dillon <dillon@apollo.backplane.com>
Message-Id: <199901300812.AAA88999@apollo.backplane.com>
To: current@FreeBSD.ORG
Subject: Tentitive fix for vn device
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
This is a tentitive fix for the vn device problems reported earlier.
It has not been well tested. Basically, the vn device tries to
do something different for B_PAGING bp's to get around potential
low-memory deadlocks. Previously this only applied to paging/swapping,
and the swapper doesn't care about b_resid. However, part of the VM update
in -4.x extends this flag for use in vm_fault paging and other similar
situations. The VN code takes an alternate path for B_PAGING which has
not been well tested due to it being previously restricted to swapper
requested only. There could be more bugs in the section of vn. I'll
run more sophisticated tests ( buildworlds and ports builds and such )
next week, replacing my MFS testbed with a VN testbed.
-Matt
Matthew Dillon
<dillon@backplane.com>
Index: vn.c
===================================================================
RCS file: /home/ncvs/src/sys/dev/vn/vn.c,v
retrieving revision 1.73
diff -u -r1.73 vn.c
--- vn.c 1999/01/23 00:28:56 1.73
+++ vn.c 1999/01/30 08:03:41
@@ -411,6 +411,7 @@
addr += sz;
resid -= sz;
}
+ bp->b_resid = resid;
biodone(bp);
putvnbuf(nbp);
}
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Sat Jan 30 00:48:20 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id AAA02629
for freebsd-current-outgoing; Sat, 30 Jan 1999 00:48:20 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from ceia.nordier.com (m1-35-dbn.dial-up.net [196.34.155.35])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA02623
for <freebsd-current@FreeBSD.ORG>; Sat, 30 Jan 1999 00:48:16 -0800 (PST)
(envelope-from rnordier@nordier.com)
Received: (from rnordier@localhost) by ceia.nordier.com (8.8.7/8.6.12) id KAA00258; Sat, 30 Jan 1999 10:47:12 +0200 (SAT)
From: Robert Nordier <rnordier@nordier.com>
Message-Id: <199901300847.KAA00258@ceia.nordier.com>
Subject: Re: Reading a text file with BTX
In-Reply-To: <36B19501.B55A19D0@newsguy.com> from "Daniel C. Sobral" at "Jan 29, 99 08:01:21 pm"
To: dcs@newsguy.com (Daniel C. Sobral)
Date: Sat, 30 Jan 1999 10:47:09 +0200 (SAT)
Cc: freebsd-current@FreeBSD.ORG
X-Mailer: ELM [version 2.4ME+ PL31 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
Daniel C. Sobral wrote:
> Robert Nordier wrote:
> >
> > The boot manager menu, for example
> >
> > F1 FreeBSD
> > F2 UNIX
> > F5 Drive 1
> >
> > Default: F1
>
> Y'know, in my computer that F5 is "Drive 0", and the system will not
> boot unless I select it first. Selecting it, makes the OSes boot and
> F5 disappear.
Try the following patch. You can use the utility
http://www.freebsd.org/~rnordier/boot0inst-1.0.2.tar.gz
to install it.
Index: boot0.s
===================================================================
RCS file: /home/ncvs/src/sys/boot/i386/boot0/boot0.s,v
retrieving revision 1.6
diff -u -r1.6 boot0.s
--- boot0.s 1998/12/05 11:58:33 1.6
+++ boot0.s 1999/01/30 08:45:58
@@ -60,7 +60,8 @@
incb1(-0xe,_di_) # Sector number
jmpnwi(main-LOAD+ORIGIN) # To relocated code
-main: movbr1(_dl,_FAKE,_bp_) # Save drive number
+main: movb $0x80,%dl # Set drive number
+ movbr1(_dl,_FAKE,_bp_) # Save drive number
callwi(putn) # To new line
movwir(partbl,_bx) # Partition table
xorl %edx,%edx # Item
--
Robert Nordier
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Sat Jan 30 03:21:39 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id DAA13113
for freebsd-current-outgoing; Sat, 30 Jan 1999 03:21:39 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from solaris.matti.ee (solaris.matti.ee [194.126.98.135])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA13108
for <current@FreeBSD.ORG>; Sat, 30 Jan 1999 03:21:36 -0800 (PST)
(envelope-from vallo@myhakas.matti.ee)
Received: from myhakas.matti.ee (myhakas.matti.ee [194.126.114.87]) by solaris.matti.ee (8.8.8/8.8.8.s) with ESMTP id NAA18538; Sat, 30 Jan 1999 13:21:32 +0200 (EET)
Received: (from vallo@localhost)
by myhakas.matti.ee (8.9.1/8.9.1) id NAA25781;
Sat, 30 Jan 1999 13:21:32 +0200 (EET)
(envelope-from vallo)
Message-ID: <19990130132132.A25750@matti.ee>
Date: Sat, 30 Jan 1999 13:21:32 +0200
From: Vallo Kallaste <vallo@matti.ee>
To: Bruce Albrecht <bruce@zuhause.mn.org>
Cc: current@FreeBSD.ORG
Subject: Re: Ne2000 PCI Card
Reply-To: vallo@matti.ee
References: <199901282223.RAA32294@speed.rcc.on.ca> <14001.14864.712443.443655@zuhause.zuhause.mn.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.93.2i
In-Reply-To: <14001.14864.712443.443655@zuhause.zuhause.mn.org>; from Bruce Albrecht on Thu, Jan 28, 1999 at 10:33:20PM -0600
Organization: =?iso-8859-15?Q?AS_Matti_B=FCrootehnika?=
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
On Thu, Jan 28, 1999 at 10:33:20PM -0600, Bruce Albrecht <bruce@zuhause.mn.org> wrote:
> performance at 10 Mbps, but it's a real dog at 100 Mbps. I'm only
> able to achieve 45-50 Mbps throughput with a dual P6-200 machine, and
> it uses nearly 30% of the CPU to do it.
Hmm.. We tried the cards here and got ca 9MB/s over crosslinked
266Mhz Celerons. Well, the CPU load is quite high, about same you
indicated. For testing we used netperf from the ports.
--
Vallo Kallaste
vallo@matti.ee
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Sat Jan 30 03:37:50 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id DAA14099
for freebsd-current-outgoing; Sat, 30 Jan 1999 03:37:50 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from post.mail.demon.net (post-11.mail.demon.net [194.217.242.40])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA14094
for <current@freebsd.org>; Sat, 30 Jan 1999 03:37:48 -0800 (PST)
(envelope-from bsdcurrent@scratch.demon.co.uk)
Received: from [212.228.22.156] (helo=scratch.demon.co.uk)
by post.mail.demon.net with smtp (Exim 2.10 #2)
id 106Yia-0001lf-00; Sat, 30 Jan 1999 11:37:41 +0000
Message-ID: <arHAtNAtYfs2Ewxc@scratch.demon.co.uk>
Date: Fri, 29 Jan 1999 17:55:57 +0000
To: Alfred Perlstein <bright@hotjobs.com>
Cc: Rod Taylor <oscentral@usa.net>, current@FreeBSD.ORG
From: Tim Preece <bsdcurrent@scratch.demon.co.uk>
Subject: Re: Ne2000 PCI Card
References: <199901282223.RAA32294@speed.rcc.on.ca>
<Pine.BSF.4.05.9901281704550.81323-100000@bright.fx.genx.net>
In-Reply-To: <Pine.BSF.4.05.9901281704550.81323-100000@bright.fx.genx.net>
MIME-Version: 1.0
X-Mailer: Turnpike (32) Version 4.00 <2bL8TQCIEWg0B+1EtXWvseZtDP>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
In message <Pine.BSF.4.05.9901281704550.81323-100000@bright.fx.genx.net>
, Alfred Perlstein <bright@hotjobs.com> writes
>
>On Thu, 28 Jan 1999, Rod Taylor wrote:
>
>> I have 2 cheap 100mbit nics (rj45 only). Both use the ReaTek 8139 chipset
>> (from the best that I can tell). Both are PCI.
>
>...snip
>
>> Tried to get help in #freebsd in efnet, but no-one had suggestions that
>> helped me... (Thanks anyhow Xanne)
>
>compile a kernel with:
>
>device rl0
>
>that should work, and if you want to know why the cards are so cheap:
>
>/usr/src/sys/pci/if_rl.c
>
>wpaul explains it quite well. :)
>
>Alfred Perlstein - Programmer, HotJobs Inc. - www.hotjobs.com
>-- There are operating systems, and then there's FreeBSD.
>-- http://www.freebsd.org/ 4.0-current
>
>
>To Unsubscribe: send mail to majordomo@FreeBSD.org
>with "unsubscribe freebsd-current" in the body of the message
I had similar problems with I think the same card - certainly realtek
Either I had PNP modem working or ed1 realtek ethenet card
Problem was in the end in my BIOS, I had to enable all ports as PNP/PCI
as opposed to ISA/EISA and enable OS is PNP aware - AMI BIOS 1998
OK now, however I am having a few network problems but I do not think
that this could be the cause
--
Tim Preece
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Sat Jan 30 04:24:44 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id EAA20139
for freebsd-current-outgoing; Sat, 30 Jan 1999 04:24:44 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from solaris.matti.ee (solaris.matti.ee [194.126.98.135])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA20134
for <current@FreeBSD.ORG>; Sat, 30 Jan 1999 04:24:42 -0800 (PST)
(envelope-from vallo@myhakas.matti.ee)
Received: from myhakas.matti.ee (myhakas.matti.ee [194.126.114.87]) by solaris.matti.ee (8.8.8/8.8.8.s) with ESMTP id OAA20606; Sat, 30 Jan 1999 14:19:42 +0200 (EET)
Received: (from vallo@localhost)
by myhakas.matti.ee (8.9.1/8.9.1) id OAA25934;
Sat, 30 Jan 1999 14:19:38 +0200 (EET)
(envelope-from vallo)
Message-ID: <19990130141938.B25750@matti.ee>
Date: Sat, 30 Jan 1999 14:19:38 +0200
From: Vallo Kallaste <vallo@matti.ee>
To: John Birrell <jb@cimlogic.com.au>
Cc: current@FreeBSD.ORG
Subject: Re: btokup().. patch to STYLE(9) (fwd)
Reply-To: vallo@matti.ee
References: <19990129152838.L8473@freebie.lemis.com> <199901290526.QAA12656@cimlogic.com.au>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.93.2i
In-Reply-To: <199901290526.QAA12656@cimlogic.com.au>; from John Birrell on Fri, Jan 29, 1999 at 04:26:53PM +1100
Organization: =?iso-8859-15?Q?AS_Matti_B=FCrootehnika?=
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
On Fri, Jan 29, 1999 at 04:26:53PM +1100, John Birrell <jb@cimlogic.com.au> wrote:
> I can image a new subscriber to this list reading a few of these messages
> and thinking: "why would I want to use an OS developed by these people?".
>
> We spend so much of our time looking up our own collective asses searching
> for the meaning of life that it is no wonder FreeBSD doesn't feel like it
> has a clear direction for the future. All people seem to want to do is
> stomp on others who try to contribute something.
You have hit the nail by some means. I'm not developer by any
means, but I do follow strictly threads like this one. All the
conflicts and such give me a good overall picture about whats going
on and what I will expect in the near future. Project is like the
people are. Yes, threads like this likely form my attitude to
FreeBSD project and some people. I'm afraid, my english isn't good
enough to explain yet some thoughts :( Maybe this is even better to
not do it.
--
Vallo Kallaste
vallo@matti.ee
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Sat Jan 30 04:41:05 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id EAA21380
for freebsd-current-outgoing; Sat, 30 Jan 1999 04:41:05 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from janus.syracuse.net (janus.syracuse.net [205.232.47.15])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA21375
for <current@FreeBSD.ORG>; Sat, 30 Jan 1999 04:41:03 -0800 (PST)
(envelope-from green@unixhelp.org)
Received: from localhost (green@localhost)
by janus.syracuse.net (8.8.8/8.8.7) with ESMTP id HAA23177;
Sat, 30 Jan 1999 07:40:40 -0500 (EST)
Date: Sat, 30 Jan 1999 07:40:40 -0500 (EST)
From: Brian Feldman <green@unixhelp.org>
X-Sender: green@janus.syracuse.net
To: Greg Lehey <grog@lemis.com>
cc: Warner Losh <imp@village.org>, Julian Elischer <julian@whistle.com>,
current@FreeBSD.ORG
Subject: Re: btokup().. patch to STYLE(9) (fwd)
In-Reply-To: <19990130104943.W8473@freebie.lemis.com>
Message-ID: <Pine.BSF.4.05.9901300740170.22917-100000@janus.syracuse.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
On Sat, 30 Jan 1999, Greg Lehey wrote:
> On Friday, 29 January 1999 at 11:02:48 -0700, Warner Losh wrote:
> >> If I were working on this code written by someone else it'd leave my
> >> editor looking like the top example, that's for sure. I think that
> >> "How easy is it to edit a piece of code and still have it do what you
> >> expect" is an important consideration, because people DO edit things.
> >
> > Agreed.
> >
> >>> I do agree that complex things like:
> >>>
> >>> if (a | b & c % d ^ e)
> >>>
> >>> should really have some parents to show what is going on.
> >>
> >> I have NO idea of what that is doing and I have plans of looking it up in
> >> the book to work it out..
> >
> > Yes. I agree with that.
> > if (a | b & c % d ^ e)
> > should have been written as:
> > if (((a | (b & (c % d))) ^ e) != 0)
> > (then again, either way it is ugly code and should have comments).
>
> It's interesting that this whole argument has just addressed the
> syntax, and nobody has given any consideration to the semantics. In
> this example, all variables are a single character. Given the fact
> that this expression is probably indented 16 characters, there's a
> strong incentive to keep the variable names short, even at the expense
> of intelligibility. Consider one possible expansion
>
> if (((allocationfail | (IGNOREFAILUREMASK & (incount % BLKSIZE))) ^ failures) != 0)
>
> (yes, this still doesn't make sense, but I can't be bothered to look
> for something more appropriate) This is now 99 characters wide, and
> it's the kind of code which doesn't gain in legibility by being broken
> into multiple lines, especially if the indentation of the follow-on
> lines is independent of the structure of the expression. bde has made
> it clear he considers code more than 80 characters wide to be Evil.
> Question: how many people still limit their editor windows to 80
> characters?
I do; doesn't everyone?
>
> Greg
> --
> See complete headers for address, home page and phone numbers
> finger grog@lemis.com for PGP public key
>
> To Unsubscribe: send mail to majordomo@FreeBSD.org
> with "unsubscribe freebsd-current" in the body of the message
>
Brian Feldman _ __ ___ ___ ___
green@unixhelp.org _ __ ___ | _ ) __| \
http://www.freebsd.org/ _ __ ___ ____ | _ \__ \ |) |
FreeBSD: The Power to Serve! _ __ ___ ____ _____ |___/___/___/
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Sat Jan 30 04:46:03 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id EAA21795
for freebsd-current-outgoing; Sat, 30 Jan 1999 04:46:03 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from adelphi.physics.adelaide.edu.au (adelphi.physics.adelaide.edu.au [129.127.36.247])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA21778
for <current@freebsd.org>; Sat, 30 Jan 1999 04:46:00 -0800 (PST)
(envelope-from kkennawa@physics.adelaide.edu.au)
Received: from bragg (bragg [129.127.36.34])
by adelphi.physics.adelaide.edu.au (8.8.8/8.8.8/UofA-1.5) with SMTP id XAA19417;
Sat, 30 Jan 1999 23:15:53 +1030 (CST)
Received: from localhost by bragg; (5.65/1.1.8.2/05Aug95-0227PM)
id AA15458; Sat, 30 Jan 1999 23:15:52 +1030
Date: Sat, 30 Jan 1999 23:15:52 +1030 (CST)
From: Kris Kennaway <kkennawa@physics.adelaide.edu.au>
X-Sender: kkennawa@bragg
To: Matthew Dillon <dillon@apollo.backplane.com>
Cc: current@FreeBSD.ORG
Subject: Re: Tentitive fix for vn device
In-Reply-To: <199901300812.AAA88999@apollo.backplane.com>
Message-Id: <Pine.OSF.4.05.9901302311150.18962-100000@bragg>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
On Sat, 30 Jan 1999, Matthew Dillon wrote:
> This is a tentitive fix for the vn device problems reported earlier.
This fixes the problems I was having with vn devices - at least, I can once
again cvsup on a vn device, which was guaranteed to fail instantly before.
THanks!
Kris
-----
(ASP) Microsoft Corporation (MSFT) announced today that the release of its
productivity suite, Office 2000, will be delayed until the first quarter
of 1901.
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Sat Jan 30 05:20:48 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id FAA23891
for freebsd-current-outgoing; Sat, 30 Jan 1999 05:20:48 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA23886
for <current@freebsd.org>; Sat, 30 Jan 1999 05:20:47 -0800 (PST)
(envelope-from jkh@zippy.cdrom.com)
Received: from zippy.cdrom.com (localhost.cdrom.com [127.0.0.1])
by zippy.cdrom.com (8.9.2/8.9.1) with ESMTP id FAA91643
for <current@freebsd.org>; Sat, 30 Jan 1999 05:21:20 -0800 (PST)
To: current@FreeBSD.ORG
Subject: Even more interesting NFS problems..
Date: Sat, 30 Jan 1999 05:21:20 -0800
Message-ID: <91639.917702480@zippy.cdrom.com>
From: "Jordan K. Hubbard" <jkh@zippy.cdrom.com>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
Scenario: Two machines, releng3.freebsd.org (running 3.0-stable) and
current.freebsd.org (running 4.0-current). releng3 has all the disk
space and is the NFS server. current is an NFS client and uses
releng3 for its CVS repository, FTP snapshot stashing area, etc.
As of the day before yesterday, I started getting all manner of NFS
errors on "current" and checked the amd.conf file it was using.
Version 3 of NFS seemed to be the default (!) for amd so I changed
it to version 2 and rebooted both boxes. Still no change. When
doing things like a cvs update from current using the cvs repo
on releng3, I get this:
root@usw2-> cvup
U Makefile.inc1
U Makefile.upgrade
? make.out
U bin/rm/rm.1
cvs update: cannot open /home/ncvs/src/contrib/groff/devps/HNI,v: RPC struct is bad
That latter message is a new one in my experience. Anyone have any
ideas? I might also add that this exact same setup worked great back
when current.freebsd.org was running 3.0-current and
releng3.freebsd.org was releng22.freebsd.org, running 2.2.8-stable.
The only thing I changed were the OS versions and now we're also
SNAPless. :-(
- Jordan
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Sat Jan 30 06:59:01 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id GAA00945
for freebsd-current-outgoing; Sat, 30 Jan 1999 06:59:01 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from peach.ocn.ne.jp (peach.ocn.ne.jp [210.145.254.87])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA00938
for <freebsd-current@FreeBSD.ORG>; Sat, 30 Jan 1999 06:58:59 -0800 (PST)
(envelope-from dcs@newsguy.com)
Received: from newsguy.com by peach.ocn.ne.jp (8.9.1a/OCN) id XAA23825; Sat, 30 Jan 1999 23:58:46 +0900 (JST)
Message-ID: <36B31DAE.C138C2E0@newsguy.com>
Date: Sat, 30 Jan 1999 23:56:46 +0900
From: "Daniel C. Sobral" <dcs@newsguy.com>
X-Mailer: Mozilla 4.5 [en] (Win98; I)
X-Accept-Language: pt-BR,ja
MIME-Version: 1.0
To: Robert Nordier <rnordier@nordier.com>
CC: freebsd-current@FreeBSD.ORG
Subject: Re: Reading a text file with BTX
References: <199901300847.KAA00258@ceia.nordier.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
Robert Nordier wrote:
>
> Daniel C. Sobral wrote:
> >
> > Y'know, in my computer that F5 is "Drive 0", and the system will not
> > boot unless I select it first. Selecting it, makes the OSes boot and
> > F5 disappear.
>
> Try the following patch. You can use the utility
[...]
Right on the mark. BTW, my BIOS is set so the cd drive is searched
before the hd on boot. Could that be the cause?
--
Daniel C. Sobral (8-DCS)
dcs@newsguy.com
Would you mind not shooting at the thermonuclear weapons?
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Sat Jan 30 08:41:10 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id IAA08902
for freebsd-current-outgoing; Sat, 30 Jan 1999 08:41:10 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from cx757770-a.fed1.sdca.home.com (cx757770-a.fed1.sdca.home.com [24.0.167.56])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA08897
for <current@freebsd.org>; Sat, 30 Jan 1999 08:41:09 -0800 (PST)
(envelope-from daren@sefcik.cc)
Received: from localhost (daren@localhost)
by cx757770-a.fed1.sdca.home.com (8.9.1/8.9.1) with ESMTP id IAA12157
for <current@freebsd.org>; Sat, 30 Jan 1999 08:53:18 -0800 (PST)
Date: Sat, 30 Jan 1999 08:53:17 -0800 (PST)
From: Daren Sefcik <daren@sefcik.cc>
X-Sender: daren@cx757770-a.fed1.sdca.home.com
To: current@FreeBSD.ORG
Subject: lkm not working
Message-ID: <Pine.BSF.4.05.9901300851300.12154-100000@cx757770-a.fed1.sdca.home.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
I am now up to 4.0 and lkm is not working...
rover# modstat
modstat: /dev/lkm: Device not configured
I have not used it much but I know it worked with
my 3.0 system...any pointers would be great.
thanks,
Daren
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Sat Jan 30 08:47:23 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id IAA09937
for freebsd-current-outgoing; Sat, 30 Jan 1999 08:47:23 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from peach.ocn.ne.jp (peach.ocn.ne.jp [210.145.254.87])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA09932
for <current@FreeBSD.ORG>; Sat, 30 Jan 1999 08:47:21 -0800 (PST)
(envelope-from dcs@newsguy.com)
Received: from newsguy.com by peach.ocn.ne.jp (8.9.1a/OCN) id BAA03956; Sun, 31 Jan 1999 01:47:14 +0900 (JST)
Message-ID: <36B33777.90725FFA@newsguy.com>
Date: Sun, 31 Jan 1999 01:46:47 +0900
From: "Daniel C. Sobral" <dcs@newsguy.com>
X-Mailer: Mozilla 4.5 [en] (Win98; I)
X-Accept-Language: pt-BR,ja
MIME-Version: 1.0
To: Daren Sefcik <daren@sefcik.cc>
CC: current@FreeBSD.ORG
Subject: Re: lkm not working
References: <Pine.BSF.4.05.9901300851300.12154-100000@cx757770-a.fed1.sdca.home.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
Daren Sefcik wrote:
>
> I am now up to 4.0 and lkm is not working...
>
> rover# modstat
> modstat: /dev/lkm: Device not configured
>
> I have not used it much but I know it worked with
> my 3.0 system...any pointers would be great.
My guess: add "option lkm" to your kernel configuration file.
--
Daniel C. Sobral (8-DCS)
dcs@newsguy.com
Would you mind not shooting at the thermonuclear weapons?
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Sat Jan 30 08:54:54 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id IAA10557
for freebsd-current-outgoing; Sat, 30 Jan 1999 08:54:54 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from khavrinen.lcs.mit.edu (khavrinen.lcs.mit.edu [18.24.4.193])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA10552
for <current@FreeBSD.ORG>; Sat, 30 Jan 1999 08:54:53 -0800 (PST)
(envelope-from wollman@khavrinen.lcs.mit.edu)
Received: (from wollman@localhost)
by khavrinen.lcs.mit.edu (8.9.1/8.9.1) id LAA07382;
Sat, 30 Jan 1999 11:54:39 -0500 (EST)
(envelope-from wollman)
Date: Sat, 30 Jan 1999 11:54:39 -0500 (EST)
From: Garrett Wollman <wollman@khavrinen.lcs.mit.edu>
Message-Id: <199901301654.LAA07382@khavrinen.lcs.mit.edu>
To: Mark Newton <newton@atdot.dotat.org>
Cc: current@FreeBSD.ORG
Subject: *1 routines in /sys/kern
In-Reply-To: <199901300730.SAA20522@atdot.dotat.org>
References: <199901300730.SAA20522@atdot.dotat.org>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
<<On Sat, 30 Jan 1999 18:00:15 +1030 (CST), Mark Newton <newton@atdot.dotat.org> said:
> If I split sigaction(), sigsuspend(), sigpending(), sigprocmask() and
> sigaltstack() into front-end and back-end pieces a-la NetBSD so that
> emulator-specific signal semantics can be imposed without totally
> duplicating those routines inside the emulator (like I did with
> sendit() and recvit() for socket I/O), will anyone complain?
I'd say, ``go ahead''. But you should probably include a comment in
the source file indicating the reason for the split, so that someone
else maintaining the code can figure it out.
-GAWollman
--
Garrett A. Wollman | O Siem / We are all family / O Siem / We're all the same
wollman@lcs.mit.edu | O Siem / The fires of freedom
Opinions not those of| Dance in the burning flame
MIT, LCS, CRS, or NSA| - Susan Aglukark and Chad Irschick
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Sat Jan 30 09:30:13 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id JAA14235
for freebsd-current-outgoing; Sat, 30 Jan 1999 09:30:13 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from ceia.nordier.com (m1-52-dbn.dial-up.net [196.34.155.52])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA14206
for <freebsd-current@FreeBSD.ORG>; Sat, 30 Jan 1999 09:30:07 -0800 (PST)
(envelope-from rnordier@nordier.com)
Received: (from rnordier@localhost) by ceia.nordier.com (8.8.7/8.6.12) id TAA00662; Sat, 30 Jan 1999 19:28:59 +0200 (SAT)
From: Robert Nordier <rnordier@nordier.com>
Message-Id: <199901301728.TAA00662@ceia.nordier.com>
Subject: Re: Reading a text file with BTX
In-Reply-To: <36B31DAE.C138C2E0@newsguy.com> from "Daniel C. Sobral" at "Jan 30, 99 11:56:46 pm"
To: dcs@newsguy.com (Daniel C. Sobral)
Date: Sat, 30 Jan 1999 19:28:56 +0200 (SAT)
Cc: freebsd-current@FreeBSD.ORG
X-Mailer: ELM [version 2.4ME+ PL31 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
Daniel C. Sobral wrote:
> Robert Nordier wrote:
> >
> > Daniel C. Sobral wrote:
> > >
> > > Y'know, in my computer that F5 is "Drive 0", and the system will not
> > > boot unless I select it first. Selecting it, makes the OSes boot and
> > > F5 disappear.
> >
> > Try the following patch. You can use the utility
> [...]
>
> Right on the mark. BTW, my BIOS is set so the cd drive is searched
> before the hd on boot. Could that be the cause?
Seems a reasonable assumption, but I don't know for sure.
--
Robert Nordier
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Sat Jan 30 09:39:41 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id JAA15674
for freebsd-current-outgoing; Sat, 30 Jan 1999 09:39:41 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from nlsystems.com (nlsys.demon.co.uk [158.152.125.33])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA15646
for <current@freebsd.org>; Sat, 30 Jan 1999 09:39:35 -0800 (PST)
(envelope-from dfr@nlsystems.com)
Received: from localhost (dfr@localhost)
by nlsystems.com (8.9.2/8.8.5) with SMTP id RAA00753;
Sat, 30 Jan 1999 17:39:19 GMT
Date: Sat, 30 Jan 1999 17:39:13 +0000 (GMT)
From: Doug Rabson <dfr@nlsystems.com>
To: Daren Sefcik <daren@sefcik.cc>
cc: current@FreeBSD.ORG
Subject: Re: lkm not working
In-Reply-To: <Pine.BSF.4.05.9901300851300.12154-100000@cx757770-a.fed1.sdca.home.com>
Message-ID: <Pine.BSF.4.01.9901301737070.637-100000@herring.nlsystems.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
On Sat, 30 Jan 1999, Daren Sefcik wrote:
> I am now up to 4.0 and lkm is not working...
>
> rover# modstat
> modstat: /dev/lkm: Device not configured
>
> I have not used it much but I know it worked with
> my 3.0 system...any pointers would be great.
The lkm system has been superceded by a new kernel linker system called
KLD. The lkm support is still available by adding 'options LKM' to your
kernel configuration but since all standard lkms have been converted to
the new system, there should be no need.
To find the list of loaded modules in the new system, use kldstat.
--
Doug Rabson Mail: dfr@nlsystems.com
Nonlinear Systems Ltd. Phone: +44 181 442 9037
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Sat Jan 30 09:58:03 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id JAA17573
for freebsd-current-outgoing; Sat, 30 Jan 1999 09:58:03 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from frolic.no-support.loc (ppp36-6.hrz.uni-bielefeld.de [129.70.36.6])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA17497;
Sat, 30 Jan 1999 09:57:58 -0800 (PST)
(envelope-from bfischer@Techfak.Uni-Bielefeld.DE)
Received: from broccoli.no-support.loc (broccoli.no-support.loc [192.168.43.99])
by frolic.no-support.loc (8.9.2/8.8.8/Debian/GNU) with ESMTP id VAA00336;
Fri, 29 Jan 1999 21:16:18 +0100 (CET)
From: Bjoern Fischer <bfischer@Techfak.Uni-Bielefeld.DE>
Received: (from bjoern@localhost)
by broccoli.no-support.loc (8.9.2/8.9.2) id VAA00507;
Fri, 29 Jan 1999 21:15:55 +0100 (CET)
(envelope-from bjoern)
Date: Fri, 29 Jan 1999 21:15:55 +0100
To: Matthew Dillon <dillon@apollo.backplane.com>
Cc: Bjoern Fischer <bfischer@Techfak.Uni-Bielefeld.DE>,
freebsd-stable@FreeBSD.ORG, freebsd-current@FreeBSD.ORG
Subject: Re: nuts'n'bolts in vfs_bio
Message-ID: <19990129211554.A349@broccoli.no-support.loc>
References: <19990129094616.A555@frolic.no-support.loc> <199901290923.BAA75985@apollo.backplane.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.95i
In-Reply-To: <199901290923.BAA75985@apollo.backplane.com>; from Matthew Dillon on Fri, Jan 29, 1999 at 01:23:05AM -0800
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
On Fri, Jan 29, 1999 at 01:23:05AM -0800, Matthew Dillon wrote:
[...]
> Please try this diff ( against RELENG_3 kern/vfs_bio.c ) and
> tell me if it works.
>
> This is for STABLE only. Current already has this patch.
Hello Matthew,
thank you for reviewing vfs_bio.c. Your patch seems to
solve the problem with NFS writes remaining uncommitted.
At the time I can't see any NFS related data corruption.
But when shutting down the server it still panics complaining
about dirty bufs. (happens in 9 out of 10 times).
Bjoern
--
-----BEGIN GEEK CODE BLOCK-----
GCS d--(+) s++: a- C+++(-) UBL++++OSI++++$ P+++(-) L+++(-) !E W- N+ o>+
K- !w !O !M !V PS++ PE- PGP++ t+++ !5 X++ tv- b+++ D++ G e+ h-- y+
------END GEEK CODE BLOCK------
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Sat Jan 30 10:00:58 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id KAA18189
for freebsd-current-outgoing; Sat, 30 Jan 1999 10:00:58 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from lion.plab.ku.dk (lion.plab.ku.dk [130.225.105.49])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA18184
for <freebsd-current@FreeBSD.ORG>; Sat, 30 Jan 1999 10:00:57 -0800 (PST)
(envelope-from tobez@lion.plab.ku.dk)
Received: (from tobez@localhost)
by lion.plab.ku.dk (8.9.2/8.9.1) id TAA69056;
Sat, 30 Jan 1999 19:01:31 +0100 (CET)
To: freebsd-current@FreeBSD.ORG
Subject: sigpending with pthreads - bug or feature?
From: Anton Berezin <tobez@plab.ku.dk>
Date: 30 Jan 1999 19:01:31 +0100
Message-ID: <863e4s1vyc.fsf@lion.plab.ku.dk>
Lines: 43
X-Mailer: Gnus v5.3/Emacs 19.34
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
I don't know whether I should file a bug report on this issue.
Consider the following little program:
/* t.c */
#include <stdio.h>
#include <signal.h>
int
main( void)
{
sigset_t set;
sigpending( &set);
return 0;
}
Compiling and running it:
$ cc t.c
$ ./a.out
$
And trying to do the same with threads:
$ cc -pthread t.c
/var/tmp/ccs690421.o: In function `main':
/var/tmp/ccs690421.o(.text+0x1a): undefined reference to `sigpending'
$
However,
$ nm /usr/lib/libc_r.a | grep sigpending
sigpending.o:
00000040 T _thread_sys_sigpending
$
Apparently this one is not documented anywhere. Is it a missing alias
then? Or is one simply not allowed to use sigpending() with threads?
--
Anton Berezin <tobez@plab.ku.dk>
The Protein Laboratory, University of Copenhagen
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Sat Jan 30 10:33:38 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id KAA21798
for freebsd-current-outgoing; Sat, 30 Jan 1999 10:33:38 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from mirage.nlink.com.br (mirage.nlink.com.br [200.238.120.3])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA21781
for <freebsd-current@freebsd.org>; Sat, 30 Jan 1999 10:33:32 -0800 (PST)
(envelope-from paulo@nlink.com.br)
Received: from localhost (paulo@localhost)
by mirage.nlink.com.br (8.9.1a/8.9.1) with SMTP id PAA13398
for <freebsd-current@freebsd.org>; Sat, 30 Jan 1999 15:33:26 -0300 (EST)
Date: Sat, 30 Jan 1999 15:33:26 -0300 (EST)
From: Paulo Fragoso <paulo@nlink.com.br>
To: freebsd-current@FreeBSD.ORG
Subject: LINUX clone? sched_yield?
Message-ID: <Pine.BSF.3.96.990130152213.13061A-100000@mirage.nlink.com.br>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
Hi,
I'm trying to install StarOffice 5.0 in my FBSD-3.0-STABLE (26Jan1999).
When setup is running the kernel reports:
linux_clone(303): Not enabled
Jan 30 15:05:39 foker /kernel: cmd setup.bin pid 303 tried to use
non-present sched_yield
Jan 30 15:05:53 foker last message repeated 892 times
What's happening?
Many thanks,
Paulo Fragoso.
ps: I'm using one Multi-Processor motherboar with LX chip set, 2 PII
266MHz:
FreeBSD foker.nlink.com.br 3.0-STABLE FreeBSD 3.0-STABLE #1: Sat Jan 30
14:56:27 EST 1999
paulo@foker.nlink.com.br:/usr/src/sys/compile/KERNEL-SMP i386
Programming 24 pins in IOAPIC #0
FreeBSD/SMP: Multiprocessor motherboard
cpu0 (BSP): apic id: 0, version: 0x00040011, at 0xfee00000
cpu1 (AP): apic id: 1, version: 0x00040011, at 0xfee00000
io0 (APIC): apic id: 2, version: 0x00170011, at 0xfec00000
------
" ... Overall we've found FreeBSD to excel in performace, stability,
technical support, and of course price. Two years after discovering
FreeBSD, we have yet to find a reason why we switch to anything else"
-David Filo, Yahoo!
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Sat Jan 30 10:51:21 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id KAA23990
for freebsd-current-outgoing; Sat, 30 Jan 1999 10:51:21 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from dingo.cdrom.com (castles119.castles.com [208.214.165.119])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA23981
for <current@FreeBSD.ORG>; Sat, 30 Jan 1999 10:51:19 -0800 (PST)
(envelope-from mike@dingo.cdrom.com)
Received: from dingo.cdrom.com (localhost [127.0.0.1])
by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id KAA01004;
Sat, 30 Jan 1999 10:47:21 -0800 (PST)
(envelope-from mike@dingo.cdrom.com)
Message-Id: <199901301847.KAA01004@dingo.cdrom.com>
X-Mailer: exmh version 2.0.2 2/24/98
To: Mark Newton <newton@atdot.dotat.org>
cc: current@FreeBSD.ORG
Subject: Re: *1 routines in /sys/kern
In-reply-to: Your message of "Sat, 30 Jan 1999 18:00:15 +1030."
<199901300730.SAA20522@atdot.dotat.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Sat, 30 Jan 1999 10:47:21 -0800
From: Mike Smith <mike@smith.net.au>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
>
> If I split sigaction(), sigsuspend(), sigpending(), sigprocmask() and
> sigaltstack() into front-end and back-end pieces a-la NetBSD so that
> emulator-specific signal semantics can be imposed without totally
> duplicating those routines inside the emulator (like I did with
> sendit() and recvit() for socket I/O), will anyone complain?
I'd second Garrett on this; as long as it's documented somewhere
that the *1 routines are the "backends", it sounds eminently sensible.
--
\\ Sometimes you're ahead, \\ Mike Smith
\\ sometimes you're behind. \\ mike@smith.net.au
\\ The race is long, and in the \\ msmith@freebsd.org
\\ end it's only with yourself. \\ msmith@cdrom.com
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Sat Jan 30 10:55:00 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id KAA24553
for freebsd-current-outgoing; Sat, 30 Jan 1999 10:55:00 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from janus.syracuse.net (janus.syracuse.net [205.232.47.15])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA24538
for <freebsd-current@FreeBSD.ORG>; Sat, 30 Jan 1999 10:54:56 -0800 (PST)
(envelope-from green@unixhelp.org)
Received: from localhost (green@localhost)
by janus.syracuse.net (8.8.8/8.8.7) with ESMTP id NAA10268;
Sat, 30 Jan 1999 13:54:36 -0500 (EST)
Date: Sat, 30 Jan 1999 13:54:36 -0500 (EST)
From: Brian Feldman <green@unixhelp.org>
X-Sender: green@janus.syracuse.net
To: Paulo Fragoso <paulo@nlink.com.br>
cc: freebsd-current@FreeBSD.ORG
Subject: Re: LINUX clone? sched_yield?
In-Reply-To: <Pine.BSF.3.96.990130152213.13061A-100000@mirage.nlink.com.br>
Message-ID: <Pine.BSF.4.05.9901301353440.9981-100000@janus.syracuse.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
On Sat, 30 Jan 1999, Paulo Fragoso wrote:
> Hi,
>
> I'm trying to install StarOffice 5.0 in my FBSD-3.0-STABLE (26Jan1999).
> When setup is running the kernel reports:
>
> linux_clone(303): Not enabled
> Jan 30 15:05:39 foker /kernel: cmd setup.bin pid 303 tried to use
> non-present sched_yield
> Jan 30 15:05:53 foker last message repeated 892 times
>
> What's happening?
sched_yield() is a stub that informs you nicely that it doesn't exist :)
Use the options:
options "P1003_1B"
options "_KPOSIX_PRIORITY_SCHEDULING"
options "_KPOSIX_VERSION=199309L"
>
> Many thanks,
> Paulo Fragoso.
>
> ps: I'm using one Multi-Processor motherboar with LX chip set, 2 PII
> 266MHz:
>
> FreeBSD foker.nlink.com.br 3.0-STABLE FreeBSD 3.0-STABLE #1: Sat Jan 30
> 14:56:27 EST 1999
> paulo@foker.nlink.com.br:/usr/src/sys/compile/KERNEL-SMP i386
>
> Programming 24 pins in IOAPIC #0
> FreeBSD/SMP: Multiprocessor motherboard
> cpu0 (BSP): apic id: 0, version: 0x00040011, at 0xfee00000
> cpu1 (AP): apic id: 1, version: 0x00040011, at 0xfee00000
> io0 (APIC): apic id: 2, version: 0x00170011, at 0xfec00000
>
> ------
> " ... Overall we've found FreeBSD to excel in performace, stability,
> technical support, and of course price. Two years after discovering
> FreeBSD, we have yet to find a reason why we switch to anything else"
> -David Filo, Yahoo!
>
>
> To Unsubscribe: send mail to majordomo@FreeBSD.org
> with "unsubscribe freebsd-current" in the body of the message
>
Brian Feldman _ __ ___ ___ ___
green@unixhelp.org _ __ ___ | _ ) __| \
http://www.freebsd.org/ _ __ ___ ____ | _ \__ \ |) |
FreeBSD: The Power to Serve! _ __ ___ ____ _____ |___/___/___/
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Sat Jan 30 12:06:38 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id MAA04658
for freebsd-current-outgoing; Sat, 30 Jan 1999 12:06:38 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from ns.tar.com (ns.tar.com [204.95.187.2])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA04647
for <freebsd-current@FreeBSD.ORG>; Sat, 30 Jan 1999 12:06:36 -0800 (PST)
(envelope-from dick@ns.tar.com)
Received: (from dick@localhost)
by ns.tar.com (8.9.2/8.9.1) id OAA65009;
Sat, 30 Jan 1999 14:06:20 -0600 (CST)
(envelope-from dick)
Date: Sat, 30 Jan 1999 14:06:20 -0600
From: "Richard Seaman, Jr." <dick@tar.com>
To: Paulo Fragoso <paulo@nlink.com.br>
Cc: freebsd-current@FreeBSD.ORG
Subject: Re: LINUX clone? sched_yield?
Message-ID: <19990130140620.A29670@tar.com>
References: <Pine.BSF.3.96.990130152213.13061A-100000@mirage.nlink.com.br>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.95i
In-Reply-To: <Pine.BSF.3.96.990130152213.13061A-100000@mirage.nlink.com.br>; from Paulo Fragoso on Sat, Jan 30, 1999 at 03:33:26PM -0300
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
On Sat, Jan 30, 1999 at 03:33:26PM -0300, Paulo Fragoso wrote:
> Hi,
>
> I'm trying to install StarOffice 5.0 in my FBSD-3.0-STABLE (26Jan1999).
> When setup is running the kernel reports:
>
> linux_clone(303): Not enabled
> Jan 30 15:05:39 foker /kernel: cmd setup.bin pid 303 tried to use
> non-present sched_yield
> Jan 30 15:05:53 foker last message repeated 892 times
>
> What's happening?
You need to:
1) Upgrade your source tree to Jan 28 or later for 3.X or Jan 26
or later for 4.0 current, and "make world" and config and remake
and install a new kernel,
or
2) Take your existing source and add -DCOMPAT_LINUX_THREADS to
CFLAGS and COPTFLAGS in /etc/make.conf and make world and
remake and install your kernel.
Also, you need to add the posix priority extensions to your
kernel (see LINT).
Or, there is also more information at http://lt.tar.com
--
Richard Seaman, Jr. email: dick@tar.com
5182 N. Maple Lane phone: 414-367-5450
Chenequa WI 53058 fax: 414-367-5852
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Sat Jan 30 13:27:39 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id NAA16194
for freebsd-current-outgoing; Sat, 30 Jan 1999 13:27:39 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from khavrinen.lcs.mit.edu (khavrinen.lcs.mit.edu [18.24.4.193])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA16188
for <freebsd-current@FreeBSD.ORG>; Sat, 30 Jan 1999 13:27:37 -0800 (PST)
(envelope-from wollman@khavrinen.lcs.mit.edu)
Received: (from wollman@localhost)
by khavrinen.lcs.mit.edu (8.9.1/8.9.1) id QAA09734;
Sat, 30 Jan 1999 16:27:31 -0500 (EST)
(envelope-from wollman)
Date: Sat, 30 Jan 1999 16:27:31 -0500 (EST)
From: Garrett Wollman <wollman@khavrinen.lcs.mit.edu>
Message-Id: <199901302127.QAA09734@khavrinen.lcs.mit.edu>
To: Peter Dufault <dufault@hda.com>
Cc: freebsd-current@FreeBSD.ORG
Subject: Re: LINUX clone? sched_yield?
In-Reply-To: <Pine.BSF.4.05.9901301353440.9981-100000@janus.syracuse.net>
References: <Pine.BSF.3.96.990130152213.13061A-100000@mirage.nlink.com.br>
<Pine.BSF.4.05.9901301353440.9981-100000@janus.syracuse.net>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
<<On Sat, 30 Jan 1999 13:54:36 -0500 (EST), Brian Feldman <green@unixhelp.org> said:
> sched_yield() is a stub that informs you nicely that it doesn't exist :)
> Use the options:
> options "P1003_1B"
> options "_KPOSIX_PRIORITY_SCHEDULING"
> options "_KPOSIX_VERSION=199309L"
Peter: is there any harm in enabling these features permanently?
-GAWollman
--
Garrett A. Wollman | O Siem / We are all family / O Siem / We're all the same
wollman@lcs.mit.edu | O Siem / The fires of freedom
Opinions not those of| Dance in the burning flame
MIT, LCS, CRS, or NSA| - Susan Aglukark and Chad Irschick
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Sat Jan 30 13:55:11 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id NAA19850
for freebsd-current-outgoing; Sat, 30 Jan 1999 13:55:11 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from ns.mt.sri.com (sri-gw.MT.net [206.127.105.141])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA19832
for <current@FreeBSD.ORG>; Sat, 30 Jan 1999 13:55:04 -0800 (PST)
(envelope-from nate@mt.sri.com)
Received: from mt.sri.com (rocky.mt.sri.com [206.127.76.100])
by ns.mt.sri.com (8.8.8/8.8.8) with SMTP id OAA09954;
Sat, 30 Jan 1999 14:54:44 -0700 (MST)
(envelope-from nate@rocky.mt.sri.com)
Received: by mt.sri.com (SMI-8.6/SMI-SVR4)
id OAA11538; Sat, 30 Jan 1999 14:54:39 -0700
Date: Sat, 30 Jan 1999 14:54:39 -0700
Message-Id: <199901302154.OAA11538@mt.sri.com>
From: Nate Williams <nate@mt.sri.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
To: "Jordan K. Hubbard" <jkh@zippy.cdrom.com>
Cc: Warner Losh <imp@village.org>,
Matthew Dillon <dillon@apollo.backplane.com>,
Bruce Evans <bde@zeta.org.au>, current@FreeBSD.ORG
Subject: Re: c_caddr_t
In-Reply-To: <86708.917669156@zippy.cdrom.com>
References: <199901300350.UAA72862@harmony.village.org>
<86708.917669156@zippy.cdrom.com>
X-Mailer: VM 6.34 under 19.16 "Lille" XEmacs Lucid
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
> > Matt, get over it. bde didn't slam *YOU* in the commit messages. You
> > were never mentioned personally. Also, taking your complaint to
> > -current is not proper proceedure for handling grievances.
>
> While this is true, I think the overall point he made was reasonable
> considering how often Bruce has corrected others for "needless
> commentary" in the commit logs and I'd be happy to see everyone follow
> their own rules at the very least. :-)
C'mon Jordan. It wasn't needless commentary. He explained in *detail*
why the commit was wrong, and why it needed to be corrected. Anything
less would have ended up with a commit war.
Doesn't anyone care for 'correct' code anymore, or do we care more for
making people feel good about themselves and their compiler?
Nate
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Sat Jan 30 13:59:39 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id NAA20600
for freebsd-current-outgoing; Sat, 30 Jan 1999 13:59:39 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from hda.hda.com (hda-bicnet.bicnet.net [209.244.238.132] (may be forged))
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA20590
for <freebsd-current@FreeBSD.ORG>; Sat, 30 Jan 1999 13:59:33 -0800 (PST)
(envelope-from dufault@hda.hda.com)
Received: (from dufault@localhost)
by hda.hda.com (8.8.5/8.8.5) id QAA20095;
Sat, 30 Jan 1999 16:53:48 -0500 (EST)
From: Peter Dufault <dufault@hda.com>
Message-Id: <199901302153.QAA20095@hda.hda.com>
Subject: Re: LINUX clone? sched_yield?
In-Reply-To: <199901302127.QAA09734@khavrinen.lcs.mit.edu> from Garrett Wollman at "Jan 30, 99 04:27:31 pm"
To: wollman@khavrinen.lcs.mit.edu (Garrett Wollman)
Date: Sat, 30 Jan 1999 16:53:47 -0500 (EST)
Cc: dufault@hda.com, freebsd-current@FreeBSD.ORG
X-Mailer: ELM [version 2.4ME+ PL25 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
> <<On Sat, 30 Jan 1999 13:54:36 -0500 (EST), Brian Feldman <green@unixhelp.org> said:
>
> > sched_yield() is a stub that informs you nicely that it doesn't exist :)
> > Use the options:
> > options "P1003_1B"
> > options "_KPOSIX_PRIORITY_SCHEDULING"
> > options "_KPOSIX_VERSION=199309L"
>
> Peter: is there any harm in enabling these features permanently?
This bumps the version that the system says it is but I think the
pieces are in place. If Bruce has any POSIX tests he can rebuild
the system with POSIX_VERSION and _KPOSIX_VERSION set to 199309L
and see what happens. This is the right thing to do for -current,
and I have it turned on with a NO_KPOSIX_PRIORITY_SCHEDULING option
in the patches I'm about to commit.
Fixed-priority scheduling is broken in the SMP case and I'm planning
on disabling both RTPRIO and _KPOSIX_PRIORITY_SCHEDULING on SMP
unless one turns it on with RTPRIO_AND_SMP_ANYWAY. SMP and RTPRIO
function but not correctly. Programs that assume that the presence
of the header means the subsystem is present will fail on SMP the
way they fail now.
When my build world completes I'm planning on applying essentially
the patches that are in my home directory on freefall in PATCHES.sched.
Peter
--
Peter Dufault (dufault@hda.com) Realtime development, Machine control,
HD Associates, Inc. Safety critical systems, Agency approval
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Sat Jan 30 13:59:41 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id NAA20614
for freebsd-current-outgoing; Sat, 30 Jan 1999 13:59:41 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from bbaer.muenster.de (bbaer.muenster.de [195.202.32.20])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA20519
for <current@FreeBSD.ORG>; Sat, 30 Jan 1999 13:59:11 -0800 (PST)
(envelope-from andre@anneck.de)
From: andre@anneck.de
Received: from windemon (mueata-e1-wan208.citykom.de [195.202.34.208])
by bbaer.muenster.de (8.8.8/8.8.8) with SMTP id WAA11017
for <current@FreeBSD.ORG>; Sat, 30 Jan 1999 22:58:52 +0100
Message-Id: <199901302158.WAA11017@bbaer.muenster.de>
To: current@FreeBSD.ORG
Date: Sat, 30 Jan 1999 23:02:55 +0100
MIME-Version: 1.0
Content-type: text/plain; charset=US-ASCII
Content-transfer-encoding: 7BIT
X-mailer: Pegasus Mail for Win32 (v3.01d)
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Sat Jan 30 14:06:29 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id OAA22116
for freebsd-current-outgoing; Sat, 30 Jan 1999 14:06:29 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from arnold.neland.dk (mail.swimsuit.internet.dk [194.255.12.232])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA22109
for <current@FreeBSD.ORG>; Sat, 30 Jan 1999 14:06:26 -0800 (PST)
(envelope-from leifn@neland.dk)
Received: from localhost (localhost [127.0.0.1])
by arnold.neland.dk (8.9.2/8.9.1) with ESMTP id WAA21569;
Sat, 30 Jan 1999 22:58:18 +0100 (CET)
(envelope-from leifn@swimsuit.internet.dk)
Date: Sat, 30 Jan 1999 22:58:18 +0100 (CET)
From: Leif Neland <leifn@neland.dk>
X-Sender: leifn@arnold.neland.dk
To: Brian Somers <brian@Awfulhak.org>
cc: Leif Neland <leif@neland.dk>, current@FreeBSD.ORG
Subject: Re: PPP (userland) troubles ?
In-Reply-To: <199901290849.IAA00595@keep.lan.Awfulhak.org>
Message-ID: <Pine.BSF.4.05.9901302255250.21521-100000@arnold.neland.dk>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
On Fri, 29 Jan 1999, Brian Somers wrote:
> > Would it be possible to add an exponential delay when connecting fails for
> > either reason?
> >
> > I just received my specified phone-bill. It filled 42 pages, with hundreds
> > of calls with a duration of 17 seconds. (Because my modem needs to be
> > software-reset; I have mentioned this before).
> >
> I've added a
>
> set redial seconds[+add[-max]] attempts
>
> to my TODO list.
>
Thanks.
I have discovered the hangup chat-script; I now allways do a software
reset ATS38=4SWR after hangup. If you have made this hook to reset bad
modems, why didn't you tell me about it before? :-)
Now at least I get connect in the second attempt.
Leif
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Sat Jan 30 14:10:13 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id OAA22798
for freebsd-current-outgoing; Sat, 30 Jan 1999 14:10:13 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from skynet.ctr.columbia.edu (skynet.ctr.columbia.edu [128.59.64.70])
by hub.freebsd.org (8.8.8/8.8.8) with SMTP id OAA22773
for <current@freebsd.org>; Sat, 30 Jan 1999 14:10:07 -0800 (PST)
(envelope-from wpaul@skynet.ctr.columbia.edu)
Received: (from wpaul@localhost) by skynet.ctr.columbia.edu (8.6.12/8.6.9) id RAA00129 for current@freebsd.org; Sat, 30 Jan 1999 17:17:08 -0500
From: Bill Paul <wpaul@skynet.ctr.columbia.edu>
Message-Id: <199901302217.RAA00129@skynet.ctr.columbia.edu>
Subject: CAP port and non-IP multicast
To: current@FreeBSD.ORG
Date: Sat, 30 Jan 1999 17:17:07 -0500 (EST)
X-Mailer: ELM [version 2.4 PL24]
Content-Type: text
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
Somebody wrote me recently to tell me they were having trouble getting
the Columbia Appletalk package to work with a PCI ethernet card. Looking
through both the Columbia Appletalk code and the kernel, I think the
problem is a general one not necessarily related to a given ethernet
driver. I'm not sure what the proper fix is though.
The CAP code contains a module called cap60/support/ethertalk/bpfiltp.c
which contains library support code for libcap when the package is
built with EtherTalk Phase 2 support. As the name implies, it works
with BPF, but it also contains the pi_addmulti() routine. The aarpd
program uses this function to join the 09:00:07:ff:ff:ff multicast
group. Since this is not an IP multicast group, you have to specify
something besides AF_INET as the family when using SIOCADDMULTI to
join.
The question is, what should this something else be. In 2.2.x, you
have to use AF_UNSPEC, but in 3.x and up, you have to use AF_LINK.
The CAP port uses AF_UNSPEC in both cases, which is incorrect if
you're building the port on a 3.0 (or 4.0) host.
What's the right way to fix this? There are really two possibilities:
1) change bpfiltp.c so that it conditionally uses AF_UNSPEC or AF_LINK
depending on the OS release on which the port is being compiled, or
2) change sys/net/if_ethersubr.c so that it treats AF_UNSPEC and
AF_LINK the same. I expect changing the CAP code would be the more
'politically correct' approach, but it doesn't seem unreasonable to
allow backwards compatibility in the kernel code either.
-Bill
--
=============================================================================
-Bill Paul (212) 854-6020 | System Manager, Master of Unix-Fu
Work: wpaul@ctr.columbia.edu | Center for Telecommunications Research
Home: wpaul@skynet.ctr.columbia.edu | Columbia University, New York City
=============================================================================
"It is not I who am crazy; it is I who am mad!" - Ren Hoek, "Space Madness"
=============================================================================
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Sat Jan 30 14:50:06 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id OAA29728
for freebsd-current-outgoing; Sat, 30 Jan 1999 14:50:06 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from sand2.sentex.ca (sand2.sentex.ca [209.167.248.3])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA29623
for <current@freebsd.org>; Sat, 30 Jan 1999 14:50:00 -0800 (PST)
(envelope-from mike@sentex.net)
Received: from gravel (ospf-wat.sentex.net [209.167.248.81])
by sand2.sentex.ca (8.8.8/8.8.8) with SMTP id RAA24449
for <current@freebsd.org>; Sat, 30 Jan 1999 17:49:58 -0500 (EST)
(envelope-from mike@sentex.net)
Message-Id: <4.1.19990130174940.05433190@granite.sentex.ca>
X-Sender: mdtancsa@granite.sentex.ca
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.1
Date: Sat, 30 Jan 1999 17:56:50 -0500
To: current@FreeBSD.ORG
From: Mike Tancsa <mike@sentex.net>
Subject: file: table is full ?
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
I have a 3.0 STABLE box that under heavy smtp activity is getting
Jan 29 21:37:05 ns3 /kernel: file: table is f
Jan 29 21:37:05 ns3 /kernel: ull
Jan 29 21:37:05 ns3 /kernel: file: table is full
I have maxusers set to 128
ns3# sysctl -a | grep -i files
kern.maxfiles: 4136
kern.maxfilesperproc: 4136
Is it really running out of file descriptors, or is it something else ? Am
I better off to increase maxusers in the kernel, or adjust other settings ?
Frankly I am a little suprised of there being that many open files as I
have other servers that burst to busier activity than this one, and that
max open files are nowhere near that. Granted, those are 2.2-STALBE systems.
---Mike
**********************************************************************
Mike Tancsa, Network Admin * mike@sentex.net
Sentex Communications Corp, * http://www.sentex.net/mike
Cambridge, Ontario * 01.519.651.3400
Canada *
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Sat Jan 30 15:10:09 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id PAA02429
for freebsd-current-outgoing; Sat, 30 Jan 1999 15:10:09 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from allegro.lemis.com (allegro.lemis.com [192.109.197.134])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA02396
for <freebsd-current@FreeBSD.ORG>; Sat, 30 Jan 1999 15:10:03 -0800 (PST)
(envelope-from grog@freebie.lemis.com)
Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137])
by allegro.lemis.com (8.9.1/8.9.0) with ESMTP id JAA10306;
Sun, 31 Jan 1999 09:39:58 +1030 (CST)
Received: (from grog@localhost)
by freebie.lemis.com (8.9.2/8.9.0) id JAA57388;
Sun, 31 Jan 1999 09:39:52 +1030 (CST)
Date: Sun, 31 Jan 1999 09:39:52 +1030
From: Greg Lehey <grog@lemis.com>
To: Chris Knight <fbsd-cur@ghostwheel.com>
Cc: freebsd-current@FreeBSD.ORG
Subject: Re: Why doesn't Vinum start automatically?
Message-ID: <19990131093951.G8473@freebie.lemis.com>
References: <4.1.19990129224142.0098b100@pop2.ghostwheel.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.95.1i
In-Reply-To: <4.1.19990129224142.0098b100@pop2.ghostwheel.com>; from Chris Knight on Fri, Jan 29, 1999 at 10:41:52PM -0800
WWW-Home-Page: http://www.lemis.com/~grog
Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia
Phone: +61-8-8388-8286
Fax: +61-8-8388-8725
Mobile: +61-41-739-7062
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
On Friday, 29 January 1999 at 22:41:52 -0800, Chris Knight wrote:
> There have been changes to rc and rc.conf lately to autostart Vinum. But
> on my system it does not auto load at start and I wind up manually loading
> the module, reading the config and mounting the volume. Any help if
> figuring out why this is not working would be appreciated.
As you say, it's happened lately. But you don't say what version
you're running. What you show below is not the latest version.
>
> rc.conf now sets a variable with the drives from to read the config:
>
> vinum_slices="/dev/da1 /dev/da2 /dev/da3 /dev/da4"
>
> and rc checks for this variable and loads vinum if it is set:
>
> if [ -n "$vinum_slices" ]; then
> if [ -r /modules/vinum.ko ]; then # jkh paranoia
> kldload vinum
> vinum read $vinum_slices
> else
> echo "Can't find /modules/vinum.ko"
> fi
> fi
In -CURRENT it is now:
if [ "X$skip_diskconf" != "XYES" -a -n "$vinum_slices" ]; then
vinum read $vinum_slices
fi
> Any ideas why this isn't working? Is it working in -current but not -stable?
It should work, but it has the big problem that it will then try to
create devices in /dev, which is read-only. This is usually only a
cosmetic problem (the devices should already exist if you closed down
properly), but it means more work is coming. Probably I'll simplify
it to:
if [ "X$skip_diskconf" != "XYES" -a "X$run_vinum" = "YES" ]; then
vinum start
fi
I'd be interested to hear what problems you have, though.
Greg
--
See complete headers for address, home page and phone numbers
finger grog@lemis.com for PGP public key
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Sat Jan 30 15:23:49 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id PAA04121
for freebsd-current-outgoing; Sat, 30 Jan 1999 15:23:49 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA04107
for <current@freebsd.org>; Sat, 30 Jan 1999 15:23:47 -0800 (PST)
(envelope-from jdp@polstra.com)
Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13])
by wall.polstra.com (8.9.1/8.9.1) with ESMTP id PAA23163;
Sat, 30 Jan 1999 15:23:45 -0800 (PST)
(envelope-from jdp@polstra.com)
From: John Polstra <jdp@polstra.com>
Received: (from jdp@localhost)
by vashon.polstra.com (8.9.1/8.9.1) id PAA01841;
Sat, 30 Jan 1999 15:23:45 -0800 (PST)
(envelope-from jdp@polstra.com)
Date: Sat, 30 Jan 1999 15:23:45 -0800 (PST)
Message-Id: <199901302323.PAA01841@vashon.polstra.com>
To: kkennawa@physics.adelaide.edu.au
Subject: Re: Tentitive fix for vn device
Newsgroups: polstra.freebsd.current
In-Reply-To: <Pine.OSF.4.05.9901302311150.18962-100000@bragg>
Organization: Polstra & Co., Seattle, WA
Cc: current@FreeBSD.ORG
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
In article <Pine.OSF.4.05.9901302311150.18962-100000@bragg>,
Kris Kennaway <kkennawa@physics.adelaide.edu.au> wrote:
>
> This fixes the problems I was having with vn devices - at least, I can once
> again cvsup on a vn device, which was guaranteed to fail instantly before.
That's my baby, the ultimate kernel test. I feel so proud. :-)
John
--
John Polstra jdp@polstra.com
John D. Polstra & Co., Inc. Seattle, Washington USA
"Nobody ever went broke underestimating the taste of the American public."
-- H. L. Mencken
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Sat Jan 30 15:27:14 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id PAA04452
for freebsd-current-outgoing; Sat, 30 Jan 1999 15:27:14 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA04441
for <current@freebsd.org>; Sat, 30 Jan 1999 15:27:10 -0800 (PST)
(envelope-from jdp@polstra.com)
Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13])
by wall.polstra.com (8.9.1/8.9.1) with ESMTP id PAA23194;
Sat, 30 Jan 1999 15:27:09 -0800 (PST)
(envelope-from jdp@polstra.com)
From: John Polstra <jdp@polstra.com>
Received: (from jdp@localhost)
by vashon.polstra.com (8.9.1/8.9.1) id PAA01878;
Sat, 30 Jan 1999 15:27:09 -0800 (PST)
(envelope-from jdp@polstra.com)
Date: Sat, 30 Jan 1999 15:27:09 -0800 (PST)
Message-Id: <199901302327.PAA01878@vashon.polstra.com>
To: jkh@zippy.cdrom.com
Subject: Re: Even more interesting NFS problems..
Newsgroups: polstra.freebsd.current
In-Reply-To: <91639.917702480@zippy.cdrom.com>
Organization: Polstra & Co., Seattle, WA
Cc: current@FreeBSD.ORG
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
In article <91639.917702480@zippy.cdrom.com>,
Jordan K. Hubbard <jkh@zippy.cdrom.com> wrote:
>
> As of the day before yesterday, I started getting all manner of NFS
> errors on "current" and checked the amd.conf file it was using.
> Version 3 of NFS seemed to be the default (!) for amd so I changed
> it to version 2 and rebooted both boxes. Still no change.
Make sure you're using the right syntax in your amd.map file. It
changed a few months ago. Use "proto=udp,vers=2".
John
--
John Polstra jdp@polstra.com
John D. Polstra & Co., Inc. Seattle, Washington USA
"Nobody ever went broke underestimating the taste of the American public."
-- H. L. Mencken
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Sat Jan 30 15:39:09 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id PAA05814
for freebsd-current-outgoing; Sat, 30 Jan 1999 15:39:09 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from liquid.tpb.net (drum-n-bass.party-animals.com [194.134.94.34])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA05808
for <current@FreeBSD.ORG>; Sat, 30 Jan 1999 15:39:05 -0800 (PST)
(envelope-from niels@bakker.net)
Received: from localhost (niels@localhost)
by liquid.tpb.net (8.9.1a/8.8.8/Debian/GNU) with SMTP id AAA26713;
Sun, 31 Jan 1999 00:38:50 +0100
Date: Sun, 31 Jan 1999 00:38:49 +0100 (CET)
From: N <niels@bakker.net>
To: Mike Tancsa <mike@sentex.net>
cc: current@FreeBSD.ORG
Subject: Re: file: table is full ?
In-Reply-To: <4.1.19990130174940.05433190@granite.sentex.ca>
Message-ID: <990131003356.26537A-100000@liquid.tpb.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
Quoth Mike Tancsa:
> Jan 29 21:37:05 ns3 /kernel: file: table is full
>
> I have maxusers set to 128
> ns3# sysctl -a | grep -i files
> kern.maxfiles: 4136
> kern.maxfilesperproc: 4136
Try running `pstat -T' and see what number of file descriptors is
generally in use.
FYI, I've had to bump it up to 16384 on a news server; 8192 wasn't enough
during peak times.
I have this as /usr/local/etc/rc.d/0sysctl.sh (the 0 so it gets run first
during boot, before other daemons get started):-
#!/bin/sh
#
sysctl -w kern.maxfiles=16384
sysctl -w net.inet.tcp.always_keepalive=1
sysctl -w net.inet.tcp.keepidle=1800
You probably won't need to increase kern.maxfilesperproc; each sendmail
process typically has < 10 fd's open (log, network connection, two queue
files in /var/spool/mqueue, pipes to delivery agent).
-- Niels.
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Sat Jan 30 16:04:13 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id QAA08777
for freebsd-current-outgoing; Sat, 30 Jan 1999 16:04:13 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from h24-64-221-247.gv.wave.shaw.ca ([24.64.221.247])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA08729
for <current@freebsd.org>; Sat, 30 Jan 1999 16:04:08 -0800 (PST)
(envelope-from jake@h24-64-221-247.gv.wave.shaw.ca)
Received: from h24-64-221-247.gv.wave.shaw.ca (localhost [127.0.0.1])
by h24-64-221-247.gv.wave.shaw.ca (8.9.2/8.9.2) with ESMTP id QAA00500;
Sat, 30 Jan 1999 16:03:48 -0800 (PST)
(envelope-from jake@h24-64-221-247.gv.wave.shaw.ca)
Message-Id: <199901310003.QAA00500@h24-64-221-247.gv.wave.shaw.ca>
X-Mailer: exmh version 2.0.2 2/24/98
To: Greg Lehey <grog@lemis.com>
cc: current@FreeBSD.ORG
Subject: Re: Why doesn't Vinum start automatically?
In-reply-to: Your message of "Sun, 31 Jan 1999 09:39:52 +1030."
<19990131093951.G8473@freebie.lemis.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Sat, 30 Jan 1999 16:03:48 -0800
From: Jake <jake@checker.org>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
> In -CURRENT it is now:
>
> if [ "X$skip_diskconf" != "XYES" -a -n "$vinum_slices" ]; then
> vinum read $vinum_slices
> fi
Has this been fixed in -stable?
There was the problem of $vinum_slices not being initialized
because it was being used before rc.conf had been sourced.
>
> > Any ideas why this isn't working? Is it working in -current but not -stable?
>
This led me to believe that he was running -stable and simply
posted to the wrong group.
The 'suck in rc.conf' part was moved to the top of rc after the split,
so i think this is the problem.
IMHO this should be back-ported to stable; seems safe enough to source
rc.conf before mounting non-root filesystems. My system isn't mission
critical or anything, but I haven't run into any gotchas.
Cheers... great project Greg!
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Sat Jan 30 16:53:57 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id QAA15733
for freebsd-current-outgoing; Sat, 30 Jan 1999 16:53:57 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from allegro.lemis.com (allegro.lemis.com [192.109.197.134])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA15728
for <current@freebsd.org>; Sat, 30 Jan 1999 16:53:53 -0800 (PST)
(envelope-from grog@freebie.lemis.com)
Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137])
by allegro.lemis.com (8.9.1/8.9.0) with ESMTP id LAA10711;
Sun, 31 Jan 1999 11:23:44 +1030 (CST)
Received: (from grog@localhost)
by freebie.lemis.com (8.9.2/8.9.0) id LAA57889;
Sun, 31 Jan 1999 11:23:41 +1030 (CST)
Date: Sun, 31 Jan 1999 11:23:41 +1030
From: Greg Lehey <grog@lemis.com>
To: Jake <jake@checker.org>
Cc: current@FreeBSD.ORG
Subject: Re: Why doesn't Vinum start automatically?
Message-ID: <19990131112340.M8473@freebie.lemis.com>
References: <19990131093951.G8473@freebie.lemis.com> <199901310003.QAA00500@h24-64-221-247.gv.wave.shaw.ca>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.95.1i
In-Reply-To: <199901310003.QAA00500@h24-64-221-247.gv.wave.shaw.ca>; from Jake on Sat, Jan 30, 1999 at 04:03:48PM -0800
WWW-Home-Page: http://www.lemis.com/~grog
Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia
Phone: +61-8-8388-8286
Fax: +61-8-8388-8725
Mobile: +61-41-739-7062
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
On Saturday, 30 January 1999 at 16:03:48 -0800, Jake wrote:
>> In -CURRENT it is now:
>>
>> if [ "X$skip_diskconf" != "XYES" -a -n "$vinum_slices" ]; then
>> vinum read $vinum_slices
>> fi
>
> Has this been fixed in -stable?
No.
> There was the problem of $vinum_slices not being initialized
> because it was being used before rc.conf had been sourced.
>
>>> Any ideas why this isn't working? Is it working in -current but not -stable?
>
> This led me to believe that he was running -stable and simply
> posted to the wrong group.
Yes, I think you must be right.
> The 'suck in rc.conf' part was moved to the top of rc after the split,
> so i think this is the problem.
>
> IMHO this should be back-ported to stable; seems safe enough to
> source rc.conf before mounting non-root filesystems. My system
> isn't mission critical or anything, but I haven't run into any
> gotchas.
I can't see any way that this could compromise the stability of
-STABLE, so I agree. Peter committed the change to -CURRENT, so I'll
leave it to him.
Greg
--
See complete headers for address, home page and phone numbers
finger grog@lemis.com for PGP public key
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Sat Jan 30 19:43:27 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id TAA01419
for freebsd-current-outgoing; Sat, 30 Jan 1999 19:43:27 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA01411
for <current@FreeBSD.ORG>; Sat, 30 Jan 1999 19:43:26 -0800 (PST)
(envelope-from jkh@zippy.cdrom.com)
Received: from zippy.cdrom.com (localhost.cdrom.com [127.0.0.1])
by zippy.cdrom.com (8.9.2/8.9.1) with ESMTP id TAA98220;
Sat, 30 Jan 1999 19:43:44 -0800 (PST)
To: Greg Lehey <grog@lemis.com>
cc: Jake <jake@checker.org>, current@FreeBSD.ORG
Subject: Re: Why doesn't Vinum start automatically?
In-reply-to: Your message of "Sun, 31 Jan 1999 11:23:41 +1030."
<19990131112340.M8473@freebie.lemis.com>
Date: Sat, 30 Jan 1999 19:43:43 -0800
Message-ID: <98217.917754223@zippy.cdrom.com>
From: "Jordan K. Hubbard" <jkh@zippy.cdrom.com>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
> I can't see any way that this could compromise the stability of
> -STABLE, so I agree. Peter committed the change to -CURRENT, so I'll
> leave it to him.
I'd prefer it if you did it - Peter is probably too busy to even
notice this request. :)
- Jordan
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Sat Jan 30 20:10:14 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id UAA04642
for freebsd-current-outgoing; Sat, 30 Jan 1999 20:10:14 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from relay.nuxi.com (nuxi.ucdavis.edu [169.237.7.38] (may be forged))
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA04617
for <current@FreeBSD.ORG>; Sat, 30 Jan 1999 20:10:08 -0800 (PST)
(envelope-from obrien@NUXI.com)
Received: (from obrien@localhost)
by relay.nuxi.com (8.9.1/8.9.1) id UAA66442;
Sat, 30 Jan 1999 20:09:58 -0800 (PST)
(envelope-from obrien)
Date: Sat, 30 Jan 1999 20:09:58 -0800
From: "David O'Brien" <obrien@NUXI.com>
To: "Jordan K. Hubbard" <jkh@zippy.cdrom.com>
Cc: current@FreeBSD.ORG
Subject: Re: Even more interesting NFS problems..
Message-ID: <19990130200958.B66257@relay.nuxi.com>
Reply-To: obrien@NUXI.com
References: <91639.917702480@zippy.cdrom.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.95i
In-Reply-To: <91639.917702480@zippy.cdrom.com>; from Jordan K. Hubbard on Sat, Jan 30, 1999 at 05:21:20AM -0800
X-Operating-System: FreeBSD 3.0-CURRENT
Organization: The NUXI BSD group
X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A
X-Pgp-Keyid: 34F9F9D5
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
> errors on "current" and checked the amd.conf file it was using.
> Version 3 of NFS seemed to be the default (!) for amd
Yes, to be consistent with the state of world WRT NFS. Or at least with
the leader -- Solaris. This has been the default in 3.0-C since the
am-utils import.
> it to version 2 and rebooted both boxes. Still no change. When
You could easily still be using TCP rather than UDP. Using "proto=X" and
"vers=Y" you can specify the version and protocol used, independent of
each other. X={tcp,udp} and Y={2,3}
"nfsv2" is an synonym for "proto=udp,vers=2".
Any bugs you expose would be of interested, of course.
--
-- David (obrien@NUXI.com -or- obrien@FreeBSD.org)
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Sat Jan 30 20:14:36 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id UAA05094
for freebsd-current-outgoing; Sat, 30 Jan 1999 20:14:36 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.26.10.9])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA05078
for <freebsd-current@FreeBSD.ORG>; Sat, 30 Jan 1999 20:14:30 -0800 (PST)
(envelope-from bde@godzilla.zeta.org.au)
Received: (from bde@localhost)
by godzilla.zeta.org.au (8.8.7/8.8.7) id PAA15601;
Sun, 31 Jan 1999 15:14:18 +1100
Date: Sun, 31 Jan 1999 15:14:18 +1100
From: Bruce Evans <bde@zeta.org.au>
Message-Id: <199901310414.PAA15601@godzilla.zeta.org.au>
To: dufault@hda.com, wollman@khavrinen.lcs.mit.edu
Subject: Re: LINUX clone? sched_yield?
Cc: freebsd-current@FreeBSD.ORG
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
>> > sched_yield() is a stub that informs you nicely that it doesn't exist :)
>> > Use the options:
>> > options "P1003_1B"
>> > options "_KPOSIX_PRIORITY_SCHEDULING"
>> > options "_KPOSIX_VERSION=199309L"
>>
>> Peter: is there any harm in enabling these features permanently?
There's a yield() syscall that is enabled permanently. Is there any
harm in untangling it from the POSIX sched_yield()? :-)
>This bumps the version that the system says it is but I think the
>pieces are in place. If Bruce has any POSIX tests he can rebuild
>the system with POSIX_VERSION and _KPOSIX_VERSION set to 199309L
I don't have any for P1003.1b, only the NIST ones for POSIX.1.
Bruce
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Sat Jan 30 21:25:24 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id VAA11787
for freebsd-current-outgoing; Sat, 30 Jan 1999 21:25:24 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from rebma.ghostwheel.com (rebma.ghostwheel.com [207.201.56.159])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA11780
for <freebsd-current@freebsd.org>; Sat, 30 Jan 1999 21:25:22 -0800 (PST)
(envelope-from fbsd-cur@ghostwheel.com)
Received: from avalon (avalon [207.201.56.88])
by rebma.ghostwheel.com (8.8.8/8.8.8) with SMTP id UAA18812
for <freebsd-current@freebsd.org>; Sat, 30 Jan 1999 20:59:50 -0800 (PST)
(envelope-from fbsd-cur@ghostwheel.com)
Message-Id: <4.1.19990130205600.009c4980@pop2.ghostwheel.com>
X-Sender: fbsd-cur@pop2.ghostwheel.com (Unverified)
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.1
Date: Sat, 30 Jan 1999 20:56:25 -0800
To: freebsd-current@FreeBSD.ORG
From: Chris Knight <fbsd-cur@ghostwheel.com>
Subject: Re: Why doesn't Vinum start automatically?
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
At 04:03 PM 1/30/99 -0800, you wrote:
>> > Any ideas why this isn't working? Is it working in -current but not
>-stable?
>>
>
>This led me to believe that he was running -stable and simply
>posted to the wrong group.
I am running -stable. I didn't 'exactly' post to the wrong group. I
posted to
-stable two days ago, and when I didn't get a repsonese I posted to -current
because I know that Greg reads -current. :)
>Cheers... great project Greg!
I second that! Vinum is a very slick module.
-ck
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Sat Jan 30 22:04:32 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id WAA15478
for freebsd-current-outgoing; Sat, 30 Jan 1999 22:04:32 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA15469
for <current@FreeBSD.ORG>; Sat, 30 Jan 1999 22:04:27 -0800 (PST)
(envelope-from jkh@zippy.cdrom.com)
Received: from zippy.cdrom.com (localhost.cdrom.com [127.0.0.1])
by zippy.cdrom.com (8.9.2/8.9.1) with ESMTP id WAA10969;
Sat, 30 Jan 1999 22:04:47 -0800 (PST)
To: obrien@NUXI.com
cc: current@FreeBSD.ORG
Subject: Re: Even more interesting NFS problems..
In-reply-to: Your message of "Sat, 30 Jan 1999 20:09:58 PST."
<19990130200958.B66257@relay.nuxi.com>
Date: Sat, 30 Jan 1999 22:04:46 -0800
Message-ID: <10965.917762686@zippy.cdrom.com>
From: "Jordan K. Hubbard" <jkh@zippy.cdrom.com>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
> Yes, to be consistent with the state of world WRT NFS. Or at least with
> the leader -- Solaris. This has been the default in 3.0-C since the
> am-utils import.
Yeah, well, amd is a whole other ball of wax. That's clearly broken
in both 3.0-stable and 4.0-current and we're going to have to revert
the last set of changes fairly soon, it's on my TODO list of things to
deal with.
> You could easily still be using TCP rather than UDP. Using "proto=X" and
> "vers=Y" you can specify the version and protocol used, independent of
> each other. X={tcp,udp} and Y={2,3}
> "nfsv2" is an synonym for "proto=udp,vers=2".
Yeah, I think that was in fact the problem here.
- Jordan
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message